Guardian Procedure Calls Reference Manual

termination-info
input
INT:value
can be provided as an option by the calling process if it is a subsystem process that defines
Subsystem Programmatic Interface (SPI) error numbers. If supplied, this parameter must be the
SPI error number that identifies the error that caused the process to stop itself. For more
information on the SPI error numbers and subsystem IDs, see the SPI Programming Manual. If
termination-info is not specified, this field is zero.
These parameters should be supplied to identify the subsystem ID that defines the SPI error
number.
spi-ssid
input
INT .EXT:ref:6
is a subsystem ID (SSID) that identifies the subsystem defining the termination-info. The
format and use of the SSID is described in the SPI Programming Manual.
length
input
INT:value
is the text length in bytes. Maximum is 80 bytes.
text
input
STRING .EXT:ref:length
is an optional string of ASCII text to be sent in the STOP system message.
Condition Code Settings
A condition code value is returned only when a process is calling STOP on another process and
that other process could not be stopped.
the process-id parameter is invalid, or an error occurred while stopping the process.< (CCL)
indicates that the STOP was successful.= (CCE)
does not return from STOP.> (CCG)
Considerations
• Differences between STOP and ABEND 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. For information about saveabend files, see
the Inspect Manual.
• Creator of the process and the caller of STOP
If the caller of STOP is also the creator of the process being deleted, the caller receives the
STOP system message.
1400 Guardian Procedure Calls (S)