SNAX/XF and SNAX/APN Event Management Programming Manual Abstract This reference manual describes the EMS event messages generated by the SNAX/XF and SNAX/APN subsystems on Compaq NonStop™ Himalaya S-series servers. Product Version SNAX/XF G06 SNAX/APN G06 Supported Releases This manual supports the G06.07 release and all subsequent G-series releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 134301 SNAX/XF G02 May 1997 SNAX/APN G02 420112-001 SNAX/XF G06 December 1998 SNAX/APN G06 421988-001 SNAX/XF G06 March 1999 SNAX/APN G06 424131-001 SNAX/XF G06 August 1999 SNAX/APN G06 426859-001 SNAX/XF G06 August 2000 SNAX/APN G06 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative.
SNAX/XF and SNAX/APN Event Management Programming Manual Glossary Index Figures Tables What’s New in This Manual vii Manual Information vii New and Changed Information vii About This Manual ix Purpose of this Manual ix Who Should Read This Manual ix How This Manual is Organized ix What Related Manuals Are Available Related Resources Available x xi Your Comments Invited xi Notation Conventions xi 1.
3. SNAX/XF Event Messages Contents 3.
3. SNAX/XF Event Messages (continued) Contents 3.
4. SNAX/APN Event Messages (continued) Contents 4.
4. SNAX/APN Event Messages (continued) Contents 4.
A. ZDNI Tokens (continued) Contents A. ZDNI Tokens (continued) ZDNI Token Dictionary (continued) Version Value A-15 Glossary Index Figures Figure 1-1. Event Reporting Interface 1-2 Tables Table 1-1. SNAX/XF Event Messages (page 1 of 3) 1-4 Table 1-2. SNAX/APN Event Messages (page 1 of 4) Table 2-1. SPI Standard Definitions Used by SNAX/XF and SNAX/APN Table 2-2. EMS Standard Definitions Used by SNAX/XF and SNAX/APN Table 2-3.
What’s New in This Manual Manual Information SNAX/XF and SNAX/APN Event Management Programming Manual Abstract This reference manual describes the EMS event messages generated by the SNAX/XF and SNAX/APN subsystems on Compaq NonStop™ Himalaya S-series servers. Product Version SNAX/XF G06 SNAX/APN G06 Supported Releases This manual supports the G06.07 release and all subsequent G-series releases until otherwise indicated in a new edition.
What’s New in This Manual • New and Changed Information Event Message 132 was added to Section 3, SNAX/XF Event Messages. and Section 4, SNAX/APN Event Messages. Changes in this edition are indicated by change bars in the margin.
About This Manual Purpose of this Manual This manual describes the ZSX1- event messages that the SNAX/XF and SNAX/APN subsystems generate by using the services of the Event Management Service (EMS). The messages are those generated on the subsystems running on a Compag Nonstop™ Himalaya S-series server.
What Related Manuals Are Available About This Manual What Related Manuals Are Available The bookmap below shows the SNAX/XF and SNAX/APN manuals set and the prerequisite G-series configurations manuals.
Related Resources Available About This Manual Related Resources Available The following Compaq manuals provide information, not covered in this manual, about SPI and EMS. • • • SPI Programming Manual SPI Common Extensions Manual EMS Manual For information on IBM Record Formatted Maintenance Statistics (RECFMS) alerts and Network Management Vector Transport (NMVT) alerts, see the IBM Systems Network Architecture: Formats manual.
About This Manual Notation for Management Programming Interfaces The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation About 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. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING.
About This Manual Change Bar Notation SNAX/XF and SNAX/APN Event Management Programming Manual—426859-001 xiv
1 Introduction SNAX/XF and SNAX/APN provide information about events occurring within their respective subsystems by sending Event Management Service (EMS) event messages. These two subsystems share a common subsystem ID and send messages with a ZSX1prefix.
Introduction Figure 1-1. Event Reporting Interface Consumer Distributor Service Manager Process SPI Management Application EMS Primary Collector ($0) Filter Consumer Distributor NET/MASTER Event Log Filter Printing Distributor Printer Filter Printing Distributor Database File Terminal Filter CDT 101.
Subsystem Processes That Send Event Messages Introduction Subsystem Processes That Send Event Messages Not all event messages received by a management application come from SNAX/XF and SNAX/APN. SNAX/XF and SNAX/APN generate event messages for events that involve the objects under their control. The Subsystem Control Point (SCP) reports events when SPI messages fail or upon an internal failure of SPI. The event messages issued by SCP are described in the SPI Common Extensions Manual.
Event Messages Sent by SNAX/XF Introduction Table 1-1 lists the SNAX/XF event messages, divided into these categories. Table 1-1. SNAX/XF Event Messages (page 1 of 3) Event Number Symbolic Name (ZSX1-EVT-) Description ZCOM Event Messages (ZCOM-EVT-) -4 IO-FATAL-ERROR Fatal error on logical device ZCL2 Event Messages (ZCL2-EVT-) 301 ET_QIO-INIT 302 ET-QIO-VERSION SNAX over Ethernet QIO initialization failed. SNAX over Ethernet QIO version incompatibility.
Event Messages Sent by SNAX/XF Introduction Table 1-1. SNAX/XF Event Messages (page 2 of 3) Event Number Symbolic Name (ZSX1-EVT-) Description 132 MESSAGE-SYSTEMINTERFACE-ERROR The SNAX interface to the X.25 line handler was unable to allocate message system queue elements (MSQE) or message system control blocks (MSCB).
Event Messages Sent by SNAX/XF Introduction Table 1-1.
Event Messages Sent by SNAX/APN Introduction Event Messages Sent by SNAX/APN The SNAX/APN event messages are divided into seven categories: • • • • • • • Common Level 2 event messages Line-handler event messages PU event messages LU event messages Service-manager event messages SPI event messages Checkpointing event messages Table 1-2 lists the SNAX/APN event messages, divided into these categories. Table 1-2.
Event Messages Sent by SNAX/APN Introduction Table 1-2.
Event Messages Sent by SNAX/APN Introduction Table 1-2.
Event Messages Sent by SNAX/APN Introduction Table 1-2. SNAX/APN Event Messages (page 4 of 4) Event Number Symbolic Name (ZSX1-EVT-) Description 113 SSNULL-FAIL Error during SSNULL call 114 SSPUT-FAIL Error during SSPUT call Checkpointing Event Messages 124 CHECKPOINT-FAILED Checkpoint to backup service-manager process failed 125 CHECKPOINT-INCOMPLETE Checkpoint to backup service-manager process incomplete Note.
2 Standard Definitions Event-message buffers, like other SPI buffers, contain header tokens and other standard tokens.
Standard Definitions Definition of Simple Token ZSPI-TKN-MAX-FIELD-VERSION contains the highest version among the non -null fields in structures added to the added to the buffer with EMSADDTOKENMAPS. ZSPI-TKN-SSID contains ZSX1-VAL-SSID, the subsystem ID of the SNAX/XF and SNAX/APN subsystems. ZSX1-VAL-SSID has the following definition; def ZSX1-VAL-SSID tacl ssid. 02 Z-FILLER type character 8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER defines Z-FILLER value is ZSPI-DDL-CHAR8.
Definitions of Header Tokens Standard Definitions Table 2-2.
Standard Definitions Definitions of Simple Tokens ZEMS-TKN-GENTIME is the time (Greenwich Mean Time) at which the service manager process created the message. ZEMS-TKN-LOGTIME is the time (Greenwich Mean Time) at which the collector process wrote the event message to its log files. ZEMS-TKN-PIN is the PIN of the reporting process. ZEMS-TKN-PROC-DESC is the process descriptor of the event creator. ZEMS-TKN-USERID is the user ID for the reporting process.
Standard Definitions SPI Common Extensions Standard Definitions Used by SNAX/XF and SNAX/APN SPI Common Extensions Standard Definitions Used by SNAX/XF and SNAX/APN Definitions whose symbolic names begin with the characters ZCOM- are SPI common extensions standard definitions. The SPI Common Extensions Manual fully explains these definitions. Table 2-3 lists all the SPI common extensions standard definitions that are used in event messages sent by SNAX/XF and SNAX/APN. Table 2-3.
Standard Definitions SPI Common Extensions Standard Definitions Used by SNAX/XF and SNAX/APN SNAX/XF and SNAX/APN Event Management Programming Manual—426859-001 2 -6
3 SNAX/XF Event Messages The event messages that the SNAX/XF subsystem can issue (ZSX1 event messages) are described in this section. For general information about event messages and their collection and interpretation, refer to the EMS Manual. For information about event messages from subsystems that use the SPI common extensions (ZCOM) tokens, refer to the SPI Common Extensions Manual. In this section, event-message tokens and their values are represented in the Compaq Data Definition Language (DDL).
SNAX/XF Event Messages which they appear in the box. However, because Compaq internal tokens are intended for Compaq use only, they are not described.
-4: ZCOM-EVT-IO-FATAL-ERR SNAX/XF Event Messages -4: ZCOM-EVT-IO-FATAL-ERR SNAX/XF detected a fatal error condition on a logical device.
SNAX/XF Event Messages -4: ZCOM-EVT-IO-FATAL-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages -4: ZCOM-EVT-IO-FATAL-ERR -16: ZCOM-VAL-IO-ERR-IOGET Cause. SNAX/XF received an error while calling the IOGET internal procedure. This message is generated by the line handler. Effect. SNAX/XF terminates. Recovery.
SNAX/XF Event Messages -4: ZCOM-EVT-IO-FATAL-ERR -5: ZCOM-VAL-IO-ERR-DEFINEPOOL Cause. A failure occurred when SNAX/XF issued a call the DEFINEPOOL procedure. This message is generated by the line handler. Effect. SNAX/XF terminates. Recovery. Verify that there are enough memory resources for the line-handler process. -4: ZCOM-VAL-IO-ERR-LOCKMEMORY Cause. A failure occurred when SNAX/XF issued a call to the LOCKMEMORY procedure. This message is generated by the service manager. Effect. SNAX/XF terminates.
SNAX/XF Event Messages • • • -4: ZCOM-EVT-IO-FATAL-ERR Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products. 1105: ZSX1-VAL-IO-ERR-IOP-INIT-FAIL Cause.
2: ZSX1-EVT-STATE-MACH-ERR SNAX/XF Event Messages 2: ZSX1-EVT-STATE-MACH-ERR SNAX/XF received an invalid state-machine event or detected a protocol violation.
SNAX/XF Event Messages 2: ZSX1-EVT-STATE-MACH-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages 2: ZSX1-EVT-STATE-MACH-ERR When contacting the Global Customer Support Center (GCSC), provide all relevant information as follows: • • • Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the
3: ZSX1-EVT-NO-POOL-SPACE SNAX/XF Event Messages 3: ZSX1-EVT-NO-POOL-SPACE No extended buffer pool space is available to complete the current request.
SNAX/XF Event Messages 3: ZSX1-EVT-NO-POOL-SPACE ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/XF Event Messages 3: ZSX1-EVT-NO-POOL-SPACE Recovery. Increase the ZSX1-TKN-EXT-PAGES value by using an ADD LINE or ALTER LINE command. If this does not correct the problem, contact the Global Customer Support Center (GCSC).
4: ZSX1-EVT-PC-REQ-ERR SNAX/XF Event Messages 4: ZSX1-EVT-PC-REQ-ERR A path-control request other than RESET or DISCONNECT was issued while the PU address table was not initialized.
SNAX/XF Event Messages 4: ZSX1-EVT-PC-REQ-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number.
SNAX/XF Event Messages • • • 4: ZSX1-EVT-PC-REQ-ERR Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products.
5: ZSX1-EVT-TS-INTERNAL-ERR SNAX/XF Event Messages 5: ZSX1-EVT-TS-INTERNAL-ERR An error occurred in an internal component of the line-handler process.
SNAX/XF Event Messages 5: ZSX1-EVT-TS-INTERNAL-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages • • • 5: ZSX1-EVT-TS-INTERNAL-ERR Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products.
7: ZSX1-EVT -CONMGR-INACT SNAX/XF Event Messages 7: ZSX1-EVT -CONMGR-INACT The Concentrator Manager was not in a STARTED state when the SNAX/XF Line Handler attempted to communicate with it.
SNAX/XF Event Messages 7: ZSX1-EVT -CONMGR-INACT ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number. This is the 32-bit equivalent of ZEMS-TKN-LDEV. ZEMS-TKN-XLDEVNAME is the string equivalent of the logical device number. ZEMS-TKN-LDEV is a standard EMS token described in the EMS Manual.
8: ZSX1-EVT-BKUP-NOTUP SNAX/XF Event Messages 8: ZSX1-EVT-BKUP-NOTUP The primary SNAX/XF Line Handler or Service Manager process could not start its backup process.
SNAX/XF Event Messages 8: ZSX1-EVT-BKUP-NOTUP ZCOM-TKN-SUBJ-SUBSYS is the fully qualified name of the service-manager process: that is, the SUBSYS object name, as described in Section 3 of the SNAX/XF Management Programming Manual, qualified by the name of the system. ZCOM-TKN-SUBJ-LINE is the fully qualified name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event.
SNAX/XF Event Messages 8: ZSX1-EVT-BKUP-NOTUP error codes can be found in the ServerNet Communications Configuration and Management Manual. ZSX1-TKN-ERRCODE-DETAIL is the code for the error detail. The error detail codes can be found in the Guardian Procedure Errors and Messages Manual. Cause. The primary SNAX line-handler or service-manager process is unable to start its backup process. Effect. The SNAX/XF device does not have fault-tolerant capabilities at this time. Recovery.
21: ZSX1-EVT-LINK-INOP SNAX/XF Event Messages 21: ZSX1-EVT-LINK-INOP The service manager received a link INOP message from a line handler because of a link-related connect or contact failure.
SNAX/XF Event Messages 21: ZSX1-EVT-LINK-INOP ZCOM-TKN-SUBJ-LINE is the fully qualified name of the line-handler process for the line on which the event occurred. ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/XF Event Messages 21: ZSX1-EVT-LINK-INOP ZSX1-TKN-CAUSE-CODE is the SNA INOP reason code indicating the reason for the inoperative condition. The reason code is a value between %H01 and %H0F. Some of the values for CAUSE-CODE are as follows: 01 Indicates a station INOP message. 02 Indicates a link INOP message. 0A Indicates an X.21 call-establishment failure. 0B Indicates an X.21 call-establishment failure, DCE in CLEAR condition. 0C Indicates an X.
22: ZSX1-EVT-LINE-UP SNAX/XF Event Messages 22: ZSX1-EVT-LINE-UP Local and remote direct-connect line handlers have exchanged reset sequences, and the line is ready to accept network requests.
SNAX/XF Event Messages 22: ZSX1-EVT-LINE-UP ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number of the line. This is the 32-bit equivalent of ZEMS-TKN-LDEV. ZEMS-TKN-XLDEVNAME is the string equivalent of the logical device number. Note.
23: ZSX1-EVT-LINE-DOWN SNAX/XF Event Messages 23: ZSX1-EVT-LINE-DOWN The operator has brought down a line, or an error has occurred that brought it down.
SNAX/XF Event Messages 23: ZSX1-EVT-LINE-DOWN ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages 23: ZSX1-EVT-LINE-DOWN ZSX1-TKN-LINE-STATE indicates the line state. This token is described in Section 4 of the SNAX/XF Management Programming Manual. ZSX1-TKN-TRACE-STATE indicates the trace state. This token is described in Section 4 of the SNAX/XF Management Programming Manual. ZSX1-TKN-ENV-RESID is the protocol-level ID. This token is described in Section 4 of the SNAX/XF Management Programming Manual. Cause.
24: ZSX1-EVT-SW-LINE-ERR SNAX/XF Event Messages 24: ZSX1-EVT-SW-LINE-ERR An attempt to disconnect a switched line failed.
SNAX/XF Event Messages 24: ZSX1-EVT-SW-LINE-ERR ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/XF Event Messages 31 Indicates that no buffer space is available. 43 Indicates that an ACTLU command failed. 24: ZSX1-EVT-SW-LINE-ERR 201 Indicates that the path is down. ZSX1-TKN-LINE-STATE indicates the line state. This token is described in Section 4 of the SNAX/XF Management Programming Manual. ZSX1-TKN-TRACE-STATE indicates the trace state. This token is described in Section 4 of the SNAX/XF Management Programming Manual.
25: ZSX1-EVT-IO-WARNING-ERR SNAX/XF Event Messages 25: ZSX1-EVT-IO-WARNING-ERR SNAX/XF detected a nonfatal error (warning condition) in the configuration of a line. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LINE ZEMS-TKN-EMPHASIS ZSPI-TKN-MANAGER ZCOM-TKN-WARNING-CAUSE token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-ENUM. Event-Message Text SNAX/XF $param1.
SNAX/XF Event Messages 25: ZSX1-EVT-IO-WARNING-ERR ZCOM-TKN-IO-WARNING-CAUSE is a token whose possible values are described in the following paragraphs under “Cause, Effect, and Recovery.” Cause, Effect, and Recovery The probable cause of this event, its effect on the system, and the action Compaq recommends that you take to remedy it depend on the value contained in ZSX1-TKNIO-WARNING-CAUSE: 15: ZSX1-VAL-IO-WARN-COUNTRY-INV Cause. The value specified for the COUNTRY modifier is invalid.
27: ZSX1-EVT-IO-PAGES-WARNING SNAX/XF Event Messages 27: ZSX1-EVT-IO-PAGES-WARNING Too many lines specifying the MULTI attribute were configured within a single line-handler process.
SNAX/XF Event Messages 27: ZSX1-EVT-IO-PAGES-WARNING ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
41: ZSX1-EVT-PU-READY SNAX/XF Event Messages 41: ZSX1-EVT-PU-READY A PU has successfully exchanged control signals.
SNAX/XF Event Messages 41: ZSX1-EVT-PU-READY ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages 41: ZSX1-EVT-PU-READY Conditional Tokens ZSX1-TKN-BASE-ALIAS-LU is the name of the SNAX Connection Manager (SNAX/CM) alias LU name used. This token is described in Section 4, “Common Definitions” in the SNAX/XF Management Programming Manual. ZSX1-TKN-ASSOC-SUBDEV is the name of the X25AM SU object when using SNAX/CM on multiple X.25lines. Cause. A PU sent an unnumbered acknowledgment (UA), indicating a successful exchange of control signals.
42: ZSX1-EVT-PU-NOT-READY SNAX/XF Event Messages 42: ZSX1-EVT-PU-NOT-READY A failure occurred in an attempt to contact or activate a PU, or a PU was successfully disconnected by a deactivate request.
SNAX/XF Event Messages 42: ZSX1-EVT-PU-NOT-READY ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages 42: ZSX1-EVT-PU-NOT-READY 177 Indicates a text overrun. 400 Indicates that the PU is not stopped. 401 Indicates that the PU is not started. ZSX1-TKN-STA-MODE indicates whether the line is acting as a primary or a secondary station. This token is described in Section 4, “Common Definitions” in the SNAX/XF Management Programming Manual. ZSX1-TKN-PU-STATE indicates the PU state. This token is described in Section 4 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages 42: ZSX1-EVT-PU-NOT-READY Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action based on a file-system error number. If ZSX1-TKN-FS-ERR is 31 and SNAX/XF event message 24 returned code 31, check the system for processes that use too much buffer space. If ZSX1-TKN-FS-ERR is 31 or 33 and the PU receiving the error is subordinate to an X.25 line, check to see whether the X.25AM process is running out of buffer space.
43: ZSX1-EVT-SW-PU-FAIL SNAX/XF Event Messages 43: ZSX1-EVT-SW-PU-FAIL A failure occurred when SNAX/XF attempted to contact or activate a switched PU (permanently subordinated or switched floating).
SNAX/XF Event Messages 43: ZSX1-EVT-SW-PU-FAIL ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/XF Event Messages 43: ZSX1-EVT-SW-PU-FAIL ZSX1-TKN-SW-STATE indicates the switched PU state. This token is described in Section 4 of the SNAX/XF Management Programming Manual. ZSX1-TKN-TEST-STATE indicates the current PU test state. This token is described in Section 4 of the SNAX/XF Management Programming Manual. ZSX1-TKN-ERRCODE is an error code that indicates why the event occurred. Some possible values are as follows: 400 Indicates that the PU is not stopped.
SNAX/XF Event Messages 43: ZSX1-EVT-SW-PU-FAIL If ZSX1-TKN-ERRCODE is 401, abort the line and then restart it. If ZSX1-TKN-ERRCODE is 405, reconfigure the PU using a lower value for ZMAX-LUS (in ZSX1-MAP-PU) , and then restart the PU. If ZSX1-TKN-ERRCODE is 406, reconfigure the PU with a valid value for ZSX1-TKNPUID-BLOCK or ZSX1-TKN-PUID-NUM, and then restart the PU.
44: ZSX1-EVT-SW-PU-ERR SNAX/XF Event Messages 44: ZSX1-EVT-SW-PU-ERR An error occurred when SNAX/XF attempted to add or contact a switched PU (permanently subordinated or switched floating).
SNAX/XF Event Messages 44: ZSX1-EVT-SW-PU-ERR ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/XF Event Messages 44: ZSX1-EVT-SW-PU-ERR ZSX1-TKN-ERRCODE is an error code that indicates why the event occurred. Some possible values are as follows: 400 Indicates that the PU is not stopped. 401 Indicates that the PU is not started. Any other error number is a file-system error, including the following errors: 31 No buffer space is available. 201 The current path to the device is down, the device is nonexistent, or there is an error in the message-system interface.
45: ZSX1-EVT-PU-ACTV SNAX/XF Event Messages 45: ZSX1-EVT-PU-ACTV A PU was successfully connected with an activate request or reconnected after a previous error.
SNAX/XF Event Messages 45: ZSX1-EVT-PU-ACTV ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/XF Event Messages 45: ZSX1-EVT-PU-ACTV Conditional Tokens ZSX1-TKN-BASE-ALIAS-LU is the name of the SNAX Connection Manager (SNAX/CM) alias LU name used. This token is described in Section 4, “Common Definitions” in the SNAX/XF Management Programming Manual. ZSX1-TKN-ASSOC-SUBDEV is the name of the X25AM SU object when using SNAX/CM on multiple X.25 lines. Cause. A PU was successfully connected with an activate request or reconnected after a previous error.
46: ZSX1-EVT-PUID-NOT-FOUND SNAX/XF Event Messages 46: ZSX1-EVT-PUID-NOT-FOUND A dial-in connection attempt from a remote PU failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZCOM-TKN-SUBJ-LINE ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZEMS-TKN-LDEV ZSX1-TKN-PUID-BLOCK-CALLER ZSX1-TKN-PUID-NUM-CALLER token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK.
SNAX/XF Event Messages 46: ZSX1-EVT-PUID-NOT-FOUND ZCOM-TKN-SUBJ-SUBSYS is the fully qualified name of the service-manager process: that is, the SUBSYS object name, as described in Section 3 of the SNAX/XF Management Programming Manual, qualified by the name of the system. ZCOM-TKN-SUBJ-LINE is the fully qualified line name on which the call came. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual.
SNAX/XF Event Messages 46: ZSX1-EVT-PUID-NOT-FOUND Recovery. Verify that the attempt to connect is valid. Determine whether a switched floating PU needs to be configured under the service manager.
47: ZSX1-EVT-PUID-MISMATCH SNAX/XF Event Messages 47: ZSX1-EVT-PUID-MISMATCH SNAX/XF rejected a dial-in connection attempt from a remote PU.
SNAX/XF Event Messages 47: ZSX1-EVT-PUID-MISMATCH ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token. ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual.
SNAX/XF Event Messages 47: ZSX1-EVT-PUID-MISMATCH Conditional Tokens ZSX1-TKN-BASE-ALIAS-LU specifies the SNAX Connection Manager (SNAX/CM) alias name for the first LU assigned to the PU for the current connection. This token is described in Section 4, “Common Definitions.” ZSX1-TKN-ASSOC-SUBDEV is the name of the X25AM SU object when using SNAX/CM on multiple X.25 lines. Cause.
49: ZSX1-EVT-SW-SESSION-TIMEOUT SNAX/XF Event Messages 49: ZSX1-EVT-SW-SESSION-TIMEOUT An application failed after a connection was made, and therefore no current session exists on the connection.
SNAX/XF Event Messages 49: ZSX1-EVT-SW-SESSION-TIMEOUT ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token. ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual.
SNAX/XF Event Messages 49: ZSX1-EVT-SW-SESSION-TIMEOUT ZSX1-TKN-BASE-ALIAS-LU specifies the SNAX Connection Manager (SNAX/CM) alias name for the first LU assigned to the PU for the current connection. This token is described in Section 4, “Common Definitions.” Cause. An application failed after a connection was made. Effect. The PU is still connected, but no current session exists on the connection; that is, no LU-LU session has existed for the interval indicated by ZSX1-TKN-SWSESSION-TIMEOUT. Recovery.
61: ZSX1-EVT-LU-ACTV SNAX/XF Event Messages 61: ZSX1-EVT-LU-ACTV A system services control point-logical unit (SSCP-LU) session became active.
SNAX/XF Event Messages 61: ZSX1-EVT-LU-ACTV ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number. This is the 32-bit equivalent of ZEMS-TKN-LDEV. ZEMS-TKN-XLDEVNAME is the string equivalent of the logical device number. Note.
62: ZSX1-EVT-LU-INACTV SNAX/XF Event Messages 62: ZSX1-EVT-LU-INACTV A system services control point-logical unit (SSCP-LU) session became inactive, or an ACTLU response is pending.
SNAX/XF Event Messages 62: ZSX1-EVT-LU-INACTV ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number. This is the 32-bit equivalent of ZEMS-TKN-LDEV. ZEMS-TKN-XLDEVNAME is the string equivalent of the logical device number. Note.
63: ZSX1-EVT-SW-LU-ERR SNAX/XF Event Messages 63: ZSX1-EVT-SW-LU-ERR An attempt to add or activate a switched floating LU failed.
SNAX/XF Event Messages 63: ZSX1-EVT-SW-LU-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number.
SNAX/XF Event Messages 63: ZSX1-EVT-SW-LU-ERR 42 Indicates that the send ACTLU failed. 43 Indicates that the ACTLU failed. 45 Indicates that the ADD LU command to the line handler failed. ZSX1-TKN-LU-ADDR is the LU address. ZSX1-TKN-LU-SESS-STATE indicates the SSCP-LU session state. This token is described in Section 4 of the SNAX/XF Management Programming Manual. ZSX1-TKN-LU-STATE indicates the LU session state. This token is described in Section 4 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages 63: ZSX1-EVT-SW-LU-ERR This message is generated by the service manager. Effect. The switched floating LU is not available for use. Recovery. Abort the PU and restart the PU and LU. If ZSX1-TKN-ERRCODE is 31 (no buffer space), retry the operation. If ZSX1-TKN-ERRCODE is 255, 402, 1218, or 1219, abort the PU and then restart both the PU and the LU.
65: ZSX1-EVT-INCONS-LU-STATE SNAX/XF Event Messages 65: ZSX1-EVT-INCONS-LU-STATE An inconsistency has been detected in the state of the LU, indicating an error in an internal service-manager component. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSX1-TKN-CODE-LOC token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-UINT.
SNAX/XF Event Messages 65: ZSX1-EVT-INCONS-LU-STATE Cause. An inconsistency has been detected in the state of the LU, indicating that an error occurred in an internal service-manager component. This message is generated by the service manager. Effect. The LU is not available for use. Recovery. Abort the LU and restart it.
66: ZSX1-EVT-TOO-MANY-INBND-BYTES SNAX/XF Event Messages 66: ZSX1-EVT-TOO-MANY-INBND-BYTES The number of bytes sent by the LU exceeded the file-system limit, indicating a possible error in the hardware for the LU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
SNAX/XF Event Messages 66: ZSX1-EVT-TOO-MANY-INBND-BYTES Recovery. Abort and restart the LU, and then begin a trace on the line. If the message appears again, stop the trace, contact the Global Customer Support Center (GCSC), and submit the trace file. When you finish the trace, abort the LU and do not restart it until the hardware is tested.
71: ZSX1-EVT-SSCP-INTERNAL-ERR SNAX/XF Event Messages 71: ZSX1-EVT-SSCP-INTERNAL-ERR An error occurred in an internal component of the service manager. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-PROCID token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
SNAX/XF Event Messages 71: ZSX1-EVT-SSCP-INTERNAL-ERR ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZSX1-TKN-CODE-LOC is the address of the error. ZSX1-TKN-PROCID is the process ID of the process that caused the event. This token is described in Section 4. Cause. An error occurred in an internal component of the service manager. Effect. The system recovers. Recovery.
73: ZSX1-EVT-SSCP-NO-POOL-SPACE SNAX/XF Event Messages 73: ZSX1-EVT-SSCP-NO-POOL-SPACE The service manager was unable to obtain buffer space from the extended buffer pool. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-POOL-SIZE ZSX1-TKN-PROCID token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK.
SNAX/XF Event Messages 73: ZSX1-EVT-SSCP-NO-POOL-SPACE ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name). ZSX1-TKN-CODE-LOC is the address of the error. ZSX1-TKN-POOL-SIZE is the number of words requested from the pool. ZSX1-TKN-PROCID is the process ID of the process that caused the event. This token is described in Section 4, “Common Definitions.” Cause.
81: ZSX1-EVT-LUNS-ERR-CON SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON The Logical Unit Network Services (LUNS) component of the service manager detected an error. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-LDEVNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEV ZSX1-TKN-ERRCODE ZSX1-TKN-CODE-LOC token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON Unconditional Tokens ZEMS-TKN-EVENTNUMBER is the event number. Its value is ZSX1-EVT-LUNS-ERR-CON. ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token. ZCOM-TKN-SUBJ-SUBSYS is the fully qualified name of the service-manager process: that is, the SUBSYS object name, as described in Section 3 of the SNAX/XF Management Programming Manual, qualified by the name of the system.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON Conditional Tokens ZSX1-TKN-FS-ERR identifies a procedure-call error. ZSX1-TKN-LUNS-INFO1 is event-related information. For example, if the value of ZSX1-TKN-ERRCODE is 2307 (unable to acquire buffer), ZSX1-TKN-LUNS-INFO1 contains the word size; if the value of ZSX1-TKN-ERRCODE is 2311 (USESEGMENT error), ZSX1-TKN-LUNS-INFO1 contains the segment ID. If ZSX1-TKN-LUNS-INFO1 is not applicable for this particular LUNS error, it is set to 0000.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON In attempting to establish a passthrough session with a host application, LUNS was unable to find the object named in ZSX1-TKN-LUNS-OBJ1 for the reason indicated by ZSX1-TKN-LUNS-INFO1, which can have the following octal values: %5 Unable to find the gateway LU (GATELU) object ZSX1-TKN-LUNS-OBJ1 when turning STATIC off. ZSX1-TKN-LUNS-OBJ2 is the name of the terminal LU.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON Recovery. Depending on the nature of the failure, perform one or more of the following steps: 1. Use the SCF INFO and STATUS commands to examine the condition of a named object. 2. In the terminal’s ESS table, examine the named ESSCMD record. If necessary, refer to the SNAX/XF LU Network Services Manual. 3. Correct any improper specifications in SCF commands or in ESSCMD records in the terminal’s ESS table. 4.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products. 2309 Cause. An internal error occurred when an internal message was being sent from LUNS (the service manager) to the line handler that services the LU named ZSX1-TKN-LUNS-OBJ2 under the line named ZSX1-TKN-LUNS-OBJ1. Effect.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON 2311 Cause. LUNS received a USESEGMENT error when attempting to place the table named in ZSX1-TKN-LUNS-OBJ1 in use through a USESEGMENT call. If the name in ZSX1-TKN-LUNS-OBJ1 is SVM^SEG, it is the service manager’s control-block segment swap file and not a table. In this case, the error can be fatal to SNAX/XF. Effect. The named table is not placed in use. Recovery. Try the request again.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON If the table named in ZSX1-TKN-LUNS-OBJ1 is an ESS table, change the SETESS command in the SET table’s SNAXUTL input file and rebuild the table. Note. Error 2312 might be the result of using a RENAME command to change the object-file name of a LUNS table. When you use this method to rename a table’s object file, the first record in the file (the descriptor record) remains unchanged.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON immediate attention. In either case, inform the Global Customer Support Center (GCSC).
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON currently active SET table. Therefore, no ESS table was assigned to the terminal, and LUNS was unable to locate the ESS message in an ESS table. Effect. If the error occurs while LUNS is processing a character-coded request from a device, LUNS builds a message and sends it to the device. When displayed, this message informs the user that the system message named Snnnn was not found.
SNAX/XF Event Messages • 81: ZSX1-EVT-LUNS-ERR-CON Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products. 2325 Cause. An associated object (line, PU, or LU), named in ZSX1-TKN-LUNS-OBJ1, is not in the proper state.
SNAX/XF Event Messages • 81: ZSX1-EVT-LUNS-ERR-CON Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products. 2333 Cause. LUNS received a character-coded command from the terminal LU named in ZSX1-TKN-LUNS-OBJ2.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products. 2334 Cause. LUNS received a character-coded command from the terminal LU named in ZSX1-TKN-LUNS-OBJ1. The command matched the command name of an ESSCMD record in the terminal’s ESS table.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON If the correct ESS table is assigned to the terminal, use SNAXUTL and its DELETE and ADD ESSCMD commands to change the ZSX1-TKN-LUNS-OBJ2 record to an INITSELF-RECEIVED type record, or change the DLU-name field in the INIT-SELF request from ZSX1-TKN-LUNS-OBJ2 to the command name of an existing INITSELFRECEIVED type ESSCMD record. 2336 Cause.
SNAX/XF Event Messages 81: ZSX1-EVT-LUNS-ERR-CON If this error is recorded while SNAXUTL is not running, issue an ALTER SUBSYS command setting the ZSX1-TKN-SET-TBL token to the name of the current SET table. If the error continues to be recorded while SNAXUTL is not running, contact the Global Customer Support Center (GCSC).
91: ZSX1-EVT-ALERT SNAX/XF Event Messages 91: ZSX1-EVT-ALERT This event is sent by the Communications Network Management server (CNMS) associated with a PU to notify its Communications Network Management application (CNMA) of an SNA unsolicited alert. Such an alert represents an event that affects the ability of the PU to perform its intended functions. The tokens for ZSX1-EVT-ALERT can vary, depending on the type of alert received.
SNAX/XF Event Messages 91: ZSX1-EVT-ALERT ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE if the alert type indicates the permanent loss of availability of a resource. (Alert type is indicated by RU byte 15; a value of %H01 indicates a permanent loss.) The value ZSPI-VAL-FALSE indicates that this event is not a critical event. This token is described in the EMS Manual.
91: ZSX1-EVT-ALERT (RECFMS Alert) SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (RECFMS Alert) When ZSX1-EVT-ALERT carries a RECFMS alert, the following tokens are present. Unconditional Tokens ZDNI-MAP-ALERT-RECFMS def ZDNI-DDL-ALERT-RECFMS. 02 ZALERT-TYPE type ZSPI-DDL-INT. 02 ZALERT-DESC type ZSPI-DDL-INT. 02 ZPROBABLE-CAUSE type ZSPI-DDL-UNIT. end Conditional Tokens ZDNI-MAP-TEXT-QUAL def ZDNI-DDL-TEXT-QUAL 02 ZLENGTH 02 ZMSG end ZDNI-TKN-TRANS-STATUS type ZSPI-DDL-INT. type ZSPI-DDL-CHAR150.
SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (RECFMS Alert) Conditional Tokens ZDNI-MAP-TEXT-QUAL is an extensible structured token whose fields are discussed in Appendix A, ZDNI Tokens. ZDNI-TKN-TRANS-STATUS is a token that explains why certain ZDNI tokens that carry RECFMS information are not included in this event. A program, internal to Compaq, attempts to translate the information contained in ZSX1-TKN-PIU into one or more of the ZDNI tokens.
91: ZSX1-EVT-ALERT (Basic Alert) SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (Basic Alert) When ZSX1-EVT-ALERT carries a basic alert, the following tokens are present. Unconditional Tokens ZDNI-MAP-ALERT-BASIC def ZDNI-DDL-ALERT-BASIC. 02 ZALERT-TYPE type ZSPI-DDL-INT. 02 ZALERT-DESC type ZSPI-DDL-INT. 02 ZPROBABLE-CAUSE type ZSPI-DDL-UNIT. end. Conditional Tokens ZDNI-MAP-TEXT-QUAL def ZDNI-DDL-TEXT-QUAL 02 ZLENGTH 02 ZMSG end ZDNI-TKN-TRANS-STATUS type ZSPI-DDL-INT. type ZSPI-DDL-CHAR150.
SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (Basic Alert) Conditional Tokens ZDNI-MAP-TEXT-QUAL is an extensible structured token whose fields are discussed in Appendix A, ZDNI Tokens. ZDNI-TKN-TRANS-STATUS is a token that explains why certain ZDNI tokens that carry RECFMS information are not included in this event. A program, internal to Compaq, attempts to translate the information contained in ZSX1-TKN-PIU into one or more of the ZDNI tokens.
SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (Generic Alert) 91: ZSX1-EVT-ALERT (Generic Alert) When ZSX1-EVT-ALERT carries a generic alert, the following tokens are present: Unconditional Tokens ZDNI-MAP-ALERT-GENERIC def ZDNI-DDL-ALERT-GENERIC. 02 ZALERT-TYPE type ZSPI-DDL-INT. 02 ZALERT-DESC type ZSPI-DDL-INT. 02 ZPROBABLE-CAUSE-NUM type ZSPI-DDL-INT. 02 ZPROBABLE-CAUSE type ZSPI-DDL-INT occurs five times. end Conditional Tokens ZDNI-MAP-FAILURE-CAUSE def ZDNI-DDL-CODE-POINT-DESC.
SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (Generic Alert) ZDNI-MAP-FAIL-RECOMM-ACT def ZDNI-DDL-CODE-POINT-DESC. 02 ZCODE-POINT type ZSPI-DDL-INT. 02 ZDETAIL-DATA-NUM type ZSPI-DDL-INT. 02 ZDETAIL-DATA occurs three times. 04 ZPRODUCT-ID-CODE type ZSPI-DDL-CHAR. 04 ZDATA-ID type ZSPI-DDL-CHAR. 04 ZDATA-ENCODING type ZSPI-DDL-CHAR. 04 ZDATA-LENGTH type ZSPI-DDL-CHAR. 04 ZDETAILED-DATA type ZDNI-DDL-CHAR44. 02 ZPSID-INDEX type ZSPI-DDL-INT. end ZDNI-MAP-INSTALL-CAUSE def ZDNI-DDL-CODE-POINT-DESC.
SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (Generic Alert) ZDNI-MAP-UNDET RECOMM-ACT def ZDNI-DDL-CODE-POINT-DESC. 02 ZCODE-POINT type ZSPI-DDL-INT. 02 ZDETAIL-DATA-NUM type ZSPI-DDL-INT. 02 ZDETAIL-DATA occurs three times. 04 ZPRODUCT-ID-CODE type ZSPI-DDL-CHAR. 04 ZDATA-ID type ZSPI-DDL-CHAR. 04 ZDATA-ENCODING type ZSPI-DDL-CHAR. 04 ZDATA-LENGTH type ZSPI-DDL-CHAR. 04 ZDETAILED-DATA type ZDNI-DDL-CHAR44. 02 ZPSID-INDEX type ZSPI-DDL-INT. end ZDNI-MAP-USER-CAUSE def ZDNI-DDL-CODE-POINT-DESC.
SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (Generic Alert) Event-Message Text PU: param1 param2 : param3. DESCRIPTION=param4. PROB. CAUSE=param5. [ USER CAUSE=param6; ACTION=param7. ] [ INSTALL CAUSE=param8; ACTION=param9. ] [ FAILURE CAUSE=param10; ACTION=param11. ] [ UNDETERMINED CAUSE; ACTION=param12. ] [ TEXT: param13 ] [ NOTE: param14 ] PIU: param15 param1 equals ZCOM-TKN-SUBJ-PU. param2 equals ZDNI-DDL-ALERT-GENERIC.ZALERT-DESC.in ZDNI-MAPALERT-GENERIC. param3 equals ZDNI-DDL-ALERT-GENERIC.
SNAX/XF Event Messages 91: ZSX1-EVT-ALERT (Generic Alert) Unconditional Tokens ZDNI-MAP-ALERT-GENERIC is an extensible structured token whose fields are discussed in Appendix A, ZDNI Tokens. Conditional Tokens (ZDNI-) FAILURE-CAUSE, FAIL-RECOMM-ACT, INSTALL-CAUSE, INST-RECOMM-ACT, TEXT-QUAL, UNDET-RECOMM-ACT, USER-CAUSE, USER-RECOMM-ACT are extensible structured tokens whose fields are discussed in Appendix A, ZDNI Tokens.
92: ZSX1-EVT-RTM-DATA SNAX/XF Event Messages 92: ZSX1-EVT-RTM-DATA The communications network management (CNM) component received a Network Management Vector Transport (NMVT) message containing unsolicited Response Time Monitor (RTM) data. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZEMS-TKN-LDEV ZSX1-TKN-PIU token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM.
SNAX/XF Event Messages 92: ZSX1-EVT-RTM-DATA ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZEMS-TKN-LDEV is a standard EMS token described in the EMS Manual. ZSX1-TKN-PIU is the path information unit (PIU) in hexadecimal digits. Cause. The service manager generates this event message when the CNM component receives an NMVT containing unsolicited Response Time Monitor (RTM) data.
101: ZSX1-EVT-LINE-STATS-LIMIT SNAX/XF Event Messages 101: ZSX1-EVT-LINE-STATS-LIMIT A line statistics counter reached the limit set by the communications network application (CNMA) in a CNM SET STATISTICS LIMIT command.
SNAX/XF Event Messages 101: ZSX1-EVT-LINE-STATS-LIMIT ZCOM-TKN-SUBJ-LINE is the fully qualified name of the line-handler process for the line on which the event occurred. ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE.
SNAX/XF Event Messages 101: ZSX1-EVT-LINE-STATS-LIMIT ZSX1-TKN-I-FRAME-RECV is the number of DLC I-frames received. ZSX1-TKN-I-FRAME-SENT is the number of DLC I-frames transmitted. ZSX1-TKN-PRIM-ABORT is the number of times eight or more consecutive 1 bits were received. ZSX1-TKN-REJ-RECV is the number of DLC command rejects received. ZSX1-TKN-REJ-SENT is the number of DLC command rejects sent. ZSX1-TKN-SNA-NEG-RSP is the number of SNA negative responses sent.
111: ZSX1-EVT-SSGET-FAIL SNAX/XF Event Messages 111: ZSX1-EVT-SSGET-FAIL An error occurred during a call to SSGET. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-ERRCODE token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
SNAX/XF Event Messages 111: ZSX1-EVT-SSGET-FAIL ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 4 of the SNAX/XF Management Programming Manual.
112: ZSX1-EVT-SSINIT-FAIL SNAX/XF Event Messages 112: ZSX1-EVT-SSINIT-FAIL An error occurred during a call to SSINIT. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-ERRCODE token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
SNAX/XF Event Messages 112: ZSX1-EVT-SSINIT-FAIL ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
113: ZSX1-EVT-SSNULL-FAIL SNAX/XF Event Messages 113: ZSX1-EVT-SSNULL-FAIL An error occurred during a call to SSNULL. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-ERRCODE ZSX1-TKN-FAILED-TOKENCODE token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
SNAX/XF Event Messages 113: ZSX1-EVT-SSNULL-FAIL ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
114: ZSX1-EVT-SSPUT-FAIL SNAX/XF Event Messages 114: ZSX1-EVT-SSPUT-FAIL An error occurred during a call to SSPUT. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-ERRCODE token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
SNAX/XF Event Messages 114: ZSX1-EVT-SSPUT-FAIL ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
115: ZSX1-EVT-EXT-POOL-LIMIT SNAX/XF Event Messages 115: ZSX1-EVT-EXT-POOL-LIMIT The EXTPOOLPAGES value specified during system generation is greater than the maximum allowed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-POOL-SIZE token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
SNAX/XF Event Messages 115: ZSX1-EVT-EXT-POOL-LIMIT ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZSX1-TKN-POOL-SIZE is the maximum number of buffer-pool pages that can be allocated. This is the value that SNAX/XF allocates for the resizing of the pool. Cause. The EXTPOOLPAGES value specified during system generation is greater than the maximum allowed.
116: ZSX1-EVT-INCONS-PTHRU-SESS-CNT SNAX/XF Event Messages 116: ZSX1-EVT-INCONS-PTHRU-SESS-CNT Inconsistent passthrough session counts exist because an internal error has occurred in the service-manager process.
SNAX/XF Event Messages 116: ZSX1-EVT-INCONS-PTHRU-SESS-CNT ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSX1-TKN-MAX-PTHRU-SESS is the maximum number of passthrough sessions as specified by the ZSX1-TKNMAX-PTHRU-SESS token. ZSX1-TKN-CUR-PTHRU-SESS is the current number of passthrough sessions that are outstanding, according to the SNAX/XF subsystem. This value is greater than or equal to the value of ZSX1-TKN-MAX-PTHRU-SESS.
117: ZSX1-EVT-ACT-PU-ERR SNAX/XF Event Messages 117: ZSX1-EVT-ACT-PU-ERR An SNA ACTPU command failed for the PU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSX1-TKN-SENSE-CODE token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT2.
SNAX/XF Event Messages 117: ZSX1-EVT-ACT-PU-ERR Cause. The PU is no longer available for use. No PUs or LUs subordinate to the line are available. Recovery. Refer to the IBM Systems Network Architecture Reference Summary or the IBM Systems Network Architecture Formats manual for sense code information.
118: ZSX1-EVT-ACT-LINK-ERR SNAX/XF Event Messages 118: ZSX1-EVT-ACT-LINK-ERR An SNA ACTLINK command failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LINE ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSX1-TKN-SENSE-CODE token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT2.
SNAX/XF Event Messages 118: ZSX1-EVT-ACT-LINK-ERR Cause. An SNA ACTLINK command failed, indicating a hardware problem with the line. This message is generated by the line handler. Effect. The specified line is no longer available for use. No physical units (PUs) or logical units (LUs) subordinate to the line are available. Recovery. Refer to the IBM Systems Network Architecture Reference Summary or the IBM Systems Network Architecture Formats manual for sense-code information.
SNAX/XF Event Messages 119: ZSX1-EVT-TS-FENOBUFSPACE 119: ZSX1-EVT-TS-FENOBUFSPACE The service-manager process was unable to communicate with a line-handler process because of multiple occurrences of file-system error 31 (no buffer space). Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LINE ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-LDEV ZSX1-TKN-NUM-NOBUFSPACE-ERRORS token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM.
SNAX/XF Event Messages 119: ZSX1-EVT-TS-FENOBUFSPACE ZEMS-TKN-LDEV is a standard EMS token described in the EMS Manual. ZSX1-TKN-NUM-NOBUFSPACE-ERRORS is the number of accumulated FENOBUFSPACE errors. Cause. The service-manager process was unable to communicate with a line-handler process because of multiple occurrences of file-system error 31 (no buffer space).
120: ZSX1-EVT-UNSUPPORTED-RU SNAX/XF Event Messages 120: ZSX1-EVT-UNSUPPORTED-RU The service manager received an SNA request or response that is not supported by SNAX/XF. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-REQ-OR-RSP ZSX1-TKN-PIU token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-ENUM.
SNAX/XF Event Messages 120: ZSX1-EVT-UNSUPPORTED-RU ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages 120: ZSX1-EVT-UNSUPPORTED-RU If the request code is not valid, the event could indicate a communications line error. If the event persists, check your communications hardware.
121: ZSX1-EVT-PIU-UNKNOWN-RESOURCE SNAX/XF Event Messages 121: ZSX1-EVT-PIU-UNKNOWN-RESOURCE The service manager received an SNA request or response from an unknown resource. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-REQ-OR-RSP ZSX1-TKN-PIU token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN.
SNAX/XF Event Messages 121: ZSX1-EVT-PIU-UNKNOWN-RESOURCE ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
122: ZSX1-EVT-WRONG-PU-MODE SNAX/XF Event Messages 122: ZSX1-EVT-WRONG-PU-MODE The service manager received a PIU from a PU on a primary line, or a gateway PU received a PIU from a host system. The PU is not in the correct mode to send or receive this kind of PIU.
SNAX/XF Event Messages 122: ZSX1-EVT-WRONG-PU-MODE ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZSX1-TKN-REQ-OR-RESP specifies whether an RU is a request or a response. ZSX1-TKN-PIU is the path information unit (PIU) in hexadecimal digits.
123: ZSX1-EVT-UNFORMATTED-PIU SNAX/XF Event Messages 123: ZSX1-EVT-UNFORMATTED-PIU A communications-line error or inconsistency occurred between the line handler and the service manager. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-REQ-OR-RSP ZSX1-TKN-PIU token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING.
SNAX/XF Event Messages 123: ZSX1-EVT-UNFORMATTED-PIU ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. ZSX1-TKN-REQ-OR-RESP specifies whether an RU is a request or a response. ZSX1-TKN-PIU is the path information unit (PIU) in hexadecimal digits. Cause.
124: ZSX1-EVT-CHECKPOINT-FAILED SNAX/XF Event Messages 124: ZSX1-EVT-CHECKPOINT-FAILED During an attempt to add or alter a SNAX/XF object, the backup service-manager process was unable to process a checkpoint from the primary service-manager process. This failure was due to a lack of memory in the backup service manager.
SNAX/XF Event Messages 124: ZSX1-EVT-CHECKPOINT-FAILED ZCOM-TKN-SUBJ-SUBSYS, ZCOM-TKN-SUBJ-LINE, ZCOM-TKN-SUBJ-PU, ZCOM-TKN-SUBJ-LU, ZSX1-TKN-APPLID, or ZSX1-TKN-APPLFILE. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual.
SNAX/XF Event Messages 124: ZSX1-EVT-CHECKPOINT-FAILED ZSX1-TKN-APPL-FILE specifies the file name of a process defined by the ADD APPL command. The attempt to add or alter this object resulted in a checkpointing failure and caused the event to occur. Cause. In a system in which the SNAX/XF service manager was running as a process pair, an attempt was made to add or alter a SNAX/XF object.
SNAX/XF Event Messages 125: ZSX1-EVT-CHECKPOINT-INCOMPLETE 125: ZSX1-EVT-CHECKPOINT-INCOMPLETE Checkpointing from the primary service-manager process to its backup process was incomplete. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32.
SNAX/XF Event Messages • • 125: ZSX1-EVT-CHECKPOINT-INCOMPLETE The backup service-manager process did not receive all of the necessary checkpoints from the primary service-manager process before a halt occurred in the CPU in which the primary service manager was running. The backup service-manager process replied with a file-system error 31 to a checkpoint from the primary service-manager process. As a result, the primary service manager stopped checkpointing to the backup service manager.
126: ZSX1-EVT-TRACE-STOPPED SNAX/XF Event Messages 126: ZSX1-EVT-TRACE-STOPPED A line-handler or service-manager trace stopped unexpectedly while writing trace data to the extended data segment. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32.
SNAX/XF Event Messages 126: ZSX1-EVT-TRACE-STOPPED ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/XF Event Messages 126: ZSX1-EVT-TRACE-STOPPED Any other error number is a file-system error number returned by the trace collector. For more information about these errors, refer to the Guardian Procedure Errors and Messages Manual. Cause. A line-handler or service-manager trace stopped unexpectedly while writing trace data to the extended data segment. Effect. Trace data is no longer being collected for the specified line-handler or servicemanager process. Recovery.
132: ZSX1-EVT-MS-PROC-ERR SNAX/XF Event Messages 132: ZSX1-EVT-MS-PROC-ERR An X.25 line-handler was unable to allocate message system queue elements (MSQE) or message system control blocks (MSCB). Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-LINE ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-FNAME32.
SNAX/XF Event Messages 132: ZSX1-EVT-MS-PROC-ERR ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZCOM-TKN-SUBJ-LINE is the fully qualified name of the SNAX Over X.25 line-handler process that generated the event. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
301: ZCL2-EVT-ET-QIO-INIT SNAX/XF Event Messages 301: ZCL2-EVT-ET-QIO-INIT SNAX over Ethernet QIO initialization failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
301: ZCL2-EVT-ET-QIO-INIT SNAX/XF Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
302: ZCL2-EVT-ET-QIO-VERSION SNAX/XF Event Messages 302: ZCL2-EVT-ET-QIO-VERSION SNAX over Ethernet QIO version incompatibility. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT. ZSPI-TYP-BOOLEAN.
302: ZCL2-EVT-ET-QIO-VERSION SNAX/XF Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
303: ZCL2-EVT-ET-QIO-FATAL-ERROR SNAX/XF Event Messages 303: ZCL2-EVT-ET-QIO-FATAL-ERROR SNAX over Ethernet encountered an unrecoverable QIO error. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
303: ZCL2-EVT-ET-QIO-FATAL-ERROR SNAX/XF Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
304: ZCL2-EVT-ET-QIO-RESOURCE SNAX/XF Event Messages 304: ZCL2-EVT-ET-QIO-RESOURCE SNAX over Ethernet encountered a QIO resource shortage. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT. ZSPI-TYP-BOOLEAN.
304: ZCL2-EVT-ET-QIO-RESOURCE SNAX/XF Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
305: ZCL2-EVT-ET-RESOURCE SNAX/XF Event Messages 305: ZCL2-EVT-ET-RESOURCE SNAX over Ethernet QIO encountered a resource shortage. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT. ZSPI-TYP-BOOLEAN.
305: ZCL2-EVT-ET-RESOURCE SNAX/XF Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
306: ZCL2-EVT-ET-FRMR SNAX/XF Event Messages 306: ZCL2-EVT-ET-FRMR SNAX over Ethernet either sent or received FRMR response frame. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 ZCL2-TKN-X3 ZCL2-TKN-X4 ZCL2-TKN-IOP 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-ENUM.
306: ZCL2-EVT-ET-FRMR SNAX/XF Event Messages ZEMS-TKN-LDEVNAME is the ldevname of the event-generating process. ZEMS-TKN-LDEV is a standard EMS token described in the EMS Manual. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual.
SNAX/XF Event Messages • • • • • • 306: ZCL2-EVT-ET-FRMR An unsolicited U-frame response An invalid S-frame command or response An unsolicited I-frame or S-frame response %h03: the rejected frame is one of the following: • • An S-frame that is more than 2 bytes long A FRMR was received with an information field that was not 5 bytes long %h04: the rejected frame is an I-frame that is longer than the rejecting station’s receive buffers.
4 SNAX/APN Event Messages The event messages that the SNAX/APN subsystem can issue (ZSX1 event messages) are described in this section. For general information about event messages and their collection and interpretation, refer to the EMS Manual. For information about event messages from subsystems that use the SPI common extensions (ZCOM) tokens, refer to the SPI Common Extensions Manual. In this section, event-message tokens and their values are represented in the Compaq Data Definition Language (DDL).
SNAX/APN Event Messages which they appear in the box. However, because Compaq internal tokens are intended for Compaq use only, they are not described.
-4: ZCOM-EVT-IO-FATAL-ERR SNAX/APN Event Messages -4: ZCOM-EVT-IO-FATAL-ERR SNAX/APN detected a fatal error condition on a logical device.
SNAX/APN Event Messages -4: ZCOM-EVT-IO-FATAL-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages • -4: ZCOM-EVT-IO-FATAL-ERR Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products. -16: ZCOM-VAL-IO-ERR-IOGET Cause. SNAX/APN received an error while calling the IOGET internal procedure. This message is generated by the line handler.
SNAX/APN Event Messages -4: ZCOM-EVT-IO-FATAL-ERR Recovery. Verify that there are enough memory resources for the service-manager process or the line-handler process. -5: ZCOM-VAL-IO-ERR-DEFINEPOOL Cause. A failure occurred when SNAX/APN issued a call the DEFINEPOOL procedure. This message is generated by the line handler. Effect. SNAX/APN terminates. Recovery. Verify that there are enough memory resources for the line-handler process. -4: ZCOM-VAL-IO-ERR-LOCKMEMORY Cause.
SNAX/APN Event Messages -4: ZCOM-EVT-IO-FATAL-ERR Recovery.
2: ZSX1-EVT-STATE-MACH-ERR SNAX/APN Event Messages 2: ZSX1-EVT-STATE-MACH-ERR SNAX/APN received an invalid state-machine event or detected a protocol violation.
SNAX/APN Event Messages 2: ZSX1-EVT-STATE-MACH-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages 2: ZSX1-EVT-STATE-MACH-ERR When contacting the Global Customer Support Center, provide all relevant information as follows: • • • Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbe
3: ZSX1-EVT-NO-POOL-SPACE SNAX/APN Event Messages 3: ZSX1-EVT-NO-POOL-SPACE No extended buffer pool space is available to complete the current request.
SNAX/APN Event Messages 3: ZSX1-EVT-NO-POOL-SPACE ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/APN Event Messages 3: ZSX1-EVT-NO-POOL-SPACE Recovery. Increase the ZSX1-TKN-EXT-PAGES value by using an ADD LINE or ALTER LINE command. If this action does not correct the problem, contact the Global Customer Support Center.
4: ZSX1-EVT-PC-REQ-ERR SNAX/APN Event Messages 4: ZSX1-EVT-PC-REQ-ERR A path-control request other than RESET or DISCONNECT was issued while the PU address table was not initialized.
SNAX/APN Event Messages 4: ZSX1-EVT-PC-REQ-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number.
SNAX/APN Event Messages • • • 4: ZSX1-EVT-PC-REQ-ERR Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products.
5: ZSX1-EVT-TS-INTERNAL-ERR SNAX/APN Event Messages 5: ZSX1-EVT-TS-INTERNAL-ERR An error occurred in an internal component of the line-handler process.
SNAX/APN Event Messages 5: ZSX1-EVT-TS-INTERNAL-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages • • • 5: ZSX1-EVT-TS-INTERNAL-ERR Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products.
6: ZSX1-EVT-SHUTDOWN SNAX/APN Event Messages 6: ZSX1-EVT-SHUTDOWN The line-handler process detects that both of the SNAX/APN service-manager processes have failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZSPI-TKN-MANAGER ZEMS-TKN-LDEVNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEVNAME ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-FNAME32 ZSPI-TYP-INT2. ZSPI-TYP-STRING. ZSPI-TYP-FNAME32. ZSPI-TYP-BOOLEAN.
SNAX/APN Event Messages 6: ZSX1-EVT-SHUTDOWN ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. Cause. Both CPUs of the SNAX/APN service-manager process failed. Effect. All the added lines are quiesced and deleted. Recovery. On a subsequent reload of the failed processors, add the SNAX/APN configuration.
7: ZSX1-EVT -CONMGR-INACT SNAX/APN Event Messages 7: ZSX1-EVT -CONMGR-INACT The Concentrator Manager was not in a STARTED state when the SNAX/APN line handler attempted to communicate with it.
SNAX/APN Event Messages 7: ZSX1-EVT -CONMGR-INACT ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/APN Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number. This is the 32-bit equivalent of ZEMS-TKN-LDEV. ZEMS-TKN-XLDEVNAME is the string equivalent of the logical device number. ZEMS-TKN-LDEV is a standard EMS token described in the EMS Manual.
8: ZSX1-EVT-BKUP-NOTUP SNAX/APN Event Messages 8: ZSX1-EVT-BKUP-NOTUP The primary SNAX/APN line handler or service Manager process could not start its backup process Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZCOM-TKN-SUBJ-LINE ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZEMS-TKN-LDEVNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEV ZSX1-TKN-BKUP-NOTUP-CAUSE ZSX1-TKN-ERRCODE ZSX1-TKN-ERRCODE-DETAIL token-type token-type token-type token-type token-type token-
SNAX/APN Event Messages 8: ZSX1-EVT-BKUP-NOTUP ZCOM-TKN-SUBJ-SUBSYS is the fully qualified name of the service-manager process: that is, the SUBSYS object name, as described in Section 3 of the SNAX/APN Management Programming Manual, qualified by the name of the system. ZCOM-TKN-SUBJ-LINE is the fully qualified name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event.
SNAX/APN Event Messages 8: ZSX1-EVT-BKUP-NOTUP error codes can be found in the ServerNet Communications Configuration and Management Manual. ZSX1-TKN-ERRCODE-DETAIL is the code for the error detail. The error detail codes can be found in the Guardian Procedure Errors and Messages Manual. Cause. The primary SNAX line-handler or service-manager process is unable to start its backup process. Effect. The SNAX/APN device does not have fault-tolerant capabilities at this time. Recovery.
21: ZSX1-EVT-LINK-INOP SNAX/APN Event Messages 21: ZSX1-EVT-LINK-INOP The service manager received a link INOP message from a line handler because of a link-related connect or contact failure.
SNAX/APN Event Messages 21: ZSX1-EVT-LINK-INOP ZCOM-TKN-SUBJ-LINE is the fully qualified name of the line-handler process for the line on which the event occurred. ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/APN Event Messages 21: ZSX1-EVT-LINK-INOP ZSX1-TKN-CAUSE-CODE is the SNA INOP reason code indicating the reason for the inoperative condition. The reason code is a value between %H01 and %H0F. Some of the values for CAUSE-CODE are as follows: 01 Indicates a station INOP message. 02 Indicates a link INOP message. 0A Indicates an X.21 call-establishment failure. 0B Indicates an X.21 call-establishment failure, DCE in CLEAR condition. 0C Indicates an X.
22: ZSX1-EVT-LINE-UP SNAX/APN Event Messages 22: ZSX1-EVT-LINE-UP Local and remote direct-connect line handlers have exchanged reset sequences, and the line is ready to accept network requests.
SNAX/APN Event Messages 22: ZSX1-EVT-LINE-UP ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number of the line. This is the 32-bit equivalent of ZEMS-TKN-LDEV. ZEMS-TKN-XLDEVNAME is the string equivalent of the logical device number. Note.
23: ZSX1-EVT-LINE-DOWN SNAX/APN Event Messages 23: ZSX1-EVT-LINE-DOWN The operator has brought down a line, or an error has occurred that brought it down.
SNAX/APN Event Messages 23: ZSX1-EVT-LINE-DOWN ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages 23: ZSX1-EVT-LINE-DOWN ZSX1-TKN-LINE-STATE indicates the line state. This token is described in Section 4 of the SNAX/APN Management Programming Manual. ZSX1-TKN-TRACE-STATE indicates the trace state. This token is described in Section 4 of the SNAX/APN Management Programming Manual. ZSX1-TKN-ENV-RESID is the protocol-level ID. This token is described in Section 4 of the SNAX/APN Management Programming Manual. Cause.
24: ZSX1-EVT-SW-LINE-ERR SNAX/APN Event Messages 24: ZSX1-EVT-SW-LINE-ERR An attempt to disconnect a switched line failed.
SNAX/APN Event Messages 24: ZSX1-EVT-SW-LINE-ERR ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/APN Event Messages 24: ZSX1-EVT-SW-LINE-ERR ZSX1-TKN-LINE-STATE indicates the line state. This token is described in Section 4 of the SNAX/APN Management Programming Manual. ZSX1-TKN-TRACE-STATE indicates the trace state. This token is described in Section 4 of the SNAX/APN Management Programming Manual. Conditional Tokens ZSX1-TKN-ERRCODE is an error code that indicates why the event occurred. Possible values are as follows: 0 Indicates that the operation was successful.
25: ZSX1-EVT-IO-WARNING-ERR SNAX/APN Event Messages 25: ZSX1-EVT-IO-WARNING-ERR SNAX/APN detected a nonfatal error (warning condition) in the configuration of a line. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LINE ZEMS-TKN-EMPHASIS ZSPI-TKN-MANAGER ZCOM-TKN-WARNING-CAUSE token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-ENUM. Event-Message Text SNAX $param1.
SNAX/APN Event Messages 25: ZSX1-EVT-IO-WARNING-ERR ZCOM-TKN-IO-WARNING-CAUSE is a token whose values are described in the following paragraphs under “Cause, Effect, and Recovery.” Cause, Effect, and Recovery The probable cause of this event, its effect on the system, and the action Compaq recommends that you take to remedy it depend on the value contained in ZSX1-TKNIO-WARNING-CAUSE: 15: ZSX1-VAL-IO-WARN-COUNTRY-INV Cause. The value specified for the COUNTRY modifier is invalid.
26: ZSX1-EVT-MEMORY-ALERT SNAX/APN Event Messages 26: ZSX1-EVT-MEMORY-ALERT During SNAX/APN operation, the memory manager in the line-handler process either detected a memory-congestion condition or exited a previously existing memorycongestion condition.
SNAX/APN Event Messages 26: ZSX1-EVT-MEMORY-ALERT This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in the SNAX/APN Management Programming Manual. ZEMS-TKN-LDEVNUMBER identifies the logical device number. This is the 32-bit equivalent of ZEMS-TKN-LDEV.
SNAX/APN Event Messages 26: ZSX1-EVT-MEMORY-ALERT ZSX1-VAL-MEM-CONGEST-CRITICAL No new sessions can be started. ZSX1-VAL-MEM-CONGEST-MODERATE New sessions can still be started, but new buffer requests could be restricted, reducing system performance. ZSX1-VAL-MEM-CONGEST-NONE A previous memory congestion condition is now relieved, and subsystem operation proceeds normally. Recovery.
27: ZSX1-EVT-IO-PAGES-WARNING SNAX/APN Event Messages 27: ZSX1-EVT-IO-PAGES-WARNING Too many lines specifying the MULTI attribute were configured within a single line-handler process.
SNAX/APN Event Messages 27: ZSX1-EVT-IO-PAGES-WARNING ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in the SNAX/APN Management Programming Manual.
41: ZSX1-EVT-PU-READY SNAX/APN Event Messages 41: ZSX1-EVT-PU-READY A PU has successfully exchanged control signals.
SNAX/APN Event Messages 41: ZSX1-EVT-PU-READY ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages 41: ZSX1-EVT-PU-READY Conditional Tokens ZSX1-TKN-BASE-ALIAS-LU does not apply to SNAX/APN. ZSX1-TKN-ASSOC-SUBDEV does not apply to SNAX/APN. Cause. A PU sent an unnumbered acknowledgment (UA), indicating a successful exchange of control signals. This message is generated by the level-3 protocol. Effect. The system waits for the next command. Recovery. This is an informative message only; no corrective action is needed.
42: ZSX1-EVT-PU-NOT-READY SNAX/APN Event Messages 42: ZSX1-EVT-PU-NOT-READY A failure occurred in an attempt to contact or activate a PU, or a PU was successfully disconnected by a deactivate request.
SNAX/APN Event Messages 42: ZSX1-EVT-PU-NOT-READY ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages 42: ZSX1-EVT-PU-NOT-READY 177 Indicates a text overrun. 400 Indicates that the PU is not stopped. 401 Indicates that the PU is not started. ZSX1-TKN-STA-MODE indicates whether the line is acting as a primary or a secondary station. This token is described in Section 4, “Common Definitions” in the SNAX/APN Management Programming Manual. ZSX1-TKN-PU-STATE indicates the PU state. This token is described in Section 4 of the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages 42: ZSX1-EVT-PU-NOT-READY If ZSX1-TKN-FS-ERR is 31 and SNAX/APN event message 24 returned code 31, check the system for processes that use too much buffer space. If ZSX1-TKN-FS-ERR is 31 or 33 and the PU receiving the error is subordinate to an X.25 line, check to see whether the X25AM process is running out of buffer space. If ZSX1-TKN-FS-ERR is 400 or 401, abort the PU and then abort and restart the line.
43: ZSX1-EVT-SW-PU-FAIL SNAX/APN Event Messages 43: ZSX1-EVT-SW-PU-FAIL A failure occurred when SNAX/APN attempted to contact or activate a switched PU.
SNAX/APN Event Messages 43: ZSX1-EVT-SW-PU-FAIL ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/APN Event Messages 43: ZSX1-EVT-SW-PU-FAIL ZSX1-TKN-TEST-STATE indicates the current PU test state. This token is described in Section 4 of the SNAX/APN Management Programming Manual. ZSX1-TKN-ERRCODE is an error code that indicates why the event occurred. Some possible values are as follows: 400 Indicates that the PU is not stopped. 401 Indicates that the PU is not started. 405 Indicates that MAXLUS has been exceeded. 408 Indicates that the line RECSIZE has been exceeded.
44: ZSX1-EVT-SW-PU-ERR SNAX/APN Event Messages 44: ZSX1-EVT-SW-PU-ERR An error occurred when SNAX/APN attempted to add or contact a switched PU.
SNAX/APN Event Messages 44: ZSX1-EVT-SW-PU-ERR ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages 44: ZSX1-EVT-SW-PU-ERR Conditional Tokens ZSX1-TKN-BASE-ALIAS-LU does not apply to SNAX/APN. ZSX1-TKN-ASSOC-SUBDEV does not apply to SNAX/APN. Cause. An error occurred when SNAX/APN attempted to add or contact a switched PU. This message is generated by the service-manager process. Effect. The specified PU cannot be used. Recovery.
45: ZSX1-EVT-PU-ACTV SNAX/APN Event Messages 45: ZSX1-EVT-PU-ACTV A PU was successfully connected with an activate request or reconnected after a previous error.
SNAX/APN Event Messages 45: ZSX1-EVT-PU-ACTV ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
SNAX/APN Event Messages 45: ZSX1-EVT-PU-ACTV Conditional Tokens ZSX1-TKN-BASE-ALIAS-LU does not apply to SNAX/APN. ZSX1-TKN-ASSOC-SUBDEV does not apply to SNAX/APN. Cause. A PU was successfully connected with an activate request or reconnected after a previous error. This message is generated by the service manager. Effect. The PU is available for use, and the system waits for the next command. Recovery. This is an informative message only; no corrective action is needed.
47: ZSX1-EVT-PUID-MISMATCH SNAX/APN Event Messages 47: ZSX1-EVT-PUID-MISMATCH SNAX/APN rejected a dial-in connection attempt from a remote PU.
SNAX/APN Event Messages 47: ZSX1-EVT-PUID-MISMATCH ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token. ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual.
SNAX/APN Event Messages 47: ZSX1-EVT-PUID-MISMATCH Conditional Tokens ZSX1-TKN-BASE-ALIAS-LU does not apply to SNAX/APN. ZSX1-TKN-ASSOC-SUBDEV does not apply to SNAX/APN. Cause. SNAX/APN rejected a dial-in connection attempt from a remote PU because its PUIDBLK and PUIDNUM (contained in the XID response) do not match the ZSX1-TKN-PUID-BLOCK and ZSX1-TKN-PUID-NUM values of the PU configured under the line. Effect. SNAX/APN rejects the connection and continues processing. Recovery.
48: ZSX1-EVT-XID-FAIL SNAX/APN Event Messages 48: ZSX1-EVT-XID-FAIL During an XID3 (Format 3) exchange, SNAX/APN detected an error. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-SENSE-CODE ZSX1-TKN-BIT-OFFSET ZSX1-TKN-BYTE-OFFSET token-type token-type token-type token-type token-type token-type token type token type token type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN.
SNAX/APN Event Messages 48: ZSX1-EVT-XID-FAIL ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZSX1-TKN-BIT-OFFSET is the bit offset into the XID frame. ZSX1-TKN-BYTE-OFFSET is the byte offset into the XID frame. ZSX1-TKN-SENSE-CODE is the SNA sense data value. The meanings of these values are given in Table 4-1. Cause. During an XID (Format 3) exchange, SNAX/APN detected an error.
SNAX/APN Event Messages 48: ZSX1-EVT-XID-FAIL Table 4-1. Sense Data Values for Event Message 48 (page 2 of 4) Sense Data Value Description 0809 0041 A negotiation-proceeding XID3 was received when a prenegotiation XID3 was expected.
SNAX/APN Event Messages 48: ZSX1-EVT-XID-FAIL Table 4-1. Sense Data Values for Event Message 48 (page 3 of 4) Sense Data Value Description 1015 0001 There were too few bytes in XID3. 1015 0002 The length specified in the Length field in XID3 was different from the number of bytes received. 1016 0001 In the received XID3, a value of 0 was assigned to the field that specifies the maximum number of I-frames that can be received by the XID sender before acknowledgment.
SNAX/APN Event Messages 48: ZSX1-EVT-XID-FAIL Table 4-1. Sense Data Values for Event Message 48 (page 4 of 4) Sense Data Value Description 1016 0013 The data-link control (DLC) Type field in the sent and received negotiation-proceeding XID3s were not the same. 1016 0014 The adjacent NRM link station sent an XID3 indicating it contained a negotiable link station after having indicated it contained a link station with a nonnegotiable role.
49: ZSX1-EVT-SW-SESSION-TIMEOUT SNAX/APN Event Messages 49: ZSX1-EVT-SW-SESSION-TIMEOUT An application failed after a connection was made, and no current session exists on the connection.
SNAX/APN Event Messages 49: ZSX1-EVT-SW-SESSION-TIMEOUT ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token. ZCOM-TKN-SUBJ-PU is the fully qualified name of the PU for which this event occurred. ZSX1-TKN-PROCNAME is the name of the line-handler process for the line on which the event occurred. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual.
SNAX/APN Event Messages 49: ZSX1-EVT-SW-SESSION-TIMEOUT Effect. The PU is still connected, but no current session exists on the connection; that is, no LU-LU session has existed for the interval indicated by ZSX1-TKN-SWSESSION-TIMEOUT. Recovery. There are two alternatives: • • Users can abort and restart the PU and Us that have the inactive connection. The PU is thus disconnected. Some users might want to maintain the connection even though there are no current sessions.
65: ZSX1-EVT-INCONS-LU-STATE SNAX/APN Event Messages 65: ZSX1-EVT-INCONS-LU-STATE An inconsistency has been detected in the state of the LU, indicating an error in an internal service-manager component. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSX1-TKN-CODE-LOC token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-UINT.
SNAX/APN Event Messages 65: ZSX1-EVT-INCONS-LU-STATE Cause. An inconsistency has been detected in the state of the LU, indicating that an error occurred in an internal service-manager component. This message is generated by the service manager. Effect. The LU is not available for use. Recovery. Abort the LU and restart it.
66: ZSX1-EVT-TOO-MANY-INBND-BYTES SNAX/APN Event Messages 66: ZSX1-EVT-TOO-MANY-INBND-BYTES The number of bytes sent by the LU exceeded the file-system limit, indicating a possible error in the hardware for the LU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
SNAX/APN Event Messages 66: ZSX1-EVT-TOO-MANY-INBND-BYTES Recovery. Abort and restart the LU, and then begin a trace on the line. If the message appears again, stop the trace, contact the Global Customer Support Center, and submit the trace file. When you finish the trace, abort the LU and do not restart it until the hardware is tested.
67: ZSX1-EVT-LU-RU-ERR SNAX/APN Event Messages 67: ZSX1-EVT-LU-RU-ERR An SNA request unit (RU) error occurred on a session with a remote LU using the CRT or ITI protocol. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-RU-TYPE ZSX1-TKN-SENSE-CODE ZSX1-TKN-SNANETID ZSX1-TKN-SNANAME token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM.
67: ZSX1-EVT-LU-RU-ERR SNAX/APN Event Messages ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZCOM-TKN-RU-TYPE identifies the type of RU on which the error occurred. This token can have one of the following enumerated values: ZSX1-VAL-BIND (numeric value 49) The error occurred on a BIND RU.
SNAX/APN Event Messages 67: ZSX1-EVT-LU-RU-ERR Cause. An SNA request unit (RU) error occurred on a session with a remote LU using the CRT or ITI protocol. Some of the errors are listed below: • • • • A sequence-number error occurred on the inbound SNA RU. A negative response to the BIND request was received. A negative response to the SDT request was received. An UNBIND request was received. Effect. The session is deactivated if it was previously activated.
71: ZSX1-EVT-SSCP-INTERNAL-ERR SNAX/APN Event Messages 71: ZSX1-EVT-SSCP-INTERNAL-ERR An error occurred in an internal component of the service manager. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-PROCID token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
SNAX/APN Event Messages 71: ZSX1-EVT-SSCP-INTERNAL-ERR ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZSX1-TKN-CODE-LOC is the address of the error. ZSX1-TKN-PROCID is the process ID of the process that caused the event. This token is described in Section 4. Cause. An error occurred in an internal component of the service manager. Effect. The system recovers. Recovery.
73: ZSX1-EVT-SSCP-NO-POOL-SPACE SNAX/APN Event Messages 73: ZSX1-EVT-SSCP-NO-POOL-SPACE The service manager was unable to obtain buffer space from the extended buffer pool. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-POOL-SIZE ZSX1-TKN-PROCID token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK.
SNAX/APN Event Messages 73: ZSX1-EVT-SSCP-NO-POOL-SPACE ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZSX1-TKN-CODE-LOC is the address of the error. ZSX1-TKN-POOL-SIZE is the number of words requested from the pool. ZSX1-TKN-PROCID is the process ID of the process that caused the event.
81: ZSX1-EVT-LUNS-ERR-CON SNAX/APN Event Messages 81: ZSX1-EVT-LUNS-ERR-CON The Logical Unit Network Services (LUNS) component of the service manager detected an error. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-LDEVNUMBER ZEMS-TKN-XLDEVNAME ZEMS-TKN-LDEV ZSX1-TKN-ERRCODE ZSX1-TKN-CODE-LOC token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM.
SNAX/APN Event Messages 81: ZSX1-EVT-LUNS-ERR-CON Unconditional Tokens ZEMS-TKN-EVENTNUMBER is the event number. Its value is ZSX1-EVT-LUNS-ERR-CON. ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token. ZCOM-TKN-SUBJ-SUBSYS is the fully qualified name of the service-manager process: that is, the SUBSYS object name, as described in Section 3 in the SNAX/APN Management Programming Manual, qualified by the name of the system.
SNAX/APN Event Messages 81: ZSX1-EVT-LUNS-ERR-CON Conditional Tokens ZSX1-TKN-FS-ERR identifies a procedure-call error. ZSX1-TKN-LUNS-INFO1 is event-related information. For example, if the value of ZSX1-TKN-ERRCODE is 2307 (unable to acquire buffer), ZSX1-TKN-LUNS-INFO1 contains the word size; if the value of ZSX1-TKN-ERRCODE is 2311 (USESEGMENT error), ZSX1-TKN-LUNS-INFO1 contains the segment ID. If ZSX1-TKN-LUNS-INFO1 is not applicable for this particular LUNS error, it is set to 0000.
SNAX/APN Event Messages 81: ZSX1-EVT-LUNS-ERR-CON When contacting the Global Customer Support Center, provide all relevant information as follows: • • • Descriptions of the problem and accompanying symptoms Details from the message(s) generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the number
SNAX/APN Event Messages 81: ZSX1-EVT-LUNS-ERR-CON Recovery. Look up ZSX1-TKN-FS-ERR for the specific cause of the ALLOCATESEGMENT error. Verify that the table’s object file exists on this system (the ALLOCATESEGMENT procedure creates a null file of the same name when it does not find the file specified in the ALLOCATESEGMENT procedure call). 2311 Cause. LUNS received a USESEGMENT error when attempting to place the table named in ZSX1-TKN-LUNS-OBJ1 in use through a USESEGMENT call.
SNAX/APN Event Messages 81: ZSX1-EVT-LUNS-ERR-CON If the table named in ZSX1-TKN-LUNS-OBJ1 is an ESS table, change the SETESS command in the SET table’s SNAXUTL input file and rebuild the table. Note. Error 2312 might be the result of using a RENAME command to change the object-file name of a LUNS table. When you use this method to rename a table’s object file, the first record in the file (the descriptor record) remains unchanged.
SNAX/APN Event Messages • 81: ZSX1-EVT-LUNS-ERR-CON Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump, if applicable If your local operating procedures require contacting the Global Customer Support Center (GCSC), please also supply your system number and the numbers and versions of all related products. 2341 Cause. The SET table referenced in an ALTER SUBSYS command is not present in the specified subvolume. Effect.
82: ZSX1-EVT-XLF-LOGON-ERR SNAX/APN Event Messages 82: ZSX1-EVT-XLF-LOGON-ERR A remote logon attempt or an attempt to acquire a remote 3270 device, using the extended logon facility (XLF), failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-SNANAME ZSX1-TKN-ERRCODE token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING.
SNAX/APN Event Messages 82: ZSX1-EVT-XLF-LOGON-ERR ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZSX1-TKN-SNANAME is the SNA name of the remote LU. ZSX1-TKN-ERRCODE indicates the reason for the failure. The possible values for error are as follows: 2 Invalid operation. 10 Name already exists. 14 No such device. 31 No buffer space available.
SNAX/APN Event Messages • • • • 82: ZSX1-EVT-XLF-LOGON-ERR If error is 14, ensure that the subdevice name in the ZSX1-TKN-CREATOR token for the TLOGMGR LU matches the subdevice-name part of the SNAX Creator-2 APPL object name. If error is 31, retry the operation. If error is 184, start the Creator-2 application. If error is 2913, either increase the value of ZMAX-LUS in ZSX1-MAP-PU for the remote PU, or wait until one or more dynamic LUs log off.
111: ZSX1-EVT-SSGET-FAIL SNAX/APN Event Messages 111: ZSX1-EVT-SSGET-FAIL An error occurred during a call to SSGET. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-ERRCODE token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
SNAX/APN Event Messages 111: ZSX1-EVT-SSGET-FAIL ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
112: ZSX1-EVT-SSINIT-FAIL SNAX/APN Event Messages 112: ZSX1-EVT-SSINIT-FAIL An error occurred during a call to SSINIT. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-ERRCODE token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
SNAX/APN Event Messages 112: ZSX1-EVT-SSINIT-FAIL ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
113: ZSX1-EVT-SSNULL-FAIL SNAX/APN Event Messages 113: ZSX1-EVT-SSNULL-FAIL An error occurred during a call to SSNULL. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-ERRCODE ZSX1-TKN-FAILED-TOKENCODE token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
SNAX/APN Event Messages 113: ZSX1-EVT-SSNULL-FAIL ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
114: ZSX1-EVT-SSPUT-FAIL SNAX/APN Event Messages 114: ZSX1-EVT-SSPUT-FAIL An error occurred during a call to SSPUT. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-CODE-LOC ZSX1-TKN-ERRCODE token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
SNAX/APN Event Messages 114: ZSX1-EVT-SSPUT-FAIL ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
115: ZSX1-EVT-EXT-POOL-LIMIT SNAX/APN Event Messages 115: ZSX1-EVT-EXT-POOL-LIMIT The EXTPOOLPAGES value specified during system generation is greater than the maximum allowed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-POOL-SIZE token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
SNAX/APN Event Messages 115: ZSX1-EVT-EXT-POOL-LIMIT ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZSX1-TKN-POOL-SIZE is the maximum number of buffer-pool pages that can be allocated. This is the value that SNAX/APN allocates for the resizing of the pool. Cause. The EXTPOOLPAGES value specified during system generation is greater than the maximum allowed.
118: ZSX1-EVT-ACT-LINK-ERR SNAX/APN Event Messages 118: ZSX1-EVT-ACT-LINK-ERR An SNA ACTLINK command failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LINE ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSX1-TKN-SENSE-CODE token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-INT2.
SNAX/APN Event Messages 118: ZSX1-EVT-ACT-LINK-ERR Cause. An SNA ACTLINK command failed, indicating a hardware problem with the line. This message is generated by the line handler. Effect. The specified line is no longer available for use. No physical units (PUs) or logical units (LUs) subordinate to the line are available. Recovery. Refer to the IBM Systems Network Architecture Reference Summary or the IBM Systems Network Architecture Formats manual for sense-code information.
SNAX/APN Event Messages 119: ZSX1-EVT-TS-FENOBUFSPACE 119: ZSX1-EVT-TS-FENOBUFSPACE The service-manager process was unable to communicate with a line-handler process because of multiple occurrences of file-system error 31 (no buffer space). Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LINE ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-LDEV ZSX1-TKN-NUM-NOBUFSPACE-ERRORS token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM.
SNAX/APN Event Messages 119: ZSX1-EVT-TS-FENOBUFSPACE ZEMS-TKN-LDEV is a standard EMS token described in the EMS Manual. ZSX1-TKN-NUM-NOBUFSPACE-ERRORS is the number of accumulated FENOBUFSPACE errors. Cause. The service-manager process was unable to communicate with a line-handler process because of multiple occurrences of file-system error 31 (no buffer space).
120: ZSX1-EVT-UNSUPPORTED-RU SNAX/APN Event Messages 120: ZSX1-EVT-UNSUPPORTED-RU The service manager received an SNA request or response that is not supported by SNAX/APN. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK * ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-REQ-OR-RSP ZSX1-TKN-PIU token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32. ZSPI-TYP-ENUM.
SNAX/APN Event Messages 120: ZSX1-EVT-UNSUPPORTED-RU ZCOM-TKN-SUBJ-SUBSYS, ZCOM-TKN-SUBJ-LINE, ZCOM-TKN-SUBJ-PU, or ZCOM-TKN-SUBJ-LU. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual.
SNAX/APN Event Messages 120: ZSX1-EVT-UNSUPPORTED-RU Recovery. Verify whether the request code is a valid SNA request code. If the request code is valid, then this request is not supported by Compaq. If the request code is not valid, the event could indicate a communications line error. If the event persists, check your communications hardware.
121: ZSX1-EVT-PIU-UNKNOWN-RESOURCE SNAX/APN Event Messages 121: ZSX1-EVT-PIU-UNKNOWN-RESOURCE The service manager received an SNA request or response from an unknown resource. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-REQ-OR-RSP ZSX1-TKN-PIU token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN.
SNAX/APN Event Messages 121: ZSX1-EVT-PIU-UNKNOWN-RESOURCE ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
123: ZSX1-EVT-UNFORMATTED-PIU SNAX/APN Event Messages 123: ZSX1-EVT-UNFORMATTED-PIU A communications-line error or inconsistency occurred between the line handler and the service manager. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-LU ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZSX1-TKN-REQ-OR-RSP ZSX1-TKN-PIU token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING.
SNAX/APN Event Messages 123: ZSX1-EVT-UNFORMATTED-PIU ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual. ZSX1-TKN-REQ-OR-RESP specifies whether an RU is a request or a response. ZSX1-TKN-PIU is the path information unit (PIU) in hexadecimal digits. Cause.
124: ZSX1-EVT-CHECKPOINT-FAILED SNAX/APN Event Messages 124: ZSX1-EVT-CHECKPOINT-FAILED During an attempt to add or alter a SNAX/APN object, the backup service-manager process was unable to process a checkpoint from the primary service-manager process. This failure was due to a lack of memory in the backup service manager.
SNAX/APN Event Messages 124: ZSX1-EVT-CHECKPOINT-FAILED ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token. In this event message, the subject token is one of the following conditional tokens: ZCOM-TKN-SUBJ-SUBSYS, ZCOM-TKN-SUBJ-LINE, ZCOM-TKN-SUBJ-PU, ZCOM-TKN-SUBJ-LU, ZSX1-TKN-APPLID, or ZSX1-TKN-APPLFILE. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual.
SNAX/APN Event Messages 124: ZSX1-EVT-CHECKPOINT-FAILED ZSX1-TKN-APPLID defines the ID names of host applications that can be accessed on a secondary line. The attempt to add or alter this object resulted in a checkpointing failure and caused the event to occur. ZSX1-TKN-APPL-FILE specifies the file name of a process defined by the ADD APPL command. The attempt to add or alter this object resulted in a checkpointing failure and caused the event to occur. Cause.
SNAX/APN Event Messages 125: ZSX1-EVT-CHECKPOINT-INCOMPLETE 125: ZSX1-EVT-CHECKPOINT-INCOMPLETE Checkpointing from the primary service-manager process to its backup process was incomplete. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-SUBSYS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32.
SNAX/APN Event Messages • • 125: ZSX1-EVT-CHECKPOINT-INCOMPLETE The backup service-manager process did not receive all of the necessary checkpoints from the primary service-manager process before a halt occurred in the CPU in which the primary service manager was running. The backup service-manager process replied with a file-system error 31 to a checkpoint from the primary service-manager process. As a result, the primary service manager stopped checkpointing to the backup service manager.
126: ZSX1-EVT-TRACE-STOPPED SNAX/APN Event Messages 126: ZSX1-EVT-TRACE-STOPPED A line-handler or service-manager trace stopped unexpectedly while writing trace data to the extended data segment. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK * ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-FNAME32.
SNAX/APN Event Messages 126: ZSX1-EVT-TRACE-STOPPED ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 in the SNAX/APN Management Programming Manual.
SNAX/APN Event Messages 126: ZSX1-EVT-TRACE-STOPPED ZSX1-TKN-ERRCODE is an error code returned by the trace collector process to indicate why the event occurred. The possible trace-collector error codes are as follows: -814 The trace was no longer active (that is, the segment ID was set to a nonzero value) at the time the trace collector attempted to write the trace data to the extended segment.
127: ZSX1-EVT-LU-REGISTER-FAILED SNAX/APN Event Messages 127: ZSX1-EVT-LU-REGISTER-FAILED An attempt to register an LU with the Network Node Server failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK * ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-LU ZSX1-TKN-SENSE-CODE ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-INT2. ZSPI-TYP-FNAME32.
SNAX/APN Event Messages 127: ZSX1-EVT-LU-REGISTER-FAILED ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. Cause. SNAX/APN sent a REGISTER request to its Network Node Server and it was rejected. Effect. The LU is not registered. Recovery. Take the recovery action suggested by the Sense Code. Stop and restart the LU to force another registration attempt.
128: ZSX1-EVT-CP-SESSION-STATUS SNAX/APN Event Messages 128: ZSX1-EVT-CP-SESSION-STATUS This event message is issued when the status of a CP-CP session changes. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK * ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PU ZSX1-TKN-CP-SESS-STATE ZSX1-TKN-SENSE-CODE ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INT2.
SNAX/APN Event Messages 128: ZSX1-EVT-CP-SESSION-STATUS ZSX1-TKN-SENSE-CODE is zeroes for session states ACTIVE and PENDING. For session state INACTIVE, it is the IBM Sense Code associated with the CP-CP session loss. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual. Cause. This message is informational for session states ACTIVE and PENDING.
129: ZSX1-EVT-ELF-LOGON-ERR SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR A remote logon attempt failed when using the enhanced logon facility (ELF). Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK * ZEMS-TKN-EMPHASIS ZSX1-TKN-SENSE-CODE ZSX1-TKN-SNANAME ZSX1-TKN-LOCALSNANAME ZSX1-TKN-SNANETID ZCOM-TKN-SUBJ-LU ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR ZSX1-TKN-SENSE-CODE indicates the reason for the failure. The values for reason code are as follows: Reason Code 00000002 Cause. Temporary memory shortage. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC).
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Reason Code 00000003 Cause. The SNALU application (APPL NAME) has not opened its LU, an indication that the application may not be running or that it is defective. Effect. The logon request is rejected. Recovery. Start or correct the SNALU application (APPL NAME) and retry the logon. Reason Code 00000004 Cause. The user is attempting to logon to an ITI or CRT application whose template LU was not defined with PROTOCOL ITI or PROTOCOL CRT. Effect.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Reason Code 00000008 Cause. Temporary memory shortage. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 00000009 Cause. Internal error. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 0000000A Cause. Temporary memory shortage. Effect.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Reason Code 0000000E Cause. Internal error. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 0000000F Cause. Temporary memory shortage. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 00000010 Cause. Internal error. Effect.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Reason Code 00000014 Cause. Internal error. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 00000015 Cause. Temporary memory shortage. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 00000018 Cause. Temporary memory shortage. Effect.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Reason Code 0000001C Cause. Internal error. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 0000001D Cause. Internal error. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 0000001E Cause. Internal error. Effect. The logon request is rejected.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Reason Code 00000022 Cause. The Creator-2 application has not been added with SCF. Effect. The logon request is rejected. Recovery. SCF ADD Creator-2 (ADD APPL $.#). Reason Code 00000023 Cause. A SNALU application returned a negative response to a CINIT. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, check the coding and/or configuration of the SNALU application.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, check the coding and/or configuration of the SNALU application. Reason Code 00000029 Cause. A SNALU LU was aborted by an operator causing the termination of logon processing Effect. The logon request is rejected. Recovery. Restart the LU and retry the logon. Reason Code 0000002A Cause.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 0000002F Cause. A dynamic LU cannot be created for the logon because the MAXLUS limit for the PU would be exceeded. Effect. The logon request is rejected. Recovery. Either stop the PU and increase its MAXLUS value or retry the logon at another time. Reason Code 00000030 Cause.
SNAX/APN Event Messages 129: ZSX1-EVT-ELF-LOGON-ERR Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 00000035 Cause. Internal error. Effect. The logon request is rejected. Recovery. Retry the logon. If the problem persists, contact the Global Customer Support Center (GCSC). Reason Code 00000036 Cause. A previous logon from this terminal is currently being processed. Effect. The logon request is rejected. Recovery.
130: ZSX1-EVT-ELF-NAME-NOT-FOUND SNAX/APN Event Messages ZCOM-TKN-SUBJ-LU is the fully qualified name of the LU that serves the target application. If the target application is CRT or ITI, the LU was dynamically created from the application’s template LU. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
SNAX/APN Event Messages 130: ZSX1-EVT-ELF-NAME-NOT-FOUND ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token. In this event message, the subject token is ZCOM-TKN-SUBJ-LINE. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZSX1-TKN-SENSE-CODE indicates the reason for the failure. The values for reason code are as follows: Reason Code 00000001 Cause.
SNAX/APN Event Messages 130: ZSX1-EVT-ELF-NAME-NOT-FOUND ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
132: ZSX1-EVT-MS-PROC-ERR SNAX/APN Event Messages 132: ZSX1-EVT-MS-PROC-ERR An X.25 line-handler was unable to allocate message system queue elements (MSQE) or message system control blocks (MSCB). Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-LINE ZSPI-TKN-MANAGER token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-FNAME32.
SNAX/APN Event Messages 132: ZSX1-EVT-MS-PROC-ERR ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZCOM-TKN-SUBJ-LINE is the fully qualified name of the SNAX Over X.25 line-handler process that generated the event. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
301: ZCL2-EVT-ET-QIO-INIT SNAX/APN Event Messages 301: ZCL2-EVT-ET-QIO-INIT SNAX over Ethernet QIO initialization failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
301: ZCL2-EVT-ET-QIO-INIT SNAX/APN Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
302: ZCL2-EVT-ET-QIO-VERSION SNAX/APN Event Messages 302: ZCL2-EVT-ET-QIO-VERSION SNAX over Ethernet QIO version incompatibility. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT. ZSPI-TYP-BOOLEAN.
302: ZCL2-EVT-ET-QIO-VERSION SNAX/APN Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
303: ZCL2-EVT-ET-QIO-FATAL-ERROR SNAX/APN Event Messages 303: ZCL2-EVT-ET-QIO-FATAL-ERROR SNAX over Ethernet encountered an unrecoverable QIO error. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
303: ZCL2-EVT-ET-QIO-FATAL-ERROR SNAX/APN Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-TRUE, indicating that this event is a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
304: ZCL2-EVT-ET-QIO-RESOURCE SNAX/APN Event Messages 304: ZCL2-EVT-ET-QIO-RESOURCE SNAX over Ethernet encountered a QIO resource shortage. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT. ZSPI-TYP-BOOLEAN.
304: ZCL2-EVT-ET-QIO-RESOURCE SNAX/APN Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
305: ZCL2-EVT-ET-RESOURCE SNAX/APN Event Messages 305: ZCL2-EVT-ET-RESOURCE SNAX over Ethernet encountered a resource shortage not related to QIO. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-MARK. ZSPI-TYP-FNAME32. ZSPI-TYP-UINT.
305: ZCL2-EVT-ET-RESOURCE SNAX/APN Event Messages ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual. ZSPI-TKN-MANAGER is the name of the service-manager process (the SUBSYS object name), as described in Section 3 of the SNAX/XF Management Programming Manual.
306: ZCL2-EVT-ET-FRMR SNAX/APN Event Messages 306: ZCL2-EVT-ET-FRMR SNAX over Ethernet either sent or received FRMR response frame. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZEMS-TKN-LDEVNAME ZEMS-TKN-LDEV ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZSPI-TKN-MANAGER ZCL2-TKN-ET-CONTEXT ZCL2-TKN-X2 ZCL2-TKN-X3 ZCL2-TKN-X4 ZCL2-TKN-IOP 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-ENUM.
306: ZCL2-EVT-ET-FRMR SNAX/APN Event Messages ZEMS-TKN-LDEVNAME is the ldevname of the event-generating process. ZEMS-TKN-LDEV is a standard EMS token described in the EMS Manual. ZEMS-TKN-EMPHASIS contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical event. This token is described in the EMS Manual. ZEMS-TKN-CONSOLE-PRINT contains the value ZSPI-VAL-FALSE. This token is described in the EMS Manual.
SNAX/APN Event Messages • • • • • • 306: ZCL2-EVT-ET-FRMR An unsolicited U-frame response An invalid S-frame command or response An unsolicited I-frame or S-frame response %h03: the rejected frame is one of the following: • • An S-frame that is more than 2 bytes long A FRMR was received with an information field that was not 5 bytes long %h04: the rejected frame is an I-frame that is longer than the rejecting station’s receive buffers.
A ZDNI Tokens This appendix provides a dictionary of ZDNI tokens. Compaq provides eleven extensible structured tokens whose symbolic names begin with the characters ZDNI: ZDNI-MAP-ALERT-BASIC ZDNI-MAP-ALERT-GENERIC ZDNI-MAP-ALERT-RECFMS ZDNI-MAP-FAILURE-CAUSE ZDNI-MAP-FAIL-RECOMM-ACT ZDNI-MAP-INSTALL-CAUSE ZDNI-MAP-INST-RECOMM-ACT ZDNI-MAP-TEXT-QUAL ZDNI-MAP-UNDET-RECOMM-ACT ZDNI-MAP-USER-CAUSE ZDNI-MAP-USER-RECOMM-ACT Only certain subsets of these tokens appear in your buffer at a given time.
ZDNI-MAP-ALERT-GENERIC ZDNI Tokens ZALERT-TYPE contains a code point that indicates the severity of the condition. For the meaning of the code point, consult the IBM Systems Network Architecture: Formats manual and see the description of the alert type field of the Basic Alert (X‘91’) Alert MS Subvector. ZALERT-DESC contains a code point that gives an index to explanatory text describing the condition.
ZDNI-MAP-ALERT-RECFMS ZDNI Tokens ZPROBABLE-CAUSE-NUM indicates how many instances of ZPROBABLE-CAUSE the token contains. The token can contain as many as five instances. ZPROBABLE-CAUSE contains code points that give the probable cause of the condition. For the meaning of the code points, see the description of the Probable Causes (X‘93’) Alert MS Subvector in the IBM Systems Network Architecture: Formats manual.
ZDNI-MAP-FAILURE-CAUSE ZDNI Tokens Subvector. The information consists of a code point for stored text that describes the probable cause of the failure. An instance of ZDNI-MAP-FAILURE-CAUSE is accompanied by an instance of ZDNI-MAP-FAIL-RECOMM-ACT. This token has the definition ZDNI-DDL-CODE-POINT-DESC and the token number ZDNI-TNM-FAILURE-CAUSE. def ZDNI-DDL-CODE-POINT-DESC. 02 ZCODE-POINT type ZSPI-DDL-INT. 02 ZDETAIL-DATA-NUM type ZSPI-DDL-INT. 02 ZDETAIL-DATA occurs three times.
ZDNI-MAP-FAIL-RECOMM-ACT ZDNI Tokens ZDATA-ENCODING contains a code point specifying how the detailed data is encoded. For the meaning of the code point, see the IBM Systems Network Architecture: Formats manual. ZDATA-LENGTH specifies the number of bytes used in the ZDETAILED-DATA field. ZDETAILED-DATA contains explanatory text. ZPSID-INDEX contains a code point and count that together specify a particular Product ID Subvector.
ZDNI-MAP-INSTALL-CAUSE ZDNI Tokens ZDETAIL-DATA-NUM indicates the number of instances of ZDETAIL-DATA the token contains. The token can contain as many as three instances. ZDETAIL-DATA carries information corresponding to the information contained in one Detailed Data (X‘82’) Network Alert Common Subfield. The ZDNI-MAP-FAIL-RECOMM-ACT token can contain as many as three instances of ZDETAIL-DATA depending on the value specified in ZCODE-POINT.
ZDNI-MAP-INSTALL-CAUSE ZDNI Tokens This token has the definition ZDNI-DDL-CODE-POINT-DESC and the token number ZDNI-TNM-INSTALL-CAUSE. def ZDNI-DDL-CODE-POINT-DESC. 02 ZCODE-POINT type ZSPI-DDL-INT. 02 ZDETAIL-DATA-NUM type ZSPI-DDL-INT. 02 ZDETAIL-DATA occurs three times. 04 ZPRODUCT-ID-CODE type ZSPI-DDL-CHAR. 04 ZDATA-ID type ZSPI-DDL-CHAR. 04 ZDATA-ENCODING type ZSPI-DDL-CHAR. 04 ZDATA-LENGTH type ZSPI-DDL-CHAR. 04 ZDETAILED-DATA type ZDNI-DDL-CHAR44. 02 ZPSID-INDEX type ZSPI-DDL-INT.
ZDNI-MAP-INST-RECOMM-ACT ZDNI Tokens ZDETAILED-DATA contains explanatory text. ZPSID-INDEX contains a code point and count that together specify a particular Product ID Subvector. This field corresponds to a Product ID Index (X‘83’) Network Alert Common Subfield. For the meaning of the values, see the IBM Systems Network Architecture: Formats manual.
ZDNI-MAP-TEXT-QUAL ZDNI Tokens value specified in ZCODE-POINT. Each instance of ZDETAIL-DATA contains the following fields: ZPRODUCT-ID-CODE specifies the Product ID Subvector code. ZDATA-ID contains a code point that designates the type of data carried in the Detailed Data (X‘82’) subfield. For the meaning of the code point, see the description of this subfield in the IBM Systems Network Architecture: Formats manual. ZDATA-ENCODING contains a code point specifying how the detailed data is encoded.
ZDNI-MAP-UNDET-RECOMM-ACT ZDNI Tokens This token has the definition ZDNI-DDL-TEXT-QUAL and the token number ZDNI-TNM-TEXT-QUAL. def ZDNI-DDL-TEXT-QUAL. 02 ZLENGTH 02 ZMSG end type ZSPI-DDL-CHAR. type ZDNI-DDL-CHAR150. ZLENGTH specifies the number of bytes used in the next field. ZMSG contains explanatory text.
ZDNI-MAP-UNDET-RECOMM-ACT ZDNI Tokens ZCODE-POINT specifies a code point for stored text that describes the recommended action to correct the alert condition. This field corresponds to the Recommended Actions (X‘81’) Network Alert Common Subfield. For the meaning of this code point, see the IBM Systems Network Architecture: Formats manual. ZDETAIL-DATA-NUM specifies the number of instances of ZDETAIL-DATA the token contains. The token can contain as many as three instances.
ZDNI-MAP-USER-CAUSE ZDNI Tokens ZDNI-MAP-USER-CAUSE This extensible structured token contains information obtained from a User Causes (X‘01’) User Causes Subfield that is included in a User Causes (X‘94’) Alert MS Subvector. The information consists of a code point for stored text that indicates the probable user cause for the alert. An instance of ZDNI-MAP-USER-CAUSE is accompanied by an instance of ZDNI-MAP-USER-RECOMM-ACT.
ZDNI-MAP-USER-RECOMM-ACT ZDNI Tokens ZDATA-ENCODING contains a code point specifying how the detailed data is encoded. For the meaning of the code point, see the IBM Systems Network Architecture: Formats manual. ZDATA-LENGTH specifies the number of bytes used in the ZDETAILED-DATA field. ZDETAILED-DATA contains explanatory text. ZPSID-INDEX contains a code point and count that together specify a particular Product ID Subvector.
ZDNI-MAP-USER-RECOMM-ACT ZDNI Tokens ZDETAIL-DATA-NUM specifies the number of instances of ZDETAIL-DATA the token contains. The token can contain as many as three instances. ZDETAIL-DATA carries information corresponding to the information contained in one Detailed Data (X‘82’) Network Alert Common Subfield. The ZDNI-MAP-USER-RECOMM-ACT token can contain as many as three instances of ZDETAIL-DATA, depending on the value specified in ZCODE-POINT.
Subsystem ID ZDNI Tokens Subsystem ID ZDNI-VAL-SSID is the subsystem ID associated with the ZDNI tokens. ZDNI-VALSSID has the following definition: def ZDNI-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-ZDNI. 02 Z-VERSION type ZSPI-DDL-UINT value is ZDNI-VAL-VERSION.
Version Value ZDNI Tokens SNAX/XF and SNAX/APN Event Management Programming Manual—426859-001 A -16
Glossary ABORTING state. As defined by SCF or SPI, the state of an object when an ABORT command has been issued against that object but has not completed. This state indicates that sessions and data traffic are being interrupted abnormally, with possible loss of data. ACTIVE state. An SNA object state indicating that the object is able to perform the function for which it was designed. ADD command. A sensitive Subsystem Control Facility (SCF) command that defines an object to a subsystem.
attribute token Glossary With associated passthrough, no USS messages flow from the host SSCP to the device. Logon requests from the device flow to the SSCP and not the host SSCP. attribute token. A parameter or response token that represents one or more characteristics of an object. availability. The amount of time an application running on a Compaq system can be used effectively by a user of that application. backup process.
Glossary channel status word (CSW) channel status word (CSW). An area in storage that provides information about the termination of I/O operations. character set. A defined collection of character representations valid for a particular program, printer, or language. cluster controller. A device that controls access (I/O operations) to a group of terminals or printers connected to it.
configuration Glossary configuration. The definition or alteration of characteristics of an object. Configuration of most SNAX products can be performed either interactively (using a command interpreter such as SCF) or programmatically (using a management programming interface such as SPI). consumer distributor. An EMS distributor process that returns selected event messages to management applications upon request. See also distributor. context token.
data terminal equipment (DTE) Glossary enclosed in lists. Programs can set the current position to them and can retrieve their values by using the NEXTCODE and NEXTTOKEN operations. See also header token. data terminal equipment (DTE). That part of a data station that serves as a data source, data link, or both, and provides for the data communications control function according to protocols. DDL. Data Definition Language. definite response mode.
DLU Glossary DLU. Destination logical unit. domain. In SNA, a system services control point (SSCP) and the PUs, LUs, links, and associated resources that the SSCP has the ability to control by means of activation requests and deactivation requests. DSM. See Distributed Systems Management (DSM). DTE. See data terminal equipment (DTE). dynamic passthrough.
error number Glossary other error lists. The return token cannot be included in an error list. See also return token. error number. A value that can be assigned to a return token, or to the last field of an error token, to identify an error that occurred. Some error numbers are defined in the SPI common extensions (ZCOM) definitions; others are defined by individual subsystems. error token.
Glossary Extended Logon Facility (XLF) Extended Logon Facility (XLF). A feature of SNAX/APN that enables LU-LU sessions between Compaq applications and remote 3270 devices in an IBM network and between Compaq applications that emulate 3270 devices and applications in an IBM network. See also SNAX/APN logon manager (TLOGMGR) and Tandem Logon Manager for IBM Systems (ILOGMGR). TLOGMGR and ILOGMGR are the components of XLF. extensible structure.
header token Glossary header token. In an SPI message, a token that provides information pertaining to the message as a whole. Header tokens differ from other tokens in several ways: they exist in the buffer at initialization and their values are usually set by SSINIT, they can occur only once in a buffer, they are never enclosed in a list, they cannot be moved to another buffer with SSMOVE, and programs cannot position to them or retrieve their values using the NEXTCODE or NEXTTOKEN operation.
Kanji Glossary Kanji. A graphic character set consisting of symbols used in Japanese ideographic alphabets. Each character is represented by 2 bytes. Kanji character set. Synonym for extended graphic character set (EGCS). Katakana. A character set of symbols used in one of the two common Japanese phonetic alphabets, which is used primarily to write foreign words phonetically. line-handler process. The process within the SNAX/XF or SNAX/APN subsystem that implements line-specific protocols.
management application Glossary management application. In general, an application that monitors or controls another entity. In the context of DSM, an application process that opens a management or subsystem process to control a subsystem. This process can issue SPI commands to subsystems and retrieve EMS event messages to assist in managing a computer system or a network of systems.
NonStop™ Glossary NonStop™. On Compaq NonStop™ systems, processing characterized by continued operation even when a component fails, when equipment is being repaired or replaced, or while new processors or peripheral devices are being added to the system. nonswitched line. A telecommunication line on which connections do not have to be established by dialing. Also called leased line. Contrast with switched line. null value.
physical unit (PU) Glossary physical unit (PU). That part of a device (hardware or software) that provides control functions for its own node and for the other less intelligent device nodes attached to the PU. PIU. See path information unit (PIU). PLU. See primary logical unit (PLU). port. An entity that provides a SNAX/XF or SMNAX/APN line with access to an X25AM subdevice or a TLAM session. The X25AM subdevice provides access to an X.25 network using the QLLC protocol. primary logical unit (PLU).
reset state Glossary reset state. An object state indicating the object has been changed back to its original configuration. application by a subsystem in reaction to a DSM command. response message. An SPI message sent from a subsystem to an application program in reaction to a command message. A message always contains entire response records (a single response record cannot be split across multiple messages). If there are multiple records in a response message, each record is enclosed in a data list.
session Glossary SNAX/APN, passing them on to a line handler when necessary. The same service manager is provided as part of SNAX/XF, and SNAX/APN, and a single service manager can manage both products. Multiple service managers can also be configured. session. A temporary logical connection between two network-addressable units (NAUs) for the purpose of exchanging data and control information in accordance with ground rules that have been agreed upon for that exchange.
SNAX Creator Glossary SNAX Creator. Compaq software that supports SNAX/XF and SNAX/CDF by creating new application processes. Creator enables the creation of a Compaq process when a terminal on an IBM subarea network sends a logon request to the application. Creator does not support SNAX/APN. SNAX Creator-2. Compaq software that supports SNAX/APN and SNAX/XF by creating new application processes.
SSCP Glossary multiple subsystems (for example, the EMS standard definitions). An application using SPI needs the SPI standard definitions and also the subsystem definitions for all subsystems with which it communicates. See also definition files. SSCP. See system services control point (SSCP). SSCP-LU session. In SNA, a session between an SSCP and an LU that enables the LU to request the SCCP to help initiate LU-LU sessions. SSID. See subsystem ID (ZSPI-TKN-SSID). STARTED state.
Subsystem Control Facility (SCF) Glossary Subsystem Control Facility (SCF). A Compaq product that is used to interactively configure, control, and collect information about Compaq data communications subsystems. SCF can be used to dynamically configure and manage the entities in the SNAX/XF environment. Subsystem Control Point (SCP). The management process for many Compaq subsystems. Several instances of this process can run on a system.
Systems Network Architecture (SNA) Glossary Systems Network Architecture (SNA). A description of the logical structure, formats, protocols, and operational sequences for transmitting information units through, and controlling the configuration and operation of, networks. system services control point (SSCP).
token code Glossary token code. A 32-bit value that, as the first part of an SPI token, allows any token to be identified and located within a message. token data type. The part of a token code that defines the kind of value (such as integer or file name) allowed for the token. token length. The part of a token code that indicates the length, in bytes, of the corresponding token value.
XID frame Glossary XID frame. Exchange identification frame. XLF. See Extended Logon Facility (XLF). ZCDG-. A token prefix for common diagnostics tokens. These tokens are defined in more detail in the SPI Common Extensions Manual. ZCL2-. A token prefix for tokens defined by the Common Level 2 (CL2) modules used by SNAX/XF, SNAX/APN, and EnvoyACP/XF. ZCOM-. A token prefix for SPI common extensions tokens. These tokens are defined in more detail in the SPI Common Extensions Manual. ZDNI-.
$SSCP Glossary SNAX/XF and SNAX/APN Event Management Programming Manual—426859-001 Glossary -22
Index A ACTLINK failure 3-127, 4-103 ACTPU failure 3-125 Alerts, CNM event message 3-97 ZDNI tokens for A-1/A-15 ALLOCATESEGMENT procedure error received by LUNS 3-87, 4-86 failure on call 3-6, 4-6 B Backup service manager, checkpointing to 3-140, 3-143, 4-114, 4-117 Basic alert, CNM 3-97, 3-101, A-1 Buffers I/O, memory allocation for 3-38, 4-43 no space for LUNS request, event message 3-86, 4-85 no space, event message 3-129, 4-105 C Checkpointing, event messages descriptions 3-140/3-144, 4-114/4-118 lis
F Index EMSGET procedure 1-1 Errors state machine 3-8, 4-8 ESS table LUNS errors 3-84/3-96 Event messages categories of, for SNAX/XF 1-3 critical 2-3 from SCP 1-3 from SNAX/APN subsystem 4-1/4-155 from SNAX/XF subsystem 3-1/3-163 noncritical 2-3 Event number 2-3, 3-1, 4-1 Extended segment storage event messages about EXTPOOLPAGES limit exceeded 3-121, 4-101 no pool space, line handler 3-11, 4-11 no pool space, service manager 3-80, 4-81 unable to obtain space for initialization 3-7, 4-7 EXTPOOLPAGES modif
M Index M Memory allocation for I/O buffers and poll list 3-38, 4-43 Memory congestion, in line handler 4-40 Memory pool storage EXTPOOLPAGES limit exceeded 3-121, 4-101 lack of for line handler 3-11, 4-11 for service manager 3-80, 4-81 in backup service manager 3-140, 4-114 MULTI modifier too many lines 3-38, 4-43 N Named values ZSPI- 2-2 Noncritical events 2-3 P Passthrough sessions counts inconsistent 3-123 Path-control request error, event message 3-14, 4-14 PIU I/O PIU from unknown resource 3-134,
T Index Service manager event messages about descriptions 3-78/3-112, 3-121/3-124, 3-131/3-149, 4-79/4-92, 4-101/4-102, 4-107/4-141 list 1-4, 1-7 role in event-message generation 1-3 Session timeout for switched lines 3-63, 4-69 event message 3-63, 4-69 SET table LUNS errors 3-87/3-96, 4-86/4-89 SNAX/APN event messages from 1-7 subsystem ID shared with SNAX/XF 1-3 SNAX/APN subsystem initialization failure 4-7 SNAX/XF event messages from 1-3 subsystem ID shared with SNAX/APN 1-3 SNAX/XF subsystem initializ
V Index Unsupported RU 3-131, 4-107 USESEGMENT procedure error received by LUNS 3-88, 4-87 failure on call 3-6, 4-6 V Values, named ZSPI- 2-2 Version of DNI token definitions A-15 X XID validation error during 4-64 Z ZCOM-EVTIO-FATAL-ERR 3-3, 4-3 ZCOM-TKNSUBJ-LINE 2-5 SUBJ-LU 2-5 SUBJ-objtype 3-1, 4-1 SUBJ-PU 2-5 SUBJ-SUBSYS 2-5 ZDNI tokens A-1/A-15 ZDNI-MAPALERT-BASIC 3-101, A-1 ALERT-GENERIC 3-103, A-2 ALERT-RECFMS 3-99, A-3 FAILURE-CAUSE A-3 FAIL-RECOMM-ACT A-5 INSTALL-CAUSE A-6 INST-RECOMM-ACT A-8
Z Index ZSX1-EVT- (continued) CHECKPOINT-FAILED SNAX/APN 4-114 SNAX/XF 3-140 CHECKPOINT-INCOMPLETE SNAX/APN 4-117 SNAX/XF 3-143 CONMGR-INACT SNAX/APN 4-22 SNAX/XF 3-20 CP-SESSION-STATUS SNAX/APN 4-124 ELF-LOGON-ERR SNAX/APN 4-126 ELF-LU-REGISTER-FAILED SNAX/APN 4-122 ELF-NAME-NOT-FOUND SNAX/APN 4-137 EXT-POOL-LIMIT 3-121, 4-101 INCONS-LU-STATE SNAX/APN 4-72 SNAX/XF 3-74 INCONS-PTHRU-SESS-CNT SNAX/XF 3-123 IO-PAGES-WARNING SNAX/APN 4-43 SNAX/XF 3-38 IO-WARNING-ERR SNAX/APN 4-38 SNAX/XF 3-36 LINE-DOWN SNAX/
Z Index ZSX1-EVT- (continued) SSINIT-FAIL SNAX/APN 4-95 SNAX/XF 3-115 SSNULL-FAIL SNAX/APN 4-97 SNAX/XF 3-117 SSPUT-FAIL SNAX/APN 4-99 SNAX/XF 3-119 STATE-MACH-ERR SNAX/APN 4-8 SNAX/XF 3-8 SW-LINE-ERR SNAX/APN 4-35 SNAX/XF 3-33 SW-LU-ERR SNAX/XF 3-70 SW-PU-ERR SNAX/APN 4-55 SNAX/XF 3-51 SW-PU-FAIL SNAX/APN 4-52 SNAX/XF 3-47 SW-SESSION-TIMEOUT SNAX/APN 4-69 SNAX/XF 3-63 TOO-MANY-INBND-BYTES SNAX/APN 4-74 SNAX/XF 3-76 TRACE-STOPPED SNAX/APN 4-119 SNAX/XF 3-145 TS-FENOBUFSPACE SNAX/APN 4-105 SNAX/XF 3-129 TS
Special Characters Index ZSX1-TKN- (continued) NUM-NOBUFSPACE-ERRORS 3-130, 4-106 NUM-XPOOL-ERRORS 3-12, 4-12 POOL-SIZE 3-12, 3-81, 3-122, 4-12, 4-82, 4-102 PRIM-ABORT 3-112 PRIM-TRACE-FILE 3-146, 4-120 PUID-BLOCK 3-61, 3-64, 4-62, 4-70 PUID-BLOCK-CALLER 3-58, 3-61, 4-62 PUID-NUM 3-61, 3-64, 4-62, 4-70 PUID-NUM-CALLER 3-58, 3-61, 4-62 REJ-RECV 3-112 REJ-SENT 3-112 REQ-OR-RESP 3-132, 3-135, 3-137, 3-139, 4-108, 4-111, 4-113 SENSE-CODE 4-122, 4-125, 4-127, 4-138 SNANAME 4-77, 4-91, 4-136, 4-138 SNANETID 4-7
