Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (S)
Guardian Procedure Calls Reference Manual—522629-013
14-171
STOP Procedure
(Superseded by PROCESS_STOP_ Procedure )
that it had open with exclusive access or before 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.
See Appendix C, Completion Codes
for a list of 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
Messages
•
Process deletion (STOP) message
The creator of the stopped process is sent a system message -5 (process deletion:
STOP), indicating that the deletion occurred. See the
Guardian Procedure Errors
and Messages Manual for the format of the interprocess system messages.