EasyManua.ls Logo

HP Guardian Errors - Page 275

HP Guardian Errors
283 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Effect For trap 4, process control passes to the Debug or Inspect debugger or to the trap handler
designated by a call to the ARMTRAP procedure, or else the process is abended. See Trap
Handling (page 271) for further information.
For the signal SIGTIMEOUT, the default or specified signal handling occurs. See “Signal Handling”
(page 272) for further information.
Note that the loop-timer trap or signal is disabled after the trap or signal is generated; the loop-timer
trap or signal will not recur unless it is rearmed by another call to SETLOOPTIMER.
Recovery Recovery is application dependent. It is possible to resume from both trap 4 and
SIGTIMEOUT, continuing the program from the site of the interruption.
SIGLIMIT, Trap 5 Limits exceeded
Cause This condition occurs for one of the following reasons:
The process called an operating-system procedure that tried to place a process identification
number (PIN) greater than 255 into a 1-byte field.
A TNS Guardian process invoked a procedure or function that is allowed only for an OSS or
TNS/R native process.
Effect For trap 5, process control passes to the Debug or Inspect debugger or to the trap handler
designated by a call to the ARMTRAP procedure, or else the process is abended. See Trap
Handling (page 271) for further information.
For the signal SIGLIMIT, the default or specified signal handling occurs. See “Signal Handling”
(page 272) for further information.
Recovery Run the process at a low PIN or recode the process.
Trap 8 (Signal delivered to TNS process)
Cause A trap 8 is generated when, under very rare circumstances, a signal is delivered to a TNS
process.
Effect Process control passes to the Debug or Inspect debugger or to the trap handler designated
by a call to the ARMTRAP procedure, or else the process is abended. See “Trap
Handling (page 271) for further information.
Recovery Contact your system manager.
SIGMEMMGR, Trap 11 Memory manager read error
Cause A hard (unrecoverable) read error occurred while the program was trying to bring a page
in from virtual memory.
Effect For trap 11, process control passes to the Debug or Inspect debugger or to the trap handler
designated by a call to the ARMTRAP procedure, or else the process is abended. See Trap
Handling (page 271) for further information.
For the signal SIGMEMMGR, the default or specified signal handling occurs. See “Signal Handling
(page 272) for further information.
If the trap or signal occurred because the disk containing the swap file went down, the process
abends, regardless of the selected trap or signal handling.
Recovery Recovery is application dependent. Usually, this condition occurs when both the primary
and backup paths to a disk are down. Contact your system manager to resolve the problem.
SIGNOMEM, Trap 12 No memory available
Signals and Trap Numbers 275

Table of Contents

Related product manuals