Guardian Procedure Calls Reference Manual

Unable to communicate with the node where the process resides.10
Process is an I/O process, but the option to allow I/O processes was not selected.11
Limited information is returned for a named process that is not started, but the process name is reserved.13
Considerations
• To perform an indexed search, initialize search-index to 0D before issuing the first call.
• Errors 11 and 12 are not returned during an indexed search. Excluded I/O processes are
skipped over with no error reported.
• If PROCESS_GETPAIRINFO_ returns any value of error that indicates that no information is
being returned, the contents of all output parameters are undefined.
• The values returned to identify the primary and backup processes reflect the current view of
the operating system at the time that PROCESS_GETPAIRINFO_ was called. When the members
of a named process pair voluntarily switch responsibilities, the new primary process must call
the PROCESS_SETINFO_ procedure with the primary attribute to inform the operating system
of the pair's new state.
• The pair parameter is the only output parameter of interest that is returned for a named
process that is not started. A named process that is not started does not have any process
handles (primary, backup, or ancestor) or ancestor program file name associated with it.
• When certain error values are returned, a null process handle (-1 in each word) or an
undefined value is returned in one or more of the output process-handle parameters. The
error values and the affected output parameters are as follows:
output process-handle parameterserror
all are undefined.2
all are undefined.3
backup-processhandle is null.4
all are undefined.7
all are undefined.8
all are undefined.9
all are undefined.10
primary-processhandle, backup-processhandle, and ancst-processhandle are null.13
Example
error := PROCESS_GETPAIRINFO_ ( prochandle, , , primary, backup );
PROCESS_GETPAIRINFO_ Procedure 1049