Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (P)
Guardian Procedure Calls Reference Manual—522629-013
12-159
PROCESS_SETINFO_ Procedure
The creator of a named process should not adopt its named child process, even if
the child is a single named process rather than a named process pair. Doing so
establishes the creator as its mom as well as its ancestor. When the process
terminates, the creator will receive two system messages—one for the
disappearance of the named process as an entity, and one for the disappearance
of the adopted process.
If PROCESS_SETINFO_ is used to set the mom of an OSS process, the new mom
receives the Guardian process deletion message when the OSS process
terminates. The received message contains an indication that the terminated
process was an OSS process and also contains the OSS process ID; otherwise,
the message is the same as one received for a terminating Guardian process. For
more information on the Guardian parent of an OSS process, see “Keeping Track
of OSS Child Processes” under the PROCESS_SPAWN_ procedure.
If the OSS process successfully executes a function from the
exec or tdm_exec
set of functions, a Guardian process deletion message is sent to the mom.
Although the process is still alive in the OSS environment (the OSS process ID still
exists), the process handle no longer exists, so the process has terminated in the
Guardian environment.
The OSS parent process (which is not necessarily the same process as the mom
process) also receives OSS process termination status if the OSS process ID no
longer exists. The order of delivery of the OSS process termination status and the
Guardian process deletion message is not guaranteed.
See the
Guardian Procedure Errors and Messages Manual for the format of the
Guardian process deletion message. See the
wait(2) function reference pages
either online or in the or the
Open System Services System Calls Reference
Manual for details on the OSS process termination status.
•
Priority
A process has two priority values: the initial priority and the current priority.
Specifying item 42 (priority) causes the initial priority to be changed to the specified
new value. The current priority is updated to the initial priority when the process
waits for an external event to occur.
Although PROCESS_SETINFO_ supersedes PRIORITY, it does not return the
initial priority value. Initial priority can be obtained by calling
PROCESS_GETINFOLIST_.