SPI Common Extensions Manual Abstract This manual describes common extensions to the Subsystem Programmatic Interface (SPI) that are used by many Compaq NonStop™ Kernel subsystems. It describes SPI commands, events, errors, data definitions (ZCOM, ZCMK, and ZCDG), and the Subsystem Control Point (SCP) process. Product Version SPI D40/G05 Supported Releases This manual supports D40.00 and all subsequent D-series and G-series releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 427508-001 SPI D40/G05 February 2002 133482 SPI C30.09/D20.
SPI Common Extensions Manual Glossary Index What’s New in This Manual xiii Manual Information xiii New and Changed Information Figures Tables xiii About This Manual xv Your Comments Invited xvi Notation Conventions xvi 1.
1. Introduction to SPI Extensions (continued) Contents 1. Introduction to SPI Extensions (continued) Subsystem Control Facility (SCF) Distributed Management 1-10 1-9 2.
3. Subsystem Control Point (continued) Contents 3. Subsystem Control Point (continued) Sending Commands and Retrieving Responses 3-6 4. ZCOM Data Definitions Naming Conventions 4-1 ZCOM Definitions 4-2 ZCOM Data Structures 4-2 ZCOM Tokens 4-3 ZCOM Maps 4-19 ZCOM Commands 4-20 ZCOM Object Types 4-20 ZCOM Events 4-24 ZCOM Errors 4-24 Retired ZCOM Definitions 4-26 5.
5. Commands and Responses (continued) Contents 5. Commands and Responses (continued) FORBIDOPENS 5-38 GETVERSION 5-39 INFO 5-43 INITIALIZE 5-45 LISTDEV 5-47 LISTOBJECTS 5-49 LISTOPENS 5-51 LOAD 5-52 MOVE 5-53 NULL 5-55 PROBE 5-56 RELEASE 5-57 RENAME 5-59 REPLACE 5-61 RESET 5-62 RESETSTATS 5-63 START 5-66 STATISTICS 5-67 STATUS 5-70 STOP 5-71 SUSPEND 5-73 SWITCH 5-75 TELL 5-78 TRACE 5-79 TRACE-ENQ 5-80 VERIFY 5-81 6.
A. ZCOM Errors (continued) Contents A.
A. ZCOM Errors (continued) Contents A.
B. ZCMK Definitions (continued) Contents B.
B. ZCMK Definitions (continued) Contents B.
B. ZCMK Definitions (continued) Contents B.
C. ZCDG Definitions (continued) Contents C.
Tables (continued) Contents Tables (continued) Table B-5. Table B-6. Table C-1. Table C-2.
Tables (continued) Contents SPI Common Extensions Manual—427508-001 xii
What’s New in This Manual Manual Information SPI Common Extensions Manual Abstract This manual describes common extensions to the Subsystem Programmatic Interface (SPI) that are used by many Compaq NonStop™ Kernel subsystems. It describes SPI commands, events, errors, data definitions (ZCOM, ZCMK, and ZCDG), and the Subsystem Control Point (SCP) process. Product Version SPI D40/G05 Supported Releases This manual supports D40.
New and Changed Information What’s New in This Manual • Added these tokens to Requester Identification on page 2-13 and ZCOM-TKNREQID-desc (D-series) on page 5-3: REQID-CPU REQID-PROC-DESC REQID-PIN • • • Updated the possible values for ZCOM-TKN-CMD-POWER on page 4-3 Added ZCOM token definitions for: ° ° ° ° ° ° ° ZCOM-TKN-DIAG-OPT on page 4-4 ZCOM-TKN-FIRMWARE-FNAME on page 4-5 ZCOM-TKN-OPENER on page 4-12 ZCOM-TKN-PATH on page 4-12 ZCOM-TKN-REQID-CPU on page 4-13 ZCOM-TKN-REQID-PIN on page 4-14
About This Manual This manual describes an extended SPI subsystem management interface that extends the basic SPI protocol described in the SPI Programming Manual (formerly the Distributed Systems Management (DSM) Programming Manual): Section Description Section 1, Introduction to SPI Extensions Reviews basic SPI and summarizes the common extensions to SPI Section 2, Extended SPI Concepts Presents the concepts that extend SPI beyond the basic interface described in the SPI Programming Manual Section 3
Related Manuals About This Manual Related Manuals Management programming is part of Distributed Systems Management (DSM). This manual assumes you are familiar with these other DSM-related manuals: • • • Introduction to Distributed Systems Management (DSM) (D-series only) SPI Programming Manual EMS Manual If the subsystems you manage expect requests to be routed through an SCP process, also read the Subsystem Control Point (SCP) Management Programming Manual.
General Syntax Notation About This Manual General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual: UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}...
Notation for Messages About This Manual !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i:i. !i,o In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
Notation for Management Programming Interfaces About This Manual horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LDEV ldev [ CU %ccu | CU %... ] UP [ (cpu,chan,%ctlr,%unit) ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed.
1 Introduction to SPI Extensions The Subsystem Programmatic Interface (SPI), a central component of the NonStop Kernel Distributed System Management (DSM) architecture, is the path that management applications and subsystems use to exchange control/inquiry messages and event messages. Its basic features are described in the SPI Programming Manual. Basic SPI provides fundamental capabilities but leaves many design and implementation decisions for individual subsystem designers.
Management Applications Introduction to SPI Extensions The definition of a logical object depends on the subsystem that uses it. For example, in an X25AM subsystem, a subdevice, which is a logical object, represents a circuit, the real object. Management Applications Management applications use SPI to help them configure, control, monitor, and report the status of subsystem objects. The primary tasks of a management application differ from those of other applications.
SPI Message Format Introduction to SPI Extensions implementation of these general rules. For detailed information about the SPI interface to a particular subsystem, see the management programming manual for that subsystem. SPI Message Format SPI messages have a common structure. Each message consists of a header followed by as many tokens as necessary to convey information relevant to the message. (The number of tokens is limited by the size of the message buffer.
SPI Data Definitions Introduction to SPI Extensions SPI Data Definitions SPI-defined data items used to build SPI messages include tokens, values, command numbers, message headers, and error numbers. You define these items using the Compaq Data Definition Language (DDL), and provide them to programmers in definition files that have names beginning with the defining subsystem’s abbreviation; for example, ZSPI or ZCOM.
Overview of Extended SPI Introduction to SPI Extensions 6. An application (or user) can respond to event-generating situations according to requirements you provided. In this case, your application could stop sending requests to the subsystem. Overview of Extended SPI This comparison shows some ways the extensions build on basic SPI: Basic SPI Extended SPI Procedures Provides procedures for creating and decoding SPI messages. Uses the basic SPI procedures.
Subsystem Support Introduction to SPI Extensions Subsystem Support To determine whether a subsystem uses the extended SPI interface, see the management programming manual for that subsystem. Procedures Basic SPI provides standard procedures for working with SPI messages: SSINIT, SSNULL, SSPUT, SSPUTTKN, SSGET, SSGETTKN, SSMOVE, and SSMOVETKN. For information on these procedures, see the SPI Programming Manual. The common extensions to SPI assume the use of these procedures.
Events Introduction to SPI Extensions Events Event messages are a type of SPI message defined by basic SPI. The SPI procedures and message structures are the foundation of the EMS procedures and the event messages they process. So basic SPI provides the foundation for the event message mechanism. However, basic SPI does not define any events. Extended SPI defines common events for reporting common occurrences.
Subsystem Control Point (SCP) Introduction to SPI Extensions Subsystem Control Point (SCP) Some subsystems based on the extended SPI specification expect messages to be routed through SCP—a process supplied by Compaq. As an intermediary, SCP can communicate with multiple management applications and multiple subsystems. SCP implements some of the requirements of the extended interface, and its role includes command routing, security, and limited version reconciliation.
Subsystem Control Facility (SCF) Introduction to SPI Extensions Subsystem Control Facility (SCF) SCF is a process supplied by Compaq that provides an interactive interface to many subsystems. SCF is an example of a management application that uses the extended SPI interface, including SCP. For more information, see the Subsystem Control Facility (SCF) Reference Manual. Figure 1-2.
Distributed Management Introduction to SPI Extensions Distributed Management An application can simultaneously manage multiple subsystems and might do so by routing commands through more than one intermediate process. Figure 1-3 shows a single management application sending commands to several subsystems through two SCP processes. An application can start its own SCP process or use one that is already running. Figure 1-3.
Distributed Management Introduction to SPI Extensions Figure 1-4.
Distributed Management Introduction to SPI Extensions An application can use a fully qualified SCP process name to direct its messages to a remote SCP process. See Figure 1-5. Figure 1-5.
2 Extended SPI Concepts The extended SPI interface is based on these concepts: Topic Page Objects 2-1 Object Types 2-2 Object Names 2-4 Commands 2-7 Command Modifiers 2-8 Summary States 2-10 Subsystem Identification 2-11 Requester Identification 2-13 Objects An object is any logical or physical entity defined and controlled by a subsystem. The subsystem itself can be viewed as an object. For example, a line to an X.
Configured and Nonconfigured Objects Extended SPI Concepts Configured and Nonconfigured Objects To better define how they respond to certain commands, objects are classified according to their mode of creation: • A configured object already exists when its controlling subsystem completes initialization or is created in response to a command issued through the SPI management interface.
Special Object Types NULL and SUBSYS Extended SPI Concepts • A token (ZCOM-TKN-SUBJ-objtype), which conveys the type and name of an object that is the subject of an event message.
Object Names Extended SPI Concepts Object Names An object’s name combined with its type, the name of its manager process, and the subsystem ID uniquely identifies the object in a NonStop Kernel network at a given time. In the context of a running subsystem, name and type together uniquely identify an object, and all objects of the same type must have unique names.
Retrieving Object Names Extended SPI Concepts Retrieving Object Names To retrieve an object name (ZCOM^TKN^OBJNAME) from a message buffer: 1. Assume that you want to retrieve the first occurrence of ZCOM^TKN^OBJNAME, which has an index of 1: INT size; INT(32) info; info := ZCOM^TKN^OBJNAME; Assigning ZCOM^TKN^OBJNAME to info puts the information that is required to find the object-name value in memory into the info variable.
Object Name Templates Extended SPI Concepts the name class is a period (.), $A.#B.C is a hierarchical name for tree C, and clearly distinguishes it from other trees named C in other orchards or on other farms. Object Name Templates In all commands except ADD, the object name serves as a template with which the names of actual objects known to the subsystem are compared to select objects to which the command should be applied.
Commands Extended SPI Concepts Commands Commands specify the type of processing to be performed on objects. For descriptions of the common commands listed here, see Section 5, Commands and Responses. For a list of the common commands, see Table 5-2 on page 5-9. A command is contained in a command message, which is identified by the value ZSPI-VAL-CMDHDR in the message header. ZSPI-VAL-CMDHDR is put into the message header with the SSINIT procedure.
Command Modifiers Extended SPI Concepts Command Modifiers Some commands allow one or more command modifiers. A command modifier characterizes or assigns properties to a command. Command modifiers can be required or optional, depending on the destination-subsystem implementation of the modifiers. Command modifiers can also be subsystem-specific. SUB (Subordinate) Command Modifier The token ZCOM-TKN-SUB is called the subordinate or SUB command modifier.
Summary-State Selector Modifier Extended SPI Concepts Objects Named in STOP Command SUB Modifier Value Objects Stopped * ZCOM-VAL-SUB-NONE A,B,C * ZCOM-VAL-SUB-ALL A,B,C,…,X,Y,Z * ZCOM-OBJ-PU D,E,F,G,H To assign a SUB modifier value to the token ZCOM-TKN-SUB: INT sub^val; sub^val := ZCOM^VAL^SUB^ONLY; status := SSPUTTKN(message^buffer,ZCOM^TKN^SUB,sub^val); Summary-State Selector Modifier The token ZCOM-TKN-SEL-SUMSTATE, called the select summary-state modifier, lets you apply a command to ob
Summary States Extended SPI Concepts Summary States A summary state is a single value with which an object reports its condition or state. Objects report summary states in response to the STATUS command. Further, commands can be applied to objects selectively based on the summary states of the objects. Table 2-2. Summary States That Objects Can Report Summary State ZCOM-VAL-SUMSTATE-… General Condition Reported ABORTING The object is responding to an ABORT command or some type of malfunction.
Subsystem Identification Extended SPI Concepts Subsystem Identification The identity of the subsystem that manages an object is a necessary part of the object’s identity. (The full identity of an object in a network also includes the object’s name, its type, and the name of the subsystem process that is managing it.) Subsystem Identifier (SSID) Every subsystem has a unique four letter subsystem identifier (SSID). The first letter is always Z.
Subsystem Manager Process Identification Extended SPI Concepts manager^id allocates storage for a structure based on the template structure. Assume the manager process name is $MGR and the system name is \LOCAL. Assign these values to the structure elements: manager^id ':=' ["\LOCAL "$MGR ", "]; status := SSPUTTKN(message^buffer ,ZSPI^TKN^MANAGER ,manager^id); The manager token ZCOM-TKN-XMGR allows string representation of the manager name for use in D-series applications.
Requester Identification Extended SPI Concepts Requester Identification Most subsystems receive commands through an intermediate routing process such as SCP. It is difficult for the subsystem to identify the true originator of the request when it only communicates directly with the routing process. So every command received must contain the identity of its originator in requester identification (REQID) tokens. SCP adds REQID information to each command before forwarding it to a subsystem.
Requester Identification Extended SPI Concepts SPI Common Extensions Manual—427508-001 2- 14
3 Subsystem Control Point Subsystems that adopt the extended SPI protocol have the option to receive commands and send responses through a routing process called the Subsystem Control Point (SCP). The SCP process: • • • • Enforces command security Supports tracing Checks for version incompatibilities Reduces the number of opens that management application and subsystem processes must maintain Subsystems, including those using the extended SPI protocol, are not required to use an SCP process.
Subsystem Control Point SCP Command-Message Processing SCP Command-Message Processing An SCP process can support up to 1000 management applications and 256 subsystems at a time. Using an SCP process to route commands and responses relieves a subsystem from maintaining many concurrent openers—a single open from the SCP process might suffice. Message Size The message buffer in your application, which holds both command messages and responses, must have a length of ZCOM-VAL-MAX-RSP-BUFLEN.
Message Queueing Subsystem Control Point Also consider the possible coexistence in a system or network of some combination of C-series and D-series requesters, SCP processes, and subsystems. This table summarizes variations in SCP request routing based on these factors: XMGR Token in Request? Converted SCP? Converted Subsystem? No Irrelevant Irrelevant SCP routes the request based on the MANAGER or OBJNAME token. The MANAGER token, if present, is forwarded to the subsystem.
Message Validation Subsystem Control Point subsystem, the SCP process cancels the command. If the command message is in a queue, it is deleted from the queue. No SPI response is returned. All or part of a command might be executed before the command is canceled. Management applications should inquire about objects that might have been affected by the command message to determine whether more processing is required to recover from the cancellation.
Command Timeout Subsystem Control Point To messages bound for C-series subsystems, an SCP process adds ZCOM-MAPREQID, which contains the process ID (CRTPID) and process access ID (PAID) of the requester. Every process has a unique, four-word CRTPID. The PAID represents the process owner. The left byte of the PAID is the group number, and the right byte is the user number.
Opening an SCP Process Subsystem Control Point Opening an SCP Process To send SPI commands to an SCP process, the process must be opened using the #ZSPI qualifier. That is, the SCP process name must be specified as $processname.#ZSPI. For example, if the SCP process name is $ZNET, your application opens it as $ZNET.#ZSPI. The #ZSPI qualifier indicates to the SCP process that subsequent messages from this process follow the SPI protocol. Note.
4 ZCOM Data Definitions This section lists the standard token-naming conventions, the ZCOM tokens, and other ZCOM data definitions. For ZCMK and ZCDG definitions, see Appendix B, ZCMK Definitions, and Appendix C, ZCDG Definitions, respectively. For more information about the DDL used to express these definitions, see the Data Definition Language (DDL) Reference Manual or the SPI Programming Manual.
ZCOM Definitions ZCOM Data Definitions description is a descriptive name for the item and can contain additional hyphens. Most definitions in this section are based on structures and types defined by the basic Subsystem Programmatic Interface (SPI), so you will encounter declarations of the types ZSPI-DDL-description and ZSPI-TYP-description throughout. For descriptions of these declaration types, see the SPI Programming Manual.
ZCOM Tokens ZCOM Data Definitions ZCOM-DDL-MSG-BUFFER This definition provides a structure for a command message. The structure is used in COBOL programs. The buffer length, Z-BUFLEN, is ZCOM-VAL-BUF-LEN, which is adequate for communicating with an SCP process. The message code, Z-MSGCODE, is ZSPI-VAL-MSGCODE (-28). def ZCOM-DDL-MSG-BUFFER. 02 Z-MSGCODE type ZSPI-DDL-INT. 02 Z-BUFLEN type ZSPI-DDL-UINT. 02 Z-OCCURS type ZSPI-DDL-UINT.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-CMD-TIMEOUT token-code value token-type ssid heading ZCOM-TKN-CMD-TIMEOUT ZCOM-TNM-CMD-TIMEOUT ZSPI-TYP-TIMESTAMP "TANDEM.21.0" "Timeout". Include this token in a command to specify the number of microseconds an SCP process waits for a response from the subsystem to which SCP forwarded the command. If this time is exceeded, the command is canceled if it has not completed.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-ENQ token-code value token-type ssid heading ZCOM-TKN-ENQ ZCOM-TNM-ENQ ZSPI-TYP-ENUM "TANDEM.21.0" "Requested-tokens". Include this token in an ENQUIRE, INFO, STATISTICS, or RESETSTATS request to limit the tokens in the response to a specific few. Only tokens whose token numbers are assigned to ENQ tokens in the request are returned in the response.
ZCOM Tokens ZCOM Data Definitions ZCOM-VAL-GETVSN-NOT-ENLIT The subsystem does not support D-series data structures. ZCOM-VAL-GETVSN-ENLIT The subsystem supports D-series data structures. ZCOM-TKN-GETVSN-SECUR-SUPP token-code value token-type ssid heading ZCOM-TKN-GETVSN-SECUR-SUPP ZCOM-TNM-GETVSN-SECUR-SUPP ZSPI-TYP-ENUM "TANDEM.21.0" "Version-security".
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-GETVSN-SUPP-PARAMS token-code value token-type ssid heading ZCOM-TKN-GETVSN-SUPP-PARAMS ZCOM-TNM-GETVSN-SUPP-PARAMS ZSPI-TYP-BOOLEAN "TANDEM.21.0" "Version-parameters". A requester includes this token in a GETVERSION request to prompt a subsystem for supplemental information in the response.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-INFO-DEFLT token-code value token-type ssid heading ZCOM-TKN-INFO-DEFLT ZCOM-TNM-INFO-DEFLT ZSPI-TYP-BOOLEAN "TANDEM.21.0" "Configuration-value". A requester can include this token in an INFO command to specify whether the values in the response should reflect original (perhaps default or SYSGEN) object definitions or current definitions (which might differ from the original if ALTER commands have been issued).
ZCOM Tokens ZCOM Data Definitions ZCOM-VAL-PATH-A Switch to path A. ZCOM-VAL-PATH-B Switch to path B. ZCOM-VAL-PATH-UNDEF New path unknown. ZCOM-TKN-OBJNAME token-code value token-type ssid heading ZCOM-TKN-OBJNAME ZCOM-TNM-OBJNAME ZSPI-TYP-STRING "TANDEM.21.0" "Object-name". The OBJNAME token appears in most commands and responses. It contains an object name or object-name template identifying the objects to which a command should be applied.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-OBJSTATE-CHG-CAUSE token-code value token-type ssid heading ZCOM-TKN-OBJSTATE-CHG-CAUSE ZCOM-TNM-OBJSTATE-CHG-CAUSE ZSPI-TYP-ENUM "TANDEM.21.0" "Object-state-change-cause". This token appears in ZCOM-EVT-SUMSTATE-CHG event messages to convey the reason for the change in summary state. Subsystem-defined values can be assigned to this token.
ZCOM Tokens ZCOM Data Definitions CUG LINE PTNR-MODE TRAPDEST CUGMEMBER LU PU TRGRECV DEV LUSER PVC TRGSEND DISK MBM QOSSET TS DLIST MEAAU QUEDIST UA DLISTMEMBER MON RESOURCE USER DOMAIN MPC RMTPASSW WIN ENDPOINT MSAP ROUTE WS ENTRY MTA SAC XMIT-GROUP EXPORT MTADIST SC ZCOM-TKN-OLD-CPU token-code value token-type ssid heading ZCOM-TKN-OLD-CPU ZCOM-TNM-OLD-CPU ZSPI-TYP-INT "TANDEM.21.0" "Old-CPU".
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-OLD-PATH token-code value token-type ssid heading ZCOM-TKN-OLD-PATH ZCOM-TNM-OLD-PATH ZSPI-TYP-ENUM "TANDEM.21.0" "Old-path". The OLD-PATH token appears in ZCOM-EVT-PATH-SWITCH event messages to identify the path used by an object before the reported path switch. Valid values and the paths they identify are: ZCOM-VAL-PATH-A Object was using path A. ZCOM-VAL-PATH-B Object was using path B. ZCOM-VAL-PATH-UNDEF Object was using unknown path.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-PATH-SWITCH-CAUSE token-code value token-type ssid heading ZCOM-TKN-PATH-SWITCH-CAUSE ZCOM-TNM-PATH-SWITCH-CAUSE ZSPI-TYP-ENUM "TANDEM.21.0" "Path-switch-cause". This token appears in ZCOM-EVT-PATH-SWITCH event messages to specify the cause of the reported path switch.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-REQID-PHANDLE token-code value token-type ssid heading ZCOM-TKN-REQID-PHANDLE ZCOM-TNM-REQID-PHANDLE ZSPI-TYP-PHANDLE "TANDEM.21.0" "Requester-process-handle". This token carries the process handle of the requester. The SCP process adds this token to requests bound for converted subsystems. Subsystems can use the value of this token when issuing a PROCESS_GETINFO_ procedure call to an originating requester.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-REQID-PSTRING token-code value token-type ssid heading ZCOM-TKN-REQID-PSTRING ZCOM-TNM-REQID-PSTRING ZSPI-TYP-STRING "TANDEM.21.0" "Requester-process-string". This token carries a string consisting of either the process name of the requester (for named processes) or the character form of the CPU and PIN (for unnamed processes). Use this value when generating a human representation of the requester’s identity.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-SUB token-code value token-type ssid heading ZCOM-TKN-SUB ZCOM-TNM-SUB ZSPI-TYP-ENUM "TANDEM.21.0" "Subordinate". This token is included in commands to specify whether the command should be applied to the command object, its subordinate objects, or both.
ZCOM Tokens ZCOM Data Definitions ZCOM-TKN-SWITCH-PATH token-code value token-type ssid heading ZCOM-TKN-SWITCH-PATH ZCOM-TNM-SWITCH-PATH ZSPI-TYP-ENUM "TANDEM.21.0" "Switch-path". This token is used in the SWITCH command to specify the path to which an object should switch. Valid values are: ZCOM-VAL-PATH-A Switch to path A. ZCOM-VAL-PATH-B Switch to path B. ZCOM-TKN-TARGET-MGR token-code value token-type ssid heading ZCOM-TKN-TARGET-MGR ZCOM-TNM-TARGET-MGR ZSPI-TYP-FNAME32 "TANDEM.21.
ZCOM Tokens ZCOM Data Definitions DISCONNECT, and PROBE commands. It can be assigned any of the defined object types listed in the description of ZCOM-TKN-OBJTYPE. ZCOM-TKN-TARGET-PARENT token-code value token-type ssid heading ZCOM-TKN-TARGET-PARENT ZCOM-TNM-TARGET-PARENT ZSPI-TYP-STRING "TANDEM.21.0" "Target-parent". This token is included in MOVE commands to specify the new parent object under which the command object is placed. It is assigned the object name of the new parent.
ZCOM Maps ZCOM Data Definitions ZCOM Maps ZCOM-MAP-description is a definition for an extensible structured token. ZCOM-MAP-AGGR-STATE-CNT AGGREGATE responses include this structured token to convey the requested object type, state, and count information. ZCOM-MAP-AGGR-STATE-CNT is based on ZCOM-DDL-AGGR-STATE-CNT: def ZCOM-DDL-AGGR-STATE-CNT. 02 ZOBJTYPE type ZSPI-DDL-ENUM. 02 ZSTATE-CNT occurs 20 times 03 ZOBJSTATE type ZSPI-DDL-ENUM. 03 ZOBJCNT type ZSPI-DDL-INT2. end.
ZCOM Commands ZCOM Data Definitions ZCRTPID contains the creation-timestamp process identifier (CRTPID) of the requester. ZPAID contains the process access ID (PAID) of the request originator. ZCOM Commands Subsystem management commands have names of the form ZCOM-CMD-command, where command is one of the commands listed in Table 5-2 on page 5-9. SSINIT assigns a particular command value to ZSPI-TKN-COMMAND when it initializes the message header.
ZCOM Object Types ZCOM Data Definitions ZCOM-OBJ-… Description (page 2 of 5) CTLR Controller running in a NonStop Kernel system (compare with ADAPT) CUG Closed user group CUGMEMBER Member of a closed user group DEV Communications device, entity on a line, or I/O process represented by an LDEV object DISK Disk volume DIST Distributor—process that accepts input and sends it to other processes DLIST Distribution list DLISTMEMBER Member of a distribution list DOMAIN Collection of nodes in a
ZCOM Object Types ZCOM Data Definitions ZCOM-OBJ-… Description (page 3 of 5) MBM Mail Box Maintenance server MEAAU Mail Enabled Application MON Monitor of a collection of processes MPC Multiprotocol Over ATM Client, configured subordinate to an ATM3SA PIF MSAP Object providing services via a message-system access point MTA Message transfer agent MTADIST Message transfer agent distributor NETGROUP Group of hosts and users within a specific network domain NEWPROCESS-ERR New process create
ZCOM Object Types ZCOM Data Definitions ZCOM-OBJ-… Description (page 4 of 5) SC Server Class SCSI Small Computer System Interface SECUR-VIOL Security Violation (token type ZSPI-TYP-BOOLEAN) SEGMENT Block of data storage SERV Service or function provided by a subsystem SERVER Server or set of server processes SERV-ERR Server error (token type ZSPI-TYP-INT) SESS Session between two logical entities SNET ServerNet SOURCE Origination point of a message SRL Shared runtime library SSIDLI
ZCOM Events ZCOM Data Definitions ZCOM-OBJ-… Description (page 5 of 5) WIN Window, application, or task running on a workstation WS Intelligent workstation or PC XMIT-GROUP Bidirectional logical connection between two adjacent subarea nodes ZCOM Events Events defined for common use by subsystem have names of the form ZCOM-EVT-event, where event is one of: CPU-SWITCH PATH-SWITCH IO-FATAL-ERR SUMSTATE-CHG For descriptions of these events, see Section 6, ZCOM Event Messages.
ZCOM Errors ZCOM Data Definitions OBJ-ALRDY-IN-SUMSTATE TKN-VAL-INV OBJ-NOT-FOUND VAL-REQ OBJ-NOT-SUPP VSN-INCOMP OBJNAME-INV For descriptions of these errors, see Appendix A, ZCOM Errors.
Retired ZCOM Definitions ZCOM Data Definitions Retired ZCOM Definitions These retired definitions cannot be used in programming for any releases after C-series but are still valid to existing code released before the definitions were retired.
Retired ZCOM Definitions ZCOM Data Definitions ZCOM-VAL-MAX-ERR ZCOM-VAL-MAX-OBJTYPE ZCOM-VAL-MAX-SUMSTATE ZCOM-VAL-MAX-TKNNUM ZCOM-VAL-MIN-CMD-NOT-SENS ZCOM-VAL-MIN-CMD-SENS ZCOM-VAL-MIN-EVT ZCOM-VAL-MIN-ERR ZCOM-VAL-MIN-OBJTYPE ZCOM-VAL-MIN-SUMSTATE ZCOM-VAL-MIN-TKNNUM ZCOM-VAL-OP-REQ ZCOM-VAL-OPT-FORCED ZCOM-VAL-OPT-NONE ZCOM-VAL-OPT-ORDERLY ZCOM-VAL-PROTO ZCOM-VAL-TAKOVR ZCOM-VAL-UNKWN All ZCOM definitions related to tracing were replaced by corresponding ZTRC definitions: Retired definition Replaced
Retired ZCOM Definitions ZCOM Data Definitions Retired definition Replaced by ZCOM-ERR-TRACE-START-PEND ZTRC-ERR-START-PEND ZCOM-ERR-SCP-COLL-VSN-INCOMP ZTRC-ERR-COLL-VSN-INCOMP ZCOM-ERR-SCP-WRAP-TABLE-FULL ZTRC-ERR-WRAP-TABLE-FULL ZCOM-ERR-SCP-TRACE-MODIF-CONFL ZTRC-ERR-TRACE-MODIF-CONFL ZCOM-ERR-SCP-COLL-FAIL ZTRC-ERR-COLL-FAIL ZCOM-ERR-ATTR-NOT-MODIF ZTRC-ERR-ATTR-NOT-MODIF ZCOM-TNM-TRACE-BKUP ZTRC-TNM-BKUP ZCOM-TNM-TRACE-MODIF ZTRC-TNM-TRACE-MODIF ZCOM-TNM-TRACE-OPT ZTRC-TNM-OPT ZC
5 Commands and Responses This section describes the syntax and semantics of the extended SPI command set available to subsystems: Topic Page Common Command Tokens 5-2 Common Response Tokens 5-6 Command Security 5-8 Command-Specific Summary State Requirements 5-9 Common Commands and Responses 5-9 Basic information about sending commands and retrieving responses is presented in the SPI Programming Manual along with descriptions of the ZSPI-defined tokens that appear in commands and responses.
Common Command Tokens Commands and Responses Common Command Tokens These tokens are common to most or all commands: Values Assigned to Command Header Tokens ZSPI-TKN-COMMAND ZSPI-TKN-OBJECT-TYPE ZSPI-TKN-SSID ZSPI-TKN-MAXRESP assigned assigned assigned assigned ZCOM-CMD-command ZCOM-OBJ-objtype subsystem ID appropriate value Common Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-ty
Common Command Tokens Commands and Responses ZSPI-TKN-MAXRESP is a header token used by the requester to specify the maximum number of response records that can be accepted in the response buffer. Use the SSINIT procedure to assign one of these values: -1 The response can contain as many response records as fit in the buffer. 0 The response can contain only one response record (default). n>0 The response can contain up to n response records.
Common Command Tokens Commands and Responses ZCOM-TKN-OBJNAME specifies the name or name template that the subsystem uses to select objects for processing. At least one OBJNAME token must be included in most commands. If no MANAGER token is included in the command, SCP tries to derive the subsystem manager process name from the OBJNAME token. ZCOM-TKN-SUB is a command modifier specifying that the command should act on a certain subset of a hierarchy of objects.
Common Command Tokens Commands and Responses ZSPI-TKN-RESPONSE-TYPE specifies the type of response returned when a command can return more than one response record. Valid values are: ZSPI-VAL-ERR-AND-WARN Only response records containing errors or warnings should be returned. ZSPI-VAL-ERR-WARN-AND-NORM All response records should be returned. The token code and token value are assigned to the command message using SSPUTTKN. This token is optional.
Common Response Tokens Commands and Responses Common Response Tokens Most of the tokens associated with a response are the same for every response. Tokens from the command-message header are put in the response header. ZSPITKN-SERVER-VERSION is also put in the response header.
Common Response Tokens Commands and Responses ZSPI-TKN-RETCODE indicates the outcome of command processing. Possible values are: 0 (ZCOM-ERR-OK) No error occurred during command processing. If a warning occurred, the response contains an error list that specifies the warning. <>0 An error occurred during command processing. If an error occurred, the response contains an error list that specifies the error. This token is always present in the response.
Command Security Commands and Responses Command Security The need for command security depends on the nature of a specific subsystem and the objects it controls. SCP provides a basic command security capability and options for augmenting or overriding it.
Overriding SCP Security Commands and Responses Overriding SCP Security To override the command security normally enforced by SCP, a subsystem assigns ZCOM-VAL-SECUR-SUPP-NONE to ZCOM-TKN-GETVSN-SECUR-SUPP and includes this token in its supplemental GETVERSION response. SCP then forwards all commands, sensitive or nonsensitive, to the subsystem. Command-Specific Summary State Requirements Standard summary state transitions result from the application of certain sensitive commands.
Common Commands and Responses Commands and Responses Table 5-2.
Common Commands and Responses Commands and Responses Table 5-2.
ABORT Commands and Responses Commands are listed in alphabetic order, and their descriptions include: • • • • The command number A description of the command A list of the tokens in the command message and the response A description of any token not previously described in Common Command Tokens on page 5-2 or Common Response Tokens on page 5-6 ABORT ZCOM-CMD-ABORT (sensitive) The ABORT command stops operation of an object as quickly as possible.
ACTIVATE Commands and Responses ZCOM-TKN-CMD-POWER is not allowed in an ABORT command.
ACTIVATE Commands and Responses The object to be activated should be in the SUSPENDED summary state and is left in the STARTED summary state on completion of command processing.
ADD Commands and Responses Some Relevant Errors and Warnings CMD-INV-IN-SUMSTATE The ACTIVATE command is not valid for the object in its current summary state. OBJ-ALRDY-IN-SUMSTATE The object is already in the STARTED summary state. ADD ZCOM-CMD-ADD (sensitive) The ADD command creates or defines objects. All of the configurable attributes for an object must be specified in the command.
AGGREGATE Commands and Responses subsys-type-name represents tokens that the requester must include to declare all of the new object’s configuration attributes.
AGGREGATE Commands and Responses preceding paragraph, appears first in the buffer, with additional AGGR-STATE-CNT structures following in preferred display order.
ALLOCATE Commands and Responses ZCOM-MAP-AGGR-STATE-CNT contains object type, state, and count information in these fields: .ZOBJTYPE specifies the object type described by the state and count information in the ZOBJSTATE and ZOBJCOUNT fields. The NULL type is specified for counts that disregard type. This field appears only once in the AGGR-STATE-CNT structure. .ZOBJSTATE specifies the summary state of the objects totaled in the corresponding ZOBJCOUNT field.
ALLOCATE Commands and Responses ALLOCATE Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT-PAIR token-type ZSPI-TYP-TIMESTAMP subsys-type-name token-type subsys-defined ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type
ALLOWOPENS Commands and Responses Relevant Errors and Warnings CMD-INV-IN-SUMSTATE The ALLOCATE command is not valid for the object in its current summary state. MAX-LIMIT-EXCEEDED Allocation of the resource would exceed some subsystem-defined limit. PATH-DOWN An inaccessible path prevents resource allocation. RES-UNAVAIL The resource is not available.
ALTER Commands and Responses ALLOWOPENS Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-
ALTER Commands and Responses ALTER Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT-PAIR token-type ZSPI-TYP-TIMESTAMP subsys-type-name token-type subsys-defined ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type token-
CONNECT Commands and Responses CONNECT ZCOM-CMD-CONNECT (sensitive) The CONNECT command creates an explicit link between two or more objects. The specific characteristics of the link and the summary state for each object in the link are defined in the subsystem management programming manuals for the subsystems that support this command. Compare with DISCONNECT on page 5-31. The object from which the link is being established is specified in ZCOM-TKNOBJNAME.
CONNECT Commands and Responses ZCOM-TKN-TARGET-OBJTYPE specifies the type of the target object. If this token is not present, the value specified in ZCOM-OBJ-objtype is assumed. ZCOM-TKN-TARGET-OBJNAME specifies the name of the target object. If this token is not present, the name specified in ZCOM-TKN-OBJNAME is assumed.
CONTROL Commands and Responses CONTROL ZCOM-CMD-CONTROL (sensitive) The CONTROL command lets you issue subsystem-specific commands. Its use is subsystem-specific. For CONTROL command considerations in a subsystem, see the SCF reference manual for that subsystem. Entering this command generates an operator message that reports the command, the time it was entered, and the group and user names of the person issuing it.
COPY Commands and Responses CONTROL Response Tokens ZSPI-TKN-DATALIST token-type ZSPI-TYP-LIST ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR token-type ZSPI-TYP-FNAME32 ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-STRING ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TYP
COPY Commands and Responses COPY Command Tokens ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR token-type ZSPI-TYP-FNAME32 token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT-PAIR token-type ZSPI-TYP-TIMESTAMP subsys-type-name token-type subsys-defined ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type token-type
DELETE Commands and Responses DELETE ZCOM-CMD-DELETE (sensitive) The DELETE command removes an object from the subsystem set of defined objects. Configured objects must be deleted using this command. Nonconfigured objects can be deleted although this normally happens when they are stopped or aborted. The CMD-POWER modifier is required to delete an object that is not reporting the STOPPED summary state.
DELETE Commands and Responses ZCOM-VAL-CMDPOWER-FORCED ZCOM-VAL-CMDPOWER-MAX can be used to delete an object that is not in the STOPPED summary state and that has links to other objects. It is equivalent to this sequence: 1. ZCOM-CMD-STOP, ZCOM-VAL-CMD-POWER-FORCED The object is stopped after its current task is completed. If the object is incapable of responding, the DELETE command is rejected. If the object is already reporting the STOPPED summary state, no error is returned. 2.
DIAGNOSE Commands and Responses DIAGNOSE ZCOM-CMD-DIAGNOSE (sensitive) The DIAGNOSE command provides the means for diagnosing a line. Depending on the supplied modifiers with the command, DIAGNOSE either brings the LINE object into the DIAGNOSING state or causes it to exit from this state.
DISCONNECT Commands and Responses ZSPI-TKN-DATALIST specifies whether the DIAGNOSING state is entered or terminated. Valid enumerated values are: ZCOM-VAL-DIAG-OPT-ENTER Specifies to enter the DIAGNOSING state ZCOM-VAL-DIAG-OPT-EXIT Specifies to terminate the DIAGNOSING state ZCDG-TKN-DIAG-PHYS-ADDR contains the physical address of the primary and backup line on which to perform diagnostics. ZSPI-TKN-RETCODE indicates whether the command was successful or the reason for failure.
DISCONNECT Commands and Responses DISCONNECT Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT-PAIR token-type ZSPI-TYP-TIMESTAMP ZCOM-TKN-TARGET-OBJNAME ZCOM-TKN-TARGET-OBJTYPE ZCOM-TKN-TARGET-MGR token-type ZSPI-TYP-STRING token-type ZSPI-TYP-ENUM token-typ
DISCONNECT Commands and Responses DISCONNECT Response Tokens ZSPI-TKN-DATALIST token-type ZSPI-TYP-LIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-ENU
DUMP Commands and Responses DUMP ZCOM-CMD-DUMP (sensitive) The DUMP command copies information from one location to another for use in diagnosing problems, such as dumping a CPU for data analysis.
ENQUIRE Commands and Responses ENQUIRE ZCOM-CMD-ENQUIRE (nonsensitive) The ENQUIRE command retrieves specific information about an object. The information can consist of any of the tokens normally returned in INFO, STATUS, and STATISTICS responses. This information is uniquely defined for each subsystem. For more information, see the subsystem-specific management programming manual. The desired response tokens are specified in occurrences of ZCOM-TKN-ENQ included in the command.
ENQUIRE Commands and Responses ENQUIRE Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING subsys-type-name token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSP
EXPORT Commands and Responses EXPORT ZCOM-CMD-EXPORT (sensitive) The EXPORT command is used to export a file system to some or all remote client systems. Its use is specific to only the NFS subsystem.
FORBIDOPENS Commands and Responses FORBIDOPENS ZCOM-CMD-FORBIDOPENS (sensitive) The FORBIDOPENS command prohibits new links to an object. This does not prevent the creation of links from the command object to other objects, and it does not affect any link already in existence. The effect of this command is canceled by using the ALLOWOPENS command. The object must be in the STARTED summary state.
GETVERSION Commands and Responses No subsystem-defined tokens can be included in a FORBIDOPENS command.
GETVERSION Commands and Responses segmented responses (in ZSPI-TKN-SEGMENTATION). This form of the command is called a supplemental GETVERSION request. All SPI subsystems support the GETVERSION command. Subsystems can return additional tokens specifying the version information for specific objects. For more information, see the subsystem-specific programming management manuals.
GETVERSION Commands and Responses GETVERSION Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING ZSPI-TKN-SERVER-BANNER token-type ZSPI-TYP-CHAR50 ZSPI-TKN-SEGMENTATION ZCOM-TKN-GETVSN-SECUR-SUPP ZCOM-TKN-GETVSN-SENS-GRP ZCOM-TKN-GETVSN-TRACE-SUPP ZCOM-TKN-GETVSN-LVL token-ty
GETVERSION Commands and Responses nn is a two-digit code, used in combination with the class code to identify a specific product. For example, T9153 is the product code for Pathway. v is the version letter for the operating system release, such as the C in C20. ff is the version number of the operating system release, such as the 20 in C20. ddmmyy is the release date day, month, and year. misc contains additional information.
INFO Commands and Responses ZTRC-VAL-SUPP-NONE SCP trace support is disabled. SCP forwards all TRACE commands to the subsystem without intervention. ZTRC-VAL-SUPP-ALL SCP handles tracing for all subsystem objects; the CMP tracing environment is used for LDEV objects, and the SCP tracing environment is used for non-LDEV objects. ZTRC-VAL-SUPP-SCP-ONLY SCP uses the SCP tracing environment for all subsystem objects, LDEV and non-LDEV.
INFO Commands and Responses INFO Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT-PAIR token-type ZSPI-TYP-TIMESTAMP ZCOM-TKN-ENQ ZCOM-TKN-INFO-DEFLT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-BOOLEAN ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-CO
INITIALIZE Commands and Responses INFO Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING subsys-type-name token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSP
INITIALIZE Commands and Responses The INITIALIZE command prepares an object to be used in a NonStop Kernel subsystem. The objects to which you can apply this command vary depending on the subsystem.
LISTDEV Commands and Responses Example -> INITIALIZE DISK $DATA1 LISTDEV ZCOM-CMD-LISTDEV (nonsensitive) The LISTDEV command retrieves DEVICEINFO information for all devices of the type and subtype specified in the command. For more information, see the Subsystem Control Point (SCP) Management Programming Manual.
LISTDEV Commands and Responses If this token is omitted from the command, information is returned for all devices configured in the system. ZSCP-MAP-XLISTDEV-PROC returns DEVICEINFO information with CPU and PIN in separate fields. Multiple occurrences of this structure can be returned, one for each device type/subtype combination specified in the command. The information is returned in these fields: .ZLDEV The logical device number .ZDEVNAME The logical device name .
LISTOBJECTS Commands and Responses LISTOBJECTS ZCOM-CMD-LISTOBJECTS (nonsensitive) The LISTOBJECTS command lists objects defined by or known to a subsystem. The content of the response depends on the tokens specified in the command: • • • If the request contains ZSPI-TKN-OBJECT-TYPE set to ZCOM-OBJ-NULL, and ZCOM-TKN-OBJNAME is missing or empty, the responses contain all the objects known to the subsystem.
LISTOBJECTS Commands and Responses LISTOBJECTS Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME . . .
LISTOPENS Commands and Responses LISTOPENS ZCOM-CMD-LISTOPENS (nonsensitive) The LISTOPENS command retrieves information about the originators of links to an object (openers of the subsystem, for example). The information is returned in an extensible structured token. The format and content of this token depend on the subsystem. See the subsystem-specific management programming manual.
LOAD Commands and Responses LOAD ZCOM-CMD-LOAD (sensitive) The LOAD command downloads a file into an object (software into a controller, for example). The identity of the download file is known to the subsystem and can only be changed with an ALTER command. If the object to be loaded is a soft controller, precede the LOAD command with a RESET command. Apply this command only to objects reporting the STOPPED summary state.
MOVE Commands and Responses LOAD Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TYP-STR
MOVE Commands and Responses The new parent object is specified in ZCOM-TKN-TARGET-PARENT.
NULL Commands and Responses NULL ZCOM-CMD-NULL (nonsensitive) The NULL command is used to obtain information or identify all objects that various subsystems support. Its use is subsystem-specific.
PROBE Commands and Responses PROBE ZCOM-CMD-PROBE (nonsensitive) The PROBE command verifies the condition of a link. The tested link is that between the command object (specified in the OBJNAME and OBJTYPE tokens) and the object specified by the TARGET tokens. The link is tested by sending test data to the target object. The data might be routed through several objects before reaching the target object. The target object then acknowledges receipt of the test data.
RELEASE Commands and Responses ZCOM-TKN-TARGET-MGR specifies the local name of the manager process of the object at the other end of the link. If this token is not present, and the information is not included in ZCOMTKN-TARGET-OBJNAME, the name specified in ZSPI-TKN-MANAGER is assumed.
RELEASE Commands and Responses RELEASE Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT-PAIR token-type ZSPI-TYP-TIMESTAMP ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type token-type token-type token-type ZSPI-TYP-ENUM
RENAME Commands and Responses RENAME ZCOM-CMD-RENAME (sensitive) The RENAME command changes an object’s name. The RENAME command does not change an object’s position in a hierarchy (for this capability, see MOVE on page 5-53).
RENAME Commands and Responses RENAME Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TYP
REPLACE Commands and Responses REPLACE ZCOM-CMD-REPLACE (sensitive) The REPLACE command installs a new version of an object while the object is executing.
RESET Commands and Responses Examples These are storage-specific examples: -> REPLACE $DATA00, PROGRAM $SYSTEM.ZDP2.TSYSDP2 -> REPLACE $DATA*, PROGRAM $SYSTEM.ZDP2.TSYSDP2 -> REPLACE $DATA*, PROGRAM $SYSTEM.ZDP2.TSYSDP2,COMMIT -> REPLACE DISK $*, PROGRAM $SYSTEM.ZDP2.TSYSDP2,SUB MAGNETIC,SEL STOPPED -> REPLACE SUBSYS $ZZSTO,SUB MAGNETIC,PROGRAM $SYSTEM.ZDP2.
RESETSTATS Commands and Responses No subsystem-defined tokens can be included in this command.
RESETSTATS Commands and Responses The response contains all defined statistics. (Use the ENQUIRE command to retrieve selectively.) A data list is returned for each object. All statistics reported in a single occurrence of the statistics structure have the same sample and reset times.
RESETSTATS Commands and Responses RESETSTATS Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING subsys-stats-struct subsys-type-name stat-template structure token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-typ
START Commands and Responses Relevant Error TKN-VAL-INV A command token contains an invalid value. START ZCOM-CMD-START (sensitive) The START command makes an object operational. Any activity associated with this transition—such as implicit link formation, code downloading, hardware resets, and so on—can still occur. Subsystems can allow this command to be applied to an object reporting any summary state. Upon completion of command processing, the object reports the STARTED summary state.
STATISTICS Commands and Responses START Response Tokens ZSPI-TKN-DATALIST token-type ZSPI-TYP-LIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSP
STATISTICS Commands and Responses STATISTICS Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT-PAIR token-type ZSPI-TYP-TIMESTAMP ZCOM-TKN-ENQ token-type ZSPI-TYP-ENUM ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type t
STATISTICS Commands and Responses STATISTICS Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING subsys-stats-struct subsys-type-name stat-template structure token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-typ
STATUS Commands and Responses STATUS ZCOM-CMD-STATUS (nonsensitive) The STATUS command retrieves the current summary state of an object, the last error associated with the object, and additional status information that might include: • • Information that characterizes an object but was not known when the object was created and was not part of the object’s original definition The values of any object configuration attributes (normally returned in an INFO response) that have been modified by some means ou
STOP Commands and Responses STATUS Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZCOM-TKN-OBJSTATE token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING token-type ZSPI-TYP-ENUM subsys-type-name token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-typ
STOP Commands and Responses STOP Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT ZCOM-TKN-CMD-POWER token-type token-type token-type token-type subsys-type-name token-type subsys-defined ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type token-type token-type token-t
SUSPEND Commands and Responses STOP Response Tokens ZSPI-TKN-DATALIST token-type ZSPI-TYP-LIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING subsys-type-name token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI
SUSPEND Commands and Responses SUSPEND Command Tokens ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT ZCOM-TKN-CMD-POWER token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-INT-PAIR ZSPI-TYP-TIMESTAMP ZSPI-TYP-ENUM ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type to
SWITCH Commands and Responses SUSPEND Response Tokens ZSPI-TKN-DATALIST token-type ZSPI-TYP-LIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING subsys-type-name token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZS
SWITCH Commands and Responses The CPU, PATH, and subsystem-defined resource specifiers are mutually exclusive. Only one can be included in the command buffer. Note. If a controller belonging to the 6100 controller family is part of a path, the effect of the SWITCH command on path changes depends on the controller configuration. For a complete explanation, see the Subsystem Control Facility (SCF) Reference Manual.
SWITCH Commands and Responses SWITCH Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING subsys-type-name token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-
TELL Commands and Responses TELL ZCOM-CMD-TELL (nonsensitive) The TELL command sends a text message to an object. Its implementation is subsystem-specific. See the appropriate management programming manual.
TRACE Commands and Responses TRACE ZCOM-CMD-TRACE (sensitive) The TRACE command is used to initiate, modify, or terminate tracing activity. For more information, see the Subsystem Control Point (SCP) Management Programming Manual.
TRACE-ENQ Commands and Responses Relevant Errors and Warnings CMD-SEQ-INV The command cannot be executed because of the current condition or activity of the object. FNAME-INV A file related to the command is the wrong type. FTYPE-INV The command contains a syntactically invalid file name. INV-IN-SUMSTATE The command is invalid for the summary state reported by the object.
VERIFY Commands and Responses TRACE-ENQ Response Tokens ZSPI-TKN-DATALIST ZSPI-TKN-MANAGER token-type ZSPI-TYP-LIST token-type ZSPI-TYP-FNAME32 or ZCOM-TKN-XMGR token-type ZSPI-TYP-STRING ZSPI-TKN-RETCODE token-type ZSPI-TYP-INT ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-STRING subsys-type-name token-type subsys-defined ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZS
VERIFY Commands and Responses VERIFY Command Tokens ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR token-type ZSPI-TYP-FNAME32 token-type ZSPI-TYP-STRING ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-INT-PAIR token-type ZSPI-TYP-TIMESTAMP subsys-type-name token-type subsys-defined ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type token-t
6 ZCOM Event Messages This section describes the event messages defined by ZCOM. These descriptions define the required contents and standard message text of the ZCOM event messages. The subsystem generating the message must include the listed tokens and can include additional tokens not listed here. Tokens in the message are described only if they have not been described elsewhere or if they have special significance within the context of the event.
–2 ZCOM-EVT-PATH-SWITCH ZCOM Event Messages ZCOM-TKN-OLD-CPU specifies the CPU where the object was running before the switch. ZCOM-TKN-NEW-CPU specifies the CPU where the object is now running. ZCOM-TKN-CPU-SWITCH-CAUSE contains the reason for the switch. For possible values, see the description of this token in ZCOM-TKN-CPU-SWITCH-CAUSE on page 4-4. Cause. The switch might be in response to an interactive command, a programmatic request, or a software or hardware failure.
–3 ZCOM-EVT-SUMSTATE-CHG ZCOM Event Messages ZCOM-TKN-NEW-PATH identifies path used by the object following the switch. For valid values, see the description of this token in ZCOM-TKN-NEW-PATH on page 4-8. Valid values are the same as those for ZCOM-TKN-OLD-PATH. ZCOM-TKN-PATH-SWITCH-CAUSE indicates the reason for the path switch. For valid values, see ZCOM-TKN-PATHSWITCH-CAUSE on page 4-13. Cause.
–4 ZCOM-EVT-IO-FATAL-ERR ZCOM Event Messages ZCOM-TKN-OBJSTATE-CHG-CAUSE indicates the reason for the change of summary state. For valid values, see ZCOM-TKN-OBJSTATE-CHG-CAUSE on page 4-10. Cause. The subsystem’s best guess at the cause of the change is indicated by the value of ZCOM-TKN-OBJSTATE-CHG-CAUSE. Effect. See the management programming manual for the subsystem that issued the message. Recovery. See the management programming manual for the subsystem that issued the message.
–4 ZCOM-EVT-IO-FATAL-ERR ZCOM Event Messages ZCOM-TKN-IO-FATAL-ERR-CAUSE contains the cause of the error: ZCOM-VAL-IO-ERR-ALLOCATESEG ALLOCATESEGMENT or SEGMENT_ALLOCATE_ procedure failed. ZCOM-VAL-IO-ERR-BROTHER-DEAD The IOP’s brother process died. ZCOM-VAL-IO-ERR-CAP-CLIP-CONF CAP^CLIP^CONFIG message to CSM failed. ZCOM-VAL-IO-ERR-CSM-OWNERSHIP CSM ownership error. ZCOM-VAL-IO-ERR-CSM-TIMEOUT CSM timed out with error #1147 CSM^ERR^SYNC.
–4 ZCOM-EVT-IO-FATAL-ERR ZCOM Event Messages SPI Common Extensions Manual—427508-001 6 -6
A ZCOM Errors This appendix lists common ZCOM error numbers and associated error lists. The error numbers have names beginning with ZCOM-ERR-. Subsystems return these errors in the response token ZSPI-TKN-RETCODE and in the Z-ERROR field of ZSPI-TKNERROR, which is included in every error list. For descriptions of ZCMK errors and ZCOM errors as issued by ZCMK-based subsystems, see Appendix B, ZCMK Definitions. Individual subsystems can add information to the error lists.
ZCOM Error Definitions ZCOM Errors Table A-1.
ZCOM Error Definitions ZCOM Errors Table A-1.
ZCOM Error Definitions ZCOM Errors Table A-2.
–1 ZCOM-ERR-ALRDY-USING-RES (warning) ZCOM Errors Table A-2.
–2 ZCOM-ERR-CMD-ACCEPTED (warning) ZCOM Errors Cause. The new resource to which the SWITCH command would assign the object is already being used by that object. Effect. The switch is not performed. Recovery. Specify another resource. –2 ZCOM-ERR-CMD-ACCEPTED (warning) The command has been accepted by the subsystem and is being processed, but has not yet been completed. This error can be issued by a subsystem if the execution of a command is taking a long time to complete.
–4 ZCOM-ERR-CMD-MISMATCH (error) ZCOM Errors ZCOM-TKN-OBJNAME contains the name of the object to which the command was not applied and is always included in the error list for this error. ZCOM-TKN-OBJTYPE specifies the type (ZCOM-OBJ-objtype) of the object to which the command was not applied and is always included in the error list for this error. ZCOM-TKN-OBJSTATE is the summary state reported by the object.
–5 ZCOM-ERR-CMD-NOT-SUPP (error) ZCOM Errors subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause. The command cannot be applied to objects of the specified type. Effect. The command is rejected. Recovery. For valid command/object-type combinations, see the subsystem-specific management programming manual. –5 ZCOM-ERR-CMD-NOT-SUPP (error) The request specifies an invalid, unknown, or unsupported command.
–7 ZCOM-ERR-CMD-TIMED-OUT (error) ZCOM Errors summary state (see ZCOM-ERR-CMD-INV-IN-SUMSTATE or ZCOM-ERR-OBJALRDY-IN-SUMSTATE).
–8 ZCOM-ERR-CMD-TOO-LARGE (error) ZCOM Errors ZCOM-TKN-OBJTYPE specifies the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. Cause. The time period specified in the TIMEOUT modifier expired before the subsystem responded to the command. Unavailable hardware or software resources might be the root cause. Effect. The command is canceled. Recovery.
–9 ZCOM-ERR-FNAME-INV (error) ZCOM Errors –9 ZCOM-ERR-FNAME-INV (error) A command contains invalid file-name syntax. The invalid file name can be contained in a simple token or in a field of a structured token.
–10 ZCOM-ERR-FS-ERR (error) ZCOM Errors –10 ZCOM-ERR-FS-ERR (error) A procedure call to the file system failed during processing of a request. For example, an OPEN was rejected by a process. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR .Z-SSID .
–11 ZCOM-ERR-FTYPE-INV (error) ZCOM Errors subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause. Depends on the specific file-system error. Effect. The command is canceled. Recovery. See the Guardian Procedure Errors and Messages Manual. –11 ZCOM-ERR-FTYPE-INV (error) A file specified in the request is not the correct file type for its intended use.
–12 ZCOM-ERR-MAX-LIMIT-EXCEEDED (error) ZCOM Errors –12 ZCOM-ERR-MAX-LIMIT-EXCEEDED (error) A fixed limit or configuration limit was exceeded. Generally, this error is used to report any overrun of a limit, including internal control blocks or tables.
–14 ZCOM-ERR-NO-MEM-SPACE (error) ZCOM Errors ZCOM-TKN-OBJTYPE specifies the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. subsys-type-name represents any number of subsystem-defined tokens. At least one of these must identify the lost modem signal. See the subsystem-specific management programming manual. Cause. The modem has a hardware fault or was placed in an unexpected state. Effect. The command is not applied. Recovery.
–15 ZCOM-ERR-OBJ-ALRDY-DEF (error) ZCOM Errors –15 ZCOM-ERR-OBJ-ALRDY-DEF (error) An ADD request attempted to define an already defined object.
–17 ZCOM-ERR-OBJ-NOT-FOUND (error) ZCOM Errors ZCOM-TKN-OBJTYPE specifies the type (ZCOM-OBJ-objtype) of the object being processed and is always included in the error list for this error. ZCOM-TKN-OBJSTATE reports the summary state of the object at the time the command was processed. subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause.
–18 ZCOM-ERR-OBJ-NOT-SUPP (error) ZCOM Errors –18 ZCOM-ERR-OBJ-NOT-SUPP (error) The specified object type is not supported by this subsystem.
–20 ZCOM-ERR-PATH-DOWN (error) ZCOM Errors ZCOM-TKN-OBJTYPE contains the object type (ZCOM-OBJ-objtype) specified in the request and is always included in the error list for this error. subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause. The command contains an improperly formed object-name template. Effect. The command is rejected. Recovery. Correct the template.
–21 ZCOM-ERR-RES-NOT-CONFIG (error) ZCOM Errors –21 ZCOM-ERR-RES-NOT-CONFIG (error) A SWITCH command specified a target resource that is not known to the subsystem.
–23 ZCOM-ERR-SPI-ERR (error) ZCOM Errors ZCOM-TKN-OBJTYPE specifies the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause. The requesting application is not authorized to issue sensitive commands. Effect. The command is rejected. Recovery.
–24 ZCOM-ERR-SSID-INV (error) ZCOM Errors ZSPI-TKN-ERROR.Z-ERROR contains the SPI error number (ZSPI-ERR-error). ZSPI-TKN-PROC-ERR identifies the SPI procedure that encountered the error (ZSPI-VAL-proc). ZSPI-TKN-ENDLIST marks the end of the nested file-system error list. subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause. Depends on the specific error. Effect. Depends on the specific error. Recovery.
–25 ZCOM-ERR-SUB-NOT-FOUND (warning) ZCOM Errors subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause. The SSID specified in the call to SSINIT is not a recognized ID. Effect. The command is canceled. Recovery. Correct the SSID and reissue the request. –25 ZCOM-ERR-SUB-NOT-FOUND (warning) A command contained the SUB modifier, but no subordinate objects were found.
–26 ZCOM-ERR-TKN-CODE-INV (error) ZCOM Errors –26 ZCOM-ERR-TKN-CODE-INV (error) An invalid, unknown, or unsupported token code was found in the request.
–27 ZCOM-ERR-TKN-DUP (error) ZCOM Errors –27 ZCOM-ERR-TKN-DUP (error) The request contains duplicate occurrences of a token that can appear only once.
–29 ZCOM-ERR-TKN-REQ (error) ZCOM Errors ZCOM-TKN-OBJNAME contains the name of the object specified in the request and is included if relevant to the analysis of the error condition. ZCOM-TKN-OBJTYPE contains the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. ZSPI-TKN-PARM-ERR contains the identity of the token whose length is invalid.
–30 ZCOM-ERR-TKN-VAL-INV (error) ZCOM Errors Effect. The command is canceled. Recovery. Rebuild the request buffer to include the required token, and reissue the request. For information about the tokens required for each command supported by that subsystem, see the programming manual for the subsystem with which you are communicating. –30 ZCOM-ERR-TKN-VAL-INV (error) An illegal value was encountered in a supported token.
–31 ZCOM-ERR-VAL-REQ (error) ZCOM Errors –31 ZCOM-ERR-VAL-REQ (error) A field in a supported structured token does not contain a required value.
–32 ZCOM-ERR-VSN-INCOMP (error) ZCOM Errors –32 ZCOM-ERR-VSN-INCOMP (error) There is a version incompatibility between the request and the subsystem.
–34 ZCOM-ERR-TKN-CNTXT-REQ (error) ZCOM Errors A subsystem returns this response when it receives a command with a context token indicating that more objects await processing but no qualifying objects are found; for example, there was another object to process but that object was since deleted. A subsystem also returns this response when a command includes the value ZSPI-VALERR-AND-WARN, but no errors or warnings apply to any object referred to by the command.
–35 ZCOM-ERR-TKN-CNTXT-CODE-INV (error) ZCOM Errors –35 ZCOM-ERR-TKN-CNTXT-CODE-INV (error) A token that is acceptable under other circumstances is not acceptable within the context of other tokens in the command buffer. The context in question is defined by tokens other than ZSPI-TKN-COMMAND, ZCOMTKN-OBJNAME, and ZCOM-TKN-OBJTYPE. If the context is based on these command and object tokens, the error ZCOM-ERR-TKN-CODE-INV is issued instead.
–36 ZCOM-ERR-TKN-CNTXT-VAL-INV (error) ZCOM Errors –36 ZCOM-ERR-TKN-CNTXT-VAL-INV (error) A token value that is acceptable under other circumstances is not acceptable within the context established by other tokens in the buffer. The context in question is defined by tokens other than ZSPI-TKN-COMMAND, ZCOMTKN-OBJNAME, and ZSPI-TKN-OBJTYPE. If the context is based on these command and object tokens, the error ZCOM-ERR-TKN-VAL-INV is issued instead.
–37 ZCOM-ERR-PWR-WEAK-FOR-SUMSTATE (error) ZCOM Errors –37 ZCOM-ERR-PWR-WEAK-FOR-SUMSTATE (error) The value specified for the ZCOM-TKN-CMD-POWER modifier is too weak for the command to be applied to an object in its current summary state. This is the case, for example, when a DELETE command with CMD-POWER-NORMAL is directed to an object in the STARTED state.
–38 ZCOM-ERR-PWR-WEAK-FOR-COND (error) ZCOM Errors –38 ZCOM-ERR-PWR-WEAK-FOR-COND (error) The value specified for the ZCOM-TKN-CMD-POWER command modifier is too weak for the command to affect an object in its current condition. This error is issued only when the command power modifier is included in the command buffer, and some condition other than the object’s summary state is the limiting factor.
–40 ZCOM-ERR-CMD-IN-PRGRSS (warning) ZCOM Errors ZCOM-TKN-OBJNAME contains the name of the object to which the command could not be applied and is always included in the error list for this error. ZCOM-TKN-OBJTYPE contains the type (ZCOM-OBJ-objtype) of the object to which the command could not be applied and is always included in the error list for this error. subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause.
–41 ZCOM-ERR-PIN-TOO-BIG (error) ZCOM Errors Recovery. No recovery is necessary. This message is informative only. –41 ZCOM-ERR-PIN-TOO-BIG (error) The SCP process returns this error to a high-PIN requester when that requester tries to send a command to an unconverted subsystem manager process.
–43 ZCOM-ERR-BKUP-NOT-RDY (error) ZCOM Errors ZCOM-TKN-OBJNAME contains the name of the object being processed and is included if relevant to the analysis of the error condition. ZCOM-TKN-OBJTYPE contains the type (ZCOM-OBJ-objtype) of the object being processed and is included if relevant to the analysis of the error condition. subsys-type-name represents any number of subsystem-defined tokens described in the subsystemspecific management programming manual. Cause.
–44 ZCOM-ERR-SWITCH-WRNG-RES (error) ZCOM Errors –44 ZCOM-ERR-SWITCH-WRNG-RES (error) The new resource specified in a SWITCH command (the resource to which the object is to be switched) does not match the configured backup resource for the object. For example, this error is issued if a SWITCH command specifying a new CPU 3 is issued to an object running in CPU 1 with a configured backup in CPU 2.
–45 ZCOM-ERR-LINKS-EXIST (error) ZCOM Errors –45 ZCOM-ERR-LINKS-EXIST (error) The specified object could not be stopped because it supports at least one link to another object.
–987 ZCOM-ERR-REQID-INV (error) ZCOM Errors ZCOM-TKN-OBJNAME contains the name of the object specified in the request and is included if relevant to the analysis of the error condition. ZCOM-TKN-OBJTYPE specifies the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. ZSPI-TKN-ERRLIST marks an embedded error list originally generated by the operating system to describe the NEWPROCESS or PROCESS_CREATE_ error. ZSPI-TKN-ERROR.
–989 ZCOM-ERR-CMD-CANCELED (warning) ZCOM Errors Error Text REQID found in SPI buffer sent by non-qualified requestor. Cause. ZCOM-MAP-REQID or ZCOM-TKN-REQID-desc was included in a command message issued by a management application that is not owned by the super ID. Effect. The request is rejected. Recovery. Remove the requester identification from your command message or correct the access ID of your process, and send the command message again.
–991 ZCOM-ERR-RCB-FULL (error) ZCOM Errors response buffer because the response consisted of more than one buffer. The SCP process could not process this particular command message because the context token was invalid. Effect. The command is rejected. Recovery. Copy the context token from the original response into the command buffer and resend the command. –991 ZCOM-ERR-RCB-FULL (error) The SCP process command-message control block table is full.
–993 ZCOM-ERR-NO-TLE (error) ZCOM Errors Effect. The SCP process rejects the command message. Recovery. Wait a few moments and reissue the command, or start an additional SCP process and route the command through it. –993 ZCOM-ERR-NO-TLE (error) A command message containing ZCOM-TKN-CMD-TIMEOUT could not be processed because no time-list element (TLE) is available.
–995 ZCOM-ERR-SERVNAME-INV (error) ZCOM Errors Recovery. If this error recurs, contact a Compaq representative. –995 ZCOM-ERR-SERVNAME-INV (error) An invalid subsystem process name was specified by ZSPI-TKN-MANAGER, ZCOM-TKN-XMGR, or ZCOM-TKN-OBJNAME. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type ZSPI-TYP-ERROR token-type ZSPI-TYP-STRING token-type ZSPI-TYP-ENUM Error Text Invalid name specified in MANAGER or OBJNAME token Cause.
–997 ZCOM-ERR-BAD-SERV-GETVSN (error) ZCOM Errors Effect. The command issued by the requester is canceled, and SCP includes this error list in the response. SCP processes also generate the event ZSCP-EVT-BADGETVSN (see the Subsystem Control Point (SCP) Management Programming Manual). Recovery. Reissue the request. If this does not help, restart the subsystem and then reissue the request. If the problem recurs, contact a Compaq representative.
–999 ZCOM-ERR-MGRNAME-INV (error) ZCOM Errors Cause. A subsystem returned invalid version information in response to SCP’s initial GETVERSION command (issued by the SCP process as part of its subsystem open activity). Effect. The command issued by the requesting application is rejected, and this error is returned in the response. D-series SCP processes also generate the event ZSCP-EVTBAD-GETVSN (see the Subsystem Control Point (SCP) Management Programming Manual). Recovery. Try reissuing the command.
B ZCMK Definitions In addition to ZSPI and ZCOM data definitions, some NonStop Kernel subsystems use a common set of data items defined by ZCMK. Subsystems based on the ZCMK definitions have a number of characteristics in common, including the way they interpret process startup parameters, the way they validate SPI messages and their content, the ZCMK tokens that appear in their commands and responses, and the ZCMK event messages and errors that they generate.
File Names in Startup Information ZCMK Definitions procedure call. For descriptions of process options relevant to ZCMK-based processes, see Process Options and Startup Parameters on page B-4. Startup parameters convey additional information to a new process. You can list them following the run options in a RUN command, declare them in PARAM statements, or include them in the startup message sent by the creator process.
Startup Parameters in PARAM Statements ZCMK Definitions Although an unrecognized or erroneous startup parameter or process option causes a process to terminate, unrecognized or erroneous specifications in PARAM statements are ignored without comment. Startup Parameters in PARAM Statements You can declare startup parameters in PARAM statements instead of including them in the RUN command: PARAM param-name param-val [, param-name param-val ] ... param-name is a defined process startup parameter name.
Process Options and Startup Parameters ZCMK Definitions 1. The process can have default file assignments. 2. A DEFINE statement overrides a process default. 3. An ASSIGN statement overrides a DEFINE assignment. Process Options and Startup Parameters [RUN] [[$vol.]subvol.
Process Options and Startup Parameters ZCMK Definitions OUT filename provides the default log file name. For important considerations affecting LOG file selection, see Selecting a Log File on page B-7. If you omit the OUT option, the command interpreter assigns a default logging file, usually the home terminal. If you include the OUT option but but do not specify a file name, logging is not performed. If the OUT option is followed by a file name, logging output goes to that file.
Process Options and Startup Parameters ZCMK Definitions CHARMAPFILE filename specifies the name of the file that the subsystem searches for character set tables. If you omit this parameter, the file $SYSTEM.SYSTEM.ZCHARMAP is used. CHARMAPNAME mapname specifies the name of the default character-map translation table. This table is found in the character-map file specified by the CHARMAPFILE parameter. If you omit this parameter, the standard ASCII-EBCDIC table is used.
Selecting a Log File ZCMK Definitions A value of FALSE, RESET, OFF, or NO disables debugging. LOG filename or LOGFILE filename specifies the name of the log file. For important considerations related to log file selection, see Selecting a Log File on page B-7. If you omit the parameter or the filename argument, the subsystem does not generate logging output. Emergency output is sent to the home terminal.
Errors During Startup ZCMK Definitions The use of a disk file as the logging file is probably the most common choice. Specifying a disk file as the log file assumes that the file already exists. The types of operations performed on such files preclude the use of an edit file. Typically, an entrysequenced file with a record size of at least 132 bytes is adequate for log output.
ZCMK Data Definitions ZCMK Definitions Other Errors During startup, if a ZCMK-based process receives a message from any process other than its creator or its creator’s backup, it rejects the message with error 2. ZCMK Data Definitions This section describes the ZCMK-defined tokens, values, and other data items: • • ZCMK tokens ZCMK maps and their associated structures ZCMK Tokens ZCMK-TKN-description is a definition for a simple token.
ZCMK Tokens ZCMK Definitions 105 Unable to allocate segment space 106 Unable to allocate segment page table space 107 Security violation on attempt to share segment 108 The pin does not exist 109 The pin does not have the segment allocated 110 Trying to share segment with self 111 Requested segment is currently being resized SEGMENT_ALLOCATE_ errors (D-series) 2 Parameter error 3 Bounds violation 4 Illegal segment-id 5 Illegal segment size 6 Unable to allocate segment space 7 Unab
ZCMK Tokens ZCMK Definitions ZCMK-TKN-ALTER-BKUP-CPU token-code value ssid token-type ZCMK-TKN-ALTER-BKUP-CPU ZCMK-TNM-ALTER-BKUP-CPU "TANDEM.83.0" ZSPI-TYP-INT. This token can appear in ALTER commands to specify a new backup CPU number in the range -1…15. Zero through 15 are CPU numbers; -1 disables the backup. If a backup process is already running in a different CPU, it is stopped and a new backup is started in the new CPU. If no backup process exists, one is started in the new CPU.
ZCMK Tokens ZCMK Definitions ZCMK-TKN-BKUP-STATE token-code value token-type ssid heading ZCMK-TKN-BKUP-STATE ZCMK-TNM-BKUP-STATE ZSPI-TYP-ENUM "TANDEM.83.0" "Backup state". This token appears in STATUS responses. Its value reports the summary state of the backup process. Valid values are: ZCOM-VAL-SUMSTATESTOPPED No backup is running, and no attempt is being made to activate one. This situation occurs when a backup CPU number of -1 has been specified or when an attempt to activate a backup fails.
ZCMK Tokens ZCMK Definitions ZCMK-TKN-CHMAP-NAME token-code value token-type ssid heading ZCMK-TKN-CHMAP-NAME ZCMK-TNM-CHMAP-NAME ZSPI-TYP-CHAR50 "TANDEM.83.0" "Charmap name". Subsystems use this token to identify the default character map. It is included in INFO responses to report the name of the current character map and can be used in ALTER commands to change the default map.
ZCMK Tokens ZCMK Definitions ZCMK-TKN-CKPERR token-code value token-type ssid heading ZCMK-TKN-CKPERR ZCMK-TNM-CKPERR ZSPI-TYP-INT "TANDEM.83.0" "Data_Initialize_Chkpt_ error code". This token appears in error and event messages to report an error that occurred during backup initialization. ZCMK-TKN-CMD-CODE token-code value token-type ssid heading ZCMK-TKN-CMD-CODE ZCMK-TNM-CMD-CODE ZSPI-TYP-ENUM "TANDEM.83.0" "Command code".
ZCMK Tokens ZCMK Definitions ZCMK-TKN-EMS-XFNAME, -XFNAME-1, -XFNAME-2, and -XFNAME-3 token-code value token-type ssid heading ZCMK-TKN-EMS-XFNAME ZCMK-TNM-EMS-XFNAME ZSPI-TYP-STRING "TANDEM.83.0" "EMS Collector". token-code value token-type ssid heading ZCMK-TKN-EMS-XFNAME-1 ZCMK-TNM-EMS-XFNAME-1 ZSPI-TYP-STRING "TANDEM.83.0" "Alternate EMS Collector #1". token-code value token-type ssid heading ZCMK-TKN-EMS-XFNAME-2 ZCMK-TNM-EMS-XFNAME-2 ZSPI-TYP-STRING "TANDEM.83.0" "Alternate EMS Collector #2".
ZCMK Tokens ZCMK Definitions ZCMK-TKN-FILE-ROLE token-code value token-type ssid heading ZCMK-TKN-FILE-ROLE ZCMK-TNM-FILE-ROLE ZSPI-TYP-ENUM "TANDEM.83.0" "File role". This token appears in error and event messages to identify the role or function being performed by the file involved in the error or event. It lets the error describe, for example, the use of a terminal as an input, output, or home terminal.
ZCMK Tokens ZCMK Definitions ZCMK-TKN-FSERR token-code value token-type ssid heading ZCMK-TKN-FSERR ZCMK-TNM-FSERR ZSPI-TYP-INT "TANDEM.83.0" "File system error code". This token appears in error and event messages to specify the file-system error code that resulted from a request. It is used as the key for explanation text appended to the error or event message. ZCMK-TKN-LIB-FILE-MOD token-code value token-type ssid heading ZCMK-TKN-LIB-FILE-MOD ZCMK-TNM-LIB-FILE-MOD ZSPI-TYP-TIMESTAMP "TANDEM.83.
ZCMK Tokens ZCMK Definitions ZCMK-TKN-LIFESTAT token-code value token-type ssid heading ZCMK-TKN-LIFESTAT ZCMK-TNM-LIFESTAT ZSPI-TYP-INT "TANDEM.83.0" "Cycle Loop Life Status". This token appears in events to explain process termination. Valid values and the termination explanations they represent are: ZCMK-VAL-LIFESTAT-ABORTREQ The process stopped in response to an operator ABORT request. ZCMK-VAL-LIFESTAT-STOPREQ The process stopped in response to an operator request (typically a STOP request).
ZCMK Tokens ZCMK Definitions The process name is in external format; that is, named processes are represented as \node.$name, and unnamed processes are represented as \node.cpu,pin. In either case, \node is omitted if the node has no name. The process name has a maximum length of 128 characters. ZCMK-TKN-LOG-XFNAME token-code value token-type ssid heading ZCMK-TKN-LOG-XFNAME ZCMK-TNM-LOG-XFNAME ZSPI-TYP-STRING "TANDEM.83.0" "Log filename". Subsystems use this token to identify the logging file.
ZCMK Tokens ZCMK Definitions ZCMK-TKN-MSG-FILE-MOD token-code value token-type ssid heading ZCMK-TKN-MSG-FILE-MOD ZCMK-TNM-MSG-FILE-MOD ZSPI-TYP-TIMESTAMP "TANDEM.83.0" "Message file creation date". This token appears in INFO responses. It contains the modification timestamp of the current message file. ZCMK-TKN-MSG-XFNAME token-code value token-type ssid heading ZCMK-TKN-MSG-XFNAME ZCMK-TNM-MSG-XFNAME ZSPI-TYP-STRING "TANDEM.83.0" "Message filename". This token contains the name of the message file.
ZCMK Tokens ZCMK Definitions Contents of NPERR(1) Contents of NPERR(2) Message Text –32000 N.A. Improper program file name -31999 N.A. Improper library file name -31998 N.A. Improper swap volume name -31997 N.A. Improper home terminal name -31996 N.A. Too many child processes -31995 N.A. Improper process name -31994 N.A.
ZCMK Tokens ZCMK Definitions Contents of NPERR(1) Contents of NPERR(2) Message Text 23 N.A. Unable to allocate segment 24 N.A. DEFINE propagation error n 27 N.A. Invalid PFS size ZCMK-TKN-PARAM-NAME token-code value token-type ssid heading ZCMK-TKN-PARAM-NAME ZCMK-TNM-PARAM-NAME ZSPI-TYP-STRING "TANDEM.83.0" "Offending parameter name". This token appears in event messages to identify an invalid startup parameter. The parameter name can be a maximum of 80 characters.
ZCMK Tokens ZCMK Definitions ZCMK-TKN-PRI-CPU token-code value token-type ssid heading ZCMK-TKN-PRI-CPU ZCMK-TNM-PRI-CPU ZSPI-TYP-INT "TANDEM.83.0" "Primary CPU". This token appears in INFO responses to identify the primary CPU for a process. ZCMK-TKN-PROC-ORD token-code value token-type ssid heading ZCMK-TKN-PROC-ORD ZCMK-TNM-PROC-ORD ZSPI-TYP-ENUM "TANDEM.83.0" "Procedure ID". This token appears in event messages and errors.
ZCMK Tokens ZCMK Definitions ZCMK-TKN-PROG-XFNAME token-code value token-type ssid heading ZCMK-TKN-PROG-XFNAME ZCMK-TNM-PROG-XFNAME ZSPI-TYP-STRING "TANDEM.83.0" "Program filename". This token appears in INFO responses. It identifies the object program file of the process being described. The maximum length of the name is 256 characters. ZCMK-TKN-SEGTYPE token-code value token-type ssid heading ZCMK-TKN-SEGTYPE ZCMK-TNM-SEGTYPE ZSPI-TYP-ENUM "TANDEM.83.0" "Segment type".
ZCMK Tokens ZCMK Definitions ZCMK-TKN-SNAERR token-code value token-type ssid heading ZCMK-TKN-SNAERR ZCMK-TNM-SNAERR ZSPI-TYP-INT "TANDEM.83.0" "SNA Sense code". This token conveys an SNA sense code. Its first occurrence in a message contains the high-order 16 bits of the sense code. If it appears twice, the second occurrence contains the low-order 16 bits. ZCMK-TKN-SSERR token-code value token-type ssid heading ZCMK-TKN-SSERR ZCMK-TNM-SSERR ZSPI-TYP-INT "TANDEM.83.0" "SPI error value".
ZCMK Tokens ZCMK Definitions ZCMK-TKN-SYS-MSG-CODE token-code value token-type ssid heading ZCMK-TKN-SYS-MSG-CODE ZCMK-TNM-SYS-MSG-CODE ZSPI-TYP-INT "TANDEM.83.0" "Code of systems message". This token appears in events to convey the message ID number of a system message. ZCMK-TKN-TKOVR-CNT token-code value token-type ssid heading ZCMK-TKN-TKOVR-CNT ZCMK-TNM-TKOVR-CNT ZSPI-TYP-INT "TANDEM.83.0" "Unplanned takeover count". This token appears in STATUS responses.
ZCMK Maps ZCMK Definitions ZCMK Maps Definitions of the form ZCMK-MAP-description describe extensible structured tokens, and are called “token maps.” ZCMK-MAP-ALTER This map can be included in an ALTER command to modify parameters that affect the behavior of a subsystem process. ZCMK-MAP-ALTER is based on ZCMK-DDL-ALTER: def ZCMK-DDL-ALTER. 02 ZDEBUG-ON-ERR 02 ZBKUP-DEBUG end. type ZSPI-DDL-BOOLEAN. type ZSPI-DDL-BOOLEAN.
ZCMK Maps ZCMK Definitions ZCMK-MAP-INFO This map is returned in INFO responses to report the internal processing conditions of a subsystem process. ZCMK-MAP-INFO is based on ZCMK-DDL-INFO: def ZCMK-DDL-INFO. 02 ZDEBUG-ON-ERR 02 ZBKUP-DEBUG 02 ZBKUP-CPU 02 ZBUF-SWAPVOL 02 ZMEM-SWAPVOL end type type type type type ZSPI-DDL-BOOLEAN. ZSPI-DDL-BOOLEAN. ZSPI-DDL-INT. ZSPI-DDL-DEVICE. ZSPI-DDL-DEVICE.
ZCMK Maps ZCMK Definitions ZCMK-MAP-LISTOP This map appears in LISTOPENS responses to report details about an opener of an object. One LISTOP map is returned for each opener of the queried process. When more than one is returned in the LISTOPENS response, they are ordered such that tokens describing all openers from the same process (as indicated by ZCMK-TKN-LISTOPXPNAME) occur together, but no order is implied between entries defining different processes.
ZCMK Maps ZCMK Definitions ZPRIM-FNUM specifies the file number used by the primary opener process. ZPROTO identifies the protocol being used by the opener. The meaning of this value is subsystem-specific. ZCMK-MAP-STATS-BUF This map is returned in STATISTICS and RESETSTATS responses to provide statistical information describing the use of buffer memory by the process. In responses to command messages, this structure appears only if the buffer pool is used by the subsystem.
ZCMK Maps ZCMK Definitions • • • These statistics were reset by a RESETSTATS command. The process was initiated. A backup takeover occurred. ZRESET-TIME records the time of the most recent of the listed occurrences. When this structure is returned in a RESETSTATS response, ZRESET-TIME indicates when the most recent reset occurred. ZSAMPLE-TIME records when the pool size was sampled.
ZCMK Maps ZCMK Definitions ZVIRTUAL records the amount of virtual memory (in bytes) originally reserved for the memory pool. This value is specified by the DATAPAGES startup parameter, multiplied by 2048. For nonextensible pools, this value is equivalent to the value in the ZCONFIG field. ZDATAPAGES records the number of data pages specified when the segment was created.
ZCMK Maps ZCMK Definitions ZCMK-MAP-STATS-MEM is based on ZCMK-DDL-INT-STATS: def ZCMK-DDL-INT-STATS. 02 ZCONFIG 02 ZCURR 02 ZMAX 02 ZRESET-TIME 02 ZSAMPLE-TIME end. type type type type type ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-TIMESTAMP. ZSPI-DDL-TIMESTAMP. ZCONFIG reports the configured or designed upper limit of the variable. If no upper limit has been established, a value of 32767 is returned. ZCURR reports the current value of the variable.
ZCMK Maps ZCMK Definitions ZCMK-MAP-STATS-RECV is based on ZCMK-DDL-INT-STATS: def ZCMK-DDL-INT-STATS. 02 ZCONFIG 02 ZCURR 02 ZMAX 02 ZRESET-TIME 02 ZSAMPLE-TIME end. type type type type type ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-TIMESTAMP. ZSPI-DDL-TIMESTAMP. ZCONFIG reports the configured or designed upper limit of the variable. If no upper limit has been established, a value of 32767 is returned. ZCURR reports the current value of the variable.
ZCMK Request Validation ZCMK Definitions ZCMK Request Validation Subsystems based on the ZCMK definitions perform a common set of tests to validate a request buffer and its contents. These tests fall into four basic categories: Category Page SPI Buffer Validation B-35 General Request Validation B-35 Token Occurrence and Value Tests B-36 Special Tests B-38 SPI Buffer Validation ZCMK-based subsystems perform these buffer tests on every request.
Token Occurrence and Value Tests ZCMK Definitions Test Result If Test Fails Retrieve the next token, allowing for end-of-buffer. Error: ZCOM-ERR-SPI-ERR Event: ZCMK-EVT-SPI-SSCALL The token’s SSID matches that of the subsystem. Error: ZCOM-ERR-SSID-INV Retrieve the address and length of the token. Error: ZCOM-ERR-SPI-ERR Compare the token number to the list of recognized tokens. Error: ZCOM-ERR-TKN-CODE-INV For tokens that can appear only once, verify that this occurrence is the first.
Token Occurrence and Value Tests ZCMK Definitions Token Test ZCMK-TKN-EMS-XFNAME Length does not exceed ZSYS-VAL-LEN-FILENAME. Allowed only in ALTER commands. ZCMK-TKN-EMS-XFNAME-1 Length does not exceed ZSYS-VAL-LEN-FILENAME. Allowed only in ALTER commands. ZCMK-TKN-EMS-XFNAME-2 Length does not exceed ZSYS-VAL-LEN-FILENAME. Allowed only in ALTER commands. ZCMK-TKN-EMS-XFNAME-3 Length does not exceed ZSYS-VAL-LEN-FILENAME. Allowed only in ALTER commands.
Special Tests ZCMK Definitions Token Test ZCOM-TKN-XMGR None. ZSPI-TKN-ALLOW-SEGMENTS Value is 1, 0, or blanks. ZSPI-TKN-ALLOW-TYPE Value is 1, 3, or 7. ZSPI-TKN-COMMENT None. ZSPI-TKN-CONTEXT None. ZSPI-TKN-MANAGER None. ZSPI-TKN-RESPONSE-TYPE Value is 6 or 7. Special Tests ZCMK-based subsystems perform three additional specialized tests on every request: 1.
ZCMK Command Processing ZCMK Definitions ZCMK Command Processing Commands sent to and responses generated by ZCMK-based subsystems can contain ZCMK tokens. For individual descriptions of these tokens, see ZCMK Data Definitions on page B-9, and the context of specific commands in these command and response descriptions. A command sent to a subsystem process that is based on the ZCMK definitions might accept additional tokens if the object specified in the command is the ZCMK-based process itself.
ALTER ZCMK Definitions ALTER Command Tokens ZCMK-MAP-ALTER specifies ZCMK debugging flags. ZCMK-TKN-ALTER-BKUP-CPU specifies a new backup CPU assignment for the process specified in the command. If a backup process is currently running in another CPU, it is stopped and restarted in the new CPU. If no backup process exists, one is started in the new CPU. Event messages are produced describing whether the attempt to initiate a backup process in the new CPU was successful.
GETVERSION ZCMK Definitions sent to the new collector. This token corresponds to the COLLECTOR startup parameter described in Process Options and Startup Parameters on page B-4. ZCMK-TKN-LOG-XFNAME specifies the identity of the log file. A zero-length name stops logging. To leave the log unchanged, omit this token from the ALTER command message.
GETVERSION ZCMK Definitions product name is the generic product name, such as Expand. T9cnnvff is the standard Compaq product number, where c is the second digit of the two-digit product class code, 9c. For example, 91 is used for transaction processing. nn is a two-digit code, used in combination with the class code to identify a specific product. For example, T9153 is the product code for Pathway. v is the version letter for the operating system release, such as the C in C20.
INFO ZCMK Definitions INFO A ZCMK-based subsystem returns the following tokens in response to an INFO command that is directed to the subsystem’s native object type: INFO Response Tokens ZCMK-TKN-CHMAP-FILE-MOD ZCMK-TKN-CHMAP-NAME ZCMK-TKN-CHMAP-NOTE ZCMK-TKN-CHMAP-XFNAME ZCMK-TKN-EMS-XFNAME ZCMK-TKN-EMS-XFNAME-1 ZCMK-TKN-EMS-XFNAME-2 ZCMK-TKN-EMS-XFNAME-3 ZCMK-MAP-INFO ZCMK-TKN-LIB-FILE-MOD ZCMK-TKN-LIB-XFNAME ZCMK-TKN-LOG-XFNAME ZCMK-TKN-MSG-FILE-MOD ZCMK-TKN-MSG-XFNAME ZCMK-TKN-PRI-CPU ZCMK-TKN-PROG-FI
INFO ZCMK Definitions ZCMK-TKN-EMS-XFNAME, XFNAME-1, XFNAME-2, XFNAME-3 identifies the current EMS collector and alternate collectors. If no EMS collection is in effect, this token is not included in the response. ZCMK-MAP-INFO contains information about internal processing conditions in the subsystem process. For a description of its structure, see ZCMK Data Definitions on page B-9. ZCMK-TKN-LIB-FILE-MOD records the modification timestamp of the file used as a user library.
LISTOBJECTS ZCMK Definitions LISTOBJECTS This subsection describes how ZCMK-based subsystems process LISTOBJECTS commands. If the request contains ZSPI-TKN-OBJECT-TYPE set to ZCOM-OBJ-NULL, ZCOMTKN-OBJNAME is not allowed in the request. Neither is ZCOM-TKN-SUB allowed in the request unless it contains the default value ZCPM-VAL-SUB-NONE. The responses list all the objects known to the subsystem.
RESETSTATS ZCMK Definitions ZCMK-TKN-LISTOP-QUALIFS records the qualifiers used when the process or object managed by the process was opened. The nth occurrence of ZCMK-TKN-LISTOP-QUALIFS corresponds to the nth occurrence of ZCMK-TKN-LISTOP-XPNAME and ZCMK-MAP-LISTOP. ZCMK-MAP-LISTOP records the details of an opener of the subsystem process. Multiple occurrences of the token are grouped so that those describing opens from the same process occur together.
STATISTICS ZCMK Definitions For a description of the structure of these tokens, see ZCMK Data Definitions on page B-9. STATISTICS A ZCMK-based subsystem returns the following tokens in response to a RESETSTATS command that is directed to the subsystem’s native object type: STATISTICS Response Tokens ZCMK-MAP-STATS-BUF ZCMK-MAP-STATS-MEM ZCMK-MAP-STATS-OPNR ZCMK-MAP-STATS-RECV ZCMK-MAP-STATS-BUF reports the condition of buffer storage pools used by the process.
SWITCH ZCMK Definitions ZCMK-TKN-BKUP-ABEND-CNT records the number of times that backup start attempts have failed. ZCMK-TKN-BKUP-STATE reports the summary state of the backup process. The possible values are: ZCOM-VAL-SUMSTATESTARTED Indicates that the backup process is running and that enough checkpoints have been taken to ensure its integrity. ZCOM-VAL-SUMSTATESTARTING Indicates that the backup has been initiated but is not yet running.
ZCMK Event Messages ZCMK Definitions ZCOM-TKN-SWITCH-CPU specifies the CPU to become the primary CPU. Only this resource token is allowed in SWITCH commands directed to the native object type of a subsystem based on the ZCMK definitions. ZCMK Event Messages Subsystems based on the ZCMK definitions generate event messages with the prefix ZCMK. The disposition of an event message to a log file or an EMS collector is subsystem-specific.
File Names in ZCMK Event Messages ZCMK Definitions Table B-1.
File Names in ZCMK Event Messages ZCMK Definitions Table B-1.
File Names in ZCMK Event Messages ZCMK Definitions Table B-2.
–32712 ZCMK-EVT-SPI-ERR ZCMK Definitions Table B-2.
–32713 ZCMK-EVT-MSGS-MISSED ZCMK Definitions ZCMK-TKN-SSERR contains the SPI error number. The explanation text is derived from this value. Cause. The issuing process was using SPI to communicate with another process, and that other process returned an SPI response that contains an error. Effect. The effect depends on the error and on the SPI command originally issued. Recovery. Appropriate recovery depends on the error and on the SPI command originally issued.
–32715 ZCMK-EVT-EMS3-SWITCHED-FROM ZCMK Definitions Message Text <1>: EMS recording for collector-3 has been switched to <2> ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-EMS3-SWITCHED-TO. ZCMK-TKN-XFNAME contains the file name of the new collector. Cause. Interactive or programmatic request. Effect. This message is sent to the old collector. The related event ZCMK-EVT-EMS3-SWITCHED-FROM is sent to the new collector. Recovery. No recovery is necessary.
–32716 ZCMK-EVT-EMS3-STOPPED ZCMK Definitions –32716 ZCMK-EVT-EMS3-STOPPED Event recording on collector 3 has been stopped. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype <1> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-MARK token-type ZSPI-TYP-STRING Message Text <1>: EMS recording on Collector-3 has been stopped ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-EMS3-STOPPED. Cause. Interactive or programmatic request. Effect.
–32718 ZCMK-EVT-EMS2-SWITCHED-FROM ZCMK Definitions –32718 ZCMK-EVT-EMS2-SWITCHED-FROM The event collection for alternate collector 2 has been switched from the previous collector process. (Compare with ZCMK-EVT-EMS2-SWITCHED-TO.
–32720 ZCMK-EVT-EMS1-SWITCHED-TO ZCMK Definitions –32720 ZCMK-EVT-EMS1-SWITCHED-TO Event collection for alternate collector 1 has been switched to a new collector process. (Compare with ZCMK-EVT-EMS1-SWITCHED-FROM.
–32722 ZCMK-EVT-EMS1-STOPPED ZCMK Definitions Cause. Interactive or programmatic request. Effect. This message is sent to the new collector. The related event ZCMK-EVT-EMS1-SWITCHED-TO was sent to the previous collector. Recovery. No recovery is necessary. –32722 ZCMK-EVT-EMS1-STOPPED Event recording on collector 1 has been stopped.
–32724 ZCMK-EVT-MEM-CNGST ZCMK Definitions ZCMK-TKN-PARAM-VAL contains the name of the invalid swap volume. ZCMK-TKN-XFNAME contains the name of the swap volume used by default. Cause. The swap volume specified in the startup parameters is not a local disk volume. Effect. The default swap volume was used instead. Recovery. Allow the process to run with the default swap volume, or abort the process and restart it with a more suitable swap volume.
–32725 ZCMK-EVT-CANT-INIT-CHKPT ZCMK Definitions –32725 ZCMK-EVT-CANT-INIT-CHKPT An attempt to start a backup process terminated because of a D-series DATA_INITIALIZE_CHKPT_ procedure failure.
–32726 ZCMK-EVT-CANT-START-CHILD ZCMK Definitions –32726 ZCMK-EVT-CANT-START-CHILD An attempt to initiate a child process has failed. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZCMK-TKN-NPERR ZCMK-TKN-NPERR ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR .Z-SSID .
–32727 ZCMK-EVT-PROC-STOPPED ZCMK Definitions ZSPI-TKN-PROC-ERR contains the name of the SPI procedure that encountered the error. ZSPI-TKN-ENDLIST marks the end of the error list. Cause. Possible causes of failure are many, as reflected in the list of values for ZCMK-TKN-NPERR and the associated explanation texts. Effect. No further attempts are made to start the child process. Recovery. Examine the error code associated with the NEWPROCESSNOWAIT call and take appropriate action.
–32728 ZCMK-EVT-BAD-CHARMAP ZCMK Definitions –32728 ZCMK-EVT-BAD-CHARMAP An attempt to specify an invalid character map during startup has been rejected.
–32730 ZCMK-EVT-TMF-NOT-CONFIG ZCMK Definitions ZCMK-TKN-CHMAP-NAME contains the name of the character map. ZCMK-TKN-CHMAP-XFNAME contains the name of the character-map file. Cause. The specified character map could not be located in the current character-map file. Effect. The requesting process terminates. Recovery. Verify that the specified map is in the character-map file declared in the process startup parameters. –32730 ZCMK-EVT-TMF-NOT-CONFIG A request for TMF services could not be satisfied.
–32732 ZCMK-EVT-LOG-STOPPED ZCMK Definitions ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-EMS-STOPPED. Cause. An interactive or programmatic request was made to stop event recording. Effect. No events are recorded by the primary collector. Recovery. No recovery is necessary. –32732 ZCMK-EVT-LOG-STOPPED The message logging functions have been stopped.
–32732 ZCMK-EVT-LOG-STOPPED ZCMK Definitions ZCMK-TKN-XFNAME specifies the name of the offending file. ZCMK-TKN-PROC-ORD contains the ordinal of the procedure involved in the error. ZSPI-TKN-ERRLIST marks the beginning of an error list provided by the file system. The list contains these tokens: ZSPI-TKN-ERROR.Z-SSID contains the ID of the subsystem that created the error list; in this case, the file system as reflected in ZFIL-VAL-VERSION. ZSPI-TKN-ERROR.
–32733 ZCMK-EVT-TOO-MANY-BKUP-ABENDS ZCMK Definitions –32733 ZCMK-EVT-TOO-MANY-BKUP-ABENDS Within the last 30 minutes more than 5 attempts were made to start a backup process, and all attempts ended in abnormal termination of the backup.
–32735 ZCMK-EVT-NO-MEM-FOR-REQ ZCMK Definitions ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-CANT-ALLOC-SEG. ZCMK-TKN-FILE-ROLE specifies the function performed by the file. For valid values and the functions they identify, see the description of this token in ZCMK Data Definitions on page B-9. ZCMK-TKN-ALERR specifies the error returned by the C-series ALLOCATESEGMENT procedure or the D-series SEGMENT_ALLOCATE_ procedure.
–32736 ZCMK-EVT-BKUP-STOPPED ZCMK Definitions ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-NO-MEM-FOR-REQ. ZCMK-TKN-XPNAME contains the name of the process that issued the request. Cause. The process might have been started with an inadequate fixed allocation of memory, the swap volume might have insufficient space (likely if this is a recurring event), or the process reporting the event might be overloaded with requests. Effect. The requested is usually rejected. Recovery.
–32737 ZCMK-EVT-WRONG-CPU ZCMK Definitions –32737 ZCMK-EVT-WRONG-CPU A process was initiated on an inappropriate processor. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype <1> token-type ZSPI-TYP-ENUM token-type ZSPI-TYP-MARK token-type ZSPI-TYP-STRING Message Text <1>: This product requires a NonStop processor and GUARDIAN 90 XF release C20 or better ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-WRONG-CPU. Cause.
–32739 ZCMK-EVT-TOO-MANY-TKOVR ZCMK Definitions Recovery. No recovery is necessary. –32739 ZCMK-EVT-TOO-MANY-TKOVR Within the last 30 minutes (since the process was initiated or since the operator caused its primary to fail) more than 5 takeover attempts have been made on the process, and each of these takeovers was due to abnormal termination of the primary process.
–32741 ZCMK-EVT-SYNCID-OLD ZCMK Definitions Effect. If recovery is successful, the backup process assumes the role of primary process and attempts to start a backup in the CPU that held the previous primary process. A message indicating that a new backup has been started or that the startup attempt has failed should follow. Recovery. No recovery is necessary. –32741 ZCMK-EVT-SYNCID-OLD A received request contains a sync ID value that is too old (that is, older than promised by the file open).
–32742 ZCMK-EVT-SPI-SSCALL ZCMK Definitions –32742 ZCMK-EVT-SPI-SSCALL An SPI subroutine (SSGET, for example) has detected an improperly formatted buffer. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZCMK-TKN-XPNAME ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR .Z-SSID .
–32743 ZCMK-EVT-SPI-SHORT ZCMK Definitions Recovery. The requester should re-create and send a valid message buffer. –32743 ZCMK-EVT-SPI-SHORT A received SPI command buffer was too short to be valid.
–32745 ZCMK-EVT-SPI-NOT-CMD ZCMK Definitions ZCMK-TKN-XPNAME contains the name of the process that issued the request. Cause. The requester might have corrupted a valid SPI buffer, lost track of where the buffer was built, or sent the wrong data. Effect. The request is rejected with file-system error 2 (ZFIL-ERR-INVALOP). Recovery. The requester should re-create and send a valid message buffer. –32745 ZCMK-EVT-SPI-NOT-CMD An SPI buffer was received that was not a valid command message.
–32747 ZCMK-EVT-SPI-BAD-OCCURS ZCMK Definitions Message Text <1>: SPI Request from <2> bad: No header ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-SPI-NO-HDR. ZCMK-TKN-XPNAME contains the name of the process that issued the request. Cause. The requester might have corrupted a valid SPI buffer, lost track of where the buffer was built, or sent the wrong data. Effect. The request is rejected with file-system error 2 (ZFIL-ERR-INVALOP). Recovery.
–32748 ZCMK-EVT-RESETSYNC ZCMK Definitions –32748 ZCMK-EVT-RESETSYNC A RESETSYNC signal has been received. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZCMK-TKN-XPNAME ZCMK-TKN-FNUM <1> <2> <3> token-type token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-MARK ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI-TYP-INT Message Text <1>: RESETSYNC from process <2> on file number <3> ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-RESETSYNC.
–32750 ZCMK-EVT-PROC-STARTED ZCMK Definitions Message Text <1>: Command message from process <2> rejected because RECEIVE queue is full ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-REJ-QUEUE-FULL. ZCMK-TKN-XPNAME contains the name of the process that issued the request. Cause. This condition indicates a resource overload. The subsystem is being asked to do too many things at the same time. The actual number of command messages that can be accommodated is 2000.
–32751 ZCMK-EVT-PROC-NOT-NAMED ZCMK Definitions Cause. An interactive or programmatic call for process initiation was made. Effect. The process is running. Recovery. No recovery is necessary. –32751 ZCMK-EVT-PROC-NOT-NAMED A process that must be named was started without a name.
–32753 ZCMK-EVT-LOG-SWITCHED-TO ZCMK Definitions Recovery. If insufficient memory was allocated at startup, adjust the value of the DATAPAGES startup argument and rerun the process. If swap space is inadequate, find additional disk space or change the designated swap volume. If the process is overloaded with requests, examine the processing load, restrict the number of command messages, or eliminate unnecessary requests.
–32755 ZCMK-EVT-IO-ERR ZCMK Definitions ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-LOG-SWITCHED-FROM. ZCMK-TKN-XFNAME specifies the name of the previous log file. Cause. An interactive or programmatic request was made. Effect. Event messages are written to the new log file. Recovery. No recovery is necessary. –32755 ZCMK-EVT-IO-ERR A file-system error was returned on a file I/O. This message is typically used for errors associated with the $RECEIVE file.
–32755 ZCMK-EVT-IO-ERR ZCMK Definitions ZCMK-TKN-FSERR contains the file-system error number. ZCMK-TKN-PROC-ORD contains the ordinal of the procedure involved in the error. ZSPI-TKN-ERRLIST marks the beginning of an error list provided by SPI. The list contains these tokens: ZSPI-TKN-ERROR.Z-SSID contains the ID of the subsystem that created the error list; in this case, the file system as reflected in ZFIL-VAL-VERSION. ZSPI-TKN-ERROR.Z-ERROR contains the error returned by the file system.
–32756 ZCMK-EVT-EMS-SWITCHED-TO ZCMK Definitions –32756 ZCMK-EVT-EMS-SWITCHED-TO Event collection for the primary collector has been switched to a new collector process. (Compare with ZCMK-EVT-EMS-SWITCHED-FROM.
–32758 ZCMK-EVT-CANT-START-BKUP ZCMK Definitions Cause. An interactive or programmatic request was made. Effect. This message is sent to the new collector. The related event ZCMK-EVT-EMS-SWITCHED-TO was sent to the previous collector. Recovery. No recovery is necessary. –32758 ZCMK-EVT-CANT-START-BKUP An attempt to initiate a backup process has failed.
–32759 ZCMK-EVT-BKUP-STARTED ZCMK Definitions ZGRD-TKN-OBJECTFILE specifies the program object file name. ZSPI-TKN-PROC-ERR specifies the procedure that encountered the error. ZSPI-TKN-ENDLIST marks the end of the error list. Cause. The cause is indicated by the error numbers and explanation text. Effect. The attempt to start the backup is abandoned. Recovery. Examine the error associated with the process creation procedure call and take appropriate action.
–32760 ZCMK-EVT-BKUP-DIED ZCMK Definitions –32760 ZCMK-EVT-BKUP-DIED The backup process stopped unexpectedly (for a reason other than a STOP issued by the primary process). Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZCMK-TKN-CPU <1> <2> token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-MARK ZSPI-TYP-STRING ZSPI-TYP-INT Message Text <1>: Backup process in CPU <2> stopped unexpectedly ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-BKUP-DIED.
–32762 ZCMK-EVT-BAD-REOPEN ZCMK Definitions ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-BAD-SYS-MSG. ZCMK-TKN-SYS-MSG-CODE contains the message ID number from the first word of the system message. Cause. This might indicate a serious problem in the subsystem. Effect. The message is ignored, and a dummy reply is generated. Recovery. If this event is reported the first time the subsystem was started or is reported repeatedly, contact your Compaq service provider.
–32763 ZCMK-EVT-BAD-PARAM-VAL ZCMK Definitions using CHECKMONITOR), make sure the backup can signal completion of the backup close so that the primary process can avoid the file until it receives that signal. –32763 ZCMK-EVT-BAD-PARAM-VAL The startup sequence contained a parameter with an invalid value.
–32765 ZCMK-EVT-BAD-OPNR ZCMK Definitions ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-BAD-PARAM-NAME. ZCMK-TKN-PARAM-NAME contains the first 80 characters of the unrecognized parameter name. Cause. The RUN command or startup message contained an invalid or unsupported parameter. Effect. The process terminates. Recovery. Correct the RUN command and retry. For descriptions of valid parameters, see Process Options and Startup Parameters on page B-4.
–32766 ZCMK-EVT-BAD-BKUP-OPEN ZCMK Definitions –32766 ZCMK-EVT-BAD-BKUP-OPEN An open message was received from a backup process, but there was no corresponding open from the primary process.
ZCMK Errors ZCMK Definitions ZEMS-TKN-EVENTNUMBER has the value ZCMK-EVT-PROG-ERR. ZCMK-TKN-PROG-ERR contains an internal error code. ZCMK-TKN-ABEND-TEXT contains text describing the problem. Cause. This message indicates a serious internal programming error. Effect. The process terminates. Recovery. Note the error code and contact your Compaq service provider. ZCMK Errors This subsection describes errors generated by subsystems that are based on the ZCMK definitions.
–32760 ZCMK-ERR-CANT-ALLOC-SEG ZCMK Definitions –32760 ZCMK-ERR-CANT-ALLOC-SEG An attempt to allocate an extended memory segment failed.
–32761 ZCMK-ERR-BAD-CHARMAP ZCMK Definitions Cause. The cause of the failure is reflected in the value of ZCMK-TKN-ALERR and its associated explanation text. Effect. The requested segment is not allocated. Recovery. Analyze the failure on the basis of the explanation text, make necessary adjustments, and reissue the request. –32761 ZCMK-ERR-BAD-CHARMAP A management application tried to assign or replace the character-map file, but the new file was not a valid character-map file.
–32762 ZCMK-ERR-NO-CHARMAP ZCMK Definitions –32762 ZCMK-ERR-NO-CHARMAP A management application tried to change the default character map, but the new map could not be found in the current character-map file.
–32764 ZCMK-ERR-CANT-RMT ZCMK Definitions Error Text Backup not yet initialized ZCOM-TKN-OBJNAME contains the name of the object on behalf of which the request was made. ZCOM-TKN-OBJTYPE contains the type of the object named in ZCOM-TKN-OBJNAME. Cause. The backup process is not yet fully initialized. Effect. The switch does not occur. Recovery. Pause before reissuing the SWITCH command. The primary process generates the event ZCMK-EVT-BKUP-STARTED when the backup process is ready.
–32765 ZCMK-ERR-CANT-ASGN ZCMK Definitions Effect. The command is canceled. Recovery. Either specify a file that can be remote, or use a file or process on the same node as the subsystem. –32765 ZCMK-ERR-CANT-ASGN A requester tried to assign a file or process to be used for a specific function, but the attempt failed because of a file-system error.
–32767 ZCMK-ERR-BKUP-IN-PRI-CPU ZCMK Definitions ZSPI-TKN-ERRLIST marks an embedded error list originally generated by the file system. ZSPI-TKN-ERROR.Z-SSID contains the SSID of the file system. ZSPI-TKN-ERROR.Z-ERROR contains the file-system error number (ZFIL-ERR-error). ZSPI-TKN-PROC-ERR contains the number of the file-system procedure that failed (ZFIL-VAL-proc). ZFIL-TKN-FILENAME is the name of the file on which the error occurred.
–32767 ZCMK-ERR-BKUP-IN-PRI-CPU ZCMK Definitions ZCMK-TKN-CPU contains the number of the primary CPU specified as backup. ZCOM-TKN-OBJNAME contains the name of the object on behalf of which the request was made. ZCOM-TKN-OBJTYPE contains the type of the object named in ZCOM-TKN-OBJNAME. Cause. An application issued an ALTER command with the value of the ZCMK-TKN-ALTER-BKUP-CPU token set to the number of the current primary CPU. Effect. The backup CPU assignment is not changed. Recovery.
ZCOM Errors As Generated by ZCMK-Based Subsystems ZCMK Definitions ZCOM Errors As Generated by ZCMK-Based Subsystems This subsection lists common ZCOM errors generated by subsystems that are based on the ZCMK definitions. They differ from the general ZCOM error descriptions presented in Appendix A, ZCOM Errors, in that they specify additional tokens in the error lists (in place of the generic subsys-type-name listed in the general descriptions).
–4 ZCOM-ERR-CMD-MISMATCH ZCMK Definitions Table B-6.
–5 ZCOM-ERR-CMD-NOT-SUPP ZCMK Definitions ZCMK-TKN-CMD-CODE contains the numeric command code. Cause. The command cannot be applied to objects of the specified type. Effect. The command is rejected. Recovery. For valid command/object-type combinations, see the subsystem-specific management programming manual. –5 ZCOM-ERR-CMD-NOT-SUPP The subsystem does not support the command specified in the request.
–10 ZCOM-ERR-FS-ERR ZCMK Definitions –10 ZCOM-ERR-FS-ERR A file-system error occurred. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZCMK-TKN-FSERR ZCMK-TKN-FILE-ROLE ZCMK-TKN-XFNAME ZCMK-TKN-PROC-ORD ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR .Z-SSID .
–14 ZCOM-ERR-NO-MEM-SPACE ZCMK Definitions ZSPI-TKN-ERRLIST marks an embedded error list originally generated by the file system. ZSPI-TKN-ERROR.Z-SSID contains the SSID of the file system. ZSPI-TKN-ERROR.Z-ERROR contains the file-system error that occurred (ZFIL-ERR-error). ZSPI-TKN-PROC-ERR contains the number of the file-system procedure that failed (ZFIL-VAL-proc). ZFIL-TKN-FILENAME contains the name of the file on which the error occurred.
–15 ZCOM-ERR-OBJ-ALRDY-DEF ZCMK Definitions ZCOM-TKN-OBJTYPE specifies the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. Cause. There is a memory shortage. Typically, this error indicates a resourceavailability problem caused by a large amount of activity (assuming that the configuration is proper for the operating environment and that the associated hardware is functioning normally). Effect. The command is canceled. Recovery.
–18 ZCOM-ERR-OBJ-NOT-SUPP ZCMK Definitions Error Text No objects of type <1> matching <2> were found ZCOM-TKN-OBJNAME contains the object name template specified in the request. ZCOM-TKN-OBJTYPE specifies the type (ZCOM-OBJ-objtype) of the object specified in the request. Cause. The object specified in the command is not defined to the subsystem. Effect. The command is not applied to the object. Recovery. Check for erroneous object name, type, or manager process name.
–19 ZCOM-ERR-OBJNAME-INV ZCMK Definitions –19 ZCOM-ERR-OBJNAME-INV The form of the object name specified in the request is not valid. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST <2> <1> token-type token-type token-type token-type token-type ZSPI-TYP-LIST ZSPI-TYP-ERROR ZSPI-TYP-STRING ZSPI-TYP-ENUM ZSPI-TYP-SSCTL Error Text Invalid name for an object of type <1>: <2> ZCOM-TKN-OBJNAME contains the invalid object name specified in the request.
–23 ZCOM-ERR-SPI-ERR ZCMK Definitions ZCOM-TKN-OBJTYPE indicates the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. Cause. The requesting application is not authorized to issue sensitive commands. Effect. The command is rejected. Recovery. If possible, acquire the proper security and reissue the request. –23 ZCOM-ERR-SPI-ERR The routines that decode SPI buffers detected an error in a request.
–24 ZCOM-ERR-SSID-INV ZCMK Definitions ZSPI-TKN-ERROR.Z-ERROR contains the SPI error number (ZSPI-ERR-error). ZSPI-TKN-PROC-ERR identifies the SPI procedure that encountered the error (ZSPI-VAL-proc). ZSPI-TKN-ENDLIST marks the end of the nested file-system error list. Cause. The requester might have sent the wrong buffer or modified the buffer after the SPI routines assembled it. Effect. The request is rejected. Recovery. Re-create the request buffer and resend.
–26 ZCOM-ERR-TKN-CODE-INV ZCMK Definitions –26 ZCOM-ERR-TKN-CODE-INV An invalid, unknown, or unsupported token code was detected in the request.
–28 ZCOM-ERR-TKN-LEN-INV ZCMK Definitions ZCOM-TKN-OBJNAME contains the name of the object specified in the request and is included if relevant to the analysis of the error condition. ZCOM-TKN-OBJTYPE specifies the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. ZSPI-TKN-PARM-ERR contains the identity of the duplicated token. Cause. The request contains multiple occurrences of a token that is allowed to appear only once. Effect.
–29 ZCOM-ERR-TKN-REQ ZCMK Definitions Recovery. Rebuild the request buffer and reissue the request. –29 ZCOM-ERR-TKN-REQ A command was issued in which a required token is missing.
–31 ZCOM-ERR-VAL-REQ ZCMK Definitions Error Text Token <1> has an invalid value ZCOM-TKN-OBJNAME contains the name of the object specified in the request and is included if relevant to the analysis of the error condition. ZCOM-TKN-OBJTYPE indicates the object type (ZCOM-OBJ-objtype) specified in the request and is included if relevant to the analysis of the error condition. ZSPI-TKN-PARM-ERR contains the identity of the token containing the invalid value. Cause.
–32 ZCOM-ERR-VSN-INCOMP ZCMK Definitions ZSPI-TKN-PARM-ERR contains the identity of the token containing the invalid value. Cause. The token was assigned the wrong value. Effect. The request is rejected. Recovery. For information about tokens required int the command, see the subsystem-specific management programming manuals. –32 ZCOM-ERR-VSN-INCOMP The requester asked for features not implemented in the server.
–36 ZCOM-ERR-TKN-CNTXT-VAL-INV ZCMK Definitions –36 ZCOM-ERR-TKN-CNTXT-VAL-INV Two values in the request are in conflict. The value of one contradicts the context established by the value of the other.
ZCMK Definitions –36 ZCOM-ERR-TKN-CNTXT-VAL-INV SPI Common Extensions Manual—427508-001 B-116
C ZCDG Definitions This appendix describes event messages and associated data definitions defined by common diagnostics routines (ZCDG). These messages are issued by common diagnostic routines that monitor data communications hardware. ZCDG Data Definitions The data items described in this subsection appear in the common event messages issued by the I/O processes (IOPs) that monitor data communications hardware.
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-ASYNC-SET-CONFIG-PARM token-code value token-type heading ZCDG-TKN-ASYNC-SET-CONFIG-PARM ZCDG-TNM-ASYNC-SET-CONFIG-PARM ZSPI-TYP-BYTESTRING "Async-Task-Config-Message". ZCDG events include this token to convey a controller microcode configuration message. The message is described in the controller or IOP documentation. ZCDG-TKN-ASYNC-VFU token-code value token-type heading ZCDG-TKN-ASYNC-VFU ZCDG-TNM-ASYNC-VFU ZCDG-TYP-ASYNC-FUNC "VFU-Data".
ZCDG Data Definitions ZCDG Definitions ZCDG-VAL-BOB-SRC-LIMPON BOB line interface module (LIM) PON ZCDG-VAL-BOB-SRC-NVRAM-XSUM BOB’s nonvolatile random access memory (NVRAM) checksum error ZCDG-VAL-BOB-SRC-PON BOB PON ZCDG-VAL-BOB-SRC-PS0-M13V-DOWN PS 0 -13V lower limit exceeded ZCDG-VAL-BOB-SRC-PS0-M13V-UP PS 0 -13V upper limit exceeded ZCDG-VAL-BOB-SRC-PS0-M65V-DOWN PS 0 -6.
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-CLB-FUNC-MODIF token-code value token-type heading ZCDG-TKN-CLB-FUNC-MODIF ZCDG-TNM-CLB-FUNC-MODIF ZCDG-TYP-CLB-FUNC-MODIF "CLB-Function-modif". This token conveys the CLB function and modifier fields from the CLB command. The first byte contains the function, and the second byte contains the modifier. ZCDG-TKN-CLB-T-S-FIELD token-code value token-type heading ZCDG-TKN-CLB-T-S-FIELD ZCDG-TNM-CLB-T-S-FIELD ZCDG-TYP-CLB-T-S-FIELD "CLB-T-S-FIELD".
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-CTLRTYPE token-code value token-type heading ZCDG-TKN-CTLRTYPE ZCDG-TNM-CTLRTYPE ZSPI-TYP-ENUM "Controller-type". ZCDG events include this token to specify the type of controller that was involved.
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-DETECT-REV token-code value token-type heading ZCDG-TKN-DETECT-REV ZCDG-TNM-DETECT-REV ZSPI-TYP-CHAR4 "Revision-of-sender". ZCDG events include this token to report the revision of the software that detected the event unless the version of the reporting software differs from the version of the detecting software. In that case, this token contains the version of the reporting software. All ZCDG events include this token.
ZCDG Data Definitions ZCDG Definitions This token is of type ZCDG-TYP-DIAG-ERR, which is based on the structure ZCDG-DDL-DIAG-ERR: def ZCDG-DDL-DIAG-ERR. 02 Z-CTLRTYPE type ZSPI-DDL-UINT. heading "Controller type". type ZSPI-DDL-UINT. heading "Error type". type ZSPI-DDL-UINT. heading "Error Code". type ZSPI-DDL-UINT. heading "Auxiliary Error Code". 02 Z-ERRTYPE 02 Z-ERRCODE 02 Z-AUXCODE end Z-CTLRTYPE contains a controller type.
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-DIAG-NEW-UPDATE token-code value token-type heading ZCDG-TKN-DIAG-NEW-UPDATE ZCDG-TNM-DIAG-NEW-UPDATE ZSPI-TYP-BYTESTRING "New-Update-Info". ZCDG events include this token to specify the new data that replaced the old as part of an UPDATE operation. The value of the token is a variable-length string. The length of the string, expressed in bytes, is stored in the first byte of the string, which is not included in the length computation.
ZCDG Data Definitions ZCDG Definitions Z-BAKUP contains the backup controller’s physical address. ZCDG-TKN-DIAG-RESULT token-code value token-type heading ZCDG-TKN-DIAG-RESULT ZCDG-TNM-DIAG-RESULT ZSPI-TYP-BYTESTRING "Diagnostic-Results". ZCDG events use this token to provide additional information about the event. The value of the token is a variable-length string that might contain any information relevant to the event.
ZCDG Data Definitions ZCDG Definitions ZCDG-VAL-LAN-TEST3 Parity detection ZCDG-VAL-LAN-TEST4 Deadman timer ZCDG-VAL-LAN-TEST5 Real-time clock ZCDG-VAL-LAN-TEST6 DMA register ZCDG-VAL-LAN-TEST7 FIFO ZCDG-VAL-LAN-TEST8 Host interface logic test ZCDG-VAL-LAN-TEST9 LAN coprocessor test ZCDG-VAL-LAN-TEST10 Memory test ZCDG-VAL-LAN-TEST11 Local LAN loopback ZCDG-VAL-LAN-TEST12 Token bus chip test ZCDG-VAL-LAN-TEST13 Modem test ZCDG-VAL-LAN-TEST14 Port test ZCDG-VAL-LAN-TEST15 Gateway t
ZCDG Data Definitions ZCDG Definitions ZCDG-VAL-CSS-LIGHT Light test ZCDG-VAL-CSS-SEEROM SEEROM test ZCDG-VAL-CSS-PREDUART Pre-DUART test ZCDG-VAL-CSS-POSTDUART Post-DUART test ZCDG-VAL-CSS-CTRLLIGHT LB light (replace) ZCDG-VAL-CSS-LIMLIGHT AB light (replace) ZCDG-TKN-DWLOAD-ERR token-code value token-type heading ZCDG-TKN-DWLOAD-ERR ZCDG-TNM-DWLOAD-ERR ZSPI-TYP-INT "Download-software-err".
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-EIO-ERR token-code value token-type heading ZCDG-TKN-EIO-ERR ZCDG-TNM-EIO-ERR ZSPI-TYP-BOOLEAN "EIO-complete". ZCDG events include this token to convey the outcome of an execute I/O (EIO) transfer. Valid values and their meanings are: ZSPI-VAL-TRUE EIO succeeded. ZSPI-VAL-FALSE EIO failed. ZCDG-TKN-EIO-LAC token-code value token-type heading ZCDG-TKN-EIO-LAC ZCDG-TNM-EIO-LAC ZSPI-TYP-INT "EIO-LAC-word".
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-EIO-RIST token-code value token-type heading ZCDG-TKN-EIO-RIST ZCDG-TNM-EIO-RIST ZSPI-TYP-INT "EIO-RIST-word". ZCDG events include this token to convey the execute I/O (EIO) read-interrupt-status (RIST) word. ZCDG-TKN-FRAME-SIZE token-code value token-type ZCDG-TKN-FRAME-SIZE ZCDG-TNM-FRAME-SIZE ZSPI-TYP-INT. This token conveys the frame size used by a multifunction controller.
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-IOC-STATUS token-code value token-type heading ZCDG-TKN-IOC-STATUS ZCDG-TNM-IOC-STATUS ZSPI-TYP-INT "IOC-status-word". ZCDG events include this token to convey the I/O-control (IOC) status word that is returned by the I/O channel. ZCDG-TKN-NET-FILENAME token-code value token-type heading ZCDG-TKN-NET-FILENAME ZCDG-TNM-NET-FILENAME ZSPI-TYP-FNAME32 "Network-file-name". ZCDG events include this token to specify a network file name.
ZCDG Data Definitions ZCDG Definitions ZCDG-TKN-REQUESTERID token-code value token-type heading ZCDG-TKN-REQUESTERID ZCDG-TNM-REQUESTERID ZSPI-TYP-INT "SPI-subsystem-value". ZCDG events include this token to convey the SSID of the software that issued the original request that resulted in the event. Valid values are defined SSIDs of the form ZSPI-SSN-Zsss, where sss is the subsystem mnemonic. The value is zero if the SSID of the requester is not known.
ZCDG Data Definitions ZCDG Definitions ZCDG-VAL-SEQ-INVALID-MSG-XSUM Invalid message checksum ZCDG-VAL-SEQ-INVALID-SEQ-NUM Invalid command sequence number ZCDG-VAL-SEQ-INVALID-CMD-CODE Invalid command code ZCDG-VAL-SEQ-INVALID-CMD-PARM Invalid command parameter other Unrecognized sequence ZCDG-TKN-SUBDEV-NUM token-code value token-type heading ZCDG-TKN-SUBDEV-NUM ZCDG-TNM-SUBDEV-NUM ZSPI-TYP-ENUM "Subdevice-number". This token contains the subdevice number.
ZCDG Events ZCDG Definitions Z-TIME contains the timestamp of the file from which the controller was updated. ZCDG Events Subsystems that deal with communications controller hardware might encounter the events described in this section. The common event messages defined by ZCDG are listed in Table C-1 and Table C-2 on page C-18. They can appear in either event or Compaq Tandem Maintenance and Diagnostic System (TMDS) logs. Table C-1.
ZCDG Events ZCDG Definitions Table C-1. ZCDG Event Messages, by Number (continued) Number Event Description –10023 ZCDG-EVT-BOB-ERR-FRAME BOB error frame. –10024 ZCDG-EVT-CLB-CMD-REJ CLB command rejected. –10025 ZCDG-EVT-BOB-WARN BOB marginal warning. –10026 ZCDG-EVT-NO-RSP No response event. –10027 ZCDG-EVT-CLIP-ERR CLIP error detected. –10028 ZCDG-EVT-CLIP-SUB-ERR Subdevice error detected. Table C-2.
Tokens Common to ZCDG Event Messages ZCDG Definitions Table C-2. ZCDG Event Messages, by Name Event Number Description ZCDG-EVT-PON-INTRPT –10003 A controller has been powered on. ZCDG-EVT-RESET-EIO –10002 Reset instruction issued to controller. ZCDG-EVT-SET-CONFIG –10007 Set port configuration. ZCDG-EVT-SET-FRAME-SIZE –10010 Load frame size EIO. ZCDG-EVT-TAKEOWN-EIO –10001 Take ownership EIO instruction issued. ZCDG-EVT-XFER-ABORT –10011 Data transfer aborted.
–10001 ZCDG-EVT-TAKEOWN-EIO ZCDG Definitions ZCDG-TKN-DEVTYPE contains the device type and subtype involved in the event. The device type and subtype are stored in the integer: byte[0:1].<4:9> = device type byte[0:1].<10:15> = device subtype ZCOM-TKN-NEW-PATH specifies the new path in use after a path switch. For valid values, see ZCOMTKN-NEW-PATH on page 4-8. –10001 ZCDG-EVT-TAKEOWN-EIO A take-ownership EIO instruction was executed on the specified device.
–10002 ZCDG-EVT-RESET-EIO ZCDG Definitions ZCDG-TKN-REQUESTERID contains the subsystem number of the software that issued the TAKEOWN EIO. ZCDG-TKN-REASON indicates the cause of the switch. Valid values and the causes they identify are listed in the description of this token earlier in this section. Cause. Take ownership EIOs are normally issued during controller initialization, but can also be issued to switch the IOC path (hence IOP and CPU) in order to lock out an overloaded or malfunctioning path.
–10003 ZCDG-EVT-PON-INTRPT ZCDG Definitions Cause. Some condition has required that the controller be reinitialized. The controller might have lost the context within which it was communicating with an associated IOP, or it might have suffered a nonrecoverable software error. Effect. The controller is reinitialized. Recovery. Examine the log for other events concerning the device. Look both before and after the RESET-IO event.
–10004 ZCDG-EVT-INTRPT-TIMEOUT ZCDG Definitions –10004 ZCDG-EVT-INTRPT-TIMEOUT A controller has failed to respond to an EIO instruction.
–10005 ZCDG-EVT-INTRPT-UNEXP ZCDG Definitions ZCDG-TKN-EIO-RDST contains the EIO read-status (RDST) word. ZCDG-TKN-RESIDUE contains the transfer residue in bytes. Cause. An EIO LAC command was issued to the controller, but the corresponding IIO did not occur within the channel timeout period. The channel or the controller is faulty. Effect. Communication through this channel or controller might be impaired. Recovery. Scan the log for other event messages about the corresponding CPU and I/O channel.
–10006 ZCDG-EVT-CTLR-DWLOAD ZCDG Definitions ZEMS-TKN-CU contains the controller and unit number of the device associated with the event. This token is used in the absence of ZEMS-MAP-EXIOADDR. ZCDG-TKN-EIO-LAC contains the EIO LAC word. ZCDG-TKN-IIO-RIC contains the IIO RIC word. ZCDG-TKN-IIO-RIST contains the IIO RIST word. ZCDG-TKN-IIO-CHNL-STATUS contains the IIO channel status word. Cause. A channel or controller is experiencing a fault. Effect.
–10007 ZCDG-EVT-SET-CONFIG ZCDG Definitions ZEMS-TKN-ZFILERR contains the error number of any file error encountered by the downloading process while accessing the microcode file. ZCDG-TKN-DWLOADID contains the identification of the downloading software. Cause. The controller has been replaced and powered up, or the controller has been reset following a failure. Effect. If the event contains no error information, the controller now contains a fresh copy of its microcode. Recovery.
–10008 ZCDG-EVT-LOAD-VFU ZCDG Definitions –10008 ZCDG-EVT-LOAD-VFU The vertical format unit (VFU) settings of the specified printing device have changed. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZEMS-TKN-LDEVNAME <1> token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-MARK ZSPI-TYP-STRING ZSPI-TYP-FNAME32 Message Text Printer VFU loaded. Device: <1> ZEMS-TKN-EVENTNUMBER has the value ZCDG-EVT-LOAD-VFU. Cause.
–10010 ZCDG-EVT-SET-FRAME-SIZE ZCDG Definitions Recovery. Run diagnostics on the hardware subsystem. –10010 ZCDG-EVT-SET-FRAME-SIZE The frame size of a multifunction controller (MFC) bit-synchronous task was changed.
–10012 ZCDG-EVT-MFC-UNOWNED-EIO ZCDG Definitions ZCDG-TKN-IIO-RIC contains the IIO RIC word. Cause. Some condition prevented the controller microcode from completing the read EIO initiated by the host. Effect. Communications is interrupted. Recovery. Examine the RIC word in ZCDG-TKN-IIO-RIC, and look for other events that report errors on this controller device. Recovery might occur automatically.
–10013 ZCDG-EVT-MFC-HW-ERR ZCDG Definitions –10013 ZCDG-EVT-MFC-HW-ERR A hardware error was detected on a multifunction controller board.
–10015 ZCDG-EVT-MFC-MODEM-STATUS ZCDG Definitions ZCDG-TKN-IIO-RIC contains the IIO RIC word. Cause. There is a hardware problem or incompatible software version. Effect. The controller is unreliable. Recovery. Examine the RIC word in ZCDG-TKN-IIO-RIC. Proper interpretation of the error depends on controller type. Do not use the controller board until it is reset or repaired. –10015 ZCDG-EVT-MFC-MODEM-STATUS A modem error was detected on a multifunction controller board.
–10017 ZCDG-EVT-NO-CTLR-BUF ZCDG Definitions Message Text A Receive Frame Overrun error occurred on <1> ZEMS-TKN-EVENTNUMBER has the value ZCDG-EVT-MFC-RECV-FRAME-OVRUN. Cause. The current frame size is not large enough for frames being generated by another node. Effect. Information is lost from this communication but should be recovered during automatic recovery. Recovery. Recovery should be automatic.
–10018 ZCDG-EVT-DIAG-TEST ZCDG Definitions –10018 ZCDG-EVT-DIAG-TEST A diagnostic test was run on a subsystem component. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZCDG-TKN-DIAG-TEST ZEMS-TKN-LDEVNAME ZEMS-TKN-DIAG-ERR .Z-ERRTYPE .Z-ERRCODE .
–10019 ZCDG-EVT-DIAG-UPDATE ZCDG Definitions –10019 ZCDG-EVT-DIAG-UPDATE Software stored in a controller or device has been modified. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZEMS-TKN-LDEVNAME <1> token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-MARK ZSPI-TYP-STRING ZSPI-TYP-FNAME32 Message Text <1> was updated with new information Update data: ZEMS-TKN-EVENTNUMBER has the value ZCDG-EVT-DIAG-UPDATE. Cause.
–10021 ZCDG-EVT-CLIP-PROBE-ERR ZCDG Definitions ZEMS-TKN-DIAG-ERR contains the error code. For a list of error codes, see the description of ZCDGTKN-DIAG-ERR on page C-6. Cause. The diagnostic software might be faulty, might have been interfered with, might be improperly installed, or might be running with the wrong version of supporting software. Effect. The controller is in an unpredictable state. Recovery. Reset the controller board.
–10022 ZCDG-EVT-CIU-ERR ZCDG Definitions –10022 ZCDG-EVT-CIU-ERR A CIU error occurred. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZEMS-TKN-LDEVNAME <1> token-type token-type token-type token-type ZSPI-TYP-ENUM ZSPI-TYP-MARK ZSPI-TYP-STRING ZSPI-TYP-FNAME32 Message Text A CIU error occurred on <1>, CSM Error code: ZEMS-TKN-EVENTNUMBER has the value ZCDG-EVT-CIU-ERR. Cause. A hardware failure occurred. Effect.
–10024 ZCDG-EVT-CLB-CMD-REJ ZCDG Definitions Effect. The BOB and associated CIU are reset or downed. Recovery. Use backup until primary is checked. Run loopback tests. –10024 ZCDG-EVT-CLB-CMD-REJ Command rejected.
–10026 ZCDG-EVT-NO-RSP ZCDG Definitions Message Text BOB marginal functional errors detected on <1> BOB source: <2> Measured value of power supply: <3> ZEMS-TKN-EVENTNUMBER has the value ZCDG-EVT-BOB-WARN. ZCDG-TKN-BOB-SRC identifies the BOB source. For valid values and their meanings, see ZCDG-TKNBOB-SRC on page C-2. ZCDG-TKN-BOB-SENSE conveys the value of the BOB power supply. Cause. The BOB’s power supply or fan might be failing. Effect. The hardware is not reliable. Recovery. Replace the board.
–10027 ZCDG-EVT-CLIP-ERR ZCDG Definitions –10027 ZCDG-EVT-CLIP-ERR An error on a CLIP was detected. Tokens in Event Message ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-objtype ZEMS-TKN-LDEVNAME ZCDG-TKN-CLIP-STATUS token-type token-type token-type token-type token-type <1> <2> ZSPI-TYP-ENUM ZSPI-TYP-MARK ZSPI-TYP-STRING ZSPI-TYP-FNAME32 ZSPI-TYP-INT Message Text A CLIP error has been detected on <1> CLIP Status: <2> ZEMS-TKN-EVENTNUMBER has the value ZCDG-EVT-CLIP-ERR.
–10028 ZCDG-EVT-CLIP-SUB-ERR ZCDG Definitions ZCDG-TKN-SUBDEV-NUM contains any error number from the downloading process. No error means the download was successful. ZCDG-TKN-CLIP-STATUS contains the CLIP status byte. Cause. The subdevice was not in the state required to perform the requested function. Effect. Communication is interrupted. Recovery. Run loopback tests.
Glossary attribute. A characteristic of an object. For example, two attributes of a DNS alias are an alias type and domain. Two attributes of a communications line might be its baud rate and its retry count. In SPI messages, an attribute of an object is usually expressed as a simple token or a field within an extensible structured token. Tokens themselves have attributes: length, count, address, and offset. Programs can retrieve attributes through special SSGET operations. buffer.
context information Glossary context information. The information required by a subsystem to continue processing a command for which a partial response was returned. Continuation of a response in multiple response messages requires the subsystem to send context information to the requester. The application program, in turn, must return that information to the subsystem in a new command message so that the subsystem can continue processing. See context token. context token.
current-token position Glossary current-token position. The location in the SPI buffer of the token whose token code, token value, or attribute has just been retrieved. Compare with next-token position and initial position. data list. A grouping of tokens used to delimit response records in an SPI response. A data list begins with ZSPI-TKN-DATALIST and ends with ZSPI-TKN-ENDLIST. See response record. definition files.
error list Glossary error list. A grouping of tokens used within a response record to provide error and warning information. An error list begins with ZSPI-TKN-ERRLIST, ends with ZSPI-TKNENDLIST, and contains an error token and other tokens explaining the error. Error lists can be nested within other error lists. The return token cannot be included in an error list. See return token. error number.
generic list Glossary generic list. The most general list construct supported by SPI. It starts with ZSPI-TKN-LIST and ends with ZSPI-TKN-ENDLIST. Generic lists can be nested. No Compaq subsystem uses generic lists, but subsystems you write can do so. Compare with data list and error list. GETVERSION command. An information command that retrieves the server version of the subsystem server and possibly additional version information about objects defined by the subsystem.
list Glossary list. In an SPI message, a group of tokens that defines a context for scanning the buffer and extracting tokens with the SSGET procedure. A list imposes a hierarchy on the buffer. To retrieve tokens from a list, a program must enter the list by retrieving the initial list token, retrieve tokens from the list, then exit the list to the next higher level of tokens by retrieving the end-list token. SPI defines four kinds of lists: data lists, error lists, segment lists, and generic lists.
nonsensitive command Glossary nonsensitive command. A command that does not affect the state of an object. Nonsensitive commands can be issued by any user or program that is allowed access to the subsystem. Most informational commands are nonsensitive. Compare with sensitive command. null value. A value in a field of an extensible structure indicating that no value was assigned by the sending process. Null values are initialized by the SSNULL procedure. object.
owner Glossary owner. In the case of a disk file, the user or program that created the file, or a user or program to whom the creator has given the file with the FUP GIVE command. In the case of a process, the user or program that created the process or, if the PROGID option was specified in the FUP SECURE command for the code file, the user or program that owns the code file. In the case of a token or other definition, the subsystem that provided the definition.
programmatic interface Glossary programmatic interface. A means for a program to communicate with another program.
return token Glossary return token. The response token that indicates whether a command was successful and why it failed if it did. Every response record in a response from a Compaq subsystem contains a return token. A response record can also contain error lists that include error tokens. The token code for the return token is ZSPI-TKN-RETCODE. Its value consists of a single integer field. Compare with error token. SCF. See Subsystem Control Facility (SCF). SCP. See Subsystem Control Point (SCP).
snapshot file Glossary snapshot file. A file used by context-sensitive servers to record response data for a command. It is used to ensure a consistent response in cases where data—for instance, statistics—might change between one reply message and the next. Compaq subsystems do not use snapshot files, but subsystems you write can do so. special operation.
SPI procedures Glossary SPI procedures. The procedures used to build and decode SPI messages. These procedures are SSINIT, SSNULL, SSPUT, SSPUTTKN, SSGET, SSGETTKN, SSMOVE, and SSMOVETKN. Corresponding TACL built-ins are also available. SPI standard definitions. The set of declarations available for use with the SPI procedures regardless of the subsystem. A set of subsystem-specific declarations is available for each subsystem, and some sets of declarations apply to multiple subsystems.
Subsystem Control Point (SCP) Glossary Subsystem Control Point (SCP). An intermediate management process used by many Compaq subsystems. There can be several instances of this process. Applications send commands to an instance of this process, which in turn sends them on to the manager processes of the target subsystem. The SCP also processes a few commands itself. It provides security features, version compatibility, support for tracing, and support for applications implemented as process pairs.
summary state Glossary summary state. One of the generally defined possible conditions of an object with respect to the management of that object. A summary state differs from a state in two ways. First, a summary state pertains to the management of an object whereas a state can convey other kinds of information about the object. Second, the set of summary states is a common list defined the same way for all extended SPI subsystems whereas the set of possible states differs from subsystem to subsystem.
token map Glossary token map. An SPI structure that describes the fields of an extensible structured token. Also, a variable name used to refer to an extensible structured token. The token map includes a token code and a description of the token value: its fields, the null values of those fields, and the versions of the fields.
warning Glossary SPI Common Extensions Manual—427508-001 Glossary -16
Index A ABORT command 5-9, 5-12 ABORTING summary state 2-10 ACTIVATE command 5-9, 5-13 ADD command 5-15 AGGREGATE command 5-16 ALLOCATE command 5-18 ALLOWOPENS command 5-20 ALTER command 5-21, B-39 B BACKUPCPU startup parameter B-5 BACKUPDEBUG startup parameter B-5 Buffer See Message buffer C CAID, role in command security 5-8 CHARMAPFILE startup parameter B-6 CHARMAPNAME startup parameter B-6 CMD data definition type 4-1 COLLECTOR startup parameter B-6 COLLECTOR-n startup parameter B-6 Command message ca
E Index Definition files (continued) version compatibility 3-4 Definitions See Data definitions DELETE command 5-28 DIAGNOSE command 5-30 DIAGNOSING summary state 2-10 DISCONNECT command 5-31 Distributed management 1-10/1-12 Distributed Systems Management (DSM) 1-1 DUMP command 5-34 E EMS B-6, B-15 See also Event messages ENM data definition type 4-1 ENQUIRE command 5-35 ERR data definition type 4-1 Errors common error messages A-1/A-46, B-92/B-115 during startup of ZCMK-based process B-8 file-system err
G Index File system (continued) error 30 B-79 error 38 3-3 error 43 B-83 error 60 B-71 errors B-82 FORBIDOPENS command 5-38 G GETVERSION command description 5-39 specifying command security 3-4 ZCMK definition B-41 H Header tokens in response 5-6 ZSPI-TKN-COMMAND 2-7, 5-2 ZSPI-TKN-HDRTYPE 2-7 ZSPI-TKN-MAXRESP 5-3 ZSPI-TKN-MAX-FIELD-VERSION 3-4 ZSPI-TKN-OBJECT-TYPE 2-2, 5-2 ZSPI-TKN-SSID 5-2 Hierarchies 2-3 changing an object’s location (MOVE) 5-53 hierarchical naming 2-5 order of object processing 2-7 H
N Index Message queuing 3-3 Message routing overview 1-8, 1-10/1-12 SCP routing algorithm 3-2 target process identification 2-11 Message validation by ZCMK subsystems B-35/B-38 security role of SCP 3-4 MOVE command 5-53 ZCMK-MAP-STATS-OPNR B-32 ZCMK-MAP-STATS-RECV B-33 Object status 5-70 Object types 2-2 description of ZCOM types 4-20 example of assigning 2-3 hierarchies 2-3 Objects 2-1 OUT process option B-5 N P NAME process option B-4 Native object type B-39 Nonconfigured objects defined 2-2 deletin
S Index S SCF and the $ZNET SCP process 3-6 overview 1-9 SCP adding new REQID tokens 3-5 buffer size 3-2 command message cancellation 3-3 command message validation 3-4 command timeout 2-9, 3-5 concurrent applications supported 3-2 message queuing 3-3 message routing 3-2 nowait depth 3-3 opening an SCP process 3-6 overview 1-8 requester identification 3-4 security validation 3-4 software version validation 3-4 Security See Command security Segmented responses INFO response B-44 LISTOPENS response B-46 ZCM
U Index TYP data definition type 4-1 U UNKNOWN summary state 2-10 V VAL data definition type 4-1 VERIFY command 5-81 Version validation 3-4 W Wild cards, in object name templates 2-6 Z ZCDG data definitions C-1/C-17 event messages C-17/C-40 ZCDG-DDL- data structures DIAG-ERR C-7 DIAG-FILEID C-16 DIAG-PHYS-ADDR C-8 ZCDG-EVT- events BOB-ERR-FRAME C-36 BOB-WARN C-37 CIU-ERR C-36 CLB-CMD-REJ C-37 CLIP-ERR C-39 CLIP-PROBE-ERR C-35 CLIP-SUB-ERR C-39 CTLR-DWLOAD C-25 DIAG-ERR C-34 DIAG-TEST C-33 DIAG-UPDATE
Z Index ZCDG-TKN- tokens (continued) DWLOAD-ERR C-11, C-25 EIO-CHNL-STATUS C-11 EIO-ERR C-12 EIO-LAC C-12, C-23, C-25 EIO-LPRM C-12, C-23 EIO-RDST C-12, C-24 EIO-RIST C-13 FRAME-SIZE C-13, C-28 IIO-CHNL-STATUS C-13, C-25 IIO-RIC C-13, C-25, C-29, C-30, C-31 IIO-RIST C-13, C-25 IOC-STATUS C-14, C-23 NET-FILENAME C-14 REASON C-14, C-21 REQUESTERID C-15, C-21 RESIDUE C-15, C-24 RETRY-CNT C-15 SEND-CLIP-STATE C-14, C-15 SEQ-NUM C-15 SUBDEV-NUM C-16, C-40 UPDATE-FILE C-16 ZCDG-TYP- token types DIAG-ERR C-7 DIA
Z Index ZCMK-ERR- errors (continued) NO-CHARMAP B-95 ZCMK-EVT- messages BAD-BKUP-OPEN B-91 BAD-CHARMAP B-64 BAD-OPNR B-90 BAD-PARAM-NAME B-89 BAD-PARAM-VAL B-89 BAD-REOPEN B-88 BAD-SWAPVOL B-59 BAD-SYS-MSG B-87 BKUP-DIED B-87 BKUP-STARTED B-86 BKUP-STOPPED B-70 CANT-ALLOC-SEG B-68 CANT-INIT-CHKPT B-61 CANT-START-BKUP B-85 CANT-START-CHILD B-62 EMS1-STOPPED B-59 EMS1-SWITCHED-FROM B-58 EMS1-SWITCHED-TO B-58 EMS2-STOPPED B-57 EMS2-SWITCHED-FROM B-57 EMS2-SWITCHED-TO B-56 EMS3-STOPPED B-56 EMS3-SWITCHED-FROM
Z Index ZCMK-TKN- tokens (continued) CHMAP-NOTE B-13, B-43 CHMAP-XFNAME B-13, B-40, B-43, B-64, B-65 CKPERR B-14, B-61 CMD-CODE B-14 CPU B-14, B-70, B-86, B-87 EMS-XFNAME B-15, B-40, B-44 EMS-XFNAME-1 B-44 EMS-XFNAME-2 B-44 EMS-XFNAME-3 B-44 EMS-XFNAME-n B-15, B-40 FILE-ROLE B-16, B-69, B-82 FNUM B-16, B-73, B-78 FSERR B-17, B-66, B-69, B-83 LIB-FILE-MOD B-17, B-44 LIB-XFNAME B-17, B-44 LIFESTAT B-18, B-63 LISTOP-QUALIFS B-18, B-46 LISTOP-XPNAME B-18, B-45 LOG-XFNAME B-19, B-41, B-44 MEM-CNGST B-19 MEM-CO
Z Index ZCOM-CMD- commands (continued) INITIALIZE 5-45, 5-47 LISTOBJECTS 5-49, B-45 LISTOPENS 5-51, B-45 LOAD 5-52 MOVE 5-53 NULL 5-55 PROBE 5-56 RELEASE 5-57 RENAME 5-59 REPLACE 5-61 RESET 5-62 RESETSTATS 5-63, B-46 START 5-66 STATISTICS 5-67, B-47 STATUS 5-70, B-47 STOP 5-71 SUSPEND 5-73 SWITCH 5-75, B-48 TELL 5-78 TRACE 5-79 TRACE-ENQ 5-80 VERIFY 5-81 ZCOM-DDL- data structures AGGR-STATE-CNT 4-19 MAX-MSG-BUFFER 4-2 MSG-BUFFER 4-3 REQID 4-19 TRACE-MODIF 4-27 TRACE-WORK 4-27 ZCOM-ERR- errors ALRDY-USING-
Z Index ZCOM-ERR- errors (continued) SWITCH-WRNG-RES A-38 TKN-CNTXT-CODE-INV A-31 TKN-CNTXT-REQ A-30 TKN-CNTXT-VAL-INV A-32, B-115 TKN-CODE-INV A-24, B-110 TKN-DUP A-25, B-110 TKN-LEN-INV A-25, B-111 TKN-REQ A-26, B-112 TKN-VAL-INV A-27, B-112 VAL-REQ A-28, B-113 VSN-INCOMP A-29, B-114 ZCOM-EVT- messages CPU-SWITCH 6-1 IO-FATAL-ERR 6-4 PATH-SWITCH 6-2 SUMSTATE-CHG 6-3 ZCOM-MAP- structure maps 3-4 AGGR-STATE-CNT 4-19, 5-18 REQID 2-13, 3-4, 4-19, 5-3 TRACE-MODIF 4-27 TRACE-WORK 4-27 ZCOM-OBJ- object types 2
Z Index ZCOM-TKN- tokens (continued) TRACE-OPT 4-27 XMGR 2-11, 3-2, 4-18, 5-3, 5-6 ZCOM-VAL- token values DIAG-OPT-ENTER 4-4 DIAG-OPT-EXIT 4-4 HW 4-4, 4-10 IO-ERR-error 6-5 MAX-REQ-BUFLEN 3-2 MAX-RSP-BUFLEN 3-2 OBJNAME-LEN 4-9 OP-REQ 4-4, 4-10 PATH-A 4-9 PATH-B 4-9 PATH-UNDEF 4-9 POWER-FORCED 4-3 POWER-MAX 4-3 POWER-NORMAL 4-3 POWER-ORDERLY 4-3 PROTO 4-4, 4-10 SECUR-SUPP-ALL 4-6 SECUR-SUPP-NONE 4-6 SUB-ALL 4-16 SUB-NONE 4-16 SUB-ONLY 4-16 SUMSTATE-ABORTING 4-9, 4-15 SUMSTATE-DEF 4-9, 4-15 SUMSTATE-SERVICE
Special Characters Index ZTRC-VAL- token values (continued) SUPP-SCP-LDEV 4-7 SUPP-SCP-ONLY 4-7 Special Characters $ZNET 3-6 SPI Common Extensions Manual—427508-001 Index -13
Special Characters Index SPI Common Extensions Manual—427508-001 Index -14
