Guardian Procedure Calls Reference Manual

These completion codes are reserved for HP use:
DefinitionCompletion Code
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,
-1
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 native mode.
Examples:
Invalid address in TNS mode:
TRAPNO=00: (UC.00) P=%000012 L=%000001 S=%000003
Arithmetic overflow (division by zero) in accelerated mode, privileged:
TRAPNO=02: (acc UC, Priv) pc=%h7042370C L=%023520 S=%023526
Limits-exceeded in native mode, privileged:
TRAPNO=05: (SCr, Priv) pc=0x808E2EDC sp=0x5FFFFF00
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.
-2
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. Because the process is stopping itself, it is stopped.
-3
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).
-4
A communications or resource failure occurred during the execution of one of the functions in the
OSS exec or tdm_exec set of functions; or an initialization failure of the new process occurred
when it was too late for the exec or tdm_exec function to return an error to its caller.
-5
An OSS process or 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
-6
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 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 native mode:
Signal 11, SIGSEGV: (UCr) pc=0x700024F0 sp=0x4FFFFC68
Illegal instruction (instruction failure) in native mode:
Signal 4, SIGILL: (SRL) pc=0x7400249C sp=0x4FFFFA6C
Arithmetic overflow (division by zero) in native mode, privileged:
Signal 8, SIGFPE: (UCr, Priv) pc=0x70002D48 sp=0x5FFFFEB8
An OSS process or native process terminated as a result of a corrupted stack frame or register
state.
-7
An OSS process or native process terminated because of insufficient user stack space for signal
delivery. Stack overflow generates completion code -8, which is otherwise like completion code
-6.
-8
Example:
Stack overflow in native mode:
Signal 25, SIGSTK: (UCr) pc=0x70000394 sp=0x4FEFFE18
An OSS process or native process terminated because of insufficient PRIV stack space for signal
delivery. The termination information field of the message contains the signal number.
-9
1534 Completion Codes