Processor Halt Codes Manual

Recovery
Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump and contact
your service provider or the Global NonStop Solution Center (GNSC), as directed by your local
operating procedures.
%004035
Cause
An internal error occurred in the part of the message system that decides whether to declare a
processor down. This halt could be caused by excessive interrupts, by long periods of disabling
interrupts, or by problems on the ServerNet.
Effect
All freeze-enabled processors halt.
Recovery
Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump and contact
your service provider or the Global NonStop Solution Center (GNSC), as directed by your local
operating procedures. .
%004036
Cause
The message cancel queue has overflowed.
Effect
All freeze-enabled processors halt.
Recovery
Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump and contact
your service provider or the Global NonStop Solution Center (GNSC), as directed by your local
operating procedures.
%004037
Cause
There was a conversion error between link control blocks (LCBs) and extended-memory link
control blocks (XLBs).
Effect
The processor halts. The rest of the system is not affected.
Recovery
Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump and contact
your service provider or the Global NonStop Solution Center (GNSC), as directed by your local
operating procedures.
%004040 through %004057
Cause
A processor was declared down by the other live processors because it failed to communicate
with them.
The number in the least significant four bits (that is, n where the halt code is %004040 + n) is
the number of the live processor that declared the failing processor down and sent it a “poison
packet” to assure that it is down.
Effect
All freeze-enabled processors halt.
144 Software Halt Code Descriptions