Operator Messages Manual
Chapter 42 GUARDLIB Messages
The messages in this chapter are sent by the HP NonStop Kernel
subsystem. The subsystem ID displayed by these messages includes GUARDLIB
as the subsystem name. Some messages that include GUARDLIB as the subsystem name are
sent by the Reload subsystem. For these messages, see the Reload chapter. | | | |  | NOTE: Negative-numbered messages are common to most subsystems. If
you receive a negative-numbered message that is not described in this
chapter, see Chapter 15. | | | | |
| 100 CPU cpu sent poison
packet(s) to CPU targetcpu. Current regroup
info is: Reason: reason. Seqno: seqno. Activating CPU: activatingcpu. Causing CPU: causingcpu. CPUs known
at beginning of current regroup: knownatbeg. CPUs known at end of current regroup: knownatend | | targetcpu | specifies the number of the processor to which the
poison packet was sent. | | reason | specifies the reason for regrouping. If reason has no value, the reason is unknown. The possible
values are: | 3: No “I’m-alive” packet received | | 4: Power restored |
| | seqno | specifies the regroup sequence number. | | activatingcpu | specifies the processor that initiated regrouping. | | causingcpu | specifies the processor causing the problem. | | knownatbeg | specifies the processors that are alive at the beginning
of the regrouping. If a processor is alive, the corresponding bit
(of 16 bits) is set to 1. | | knownatend | specifies the processors that are alive at the end
of the regrouping. If a processor is alive, the corresponding bit
(of 16 bits) is set to 1. |
Cause The target processor became unresponsive and was declared down
by the other processors. Subsequent to being declared down, the target
processor sent a message. Effect The processor receiving the message responds to the message
by sending a poison packet to make the target processor declare itself
down. Then, the receiving processor reports the event to the monitor
process. Recovery Informational message only; no corrective action is needed. |
| 104 process-name [, Job
ID batchjob-ID,] trapped [ while in SQL | while
in SQL file system ] [termination-text] | | process-name | is the name of the process that encountered the trap.
If the process was named, the process name has the following format: | \node.$process-name[:sequence-number] |
If the process was unnamed, the process name has the following
format: | \node.cpu,pin[:sequence-number] |
| | batchjob-ID | is the job ID associated with the process, if any. | | termination-text | is ASCII text describing the state of the process
at the time of the trap. See the explanation of completion codes ‑1,
‑6, or ‑8 in Appendix C of the Guardian Procedure Calls
Reference Manual for an explanation of this text. |
Cause The specified process trapped while executing SQL or SQL file‑system
code due to a logic error. Effect A saveabend file is generated for the process that trapped,
and the process is terminated abnormally. Recovery Use the saveabend file to diagnose the problem and correct the
process code. |
| 108 Misalignment Record Collected for Processor processor, PIN pin [Process
Name: process-name] Program
Name: program-file Exception
Count: exception-count Reference
Address: address Emulation Mode:
emulation-mode Priv Mode:
priv-mode P[C]:
code-address [PC (millicode):
millicode-PC] Code Space:
code-space Object Name:
object-name | | processor | is the processor in which a process that has misalignment
is running. | | pin | is the PIN of the process that has misalignment. | | process-name | is the name of the process that has misalignment.
This name is displayed only for named processes. | | program-file | is the Guardian filename or OSS path name of the object
file containing the code address for the misalignment (ZGRD-TKN-MISALIGN-NMPC).
If program-file is the same as object-name, See Program Name is displayed (if the
misalignment occurred in a library, for example, program-file would not be the same as object-name). | | exception-count | is the number of misalignment exceptions for this
PIN (expressed as a decimal value). | | address | is the misaligned address that caused the misalignment
exception (expressed as a hexadecimal value). | | emulation-mode | is the emulation mode of the process that has misalignment.
The possible values are: | | priv-mode | is the privilege mode of the process that has misalignment.
The possible values are: | Priv | | Non-Priv | | Priv and Interrupt |
| | code-address | for accelerated or native code, is the code address
(program counter) associated with the misalignment exception (expressed
as a hexadecimal value). For emulated TNS code, code-address is the emulated TNS instruction (expressed as an octal value). If the misalignment exception occurred in millicode (millicode-PC is present), then the address is a return
address, indicating the point at which the millicode was invoked. | | millicode-PC | is the millicode address (program counter) associated
with the misalignment exception (expressed as a hexadecimal value),
if the exception occurred in the millicode. This value is present
only if millicode-PC is not contain the
same value as code-address. | | code-space | is translated from the instruction address. In interpreted
TNS or accelerated TNS code, code-space is a string value in the form code_space.space_index. In native code, the code space without index is displayed. | | object-name | is the Guardian filename or OSS path name of the program
file for the process that has misalignment. |
Cause The process reported in the event encountered one or more data
misalignment exceptions. Effect The effects are unpredictable. The program may silently corrupt
adjacent data, compute wrong answers, or make wrong decisions. Recovery Fix the data-misalignment coding error at the code address indicated
by code-address. If you are unable to do
fix the code, for whatever reason, contact your service provider or
the Global Mission Critical Solution Center (GMCSC), as directed by
your local operating procedures. Provide the details from the message. |
| 109 Due to resource limitations, the NonStop Kernel
was unable at this time to check for misalignment exceptions in current
processes. Another attempt will occur in about an hour. | Cause The process that checks for data misalignment exceptions could
not obtain sufficient system resources to run. Effect Running processes are not checked for data misalignment exceptions.
However, misalignment events will be logged at process termination. Recovery Informational message only; no corrective action is needed. |
| 110 The Messenger on CPU X has crossed send use
threshold (73%). Currently, at number% of send use limit. Processes
having maximum SENDUSE share are (S C P N) (S C P N) ... Where (S
C P N) stands for (System Name CPU PIN Number of SENDUSE share). Max
10 processes are displayed. | Cause An application either did not open or did not process $RECEIVE
for all incoming system messages from the Messenger process. Effect The CPU appears to hang. Recovery Check the status of each process shown in the message. If you
cannot restart a process so that it begins to read $RECEIVE again
(for example, by typing PAUSE on the home terminal), stop that process
(this frees the pending messages from the Messenger process). Correct
the server process that was not reading $RECEIVE. |
|