HP Guardian Errors Manual page 260

sysmsg[34]
sysmsg[35]
sysmsg[36]
sysmsg[37].<0:13>
sysmsg[37].<14>
sysmsg[37].<15>
sysmsg[38] FOR 2
sysmsg[40]
sysmsg[41] FOR *
sysmsg[ ] FOR *
The returned process descriptor for a terminated named process (pair) is in the form:
\node.$name:seqno
Table 15 shows HP completion codes; we recommend that you use positive completion codes in
the same way. You can specify a completion code with any positive value in a PROCESS_STOP_,
STOP, or ABEND procedure call. Negative completion codes are reserved for HP use.
For an OSS process terminating as a result of an exit() function call, the completion code is set to
the low-order 8 bits of the exit status.
Table 15 Completion Codes
Completion Code
0
1
2
3
4
260 System Messages
handle (all words set to -1) if none
= Length in bytes of termination text
= Offset in bytes (from beginning of
message) of process descriptor
of terminated named process (pair)
= Length in bytes of process descriptor
of terminated named process (pair)
= Reserved
= OSS system type: 1 if the terminated
process was an OSS process; 0 if
the terminated process was a Guardian
process
= Abend: termination caused by ABEND if 1,
STOP if 0
= OSS process ID
= Reserved
= Termination text (80-byte limit). The
length of this item is in sysmsg[34].
It is zero length if no text was
supplied.
= Process descriptor of terminated named
process (pair). The offset of this
item is in sysmsg[35]. The length of
this item is in sysmsg[36]. If the
terminated process is unnamed or is
the recipient's backup, this is zero
length.
Definition
Normal, voluntary termination with no errors. This code is the default for PROCESS_STOP_ (if
abnormal termination is not specified) and STOP if no completion code is specified, and for the
OSS exit() function if no exit status is specified.
Normal, voluntary termination with WARNING diagnostics. For example, if the process is a compiler,
the compilation terminated with WARNING diagnostics after building a complete object file.
Abnormal, voluntary termination with FATAL errors or diagnostics. For example, if the process is a
compiler, the compilation terminated with FATAL diagnostics and either an object file was not built
or, if built, might be incomplete. A complete listing is generated.
Abnormal, voluntary, but premature termination with FATAL errors or diagnostics. For example, if
the process is a compiler, the compilation terminated with FATAL diagnostics, with either no object
file or an incomplete object file being built and an incomplete listing generated (the compiler quit
compiling prematurely).
Process never got started. This completion code exists primarily for the use of the command interpreter
or other command language interpreters that can act as the executor process of a batch job. This
code allows the executor process to detect that a process associated with a RUN statement never
got started. In that sense, this completion code is a "fake" completion code. The command interpreter
acts as though it received a termination message from the process that it tried to create, when in
fact it received an error returned by the procedure or OSS function that launched the process. The
command interpreter then makes the completion code and the error returned by the procedure or
OSS function that launched the process available for evaluation, for example, by a batch job
executor process.