Guardian Procedure Calls Reference Manual

error-detail
output
INT .EXT:ref:1
returns the error detail information returned from the backup process' call to
SEGMENT_ALLOCATE_, or one of these file-system errors:
Segment is not allocated by the primary or the segment ID is invalid.2
No message-system control blocks are available.30
There is no room in the process file segment (PFS) for a message buffer in either the backup or the primary.31
Unable to send to the backup.201
For information about the error values for which detail information can be returned, see the
returned value for SEGMENT_ALLOCATE_.
pin
input
INT:value
if present and not -1, requests allocation of a segment that is shared by the PIN method. pin
specifies the process identification number of the process that has previously allocated the
segment and with which the caller wishes to share the segment. The process designated by
pin must be in the same processor as the caller. Processes sharing a segment by this method
must reference the segment by the same segment-id.
If pin is specified, filename must be omitted.
Returned Value
INT
Outcome of the backup process' call to SEGMENT_ALLOCATE_. Any error returned to the backup
by SEGMENT_ALLOCATE_ is returned here. For a list of possible values, see the returned value
for SEGMENT_ALLOCATE_.
Considerations
• The segment-size, segment-type, max-size, and alloc-options parameters of
SEGMENT_ALLOCATE_ are not supported in SEGMENT_ALLOCATE_CHKPT_ because the
values for the primary process' segment are used.
• A segment with the same segment ID must be allocated in the primary process before the call
to SEGMENT_ALLOCATE_CHKPT_.
• If the filename parameter is provided, that file name is used by SEGMENT_ALLOCATE_ in
the backup process; otherwise, no file name parameter is passed to SEGMENT_ALLOCATE_
in the backup process.
• If you use the pin parameter, set it carefully because the PIN might not be the same on the
backup processor. You must determine the correct PIN for the backup processor.
• If the segment is not read-only, the swap file name must be different on the backup and primary
processors. If the same file name is given, allocation in the backup fails because swap files
cannot be shared between processors.
• Nonexisting temporary swap file
If a shared segment is being allocated and only a volume name is supplied in the filename
parameter, then the complete file name of the temporary file created by
SEGMENT_ALLOCATE_CHKPT_ can be obtained from a subsequent call to
SEGMENT_GETBACKUPINFO_.
1274 Guardian Procedure Calls (S)