Guardian Procedure Calls Reference Manual

OSS Considerations
• When an OSS process is stopped by the ABEND 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, an ABEND system message is sent to the MOM, GMOM, or ancestor process
according to the usual Guardian rules.
• When the ABEND procedure is used to terminate 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 SIGABEND
◦ The pid parameter set to the OSS process ID of the process identified by processhandle
in the PROCESS_STOP_ call
• The security rules that apply to terminating an OSS process using ABEND are the same as
those that apply to the OSS kill() function. For details, see the kill(2) function reference
page either online or in the Open System Services System Calls Reference Manual.
Messages
• Process deletion (ABEND) message
The creator of the stopped process is sent a system message -6 (process deletion: ABEND)
indicating that the deletion occurred. For the format of the interprocess system messages, see
the Guardian Procedure Errors and Messages Manual.
Examples
CALL ABEND; ! cause this process to abend.
CALL ABEND ( ProcID ); ! cause the process that has this process ID to abend.
Related Programming Manual
For information on batch processing, see the NetBatch User's Guide.
44 Guardian Procedure Calls (A-B)