Runtime for ClearPath OS 2200 Software Release Announcement

Restrictions and Known Limitations
Restriction on S_T_N Records in Memory
The feature is only active for the most common use of the S_T_N structure, namely the
storing of the record associated with GLB.WORK. It is not used for the storage of error
screens, Ispec data or PCE switch information as each of these cases should be low
frequency occurrence. To reserve memory for each of these S_T_N structures would use
a lot more memory and would be inconsistent with the current implementation, which
uses RDMS S_T_N/FCSS for these structures.
KEYONLY; Restrictions
The following points should be noted about use of the KEYONLY; command:
• The KEYONLY; command option must be included on the same line as the
DETERMINE; or LOOK.UP; command.
• LOOK.UP; retrievals can use the KEYONLY; command option only on Standard
Components.
• KEYONLY; is ignored for:
– Integrity systems
– Ispecs that require multiple RDMS tables
(FLAG commands to an Ispec (or EVENT) which are successfully read with
KEYONLY; will update the record retrieved with the KEYONLY.)
• If you reference a non-key data item it will contain high-values. The contents of nonkey
numeric data items may vary depending on the machine type. Therefore, access
to non-key data items, while syntactically valid, may produce unwanted and
unpredictable results.
• Runtime Test Environment 4R1 for ClearPath OS 2200 does not support KEYONLY;
on the 2200 platform.
LRSS Restrictions
A couple of points to note about use of the Remote Subroutine Server:
• Each LRSS Server can have up to a maximum of 10 concurrent activities servicing a
connection.
• The target subroutines cannot be in HVTIP libraries nor can they be Basic Mode
Routines.
• Dynamic Linking from a Bound Object Module places certain constraints on the
LRSS:
– Once the LRSS has associated itself with a particular file, subsequent calls
always search that file.
– The inability to unload Object Modules after a connection had been terminated
and, as a consequence, the LRSS server has to terminate after each connection
and be restarted. If this is not done, the size of each LRSS activity continues to
grow until the Exec detects a bounding violation.
5–2 78616414–000