Guardian Procedure Calls Reference Manual

PIN of backup process, if it is a process pair. (This is 0 if there is no backup.)[4].<8:15>
process-id of ancestor. Note that the process-id is a 4- word array of this form:[5:8]
Process name or creation timestamp[0:2]
Reserved[3].<0:3>
Processor number where the process is executing[3].<4:7>
PIN assigned by the operating system to identify the process in the processor[3].<8:15>
Condition Code Settings
indicates that the DCT in the given system cannot be accessed.< (CCL)
indicates that the GETPPDENTRY completed successfully.= (CCE)
indicates that the index is greater than the last entry in the DCT.> (CCG)
Considerations
• Checking the DCT entry
If index is not currently being used, GETPPDENTRY returns CCE and sets ppd to zeros. To
check for all conditions, an application could contain this code:
CALL GETPPDENTRY( INDEX^NUM , SYS^NUM , PROCESS^PAIR^DESCRIPT
);
IF < THEN ... ; ! system unavailable.
IF > THEN ! STOP, no more DCT entries available.
IF=AND PROCESS^PAIR^DESCRIPT THEN ... ! found an entry.
ELSE
! unused entry, try the next INDEX^NUM.
• Difference between GETPPDENTRY and LOOKUPPROCESSNAME
The difference between the GETPPDENTRY procedure and the LOOKUPPROCESSNAME
procedure is:
is primarily used to obtain a local or remote process pair description by its index into a
system table.
GETPPDENTRY
is primarily used to obtain a local or remote process pair description by its name.LOOKUPPROCESSNAME
• High-PIN considerations
If you call GETPPDENTRY for a named process pair that has a high-PIN process as the primary
or backup, the ppd array (ppd[0:8]) is returned filled with zeros.
If you call GETPPDENTRY for a named process pair that has a high-PIN process as the ancestor,
a synthetic process ID is returned in ppd[5:8]. A synthetic process ID contains a PIN value of
255 in place of a high-PIN value, which cannot be represented by eight bits.
GETPPDENTRY Procedure (Superseded by PROCESS_GETPAIRINFO_ Procedure) 667