Guardian Procedure Calls Reference Manual

Considerations
• Differences between ABEND and STOP procedures
When used to stop the calling process, the ABEND and STOP procedures operate almost
identically; they differ in the system messages that are sent and the default completion codes
that are reported. In addition, ABEND, but not STOP, causes a saveabend file to be created
if the process' SAVEABEND attribute is set to ON. See the Inspect Manual for information
about saveabend files.
• Creator of the process and the caller of ABEND
If the caller of ABEND is also the creator of the process being deleted, the caller receives the
ABEND system message.
• Rules for stopping a Guardian process: process access IDs and creator access IDs
If the process is a local process and the request to stop it is also from a local process,
these user IDs or associated processes may stop the process:
◦
– Local super ID (255, 255)
– The process' creator access ID (CAID) or the group manager of the CAID
– The process' process access ID (PAID) or the group manager of the PAID
◦ If the process is a local process, a remote process cannot stop it.
◦ If the process is a remote process running on this node and the request to stop it is from
a local process on this node, these user IDs or associated processes may stop the process:
– Local super ID
– The process' creator access ID (CAID) or the group manager of the CAID
– The process' process access ID (PAID) or the group manager of the PAID
◦ If the process is a remote process on this node and the request to stop it is from a remote
process, these user IDs or associated processes can stop the process:
– A network super ID
– The process' network process access ID
– The process' network process access ID group manager
– The process' network creator access ID
– The process' network creator access ID group manager
where network ID implies that the user IDs or associated process creators have matching
remote passwords.
Being local on a system means that the process has logged on by successfully calling
USER_AUTHENTICATE_ or VERIFYUSER on the system or that the process was created by a
process that had done so. A process is also considered local if it is run from a program file
that has the PROGID attribute set.
• Rules for stopping an OSS process
The same rules apply when stopping an OSS process with the ABEND procedure as apply
for the OSS kill() function. See the kill(2) function reference page either online or in
the Open System Services System Calls Reference Manual.
• Rules for stopping any process: stop mode
When one process attempts to stop another process, another item checked is the "stop mode"
of the process. Stop mode is a value associated with every process that determines which
42 Guardian Procedure Calls (A-B)