Guardian Procedure Calls Reference Manual

The segment-id is missing.29
No message-system control blocks available.30
Cannot use the PFS, or there is no room in the PFS for a message buffer in either the backup or the
primary.
31
Unable to LINK to the backup.201
Condition Code Settings
is set if the error parameter is missing, or there is a bounds error on the error parameter.< (CCL)
is set by all other errors (see the error parameter).= (CCE)
is never returned from this procedure.> (CCG)
Considerations
• The segment-size parameter of ALLOCATESEGMENT is not supported because the size
of the primary process' segment is used.
• An extended data segment with the same segment ID must be previously allocated in the
primary process; that is, before the call to CHECKALLOCATESEGMENT.
• If the file-name parameter is provided, that file name is used by ALLOCATESEGMENT in
the backup process; otherwise, no file-name parameter is passed to ALLOCATESEGMENT in
the backup process.
• If the pin-and-flags parameter is omitted, the default value is used (%040000).
• Be careful when using the pin-and-flags parameter. The flag settings should be the same
as the flag settings used when the extended data segment was allocated by the primary
process. CHECKALLOCATESEGMENT does not check the flag settings; the information is no
longer available.
If a PIN is specified, assign it carefully, because the PIN may not necessarily be the same on
the backup processor. You must determine the correct PIN for the backup processor.
• If the extended data segment is not read-only, the swap file name must be different on the
backup and primary processors because swap files cannot be shared between processors.
An error is returned from ALLOCATESEGMENT on the backup.
• Nonexisting temporary swap file
If a shared segment is being allocated (pin-and-flags bits <3:2> not equal to 0), and a
volume name only is supplied in the file-name parameter, then the complete file name of
the temporary file created by CHECKALLOCATESEGMENT is returned.
• Swap file extent allocation
If an extensible segment is being created, then only one extent of the swap file is allocated
when CHECKALLOCATESEGMENT returns.
• Segment sharing
Subject to security requirements, a process can share a segment with another process running
on the same processor. For example, process $X can share a segment with any of these
processes on the same processor:
◦ Any process that has the same process access ID (PAID)
◦ Any process that has the same group ID, if $X is the group manager (n,255)
◦ Any process, if $X is the super ID (255,255)
130 Guardian Procedure Calls (C)