HP Guardian Errors Manual page 261

Table 15 Completion Codes (continued)
Completion Code Definition
5 Process calls PROCESS_STOP_ (with abnormal termination specified) or ABEND on itself. This code
is the default completion code for the PROCESS_STOP_ procedure (when abnormal termination is
specified) and the ABEND procedure.
6 PROCESS_STOP_, STOP, or ABEND was called to delete a process by an external, but authorized,
process. The system includes this completion code in the process deletion message. If the process
cannot be stopped, the request is saved so that when the process calls SETSTOP this completion
code is sent with the process deletion message. The user ID, the PCBCRAID (CAID) and the process
ID of the process that caused the termination, are included in the termination message.
7 Restart this job. This completion code is used by the NetBatch scheduler and an executor process.
The executor process sets its completion code to this value upon termination; the scheduler interprets
this completion code and restarts a "restartable" job.
8 Code 8 is the same as code 1, normal termination, except that the user must examine the listing
file to determine whether the results are acceptable. Completion code 8 is typically used by compilers.
9 The kill() or raise() OSS function generated a signal that stopped the process. The termination
information provides the signal number. Note that if a signal is delivered to a signal handler that
stops the process, the completion code will be determined by the handler. For example, when a
signal stops a TNS/R native C program, a different completion code is returned as set by the signal
handler installed by the Common Run-Time Environment (CRE).
- 1 A trap was detected in a Guardian TNS process. If the system detects the absence of a trap handler
routine or encounters another trap in a trap handler, then in addition to an abnormal termination,
this completion code is returned automatically in the process deletion (ABEND) message. The
contents of the text string vary with the state of the process. The first nine characters are
"TRAPNO=nn" with nn representing the trap number in decimal. Then the text identifies the code
space, including the TNS code segment index when appropriate, and indicates whether the process
was privileged. Finally, the text displays key registers, depending upon the execution mode of the
process at the time of its termination: P or pc, L, and S for TNS or accelerated mode; pc and sp for
TNS/R native mode. Examples: Invalid address in TNS mode: TRAPNO=00: (UC.00) P=%000012
L=%000001 S=%000003 Instruction failure in accelerated mode: TRAPNO=01: (acc UC)
pc=%h704239D8 L=%023520 S=%023520
-2 This code is returned by the system when a process has terminated itself but the system is unable
to pass along the requested completion code and the associated termination information due to a
resource problem in the system.
-3 This code is returned by the system when a process terminating itself passed bad parameters to
PROCESS_DELETE_, STOP, or ABEND. In this case, some or all of the information requested in the
completion code message may not be present. Since the process is stopping itself, it is stopped.
-4 This code is returned by the system when a processor failure caused the name of a process to be
deleted (that is, the only process running under that name was in the processor that failed).
-5 A communications or resource failure occurred during the execution of one of the OSS exec set of
functions; or an initialization failure of the new process occurred when it was too late for the exec
set of functions to return an error to its caller.
-6 An OSS process or TNS/R native process terminated when it caused a hardware exception. The
termination information field of the message contains the signal number. The termination text is in
the message for all processes. However, while the TACL command interpreter displays the termination
text when it is present in the message for a process created by TACL, OSS utilities such as osh
typically do not. The text shows the signal number and name, identifies the code space, and indicates
whether the process was privileged. For a TNS/R native process, the text displays the pc and sp
registers. For an OSS process, it shows registers appropriate to the mode, as for completion code
- 1 . Examples: Invalid address in TNS/R native mode: Signal 1 1, SIGSEGV: (UCr) pc=0x700024F0
sp=0x4FFFFC68 Illegal instruction (instruction failure) in TNS/R native mode: Signal 4, SIGILL: (SRL)
pc=0x7400249C sp=0x4FFFFA6C
- 1 2 One of the OSS exec or tdm_exec set of functions executed successfully. The OSS process ID
continues to exist as it migrates to another process handle, but the original process handle is deleted.
Call PROCESS_GETINFOLIST_ to obtain the new process handle of the OSS process.
- 1 3 The OSS open() or dup() function performed by the PROCESS_SPAWN_ procedure failed. The
termination information in sysmsg[17]contains the OSS errno for the error that occurred. The
Message Descriptions 261