Guardian Procedure Calls Reference Manual

you try to create a new process with the same name. The best way to be sure that a process
has terminated is to wait for the process deletion message.
• Stopping a process that has the Inspect or saveabend attribute set
If the process being stopped has either the Inspect attribute or the saveabend attribute set,
and if DMON exists, STOP returns error 0 but deletion of the process is delayed until DMON
approves it.
• Completion codes
In response to the STOP procedure, the operating system supplies a completion code in the
system message and, for OSS processes, in the OSS process termination status as follows:
◦ If a process calls STOP on another process, the system supplies a completion code value
of 6.
◦ If a process calls STOP on itself but does not supply a completion code, the system supplies
a completion code value of 0.
For a list of completion codes, see Appendix C: Completion Codes.
• Deleting high-PIN processes
STOP cannot be used to delete a high-PIN unnamed process, but it can be used to delete a
high-PIN named process or process pair.
A high-PIN caller (named or unnamed) can delete itself by omitting process-id.
NetBatch Considerations
• The STOP procedure supports NetBatch processing by:
◦ returning completion code information in the STOP system message
◦ returning the process processor times in the STOP system message
◦ sending a STOP system message to the ancestor of a job (GMOM) as well as the ancestor
of a process
OSS Considerations
• When an OSS process is stopped by the STOP procedure, either by calling the procedure to
stop itself or when some other process calls the procedure, the OSS parent process receives
a SIGCHLD signal and the OSS process termination status. For details on the OSS process
termination status, see the wait(2) function reference page either online or in the Open
System Services System Calls Reference Manual.
In addition, a STOP system message is sent to the mom, GMOM, or ancestor process according
to the usual Guardian rules.
• When the STOP procedure is used to stop an OSS process other than the caller, the Guardian
process ID must be specified in the call. The effect is the same as if the OSS kill() function
was called with the input parameters as follows:
◦ The signal parameter set to SIGKILL
◦ The pid parameter set to the OSS process ID of the process identified by process-id
in the STOP call
• The security rules that apply to stopping an OSS process using STOP are the same as those
that apply to 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.
1402 Guardian Procedure Calls (S)