NonStop Operating System Event Management Programming Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

HP NonStop Operating

System Event

Management

Programming Manual

Abstract

This publication describes event messages generated by components of the

HP NonStop™ operating system.

Product Version

N.A.

Supported Release Version Updates (RVUs)

This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all

subsequent H-series RVUs, G06.08 and all subsequent G-series RVUs, D48.03 and all

subsequent D-series RVUs, until otherwise indicated by its replacement publication.

Part Number Published

520372-020 February 2012

Summary of content (1400 pages)

PAGE 1
HP NonStop Operating System Event Management Programming Manual Abstract This publication describes event messages generated by components of the HP NonStop™ operating system. Product Version N.A. Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all subsequent H-series RVUs, G06.08 and all subsequent G-series RVUs, D48.03 and all subsequent D-series RVUs, until otherwise indicated by its replacement publication.
PAGE 2
Document History Part Number Product Version Published 520372-014 N.A. September 2005 520372-015 N.A. November 2008 520372-016 N.A. February 2009 520372-017 N.A December 2010 520372-019 N.A. August 2011 520372-020 N.A.
PAGE 3
Legal Notices  Copyright 2012 Hewlett-Packard Development Company L.P. 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.
PAGE 4
PAGE 5
HP NonStop Operating System Event Management Programming Manual Glossary Index Examples Figures Tables Legal Notices What’s New in This Manual xvii Manual Information xvii New and Changed Information xvii About This Manual xix Manuals to Which This Manual Refers Notation Conventions xx xxiii Abbreviations xxiv xix 1.
PAGE 6
Contents 4. Interprocessor Bus Event Messages (ZIPB) Subsystem Programmatic Interface (SPI) Standard Definitions Event Management Service (EMS) Standard Definitions 3-6 Low-Level I/O (ZGIO-) Definitions 3-7 Description of ZGIO Event Messages 3-12 Information in Event Description Messages 3-12 Recovery Action Requiring Vendor Support 3-13 Messages 3-14 3-5 4.
PAGE 7
Contents 7. System Monitor Event Messages (ZMON) 7. System Monitor Event Messages (ZMON) Common Definitions 7-2 SPI (ZSPI-)Standard Definitions 7-2 Event Management Service (EMS) Standard Definitions Operating System (ZGRD-) Definitions 7-4 System Monitor (ZMON-) Definitions 7-4 Description of ZMON Event Messages 7-6 Information in Event Description Messages 7-6 Recovery Action Requiring Vendor Support 7-7 Messages 7-7 7-3 8.
PAGE 8
Contents 11. Disk Process Event Messages (ZDSK) 11. Disk Process Event Messages (ZDSK) Common Definitions 11-10 Subsystem Programmatic Interface (SPI) Standard Definitions 11-10 Event Management Service (EMS) Standard Definitions 11-11 Disk Process (ZDSK-) Definitions 11-12 Description of ZDSK Event Messages 11-18 Information in Event Description Messages 11-19 Recovery Action Requiring Vendor Support 11-20 Messages 11-20 12.
PAGE 9
Contents 15. XIO Subsystem Event Messages (ZXIO) 15. XIO Subsystem Event Messages (ZXIO) Common Definitions 15-2 Subsystem Programmatic Interface (SPI) Standard Definitions 15-3 Event Management Service (EMS) Standard Definitions 15-4 XIO Subsystem (ZXIO-) Definitions 15-4 Description of ZXIO Event Messages 15-5 Information in Event Description Messages 15-5 Recovery Action Requiring Vendor Support 15-6 Messages 15-6 16.
PAGE 10
19. ServerNet Error Handler Event Messages (ZSNT) Contents Recovery Action Requiring Vendor Support Messages 18-7 18-7 19. ServerNet Error Handler Event Messages (ZSNT) Common Definitions 19-5 SPI (ZSPI-)Standard Definitions 19-6 Event Management Service (EMS) Standard Definitions ServerNet Error Handler (ZSNT-) Definitions 19-7 Description of ZSNT Event Messages 19-8 Information in Event Description Messages 19-9 Recovery Action Requiring Vendor Support 19-10 Messages 19-10 19-7 20.
PAGE 11
Contents 23. Storage Subsystem Event Messages (ZSTO) 23. Storage Subsystem Event Messages (ZSTO) Common Definitions 23-8 Subsystem Programmatic Interface (SPI) Standard Definitions 23-8 Event Management Service (EMS) Standard Definitions 23-9 SCP (ZCOM-) Standard Definitions 23-10 Storage Subsystem (ZSTO-) Definitions 23-14 Description of ZSTO Event Messages 23-24 Information in Event Description Messages 23-24 Recovery Action Requiring Vendor Support 23-25 Messages 23-25 24.
PAGE 12
Index Contents Recovery Action Requiring Vendor Support Messages 26-6 26-6 Index Examples Figures Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 4-1. Figure 4-2. Figure 4-3. Figure 5-1. Figure 5-2. Figure 5-3. Figure 5-4. Figure 5-5. Figure 6-1. Figure 6-2. Figure 7-1. Figure 7-2. Figure 8-1. Figure 8-2. Figure 9-1. Figure 10-1. Figure 11-1. Figure 12-1. Figure 12-2. Figure 13-1. Figure 13-2. Figure 14-1. Figure 14-2. Figure 15-1. Figure 16-1. Figure 16-2. Figure 16-3. Figure 16-4.
PAGE 13
Tables Contents Figure 16-5. Figure 16-6. Figure 16-7. Figure 16-8. Figure 17-1. Figure 18-1. Figure 19-1. Figure 19-2. Figure 19-3. Figure 20-1. Figure 20-2. Figure 20-3. Figure 20-4. Figure 20-5. Figure 20-6. Figure 20-7. Figure 20-8. Figure 20-9. Figure 20-10. Figure 21-1. Figure 22-1. Figure 23-1. Figure 23-2. Figure 23-3. Figure 23-4. Figure 24-1. Figure 25-1. Figure 25-2. Figure 26-1. Figure 26-2.
PAGE 14
Tables Contents Table 3-2. Table 3-3. Table 4-1. Table 4-2. Table 4-3. Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table 5-5. Table 5-6. Table 5-7. Table 5-8. Table 5-9. Table 5-10. Table 5-11. Table 6-1. Table 6-2. Table 6-3. Table 7-1. Table 7-2. Table 7-3. Table 7-4. Table 7-5. Table 7-6. Table 8-1. Table 8-2. Table 8-3. Table 8-4. Table 8-5. Table 8-6. Table 8-7. Table 8-8. Table 9-1. Table 9-2. Table 9-3. Table 9-4.
PAGE 15
Tables Contents Table 10-1. Table 10-2. Table 10-3. Table 10-4. Table 10-5. Table 10-6. Table 10-7. Table 10-8. Table 10-9. Table 10-10. Table 11-1. Table 11-2. Table 11-3. Table 11-4. Table 11-5. Table 11-6. Table 11-7. Table 11-8. Table 11-9. Table 11-10. Table 11-11. Table 11-12. Table 11-13. Table 11-14. Table 11-15. Table 11-16. Table 11-17. Table 11-18. Table 11-19. Table 11-20. Table 11-21. Table 11-22. Table 11-23. Table 11-24. Table 11-25. Table 12-1. Table 12-2.
PAGE 16
Tables Contents Table 12-3. Table 12-4. Table 12-5. Table 13-1. Table 13-2. Table 13-3. Table 14-1. Table 14-2. Table 14-3. Table 14-4. Table 14-5. Table 14-6. Table 15-1. Table 15-2. Table 15-3. Table 16-1. Table 16-2. Table 16-3. Table 16-4. Table 16-5. Table 16-6. Table 16-7. Table 16-8. Table 16-9. Table 16-10. Table 17-1. Table 17-2. Table 17-3. Table 18-1. Table 18-2. Table 18-3. Table 19-1.
PAGE 17
Tables Contents Table 19-2. Table 19-3. Table 20-1. Table 20-2. Table 20-3. Table 21-1. Table 21-2. Table 21-3. Table 22-1. Table 22-2. Table 22-3. Table 23-1. Table 23-2. Table 23-3. Table 23-4. Table 23-5. Table 23-6. Table 23-7. Table 23-8. Table 23-9. Table 23-10. Table 23-11. Table 23-12. Table 23-13. Table 23-14. Table 23-15. Table 23-16. Table 23-17. Table 24-1. Table 24-2. Table 24-3. Table 25-1.
PAGE 18
Tables Contents Table 25-2. Table 25-3. Table 25-4. Table 25-5. Table 25-6. Table 25-7. Table 25-8. Table 25-9. Table 25-10. Table 25-11. Table 25-12. Table 25-13. Table 25-14. Table 25-15. Table 25-16. Table 25-17. Table 25-18. Table 25-19. Table 25-20. Table 25-21. Table 25-22. Table 25-23. Table 25-24. Table 25-25. Table 25-26. Table 25-27. Table 25-28. Table 25-29. Table 25-30. Table 25-31. Table 25-32. Table 25-33. Table 25-34. Table 25-35. Table 25-36. Table 25-37. Table 25-38. Table 25-39.
PAGE 19
Contents Table 26-1. Table 26-2. Table 26-3. Table 26-4.
PAGE 20
Contents HP NonStop Operating System Event Management Programming Manual—520372-020 xvi
PAGE 21
What’s New in This Manual Manual Information HP NonStop Operating System Event Management Programming Manual Abstract This publication describes event messages generated by components of the HP NonStop™ operating system. Product Version N.A. Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all subsequent H-series RVUs, G06.08 and all subsequent G-series RVUs, D48.
PAGE 22
What’s New in This Manual Additions and Changes, August 2011 Additions and Changes, August 2011   Updated the conditional tokens in the event 402 on pages 5-46 and 5-50. Added a new event message 131: ZNSK-EVT-PS-CHANGE to Nonstop operating system event messages. Additions and Changes, December 2010  Added event message 2505: ZSTO-EVT-SMF-LAUNCH-DELAY to Section 23, Storage Subsystem Event Messages (ZSTO).
PAGE 23
What’s New in This Manual Additions and Changes, February 2009 Additions and Changes, February 2009    Added event messages -1000: ZDSK-EVT-SK-RECVRD-ERR through -1034: ZDSK-EVT-SK-DEFERED-ERROR to Section 11, Disk Process Event Messages (ZDSK). Added event message 224: ZCMP-EVT-ECHO-CRAM-ERROR. Changed all occurrences of the Global Customer Support Center (GCSC) to the updated term, Global Mission Critical Solution Center (GMCSC).
PAGE 24
What’s New in This Manual Additions and Changes, November 2008 HP NonStop Operating System Event Management Programming Manual—520372-020 xx
PAGE 25
About This Manual This manual describes Event Management Service (EMS) event messages for D-series, G-series, and H-Series HP NonStop operating system components from a programmatic perspective. This manual applies to all of the D-series, G-series, and H-Series NonStop operating systems unless otherwise specified.
PAGE 26
About This Manual Notation Conventions Notation Conventions There are four categories of notation conventions:     General Syntax Notation Event Message Text Notation Event Message Token Notation Change Bar Notation General Syntax Notation The following list summarizes the syntax-notation conventions used in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required.
PAGE 27
About This Manual General Syntax Notation { } 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 might 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.
PAGE 28
About This Manual Event Message Text Notation Event Message Text Notation The following list summarizes the event-message text conventions used in this manual. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets.
PAGE 29
Event Message Token Notation About This Manual Event Message Token Notation The following list summarizes the event-message token conventions used in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r.
PAGE 30
About This Manual Abbreviations Abbreviations A B C D E F G H I K L M N O P R S T U V W X A ACS. automated cartridge system ACTT. Audit Checkpoint Transaction Table AM. Application Monitor AVR. automatic volume recognition AVT. Either:   access validation table [in Section 20, SCSI Module Driver Event Messages (ZSMD)] address validation and translation [in Section 10, Tape Process Event Messages (ZTAP)] B BEB. back-end board BIC. backplane interconnect card BLP. bypass label processing BMC.
PAGE 31
About This Manual CRL. complex reintegration leader CRU. customer-replaceable unit CTL table. controller table D DBIO. direct-bulk I/O DBIOPROC. direct-bulk I/O support procedures DCT. destination control table DDL. Data Definition Language DMA. direct memory access DSAP. Disk Space Analysis Program DSM/TC. Distributed Systems Management/Tape Catalog DST. daylight-saving time E ECC. error correction code EIO. execute I/O ELF. extended link format EMS. Event Management Service EOF. end of file EOT.
PAGE 32
About This Manual G GCSC. Global Customer Support Center GFH. General Fault Handler GMS. Group Module Slot GMT. Greenwich mean time H HAD. host access disable HEF. hardware error freeze HSS. Halted State Services I I/O. input/output IB IP. Instruction Breakpoint Interrupt Process IBC. in-bound control IFM. interface monitor IIO. interrogate I/O IIP. interrupt instruction pointer IIRV. interrupt rendezvous IOC. I/O controller IOP. I/O process IOPON. I/O power on IPB. interprocessor bus IPU.
PAGE 33
About This Manual L LCS. loadable control store LID. local interrupt ID LSU. logical synchronization unit LED. light-emitting diode M MAB. memory access breakpoint MAR. memory address registers MB. AuditTrailBuffer/SQLMXBuffer MER AP. Millicode Event Reporter Auxiliary Process MIOP. maintenance I/O process MOA. Medusa Optics Adapter N NACK. not acknowledged NL. no label nld. native mode linker NRL. named resource list NRZI. nonreturn to zero inverted NSBC. NonStop Blade Complex NSBE.
PAGE 34
About This Manual P PAID. process access ID PC. program counter PCB. process control block PCP. Primitive Communications Protocol PCT. Physical CRU Table PE. phase-encoded PE. processing element PIN. process identification number PDT. physical device table PFS. process file segment PON. power on POST. power-on self-test PUP. Peripheral Utility Program R RAC. reconnect address controller RCI. reconnect request RDC. register display code rld. run-time loader RMI. Remote Maintenance Interface RV.
PAGE 35
About This Manual S SAC. ServerNet addressable controller SAD. Slow Access Device SCD. system configuration database SCF. Subsystem Control Facility SCHANL. special channel error SCP. Subsystem Control Point SCSI. small computer system interface SIB. Send Information Block SIFM. SCSI Interface Monitor SIV. system interrupt vector SLM. SCSI Lock Manager SMD. SCSI module driver SMF. HP NonStop Storage Management Foundation SNDA. ServerNet device adapter SP. service processor SMART.
PAGE 36
About This Manual T TACL. HP Tandem Advanced Command Language TAL. Transaction Application Language TERMSTAT. termination status TFDS. HP Tandem Failure Data System TMDS. HP Tandem Maintenance and Diagnostic System TMF. HP NonStop Transaction Management Facility TNT. TNet Node Table TPB. this packet bad TPTM. Third Party Tapes Manager TMS. Tandem Management System U UCME. uncorrectable memory error V VRO. voluntary rendezvous opportunity W WDT. watchdog timer X XIO. extensible I/O XIOMON.
PAGE 37
1 Introduction This manual describes Event Management Service (EMS) event messages for D-series, G-series, and H-Series NonStop operating system components.
PAGE 38
Programmatic Event Message Management Introduction Programmatic Event Message Management Using the EMS programmatic interface, you can write an application in C/C++, COBOL, Pascal, Transaction Application Language (TAL), or TACL that uses a consumer distributor to read events from the EMS log file. The application can take appropriate action in response to a particular event.
PAGE 39
Variable Naming Rules Introduction In addition, use the file that is specific for the component and programming language you are using. These components are identified by a four-character component ID. For example, if you are writing an application in COBOL for the system monitor, use the ZSPIDEF.ZMONCOB file. Note. All definitions are shown in DDL format using hyphens (-) as separators. If you are programming in TAL or TACL, substitute the circumflex symbol (^) for the hyphens.
PAGE 40
Potentially Critical or Noncritical Event Designation Introduction Potentially Critical or Noncritical Event Designation The value of the token ZEMS-TKN-EMPHASIS indicates whether an event is potentially critical or noncritical: Value of ZEMS-TKN-EMPHASIS Meaning Example ZSPI-VAL-TRUE Potentially critical event. The disk process message ZDSKEVT-BAD-MIRROR-VOLS reports inconsistent primary and mirror disk volumes.
PAGE 41
2 Header and Common Tokens Operating system component event messages consist of common header tokens and a common set of nonheader message tokens. This section describes the tokens that are common to all operating system component event messages:   Event-Message Header Tokens on page 2-1 Common Tokens on page 2-3 This section also summarizes Subsystem Programmatic Interface (SPI) Standard Token Types on page 2-5.
PAGE 42
Event-Message Header Tokens Header and Common Tokens Table 2-1.
PAGE 43
Common Tokens Header and Common Tokens Common Tokens Every EMS event message has a non-header section consisting of one or more of a common set of tokens. Table 2-2. Common Event-Message Non-Header Tokens Non-Header Token Token Type What Token Specifies ZEMS-TKN-ACTION-NEEDED ZSPI-TYP-BOOLEAN Action event message (see Action Events on page 1-4) ZEMS-TKN-SUBJECT-MARK ZSPI-TYP-MARK That the next token is the subject token ZEMS-TKN-TEXT ZSPI-TYP-STRING Message text.
PAGE 44
Common Tokens Header and Common Tokens Table 2-3.
PAGE 45
Subsystem Programmatic Interface (SPI) Standard Token Types Header and Common Tokens Subsystem Programmatic Interface (SPI) Standard Token Types Operating system component event message tokens use the standard SPI token types that are listed in Table 2-4. For more information about these tokens, see the SPI Programming Manual. Table 2-4.
PAGE 46
Subsystem Programmatic Interface (SPI) Standard Token Types Header and Common Tokens Table 2-4.
PAGE 47
3 Low-Level I/O Event Messages (ZGIO) Low-level I/O event messages are detected by an I/O process or monitor process and reported to the EMS by the monitor process. Table 3-1. Low-Level I/O Event Messages (page 1 of 3) Event Number and Symbolic Name Description 100: ZGIO-EVT-BADEIOSTATUS A bad status was received from an EIO instruction. 101: ZGIO-EVT-BADIIOSTATUS A bad status was received from an IIO instruction. 102: ZGIO-EVT-CHANNELKILLED A channel was disabled.
PAGE 48
Low-Level I/O Event Messages (ZGIO) Table 3-1. Low-Level I/O Event Messages (page 2 of 3) Event Number and Symbolic Name Description 123: ZGIO-EVT-IIOPADIN Final handshake was missing following an odd-byte data transfer. 124: ZGIO-EVT-IIOPADINOSTI A device controller returned an illegal handshake on the last byte transferred. 125: ZGIO-EVT-IIOPROTECTVIOLATION A protect violation occurred on a read transfer. 126: ZGIO-EVT-IIOSTIFAIL Final handshake on a data transfer was not acknowledged.
PAGE 49
Low-Level I/O Events Low-Level I/O Event Messages (ZGIO) Table 3-1. Low-Level I/O Event Messages (page 3 of 3) Event Number and Symbolic Name Description 143: ZGIO-EVT-SCHANLRPSFREEZE The channel microcode detected an unknown error. 144: ZGIO-EVT-SCHANLRPSUNKNOWN The channel microcode detected an undecodable bus protocol error. 145: ZGIO-EVT-SCHANLTBUSRAC A device-handshake error or a parity error occurred during initial access of a controller.
PAGE 50
Low-Level I/O Event Messages (ZGIO) Channel-Related Events Channel-Related Events Channel-related events describe the operation and performance of the processor I/O channels connected to a specific processor. These events report errors detected by the channel hardware and communications errors between the channel and device controllers. Channel-related events do not identify a specific device; you can assume that they affect all controllers connected to the reporting processor’s I/O channel.
PAGE 51
Common Definitions Low-Level I/O Event Messages (ZGIO) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component. Low-level I/O event messages use definitions from the following sources:    Subsystem Programmatic Interface (SPI) Standard Definitions on page 3-5 Event Management Service (EMS) Standard Definitions on page 3-6 Low-Level I/O (ZGIO-) Definitions on page 3-7 Note.
PAGE 52
Event Management Service (EMS) Standard Definitions Low-Level I/O Event Messages (ZGIO) Figure 3-1. ZGIO-VAL-SSID Structure def ZGIO-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-INT value is ZSPI-SSN-ZGIO. 02 Z-VERSION type ZSPI-DDL-UINT value is ZGIO-VAL-VERSION. end. Token Description ZSPI-TKN-SSID Contains ZGIO-VAL-SSID, the subsystem ID of the I/O subsystem.
PAGE 53
Low-Level I/O (ZGIO-) Definitions Low-Level I/O Event Messages (ZGIO) Token Description (page 2 of 2) ZEMS-TKN-LOGTIME Standard EMS token that specifies the timestamp when the event message was logged to the collector ($0). ZEMS-TKN-NODENUM Expand node number of the affected process. ZEMS-TKN-PIN Process identification number of the affected process. ZEMS-TKN-PROC-DESC Process descriptor of the affected process. ZEMS-TKN-USERID PAID of the affected process.
PAGE 54
Low-Level I/O (ZGIO-) Definitions Low-Level I/O Event Messages (ZGIO)  Simple Tokens and Structured Tokens for Device-Related or Controller-Related Events on page 3-10 Private Token and Field Types Token Description ZGIO-DDL-MSG-BUFFER SPI message buffer to use for low-level I/O event messages. ZGIO-DDL-CNTLR-LOCATION Location for the controller. Figure 3-3. ZGIO-DDL-MSG-BUFFER Definition def ZGIO-DDL-MSG-BUFFER. 02 Z-MSGCODE 02 Z-BUFLEN 02 Z-OCCURS 02 Z-FILLER type ZSPI-DDL-INT.
PAGE 55
Low-Level I/O (ZGIO-) Definitions Low-Level I/O Event Messages (ZGIO) Simple Tokens and Structured Tokens for Channel-Related Events The following tokens are present in all channel-related events: ZGIO-TKN-CHANNEL ZGIO-TKN-INTFREQ ZGIO-TKN-MAXINTFREQ ZGIO-TKN-BADINTFREQ ZGIO-TKN-MAXBADINTFREQ ZGIO-TKN-SCHANERRFREQ ZGIO-TKN-MAXSCHANERRFREQ ZGIO-TKN-CHANNELKILLED ZGIO-TKN-CHANNELRESET token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-
PAGE 56
Low-Level I/O (ZGIO-) Definitions Low-Level I/O Event Messages (ZGIO) Token Description (page 2 of 2) ZGIO-TKN-CTL CTL marker. This token marks the beginning of an entry in the controller table, and it occurs once for each controller. A controller entry comprises this and the next six defined tokens (ZGIO-TKN-CTLKILL through ZGIO-TKNCTLRACWORD). ZGIO-TKN-CTLKILL Indicates whether the controller for this CTL entry was disabled.
PAGE 57
Low-Level I/O (ZGIO-) Definitions Low-Level I/O Event Messages (ZGIO) Physical Device Table (PDT) Entry ZGIO-TKN-PDT ZGIO-TKN-PDTINTCAUSE ZGIO-TKN-PDTCHOWN ZGIO-TKN-PDTCHABORT ZGIO-TKN-PDTCHPARITY ZGIO-TKN-PDTINTDEV ZGIO-TKN-PDTCHANSTAT ZGIO-TKN-PDTIOCSTAT ZGIO-TKN-PDTPIN ZGIO-TKN-PDTLDEV token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-BOOLEAN ZSPI-TYP-BOOLEAN ZSPI-TYP-BOOLEAN ZSPI-TYP-BYTE ZSPI-TYP-ENUM Z
PAGE 58
Description of ZGIO Event Messages Low-Level I/O Event Messages (ZGIO) Token Description (page 2 of 2) ZGIO-TKN-PDTCHABORT Specifies whether the last data transfer by the channel aborted for this PDT entry. Values can be:   ZGIO-TKN-PDTCHPARITY ZSPI-VAL-TRUE (the channel aborted) ZSPI-VAL-FALSE (the channel did not abort) Specifies whether a channel parity error was detected by the channel on the last data transfer for this PDT entry.
PAGE 59
Low-Level I/O Event Messages (ZGIO)   Recovery Action Requiring Vendor Support A list:   Identifying the subject of the event message.  Indicating whether the message identifies a potentially critical event (whether ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE).  Indicating whether the message identifies an action-attention event (whether ZEMS-TKN-ACTION-NEEDED has the value ZSPI-VAL-TRUE).   Identifying the sender of the event message to the EMS collector ($0 process).
PAGE 60
Messages Low-Level I/O Event Messages (ZGIO) Messages 100: ZGIO-EVT-BADEIOSTATUS A protocol error occurred between the channel and device controllers during an EIO instruction.
PAGE 61
Messages Low-Level I/O Event Messages (ZGIO) Token Description (page 2 of 2) ZGIO-TKN-DEVSTAT Status from the controller. ZGIO-TKN-CHANSTAT Status from the channel. Cause. The state of the device controller does not match the state expected by the I/O process at the time the EIO was attempted. Probably a channel or controller failed. Effect. The operation aborts. ZGIO-TKN-CHANSTAT contains the status of the transaction. Recovery.
PAGE 62
Messages Low-Level I/O Event Messages (ZGIO) Token Description (page 2 of 2) ZGIO-TKN-CONTROLLE Subject token that specifies the controller number for the event. ZGIO-TKN-UNIT Subject token that specifies the device number for the event. ZGIO-TKN-FECOD File-system error code returned when an invalid command is sent to the device Cause. An illegal or unknown IIO or HIIO completion status was detected. Effect. The state of the IO operation is unknown. Recovery.
PAGE 63
Messages Low-Level I/O Event Messages (ZGIO) itself when polled, the controller does not respond to other forms of corrective action (such as channel reset), or a channel is defective. Effect. The operating system disables the channel. All input/output (I/O) processes using that channel switch to their configured backups. Channel-based I/O can no longer be performed through this processor and channel; however, the processor and any other channel remain up, and processes can run in the processor. Recovery.
PAGE 64
Messages Low-Level I/O Event Messages (ZGIO) Effect. The operating system resets the specified channel. This action causes the failing component (controller or channel) to reset its internal status and resume normal operation. Recovery. If this condition persists, identify and replace the failing component (controller or channel). If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13.
PAGE 65
Messages Low-Level I/O Event Messages (ZGIO) 1. 2. 3. 4. No controller board plugged in No power to controller Incorrect SYSGEN Controller port logic failure Effect. None. Recovery. See the Guardian Procedure Errors and Messages Manual for the corrective action for the file-system error (given by ZGIO-TKN-FECODE). If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 105: ZGIO-EVT-CONTROLLERKILLED The system issued an EIO kill command to disable the controller.
PAGE 66
Messages Low-Level I/O Event Messages (ZGIO) Effect. The sender processor cannot use this controller or any device attached to it until the associated processor module is reloaded. Recovery. Power off and then power on the offending controller. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 106: ZGIO-EVT-CTLBUSY The device controller rejected the EIO instruction because of an operation in progress.
PAGE 67
Messages Low-Level I/O Event Messages (ZGIO) Token Description ZGIO-TKN-DEVSTAT Status from the controller. ZGIO-TKN-CHANSTAT Status from the channel. Cause. Either a controller, device, or I/O process failed. The state of the device controller does not match the state expected by the I/O process at the time the EIO instruction was attempted. Effect. The controller, device, or I/O process might fail. Recovery.
PAGE 68
Messages Low-Level I/O Event Messages (ZGIO) Token Description (page 2 of 2) ZGIO-TKN-CHANNEL Subject token that specifies the channel affected by this event. ZGIO-TKN-CONTROLLER Subject token that specifies the controller number for the event. ZGIO-TKN-UNIT Subject token that specifies the unit number for the event. ZGIO-TKN-FECODE File-system error code returned when an invalid command is sent to the device. ZGIO-TKN-DEVSTAT Status from the controller.
PAGE 69
Messages Low-Level I/O Event Messages (ZGIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZGIO-EVTEIOOWNERSHIPERROR (108). ZEMS-MAP-EXIOADDR External (physical) I/O address. ZGIO-TKN-CHANNEL Subject token that specifies the channel affected by this event. ZGIO-TKN-CONTROLLER Subject token that specifies the controller number for the event. ZGIO-TKN-UNIT Subject token that specifies the unit number for the event.
PAGE 70
Messages Low-Level I/O Event Messages (ZGIO) Event-Message Text PAGE ABSENT DURING DATA TRANSFER, CHAN %channel, CTLR %controller, UNIT %device Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZGIO-EVTIIOABSENTPAGE (109). ZEMS-MAP-EXIOADDR External (physical) I/O address. ZGIO-TKN-CHANNEL Subject token that specifies the channel affected by this event. ZGIO-TKN-CONTROLLER Subject token that specifies the controller number for the event.
PAGE 71
Messages Low-Level I/O Event Messages (ZGIO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-MAP-EXIOADDR ZGIO-TKN-CHANNEL ZGIO-TKN-CONTROLLER ZGIO-TKN-UNIT ZGIO-TKN-FECODE token-type definition token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-DDL-EXIOADDR ZSPI-TYP-UINT ZSPI-TYP-BYTE ZSPI-TYP-BYTE ZSPI-TYP-BYTE Event-Message Text CONTROLLER COMMAND NOT READ OR WRITE, CHAN %channel, CTLR %controller, UNIT %device Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number fo
PAGE 72
Messages Low-Level I/O Event Messages (ZGIO) Action event: No Message sender: I/O process TMDS collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-MAP-EXIOADDR ZGIO-TKN-CHANNEL ZGIO-TKN-CONTROLLER ZGIO-TKN-UNIT ZGIO-TKN-FECODE token-type definition token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-DDL-EXIOADDR ZSPI-TYP-UINT ZSPI-TYP-BYTE ZSPI-TYP-BYTE ZSPI-TYP-BYTE Event-Message Text PARITY ERROR IOBUS DATA-TO-CHANNEL, CHAN %channel, CTLR %controller, UNIT %device Unconditi
PAGE 73
Messages Low-Level I/O Event Messages (ZGIO) 112: ZGIO-EVT-IIOILLEGALRECONNECT A controller tried to transfer data but the I/O control (IOC) table status for that channel indicates that no data transfer was expected.
PAGE 74
Messages Low-Level I/O Event Messages (ZGIO) Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 113: ZGIO-EVT-IIOINTTIMEOUT A timeout occurred during the data transfer sequence.
PAGE 75
Messages Low-Level I/O Event Messages (ZGIO) Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 114: ZGIO-EVT-IIOIOCUCME The channel microcode detected an uncorrectable memory error (UCME) while accessing the IOC.
PAGE 76
Messages Low-Level I/O Event Messages (ZGIO) Effect. The I/O operation in progress is aborted. This event is probably followed by a processor freeze. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 116: ZGIO-EVT-IIOIOCABSENT The page containing the current IOC is marked absent from physical memory.
PAGE 77
Messages Low-Level I/O Event Messages (ZGIO) responsible for ensuring that the IOC table is locked in physical memory or in the processor memory controller. Effect. The operation aborts. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 117: ZGIO-EVT-IIOMABIOC A memory access breakpoint (MAB) occurred when the I/O control (IOC) table was accessed during an I/O operation.
PAGE 78
Messages Low-Level I/O Event Messages (ZGIO) Token Description ZGIO-TKN-UNIT Subject token that specifies the unit number for the event. ZGIO-TKN-FECODE File-system error code returned when an invalid command is sent to the device. Cause. A MAB occurred when the IOC table was accessed. Either an MAB was set using Debug or there is a failure in MAB circuitry on the processor. Effect. The data transfer in progress is aborted. Recovery.
PAGE 79
Messages Low-Level I/O Event Messages (ZGIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZGIO-EVTIIOMABONREAD (120). ZEMS-MAP-EXIOADDR External (physical) I/O address. ZGIO-TKN-CHANNEL Subject token that specifies the channel affected by this event. ZGIO-TKN-CONTROLLER Subject token that specifies the controller number for the event. ZGIO-TKN-UNIT Subject token that specifies the unit number for the event.
PAGE 80
Messages Low-Level I/O Event Messages (ZGIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZGIO-EVTIIOMABONWRITE (121). ZEMS-MAP-EXIOADDR External (physical) I/O address. ZGIO-TKN-CHANNEL Subject token that specifies the channel affected by this event. ZGIO-TKN-CONTROLLER Subject token that specifies the controller number for the event. ZGIO-TKN-UNIT Subject token that specifies the unit number for the event.
PAGE 81
Messages Low-Level I/O Event Messages (ZGIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZGIO-EVTIIOOWNERSHIPERROR (122). ZEMS-MAP-EXIOADDR External (physical) I/O address. ZGIO-TKN-CHANNEL Subject token that specifies the channel affected by this event. ZGIO-TKN-CONTROLLER Subject token that specifies the controller number for the event. ZGIO-TKN-UNIT Subject token that specifies the unit number for the event.
PAGE 82
Messages Low-Level I/O Event Messages (ZGIO) Event-Message Text PAD IN VIOLATION, CHAN %channel, CTLR %controller, UNIT %device Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZGIO-EVTIIOPADIN (123). ZEMS-MAP-EXIOADDR External (physical) I/O address. ZGIO-TKN-CHANNEL Subject token that specifies the channel affected by this event. ZGIO-TKN-CONTROLLER Subject token that specifies the controller number for the event.
PAGE 83
Messages Low-Level I/O Event Messages (ZGIO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-MAP-EXIOADDR ZGIO-TKN-CHANNEL ZGIO-TKN-CONTROLLER ZGIO-TKN-UNIT ZGIO-TKN-FECODE token-type definition token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-DDL-EXIOADDR ZSPI-TYP-UINT ZSPI-TYP-BYTE ZSPI-TYP-BYTE ZSPI-TYP-BYTE Event-Message Text DEVICE RETURNED PADI WITHOUT STI, CHAN %channel, CTLR %controller, UNIT %device Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for th
PAGE 84
Messages Low-Level I/O Event Messages (ZGIO) Action event: No Message sender: I/O process TMDS collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-MAP-EXIOADDR ZGIO-TKN-CHANNEL ZGIO-TKN-CONTROLLER ZGIO-TKN-UNIT ZGIO-TKN-FECODE token-type definition token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-DDL-EXIOADDR ZSPI-TYP-UINT ZSPI-TYP-BYTE ZSPI-TYP-BYTE ZSPI-TYP-BYTE Event-Message Text I/O PROTECT VIOLATION, CHAN %channel, CTLR %controller, UNIT %device Unconditional Tokens T
PAGE 85
Messages Low-Level I/O Event Messages (ZGIO) Action event: No Message sender: I/O process TMDS collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-MAP-EXIOADDR ZGIO-TKN-CHANNEL ZGIO-TKN-CONTROLLER ZGIO-TKN-UNIT ZGIO-TKN-FECODE token-type definition token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-DDL-EXIOADDR ZSPI-TYP-UINT ZSPI-TYP-BYTE ZSPI-TYP-BYTE ZSPI-TYP-BYTE Event-Message Text DEVICE DID NOT RETURN STI, CHAN %channel, CTLR %controller, UNIT %device Unconditional Toke
PAGE 86
Messages Low-Level I/O Event Messages (ZGIO) 127: ZGIO-EVT-IIOSVIANDSTI A controller sent an illegal handshake during a data transfer.
PAGE 87
Messages Low-Level I/O Event Messages (ZGIO) 128: ZGIO-EVT-IIOUCMEDATA During a write data transfer between memory and a device, an UCME occurred in processor memory.
PAGE 88
Messages Low-Level I/O Event Messages (ZGIO) Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 129: ZGIO-EVT-IIOZEROBYTEREAD An attempt to perform a zero-byte read data transfer was detected.
PAGE 89
Messages Low-Level I/O Event Messages (ZGIO) Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 130: ZGIO-EVT-IIOZEROBYTEWRITE An attempt to perform a zero-byte write data transfer was detected.
PAGE 90
Messages Low-Level I/O Event Messages (ZGIO) Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 131: ZGIO-EVT-INTCCL An IIO instruction failed with a condition code less than (CCL) status error.
PAGE 91
Messages Low-Level I/O Event Messages (ZGIO) 132: ZGIO-EVT-IOTRACE An error occurred during an I/O operation.
PAGE 92
Messages Low-Level I/O Event Messages (ZGIO) 133: ZGIO-EVT-SCHANLBADCOMMAND The channel microcode detected a data transfer protocol error that did not indicate a read or write data transfer.
PAGE 93
Messages Low-Level I/O Event Messages (ZGIO) 134: ZGIO-EVT-SCHANLBADSTAT The channel microcode detected an undecodable error.
PAGE 94
Messages Low-Level I/O Event Messages (ZGIO) 135: ZGIO-EVT-SCHANLDEVRECON A same device has had a continuous reconnect pending over the last two operations.
PAGE 95
Messages Low-Level I/O Event Messages (ZGIO) 136: ZGIO-EVT-SCHANLIOCUCME The channel microcode detected an UCME while accessing the I/O control (IOC) table.
PAGE 96
Messages Low-Level I/O Event Messages (ZGIO) 137: ZGIO-EVT-SCHANLIOCABSENT The page for the I/O control (IOC) table entry being accessed is marked absent.
PAGE 97
Messages Low-Level I/O Event Messages (ZGIO) 138: ZGIO-EVT-SCHANLRANK0TIMEOUT A handshake timeout occurred during initial data transfer protocol with a rank 0 controller.
PAGE 98
Messages Low-Level I/O Event Messages (ZGIO) 139: ZGIO-EVT-SCHANLRANK1TIMEOUT A handshake timeout occurred during initial data transfer protocol with a rank 1 controller.
PAGE 99
Messages Low-Level I/O Event Messages (ZGIO) 140: ZGIO-EVT-SCHANLRCIERROR A reconnect request (RCI) was sent but no device controller responded to the reconnect poll.
PAGE 100
Messages Low-Level I/O Event Messages (ZGIO) 141: ZGIO-EVT-SCHANLRPOLLRANK0 A rank 0 device controller illegally sent a handshake during a poll for data transfer requests.
PAGE 101
Messages Low-Level I/O Event Messages (ZGIO) 142: ZGIO-EVT-SCHANLRPOLLRANK1 A rank 1 device controller illegally sent a handshake during a poll for data transfer requests.
PAGE 102
Messages Low-Level I/O Event Messages (ZGIO) 143: ZGIO-EVT-SCHANLRPSFREEZE The channel microcode detected an unknown error.
PAGE 103
Messages Low-Level I/O Event Messages (ZGIO) 144: ZGIO-EVT-SCHANLRPSUNKNOWN The channel encountered an unknown bus protocol error caused by an unknown TBUS function.
PAGE 104
Messages Low-Level I/O Event Messages (ZGIO) 145: ZGIO-EVT-SCHANLTBUSRAC A device controller did not perform a handshake correctly, or a parity error occurred on the data returned during initial data transfer protocol.
PAGE 105
Messages Low-Level I/O Event Messages (ZGIO) 146: ZGIO-EVT-SCHANLTBUSSEL A device controller did not perform a handshake correctly during the select-for-data transfer protocol.
PAGE 106
Messages Low-Level I/O Event Messages (ZGIO) 147: ZGIO-EVT-MULTICCLMESS Multiple IIO or HIIO instructions failed with a CCL error.
PAGE 107
Messages Low-Level I/O Event Messages (ZGIO) 148: ZGIO-EVT-INTERRUPTPENDING A device controller posted an interrupt while an EIO instruction was being processed.
PAGE 108
Messages Low-Level I/O Event Messages (ZGIO) Effect. The device port is brought down. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 149: ZGIO-EVT-IIOPADINNOPADO A controller returned an illegal handshake on an even-byte write data transfer.
PAGE 109
Messages Low-Level I/O Event Messages (ZGIO) Effect. The data transfer in progress is aborted. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 3-13. 150: ZGIO-EVT-SCHANLBADRETURN The channel detected an undecodable data transfer request.
PAGE 110
Messages Low-Level I/O Event Messages (ZGIO) 151: ZGIO-EVT-SUCC-CNTRL-RELOCATE The specified controller was relocated successfully. Subject: ZGIO-TKN-CHANNEL Type of event: Channel-related Potentially critical event: No Action event: No Message sender: Monitor process TMDS collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZGIO-TKN-OLD-CNTRL-LOC.Z-SEC ZGIO-TKN-OLD-CNTRL-LOC.Z-CAB ZGIO-TKN-OLD-CNTRL-LOC.Z-POS ZGIO-TKN-NEW-CNTRL-LOC.Z-SEC ZGIO-TKN-NEW-CNTRL-LOC.
PAGE 111
Messages Low-Level I/O Event Messages (ZGIO) Token Description (page 2 of 2) ZGIO-TKN-NEW-CNTRL-LOCATION.Z-SEC Section (1 through 4) where the relocation of the target controller is to take place. ZGIO-TKN-NEW-CNTRL-LOCATION.Z-CAB Cabinet (1 through 10) to which the target controller was moved. ZGIO-TKN-NEW-CNTRL-LOCATION.Z-POS Position to which the target controller was moved.
PAGE 112
Messages Low-Level I/O Event Messages (ZGIO) Unconditional Tokens ZGIO-TKN-CONTROLLER ZGIO-TKN-UNIT ZGIO-TKN-CTLCONFMASK ZGIO-TKN-CTLKILL ZGIO-TKN-CTLNEXTCHN ZGIO-TKN-CTLNEXTCTL ZGIO-TKN-CTLINTFREQ ZGIO-TKN-CTLMAXINTFREQ ZGIO-TKN-CTLRACWORD ZGIO-TKN-PDTCHABORT ZGIO-TKN-PDTCHPARITY ZGIO-TKN-PDTCHANSTAT ZGIO-TKN-PDTCHOWN ZGIO-TKN-PDTLDEV ZGIO-TKN-PDTPIN ZGIO-TKN-PDTINTCAUSE ZGIO-TKN-PDTINTDEV ZGIO-TKN-PDTIOCSTAT token-type token-type token-type token-type token-type token-type token-type token-type token-t
PAGE 113
Messages Low-Level I/O Event Messages (ZGIO) Token Description (page 2 of 2) ZGIO-TKN-PDTINTCAUSE Cause for the interrupt. ZGIO-TKN-PDTINTDEV Subchannel number resulting from the IIO instruction. ZGIO-TKN-PDTIOCSTAT IOC transfer status. Cause. Three or more IOPONs have occurred on the controller within 10.2 minutes. Effect. The IOPONs from the controller are ignored. Recovery. Replace the controller.
PAGE 114
Low-Level I/O Event Messages (ZGIO) HP NonStop Operating System Event Management Programming Manual—520372-020 3-68 Messages
PAGE 115
4 Interprocessor Bus Event Messages (ZIPB) Interprocessor bus (IPB) event messages are reported to the EMS by the monitor process. Each event message identifies a bus (X bus or Y bus), processors, and other information specific to the event. Table 4-1. IPB Event Messages Event Number and Symbolic Name Description 100: ZIPB-EVT-BUSSEND The sending processor detected a problem on the bus. 101: ZIPB-EVT-BUSDOWN A bus to a processor is down.
PAGE 116
Interprocessor Bus Event Messages (ZIPB)    Subsystem Programmatic Interface (SPI) Standard Definitions Subsystem Programmatic Interface (SPI) Standard Definitions on page 4-2 Event Management Service (EMS) Standard Definitions on page 4-3 Interprocessor Bus (ZIPB-) Definitions on page 4-4 A general description of these definitions is provided in the following paragraphs. Note. The event-message header tokens are described in Section 2, Header and Common Tokens. Note.
PAGE 117
Event Management Service (EMS) Standard Definitions Interprocessor Bus Event Messages (ZIPB) Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for IPB events are listed in Table 4-3. EMS standard definitions are described in detail in the EMS Manual. Table 4-3.
PAGE 118
Interprocessor Bus (ZIPB-) Definitions Interprocessor Bus Event Messages (ZIPB) Interprocessor Bus (ZIPB-) Definitions Interprocessor Bus definitions begin with ZIPB- and are found in the source-definition files ZIPBTAL, ZIPBCOB, ZIPBTACL, ZIPBDDL, ZIPBC, and ZIPBPAS. These definitions are described in this section.
PAGE 119
Interprocessor Bus Event Messages (ZIPB) Description of ZIPB Event Messages Description of ZIPB Event Messages The IPB event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZIPB-EVT-name, where name describes the event that generated the message.
PAGE 120
Interprocessor Bus Event Messages (ZIPB)  Recovery Action Requiring Vendor Support A box contains the list of tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens. The tokens might not necessarily appear in the message buffer in the same order that they are listed in the box. The tokens in the list are either:   Unconditional (always present in the message).
PAGE 121
Messages Interprocessor Bus Event Messages (ZIPB) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZIPB-TKN-BUS ZIPB-TKN-CPU ZIPB-TKN-SENDTIMEOUT ZIPB-TKN-SENDRESEND ZIPB-TKN-RPTCPU ZIPB-TKN-PRBCPU token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-BYTE ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text CPU nn : BUS {X|Y} SEND ERRORS TO CPU nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for t
PAGE 122
Messages Interprocessor Bus Event Messages (ZIPB) 101: ZIPB-EVT-BUSDOWN A bus to a processor is down.
PAGE 123
Messages Interprocessor Bus Event Messages (ZIPB) Cause. If either the ZIPB-EVT-BUSSEND (100) or ZIPB-EVT-BUSXSUM (102) event message was already issued, a hardware failure occurred on the bus. Prior to this event message, one of the following situations occurred:   The operating system disabled the bus path because of bus errors. The operator issued the XBUSDOWN or YBUSDOWN command. Effect. The operating system brings down the bus. Recovery.
PAGE 124
Messages Interprocessor Bus Event Messages (ZIPB) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPB-EVTBUSXSUM (102). ZIPB-TKN-BUS Is the subject token that specifies the bus. Value is either 0 (X bus) or 1 (Y bus). ZIPB-TKN-CPU Processor number of the processor that is reporting the bus error. ZIPB-TKN-RECVCHECKSUM Number of checksum errors from the problem processor. ZIPB-TKN-RECVROUTE Number of routing errors from the problem processor.
PAGE 125
Messages Interprocessor Bus Event Messages (ZIPB) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZIPB-TKN-BUS ZIPB-TKN-CPU ZIPB-TKN-RPTCPU token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-BYTE ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text CPU nn : BUS {X|Y} UP TO PROCESSOR Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPB-EVT-BUSUP (104). ZIPB-TKN-BUS Is the subject token that specifies the bus.
PAGE 126
Messages Interprocessor Bus Event Messages (ZIPB) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZIPB-TKN-BUS ZIPB-TKN-CPU ZIPB-TKN-RECVSYNCS ZIPB-TKN-RECVUNEXPECTED ZIPB-TKN-RPTCPU ZIPB-TKN-PRBCPU token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-BYTE ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text CPU nn : BUS {X|Y} RECEIVE SEQUENCE ERRORS FROM CPU nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Ev
PAGE 127
Messages Interprocessor Bus Event Messages (ZIPB) 106: ZIPB-EVT-INQTIMEOUTS A full packet was not found in the INQ.
PAGE 128
Messages Interprocessor Bus Event Messages (ZIPB) 107: ZIPB-EVT-OUTQPARITY A parity error was detected on the OUTQ of the IPB interface.
PAGE 129
Messages Interprocessor Bus Event Messages (ZIPB) 108: ZIPB-EVT-EXCESIVEOUTQTIMEOUTS The OUTQ timed out in a NonStop™ VLX, NonStop™ CLX, or NonStop™ Cyclone system.
PAGE 130
Messages Interprocessor Bus Event Messages (ZIPB) 109: ZIPB-EVT-MISROUTE A processor received a packet intended for another processor.
PAGE 131
Messages Interprocessor Bus Event Messages (ZIPB) Effect. None. Recovery. Normally, no recovery action is necessary. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 4-6. 110: ZIPB-EVT-BUSCTRLPARITYERROR A reset or a parity error occurred on the control lines from the bus controller on a Cyclone or K10000 processor.
PAGE 132
Messages Interprocessor Bus Event Messages (ZIPB) Effect. Events 110, 111, and 112 are hardware errors reported by the Cyclone or K10000 IPB chip and recorded in a common error counter. If more than 1000 of these occur in a 19.2-second interval, the operating system shuts down the bus to all processors and issues the ZIPB-EVT-BUSDOWN (101) event message. Recovery. Normally, no recovery action is necessary. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 4-6.
PAGE 133
Messages Interprocessor Bus Event Messages (ZIPB) Effect. Events 110, 111, and 112 are hardware errors reported by the Cyclone or K10000 IPB chip and are recorded in a common error counter. If more than 1000 of these occur in a 19.2-second interval, the operating system shuts down the bus to all processors and issues the ZIPB-EVT-BUSDOWN (101) event message. Recovery. Normally, no recovery action is necessary. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 4-6.
PAGE 134
Messages Interprocessor Bus Event Messages (ZIPB) Effect. Events 110, 111, and 112 are hardware errors reported by the Cyclone or K10000 IPB chip and are recorded in a common error counter. If more than 1000 of these occur in a 19.2-second interval, the operating system shuts down the bus to all processors and issues the ZIPB-EVT-BUSDOWN (101) event message. Recovery. Normally, no recovery action is necessary. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 4-6.
PAGE 135
Messages Interprocessor Bus Event Messages (ZIPB) Token Description (page 2 of 2) ZIPB-TKN-MASKINT Integer that indicates the reason for turning off bus reception. The possible values can be: 1. Checksum errors occurred 2. NQ timeouts (a full packet was not found in the INQ) occurred 3. IPB controller errors occurred 4. Cyclic redundancy check (CRC) errors occurred (D20 and later RVUs only) 5. OUTQ parity errors occurred Cause.
PAGE 136
Messages Interprocessor Bus Event Messages (ZIPB) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPB-EVTBUSCRCERROR (114). ZIPB-TKN-BUS Is the subject token that specifies the bus. Value is either 0 (X bus) or 1 (Y bus). ZIPB-TKN-RPTCPU Processor number of the processor that received the CRC error. This processor is reporting the bus error. ZIPB-TKN-CRCERRORS Number of CRC errors received.
PAGE 137
6 Message System Event Messages (ZMSG) The message system event messages are reported to the EMS by the monitor process or the SENDVIAMESSENGER procedure (the ZMSG-EVT-SENDVIAMSNGR event message only). No other process reports these event messages. Table 6-1. Message System Event Messages Event Number and Symbolic Name Description 106: ZMSG-EVT-SENDVIAMSNGR An I/O process made an improper call to the SENDVIAMESSENGER procedure.
PAGE 138
Message System Event Messages (ZMSG) Subsystem Programmatic Interface (SPI) Standard Definitions Subsystem Programmatic Interface (SPI) Standard Definitions SPI standard definitions that have a specific meaning for message system events are listed in Table 6-2. SPI standard definitions are described in detail in the SPI Programming Manual. Table 6-2.
PAGE 139
Event Management Service (EMS) Standard Definitions Message System Event Messages (ZMSG) Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for message system events are listed in Table 6-3. Table 6-3.
PAGE 140
Message System (ZMSG-) Definitions Message System Event Messages (ZMSG) Private Token and Field Types Token Description ZMSG-DDL-MSG-BUFFER SPI message buffer to use for message system event messages. Figure 6-2. ZMSG-DDL-MSG-BUFFER Definition def ZMSG-DDL-MSG-BUFFER. 02 Z-MSGCODE 02 Z-BUFLEN 02 Z-OCCURS 02 Z-FILLER type ZSPI-DDL-INT. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. type ZSPI-DDL-BYTE occurs 0 TO ZMSG-VAL-BUFLEN times depending on Z-OCCURS. end.
PAGE 141
Message System Event Messages (ZMSG) Description of ZMSG Event Messages Description of ZMSG Event Messages The message system event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZMSG-EVT-name, where name describes the event that generated the message.
PAGE 142
Message System Event Messages (ZMSG)  Recovery Action Requiring Vendor Support A box contains the list of tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens. The tokens might not necessarily appear in the message buffer in the same order that they are listed in the box. The tokens in the list are either:   Unconditional (always present in the message).
PAGE 143
Messages Message System Event Messages (ZMSG) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZMSG-TKN-CPU ZMSG-TKN-PIN ZMSG-TKN-STACKADDR token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text SENDVIAMESSENGER ERROR, CPU nn, PIN nnnnn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMSG-EVTSENDVIAMSNGR (106).
PAGE 144
Message System Event Messages (ZMSG) HP NonStop Operating System Event Management Programming Manual—520372-020 6-8 Messages
PAGE 145
7 System Monitor Event Messages (ZMON) System monitor event messages are reported to the EMS only by the monitor process. Table 7-1. System Monitor Event Messages Event Number and Symbolic Name Description 105: ZMON-EVT-OSIMAGE An error occurred while the system monitor process was opening the OSIMAGE file. 106: ZMON-EVT-TMDS-STARTED TMDSAUTO started successfully. 107: ZMON-EVT-TMDS-STARTUPERROR The operating system failed to start TMDS.
PAGE 146
Common Definitions System Monitor Event Messages (ZMON) Topics:   Common Definitions on page 7-2 Description of ZMON Event Messages on page 7-6 Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 147
Event Management Service (EMS) Standard Definitions System Monitor Event Messages (ZMON) Figure 7-1. ZMON-VAL-SSID Structure def ZMON-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-INT value is ZSPI-SSN-ZMON. 02 Z-VERSION type ZSPI-DDL-UINT value is ZMON-VAL-VERSION. end. Token Description ZSPI-TKN-SSID Contains ZCPU-VAL-SSID, the subsystem ID of the processor subsystem.
PAGE 148
Operating System (ZGRD-) Definitions System Monitor Event Messages (ZMON) Operating System (ZGRD-) Definitions Operating system definitions begin with ZGRD-. Those that appear in system monitor event messages are described in the event-message descriptions. System Monitor (ZMON-) Definitions System monitor definitions begin with ZMON- and are found in the source-definition files ZMONTAL, ZMONCOB, ZMONTACL, ZMONDDL, ZMONC, and ZMONPAS. These definitions are described in this section.
PAGE 149
System Monitor (ZMON-) Definitions System Monitor Event Messages (ZMON) Table 7-4. ZCPU-TKN-CPU-TYPE Values Value Microprocessor Processor 8 R4400 S7000 9 R10000 S7400 S70000 S72000 R12000 S7600 S74000 R14000 S7800 S76000 S78000 S86000 R16000 S88000 DRP NS16000 10 Table 7-5.
PAGE 150
System Monitor Event Messages (ZMON) Description of ZMON Event Messages Predefined Token and Field Values Token Description ZMON-VAL-BUFLEN Recommended buffer length (in bytes) for all system monitor event messages ZMON-VAL-SSID System monitor subsystem ID—the structure is shown under the description for ZSPI-TKN-SSID ZMON-VAL-VERSION Version number of the system monitor Simple Tokens and Structured Tokens These tokens are described in the event-message descriptions.
PAGE 151
Recovery Action Requiring Vendor Support System Monitor Event Messages (ZMON)   Indicating whether the message identifies an action-attention event (whether ZEMS-TKN-ACTION-NEEDED has the value ZSPI-VAL-TRUE).   Identifying the sender of the event message to the EMS collector ($0 process). Indicating whether the event message is sent to the TMDS collector (D-series NonStop operating system RVUs) or OSM/TSM collector (G-series and Hseries NonStop operating system RVUs).
PAGE 152
Messages System Monitor Event Messages (ZMON) Action event: No Message sender: Monitor process TMDS collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZMON-TKN-CPU ZMON-TKN-FECODE token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-ENUM Event-Message Text Unable to Open Operating System Image, File Error errnum Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 153
Messages System Monitor Event Messages (ZMON) Event-Message Text TMDSAUTO Started Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMON-EVTTMDS-STARTED (106). ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. Cause. The TMDS TMDSAUTO program started successfully. Effect. None. Recovery. This is an informational message only; no corrective action is needed.
PAGE 154
Messages System Monitor Event Messages (ZMON) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMON-EVTTMDS-STARTUPERROR (107). ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZGRD-TKN-ERRORCODE PROCESS_CREATE error returned. ZGRD-TKN-OBJECTFILE Object file name. ZGRD-TKN-SWAPFILE Swap file name for the data stack. Cause. TMDS failed to start because of a PROCESS_CREATE error.
PAGE 155
Messages System Monitor Event Messages (ZMON) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMON-EVTTMDS-WARNING (108). ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZMON-TKN-FECODE File-system error that caused this event message. ZMON-TKN-TMDSAUTOSTARTOP File-system operation code. Cause. TMDSAUTO did not read its startup message as expected. Effect. TMDS does not start.
PAGE 156
Messages System Monitor Event Messages (ZMON) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMON-EVTCOUP-STARTED (109). ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZGRD-TKN-ERRORCODE File-system error returned. ZGRD-TKN-OBJECTFILE Object file name. ZGRD-TKN-SWAPFILE Swap file name for the data stack. Cause. COUP was started successfully. Effect. None. Recovery.
PAGE 157
Messages System Monitor Event Messages (ZMON) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMON-EVTCOUP-STARTUPERROR (110). ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZGRD-TKN-ERRORCODE PROCESS_CREATE error returned. ZGRD-TKN-OBJECTFILE Object file name. Cause. A PROCESS_CREATE_ error occurred when an attempt was made to start COUP. Effect. COUP does not start. Recovery.
PAGE 158
Messages System Monitor Event Messages (ZMON) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMONEVT-COUP-WARNING (111). ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZGRD-VAL-SSID.ZSPI-TKN-ERRLIST PROCESS_CREATE_ error list. ZGRD-TKN-ERRORCODE Error returned by the PROCESS_CREATE procedure. ZGRD-TKN-ERRORDETAIL Error detail returned by the file-system. Cause.
PAGE 159
Messages System Monitor Event Messages (ZMON) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMON-EVTINITCICREATEERR (112) ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZGRD-TKN-ERRORCODE PROCESS_CREATE_ error returned. ZGRD-TKN-OBJECTFILE Object file name. ZGRD-TKN-SWAPFILE Swap file name for the data stack. Cause.
PAGE 160
Messages System Monitor Event Messages (ZMON) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMON-EVTINITCIFOPENERR (113). ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZGRD-TKN-CPU Processor number of the operating system processor. ZGRD-TKN-ERRORCODE PROCESS_CREATE error returned. ZGRD-TKN-PROCESSDESCR File name that identifies the process. Cause.
PAGE 161
Messages System Monitor Event Messages (ZMON) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZMON-EVT-OSSSTARTED (114). ZMON-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZGRD-TKN-TOSVERSION TOSVERSION value. Cause. The OSS pipe server process was started. Effect. None. Recovery. This is an informational message only; no corrective action is needed.
PAGE 162
Messages System Monitor Event Messages (ZMON) Recovery. This is an informational message only; no corrective action is needed. 116: ZMON-EVT-OSS-STARTUPERROR A PROCESS_CREATE_ error occurred when the system monitor attempted to start the OSS pipe server.
PAGE 163
Messages System Monitor Event Messages (ZMON) Take the corrective action needed, then reload or reboot the affected processor. 117: ZMON-EVT-OSS-STARTUPERROR2 A PROCESS_CREATE_ error occurred when the system monitor attempted to start the OSS file manager.
PAGE 164
Messages System Monitor Event Messages (ZMON) Take the corrective action needed, then reboot. 120: ZMON-EVT-OSS-INSTALLERR An OSS pipe server or file manager program file is missing.
PAGE 165
Messages System Monitor Event Messages (ZMON) 121: ZMON-EVT-OSS-TA-STARTED The OSS socket transfer agent process was started. Subject: ZMON-TKN-CPU Potentially critical event: No Action event: No Message sender: Monitor process TMDS collector: Yes OSM/TSM collector: No Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZMON-TKN-CPU ZGRD-TKN-TOSVERSION token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-BYTE-PAIR Event-Message Text OSS Socket Agent started successfully.
PAGE 166
Messages System Monitor Event Messages (ZMON) Message sender: Monitor process TMDS collector: Yes OSM/TSM collector: No Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZMON-TKN-CPU ZGRD-TKN-TOSVERSION ZGRD-VAL-SSID.ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZGRD-TKN-ERRORCODE ZGRD-TKN-ERRORDETAIL * ZGRD-VAL-SSID.
PAGE 167
Messages System Monitor Event Messages (ZMON) Token Description ZSPI-TKN-PROC-ERR Contains ZGRD-VAL-PROCESS-CREATE to indicate a process-creation error. ZGRD-TKN-ERRORCODE PROCESS_CREATE_ error value. This value is a decimal number indicating the outcome of the process-creation attempt. See the Guardian Procedure Errors and Messages Manual for the possible error values. ZGRD-TKN-ERRORDETAIL PROCESS_CREATE_ error detail value.
PAGE 168
System Monitor Event Messages (ZMON) HP NonStop Operating System Event Management Programming Manual—520372-020 7-24 Messages
PAGE 169
8 System Clock Event Messages (ZCLK) System clock event messages are reported to the EMS by the monitor process or the SETSYSTEMCLOCK procedure, as indicated in each event-message description. Table 8-1. System Clock Event Messages Event Number and Symbolic Name Description 100: ZCLK-EVT-TIMERESETDST The system time was reset because of a daylightsaving time (DST) change.
PAGE 170
Common Definitions System Clock Event Messages (ZCLK) Topics:   Common Definitions on page 8-2 Description of ZCLK Event Messages on page 8-6 Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 171
Event Management Service (EMS) Standard Definitions System Clock Event Messages (ZCLK) Figure 8-1. ZCLK-VAL-SSID Structure def ZCLK-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-UINT value is ZSPI-SSN-ZCLK. 02 Z-VERSION type ZSPI-DDL-UINT value is ZCLK-VAL-VERSION. end. Token Description ZSPI-TKN-SSID Contains ZCLK-VAL-SSID, the subsystem ID of the system clock subsystem.
PAGE 172
System Clock (ZCLK-) Definitions System Clock Event Messages (ZCLK) System Clock (ZCLK-) Definitions System clock definitions begin with ZCLK- and are found in the source-definition files ZCLKTAL, ZCLKCOB, ZCLKTACL, ZCLKDDL, ZCLKC, and ZCLKPAS.
PAGE 173
System Clock (ZCLK-) Definitions System Clock Event Messages (ZCLK) Table 8-4. ZCPU-TKN-CPU-TYPE Values Value Microprocessor Processor 8 R4400 S7000 9 R10000 S7400 S70000 S72000 R12000 S7600 S74000 R14000 S7800 S76000 S78000 S86000 R16000 S88000 DRP NS16000 10 Table 8-5.
PAGE 174
System Clock Event Messages (ZCLK) Description of ZCLK Event Messages Predefined Token and Field Values Token Description ZCLK-VAL-BUFLEN Recommended buffer length (in bytes) for all system clock event messages ZCLK-VAL-SSID System clock subsystem ID—the structure is shown under the description for ZSPI-TKN-SSID ZCLK-VAL-VERSION Version number of the system clock subsystem Simple Tokens and Structured Tokens These tokens are described in the event-message descriptions.
PAGE 175
Recovery Action Requiring Vendor Support System Clock Event Messages (ZCLK)   Indicating whether the message identifies an action-attention event (whether ZEMS-TKN-ACTION-NEEDED has the value ZSPI-VAL-TRUE).   Identifying the sender of the event message to the EMS collector ($0 process). Indicating whether the event message is sent to the TMDS collector (D-series NonStop operating system RVUs) or OSM/TSM collector (G-series and Hseries NonStop operating system RVUs).
PAGE 176
Messages System Clock Event Messages (ZCLK) Message sender: Monitor process TMDS collector: Yes OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZCLK-TKN-SYSCLOCK token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SYSTEM TIME RESET DUE TO DST TRANSITION Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCLK-EVTTIMERESETDST (100). ZCLK-TKN-SYSCLOCK Subject token that specifies the system time event. Cause.
PAGE 177
Messages System Clock Event Messages (ZCLK) Event-Message Text (D-Series) SYSTEM CLOCK SET FROM RMI CLOCK Event-Message Text (G-Series) SYSTEM CLOCK SET FROM SP CLOCK Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCLK-EVTCLOCKSETFROMRMI (101) on D-series NonStop operating system RVUs and ZCLK-EVT-CLOCKSETFROMSP (101) on G-series and H-series NonStop operating system RVUs.
PAGE 178
Messages System Clock Event Messages (ZCLK) Unconditional Tokens (D20 and later) ZEMS-TKN-EVENTNUMBER ZCLK-TKN-SYSCLOCK ZCLK-TKN-INTERVAL-WORD token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-INT4 Event-Message Text SYSTEM CLOCK RESET Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCLK-EVTTIMERESET (102). ZCLK-TKN-SYSCLOCK Subject token that specifies that this is a system time event.
PAGE 179
Messages System Clock Event Messages (ZCLK) Message sender: SETSYSTEMCLOCK procedure TMDS collector: Yes OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZCLK-TKN-SYSCLOCK token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SYSTEM CLOCK RESET DURING MEASUREMENT Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCLK-EVTTIMESETMEAS (103). ZCLK-TKN-SYSCLOCK Subject token that specifies that this is a system time event. Cause.
PAGE 180
Messages System Clock Event Messages (ZCLK) Unconditional Tokens (D20 and later, D-Series) ZEMS-TKN-EVENTNUMBER ZCLK-TKN-RMICLOCK ZCLK-TKN-RMIIOERROR ZCLK-TKN-INTERVAL-WORD token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-UINT ZSPI-TYP-ENUM ZSPI-TYP-INT4 Unconditional Tokens (D20 and later, G-Series, H-Series) ZEMS-TKN-EVENTNUMBER ZCLK-TKN-INTERVAL-WORD ZCLK-TKN-SPCLOCK ZCLK-TKN-SPIOERROR token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT4 ZSPI-TYP-UINT ZSPI-TYP-EN
PAGE 181
System Clock Event Messages (ZCLK)  Messages A recovery from a system power failure occurred and the RMI clock or the SP clock batteries were dead. Effect. The system time is not automatically initialized. The RMI clock or the SP clock might have failed. Recovery. If the RMI clock or the SP clock failed, see Recovery Action Requiring Vendor Support on page 8-7. Otherwise, enter a SETTIME command to set the correct system time.
PAGE 182
Messages System Clock Event Messages (ZCLK) 105: ZCLK-EVT-CLOCKSETFAILED An error occurred while the operating system was setting the Remote Maintenance Interface (RMI) clock (on D-series NonStop operating system RVUs) or the SP clock (on G-series and H-series NonStop operating system RVUs).
PAGE 183
Messages System Clock Event Messages (ZCLK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCLK-EVTCLOCKSETFAILED (105). ZCLK-TKN-RMICLOCK Subject token that specifies that this is an RMI clock event. ZCLK-TKN-SPCLOCK Subject token that specifies that this is an SP clock event. ZCLK-TKN-RMIIOERROR File-system error number that indicates why the failure occurred (see Table 8-7).
PAGE 184
Messages System Clock Event Messages (ZCLK) Recovery. If ZCLK-TKN-RMIIOERROR is %12, no recovery action is necessary. The system automatically updates the RMI clock every hour, and the RMI clock can run for two hours without an update. If ZCLK-TKN-RMIIOERROR is a value other than %12 (indicating a hardware problem), see Recovery Action Requiring Vendor Support on page 8-7. If ZCLK-TKN-SPIOERROR is %12, no recovery action is necessary.
PAGE 185
Messages System Clock Event Messages (ZCLK) 107: ZCLK-EVT-TIMEADJUSTED An adjustment has been started to correct the system time.
PAGE 186
Messages System Clock Event Messages (ZCLK) Cause. A request was passed to the SETSYSTEMCLOCK procedure to update the time. An initial check determined that the difference between the current time and the new time was small enough that an adjustment could be set up to correct the clock over time (instead of resetting the clock). This adjustment was started. Effect. The time is adjusted. Recovery. This is an informational message only; no corrective action is needed.
PAGE 187
Messages System Clock Event Messages (ZCLK) (Pre-D20 version) The following four tokens form the fixed-point value of the difference in time between system time and the processor’s local time: Token Description ZCLK-TKN-INTERVAL-W-0 Word 0 of the fixed value. ZCLK-TKN-INTERVAL-W-1 Word 1 of the fixed value. ZCLK-TKN-INTERVAL-W-2 Word 2 of the fixed value. ZCLK-TKN-INTERVAL-W-3 Word 3 of the fixed value.
PAGE 188
Messages System Clock Event Messages (ZCLK) Unconditional Tokens (pre-D20) ZEMS-TKN-EVENTNUMBER ZCLK-TKN-CPU ZCLK-TKN-INTERVAL-W-0 ZCLK-TKN-INTERVAL-W-1 ZCLK-TKN-INTERVAL-W-2 ZCLK-TKN-INTERVAL-W-3 token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Unconditional Tokens (D20 and later) ZEMS-TKN-EVENTNUMBER ZCLK-TKN-CPU ZCLK-TKN-INTERVAL-WORD token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-T
PAGE 189
Messages System Clock Event Messages (ZCLK) 110: ZCLK-EVT-BACKINSYNC A processor is again synchronized with system time.
PAGE 190
Messages System Clock Event Messages (ZCLK) (D20 and later version) ZCLK-TKN-INTERVAL-WORD specifies the difference in time between system time and the processor’s local time. Cause. The difference between the processor time and system time has become small enough to claim that this processor is synchronized. Effect. Processes running in the processor obtain timestamps that are within 100 milliseconds of the system time. Recovery. This is an informational message only; no corrective action is needed.
PAGE 191
Messages System Clock Event Messages (ZCLK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCLK-EVTRMIOUTOFSYNC (111) on D-series NonStop operating system RVUs and ZCLK-EVT-SPOUTOFSYNC (111) on G-series and H-series NonStop operating system RVUs. ZCLK-TKN-RMICLOCK Subject token that specifies that this is an RMI clock event. ZCLK-TKN-SPCLOCK Subject token that specifies that this is an SP clock event.
PAGE 192
Messages System Clock Event Messages (ZCLK) Event-Message Text (G-Series, H-Series) SP CLOCK INVALID WHEN TRYING TO RESET SYSTEM CLOCK AFTER POWER FAILURE Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCLK-EVTSYSCLOCKSETFAILED (112). ZCLK-TKN-SYSCLOCK Subject token that specifies the time value of the system clock. ZCLK-TKN-INTERVAL-WORD Difference in time between system time and RMI clock time. Cause.
PAGE 193
9 Labeled-Tape Server Events Messages (ZTAP) The labeled-tape server event messages are reported to the EMS only by the $ZSVR process. Table 9-1. Labeled-Tape Server Event Messages (page 1 of 7) Event Number and Symbolic Name Description 600: ZTAP-EVT-MOUNTOUT A request was made to mount an ANSI labeled tape for output. 601: ZTAP-EVT-MOUNTIN A request was made to mount an ANSI labeled tape for input. 602: ZTAP-EVT-MOUNTSCRATCH A request was made to mount an ANSI labeled scratch tape.
PAGE 194
Labeled-Tape Server Events Messages (ZTAP) Table 9-1. Labeled-Tape Server Event Messages (page 2 of 7) Event Number and Symbolic Name Description 618: ZTAP-EVT-USEANSITAPEERR An ANSI labeled tape was requested, but the mounted tape volume is an IBM labeled tape. 619: ZTAP-EVT-WRITEPROTECTERR A file write-protect error occurred. 620: ZTAP-EVT-NOTMFTAPEERR The mounted tape volume is a TMF tape—do not use it.
PAGE 195
Labeled-Tape Server Events Messages (ZTAP) Table 9-1. Labeled-Tape Server Event Messages (page 3 of 7) Event Number and Symbolic Name Description 638: ZTAP-EVT-TAPEOPENED $ZSVR matched a request for the specified tape volume and device. 639: ZTAP-EVT-NLTAPEONLINE An unlabeled tape is mounted, but there has been no request for it. 640: ZTAP-EVT-ANSITAPEONLINE An ANSI labeled tape is mounted, but there has been no request for it.
PAGE 196
Labeled-Tape Server Events Messages (ZTAP) Table 9-1. Labeled-Tape Server Event Messages (page 4 of 7) Event Number and Symbolic Name Description 654: ZTAP-EVT-DENSITYCHANGED The density of a tape volume was changed to match the DEFINE. 655: ZTAP-EVT-TAPEMODECHANGED The tape mode of a tape volume was changed to match the DEFINE. 656: ZTAP-EVT-DENSITYUSED The density of a tape volume was not changed to match the DEFINE.
PAGE 197
Labeled-Tape Server Events Messages (ZTAP) Table 9-1. Labeled-Tape Server Event Messages (page 5 of 7) Event Number and Symbolic Name Description 673: ZTAP-EVT-SSIDISMOUNT $ZSVR could not dismount a tape from a tape drive in an automated cartridge system. 674: ZTAP-EVT-SSIWRONGTYPE $ZSVR detected a mismatched tape type mounted in an automated cartridge system.
PAGE 198
Labeled-Tape Server Events Messages (ZTAP) Table 9-1. Labeled-Tape Server Event Messages (page 6 of 7) Event Number and Symbolic Name Description 688: ZTAP-EVT-TAPEFILEABEND An application using a tape drive terminated without closing the tape file. 689: ZTAP-EVT-TPTMUP A connection to the TPTM was completed successfully. 690: ZTAP-EVT-TPTMDOWN A connection to the TPTM failed. 691: ZTAP-EVT-TPTMSEVERED The connection to TPTM was severed. 692: ZTAP-EVT-TPTMREJECTED TPTM disallowed a tape request.
PAGE 199
Common Definitions Labeled-Tape Server Events Messages (ZTAP) Table 9-1. Labeled-Tape Server Event Messages (page 7 of 7) Event Number and Symbolic Name Description 707: ZTAP-EVT-TPTMWRITEREAD An error occurred during an attempt to WRITEREAD to TPTM. 708: ZTAP-EVT-TPTMTIMEOUT A request to TPTM timed out. 709: ZTAP-EVT-TPTMNOTCONFIGURED A request to TPTM aborted because TPTM is not configured. 713: ZTAP-EVT-SSIDRIVEBUSY The ACS drive specified in DEFINE is currently busy.
PAGE 200
Labeled-Tape Server Events Messages (ZTAP) Subsystem Programmatic Interface (SPI) Standard Definitions Subsystem Programmatic Interface (SPI) Standard Definitions SPI standard definitions that have a specific meaning for labeled-tape server events are listed in Table 9-2. SPI standard definitions are described in detail in the SPI Programming Manual. Table 9-2.
PAGE 201
Event Management Service (EMS) Standard Definitions Labeled-Tape Server Events Messages (ZTAP) Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for labeled-tape server events are listed in Table 9-3. EMS standard definitions are described in detail in the EMS Manual. Table 9-3.
PAGE 202
Labeled-Tape Server (ZTAP-) Definitions Labeled-Tape Server Events Messages (ZTAP) Labeled-Tape Server (ZTAP-) Definitions Labeled-tape server definitions begin with ZTAP- and are found in the source-definition files ZTAPTAL, ZTAPCOB, ZTAPTACL, ZTAPDDL, ZTAPC, and ZTAPPAS. These definitions are described in this section.
PAGE 203
Labeled-Tape Server Events Messages (ZTAP) Description of ZTAP Event Messages Description of ZTAP Event Messages The labeled-tape server event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZTAP-EVT-name, where name describes the event that generated the message.
PAGE 204
Labeled-Tape Server Events Messages (ZTAP)  Recovery Action Requiring Vendor Support A box listing tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens. The tokens might not necessarily appear in the message buffer in the same order that they are listed in the box. The tokens in the list are either:   Unconditional (always present in the message).
PAGE 205
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-ACTION-ID ZEMS-TKN-TEXT ZTAP-TKN-TAPE-VOLUME token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-STRING ZTAP-TYP-TAPE-VOLUME token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-ENUM ZSPI-TYP-DEVICE ZSPI-TYP-STRING Conditional Tokens ZTAP-TKN-REEL ZTAP-TKN-DENSITY ZTAP-TKN-DEV-NAME ZEMS-TKN-TEXT Event-Message Text $ZSVR: seq MOUNT vid [ REEL num ] [ DENSITY d
PAGE 206
Messages Labeled-Tape Server Events Messages (ZTAP) Token Description ZTAP-TKN-DEV-NAME Subject token that specifies the tape drive device name in the system. This token is present if the request is for a continuation volume of a multivolume operation or if the user requested a specific device. ZEMS-TKN-TEXT Up to 80 bytes of comments that were specified with the DEFINE attribute MOUNTMSG. These comments provide information for the operator such as the relative length and urgency of the job. Cause.
PAGE 207
Messages Labeled-Tape Server Events Messages (ZTAP) Conditional Tokens ZTAP-TKN-REEL ZTAP-TKN-DENSITY ZTAP-TKN-DEV-NAME ZEMS-TKN-TEXT token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-ENUM ZSPI-TYP-DEVICE ZSPI-TYP-STRING Event-Message Text $ZSVR: seq MOUNT vid [ REEL num ] [ DENSITY density ] [ ON $dev ] NO RING [ comment ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTMOUNTIN (601).
PAGE 208
Messages Labeled-Tape Server Events Messages (ZTAP)    Abort the operation with the MEDIACOM REJECT command, if the requested tape volume is not available. $ZSVR generates the action-completion message ZTAPEVT-REJECTMOUNT (651). Mount the requested tape volume on the tape device indicated by ZTAP-TKN-DEVNAME, if this token is specified in the event message.
PAGE 209
Labeled-Tape Server Events Messages (ZTAP) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTMOUNTSCRATCH (602). ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZEMS-TKN-TEXT Standard EMS token that contains the message text. See Event Management Service (EMS) Standard Definitions on page 9-9.
PAGE 210
Messages Labeled-Tape Server Events Messages (ZTAP) $ZSVR generates the action-completion message ZTAP-EVT-ACCEPTMOUNT (648).  Leave the request suspended until one of the above actions is taken. If the processor of the requester goes down while the request is suspended, $ZSVR generates the action-completion message ZTAP-EVT-CANCELMOUNT (649). 603: ZTAP-EVT-MTIBMOUT A request was made to mount an IBM labeled tape for output.
PAGE 211
Labeled-Tape Server Events Messages (ZTAP) Messages Token Description ZEMS-TKN-TEXT Standard EMS token that contains the message text. See Event Management Service (EMS) Standard Definitions on page 9-9. ZTAP-TKN-TAPE-VOLUME Subject token that specifies the volume serial number of the requested volume. Conditional Tokens Token Description ZTAP-TKN-REEL Reel number, if this operation is a multivolume operation. ZTAP-TKN-DENSITY Tape density.
PAGE 212
Messages Labeled-Tape Server Events Messages (ZTAP) 604: ZTAP-EVT-MTIBMIN A request was made to mount an IBM labeled tape for input.
PAGE 213
Labeled-Tape Server Events Messages (ZTAP) Messages Conditional Tokens Token Description ZTAP-TKN-REEL Reel number, if this operation is a multivolume operation. ZTAP-TKN-DENSITY Tape density. Values are ZSPI-VAL-800BPI, ZSPI-VAL1600BPI, and ZSPI-VAL-6250BPI. ZTAP-TKN-DEV-NAME Subject token that specifies the tape drive device name in the system. This token is present if the request is for a continuation volume of a multivolume operation or if the user requested a specific device.
PAGE 214
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-ACTION-ID ZEMS-TKN-TEXT ZTAP-TKN-TAPE-VOLUME token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-STRING ZTAP-TYP-TAPE-VOLUME token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-ENUM ZSPI-TYP-DEVICE ZSPI-TYP-STRING Conditional Tokens ZTAP-TKN-REEL ZTAP-TKN-DENSITY ZTAP-TKN-DEV-NAME ZEMS-TKN-TEXT Event-Message Text $ZSVR: seq MOUNT IBM SCRATCH TAPE vid [ REEL
PAGE 215
Messages Labeled-Tape Server Events Messages (ZTAP)   An operation requests an IBM labeled scratch tape. An output file requires more than one volume, but not enough volume serial numbers were specified in the DEFINE entry. Effect. The operation waits for the tape to be mounted. Recovery. The request is suspended until one of the following actions is taken:    Abort the operation with the MEDIACOM REJECT command, if a IBM scratch volume is not available.
PAGE 216
Labeled-Tape Server Events Messages (ZTAP) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTREQNL (606). ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 to 9999. ZEMS-TKN-TEXT Standard EMS token that contains the message text. See Event Management Service (EMS) Standard Definitions on page 9-9.
PAGE 217
Messages Labeled-Tape Server Events Messages (ZTAP) Message sender: $ZSVR TMDS collector: No OSM/TSM collector: No Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-ACTION-ID ZEMS-TKN-TEXT ZTAP-TKN-DEV-NAME token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-DEVICE Conditional Tokens ZEMS-TKN-TEXT token-type ZSPI-TYP-STRING Event-Message Text $ZSVR: seq REQUEST TO USE $dev WITH NO LABEL PROTECTION [ comment ] Unconditional Tokens Token Description
PAGE 218
Labeled-Tape Server Events Messages (ZTAP)    Messages Abort the operation with the MEDIACOM REJECT command. $ZSVR generates the action-completion message ZTAP-EVT-REJECTDEVICE (653). Accept the operation with the MEDIACOM ACCEPT command. $ZSVR generates the action-completion message ZTAP-EVT-ACCEPTDEVICE (652).
PAGE 219
Messages Labeled-Tape Server Events Messages (ZTAP) 608: ZTAP-EVT-REQUNKNOWN A request was made to mount questionable tape on a tape device. The operator must approve the mounting of this tape.
PAGE 220
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. The request is suspended as a outstanding request until one of the following actions is taken:    Accept the operation with the MEDIACOM ACCEPT command. $ZSVR generates the action-completion message ZTAP-EVT-ACCEPTDEVICE (652). Correct the density switch setting, then press the ONLINE button twice to enable AVR. $ZSVR generates the action-completion message ZTAP-EVTACCEPTMOUNT (648). Mount another tape on the drive.
PAGE 221
Labeled-Tape Server Events Messages (ZTAP) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTMTTMFOUT (609). ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZEMS-TKN-TEXT Standard EMS token that contains the message text. See Event Management Service (EMS) Standard Definitions on page 9-9.
PAGE 222
Messages Labeled-Tape Server Events Messages (ZTAP)   Use the MEDIACOM command ALTER TAPEMOUNT or the TAPECOM command NEXTTAPE to have the TMF Catalog try to find a replacement TMF labeled tape. If a replacement is found, the old event message is canceled and a new event message is generated for the replacement TMF labeled tape.
PAGE 223
Labeled-Tape Server Events Messages (ZTAP) Messages Token Description (page 2 of 2) ZEMS-TKN-TEXT Standard EMS token that contains the message text. See Event Management Service (EMS) Standard Definitions on page 9-9. ZTAP-TKN-TAPE-VOLUME Subject token that specifies the volume serial number of the requested volume. Conditional Tokens Token Description ZTAP-TKN-REEL Reel number, if this operation is a multivolume operation. ZTAP-TKN-DENSITY Tape density.
PAGE 224
Messages Labeled-Tape Server Events Messages (ZTAP) 612: ZTAP-EVT-AVRERR An AVR error occurred.
PAGE 225
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. If the tape is blank, mount the correct tape. If the density switch is incorrectly set, set the density switch to the value indicated on the tape volume. If none of these errors occurred, check the tape device. 613: ZTAP-EVT-PROCTECTERR A protection-violation error occurred.
PAGE 226
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. To use the tape, run TAPECOM SCRATCH or MEDIACOM ADDTAPELABEL SCRATCH to make the volume a scratch tape; then repeat the operation that caused the error. 614: ZTAP-EVT-WRONGTAPEERR A tape device was expecting a specific continuation volume.
PAGE 227
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. Either mount the correct tape volume or, if the volume requested by the application is not available, abort the operation by rejecting the mount request with TAPECOM or MEDIACOM. 615: ZTAP-EVT-NOTLTERR The mounted tape volume is not a labeled tape.
PAGE 228
Messages Labeled-Tape Server Events Messages (ZTAP) 616: ZTAP-EVT-USENLTAPEERR An unlabeled tape was requested, but the mounted tape volume is a labeled tape.
PAGE 229
Messages Labeled-Tape Server Events Messages (ZTAP) 617: ZTAP-EVT-USEIBMTAPEERR An IBM labeled tape was requested, but the mounted tape volume is an ANSI labeled tape.
PAGE 230
Messages Labeled-Tape Server Events Messages (ZTAP) 618: ZTAP-EVT-USEANSITAPEERR An ANSI labeled tape was requested, but the mounted tape volume is an IBM labeled tape.
PAGE 231
Messages Labeled-Tape Server Events Messages (ZTAP) 619: ZTAP-EVT-WRITEPROTECTERR A file write-protect error occurred.
PAGE 232
Messages Labeled-Tape Server Events Messages (ZTAP) 620: ZTAP-EVT-NOTMFTAPEERR The mounted tape volume is a TMF tape—do not use it.
PAGE 233
Messages Labeled-Tape Server Events Messages (ZTAP) 621: ZTAP-EVT-INPUTINCOMPERR The file did not end on the last volume specified in the DEFINE attribute.
PAGE 234
Messages Labeled-Tape Server Events Messages (ZTAP) 622: ZTAP-EVT-USEBACKUPTAPEERR A volume was mounted to satisfy a backup request, but the volume had an IBM label.
PAGE 235
Messages Labeled-Tape Server Events Messages (ZTAP) 623: ZTAP-EVT-USETMFNOTANSIERR A tape device expected a TMF labeled tape, but the mounted tape was an ANSI labeled tape.
PAGE 236
Messages Labeled-Tape Server Events Messages (ZTAP) 624: ZTAP-EVT-USETMFNOTIBMERR A tape device expected a TMF labeled tape, but the mounted tape was an IBM labeled tape.
PAGE 237
Messages Labeled-Tape Server Events Messages (ZTAP) 625: ZTAP-EVT-USETMFNOTBKUPERR A tape device expected a TMF labeled tape, but the mounted tape was a BACKUP labeled tape.
PAGE 238
Messages Labeled-Tape Server Events Messages (ZTAP) 626: ZTAP-EVT-BADTRAILERERR The system failed to finish writing the trailer labels.
PAGE 239
Messages Labeled-Tape Server Events Messages (ZTAP) Effect. Trailer labels for an output file on a labeled tape are written when the file is closed. Because no error was returned from the file-system CLOSE procedure, the application that called CLOSE continues processing. This event message is the only indication of the error. Recovery. If the trailer labels are relevant, the application must retry the operation.
PAGE 240
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. Correct the DEFINE value indicated in the ZTAP-TKN-BADNUM token. If the DEFINE value is correct (within the allowable range), make a note of this event message and see Recovery Action Requiring Vendor Support on page 9-12. 629: ZTAP-EVT-USESCRATCHERR The mounted tape is an unlabeled tape, but a scratch tape was requested.
PAGE 241
Messages Labeled-Tape Server Events Messages (ZTAP) 630: ZTAP-EVT-OPENRECEIVEERR The $ZSVR process failed to open $RECEIVE.
PAGE 242
Messages Labeled-Tape Server Events Messages (ZTAP) 631: ZTAP-EVT-READRECEIVEERR The $ZSVR process failed to read $RECEIVE.
PAGE 243
Messages Labeled-Tape Server Events Messages (ZTAP) 632: ZTAP-EVT-NOMEMERR Insufficient memory is available to run the $ZSVR process.
PAGE 244
Messages Labeled-Tape Server Events Messages (ZTAP) 633: ZTAP-EVT-DATALENERR The $ZSVR process received an incomplete data buffer from MEDIACOM.
PAGE 245
Messages Labeled-Tape Server Events Messages (ZTAP) 634: ZTAP-EVT-VOLUMEREJECT The mount request for the specified tape volume was rejected by the operator.
PAGE 246
Messages Labeled-Tape Server Events Messages (ZTAP) 635: ZTAP-EVT-ZSVRUP The $ZSVR process started successfully.
PAGE 247
Messages Labeled-Tape Server Events Messages (ZTAP) 636: ZTAP-EVT-TAPECOMREJECT The operator used MEDIACOM used to reject a mount or device request.
PAGE 248
Messages Labeled-Tape Server Events Messages (ZTAP) 637: ZTAP-EVT-TAPECOMACCEPT The operator used MEDIACOM to accept a mount or device request.
PAGE 249
Messages Labeled-Tape Server Events Messages (ZTAP) 638: ZTAP-EVT-TAPEOPENED The $ZSVR process matched a request for the specified tape volume and device.
PAGE 250
Messages Labeled-Tape Server Events Messages (ZTAP) Cause. $ZSVR matched a request for the specified tape volume and device. An action-attention event asking the operator to mount the tape does not necessarily precede this event. The required tape might have been mounted before the application requested it. For an unlabeled open of a tape, the status 1504 message might occur even if there is no tape online. The message does not include a volume name for any unlabeled opens. Effect. None. Recovery.
PAGE 251
Messages Labeled-Tape Server Events Messages (ZTAP) Cause. An unrequested unlabeled tape is mounted because either:   The operator promenaded the tape for an upcoming request. The operator mounted the wrong tape. Effect. The tape is used to satisfy subsequent mount requests. Recovery. Ensure that the correct tape is mounted and that a mount request is issued. 640: ZTAP-EVT-ANSITAPEONLINE An ANSI labeled tape is mounted, but there has been no request for it.
PAGE 252
Messages Labeled-Tape Server Events Messages (ZTAP) Cause. An unrequested ANSI labeled tape is mounted because either:    The operator promenaded the tape for an upcoming request. The operator mounted the wrong tape. The operator mounted a requested tape on the wrong tape drive. Effect. The tape is used to satisfy subsequent mount requests. Recovery. Ensure that the correct tape is mounted on the correct device and that a mount request is issued.
PAGE 253
Messages Labeled-Tape Server Events Messages (ZTAP) Cause. An unrequested IBM labeled tape is mounted because either:   The operator promenaded a tape for an upcoming request. The operator mounted a requested tape on the wrong tape drive. Effect. The tape is used to satisfy subsequent request for the volume. Recovery. Ensure that the correct tape is mounted on the correct device and that a mount request is issued.
PAGE 254
Messages Labeled-Tape Server Events Messages (ZTAP) Effect. The tape is used to satisfy subsequent mount requests. Recovery. Ensure that the correct tape is mounted and that a mount request is issued after the tape is mounted. If you want to substitute this TMF tape for another, for output only, use the TAPECOM command USETAPE or MEDIACOM ALTER TAPEMOUNT. 643: ZTAP-EVT-BKUPTAPEONLINE A BACKUP labeled tape is mounted, but there has been no request for it.
PAGE 255
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. Ensure that the correct tape is mounted on the correct device and that a mount request is issued. 644: ZTAP-EVT-TMFTAPEONLINE A new-format TMF labeled tape is mounted, but there has been no request for it.
PAGE 256
Messages Labeled-Tape Server Events Messages (ZTAP) 645: ZTAP-EVT-BADTRAILERWARN An error was returned from the tape device while the $ZSVR process was reading the trailer labels that follow the input data.
PAGE 257
Messages Labeled-Tape Server Events Messages (ZTAP) 646: ZTAP-EVT-BADBLKCTWARN The block count in the file trailer label does not match the number of blocks in the file.
PAGE 258
Messages Labeled-Tape Server Events Messages (ZTAP) 647: ZTAP-EVT-INPUTENDWARN A file ended on a volume that is before the last volume specified.
PAGE 259
Messages Labeled-Tape Server Events Messages (ZTAP) 648: ZTAP-EVT-ACCEPTMOUNT This action-completion message indicates that a tape was mounted to satisfy an earlier action-attention event message.
PAGE 260
Messages Labeled-Tape Server Events Messages (ZTAP) 649: ZTAP-EVT-CANCELMOUNT This action-completion message indicates that a request for a tape mount from an earlier action-attention event message was canceled.
PAGE 261
Messages Labeled-Tape Server Events Messages (ZTAP) 650: ZTAP-EVT-CANCELDEVICE This action-completion message indicates that a request for a tape device from an earlier action-attention event message was canceled.
PAGE 262
Messages Labeled-Tape Server Events Messages (ZTAP) 651: ZTAP-EVT-REJECTMOUNT This action-completion message indicates that was rejected by the operator a request for a tape mount from an earlier action-attention event message.
PAGE 263
Messages Labeled-Tape Server Events Messages (ZTAP) 652: ZTAP-EVT-ACCEPTDEVICE This action-completion message indicates that was accepted by the operator a request for a tape device from an earlier action-attention event message.
PAGE 264
Messages Labeled-Tape Server Events Messages (ZTAP) 653: ZTAP-EVT-REJECTDEVICE This action-completion message indicates that was rejected by the operator a request for a tape device from an earlier action-attention event message.
PAGE 265
Messages Labeled-Tape Server Events Messages (ZTAP) 654: ZTAP-EVT-DENSITYCHANGED The tape density specified in the DEFINE for a tape is different from the existing density of the volume. Data is written at the density requested in the DEFINE.
PAGE 266
Messages Labeled-Tape Server Events Messages (ZTAP) Cause. The first file is being written to a tape volume on a tape drive on which the tape density can be set programmatically (5106 or 5130), and the tape density specified in the DEFINE for the tape is different from the existing tape density of the volume. This warning message is displayed only when a volume is open for output. Effect. Data is written at the density specified in the DEFINE. Recovery. This is a warning message only.
PAGE 267
Messages Labeled-Tape Server Events Messages (ZTAP) Token Description (page 2 of 2) ZTAP-TKN-WRNMSGNUMBER $ZSVR warning message number (905). ZTAP-TKN-TAPE-VOLUME Subject token that specifies the volume serial number of the tape volume. ZTAP-TKN-NEW-TAPEMODE Tape mode being used. Values are either ZTAP-VALSTREAM or ZTAP-VAL-STARTSTOP. ZTAP-TKN-OLD-TAPEMODE Old tape mode. Values are either ZTAP-VAL-STREAM or ZTAP-VAL-STARTSTOP. Cause.
PAGE 268
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTDENSITYUSED (656). ZTAP-TKN-DEV-NAME Subject token that specifies the tape drive device name in the system. ZEMS-TKN-TEXT Standard EMS token that contains the message text. See Event Management Service (EMS) Standard Definitions on page 9-9. ZTAP-TKN-WRNMSGNUMBER $ZSVR warning message number (906).
PAGE 269
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZTAP-TKN-DEV-NAME ZEMS-TKN-TEXT ZTAP-TKN-WRNMSGNUMBER ZTAP-TKN-TAPE-VOLUME ZTAP-TKN-USED-TAPEMODE ZTAP-TKN-REQD-TAPEMODE token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-DEVICE ZSPI-TYP-STRING ZSPI-TYP-INT ZTAP-TYP-TAPE-VOLUME ZSPI-TYP-INT ZSPI-TYP-INT Event-Message Text WARNING 907 - VOLUME vid IS aaa INSTEAD OF bbb Unconditional Tokens Token Description ZE
PAGE 270
Messages Labeled-Tape Server Events Messages (ZTAP) 658: ZTAP-EVT-NOTEXPIRED The requested tape was mounted in response to an output request, but the tape was not expired.
PAGE 271
Messages Labeled-Tape Server Events Messages (ZTAP) 659: ZTAP-EVT-DISMOUNTED A tape was dismounted from a drive.
PAGE 272
Messages Labeled-Tape Server Events Messages (ZTAP) 660: ZTAP-EVT-SQUEALERSTATUS A Guardian file-system error has occurred.
PAGE 273
Messages Labeled-Tape Server Events Messages (ZTAP) Table 9-4. ZTAP-TKN-SQUEALER-TYPE Values (page 2 of 2) Value Meaning 5 An unexpected message length was returned by the enforcer process, $XENF. file-system-error is 0. The operation fails with Guardian file-system error 48 (FESECVIOL). 6 An unexpected reply was returned by the enforcer process, $XENF. filesystem-error is 0. The operation fails with Guardian file-system error 48 (FESECVIOL). Cause. See Table 9-4 on page 9-80. Effect.
PAGE 274
Messages Labeled-Tape Server Events Messages (ZTAP) Token Description (page 2 of 2) ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZTAP-TKN-PROCESS Subject token that specifies the process for this event. ZTAP-TKN-ERRMSGNUMBER Labeled-tape defined error number (1005). ZEMS-TKN-TEXT is the standard EMS token that contains the message text.
PAGE 275
Messages Labeled-Tape Server Events Messages (ZTAP) Token Description (page 2 of 2) ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZTAP-TKN-PROCESS Subject token that specifies the process for this event. ZTAP-TKN-ERRMSGNUMBER Labeled-tape defined error number (1006). ZTAP-TKN-FSERR File-system error number received. Cause.
PAGE 276
Messages Labeled-Tape Server Events Messages (ZTAP) Token Description (page 2 of 2) ZTAP-TKN-PROCESS Subject token that specifies the process for this event. ZTAP-TKN-ERRMSGNUMBER Labeled-tape defined error number (1007). ZTAP-TKN-BADNUM DSM/TC error number. Cause. MEDIADBM was unable to process the $ZSVR request because of the DSM/TC error reported in the message. Effect. If $ZSVR is servicing a mount request, the application process making the request fails with file-system error 594.
PAGE 277
Messages Labeled-Tape Server Events Messages (ZTAP) Token Description (page 2 of 2) ZTAP-TKN-PROCESS Subject token that specifies the process for this event. ZTAP-TKN-ERRMSGNUMBER Labeled-tape defined error number (1008). ZTAP-TKN-FSERR File-system error number received. Cause. $ZSVR could not create the MEDDEM process because of a file-system error. Effect. No DSM/TC cleanup can be done. No tape volumes expire automatically. Recovery.
PAGE 278
Messages Labeled-Tape Server Events Messages (ZTAP) Effect. The DSM/TC database has been checked, and its Structured Query Language (SQL) statistics have been updated to optimize performance. Recovery. This is an informational message only; no corrective action is needed. 666: ZTAP-EVT-MOUNTCORRECTERR The wrong tape is mounted on a tape drive.
PAGE 279
Messages Labeled-Tape Server Events Messages (ZTAP) 667: ZTAP-EVT-SSIOPEN The $ZSVR process could not create the storage server interface (ZSSI) process.
PAGE 280
Messages Labeled-Tape Server Events Messages (ZTAP) 668: ZTAP-EVT-SSIWRITEREAD The $ZSVR process sent a message to the storage server interface (SSI) process, but a file-system error was returned.
PAGE 281
Messages Labeled-Tape Server Events Messages (ZTAP) 669: ZTAP-EVT-SSIRETRY The $ZSVR process has received a nonfatal error from the Storage Server Interface (ZSSI) process.
PAGE 282
Messages Labeled-Tape Server Events Messages (ZTAP) 670: ZTAP-EVT-SSINORETRY The $ZSVR process received a nonretryable fatal error from the SSI process.
PAGE 283
Messages Labeled-Tape Server Events Messages (ZTAP) 671: ZTAP-EVT-SSINODRIVE No tape drive was specified in the DEFINE and all tape drives in the ACS are busy.
PAGE 284
Messages Labeled-Tape Server Events Messages (ZTAP) 672: ZTAP-EVT-SSIMISMATCH The $ZSVR process detected a mismatched tape mounted in an ACS.
PAGE 285
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. This is an informational message only; no corrective action is needed. In order to use this tape in the ACS, the tape must be relabeled using the MEDIACOM ADD TAPELABEL command. For more information on this error, see the DSM/Tape Catalog Management Programming Manual. For further assistance, see Recovery Action Requiring Vendor Support on page 9-12.
PAGE 286
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. Check that the tape volume was unloaded from the tape drive. 674: ZTAP-EVT-SSIWRONGTYPE The $ZSVR process detected a mismatched tape type mounted in an ACS.
PAGE 287
Messages Labeled-Tape Server Events Messages (ZTAP) Effect. The application receives file-system error 595, and the tape volume is dismounted from the tape cartridge. (The name of the tape was correct, but the label attribute was mismatched.) For more information on this error, see the DSM/Tape Catalog Management Programming Manual. Recovery. Either label the tape correctly or use a different tape volume, and retry the application.
PAGE 288
Messages Labeled-Tape Server Events Messages (ZTAP) 676: ZTAP-EVT-CMNOSCRATCH The pool specified in the TAPECATALOG DEFINE attribute is out of scratch tape volumes that match the appropriate type.
PAGE 289
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. Either add more scratch tapes of the correct type or use the MEDIACOM command DELETE TAPEFILE to free some tape volumes. $ZSVR automatically retries the operation. The request continues automatically when more scratch tapes are made available. 677: ZTAP-EVT-CMWRONGFILESECT The FILESECT attribute specified in a TAPECATALOG DEFINE is incorrect.
PAGE 290
Messages Labeled-Tape Server Events Messages (ZTAP) 678: ZTAP-EVT-CMWRONGVOLUME The volume name specified in a TAPECATALOG DEFINE was not used for the specified FILEID.
PAGE 291
Messages Labeled-Tape Server Events Messages (ZTAP) 679: ZTAP-EVT-CMNOTSCRATCH The volume name specified in a tape DEFINE could not be used.
PAGE 292
Messages Labeled-Tape Server Events Messages (ZTAP) 680: ZTAP-EVT-CMNOTASSIGNED The volume name specified in a tape DEFINE could not be used because it is not assigned.
PAGE 293
Messages Labeled-Tape Server Events Messages (ZTAP) 681: ZTAP-EVT-CMNEEDVOLUME The volume name was not specified in the TAPECATALOG DEFINE when writing multifile volume sets (FILESEQ > 1).
PAGE 294
Messages Labeled-Tape Server Events Messages (ZTAP) 682: ZTAP-EVT-CMWRONGFILESEQ The FILESEQ attribute specified in the TAPECATALOG DEFINE for the file identification is incorrect.
PAGE 295
Messages Labeled-Tape Server Events Messages (ZTAP) 683: ZTAP-EVT-CMNOALTAVAILABLE A MEDIACOM ALTER TAPEMOUNT command was attempted but no alternate copy is available.
PAGE 296
Messages Labeled-Tape Server Events Messages (ZTAP) 684: ZTAP-EVT-SSINOAVR A tape successfully mounted in an ACS was not being detected by the tape drive.
PAGE 297
Messages Labeled-Tape Server Events Messages (ZTAP) Effect. The open operation fails and file-system error 595 is returned. Recovery. Correct the problem with the tape drive and retry the operation. If the problem cannot be corrected, use the Subsystem Control Facility (SCF) STOP TAPE command to stop the system from using the tape drive for automated cartridge tapes. 685: ZTAP-EVT-CMCONSOLEWRITE An error occurred during an attempt to send a message to the DSM/TC console.
PAGE 298
Messages Labeled-Tape Server Events Messages (ZTAP) Effect. The DSM/TC console is automatically closed. Recovery. To reopen the DSM/TC console, use the MEDIACOM ALTER CONSOLE command. 686: ZTAP-EVT-LINKDOWN An error occurred during an attempt to communicate with a tape drive.
PAGE 299
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. Connection to the tape drive is retried automatically as follows:    If the processor is down, reload the primary processor or backup processor of the device. If the processor is not down, perform a MEDIACOM STATUS TAPEDRIVE device command on the tape drive. Stop the primary $ZSVR process. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 9-12.
PAGE 300
Messages Labeled-Tape Server Events Messages (ZTAP) 688: ZTAP-EVT-TAPEFILEABEND An application using a tape drive without closing the tape file.
PAGE 301
Messages Labeled-Tape Server Events Messages (ZTAP) 689: ZTAP-EVT-TPTMUP A connection to the Third Party Tapes Manager (TPTM) was completed successfully.
PAGE 302
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-ACTION-NEEDED ZEMS-TKN-ACTION-ID ZTAP-TKN-PROCESS ZTAP-TKN-ERRMSGNUMBER ZTAP-TKN-FSERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-BOOLEAN ZSPI-TYP-INT ZSPI-TYP-CRTPID ZSPI-TYP-UINT ZSPI-TYP-ENUM Event-Message Text ERROR 1030 - CONNECTION TO TPTM FAILED WITH ERROR num Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this messa
PAGE 303
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-ACTION-NEEDED ZEMS-TKN-ACTION-ID ZTAP-TKN-PROCESS token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-BOOLEAN ZSPI-TYP-INT ZSPI-TYP-CRTPID Event-Message Text ERROR 1031 - SEVERING CONNECTION TO TPTM Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTTPTMSEVERED (691). ZEMS-TKN-ACTION-NEEDED Has the value ZSPI-VAL-FALSE.
PAGE 304
Messages Labeled-Tape Server Events Messages (ZTAP) Event-Message Text ERROR 1032 - TPTM REJECTED REQUEST WITH ERROR num Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTTPTMREJECTED (692). ZEMS-TKN-ACTION-NEEDED Has the value ZSPI-VAL-FALSE. ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999.
PAGE 305
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTTPTMREJECTEDLABEL (693). ZEMS-TKN-ACTION-NEEDED Has the value ZSPI-VAL-FALSE. ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZTAP-TKN-PROCESS Subject token that specifies the process for this event.
PAGE 306
Messages Labeled-Tape Server Events Messages (ZTAP) Token Description (page 2 of 2) ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZTAP-TKN-PROCESS Subject token that specifies the process for this event. ZTAP-TKN-ERRMSGNUMBER Labeled-tape defined error number (1034). ZTAP-TKN-FSERR File-system error number received. Cause.
PAGE 307
Messages Labeled-Tape Server Events Messages (ZTAP) Token Description (page 2 of 2) ZTAP-TKNWRNMSGNUMBER $ZSVR warning message number (909). ZTAP-TKN-TAPE-VOLUME Subject token that specifies the volume serial number of the correct volume to use. ZTAP-TKN-DEV-NAME Subject token that specifies the device name. Cause. The requested and actual tape density or tape mode did not match. The requested tape volume is not mounted on the tape drive that does not support the requested DENSITY/TAPEMODE.
PAGE 308
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTSSINOTAPE (696). ZEMS-TKN-ACTION-NEEDED Has the value ZSPI-VAL-FALSE. ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZTAP-TKN-DEV-NAME Subject token that specifies the device name.
PAGE 309
Labeled-Tape Server Events Messages (ZTAP) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTALTERTAPEMOUNT (697). ZEMS-TKN-ACTION-NEEDED Has the value ZSPI-VAL-FALSE. ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZTAP-TKN-DEV-NAME Subject token that specifies the device name.
PAGE 310
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-ACTION-NEEDED ZEMS-TKN-ACTION-ID ZTAP-TKN-DEV-NAME ZTAP-TKN-ERRMSGNUMBER ZTAP-TKN-DEFINE-NAME ZTAP-TKN-BADNUM token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-BOOLEAN ZSPI-TYP-INT ZSPI-TYP-DEVICE ZSPI-TYP-UINT ZTAP-TYP-DEFINE-NAME ZSPI-TYP-UINT Event-Message Text ERROR 1037 - TAPE AUTO SUBSTITUTE FOR define-name FAILED WITH ERROR num Unconditional Tok
PAGE 311
Messages Labeled-Tape Server Events Messages (ZTAP) 699: ZTAP-EVT-TAPEINUSE A tape volume is now being used by the specified process.
PAGE 312
Messages Labeled-Tape Server Events Messages (ZTAP) 700: ZTAP-EVT-TAKEOVER The primary $ZSVR process has stopped and the backup $ZSVR process has successfully taken over.
PAGE 313
Messages Labeled-Tape Server Events Messages (ZTAP) 701: ZTAP-EVT-SSIACCESSDENIED Access was denied to the requested ACS tape volume.
PAGE 314
Messages Labeled-Tape Server Events Messages (ZTAP) 702: ZTAP-EVT-DOWNREVMDBM The local MEDIADBM program has an incompatible version.
PAGE 315
Messages Labeled-Tape Server Events Messages (ZTAP) 703: ZTAP-EVT-FSEQMATCH $ZSVR used a currently mounted tape volume instead of a requested one.
PAGE 316
Messages Labeled-Tape Server Events Messages (ZTAP) 704: ZTAP-EVT-ESMTAPEONLINE An ESM tape that was not requested is mounted.
PAGE 317
Messages Labeled-Tape Server Events Messages (ZTAP) 705: ZTAP-EVT-MTESMOUT A tape file was opened for output for ESM processing, but the tape was not mounted.
PAGE 318
Messages Labeled-Tape Server Events Messages (ZTAP) Conditional Tokens Token Description ZTAP-TKN-REEL Reel number, if this operation is a multivolume operation. ZTAP-TKN-DENSITY Tape density. Values are ZSPI-VAL-800BPI, ZSPI-VAL1600BPI, and ZSPI-VAL-6250BPI. ZTAP-TKN-DEV-NAME Subject token that specifies the tape drive device name in the system. This token is present if the request is for a continuation volume of a multivolume operation or if the user requested a specific device.
PAGE 319
Messages Labeled-Tape Server Events Messages (ZTAP) Event-Message Text MOUNT ESM volser [REEL reel] [DENSITY density] [ON drive] NO RING ALIAS = alias Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTMTESMIN (706). ZEMS-TKN-ACTION-ID $ZSVR internal message number that identifies the request. This token contains a four-digit number ranging from 0000 through 9999. ZEMS-TKN-TEXT Standard EMS token that contains the message text.
PAGE 320
Messages Labeled-Tape Server Events Messages (ZTAP) 707: ZTAP-EVT-TPTMWRITEREAD An error occurred during an attempt to WRITEREAD to TPTM.
PAGE 321
Messages Labeled-Tape Server Events Messages (ZTAP) 708: ZTAP-EVT-TPTMTIMEOUT A request to TPTM timed out.
PAGE 322
Messages Labeled-Tape Server Events Messages (ZTAP) 709: ZTAP-EVT-TPTMNOTCONFIGURED A request to TPTM aborted because TPTM is not configured.
PAGE 323
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. If a third-party tape manager is to be used: 1. Verify that the MEDIADEFS level is INTEGRATED, TPTM, or TPTMCOMPATIBLE. 2. Stop the TPTM process, if it is running. 3. Start the TPTM process. If a third-party tape manager is not to be used, verify that the MEDIADEFS level is NOT INTEGRATED, TPTM, or TPTMCOMPATIBLE. 713: ZTAP-EVT-SSIDRIVEBUSY The ACS drive specified in DEFINE is currently busy.
PAGE 324
Messages Labeled-Tape Server Events Messages (ZTAP) Recovery. This is an informational message only; no corrective action is needed. 992: ZTAP-EVT-SYN-CMD-ABORT An operation was aborted by a tape device.
PAGE 325
Messages Labeled-Tape Server Events Messages (ZTAP) 993: ZTAP-EVT-SYN-CMD-ABORT-ON-REQ An operation was aborted by a tape device.
PAGE 326
Messages Labeled-Tape Server Events Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-DEVICE token-type ZSPI-TYP-UINT Event-Message Text $device-name error-injection, LDEV $logical-device-number Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNERR-INJECTION (1008). ZTAP-TKN-XLDEVNAME Name of the tape device in the form $nnnn.
PAGE 327
Labeled-Tape Server Events Messages (ZTAP) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTEXCEPT-ERR (5101). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Logical device number of the tape device. ZEMS-MAP-PHYSICALADDRESS.ZEMS-DDLPHYSICAL-ADDRESS.ZPAGROUP Group number of the physical address of the tape device. ZEMS-MAP-PHYSICALADDRESS.
PAGE 328
Labeled-Tape Server Events Messages (ZTAP) HP NonStop Operating System Event Management Programming Manual—520372-020 9-136 Messages
PAGE 329
10 Tape Process Event Messages (ZTAP) Tape process event messages are reported to the EMS only by the tape process. Table 10-1. Tape Process Event Messages (page 1 of 7) Event Number and Symbolic Name Description -1032: ZTAP-EVT-DEV-RESET A tape drive has been reset by its controller. -1031: ZTAP-EVT-DEV-IF-ERROR An error occurred between a tape drive controller and a tape drive. -1030: ZTAP-EVT-DEV-SCSI-STATUS A tape drive reported a SCSI status.
PAGE 330
Tape Process Event Messages (ZTAP) Table 10-1. Tape Process Event Messages (page 2 of 7) Event Number and Symbolic Name Description -1014: ZTAP-EVT-RECOVERY-COMPLETION A sense key reported an error recovery. -1013: ZTAP-EVT-SK-MISCOMPARE A sense key reported that source data did not match read data. -1012: ZTAP-EVT-SK-VOL-OVFLOW A sense key reported that end-ofpartition and unwritten data was left in a buffer.
PAGE 331
Tape Process Event Messages (ZTAP) Table 10-1. Tape Process Event Messages (page 3 of 7) Event Number and Symbolic Name Description 97: ZTAP-EVT-SYN-MD-STRUCT-ERR A module driver structure error occurred. 98: ZTAP-EVT-SYN-MD-MB-SM-ERR A module driver structure error occurred. 99: ZTAP-EVT-SYN-MD-CONFIG-ERR A module driver configuration error occurred. 100: ZTAP-EVT-WRITE-RETRIED A tape write operation was retried. 101: ZTAP-EVT-READ-RETRIED A tape read operation was retried.
PAGE 332
Tape Process Event Messages (ZTAP) Table 10-1. Tape Process Event Messages (page 4 of 7) Event Number and Symbolic Name Description 194: ZTAP-EVT-SYN-DEV-CMD-INCOMP A tape drive was performing another action when another command was received. 195: ZTAP-EVT-SYN-DEV-BUSY A tape drive was performing another operation when another command was received. 196: ZTAP-EVT-SYN-SCSI-STATUS A command was incomplete. 197: ZTAP-EVT-SYN-DEV-INTF-ERR An error occurred between a tape drive and a controller.
PAGE 333
Tape Process Event Messages (ZTAP) Table 10-1. Tape Process Event Messages (page 5 of 7) Event Number and Symbolic Name Description 288: ZTAP-EVT-SYN-SCSI-BUS-RESET A SCSI-bus reset was issued by a controller. 289: ZTAP-EVT-SYN-SCSI-BUS-IN A SCSI-bus reset was initiated by some external cause, not by a controller. 300: ZTAP-EVT-DATA-CORRECTED A correctable data error occurred. 301: ZTAP-EVT-DATA-UNCORRECTED An uncorrectable data error occurred.
PAGE 334
Tape Process Event Messages (ZTAP) Table 10-1. Tape Process Event Messages (page 6 of 7) Event Number and Symbolic Name Description 322: ZTAP-EVT-3202-UNUSUAL-END A 3202 controller indicated an unusual end. 323: ZTAP-EVT-3202-COMMAND-REJECT A 3202 controller rejected a command. 324: ZTAP-EVT-3202-OVERRUN A 3202 controller detected an overrun condition. 325: ZTAP-EVT-3202-PARITY-ERROR A 3202 controller detected a parity error. 326: ZTAP-EVT-3202-CRCERROR A 3202 controller detected a CRC error.
PAGE 335
Common Definitions Tape Process Event Messages (ZTAP) Table 10-1. Tape Process Event Messages (page 7 of 7) Event Number and Symbolic Name Description 408: ZTAP-EVT-SET-BURST-EIO A SET BURST EIO instruction was executed. 409: ZTAP-EVT-SET-HOLDOFF-EIO A SET HOLDOFF EIO instruction was executed. 410: ZTAP-EVT-UNEXPECTED-INT An unexpected interrupt occurred. 511: ZTAP-EVT-TAPE-STACK Stack information has been added to an error event.
PAGE 336
Event Management Service (EMS) Standard Definitions Tape Process Event Messages (ZTAP) Table 10-2. SPI Standard Definitions Used in Tape Process Event Messages Header Tokens Token Types Value Names ZSPI-TKN-SSID ZSPI-TKN-USEDLEN ZSPI-TYP-BOOLEAN ZSPI-TYP-BYTE-PAIR ZSPI-TYP-CHAR8 ZSPI-TYP-DEVICE ZSPI-TYP-ENUM ZSPI-TYP-STRING ZSPI-TYP-UINT ZSPI-SSN-ZTAP ZSPI-VAL-FALSE ZSPI-VAL-TANDEM ZSPI-VAL-TRUE Figure 10-1. ZTAP-VAL-SSID Structure def ZTAP-VAL-SSID tacl ssid.
PAGE 337
Tape Process (ZTAP-) Definitions Tape Process Event Messages (ZTAP) Token Description ZEMS-TKN-ACTION-NEEDED Occurs in event message pairs. The first message indicates that operation intervention is needed (ZSPIVAL-TRUE), and the second message indicates that operator intervention is completed (ZSPI-VAL-FALSE). ZEMS-TKN-EMPHASIS Has the value ZSPI-VAL-TRUE for those tape process event messages that are potentially critical. Otherwise ZEMS-TKN-EMPHASIS always has the value ZSPI-VALFALSE.
PAGE 338
Tape Process (ZTAP-) Definitions Tape Process Event Messages (ZTAP) Predefined Token and Field Values Token Description ZTAP-VAL-SSID Tape process subsystem ID—the structure is shown under the description for ZSPI-TKN-SSID ZTAP-VAL-VERSION Version number of the tape process subsystem Simple Tokens and Structured Tokens Unconditional tokens appear in all tape process event messages; conditional tokens appear in tape process event messages only under certain conditions.
PAGE 339
Tape Process (ZTAP-) Definitions Tape Process Event Messages (ZTAP) Token Description (page 2 of 2) ZTAP-TKN-DETECTOR-REV Two ASCII characters that specify the revision level of the detecting process for the event. ZTAP-TKN-CPU Indicates (in bytes [0]) the processor number of the processor that is executing the primary tape process that initiated the event. ZTAP-TKN-PIN PIN of the tape process that initiated the event. ZTAP-TKN-LDEV Logical device number of the tape device.
PAGE 340
Tape Process (ZTAP-) Definitions Tape Process Event Messages (ZTAP) Token Description (page 2 of 2) ZTAP-TKN-EIO-RDST EIO instruction RDST word (see Table 10-4). ZTAP-TKN-EIO-CHANSTAT EIO instruction channel status word (see Table 10-5). ZTAP-TKN-IIO-RIC RIC word returned by the IIO instruction (see Table 10-6 on page 10-13). ZTAP-TKN-IIO-RIST RIST word returned by the IIO instruction (see Table 10-7 on page 10-13).
PAGE 341
Tape Process Event Messages (ZTAP) Tape Process (ZTAP-) Definitions Table 10-6. ZTAP-TKN-IIO-RIC Values Bit Position Meaning <0> If equal to 1, unit power is on. <1> If equal to 1, tape is positioned at the beginning (BOT). <2> If equal to 1, tape is positioned at a file mark (EOF). <3> If equal to 1, tape is positioned at the end (EOT). <4> If equal to 1, tape is online and ready. <5> If equal to 1, tape is write-enabled. <6> If equal to 1, tape is rewinding.
PAGE 342
Description of ZTAP Event Messages Tape Process Event Messages (ZTAP) Description of ZTAP Event Messages Token Description ZTAP-TKN-IOC-COUNT Original IOC byte count. ZTAP-TKN-IOC-RESIDUE Residual IOC entry after the data transfer. ZTAP-TKN-RETRY-CNT Total number of retries for the write retry event (ZTAP-EVTWRITE-RETRIED), read retry event (ZTAP-EVT-READRETRIED), and correctable data error event (ZTAP-EVTDATA-CORRECTED). ZTAP-TKN-TAPE-VOLUME 6-byte volume serial number for a labeled tape volume.
PAGE 343
Recovery Action Requiring Vendor Support Tape Process Event Messages (ZTAP)    Identifying the sender of the event message to the EMS collector ($0 process). Indicating whether the event message is sent to the TMDS collector (D-series NonStop operating system RVUs) or OSM/TSM collector (G-series and Hseries NonStop operating system RVUs). A box contains the list of tokens that can appear in the event message.
PAGE 344
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn Device reset, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-DEVRESET (-1032). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 345
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-DEVIF-ERROR (-1031). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. A controller or SCSI bus error occurred when a command was sent from the controller to the tape drive. Effect. The command fails.
PAGE 346
Messages Tape Process Event Messages (ZTAP) Cause. This function is not supported. Effect. None. Recovery. None. -1029: ZTAP-EVT-DEV-BUSY A tape drive reported an incomplete command.
PAGE 347
Messages Tape Process Event Messages (ZTAP) -1028: ZTAP-EVT-DEV-CMD-INCOMP A tape drive reported an incomplete command.
PAGE 348
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn Device command timeout, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-DEVCMD-TIMEOUT (-1027). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 349
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-DEVSEL-TIMEOUT (-1026). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. There is a tape drive or tape-drive controller problem. Effect. The drive cannot be selected. Recovery.
PAGE 350
Messages Tape Process Event Messages (ZTAP) Event-Message Text dev-name INTERRUPT TIMED OUT, LDEV $ldev, PHYS ADDR: GROUP group,MODULER module, SLOT slot, TARGET ID scsi-target-id,LUN scsi-lun, FABRIC fabric, SAC NAME sac-name Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTCTLR-DOWNLOADED-CMN (-1025). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device.
PAGE 351
Messages Tape Process Event Messages (ZTAP) -1024: ZTAP-EVT-STRUCTURED-XSUM-CMN A tape drive reported a structured checksum error.
PAGE 352
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn Sector checksum error, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTSECTOR-XSUM (-1023). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 353
Messages Tape Process Event Messages (ZTAP) ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN ZEMS-TKN-SERVERNET-FABRIC ZEMS-TKN-SAC-NAME token-type ZSPI-TYP-INT4 token-type ZSPI-TYP-INT4 token-type ZEMS-TYPSERVERNET-FABRIC token-type ZSPI-TYP-INT4 Event-Message Text dev-name UNEXPECTED INTERRUPT, LDEV $ldev, PHYS ADDR: GROUP group,MODULER module, SLOT slot, TARGET ID scsi-target-id,LUN scsi-lun, FABRIC fabric, SAC NAME sac-name Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for th
PAGE 354
Messages Tape Process Event Messages (ZTAP) -1021: ZTAP-EVT-INT-TIMEOUT-CMN An interrupt time-out has been detected. Subject: ZTAP-TKN-DEV-NAME Potentially critical event: No Action event: No Message sender: Tape process OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZTAP-TKN-DEV-NAME ZEMS-TKN-XLDEVNAME ZEMS-TKN-COMMAND ZEMS-TKN-MAP-PHYSICAL-ADDRESS. ZEMS-DDL-PHYSICAL-ADDRESS. ZPA-GROUP ZEMS-TKN-MAP-PHYSICAL-ADDRESS. ZEMS-DDL-PHYSICAL-ADDRESS.
PAGE 355
Messages Tape Process Event Messages (ZTAP) Token Description (page 2 of 2) ZEMS-TKN-MAP-PHYSICALADDRESS.ZEMS-DDLPHYSICAL-ADDRESS.ZPAGROUP Nonshared group token that is reserved for the vendor. ZEMS-TKN-MAP-PHYSICALADDRESS.ZEMS-DDLPHYSICAL-ADDRESS.ZPAMODULE Nonshared module token that is reserved for the vendor. ZEMS-TKN-MAP-PHYSICALADDRESS.ZEMS-DDLPHYSICAL-ADDRESS.ZPA-SLOT Nonshared slot token that is reserved for the vendor.
PAGE 356
Messages Tape Process Event Messages (ZTAP) ZEMS-TKN-MAP-PHYSICAL-ADDRESS. ZEMS-DDL-PHYSICAL-ADDRESS. ZPA-MODULE ZEMS-TKN-MAP-PHYSICAL-ADDRESS. ZEMS-DDL-PHYSICAL-ADDRESS.
PAGE 357
Messages Tape Process Event Messages (ZTAP) Effect. Microcode is reloaded for all downloadable ServerNet addressable (SACs) controllers for which the processor where the power failed was the primary processor. Recovery. This is an informational message only; no corrective action is needed. -1019: ZTAP-EVT-ERROR-INJECTION An error was injected by an external program.
PAGE 358
Messages Tape Process Event Messages (ZTAP) -1018: ZTAP-EVT-TIMEOUTS-EXCEEDED-CMN A tape drive reported a that the number of timeouts allocated for an operation was exceeded.
PAGE 359
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn Path switch, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-PATHSW-CMN (-1017). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 360
Messages Tape Process Event Messages (ZTAP) ZEMS-TKN-MAP-PHYSICAL-ADDRESS. ZEMS-DDL-PHYSICAL-ADDRESS. ZPA-SLOT ZTAP-TKN-OLD-PATH-STATE ZTAP-TKN-CHANGE-INITIATOR-CMN token-type ZSPI-DDL-INT2 token-type ZXYZ-TYP-PATHSTATE token-type ZXYZ-DDLCHANGE-INITIATOR Event-Message Text dev-name PATH STATE CHANGE, LDEV $ldev, PHYS ADDR: GROUP group,MODULER module, SLOT slot, NEW STATE state-old,change-initiator, msg-txt Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 361
Messages Tape Process Event Messages (ZTAP) -1015: ZTAP-EVT-CPU-SWITCH-CMN An I/O process was switched to another processor. Subject: ZTAP-TKN-DEV-NAME Potentially critical event: No Action event: No Message sender: Tape process OSM/TSM collector: Yes Unconditional Tokens ZTAP-TKN-DEV-NAME ZEMS-TKN-XLDEVNAME ZEMS-TKN-EVENTNUMBER ZEMS-TKN-MAP-PHYSICAL-ADDRESS. ZEMS-DDL-PHYSICAL-ADDRESS. ZPA-GROUP ZEMS-TKN-MAP-PHYSICAL-ADDRESS. ZEMS-DDL-PHYSICAL-ADDRESS. ZPA-MODULE ZEMS-TKN-MAP-PHYSICAL-ADDRESS.
PAGE 362
Messages Tape Process Event Messages (ZTAP) Token Description (page 2 of 2) ZEMS-TKN-MAP-PHYSICALADDRESS.ZEMS-DDLPHYSICAL-ADDRESS.ZPAMODULE Nonshared module token that is reserved for the vendor. ZEMS-TKN-MAP-PHYSICALADDRESS.ZEMS-DDLPHYSICAL-ADDRESS.ZPASLOT Nonshared slot token that is reserved for the vendor. ZTAP-TKN-OLD-CPU Processor number of the processor that the I/O process was running on before the switch. ZTAP-TKN-CHANGEINITIATOR-CMN Internal operator message. Cause.
PAGE 363
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTRECOVERY-COMPLETION (-1014). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. Any request that has a problem that can be corrected by the tape device. Effect. None. Recovery.
PAGE 364
Messages Tape Process Event Messages (ZTAP) Recovery. None. -1012: ZTAP-EVT-SK-VOL-OVFLOW A sense key reported that end-of-partition and unwritten data was left in a buffer.
PAGE 365
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn Sense Key: Equal, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SKEQUAL (-1011). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 366
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SKABORTED-CMND (-1010). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. A command operation was aborted. Effect. The command request is not completed. Recovery.
PAGE 367
Messages Tape Process Event Messages (ZTAP) Recovery. None. -1008: ZTAP-EVT-SK-VENDOR-SPECIFIC A sense key reported a vendor-specific error.
PAGE 368
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn Sense Key: Blank Check, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SKBLANK-CHK (-1007). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 369
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SKDATA-PRTCT (-1006). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. The tape cartridge is write protected. Effect. The tape cannot be written to. Recovery. Write-enable the tape cartridge.
PAGE 370
Messages Tape Process Event Messages (ZTAP) Recovery. This is an informational message only; no corrective action is needed. -1004: ZTAP-EVT-SK-ILLEGAL-REQ A sense key reported an illegal request.
PAGE 371
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn Sense Key: Hardware Error, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SKHW-ERR (-1003). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 372
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SKMEDIUM-ERR (-1002). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. A damaged tape has been loaded on the drive. Effect. Read and write errors. Recovery. Replace the tape.
PAGE 373
Messages Tape Process Event Messages (ZTAP) Recovery. Load a tape. -1000: ZTAP-EVT-SK-RECVRD-ERR A sense key reported an error recovery.
PAGE 374
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn SMD sector checksum err, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNSEC-XSUM-ERR (32). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 375
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNBLK-XSUM-ERR (33). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. This function is not supported. Effect. None. Recovery. None. 64: ZTAP-EVT-SYN-FN-CODE-INV An MDR function code is invalid.
PAGE 376
Messages Tape Process Event Messages (ZTAP) Cause. There is a software code error. Effect. The command operation fails. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 65: ZTAP-EVT-SYN-MDR-FLD-CONT-ERR An MDR field content error occurred.
PAGE 377
Messages Tape Process Event Messages (ZTAP) 66: ZTAP-EVT-SYN-CTRL-LOC-RQD A controller lock is required.
PAGE 378
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn SMD md interface err, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNMD-INT-ERR (96). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 379
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNMD-STRUCT-ERR (97). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. There is a coding error in the module driver. Effect. The command operation fails. Recovery.
PAGE 380
Messages Tape Process Event Messages (ZTAP) Cause. There is a coding error in the module driver. Effect. The command operation fails. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 99: ZTAP-EVT-SYN-MD-CONFIG-ERR A module driver configuration error occurred.
PAGE 381
Messages Tape Process Event Messages (ZTAP) 100: ZTAP-EVT-WRITE-RETRIED A tape write operation was retried.
PAGE 382
Messages Tape Process Event Messages (ZTAP) Cause. The tape media or tape drive failed. An EIO instruction was issued and the TERMSTAT returned indicates that the tape write operation was retried. The TERMSTAT values are: Controller TERMSTAT 3206 36 3207 36 3208 36 3209 36 3211 36 3214 36 3215 (No event) 3681 36 Effect. If the retry is successful, the write operation finishes. Recovery. Check the tape media or tape drive.
PAGE 383
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT token-type token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-RETRY-CNT ZTAP-TKN-TAPE-VOLUME ZTAP-TKN-DEV-STATUS ZEMS-MAP-EXIOADDR token-type token-type token-type token-type token-type token-type ZSPI-TYP-UIN
PAGE 384
Messages Tape Process Event Messages (ZTAP) 102: ZTAP-EVT-3202-WRITE-RETRIED A 3202 controller successfully retried a tape write operation.
PAGE 385
Messages Tape Process Event Messages (ZTAP) Cause. A 3202 controller successfully retried a tape write operation. The write is retried until either it is successful, a nonreturnable error occurs, or 40 retries have been attempted. If the retry is successful, this message is generated; if not, some other message is generated. The retryable error conditions are overrun, parity error, and CRC error. The event message contains information explaining the reason for the retry operation.
PAGE 386
Messages Tape Process Event Messages (ZTAP) Event-Message Text dev-name READ RETRIED, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr, NUMBER OF RETRIES retry-cnt Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-3202READ-RETRIED (103). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. A 3202 controller successfully retried a tape read operation. The tape media or tape drive failed.
PAGE 387
Messages Tape Process Event Messages (ZTAP) ZEMS-MAP-EXIOADDR ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM token-type ZSPI-DDL-EXIOADDR token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-RETRY-CNT ZTAP-TKN-TAPE-VOLUME
PAGE 388
Messages Tape Process Event Messages (ZTAP) 128: ZTAP-EVT-SYN-TNET-SVC-IF-ERR A ServerNet services interface error occurred.
PAGE 389
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn SMD tnet cpu timeout, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNTNET-CPU-TIMEOUT (129). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 390
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNTNET-NO-AVT (130). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. A ServerNet services AVT error occurs. Effect. The command operation fails. Recovery.
PAGE 391
Messages Tape Process Event Messages (ZTAP) Effect. The command operation fails. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 132: ZTAP-EVT-SYN-TNET-CTLR-HW-ERR A ServerNet services controller hardware error occurred.
PAGE 392
Messages Tape Process Event Messages (ZTAP) 133: ZTAP-EVT-SYN-TNET-CTLR-HAD-ERR A ServerNet services controller hardware error occurred.
PAGE 393
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn SMD tnet path down, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNTNET-PATH-DOWN (134). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 394
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNTNET-POWER-FAIL (135). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. A ServerNet services power failure occurs. Effect. The command operation fails. Recovery. Turn on the power.
PAGE 395
Messages Tape Process Event Messages (ZTAP) Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 137: ZTAP-EVT-SYN-TNET-CTLR-AVT-ERR A ServerNet services controller AVT error occurred.
PAGE 396
Messages Tape Process Event Messages (ZTAP) 192: ZTAP-EVT-SYN-DEV-SEL-TIMEOUT A tape device could not be selected.
PAGE 397
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn SMD device command timeout, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNDEV-CMD-TIMEOUT (193). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 398
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNDEV-CMD-INCOMP (194). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. A tape drive is performing another action when another command is received. Effect. The command fails. Recovery.
PAGE 399
Messages Tape Process Event Messages (ZTAP) Recovery. Reissue the command. 196: ZTAP-EVT-SYN-SCSI-STATUS A command was incomplete.
PAGE 400
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn SMD device if err, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNDEV-INTF-ERR (197). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 401
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNDEV-RESET (198). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. A tape drive was reset by the controller because a command operation was aborted. Effect. The command operation fails. Recovery. None.
PAGE 402
Messages Tape Process Event Messages (ZTAP) Effect. The command operation fails. Recovery. None. 200: ZTAP-EVT-BAD-UCODE The microcode is incorrect.
PAGE 403
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-BADUCODE (200). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. ZTAP-TKN-DL-UCODE-ERR Microcode download error code (see Table 10-9 on page 10-75). Table 10-9. ZTAP-TKN-DL-UCODE-ERR Values Symbolic Name (ZTAP-VAL-) Numeric Value Description DLU-OK 0 The download was successful.
PAGE 404
Messages Tape Process Event Messages (ZTAP) Cause. A problem occurred in the controller or channel. An EIO instruction was issued, and the TERMSTAT returned indicates that the microcode is incorrect. The TERMSTAT values are: Controller TERMSTAT 3206 45 3207 48 3208 48 3209 48 3211 118 3214 49 3215 49 3681 49 Effect. The tape drives connected to the controller are inoperative. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15.
PAGE 405
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text dev-name CHANNEL DMA ERROR, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTCHANNEL-DMA-ERROR (201).
PAGE 406
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZTAP-TKN-DEV-NAME ZTAP-TKN-DETECTOR-PROCESS ZTAP-TKN-DETECTOR-REV ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type token-type token-type token-type token-type tok
PAGE 407
Messages Tape Process Event Messages (ZTAP) Effect. The tape operation aborts. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 203: ZTAP-EVT-FORMATTER-PWR-OFF The formatter is powered off.
PAGE 408
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that the formatter is powered off. Depending on the particular drive status value, this event message can indicate a problem with the drive or drive formatter. The TERMSTAT values are: Controller TERMSTAT 3206 50 3207 (No event) 3208 56 3209 50 3211 202 3214 202 3215 202 3681 202 Effect. The tape operation aborts. Recovery.
PAGE 409
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text dev-name HARD CONTROLLER ERROR, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Uncondition
PAGE 410
Messages Tape Process Event Messages (ZTAP) 205: ZTAP-EVT-HARD-SELFTEST-ERROR A hard self-test error occurred.
PAGE 411
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that a hard self-test error occurred. Depending on the particular TERMSTAT value, this event message indicates a problem with the controller. The TERMSTAT values are: Controller TERMSTAT 3206 86 through 91 3207 87 through 92 3208 (No event) 3209 (No event) 3211 125, 126 3214 125, 126 3215 (No event) 3681 125, 126, 206 Effect. The tape operation aborts. Recovery.
PAGE 412
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text dev-name ILLEGAL COMMAND ERROR, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Uncondition
PAGE 413
Messages Tape Process Event Messages (ZTAP) 207: ZTAP-EVT-NVRAM-XSUM A checksum error occurred on nonvolatile random-access memory (NVRAM).
PAGE 414
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that the NVRAM checksum is incorrect. Either the data written into the NVRAM is invalid, or the controller is incorrectly calculating the checksum. The TERMSTAT values are: Controller TERMSTAT 3206 (No event) 3207 46 3208 46 3209 46 3211 (No event) 3214 (No event) 3215 (No event) 3681 (No event) Effect. The tape operation aborts. Recovery.
PAGE 415
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text dev-name NVRAM WRITTEN MORE THAN 1000 TIMES, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr
PAGE 416
Messages Tape Process Event Messages (ZTAP) 209: ZTAP-EVT-SOFT-SELFTEST-ERROR A soft self-test error occurred on a controller.
PAGE 417
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that a soft self-test error occurred on a controller. The TERMSTAT values are: Controller TERMSTAT 3206 70 through 75 3207 70 through 76 3208 70 through 76 3209 70, 76 3211 (No event) 3214 (No event) 3215 (No event) 3681 (No event) Effect. The tape operation aborts. Recovery. If several of these events occur, replace the controller board.
PAGE 418
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNCTRL-DISABLED (256). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. The controller is not available or has caused too many interrupts. Effect. The path to the tape device is lost. Recovery.
PAGE 419
Messages Tape Process Event Messages (ZTAP) Recovery. None. 258: ZTAP-EVT-SYN-CTRL-UNLOADED A controller was unloaded.
PAGE 420
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn SMD controller queue active, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNCTRL-QUEUE-ACTIVE (259). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 421
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-SYNCTRL-QUEUE-ERROR (260). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause.
PAGE 422
Messages Tape Process Event Messages (ZTAP) Effect. The path is lost. Recovery. Check the controller hardware. Reset the controller, if necessary. In the event of a controller failure, see Recovery Action Requiring Vendor Support on page 10-15. 288: ZTAP-EVT-SYN-SCSI-BUS-RESET A SCSI-bus reset was issued by a controller.
PAGE 423
Messages Tape Process Event Messages (ZTAP) 289: ZTAP-EVT-SYN-SCSI-BUS-IN A SCSI-bus reset was initiated by a person or another device on the same bus.
PAGE 424
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZTAP-TKN-DEV-NAME ZTAP-TKN-DETECTOR-PROCESS ZTAP-TKN-DETECTOR-REV ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-RETRY-CNT ZTAP-TKN-TAPE-VOLUME ZTAP-TKN-DEV-STATUS token-typ
PAGE 425
Messages Tape Process Event Messages (ZTAP) Controller TERMSTAT (page 2 of 2) 3214 39 3215 (No event) 3681 39 Effect. None. Recovery. Check the tape and try it on another drive. If the tape is causing the problem, replace it. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 301: ZTAP-EVT-DATA-UNCORRECTED An uncorrectable data error occurred.
PAGE 426
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-DATAUNCORRECTED (301). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that an uncorrectable data error occurred.
PAGE 427
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-BYTE-PAIR ZSPI-TYP-UINT ZSPI-DDL-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST token-type token-type token-type token-type ZSPI-TYP-BOOLEAN ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-I
PAGE 428
Messages Tape Process Event Messages (ZTAP) Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 303: ZTAP-EVT-DRIVE-PWR-OFF A tape drive was powered off.
PAGE 429
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that the tape drive is powered off. This event message can also indicate a problem with the tape drive or formatter. The TERMSTAT values are: Controller TERMSTAT 3206 51 3207 50 3208 50 3209 50 3211 (No event) 3214 (No event) 3215 201 3681 201 Effect. The tape operation aborts. Recovery. Ensure that the tape drive and formatter are powered on.
PAGE 430
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-TAPE-VOLUME ZTAP-TKN-DEV-STATUS token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TYP-TAPE-VOLUME ZSPI-TYP-UINT Event-Message Text dev-name ERASE FAILED, LDEV $ldev, SUBCHANNEL ADDRESS %unit-add Unconditi
PAGE 431
Messages Tape Process Event Messages (ZTAP) 305: ZTAP-EVT-FORMATTER-REJECT A 3206 controller formatter command was rejected.
PAGE 432
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued to a 3206 controller, and the TERMSTAT returned indicates that the formatter rejected the command. Depending on the drive status value, this event message can indicate a problem with the drive, formatter, or controller. The TERMSTAT values are: Controller TERMSTAT 3206 41 3207 (No event) 3208 (No event) 3209 (No event) 3211 (No event) 3214 (No event) 3215 (No event) 3681 (No event) Effect.
PAGE 433
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-TAPE-VOLUME ZTAP-TKN-DEV-STATUS token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TYP-TAPE-VOLUME ZSPI-TYP-UINT Event-Message Text dev-name CHANNEL DMA ERROR, LDEV $ldev, SUBCHANNEL ADDRESS %unit-add Unco
PAGE 434
Messages Tape Process Event Messages (ZTAP) 307: ZTAP-EVT-FTM-ERROR A formatter or formatter module error occurred.
PAGE 435
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that an error occurred in the formatter (or formatter module for the 3207 controller). Depending on the drive status value, this event message can indicate a problem with the drive, formatter, or controller. TERMSTAT values are: Controller TERMSTAT 3206 (No event) 3207 55 3208 55 3209 (No event) 3211 (No event) 3214 (No event) 3215 (No event) 3681 (No event) Effect.
PAGE 436
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-TAPE-VOLUME ZTAP-TKN-DEV-STATUS token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TYP-TAPE-VOLUME ZSPI-TYP-UINT Event-Message Text dev-name ILLEGAL DRIVE STATUS, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr
PAGE 437
Messages Tape Process Event Messages (ZTAP) 309: ZTAP-EVT-LARGE-READ The amount of data to read was too large for a 3206 controller formatter buffer.
PAGE 438
Messages Tape Process Event Messages (ZTAP) Cause. A read EIO instruction was issued, and the TERMSTAT returned indicates that the data on the tape was too large for the formatter buffer. This event can indicate a problem with the drive, formatter, or data on the tape. The TERMSTAT values are: Controller TERMSTAT 3206 46 3207 (No event) 3208 (No event) 3209 (No event) 3211 (No event) 3214 (No event) 3215 (No event) 3681 (No event) Effect. The tape operation aborts. Recovery.
PAGE 439
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-TAPE-VOLUME ZTAP-TKN-DEV-STATUS token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TYP-TAPE-VOLUME ZSPI-TYP-UINT Event-Message Text dev-name OPERATION FAILED, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unco
PAGE 440
Messages Tape Process Event Messages (ZTAP) 311: ZTAP-EVT-RUNAWAY-TAPE A runaway tape occurred.
PAGE 441
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that a runaway tape occurred. Depending on the device status, this event message can indicate a problem with the drive, controller, or channel. Also, the tape density might be incorrect for the switch setting for the 3207 controller, or the tape might be NRZI for the 3208 controller.
PAGE 442
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST token-type token-type token-type token-type ZSPI-TYP-BOOLEAN ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZEMS-MAP-EXIOADDR ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT token-type token-type token-type token-type token-type ZSPI-DDL-EXIOADDR ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-TAPE-VO
PAGE 443
Messages Tape Process Event Messages (ZTAP) 313: ZTAP-EVT-SOFT-FTM-ERROR A soft formatter error occurred.
PAGE 444
Messages Tape Process Event Messages (ZTAP) Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that a soft formatter error occurred (3208 controllers only). Depending on the drive status value, this event message can indicate a problem with the drive, formatter, or controller. The TERMSTAT values are: Controller TERMSTAT 3206 (No event) 3207 (No event) 3208 78 through 81 3209 (No event) 3211 (No event) 3214 (No event) 3215 (No event) 3681 (No event) Effect.
PAGE 445
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text dev-name UNKNOWN RIC TERMSTAT, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditiona
PAGE 446
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-DETECTOR-REV ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE token-type token-type token-type token-type token-type ZSPI-TYP-BYTE-PAIR ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-BYTE-PAIR ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-DDL-EXIOADDR ZSPI-TYP-BOOLEAN ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-EIO-RDST ZT
PAGE 447
Messages Tape Process Event Messages (ZTAP) Effect. The tape operation aborts. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 316: ZTAP-EVT-CABLE-OPEN A cable is not connected or is broken.
PAGE 448
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTCABLE-OPEN (316). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that the cable is not connected or is broken. Depending on the device status value, this event message can indicate a problem with the drive, controller, or cable.
PAGE 449
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-BYTE-PAIR ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LAC token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-DDL-EXIOADDR ZSPI-TYP-BOOLEAN ZSPI-TYP-UINT ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC token-type token-type token-type token-
PAGE 450
Messages Tape Process Event Messages (ZTAP) Effect. The tape operation aborts. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 318: ZTAP-EVT-PHYSICAL-EOT The physical EOT was encountered.
PAGE 451
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTPHYSICAL-EOT (318). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. An EIO instruction was issued, and the TERMSTAT returned indicates that the physical EOT was encountered on a 3209 controller. This event message usually indicates a software error or a problem with the tape drive.
PAGE 452
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-BYTE-PAIR ZSPI-TYP-UINT ZSPI-DDL-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST token-type token-type token-type token-type ZSPI-TYP-BOOLEAN ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-I
PAGE 453
Messages Tape Process Event Messages (ZTAP) Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 320: ZTAP-EVT-3202-BAD-STATUS A 3202 controller or a device attached to it is malfunctioning.
PAGE 454
Messages Tape Process Event Messages (ZTAP) Cause. A hardware problem occurred with a 3202 controller or a tape drive attached to it. Effect. The tape operation aborts. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 321: ZTAP-EVT-3202-RUNAWAY-TAPE A 3202 controller indicated a runaway tape.
PAGE 455
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-3202RUNAWAY-TAPE (321). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. The RIC word for an I/O completion on a 3202 controller indicated a runaway tape.
PAGE 456
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-BYTE-PAIR ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-DDL-EXIOADDR ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST token-type token-type token-type token-type Z
PAGE 457
Messages Tape Process Event Messages (ZTAP) 323: ZTAP-EVT-3202-COMMAND-REJECT A 3202 controller rejected a command.
PAGE 458
Messages Tape Process Event Messages (ZTAP) Cause. The RIC word from an I/O operation on a 3202 controller has the command reject flag set. The controller sets this flag if any of the following occur:   A command for an illegal address is received. An illegal command is received. An error occurred on a previous command when command chaining. (The tape process does not use command chaining, so this event must never occur.) Effect. The tape operation aborts. Recovery.
PAGE 459
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-3202OVERRUN (324). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. The RIC word from an I/O operation on a 3202 controller has the overrun flag set. A read, write, or write-file-mark operation that receives this error is retried up to 40 times.
PAGE 460
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-TAPE-VOLUME token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TYP-TAPE-VOLUME Event-Message Text dev-name PARITY ERROR, LDEV $ldev, SUBCHANNEL ADDRESS %unit-add Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-3202PARITY-ERROR (325).
PAGE 461
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-DDL-EXIOADDR ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE ZTAP-TKN-TAPE-VOLUME token-type token-type toke
PAGE 462
Messages Tape Process Event Messages (ZTAP) No file mark was detected by the read head when writing a file mark. Effect. The operation aborts. Recovery. If the error continues to occur, see Recovery Action Requiring Vendor Support on page 10-15. 327: ZTAP-EVT-COVER-OPEN The cover on a tape drive was left open.
PAGE 463
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTCOVER-OPEN (327). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. The cover on a tape drive was left open.
PAGE 464
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LAC token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-DDL-EXIOADDR ZSPI-TYP-BOOLEAN ZSPI-TYP-UINT ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT ZTAP-TKN-IIO-RIC token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type
PAGE 465
Messages Tape Process Event Messages (ZTAP) 330: ZTAP-EVT-EQUIP-CHECK A problem exists with a tape drive, and it must be checked.
PAGE 466
Messages Tape Process Event Messages (ZTAP) Cause. A problem exists in the tape drive. An EIO instruction was issued, and the TERMSTAT returned indicates that a tape drive problem occurred. The TERMSTAT values are: Controller TERMSTAT 3206 (No event) 3207 (No event) 3208 (No event) 3209 (No event) 3211 198, 200, 203 3214 198, 200, 203, 204 3215 198, 203, 204, 209, 210 3681 198, 200, 203, 204 Effect. The tape operation aborts. Recovery.
PAGE 467
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text dev-name ID BURST ERROR, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-IDBURST-ERROR (331).
PAGE 468
Messages Tape Process Event Messages (ZTAP) 332: ZTAP-EVT-SOFT-CNTLR-ERROR A soft controller error occurred.
PAGE 469
Messages Tape Process Event Messages (ZTAP) Cause. A problem exists in a controller. An EIO instruction was issued, and the TERMSTAT returned indicates that a soft controller error occurred. The TERMSTAT values are: Controller TERMSTAT 3206 (No event) 3207 (No event) 3208 (No event) 3209 (No event) 3211 112, 124 3214 112, 124 3215 (No event) 3681 112, 124 Effect. The tape operation aborts. Recovery.
PAGE 470
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT ZTAP-TKN-IOC-COUNT ZTAP-TKN-IOC-RESIDUE token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text dev-name UNKNOWN ERROR, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTUNKNOWN-ERROR (333).
PAGE 471
Messages Tape Process Event Messages (ZTAP) 334: ZTAP-EVT-WRITE-ENABLED-ERR A tape write was attempted, but the write ring is absent.
PAGE 472
Messages Tape Process Event Messages (ZTAP) Controller TERMSTAT (page 2 of 2) 3214 226 3215 226 3681 226 Effect. The tape operation aborts. Recovery. Install a write ring on the tape and retry the operation. 335: ZTAP-EVT-DEV-ASSGN-ELSEWHERE A tape drive is assigned to another controller.
PAGE 473
Messages Tape Process Event Messages (ZTAP) 336: ZTAP-EVT-VOL-FENCED A tape drive is unloaded because of an unrecoverable error.
PAGE 474
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text $tapenn mounted media is incompatible with drive, LDEV $nn Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-INVMEDIA-FORMAT (337).
PAGE 475
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-OLD-CPU ZTAP-TKN-CHANGE-INITIATOR token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT Event-Message Text dev-name CPU SWITCH, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr, OLD CPU cpu-old, change-initiator Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER. Event number for this message.
PAGE 476
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZTAP-TKN-DEV-NAME ZTAP-TKN-DETECTOR-PROCESS ZTAP-TKN-DETECTOR-REV ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-EIO-LAC ZTAP-TKN-EIO-LPRM ZTAP-TKN-EIO-RDST ZTAP-TKN-EIO-CHANSTAT token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-DEVICE ZSPI
PAGE 477
Messages Tape Process Event Messages (ZTAP) 402: ZTAP-EVT-IIO-BAD An IIO instruction returned an invalid status.
PAGE 478
Messages Tape Process Event Messages (ZTAP) Cause. A controller or channel problem occurred. An IIO instruction was issued, and the RIST or the channel status returned contained an error condition. The EIO instruction executed properly, but the IIO instruction failed. Effect. The tape operation aborts. Recovery. For more information, you can access the TMDS HELP file for this event.
PAGE 479
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-INTOVERRUN (403). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. An interrupt was received from a device before the previous interrupt from that device was processed. A unit must not interrupt more than once per EIO instruction. Effect. The tape operation aborts. Recovery.
PAGE 480
Messages Tape Process Event Messages (ZTAP) Event-Message Text dev-name INTERRUPT TIMED OUT, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-INTTIMEOUT (404). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn. Cause. A problem exists in the channel or the controller. This problem just occurred, because a timeout on the EIO instruction did not happen.
PAGE 481
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-DL-UCODE-REV ZTAP-TKN-DL-UCODE-TYPE ZTAP-TKN-DL-UCODE-ERR token-type ZSPI-TYP-BYTE-PAIR token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT Event-Message Text dev-name LOAD MICROCODE EXECUTED, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-LOADUCODE (405).
PAGE 482
Messages Tape Process Event Messages (ZTAP) Table 10-10. ZTAP-TKN-DL-UCODE-ERR Values (page 2 of 2) Symbolic Name (ZTAP-VAL-) Numeric Value Description DLU-SELF-TEST 11 A controller-selftest error occurred. DLU-GENR-ERR 12 A device-generation error occurred. DLU-GENR-FILE-TYPE 13 An incorrect microcode file type was detected. DLU-FILE-ACCESS 14 An access error occurred on the microcode file. DLU-UND-ERR -1 An undetermined error occurred on a microcode download. Cause.
PAGE 483
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-PATH-STATE ZTAP-TKN-PATH-STATE-NEW ZTAP-TKN-CHANGE-INITIATOR token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT Event-Message Text dev-name PATH STATE CHANGE, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTPATH-STATE (406). ZTAP-TKN-DEV-NAME Subject token that specifies the name of the tape device in the form $nnnn.
PAGE 484
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZTAP-TKN-DEV-NAME ZTAP-TKN-DETECTOR-PROCESS ZTAP-TKN-DETECTOR-REV ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-PON token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-DEVICE ZSPI-TYP-UINT ZSPI-TYP-BYTE-PAIR ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-
PAGE 485
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZTAP-TKN-DEV-NAME ZTAP-TKN-DETECTOR-PROCESS ZTAP-TKN-DETECTOR-REV ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LPRM token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-DEVICE ZSPI-TYP-UINT ZSPI-TYP-BYTE-PAIR ZSPI-TYP-UINT ZSPI-TYP-UINT
PAGE 486
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-CPU ZTAP-TKN-PIN ZTAP-TKN-LDEV ZTAP-TKN-DEV-TYPE ZTAP-TKN-UNIT-ADR ZEMS-MAP-EXIOADDR ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-EIO-LPRM token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-BYTE-PAIR ZSPI-TYP-UINT ZSPI-DDL-EXIOADDR ZSPI-TYP-BOOLEAN ZSPI-TYP-UINT Event-Message Text dev-name SET HOLDOFF EIO EXECUTED, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditional Tokens
PAGE 487
Messages Tape Process Event Messages (ZTAP) ZTAP-TKN-CNTLR-SHARED ZTAP-TKN-IIO-RIC ZTAP-TKN-IIO-RIST ZTAP-TKN-IIO-CHANSTAT token-type token-type token-type token-type ZSPI-TYP-BOOLEAN ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text dev-name UNEXPECTED INTERRUPT, LDEV $ldev, SUBCHANNEL ADDRESS %unit-addr Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVTUNEXPECTED-INT (410).
PAGE 488
Messages Tape Process Event Messages (ZTAP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZTAP-EVT-TAPESTAC (511). ZEMS-TKN-XLDEVNAME Subject token that specifies the name of the tape device in the form $nnnn. ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number in the form $nn. Cause. An I/O process has added error information to an event. Effect. None. Recovery.
PAGE 489
11 Disk Process Event Messages (ZDSK) Disk process event messages are reported to the EMS by the disk process—that is, by DP2 or the DP2 Driver (T9753). Table 11-1. Disk Process Event Messages (page 1 of 9) -1000: ZDSK-EVT-SK-RECVRD-ERR* The disk completed the last command successfully, after performing some recovery action. -1001: ZDSK-EVT-SK-NOT-RDY* The disk is not in a ready state and cannot be accessed now.
PAGE 490
Disk Process Event Messages (ZDSK) Table 11-1. Disk Process Event Messages (page 2 of 9) -1017: ZDSK-EVT-PATH-SWITCH-CMN* A disk drive reported an internally or externally initiated path switch. -1018: ZDSK-EVT-TIMEOUTS-EXCEEDED-CMN* The maximum number of interrupt timeouts for the I/O process (IOP) has been exceeded. -1020: ZDSK-EVT-PON-CMN* A power on (PON) interrupt (indicating a power failure) occurred. The state of the hardware can be changed by a power failure and a subsequent power on.
PAGE 491
Disk Process Event Messages (ZDSK) Table 11-1. Disk Process Event Messages (page 3 of 9) -1034: ZDSK-EVT-SK-DEFERED-ERROR* Some error has already occurred and most likely this indicates that a write of the disk drive's internal cache did not succeed. 000449: ZDSK-EVT-BLK-REWRITTEN* A checksum error was detected on one disk drive of a mirrored volume, but was successfully read from the other disk drive.
PAGE 492
Disk Process Event Messages (ZDSK) Table 11-1. Disk Process Event Messages (page 4 of 9) 5020: ZDSK-EVT-EXCEPT-ERR-EXT* An exception error occurred on a disk during a disk process extended command. 5021: ZDSK-EVT-INCONSISTENT-VLABS* The disk process encountered inconsistent volume labels. 5022: ZDSK-EVT-INTERNAL-ERR The disk process detected an internal error. 5028: ZDSK-EVT-MEMORY-PRESSURE Insufficient physical memory is available.
PAGE 493
Disk Process Event Messages (ZDSK) Table 11-1. Disk Process Event Messages (page 5 of 9) 5050: ZDSK-EVT-WRTVFY-MODE-OFF* The persistent write verify mode has been turned off. 5051: ZDSK-EVT-BADDOWN-VOLUME A disk volume went down because of reasons described in preceding event messages generated by the driver. 5052: ZDSK-EVT-DP2-BAD-FILE-BLOCK The disk process detected an invalid file or file block.
PAGE 494
Disk Process Event Messages (ZDSK) Table 11-1. Disk Process Event Messages (page 6 of 9) 5068: ZDSK-EVT-CBPOOL-USAGE DP2 cannot obtain control block space. 5069: ZDSK-EVT-FCB-TABLE-USE DP2 cannot obtain control block space. 5070: ZDSK-EVT-OCB-TABLE-USE DP2 cannot obtain control block space. 5071: ZDSK-EVT-NO-LKTABLE-SPACE DP2 cannot obtain lock table space. 5072: ZDSK-EVT-LK-TABLE-USE DP2 cannot obtain lock table space. 5073: ZDSK-EVT-LAB-TABLE-USE DP2 cannot obtain lock table space.
PAGE 495
Disk Process Event Messages (ZDSK) Table 11-1. Disk Process Event Messages (page 7 of 9) 5090: ZDSK-EVT-OPER-ABORTED-DUMP A DP2 failure data system (TFDS) data capture was aborted because of a PUP UP request2 or SCF START request3. 5091: ZDSK-EVT-DP2-ABORTED-DUMP A DP2 failure data system (TFDS) data captured was aborted because of a takeover. 5093: ZDSK-EVT-SOFTDOWN-STATE A DP2 processor has entered a softdown state.
PAGE 496
Disk Process Event Messages (ZDSK) Table 11-1. Disk Process Event Messages (page 8 of 9) 5108: ZDSK-EVT-PREDICT-FAIL-TEST* A device that has the SMART feature enabled attempted to report a performance degradation or a device failure before the problem occurred, and sent a recovery action against data loss. This event is used by the vendor for software development. 5109: ZDSK-EVT-LKIDLONGPOOLEN-OFFLN A user has unsucessfully attempted to increase LKID Long Pool length.
PAGE 497
Disk Process Event Messages (ZDSK) Table 11-1. Disk Process Event Messages (page 9 of 9) 5119: ZDSK-EVT-CONFIG-RECORD-FETCH When a DP2 process initialized, it tried and failed to read its configuration record from the SCF configuration database. 5120: ZDSK-EVT-PROT-STRUCT-OFFLN A user has unsucessfully attempted to change the FullCheckpoints or SerialWrites configuration parameters.
PAGE 498
Common Definitions Disk Process Event Messages (ZDSK) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 499
Event Management Service (EMS) Standard Definitions Disk Process Event Messages (ZDSK) Figure 11-1. ZDSK-VAL-SSID Structure def ZDSK-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-INT value is ZSPI-SSN-ZDSK. 02 Z-VERSION type ZSPI-DDL-INT value is ZDSK-VAL-VERSION. end. Token Description ZSPI-TKN-SSID Contains ZDSK-VAL-SSID, the disk process subsystem ID.
PAGE 500
Disk Process (ZDSK-) Definitions Disk Process Event Messages (ZDSK) Token Description (page 2 of 2) ZEMS-TKN-EMPHASIS Has the value ZSPI-VAL-TRUE for those disk process event messages that are potentially critical. Otherwise, it always has the value ZSPI-VAL-FALSE. ZEMS-TKN-EVENTNUMBER Contains the event number for each disk process event message. ZEMS-TKN-GENTIME Standard EMS token that specifies the timestamp when the event message was generated.
PAGE 501
Disk Process (ZDSK-) Definitions Disk Process Event Messages (ZDSK) Token Description (page 2 of 2) ZDSK-TKN-CBTABLE Type of DP2 internal data structure (see Table 11-6 on page 11-14). Most of these data structures are control block tables. ZDSK-TKN-DRIVE Specifies whether a drive in a mirrored pair is the primary or mirror drive (see Table 11-7 on page 11-14).
PAGE 502
Disk Process (ZDSK-) Definitions Disk Process Event Messages (ZDSK) Table 11-6. ZDSK-TKN-CBTABLE Values Value Display String ZDSK-VAL-AC-DATA DP2 A/C Manager ZDSK-VAL-FCB-HASH-TABLE DPShare FCB Hash Table ZDSK-VAL-FCB-TABLE DPShare FCB Table ZDSK-VAL-LOCK-TABLES DP2 Lock Manager ZDSK-VAL-OCB-TABLE DPShare OCB Table ZDSK-VAL-OCB-CPUSYS-TABLE DPShare OCB^CPUSys Table ZDSK-VAL-RECOVERY-TABLE Recovery Requester Table Otherwise DP2 internal tables Table 11-7.
PAGE 503
Disk Process (ZDSK-) Definitions Disk Process Event Messages (ZDSK) Simple Tokens and Structured Tokens ZDSK-TKN-LACCMD ZDSK-TKN-OPCODE ZDSK-TKN-TERMCODE ZDSK-TKN-VOL-NAME token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TYP-DEVICE Token Description ZDSK-TKN-LACCMD Controller command that the disk process issued (see Table 11-9). ZDSK-TKN-OPCODE Extended controller command that the disk process issued (see Table 11-10 on page 11-16).
PAGE 504
Disk Process (ZDSK-) Definitions Disk Process Event Messages (ZDSK) Table 11-9.
PAGE 505
Disk Process (ZDSK-) Definitions Disk Process Event Messages (ZDSK) Table 11-11. ZDSK-TKN-TERMCODE Values (page 1 of 2) Name (ZDSK-VAL-) Description ACCESS-ALT-TRACK A direct access to an alternate track occurred. BAD-CMD-COUNT The command count exceeds 30,720 bytes. BAD-EIO-PARM An invalid EIO instruction parameter was detected. BAD-NVRAM An NVRAM was written more than 1000 times and must be replaced. BAD-PART-SER-NUM The part and serial number do not compare on an update revision.
PAGE 506
Description of ZDSK Event Messages Disk Process Event Messages (ZDSK) Table 11-11. ZDSK-TKN-TERMCODE Values (page 2 of 2) Name (ZDSK-VAL-) Description SRVO-CLOCK-LOST The servo clock was lost during a write. SRVO-OFF-MINUS A successful retry resulted from the head positioner offset toward the outer edge of the disk. SRVO-MNS-STROB-EARLY A successful retry resulted from the head positioner offset toward the outer edge of the disk.
PAGE 507
Disk Process Event Messages (ZDSK)  Information in Event Description Messages Descriptions of individual event messages (for a linked list, see Table 11-1 on page 11-1) Note. Each event message also contains the header tokens listed in Section 2, Header and Common Tokens, and the tokens listed in the Common Definitions on page 3-5.
PAGE 508
Recovery Action Requiring Vendor Support Disk Process Event Messages (ZDSK) Recovery Action Requiring Vendor Support Contact your service provider or the Global Mission Critical Solution Center (GMCSC), as directed by your local operating procedures.
PAGE 509
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-SK-RECVRD-ERR (-1000). ZEMS-TKN-XLDEVNAME Subject token that specifies the logical device name of the affected disk drive. Conditional Tokens Token Description ZEMS-TKN-LDEVNUMBER The logical device number of the affected disk drive. ZDSK-TKN-LOGICAL-PATH-CMN Logical path command of the event.
PAGE 510
Messages Disk Process Event Messages (ZDSK) Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text SCSI SK - Not Ready Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-SK-NOT-RDY (-1001).
PAGE 511
Messages Disk Process Event Messages (ZDSK) $ZLOG: Yes $0: No OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text SCSI SK - Medium Error Unconditi
PAGE 512
Messages Disk Process Event Messages (ZDSK) -1003: ZDSK-EVT-SK-HW-ERR The disk drive detected an unrecoverable hardware failure.
PAGE 513
Messages Disk Process Event Messages (ZDSK) Cause. The disk drive detected an unrecoverable hardware failure. Effect. Any command to the device fails. Recovery. Replace the disk. -1004: ZDSK-EVT-SK-ILLEGAL-REQ A request has been issued for a disk other than the one being used or resulted in a malformed SCSI command to the disk.
PAGE 514
Messages Disk Process Event Messages (ZDSK) Conditional Tokens Token Description ZEMS-TKN-LDEVNUMBER The logical device number of the affected disk drive. ZDSK-TKN-LOGICAL-PATH-CMN Logical path command of the event. ZEMS-TKN-SAC-NAME Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-TARGET-ID Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-LUN Nonshared token that is reserved for the vendor. Cause.
PAGE 515
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-SK-UNIT-ATTN (-1005). ZEMS-TKN-XLDEVNAME Subject token that specifies the logical device name of the affected disk drive. Conditional Tokens Token Description ZEMS-TKN-LDEVNUMBER The logical device number of the affected disk drive. ZDSK-TKN-LOGICAL-PATH-CMN Logical path command of the event.
PAGE 516
Messages Disk Process Event Messages (ZDSK) Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text SCSI SK - Data Protect Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-SK-DATA-PRTCT (-1006).
PAGE 517
Messages Disk Process Event Messages (ZDSK) $ZLOG: Yes $0: No OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text SCSI SK - Aborted command Uncond
PAGE 518
Messages Disk Process Event Messages (ZDSK) -1013: ZDSK-EVT-SK-MISCOMPARE A source data mismatch has occurred during a write verify command. This can happen because of bad controller hardware, SCSI command queuing, or an initial path switch to the disk.
PAGE 519
Messages Disk Process Event Messages (ZDSK) Token Description ZEMS-TKN-SCSI-TARGET-ID Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-LUN Nonshared token that is reserved for the vendor. Cause. A source data mismatch has occurred during a write verify command. This can happen because of a bad controller hardware, SCSI command queuing, or an initial path switch to the disk. Effect. If the controller is bad, the path to the disk might be brought down if an alternative path is available.
PAGE 520
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-RECOVERY-COMPLETION (1014). ZEMS-TKN-XLDEVNAME Subject token that specifies the logical device name of the affected disk drive. ZDSK-TKN-RECOVERY-RESULT Recovery result, whether successful or unsuccessful. Conditional Tokens Token Description ZEMS-TKN-LDEVNUMBER The logical device number of the affected disk drive.
PAGE 521
Messages Disk Process Event Messages (ZDSK) Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text CPU Switch Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-CPU-SWITCH-CMN (-1015).
PAGE 522
Messages Disk Process Event Messages (ZDSK) -1016: ZDSK-EVT-PATH-STATE-CHANGE A device path state has changed.
PAGE 523
Messages Disk Process Event Messages (ZDSK) Conditional Tokens Token Description ZEMS-TKN-LDEVNUMBER The logical device number of the affected disk drive. ZDSK-TKN-LOGICAL-PATH-CMN Logical path command of the event. ZEMS-TKN-SAC-NAME Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-TARGET-ID Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-LUN Nonshared token that is reserved for the vendor. Cause. A device path state has changed. Effect. None. Recovery.
PAGE 524
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-PATH-SWITCH-CMN (-1017). ZEMS-TKN-XLDEVNAME Subject token that specifies the logical device name of the affected disk drive. ZDSK-TKN-CHANGE-INITIATORCMN Specifies the initiator of an action, whether it is an internal (I/O) or external process (other process). ZDSK-TKN-OLD-PATH-NAME The previous name of the path.
PAGE 525
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZDSK-TKN-THRESHOLD-COUNT ZDSK-TKN-THRESHOLD-TIME token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-INT4 token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN
PAGE 526
Messages Disk Process Event Messages (ZDSK) -1020: ZDSK-EVT-PON-CMN A power on (PON) interrupt (indicating a power failure) occurred. The state of the hardware can be changed by a power failure and a subsequent power on.
PAGE 527
Messages Disk Process Event Messages (ZDSK) -1021: ZDSK-EVT-INT-TIMEOUT-CMN An execute I/O (EIO) was issued, but no interrupt was received for the EIO; a timeout on the EIO did not occur. The interrupt from the controller never occurred, or the interrogate I/O (IIO) processing the interrupt failed. A problem exists with the channel or the controller.
PAGE 528
Messages Disk Process Event Messages (ZDSK) Conditional Tokens Token Description ZEMS-TKN-LDEVNUMBER The logical device number of the affected disk drive. ZDSK-TKN-LOGICAL-PATH-CMN Logical path command of the event. ZEMS-TKN-SAC-NAME Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-TARGET-ID Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-LUN Nonshared token that is reserved for the vendor. Cause.
PAGE 529
Messages Disk Process Event Messages (ZDSK) Event-Message Text Sector Checksum Error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-SECTOR-XSUM (-1023). ZEMS-TKN-XLDEVNAME Subject token that specifies the logical device name of the affected disk drive. ZDSK-TKN-COMMAND I/O command number for this event. ZDSK-TKN-SECTOR-COUNT Sector count number. ZDSK-TKN-SECTOR-ADDR-ERR Logical Block Address of the sector in error.
PAGE 530
Messages Disk Process Event Messages (ZDSK) Message sender: Disk process (ZDSK) $ZLOG: Yes $0: No OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message
PAGE 531
Messages Disk Process Event Messages (ZDSK) -1027: ZDSK-EVT-DEV-CMD-TIMEOUT The device could not complete the command within the time frame. There could be some issues with the disk drive.
PAGE 532
Messages Disk Process Event Messages (ZDSK) Token Description ZEMS-TKN-SCSI-TARGET-ID Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-LUN Nonshared token that is reserved for the vendor. Cause. The device could not complete the command within the time frame. There could be some issues with the disk drive. Effect. The input/output (I/O) command fails. The I/O driver will retry the command before putting the specific path to down state. Recovery. Reset the disk drive.
PAGE 533
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-DEV-CMD-INCOMP (-1028). ZEMS-TKN-XLDEVNAME Subject token that specifies the logical device name of the affected disk drive. Conditional Tokens Token Description ZEMS-TKN-LDEVNUMBER The logical device number of the affected disk drive. ZDSK-TKN-LOGICAL-PATH-CMN Logical path command of the event.
PAGE 534
Messages Disk Process Event Messages (ZDSK) Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text Device Busy Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-DEV-BUSY (-1029).
PAGE 535
Messages Disk Process Event Messages (ZDSK) $ZLOG: Yes $0: No OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text Device SCSI status Unconditional
PAGE 536
Messages Disk Process Event Messages (ZDSK) -1031: ZDSK-EVT-DEV-IF-ERR A controller or a SCSI bus error occurred when a command was sent from the controller to the disk drive.
PAGE 537
Messages Disk Process Event Messages (ZDSK) Token Description ZEMS-TKN-SCSI-TARGET-ID Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-LUN Nonshared token that is reserved for the vendor. Cause. A controller or a SCSI bus error occurred when a command was sent from the controller to the disk drive. Effect. The input/output (I/O) command fails. Recovery.
PAGE 538
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-DEV-RESET (-1032). ZEMS-TKN-XLDEVNAME Subject token that specifies the logical device name of the affected disk drive. Conditional Tokens Token Description ZEMS-TKN-LDEVNUMBER The logical device number of the affected disk drive. ZDSK-TKN-LOGICAL-PATH-CMN Logical path command of the event.
PAGE 539
Messages Disk Process Event Messages (ZDSK) Conditional Tokens ZEMS-TKN-LDEVNUMBER ZDSK-TKN-LOGICAL-PATH-CMN ZEMS-TKN-SAC-NAME ZEMS-TKN-SCSI-TARGET-ID ZEMS-TKN-SCSI-LUN token-type token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text SCSI SK Deferred Error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-SK-DEFERED-ERROR (-1034).
PAGE 540
Messages Disk Process Event Messages (ZDSK) Message sender: Disk process (ZDSK) TMDS collector: No OSM/TSM collector: No Unconditional Tokens ZDSK-TKN-CURR-SECTOR-ADDR ZDSK-TKN-NUM-BYTES ZDSK-TKN-XSUM-TYPE token-type ZSPI-TYP-INT4 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT Event-Message Text Block was re-written Unconditional Tokens Token Description ZDSK-TKN-CURR-SECTOR-ADDR Address of the I/O operation that was rewritten. ZDSK-TKN-NUM-BYTES Length in bytes of the I/O operation.
PAGE 541
Messages Disk Process Event Messages (ZDSK) Event-Message Text Verified Write buffer compare failed Unconditional Tokens Token Description ZDSK-TKN-MISCOMPARE-ADDR Address of the start of the I/O operation that found the miscomparison. ZDSK-TKN-SECTOR-COUNT Length in bytes of the I/O operation that found the miscomparison. Cause. After writing a block to the disk, the DP2 Driver found that the data did not compare. Effect. There is a serious problem with the I/O subsystem. Recovery.
PAGE 542
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV ZDSK-TKN-REQUESTOR ZDSK-TKN-NUM-MEDIA ZDSK-TKN-THIS-CPU-PP ZDSK-TKN-THIS-CPU-PB ZDSK-TKN-THIS-CPU-MP ZDSK-TKN-THIS-CPU-MB ZDSK-TKN-OTHER-CPU-PP ZDSK-TKN-OTHER-CPU-PB ZDSK-TKN-OTHER-CPU-MP ZDSK-TKN-OTHER-CPU-MB ZDSK-TKN-CTLR-STATE-PP ZDSK-TKN-CTLR-STATE-PB ZDSK-TKN-CTLR-STATE-MP ZDSK-TKN-CTLR-STATE-MB ZDSK-TKN-IO-RESULT ZDSK-TKN-NEW-STATE-PP ZDSK-TKN-NEW-STATE-PB ZDSK-TKN-NEW-STATE-MP ZDSK-TKN-NEW-STATE-MB
PAGE 543
Messages Disk Process Event Messages (ZDSK) Token Description (page 2 of 2) ZDSK-TKN-THIS-CPU-MB Error encountered (if any) through the currently configured primary processor, backup controller, and mirror drive (see Table 11-14 on page 11-56). ZDSK-TKN-OTHER-CPU-PP Error encountered (if any) through the currently configured backup processor, primary controller, and primary drive (see Table 11-14 on page 11-56).
PAGE 544
Messages Disk Process Event Messages (ZDSK) Table 11-12. ZDSK-TKN-REQUESTOR Values Value Meaning ZDSK-VAL-DP2 The requester is the disk process. This request is usually a user request. ZDSK-VAL-NON-DP2 The requester is not the disk process. This request is usually a PUP request such as LISTHEADERS. Table 11-13. ZDSK-TKN-NUM-MEDIA Values Value Meaning ZDSK-VAL-ONE One-path request ZDSK-VAL-TWO Two-path request Table 11-14.
PAGE 545
Messages Disk Process Event Messages (ZDSK) Table 11-16. ZDSK-TKN-IO-RESULT Values Value Meaning ZDSK-VAL-IO-HALFOP The I/O request failed because a two-path write succeeded on only one half of the volume. ZDSK-VAL-IO-MEDIA-FAILURE The I/O request failed because of media failures. ZDSK-VAL-IO-PATH-FAILURE The I/O request failed because of path failures. ZDSK-VAL-IO-SUCCEEDED The I/O request was successful. Table 11-17. New States of Paths Value of Token State ZDSK-VAL-DOWN Path is down.
PAGE 546
Messages Disk Process Event Messages (ZDSK) Event-Message Text LDEV ldev Bad disk free space table[; Error = #oooooo] Must use PUP REBUILDDFS (D-series) Must use SCF REBUILDDFS (G-series and H-series) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-BADFST (5003). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive.
PAGE 547
Messages Disk Process Event Messages (ZDSK) Event-Message Text LDEV ldev [ CU %ccu ] INCONSISTENT MIRROR VOLUMES Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-BADMIRROR-VOLS (5005). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Cause.
PAGE 548
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-BADUNDO-AREA (5008). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Cause. The undo area, which is normally used for key-sequenced file recovery either during processor failures or when a disk is brought up, is invalid or inaccessible to the disk. Effect. The disk goes down or stays down. Recovery.
PAGE 549
Messages Disk Process Event Messages (ZDSK) Conditional Tokens Token Description ZDSK-TKN-VLAB-SECT Invalid section in the volume label (see Table 11-18). Table 11-18. ZDSK-TKN-VLAB-SECT Values Value Meaning ZDSK-VAL-BOOTSTRAP Bootstrap ZDSK-VAL-DIR-FILE-LABEL Directory file label ZDSK-VAL-FREE-SPACE-POOL Free space pool ZDSK-VAL-FST Free space table (FST) ZDSK-VAL-STT Spare tracks table (STT) ZDSK-VAL-UNDO-AREA Undo area Cause. The volume label contained invalid data.
PAGE 550
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-BADVOL-NAME (5011). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Cause. The disk could not be brought up because the disk process could not use either of the disk names in the volume label. Effect. The disk stays down. Recovery.
PAGE 551
Messages Disk Process Event Messages (ZDSK) Event-Message Text LDEV ldev Volume {$vol} went down for TMF due to { error #dddddd on an audit write { broken file detected during logical undo { inability to post a control point TLE { error #dddddd getting MAT info for a control point { error #dddddd generating a control point { error #dddddd writing the volume label { error #dddddd on an audit write during a takeover } } } } } } } Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number
PAGE 552
Messages Disk Process Event Messages (ZDSK) 5015: ZDSK-EVT-DRV-DOWN The specified path has been placed in the down state (usually with the PUP DOWN command for D-series NonStop operating system RVUs and with SCF STOP DISK command for G-series and H-series NonStop operating system RVUs).
PAGE 553
Messages Disk Process Event Messages (ZDSK) 5016: ZDSK-EVT-ERR-ELEM An error occurred on a disk during a disk process elementary command.
PAGE 554
Messages Disk Process Event Messages (ZDSK) Effect. Retries on this path have failed. Other paths are tried if they are available. If no other paths are available, the drive goes down. Recovery. Check for a drive hardware problem. 5017: ZDSK-EVT-DRV-ERR-EXT An error occurred on a disk during a disk process extended command.
PAGE 555
Messages Disk Process Event Messages (ZDSK) Token Description (page 2 of 2) ZDSK-TKN-DRV-ERR Drive error encountered (see Table 11-19 on page 11-65). ZDSK-TKN-OPCODE Extended controller command issued by the disk process. Values are listed in Disk Process (ZDSK-) Definitions on page 11-12. Conditional Tokens Token Description (page 1 of 2) ZDSK-TKN-ADDED-DFCTS Opcode modifier for the READ DEFECT LIST command. Defects are to be read from the added defect map.
PAGE 556
Messages Disk Process Event Messages (ZDSK) Token Description (page 2 of 2) ZDSK-TKN-NO-CHAN-DATA Opcode modifier used by the READ command. No channel transfer will occur through the data IOC. This token appears only if ZDSK-TKN-OPCODE has a value of ZDSK-VAL-READ-OP and the corresponding opcode modifier was specified. ZDSK-TKN-RES-XSUM-ARRAY Opcode modifier for the READ command. A checksum array will be returned from the controller.
PAGE 557
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text LDEV ldev [ CU %ccu ] UP Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-DRVUP (5018). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Cause.
PAGE 558
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTEXCEPT-ERR-ELEM (5019). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-EXCEPT-ERR Exception error encountered (see Table 11-20). ZDSK-TKN-LACCMD Elementary controller command issued by the disk process. Values are listed under Disk Process (ZDSK-) Definitions on page 11-12. Table 11-20.
PAGE 559
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV ZDSK-TKN-EXCEPT-ERR ZDSK-TKN-OPCODE token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-UINT ZSPI-TYP-ENUM ZSPI-TYP-ENUM token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN ZSPI-TYP-BOOLEAN ZSPI-TYP-BOOLEAN ZSPI-TYP-BOOLEAN ZSPI-TYP-BOOLEAN ZSPI-TYP-BOOLEAN ZSPI-TYP-BOOLEA
PAGE 560
Messages Disk Process Event Messages (ZDSK) Table 11-21. ZDSK-TKN-EXCEPT-ERR Values Value Meaning ZDSK-VAL-DEV-INTF-EXCEPT Device-interface exception error ZDSK-VAL-DRV-EXCEPT Drive exception error ZDSK-VAL-ECC-EXCEPT ECC exception error Conditional Tokens Token Description (page 1 of 2) ZDSK-TKN-ADDED-DFCTS Opcode modifier for the READ DEFECT LIST command. Defects are to be read from the added defect map.
PAGE 561
Messages Disk Process Event Messages (ZDSK) Token Description (page 2 of 2) ZDSK-TKN-INSRT-BLOCK-XSUM Opcode modifier used by the WRITE command. A block checksum will be calculated and inserted into the structured block. This token appears only if ZDSKTKN-OPCODE has a value of ZDSK-VAL-WRITE-OP and the corresponding opcode modifier was specified. ZDSK-TKN-NO-CHAN-DATA Opcode modifier used by the READ command. No channel transfer will occur through the data IOC.
PAGE 562
Messages Disk Process Event Messages (ZDSK) 5021: ZDSK-EVT-INCONSISTENT-VLABS The disk process encountered inconsistent volume labels.
PAGE 563
Messages Disk Process Event Messages (ZDSK) Recovery. Correct the error with the PUP LABEL command (D-series NonStop operating system RVUs) or System Control Facility (SCF) command (G-series and H-series NonStop operating system RVUs). See the Peripheral Utility Program (PUP) Reference Manual for information about PUP commands and Subsystem Control Facility (SCF) Reference Manual for SCF commands. 5022: ZDSK-EVT-INTERNAL-ERR The disk process detected an internal error.
PAGE 564
Messages Disk Process Event Messages (ZDSK) 5028: ZDSK-EVT-MEMORY-PRESSURE Insufficient physical memory is available to support all the activity for the processor.
PAGE 565
Messages Disk Process Event Messages (ZDSK) 5029: ZDSK-EVT-NO-MEMORY The disk process ran out of memory while attempting to allocate its internal tables.
PAGE 566
Messages Disk Process Event Messages (ZDSK) 5031: ZDSK-EVT-PENDING-STATUS An attempt to issue a command was rejected with report-of-pending-status too many times.
PAGE 567
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text REVIVE ABORTED Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTREVIVE-ABORTED (5032). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Cause.
PAGE 568
Messages Disk Process Event Messages (ZDSK) Conditional Tokens ZEMS-TKN-LDEV ZDSK-TKN-SW-ERR ZDSK-TKN-SECTOR-ADDR ZDSK-TKN-LOGICAL-PATH-CMN token-type token-type token-type token-type ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text PATH: SW DETECTED SECTOR XSUM ERROR Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-SWERR (5033).
PAGE 569
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT ZEMS-TKN-LDEV token-type ZSPI-TYP-UINT ZDSK-TKN-REVIVE-TIME-DELAY token-type ZSPI-TYP-INT2 ZDSK-TKN-REVIVE-CURR-SECT token-type ZSPI-TYP-LOGICAL-SECTOR Event-Message Text Revive-Suspended Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTREVIVE-SUSPENDED (5034).
PAGE 570
Messages Disk Process Event Messages (ZDSK) Event-Message Text LDEV ldev Unable to read directory label; Error = #dddddd Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number of the error that for this message. Value is ZDSK-EVT-UNABLE-READ-DIR-LABEL (5036). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-FILE-ERR File-system error number the disk process received while reading the directory label. Cause.
PAGE 571
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTUNABLE-WRITE-VLAB (5037). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-FILE-ERR File-system error number of the error that the disk process received while writing the volume label. Cause. The disk process received an error while writing the volume label.
PAGE 572
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTUNEXP-INTR (5038). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-RIC-STATUS RIC status returned from the controller. The encoded status (bits <4:7> of the RIC status) can be any value in Table 11-23). Table 11-23.
PAGE 573
Messages Disk Process Event Messages (ZDSK) 5040: ZDSK-EVT-BADDOWN-ADP The disk process for a TMF audit-trail volume encountered an error while writing an audit-trail file.
PAGE 574
Messages Disk Process Event Messages (ZDSK) Effect. The audit trail rejects all audit requests. All audit-trail volumes that audit to the audit trail go down, and the TMF subsystem halts. Recovery. Correct the problem that caused the failure. Then restart the TMF subsystem using the TMFCOM START TMF command. 5042: ZDSK-EVT-UPPROCESS-TERMINATED The disk process encountered an inconsistency or error while trying to clean up its free space table and volume label.
PAGE 575
Messages Disk Process Event Messages (ZDSK) 5044: ZDSK-EVT-DP2DRVR-INTERNAL-ERR The controller returned an invalid status response to the disk process.
PAGE 576
Disk Process Event Messages (ZDSK) Table 11-24. ZEMS-TKN-PARM1 Values, Bits <4:7> (page 2 of 2) 3 Report of pending status 4 Command exception 5 Channel-interface exception 6 Controller exception 7 Device-interface exception 8 Drive exception 9 ECC exception A (not used) B (not used) C (not used) D Drive not ready E Drive-selection error F Drive not responding Table 11-25.
PAGE 577
Messages Disk Process Event Messages (ZDSK) Table 11-25. ZEMS-TKN-PARM1 Values, Bits <8:15> (page 2 of 2) 19 Too many reports of pending status 20 Checksum parameter not found 21 Bad spares exhausted Cause. The controller returned an invalid status response to the disk process. This error is classified as a retryable, power-fail type, controller global error. Effect.
PAGE 578
Messages Disk Process Event Messages (ZDSK) 5047: ZDSK-EVT-ENV-RPT An environmental monitoring report has been provided by the controller.
PAGE 579
Messages Disk Process Event Messages (ZDSK) 5048: ZDSK-EVT-BAD-LABEL The disk process encountered an invalid SQL label.
PAGE 580
Messages Disk Process Event Messages (ZDSK) Cause. The disk process detected an inconsistency in an SQL label whose external name is ZDSK-TKN-FILE-NAME and whose record code is ZDSK-TKN-RCODE. The ZDSK-TKN-INTERNAL-ERR value pinpoints where in the disk process the inconsistency was detected. Effect. The operation is not performed. Recovery. See Recovery Action Requiring Vendor Support on page 11-20. 5049: ZDSK-EVT-WRTVFY-MODE-ON The persistent write verify mode has been turned on.
PAGE 581
Messages Disk Process Event Messages (ZDSK) 5050: ZDSK-EVT-WRTVFY-MODE-OFF The persistent write verify mode has been turned off.
PAGE 582
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV ZDSK-TKN-VOL-NAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-DEVICE Event-Message Text LDEV ldev Volume $vol went down Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTBADDOWN-VOLUME (5051). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive.
PAGE 583
Messages Disk Process Event Messages (ZDSK) Conditional Tokens ZDSK-TKN-FILE-RSN ZDSK-TKN-VSN ZDSK-TKN-LOGICAL-FILE-NAME token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT4 token-type ZSPI-TYP-STRING Event-Message Text { LDEV ldev Bad file $vol.subvol.file, { LOGICAL NAME: $lvol.subvol.file} detected at error label 'cccccccc' | LDEV ldev Bad block in file $vol.subvol.file, { LOGICAL NAME: $lvol.subvol.file} detected at error label 'cccccccc'; Block RSN %oooooo.oooooo, block VSN %oooooo.oooooo.
PAGE 584
Messages Disk Process Event Messages (ZDSK) Effect. Attempts to access the file might result in error 59. Recovery. If the file is protected by TMF roll forward recovery and the first cause listed earlier was not the problem, use a TMF RECOVER FILES command to recover the file. If the file is protected by TMF roll forward recovery and the first cause listed earlier was the problem, issue a TMF RECOVER FILES command with a timestamp less than or equal to the initial recovery timestamp.
PAGE 585
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-DP2DATA-LOSS (5053). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-FILE-NAME Internal representation of the name of the file whose changes are being checkpointed. ZDSK-TKN-FILE-RSN File-relative sector number of the block whose changes are being checkpointed.
PAGE 586
Messages Disk Process Event Messages (ZDSK) Conditional Tokens ZDSK-TKN-FILE-NAME ZDSK-TKN-PSEUDO-FILENAME ZDSK-TKN-LOGICAL-FILE-NAME token-type ZSPI-TYP-FNAME token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Event-Message Text LDEV ldev Driver write errors for file $vol.{subvol.file } { LOGICAL NAME: $lvol.subvol.file} {pseudofile }; RSN %oooooo.oooooo, error #dddddd Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 587
Messages Disk Process Event Messages (ZDSK) Recovery. The recovery action depends on the problem. Analyze the preceding DP2 Driver event messages to determine what went wrong. The system might automatically retry the error. Try the following recovery actions. Check for additional disk process event messages that follow. These messages might indicate that the volume went down or that it went down for the TMF subsystem.
PAGE 588
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-FLAUDITED-FLAG-CHG (5056). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-FILE-NAME Internal representation of the name of the file that was altered from an audited file or table to a nonaudited one or vice-versa.
PAGE 589
Messages Disk Process Event Messages (ZDSK) Event-Message Text LDEV ldev [ CU %ccu ] Timestamp mismatch. drive text will be brought down. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTTIMESTAMP-DRV-DOWN (5058). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-DRIVE Indicates whether the drive in question is the primary or mirror drive in a volume. Cause.
PAGE 590
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTCACHE-INIT-FAILURE (5059). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-VOL-NAME Additional subject token that contains the volume name of the affected disk drive. Conditional Tokens Token Description ZDSK-TKN-CACHE-INIT-REASON Reason that cache initialization for the volume failed.
PAGE 591
Messages Disk Process Event Messages (ZDSK) Event-Message Text LDEV ldev Volume $vol has been configured with the default cache sizes instead of the requested cache sizes Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTDEFAULT-CACHE-SIZES (5060). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive.
PAGE 592
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV ZDSK-TKN-FILE-NAME ZDSK-TKN-EXTENT-NUM token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-UINT ZSPI-TYP-FNAME ZSPI-TYP-INT Conditional Tokens ZDSK-TKN-LOGICAL-FILE-NAME token-type ZSPI-TYP-STRING Event-Message Text (D20 and later RVUs) LDEV ldev. During PUP REBUILDDFS, the file file-name, { LOGICAL NAME: $lvol.subvol.file} was found to have a doubly allocated extent (extent-num).
PAGE 593
Messages Disk Process Event Messages (ZDSK) Recovery. Try the following recovery action and then see Recovery Action Requiring Vendor Support on page 11-20.    Run the Disk Space Analysis Program (DSAP) utility to determine which file owns the extent. Duplicate the file that does not own the extent using a different file name. Delete the original file that you just made a duplicate of.
PAGE 594
Messages Disk Process Event Messages (ZDSK) 5063: ZDSK-EVT-UNEXPECTED-MSG-ERROR The disk process encountered an unexpected message error on a message reply.
PAGE 595
Messages Disk Process Event Messages (ZDSK) 5064: ZDSK-EVT-DV-ADPINFO-FROMTMFLIB A data volume queried the TMF Library for the name of the audit disk process to which that data volume must send its audit.
PAGE 596
Messages Disk Process Event Messages (ZDSK) Recovery. This is an informational message only; no corrective action is needed. 5065: ZDSK-EVT-UNKNOWN-LABEL The disk process encountered a label of unknown type.
PAGE 597
Messages Disk Process Event Messages (ZDSK) 5066: ZDSK-EVT-REFRESH A volume REFRESH or DISK CONTROL operation has been initiated. Subject: ZEMS-TKN-LDEV Potentially critical event: Yes Action event: No Message sender: Disk process (ZDSK) TMDS collector: No Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text LDEV ldev DP2 REFRESH cache flush initiated, performance loss is possible.
PAGE 598
Messages Disk Process Event Messages (ZDSK) 5067: ZDSK-EVT-NO-CBPOOL-SPACE DP2 cannot obtain control block space. This message also provides information on the number of failures since the processor was last reloaded.
PAGE 599
Messages Disk Process Event Messages (ZDSK) 5068: ZDSK-EVT-CBPOOL-USAGE This message provides information on the current use of DP2 control block pool space.
PAGE 600
Messages Disk Process Event Messages (ZDSK) 5069: ZDSK-EVT-FCB-TABLE-USE This message provides information on the current use of disk file control block (FCB) space.
PAGE 601
Messages Disk Process Event Messages (ZDSK) 5070: ZDSK-EVT-OCB-TABLE-USE This message provides information on the current use of disk open control block space utilization.
PAGE 602
Messages Disk Process Event Messages (ZDSK) 5071: ZDSK-EVT-NO-LKTABLE-SPACE DP2 cannot obtain lock table space. This message also provides information on the number of failures since the processor was last reloaded.
PAGE 603
Messages Disk Process Event Messages (ZDSK) 5072: ZDSK-EVT-LK-TABLE-USE This message provides information on the amount of space currently in use by the combined lock tables. This includes the LAB, LNB, Posix lock, and LKSHORT tables. The message specifies the current size and limit for all lock tables, and the current size and limit for the lock-id long pool. (The lock-id long pool is used for keys greater than 16 bytes long.
PAGE 604
Messages Disk Process Event Messages (ZDSK) Recovery. This event typically coincides with space allocation errors being returned to the application. There are two possible methods to prevent these errors:   Redistribute files and tables to reduce the demand for the volume that incurred the space allocation errors.
PAGE 605
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-LABTABLE-USE (5073). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive.
PAGE 606
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV ZDSK-TKN-POOL-SIZE token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-INT2 Event-Message Text LDEV ldev DP2 LOCK NAME SPACE: n entries, requiring nKB, In-use entries is n, requiring nKB. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-LNBTABLE-USE (5074).
PAGE 607
Messages Disk Process Event Messages (ZDSK) 5075: ZDSK-EVT-NO-ACPOOL-SPACE DP2 cannot obtain checkpoint pool space. This message also provides information on the number of failures since the processor was last reloaded.
PAGE 608
Messages Disk Process Event Messages (ZDSK) 5076: ZDSK-EVT-ACPOOL-USAGE This message provides information on the current use of DP2 checkpoint pool space.
PAGE 609
Messages Disk Process Event Messages (ZDSK) 5077: ZDSK-EVT-DPSHARE-SIZE This message provides information on the current use of DP2 pool space.
PAGE 610
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text LDEV ldev DP2 Insufficient virtual memory space - device DOWN Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-NOVIRTUAL-SPACE (5078). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Cause.
PAGE 611
Messages Disk Process Event Messages (ZDSK) Event-Message Text LDEV ldev DP2 Work pool space allocation failure, Number of allocation failures is n Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-NOWORKPOOL-SPACE (5079). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-POOL-SIZE Number of allocation failures. Cause. DP2 failed to obtain space from the workpool. Effect.
PAGE 612
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTWORKPOOL-USAGE (5080). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-POOL-SIZE Occurs three times and specifies, in this order: the capacity of the DP2 work pool, the maximum size of the pool, and the amount of in-use space (all in kilobytes). Cause.
PAGE 613
Messages Disk Process Event Messages (ZDSK) Cause. A processor failed during DP2 volume initialization. This event is generated every five minutes. Effect. The DP2 volume is not accessible. Recovery. System load or reload the primary and backup processors for the DP2 volume. If SCF support of DP2 is available, the volume can be stopped and restarted. If a subsequent attempt to reload the processor continues to report this event, take a memory dump after halting the processor.
PAGE 614
Messages Disk Process Event Messages (ZDSK) Effect. While the primary processor continues to provide service, a failure by the primary processor results in a down volume. This message is generated every five minutes until the backup processor is reloaded and initializes successfully. The DP2 volume will not be accessible if the primary processor fails. Recovery. Reload the backup processor. If SCF support of DP2 is available, the volume can be stopped and restarted.
PAGE 615
Messages Disk Process Event Messages (ZDSK) Recovery. If this event is reported during system load or reload, the primary and backup processors of DP2 must be halted, dumped, and reloaded. If SCF support of DP2 is available, the volume can be stopped and restarted. If this message occurs after a system load or reload, see Recovery Action Requiring Vendor Support on page 11-20. 5085: ZDSK-EVT-PROCESS-CREATE-BK DP2 failed to create the brother processor headpin.
PAGE 616
Messages Disk Process Event Messages (ZDSK) Recovery. If this event is reported during a system or reload, the brother DP2 processor must be halted, dumped, and reloaded. If SCF support of DP2 is available, the volume can be stopped and restarted. If this message occurs after a system load or reload, see Recovery Action Requiring Vendor Support on page 11-20. 5086: ZDSK-EVT-RESIZE-FAILED DP2 received an error during an attempt to resize virtual memory segment space.
PAGE 617
Messages Disk Process Event Messages (ZDSK) 5087: ZDSK-EVT-ALLOCATE-FAILED DP2 received an error during an attempt to allocate virtual memory segment space.
PAGE 618
Messages Disk Process Event Messages (ZDSK) 5088: ZDSK-EVT-CURRENT-STATE DP2 detected an internal inconsistency and initiated a processor softdown state.
PAGE 619
Messages Disk Process Event Messages (ZDSK) Conditional Tokens Token Description ZDSK-TKN-FL-AUDITED-FLAG Indicates whether the file was audited. ZDSK-TKN-PSEUDO-FILENAME Name of the disk control information block that was being processed at the time of the failure. ZDSK-TKN-PHANDLE Process handle of the requestor. ZDSK-TKN-LOGICAL-FILE-NAME SMF logical file name. Cause. DP2 detected an internal inconsistency and initiated a processor softdown state.
PAGE 620
Messages Disk Process Event Messages (ZDSK) Event-Message Text LDEV ldev DP2 volume successfully recovered from internal software error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTSOFTDOWN-RESET (5089). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Cause.
PAGE 621
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTOPER-ABORTED-DUMP (5090). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Cause. A softdown DP2 processor was reset by a PUP UP command (D-series NonStop operating system RVUs) or an SCF START command (G-series and H-series NonStop operating system RVUs). Effect.
PAGE 622
Messages Disk Process Event Messages (ZDSK) Recovery. This is an informational message only; no corrective action is needed. 5093: ZDSK-EVT-SOFTDOWN-STATE A DP2 processor has entered a softdown state.
PAGE 623
Messages Disk Process Event Messages (ZDSK) Recovery. Initiate a RECEIVEDUMP command with the ONLINE option for the affected DP2 processor, if possible. After the online dump is complete, use the PUP UP command (D-series NonStop operating system RVUs) or SCF START command (G-series and H-series NonStop operating system RVUs) to bring up the affected DP2 processor, which resets the state of the processor.
PAGE 624
Messages Disk Process Event Messages (ZDSK) 5095: ZDSK-EVT-SMS-FILE-FULL The number of extents in the specified file has crossed a user-specified threshold or interval value for the number of remaining extents.
PAGE 625
Messages Disk Process Event Messages (ZDSK) 5096: ZDSK-EVT-SMS-DISK-FULL The space available on a disk has crossed a user-specified threshold or interval for the amount of remaining space.
PAGE 626
Messages Disk Process Event Messages (ZDSK) 5097: ZDSK-EVT-CHECKPOINT-TIMEOUT DP2 timed out during an attempt to checkpoint to the backup processor.
PAGE 627
Messages Disk Process Event Messages (ZDSK) 5099: ZDSK-EVT-INVALID-STATUS An internal error occurred.
PAGE 628
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV ZDSK-TKN-EXCEPT-ERR ZDSK-TKN-EXCEPT-TYPE ZDSK-TKN-SYNDROME ZDSK-TKN-SECTOR-CNT ZDSK-TKN-SECTOR-ADDR-CMN token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-UINT ZSPI-TYP-ENUM ZSPI-TYP-INT ZSPI-TYP-UINT2 ZSPI-TYP-INT ZSPI-TYP-INT2 Conditional Tokens ZEMS-TKN-LOGICAL-PATH-CMN ZEMS-TKN-MAP-PHYSICAL-ADDRESSZEMS-DDL-PHYSICAL-ADDRESS.
PAGE 629
Messages Disk Process Event Messages (ZDSK) Conditional Tokens Token Description ZEMS-TKN-LOGICAL-PATH-CMN Logical path command of the event. ZEMS-TKN-MAP-PHYSICALADDRESS-ZEMS-DDL-PHYSICALADDRESS.ZPA-GROUP Nonshared group token that is reserved for the vendor. ZEMS-TKN-MAP-PHYSICALADDRESS.ZEMS-DDL-PHYSICALADDRESS.ZPA-MODULE Nonshared module token that is reserved for the vendor. ZEMS-TKN-MAP-PHYSICALADDRESS-ZEMS-DDL-PHYSICALADDRESS.ZPA-SLOT Nonshared slot token that is reserved for the vendor.
PAGE 630
Messages Disk Process Event Messages (ZDSK) ZEMS-TKN-MAP-PHYSICAL-ADDRESSZEMS-DDL-PHYSICAL-ADDRESS. ZPA-MODULE ZEMS-TKN-MAP-PHYSICAL-ADDRESSZEMS-DDL-PHYSICAL-ADDRESS.
PAGE 631
Messages Disk Process Event Messages (ZDSK) Cause. An online disk upgrade was initiated by a user. Effect. An online disk upgrade allows data to be revived from a low-capacity disk to a high-capacity disk, which enables customers to migrate to higher-capacity disks without an interruption in data availability. At the end of the online disk upgrade, the source device is brought down because the source and the target devices no longer have the same capacity. Recovery.
PAGE 632
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-BADSUBTYPE (5104). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Conditional Tokens Token Description ZEMS-TKN-LOGICAL-PATH-CMN Logical path command of the event. ZEMS-TKN-MAP-PHYSICALADDRESS-ZEMS-DDL-PHYSICALADDRESS.ZPA-GROUP Nonshared group token that is reserved for the vendor.
PAGE 633
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV ZEMS-TKN-LDEVNUMBER token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-UINT Conditional Tokens ZEMS-TKN-LOGICAL-PATH-CMN ZEMS-TKN-MAP-PHYSICAL-ADDRESSZEMS-DDL-PHYSICAL-ADDRESS. ZPA-GROUP ZEMS-TKN-MAP-PHYSICAL-ADDRESSZEMS-DDL-PHYSICAL-ADDRESS. ZPA-MODULE ZEMS-TKN-MAP-PHYSICAL-ADDRESSZEMS-DDL-PHYSICAL-ADDRESS.
PAGE 634
Messages Disk Process Event Messages (ZDSK) Token Description (page 2 of 2) ZEMS-TKN-MAP-PHYSICALADDRESS-ZEMS-DDL-PHYSICALADDRESS.ZPA-SLOT Nonshared slot token that is reserved for the vendor. ZEMS-TKN-SCSI-TARGET-ID Nonshared token that is reserved for the vendor. ZEMS-TKN-SCSI-LUN Nonshared token that is reserved for the vendor. ZEMS-TKN-SERVERNET-FABRIC Nonshared token that is reserved for the vendor. ZEMS-TKN-SAC-NAME Nonshared token that is reserved for the vendor. Cause.
PAGE 635
Messages Disk Process Event Messages (ZDSK) ZEMS-TKN-SCSI-LUN ZEMS-TKN-SERVERNET-FABRIC ZEMS-TKN-SAC-NAME token-type ZSPI-TYP-INT4 token-type ZEMS-TYPSERVERNET-FABRIC token-type ZSPI-TYP-INT4 Event-Message Text LDEV ldev PATH: path Predictive Failure Analysis Threshold Reached on Recovered Error PHYS ADDR: group, module, slot, target-id, lun, fabric, sac-name Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTPREDICT-FAIL (5107).
PAGE 636
Messages Disk Process Event Messages (ZDSK) Effect. Performance degradation or a device failure might occur if the suggested recovery action is not performed. Recovery. You might want to replace the device, which reduces the likelihood of a driver failure and loss of data. 5108: ZDSK-EVT-PREDICT-FAIL-TEST A device attempted to predict a performance degradation or a failure and instructed the user to take action against data loss before the degradation or failure actually occurred.
PAGE 637
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTPREDICT-FAIL-TEST (5108). ZEMS-TKN-LDEV Subject token that specifies the logical device number of the affected disk drive. Conditional Tokens Token Description ZEMS-TKN-LOGICAL-PATH-CMN Logical path command of the event. ZEMS-TKN-MAP-PHYSICALADDRESS-ZEMS-DDLPHYSICALADDRESS.ZPA-GROUP Nonshared group token that is reserved for the vendor.
PAGE 638
Messages Disk Process Event Messages (ZDSK) 5109: ZDSK-EVT-LKIDLONGPOOLEN-OFFLN A user has unsucessfully attempted to change the value of the LKIDLongPoolLen configuration parameter. This parameter determines the amount of memory (in 128kilobyte units) to be allocated for lock key space. This space stores keys larger than 16 bytes when records in key-sequenced files are locked.
PAGE 639
Messages Disk Process Event Messages (ZDSK) 5110: ZDSK-EVT-LKTABLESPACELEN-OFFLN A user has unsucessfully attempted to change the LKTableSpaceLen configuration parameter. This parameter determines the amount of memory (in 128-kilobyte units) to be allocated for lock-related data structures. The memory available for these structures limits the total file and record locks allowed on a disk.
PAGE 640
Messages Disk Process Event Messages (ZDSK) 5111: ZDSK-EVT-AUDITRAILBUFF-OFFLN A user has unsucessfully attempted to increase the AuditTrailBuffer/SQLMXBuffer (MB) configuration parameter. This parameter determines the audit-trail buffer size (in megabytes) for a TMF audit trail volume or the SQLMX buffer size (in megabytes) for an SQL/MX session.
PAGE 641
Messages Disk Process Event Messages (ZDSK) 5112: ZDSK-EVT-BAD-NUMDISCPROCESSES A user has unsucessfully attempted to change the number of disk processes allocated for a disk. This operation is performed with SCF by using the parameter NumDiskProcesses.
PAGE 642
Messages Disk Process Event Messages (ZDSK) 5113: ZDSK-EVT-BAD-CBPOOLLEN A user has unsucessfully attempted to change the the maximum memory (in 128kilobyte units) that can be allocated for open-related data structures on the disk. The memory available for these structures limits the total concurrent opens allowed on the disk. This operation is performed with SCF by using the parameter CBPoolLen.
PAGE 643
Messages Disk Process Event Messages (ZDSK) 5114: ZDSK-EVT-BAD-MAXLOCKSPEROCB A user has unsucessfully attempted to change the maximum number of records that can be locked outside a transaction. This operation is performed with SCF by using the parameter MaxLocksPerOCB.
PAGE 644
Messages Disk Process Event Messages (ZDSK) 5115: ZDSK-EVT-BAD-MAXLOCKSPERTCB A user has unsucessfully attempted to change the maximum number of records and files a transaction can lock. This operation is performed with SCF by using the parameter MaxLocksPerTCB.
PAGE 645
Messages Disk Process Event Messages (ZDSK) 5116: ZDSK-EVT-BAD-HALT-ON-ERROR A user has unsucessfully attempted to change whether an internally detected disk process failure must force a halt (code %11500) in the primary processor, backup processor, or both. This operation is performed with SCF by using the parameter HaltOnError.
PAGE 646
Messages Disk Process Event Messages (ZDSK) 5117: ZDSK-EVT-BAD-FULL-CHECKPOINTS A user has unsucessfully attempted to change whether the validity of data written to the disk is being protected by a full-block checkpoint (applies only to nondirectory structured files). This operation is performed with SCF by using the parameter FullCheckpoints.
PAGE 647
Messages Disk Process Event Messages (ZDSK) 5118: ZDSK-EVT-BAD-PROTECT-DIRECTORY A user has unsucessfully attempted to change the type of protection to use for the disk volume directory:    Full-block checking (CHECKPOINT) Serial writes (SERIAL) Disabled (OFF) This operation is performed with SCF by using the parameter ProtectDirectory.
PAGE 648
Messages Disk Process Event Messages (ZDSK) Recovery. Retry the operation. See the SCF Reference Manual for the Storage Subsystem for information about changing this parameter. 5119: ZDSK-EVT-CONFIG-RECORD-FETCH When a DP2 process initialized, it tried and failed to read its configuration record from the SCF configuration database.
PAGE 649
Messages Disk Process Event Messages (ZDSK) 5120: ZDSK-EVT-PROT-STRUCT-OFFLN Note. This message is currently not implemented. A user has unsucessfully attempted to change the FullCheckpoints or SerialWrites configuration parameters. The FullCheckpoints parameter determines whether the validity of data written to the disk is being protected by a full-block checkpoint (applies only to nondirectory structured files).
PAGE 650
Messages Disk Process Event Messages (ZDSK) 5123: ZDSK-EVT-STT-UPDATE-FAILED An attempt by the DP2 Driver to add an entry to the Spare Tracks Table (STT) failed because of an I/O error.
PAGE 651
Messages Disk Process Event Messages (ZDSK) 5124: ZDSK-EVT-DRIVER-MANGLE-CALLED The SNOOP DP2TP I/F was used to modify a DP2 Driver internal state.
PAGE 652
Messages Disk Process Event Messages (ZDSK) Recovery. This is an informational message only; no corrective action is needed. 5125: ZDSK-EVT-DRIVER-MEMORY-LOW The DP2 Driver’s memory space is low.
PAGE 653
Messages Disk Process Event Messages (ZDSK) 5126: ZDSK-EVT-TEXT-MESSAGE This event is used by HP for diagnostic purposes.
PAGE 654
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEVNUMBER ZDSK-TKN-TEXT-MESSAGE token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text LDEV logical-device-name message-text Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVT-ZDSKEVT-TEXT-MESSAGE (5126). ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number of the affected disk drive.
PAGE 655
Messages Disk Process Event Messages (ZDSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSK-EVTDETECTED-HUNG-IO (5128). ZEMS-TKN-LDEVNUMBER Subject token that specifies the logical device number of the affected disk drive. ZDSK-TKN-TEXT-MESSAGE Text supplied by HP. Cause. Unknown software problem. Effect. Delay in processing an DP2 request. Recovery.
PAGE 656
Messages Disk Process Event Messages (ZDSK) Token Description (page 2 of 2) ZDSK-TKN-OLD-SECTOR-CAPACITY Disk’s previous capacity. ZDSK-TKN-NEW-SECTOR-CAPACITY Disk’s new capacity. Cause. The capacity of the volume changed. Effect. None Recovery. This is an informational message only; no corrective action is needed. 5139: ZDSK-EVT-CAPACITY-MISMATCH The capacity of the primary and mirror disks does not match.
PAGE 657
Messages Disk Process Event Messages (ZDSK) Recovery. This is an informational message only; no corrective action is needed. 5140: ZDSK-EVT-NO-ACTT-SPACE DP2 cannot obtain space from Audit-Checkpoint Transaction Table (ACTT). This event might coincide with an error (35) reported to application requests for DP2 services.
PAGE 658
Messages Disk Process Event Messages (ZDSK) Recovery. See Recovery Action Requiring Vendor Support on page 11-20. 5141: ZDSK-EVT-BAD-MEMORY-REQUEST A pool allocation request exceeded %377770D (eight bytes less than 128 KB).
PAGE 659
12 Operating System Event Messages (ZGRD) Operating system event messages are reported to the EMS only by the monitor process. Table 12-1. Operating System Event Messages Event Number Symbolic Name Description 100: ZGRD-EVT-POISONPKTSENT A poison packet was sent in response to a message from a processor that had been declared halted. 104: ZGRD-EVT-PROC-TRAPPED A process trapped while executing SQL or SQL file-system code.
PAGE 660
Operating System Event Messages (ZGRD) Subsystem Programmatic Interface (SPI) Standard Definitions Note. All definitions are shown in DDL format using hyphens (-) as separators. If you are programming in TAL or TACL, substitute the circumflex symbol (^) for the hyphens. If you are programming in Pascal or C, substitute the underscore symbol (_) for the hyphens. For a quick explanation of DDL, see the SPI Programming Manual.
PAGE 661
Event Management Service (EMS) Standard Definitions Operating System Event Messages (ZGRD) Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for the operating system events are listed in Table 12-3. EMS standard definitions are described in detail in the EMS Manual. Table 12-3.
PAGE 662
Description of ZGRD Event Messages Operating System Event Messages (ZGRD) Private Token and Field Types Token Description ZGRD-DDL-MSG-BUFFER SPI message buffer that you must use for operating system event messages. Figure 12-2. ZGRD-DDL-MSG-BUFFER Definition def ZGRD-DDL-MSG-BUFFER. 02 Z-MSGCODE 02 Z-BUFLEN 02 Z-OCCURS 02 Z-FILLER type ZSPI-DDL-INT. type ZSPI-DDL-UINT. type ZSPI-DDL-UINT. type ZSPI-DDL-BYTE occurs 0 TO ZGRD-VAL-BUFLEN times depending on Z-OCCURS. end.
PAGE 663
Operating System Event Messages (ZGRD)  Information in Event Description Messages Descriptions of individual event messages (for a linked list, see Table 12-1 on page 12-1) Note. Each event message also contains the header tokens listed in Section 2, Header and Common Tokens, and the tokens listed in the Common Definitions on page 3-5.
PAGE 664
Recovery Action Requiring Vendor Support Operating System Event Messages (ZGRD) Recovery Action Requiring Vendor Support Contact your service provider or the Global Mission Critical Solution Center (GMCSC), as directed by your local operating procedures.
PAGE 665
Messages Operating System Event Messages (ZGRD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZGRD-EVTPOISONPKTSENT (100). ZGRD-TKN-TARGETCPU Subject token that specifies the processor number of the processor to which the poison packets were sent. ZGRD-TKN-REGROUPREASON Reason for regrouping. If it has no value, the reason is unknown (see Table 12-4 on page 12-7). ZGRD-TKN-REGROUPSEQNO Regroup sequence number.
PAGE 666
Messages Operating System Event Messages (ZGRD) Message sender: Monitor process TMDS collector: Yes OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT Conditional Tokens ZEMS-TKN-BATCHJOB-ID ZGRD-TKN-FAULT-SUBSYS token-type ZSPI-TYP-UINT token-type ZGRD-TYP-FAULTSUBSYS token-type ZSPI-TYP-STRING ZGRD-TKN-STOP-TEXT Event-Message Text process-name [, Job ID batchjob-ID,] trapped [ while in SQL | while in SQL file system ] [termination-text] Unconditional Tok
PAGE 667
Messages Operating System Event Messages (ZGRD) Effect. A saveabend file is generated for the process that trapped, and the process is terminated abnormally. Recovery. Use the saveabend file to diagnose the problem and correct the program. 108: ZGRD-EVT-MISALIGN-RECORD A misalignment exception has occurred for a process.
PAGE 668
Messages Operating System Event Messages (ZGRD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZGRDEVT-MISALIGN-RECORD (108). ZGRD-TKN-CPU16 Processor in which the process that has misalignment is running. ZGRD-TKN-PIN-SIGNED PIN for the process that has misalignment. ZGRD-TKN-PROGRAM-PATH. Guardian filename or OSS path name of the object file containing the code address for the misalignment (ZGRD-TKN-MISALIGN-NMPC).
PAGE 669
Messages Operating System Event Messages (ZGRD) Conditional Tokens Token Description ZGRD-TKN-XPROCESSNAME Name of the process that has misalignment. It is displayed only for named processes. ZGRD-TKN-MISALIGN-P Code address (program counter) of the emulated TNS instruction (expressed as an octal value). This token is present only if the misalignment exception occurs in emulated code.
PAGE 670
Messages Operating System Event Messages (ZGRD) Header Tokens Only (Text-Only Message) Event-Message Text Due to resource limitations, the NonStop was unable at this time to check for misalignment exceptions in current processes. Another attempt will occur in about an hour. Cause. The process that checks for data misalignment exceptions could not obtain sufficient system resources to run. Effect.
PAGE 671
Operating System Event Messages (ZGRD) Messages Cause. An application either did not open or did not process $RECEIVE for all incoming system messages from the Messenger process. Effect. The CPU appears to hang. Recovery. Check the status of each process shown in the message. If you cannot make the process resume executing so that it begins to read $RECEIVE again (for example, by typing PAUSE on the home terminal), stop that process (this frees the pending messages from the Messenger process).
PAGE 672
Operating System Event Messages (ZGRD) HP NonStop Operating System Event Management Programming Manual—520372-020 12-14 Messages
PAGE 673
13 NonStop Operating System Event Messages (ZNSK) NonStop operating system event messages are reported to the EMS by:         Client debugger Instruction Breakpoint Interrupt Process (IB IP) Memory Access Breakpoint Interrupt Process (MAB IP) Monitor process NSKCOM process OSS Kernel Debug Monitor (ZDBGMON) ZMSGQ process Table 13-1.
PAGE 674
NonStop Operating System Event Messages (ZNSK) Table 13-1. NonStop Operating System Event Messages (page 2 of 3) Event Number and Symbolic Name Description 114: ZNSK-EVT-PMEUSAGE POSIX Mapping Entry (PME) table usage is either above 70% or below 70%. 115: ZNSK-EVT-IBIP-INV-EXCEPTION An invalid exception occurred for the specified process. 116: ZNSK-EVT-DFLT-DBGR-CREAT-ERR Debug Services was unable to start the default debugger.
PAGE 675
NonStop Operating System Event Messages (ZNSK) Table 13-1. NonStop Operating System Event Messages (page 3 of 3) Event Number and Symbolic Name Description 206: ZNSK-EVT-KMS-SWAP-MAXEXT-ALTER An NSKCOM ALTER command a specified new value for MAXEXTENTS. 207: ZNSK-EVT-KMS-SWAP-THRES-ALTER An NSKCOM ALTER command changed the configured threshold for the swap file. 208: ZNSK-EVT-KMS-SWAP-STOP-PENDING An NSKCOM STOP command has stopped specified swap file.
PAGE 676
Common Definitions NonStop Operating System Event Messages (ZNSK) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 677
NonStop Operating System Event Messages (ZNSK) Event Management Service (EMS) Standard Definitions Token Description ZSPI-TKN-SSID Contains ZNSK-VAL-SSID, the subsystem ID of the NonStop operating system. ZSPI-SSN-ZNSK Subsystem number assigned to the NonStop operating system. Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for NonStop operating system events are listed in Table Table 13-3.
PAGE 678
NonStop Operating System Event Messages (ZNSK)   NonStop Operating System (ZNSK-) Definitions Predefined Token and Field Values on page 13-6 Simple Tokens and Structured Tokens on page 13-6 Private Token and Field Types Token Description ZNSK-DDL-MSG-BUFFER SPI message buffer that you must use for NonStop operating system event messages. Figure 13-2. ZNSK-DDL-MSG-BUFFER Definition def ZGRD-DDL-MSG-BUFFER. 02 Z-MSGCODE 02 Z-BUFLEN 02 Z-OCCURS 02 Z-FILLER type ZSPI-DDL-INT. type ZSPI-DDL-UINT.
PAGE 679
NonStop Operating System Event Messages (ZNSK) Description of ZNSK Event Messages Description of ZNSK Event Messages The NonStop operating system event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZNSK-EVT-name, where name describes the event that generated the message.
PAGE 680
Recovery Action Requiring Vendor Support NonStop Operating System Event Messages (ZNSK)    The cause describes what might have caused the event. The effect describes the implication (if any) of the generated event. The recovery describes the action (if any) to be taken. Recovery Action Requiring Vendor Support Contact your service provider or the Global Mission Critical Solution Center (GMCSC), as directed by your local operating procedures.
PAGE 681
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVTPARAMETERS-BAD (101). ZNSK-TKN-SERVERNAME Subject token that specifies the name of the server process for which the command was entered. ZNSK-TKN-PARAM Lists the invalid parameters. Cause. The command to start the server process was entered with one or more invalid parameters. Effect. The server process does not start. Recovery.
PAGE 682
Messages NonStop Operating System Event Messages (ZNSK) Effect. The server process immediately terminates. Recovery. See Recovery Action Requiring Vendor Support on page 13-8. 104: ZNSK-EVT-CREATEBACKUP-FAILED The server process was unable to create a backup process.
PAGE 683
Messages NonStop Operating System Event Messages (ZNSK) Recovery. Check the error code and error detail code to determine the cause of the resource shortage. If necessary, allocate additional swap space or stop unneeded processes in the backup processor. For description of the PROCESS_CREATE_ error codes, see the Guardian Procedure Errors and Messages Manual. 105: ZNSK-EVT-MEMALLOC-FAILED The server process was unable to allocate memory.
PAGE 684
Messages NonStop Operating System Event Messages (ZNSK) 106: ZNSK-EVT-SERVER-NAME An attempt to start the server process failed because the wrong server name was specified.
PAGE 685
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSK-TKN-SERVERNAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Event-Message Text server-name: Mom Process failed Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVT-MOMFAIL (107). ZNSK-TKN-SERVERNAME Subject token that specifies the incorrect server name. Cause. The mom process of the message-queue server failed. Effect.
PAGE 686
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVTBACKUP-FAIL-OFTEN (108). ZNSK-TKN-SERVERNAME Subject token that specifies the name of the server process. Cause. The backup process of the message-queue server is failing too often. Effect.
PAGE 687
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVTBACKUP-INVALID-STATE (109). ZNSK-TKN-SERVERNAME Subject token that specifies the name of the server process. Cause. The message-queue server primary process failed before it checkpointed all the information to the backup process, because the backup process is in an invalid state. Effect.
PAGE 688
Messages NonStop Operating System Event Messages (ZNSK) Recovery. This is an informational message only; no corrective action is needed. 111: ZNSK-EVT-INVALID-DIALECT The message-queue server received a request with an invalid dialect.
PAGE 689
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSK-TKN-SERVERNAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Event-Message Text server-name: Invalid Request type Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVTINVALID-REQUEST (112). ZNSK-TKN-SERVERNAME Subject token that specifies the name of the server. Cause. The message-queue server received an invalid request. Effect.
PAGE 690
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVTBACKUP-NOT-RUNNING (113). ZNSK-TKN-SERVERNAME Subject token that specifies the name of the server. Cause. The message-queue server is running without a backup process. Effect. The message-queue server is no longer fault-tolerant. Recovery.
PAGE 691
NonStop Operating System Event Messages (ZNSK) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVTPMEUSAGE (114). ZNSK-TKN-PME-INUSE Current PME table usage count. ZNSK-TKN-PME-PERCENT Current PME table usage as a percentage of the maximum PME table size. ZNSK-TKN-PME-MAXIMUM Maximum number of PME table entries available. Cause.
PAGE 692
Messages NonStop Operating System Event Messages (ZNSK) 115: ZNSK-EVT-IBIP-INV-EXCEPTION An invalid exception occurred for the specified process.
PAGE 693
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens ZNSK-TKN-FILE ZNSK-TKN-ERRORCODE ZNSK-TKN-ERRORDETAIL ZNSK-TKN-CPU ZNSK-TKN-PIN token-type token-type token-type token-type token-type ZSPI-TYP-STRING ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-UINT Event-Message Text Debug Services was unable to start the default debugger Unconditional Tokens Token Description ZNSK-TKN-FILE Subject token that specifies the name of the file that was to be debugged.
PAGE 694
Messages NonStop Operating System Event Messages (ZNSK) Event-Message Text Debug Services encountered an IO error with the default debugger Unconditional Tokens Token Description ZNSK-TKN-FILE Subject token that specifies the name of the file that was to be debugged. ZNSK-TKN-CPU Processor number of the processor on which Debug Services encountered the I/O error. ZNSK-TKN-PIN Process identification number of the processor on which Debug Services encountered the I/O error.
PAGE 695
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens Token Description ZNSK-TKN-FILE Subject token that specifies the name of the file that was being debugged. ZNSK-TKN-CPU Processor number of the debugging process. ZNSK-TKN-PIN Process identification number of the debugging process. Cause. The default debugger might have terminated. Effect. The process requiring debug services resumes. Recovery. This is an informational message only; no corrective action is needed.
PAGE 696
Messages NonStop Operating System Event Messages (ZNSK) 120: ZNSK-EVT-MAB-PIN-MISMATCH A process encountered an unregistered memory access breakpoint (MAB).
PAGE 697
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens ZNSK-TKN-CPU ZNSK-TKN-PIN token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text A process encountered a TFDS trigger, but the TFDS subsystem is not registered with Debug Services Unconditional Tokens Token Description ZNSK-TKN-CPU Processor number of the process that encountered the TFDS trigger. ZNSK-TKN-PIN Process identification number of the process that encountered the TFDS trigger. Cause.
PAGE 698
Messages NonStop Operating System Event Messages (ZNSK) 123: ZNSK-EVT-DS-DEREG-ERR The Debug Services monitor encountered an error while deregistering.
PAGE 699
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens ZNSK-TKN-CPU ZNSK-TKN-PIN ZNSK-TKN-ERRORDETAIL token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-INT Event-Message Text Debug Services monitor encountered an error registering itself with NSK Unconditional Tokens Token Description ZNSK-TKN-CPU Processor number of the debugging process. ZNSK-TKN-PIN Process identification number of the debugging process.
PAGE 700
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens Token Description ZNSK-TKN-CPU Processor number of the debugging process. ZNSK-TKN-PIN Process identification number of the debugging process. Cause. The Debug Services monitor successfully registered with the NonStop operating system. Effect. None. Recovery. This is an informational message only; no corrective action is needed. 126: ZNSK-EVT-PRIV-DEBUGGING A debugger enabled privileged debugging with a particular process.
PAGE 701
Messages NonStop Operating System Event Messages (ZNSK) Cause. A debugger enabled privileged debugging with a particular process. Effect. None. Recovery. This is an informational message only; no corrective action is needed. 131: ZNSK-EVT-PS-CHANGE A change is made to the IPU affinity policies of the Process Scheduler in this CPU.
PAGE 702
NonStop Operating System Event Messages (ZNSK) Messages Conditional Tokens Token Description ZNSK-TKN-PIN If there is a change in the IPU affinity of a process, this PIN identifies that process. ZNSK-TKN-IPU If there is a change in the IPU affinity of a process, the process is bound to this IPU. ZNSK-TKN-PS-UNBIND If the IPU affinity of a process is modified to unbind a process, this value will be 1.
PAGE 703
Messages NonStop Operating System Event Messages (ZNSK) 200: ZNSK-EVT-KMS-THRES-XCEED The specified Kernel-Managed Swap Facility (KMSF) swap file exceeded its configured threshold.
PAGE 704
Messages NonStop Operating System Event Messages (ZNSK) Token Description (page 2 of 2) ZNSK-TKN-RESERVEDSIZE The part of the swap file that the processor currently uses. ZNSK-TKN-TOTALSIZE Number of memory pages currently allocated for the swap file. ZNSK-TKN-EXTENTS Number of extents that the swap file has. Cause. The specified kernel-managed swap file (represented by the token ZNSKTKN-FILE) exceeded its configured threshold. Effect.
PAGE 705
Messages NonStop Operating System Event Messages (ZNSK) Effect. The swap file is fully allocated, and disk free space is reduced by its configured size. The swap file cannot be used until it is enabled for use by the NSKCOM START command. Recovery. This is an informational message only; no corrective action is needed. 202: ZNSK-EVT-KMS-SWAP-PURGE A KMSF swap file was purged by the NSKCOM DELETE command.
PAGE 706
Messages NonStop Operating System Event Messages (ZNSK) Recovery. This is an informational message only; no corrective action is needed. 203: ZNSK-EVT-KMS-SWAP-START The specified KMSF swap file was started.
PAGE 707
Messages NonStop Operating System Event Messages (ZNSK) Message sender: Monitor process or NSKCOM process TMDS collector: No OSM/TSM collector: No Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSK-TKN-FILE ZNSK-TKN-CPU token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT Event-Message Text KMSF SWAPFILE STOPPED: swapfile CPU cpu Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVT-KMSSWAP-STOPPED (204).
PAGE 708
Messages NonStop Operating System Event Messages (ZNSK) 206: ZNSK-EVT-KMS-SWAP-MAXEXT-ALTER An NSKCOM ALTER command specified a new value for MAXEXTENTS, the maximum number of extents allowed, for the indicated KMSF swap file.
PAGE 709
Messages NonStop Operating System Event Messages (ZNSK) 207: ZNSK-EVT-KMS-SWAP-THRES-ALTER An NSKCOM ALTER command changed the configured threshold for a Kernel-Managed Swap Facility (KMSF) swap file.
PAGE 710
Messages NonStop Operating System Event Messages (ZNSK) 208: ZNSK-EVT-KMS-SWAP-STOP-PENDING An NSKCOM STOP command has stopped the indicated KMSF swap file.
PAGE 711
Messages NonStop Operating System Event Messages (ZNSK) Recovery. If other swap files are available for the processor, no corrective action is needed. If no other swap files are available for the processor, you must add and enable a swap file for that processor to allow for process creation. Because you cannot start a new process on that processor while no swap file is enabled, you can run NSKCOM on another processor.
PAGE 712
Messages NonStop Operating System Event Messages (ZNSK) 210: ZNSK-EVT-KMS-CONFIG-NOTFOUND The KMSF configuration file is either missing or corrupt.
PAGE 713
Messages NonStop Operating System Event Messages (ZNSK) 211: ZNSK-EVT-KMS-CONFIG-FILENAME A KMSF configuration file exists.
PAGE 714
Messages NonStop Operating System Event Messages (ZNSK) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSK-TKN-LINE-NUM token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Event-Message Text KMSF CONFIGURATION FILE SYNTAX ERROR ON LINE NUMBER:line-num Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSK-EVT-KMSCONFIG-ERROR (212). ZNSK-TKN-LINE-NUM EDIT line number where the syntax error was detected in the ZSYSCFG file. Cause.
PAGE 715
Messages NonStop Operating System Event Messages (ZNSK) 213: ZNSK-EVT-KMS-SWAP-NOTFOUND A KMSF swap file was not found.
PAGE 716
Messages NonStop Operating System Event Messages (ZNSK) 214: ZNSK-EVT-KMS-SWAP-START-FAILED An attempt to start a KMSF swap file failed.
PAGE 717
Messages NonStop Operating System Event Messages (ZNSK) Recovery. Correct the error as follows, then restart the swap file:    If the disk is down, bring up the disk. If the swap file’s code is incorrect, delete the file. Then use NSKCOM to add and enable the file. If the swap file is specified for multiple processors, add and enable another swap file for each of the other processors. 215: ZNSK-EVT-KMS-SWAP-DEFAULT The NonStop operating system created and enabled a default KMSF swap file.
PAGE 718
NonStop Operating System Event Messages (ZNSK) Messages 300: ZNSK-EVT-CORE-LIC-ENABLED A Core License has been enabled on the system.
PAGE 719
Messages NonStop Operating System Event Messages (ZNSK) 301: ZNSK-EVT-CORE-LIC-FAILED An online Core License Enablement failed..
PAGE 720
Messages NonStop Operating System Event Messages (ZNSK) Message sender: Kernel from VCore functions $ZLOG: Yes $0: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSK-TKN-ENABLED-IPUS ZNSK-TKN-ENABLED-CPUS ZNSK-TKN-CORE-LIC-REASON token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-INT2 Event-Message Text Core license defaults enabled (ENABLED-IPUS IPUs, ENABLEDCPUS CPUs), reason: CORE-LIC-REASON Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMB
PAGE 721
NonStop Operating System Event Messages (ZNSK) Message sender: Kernel from VCore functions $ZLOG: Yes $0: Yes Messages Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSK-TKN-CORE-LIC-REASON token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT2 Event-Message Text Core license not enabled, reason: CORE-LIC-REASON. A valid Core license file needs to be installed Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 722
NonStop Operating System Event Messages (ZNSK) HP NonStop Operating System Event Management Programming Manual—520372-020 13-50 Messages
PAGE 723
14 Shared Run-Time Library (SRL) Event Messages (ZSRL) SRL event messages are reported to the EMS by the ZTILT_CREATE_ system library procedure called by the NonStop operating system, and by the ZTILT process itself. No other process reports these event messages. Table 14-1. SRL Event Messages (page 1 of 3) Event Number and Symbolic Name Description 100: ZSRL-EVT-ADDR-ERR The SRL table in memory has already been loaded or has been corrupted.
PAGE 724
Shared Run-Time Library (SRL) Event Messages (ZSRL) Table 14-1. SRL Event Messages (page 2 of 3) Event Number and Symbolic Name Description 114: ZSRL-EVT-SRL-NAME-ERR The name of an SRL that ZTILT was linked to was not found in the specified SRL when ZTILT process creation was attempted. 115: ZSRL-EVT-SRL-ORDER-ERR The ZTILT internal SRL names table is out of alphabetic sequence. 116: ZSRL-EVT-SRL-FLAG-ERR The specified SRL object file was not built as an SRL.
PAGE 725
Common Definitions Shared Run-Time Library (SRL) Event Messages (ZSRL) Table 14-1. SRL Event Messages (page 3 of 3) Event Number and Symbolic Name Description 130: ZSRL-EVT-PARTIAL-SRL-REMOVED The specified SRL was not loaded because of the given reason. 131: ZSRL-EVT-NO-RLD-LOADED No rld was loaded; PIC programs cannot be run. 132: ZSRL-EVT-NOT-ALL-HYBRIDS The indicated number of SRLs are not hybrid SRLs.
PAGE 726
Shared Run-Time Library (SRL) Event Messages (ZSRL) Subsystem Programmatic Interface (SPI) Standard Definitions Subsystem Programmatic Interface (SPI) Standard Definitions SPI standard definitions that have a specific meaning for SRL events are listed in Table 14-2. SPI standard definitions are described in detail in the SPI Programming Manual. Table 14-2.
PAGE 727
Shared Run-Time Library (SRL) Event Messages (ZSRL) Event Management Service (EMS) Standard Definitions Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for SRL events are listed in Table 14-3. EMS standard definitions are described in detail in the EMS Manual. Table 14-3.
PAGE 728
Shared Run-Time Library (SRL) Event Messages (ZSRL) Shared Run-Time Library (ZSRL-) Definitions Private Token and Field Types Token Description ZSRL-DDL-MSG-BUFFER SPI message buffer that you must use for SRL event messages (see Figure 14-2). ZCPU-TKN-CPU-TYPE Subject token that specifies the processor type (see Table 14-4). ZCPU-TKN-NEV-MODEL Processor model ID (see Table 14-5 on page 14-7). ZCPU-TKN-YOS-MODEL Processor model ID (see Table 14-6 on page 14-7). Figure 14-2.
PAGE 729
Shared Run-Time Library (SRL) Event Messages (ZSRL) Shared Run-Time Library (ZSRL-) Definitions Table 14-5. ZCPU-TKN-NEV-MODEL Values Value Processor Model ID Processor 0 (with processor type 8) NSR-W S7000 0 (with processor type 9) NSR-G S70000 1 NSR-T S72000 2 NSR-V S74000 3 NSR-X S76000 4 NSR-Y S86000 5 NSR-Z S88000 10 NSR-D S7400 11 NSR-E S7600 13 NSR-H S78000 14 NSR-J S7800 Table 14-6.
PAGE 730
Shared Run-Time Library (SRL) Event Messages (ZSRL) Description of ZSRL Event Messages Description of ZSRL Event Messages The SRL event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZSRL-EVT-name, where name describes the event that generated the message.
PAGE 731
Recovery Action Requiring Vendor Support Shared Run-Time Library (SRL) Event Messages (ZSRL)  A box contains the list of tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens. The tokens might not necessarily appear in the message buffer in the same order that they are listed in the box. The tokens in the list are either:   Unconditional (always present in the message).
PAGE 732
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Event-Message Text SRL_TABLE_ADDRESS already loaded or corrupt. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-ADDRERR (100). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. Cause. The internal public SRL table in the processor’s memory has already been loaded or has been corrupted. Effect.
PAGE 733
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-ZTILTLOC-ERR (101). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FECODE File-system error number. ZSRL-TKN-FILE Name of the ZTILT program file. Cause. A file-system error occurred during an attempt to find the ZTILT program file. Effect.
PAGE 734
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-ZTILTSECUR-ERR (102). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FILE Name of the ZTILT program file. Cause. The ZTILT object file was not owned by the super ID (255, 255).
PAGE 735
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Cause. A file-system error occurred while the ZTILT program environment was being created. Effect. ZTILT process creation is terminated, and no public SRLs are loaded. Recovery. Examine the file-system error to determine the cause of the problem and correct it. For example, file-system error 11, indicating that the ZTILT file was not found, could be encountered if ZTILT was not placed in the system-load SYSnn subvolume.
PAGE 736
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Token Description (page 2 of 2) ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-MODSTAMP Modification time stamp of the ZTILT file in Greenwich mean time (GMT). ZSRL-TKN-FILEEOF EOF value for the ZTILT file. Cause. The indicated ZTILT program file is not an executable native object file (a file in the ELF format). Either the filecode is not 700, or the file is internally corrupt. Effect.
PAGE 737
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-ZTILTREAD-ERR (105). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FECODE File-system error number. ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-MODSTAMP Modification timestamp of the ZTILT file in GMT.
PAGE 738
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-MEMERR (106). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-MEMCODE Internal memory error that occurred. Cause. An internal error occurred during an attempt to obtain memory for ZTILT’s SRLs. Effect.
PAGE 739
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Token Description (page 2 of 2) ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-MODSTAMP Modification timestamp of the ZTILT file in GMT. ZSRL-TKN-FILEEOF EOF value for the ZTILT file. Cause. The indicated ZTILT program file does not have any entries in its internal PUBLIC_SRL_NAMES table. Effect. ZTILT process creation is terminated, and no public SRLs are loaded. Recovery.
PAGE 740
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLLOCATED (108). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. ZSRL-TKN-TILTNUM SRL’s tilt number in the ZTILT SRL table. ZSRL-TKN-SRL SRL name. ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-MODSTAMP Modification timestamp of the ZTILT file in GMT.
PAGE 741
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLOPEN-ERR (109). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FECODE File-system error number. ZSRL-TKN-FILE Name of the ZTILT program file. Cause. A file-system error occurred during an attempt to open the indicated SRL. Effect.
PAGE 742
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLNAME-EDIT-ERR (110). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FECODE File-system error number. ZSRL-TKN-FILE Name of the ZTILT program file. Cause. A file-system error occurred during an attempt to locate the SRL or construct its name. Effect.
PAGE 743
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLSTRUCT-ERR (111). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-MODSTAMP Modification timestamp of the ZTILT file in GMT. ZSRL-TKN-FILEEOF EOF value for the ZTILT file. Cause.
PAGE 744
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLREAD-ERR (112). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FECODE File-system error number. ZSRL-TKN-FILE Name of the ZTILT program file. Cause. A file-system error occurred during an attempt to locate a position within the indicated SRL. Effect.
PAGE 745
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLTANDEM-INFO-ERR (113). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-MODSTAMP Modification timestamp of the ZTILT file in GMT. ZSRL-TKN-FILEEOF EOF value for the ZTILT file. Cause.
PAGE 746
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLNAME-ERR (114). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-SRL SRL name. ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-OTHER Name of the SRL that ZTILT was expecting. Cause.
PAGE 747
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLORDER-ERR (115). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-SRL SRL name in the ZTILT SRL table. ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-OTHER SRL name in the ZTILT SRL table that precedes the name specified by ZSRL-TKN-SRL. Cause.
PAGE 748
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLFLAG-ERR (116). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-MODSTAMP Modification timestamp of the ZTILT file in GMT. ZSRL-TKN-FILEEOF EOF value for the ZTILT file. Cause.
PAGE 749
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-ZTILTSTART-ERR (117). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-ERRORCODE PROCESS_CREATE_ error that occurred. ZSRL-TKN-ERRORDETAIL Error detail code for the PROCESS_CREATE_ error that occurred. Cause.
PAGE 750
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-SRLSTARTED (118). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the event. Cause. The ZTILT process was successfully created and all public SRLs were successfully loaded. Effect. All public SRLs are available for use. Recovery.
PAGE 751
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Token Description (page 2 of 2) ZSRL-TKN-ERRORCODE PROCESS_CREATE_ error that occurred. ZSRL-TKN-ERRORDETAIL Error detail code for the PROCESS_CREATE_ error that occurred. Cause. An attempt was made to start a second ZTILT process in the same processor. Effect. The second ZTILT process terminates. Recovery. Run LTILT to determine whether there are any SRLs.
PAGE 752
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSRL-EVT-ZTILTRECV-ERR (120). ZSRL-TKN-CPU Subject token that specifies the processor number of the processor that is reporting the error. ZSRL-TKN-FECODE File-system error number. Cause. The ZTILT process encountered a FILE_OPEN_ error when it attempted to open $RECEIVE. Effect. The ZTILT process terminates. Recovery.
PAGE 753
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Token Description (page 2 of 2) ZSRL-TKN-FILE Name of the ZTILT program file. ZSRL-TKN-MODSTAMP Modification timestamp of the ZTILT file in GMT. ZSRL-TKN-FILEEOF EOF value for the ZTILT file. Cause. The indicated SRL object file does not contain an ELF TANDEM_GINFO section. Effect. ZTILT process creation is terminated, and no public SRLs are loaded. Recovery.
PAGE 754
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Token Description (page 2 of 2) ZSRL-TKN-MODSTAMP Modification timestamp of the ZTILT file in GMT. ZSRL-TKN-FILEEOF EOF value for the ZTILT file. Cause. The indicated ZTILT object file was successfully located. Effect. Processing of the ZTILT object file continues. SRL loading is attempted. Recovery. This is an informational message only; no corrective action is needed.
PAGE 755
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Cause. The indicated ZTILT program file does not contain a GINFO section in its internal PUBLIC_SRL_NAMES table. Effect. ZTILT process creation is terminated, and no public SRLs are loaded. Recovery. Ensure that the program file is actually the ZTILT program file, and if it is not, install the correct program file. If the error persists, the ZTILT program file is probably corrupted. See Recovery Action Requiring Vendor Support on page 14-9.
PAGE 756
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Recovery. Ensure that the object file is actually the ZTILT object file, and if it is not, install the correct object file. If the error persists, the ZTILT object file is probably corrupted. See Recovery Action Requiring Vendor Support on page 14-9. 125: ZSRL-EVT-ZTILT-GINFO-SRL-ERR ZTILT was linked to an SRL that was not defined in its internal SRL names table.
PAGE 757
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Recovery. Ensure that the object file is actually the ZTILT object file, and if it is not, install the correct object file. If the error persists, the ZTILT object file is probably corrupted. See Recovery Action Requiring Vendor Support on page 14-9. 126: ZSRL-EVT-ZTILT-TABLE-SRL-ERR ZTILT is not linked by the native mode linker (nld) to the specified SRL, or the SRL’s version is not exported to ZTILT.
PAGE 758
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Cause. The indicated SRL is defined in the internal ZTILT PUBLIC_SRL_NAMES table, but either ZTILT is not linked to it with nld, the native mode linker, or the SRL’s version is not exported to ZTILT. Effect. ZTILT process creation is terminated, and no public SRLs are loaded. Recovery. Ensure that the object file is actually the ZTILT object file, and if it is not, install the correct object file.
PAGE 759
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) Recovery. Examine the file-system error and the specified ZTILT object file to determine the cause of the error and attempt to correct the problem. For a description of the given error, see the description of file-system errors in the Operator Messages Manual. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.
PAGE 760
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) 129: ZSRL-EVT-PARTIAL-ERR-RECOVERY The ZTILT process was created successfully, but some SRLs were not loaded.
PAGE 761
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) 130: ZSRL-EVT-PARTIAL-SRL-REMOVED The specified SRL was not loaded for the given reason.
PAGE 762
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) 131: ZSRL-EVT-NO-RLD-LOADED No rld was loaded; PIC programs cannot be run. Subject: ZSRL-TKN-CPU Potentially critical event: Yes Action event: No Message sender: ZTILT_CREATE_ library procedure TMDS collector: No OSM/TSM collector: No Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSRL-TKN-CPU token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text No RLD was loaded. PIC programs cannot be run.
PAGE 763
Messages Shared Run-Time Library (SRL) Event Messages (ZSRL) 132: ZSRL-EVT-NOT-ALL-HYBRIDS The indicated number of SRLs are not hybrid SRLs.
PAGE 764
Shared Run-Time Library (SRL) Event Messages (ZSRL) HP NonStop Operating System Event Management Programming Manual—520372-020 14-42 Messages
PAGE 765
15 XIO Subsystem Event Messages (ZXIO) XIO subsystem event messages are reported to the EMS by:      XIO monitor (XIOMON) Process invoking XIO library call XioColoradoPktConfig() Process invoking XIO library call XioEvtInfo() Process invoking the XIO procedure XioEvtBadRc() Process invoking the XIO procedure XioPktConfig() Table 15-1.
PAGE 766
Common Definitions XIO Subsystem Event Messages (ZXIO) Table 15-1. XIO Subsystem Event Messages (page 2 of 2) Event Number and Symbolic Name Description 112: ZXIO-EVT-TNET-BADRC A ServerNet request related to the ServerNet addressable controller (SAC) failed. 113: ZXIO-EVT-MDRVR-BADRCC A SCSI MD error occurred when an attempt was made to initialize a SAC packetizer. 114: ZXIO-EVT-BADRCC A generic message that is issued when an API returns an error.
PAGE 767
XIO Subsystem Event Messages (ZXIO) Subsystem Programmatic Interface (SPI) Standard Definitions Subsystem Programmatic Interface (SPI) Standard Definitions SPI standard definitions that have a specific meaning for XIO subsystem events are listed in Table 15-2. SPI standard definitions are described in detail in the SPI Programming Manual. Table 15-2.
PAGE 768
Event Management Service (EMS) Standard Definitions XIO Subsystem Event Messages (ZXIO) Event Management Service (EMS) Standard Definitions EMS standard definitions hat have a specific meaning for XIO subsystem events are listed in Table 15-3. EMS standard definitions are described in detail in the EMS Manual. Table 15-3.
PAGE 769
XIO Subsystem Event Messages (ZXIO) Description of ZXIO Event Messages Predefined Token and Field Values Token Description ZXIO-VAL-SSID XIO subsystem ID—the structure is shown under the description for ZSPI-TKN-SSID ZXIO-VAL-VERSION Version number of the XIO subsystem Simple Tokens and Structured Tokens These tokens are described in the event-message descriptions. Description of ZXIO Event Messages The ZXIO event messages are described in detail on the following pages.
PAGE 770
Recovery Action Requiring Vendor Support XIO Subsystem Event Messages (ZXIO)   Indicating whether the event message is sent to the TMDS collector (D-series NonStop operating system RVUs) or OSM/TSM collector (G-series and Hseries NonStop operating system RVUs). A box contains the list of tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens.
PAGE 771
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZXIO-TKN-ADAPTER-NAME ZXIO-TKN-SAC-NAME token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Adapter record with name adapter-name for SAC sac-name was not found in CONFIG. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Subject token that specifies the event number for this message.
PAGE 772
Messages XIO Subsystem Event Messages (ZXIO) Event-Message Text SAC record for SAC sac-name was not found in CONFIG Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVT-SACREC-NOT-FOUND (101). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-SAC-NAME SAC name that was requested. Cause. The XIO subsystem did not find a SAC record in CONFIG for the specified SAC. Effect.
PAGE 773
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVTCONFIG-MISMATCH (102). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-SAC-NAME SAC name that was requested. ZXIO-TKN-CONFIG-PRODUCT-ID Product ID of the SAC in CONFIG. ZXIO-TKN-HWINV-PRODUCT-ID Product ID as specified in the hardware inventory. Cause.
PAGE 774
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVTINSTALL-DEV-FAIL (103). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-SAC-NAME SAC name that was requested. Cause. ServerNet Services returned an error to the XIO subsystem during the installation of a device handle. Effect. The device handle for this module is invalid.
PAGE 775
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVT-SETSNETID-FAIL (104). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-SNET-ID ServerNet ID. ZXIO-TKN-SNET-DEV-HANDLE ServerNet device handle. ZXIO-TKN-SAC-NAME SAC name that was requested. Cause. ServerNet Services returned an error during an attempt to set the ServerNet ID. Effect.
PAGE 776
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVT-PKTSETUP-TIMEOUT (105). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-SNET-ID ServerNet ID of the ICEPACK. ZXIO-TKN-SNET-DEV-HANDLE ServerNet device handle. ZXIO-TKN-ADAPTER-NAME Adapter name that corresponds to the SAC in this event. Cause. The ICEPACK setup response timed out. Effect.
PAGE 777
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVT-MTCREATE-FAIL (106). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-MT-SIZE Size (in number of entries) of the module table that the XIO subsystem attempted to create. Cause. An error was detected during an attempt to expand the module table. Effect.
PAGE 778
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVT-PKTSETUP-FAIL (107). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-SNET-ID ServerNet ID of the ICEPACK. ZXIO-TKN-SNET-DEV-HANDLE ServerNet device handle. ZXIO-TKN-ADAPTER-NAME Adapter name that corresponds to the SAC in this event. Cause. XIOMON could not configure the ICEPACK. Effect.
PAGE 779
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVT-SLMERROR (108). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-ERR-DESC Description of the error. ZXIO-TKN-ADAPTER-NAME Name of the adapter experiencing the error. ZXIO-TKN-SLM-RC Return code resulting from the SCSI Lock Manager request.
PAGE 780
Messages XIO Subsystem Event Messages (ZXIO) Conditional Tokens ZXIO-TKN-COL-REG-DATA0 ZXIO-TKN-COL-REG-DATA1 ZXIO-TKN-COL-REG-DATA2 ZXIO-TKN-COL-REG-DATA3 ZXIO-TKN-COL-REG-ADDR0 ZXIO-TKN-COL-REG-ADDR1 ZXIO-TKN-COL-REG-ADDR2 ZXIO-TKN-COL-REG-ADDR3 token-type token-type token-type token-type token-type token-type token-type token-type is is is is is is is is ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 ZSPI-TYP-INT4 Event-Message Text TANDEM.XIO.
PAGE 781
Messages XIO Subsystem Event Messages (ZXIO) Recovery. This event is generated as a result of a hardware problem. Check the hardware indicated in this event. If the error persists, see Recovery Action Requiring Vendor Support on page 15-6. 110: ZXIO-EVT-INFORMATIONAL An informational message used by software developers to capture a current processing state.
PAGE 782
Messages XIO Subsystem Event Messages (ZXIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZXIO-EVT-INFORMATIONAL (110). ZEMS-TKN-XLDEVNAME Subject token that specifies the subsystem name for this event. ZXIO-TKN-ERR-DESC Description of the error. ZXIO-TKN-XIO-RC XIO return code resulting from this error. ZXIO-TKN-XIOSTRING1-XIOTKN-XIOSTRING6 Event-related descriptions and values related to these descriptions.
PAGE 783
Messages XIO Subsystem Event Messages (ZXIO) Conditional Tokens ZXIO-TKN-GROUP ZXIO-TKN-MODULE ZXIO-TKN-SLOT ZXIO-TKN-ADAPTER-NAME token-type token-type token-type token-type is is is is ZSPI-TYP-INT2 ZSPI-TYP-INT2 ZSPI-TYP-INT2 ZSPI-TYP-STRING Event-Message Text TANDEM.XIO.
PAGE 784
Messages XIO Subsystem Event Messages (ZXIO) 112: ZXIO-EVT-TNET-BADRC A ServerNet request related to the SAC failed.
PAGE 785
Messages XIO Subsystem Event Messages (ZXIO) Token Description (page 2 of 2) ZXIO-TKN-SITUATION Description of the scenario in which the failure occurred. ZXIO-TKN-INVOKEE-NAME Name of ServerNet API that was invoked. ZXIO-TKN-BADRC Error code returned from the ServerNet API that was invoked. ZXIO-TKN-SAC-NAME SAC name. Conditional Tokens Token Description ZXIO-TKN-SNET-DEVHANDLE ServerNet Device Handle associated with the request. ZXIO-TKN-SNET-ID ServerNet ID associated with the request.
PAGE 786
Messages XIO Subsystem Event Messages (ZXIO) ZXIO-TKN-ADAPTER-NAME ZXIO-TKN-SNET-ID ZXIO-TKN-SNET-DEVHANDLE ZXIO-TKN-TNET-CODE ZXIO-TKN-TNET-PATH ZXIO-TKN-MDRVR-REQCODE token-type token-type token-type token-type token-type token-type is is is is is is ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-INT4 ZSPI-TYP-INT2 ZSPI-TYP-INT ZSPI-TYP-INT Event-Message Text TANDEM.XIO.
PAGE 787
Messages XIO Subsystem Event Messages (ZXIO) Recovery. Check the ServerNet Path related to the adapter. Ensure the adapter is properly seated and the related ServerNet paths are up. If the problem still persists, see Recovery Action Requiring Vendor Support on page 15-6. 114: ZXIO-EVT-BADRCC A generic message that is issued when an API returns an error.
PAGE 788
Messages XIO Subsystem Event Messages (ZXIO) 115: ZXIO-EVT-COL-PKT-SETUP-TIMEOUT A MD request to ServerNet timed out during Colorado setup.
PAGE 789
Messages XIO Subsystem Event Messages (ZXIO) 116: ZXIO-EVT-DEINSTALL-DEV-FAIL The deinstallation of a ServeNet device handle failed.
PAGE 790
XIO Subsystem Event Messages (ZXIO) HP NonStop Operating System Event Management Programming Manual—520372-020 15-26 Messages
PAGE 791
16 Nonstop Operating System Message System Event Messages (ZIPC) NonStop operating system message system event messages are reported to EMS by the monitor process on behalf of the message system. No other process reports these event messages. Table 16-1. Message System Event Messages (page 1 of 2) Event Number and Symbolic Name Description 100: ZIPC-EVT-DET-SEQ-ERR The reporting processor received an out-ofsequence ServerNet message system interrupt packet from the problem processor.
PAGE 792
Nonstop Operating System Message System Event Messages (ZIPC) Table 16-1. Message System Event Messages (page 2 of 2) Event Number and Symbolic Name Description 115: ZIPC-EVT-SUPPRESS-MSG Logging of PATH-DOWN and PATH-UP (events 110 and 111) have been temporarily suspended for the indicated path, because the events were occurring too often. 116: ZIPC-EVT-PATH-RECOVERY-COUNT The number of automatic recoveries has been recorded for the indicated path since the last log.
PAGE 793
Common Definitions Nonstop Operating System Message System Event Messages (ZIPC) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 794
Event Management Service (EMS) Standard Definitions Nonstop Operating System Message System Event Messages (ZIPC) Figure 16-1. ZIPC-VAL-SSID Structure def ZIPC-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-INT value is ZSPI-SSN-ZIPC. 02 Z-VERSION type ZSPI-DDL-UINT value is ZIPC-VAL-VERSION. end. Token Description ZSPI-TKN-SSID Contains ZIPC-VAL-SSID, the subsystem ID of the message system.
PAGE 795
Nonstop Operating System Message System Event Messages (ZIPC) NonStop Message System (ZIPC-) Definitions NonStop Message System (ZIPC-) Definitions Message system definitions begin with ZIPC- and are found in the source-definition files ZIPCTAL, ZIPCCOB, ZIPCTACL, ZIPCDDL, ZIPCC, and ZIPCPAS. These definitions are described in this section.
PAGE 796
NonStop Message System (ZIPC-) Definitions Nonstop Operating System Message System Event Messages (ZIPC) Token Description (page 2 of 2) ZIPC-ENM-POOR-QUALITY Indicates that there were excessive BTE timeouts on the path. ZIPC-ENM-MAX-REVIVALS Indicates that there were persistent BTE timeouts on the path. ZIPC-ENM-PATH-AUTO-UP Indicates that an automatic path recovery has occurred. ZIPC-ENM-BARRIER-NACK Indicates that a barrier packet was replied to with a negative acknowledgement.
PAGE 797
NonStop Message System (ZIPC-) Definitions Nonstop Operating System Message System Event Messages (ZIPC) Table 16-5. ZIPC-DDL-RCVD-PKT-STATUS Values (page 2 of 2) Value Meaning ZIPC-ENM-BAD-DID The destination ID of the packet did not match the ID of the processor that received the packet. ZIPC-ENM-SPURIOUS-ACK An out-of-sequence ServerNet acknowledgment was received. ZIPC-ENM-BAD-MASK A ServerNet address was out of range, and the transaction was aborted.
PAGE 798
NonStop Message System (ZIPC-) Definitions Nonstop Operating System Message System Event Messages (ZIPC) Table 16-6. ZIPC-DDL-TR-TYPE Values (page 2 of 2) Value Meaning ZIPC-ENM-TR-BAR-WP-EN A request to send a barrier packet with the path enable option. ZIPC-ENM-TR-ATOMIC-WRITE A request for atomic write. ZIPC-TYP-NACK-CODE The reason that a packet was rejected Figure 16-5. ZIPC-DDL-NACK-CODE Definition ZIPC-TYP-NACK-CODE value is ZSPI-TDT-ENUM def is ZIPC-DDL-NACK-CODE.
PAGE 799
NonStop Message System (ZIPC-) Definitions Nonstop Operating System Message System Event Messages (ZIPC) Table 16-8. ZIPC-DDL-SIB-TYPE Values Value Meaning ZIPC-ENM-NO-SIB The SIB contains no send information. ZIPC-ENM-SEQ-SIB The SIB contains the request to write several data buffers and a setup buffer that interrupts the problem processor. ZIPC-ENM-GETDATA-SIB The SIB contains requests from the operating system to read the memory of the problem processor.
PAGE 800
NonStop Message System (ZIPC-) Definitions Nonstop Operating System Message System Event Messages (ZIPC) Table 16-9. ZIPC-DDL-PATH-REASON Values (page 2 of 2) Value Meaning ZIPC-ENM-OP-UP-CMD An attempt for the reporting processor to start using a fabric to communicate to the problem processor failed. ZIPC-ENM-PATH-OTHER-PATH-DOWN A path was brought up because another path was down. ZIPC-ENM-PATH-DOWN-COMMAND A path cannot be used. ZIPC-ENM-CPUDOWN A processor went down. Figure 16-8.
PAGE 801
Nonstop Operating System Message System Event Messages (ZIPC) Description of ZIPC Event Messages Description of ZIPC Event Messages The ZIPC event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZIPC-EVT-name, where name describes the event that generated the message.
PAGE 802
Nonstop Operating System Message System Event Messages (ZIPC)  Recovery Action Requiring Vendor Support A box contains the list of tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens. The tokens might not necessarily appear in the message buffer in the same order that they are listed in the box. The tokens in the list are either:   Unconditional (always present in the message).
PAGE 803
Messages Nonstop Operating System Message System Event Messages (ZIPC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZIPC-TKN-REPORTING-CPU ZIPC-TKN-PROBLEM-CPU ZIPC-TKN-PATH ZIPC-TKN-SEQ-NO-EXPECTED ZIPC-TKN-SEQ-NO-RECEIVED token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-ENUM ZSPI-TYP-UINT ZSPI-TYP-UINT Conditional Token ZIPC-TKN-PROBLEM-NODE token-type ZSPI-TYP-UINT Event-Message Text Sequence error packets received on the path path b
PAGE 804
Messages Nonstop Operating System Message System Event Messages (ZIPC) Recovery. This is an informational message only; no corrective action is needed. 101: ZIPC-EVT-DET-BAD-PKT-RCVD A ServerNet error has been detected on the indicated path.
PAGE 805
Messages Nonstop Operating System Message System Event Messages (ZIPC) Token Description (page 2 of 2) ZIPC-TKN-RCVD-PKT-STATUS ServerNet error code contained in the packet. ZIPC-TKN-TR-TYPE Type of ServerNet transaction being attempted. ZIPC-TKN-SNET-ADDR-USED Target ServerNet address in the packet. ZIPC-TKN-BYTE-COUNT-USED Length of the packet received, in bytes. Conditional Token Token Description ZIPC-TKN-PROBLEM-NODE Node number of the node containing the problem processor.
PAGE 806
Messages Nonstop Operating System Message System Event Messages (ZIPC) Conditional Token ZIPC-TKN-PROBLEM-NODE token-type ZSPI-TYP-UINT Event-Message Text ServerNet nack received on the path path by processor reporting-cpu from processor problem-cpu {in ServerNet node node-number}.
PAGE 807
Messages Nonstop Operating System Message System Event Messages (ZIPC) Effect. If the error is because of a power fail recovery or the nack status code indicates an interrupt to a full queue, the packet will eventually be resent. Otherwise,, both plans will be downed and communication to the problem processor will be severed. If the problem and reporting processors are in the same system, regroup will be invoked, which will halt one of the processors. Recovery.
PAGE 808
Nonstop Operating System Message System Event Messages (ZIPC) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPC-EVTDET-BAD-DID-PKT-RCVD (103). ZIPC-TKN-REPORTING-CPU Processor number of the processor on which the error was detected. ZIPC-TKN-PROBLEM-CPU Subject token that specifies the processor in which the message originated. ZIPC-TKN-PATH Fabric over which the message was transmitted.
PAGE 809
Messages Nonstop Operating System Message System Event Messages (ZIPC) 104: ZIPC-EVT-DET-UNEXP-PKT-RCVD The reporting processor has received a message from a source processor which it does not believe is up.
PAGE 810
Messages Nonstop Operating System Message System Event Messages (ZIPC) Cause. The problem processor was sending “I'm alive” packets to the reporting processor, but the reporting processor has declared the problem processor as down. Effect. Generally, the reporting processor ignores the packet; but for packets originating in the local system, the reporting processor returns a “poison packet” to the problem processor, causing it to halt itself. Recovery.
PAGE 811
Nonstop Operating System Message System Event Messages (ZIPC) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPC-EVT-PATHDOWN (110). ZIPC-TKN-REPORTING-CPU Processor number of the processor on which the error was detected. ZIPC-TKN-PROBLEM-CPU Subject token that specifies the processor in which the message originated. ZIPC-TKN-PATH Fabric over which the message was transmitted. ZIPC-TKN-PATH-REASON Reason the path was taken down.
PAGE 812
Messages Nonstop Operating System Message System Event Messages (ZIPC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZIPC-TKN-REPORTING-CPU ZIPC-TKN-PROBLEM-CPU ZIPC-TKN-PATH ZIPC-TKN-PATH-REASON token-type token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-ENUM ZSPI-TYP-ENUM Conditional Token ZIPC-TKN-PROBLEM-NODE token-type ZSPI-TYP-UINT Event-Message Text The path path from processor reporting-cpu to processor problem-cpu, {in ServerNet node node-number,} wa
PAGE 813
Messages Nonstop Operating System Message System Event Messages (ZIPC) 112: ZIPC-EVT-FABRIC-DOWN The reporting processor’s connection to the ServerNet fabric has failed or been brought down.
PAGE 814
Messages Nonstop Operating System Message System Event Messages (ZIPC) 113: ZIPC-EVT-FABRIC-UP The reporting processor has recovered its connection to the ServerNet fabric.
PAGE 815
Messages Nonstop Operating System Message System Event Messages (ZIPC) 114: ZIPC-EVT-FABRIC-STILL-DOWN The connection between the indicated processor and fabric has been down for over ten minutes..
PAGE 816
Messages Nonstop Operating System Message System Event Messages (ZIPC) 115: ZIPC-EVT-SUPPRESS-MSG Logging of PATH-DOWN and PATH-UP (events 110 and 111) for the indicated path is temporarily suspended because the events are occurring too frequently.
PAGE 817
Messages Nonstop Operating System Message System Event Messages (ZIPC) Effect. The logging of PATH-UP and PATH-DOWN events on the indicated path is suspended to avoid flooding the logs. Recovery. This is an informational message only; no corrective action is needed. 116: ZIPC-EVT-PATH-RECOVERY-COUNT Document the number of automatic recoveries of the indicated path since the last time it was logged.
PAGE 818
Messages Nonstop Operating System Message System Event Messages (ZIPC) Conditional Token Token Description ZIPC-TKN-PROBLEM-NODE Node number of the node containing the problem processor. This is an optional token and is not passed if the reporting and problem processors are in the same (local) node. Cause. The number of automatic recoveries has been recorded for the indicated path since the last log. Effect. None, the system is simply displaying a count indicating ongoing actions. Recovery.
PAGE 819
Messages Nonstop Operating System Message System Event Messages (ZIPC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPC-EVT-BTETIMEOUTS (120). ZIPC-TKN-REPORTING-CPU Processor number of the processor making this report, in this case, the sending processor. ZIPC-TKN-PROBLEM-CPU Subject token that specifies the processor at the other end of the point-to-point connection, in this case, the target processor.
PAGE 820
Messages Nonstop Operating System Message System Event Messages (ZIPC) Conditional Token ZIPC-TKN-PROBLEM-NODE token-type ZSPI-TYP-UINT Event-Message Text Barrier timeouts on the path path from processor reportingcpu to processor problem-cpu {in ServerNet node node-number}. Number of barrier timeouts: count. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPC-EVTBARRIER-TIMEOUTS (121).
PAGE 821
Messages Nonstop Operating System Message System Event Messages (ZIPC) 122: ZIPC-EVT-SPURIOUS-ACKS Spurious ServerNet acknowledgments are occurring on the indicated path.
PAGE 822
Messages Nonstop Operating System Message System Event Messages (ZIPC) Conditional Token Token Description ZIPC-TKN-PROBLEM-NODE Node number of node containing the problem processor. This is an optional token and is not passed if the reporting and problem processors are in the same (local) node. Cause. Spurious ServerNet acknowledgments occurred on the indicated path. Effect. None. Note. Spurious ACKs are normally reported if the problem processor is subjected to heavy ServerNet traffic.
PAGE 823
Messages Nonstop Operating System Message System Event Messages (ZIPC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPC-EVTSEQUENCE-ERRS (123). ZIPC-TKN-REPORTING-CPU Processor number of the processor making this report, in this case, the processor receiving the sequence errors.
PAGE 824
Messages Nonstop Operating System Message System Event Messages (ZIPC) Conditional Tokens ZIPC-TKN-UNSUP-PKT-TYPE ZIPC-TKN-UNSUP-PKT-LENGTH ZIPC-TKN-BAD-MASK ZIPC-TKN-BAD-SOURCE ZIPC-TKN-ACCESS-ERROR ZIPC-TKN-BAD-INTERRUPT ZIPC-TKN-INT-TO-FULL-Q ZIPC-TKN-PROBLEM-NODE token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT2 ZSPI-TYP-INT2 ZSPI-TYP-INT2 ZSPI-TYP-INT2 ZSPI-TYP-INT2 ZSPI-TYP-INT2 ZSPI-TYP-INT2 ZSPI-TYP-UINT Event-Message Text Bad ServerNet packet
PAGE 825
Messages Nonstop Operating System Message System Event Messages (ZIPC) Token Description (page 2 of 2) ZIPC-TKN-INT-TO-FULL-Q Number of ServerNet interrupts that occurred while the queue was full. ZIPC-TKN-PROBLEM-NODE Node number of the node containing the problem processor. This is an optional token and is not passed if the reporting and problem processors are in the same (local) node. Cause. A summary of the bad packet-type errors detected on the indicated path is logged. Effect.
PAGE 826
Nonstop Operating System Message System Event Messages (ZIPC) Messages Event-Message Text Nacks received on the path path by processor reporting-cpu from processor problem-cpu {in ServerNet node node-number}.
PAGE 827
Messages Nonstop Operating System Message System Event Messages (ZIPC) 126: ZIPC-EVT-BAD-DID-PKT-RCVD This event provides a summary count of packets received on the indicated path, which had an invalid destination ID.
PAGE 828
Messages Nonstop Operating System Message System Event Messages (ZIPC) Conditional Token Token Description ZIPC-TKN-PROBLEM-NODE Node number of the node containing the problem processor. This is an optional token and is not passed if the reporting and problem processors are in the same (local) node. Cause. A summary of packet counts with invalid destination ID are received on the indicated path. Effect. None, the summary is simply logged periodically. Recovery.
PAGE 829
Messages Nonstop Operating System Message System Event Messages (ZIPC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPC-EVTUNEXP-PKT-RCVD (127). ZIPC-TKN-REPORTING-CPU Processor number of the processor making this report. ZIPC-TKN-PROBLEM-CPU Subject token that specifies the processor at the other end of this point-to-point connection. ZIPC-TKN-PATH Fabric on which the errors were detected. ZIPC-TKN-COUNT Number of unexpected packets.
PAGE 830
Messages Nonstop Operating System Message System Event Messages (ZIPC) Conditional Tokens ZIPC-TKN-R10K-LOGALTBUFSWOK ZIPC-TKN-R10K-LIFEALTBUFSWOK ZIPC-TKN-R10K-LOGALTBUFSWFAIL ZIPC-TKN-R10K-LIFEALTBUFSWFAIL ZIPC-TKN-R10K-FAILBUFADDR ZIPC-TKN-R10K-FAILBUFTYPE ZIPC-TKN-R10K-SOURCENODE ZIPC-TKN-R10K-SOURCECPU ZIPC-TKN-R10K-PIN * ZIPC-TKN-R10K-INTERNALDATA ZIPC-TKN-R10K-REQCONTROLSIZE ZIPC-TKN-R10K-REQDATASIZE ZIPC-TKN-R10K-REPLYCONTROLSIZE ZIPC-TKN-R10K-REPLYDATASIZE token-type ZSPI-TYP-UNIT token-type ZSP
PAGE 831
Messages Nonstop Operating System Message System Event Messages (ZIPC) Token Description (page 2 of 2) ZIPC-TKN-R10K-LOGSPECWRITE Number of occurrences of this event since the last time one was logged. ZIPC-TKN-R10K-LIFESPECWRITE Number of occurrences of this event. in this processor, since the system was loaded.
PAGE 832
Messages Nonstop Operating System Message System Event Messages (ZIPC) Token Description (page 2 of 2) ZIPC-TKN-R10K-REQCONTROLSIZE Size of the message’s request control element, in bytes. ZIPC-TKN-R10K-REQDATASIZE Size of the message’s data element, in bytes. ZIPC-TKN-R10K-REPLYCONTROLSIZE Size of the message’s reply control element, in bytes. ZIPC-TKN-R10K-REPLYCONTROLSIZE Size of the message’s reply control element, in bytes. Cause.
PAGE 833
Nonstop Operating System Message System Event Messages (ZIPC) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZIPC-EVTRGP-COMPLETION (150). ZIPC-TKN-REPORTING-CPU Processor number of the processor making this report. It is the highest numbered processor that survived the regroup incident. ZIPC-TKN-PROBLEM-CPU Subject token to which all communication was lost. ZIPC-TKN-RGP-REASON Reason that the regroup was started.
PAGE 834
Nonstop Operating System Message System Event Messages (ZIPC) HP NonStop Operating System Event Management Programming Manual—520372-020 16-44 Messages
PAGE 835
17 NonStop Subsystem Manager Event Messages (ZKRN) NonStop subsystem manager (ZKRN) event messages are reported to the EMS by the NonStop subsystem manager process ($ZZKRN). Table 17-1. NonStop Subsystem Event Messages Event Number and Symbolic Name Description 1: ZKRN-EVT-CONFIG-MISMATCH A system configuration mismatch has been detected. 2: ZKRN-EVT-POWER-DOWN The NonStop subsystem manager initiated a system power down.
PAGE 836
Common Definitions NonStop Subsystem Manager Event Messages (ZKRN) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 837
NonStop Subsystem Manager Event Messages (ZKRN) Event Management Service (EMS) Standard Definitions Token Description ZSPI-TKN-SSID Contains ZKRN-VAL-SSID, the subsystem ID of the NonStop subsystem manager. ZSPI-SSN-ZKRN Subsystem number assigned to the NonStop subsystem manager. Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for NonStop subsystem manager events are listed in Table 17-3.
PAGE 838
NonStop Subsystem Manager (ZKRN-) Definitions NonStop Subsystem Manager Event Messages (ZKRN) Token Description (page 2 of 2) ZEMS-TKN-PIN PIN of the affected process. ZEMS-TKN-PROC-DESC Process descriptor of the affected process. ZEMS-TKN-USERID PAID of the affected process. NonStop Subsystem Manager (ZKRN-) Definitions NonStop subsystem manager definitions begin with ZKRN- and are found in the source-definition files ZKRNTAL, ZKRNCOB, ZKRNTACL, ZKRNDDL, ZKRNC, and ZKRNPAS.
PAGE 839
NonStop Subsystem Manager Event Messages (ZKRN) Description of ZKRN Event Messages Description of ZKRN Event Messages The NonStop subsystem manager event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZKRN-EVT-name, where name describes the event that generated the message.
PAGE 840
NonStop Subsystem Manager Event Messages (ZKRN)  Recovery Action Requiring Vendor Support A box contains the list of tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens. The tokens might not necessarily appear in the message buffer in the same order that they are listed in the box. The tokens in the list are either:   Unconditional (always present in the message).
PAGE 841
Messages NonStop Subsystem Manager Event Messages (ZKRN) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZKRN-TKN-PROC-NAME ZKRN-TKN-CONFIG-NAME ZKRN-TKN-CONFIG-SYSNUM ZKRN-TKN-CONFIG-DST ZKRN-TKN-CONFIG-GMT ZKRN-TKN-ACTUAL-SYSNAME ZKRN-TKN-ACTUAL-SYSNUM ZKRN-TKN-ACUTAL-DST token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-ENUM ZKRN-TIME-ZONE-OFFSET ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-ENUM
PAGE 842
Messages NonStop Subsystem Manager Event Messages (ZKRN) 2: ZKRN-EVT-POWER-DOWN The NonStop subsystem manager initiated a system power down.
PAGE 843
Messages NonStop Subsystem Manager Event Messages (ZKRN) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZKRN-TKN-PROC-NAME ZKRN-TKN-GP-NAMES token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Event-Message Text System failed to backout name reservation records Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZKRN-EVTCONFIG-BACKOUT-FAILED (3).
PAGE 844
Messages NonStop Subsystem Manager Event Messages (ZKRN) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZKRN-EVTALLPROC-ADDED (4). ZKRN-TKN-PROC-NAME Subject token that specifies the process name of the subsystem manager ($ZZKRN). Cause. Because no ALLPROCESSORS record was found in the system configuration database, a default ALLPROCESSORS record was added. This message occurs when the system is loaded from CONFBASE. Effect. None. Recovery.
PAGE 845
Messages NonStop Subsystem Manager Event Messages (ZKRN) Cause. A default KRN_SUBSYS record was added to the system configuration database because no KRN_SUBSYS record was found in the system configuration database. This message occurs when the system is loaded from CONFBASE. Effect. None. Recovery. This is an informational message only; no corrective action is needed.
PAGE 846
Messages NonStop Subsystem Manager Event Messages (ZKRN) 9: ZKRN-EVT-DCT-ALTERED-MEDIUM The size of the DCT was changed to MEDIUM (65,375 entries) in the system configuration. Subject: ZKRN-EVT-DCT-ALTERED-MEDIUM Potentially critical event: No Action event: No Message sender: NonStop Subsytem Manager TMDS collector: No OSM/TSM collector: Yes Unconditional Token ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT Event-Message Text Size of DCT altered to MEDIUM (65375) in system configuration.
PAGE 847
18 NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) NSC is an internal library used by the NonStop persistence monitor process ($ZPM), the storage subsystem manager process ($ZZSTO), and the Tandem Failure Data System (TFDS) process ($ZDMP). NSC event messages are reported to the EMS by processes based on the NSC. Table 18-1. NonStop C-Base Multitasking Engine (NSC) Event Messages (page 1 of 2) Event Number and Symbolic Name Description 1: ZNSC-EVT-CHKPT-ERR A checkpoint failed.
PAGE 848
NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Table 18-1. NonStop C-Base Multitasking Engine (NSC) Event Messages (page 2 of 2) Event Number and Symbolic Name Description 18: ZNSC-EVT-FILE-SYNCBLOCK-ERR An attempt to retrieve file synchronization information failed. 19: ZNSC-EVT-NOWAIT-DEPTH-ERR The opener process has too many pending requests active against the reporting process. 20: ZNSC-EVT-MEMORY-LEAK-ERR A memory leak was detected.
PAGE 849
Common Definitions NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 850
NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Event Management Service (EMS) Standard Definitions Token Description ZSPI-TKN-SSID Contains ZNSC-VAL-SSID, the subsystem ID of NSC. ZSPI-SSN-ZNSC Subsystem number assigned to the NSC. Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for NSC events are listed in Table 18-3. EMS standard definitions are described in detail in the EMS Manual. Table 18-3.
PAGE 851
NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) NonStop Subsystem Manager (ZNSC-) Definitions Predefined Token and Field Values Token Description ZNSC-VAL-BUFLEN Recommended buffer length (in bytes) for all NSC event messages ZNSC-VAL-SSID Subsystem ID of the NSC—the structure is shown under the description for ZSPI-TKN-SSID ZNSC-VAL-VERSION Version number of the NSC Simple Tokens and Structured Tokens Token Description ZNSC-TKN-PROC-NAME Subject token that specifies the process
PAGE 852
NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Description of ZNSC Event Messages Description of ZNSC Event Messages The NSC event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZNSC-EVT-name, where name describes the event that generated the message.
PAGE 853
NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC)  Recovery Action Requiring Vendor Support A box contains the list of tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens. The tokens might not necessarily appear in the message buffer in the same order that they are listed in the box. The tokens in the list are either:   Unconditional (always present in the message).
PAGE 854
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSC-TKN-PROC-NAME ZNSC-TKN-RESULT ZNSC-TKN-FILE-ERROR ZNSC-TKN-ERROR-DETAIL token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-UINT ZSPI-TYP-INT2 ZSPI-TYP-UINT Event-Message Text Checkpoint failure. Checkpoint error code code, error detail: error-detail. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 855
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSC-TKN-PROC-NAME ZNSC-TKN-RESULT ZNSC-TKN-FILE-ERROR token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-UINT ZSPI-TYP-INT2 Event-Message Text Backup has taken over processing from the primary process, checkpoint error code code, error detail error-detail Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 856
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Event-Message Text Process ownership switch occurred. Primary process is now executing in processor cpu Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVTSWITCH (3). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC.
PAGE 857
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVTCHKOPEN-ERR (4). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-FILE-NAME Name of the file or process that could not be checkopened. ZNSC-TKN-FILE-ERROR File error information returned from the FILE_OPEN_ CHKPT_ procedure.
PAGE 858
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Cause. NSC’s retry limit for backup creation was exceeded. This could be because of a logical error in the process or it could be because of a problem in the process’s environment (either the primary or backup processor repeatedly going down and then coming up). Effect. The process using NSC continues to run, but without a backup process. The process is no longer fault-tolerant. Recovery.
PAGE 859
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Token Description (page 2 of 2) ZNSC-TKN-FILE-ERROR File error returned from the PROCESS_LAUNCH_ procedure. ZNSC-TKN-ERROR-DETAIL Error detail information returned from the PROCESS_LAUNCH_ procedure. Cause. An error was returned from the PROCESS_LAUNCH_ procedure, so NSC was unable to create a backup process.
PAGE 860
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVT-BKPCREATED (7). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-CPU Processor number of the processor where the backup process was created. Cause. NSC successfully created a backup process. Effect. The backup process is running. Recovery.
PAGE 861
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Cause. An error occurred during a checkpointing of the global data, causing NSC to fail to complete the initial checkpoint to a backup process. Effect. NSC stops the backup process, then restarts it 10 seconds later. Recovery. If the problem persists, see Recovery Action Requiring Vendor Support on page 18-7. 9: ZNSC-EVT-BKP-LOST A backup process was terminated.
PAGE 862
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) 10: ZNSC-EVT-BKP-LOST-FATAL The NSC backup process stopped for an unknown reason.
PAGE 863
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSC-TKN-PROC-NAME ZNSC-TKN-FILE-ERROR token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-TYP-INT2 Event-Message Text REPLYX to $RECEIVE failed, error error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVTRECEIVE-REPLY-ERR (11).
PAGE 864
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Event-Message Text Attempt to create subordinate process for tasks task-name failed. Error error, error detail error-detail. Programfile: file-name Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVTPROC-CREATE-ERR (12). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC.
PAGE 865
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Event-Message Text Failed to start task task-name, ancestor task-ancst Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVT-TASKSTART-ERR (13). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-TASK-NAME Name of the task that is trying to create the subordinate process. ZNSC-TKN-TASK-ANCST Ancestor task. Cause.
PAGE 866
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVT-TASKKILLED (14). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-TASK-NAME Name of the task that terminated abnormally. ZNSC-TKN-TASK-RESULT Error associated with the task termination. Cause.
PAGE 867
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Cause. One of the process’s tasks has stopped, and its ancestor task cannot be found. Effect. Data that might have been intended for the ancestor is lost. The process using NSC continues normally. Recovery. If the problem persists, restart the reporting process, for example $ZPM, $ZZSTO, or $ZDMP. If the problem persists after restarting the process, see Recovery Action Requiring Vendor Support on page 18-7.
PAGE 868
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) 17: ZNSC-EVT-TASK-FUNC-MISSING A task function pointer could not be resolved because the function was missing.
PAGE 869
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) 18: ZNSC-EVT-FILE-SYNCBLOCK-ERR An attempt to retrieve file synchronization information failed.
PAGE 870
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) 19: ZNSC-EVT-NOWAIT-DEPTH-ERR The opener process has too many pending requests active against the reporting process.
PAGE 871
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) 20: ZNSC-EVT-MEMORY-LEAK-ERR A memory leak was detected.
PAGE 872
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) 21: ZNSC-EVT-MEMORY-POOL-ERR The internal memory pool was invalid.
PAGE 873
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSC-TKN-PROC-NAME ZNSC-TKN-PROC-DESC ZNSC-TKN-RESULT ZNSC-TKN-TEXT token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-PHANDLE ZSPI-TYP-UINT ZSPI-TYP-STRING Event-Message Text Subordinate process proc-desc. Termination text: text Completion code: code Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 874
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSC-TKN-PROC-NAME ZNSC-TKN-SERV-NAME ZNSC-TKN-TASK-NAME ZNSC-TKN-FUNC-NAME ZNSC-TKN-RESULT token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-UINT Event-Message Text Error communication with server serv-name. Task task-name, function: func-name.
PAGE 875
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSC-TKN-PROC-NAME ZNSC-TKN-SERV-NAME ZNSC-TKN-TASK-NAME ZNSC-TKN-FUNC-NAME token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text Too many errors communication with server serv-name. Task task-name, function: func-name.
PAGE 876
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZNSC-TKN-PROC-NAME ZNSC-TKN-PROC-DESC token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-TYP-PHANDLE Event-Message Text Unable to establish owning task for process proc-desc. Process is abended Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVTPROC-OWNER-ERR (25).
PAGE 877
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Event-Message Text No owning task for completion on file-name, error file-error. File is closed. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVT-FILESTATE-ERROR (26). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-FILE-NAME Name of the opened file.
PAGE 878
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVT-OHTASK-ERROR (27). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-TASK-NAME Name of the openhandler task. ZNSC-TKN-FILE-ERROR Error information returned from the subordinate task. ZNSC-TKN-ERROR-DETAIL Error detail from the subordinate task. Cause.
PAGE 879
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVTBOUNDARY-FATAL (28). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-ADDRESS Address of the failed boundary tag. ZNSC-TKN-TASK-NAME Name of the active task when the error occurred. Cause. An internal boundary tag is invalid. Effect. The primary process fails.
PAGE 880
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVTEYECATCHER-FATAL (29). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-ADDRESS Address of the invalid eyecatcher value. ZNSC-TKN-TASK-NAME Name of the active task where the error occurred. ZNSC-TKN-EYECATCHER Expected eyecatcher value.
PAGE 881
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVT-USRCHECKPOINT (30). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-ADDRESS Address of the user-defined checkpoint area. ZNSC-TKN-SIZE Size of the user-defined checkpoint area. ZNSC-TKN-TASK-NAME Name of the active task.
PAGE 882
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZNSC-EVT-USRFREESTATE (31). ZNSC-TKN-PROC-NAME Subject token that specifies the process name of the process using NSC. ZNSC-TKN-ADDRESS Address of the buffer that the task attempted to free. ZNSC-TKN-TASK-NAME Name of the task that attempted to free the buffer. Cause.
PAGE 883
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Token Description (page 2 of 2) ZNSC-TKN-ADDRESS Address of the buffer that the task attempted to free. ZNSC-TKN-TASK-NAME Name of the task that attempted to free the buffer. Cause. A task attempted to free a buffer that it did not own. Effect. The buffer is not freed. Recovery. If the problem persists, see Recovery Action Requiring Vendor Support on page 18-7. 33: ZNSC-EVT-TRACE-ERROR Tracing failed to start.
PAGE 884
Messages NonStop C-Base Multitasking Engine (NSC) Event Messages (ZNSC) Effect. Tracing fails to start. If tracing has started, it stops. Recovery. Restart the reporting process. If the problem persists, this suggests a logical error in the process rather than a lack of resources. In this case, see Recovery Action Requiring Vendor Support on page 18-7. 34: ZNSC-EVT-SMSG-MISSED The process missed system messages.
PAGE 885
19 ServerNet Error Handler Event Messages (ZSNT) The ServerNet error handler event messages are reported to the EMS by processes servicing the ServerNet generic error handler (GenErr). Table 19-1. ServerNet Error Handler Event Messages (page 1 of 5) Event Number and Symbolic Name Description 1000: ZSNT-EVT-RCV-UGLY-ERRORS Badly formatted packets were detected on a ServerNet link. 1001: ZSNT-EVT-TPB-ERRORS Packets with this packet bad (TPB) tag were detected on a ServerNet link.
PAGE 886
ServerNet Error Handler Event Messages (ZSNT) Table 19-1. ServerNet Error Handler Event Messages (page 2 of 5) Event Number and Symbolic Name Description 1013: ZSNT-EVT-OVRUN-TPB-ERRORS Packets with an overrun error and the TPB tag were detected on a ServerNet link. 1014: ZSNT-EVT-OVRUN-CRC-ERRORS Packets with an overrun error and a CRC error were detected on a ServerNet link.
PAGE 887
ServerNet Error Handler Event Messages (ZSNT) Table 19-1. ServerNet Error Handler Event Messages (page 3 of 5) Event Number and Symbolic Name Description 1028: ZSNT-EVT-BABBLE-ERRORS A source of ServerNet interrupt packets was generating too many interrupt packets on a ServerNet link. 1029: ZSNT-EVT-NO-DEVICE-INT-ERRORS Interrupt packets were detected when the corresponding software subsystem was deinstalled.
PAGE 888
ServerNet Error Handler Event Messages (ZSNT) Table 19-1. ServerNet Error Handler Event Messages (page 4 of 5) Event Number and Symbolic Name Description 1043: ZSNT-EVT-SNET-INFO ServerNet software sent an informational event to the event log. 1044: ZSNT-EVT-LINK-UP ServerNet “link up” condition occurred and the link can be used for communications. 1045: ZSNT-EVT-UNDEFINED-ASIC ServerNet software received an undefined interrupt from lower-level software.
PAGE 889
Common Definitions ServerNet Error Handler Event Messages (ZSNT) Table 19-1. ServerNet Error Handler Event Messages (page 5 of 5) Event Number and Symbolic Name Description 1058: ZSNT-EVT-INTF-MESSAGE Either an interface error occurred between the ServerNet software and the event-generating software, or an internal error occurred during ServerNet event generation. 1059: ZSNT-EVT-SINGLE-SYMBOL ServerNet Hardware detected the transmission of a Single Symbol.
PAGE 890
ServerNet Error Handler Event Messages (ZSNT) SPI (ZSPI-)Standard Definitions SPI (ZSPI-)Standard Definitions SPI standard definitions that have a specific meaning for ServerNet error handler events are listed in Table 19-2. SPI standard definitions are described in detail in the SPI Programming Manual. Table 19-2.
PAGE 891
ServerNet Error Handler Event Messages (ZSNT) Event Management Service (EMS) Standard Definitions Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for ServerNet error handler events are listed in Table 19-3. EMS standard definitions are described in detail in the EMS Manual. Table 19-3.
PAGE 892
Description of ZSNT Event Messages ServerNet Error Handler Event Messages (ZSNT) Private Token and Field Types Token Type Description ZSNT-TYP-FABRIC Token type for ZSNT-TKN-FABRIC-NUMBER, which indicates a fabric where an error occurred, as follows. Value of ZSNT-TKN-FABRIC-NUMBER Fabric Where Error Occurred 0 X 1 Y Token Type Description ZSNT-TYP-DOWN-REASON Token type for ZSNT-TKN-DOWN-REASON, which provides the reason that caused a fabric to be down.
PAGE 893
ServerNet Error Handler Event Messages (ZSNT) Information in Event Description Messages Information in Event Description Messages Each description contains the following information:   A header showing the numeric value and symbolic name for the event number. A paragraph describing the event message.
PAGE 894
ServerNet Error Handler Event Messages (ZSNT) Recovery Action Requiring Vendor Support Recovery Action Requiring Vendor Support Contact your service provider or the Global Mission Critical Solution Center (GMCSC), as directed by your local operating procedures.
PAGE 895
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTRCV-UGLY-ERRORS (1000). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the TPB error. ZSNT-TKN-RCV-UGLY-ERROR Number of RCV Ugly errors encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 896
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: TPB Packet Errors errors Occurred on Fabric fabricnumber [ Source-ID: 0xsource-id, Dest-ID: 0xdest-id, ServerNet Address: 0xservernet-addr ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVT-TPBERRORS (1001).
PAGE 897
Messages ServerNet Error Handler Event Messages (ZSNT) 1002: ZSNT-EVT-CRC-ERRORS Packets with a CRC error were detected on a ServerNet link.
PAGE 898
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause. Packets with CRC error were detected. Effect.
PAGE 899
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVT-TPBCRC-ERRORS (1003). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error. ZSNT-TKN-TPB-CRC-ERRORS Number of TPB with CRC error that were encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 900
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Underrun Errors errors Occurred on Fabric fabric-number [ Source-ID: 0xsource-id, Dest-ID: 0xdest-id, ServerNet Address: 0xservernet-addr ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTUNDRUN-ERRORS (1004).
PAGE 901
Messages ServerNet Error Handler Event Messages (ZSNT) 1005: ZSNT-EVT-UNDRUN-TPB-ERRORS Packets with an underrun and the TPB tag were detected on a ServerNet link.
PAGE 902
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause.
PAGE 903
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNTEVT-UNDRUN-CRC-ERRORS (1006). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error. ZSNT-TKN-UNDRUN-CRC-ERRORS Number of underrun with CRC errors that were encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 904
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Underrun with TPB with CRC Errors errors Occurred on Fabric fabric-number [ Source-ID: 0xsource-id, Dest-ID: 0xdest-id, ServerNet Address: 0xservernet-addr ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 905
Messages ServerNet Error Handler Event Messages (ZSNT) 1008: ZSNT-EVT-RUNT-ERRORS Runt packets were detected on a ServerNet link.
PAGE 906
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause. Runt packets were detected. Effect.
PAGE 907
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTRUNT-TPB-ERRORS (1009). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error. ZSNT-TKN-RUNT-TPB-ERRORS Number of runt packets with TPB encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 908
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Runt Packet with CRC Errors errors Occurred on Fabric fabric-number [ Source-ID: 0xsource-id, Dest-ID: 0xdest-id, ServerNet Address: 0xservernet-addr ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 909
Messages ServerNet Error Handler Event Messages (ZSNT) 1011: ZSNT-EVT-RUNT-TPB-CRC-ERRORS Runt packets with the TPB tag and a CRC error were detected on a ServerNet link.
PAGE 910
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause.
PAGE 911
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTOVRUN-ERRORS (1012). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error. ZSNT-TKN-OVRUN-ERRORS Number of the overrun errors encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 912
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Overrun Packet with TPB Errors errors Occurred on Fabric fabric-number [ Source-ID: 0xsource-id, Dest-ID: 0xdest-id, ServerNet Address: 0xservernet-addr ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 913
Messages ServerNet Error Handler Event Messages (ZSNT) 1014: ZSNT-EVT-OVRUN-CRC-ERRORS Packets with an overrun error and a CRC error were detected on a ServerNet link.
PAGE 914
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause.
PAGE 915
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNTEVT-OVRUN-TPB-CRC-ERRORS (1015). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error. ZSNT-TKN-OVRUN-TPB-CRC-ERRORS Number of overrun with TPB and CRC errors encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 916
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Unsupported Packet Type Errors errors Occurred on Fabric fabric-number [ Source-ID: 0xsource-id, Dest-ID: 0xdest-id, ServerNet Address: 0xservernet-addr ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 917
Messages ServerNet Error Handler Event Messages (ZSNT) 1017: ZSNT-EVT-UNSUPP-LEN-ERRORS Packets with an unsupported length were detected on a ServerNet link.
PAGE 918
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause.
PAGE 919
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVT-BADDID-ERRORS (1018). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error encountered. ZSNT-TKN-BAD-DID-ERRORS Number of packets with bad destination node ID errors encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 920
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Bad SrcIdBad Errors errors Occurred on Fabric fabric-number Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNTEVT-BAD-SRCIBAD-ERRORS (1019).
PAGE 921
Messages ServerNet Error Handler Event Messages (ZSNT) 1020: ZSNT-EVT-BAD-RDREQOVFLO-ERRORS Packets with a bad request overflow error were detected on a ServerNet link.
PAGE 922
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause.
PAGE 923
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNTEVT-SPURIOUS-ACK-ERRORS (1021). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error. ZSNT-TKN-SPURIOUS-ACK-ERRORS Number of unexpected ServerNet acknowledgment packets encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 924
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSNT-TKN-CPU-NUMBER ZSNT-TKN-BAD-MASK-ERRORS ZSNT-TKN-FABRIC-NUMBER token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-INT2 ZSNT-TYP-FABRIC Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Bad Mask Errors errors Occurred on Fabric fabric-number Uncond
PAGE 925
Messages ServerNet Error Handler Event Messages (ZSNT) 1023: ZSNT-EVT-BAD-PATH-ERRORS Packets that failed the path bit address validation and translation (AVT) check were detected on a ServerNet link.
PAGE 926
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause.
PAGE 927
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNTEVT-BAD-SOURCE-ERRORS (1024). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error. ZSNT-TKN-BAD-SOURCE-ERRORS Number of packets that failed the AVT source node check. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y).
PAGE 928
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID ZSNT-TKN-TNET-ADDR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Bad Access Errors errors Occurred on Fabric fabric-number Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTACCESS-ERRORS (1025).
PAGE 929
Messages ServerNet Error Handler Event Messages (ZSNT) 1026: ZSNT-EVT-BAD-INTERRUPT-ERRORS Packets that failed the interrupt address validation and translation (AVT) check were detected on a ServerNet link.
PAGE 930
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens Token Description ZSNT-TKN-SOURCE-ID ServerNet identifier of the adaptor or processor that sent the packet. ZSNT-TKN-DEST-ID ServerNet identifier of the adaptor or processor that was to receive the packet ZSNT-TKN-TNET-ADDR ServerNet address where the received packet was directed. This could be an interrupt address or a location from which data was to be written or read. Cause.
PAGE 931
ServerNet Error Handler Event Messages (ZSNT) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTINTQ-FULL-ERRORS (1027). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor \that encountered the error. ZSNT-TKN-INTQ-FULL-ERRORS Number of packets that were dropped because the interrupt queue was full. ZSNT-TKN-FABRIC-NUMBER Fabric where the interrupt occurred (0 for X, 1 for Y).
PAGE 932
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSNT-TKN-CPU-NUMBER ZSNT-TKN-BABBLE-ERRORS ZSNT-TKN-FABRIC-NUMBER token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-INT2 ZSNT-TYP-FABRIC Event-Message Text CPU cpu: Babbling Source Detected Errors errors Occurred on Fabric fabric-number Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTBABBLE-ERRORS (1028).
PAGE 933
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSNT-TKN-CPU-NUMBER ZSNT-TKN-NO-DEVICE-INT-ERRORS ZSNT-TKN-FABRIC-NUMBER token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-INT2 ZSNT-TYP-FABRIC Event-Message Text CPU cpu: Interrupt With No Device Errors errors Occurred on Fabric fabric-number Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 934
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSNT-TKN-CPU-NUMBER ZSNT-TKN-EXC-QUEUE-ERRORS token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT token-type ZSPI-TYP-INT2 Conditional Tokens (G-Series Only) ZSNT-TKN-CAUSE-REG ZSNT-TKN-LINK-XCEPT-X ZSNT-TKN-LINK-XCEPT-Y token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text CPU cpu: Exception Errors errors Occurred [ Cause Reg: 0xcause-reg, Link Exception X: 0xlink-xcept
PAGE 935
Messages ServerNet Error Handler Event Messages (ZSNT) 1031: ZSNT-EVT-WRITE-OVERFLOW-ERRORS At least one write request response was lost because all the write response buffer space was exhausted.
PAGE 936
Messages ServerNet Error Handler Event Messages (ZSNT) Cause. The write response buffer was exhausted, and at least one write request response was lost. Effect. These interrupts are counted, and if too many such interrupts occur, the processor halts. Recovery. This is an informational message only; no corrective action is needed. 1032: ZSNT-EVT-READ-OVERFLOW-ERRORS The receiver read request buffer received more than the maximum allowed number of read request packets.
PAGE 937
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens (G-Series Only) Token Description ZSNT-TKN-CAUSE-REG Interrupt Cause Register at the time of the exception. ZSNT-TKN-LINK-XCEPT-X Port X Link Exception Register. ZSNT-TKN-LINK-XCEPT-Y Port Y Link Exception Register. Cause. The receiver read request buffer received more than the maximum allowed number of read request packets. Effect. These interrupts are counted, and if too many such interrupts occur, the processor halts.
PAGE 938
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTQUEUE-FULL-ERRORS (1033). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error. ZSNT-TKN-QUEUE-FULL-ERRORS Number of times the queue-full error occurred. Conditional Tokens (G-Series Only) Token Description ZSNT-TKN-CAUSE-REG Interrupt Cause Register at the time of the exception.
PAGE 939
Messages ServerNet Error Handler Event Messages (ZSNT) Event-Message Text CPU cpu: Link Exception Errors errors occurred on the X fabric. [ Cause Reg: 0xcause-reg, Link Exception X: 0xlink-xcept-x, Link Exception Y: 0xlink-xcept-y ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNTEVT-LINK-EXCEPT-X-ERRORS (1034). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor that encountered the error.
PAGE 940
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Tokens ZSNT-TKN-CAUSE-REG ZSNT-TKN-LINK-XCEPT-X ZSNT-TKN-LINK-XCEPT-Y token-type ZSPI-TYP-INT2 (G-series) token-type ZSPI-TYP-INT2 (G-series) token-type ZSPI-TYP-INT2 (G-series) Event-Message Text CPU cpu: Link Exception Errors errors occurred on the Y fabric.
PAGE 941
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSNT-TKN-CPU-NUMBER ZSNT-TKN-FABRIC-NUMBER ZSNT-TKN-DOWN-REASON token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-INT ZSNT-TYP-FABRIC ZSNT-TYP-DOWN-REASON Event-Message Text CPU cpu: Fabric fabric-number Down Due to Reason down-reason Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTFABRIC-DOWN (1036).
PAGE 942
Messages ServerNet Error Handler Event Messages (ZSNT) Event-Message Text CPU cpu: Packet abnormal end Errors pkt-abnormal-end Occurred on Fabric fabric-number Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNTEVT-AVT-PKT-ABNORMAL-END (1037). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor number that encountered the TPB error. ZSNT-TKN-AVT-PKT-ABNORMAL-END Number of abnormal end error encountered.
PAGE 943
Messages ServerNet Error Handler Event Messages (ZSNT) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNTEVT-NATMWRT-DURING-SLEEP (1038). ZSNT-TKN-CPU-NUMBER Subject token that specifies the processor number that encountered the TPB error. ZSNT-TKN-NATMWRT-DURING-SLEEP Number of nonatomic packets received during sleep mode that were encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y). Cause.
PAGE 944
Messages ServerNet Error Handler Event Messages (ZSNT) Token Description (page 2 of 2) ZSNT-TKN-AVT-UNKNOWN Number of unknown errors encountered. ZSNT-TKN-FABRIC-NUMBER Fabric where the error occurred (0 for X, 1 for Y). Cause. The processor has detected badly formatted packets on a ServerNet link. Effect. The packets are dropped, and an internal error handler takes care of the dropped packets. Recovery. This is an informational message only; no corrective action is needed.
PAGE 945
Messages ServerNet Error Handler Event Messages (ZSNT) Recovery. This is an informational message only; no corrective action is needed. The client might retry the operation. 1041: ZSNT-EVT-FABRIC-UP A ServerNet link that was previously marked down has been marked up.
PAGE 946
Messages ServerNet Error Handler Event Messages (ZSNT) 1042: ZSNT-EVT-CONGESTION-RECOVERY ServerNet software detected a timeout condition that might indicate ServerNet fabric congestion, and is performing recovery actions.
PAGE 947
Messages ServerNet Error Handler Event Messages (ZSNT) Cause. Congestion or back pressure has been detected, and ServerNet software is performing recovery procedures. Effect. The packet that timed out is not delivered, but higher-level software must tolerate this condition and recover from it. If the cause of the timeout was transient, the ServerNet software will be able to clear the error state and continue.
PAGE 948
Messages ServerNet Error Handler Event Messages (ZSNT) 1044: ZSNT-EVT-LINK-UP ServerNet “link up” condition occurred and the link can be used for communications.
PAGE 949
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Token Token Description ZSNT-TKN-PORT-INFO Uses the ZSNT-DDL-PORT-INFO structure definition (see Figure 19-2). Fields contain hardware register and status information. Up to two of these structures can be associated with the event. Figure 19-2. ZSNT-DDL-PORT-INFO Structure Definition DEF zsnt-ddl-port-info. 02 version 02 lp-status 02 zfiller1 02 02 02 02 02 02 02 02 02 02 END.
PAGE 950
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Token ZSNT-TKN-UNDEF-ASIC-DATA token-type ZSPI-TDT-STRUCT Event-Message Text Processor cpunum: reported.
PAGE 951
Messages ServerNet Error Handler Event Messages (ZSNT) 1046: ZSNT-EVT-MINOR-PORT-ERR ServerNet hardware reported a minor error on a data port..
PAGE 952
Messages ServerNet Error Handler Event Messages (ZSNT) Token Description (page 2 of 2) ZSNT-TKN-MINOR-PORT-ERR Number of errors of this type detected by ServerNet since the last event of this type was generated. This is the number of minor port error interrupts handled. For the actual number of minor port errors seen by hardware, compare the values of this token for the first and last minor port errors.
PAGE 953
Messages ServerNet Error Handler Event Messages (ZSNT) Event-Message Text Processor cpunum: on port fabric. count Transmit FILL error(s) have occurred [ Additional info at the time of the first error: LLP Status: status Transmit Buffer Watermark: watermark ] [ Additional info at the time of the last error: LLP Status: status Transmit Buffer Watermark: watermark ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVT-LLPFILL (1047).
PAGE 954
Messages ServerNet Error Handler Event Messages (ZSNT) Recovery. This is an informational message only; no corrective action is needed. 1048: ZSNT-EVT-LLP-RUNON ServerNet hardware is transmitting excessive data symbols within the data stream.
PAGE 955
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Token Token Description ZSNT-TKN-XFER-PKT-LAYER Uses the ZSNT-DDL-XFER-PKT-LAYER structure definition (see Figure 19-3 on page 19-69). There can be up to two of these structures associated with the event. Cause. ServerNet hardware is transmitting too many symbols in the data stream without sending an end-of-packet indicator. Effect. The receiver of the data stream might report a minor port error.
PAGE 956
ServerNet Error Handler Event Messages (ZSNT) Messages Event-Message Text Processor cpunum: occurred.
PAGE 957
Messages ServerNet Error Handler Event Messages (ZSNT) 1050: ZSNT-EVT-LOLA ServerNet hardware generated an exception indicating that a link lost connectivity.
PAGE 958
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Token Token Description ZSNT-TKN-MAJOR-PORT Uses the ZSNT-DDL-MAJOR-PORT structure definition, which holds various hardware register and status values. There can be up to two of these structures associated with the event. Cause. ServerNet hardware detected that one of the transmission links has become inoperative. Effect. Data cannot be transmitted on the specified port until the link is recovered. Recovery.
PAGE 959
ServerNet Error Handler Event Messages (ZSNT) Messages Event-Message Text Processor cpunum: Excessive Minor Port errors have caused a major error on port fabric. [ Additional info at the time of the first event: LLP Status: status SNet Config Reg: configreg Link Event: eventreg ] [ Additional info at the time of the last event: LLP Status: status SNet Config Reg: configreg Link Event: eventreg ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 960
Messages ServerNet Error Handler Event Messages (ZSNT) 1052: ZSNT-EVT-OFP-THRESH ServerNet hardware cannot achieve satisfactory progress when transmitting data on the specified port.
PAGE 961
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Token Token Description ZSNT-TKN-MAJOR-PORT Uses the ZSNT-DDL-MAJOR-PORT structure definition, which holds various hardware register and status values. There can be up to two of these structures associated with the event. Cause. ServerNet hardware cannot achieve satisfactory progress when transmitting data on the specified port. The reason might be congestion in the fabric. Effect. The packet being transmitted is truncated.
PAGE 962
ServerNet Error Handler Event Messages (ZSNT) Messages Event-Message Text Processor cpunum: fabric. Inbound Forward Progress error on port [ Additional info at the time of the first event: LLP Status: status SNet Config Reg: configreg Link Event: eventreg ] [ Additional info at the time of the last event: LLP Status: status SNet Config Reg: configreg Link Event: eventreg ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVT-IFPTHRESH (1053).
PAGE 963
Messages ServerNet Error Handler Event Messages (ZSNT) 1054: ZSNT-EVT-LLP-SELFCHECK ServerNet hardware reported a SelfCheck condition.
PAGE 964
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Token Token Description ZSNT-TKN-MAJOR-PORT Uses the ZSNT-DDL-MAJOR-PORT structure definition, which holds various hardware register and status values. There can be up to two of these structures associated with the event. Cause. ServerNet hardware reported a SelfCheck condition in its link portion. Effect. The port is down. Incoming data is discarded. Outgoing data is truncated.
PAGE 965
ServerNet Error Handler Event Messages (ZSNT) Messages Event-Message Text Processor cpunum: count Packet Toss errors have occurred.
PAGE 966
Messages ServerNet Error Handler Event Messages (ZSNT) 1056: ZSNT-EVT-CONGESTION-NACK ServerNet routers detected severe congestion..
PAGE 967
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Token Token Description ZSNT-TKN-CONGEST-DATA Uses the ZSNT-DDL-CONGEST-DATA structure definition, which contains the NACK data and the affected ServerNet IDs. There can be up to two of these structures associated with the event. Cause. A ServerNet router detected a minor congestion condition. The ServerNet node is not necessarily the cause of the congestion. Effect. Possible delay in packet routing.
PAGE 968
ServerNet Error Handler Event Messages (ZSNT) Messages Event-Message Text Processor cpunum: port fabric. count Congestion Link Down NACKs seen on [ Additional info at the time of the first event: Nack Data: data Source ID: srcid Destination ID: destid ] [ Additional info at the time of the last event: Nack Data: data Source ID: srcid Destination ID: destid ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTLINKDOWN-NACK (1057).
PAGE 969
Messages ServerNet Error Handler Event Messages (ZSNT) 1058: ZSNT-EVT-INTF-MESSAGE Either an interface error occurred between the ServerNet software and the eventgenerating software, or an internal error occurred during ServerNet event generation.
PAGE 970
Messages ServerNet Error Handler Event Messages (ZSNT) Cause. ServerNet error-logging software detected either an interface error or an internal error. Effect. An expected event might not generate properly. Recovery. This is an informational message only; no corrective action is needed. 1059: ZSNT-EVT-SINGLE-SYMBOL ServerNet Hardware detected the transmission of a Single Symbol.
PAGE 971
Messages ServerNet Error Handler Event Messages (ZSNT) Effect. The symbol was transmitted. This is usually benign, but might cause ServerNet anomalies. Recovery. This is an informational message only; no corrective action is needed. 1060: ZSNT-EVT-IBC-RECEIVED ServerNet Hardware received an old-style in-bound control (IBC) symbol..
PAGE 972
Messages ServerNet Error Handler Event Messages (ZSNT) 1061: ZSNT-EVT-SPURIOUS-EXCEPTION ServerNet software detected a spurious exception condition..
PAGE 973
Messages ServerNet Error Handler Event Messages (ZSNT) Token Description (page 2 of 2) ZSNT-TKN-COL-CAUSEREG Contents of cause register. ZSNT-TKN-HW-EXCEPTION-REG Contents of hardware exception register. Conditional Token Token Description ZSNT-TKN-LP-INT-SRC Contents of interrupt source register. Present only for spurious major and minor exceptions. Cause. ServerNet software determined that an exception condition was spurious because additional exception data was either missing or inconsistent.
PAGE 974
Messages ServerNet Error Handler Event Messages (ZSNT) Conditional Token ZSNT-TKN-SOURCE-ID ZSNT-TKN-DEST-ID token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text Processor cpunum: errors soft memory error(s) detected in ServerNet data transfers. Transfering xferlen bytes. [Source-ID: source-id] Dest-ID: destination-id ]] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSNT-EVTDATAPATH-SOFTERROR (1063).
PAGE 975
Messages ServerNet Error Handler Event Messages (ZSNT) 1064: ZSNT-EVT-CAPACITY-NOTIFICATION ServerNet software has received a notification that the ServerNet hardware is nearing its capacity.
PAGE 976
ServerNet Error Handler Event Messages (ZSNT) Messages Cause. Hardware has notified ServerNet that it is approaching its capacity and is taking action to alleviate that condition. Effect. The alleviation mechanism may cause some data flowing through the fabric to be truncated or returned to the sender. ServerNet and upper-level software will resend the data. Recovery. This is an informational message only; no corrective action is needed.
PAGE 977
20 SCSI Module Driver Event Messages (ZSMD) The SMD subsystem returns syndrome codes to the input/output processes (IOPs) (disk, tape, and so on) that communicate with SCSI devices. The IOPs, in turn, generate SCSI common events. The SMD event messages are reported to the EMS service event logger ($ZLOG). These messages are viewable using the OSM Event Viewer or the TSM EMS Event Viewer Application. SCSI module driver event messages are reported to the EMS by the DP2 Driver. Table 20-1.
PAGE 978
SCSI Module Driver Event Messages (ZSMD) Table 20-1. SCSI Module Driver Event Messages (page 2 of 3) Event Number and Symbolic Name Description 133: ZSMD-EVT-SVNET-CTLR-HAD-ERR A host access disable (HAD) error has been detected by a processor that accesses the controller. 134: ZSMD-EVT-SVNET-PATH-DOWN A ServerNet path from the processor to the controller has been brought down by the ServerNet Services.
PAGE 979
Common Definitions SCSI Module Driver Event Messages (ZSMD) Table 20-1. SCSI Module Driver Event Messages (page 3 of 3) Event Number and Symbolic Name Description 304: ZSMD-EVT-CTLR-INTF-ERR A controller interface error occurred. 305: ZSMD-EVT-CTLR-MB-STATUS-ERR The controller mailbox status error occurred. 306: ZSMD-EVT-CTLR-MB-INTR-ERR The controller sent a mailbox interrupt error. 307: ZSMD-EVT-CTLR-ASYNC-INTR The controller sent an asynchronous interrupt.
PAGE 980
SCSI Module Driver Event Messages (ZSMD)   Subsystem Programmatic Interface (SPI) Standard Definitions Event Management Service (EMS) Standard Definitions on page 20-5 SCSI Module Driver (ZSMD-) Definitions on page 20-5 A general description of these definitions is provided in the following paragraphs. Note. The event-message header tokens are described in Section 2, Header and Common Tokens. Note. All definitions are shown in DDL format using hyphens (-) as separators.
PAGE 981
Event Management Service (EMS) Standard Definitions SCSI Module Driver Event Messages (ZSMD) Token Description ZSPI-TKN-SSID Contains ZSMD-VAL-SSID, the subsystem ID of the SCSI module driver. ZSPI-SSN-ZSMD Subsystem number assigned to the SCSI module driver. Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for ServerNet error handler events are listed in Table 20-3. EMS standard definitions are described in detail in the EMS Manual.
PAGE 982
SCSI Module Driver (ZSMD-) Definitions SCSI Module Driver Event Messages (ZSMD)    Private Token and Field Types on page 20-7 Predefined Token and Field Values on page 20-10 Simple Tokens and Structured Tokens on page 20-10 Additional Status Tokens The following SCSI module driver tokens are additional status tokens that provide information about the event for development. Each event might have one of these tokens.
PAGE 983
SCSI Module Driver (ZSMD-) Definitions SCSI Module Driver Event Messages (ZSMD) Private Token and Field Types Token Description ZSMD-DDL-AST Generic additional status token from the module driver (see Figure 20-2). ZSMD-DDL-AST-COMMAND SPI command status token that you must use for SCSI module driver event messages (see Figure 20-3 on page 20-8). ZSMD-DDL-AST-XFER SPI ServerNet transfer status token that you must use for SCSI module driver event messages (see Figure 20-4 on page 20-8).
PAGE 984
SCSI Module Driver (ZSMD-) Definitions SCSI Module Driver Event Messages (ZSMD) Figure 20-3. ZSMD-DDL-AST-COMMAND Definition def ZSMD-DDL-AST-COMMAND. 02 Z-TYPE 02 Z-RESERVE0 02 Z-MDCODE 02 Z-FUNCTION 02 Z-FIELDCODE 02 Z-CTLRSTATE 02 Z-CTLRSTATEREASON 02 Z-FIELDCONTENT 02 Z-RESERVE2 end. type type type type type type type type type ZSPI-DDL-BYTE ZSPI-DDL-CHAR ZSPI-DDL-UINT ZSPI-DDL-CHAR ZSPI-DDL-BYTE ZSPI-DDL-BYTE ZSPI-DDL-BYTE character 8 character 16 Figure 20-4.
PAGE 985
SCSI Module Driver (ZSMD-) Definitions SCSI Module Driver Event Messages (ZSMD) Figure 20-6. ZSMD-DDL-AST-ISP-STAT Definition def ZSMD-DDL-AST-ISP-STAT. 02 Z-TYPE type 02 Z-RESERVE0 type 02 Z-MDCODE type 02 Z-PINFOPTR type 02 Z-HRDFLAGS type 02 Z-COMPLSTATUS type 02 Z-STATEFLAGS type 02 Z-STATUSFLAGS type 02 Z-SCSISTATUS type 02 Z-TIME type 02 Z-TAG type 02 Z-RESERVE1 type end.
PAGE 986
Description of ZSMD Event Messages SCSI Module Driver Event Messages (ZSMD) Figure 20-10. ZSMD-DDL-AST-ISP-UNKNOWN Definition def ZSMD-DDL-AST-ISP-TRACE. 02 Z-UNKNOWN end. type character 32 See the SPI Programming Manual for more information about the SPI status tokens.
PAGE 987
SCSI Module Driver Event Messages (ZSMD) Information in Event Description Messages Information in Event Description Messages Each description contains the following information:     A header showing the numeric value and symbolic name for the event number. A paragraph describing the event message. A list:   Identifying the subject of the event message.  Indicating whether the message identifies a potentially critical event (whether ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE).
PAGE 988
SCSI Module Driver Event Messages (ZSMD) Recovery Action Requiring Vendor Support Recovery Action Requiring Vendor Support Contact your service provider or the Global Mission Critical Solution Center (GMCSC), as directed by your local operating procedures.
PAGE 989
Messages SCSI Module Driver Event Messages (ZSMD) 65: ZSMD-EVT-MDR-FIELD-CONTENT-ERR Module Driver Request structure field content error occurred.
PAGE 990
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI Controller Lock Required Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-LOCK-RQD (67). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause.
PAGE 991
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVT-MDINTERNAL-ERR (96). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. SCSI module driver programming error has occurred. When present, the SCSI Additional Status Token will provide more information for development. Effect. The command cannot be completed. Recovery.
PAGE 992
Messages SCSI Module Driver Event Messages (ZSMD) Recovery. Check the version of both the SCSI module driver and SIFM. 98: ZSMD-EVT-MD-MB-SM-ERR Module Driver internal mailbox state machine error has occurred.
PAGE 993
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI MD Syndrome Unknown Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER. Event number for this message. Value is ZSMD-EVT-MDSYNDROME-UNKNOWN (103) ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. The SCSI module driver version might not match the IOP version.
PAGE 994
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTSVNET-SVC-INTF-ERR (128). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. A SCSI module driver programming error has occurred. When present, the SCSI Additional Status Token provides more information for development. Effect. The command cannot be completed. Recovery.
PAGE 995
Messages SCSI Module Driver Event Messages (ZSMD) Recovery. This is an informational message only; no corrective action is needed. The device input/output process (IOP) will retry the command. 130: ZSMD-EVT-SVNET-NO-AVT ServerNet Services reported that no access validation table (AVT) is available.
PAGE 996
Messages SCSI Module Driver Event Messages (ZSMD) 131: ZSMD-EVT-SVNET-CPU-RCV-ERR The processor’s ServerNet hardware has received a ServerNet packet error.
PAGE 997
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI ServerNet Controller Hardware Error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTSVNET-CTLR-HW-ERR (132). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause.
PAGE 998
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTSVNET-CTLR-HAD-ERR (133). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. The most probable cause is a ServerNet traffic or hardware error. Effect. The command cannot be completed. Recovery. This is an informational message only; no corrective action is needed.
PAGE 999
Messages SCSI Module Driver Event Messages (ZSMD) Recovery. The device input/output process (IOP) will retry the command with other paths. Check the ServerNet hardware. 135: ZSMD-EVT-SVNET-POWER-FAIL ServerNet transfers have been aborted by ServerNet Services.
PAGE 1000
Messages SCSI Module Driver Event Messages (ZSMD) 136: ZSMD-EVT-SVNET-BUF-INVALID An invalid memory access has led to an invalid ServerNet inbound transfer.
PAGE 1001
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI Device Selection Timeout Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVT-DEVSEL-TIMEOUT (192). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause.
PAGE 1002
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVT-DEVCMD-TIMEOUT (193). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. Either a device problem has occurred or an insufficient timeout has been set by the device input/output process (IOP). Effect. The command cannot be completed. Recovery.
PAGE 1003
Messages SCSI Module Driver Event Messages (ZSMD) Recovery. This is an informational message only; no corrective action is needed. The device input/output process (IOP) will retry the command. 195: ZSMD-EVT-DEV-BUSY The device is busy.
PAGE 1004
Messages SCSI Module Driver Event Messages (ZSMD) 196: ZSMD-EVT-DEV-SCSI-STATUS The device SCSI status was not expected.
PAGE 1005
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI Device Interface Error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVT-DEVINTF-ERR (197). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. A device, SCSI bus, or controller problem has occurred.
PAGE 1006
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVT-DEVRESET (198). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. The device hung the SCSI bus. Effect. The command cannot be completed. Recovery. This is an informational message only; no corrective action is needed. The device input/output process (IOP) will retry the command.
PAGE 1007
Messages SCSI Module Driver Event Messages (ZSMD) Recovery. This is an informational message only; no corrective action is needed. The device IOP will retry the command. 256: ZSMD-EVT-CTLR-DISABLED The controller was disabled.
PAGE 1008
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI Controller Acess Not Established Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-ACCESS-NOT-ESTB (257). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause.
PAGE 1009
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-UNLOADED (258). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. The controller possibly has lost power. Effect. None. Recovery. This is an informational message only; no corrective action is needed. The device input/output process (IOP) will download the controller.
PAGE 1010
Messages SCSI Module Driver Event Messages (ZSMD) Recovery. This is an informational message only; no corrective action is needed. 260: ZSMD-EVT-CTLR-QUEUE-ERROR The controller request queue is out of sync with the processor.
PAGE 1011
Messages SCSI Module Driver Event Messages (ZSMD) 261: ZSMD-EVT-CTLR-SHUT-DOWN The Module Driver shut down the controller because it generated too many ServerNet errors.
PAGE 1012
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI Bust Reset Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVT-SCSIBUS-RESET (288). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. The SCSI bus is hung. Effect.
PAGE 1013
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVT-SCSIBUS-RESET-IN (289). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. A controller has detected that the SCSI bus is hung. Effect. Commands to the devices on the SCSI bus have been aborted. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1014
Messages SCSI Module Driver Event Messages (ZSMD) 305: ZSMD-EVT-CTLR-MB-STATUS-ERR A controller mailbox status error occurred.
PAGE 1015
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI Controller MailBox Interrupt Error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-MB-INTR-ERR (306). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. A controller problem has occurred. Effect.
PAGE 1016
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-ASYNC-INTR (307). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. The controller has reset either a device or the SCSI bus. Effect. None. This is an indication of some other event. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1017
Messages SCSI Module Driver Event Messages (ZSMD) 309: ZSMD-EVT-CTLR-HW-ERR The controller had a hardware error.
PAGE 1018
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI Controller DMA Error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-DMA-ERR (310). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. A controller, device, or ServerNet hardware problem has occurred.
PAGE 1019
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-INTR-ERR (311). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. A controller problem has occurred. Effect. None. This might be an indication of some other problem. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1020
Messages SCSI Module Driver Event Messages (ZSMD) 313: ZSMD-EVT-CTLR-EXCESS-SVNET-ERR The controller caused too many ServerNet errors.
PAGE 1021
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEV token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text SCSI Controller Servernet Handle Error Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-SVNET-HNDL-ERR (314). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. A configuration error has occurred.
PAGE 1022
Messages SCSI Module Driver Event Messages (ZSMD) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSMD-EVTCTLR-FW-CHECK-ERR (315). ZEMS-TKN-LDEV Subject token that contains the logical device number of the affected disk drive. Cause. A firmware file error, controller memory error, or transfer error has occurred. Effect. The controller download has failed.
PAGE 1023
Messages SCSI Module Driver Event Messages (ZSMD) Recovery. This is an informational message only; no corrective action is needed. The device IOP will retry the command. 993: ZSMD-EVT-CMD-ABORT-ON-REQUEST The command was aborted on request from the input/output process (IOP).
PAGE 1024
SCSI Module Driver Event Messages (ZSMD) HP NonStop Operating System Event Management Programming Manual—520372-020 20-48 Messages
PAGE 1025
21 DBIOPROC Event Messages (ZDIO) This section describes the event messages generated by the Direct Bulk I/O Support Procedures (DBIOPROC) subsystem. These event messages are also known as DIO (ZDIO) event messages. DBIOPROC is one of several subsystems that work together to provide Direct Bulk I/O to enhance system performance.
PAGE 1026
Common Definitions DBIOPROC Event Messages (ZDIO) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 1027
Event Management Service (EMS) Standard Definitions DBIOPROC Event Messages (ZDIO) Figure 21-1. ZDIO-VAL-SSID Structure def ZDIO-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-INT value is ZSPI-SSN-ZDIO. 02 Z-VERSION type ZSPI-DDL-UINT value is ZDIO-VAL-VERSION. end. Token Description ZSPI-TKN-SSID Contains ZDIO-VAL-SSID, the subsystem ID of the DBIOPROC.
PAGE 1028
DBIOPROC Event Messages (ZDIO) DBIOPROC (ZDIO-) Definitions DBIOPROC (ZDIO-) Definitions DIO definitions begin with ZDIO- and are found in the source-definition files ZDIOTAL, ZDIOCOB, ZDIOTACL, ZDIOSEOF, ZDIODDL, and ZDIOC. These definitions are described in this section.
PAGE 1029
DBIOPROC Event Messages (ZDIO) Description of DBIOPROC Event Messages Description of DBIOPROC Event Messages The DBIOPROC event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZDIO-EVT-name, where name describes the event that generated the message.
PAGE 1030
Recovery Action Requiring Vendor Support DBIOPROC Event Messages (ZDIO)  A box contains the list of tokens that can appear in the event message. Header and other common tokens are not included in the list but are described in Section 2, Header and Common Tokens. The tokens might not necessarily appear in the message buffer in the same order that they are listed in the box. The tokens in the list are either:   Unconditional (always present in the message).
PAGE 1031
Messages DBIOPROC Event Messages (ZDIO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-LDEVNUMBER ZDIO-TKN-INTERNAL-CALLER ZDIO-TKN-INTERNAL-CALLED ZDIO-TKN-RCVD-RTRN-CODE token-type token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-INT2 ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-INT Conditional Token ZEMS-TKN-XLDEVNAME token-type ZSPI-TYP-STRING Event-Message Text Error return code received. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 1032
Messages DBIOPROC Event Messages (ZDIO) 2: ZDIO-EVT-HW-XSUM-SW-FIXED A checksum error detected using hardware checksumming did not recur when the checksumming operation was repeated using software.
PAGE 1033
Messages DBIOPROC Event Messages (ZDIO) Recovery. This event must be rare; infrequent occurrence must not require any service action; however, if this event occurs frequently, you might want to disable Direct Bulk I/O must be disabled by using SCF in order to minimize system performance impact and notify your service provider even though no service action is required for recovery.
PAGE 1034
Messages DBIOPROC Event Messages (ZDIO) Token Description (page 2 of 2) ZDIO-TKN-INTERNAL-CALLER Internal caller code that identifies to development where in the subsystem the event was initiated. ZEMS-TKN-EVENT-TAG Standard EMS tag token that can be used to correlate this event with the subsequent corresponding ZDIO-EVTQUARANTINE-END. Conditional Tokens Token Description ZEMS-TKN-XLDEVNAME Primary subject token that specifies the logical device name associated with the relevant I/O process.
PAGE 1035
Messages DBIOPROC Event Messages (ZDIO) Recovery. This is an informational message only; no recovery action is needed. 4: ZDIO-EVT-QUARANTINE-END The quarantine has ended. The specific set of quarantined ServerNet virtual addresses, identified in the ZDIO-EVT-QUARANTINE-START event with the corresponding ZEMS-TKN-EVENT-TAG token, has been made available for reallocation.
PAGE 1036
Messages DBIOPROC Event Messages (ZDIO) Cause. The quarantine has elapsed. Effect. The specific set of previously quarantined ServerNet virtual addresses are available for reallocation. Recovery. This is an informational message only; no recovery action is needed. 5: ZDIO-EVT-SECTOR-XSUM A sector checksum error has been detected.
PAGE 1037
Messages DBIOPROC Event Messages (ZDIO) Effect. An error is returned to the client of the DBIOPROC, typically resulting in recovery by the client file system by ending the Direct Bulk I/O session and reverting to a normal I/O. Recovery. Infrequent occurrence of this event does not need a recovery action. If the underlying cause persists, an error is likely to occur during normal I/O and can result in a more detailed error event generated by the input/output process (IOP).
PAGE 1038
Messages DBIOPROC Event Messages (ZDIO) Conditional Token Token Description ZEMS-TKN-XLDEV.NAME Primary subject token that specifies the logical device name associated with the relevant I/O process. Cause. The data read from the disk into the application buffer is inconsistent with the expected overall checksum value of zero for structured blocks. Effect.
PAGE 1039
Messages DBIOPROC Event Messages (ZDIO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDIO-EVTSTRUCTURED-RSN (7). ZEMS-TKN-LDEV.NUMBER Logical device number associated with the relevant IOP. ZDIO-TKN-EXPECTED-RSN Value obtained from the client file system for the expected RSN. ZDIO-TKN-ACTUAL-RSN Contains the value obtained from the client file system for the actual RSN.
PAGE 1040
DBIOPROC Event Messages (ZDIO) HP NonStop Operating System Event Management Programming Manual—520372-020 21-16 Messages
PAGE 1041
22 File-System Event Messages (ZFIL) The file-system subsystem (ZFIL) event messages are reported to the EMS through the service event logger ($ZLOG). These messages are viewable using the TSM EMS Event Viewer application. Table 22-1. File-System Subsystem Event Messages Event Number and Symbolic Name Description 101: ZFIL-EVT-PROC-PFS-WARN A warning message has occurred indicating that a process has consumed three-quarters of the available process file segment (PFS).
PAGE 1042
Subsystem Programmatic Interface (SPI) Standard Definitions File-System Event Messages (ZFIL) Subsystem Programmatic Interface (SPI) Standard Definitions SPI standard definitions hat have a specific meaning for file-system subsystem events are listed in Table 22-2. SPI standard definitions are described in detail in the SPI Programming Manual. Table 22-2.
PAGE 1043
Event Management Service (EMS) Standard Definitions File-System Event Messages (ZFIL) Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for file-system events are listed in Table 22-3. EMS standard definitions are described in detail in the EMS Manual. Table 22-3.
PAGE 1044
File-System Event Messages (ZFIL) File-system (ZFIL-) Definitions File-system (ZFIL-) Definitions File-system definitions begin with ZFIL- and are found in the source-definition files ZFILTAL, ZFILCOB, ZFILTACL, ZFILDDL, ZFILC, and ZFILPAS. These definitions are described in the following paragraphs and under each event message in this section.
PAGE 1045
File-System Event Messages (ZFIL) Information in Event Description Messages Information in Event Description Messages Each description contains the following information:     A header showing the numeric value and symbolic name for the event number. A paragraph describing the event message. A list:   Identifying the subject of the event message.  Indicating whether the message identifies a potentially critical event (whether ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE).
PAGE 1046
Information in Event Description Messages File-System Event Messages (ZFIL) 101: ZFIL-EVT-PROC-PFS-WARN A warning message has occurred indicating that a process has consumed threequarters of the available PFS.
PAGE 1047
Information in Event Description Messages File-System Event Messages (ZFIL) 102: ZFIL-EVT-PROC-PFS-FULL A PFS allocation failed on the indicated process, because the available PFS space is exhausted.
PAGE 1048
File-System Event Messages (ZFIL)   Information in Event Description Messages The use of sequential block buffering on open files. Turning off PFS I/O buffering using SETMODE function 72. For more information about the SETMODE procedure, see the Guardian Procedure Calls Reference Manual.
PAGE 1049
23 Storage Subsystem Event Messages (ZSTO) The storage subsystem event messages are reported to the EMS by:      SIFM SLM Storage subsystem helper process Storage subsystem manager process ($ZZSTO) Storage XIOP Table 23-1. Storage Subsystem Event Messages (page 1 of 7) Event Number and Symbolic Name Description 1: ZSTO-EVT-ERROR-IN-CONFIG The SCSI Interface Monitor (SIFM) found incorrect configuration information for a logical device.
PAGE 1050
Storage Subsystem Event Messages (ZSTO) Table 23-1. Storage Subsystem Event Messages (page 2 of 7) Event Number and Symbolic Name Description 1005: ZSTO-EVT-PRIMARY The storage subsystem manager has swapped the primary and backup processors for a device or process. 1006: ZSTO-EVT-REBUILDDFS The storage subsystem manager has rebuilt the free space table on a magnetic disk. 1007: ZSTO-EVT-REFRESH The storage subsystem manager has refreshed a magnetic disk.
PAGE 1051
Storage Subsystem Event Messages (ZSTO) Table 23-1. Storage Subsystem Event Messages (page 3 of 7) Event Number and Symbolic Name Description 1021: ZSTO-EVT-ADD The storage subsystem manager defined an object in the storage subsystem and added the object to the system configuration database. 1022: ZSTO-EVT-DELETE The storage subsystem manager has removed an object from the system configuration database.
PAGE 1052
Storage Subsystem Event Messages (ZSTO) Table 23-1. Storage Subsystem Event Messages (page 4 of 7) Event Number and Symbolic Name Description 1033: ZSTO-EVT-CRU-INIT-FAILED The storage subsystem manager failed to initialize a CRU. The event contains the error number returned from the support function used (provided by either the SIFM or the extensible I/O (XIO) product.
PAGE 1053
Storage Subsystem Event Messages (ZSTO) Table 23-1. Storage Subsystem Event Messages (page 5 of 7) Event Number and Symbolic Name Description 1045: ZSTO-EVT-CRU-CONFIG-FAILED The storage subsystem manager failed to autoconfigure a CRU. The event contains information describing the reason for the failure. 1046: ZSTO-EVT-CRU-ACCESS-ERROR The storage subsystem manager failed to obtain CRU information. 1047: ZSTO-EVT-CRU-RECONFIG The storage subsystem manager has changed the configuration for a CRU.
PAGE 1054
Storage Subsystem Event Messages (ZSTO) Table 23-1. Storage Subsystem Event Messages (page 6 of 7) Event Number and Symbolic Name Description 2002: ZSTO-EVT-CNFG-DISK-CACHE The storage subsystem manager generates an audit event when a disk configuration changes and cache settings have been altered. 2003: ZSTO-EVT-CNFG-DISK-REVIVE The storage subsystem manager generates an audit event when a disk changes configuration. Revive settings are altered and reported.
PAGE 1055
Storage Subsystem Event Messages (ZSTO) Table 23-1. Storage Subsystem Event Messages (page 7 of 7) Event Number and Symbolic Name Description 3000: ZSTO-EVT-LOCK-TIMEOUT The SCSI Lock Manager (SLM) detected that a lock owner did not release the lock in the specified time. When the specified time expires, the lock manager checks if the owner is “alive.” If it is “alive,” this event occurs.
PAGE 1056
Common Definitions Storage Subsystem Event Messages (ZSTO) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 1057
Event Management Service (EMS) Standard Definitions Storage Subsystem Event Messages (ZSTO) Figure 23-1. ZSTO-VAL-SSID Structure def ZSTO-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-INT value is ZSPI-SSN-ZSTO. 02 Z-VERSION type ZSPI-DDL-INT value is ZSTO-VAL-VERSION. end. Token Description ZSPI-TKN-SSID Contains ZSTO-VAL-SSID, the storage subsystem process ID.
PAGE 1058
SCP (ZCOM-) Standard Definitions Storage Subsystem Event Messages (ZSTO) Figure 23-2. ZEMS-VAL-SSID Structure def ZCOM-VAL-SSID 02 Z-FILLER 02 Z-OWNER 02 Z-NUMBER 02 Z-VERSION type character 8 value is ZSPI-VAL-TANDEM. redefines Z-FILLER type ZSPI-DDL-CHAR8. type ZSPI-DDL-INT value is ZSPI-SSN-ZEMS. type ZSPI-DDL-UINT value is ZEMS-VAL-VERSION. end. Figure 23-3. ZEMS-DDL-PHYSICAL-ADDRESS Structure def ZEMS-DDL-PHYSICAL-ADDRESS. 02 ZPA-GROUP type ZSPI-DDL-INT2 heading "Group:".
PAGE 1059
SCP (ZCOM-) Standard Definitions Storage Subsystem Event Messages (ZSTO) Figure 23-4. ZCOM-VAL-SSID Structure def ZCOM-VAL-SSID 02 Z-FILLER 02 Z-OWNER 02 Z-NUMBER 02 Z-VERSION type character 8 value is ZSPI-VAL-TANDEM. redefines Z-FILLER type ZSPI-DDL-CHAR8. type ZSPI-DDL-INT value is ZSPI-SSN-ZCOM. type ZSPI-DDL-UINT value is ZCOM-VAL-VERSION. end. Token Description ZCOM-TKN-SWITCH-CPU Processor in which the backup process— soon to be the primary process—is running.
PAGE 1060
SCP (ZCOM-) Standard Definitions Storage Subsystem Event Messages (ZSTO) Table 23-5.
PAGE 1061
SCP (ZCOM-) Standard Definitions Storage Subsystem Event Messages (ZSTO) Table 23-5.
PAGE 1062
Storage Subsystem (ZSTO-) Definitions Storage Subsystem Event Messages (ZSTO) Table 23-5.
PAGE 1063
Storage Subsystem Event Messages (ZSTO) Storage Subsystem (ZSTO-) Definitions Private Token and Field Types The following storage subsystem token types are defined as enumeration data types. A display string is defined for each enumeration value. When an event message is displayed by EMS, the display string is substituted for the enumeration value to which it corresponds. Token Token type for ...
PAGE 1064
Storage Subsystem (ZSTO-) Definitions Storage Subsystem Event Messages (ZSTO) Table 23-7. Values and Display Strings for ZSTO-TYP-ENM-CRU-TYPE Value Display String ZSTO-VAL-CRU-UNKNOWN Unknown CRU ZSTO-VAL-CRU-PMF PMF adapter ZSTO-VAL-CRU-IOMF IOMF adapter ZSTO-VAL-CRU-SNDA SNDA adapter ZSTO-VAL-CRU-SAC ServerNet-Addressable-Controller ZSTO-VAL-CRU-INT-MAGDISK Internal magnetic disk ZSTO-VAL-CRU-EXT-TAPE External tape Other Undefined-CRU-Type Table 23-8.
PAGE 1065
Storage Subsystem (ZSTO-) Definitions Storage Subsystem Event Messages (ZSTO) Table 23-9.
PAGE 1066
Storage Subsystem (ZSTO-) Definitions Storage Subsystem Event Messages (ZSTO) Table 23-10.
PAGE 1067
Storage Subsystem (ZSTO-) Definitions Storage Subsystem Event Messages (ZSTO) Table 23-12.
PAGE 1068
Storage Subsystem (ZSTO-) Definitions Storage Subsystem Event Messages (ZSTO) Table 23-14. Values and Display Strings for ZSTO-TYP-IFM-SSSERROR (page 2 of 2) Value Display String ZSTO-VAL-SSS-ERR-NSK NSK-error ZSTO-VAL-SSS-ERR-NOT-FOUND Not-found Other Unknown-Error Table 23-15.
PAGE 1069
Storage Subsystem (ZSTO-) Definitions Storage Subsystem Event Messages (ZSTO) Table 23-17.
PAGE 1070
Storage Subsystem (ZSTO-) Definitions Storage Subsystem Event Messages (ZSTO) Predefined Token and Field Values Token Description ZSTO-VAL-SSID Subsystem ID of the storage subsystem—the structure is shown under the description for ZSPI-TKN-SSID ZSTO-VAL-VERSION Version number of the storage subsystem Most predefined token and field values used in storage subsystem event messages are described in the event-message descriptions and in Simple Tokens and Structured Tokens on page 23-22.
PAGE 1071
Storage Subsystem Event Messages (ZSTO) Storage Subsystem (ZSTO-) Definitions Token Description (page 2 of 3) ZSTO-TKN-CTLR-ACTION Enumerated value describing the controller action. ZSTO-TKN-REASON Enumerated value specifying the reason for a configuration. ZSTO-TKN-REASONTEXT Text of the reason for the error. ZSTO-TKN-FILESYSTEMERROR Number of the file-system error. ZSTO-TKN-PATH Enumerated value containing the type of device path. ZSTO-TKN-IFM-ERROR Enumerated type.
PAGE 1072
Description of ZSTO Event Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 3 of 3) ZSTO-TKN-LOCKINFO-STR, where n =1.3 Informational string. ZSTO-TKN-LOCKINFO-VAL, where n =1.2 Informational value. ZSTO-TKN-SLM-PRIMARY Flag indicating a primary or backup process. ZSTO-TKN-OBJECT-TYPE Name of the object type. ZSTO-TKN-COMMAND SCF command. ZSTO-TKN-ATTRIBUTE.
PAGE 1073
Storage Subsystem Event Messages (ZSTO)    Recovery Action Requiring Vendor Support Identifying the sender of the event message to the EMS collector ($0 process). Indicating whether the event message is sent to the TMDS collector (D-series NonStop operating system RVUs) or OSM/TSM collector (G-series and Hseries NonStop operating system RVUs). A box contains the list of tokens that can appear in the event message.
PAGE 1074
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZSTO-TKN-RETCODE ZSTO-TKN-ERRORCODE token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-INT2 token-type token-type token-type token-type token-type ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Conditional Tokens ZSTO-TKN-ERR-DESC ZSTO-TKN-DEVICE-TYPE ZSTO-TKN-PROC-NAME ZSTO-TKN-FILE-NAME ZSTO-TKN-OBJECT-NAME Event-Me
PAGE 1075
Messages Storage Subsystem Event Messages (ZSTO) 2: ZSTO-EVT-INTERNAL-ERROR The SIFM detected an error. Subject: ZEMS-TKN-XLDEVNAME Potentially critical event: Yes Action event: No Message sender: SIFM TMDS collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Conditional Tokens ZSTO-TKN-ERR-DESC ZSTO-TKN-RETCODE ZSTO-TKN-ONLYNUM ZSTO-TKN-SAC-NAME ZSTO-TKN-IFMSTRING, n=1..5 ZSTO-TKN-IFMVALUE, n=1..
PAGE 1076
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZSTO-TKN-IFMSTRING, where n =1..5 Optional token containing the error description. ZSTO-TKN-IFMVALUE, where n =1..5 Optional token containing a number associated with the error description. Cause. The SCSI Interface Monitor detected an error that occurred when processing an external request or during startup. Effect. The requested operation is not executed. Recovery.
PAGE 1077
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTDOWNLOAD-COMPLETE (3). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZSTO-TKN-GROUP Group number. ZSTO-TKN-MODULE Module number. ZSTO-TKN-SLOT Slot number. ZSTO-TKN-SAC-NAME SAC name.
PAGE 1078
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens ZSTO-TKN-SAC-INSTANCE ZSTO-TKN-IFM-SLM-ERR token-type ZSPI-TYP-INT2 token-type ZSPI-TYP-INT2 Event-Message Text Firmware download FAILED in location (group, module, slot), SAC Name: sac-name,[ SAC instance: sac-instance ] Error: error code Error-Desc: error-description Return-Code: return-code [ SLM-Error: slm-error-code] [Syndrome: (class, value)] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this mes
PAGE 1079
Messages Storage Subsystem Event Messages (ZSTO) 5: ZSTO-EVT-CONTROLLER-ACTION The SIFM reports an error from a SSS procedure requesting a controller action.
PAGE 1080
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZSTO-TKN-SAC-INSTANCE Subdevice number of the controller for ISP/ICEPACK devices or the PIC number for SNDA devices. ZSTO-TKN-ERR-DESCRIPTOR Enumerated value identifying the specific call that failed. ZSTO-TKN-ERRORCODE Value returned by that call. ZSTO-TKN-SYNDROMECLASS Syndrome class. ZSTO-TKN-SYNDROMEVALUE Syndrome value.
PAGE 1081
Storage Subsystem Event Messages (ZSTO) Messages Event-Message Text error-description [ number][ , Retcode return-code] [, sac-name] [ description1 ] [ number1 ] [ description2 ] [ number2 ] [ description3 ] [ number3 ] [ description4 ] [ number4 ] [ description5 ] [ number5 ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTINFORMATIONAL (6). ZEMS-TKN-XLDEVNAME Subject token that contains the device name.
PAGE 1082
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZSTO-TKN-SAC-NAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING Event-Message Text CPU-I/O-Access successful. SAC Name: sac-name Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVT-IOACCESS-COMPLETE (7). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZSTO-TKN-SAC-NAME SAC name.
PAGE 1083
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text SCF ABORT object-type device-name [device-path] executed { at terminal terminal-name | by process process-descriptor } by user user-id. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTABORT (1000). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZCOM-TKN-OBJTYPE Enumerated type that contains the object type.
PAGE 1084
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZCOM-TKN-OBJTYPE ZSTO-TKN-PROC-DESC ZSTO-TKN-USERID token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZCOM-TYP-ENM-OBJ ZSPI-TYP-STRING ZSPI-TYP-USERID Conditional Tokens ZSTO-TKN-PATH ZSTO-TKN-TERMINALPROCESS token-type ZSTO-TYP-ENM-PATH token-type ZSPI-TYP-STRING Event-Message Text SCF ALLOWOPENS object-type device-name [device-path] executed { at terminal t
PAGE 1085
Messages Storage Subsystem Event Messages (ZSTO) 1002: ZSTO-EVT-ALTER The storage subsystem manager has altered the attributes of an existing object.
PAGE 1086
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager has altered the attributes of an existing object. Effect. The object attributes that were specified have been altered. If the device is in a STOPPED state, the I/O process might terminate. Recovery. The attributes that were altered can be restored with another ALTER command. If the I/O process has terminated, use the START command to restart the device.
PAGE 1087
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZSTO-TKN-PROC-DESC Process descriptor. ZSTO-TKN-USERID User ID. Conditional Tokens Token Description ZSTO-TKN-PATH Optional token containing the device path being used. ZSTO-TKN-TERMINALPROCESS Name of the terminal. Cause. The storage subsystem manager has initialized a disk. Effect.
PAGE 1088
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTLABEL (1004). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZCOM-TKN-OBJTYPE Enumerated type that contains the object type. ZSTO-TKN-TERMINALPROCESS Either this token or token ZSTO-TKN-PROC-DESC must be present. ZSTO-TKN-PROC-DESC Process descriptor. ZSTO-TKN-USERID User ID.
PAGE 1089
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens ZSTO-TKN-TERMINALPROCESS token-type ZSPI-TYP-STRING Event-Message Text SCF PRIMARY object-type device-name, cpu number executed { at terminal terminal-name | by process process-descriptor } by user user-id. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTPRIMARY (1005). ZEMS-TKN-XLDEVNAME Subject token that contains the device name.
PAGE 1090
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZCOM-TKN-OBJTYPE ZSTO-TKN-PROC-DESC ZSTO-TKN-USERID token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZCOM-TYP-ENM-OBJ ZSPI-TYP-STRING ZSPI-TYP-USERID Conditional Tokens ZSTO-TKN-PATH ZSTO-TKN-TERMINALPROCESS token-type ZSTO-TYP-ENM-PATH token-type ZSPI-TYP-STRING Event-Message Text SCF CONTROL object-type device-name [device-path] REBUILDDFS executed { at te
PAGE 1091
Messages Storage Subsystem Event Messages (ZSTO) 1007: ZSTO-EVT-REFRESH The storage subsystem manager has refreshed a magnetic disk.
PAGE 1092
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager has refreshed a magnetic disk. Effect. The dirty (changed) cache pages and file-control blocks are written to the disk. Recovery. This is an informational message only; no corrective action is needed. 1008: ZSTO-EVT-RENAME A user command has caused the storage subsystem manager to rename a magnetic disk.
PAGE 1093
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens Token Description ZSTO-TKN-TERMINALPROCESS Name of the terminal. Cause. A user command has renamed a magnetic disk. Effect. The default volume name and alternate volume name of a disk have been permanently changed. If the disk is a member of a pool, the pool process and virtual disks are not informed. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1094
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZSTO-TKN-NEW-NAME New name of an object. ZSTO-TKN-TERMINALPROCESS Either this token or token ZSTO-TKN-PROC-DESC must be present. ZSTO-TKN-PROC-DESC. Process descriptor ZSTO-TKN-USERID User ID. Conditional Tokens Token Description ZSTO-TKN-PATH Optional token containing the device path being used. ZSTO-TKN-TERMINALPROCESS Name of the terminal. Cause.
PAGE 1095
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTRESET (1010). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZCOM-TKN-OBJTYPE Enumerated type that contains the object type. ZSTO-TKN-NEW-NAME New name of an object. ZSTO-TKN-TERMINALPROCESS Either this token or token ZSTO-TKN-PROC-DESC must be present. ZSTO-TKN-PROC-DESC. Process descriptor ZSTO-TKN-USERID User ID.
PAGE 1096
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZCOM-TKN-OBJTYPE ZSTO-TKN-PROC-DESC ZSTO-TKN-USERID token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZCOM-TYP-ENM-OBJ ZSPI-TYP-STRING ZSPI-TYP-USERID Conditional Tokens ZSTO-TKN-PATH ZSTO-TKN-TERMINALPROCESS token-type ZSTO-TYP-ENM-PATH token-type ZSPI-TYP-STRING Event-Message Text SCF CONTROL object-type device-name [device-path], SPARE executed { at termin
PAGE 1097
Messages Storage Subsystem Event Messages (ZSTO) 1012: ZSTO-EVT-START The storage subsystem manager has successfully placed an object into the STARTED state.
PAGE 1098
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens Token Description ZSTO-TKN-PATH Optional token containing the device path being used. ZSTO-TKN-TERMINALPROCESS Name of the terminal. Cause. The storage subsystem manager has successfully placed an object into the STARTED state. Effect. The object is in the STARTED state and is accessible to user processes. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1099
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZCOM-TKN-OBJTYPE Enumerated type that contains the object type. ZSTO-TKN-NEW-NAME New name of an object. ZSTO-TKN-TERMINALPROCESS Either this token or token ZSTO-TKN-PROC-DESC must be present. ZSTO-TKN-PROC-DESC. Process descriptor ZSTO-TKN-USERID User ID. Conditional Tokens Token Description ZSTO-TKN-PATH Optional token containing the device path being used. ZSTO-TKN-TERMINALPROCESS Name of the terminal.
PAGE 1100
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text SCF STOP object-type device-name [device-path] executed { at terminal terminal-name | by process process-descriptor } by user user-id. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTSTOP (1014). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZCOM-TKN-OBJTYPE Enumerated type that contains the object type. ZSTO-TKN-NEW-NAME New name of an object.
PAGE 1101
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZCOM-TKN-OBJTYPE ZSTO-TKN-PROC-DESC ZSTO-TKN-USERID token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZCOM-TYP-ENM-OBJ ZSPI-TYP-STRING ZSPI-TYP-USERID Conditional Tokens ZSTO-TKN-PATH ZSTO-TKN-TERMINALPROCESS token-type ZSTO-TYP-ENM-PATH token-type ZSPI-TYP-STRING Event-Message Text SCF STOPOPENS object-type device-name [device-path] executed { at terminal te
PAGE 1102
Messages Storage Subsystem Event Messages (ZSTO) 1016: ZSTO-EVT-SWITCH The storage subsystem manager has changed the active path to a device.
PAGE 1103
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager has changed the active path to a device. Effect. The active path is changed. Recovery. This is an informational message only; no corrective action is needed. 1017: ZSTO-EVT-CHECKIN-LAUNCH The storage subsystem manager processor checkin task launch failed.
PAGE 1104
Messages Storage Subsystem Event Messages (ZSTO) 1018: ZSTO-EVT-DISK-CHECKNAME-LAUNCH The storage subsystem manager fails to launch the disk rename notification task.
PAGE 1105
Messages Storage Subsystem Event Messages (ZSTO) 1020: ZSTO-EVT-CONFIG-GETINFO-ERR The storage subsystem manager received an unexpected error when querying a process for configuration information.
PAGE 1106
Messages Storage Subsystem Event Messages (ZSTO) 1021: ZSTO-EVT-ADD The storage subsystem manager defined an object in the storage subsystem and added the object to the system configuration database.
PAGE 1107
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager defined an object in the storage subsystem and added the object to the system configuration database. Effect. The name of the object has been defined and has been added to the system configuration database. The name of the object has been reserved. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1108
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens Token Description ZSTO-TKN-PATH Optional token containing the device path being used. ZSTO-TKN-TERMINALPROCESS Name of the terminal. Cause. The storage subsystem manager removed an object configured in the storage subsystem and removed the object from the system configuration database. Effect. The object name is no longer reserved. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1109
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager received an error when communicating with SIFM. Effect. The command was not executed. Recovery. Take the action directed by the error messages and try the command again. 1024: ZSTO-EVT-DEVICE-ALTER-STOP The storage subsystem manager reports an implicit device termination because of an ALTER command.
PAGE 1110
Messages Storage Subsystem Event Messages (ZSTO) 1025: ZSTO-EVT-ZCNF-ACCESS-ERROR The storage subsystem manager failed to access the configuration utility process ($ZCNF).
PAGE 1111
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager failed to access the configuration utility process ($ZCNF). Effect. The command was not executed. Recovery. Retry the command. If the problem persists, see Recovery Action Requiring Vendor Support on page 23-25. 1026: ZSTO-EVT-ADAPTER-AUTO-FAIL The storage subsystem manager failed to autoconfigure an adapter.
PAGE 1112
Messages Storage Subsystem Event Messages (ZSTO) 1027: ZSTO-EVT-ADAPTER-AUTO-RETRY The storage subsystem manager is waiting for a resource that is blocking autoconfiguration of an adapter.
PAGE 1113
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSTO-TKN-CRU-TYPE ZEMS-MAP-PHYSICAL-ADDRESS token-type ZSPI-TYP-INT token-type ZSTO-TYP-ENM-CRU-TYPE token-type ZEMS-DDL-PHYSICALADDRESS Event-Message Text cru-type detected in location ( group, module, slot ). Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTCRU-INSERTED (1028). ZSTO-TKN-CRU-TYPE CRU type.
PAGE 1114
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text cru-type object-name in location (group, module, slot) removed. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTCRU-REMOVED (1029). ZSTO-TKN-OBJECT-NAME Object name. ZSTO-TKN-CRU-TYPE CRU type. ZEMS-MAP-PHYSICAL-ADDRESS Physical location of the CRU. Cause. The storage subsystem manager received a hardware deletion event from the configuration utility process ($ZCNF).
PAGE 1115
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text Wrong CRU inserted in location ( group, module, slot ): cru-type [ SAC instance: sac-instance ] [ SAC type: sac-type ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTWRONG-CRU-INSERTED (1030). ZSTO-TKN-CRU-TYPE CRU type. ZEMS-MAP-PHYSICAL-ADDRESS Physical location of the CRU.
PAGE 1116
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens ZSTO-TKN-SAC-INSTANCE ZSTO-TKN-SAC-TYPE ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-INT2 token-type ZSTO-TYP-ENM-SAC-TYPE token-type ZCOM-TYP-ENM-OBJ Event-Message Text The Storage Subsystem Manager automatically configured an cru-type in location (group, module, slot) [ , SAC instance: sac-instance] [ , SAC type: sac-type. ] Name: object-name. [ The cru-type is used as a object-type cru-type.
PAGE 1117
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSTO-TKN-OBJECT-NAME ZSTO-TKN-CRU-TYPE ZEMS-MAP-PHYSICAL-ADDRESS token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSTO-TYP-ENM-CRU-TYPE ZEMS-DDL-PHYSICALADDRESS Event-Message Text cru-type object-name in location (group, module, slot) initialized. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTCRU-INIT (1032).
PAGE 1118
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text Failed to initialize cru-type object-name in location (group, module, slot). Error Code: error-number (error-message). Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTCRU-INIT-FAILED (1033). ZSTO-TKN-OBJECT-NAME Object name. ZSTO-TKN-CRU-TYPE CRU type. ZEMS-MAP-PHYSICAL-ADDRESS Physical location of the CRU.
PAGE 1119
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens ZSTO-TKN-SAC-INSTANCE ZSTO-TKN-SAC-TYPE ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-INT2 token-type ZSTO-TYP-ENM-SAC-TYPE token-type ZCOM-TYP-ENM-OBJ Event-Message Text Power On Self Test (POST) completed for cru-type object-name in location (group, module, slot) [, SAC instance: sac-instance ] [, SAC type: sac-type ] [, SAC usuage: object-type. ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 1120
Messages Storage Subsystem Event Messages (ZSTO) 1035: ZSTO-EVT-POST-FAILED The storage subsystem manager determined that the power-on self-test failed for a CRU that was inserted.
PAGE 1121
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens Token Description ZSTO-TKN-SAC-INSTANCE Optional token containing the SAC instance. ZSTO-TKN-SAC-TYPE Optional token containing the SAC type. ZCOM-TKN-OBJTYPE Optional token that is an enumerated type that contains the object type. Cause. The storage subsystem manager determined that the power-on-self-test (POST) failed for a CRU that was inserted. Effect. The CRU did not pass POST and it is not usable. Recovery.
PAGE 1122
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTCHECKSUM (1036). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZCOM-TKN-OBJTYPE Enumerated type that contains the object type. ZSTO-TKN-TERMINALPROCESS Either this token or the token ZSTO-TKN-PROCDESC must be present. ZSTO-TKN-PROC-DESC Process descriptor. ZSTO-TKN-USERID User ID.
PAGE 1123
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text The cru-type inserted in location (group, module, slot) is invalid. The CRU information cannot be used to configure the CRU. Check whether the CRU’s firmware has been initialized. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTINVALID-CRU (1037). ZSTO-TKN-CRU-TYPE Enumerated type containing the CRU-type. ZEMS-MAP-PHYSICAL-ADDRESS Physical location of the CRU. Cause.
PAGE 1124
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTSERVER-ERROR (1038). ZSTO-TKN-OBJECT-NAME Object name. ZSTO-TKN-RETCODE Type of error. ZSTO-TKN-ERRORCODE Error. Cause. The storage subsystem manager detected a server access error. Effect. The command was not executed. Recovery. Retry the command. If the problem persists, see Recovery Action Requiring Vendor Support on page 23-25.
PAGE 1125
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager detected a process startup I/O error. This is caused by a failure to send startup messages to a process that was just launched. Effect. The command is not executed. Recovery. Retry the command. If the problem persists, see Recovery Action Requiring Vendor Support on page 23-25. 1040: ZSTO-EVT-UNSUPPORTED-CRU The storage subsystem manager received a hardware insertion event for a CRU it does not support.
PAGE 1126
Messages Storage Subsystem Event Messages (ZSTO) 1041: ZSTO-EVT-CRU-OWNERSHIP The storage subsystem manager detected that it cannot configure a CRU because the slot where the CRU was inserted is already configured by another subsystem.
PAGE 1127
Messages Storage Subsystem Event Messages (ZSTO) 1042: ZSTO-EVT-CRU-DELETED The storage subsystem manager has deleted the customer-replaceable unit’s (CRU) configurations from the system configuration database.
PAGE 1128
Messages Storage Subsystem Event Messages (ZSTO) 1043: ZSTO-EVT-TASK-ERROR The storage subsystem manager detected that an internal task failed.
PAGE 1129
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSTO-TKN-OBJECT-NAME ZCOM-TKN-OBJTYPE ZCOM-TKN-NEW-CPU token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZCOM-TYP-ENM-OBJ ZSPI-TYP-INT Event-Message Text object-type object-name started in processor cpu-number. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVT-IOPLAUNCH (1044). ZSTO-TKN-OBJECT-NAME Object name.
PAGE 1130
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens ZSTO-TKN-REASON ZSTO-TKN-REASONTEXT ZSTO-TKN-RETCODE ZSTO-TKN-ERRORCODE token-type token-type token-type token-type ZSTO-TYP-CONF-ERROR ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-INT2 Event-Message Text Failed to configure object-type device-name for location (group, module, slot) [. Reason: reason [(reason-text)]] [, Error code: error-code] [, Error detail: error-detail].
PAGE 1131
Messages Storage Subsystem Event Messages (ZSTO) 1046: ZSTO-EVT-CRU-ACCESS-ERROR The storage subsystem manager failed to obtain CRU information.
PAGE 1132
Messages Storage Subsystem Event Messages (ZSTO) 1047: ZSTO-EVT-CRU-RECONFIG The storage subsystem manager changed the configuration for a CRU (for example, when a ServerNet device adapter’s (SNDA) configuration is changed from tape to disk usage.
PAGE 1133
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager changed the configuration for the CRU. Effect. The configuration of a CRU is changed. Recovery. This is an informational message only; no corrective action is needed. 1048: ZSTO-EVT-CONFIG-DEFERRED The storage subsystem manager has deferred the configuration of a CRU.
PAGE 1134
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager has deferred the configuration of a CRU. This event is generated when the storage profile record forces the storage subsystem manager to start the I/O process to complete the configuration of the CRU, and the processors in which the I/O process is configured to run are not available. Effect. The configuration of the CRU is not completed. Recovery. Reload one of the required processors.
PAGE 1135
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem encountered an error while attempting to notify a primary process to launch its backup process. Effect. The disk process continues to run without a backup process. Recovery. Reload the processor where the backup process must have been launched, or terminate the disk process using the SCF RESET DISK, FORCED command. Relaunch it using the SCF START DISK command. 1050: ZSTO-EVT-REPLACE A user issued an SCF REPLACE command.
PAGE 1136
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZEMS-TKN-SUBJECT-MARK EMS token that marks the token that follows it in the event message as a subject of the event. See the EMS Manual for more information about this token. ZSPI-TKN-NEXTTOKEN Pointer to the next token code in the buffer. See the SPI Programming Manual for more information about this token. ZSTO-TKN-PROC-DESC Process descriptor. ZSTO-TKN-USERID User ID.
PAGE 1137
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTACCESS-LIST (1051). ZEMS-TKN-CRU-TYPE Enumerated type that contains the CRU type. ZEMS-MAP-PHYSICAL-ADDRESS Physical location of the CRU. Cause. The storage subsystem manager received a hardware insertion event from the configuration utility process ($ZCNF). Effect.
PAGE 1138
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZEMS-TKN-CONTENT-STANDARD Has the value ZEMS-VAL-OTHER-STATECHANGE. ZSTO-TKN-TERMINALPROCESS Terminal-process name. ZSTO-TKN-USERID User ID. ZCOM-TKN-OBJTYPE. Object type. ZCOM-OBJ-DISK.ZEMS-TKN-LDEVNUMBER ldev number. Cause. A user issued an SCF LABEL command. Effect. The command was executed. Recovery. This is an informational message only; no action is needed.
PAGE 1139
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZEMS-TKN-CONTENT-STANDARD Has the value ZEMS-VAL-OTHER-STATECHANGE. ZSTO-TKN-TERMINALPROCESS Terminal-process name. ZSTO-TKN-USERID User ID. ZCOM-TKN-OBJTYPE. Object type. ZCOM-OBJ-DISK.ZEMS-TKN-LDEVNUMBER ldev number. Cause. A user issued an SCF EJECT command. Effect. The command was executed. Recovery. This is an informational message only; no action is needed.
PAGE 1140
Messages Storage Subsystem Event Messages (ZSTO) Cause. A REPLACE ADAPTER command did not download all SACs with a new firmware version. Possible reasons are:    The user limited the command to one processor. The user terminated the downloads with the ABANDON option. The downloads were terminated because a processor was halted or reloaded. Effect. The system continues to use two different versions of the same firmware type. Recovery.
PAGE 1141
Messages Storage Subsystem Event Messages (ZSTO) 1056: ZSTO-EVT-IOP-ACCESS-FAILED A SCSI command to a device failed.
PAGE 1142
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZSTO-TKN-SYNDROMECLASS Syndrome class. ZSTO-TKN-SYNDROMEVALUE Syndrome value. Cause. A command that you tried to send to the I/O process failed. Effect. The command is not executed. SCF waits for the next command. Recovery. Collect the information in the error text and contact your service representative for further assistance. See the SCF Reference Manual for the Storage Subsystem.
PAGE 1143
Messages Storage Subsystem Event Messages (ZSTO) Recovery. This is an informational message only; no corrective action is needed. 2001: ZSTO-EVT-CNFG-DISK-NAME The storage subsystem manager has been informed that a disk has changed its name automatically.
PAGE 1144
Messages Storage Subsystem Event Messages (ZSTO) 2002: ZSTO-EVT-CNFG-DISK-CACHE The storage subsystem manager generates an audit event when a disk configuration changes and cache settings have been altered.
PAGE 1145
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZSTO-TKN-CACHE-2048 Optional token that contains the value of the cache setting for cache-2048. ZSTO-TKN-CACHE-4096 Optional token that contains the value of the cache setting for cache-4096. Cause. The storage subsystem manager generates an audit event when a disk configuration is changed and cache settings are altered. Effect. The disk configuration are changed with a new cache settings. Recovery.
PAGE 1146
Messages Storage Subsystem Event Messages (ZSTO) Conditional Tokens Token Description ZSTO-TKN-REVIVEBLOCKS Optional token that contains the value of the reviveblocks setting. ZSTO-TKN-REVIVEINTERVAL Optional token that contains the value of the revive interval setting. Cause. The storage subsystem manager generates an audit event when a disk changes configuration. Revive settings are altered and reported. Effect. A disk has changed configuration. The revive settings are altered and reported.
PAGE 1147
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager has detected that a CRU is not configured. This event is generated during system load or when a hardware insertion event is received. This event is generated only when storage automatic configuration is disabled. Effect. None. The CRU remains unconfigured. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1148
Messages Storage Subsystem Event Messages (ZSTO) Token Description (page 2 of 2) ZCOM-TKN-OBJTYPE Token that contains the object type. ZEMS-MAP-PHYSICAL-ADDRESS Physical location of the CRU. Conditional Tokens Token Description ZSTO-TKN-SAC-INSTANCE Optional token containing the SAC instance. ZSTO-TKN-SAC-TYPE Optional token containing the SAC type. ZCOM-TKN-USAGE Optional token that contains the object type. Cause.
PAGE 1149
Messages Storage Subsystem Event Messages (ZSTO) Cause. The storage subsystem manager has detected that the newly installed SAC is incompatible with the devices currently configured for the SAC. Effect. The SAC is unusable as configured because the SAC type does not match the devices configured for it. Recovery. Do one of the following:   Replace the SAC with one that matches the configuration. Delete the devices that are not compatible with the installed SAC.
PAGE 1150
Messages Storage Subsystem Event Messages (ZSTO) Recovery. To recognize and recover from this type of inconsistency, see the SOFTDOC for the T1083 product. 2501: ZSTO-EVT-RECONCILE-CONFIG The storage subsystem manager reports that an object exists in the system configuration database but not in SMF catalogs.
PAGE 1151
Messages Storage Subsystem Event Messages (ZSTO) 2502: ZSTO-EVT-SMF-LAUNCH-FAILURE The storage subsystem manager reports that a pool launch failed.
PAGE 1152
Messages Storage Subsystem Event Messages (ZSTO) 2503: ZSTO-EVT-XIOCOLORADOPKTCONFIG The storage subsystem manager reports a failure to configure a SNDA.
PAGE 1153
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSTO-TKN-OBJECT-NAME ZSTO-TKN-COMMAND ZSTO-TKN-ATTRIBUTE ZSTO-TKN-OBJECT-TYPE token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text command object-type object-name [,attribute] has created inconsistency between SMF catalogs and the CONFIG file.
PAGE 1154
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZCOM-TKN-OBJTYPE ZSTO-TKN-OBJECT-NAME ZSTO-TKN-REASONTEXT token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZCOM-TYP-ENM-OBJ ZSPI-TYP-STRING ZSPI-TYP-STRING Event-Message Text object-type object-name cannot be started now, reason: reason-text Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 1155
Messages Storage Subsystem Event Messages (ZSTO) achieved. For “Disk process not running” and “SMF configured CPU not running,” the storage subsystem manager aborts the task. Recovery. Check the reason text returned and take the appropriate corrective action as follows:   If TMF is not running, start TMF. If TMF is already started, verify whether TMF is ready for transactions. For information on starting TMF or checking or enabling transactions on TMF, see the TMF Reference Manual.
PAGE 1156
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text Lock timed out on resource:resource-type:resource-name, Owner: proc-name Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVT-LOCKTIMEOUT (3000). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZSTO-TKN-RESOURCETYPE Resource type. ZSTO-TKN-RESOURCENAME Resource ID.
PAGE 1157
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text PreLock Coordination I/O timed out on Member:proc-name, for Resource:resource-type: resource-name. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTPRE-COORDN-TIMEOUT (3001). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZSTO-TKN-RESOURCE-TYPE Resource type. ZSTO-TKN-RESOURCE-NAME Resource ID.
PAGE 1158
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text PostLock Coordination I/O timed out on Member:proc-name, for Resource:resource-type: resource-name. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVTPOST-COORDN-TIMEOUT (3002). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZSTO-TKN-SLM-PRIMARY Indicates whether the primary or backup lock manager process is reporting this event.
PAGE 1159
Messages Storage Subsystem Event Messages (ZSTO) Event-Message Text Cannot obtain enough resident memory to support new-isp-icepacks Isp-Icepacks, new-fpic-colorados Fpic-Colorados; Currently supporting curr-isp-icepacks Isp-Icepacks, curr-fpic-colorados Fpic-Colorados. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTOEVT-LOCK-MEMORY-FAIL (3003). ZEMS-TKN-XLDEVNAME Subject token that contains the device name.
PAGE 1160
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZSTO-TKN-SLM-PRIMARY ZSTO-TKN-LOCKINFO-STR,n=13 ZSTO-TKN-LOCKINFO-VAL,n=12 token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-STRING ZSPI-TYP-INT2 Event-Message Text string1 string2 string3 value1 value2 Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVT-LOCKINFO (3004).
PAGE 1161
Messages Storage Subsystem Event Messages (ZSTO) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-XLDEVNAME ZSTO-TKN-SLM-PRIMARY ZSTO-TKN-LOCKINFO-STR,N=13 token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-INT2 Event-Message Text Requestor: string1, Resource: string2, Owner: string3 Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVT-LOCKFAIL-INFO (3005).
PAGE 1162
Storage Subsystem Event Messages (ZSTO) Messages Event-Message Text SCSI Lock Manager is abending. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZSTO-EVT-LOCKMANAGER-ABEND (3006). ZEMS-TKN-XLDEVNAME Subject token that contains the device name. ZSTO-TKN-SLM-PRIMARY Indicates whether the primary or backup lock manager process is reporting this event. Cause. The primary SCSI Lock Manager process has abended. Effect.
PAGE 1163
24 Configuration Services Event Messages (ZDSC) ZDSC event messages are reported to EMS by:     $ZCNF process $ZCDB process $ZPM process $ZHOME process Table 24-1. ZDSC Event Messages (page 1 of 4) Event Number and Symbolic Name Description 1024: ZDSC-EVT-ZPM-STARTUP-FAILURE The persistence manager process ($ZPM) could not be launched. 1025: ZDSC-EVT-ZPM-PROCESS-STOPPED The persistence manager process ($ZPM) was stopped unexpectedly.
PAGE 1164
Configuration Services Event Messages (ZDSC) Table 24-1. ZDSC Event Messages (page 2 of 4) 1036: ZDSC-EVT-USING-BASE-CONFIG The base configuration file was copied and is now in use as the system’s configuration database. 1037: ZDSC-EVT-USING-CONFIG The file was opened and is now in use as the system’s configuration database. 1038: ZDSC-EVT-CONFIG-SAVED The previous version of the file was saved. 1039: ZDSC-EVT-CANNOT-READ-CONFIG An error occurred while reading the system configuration database.
PAGE 1165
Configuration Services Event Messages (ZDSC) Table 24-1. ZDSC Event Messages (page 3 of 4) 1054: ZDSC-EVT-ZCDB-RESTART-THRES The persistence manager process has ($ZCDB) exceeded the restart threshold. 2048: ZDSC-EVT-GNRC-PROCESS-STARTED A generic process was started in a processor by $ZPM. 2049: ZDSC-EVT-GNRC-PROCESS-RESTRTED A generic process was restarted in a processor by $ZPM. 2050: ZDSC-EVT-RESERVED-NAME-FAIL An error occurred and $ZPM was unable to reserve a permanent process name.
PAGE 1166
Configuration Services Event Messages (ZDSC) Table 24-1. ZDSC Event Messages (page 4 of 4) 2064: ZDSC-EVT-CANT-OPEN-CLDLD-TACL The persistence manager process ($ZPM) encountered an error when attempting to open the system load TACL process to send it a startup message. The system load TACL will timeout and stop.
PAGE 1167
Common Definitions Configuration Services Event Messages (ZDSC) Common Definitions Common definitions are definitions that are used in several (usually three or more) event messages for a specific subsystem or system component.
PAGE 1168
Event Management Service (EMS) Standard Definitions Configuration Services Event Messages (ZDSC) Token Description ZSPI-TKN-SSID Contains ZDSC-VAL-SSID, the subsystem ID of ZDSC. ZSPI-SSN-ZDSC Subsystem number of ZDSC. Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for ZDSC events are listed in Table 24-3. EMS standard definitions are described in detail in the EMS Manual. Table 24-3.
PAGE 1169
Configuration Services Event Messages (ZDSC) Configuration Services (ZDSC-) Definitions Private Token and Field Types Token Description ZDSC-TKN-PROC-LAUNCH-ERR Error that occurred during the process launch ZDSC-TKN-PROC-LAUNCH-ERR-DETAIL Detail of the error that occurred during the process launch ZDSC-TKN-PROC-DEATH-CCODE Process completion code of the stopped persistence manager process ZDSC-TKN-PROC-DEATH-TCODE Process termination code of the stopped persistence manager process ZDSC-TKN-PROC-
PAGE 1170
Configuration Services (ZDSC-) Definitions Configuration Services Event Messages (ZDSC) Predefined Token and Field Values Token Description ZDSC-VAL-SSID ZDSC subsystem ID—the structure is shown under the description for ZSPI-TKN-SSID ZDSC-VAL-VERSION Version number for the ZDSC system ZDSC-TKN-PROC-DESC Descriptor of the previous locker process ZDSC-TKN-PROC-LAUNCH-ERR Process launch error received while trying to create a process ZDSC-TKN-PROC-LAUNCH-ERR-DETAIL Details of the error that occur
PAGE 1171
Configuration Services Event Messages (ZDSC) Description of ZDSC Event Messages Description of ZDSC Event Messages The ZDSC event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZDSC-EVT-name, where name describes the event that generated the message.
PAGE 1172
Configuration Services Event Messages (ZDSC)    Recovery Action Requiring Vendor Support A description of each token follows the box The cause describes what might have caused the event The effect describes the implication (if any) of the generated event The recovery describes what action (if any) must be taken Recovery Action Requiring Vendor Support Contact your service provider or the Global Mission Critical Solution Center (GMCSC), as directed by your local operating procedures.
PAGE 1173
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSCEVT-ZPM-STARTUP-FAILURE (1024). ZDSC-TKN-PROC-LAUNCH-ERR Error that occurred during the process launch. Value is ZDSC-TNM-PROC-LAUNCH-ERR. ZDSC-TKN-PROC-LAUNCH-ERR-DETL Detailed error information about the failed launch. Value is ZDSC-TNM-PROC-LAUNCHERR-DETL. Cause.
PAGE 1174
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTZPM-PROCESS-STOPPED (1025). ZDSC-TKN-PROC-DEATH-CCODE Process completion code of the stopped persistence manager process. Value is ZDSC-TNM-PROCDEATH-CCODE. ZDSC-TKN-PROC-DEATH-TCODE Process termination code of the stopped persistence manager process. Value is ZDSC-TNM-PROCDEATH-TCODE.
PAGE 1175
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this event. Value is ZDSC-EVT-ZPMRESTART-THRES (1026). Cause. The configuration utility process ($ZCNF) attempted to start $ZPM three times in the last 10 minutes. Effect. $ZCNF will wait 10 minutes, then attempt to start $ZPM again. Recovery. If the error persists, see Recovery Action Requiring Vendor Support on page 24-10.
PAGE 1176
Messages Configuration Services Event Messages (ZDSC) 1029: ZDSC-EVT-UNKNOWN-CRU-DELETION A Customer Replaceable Unit (CRU) that was not known in the hardware configuration tables was removed from the system.
PAGE 1177
Messages Configuration Services Event Messages (ZDSC) Effect. $ZCNF will not update its hardware configuration table for this event; however, it will send the event to the registrants of this CRU deletion event. Recovery. See Recovery Action Requiring Vendor Support on page 24-10. 1030: ZDSC-EVT-CANNOT-ADD-CRU The inserted Customer Replaceable Unit (CRU) information cannot be added to the hardware configuration tables.
PAGE 1178
Messages Configuration Services Event Messages (ZDSC) Cause. After $ZCNF received a CRU Insertion or TNet CRU Configured event, it tried to add CRU information to the Physical CRU Table (PCT) or the TNet Node Table (TNT) respectively, but found that the tables were full. Effect. The CRU information does not get stored into the PCT or TNT and, therefore, is unavailable for later queries. Recovery. See Recovery Action Requiring Vendor Support on page 24-10.
PAGE 1179
Messages Configuration Services Event Messages (ZDSC)  If the event is followed by a TNet CRU configured event from SP, there could be a mismatch in the Group, Module Slot information contained in the event and the information in the TNT maintained by $ZCNF. Effect. If the event packet for which $ZCNF generated a bad maintenance event contains any events for which there are registered clients, the clients will not be able to receive the registered events. Recovery.
PAGE 1180
Messages Configuration Services Event Messages (ZDSC) Cause. $ZCNF received a CRU configured event from the service processor for a CRU whose entry was not found in the Physical CRU Table. Effect. No CRU information will be sent to registrants of this event. Recovery. Check for any previous CRU deletion events from SP.
PAGE 1181
Messages Configuration Services Event Messages (ZDSC) Cause. $ZCNF received a TNet CRU configured event from the SP for a CRU whose entry was not found in the Physical CRU Table. Effect. No entry will be made for this TNet CRU in the TNet node table by $ZCNF and hence no information about it will be returned. Recovery. Check for any previous CRU deletion events from the SP.
PAGE 1182
Messages Configuration Services Event Messages (ZDSC) Token Description (page 2 of 2) ZDSC-TKN-ACTUAL-SEQ-NUMBER Sequence number contained in the message received. Value is ZDSC-TNM-ACTUAL-SEQNUMBER. ZDSC-TKN-SP-DOMAIN-NUMBER Number of the cabinet possessing the sequence number that is out of sequence with $ZCNF. Value is ZDSC-TNM-SP-DOMAIN-NUMBER. Cause. SP events delivered to $ZCNF are not in sync with the sequence number that $ZCNF was expecting according to its internal tables. Effect.
PAGE 1183
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTUSING-BACKUP-CONFIG (1035). ZDSC-TKN-FILENAME (1) Configuration file that had been previously saved. Value is ZDSC-TNM-FILENAME (1). ZDSC-TKN-FILENAME (2) File to which the saved file was copied. It is now in use as the system’s configuration database. Value is ZDSC-TNMFILENAME (2). Cause.
PAGE 1184
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTUSING-BASE-CONFIG (1036). ZDSC-TKN-FILENAME (1) File to which the base configuration file has been copied. Value is ZDSC-TNM-FILENAME (1). ZDSC-TKN-FILENAME (2) Base configuration file that is now in use as the system’s configuration database. Value is ZDSC-TNM-FILENAME (2). Cause.
PAGE 1185
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTUSING-CONFIG (1037). ZDSC-TKN-FILENAME Name of the file that has been opened and is serving as the configuration database for the system. Value is ZDSCTNM-FILENAME. Cause. The CONFIG file was successfully opened and is serving as the system’s configuration database. Effect. None. Recovery. None required.
PAGE 1186
Messages Configuration Services Event Messages (ZDSC) Cause. An SCF SAVE CONFIGURATION command was used or the CONFIG file was saved to CONFSAVE by $ZCDB during its processing. $ZCDB always saves the current configuration file into CONFSAVE when the system is loaded. Effect. The current configuration has been saved into either CONFnnnn or CONFSAVE. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1187
Messages Configuration Services Event Messages (ZDSC) Cause. The configuration database manager ($ZCDB) was trying to read records from the configuration database as specified by the client, but encountered an error other than FEEOF and FEOK. Effect. The records read before this event occurred are returned to the client but no further records are read. The event contains information about the last record read. Recovery.
PAGE 1188
Messages Configuration Services Event Messages (ZDSC) Token Description (page 2 of 2) ZDSC-TKN-RECORD-TYPE Type of record. Value is ZDSC-TNM-RECORDTYPE. ZDSC-TNM-RECORD-NAME Name of the record. Value is ZDSC-TNM-RECORDNAME. Cause. The request to insert a record into the configuration database failed because the configuration database manager ($ZCDB) encountered an error other than FEOK and FEDUP while trying to write to the file. Effect.
PAGE 1189
Messages Configuration Services Event Messages (ZDSC) Cause. While $ZCDB was trying to insert or delete a record in the configuration database, it found that the configuration database file was locked by a locker, but the locker had died. This event can also occur when $ZCDB receives a request for locking the file and finds that the current lock owner does not exist. Effect.
PAGE 1190
Messages Configuration Services Event Messages (ZDSC) Effect. The event description provides a file system procedure number (as defined in $SYSTEM.ZSPIDEF.ZFILC), the error that was returned from this procedure, and the file number. Use this information to determine what went wrong and what effect can be expected. Recovery. If the error persists, see Recovery Action Requiring Vendor Support on page 24-10. 1044: ZDSC-EVT-CONFIG-BAD-FTYPE The configuration file is not a key-sequenced file.
PAGE 1191
Messages Configuration Services Event Messages (ZDSC) Recovery. Use a FUP INFORMATION command to ensure that the configuration database file currently in use is a key-sequenced file. If the configuration database file is not key-sequenced, copy CONFSAVE to a file such as CONFnnnn, where nnnn is a four-digit number indicating the configuration version to be saved. Use this CONFnnnn file to load the system by specifying nn.nn as the saved config version during system load.
PAGE 1192
Messages Configuration Services Event Messages (ZDSC) 1046: ZDSC-EVT-NO-TEMPNAME A temporary file name could not be created. Potentially critical event: No Action event: No Message sender: $ZCDB TMDS collector: No OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZDSC-TKN-FILE-ERROR ZDSC-TKN-FILENAME token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT token-type ZSPI-TYP-STRING Event-Message Text Unable to create a temporary configuration filename.
PAGE 1193
Messages Configuration Services Event Messages (ZDSC) If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. 1047: ZDSC-EVT-PURGE-RENAME A file name could not be purged and was instead renamed.
PAGE 1194
Messages Configuration Services Event Messages (ZDSC) 1048: ZDSC-EVT-CONFIG-READ-ERR An error occurred while trying to read the configuration database. Potentially critical event: No Action event: No Message sender: $ZCDB TMDS collector: No OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZDSC-TKN-FILENAME ZDSC-TKN-FILE-ERROR token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-TYP-UINT Event-Message Text Cannot read configuration file filename, error file-error.
PAGE 1195
Messages Configuration Services Event Messages (ZDSC) 1049: ZDSC-EVT-CONFIG-CONVERT-ERROR An error occurred and shared adapter records cannot be converted. $ZCNF cannot guarantee checks for adapter sharing conflicts.
PAGE 1196
Messages Configuration Services Event Messages (ZDSC) 1050: ZDSC-EVT-CONFIG-CONFLICT-ERR An error occurred and configuration adapter conflict was detected.
PAGE 1197
Messages Configuration Services Event Messages (ZDSC) 1051: ZDSC-EVT-RLBACK-LOSS-ERR Service processor hardware state change events with timestamps preceding the system load time were received, and might be stale.
PAGE 1198
Messages Configuration Services Event Messages (ZDSC) 1052: ZDSC-EVT-ZCDB-STARTUP-FAILURE The configuration database manager process ($ZCDB) could not be launched because of a process launch error.
PAGE 1199
Messages Configuration Services Event Messages (ZDSC) 1053: ZDSC-EVT-ZCDB-PROCESS-STOPPED The configuration database manager process ($ZCDB) has stopped unexpectedly.
PAGE 1200
Messages Configuration Services Event Messages (ZDSC) 1054: ZDSC-EVT-ZCDB-RESTART-THRES The configuration database manager process ($ZCDB) has exceeded the restart threshold. Potentially critical event: No Action event: No Message sender: $ZCNF TMDS collector: No OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT Event-Message Text The configuration database manager process ($ZCDB) restart threshold exceeded.
PAGE 1201
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZDSC-TKN-PROC-NAME ZDSC-TKN-CPU token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-TYP-UINT Event-Message Text Proc-name started by $ZPM in processor cpu. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTGNRC-PROCESS-STARTED (2048). ZDSC-TKN-PROC-NAME Name of the generic process that was started. Value is ZDSC-TNM-PROC-NAME.
PAGE 1202
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTGNRC-PROCESS-STARTED (2049). ZDSC-TKN-PROC-NAME Name of the process restarted by $ZPM. Value is ZDSCTNM-PROC-NAME. ZDSC-TKN-CPU Name of the processor where the process was restarted. Value is ZDSC-TNM-CPU. Cause.
PAGE 1203
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTRESERVED-NAME-FAIL (2050). ZDSC-TKN-PROC-NAME Name of the process that could not be named. Value is ZDSC-TNM-PROC-NAME. ZDSC-TKN-FILE-ERROR File error that occurred. Value is ZDSC-TNM-FILEERROR. ZDSC-TKN-ERROR-DESCRIPTION Reason $ZPM was unable to reserve a name for the process. Value is ZDSC-TNM-ERRORDESCRIPTION. Cause.
PAGE 1204
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTPRSTNT-PROC-STOPPED (2051). ZDSC-TKN-PROC-DESC Description of the process that has stopped. Value is ZDSC-TNM-PROC-DESC. ZDSC-TKN-PROC-DEATH-CCODE Completion code of the stopped process. Value is ZDSC-TNM-PROC-DEATH-CCODE. ZDSC-TKN-PROC-DEATH-TCODE Termination code of the stopped process. Value is ZDSC-TNM-PROC-DEATH-TCODE.
PAGE 1205
Messages Configuration Services Event Messages (ZDSC) Event-Message Text Persistent process proc-desc has abended. Completion code: proc-death-ccode, termination code: proc-death-tcode Termination text:proc-death-text Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTPRSTNT-PROC-ABEND (2052). ZDSC-TKN-PROC-DESC Description of the process that abended. Value is ZDSC-TNM-PROC-DESC.
PAGE 1206
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZDSC-TKN-PROC-DESC ZDSC-TKN-PROC-DEATH-CCODE ZDSC-TKN-PROC-DEATH-TCODE ZDSC-TKN-PROC-DEATH-TEXT token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-STRING Event-Message Text Non-persistent process, proc-desc, that was started by $ZPM has abended.
PAGE 1207
Messages Configuration Services Event Messages (ZDSC) 2054: ZDSC-EVT-PROCESS-LAUNCH-FAIL An error occurred and a generic process failed to launch in a processor.
PAGE 1208
Messages Configuration Services Event Messages (ZDSC) Effect. The indicated process is not launched. If the process is system load TACL, $ZPM abends. If it is any other process, $ZPM attempts to launch the process on another processor if the processor is available and the process was configured to run on that processor. If the process is a subsystem manager process, applications or other processes that were configured to run through that subsystem will fail.
PAGE 1209
Messages Configuration Services Event Messages (ZDSC) Token Description (page 2 of 2) ZDSC-TKN-RESTART-COUNT-LIMIT Number of restarts allowed for the restart process. Value is ZDSC-TNM-RESTART-COUNT-LIMIT. ZDSC-TKN-RESTART-DELAY Delay, in minutes, before the program can begin the next restart attempt. Value is ZDSC-TNMRESTART-DELAY. Cause.
PAGE 1210
Messages Configuration Services Event Messages (ZDSC) Token Description (page 2 of 2) ZDSC-TKN-FILE-ERROR Type of file error that occurred. Value is ZDSCTNM-FILE-ERROR. ZDSC-TKN-ERROR-DESCRIPTION Reason for the occurrence of this event. Value is ZDSC-TNM-ERROR-DESCRIPTION. Cause. The Persistence Manager ($ZPM) encountered a critical internal error and is abending. Effect.
PAGE 1211
Messages Configuration Services Event Messages (ZDSC) Token Description (page 2 of 2) ZDSC-TKN-FILE-ERROR Type of file error that occurred. Value is ZDSC-TNM-FILEERROR. ZDSC-TKN-ERROR-DETAIL Detailed information about the error that occurred. Value is ZDSC-TNM-ERROR-DETAIL. ZDSC-TKN-CPU Processor in which the process with which $ZPM is communicating was started. Value is ZDSC-TNM-CPU. Cause.
PAGE 1212
Messages Configuration Services Event Messages (ZDSC) Event-Message Text The $ZPM process experienced an internal error. Procedure name: zpm-procedure-name Source line: program-counter Error type: internal-error Error: error-description Error value: file-error Error detail: error-detail Process descriptor: process-descriptor CPU number: cpu Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSCEVT-ZPM-INTERNAL-ERROR (2060).
PAGE 1213
Messages Configuration Services Event Messages (ZDSC) Effect. The event text names the procedure where the internal error occurred. If it happened during a reload, the reload process might not complete, resulting in $ZPM not being able to start all processes that are dependent on $ZPM. Also, checkin protocols with subsystem managers might not get executed. If the internal error occurs when $ZPM is trying to process a PROCDEATH message from a process, $ZPM will not attempt to restart the process.
PAGE 1214
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSCEVT-BAD-RESERVED-NAME-REC (2061). ZDSC-TKN-PROCEDURE-NAME Procedure containing the configuration database where the inconsistent reserve name was found. Value is ZDSC-TNM-PROCEDURE-NAME. ZDSC-TKN-RECORD-NAME Record name. Value is ZDSC-TNM-RECORDNAME. ZDSC-TKN-DB-RECORD-FIELD-NUM Number of the bad field. Value is ZDSC-TNM-DBRECORD-FIELD-NUM.
PAGE 1215
Messages Configuration Services Event Messages (ZDSC) Event-Message Text An inconsistent generic process record was found in the configuration database in procedure procedure-name. Record name: record-name Bad field number: db-bad-field-num Bad field value: db-bad-field-val Bad field is: error-description Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSCEVT-BAD-GENERIC-PROC-REC (2062).
PAGE 1216
Messages Configuration Services Event Messages (ZDSC) 2063: ZDSC-EVT-CANT-PURGE-TACL-SWAP The persistence manager process ($ZPM) encountered an error when attempting to purge the system load TACL swap file.
PAGE 1217
Messages Configuration Services Event Messages (ZDSC) Recovery. This is an informational message only; no corrective action is needed. 2064: ZDSC-EVT-CANT-OPEN-CLDLD-TACL The persistence manager process ($ZPM) encountered an error when attempting to open the system load TACL process to send it a startup message. The system load TACL will timeout and stop.
PAGE 1218
Messages Configuration Services Event Messages (ZDSC) 2065: ZDSC-EVT-CANT-DO-RESTART-WAIT The persistence manager process ($ZPM) detected an error while trying to set a delay before resuming restart attempts for the process after the restart threshold was exceeded.
PAGE 1219
Messages Configuration Services Event Messages (ZDSC) 2066: ZDSC-EVT-STRTMSG-FAIL-OPEN An error occurred when attempting to open the generic process to send a startup message.
PAGE 1220
Messages Configuration Services Event Messages (ZDSC) 2067: ZDSC-EVT-STRTMSG-FAIL-SEND An error occurred when attempting to send the generic process a startup message.
PAGE 1221
Messages Configuration Services Event Messages (ZDSC) 2068: ZDSC-EVT-SPI-STOP-OPEN-FAILED An error occurred when attempting to open the target process to send an SPI STOP command.
PAGE 1222
Messages Configuration Services Event Messages (ZDSC) 2069: ZDSC-EVT-ASSIGNMSG-FAIL-SEND An error occurred when attempting to send an assign message to the generic process.
PAGE 1223
Messages Configuration Services Event Messages (ZDSC) 2070: ZDSC-EVT-PARAMMSG-FAIL-SEND An error occurred when attempting to send a parameter message to the generic process.
PAGE 1224
Messages Configuration Services Event Messages (ZDSC) 2071: ZDSC-EVT-DEFINES-OVERFLOW An error occurred when attempting to send all configured defines to the generic process.
PAGE 1225
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZDSC-TKN-CPU token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT Event-Message Text $ZHOME backup process created in processor cpu. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDSC-EVTBACKUP-CREATED (3072). ZDSC-TKN-CPU Processor where the process with which $ZPM is communicating was started. Value is ZDSC-TNM-CPU. Cause.
PAGE 1226
Messages Configuration Services Event Messages (ZDSC) Cause. The primary process for $ZHOME died and the backup process has taken over. Effect. None; this is an informational message. Recovery. This is an informational message only; no corrective action is needed. 3074: ZDSC-EVT-OUTPUT-UNAVAIL An error occurred when attempting to access a file for output.
PAGE 1227
Messages Configuration Services Event Messages (ZDSC) 3075: ZDSC-EVT-OUTPUT-AVAILABLE The open retry was successful and the output file is now available and being used. Potentially critical event: No Action event: No Message sender: $ZHOME TMDS collector: No OSM/TSM collector: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZDSC-TKN-filename token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING Event-Message Text Device filename is available and is being used.
PAGE 1228
Messages Configuration Services Event Messages (ZDSC) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZDSC-TKN-FILENAME ZDSC-TKN-ZPM-PROGRAM-COUNTER ZDSC-TKN-FILE-ERROR ZDSC-TKN-ERROR-DETAIL token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-STRING ZSPI-TYP-INT2 ZSPI-TYP-UINT ZSPI-TYP-UINT Event-Message Text $ZHOME internal error at file filename, line line-number error file-error, detail error-detail.
PAGE 1229
25 Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Note. These messages are generated only by the H-series NonStop operating system RVUs. Complex manager auxiliary process (ZCMP) event messages are reported to the EMS by the service event logger process ($ZLOG), and in some cases, by the EMS collector process ($0). Note. In software interfaces and messages, the old terms in Table 25-1 are equivalent to the new terms in Table 25-1.
PAGE 1230
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-2. ZCMP Event Messages (page 2 of 5) 103: ZCMP-EVT-PE-REINT-START A PE reintegration started. 104: ZCMP-EVT-PE-REINT-FAILED A PE reintegration failed. 105: ZCMP-EVT-PE-REINT-DEFERRED A PE reintegration was deferred. 106: ZCMP-EVT-PE-REINT-DISABLED A PE reintegration was disabled. 107: ZCMP-EVT-PE-REINT-ENABLED A PE reintegration was enabled.
PAGE 1231
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-2. ZCMP Event Messages (page 3 of 5) 129: ZCMP-EVT-MEMCOPY-ERROR Memory copy operation could not be started. 130: ZCMP-EVT-PE-IN-ERROR A PE reported an internal error. 132: ZCMP-EVT-PE-REINT-START-ERROR A PE reintegration could not start. 133: ZCMP-EVT-PE-QUIESCE-TO An attempt to make a PE quiescent in preparation for reintegration timed out. 134: ZCMP-EVT-PE-REINT-START-TO A PE reintegration timed out.
PAGE 1232
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-2. ZCMP Event Messages (page 4 of 5) 214: ZCMP-EVT-ECHO-CABLING-VALID* An invalid reintegration cabling configuration became valid. 215: ZCMP-EVT-ECHO-SCRUB-ERROR FPGA 3 scrub error. 216: ZCMP-EVT-LID-CHANGED* Local interrupt ID (LID) of one PE in a processor changed. 217: ZCMP-EVT-LSU-CHANGED* Logical synchronization unit (LSU) status changed. 218: ZCMP-EVT-SLICE-CHANGED A NonStop Blade Element tracking ID changed.
PAGE 1233
Common Definitions Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-2. ZCMP Event Messages (page 5 of 5) 500: ZCMP-EVT-RCVDUMP-FAILURE A PE’s scheduled receive dump either failed to launch or failed after being launched. 600: ZCMP-EVT-SAD-PROCESS-FAILED Slow Access Device (SAD) process either could not be launched or failed after being launched. * Both $ZLOG and $0 report this event to the EMS.
PAGE 1234
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Subsystem Programmatic Interface (SPI) Standard Definitions Subsystem Programmatic Interface (SPI) Standard Definitions SPI standard definitions that have a specific meaning for CMAP events are listed in Table 25-3. SPI standard definitions are described in detail in the SPI Programming Manual. Table 25-3.
PAGE 1235
Event Management Service (EMS) Standard Definitions Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event Management Service (EMS) Standard Definitions EMS standard definitions that have a specific meaning for CMAP events are listed in Table 25-4. EMS standard definitions are described in detail in the EMS Manual. Table 25-4.
PAGE 1236
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Description of ZCMP Event Messages Description of ZCMP Event Messages The ZCMP event messages are described in detail on the following pages. The descriptions are in ascending order by event number. The symbolic name for the event number is ZCMP-EVT-name, where name describes the event that generated the message.
PAGE 1237
Recovery Action Requiring Vendor Support Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP)     A description of each token follows the box The cause describes what might have caused the event The effect describes the implication (if any) of the generated event The recovery describes what action (if any) must be taken Recovery Action Requiring Vendor Support Contact your service provider or the Global Mission Critical Solution Center (GMCSC), as directed by your local operating procedure
PAGE 1238
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Event-Message Text On CPU <1>, the PE on slice <2> (LID <3>) has stopped Slice module tracking ID : <4> LSU0 module tracking ID : <5> LSU1 module tracking ID: <6> Stop code : 0x<7> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTPE-STOPPED (100). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN.
PAGE 1239
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-CPU ZCPU-TKN-SLICEID ZCPU-TKN-LID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID1 <1> <2> <3> <4> <5> <6> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRI
PAGE 1240
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 102: ZCMP-EVT-PE-REINTEGRATED A PE was reintegrated into a processor.
PAGE 1241
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description ZCMP-TKN-LSU-TRACKING-ID Tracking ID of the first LSU to which the PE connects. ZCMP-TKN-LSU-TRACKING-ID1 Tracking ID of the second LSU to which the PE connects. ZCMP-TKN-RETRIES Number of tries required to reintegrate the PE. Cause. A PE has been reintegrated into a processor. Effect. None. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1242
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Event-Message Text On CPU <1>, reintegration of PE on slice <2> (LID <3>) started Target slice module tracking ID: <4> Source slice module tracking ID: <5> LSU0 module tracking ID: <6> LSU1 module tracking ID: <7> Reintegration reason : <8> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTPE-REINT-START (103). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE.
PAGE 1243
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 104: ZCMP-EVT-PE-REINT-FAILED Reintegration of a PE into a processor failed.
PAGE 1244
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the NonStop Blade Element where the PE resides. ZCMP-TKN-LSU-TRACKING-ID Tracking ID of the first LSU to which the PE connects. ZCMP-TKN-LSU-TRACKING-ID1 Tracking ID of the second LSU to which the PE connects. ZCMP-TKN-REINT-FAIL-REASON Reason that reintegration failed (see Table 25-6).
PAGE 1245
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-CPU ZCPU-TKN-SLICEID ZCPU-TKN-LID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID1 ZCMP-TKN-DEFER-REINT-RSN <1> <2> <3> <4> <5> <6> <7> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-ST
PAGE 1246
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-7. ZCMP-TKN-DEFER-REINT-RSN Values Value Meaning ZCMP-ENM-DEFER-REINT-DISABLED PE reintegration is disabled. ZCMP-ENM-DEFER-REINT-HALT Reintegration would halt processor. ZCMP-ENM-DEFER-REINT-SOURCE Copy source is not available. Cause. See Table 25-7. Effect. None. Recovery. This is an informational message only; no corrective action is needed.
PAGE 1247
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTPE-REINT-DISABLED (106). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-CPU Subject token that specifies the processor where the PE resides. ZCPU-TKN-SLICEID Subject token that specifies the NonStop Blade Element where the PE resides.
PAGE 1248
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-CPU ZCPU-TKN-SLICEID ZCPU-TKN-LID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID1 ZCMP-TKN-ENABLE-REINT-RSN <1> <2> <3> <4> <5> <6> <7> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-S
PAGE 1249
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-9. ZCMP-TKN-ENABLE-REINT-RSN Values Value Meaning ZCMP-ENM-ENABLE-REINT-TIMEOUT Enable-reintegration time limit expired. ZCMP-ENM-ENABLE-REINT-API Enable-reintegration API called. Cause. See Table 25-9. Effect. None. Recovery. This is an informational message only; no corrective action is needed. 108: ZCMP-EVT-CRL-CHANGE A NonStop Blade Complex has a new complex reintegration leader (CRL).
PAGE 1250
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the first NonStop Blade Element of the NonStop Blade Complex. ZCPU-TKN-SLICE-TRACKING-ID1 Tracking ID of the second NonStop Blade Element of the NonStop Blade Complex. ZCPU-TKN-SLICE-TRACKING-ID2 Tracking ID of the third NonStop Blade Element of the NonStop Blade Complex. Cause.
PAGE 1251
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event-Message Text Slice reset has started Slice ID : <1> Slice module tracking ID : <2> Reset reason : <3> Affected CPUs : CPU <11>, LID <12> <*IF 20 > CPU <21>, LID <22><*ENDIF> <*IF 25 > CPU <26>, LID <27><*ENDIF> <*IF 30 > CPU <31>, LID <32><*ENDIF> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-SLICE-RESET-STARTED (109). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE.
PAGE 1252
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 110: ZCMP-EVT-SLICE-RESET-DONE A NonStop Blade Element reset completed. Potentially critical event: No Action event: No Message sender: CMAP $ZLOG: Yes $0: No Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCMP-TKN-SLICEID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-SLICE-ARRAY.CPU(0) ZCMP-TKN-SLICE-ARRAY.LID(0) ZCMP-TKN-SLICE-ARRAY.CPU(1) ZCMP-TKN-SLICE-ARRAY.LID(1) ZCMP-TKN-SLICE-ARRAY.
PAGE 1253
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-SLICEID Subject token that specifies the NonStop Blade Element. ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the NonStop Blade Element. ZCMP-TKN-SLICE-ARRAY.CPU(n ) Subject token that specifies the processor of PE n +1 on the NonStop Blade Element. ZCMP-TKN-SLICE-ARRAY.
PAGE 1254
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Interpretations ZCMP-TKN-SLICE-ARRAY.NUMLIDS > 1 <20> ZCMP-TKN-SLICE-ARRAY.NUMLIDS > 2 <25> ZCMP-TKN-SLICE-ARRAY.
PAGE 1255
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-11. ZCMP-TKN-RESET-FAIL-REASON Values (page 2 of 2) Value Meaning ZCMP-ENM-RESETFAIL-RESET-TO NonStop Blade Element-reset time limit expired. ZCMP-ENM-RESETFAIL-ECHO FPGA 3 hardware could not be initialized. Cause. See Table 25-11. Effect. Every processor that has a PE on this NonStop Blade Element continues to lose some redundancy. Recovery. CMAP tries to reset the NonStop Blade Element again.
PAGE 1256
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event-Message Text Slice reset has been deferred Slice ID : <1> Slice module tracking ID : <2> Reset defer reason : <3> Affected CPUs : CPU <11>, LID <12> <*IF 20 > CPU <21>, LID <22><*ENDIF> <*IF 25 > CPU <26>, LID <27><*ENDIF> <*IF 30 > CPU <31>, LID <32><*ENDIF> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-SLICE-RESET-DEFERRED (112).
PAGE 1257
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 113: ZCMP-EVT-SLICE-RESET-DISABLED A NonStop Blade Element reset was disabled. Potentially critical event: No Action event: No Message sender: CMAP $ZLOG: Yes $0: No Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCMP-TKN-SLICEID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-DISABLE-RESET-RSN ZCMP-TKN-SLICE-ARRAY.CPU(0) ZCMP-TKN-SLICE-ARRAY.LID(0) ZCMP-TKN-SLICE-ARRAY.CPU(1) ZCMP-TKN-SLICE-ARRAY.
PAGE 1258
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-SLICE-RESET-DISABLED (113). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-SLICEID Subject token that specifies the NonStop Blade Element. ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the NonStop Blade Element.
PAGE 1259
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCMP-TKN-SLICEID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-ENABLE-RESET-RSN ZCMP-TKN-SLICE-ARRAY.CPU(0) ZCMP-TKN-SLICE-ARRAY.LID(0) ZCMP-TKN-SLICE-ARRAY.CPU(1) ZCMP-TKN-SLICE-ARRAY.LID(1) ZCMP-TKN-SLICE-ARRAY.CPU(2) ZCMP-TKN-SLICE-ARRAY.LID(2) ZCMP-TKN-SLICE-ARRAY.CPU(3) ZCMP-TKN-SLICE-ARRAY.
PAGE 1260
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-SLICE-ARRAY.CPU(n ) Subject token that specifies the processor of PE n +1 on the NonStop Blade Element. ZCMP-TKN-SLICE-ARRAY.LID(n ) Subject token that specifies the LID of PE n +1 on the NonStop Blade Element. ZCMP-TKN-SLICE-ARRAY.NUMLIDS Number of unique LIDs (PEs) that are running the NonStop operating system on the NonStop Blade Element. Table 25-14.
PAGE 1261
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-INTERNAL-ERROR (115). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-TRUE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-MAJOR. ZCMP-TKN-INTERNAL-ERROR Error value. ZCMP-TKN-ERROR-DETAIL Error detail. Cause. The reason that the tokens ZCMP-TKN-INTERNAL-ERROR and ZCMP-TKNERROR-DETAIL specify (usually an assertion failure).
PAGE 1262
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event-Message Text On CPU <1>, the PE on slice <2> (LID <3>) cannot be reintegrated Reason : <4> Slice module tracking ID : <5> CPU : <6> LID : <7> Slice 1 : <8> Slice module tracking ID 1 : <9> Unconditional Tokens Token Description (page 1 of 2) ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-CANT-REINTEGRATE (116). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE.
PAGE 1263
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCPU-TKN-SLICE-TRACKING-ID1 If the value of ZCMP-TKN-CANT-REINTREASON is ZCMP-ENM-REINT-LOC-PEDOWN, the value of this token is the ID of the NonStop Blade Element that is preventing reintegration of the PE; otherwise, it is 255 (decimal). Table 25-15. ZCMP-TKN-CANT-REINT-REASON Values Value Meaning ZCMP-ENM-REINT-CPU-HALT Reintegration would halt processor.
PAGE 1264
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCMP-TKN-SLICEID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-CANT-RESET-REASON ZCMP-TKN-SLICE-ARRAY.CPU(0) ZCMP-TKN-SLICE-ARRAY.LID(0) ZCMP-TKN-SLICE-ARRAY.CPU(1) ZCMP-TKN-SLICE-ARRAY.LID(1) ZCMP-TKN-SLICE-ARRAY.CPU(2) ZCMP-TKN-SLICE-ARRAY.LID(2) ZCMP-TKN-SLICE-ARRAY.CPU(3) ZCMP-TKN-SLICE-ARRAY.
PAGE 1265
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-SLICE-ARRAY.LID(n ) Subject token that specifies the LID of PE n +1 on the NonStop Blade Element. ZCMP-TKN-SLICE-ARRAY.NUMLIDS Number of unique LIDs (PEs) that are running the NonStop operating system on the NonStop Blade Element. Table 25-16. ZCMP-TKN-CANT-RESET-REASON Values Value Meaning ZCMP-ENM-RESET-CPU-HALT Reset would halt processor.
PAGE 1266
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Token Interpretation ZCPU-TKN-LID <> %HFF Event-Message Text Operation aborted Operation : <1> Abort reason : <2> Affected Slice Tracking ID : <3> <*IF 10 > Affected CPU : <4> Affected LID : <5> <*ENDIF> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTOPERATION-ABORTED (118). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE.
PAGE 1267
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-18. ZCMP-TKN-ABORT-REASON Values Value Meaning ZCMP-ENM-ABORT-CMPLX-CFG Invalid NonStop Blade Complex configuration ZCMP-ENM-ABORT-CPU-CFG Invalid CPU configuration ZCMP-ENM-ABORT-REQ Disable request received Cause. Either:   A CMAP client explicitly requested that the operation be aborted. An error event required that the operation be aborted. Effect. None. Recovery.
PAGE 1268
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-CRL-FAILED (119). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-CPU Subject token that specifies the processor where the CRL failed. ZCMP-TKN-COMPLEX-ID ID of the NonStop Blade Complex.
PAGE 1269
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event-Message Text CPU <1> has been declared invalid Complex ID : <2> Slice module tracking ID : <3> Slice module tracking ID1 : <4> Slice module tracking ID2 : <5> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-CPU-INVALID (120). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-TRUE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-MAJOR.
PAGE 1270
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 121: ZCMP-EVT-CPU-VALID An invalid processor became valid.
PAGE 1271
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Effect. The processor can reintegrate PEs and, if necessary, be reset. Recovery. This is an informational message only; no corrective action is needed. 122: ZCMP-EVT-HSS-ERROR Either Halted State Services (HSS) or a timeout communicating with HSS returned an error.
PAGE 1272
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-HSS-OPERATION HSS operation being requested (see Table 25-19) ZCMP-TKN-HSS-STATUS Status of HSS (see Table 25-20). Table 25-19.
PAGE 1273
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY ZCMP-TKN-COMPLEX-ID ZCPU-TKN-SLICEID ZCPU-TKN-LID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-PE-ISOLATE-ERR <1> <2> <3> <4> <5> token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-BYTE ZSPI-TYP-BYTE ZSPI-TYP-STRING ZSPI-TYP-ENUM Event-Message Text
PAGE 1274
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Effect. None. Recovery. This is an informational message only; no corrective action is needed. 124: ZCMP-EVT-SLICE-RESET-ERROR A NonStop Blade Element reset could not be performed.
PAGE 1275
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-SLICE-RESET-ERROR (124). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-CPU Subject token that specifies the processor. ZCPU-TKN-SLICEID Subject token that specifies the NonStop Blade Element.
PAGE 1276
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-CPU ZCPU-TKN-SLICEID ZCPU-TKN-LID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID1 ZCMP-TKN-QUIESCE-ERROR <1> <2> <3> <4> <5> <6> <7> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-STRI
PAGE 1277
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-23. ZCMP-TKN-QUIESCE-ERROR Values Value Meaning ZCMP-ENM-QUIESCE-PE-TO PE communication time limit expired. ZCMP-ENM-QUIESCE-PE-ERR PE rejected request. Cause. See Table 25-23. Effect. None. Recovery. This is an informational message only; no corrective action is needed. 126: ZCMP-EVT-ECHO-INIT-ERROR FPGA 3 hardware could not be initialized.
PAGE 1278
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTECHO-INIT-ERROR (126). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-SLICEID Subject token that specifies the NonStop Blade Element that was to be reset. ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the source NonStop Blade Element.
PAGE 1279
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Effect. If FPGA 3 hardware is not working correctly, PEs that are on the NonStop Blade Element with the FPGA 3 hardware cannot be reintegrated. Recovery. Contact your service provider. 127: ZCMP-EVT-TARG-ECHO-INIT-ERROR Target FPGA 3 hardware could not be initialized.
PAGE 1280
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-ECHO-CHANNEL Subject token that specifies the LID of the affected channel. ZCMP-TKN-TARG-ECHO-INIT-ERR Initialization error that occurred (see Table 25-25). Table 25-25. ZCMP-TKN-TARG-ECHO-INIT-ERROR Values Value Meaning ZCMP-ENM-TARGECHOINIT-PE-TO PE communication time limit expired. ZCMP-ENM-TARGECHOINIT-PE-ERR PE rejected request. Cause. See Table 25-25. Effect. None. Recovery.
PAGE 1281
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-PE-REINT-FINAL-ERROR (128). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-CPU Subject token that specifies the processor where the PE resides. ZCPU-TKN-SLICEID Subject token that specifies the NonStop Blade Element where the PE failed to reintegrate.
PAGE 1282
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 129: ZCMP-EVT-MEMCOPY-ERROR Memory copy operation could not be started.
PAGE 1283
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-ECHO-STATUS Status of the FPGA 3 device for the source NonStop Blade Element (contents of the FPGA 3 status register, which might provide FPGA 3 hardware error information). ZCMP-TKN-ECHO-ERROR Contents of the FPGA 3 error register for the source NonStop Blade Element (contents of the FPGA 3 status register, which might provide FPGA 3 hardware error information).
PAGE 1284
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 130: ZCMP-EVT-PE-IN-ERROR A PE reported an internal error.
PAGE 1285
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-LSU-TRACKING-ID1 Tracking ID of the second LSU to which the PE connects. ZCMP-TKN-PE-ERROR-RSN Reason for this message (see Table 25-28). Messages Table 25-28. ZCMP-TKN-PE-ERROR Values Value Meaning ZCMP-ENM-PE-TO PE communication time limit expired. ZCMP-ENM-PE-ERR PE rejected request. ZCMP-ENM-PE-LID PE LID mismatch. ZCMP-ENM-PE-MEMORY PE memory size mismatch.
PAGE 1286
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-CPU ZCPU-TKN-SLICEID ZCPU-TKN-LID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID ZCMP-TKN-LSU-TRACKING-ID1 ZCMP-TKN-REINT-START-ERR <1> <2> <3> <4> <5> <6> <7> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-ST
PAGE 1287
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-29. ZCMP-TKN-REINT-START-ERR Values Value Meaning ZCMP-ENM-REINTSTART-PE-TO PE communication time limit expired. ZCMP-ENM-REINTSTART-PE-ERR PE rejected request. Cause. See Table 25-29. Effect. None. Recovery. This is an informational message only; no corrective action is needed. 133: ZCMP-EVT-PE-QUIESCE-TO An attempt to make a PE quiescent in preparation for reintegration timed out.
PAGE 1288
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-CPU Subject token that specifies the processor where the PE resides. ZCPU-TKN-SLICEID Subject token that specifies the NonStop Blade Element where PE resides. ZCPU-TKN-LID Subject token that specifies the LID of the PE whose reintegration timed out.
PAGE 1289
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Event-Message Text On CPU <1>, PE on slice <2> (LID <3>) failed to enter state to allow reintegration start Slice module tracking ID: <4> LSU0 module tracking ID: <5> LSU1 module tracking ID: <6> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTPE-REINT-START-TO (134). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE.
PAGE 1290
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-SLICEID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-ECHO-STATE ZCMP-TKN-ECHO-STATUS ZCMP-TKN-ECHO-ERROR ZCMP-TKN-ECHO-INFO <1> <2> <3> <4> <5> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-BYTE token-type ZSPI-TYP-STRING token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT4 token-type ZSPI-TYP-INT4
PAGE 1291
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITYINDETERMIN. ZCPU-TKN-SLICEID Subject token that specifies the NonStop Blade Element to which the FPGA 3 device is connected. ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the NonStop Blade Element where the PE resides. ZCMP-TKN-ECHO-STATE State of the FPGA 3 copy logic (see Table 25-27 on page 25-55).
PAGE 1292
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 201: ZCMP-EVT-COMPLEX-INVALID-1 A NonStop Blade Complex is invalid because PEs with the same NonStop Blade Element tracking ID have different NonStop Blade Element IDs. (This event can be generated for each NonStop Blade Element in the NonStop Blade Complex.
PAGE 1293
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-COMPLEX-INVALID-1 (201). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the NonStop Blade Element where the PEs reside. ZCMP-TKN-SLICE-ARRAY.CPU(n ) Subject token that specifies the processor of PE n +1.
PAGE 1294
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-SLICEID ZCPU-TKN-SLICE-TRACKING-ID token-type ZSPI-TYP-INT token-type ZSPI-TYPBOOLEAN token-type ZSPI-TYPISO-SEVERITY <1> token-type ZSPI-TYPBYTE <2> token-type ZSPI-TYPSTRING ZCMP-TKN-SLICE-ARRAY.CPU(0) ZCMP-TKN-SLICE-ARRAY.LID(0) <11> token-type ZSPI-TYP-INT <12> token-type ZSPI-TYPBYTE ZCMP-TKN-SLICE-ARRAY.
PAGE 1295
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event-Message Text All PEs on a slice are not reporting Node number Slice ID : <1> Slice module tracking ID : <2> CPU : <11>, LID :<12> Node Number : <13>, Node Name : <*IF 20 > CPU : <21>, LID : <22> Node Number : <23>, Node Name : <*IF 25 > CPU : <26>, LID : <27> Node Number : <28>, Node Name : <*IF 30 > CPU : <31>, LID : <32> Node Number : <33>, Node Name : the same Node Name and <14> <24><*ENDIF> <29><*ENDIF> <34><*ENDIF> Uncon
PAGE 1296
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Cause. Not all PEs that have the same NonStop Blade Element tracking ID are connected to the same port on each LSU NonStop Blade Complex; therefore, the PEs’ node names and node numbers do not match. Effect. The NonStop Blade Complex is invalid; therefore, CMAP cannot reintegrate its PEs or reset its NonStop Blade Elements. Recovery. Correct the PE/LSU cabling problem.
PAGE 1297
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Event-Message Text In complex <1>, all CPUs do not share a common set of slices - complex invalid CPU : <2> LID : <3> LSU0 Tracking ID : <4> LSU1 Tracking ID : <5> Slice 1, Slice Tracking number : <7> <*IF 10>, Slice 2, Slice Tracking number : <12> <*ENDIF> <*IF 20>, Slice 3, Slice Tracking number : <22> <*ENDIF> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 1298
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Recovery. Correct the PE/LSU cabling problem. 204: ZCMP-EVT-COMPLEX-INVALID-4 A NonStop Blade Complex is invalid because its NonStop Blade Elements have different numbers of PEs.
PAGE 1299
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCPU-TKN-SLICE-TRACKING-ID1 NonStop Blade Element tracking ID of the second NonStop Blade Element in the NonStop Blade Complex. ZCMP-TKN-SLICE-NUM-PES1 Number of unique LIDs (PEs) on the second NonStop Blade Element ZCPU-TKN-SLICE-TRACKING-ID2 NonStop Blade Element tracking ID of the third NonStop Blade Element in the NonStop Blade Complex.
PAGE 1300
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Event-Message Text CPU <1> reported slice tracking IDs that do not match the tracking IDs for the complex - complex invalid Complex ID : <2> Slice module tracking ID : <3> Slice module tracking ID1 : <4> Slice module tracking ID2 : <5> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTCOMPLEX-INVALID-5 (205). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE.
PAGE 1301
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 206: ZCMP-EVT-COMPLEX-NOW-INVALID A valid NonStop Blade Complex became invalid.
PAGE 1302
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Effect. The NonStop Blade Complex is invalid; therefore, it cannot reintegrate PEs or reset NonStop Blade Elements. Recovery. Correct the problem specified in preceding ZCMP event messages. 207: ZCMP-EVT-COMPLEX-NOW-VALID An invalid NonStop Blade Complex became valid.
PAGE 1303
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTCOMPLEX-NOW-VALID (207). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCMP-TKN-COMPLEX-ID ID of the affected NonStop Blade Complex. ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the first NonStop Blade Element in the NonStop Blade Complex.
PAGE 1304
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-SLICE-TRACKING-ID token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY <1> token-type ZSPI-TYP-STRING ZCMP-TKN-SLICE-ARRAY.ECHCN-NUM(0) <11> token-type ZSPI-TYPBYTE ZCMP-TKN-SLICE-ARRAY.ECHCN-RCV(0) <12> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.ECHCN-EXP(0) <13> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.
PAGE 1305
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-SLICE-ARRAY.ECHCN-NUM(n ) ID of channel n +1. ZCMP-TKN-SLICE-ARRAY.ECHCN-RCV(n ) Contents of the receive register for channel n +1. ZCMP-TKN-SLICE-ARRAY.ECHCN-EXP(n ) Contents of the expecting register for channel n +1. ZCMP-TKN-SLICE-ARRAY.ECHCN-XMT(n ) Contents of the transmit register for channel n +1. ZCMP-TKN-SLICE-ARRAY.
PAGE 1306
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) ZCMP-TKN-SLICE-ARRAY.ECHCN-NUM(1) <21> token-type ZSPI-TYPBYTE ZCMP-TKN-SLICE-ARRAY.ECHCN-RCV(1) <22> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.ECHCN-EXP(1) <23> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.ECHCN-XMT(1) <24> token-type ZSPI-TYPINT Token Interpretations ZCMP-TKN-SLICE-ARRAY.
PAGE 1307
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Effect. CMAP cannot reintegrate one or more PEs or reset one or more NonStop Blade Elements. Miscabling the FPGA 3 device does not exclude CPUs from the system, but it compromises the system’s ability to recover from PE failures. Recovery. Correct the reintegration cabling problem as soon as possible. 210: ZCMP-EVT-ECHO-CABLING-ERR-3 Incoming reintegration cables come from different sides of the same NonStop Blade Element.
PAGE 1308
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event-Message Text For slice tracking ID <1>, both echo cables do not come from same side Echo Error State : <2> Echo Status Register : 0x<3> Echo Error Register : 0x<4> Channel <11>, Rcv : 0x<12>, Exp: 0x<13> Xmit: 0x<14> <*IF 20> Channel <21>, Rcv : 0x<22>, Exp: 0x<23> Xmit: 0x<24><*ENDIF> Unconditional Tokens Token Description (page 1 of 2) ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 1309
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-SLICE-ARRAY.ECHCN-XMT(n ) Contents of the transmit register for channel n +1. ZCMP-TKN-SLICE-ARRAY.ECHCN-NUMCHANS Number of channels on the NonStop Blade Element. Cause. Incoming reintegration cables come from different sides of the same NonStop Blade Element.
PAGE 1310
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) ZCMP-TKN-SLICE-ARRAY.ECHCN-NUM(1) <21> token-type ZSPI-TYPBYTE ZCMP-TKN-SLICE-ARRAY.ECHCN-RCV(1) <22> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.ECHCN-EXP(1) <23> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.ECHCN-XMT(1) <24> token-type ZSPI-TYPINT Token Interpretation ZCMP-TKN-SLICE-ARRAY.
PAGE 1311
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Cause. Reintegration cables do not form a ring. (An example of a ring is: A transmits to B, B transmits to C, and C transmits to A.) Effect. CMAP cannot reintegrate one or more PEs or reset one or more NonStop Blade Elements. Miscabling the FPGA 3 device does not exclude CPUs from the system, but it compromises the system’s ability to recover from PE failures. Recovery. Correct the reintegration cabling problem as soon as possible.
PAGE 1312
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Interpretation ZCMP-TKN-SLICE-ARRAY.
PAGE 1313
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Cause. Reintegration cables form a ring, but a NonStop Blade Element is excluded from the ring. Effect. CMAP cannot reintegrate one or more PEs or reset one or more NonStop Blade Elements. Miscabling the FPGA 3 device does not exclude CPUs from the system, but it compromises the system’s ability to recover from PE failures. Recovery. Correct the reintegration cabling problem as soon as possible.
PAGE 1314
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCPU-TKN-SLICE-TRACKING-ID1 Tracking ID of the second NonStop Blade Element in the NonStop Blade Complex. ZCPU-TKN-SLICE-TRACKING-ID2 Tracking ID of the third NonStop Blade Element in the NonStop Blade Complex. Cause. A cabling or hardware error. Effect. CMAP cannot reintegrate one or more PEs or reset one or more NonStop Blade Elements.
PAGE 1315
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCMP-TKN-COMPLEX-ID ID of the affected NonStop Blade Complex. ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the first NonStop Blade Element in the NonStop Blade Complex. ZCPU-TKN-SLICE-TRACKING-ID1 Tracking ID of the second NonStop Blade Element in the NonStop Blade Complex.
PAGE 1316
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Event-Message Text Echo scrub error on slice <1> detected Slice module tracking ID: <2> Echo Status Register : 0x<3> Echo Error Register : 0x<4> Echo info : 0x<5> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTECHO-SCRUB-ERROR (215). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN.
PAGE 1317
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCPU-TKN-CPU ZCMP-TKN-COMPLEX-ID ZCPU-TKN-LID ZCPU-TKN-LID1 ZCPU-TKN-LID2 <1> <2> <3> <4> <5> token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-INT ZSPI-TYP-BOOLEAN ZSPI-TYP-ISO-SEVERITY ZSPI-TYP-INT ZSPI-TYP-INT ZSPI-TYP-BYTE ZSPI-TYP-BYTE ZSPI-TYP-BYTE Token Interpretations ZCMP-TKN-LID1 <> %HFF <10> Z
PAGE 1318
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 217: ZCMP-EVT-LSU-CHANGED Logical synchronization unit (LSU) status changed. (This event is generated for each PE connected to the LSU and its strand.
PAGE 1319
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event-Message Text On CPU <1>, the PE in slice <2> (LID <3>) detected an LSU state change.
PAGE 1320
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-PE1-OLDSTATUS Previous status of the second PE (see Table 25-30). ZCMP-TKN-PE2-STATUS Status of the third PE (see Table 25-30). ZCMP-TKN-PE2-OLDSTATUS Previous status of the third PE (see Table 25-30). ZCMP-TKN-STRAND1-STATUS Status (from the LSU register) of the first strand connecting the LSU to the PE.
PAGE 1321
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 218: ZCMP-EVT-SLICE-CHANGED A NonStop Blade Element tracking ID changed.
PAGE 1322
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Effect. None. Recovery. This is an informational message only; no corrective action is needed. 219: ZCMP-EVT-SLICE-NO-PES No PEs on a NonStop Blade Element are responding.
PAGE 1323
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Recovery. This is an informational message only; no corrective action is needed. 220: ZCMP-EVT-SLICE-MEM-SIZE NonStop Blade Elements in a NonStop Blade Complex have different memory sizes. (This event can be generated for each PE in the NonStop Blade Element.
PAGE 1324
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCPU-TKN-LID Subject token that specifies the LID of the PE reporting inconsistent NonStop Blade Element memory sizes. ZCPU-TKN-SLICE-TRACKING-ID Tracking ID of the first NonStop Blade Element in the NonStop Blade Complex. ZCPU-TKN-SLICE-MEM-SIZE Memory size reported for the first NonStop Blade Element in the NonStop Blade Complex.
PAGE 1325
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) ZCMP-TKN-SLICE-ARRAY.ECHCN-NUM(0) <11> token-type ZSPI-TYPBYTE ZCMP-TKN-SLICE-ARRAY.ECHCN-RCV(0) <12> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.ECHCN-EXP(0) <13> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.ECHCN-XMT(0) <14> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.ECHCN-NUM(1) <21> token-type ZSPI-TYPBYTE ZCMP-TKN-SLICE-ARRAY.ECHCN-RCV(1) <22> token-type ZSPI-TYPINT ZCMP-TKN-SLICE-ARRAY.
PAGE 1326
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-ECHO-ERROR Contents of the FPGA 3 error register (contents of the FPGA 3 status register, which might provide FPGA 3 hardware error information). ZCMP-TKN-ECHO-INFO Additional FPGA 3 information returned for the source NonStop Blade Element in hexadecimal (contents of the echoAdditionalInfo field of the echoInfo structure). ZCMP-TKN-SLICE-ARRAY.
PAGE 1327
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCMP-TKN-COMPLEX-ID ZCPU-TKN-SLICE-TRACKING-ID ZCMP-TKN-SLICE-NUM-PES ZCPU-TKN-SLICE-TRACKING-ID1 ZCMP-TKN-SLICE-NUM-PES1 ZCPU-TKN-SLICE-TRACKING-ID2 ZCMP-TKN-SLICE-NUM-PES2 <1> <2> <3> <4> <5> <6> <7> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-STRING token-type ZSPI-T
PAGE 1328
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Effect. CMAP cannot reintegrate or reset any NonStop Blade Element connected to the NonStop Blade Complex. Recovery. Correct the NonStop Blade Element problem. 223: ZCMP-EVT-COMPLEX-INVALID-7 A NonStop Blade Complex is invalid because two processors report the same LID for a given NonStop Blade Element.
PAGE 1329
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCPU-TKN-LID Subject token that specifies the LID that two processors report. ZCPU-TKN-CPU(0) Subject token that specifies the first processor that reports the LID. ZCPU-TKN-SLICEID NonStop Blade Element ID of the NonStop Blade Element for ZCPU-TKN-CPU(0). ZCPU-TKN-CPU(1) Subject token that specifies the second processor that reports the LID.
PAGE 1330
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Event-Message Text Configuration image error on slice <1> detected Slice module tracking ID : <2> Echo slice 0 Error register : 0x<3> Echo slice 1 Error register : 0x<3> Echo slice 2 Error register : 0x<3> Call Development : 0x<6> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP_EVT_ECHO_CRAM_ERROR (224). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE.
PAGE 1331
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages 300: ZCMP-EVT-SLICE-PWR-REDUNDANCY Power supply redundancy status changed. Potentially critical event: No Action event: No Message sender: CMAP $ZLOG: Yes $0: Yes Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY ZCPU-TKN-SLICEID <1> token-type ZSPI-TYP-BYTE ZCMP-TKN-GMS.ZEMS-DDL-PHYSICAL-ADDRESS.
PAGE 1332
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Token Description (page 2 of 2) ZCMP-TKN-GMS.ZEMS-DDLPHYSICAL-ADDRESS.ZPAMODULE Module identification of the affected NonStop Blade Element. ZCMP-TKN-GMS.ZEMS-DDLPHYSICAL-ADDRESS.ZPA-SLOT Slot identification of the affected NonStop Blade Element. ZCPU-TKN-SLICE-TRACKING-ID NonStop Blade Element tracking ID of the affected NonStop Blade Element.
PAGE 1333
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) ZCMP-TKN-BMC-OLDSTATUS ZCMP-TKN-FAN1-STATUS ZCMP-TKN-FAN1-OLDSTATUS ZCMP-TKN-FAN2-STATUS ZCMP-TKN-FAN2-OLDSTATUS <7> <8> <9> <10> <11> token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZCMP-TKN-FAN3-STATUS ZCMP-TKN-FAN3-OLDSTATUS ZCMP-TKN-TEMP1-STATUS ZCMP-TKN-TEMP1-OLDSTATUS ZCMP-TKN-POWER1-STATUS <12> <13> <14> <15> <16> token-type token-type token-t
PAGE 1334
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCPU-TKN-SLICE-TRACKING-ID NonStop Blade Element tracking ID of the affected NonStop Blade Element. ZCMP-TKN-BMC-STATUS Indicates whether Baseboard Management Controller (BMC) communications are functioning normally. ZCMP-TKN-BMC-OLDSTATUS Indicates whether BMC communications were functioning normally. ZCMP-TKN-FAN1-STATUS Status of the first fan (see Table 25-31 on page 25-106).
PAGE 1335
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-32. ZCMP-TKN-TEMPn-[OLD]STATUS Values Value Meaning ZCMP-ENM-TEMP-OK Temperature is within specification. ZCMP-ENM-TEMP-WARNING Temperature is near critical. ZCMP-ENM-TEMP-CRITICAL Temperature is critical. ZCMP-ENM-TEMP-FAULT Temperature is past critical - BMC shutdown. ZCMP-ENM-TEMP-ACCESS-ERR Temperature access error occurred. Table 25-33.
PAGE 1336
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY ZCPU-TKN-SLICEID <1> token-type ZSPI-TYP-BYTE ZCMP-TKN-GMS.ZEMS-DDL-PHYSICAL-ADDRESS.ZPA-GROUP <2> token-type ZSPI-TYP-STRING ZCMP-TKN-GMS.ZEMS-DDL-PHYSICAL-ADDRESS.ZPA-MODULE <3> token-type ZSPI-TYP-STRING ZCMP-TKN-GMS.ZEMS-DDL-PHYSICAL-ADDRESS.
PAGE 1337
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZCMP-TKN-SLED-STATUS Status of the LED. ZCMP-TKN-SLED-OLDSTATUS Previous status of the LED. Table 25-34. ZCMP-TKN-LED-ID Values Value Meaning ZCMP-ENM-LED-SLICE-SYS NonStop Blade Element system LED. ZCMP-ENM-LED-SLICE-SYS-LOC NonStop Blade Element system locator LED. ZCMP-ENM-LED-SLICE-FRONT NonStop Blade Element front LED. ZCMP-ENM-LED-SLICE-REAR NonStop Blade Element rear LED.
PAGE 1338
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCMP-TKN-LSU-TRACKING-ID ZCMP-TKN-GMS ZCMP-TKN-LSU-RAIL1-STATE ZCMP-TKN-LSU-RAIL1-OLDSTATE ZCMP-TKN-LSU-RAIL2-STATE ZCMP-TKN-LSU-RAIL2-OLDSTATE <1> <2> <3> <4> <5> <6> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-STRING token-type ZSPI-TYP-STRING token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-ENU
PAGE 1339
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Cause. The power supply status of an LSU changed. Effect. None. Recovery. Check power supply and repair it if necessary. 304: ZCMP-EVT-LSU-LED-CHANGE Fault LED status changed.
PAGE 1340
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Description (page 2 of 2) ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCMP-TKN-LSU-TRACKING-ID Tracking ID of the affected LSU. ZCMP-TKN-GMS.ZEMS-DDLPHYSICAL-ADDRESS.ZPA-GROUP Group identification of the affected LSU. ZCMP-TKN-GMS.ZEMS-DDLPHYSICAL-ADDRESS.ZPA-MODULE Module identification of the affected LSU. ZCMP-TKN-GMS.ZEMS-DDLPHYSICAL-ADDRESS.ZPA-SLOT Slot identification of the affected LSU.
PAGE 1341
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Token Interpretations TOKENPRESENT(ZCPU-TKN-CPU) <11> TOKENPRESENT(ZCPU-TKN-LID) <12> TOKENPRESENT(ZCPU-TKN-LSU-TRACKING-ID) <13> Event-Message Text FWUPDT : Firmware scrub start Firmware module : <1> Slice module tracking ID : <2> <*IF 11>CPU : <3><*ENDIF> <*IF 12>LID : <4><*ENDIF> <*IF 13>LSU Tracking ID : <5><*ENDIF> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 1342
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-36. ZCMP-TKN-FIRMWARE-MODULE Values Value Meaning ZCMP-ENM-FW-ECHO FPGA 3 ZCMP-ENM-FW-IPF-HDR PAL and SAL Firmware Header ZCMP-ENM-FW-BMC-HDR BMC Firmware Header Conditional Tokens Token Description ZCPU-TKN-CPU Subject token that specifies the processor where the module that was scrubbed resides. ZCPU-TKN-LID LID of the PE on the NonStop Blade Element. ZCMP-TKN-LSU-TRACKING-ID Tracking ID of the affected LSU.
PAGE 1343
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Token Interpretations TOKENPRESENT(ZCPU-TKN-CPU) <11> TOKENPRESENT(ZCPU-TKN-LID) <12> TOKENPRESENT(ZCPU-TKN-LSU-TRACKING-ID) <13> Event-Message Text FWUPDT : Firmware scrubbed Firmware module : <1> Slice module tracking ID : <2> <*IF 11>CPU : <3><*ENDIF> <*IF 12>LID : <4><*ENDIF> <*IF 13>LSU Tracking ID : <5><*ENDIF> Scrub Result : <6> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 1344
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Cause. A scrub completed on a firmware module. Effect. Depends on the result. The firmware might need to be scrubbed again or updated. Recovery. If there is a problem, contact your service provider. 402: ZCMP-EVT-FIRMW-UPDATE-START Firmware update started.
PAGE 1345
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMP-EVTFIRMW-UPDATE-START (402). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-TRUE. ZEMS-TKN-ISO-SEVERITY Value is ZEMS-VAL-SEVERITY-INDETERMIN. ZCMP-TKN-FIRMWARE-MODULE Module ID for the firmware that was updated (see Table 25-36 on page 25-113).
PAGE 1346
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZEMS-TKN-ISO-SEVERITY ZCMP-TKN-FIRMWARE-MODULE ZCPU-TKN-SLICE-TRACKING-ID ZGRD-TKN-FILENAME ZCMP-TKN-FW-UPDATE-RESULT <1> <2> <3> <7> token-type ZSPI-TYP-INT token-type ZSPI-TYP-BOOLEAN token-type ZSPI-TYP-ISOSEVERITY token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-FNAME token-type ZSPI-TYP-ENUM Conditional Tokens ZCPU-TKN-CPU ZCPU-TKN-LID ZCMP-TKN-
PAGE 1347
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-38. ZCMP-TKN-FW-UPDATE-RESULT Values Value Meaning ZCMP-ENM-FW-UPDATE-OK Updated succeeded. ZCMP-ENM-FW-UPDATE-FILE File format error occurred. ZCMP-ENM-FW-UPDATE-MILLICODE Millicode error occurred. Conditional Tokens Token Description ZCPU-TKN-CPU Subject token that specifies the processor where the module that was updated resides. ZCPU-TKN-LID LID of the PE on the NonStop Blade Element.
PAGE 1348
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Conditional Tokens ZCPU-TKN-CPU1 ZCPU-TKN-LID ZCMP-TKN-LSU-TRACKING-ID <6> token-type ZSPI-TYP-INT <7> token-type ZSPI-TYP-BYTE <8> token-type ZSPI-TYP-STRING Token Interpretations TOKENPRESENT(ZCPU-TKN-CPU) <11> TOKENPRESENT(ZCPU-TKN-LID) <12> TOKENPRESENT(ZCPU-TKN-LSU-TRACKING-ID) <13> Event-Message Text FWUPDT : Firmware update program failed CPU : <1> PIN : <2> Firmware module : <3> File Name : <4> Slice module tracking ID : <5>
PAGE 1349
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Table 25-39. ZCMP-TKN-FAIL-REASON Values Value Meaning ZCMP-ENM-FW-FAIL-CPU CPU hosting update process failed. ZCMP-ENM-FW-FAIL-ABEND Update process abended. Conditional Tokens Token Description ZCPU-TKN-CPU1 Subject token that specifies the processor where the module that was updated resides. ZCPU-TKN-LID LID of the PE on the NonStop Blade Element. ZCMP-TKN-LSU-TRACKING-ID Tracking ID of the affected LSU. Cause.
PAGE 1350
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Event-Message Text RCVDUMP : RCVDUMP with PARALLEL option failed CPU : <1> LID : <2> Slice : <3> Slice module tracking ID : <4> File Name : <5> Process Launch error : <6> Completion Code : <7> Termination Code : <8> Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZCMPEVT-RCVDUMP-FAILURE (500). ZEMS-TKN-EMPHASIS Value is ZSPI-VAL-FALSE.
PAGE 1351
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) 600: ZCMP-EVT-SAD-PROCESS-FAILED The Slow Access Device (SAD) process either could not be launched or failed after being launched. Note. In every processor where CMAP is running, CMAP tries to launch a SAD process named $ZSDnn (where nn is the processor number).
PAGE 1352
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Messages Conditional Token Token Description ZCMP-TKN-RETRIES Number of times CMAP tried to restart the SAD process without receiving updated information from it (maximum is four). Table 25-40. ZCMP-TKN-SAD-FAILURE-TYPE Values Value Meaning ZCMP-ENM-SAD-LAUNCH-FAIL Launch of SAD process failed. ZCMP-ENM-SAD-STOPPED SAD process stopped or abended. Cause.
PAGE 1353
Messages Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) Figure 25-2. CMAP Tries to Restart SAD Process (ZCMP-TKN-SAD-FAILURETYPE is ZCMP-ENM-SAD-STOPPED) Start retries = 0 CMAP tries to restart SAD process Yes SAD provides info? No retries < 4 ? Yes retries = retries + 1 No Stop VST001.
PAGE 1354
Complex Manager Auxiliary Process (CMAP) Event Messages (ZCMP) HP NonStop Operating System Event Management Programming Manual—520372-020 25-126 Messages
PAGE 1355
26 Dynamic Link Library (DLL) Event Messages (ZDLL) DLL event messages are generated by the ZDLL subsystem on H-series systems during the preloading of public DLLs while the processor starts. The subsystem ID displayed by these messages includes ZDLL as the subsystem name.
PAGE 1356
Common Definitions Dynamic Link Library (DLL) Event Messages (ZDLL) Table 26-1. DLL Event Messages (page 2 of 2) Event Number and Symbolic Name Description 105: ZDLL-EVT-IMP-IMP-PROBLEM The specification in the ZREG file’s implicit_import statement did not match that of the ZIMPIMP file that was loaded for the processor. 106: ZDLL-EVT-PRELOAD-SUMMARY Preloading completed. The specified numbers of public DLLs were preloaded successfully, failed preload, or were discarded.
PAGE 1357
Dynamic Link Library (DLL) Event Messages (ZDLL) Subsystem Programmatic Interface (SPI) Standard Definitions Subsystem Programmatic Interface (SPI) Standard Definitions SPI standard definitions that have a specific meaning for DLL events are listed in Table 26-2. SPI standard definitions are described in detail in the SPI Programming Manual. Table 26-2.
PAGE 1358
Dynamic Link Library (DLL) Event Messages (ZDLL) Dynamic Link Library (ZDLL-) Definitions Token Description ZEMS-TKN-EVENTNUMBER Event number for each ZDLL event message. ZEMS-TKN-ACTION-NEEDED Occurs in event message pairs. The first message indicates that operator intervention is needed (ZSPI-VALTRUE), and the second message indicates that operator intervention is completed (ZSPI-VAL-FALSE).
PAGE 1359
Description of ZDLL Event Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Table 26-4. ZCPU-TKN-YOS-MODEL Values Value Processor Model ID Processor 0 (with processor type 10) NSE-A NS16000 Simple Tokens and Structured Tokens These tokens are described in the event-message descriptions. Description of ZDLL Event Messages The ZDLL event messages are described in detail on the following pages. The descriptions are in ascending order by event number.
PAGE 1360
Recovery Action Requiring Vendor Support Dynamic Link Library (DLL) Event Messages (ZDLL)       A box contains a list of tokens that can appear in the event message. Header and other common tokens are not included in the list. For descriptions of these tokens, see Section 2, Header and Common Tokens. Tokens in an actual event message will not necessarily appear in the order in which they are listed in the box.
PAGE 1361
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Message sender: PubLibsPreload_ system library procedure Message sent to TMDS collector? No Message sent to TMS collector? No Unconditional Tokens ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-INT ZCPU-TKN-CPU token-type ZSPI-TYP-UINT ZDLL-TKN-STATEMENT-ATTR-STRING <1> token-type ZSPI-TYP-STRING ZDLL-TKN-FILE <2> token-type ZSPI-TYP-STRING Conditional Tokens ZDLL-TKN-ERRORCODE ZDLL-TKN-STATEMENT-ATTR-STR2 <3> token-type ZSPI-TYP-INT <4> token-typ
PAGE 1362
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Recovery. If the problem occurred while loading the system, revert to a previously working system image (SYSnn and ZDLLrrr subvolumes). If you modified the ZREG or ZREGPTR file, revert to the original file and reboot the system. Otherwise, recovery depends on the file-system error that ZDLL-TKN-ERRORCODE or ZDLL-TKN-STATEMENT-ATTR-STR2 specifies.
PAGE 1363
Dynamic Link Library (DLL) Event Messages (ZDLL) Messages Cause. Either:    The required public DLL was not specified in the ZREG file. The required public DLL was specified incorrectly in the ZREG file (as message 107: ZDLL-EVT-PARSER on page 26-21 might report). An error (which message 102: ZDLL-EVT-DLL-FAIL on page 26-10 reports) occurred while preloading the required public DLL. Effect. The required public DLL is not preloaded.
PAGE 1364
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) 102: ZDLL-EVT-DLL-FAIL The specified public DLL in the ZREG file failed to preload; process creation error and detail are specified.
PAGE 1365
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Event-Message Text Public DLL file <1> preload failed: process creation error <2>, detail <3>. [ Export digest mismatched: expected <4>, found <5>. ] [ Export digest missing in zreg file. ] [ Warning: link timestamp mismatched: expected <6>, ] [ found <7>. ] [ Warning: link timestamp missing in ZREG file. ] [ Warning: update timestamp mismatched: expected <8>, ] [ found <9>. ] [ Warning: update timestamp missing in ZREG file.
PAGE 1366
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Token Description (page 2 of 2) ZDLL-TKN-LINK-MISG Link timestamp for the public DLL was missing from its ZREG file specification. ZDLL-TKN-UPDATE-EXPECTED Update timestamp that the ZREG file specified for the public DLL. ZDLL-TKN-UPDATE-FOUND Actual update timestamp for the public DLL. ZDLL-TKN-UPDATE-MISG Update timestamp for the public DLL was missing from its ZREG file specification.
PAGE 1367
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZCPU-TKN-CPU ZDLL-TKN-FILE token-type ZSPI-TYP-INT token-type ZSPI-TYP-UINT <1> token-type ZSPI-TYP-STRING Conditional Tokens ZDLL-TKN-DISCARDED ZDLL-TKN-LINK-EXPECTED ZDLL-TKN-LINK-FOUND ZDLL-TKN-LINK-MISG ZDLL-TKN-UPDATE-EXPECTED ZDLL-TKN-UPDATE-FOUND ZDLL-TKN-UPDATE-MISG ZDLL-TKN-MOD-EXPECTED ZDLL-TKN-MOD-FOUND ZDLL-TKN-MOD-MISG token-type ZSPI-TYP-INT <2> token-type ZSPI-TYP-STRING <3> token-type ZSP
PAGE 1368
Dynamic Link Library (DLL) Event Messages (ZDLL) Messages Conditional Tokens Token Description ZDLL-TKN-DISCARDED Indication that the public DLL was discarded because of insufficient space in the public DLL table. ZDLL-TKN-LINK-EXPECTED Link timestamp that the ZREG file specified for the public DLL. ZDLL-TKN-LINK-FOUND Actual link timestamp for the public DLL. ZDLL-TKN-LINK-MISG Link timestamp for the public DLL was missing from its ZREG file specification.
PAGE 1369
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Effect. If the public DLL file preloaded successfully, it can be used by programs and DLLs that require it. If the public DLL file was discarded, it is not preloaded and cannot be used by programs and DLLs that require it. Message 106: ZDLL-EVT-PRELOAD-SUMMARY on page 26-19 reports the number of discarded entries. Recovery.
PAGE 1370
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Recovery. If the problem occurred while loading the system, revert to a previously working system image (SYSnn and ZDLLrrr subvolumes). If you modified the ZREG file, revert to the original file and reboot the system. If this error occurs with the original ZREGPTR and ZREG files that DSM/SCM installs, contact your service provider (see Recovery Action Requiring Vendor Support on page 26-6).
PAGE 1371
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Event-Message Text Problems seen in implicit_import statement. { Export digest mismatched: expected <1>, found <2> } { } { Export digest missing in zreg file. } [ Warning: link timestamp mismatched: expected <3>, ] [ found <4>. ] [ Warning: link timestamp missing in ZREG file. ] [ Warning: update timestamp mismatched: expected <5>, ] [ found <6>. ] [ Warning: update timestamp missing in ZREG file.
PAGE 1372
Dynamic Link Library (DLL) Event Messages (ZDLL) Messages Token Description (page 2 of 2) ZDLL-TKN-UPDATE-MISG Update timestamp for the ZIMPIMP file was missing from the implicit_import statement in the ZREG file. ZDLL-TKN-MOD-EXPECTED Mod (modification) timestamp that the ZREG file specified for the ZIMPIMP file in the implicit_import statement. ZDLL-TKN-MOD-FOUND Actual mod (modification) timestamp for the ZIMPIMP file.
PAGE 1373
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) 106: ZDLL-EVT-PRELOAD-SUMMARY Preloading completed. The specified numbers of public DLLs were preloaded successfully, failed preload, or were discarded.
PAGE 1374
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Conditional Tokens Token Description ZDLL-TKN-DLL-COUNT-EXPECTED Number of public DLLs that the ZREG file specified (if any) or the default number. ZDLL-TKN-DLL-COUNT-FOUND Number of successfully parsed DLL entries in the ZREG file. ZDLL-TKN-COUNT-FAILED Number of public DLLs that failed to preload.
PAGE 1375
Messages Dynamic Link Library (DLL) Event Messages (ZDLL)  Message 103: ZDLL-EVT-DLL-SUCCESS on page 26-12 is issued, reporting either that the DLL preloaded successfully or that it was discarded. Note. The PLINSTL command list is another way to show which public DLLs preloaded successfully. Recovery. If good entries were discarded, increase the value of dll_count in the ZREG file by at least the value of ZDLL-TKN-GOOD-DISCARDS.
PAGE 1376
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Event-Message Text Problem found on line <1> column <2> of <3>. [ <4> ] [ <5> ] [ dll_count statement not found before the first dll statement in zreg. The default (<6>) is being used. ] [ dll_count has already been set. This count (<7>) is being ignored. ] [ Specified dll_count value (<8>) is too large, using max (<9>).] [ Read error is <10>. ] Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message.
PAGE 1377
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Token Description (page 2 of 2) ZDLL-TKN-TOOBIG-COUNT Specification for dll_count that was too large to support (so that a max is used instead). ZDLL-TKN-MAXCOUNT Maximum dll_count that can be supported. ZDLL-TKN-READ-ERR A file-system error number reported by READX through FILE-GETINFO_. Cause. The direct cause is that the ZREG or ZREGPTR file contains the specified defect at the specified location.
PAGE 1378
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDLLEVT-PRELOAD-INTERNAL (108). ZCPU-TKN-CPU Subject token that specifies the processor that is reporting the event. ZDLL-TKN-INTERNAL-ERROR Internal preload error number. Conditional Tokens Token Description ZDLL-TKN-ERRORCODE Error number associated with the specified internal preload error number. Cause. An internal preloading problem.
PAGE 1379
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDLL-EVTEMPTY-ZREGPTR (109). ZCPU-TKN-CPU Subject token that specifies the processor that is reporting the event. ZDLL-TKN-FILE Fully qualified name of the ZREGPTR file. Cause. The ZREGPTR file was empty. Effect. The SYSnn subvolume is treated as the public DLL subvolume, which is expected to contain the ZREG file and the public DLLs.
PAGE 1380
Messages Dynamic Link Library (DLL) Event Messages (ZDLL) Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDLL-EVT-NOPUB-DLLS (110). ZCPU-TKN-CPU Subject token that specifies the processor that is reporting the event. Cause. Reported by a previous event, such as:     100: ZDLL-EVT-OPEN-ERR on page 26-6 104: ZDLL-EVT-NO-IMP-IMP on page 26-15 105: ZDLL-EVT-IMP-IMP-PROBLEM on page 26-16 108: ZDLL-EVT-PRELOAD-INTERNAL on page 26-23 Effect.
PAGE 1381
Dynamic Link Library (DLL) Event Messages (ZDLL) Messages Event-Message Text Warning: The scan marker was not found in <1>. Unconditional Tokens Token Description ZEMS-TKN-EVENTNUMBER Event number for this message. Value is ZDLL-EVT-NOSCAN-MARKER (111). ZCPU-TKN-CPU Subject token that specifies the processor that is reporting the event. ZDLL-TKN-FILE Fully qualified name of the ZREGPTR file. Cause. The ZREG file was not produced by PLINSTL, which inserts the scan marker. Effect.
PAGE 1382
Index A Abbreviations -xxiv/-xxx Action events 1-4 B Blade Complex 5-1 Blade Element 5-1, 25-1 C CMAP event messages 25-1/25-121 Collector ($0 process) 1-1 Common tokens 2-3/2-4 Complex manager AP event messages 25-1/25-121 Configuration services event messages 24-1/24-66 Consumer distributor 1-1 Correctable memory error 5-23/5-27 CPU-number token 2-1 Critical events 1-4 Critical-event token 2-1 D DBIOPROC event messages 21-1 DBIOPROC subsystem event messages 21-1/21-15 Direct Bulk I/O Support Procedures
PAGE 1383
F Index in ZSMD (SCSI module driver) event messages 20-5 in ZSNT (ServerNet error handler) event messages 19-7 in ZSRL (shared run-time library) event messages 14-5 in ZSTO (storage subsystem) event messages 23-9/23-10 in ZTAP event messages reported by labeled-tape server 9-9 reported by tape process 10-8/10-9 in ZXIO (XIO subsystem) event messages 15-4 tokens definition files for 1-2 in event-message header section 2-1/2-2 Events action 1-4 critical 1-4 managing 1-2 names of 1-3 noncritical 1-4 numbers
PAGE 1384
P Index P Process access ID (PAID) token 2-2 Process identification number (PIN) token 2-2 Processor complex 5-1 Processor event messages 5-1/5-50 Processor-type tokens 2-3 S SCSI module driver event messages 20-1, 20-47 ServerNet error handler event messages 19-1/19-89 Service event logger ($ZLOG) 1-1 Shared run-time library event messages 14-1/14-41 Slice 5-1, 25-1 Software-release version token 2-1 SPI See Subsystem Programmatic Interface (SPI) SRL event messages 14-1/14-41 Storage subsystem event mes
PAGE 1385
T Index in event-message header section 2-1/2-2 standard types of 2-5/2-6 System clock event messages 8-1/8-24 System monitor event messages 7-1/7-23 System-component token 2-1 T Tape process event messages 10-1/10-160 Timestamp for message generation token 2-1 Timestamp for message logging token 2-2 Tokens common 2-3/2-4 header 2-1/2-2 Subsystem Programmatic Interface (SPI) 2-5/2-6 Token-definition files 1-2 U Uncorrectable memory errors ZCPU-EVT-UCME 5-27/5-29 ZGIO-EVT-IIOIOCUCME 3-29/3-30 ZGIO-EVT-II
PAGE 1386
Z Index 5 25-83/25-85 INVALID 25-85/25-86 VALID 25-86/25-87 CONNECT-ERR 25-96/25-98 INIT-ERROR 25-49/25-51 SCRUB-ERROR 25-87/25-88 STATUS 25-61/25-63 FIRMWSCRUBBED 25-114/25-116 SCRUB-START 25-112/25-114 UPDATEDONE 25-117/25-119 FAILED 25-119/25-121 START 25-116/25-117 HSS-ERROR 25-43/25-44 INTERNAL-ERROR 25-32/25-33 LED-CHANGED 25-88/25-89 LSUCHANGED 25-90/25-92 LED-CHANGE 25-111/25-112 PWR-STATUS 25-109/25-111 MEMCOPY-ERROR 25-54/25-55 OPERATION-ABORTED 25-37/25-39 PECANT-RESET 25-35/25-37 IN-ERROR 25-5
PAGE 1387
Z Index RAPIDCYCLE-DONE 5-32/5-33 RENDEZVOUS-FAULT 5-43/5-45 SHOUT-RECD-NO-PWARN 5-18/5-19 SNIFFERACTIVATED 5-34 REDIRECTED 5-34/5-35 SCRUBBED 5-35/5-36 SUSPENDED 5-33 SOFTWARE-HALT 5-22/5-23 UCME 5-27/5-29 UCODE-COUNTERERROR 5-14/5-16 STATUS 5-11/5-13 UNCPANDRV-STATISTICS 5-45/5-50 UP 5-8/5-9 VRO 5-38/5-43 ZDIO event messages 21-1/21-15 ZDIO-EVTHW-XSUM-SW-FIXED 21-8/21-9 QUARANTINEEND 21-11/21-12 START 21-9/21-11 SECTOR-XSUM 21-12/21-13 STRUCTUREDRSN 21-14/21-15 XSUM 21-13/21-14 ZERROR-RTRN-RCVD 21-6/21-
PAGE 1388
Z Index NON-PRSTNT-PROCABEND 24-43/24-44 NO-TEMPNAME 24-30/24-31 OUTPUTAVAILABLE 24-65 UNAVAIL 24-64 PARAMMSG-FAIL-SEND 24-61 PROCESS-LAUNCH-FAIL 24-45/24-46 PROC-PRSTNT-THRES 24-46/24-47 PRSTNT-PROCABEND 24-42/24-43 STOPPED 24-41/24-42 PURGE-RENAM 24-31 RESERVED-NAME-FAIL 24-40/24-41 RLBACK-LOSS-ERR 24-35 SPI-STOP-OPEN-FAILED 24-59 SSM-CHECKIN-FAILED 24-48/24-49 STRTMSG-FAILOPEN 24-57 SEND 24-58 SUBTYPE-NOT-SUPPORTED 11-105 TAKEOVER 24-63/24-64 UNKNOWN-CRUDELETION 24-14/24-15 UNXPCTD-CRUCNF 24-17/24-18 S
PAGE 1389
Z Index CONFIG-RECORD-FETCH 11-160 CURRENT-STATE 11-130/11-131 DEFAULT-CACHESIZES 11-102/11-103 DETECTED-HUNG-IO 11-166/11-167 DP2DRVR-INTERNALERR 11-87/11-89 DP2ABORTED-DUMP 11-133/11-134 BAD-FILE-BLOCK 11-94/11-96 DATA-LOSS 11-96/11-97 DPSHARE-SIZE 11-121 DRIVERMANGLE-CALLED 11-163/11-164 MEMORY-LOW 11-164 DRVDOWN 11-64 ERR-EXT 11-66/11-68 UP 11-68/11-69 DV-ADPINFOFROMTMFLIB 11-107/11-108 EIO-OWNERSHIP-ERR 11-89 ENV-RPT 11-90 ERR-ELEM 11-65/11-66 EXCEPTERR 11-139/11-141 ERR-ELEM 11-69/11-70 ERR-EXT 11-7
PAGE 1390
Z Index MESSAGE-NULL 11-165/11-166 TIMESTAMP-DRVDOWN 11-100/11-101 UNABLEREAD-DIR-LABEL 11-81/11-82 WRITE-VLAB 11-82/11-83 UNEXPECTED-MSG-ERROR 11-106 UNEXP-INTR 11-83/11-84 UNKNOWN-LABEL 11-108 UPGRADE-DONE 11-141/11-143 UPPROCESS-TERMINATED 11-86 WORKPOOL-USAGE 11-123/11-124 WRITE-FAILURE 11-97/11-99 WRTVFY-MODEOFF 11-93 ON 11-92 ZDSK-EVT-CPU-SWITCHCMN 11-32/11-33 ZDSK-EVT-DEV-BUSY 11-45/11-46 ZDSK-EVT-DEV-CMDINCOMP 11-44/11-45 ZDSK-EVT-DEV-CMDTIMEOUT 11-43/11-44 ZDSK-EVT-DEV-IF-ERR 11-48/11-49 ZDSK-EVT
PAGE 1391
Z Index IIOOWNERSHIPERROR 3-34/3-35 IIOPADIN 3-35/3-36 IIOPADINNOPADO 3-62/3-63 IIOPADINOSTI 3-36/3-37 IIOPROTECTVIOLATION 3-37/3-38 IIOSTIFAIL 3-38/3-39 IIOSVIANDSTI 3-40 IIOUCMEDATA 3-41/3-42 IIOZEROBYTEREAD 3-42/3-43 IIOZEROBYTEWRITE 3-43/3-44 INTCCL 3-44 INTERRUPTPENDING 3-61/3-62 IOTRACE 3-45 MULTICCLMESS 3-60 SCHANLBADCOMMAND 3-46 SCHANLBADRETURN 3-63 SCHANLBADSTAT 3-47 SCHANLDEVRECON 3-48 SCHANLIOCABSENT 3-50 SCHANLIOCUCME 3-49 SCHANLRANK0TIMEOUT 3-51 SCHANLRANK1TIMEOUT 3-52 SCHANLRCIERROR 3-53 SCH
PAGE 1392
Z Index SEQUENCE-ERRS 16-32/16-33 SPURIOUS-ACKS 16-31/16-32 SUPPRESS-MSG 16-26/16-27 UNEXP-PKT-RCVD 16-38/16-39 ZKRN event messages 17-1/17-12 ZKRN-EVTALLPROC-ADDED 17-9/17-10 CONFIGBACKOUT-FAILED 17-8/17-9 KRN-ADDED 17-10/17-11 MISMATCH 17-6/17-7 DCT-ALTEREDMEDIUM 17-12 SMALL 17-11 POWER-DOWN 17-8 ZMON event messages 7-1/7-23 ZMON-EVTCOUPSTARTED 7-11/7-12 STARTUPERROR 7-12/7-13 WARNING 7-13/7-14 INITCICREATEERR 7-14/7-15 INITCIFOPENERR 7-15/7-16 OSIMAGE 7-7/7-8 OSSINSTALLERR 7-20 STARTED 7-16/7-17 STARTE
PAGE 1393
Z Index USRCHECKPOINT 18-34/18-35 FREEOWNER 18-36/18-37 FREESTATE 18-35/18-36 ZNSK event messages 13-1/13-43 ZNSK-EVTBACKUPFAIL-OFTEN 13-13/13-14 INVALID-STATE 13-14/13-15 NOT-RUNNING 13-17/13-18 STOPPED 13-15/13-16 CREATEBACKUP-FAILED 13-10/13-11 DBGMON-REG 13-27/13-28 DBGR-NOT-RESTARTED 13-23 DFLT-DBGRCREAT-ERR 13-20/13-21 IO-ERR 13-21/13-22 TIMEOUT 13-22/13-23 DSDEREG-ERR 13-26 NO-MEMORY 13-25 REG-ERR 13-26/13-27 IBIP-INV-EXCEPTION 13-20 INTERNAL-ERROR 13-9/13-10 INVALIDDIALECT 13-16 REQUEST 13-16/13-1
PAGE 1394
Z Index SVNET-HNDL-ERR 20-44/20-45 SVT-ERROR 20-40 UNLOADED 20-32/20-33 DEVBUSY 20-27 CMDINCOMP 20-26/20-27 TIMEOUT 20-25/20-26 DATA-OVERRUN 20-30/20-31 INTF-ERR 20-28/20-29 RESET 20-29/20-30 SCSI-STATUS 20-28 SEL-TIMEOUT 20-24/20-25 FUNCT-CODE-INVALID 20-12 MDR-FIELD-CONTENT-ERR 20-13 MDINTERNAL-ERROR 20-14/20-15 MB-SM-ERR 20-16 STRUCT-ERR 20-15/20-16 SYNDROMEUNKNOWN 20-16/20-17 SCSI-BUSRESET 20-35/20-36 RESET-IN 20-36/20-37 SVNETBUF-INVALID 20-24 CPURCV-ERR 20-20 TIMEOUT 20-18/20-19 CTLRHAD-ERR 20-21/20
PAGE 1395
Z Index RUNON 19-70/19-71 SELFCHECK 19-79/19-80 LOLA 19-73/19-74 MINOR-PORT-ERR 19-67/19-68 NATMWRT-DURINGSLEEP 19-58/19-59 OFP-THRESH 19-76/19-77 OVRUNCRC-ERRORS 19-29/19-30 ERRORS 19-26/19-27 TPBCRC-ERRORS 19-30/19-31 ERRORS 19-27/19-28 PKT-TOSS 19-80/19-81 PORTERR-THRESH 19-74/19-75 QUEUE-FULL-ERRORS 19-53/19-54 RCV-UGLY-ERRORS 19-10/19-11 READ-OVERFLOWERRORS 19-52/19-53 RUNTCRC-ERRORS 19-23/19-24 ERRORS 19-21/19-22 TPBCRC-ERRORS 19-25/19-26 ERRORS 19-22/19-23 SINGLE-SYMBOL 19-86/19-87 SNET-INFO 19-63
PAGE 1396
Z Index GINFO-ERR 14-30/14-31 INFO-ERR 14-22/14-23 ZTILTGINFO-SRL-ERR 14-34/14-35 LOCATED 14-31/14-32 LOC-ERR 14-10/14-11 OPEN-ERR 14-36/14-37 READ-ERR 14-14/14-15 RECV-ERR 14-29/14-30 SEARCH-ERR 14-28/14-29 SECUR-ERR 14-11/14-12 START-ERR 14-26/14-27 STRUCT-ERR 14-13/14-14 TABLE-SRL-ERR 14-35/14-36 ZSTO event messages 23-1/23-114 ZSTO-EVTABANDON-FW 23-92 ABORT 23-34/23-35 ACCESS-LIST 23-88/23-89 ADAPTER-AUTOFAIL 23-63 RETRY 23-64 ADD 23-58/23-59 ALLOWOPENS 23-35/23-36 ALTER 23-37/23-38 BACKUP-START-ERROR
PAGE 1397
Z Index TIMEOUT 23-107/23-108 POSTCOMPLETE 23-70/23-71 COORDNTIMEOUT 23-109/23-110 FAILED 23-72/23-73 POWER-ACTION 23-94/23-95 PRE-COORDNTIMEOUT 23-108/23-109 PRIMARY 23-40/23-41 PROCESS-IO-ERROR 23-76/23-77 REBUILDDFS 23-41/23-42 RECONCILECONFIG 23-102 SMF 23-101/23-102 REFRESH 23-43/23-44 RENAME 23-44/23-45 REPLACE 23-87/23-88 REPLACEBOOT 23-45/23-46 RESET 23-46/23-47 SERVER-ERROR 23-75/23-76 SMFINCONSISTENCY 23-104/23-105 LAUNCH-FAILURE 23-103, 23-105/23-107 SPARE 23-47/23-48 START 23-49/23-50 START-SP
PAGE 1398
Z Index CORRECTED 10-95/10-97 UNCORRECTED 10-97/10-98 DENSITYCHANGED 9-73/9-74 DENSITYUSED 9-75/9-76 DEVICEINTF-ERROR 10-123/10-125 NOTRESPONDING 10-135/10-136 DEVASSGN-ELSEWHERE 10-144 BUSY 10-18 CMDINCOMP 10-19 TIMEOUT 10-19/10-20 IF-ERROR 10-16/10-17 RESET 10-15/10-16 SCSI-STATUS 10-17/10-18 SEL-TIMEOUT 10-20/10-21 DRIVE-PWR-OFF 10-100/10-101 D-PATH-PARITYERROR 10-98/10-100 EIO-BAD 10-147/10-148 EQUIP-CHECK 10-137/10-138 ERASE-FAILED 10-101/10-102 ERROR-INJECTION 10-29 ESMTAPEONLINE 9-124 EXCEPT-ERR 9-
PAGE 1399
Z Index PON-CMN 10-27/10-29 PROCTECTERR 9-33/9-34 READRECEIVEERR 9-50 READ-RETRIED 10-54/10-55 RECOVERYCOMPLETION 10-34/10-35 REJECTDEVICE 9-72 REJECTMOUNT 9-70 REQBLP 9-24/9-26 REQNL 9-23/9-24 REQUNKNOWN 9-27/9-28 RUNAWAY-TAPE 10-112/10-113 SECTOR-XSUM 10-23/10-24 SETBURST-EIO 10-156/10-157 HOLDOFF-EIO 10-157/10-158 SHORT-WRITE 10-113/10-114 SKABORTED-CMND 10-37/10-38 BLANK-CHK 10-39/10-40 COPY-ABORT 10-38/10-39 DATA-PRTCT 10-40/10-41 EQUAL 10-36/10-37 HW-ERR 10-42/10-43 ILLEGAL-REQUEST 10-42 MEDIUM-ERR
PAGE 1400
Special Characters Index CTLRAVT-ERR 10-67 HAD-ERR 10-64 HW-ERR 10-63 NO-AVT 10-61/10-62 PATH-DOWN 10-64/10-65 POWER-FAIL 10-65/10-66 SVC-IF-ERR 10-60 TAPECOMACCEPT 9-56 TAPECOMREJECT 9-55 TAPEDISMOUNTED 9-79 TAPEMODECHANGED 9-74/9-75 TAPEMODEUSED 9-76/9-77 TAPEOPENED 9-57/9-58 TAPE-STACK 10-159/10-160 TERMSTAT-UNKNOWN 10-116/10-117 TIMEOUTS-EXCEEDED-CMN 10-30 TMFATAPEONLINE 9-61/9-62 TMFTAPEONLINE 9-63 TPTMNOTCONFIGURED 9-130/9-131 TPTMTIMEOUT 9-129 TPTMWRITEREAD 9-128 UNEXPECTEDINT 10-158/10-159 INT-CMN