Guardian Procedure Calls Reference Manual

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 (page 1116).
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 page 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_.
• Primary
If a switch or a backup takeover occurs (causing the backup process to become the new
primary) through use of the checkpoint procedures, it is not necessary to use
PROCESS_SETINFO_ to set the primary attribute of the new primary. The checkpoint procedures
automatically identify the new primary process to the operating system.
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.
Applications setting values for a 64-bit process should use the new 64-bit attributes rather than the
equivalent 32-bit attributes. These 64-bit wide attributes can also be used to set values for a 32-bit
process.
Safeguard Considerations
For information on processes protected by Safeguard, see the Safeguard Reference Manual.
OSS Considerations
If PROCESS_SETINFO_ is used to change the priority of an OSS process, the same security rules
apply as for the OSS kill() function. See the kill(2) function reference page either online
or in the Open System Services System Calls Reference Manual for details.
Example
INT set^attribute^code := 42; ! set execution priority
.
.
err := PROCESS_SETINFO_ ( proc^handle , ,
1090 Guardian Procedure Calls (P)