Guardian Procedure Calls Reference Manual

• All returned file names are fully qualified.
• When using PROCESS_GETINFOLIST_ procedure, if you want to get information on every
process in the processor, specify a search criteria that will find every process. For example,
specify Search Attribute Code 9 with 0 as the search value. Information will be returned for
all processes because all processes have a priority that is greater than or equal to 0.
OSS Considerations
• The PROCESS_GETINFOLIST_ procedure returns as many complete sets of values as will fit in
the ret-values-list buffer; it returns no partial sets. In particular, the OSS attributes OSS
controlling terminal (27), OSS program pathname (93), and absolute OSS program pathname
(158) can return large amounts of information. The ret-values-list buffer must be large
enough to accommodate all the information requested.
• To retrieve the corresponding process handle of an OSS process ID, specify the desired OSS
process ID in the oss-pid parameter, specify the process handle attribute code (48) in the
ret-attr-list parameter, and search for only the specified OSS process ID by setting the
srch-option parameter to 3. Note that an OSS process can use a number of process
handles during its lifetime.
• The OSS CONT process state is equivalent to the Guardian runnable process state. The OSS
STOP process state is equivalent to the Guardian suspend process state. The OSS zombie
process state has no Guardian equivalent.
• The OSS attributes OSS controlling terminal (27) and OSS program pathname (93) can be
used only on the local node. For these attributes, either specify the local node in the
nodename:length parameter, set length to 0, or omit the parameter.
• OSS SEEP programmers must use attribute 158 instead of attribute 93 to obtain the fully
qualified OSS program pathname for the OSS program. Using attribute 93 can lead to
deadlock between the OSS SEEP process and the OSS Name Server and will result in a
timeout of the request to the OSS Name Server.
• Requests about a remote OSS process using its PID can lead to multiple message system calls.
In such instances, the timeout value specified is used for each individual call, and the total
applicable timeout value will be at least the twice the timeout value specified.
Due to the presence of multiple messages, HP recommends you increase the timeout values
for remote processes in comparison to the timeout values specified for local requests. If an
application needs to execute repeated or frequent PROCESS_GETINFOLIST_ calls for a remote
OSS process, it is more efficient to find the process handle prior to executing these calls and
use that as an input in the PROCESS_GETINFOLIST_ call. This optimization removes the
necessity for multiple message system calls and increases system performance.
32-bit/64-bit Considerations
The new 64-bit attributes can be used for either a 32-bit or 64-bit target process. The new 64-bit
attributes can be used by either a 32-bit or 64-bit calling process.
Examples
attr^list := 8; ! get subdevice type only
attr^count := 1;
ret^vals^maxlen := 1;
error := PROCESS_GETINFOLIST_ ( , , , prochandle, attr^list,
attr^count, ret^vals^list,
ret^val^maxlen, ret^val^length );
PROCESS_GETINFOLIST_ Procedure 1043