Processor Halt Codes Manual HP Part Number: 523309-023 Published: May 2013 Edition: J06.03 and subsequent J-series RVUs, H06.03 and subsequent H-series RVUs, and G06.24 and subsequent G-series RVUs.
© Copyright 2012, 2013 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About This Document.....................................................................................5 Supported Release Version Updates (RVUs)..................................................................................5 Intended Audience....................................................................................................................5 Document Organization............................................................................................................
Tables 1 2 3 Summary of Contents.........................................................................................................5 Status Messages and Corresponding Halt Codes ................................................................12 Categories of Standard Processor Halt Codes .....................................................................
About This Document This publication describes processor halt codes and millicode halt codes for HP NonStop systems. Cause, effect, and suggested recovery procedures are included for each code. Supported Release Version Updates (RVUs) This manual supports J06.03 and subsequent J-series RVUs, H06.03 and all subsequent H-series RVUs, and G06.24 and all subsequent G-series RVUs until otherwise indicated in a replacement publication.
Notation Conventions General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required.
{ } Braces A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic Text Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up.
%005400 %B101111 %H2F P=%p-register E=%e-register Related Information These manuals provide additional information about collecting information relevant to a halt, generating a memory dump, and recovering from a halt: • • For G-series RVUs: ◦ NonStop S-Series Operations Guide ◦ OSM online help or TSM Online User Guide ◦ TFDS Manual For H-series and J-series RVUs: ◦ NonStop NS-Series Operations Guide ◦ OSM online help Publishing History Part Number Product Version Publication Date 523309-01
1 Overview When certain unrecoverable hardware, millicode, system configuration, or operating-system software errors occur in a processor, the operating system stops everything that is executing in this processor. Other processors in the system may or may not be affected by this halt.
If a system predates or does not have OSM or TSM, these instructions are invalid. For recovery instructions, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
2 Millicode Halt Code Descriptions This chapter describes processor halt codes generated by the millicode. Millicode halt %nnnnnn When a millicode halt occurs, look up the halt code in this section. The codes are listed in numeric order. If a text message rather than a numeric value is displayed for a halt, consult Table 2 to find the text message, and then look up the description for the corresponding halt code.
Table 2 Status Messages and Corresponding Halt Codes (continued) Status Message Millicode Halt Number POST has successfully completed %100526 Power fail, lost memory %002000 Priv instruction failed %100010 Reset after error freeze %100232 Spurious bus error %100213 Spurious interrupt %177777 TLB exception %100214 TLB exception failure %100230 Unexpected break %100207 Unexpected exception %000103 Unexpected interrupt %100210 Watch exception taken %100222 Millicode Halt Codes %000000
Effect The processor halts. The rest of the system is not affected. Recovery Try the system-load operation again. If this operation fails, see Processor Halt Monitoring and Recovery (page 10). Before attempting a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000006 I/O ownership failed Cause A TAKEOWNERSHIP EIO (execute input/output) error occurred during device load. Effect The processor halts.
%000074 Halt code = %nnnnnn Cause A halt instruction was executed by privileged software. The nnnnnn variable indicates the software halt code. If you do not receive the OSM or TSM facility CPU status screen message, the halt code is in SG122. Effect The processor halts. The rest of the system is not affected. Recovery Look up the description of the nnnnnn halt in Chapter 3 (page 97). %000074 UCME - Page %nn Cause An uncorrectable memory error occurred.
Recovery If you requested the system freeze with the OSM or TSM facility, continue performing the operation for which you requested the halt. If the system freeze was requested by another processor, see Processor Halt Monitoring and Recovery (page 10). %000103 Unexpected exception Cause An unexpected exception, other than a maintenance and diagnostic processor (MDP) freeze request, invalid instruction, or system halt request, occurred.
bit errors (on 64 bits of data) are called uncorrectable memory errors (UCMEs) and cause a processor hardware error freeze. Effect The processor remains halted. The rest of the system is not affected. Recovery If the processor is not reloaded automatically by TFDS, reload it. %002000 Cause A processor that incurred a hardware error freeze was reset.
Recovery See Processor Halt Monitoring and Recovery (page 10). Before taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100002 Code page fault Cause A code page fault (IABS) occurred when the page-fault interrupt was not enabled (masked off). Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10).
Cause The Read FIFO queue was not empty on the entrance into a halt loop, indicating that the interprocessor bus (IPB) chip could be failing. Effect The processor halts. The rest of the system is not affected. Recovery This halt can indicate a hardware failure. See Processor Halt Monitoring and Recovery (page 10). Before taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Recovery See Processor Halt Monitoring and Recovery (page 10). %100212 PON - no operating system image Cause The processor thought a power-fail recovery was in progress and tried to restart the operating system, but the operating system has not been loaded. Effect The processor halts. The device load has failed. The rest of the system is not affected. Recovery Check your system-load paths and retry the operation.
Effect The processor halts. The device load has failed. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10). Before taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100230 TLB exception failure Cause The TLB hardware in the processor is not working and a TLB exception could not be forced. This message can occur only when the processor is reset.
%100236 Cause The power-on self-test failed with a correctable memory error (CME). Effect The processor remains halted. The rest of the system is not affected. Recovery Before taking any action, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. A device load or reload might be possible; however, the board might need to be replaced. %100237 Cause The power-on self-test failed. Effect The processor remains halted.
Recovery Attempt to take a memory dump. After the dump completes or if taking a dump is not possible, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100277 Cause There is insufficient memory configured on the processor to support the current software RVU. Effect The processor halts. The rest of the system is not affected. Recovery Either add more memory to the processor, or revert to an earlier software RVU.
Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100304 Cause The millicode has detected an uncorrectable memory error (UCME), but the memory interface chip (MIC) has not detected an error. Effect The processor halts. The rest of the system is not affected.
Cause An internal processor error has occurred. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100315 Cause An internal processor error has occurred. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10).
%100321 Cause An internal processor error has occurred. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100322 Cause The processor interface chip (PIC) passed bad data to the system. A hardware error probably occurred. Effect The processor halts.
Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100326 Cause An error occurred in the service processor (SP). Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10).
Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100333 Cause The millicode has detected an error. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10).
Cause A bad address was received from $OSP. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100341 Cause An overflow from INTERRUPT A (INTA) was received. Effect The processor halts. The rest of the system is not affected.
Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100345 Cause An error in the secondary cache occurred. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10).
Cause During internal testing (performed by software development), the millicode that was processing a watch exception was unable to simulate a requested instruction. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100404 Cause The millicode timed out the ServerNet memory interface (SMI) hardware while trying to reset an interrupt. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10).
%100414 Cause A privileged process has tried to execute an unblock INTA call when INTA was already blocked by a previous call. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100421 Cause A cache coherency problem has failed. This halt is generally not encountered by users, because it is usually a result of diagnostics performed by software development personnel. Effect The processor halts. The rest of the system is not affected.
%100425 Cause An uncorrectable cache error has occurred. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100426 Cause An uncorrectable cache error has occurred. Effect The processor halts. The rest of the system is not affected.
Recovery See Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100432 Cause An uncorrectable cache error has occurred. Effect The processor halts. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10).
Effect The processor halts. The rest of the system is not affected. Recovery Write down the halt code number, take a memory dump, then contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100443 MICROHALT_DIVERGENCE_ Cause A temporary error in the lockstep process has been detected by the system millicode. Effect The processor halts. The rest of the system is not affected.
Effect The processor halts. The rest of the system is not affected. Recovery Write down the halt code number, take a memory dump, then contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100450 MICROHALT_DIVERGENCE_ Cause A temporary error in the lockstep process has been detected by the system millicode. Effect The processor halts. The rest of the system is not affected.
Effect The processor halts. The rest of the system is not affected. Recovery Write down the halt code number, take a memory dump, then contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100455 MICROHALT_DIVERGENCE_ Cause A temporary error in the lockstep process has been detected by the system millicode. Effect The processor halts. The rest of the system is not affected.
Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Verify that you have specified the correct slot location for the device that you are trying to access. Try the processor load or tape dump again. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100502 Cause The block transfer engine reported an error.
Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Verify that you have specified the correct slot location for the device that you are trying to access and try the processor load or tape dump again. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Try the processor load or tape dump again. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100512 Cause The processor load timed out waiting for the service processor (SP) to translate ServerNet IDs. Effect The processor load or tape dump fails; the processor remains halted.
Recovery Try the processor load or tape dump again. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100517 Cause The parameters for a processor or system-load operation were not specified correctly. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected.
If the problem recurs during the processor dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100526 Cause This halt code occurs is combination with a status message indicating that a Power-On Self Test (POST) operation has completed successfully. A POST operation occurs whenever power is applied to a customer-replaceable unit (CRU). Effect The processor halts. The rest of the system is not affected. Recovery.
Cause Effect Required Recovery Because the batteries and MOS FET are periodically checked when the system is operating (and reported if bad), then this scenario should only happen when the batteries discharge too quickly or can not hold the proper charge. Power-fail event occurs for a processor. When power is restored, a POST The message is expected. operation is executed for each CRU Do not replace the battery. Use OSM The duration of the event exceeds the in the affected enclosures.
Cause The boot millicode’s PROM_CODE_DATE does not match between internal modules. This generally indicates that the FIRMUP operation on the boot millicode was not successful. Effect The processor halts. The rest of the system is not affected. Recovery First perform a firmware update of the boot millicode by using the OSM or TSM facility. Then perform a hard reset on the processor by using the OSM or TSM Low-Level Link.
retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100602 Cause The service processor (SP) reported a bad POST result. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access.
retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100606 Cause The millicode cannot read the ServerNet addressable controller (SAC) registers. The ISP controller is not online because a software failure has occurred. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected.
Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100612 Cause The block transfer engine (BTE) cannot send a packet through ServerNet system area network (SAN).
Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Cause The disk block size is not correct; it should be 514 bytes. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation.
Cause All internal storage for the ServerNet bus interface (SBI) data structures was exhausted. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation.
Cause A software internal error occurred. The ServerNet addressable controller (SAC) subdevice ID should be 1, 2, or 5. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation.
Cause The millicode received an unexpected interrupt packet. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation.
Cause An asynchronous error occurred. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation.
Cause An asynchronous error occurred. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation.
%100760 Cause Unexpected sense code was received during a SCSI FORMAT operation. Effect The processor halts. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. Then retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
problem recurs again, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100764 Cause Fewer than the requested number of bytes have been read from tape, possibly because the end-of-data (EOD) mark or the end-of-file (EOF) mark was encountered during a tape READ operation. The tape might be defective. Effect The processor load or tape dump fails; the processor remains halted. The rest of the system is not affected.
Effect The tape dump fails; the processor remains halted. The rest of the system is not affected. Recovery Write-enable the tape, and retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100770 Cause A tape is not present in the tape drive. Effect The tape dump or device load fails; the processor remains halted. The rest of the system is not affected.
Effect The tape dump or device load fails; the processor remains halted. The rest of the system is not affected. Recovery Check that you specified the correct slot location for the device you are attempting to access. If attempting a tape dump, check that the tape is properly loaded, online, and write-enabled. Then retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect None. Recovery Informational message only; no corrective action is needed. %177777 Spurious interrupt Cause A spurious interrupt occurred. This halt might indicate that the processor is already halted or that the system image has not been loaded into the processor. Effect The processor halts; the processor remains halted. The rest of the system is not affected. Recovery See Processor Halt Monitoring and Recovery (page 10).
Recovery Check that you specified the correct configuration for load. Then, retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100731 MICROHALT_BOOT_BTE_PKT Cause A Fibre Channel Adapter or NonStop Storage CLIM error has occurred during system load. Effect The processor load fails; the processor remains halted. Recovery Check that you specified the correct configuration for load.
Effect The processor load fails; the processor remains halted. Recovery Check that you specified the correct configuration for load and ensure that the Fibre Channel cable is properly connected. Then, retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %100736 MICROHALT_BOOT_FC_ERROR Cause A Fibre Channel Adapter or NonStop Storage CLIM error has occurred during system load.
%100742 MICROHALT_BOOT_USAGE_ERROR Cause A Fibre Channel Adapter or NonStop Storage CLIM error has occurred during system load. Effect The processor load fails; the processor remains halted. Recovery Check that you specified the correct configuration for load. Then, retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Recovery Check that you specified the correct configuration for load. Then, retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %102200 MICROHALT_HARD_RESET Cause The software has detected an inconsistency and reset the processor. Effect The processor halts. The rest of the system is unaffected.
Recovery Write down the halt code and contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %102205 MICROHALT_HALT_FLASH_CHECKSUM_ERROR Cause The flash checksum is bad. The code and or data in flash may be corrupted. Effect The processor halts. The rest of the system is unaffected.
Recovery Write down the halt code and contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %102212 MICROHALT_LOST_ALL_LINKS Cause Both ServerNet links are down to this NonStop Kernel logical processor. Effect The processor is unavailable. The rest of the system is unaffected. Recovery Write down the halt code. Take a dump. After the dump completes, "Hard Reset" this NonStop Kernel logical processor.
Cause HSS detected an internal error. Effect The processor halts. The rest of the system is unaffected. Recovery Retry the operation. If the problem recurs, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %102217 MICROHALT_LSU_WATCHDOG_TIMEOUT Cause A programming error resulted in the expiration of the LSU watchdog timer. Effect The processor halts. The rest of the system is unaffected.
Effect The processor halts, and the ServerNet links to this NonStop Kernel logical processor are brought back up. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump. After the dump completes, do a "Hard Reset" on this NonStop Kernel logical processor. This reset can be accomplished using the Onboard Administrator (OA) or OSM Low-Level Link (LLL), to ensure complete clean-up of and recovery from the MCA.
Effect The processor halts. The rest of the system is unaffected. Recovery Write down the halt code and contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %102301 MICROHALT_BTE_SEQ_ERR_DETECT Cause The millicode detected an internal inconsistency. Effect The processor halts. The rest of the system is unaffected.
Effect The processor halts. The rest of the system is unaffected. 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. %102402 MC_FAULT_TOTAL_LOCK_BREAKDOWN Cause Millicode detected a total breakdown associated with a MUTEX lock. Effect The processor halts. The rest of the system is unaffected.
%102406 MC_FAULT_CANONICAL_UNLOCK_ERROR Cause Millicode detected an error associated with unlocking a canonical lock (trying to release a lock owned by another process). Effect The processor halts. The rest of the system is unaffected. 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.
Effect The processor halts. The rest of the system is unaffected. 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. %102413 MC_FAULT_CANT_BE_HERE Cause Millicode detected a state that should not occur. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause Millicode detected a fault that requires turning over control to the GFH. Effect The processor halts. The rest of the system is unaffected. 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.
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. %102424 MC_FAULT_CANNOT_GIVE_SELF_TO_IP Cause Millicode detected a problem with a process passing ownership to an Interrupt Process. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Effect The processor halts. The rest of the system is unaffected. 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. %102431 MC_FAULT_INCONSISTENT_PROCESS_STATE Cause Millicode detected an internal inconsistency in the state of a process (runnable but not on the ready list). Effect The processor halts. The rest of the system is unaffected.
%102435 MC_FAULT_NO_SEGMENT Cause Millicode detected an attempt to map an invalid memory segment. Effect The processor halts. The rest of the system is unaffected. 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. %102436 MC_FAULT_VHPTFLT Cause Millicode detected a VHPT translation fault. Effect The processor halts.
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. %102442 MC_FAULT_IKEYMISSFLT Cause Millicode detected an instruction key miss fault. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Effect The processor halts. The rest of the system is unaffected. 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. %102447 MC_FAULT_PAGENOTPFLT Cause Millicode detected a page not present fault. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause Millicode detected a debug fault. Effect The processor halts. The rest of the system is unaffected. 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. %102454 MC_FAULT_LOCKDREFFLT Cause Millicode detected a locked reference fault. Effect The processor halts. The rest of the system is unaffected.
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. %102460 MC_FAULT_IA32EXCEPTN Cause Millicode detected an IA32 exception. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Effect The processor halts. The rest of the system is unaffected. 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. %102465 MC_FAULT_NEED_PAGE Cause . Millicode detected a situation where a page fault is needed but cannot yet be handled. Effect The processor halts. The rest of the system is unaffected.
%102471 MC_FAULT_TNET_ASIC_ERR Cause Millicode detected an error associated with the ServerNet ASIC. Effect The processor halts. The rest of the system is unaffected. 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.
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. %102476 MC_FAULT_NSAA_INCONSISTENT_PTE Cause The millicode detected inconsistent bits (besides the dirty and referenced bits) in the page table entries for the memory of an uncooperative process. Effect The processor halts. The rest of the system is unaffected.
Cause Millicode detected a fault that the lower FRs are disabled. These FRs should always be enabled. Effect The processor halts. The rest of the system is unaffected. 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. %102503 MC_FAULT_FPSA_FAILURE Cause Millicode detected a floating point software assist failure. Effect The processor halts.
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. %102507 MC_FAULT_SM_IP_NOT_RUNNING Cause Millicode detected that an Interrupt Process is not running. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %102513 MC_FAULT_NO_SPACE_PRIV_RSE_STK Cause Millicode detected that there is insufficient space available on the privileged RSE stack. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Effect The processor halts. The rest of the system is unaffected. 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. %102520 MC_FAULT_PROCESS_PRIORITY_BOGUS Cause The millicode detected an incorrect process priority. Effect The processor halts. The rest of the system is unaffected.
%102525 MC_FAULT_SMP_IPI_HALT Cause An IPU received an IPI instructing the IPU to halt. Effect The processor halts. The rest of the system is unaffected. 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. %102526 MC_FAULT_NESTED_LOCK_ON_MTCB Cause Millicode detected an attempt to lock a Task Control Block that is already locked.
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. %102532 MC_FAULT_MTCB_LOCK_NOT_HELD Cause Millicode detected a case in which the Task Control Block has not been locked by the IPU that is attempting to perform an operation on it. Effect The processor halts. The rest of the system is unaffected.
fails to boot to the PON Halt, then it must be replaced. If the MC_FAULT_CMC_ERR_EXCEEDED halt code occurs again after this processor has been reloaded, then the processor should be scheduled for replacement at the earliest convenience. Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
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. %102777 MC_FAULT_GRACEFUL_SHUTDOWN Cause A 'Graceful Shutdown' occurs in response to a 'Graceful Shutdown' request from HP SUM (HP Smart Update Manager) issued as part of the firmware update procedure (see the HP Smart Update Manager User Guide for details).
Cause Arrived at a VRO who VRO Sequence Number is past the expected signpost. Effect The processor halts. The rest of the system is unaffected. 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. %103421 MC_FAULT_SOFTWARE_RV_FAULT Cause Invalid count of interrupt vectors in Rendezvous. Effect The processor halts.
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. %103427 MC_FAULT_SN_PROBLEM Cause Problem with VRO Sequence Number detected at a signpost. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause Problem with local list. Effect The processor halts. The rest of the system is unaffected. 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. %103441 MC_FAULT_SOFTWARE_LIST_FAULT_1 Cause Problem with local list. Effect The processor halts. The rest of the system is unaffected.
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. %103463 MC_FAULT_PIO_HACKED_OFF Cause PIO done without sufficient Rendezvous. Effect The processor halts. The rest of the system is unaffected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
3 Software Halt Code Descriptions This chapter describes processor halt codes generated by the operating-system software. Halt code = %nnnnnn When a millicode halt occurs, look up the halt code in this section. The codes are listed in numeric order. For information about recovering a halted processor, refer to Processor Halt Monitoring and Recovery (page 10). If a system predates or does not have OSM or TSM, these instructions are invalid.
Table 3 Categories of Standard Processor Halt Codes (continued) Error Code Type of Error %017000 to %017777 ServerNet services errors %020000 to %020777 Open System Services (OSS) kernel errors, including: Notes PKMGR errors Signalling errors Process control errors %021000 to %021777 DP2 driver error %040000 to %047777 Communications product internal errors, For communications product error including: numbers, the two rightmost octal digits give unique error information, and the General Access Met
Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000002 Cause A writable control store (WCS) operation could not be verified. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
%000027 Cause An unexpected interrupt or trap occurred during a load operation. Effect The processor halts. The rest of the system is not affected. Recovery contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000030 Cause A condition code less than zero (CCL) was returned from an execute input/output (EIO) command. Effect The processor halts. The rest of the system is not affected.
Cause An interrupt timeout occurred and the device is not responding. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000040 Cause The disk bootstrap loader could not verify the processor millicode. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause No disk millicode could be found on the system-image tape (SIT) for downloading the system-load disk controller. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000053 Cause The processor image found in the system-image file was for a different processor type or a different processor number. Effect The processor halts.
Recovery There are two possible recovery procedures for this halt code: • Choose another disk from which to load. • If the error persists, load the system from a system-image tape (SIT). Loading the system from a SIT is the last resort, because it erases the disk to which the tape is copied. Before performing this operation, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Cause While checking the file label for the system-image file, either the system detected an invalid value for primary or secondary extents, or it detected the flag that indicates the file is greater than 2 gigabytes. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000064 Cause The bootstrap code is too large to fit in the space allotted.
Cause The type of processor being loaded is unknown. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000071 Cause Memory for a disk controller was not sufficient to download the millicode. Effect The processor halts. The rest of the system is not affected.
Cause Disk space was not large enough to load all of the system-image files during tape boot. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000076 Cause The version of the programmable read-only memory (PROM) code is too low to be compatible with the bootstraps. Effect The processor remains halted. The rest of the system is not affected.
%000120 Cause The primary or secondary extent of a file is bad or is zero. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000121 Cause The tape or disk boot work area is corrupted. Effect The processor halts. The rest of the system is not affected.
Cause The Read Interrupt Cause (RIC) word returned from the system-load device indicated that the controller is “dead.” This might be the result of an actual malfunction or failure of the device, or the device’s millicode might be incompatible with the programmable read-only memory (PROM) code. Effect The processor halts. The rest of the system is not affected. Recovery Examine the state of the controller and reconfigure the device.
Cause A breakpoint was encountered during a disk boot operation. Breakpoints are used only by software development. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000201 Cause PROMBoot has detected that the ServerNet addressable controller (SAC) controller chip is not initialized. Effect The processor halts. The rest of the system is not affected.
Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000205 Cause PROMBoot has detected that the timeout period expired during a SCSI operation without receiving any acknowledgment from the controller. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000212 Cause PROMBoot has detected an unrecognized error code. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000217 Cause The system-load-from-tape operation failed trying to backspace on the tape. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000224 Cause A tape load or unload operation failed. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000402 Cause The operating system loader detected an error in the OS fileset directory. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000410 Cause Boot Driver encountered an error while using AVT during load of operating system file. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000415 Cause Boot Driver link is down while attempting to load an operating system file. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %000422 Cause Boot Driver usage error while loading an operating system file. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Effect The processor halts. The rest of the system is not affected. Recovery If an instruction failed, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. To put the new bootstraps onto the system disk, load the system from a tape that has the new operating system, or use the Subsystem Control Facility (SCF) command CONTROL DISK.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). Before attempting a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %001010 Cause A bad processor PMAP (an internal data structure) was found. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause A ServerNet error interrupt occurred because either internal inconsistencies occurred in the kernel software or inconsistencies occurred between the ServerNet interface hardware and the kernel software. 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.
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. %001025 Cause I/P queuing failure. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause The CPU being reloaded is not supported. Effect The CPU being reloaded halts. Recovery The CPU processor type is not supported in the system. This can occur, for example, if an NB50000c blade is inserted in an NB54000c system (i.e., a system whose coldload CPU is an NB54000c). %002001 Cause The monitor was unable to lock the stack after the system was loaded. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %002013 Cause The monitor process could not allocate a data segment for its helper processes. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Effect The system fails to load. The rest of the system is not affected. Recovery With the Subsystem Control Facility (SCF), reconfigure the system terminal name. Retry the system-load operation. If the error recurs, refer to Processor Halt Monitoring and Recovery (page 10). %002021 Cause An internal error occurred. The monitor process received an unexpected message from the message system. Effect The processor halts. The rest of the system is not affected.
service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %002025 Cause The monitor is unable to obtain the physical path corresponding to $SYSTEM. (You might be loading from a disk other than the one you specified in the system generation process.) Effect The processor halts. The rest of the system is not affected.
Cause An IPU failed to dispatch processes while there were processes ready for it to dispatch. The number in the least significant four bits (that is, n where the halt code is %002400 + n) is the number of the IPU that stopped dispatching. Effect The logical processor halts. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Recovery Add more main memory so that the main memory size equals the minimum number of pages of memory required. Check the system-generation process output to determine the minimum pages of memory required for the halted processor. If you need assistance, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %003001 Cause The GETENTRY table contains a bad freelist. Effect The processor halts. The rest of the system is not affected.
Cause A LOCKTLE timed out with no corresponding LOCKWAITLIST entry. Effect The processor halts. The rest of the system is not affected. Recovery Take a memory dump of the affected processor, collect the required information, and contact the Tandem NonStop Support Center (TNSC). %003006 Cause A bad address was found in the LOCKWAITLIST entry. 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. %003012 Cause A privileged software error occurred—a bad input/output (I/O) segment address was supplied to the RETURNIOSPACE procedure. Effect The processor halts. The rest of the system is not affected.
Effect The processor halts. The rest of the system is not affected. Recovery Take a memory dump of the affected processor, collect the required information, and contact the Tandem NonStop Support Center (TNSC). %003017 Cause A bad process segment table (PST) entry led to an attempt to deallocate a segment that does not exist. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause The memory manager received a bad segment deallocation request. Effect The processor halts. The rest of the system is not affected. Recovery Take a memory dump of the affected processor, collect the required information, and contact the Tandem NonStop Support Center (TNSC). %003024 Cause A bad page count was detected in a page table. Effect The processor halts. The rest of the system is not affected.
Cause Inconsistent pools in a privileged process were detected during GETPOOL. 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. %003031 Cause Inconsistent pools in a privileged process were detected during a call on the PUTPOOL procedure. Effect The processor halts.
Cause A message system buffer adjustment failed for the RESIZESEGMENT procedure. Effect The processor halts. The rest of the system is not affected. Recovery Take a memory dump of the affected processor, collect the required information, and contact the Tandem NonStop Support Center (TNSC). %003036 Cause The memory manager could not find a segment page table (SPT) for the absolute segment. Effect The processor halts. The rest of the system is not affected.
Cause The input parameter values passed to the quick cell initialization procedure were out of range. Effect The processor halts. The rest of the system is not affected. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %003043 Cause The quick cell initialization procedure was unable to lock memory for the quick cell control block. Effect The processor halts. The rest of the system is not affected.
%003047 Cause The FLEXPOOL Header Table is invalid. 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. %003050 Cause A FLEXPOOL Pool header is inconsistent. Effect All freeze-enabled processors halt. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %003054 Cause A privileged memory-management procedure was called by either a process with invalid parameters or a process that was in an invalid state. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %003060 Cause An internal error occurred in the Memory-management subsystem. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause An internal consistency check related to locking/wiring memory failed. 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. %003067 Cause An internal memory-management assertion failed. Effect The processor halts. The rest of the system is not affected.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %003777 Cause An obsolete procedure was called. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause No link control block (LCB) or message quick cells (MQCs) were available for a special request, or no time-list elements (LCB extensions) were available to the processor. 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. %004007 Cause There was a bad backup controller entry on the send ownership.
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. %004013 Cause A privileged software error occurred—a process attempted a BREAKLINK with a link control block (LCB) not belonging to the process. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause The global update protocol, which keeps all processors synchronized, became unsynchronized. This is an operating system kernel logic error. Effect The unsynchronized processor freezes. If system freeze is not enabled on the system, the global update request (a destination control table update, for example) also fails, but it is automatically retried to the remaining processors. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %004031 Cause The operating system was unable to lock down memory for the message-system cache buffers. Effect All freeze-enabled processors halt. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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 Take a memory dump of both the affected processor and processor n (see “cause,” above). If the halt occurred during a processor reload, also take a memory dump of the system-load processor, the processor that was being reloaded, and the processor from which the reload operation was being run. Collect the required information and contact your service provider. %004060 Cause No more extended-memory link control blocks (XLBs) can be built. Effect The processor halts.
%004064 Cause An error was detected during release of an extended-memory link control block (XLB) or of a message quick cell (MQC). 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. %004065 Cause A link control block (LCB) or an LCB table was bad. Effect The processor halts.
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. %004071 Cause A bad extended-memory link control block (XLB), link control block (LCB), or message quick cell (MQC) was detected. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause An error was detected during a process stop. 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. %004076 Cause An internal consistency check failed in EBSD (a message-system control block that relates to the Fiber Optic Extension, or FOX, network). Effect All freeze-enabled processors halt.
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. %004103 Cause An internal error occurred because a running process or the message system tried to send too much processor information-only (PIO) data. 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. %004107 Cause An internal message-system error occurred when the message system was trying to perform a remote lookup. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause The regroup algorithm halted the processor because it was not communicating with the other processors in the system. 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.
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. %004210 Cause An internal consistency check failed while processing a send info block (SIB) that was aborted by ServerNet services. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %004306 Cause An unsupported packet type was received from the Fiber Optic Extension (FOX) network. Effect All freeze-enabled processors halt. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause The message-system driver received unexpected return code while trying to perform cache operations on a buffer. 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.
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. %004407 Cause The message-system driver received unexpected return code during the installation of a processor device. Effect The processor halts. The rest of the system is not affected.
%004413 Cause The list of ServerNet IDs maintained by the message-system driver is inconsistent with the ServerNet IDs received from another source. 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.
Effect The processor halts. 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. %004420 Cause Device removal failed due to resources not returned. Effect The processor halts. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %004515 Cause An internal consistency check failed while the Fiber Optic Extension (FOX) message-system driver was doing error handling. Effect All freeze-enabled processors halt. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause A trap occurred under mutual exclusion. 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. %005006 Cause An internal error occurred in the operating system—bad pool allocation occurred in the TRAPOUT procedure. Effect The processor halts.
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. %005012 Cause An internal error occurred in the operating system’s PROCESS_GETINFO_ procedure. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause A processor initialization error occurred. 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. This processor cannot be used until the system is coldloaded from a different SYSnn. %005017 Cause The TRAPOUT procedure received an unknown trap number.
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. This processor cannot be used until the system is coldloaded from a different SYSnn. %005023 Cause A negative timeout value was passed to PROCESS_WAIT_. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause An invalid PCB is encountered. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %005030 Cause No public DLLs were preloaded, due to a problem with the ZREG or ZREGPTR files, or the implicit_import statement in the ZREG file.
Errors and Messages Manual. An event 101 will also have been emitted, indicating that failing to preload the TNS emulator prevents running TNS processes. See also halt %005030. %005032 Cause A failure occurred while attempting to preload a public DLL specified in the zreg file. Error details are: 1- The export digest of the public DLL is not a match to the export digest found in the specified zreg file.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %005061 Cause Privileged system software synchronization data structures were internally inconsistent. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause An interrupt handler, an unstoppable process, or a system process experienced an instruction failure. 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. %005102 Cause An interrupt handler, an unstoppable process, or a system process experienced an arithmetic overflow.
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. %005110 Cause An interrupt handler, an unstoppable process, or a system process received an invalid OSS signal. 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. %005177 Cause A page fault occurred while the processor was executing an interrupt handler. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause An inconsistency has occurred in the Process Time-list Element (PTLE) table. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %005204 Cause An invalid process-timer value was encountered by microcode. Effect The processor halts.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %005222 Cause While Dynamic System Configuration (DSC) was adding, deleting, or relocating a controller, an inconsistency occurred in a controller (CTL) table entry. Effect The processor halts. The rest of the system is not affected.
%005227 Cause The system tried to modify some fields in a register save area, but the mode of the register save area was incorrect. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
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. %005234 Cause A bad hitlist entry was found during dispatcher initialization. Effect The processor halts. The rest of the system is unaffected. Recovery Take a memory dump, collect the required information, and contact your service provider.
Cause A free PCB is not present on the list of free PCBs. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %005304 Cause An attempt was made by the process to change an internal flag of another process. 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. %005420 Cause TNS State Library internal error. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
%005503 Cause Initialization error for a system process created by OSBUILD. 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. This processor cannot be used until the system is coldloaded from a different SYSnn.
Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %005512 Cause An internal error occurred in a system process. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
%005572 Cause Allocation or initialization of a segment by CMAP failed. Effect The processor halts. The rest of the system is not affected. 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. Recovery Take a memory dump of the affected processor, collect the required information and contact your service provider.
Cause A required privileged system process was unavailable to process a system function. 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. %005601 Cause Process to be terminated is still using critical system resources. Effect The processor halts.
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. %005605 Cause Error in initializing a critical system process. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %005612 Cause An invalid request was made to a privileged event tracing routine. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause An internal error occurred in a process ownership related operation. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %005773 Cause Bad parameter to NSKIPAP interface. 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. %005777 Cause Internal error in process control sequencing operation. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause A breakpoint was encountered. Breakpoints are used only by software development. Effect The system halts. Recovery Contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %006006 Cause An internal error occurred in the debugger. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
%006200 Cause Debug Services was unable to find the event handle for the instruction breakpoint or MAB. 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. %006201 Cause Debug Services unable to determine physical address. Effect The processor halts.
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. %006206 Cause An Invalid event was reported to Debug Services. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %007003 Cause When the system was being loaded or a processor was being reloaded, SYSPOOL space was unavailable for the Measure page process identification number (PIN) table. Effect The processor halts.
Recovery You can do one of three things: • Run the system without a DST table. • Decrease the memory requirements of the operating system in other areas. • Add more memory. %007007 Cause The system clock in a processor has become incorrect. There are two ways this halt can occur: • If the system clock data has been altered by something other than one of the procedures responsible for maintaining this data.
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. %007013 Cause Data corruption occurred in interval-timing memory. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %007024 Cause The Timer IP was blocked for too long. Effect The logical processor halts. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump of the halted processor.
Cause Insufficient main memory was available to expand the destination control table (DCT). Either the processor memory was insufficient for the configuration and application, or a logic error locked too many pages. 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.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump of the halted processor. Collect the required information and contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %007423 Cause The Destination Control code invoked with insufficient parameters to specify a process name. Effect The logical processor halts. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause The Destination Control code invoked with an invalid index. Effect The logical processor halts. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump of the halted processor. Collect the required information and contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %007441 Cause The Destination Control Table has detected an invalid verifier. Effect The logical processor halts.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %007445 Cause An internal error occurred while constructing a DCT entry. Effect The system freezes. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause A LINKMON process encountered an internal error. If you have NonStop TS/MP installed on your system, a LINKMON process executes in each processor. A LINKMON process is a system process that enables client and requester processes to access Pathway server classes. Effect The processor halts. The rest of the system is not affected. Recovery Report this error to your service provider. %007601 Cause Not enough virtual memory was available to run $ZNUP. $ZNUP is a process that exists on all network nodes.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). Take a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %007701 Cause The amount of virtual memory available is not sufficient to run $ZCNF. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). Before attempting a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %007705 Cause The configuration database could not be opened during a system-load operation. Effect The processor halts. The rest of the system is not affected. Recovery Retry the system-load operation with a different configuration database file.
%007711 Cause A logic error occurred with the system configuration database manager process ($ZCDB). Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). Before attempting a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %007712 Cause The system configuration database could not be opened during a system-load operation.
Recovery Specify all four paths to the coldload volume, even if some paths lead to a missing or uninitialized disk drive. Uncheck the box in the OSM LLL GUI next to any path that you don't want to coldload from. %007773 Cause A disk that has a user-specified World Wide Name (WWN) is in a different shelf and bay from the shelf and bay specified by the user. Effect The processor halts. Since it's the only processor up during coldload, the system halts.
Cause The operator process ($0) was unable to lock down memory in its message queue. For systems configured with $Z0, a failure occurred in locking down memory for internal data structures. 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.
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. %010007 Cause Either the $0 or $Z0 process was unable to obtain sufficient memory for the input/output (I/O) process request manager (IOPRM). Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause An internal logic error occurred in the BDS (burst detection/suppression) code for the $0, $Z0, or $ZOPR process. Effect The processor halts. The rest of the system is not affected. Recovery Take a memory dump of the affected processor, collect the required information, and call your service provider. %010040 Cause An internal logic error occurred in either the $0 or $Z0 process. 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. %011501 Cause The disk process required more physical memory to complete an operation, but none was available. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
%011701 Cause Either the driver detected errors in the internal driver state or the driver request packet contained invalid values (such as an odd transfer length). 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.
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. %011711 Cause The DRIVERTAKEOVER procedure froze because a tray was queued on a path associated with the disk process. (A tray is used to record facts about outstanding requests.) Effect The processor halts. The rest of the system is not affected.
%011716 Cause During its consistency check, the magnetic disk driver found an error in the command packet of an extended controller device input/output (I/O). 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.
Recovery Take a memory dump of the affected processor, collect the required information, and contact your Tandem NonStop Support Center (TNSC). %012003 Cause An operations and service processor (OSP) write interrupt occurred with a count less than or equal to 0. Effect The processor halts. The rest of the system is not affected. Recovery Take a memory dump of the affected processor, collect the required information, and contact your Tandem NonStop Support Center (TNSC).
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. %012103 Cause The maintenance I/O process (MIOP) failed to synchronize memory and cache. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
%014003 Cause An internal Measure error occurred because an internal message ID number was corrupted. Effect The processor halts. The rest of the system is not affected. Recovery Take a memory dump of the affected processor and save a copy of the Measure data file that was taken before the processor halted. Next, collect the required information and contact your service provider. %014005 Cause An internal inconsistency occurred between Measure and the magnetic disk process. Effect The processor halts.
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. %017002 Cause An internal inconsistency was discovered during either a ServerNet transfer request or during the handling of the completion interrupt of that request. Effect The processor halts. The rest of the system is not affected.
Cause An internal ServerNet services defect occurred; the error freeze code was not recognized. 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. %017007 Cause Both ServerNet fabrics are down. Effect The processor halts. The rest of the system is not affected.
it recommends for replacement. Contact your service provider or the Global NonStop Solution Center (GNSC) as directed by your local operating procedures. %017013 - %017017 Cause An internal TNet Services error has occurred. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures.
Recovery Refer to Processor Halt Monitoring and Recovery (page 10). After taking a memory dump, contact your service provider or the Global NonStop Solution Center (GNSC), as directed by your local operating procedures. %017024 Cause TNet Services received a Halt symbol from a debugger. Effect The processor halts. The rest of the system is not affected. Recovery Disable system freeze. Reload the processor.
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. %040000 Cause The PUTPOOL procedure failed to free a local pool buffer. This halt could indicate that there is a bad boundary tag in a pool buffer or that there was an attempt to free a buffer that was already free.
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. %041502 Cause A line-handler process is out of sync with the service-manager process with regard to the configuration. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause A LANMON error occurred within the ServerNet LAN systems access (SLSA) subsystem. Effect The processor halts. 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. %045310 Cause A driver or interrupt handler error occurred within the ServerNet LAN systems access (SLSA) subsystem. Effect The processor halts.
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. %045410 Cause The CIPSREQ MGMT halt code causes fatal software conditions and unexpected QIO returns that would otherwise cause memory corruption. Effect The processor halts. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
%046300 Cause An internal error occurred in CP6100. 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. %046301 Cause An error occurred in CP6100 during initialization. Effect All freeze-enabled processors halt. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %047202 Cause The SNAX/XF line-handler global low memory has been corrupted. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %047277 Cause A coding error occurred. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Recovery Take a memory dump of the affected processor, collect the required information, and contact your Tandem NonStop Support Center (TNSC). %047404 Cause An invalid or improper level-4 protocol existed. Effect The processor halts. The rest of the system is not affected. Recovery Take a memory dump of the affected processor, collect the required information, and contact your Tandem NonStop Support Center (TNSC). %047405 Cause A poll-list error occurred. Effect The processor halts.
%22 LAP level 2 %23 LAPB level 2 %24 LAPX level 2 %30 Level 3 packet %41 Level 4 Debug %42 Level 4 ITI %43 Level 4 MGR %44 Level 4 NAM %45 Level 4 PMX %46 Level 4 PTP %47 Level 4 QLLC 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.
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. %047603 Cause A state transition error occurred. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %047610 Cause During initialization, a call to the SEGMENT_ALLOCATE_ procedure returned an error. Effect The processor halts. The rest of the system is not affected.
Cause A level-4 length error occurred. 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. %047702 Cause A level-4 state transition error occurred. 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. %047706 Cause Not enough control-block pool space was available in ADD^NODE. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
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. %047713 Cause An invalid request block/list management block (RQB/LMB) was detected. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause A signal was raised when the Expand line handler called a system library. 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. %050000 Cause TAPEPROCESS has detected an inconsistency in its internal data structures. Effect The processor halts.
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. %050100 Cause An integrity error occurred in the file system. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
Cause An input/output (I/O) process supplied an invalid value when calling an I/O process request manager (IOPRM) procedure. 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.
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. %060062 Cause A send request from an input/output (I/O) process could not be abandoned because the I/O process had already received the send completion. 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. %060066 Cause An input/output (I/O) process passed an invalid dialect value to the IOPRM_DIALECT_ procedure. Effect The processor halts. The rest of the system is not affected. Recovery Refer to Processor Halt Monitoring and Recovery (page 10).
%060072 Cause An input/output (I/O) process attempted to checkpoint the open context area, but there was no open context area. 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.
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. %060077 Cause An input/output (I/O) process supplied an invalid checkpoint data size to an I/O process request manager (IOPRM) procedure. Effect The processor halts. The rest of the system is not affected.
Cause The Open System Services (OSS) file system detected an unexpected error. 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. %061044 Cause The Open System Services (OSS) Terminal Helper process detected an unexpected error.
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. %061050 Cause The extensible input/output (XIO) monitor process was unable to allocate or initialize its data structures or was unable to lock its message-system buffers in memory. Effect The processor halts.
Cause An error occurred during a tape boot. 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. %177777 Cause The tape boot has finished successfully. Effect None. Recovery Informational message only; no corrective action is needed.
Index Symbols I $0 errors, 199 $ZNUP errors, 194 I/O kernel errors, 173 I/O process request manager (IOPRM) errors, 228, 229 Identifying millicode halts, 12 Input/output (I/O) errors, 100 Interrupt errors, 100, 211, 212 IOPLIB errors, 233 IOPRM errors, 228, 229 A AM3270 Access Method errors, 219 ATP6100 Access Method errors, 217 B Bootstrap errors, 100 L C LAN errors, 215 LINKMON errors, 194 Communications products internal errors AM3270 Access Method errors, 219 ATP6100 Access Method errors, 217 C
SQL file-system errors, 227 Status screen messages, finding halt code, 12 System image loading errors, 101 System monitor errors, 122 T Tape boot errors, special, 236 TAPEPROCESS errors, 227 Text messages , 12 Time control errors, 185 TMF errors, 207 TR3271 Access Method errors, 219 Transaction Monitoring Facility (TMF) errors, 207 TSM CPU status screen, 10 Types of processor halts, 10 X X.
