Guardian Procedure Calls Reference Manual

Wait on LINSP (Inspect event)<11>
Wait on LCAN (message system: cancel)<12>
Wait on LDONE (message system: done)<13>
Wait on LTMF (TMF request)<14>
Wait on LREQ (message system: request)<15>
The bits in the wait field are numbered from left to right. Thus, if octal 3 (%003) is returned,
it means that bits 14 and 15 are equal to 1.
• 32: process state
returns the state of the process. The bits are defined as follows, where 0 refers to the high-order
bit:
Privileged process<0>
Process is waiting for memory manager service, probably for a page fault.<1>
Process is on the ready list. See the discussion of "ready" below.<2>
System process<3>
(reserved)<4:5>
Memory access breakpoint in system code<6>
Process not accepting any messages<7>
Temporary system process<8>
Process has logged on (called USER_AUTHENTICATE_ or VERIFYUSER).<9>
In a pending process state<10>
The process state, where:<11:15>
starting0
unallocated process1
runnable (OSS process state equivalent is CONT)2
suspended (OSS process state equivalent is STOP)3
(reserved)4
Debug breakpoint5
Debug trap or signal6
Debug request7
Inspect memory-access breakpoint8
Inspect breakpoint9
Inspect trap or signal10
Inspect request11
saveabend12
terminating13
XIO initialization (not applicable on G-series RVUs)14
The OSS zombie process state has no Guardian equivalent.
This attribute and the process state attribute (10) return the same information for bits <11:15>.
The “ready list” mechanism and the definition of “ready to run” are implementation-dependent.
In general, a ready process is waiting its turn for a processor. However, on TNS/R systems,
a process is also deemed ready while it is running or servicing a page fault. On H-series
TNS/E systems prior to T9050H02^AXH, a process is also deemed ready if it is running. On
1028 Guardian Procedure Calls (P)