Networking and Data Communications Library SNAX/APC Management Programming Manual Abstract SNAX/APC provides LU type 6.2 support for the Tandem implementation of SNA. This manual provides information about the management programming interface to SNAX/APC. Part Number 111813 Edition Second Published Product Version Release ID Supported Releases July 1995 SNAX/APC D30 D30.02 This manual supports D30.00 and all subsequent releases until otherwise indicated in a new edition.
Document History Edition Part Number Product Version Earliest Supported Release Published First Second 064526 111813 SNAX/APC D10 SNAX/APC D30 D10.00 D30.00 February 1993 July 1995 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT).
New and Changed Information This version of the SNAX/APC Management Programming Manual (part number 111813) is a revision of the previous version of the manual (part number 064526). It has been changed to reflect several enhancements, new features, and upgrades. All changes in technical content in this manual have been indicated with change bars.
New and Changed Information The ZAPC-TKN-D-MAXINRUSIZE token definition has been changed to reflect the addition of this token to the ADD, ALTER, and INFO PTNR-MODE response buffer. The ZAPC-TKN-D-MAXOUTRUSIZE token definition has been changed to reflect the addition of this token to the ADD, ALTER, and INFO PTNR-MODE response buffer. The ZAPC-TKN-REMOTE-ATTACH-DISP token description has been enhanced to note that this token is included in the INFO PROC response buffer.
New and Changed Information The ADD TPN command has the following changes: The ZAPC-TKN-CHAR-MAPPING-SUPP token has been added. The ZCMK-TKN-CHMAP-NAME token has been added. The ZAPC-TKN-REPLY-DELAYED-ON-ERR token has been added. Additional items have been included in the “Operational Notes” subsection. The ALTER LU command has the following changes: The ZAPC-TKN-SNAX-MAX-RETRY-COUNT token has been added. The ZAPC-TKN-SNAX-RETRY-TIMER token has been added.
New and Changed Information The INFO PROC command has the following changes: ZSPI-TKN-ALLOW has been added to the command buffer. The ZSPI-TKN-SEGLIST token has been added. Within this list token the ZCMK-TKN-SEGTYPE, ZCMK-TKN-CHFILE-MAPNAME, and ZCMK-TKNCHFILE-MAPNOTE tokens have been added. ZCMK-MAP-INFO. The ZCMK-TKN-CHMAP-BANNER token has been added. The ZCMK-TKN-CHMAP-FILE-MOD token has been added. The ZCMK-TKN-CHMAP-NAME token has been added. The ZCMK-TKN-CHMAP-NOTE token has been added.
New and Changed Information Several new operational notes have been added to the START command. The token ZAPC-TKN-SNAX-RETRY-COUNT has been added to the STATUS LU command. The STATISTICS PROC command has been added. An operational note has been added for the STOP LU and STOP PTNR-MODE commands. Section 6 This section, entitled “Event Management,” has the following changes: The subsection entitled “Subsystem Processes That Report Events” has been enhanced to include a discussion of common events.
New and Changed Information (This viii page left intentionally blank) 111813 Tandem Computers Incorporated
Contents About This Manual xv Notation Conventions Section 1 xix Introduction to SNAX/APC Interfaces to SNAX/APC 1-2 Relationship of Applications to the SNAX/APC Subsystem Comparing DSM Applications and SCF 1-3 Management Programming for SNAX/APC 1-5 SNAX/APC Management Functions 1-5 Objects Controlled by SNAX/APC 1-5 Introduction to SNAX/APC Programmatic Commands SPI Programming Considerations 1-7 Section 2 1-6 Communicating With the SNAX/APC Process Communicating With SCP 2-1 Fault-Tolerant
Contents Section 4 Common Definitions Standard SPI Definitions Used by SNAX/APC Standard EMS Definitions Used by SNAX/APC 4-1 4-5 Standard Data Communications Definitions 4-6 ZCOM Object Types 4-8 ZCOM Values 4-8 Data Communications Simple Tokens (ZCMK and ZCOM) ZCMK and ZCOM Extensible Structured Tokens 4-14 Standard SNAX/APC Definitions 4-15 Version Value 4-18 Buffer Declarations 4-18 Simple Tokens Used by SNAX/APC 4-19 Statistics Extensible Structured Tokens 4-48 Status Extensible Structured Token 4-
Contents INFO Command 5-44 INFO CONVERSATION 5-47 INFO LU 5-49 INFO PROC 5-51 INFO PTNR-LU 5-55 INFO PTNR-MODE 5-56 INFO SESS 5-59 INFO TPI 5-62 INFO TPN 5-63 LISTOBJECTS Command LISTOPENS Command 5-65 5-68 RESETSTATS Command 5-72 RESETSTATS LU 5-75 RESETSTATS PROC 5-76 RESETSTATS PTNR-MODE RESETSTATS SESS 5-79 START Command 5-78 5-80 STATISTICS Command 5-84 STATISTICS LU 5-87 STATISTICS PROC 5-88 STATISTICS PTNR-MODE STATISTICS SESS 5-91 5-90 STATUS Command 5-92 STATUS CONVERSATION 5-95 STATUS LU 5
Contents Section 6 Event Management Before You Report a Problem 6-1 Subsystem Processes That Report Events 6-2 Common Events -00001 Through -00999 and -32nnn Series Events SNAX/APC Event Summary 6-5 Potentially Critical Events 6-8 Event Management Programming Considerations 6-8 Event Message Descriptions 6-9 1: ZAPC–EVT–FSM–ERR 6-10 2: ZAPC–EVT–INV–INIT 6-14 3: ZAPC–EVT–INV–CONFIG 6-16 6: ZAPC–EVT–INV–OP 6-18 10: ZAPC–EVT–BID–REJECT 6-19 11: ZAPC–EVT–BKP–TAKEOVER 6-20 12: ZAPC–EVT–DEALLOCATE–ERR 6-2
Contents Appendix A Error Messages Before You Report a Problem A-1 Common Errors Notation Used A-3 SNAX/APC Errors A-4 1: ZAPC-ERR-ACTV-FAIL-NO-RETRY A-5 2: ZAPC-ERR-ACTV-FAIL-RETRY A-6 3: ZAPC-ERR-ALLOC-ERR-NO-RETRY A-7 4: ZAPC-ERR-ALLOC-ERR-RETRY A-8 5: ZAPC-ERR-ALLOC-ERR-PGM-NOT-AVL A-9 6: ZAPC-ERR-CMD-FORCED A-10 7: ZAPC-ERR-CMD-INV-DEFT-OBJ A-11 8: ZAPC-ERR-CMD-INV-NOT-PS-LU A-12 9: ZAPC-ERR-CMD-NEGOTIATED A-13 10: ZAPC-ERR-CMD-RACE-REJECT A-14 11: ZAPC-ERR-CONFIG-IN-PROGRESS A-15 12: ZAPC-ERR-DE
Contents 35: 36: 37: 38: 39: 40: 41: 42: Appendix B ZAPC-ERR-UPPER-OBJ-NOT-FOUND A-40 ZAPC-ERR-UPPER-OBJ-NOT-STARTED A-41 ZAPC-ERR-TKN-INV-IN-SUMSTATE A-42 ZAPC-ERR-CANNOT-SWITCH-TO-SS A-43 ZAPC-ERR-CONFIG-IS-BAD A-44 ZAPC-ERR-CONFIG-IS-SWITCHING A-45 ZAPC-ERR-CONFIG-FILE-NAME A-46 ZAPC-ERR-OBJ-IS-STARTING A-47 Programming Example Glossary Glossary–1 Index Figures Index–1 Figure 1-1. Interfaces to SNAX/APC Figure 1-2. How SNAX/APC Fits Into the DSM Architecture Figure 3-1.
About This Manual Audience and Purpose This manual serves as both a user's guide and a reference manual for the development of Distributed Systems Management (DSM) applications that communicate with the SNAX/APC subsystem. This manual is for programmers writing network management applications. Support is provided for the C, TAL, COBOL85, Pascal, and TACL programming languages.
About This Manual Prerequisite Knowledge Prerequisite To use this manual effectively, you should be familiar with Tandem system Knowledge architecture, have a reading knowledge of the Data Definition Language (DDL), and have a working knowledge of both the SNAX/APC subsystem and the language in which you are programming: TAL, C, COBOL85, Pascal, or TACL.
About This Manual Prerequisite Knowledge Availability Information in Tandem Manuals Tandem provides several manuals which address issues of availability. Availability refers to end-user availability—that is, the amount of time an application running on a Tandem system can be used effectively by a user of that application.
About This Manual Prerequisite Knowledge Transaction Programmer's Reference Manual for LU Type 6.2 ) describes the set of functions – of both the base and option sets – that may be available in an implementation of a type 6.2 LU. The syntax of each verb is described, as well as all of the verbs types (such as basic and mapped, and the control operators) and the return codes. It also provides conversation state and verb matrixes.
Notation Conventions The following list summarizes the conventions for syntax presentation in this manual. Notation Meaning UPPERCASE LETTERS Uppercase letters represent keywords and reserved words; enter these items exactly as shown. In syntax boxes, uppercase letters represent names from the definition files; enter these names exactly as shown. Lowercase letters represent words that are part of the syntax notation in syntax boxes, including DDL keywords.
About This Manual (This page left intentionally blank) xx 111813 Tandem Computers Incorporated
1 Introduction to SNAX/APC Tandem’s SNAX Advanced Program Communications (SNAX/APC) consists of several programs and support files that jointly form a subsystem. The purpose of this subsystem is to allow programs in a Tandem system to communicate with programs supporting LU 6.2 in an SNA network. This release of SNAX/APC supports the management programming interface provided by Tandem’s Distributed Systems Management (DSM).
Introduction to SNAX/APC Interfaces to SNAX/APC Interfaces to Figure 1-1 shows SNAX/APC and its DSM interfaces. The SNAX/APC Planning and SNAX/APC Configuration Manual and the SNAX/APC Application Programming Manual describe SNAX/APC and its architecture in much greater detail. Figure 1-1.
Introduction to SNAX/APC Comparing DSM Applications and SCF Comparing DSM Applications and SCF SCF provides an interface to SNAX/APC that allows you to control SNAX/APC interactively. The programmatic interface provided by DSM—including the Subsystem Programmatic Interface (SPI) and EMS—offers the following advantages: Programs can handle many routine SNAX/APC management tasks, which frees operators and other network-management personnel to do work that requires judgment and creativity.
Introduction to SNAX/APC Comparing DSM Applications and SCF Figure 1-2. How SNAX/APC Fits Into the DSM Architecture EMS Filter Consumer Distributor DSM Application Responses Commands SCP Event Log $SNAX/APC-process .
Introduction to SNAX/APC Management Programming for SNAX/APC Management The DSM management programming interfaces to the SNAX/APC subsystem enable Programming for applications to execute configuration commands programmatically and to obtain SNAX/APC configuration and statistical information about SNAX/APC objects. They may also initiate and stop the tracing of certain SNAX/APC objects.
Introduction to SNAX/APC Management Programming for SNAX/APC Introduction to SNAX/APC Programmatic Commands Table 1-1 briefly describes the programmatic commands available for SNAX/APC. This table also indicates the commands that accept the wild-card characters * and ?. These characters are described in “Using Wild-Card Characters,” later in this subsection. Table 1-1.
Introduction to SNAX/APC Management Programming for SNAX/APC SPI Programming Considerations DSM applications use SPI procedures to build command buffers and to extract data from response buffers. Tasks for SNAX/APC Management Programming SNAX/APC programming for DSM involves both communicating with the SCP to configure and manage your system (control and inquiry) and communicating with EMS to manage events that occur as the system is running.
Introduction to SNAX/APC Management Programming for SNAX/APC Security SNAX/APC commands are classified as either sensitive or nonsensitive. Sensitive commands can only be issued by users with the super group ID (or any member of the same user group that started the SNAX/APC process). Nonsensitive commands can be issued by any user. Section 5, “Commands and Responses,” describes which commands are sensitive and which are nonsensitive.
2 Communicating With the SNAX/APC Process SNAX/APC subsystem commands are processed and responses are generated by the SNAX/APC process. However, DSM applications do not communicate directly with the SNAX/APC process. DSM applications send requests to the SCP, which then routes the SCP requests to the correct process. In the case of SNAX/APC, this is done by opening the process with the qualifier #ZSPI, (such as $snax/apc-process.#ZSPI) where $snax/apc-process is the name of the SNAX/APC process.
Communicating With the SNAX/APC Process Fault-Tolerant Attributes of SNAX/APC Fault-Tolerant The SNAX/APC process runs as a NonStop process pair. If the SNAX/APC primary Attributes of processor fails while processing a request, the SCP receives a file-system error, such as SNAX/APC 211 (CPU performing operation failed during operation).
3 Elements of SPI Messages for SNAX/APC This section describes the portions of Subsystem Programmatic Interface (SPI) messages that have specific meaning to SNAX/APC. SNAX/APC Definition The tokens and other definitions for SNAX/APC are provided by the following six Files definition files: ZSPIDEF.ZAPCCOB contains COBOL85 definitions. ZSPIDEF.ZAPCDDL contains DDL definitions. ZSPIDEF.ZAPCTACL contains TACL definitions. ZSPIDEF.ZAPCTAL contains TAL definitions. ZSPIDEF.ZAPCC contains C definitions. ZSPIDEF.
Elements of SPI Messages for SNAX/APC SNAX/APC Object Types and Names SNAX/APC Object Command messages contain a standard header token, ZCOM-CMD-command, which Types and Names contains a command number value that represents a command name. The commands applicable for a SNAX/APC subsystem are described in Section 5, “Commands and Responses.” Another standard header token in the command message indicates the type of object upon which the command is to operate.
Elements of SPI Messages for SNAX/APC Object Hierarchies Object Hierarchies A hierarchical relationship exists among the object types in the SNAX/APC subsystem. All object types are subordinate to the SNAX/APC process. In addition to this master hierarchy, other hierarchical relationships exist between some of the object types. For example, a PTNR-MODE object is always subordinate to a PTNR-LU object. Figure 3-1 shows the hierarchical relationships among the SNAX/APC objects. Figure 3-1.
Elements of SPI Messages for SNAX/APC The CONVERSATION Object The CONVERSATION Object The CONVERSATION object type, ZCOM–OBJ-CONVERSATION, represents an LU 6.2 conversation. The conversation can be created by a transaction program (TP) issuing an ALLOCATE or MC-ALLOCATE conversation verb, and can be deleted by a TP issuing a DEALLOCATE OR MC-DEALLOCATE conversation verb.
Elements of SPI Messages for SNAX/APC The LU Object The LU Object The LU object type, ZCOM–OBJ–LU, is used when the object of a control or inquiry operation is a SNAX/APC local LU to the SNAX/APC process. An LU is the entry point through which a transaction program accesses the SNA network. The LU object name is the name of the local LU, and it has the following format: $apc-process.local-lu $apc-process is the name of the SNAX/APC process. local-lu is the name of the local LU object.
Elements of SPI Messages for SNAX/APC The PROC Object The PROC Object The PROC object type, ZCOM–OBJ–PROC, is used when the object of a control or inquiry operation is the SNAX/APC process itself. The name of the SNAX/APC process is accepted if it is present. The object name for the PROC object has the following format: $apc-process $apc-process is the name of the PROC object. It is the SNAX/APC process name. The name must begin with a dollar sign ($) followed by from 1 through 5 characters.
Elements of SPI Messages for SNAX/APC The PTNR-LU Object The PTNR-LU Object The PTNR-LU object type, ZCOM–OBJ–PTNR-LU, is used when the object of a control or inquiry operation is a partner (remote) LU to which the command is addressed. The object name for the PTNR-LU object is partner-lu, and it has the following format: $apc-process.local-lu.partner-lu $apc-process is the name of the SNAX/APC process. local-lu is the name of the local LU. partner-lu is the PTNR-LU object name.
Elements of SPI Messages for SNAX/APC The PTNR-MODE Object The PTNR-MODE Object The PTNR-MODE object type, ZCOM–OBJ–PTNR-MODE, is used to describe a group of sessions (or allowable sessions) established between a local LU and its partner LU. It specifies the set of characteristics that this group of sessions commonly shares. The object name for the PTNR-MODE object is partner-mode, and it has the following format: $apc-process.local-lu.partner-lu.
Elements of SPI Messages for SNAX/APC The SESS Object The SESS Object The SESS object type, ZCOM–OBJ–SESS, is used when the object of a control or inquiry operation is an LU-LU session known to the specific instance of SNAX/APC to which the command is addressed. SNAX/APC reserves no specific names for session objects. The object name for the SESS object is session-id, and it has the following format: $apc-process.local-lu.partner-lu.partner-mode.
Elements of SPI Messages for SNAX/APC The TPI Object The TPI Object The TPI object type, ZCOM-OBJ-TPI, is used when the object of a control or inquiry operation is a local instance of a transaction program. The TPI object can be a Tandem process or a thread within a Tandem process. A TPI object can be created by a TP issuing a TP-READY service verb. It can be deleted by a TP issuing a TP-END service verb, an ABORT or STOP command, or a file system CLOSE request.
Elements of SPI Messages for SNAX/APC The TPN Object The TPN Object The TPN object type, ZCOM-OBJ-TPN, is used when the object of a control or inquiry operation is a local transaction program (TP) name entry known to the SNAX/APC process.. The object name for the TPN object is tpn, and it has the following format: $apc-process.local-lu.tpn $apc-process is the name of the SNAX/APC process. local-lu is the name of the parent LU object. tpn is the name of the TPN object.
Elements of SPI Messages for SNAX/APC Object Referencing Object Referencing A requester can use the SEL-SUMSTATE modifier and the SUB modifier to indicate to which objects a given command is to be applied. These modifiers can be used simultaneously. It is the responsibility of the requester to make sure that the objects can be referenced by the command. For example, an attempt to issue an ALTER PROC command produces errors if the SUB modifier causes the command to be applied to sessions.
Elements of SPI Messages for SNAX/APC Object Referencing The SUB Modifier SNAX/APC accepts the SUB modifier in almost all commands. You specify the subordinate modifier by using ZCOM–TKN–SUB. The enumerated values for this token are: ZCOM–VAL–SUB–ALL specifies that the command must affect the named object and all the subordinate objects, if any. ZCOM–VAL–SUB–NONE specifies that the named object, but none of the subordinate objects, is affected by the command.
Elements of SPI Messages for SNAX/APC Object Summary States Object Summary Objects defined for SNAX/APC are always in one of several states. The state of an States object at any given instant is important: certain commands require that an object be in a particular state. For most objects, the state changes as commands are issued against the object. This can be illustrated by the act of starting an LU, which causes the state to change from STOPPED, to STARTING, to STARTED. The state is used in several ways.
4 Common Definitions The token-oriented programmatic interface to the SNAX/APC subsystem uses definitions from four different sources: the SPI standard definitions, the EMS standard definitions, the data communications standard definitions, and the SNAX/APC definitions. This section discusses the definitions from these four sources that can be used in a management application to communicate with SNAX/APC.
Common Definitions Standard SPI Definitions Used by SNAX/APC Table 4-1.
Common Definitions Standard SPI Definitions Used by SNAX/APC All SPI standard definitions are fully described in the SPI Programming Manual. Information about these definitions specific to the SNAX/APC subsystem is given below. ZSPI-SSN-ZAPC is the subsystem number assigned to SNAX/APC. ZSPI-TKN-ALLOW is a standard SPI token described in the SPI Programming Manual. This is an enumerated token with several enumerated values. The only token value of interest to SNAX/APC is ZSPI-VAL-ALLOW-SEGMENTS.
Common Definitions Standard SPI Definitions Used by SNAX/APC ZSPI-TKN-SSID contains ZAPC-VAL-SSID, the subsystem ID of the SNAX/APC subsystem. ZAPC-VAL-SSID has the following definition: def ZAPC-VAL-SSID tacl ssid. 02 Z-FILLER type ZSPI-DDL-CHAR8 value is ZSPI-VAL-TANDEM. 02 Z-OWNER redefines Z-FILLER type ZSPI-DDL-CHAR8. 02 Z-NUMBER type ZSPI-DDL-INT value is ZSPI-SSN-ZAPC. 02 Z-VERSION type ZSPI-DDL-UINT value is ZAPC-VAL-VERSION. end.
Common Definitions Standard EMS Definitions Used by SNAX/APC Standard EMS Definitions Used by SNAX/APC Definitions whose symbolic names begin with the characters ZEMS- are Event Management Service (EMS) standard definitions. Table 4-2 lists all the EMS standard definitions used in the token-oriented programmatic interface to SNAX/APC. These definitions consist of simple tokens used in SNAX/APC event messages and header tokens available to all applications using EMS. Table 4-2.
Common Definitions Standard Data Communications Definitions Standard Data Communications Definitions Definitions whose symbolic names begin with the characters ZCMK- and ZCOM- are standard definitions for the data communications subsystems. Table 4-3 lists all the data communications standard definitions used in the tokenoriented programmatic interface to SNAX/APC.
Common Definitions Standard Data Communications Definitions Table 4-3.
Common Definitions ZCOM Object Types ZCOM Object Types ZCOM Values The SNAX/APC subsystem uses the following ZCOM object types. For more information about these object types, refer to Section 3, “Elements of SPI Messages for SNAX/APC.” ZCOM-OBJ-CONVERSATION indicates a CONVERSATION object. ZCOM-OBJ-LU indicates an LU object. ZCOM-OBJ-NULL indicates that the object type is irrelevant or that the command refers to a set of objects. ZCOM-OBJ-PROC indicates a PROC object.
Common Definitions Data Communications Simple Tokens (ZCMK and ZCOM) ZCOM-VAL-SUMSTATE-STARTING indicates the STARTING summary state. ZCOM-VAL-SUMSTATE-STOPPED indicates the STOPPED summary state. ZCOM-VAL-SUMSTATE-STOPPING indicates the STOPPING summary state. ZCOM-VAL-TRACE-SUPP-NONE is returned in the ZCOM-TKN-GETVSN-TRACE-SUPP response token (in response to the SNAX/APC GETVERSION command) to indicate that the SCP trace facility is not supported by SNAX/APC.
Common Definitions Data Communications Simple Tokens (ZCMK and ZCOM) ZCMK-TKN-CHMAP-NAME identifies the default character map used for data translations. The value of this token has to be an exact 50-byte string with trailing blanks. If the token value is a string of all blanks, the Tandem standard ASCII-to-EBCDIC translation table will be used. ZCMK-TKN-CHMAP-NOTE conveys the notes associated with the character map table specified in the ZCMKTKN-CHMAP-NAME token.
Common Definitions Data Communications Simple Tokens (ZCMK and ZCOM) ZCMK-TKN-LOG-XFNAME identifies the log file. This token is not recommended for use in a production environment. In a production environment, you should specify the COLLECTOR startup parameter or the ZCMK-TKN-EMS-XFNAME token in an ALTER PROC command for message logging. ZCMK-TKN-MSG-XFNAME is the name of the SNAX/APC message file. This token must contain a file name that identifies a valid SNAX/APC message file.
Common Definitions Data Communications Simple Tokens (ZCMK and ZCOM) ZCOM-TKN-GETVSN-SECUR-SUPP is the security support level returned in the response to the GETVERSION command. The supported value of this token for SNAX/APC is ZCOM-VALSECUR-SUPP-ALL. ZCOM-TKN-GETVSN-TRACE-SUPP is the trace support level returned in the response to the GETVERSION command. The supported value of this token for SNAX/APC is ZCOM-VAL-TRACE-SUPPNONE. ZCOM-TKN-OBJNAME contains the object name of a SNAX/APC object.
Common Definitions Data Communications Simple Tokens (ZCMK and ZCOM) ZCOM-TKN-SUBJ-CONVERSATION identifies a conversation. ZCOM-TKN-SUBJ-LU identifies an LU. ZCOM-TKN-SUBJ-PROC identifies the SNAX/APC process. ZCOM-TKN-SUBJ-PTNR-LU identifies a partner LU. ZCOM-TKN-SUBJ-PTNR-MODE identifies a partner mode. ZCOM-TKN-SUBJ-SESS identifies a session. ZCOM-TKN-SUBJ-TPN identifies a transaction program. ZCOM-TKN-SUBJ-TPI identifies an instance of a transaction program.
Common Definitions ZCMK and ZCOM Extensible Structured Tokens ZCMK and ZCOM Extensible Structured Tokens SNAX/APC uses the following extensible structured tokens, which are described in more detail in the SPI Common Extensions Manual. ZCMK-MAP-ALTER allows alteration of the debugging flags. ZCMK-MAP-INFO is included in the INFO command response and details the current values of the DebugOnError and BackupDebug flags, and the BackupCPU number.
Common Definitions Standard SNAX/APC Definitions Standard SNAX/APC The following subsections describe tokens defined by SNAX/APC: Definitions The first subsection describes the version value. The second subsection describes the buffer declaration values. The third subsection describes the common simple tokens. The fourth subsection describes the extensible structured tokens used by SNAX/APC. The names of all SNAX/APC token definitions begin with the string ZAPC-.
Common Definitions Standard SNAX/APC Definitions Table 4-4.
Common Definitions Standard SNAX/APC Definitions Table 4-4.
Common Definitions Version Value Version Value The version value (ZAPC-VAL-VERSION) indicates the version of the SNAX/APC subsystem currently being used. For example, the version value may have the following definition: constant Buffer Declarations ZAPC-VAL-VERSION value is version "D30".
Common Definitions Simple Tokens Used by SNAX/APC Simple Tokens Used by SNAX/APC The following simple tokens are defined in the SNAX/APC subsystem: ZAPC-TKN-ACTV-CONLOSERS-CNT specifies the currently active contention loser session count. The integer value ranges from 0 to 1024. The ACTV-CONLOSERS-CNT token has the token type ZSPI-TYP-INT. The programmatic commands that use this token are ZCOM-CMD-INFO and ZCOMCMD-STATUS. The valid object type for this token is PTNR-MODE.
Common Definitions ZAPC-TKN-AUTO-ACTIVATE-LIM ZAPC-TKN-AUTO-ACTIVATE-LIM specifies the number of contention-winner sessions that are activated automatically after the PTNR-MODE object is in the STARTED state. If the value of the AUTO-ACTIVATE-LIM token is greater than the value of the MINCONWINNERS-LIM token after the CNOS command has been negotiated, only the number of sessions specified by the MIN-CONWINNERS-LIM token is pre-established. Valid values for this token range from 0 to 1024.
Common Definitions ZAPC-TKN-CONFIG-XFNAME ZAPC-TKN-CHAR-MAPPING-SUPP specifies whether the SNAX/APC process performs character translations for mapped conversations subordinate to the target TPN or for a target conversation. The CHAR-MAPPING-SUPP token has the token type ZSPI-TYP-BOOLEAN. The programmatic commands that use this token include ZCOM-CMD-ADD (TPN object only), ZCOM-CMD-ALTER (TPN object only), and ZCOM-CMD-INFO. The valid object types for this token are CONVERSATION and TPN.
Common Definitions ZAPC-TKN-CONV-ID ZAPC-TKN-CONV-ID identifies the current conversation using a session. This token only exists when a conversation is active. The CONV-ID token has the token type ZSPI-TYP-STRING, with a maximum length of 8. The programmatic commands that use this token include ZCOMCMD-INFO and ZCOM-CMD-STATUS. The valid object type for this token is SESS. The CONV-ID token is returned in the ZCOM-CMD-STATUS and ZCOM-CMDINFO response buffers only when a conversation is active.
Common Definitions ZAPC-TKN-CUR-SEND-PACING-CNT ZAPC-TKN-CUR-MAXOUTRUSIZE indicates the current maximum size of normal flow request units (RUs) that the local LU sends on the session. This value is used to construct BIND images for local LU-initiated sessions. The CUR-MAXOUTRUSIZE token has the token type ZSPI-TYP-INT. The programmatic command that uses this token is ZCOM-CMD-INFO. The valid object types for this token are PTNR-MODE and SESS.
Common Definitions ZAPC-TKN-D-MAXINRUSIZE ZAPC-TKN-D-MAXINRUSIZE (for INFO SESS command) specifies the default maximum number of bytes for an incoming request/response unit (RU) . This value is taken from the PTNR-MODE for the session.. (for ADD, ALTER, or INFO PTNR-MODE command) specifies the maximum size of normal flow request units (RUs) that the local LU can receive over sessions started with the partner mode. Valid values are from 16 through 16,000.
Common Definitions ZAPC-TKN-D-MIN-CONWINNERS-LIM ZAPC-TKN-D-MIN-CONLOSERS-LIM specifies the number of sessions for which the local LU is designated to be the contention loser. The value can range from 0 to 1024. The value is used as the MIN_CONWINNERS_TARGET parameter of the INITIALIZE_SESSION_LIMIT CNOS verb. The D-MIN-CONLOSERS-LIM token has the token type ZSPI-TYP-INT. The programmatic commands that use this token include ZCOM-CMD-ADD, ZCOMCMD-ALTER, and ZCOM-CMD-INFO.
Common Definitions ZAPC-TKN-D-SESS-LIM ZAPC-TKN-D-SESS-LIM specifies the maximum number of sessions that can be established under a PTNRMODE object. The value can range from 1 to 1024, and is used as the LU_MODE_SESSION_LIMIT parameter of the INITIALIZE_SESSION_LIMIT CNOS verb. The sum of the D-SESS-LIMIT tokens of all started PTNR-MODE objects must be at least two less than the SESS-LIM value of the parent LU for those PTNR-MODE objects.
Common Definitions ZAPC-TKN-EMS-SUPPRESSION ZAPC-TKN-DRAIN-TARGET specifies whether the target LU in a CNOS conversation, initiated by a RESET_SESSION_LIMIT CNOS verb, can drain its allocation requests. A value of ZSPI-VAL-FALSE indicates that the target LU cannot drain its allocation requests. The DRAIN-TARGET token has the token type ZSPI-TYP-BOOLEAN. The programmatic commands that use this token include ZCOM-CMD-INFO and ZCOM-CMD-STOP. The valid object type for this token is PTNR-MODE.
Common Definitions ZAPC-TKN-FSM-CONV ZAPC-TKN-FSM-CONV specifies the status of the conversation. The FSM-CONV token has the token type ZSPI-TYP-ENUM. The programmatic command that uses this token is ZCOM-CMD-STATUS. The valid object type for this token is CONVERSATION. The following values are valid for this token: ZAPC-VAL-FSM-CV-RESET indicates Reset. ZAPC-VAL-FSM-CV-SEND indicates Send. ZAPC-VAL-FSM-CV-RCV indicates Receive. ZAPC-VAL-FSM-CV-RCVD-CNF indicates Receive Confirm.
Common Definitions ZAPC-TKN-LOCAL-SEC-ACCEPTANCE ZAPC-TKN-GENERAL-TP-RDY-SUPP specifies whether the TPN supports this TP-READY feature. A value of ZSPIVAL-FALSE indicates that it does not. (For more information about the general TP-READY feature, see the SNAX/APC Application Programming Manual.) The GENERAL-TP-RDY-SUPP token has the token type ZSPI-TYP-BOOLEAN. The programmatic commands that use this token include ZCOM-CMD-ADD, ZCOM-CMD-ALTER, and ZCOM-CMD-INFO. The valid object type for this token is TPN.
Common Definitions ZAPC-TKN-LOCAL-TP-NAME ZAPC-TKN-LOCAL-TP-NAME specifies the name of the local TPN that currently has a conversation using this session. The LOCAL-TP-NAME token has the token type ZSPI-TYP-STRING. The programmatic command that uses this token is ZCOM-CMD-INFO. The valid object type for this token is SESS. This token is returned in the ZCOM-CMD-INFO response buffer only when there is an active conversation using the session.
Common Definitions ZAPC-TKN-MIN-CONLOSERS-LIM ZAPC-TKN-MAXINRUSIZE specifies a default for the maximum number of bytes allowed on an incoming request/response unit (RU). Valid values range from 16 to 4096, and are provided by the MAXINRUSIZE SNAX/APC startup parameter. The MAXINRUSIZE token has the token type ZSPI-TYP-INT. The programmatic command that uses this token is ZCOM-CMD-INFO. The valid object type for this token is PROC. This token is always returned in the ZCOM-CMD-INFO response buffer.
Common Definitions ZAPC-TKN-MIN-CONWINNERS-LIM ZAPC-TKN-MIN-CONWINNERS-LIM specifies the minimum number of contention-winner sessions that the partner mode has. The value is used as the MIN_CONWINNER_SOURCE parameter of the CHANGE_SESSION_LIMIT (CNOS) verb. Valid values range from 0 to 1024. The MIN-COWINNERS-LIM token has the token type ZSPI-TYP-INT. The programmatic commands that use this token include ZCOM-CMD-ALTER and ZCOM-CMD-INFO. The valid object type for this token is PTNR-MODE.
Common Definitions ZAPC-TKN-PERIPHERAL-NODE ZAPC-TKN-PARALLEL-SESS-LU specifies whether or not the partner LU supports parallel sessions. A value of ZSPI-VAL-TRUE indicates that partner LU is a parallel-session LU (or supports parallel sessions). A value of ZSPI-VAL-FALSE indicates that the partner LU is a single-session LU; therefore, the local LU will neither initiate nor expect any CNOS commands. The PARALLEL-SESS-LU token has the token type ZSPI-TYP-BOOLEAN.
Common Definitions ZAPC-TKN-POLARITY ZAPC-TKN-POLARITY specifies whether the LU is the bidder or the first speaker of the current session. The POLARITY token has the token type ZSPI-TYP-ENUM. The programmatic command that uses this token is ZCOM-CMD-INFO. The valid object type for this token is SESS. The following enumerated values are valid for this token: ZAPC-VAL-POLARITY-BIDDER specifies that LU is the bidder in the current session.
Common Definitions ZAPC-TKN-REMOTE-ATTACH-DISP ZAPC-TKN-RCVD-BYTES-NOT-READ specifies the number of bytes that have been received by the local LU but have not yet been read by a transaction program (TP). If this value is greater than the value of the MAXAPPLIOSIZE token, SNAX/APC does not send a pacing response to the partner LU; the TP must read a sufficient number of bytes of data to make this value less than MAXAPPLIOSIZE, before SNAX/APC can send a pacing response to the partner LU.
Common Definitions ZAPC-TKN-REMOTE-ATTACH-TIMER ZAPC-TKN-REMOTE-ATTACH-TIMER specifies the amount of time in milliseconds that SNAX/APC will wait for a remote TP-READY to arrive to satisfy the Attach. If no remote TP-READY arrives before the time elapses, the Attach is rejected. Valid values are -1 and from 1 to 86,400,000 (24 hours). The default, -1, specifies an indefinite amount of time. The REMOTE-ATTACH-TIMER token has the token type ZSPI-TYP-INT2.
Common Definitions ZAPC-TKN-RESOURCE-ID The REPLY-DELAYED-ON-ERR token has the token type ZSPI-TYP-BOOLEAN. The programmatic commands that use this token are ZCOM-CMD-ADD, ZCOMCMD-ALTER, and ZCOM-CMD-INFO. The valid object type for this token is TPN. ZAPC-TKN-RESPONSIBLE specifies the LU that is responsible for selecting and deactivating sessions, as a result of a change that decreases the session limit or the maximum number of contention-winner sessions for the source or target LU.
Common Definitions ZAPC-TKN-RUS-TO-BE-SENT ZAPC-TKN-RUS-TO-BE-SENT specifies the number of RUs waiting to be sent to the partner LU. The RUS-TO-BE-SENT token has the token type ZSPI-TYP-INT. The programmatic command that uses this token is ZCOM-CMD-STATUS. The valid object types for this token are SESS and CONVERSATION. When specified for the SESS object, the token will not be returned in the ZCOMCMD-STATUS response buffer if the session is not in the STARTED state.
Common Definitions ZAPC-TKN-SESS-INST-ID ZAPC-TKN-SESS-CTRL-PRIV specifies whether or not the TPN is authorized to issue the ACTIVATE_SESSION and DEACTIVATE_SESSION session control verbs. The value ZSPI-VAL-TRUE indicates that the TPN is authorized to issue session control verbs, and the value ZSPI-VAL-FALSE indicates that the TPN is not authorized to issue session control verbs. The SESS-CTRL-PRIV token has the token type ZSPI-TYP-BOOLEAN.
Common Definitions ZAPC-TKN-SESS-LIM ZAPC-TKN-SESS-LIM specifies the maximum number of sessions that the local LU can have. Valid values range from 1 to 1024. If the value of ZAPC-TKN-SESS-LIM is 1, the local LU is treated as a single-session LU (that is, not supporting parallel sessions). If the value of ZAPC-TKN-SESS-LIM is greater than 1, the local LU is treated as a parallel-session LU. The maximum number of active sessions supported by a SNAX/APC process is 1024.
Common Definitions ZAPC-TKN-SNA-NAME ZAPC-TKN-SNA-NAME specifies the name of the LU as it is known by the partner system. It can be up to 17 characters, if entered in the form: [net-id.]LU-name where net-id is up to 8 characters long and LU-name is either a local or partner LU name that is up to 8 characters long. If the partner system changes its name for the local LU, you can change the value of this attribute without affecting the local transaction program.
Common Definitions ZAPC-TKN-SNAX-FILE-NAME ZAPC-TKN-SNAX-FILE-NAME specifies the file name of the Tandem access method that the local LU uses to exchange data with an SNA network. Although SNAX/APC does not check for duplicate files, every local LU should have a distinct SNAX-FILE-NAME, since SNAX/APC issues the OPEN request to the underlying access method exclusively.
Common Definitions ZAPC-TKN-SYNC-LEVEL ZAPC-TKN-SNAX-RETRY-COUNT returns the number of times that SNAX/APC has retried the open request. The SNAX-RETRY-COUNT token has the token type ZSPI-TYP-INT. The programmatic commands that use this token are ZCOM-CMD-INFO and ZCOMCMD-STATUS. The valid object type for this token is LU.
Common Definitions ZAPC-TKN-TERMINATION-CNT ZAPC-TKN-TERMINATION-CNT specifies the number of sessions that need to be terminated. Valid values range from 0 to 1024. The TEMINATION-CNT token has the token type ZSPI-TYP-INT. The programmatic commands that use this token are ZCOM-CMD-INFO and ZCOMCMD-STATUS. The valid object type for this token is PTNR-MODE. This token is always returned in the ZCOM-CMD-INFO and ZCOM-CMDSTATUS response buffers.
Common Definitions ZAPC-TKN-TRACE-RECSIZE ZAPC-VAL-TRC-OPT-BUFFER traces records obtained and returned to the local or extended buffer pool. ZAPC-VAL-TRC-OPT-DFC traces the finite state machines (FSMs) for the Data Flow Control (DFC) layer. ZAPC-VAL-TRC-OPT-LNS traces the FSMs for the Logical Network Services (LNS) layer. ZAPC-VAL-TRC-OPT-PROC traces data handled by the internal procedures of SNAX/APC. ZAPC-VAL-TRC-OPT-PS traces the FSMs for the Presentation Services (PS) layer.
Common Definitions ZAPC-TKN-TRACE-STATE ZAPC-TKN-TRACE-STATE specifies the current state of trace activity for the LU or PROC objects. The TRACE-STATE token has the token type ZSPI-TYP-ENUM. The programmatic command that uses this token is ZCOM-CMD-STATUS. The valid object types for this token are PROC and LU. The following enumerated values are valid for this token: ZAPC-VAL-TRACE-STATE-ACTV specifies that tracing is active. ZAPC-VAL-TRACE-STATE-INACTV specifies that tracing is inactive.
Common Definitions ZAPC-TKN-VERB-IN-PROGRESS ZAPC-TKN-TRACE-XFNAME specifies the name of the file to which trace information is to be written. If the file already exists, it is purged before a new file is created. If the file does not exist, a new file is created with an extent size of 100 pages for the primary extent and 20 pages for each of the secondary extents. The TRACE-XFNAME token has the token type ZSPI-TYP-STRING.
Common Definitions Statistics Extensible Structured Tokens Statistics Extensible Structured Tokens The extensible structured tokens specific to the RESETSTATS and STATISTICS commands in SNAX/APC are described in this subsection. ZAPC-MAP-STATS-LU This extensible structured token is defined by the DDL DEF ZAPC-MAP-STATS-LU. It contains statistical counters for the specified LU. The programmatic commands that use ZAPC-MAP-STATS-LU are ZCOM-CMDRESETSTATS and ZCOM-CMD-STATISTICS.
Common Definitions Statistics Extensible Structured Tokens ZDATA-SENT-CNT records how many bytes of data have been sent. ZDATA-RCVD-CNT records how many bytes of data have been received.
Common Definitions ZAPC-MAP-STATS-PTNR-MODE ZAPC-MAP-STATS-PTNR-MODE This extensible structured token is defined by the DDL DEF ZAPC-MAP-STATSPTNR-MODE. It displays the current statistical counters for the target partner mode. Included in this display are counters showing the number of times various CNOS verbs have been processed. The programmatic commands that use ZAPC-MAP-STATS-PTNR-MODE are ZCOMCMD-RESETSTATS and ZCOM-CMD-STATISTICS. The valid object type for this extensible token is PTNR-MODE.
Common Definitions ZAPC-MAP-STATS-PTNR-MODE ZCNOS-VERB-ISL-CNT specifies how many times the INITIALIZE_SESSION_LIMIT CNOS verb has been processed by SNAX/APC. ZCNOS-VERB-CSL-CNT specifies how many times the CHANGE_SESSION_LIMIT CNOS verb has been processed by SNAX/APC. ZCNOS-VERB-RSL-CNT specifies how many times the RESET_SESSION_LIMIT CNOS verb has been processed by SNAX/APC. ZCNOS-VERB-PSL-CNT specifies how many times the PROCESS_SESSION_LIMIT CNOS verb has been processed by SNAX/APC.
Common Definitions ZAPC-MAP-STATS-SESS ZAPC-MAP-STATS-SESS This extensible structured token is defined by the DDL DEF ZAPC-MAP-STATS-SESS. It displays the current statistical counters for the target session. Included in this display are counters showing the number of times various conversation verbs have been processed. The programmatic commands that use ZAPC-MAP-STATS-SESS are ZCOM-CMDRESETSTATS and ZCOM-CMD-STATISTICS. The valid object type for this extensible token is SESS.
Common Definitions ZAPC-MAP-STATS-SESS ZRESET-TIME specifies the date and time that the statistics counters were last reset by one of the following events: The statistics counters were reset by the RESETSTATS command (ZCOMCMD-RESETSTATS). The process was initiated. A takeover by the backup process occurred. ZSAMPLE-TIME is the date and time that the statistics were last sampled by a STATISTICS command.
Common Definitions ZAPC-MAP-STATS-SESS ZSEND-DATA-CNT specifies how many times the basic conversation verb SEND_DATA has been processed during this session. ZSEND-ERROR-CNT specifies how many times the basic conversation verb SEND_ERROR has been processed during this session. ZPREP-TO-RCV-CNT specifies how many times the basic conversation verb PREPARE_TO_RECEIVE has been processed during this session.
Common Definitions ZAPC-MAP-STATS-SESS ZMC-RCV-AND-WAIT-CNT specifies how many times the mapped conversation verb MC_RECEIVE_AND_WAIT has been processed during this session. ZMC-REQ-TO-SEND-CNT specifies how many times the mapped conversation verb MC_REQUEST_TO_SEND has been processed during this session. ZMC-SEND-DATA-CNT specifies how many times the mapped conversation verb MC_SEND_DATA has been processed during this session.
Common Definitions Status Extensible Structured Token Status Extensible Structured Token The extensible structured token specific to the STATUS command in SNAX/APC is described in this subsection. ZAPC-MAP-FSM-STATES This extensible structured token is specific to the ZCOM-CMD-STATUS command. The values in this extensible structured token display current status information about the specified objects. def ZAPC-DDL-FSM-STATES.
Common Definitions Status Extensible Structured Token ZFSM-CHAIN-RCV indicates the received chain states. If the session is not in the STARTED state, the value may be 0. Other possible values are: ZAPC-VAL-FSM-CHAINRCV-BETC (Between Chain) ZAPC-VAL-FSM-CHAINRCV-INC (In Chain) ZAPC-VAL-FSM-CHAINRCV-NG-SENT (Negative Response Sent) ZAPC-VAL-FSM-CHAINRCV-PND-RSP (Pending Response) ZAPC-VAL-FSM-CHAINRCV-PND-SND (Pending Send Reply) ZFSM-CHAIN-SEND indicates the sending chain states.
Common Definitions Status Extensible Structured Token ZFSM-ERROR-OR-FAILURE indicates errors or failures reported by other layers. If no conversation is active, the value is 0.
Common Definitions Status Extensible Structured Token ZFSM-QRI-CHAIN-RCV indicates whether SNAX/APC enforces the setting of the queued request indicator (QRI). If the session is not in the STARTED state, the value may be 0 Other possible values are: ZAPC-VAL-FSM-QRICHAINRCV-RESET (Reset) ZAPC-VAL-FSM-QRICHAINRCV-QR (Chain is QR chain) ZAPC-VAL-FSM-QRICHAINRCV-NOTQR (Chain is not QR chain) ZFSM-RCB-STATUS indicates the conversation resource status.
Common Definitions Status Extensible Structured Token ZFSM-STATUS indicates the LU-LU session status.
5 Commands and Responses This section defines the syntax and semantics for all the commands and responses supported by the SNAX/APC subsystem. Some tokens occur in multiple commands or responses. These common tokens are described in Section 4, “Common Definitions.
Commands and Responses Command Summary Command Summary Table 5–1 shows the commands that can be used in the management programming interfaces to SNAX/APC. Table 5–1.
Commands and Responses Command Summary Table 5–1.
Commands and Responses Commands by Target Object Type Commands by Target ZCOM–OBJ–CONVERSATION can be the target object type in the following Object Type SNAX/APC subsystem commands: INFO LISTOBJECTS STATUS ZCOM–OBJ–LU can be the target object type in the following SNAX/APC subsystem commands: ABORT ADD ALTER DELETE INFO LISTOBJECTS RESETSTATS START STATISTICS STATUS STOP TRACE ZCOM–OBJ–PROC can be the target object type in the following SNAX/APC subsystem commands: ALTER RESETSTATS GETVERSION STATISTI
Commands and Responses Commands by Target Object Type ZCOM–OBJ–TPN can be the target object type in the following SNAX/APC subsystem commands: ABORT LISTOBJECTS ADD START ALTER STATUS DELETE STOP INFO ZCOM–OBJ–TPI can be the target object type in the following SNAX/APC subsystem commands: ABORT INFO LISTOBJECTS STATUS STOP ZCOM–OBJ–NULL can be the target object type in the following SNAX/APC subsystem commands: GETVERSION LISTOBJECTS 111813 Tandem Computers Incorporated 5–5
Commands and Responses SNAX/APC Response Buffers SNAX/APC Response SNAX/APC can return nonsegmented and segmented responses. Segmented Buffers responses may be requested on the INFO PROC and LISTOPENS command. The structure of a response record returned by SNAX/APC adheres to the definitions in the SPI Programming Manual. The possible values of ZSPI–TKN–RETCODE and their associated error lists are given in Appendix A, “Error Numbers and Error Lists.
Commands and Responses SNAX/APC Commands and Responses SNAX/APC Commands On the following pages, each SNAX/APC command and its response is described in and Responses detail. The command descriptions appear in alphabetical order by command name.
Commands and Responses ABORT Command ABORT Command The ABORT command terminates the operation of the specified object as quickly as possible. ABORT is a sensitive command. If the ABORT command is applied to an object with subordinate objects, the subordinate objects are also forced into a STOPPED state. No attempt is made to inform the command issuer that the subordinate objects are active. Subordinate objects are aborted before the parent object.
Commands and Responses ABORT Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses ABORT Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses ABORT Command The ABORT PTNR-MODE command does the following: 1. Places the target PTNR-MODE object in the STOPPING state. 2. Issues a RESET_SESSION_LIMIT CNOS verb with the following settings: LU_NAME = the superior PTNR-LU name MODE_NAME = the target PTNR-MODE object’s attribute, mode-name RESPONSIBLE = SOURCE DRAIN_SOURCE = NO DRAIN_TARGET = NO FORCE = YES 3. Upon completion of the RESET_SESSION_LIMIT CNOS verb, the specified PTNR-MODE object is placed in the STOPPED state.
Commands and Responses ABORT Command The ABORT TPI command can be issued only when the specified TPI object is in the STARTING state. The command is rejected with the error ZCOM-ERR-CMDINV-IN-SUMSTATE if the TPI object is in any other state. As a result of the ABORT TPI command, any remote Attach requests that are queued are rejected with the sense data %H084B6031 (transaction program not available - retry allowed) when the origin of the TPI is remote.
Commands and Responses ADD Command ADD Command The ADD command is used to define new objects to the SNAX/APC process. The ADD command is a sensitive command. In addition to the following tokens, which are valid for all object types, an object type can have additional tokens that are valid for that object type only. Such objectdependent tokens are described specifically for each object in a separate subsection.
Commands and Responses ADD Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is required.
Commands and Responses ADD Command ZSPI-TKN-ERRLIST is a standard SPI error list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. Operational Note ZCOM-TKN-SUB is not valid for the ADD command.
Commands and Responses ADD LU ADD LU When the ADD command is applied to the object type ZCOM-OBJ-LU, the following additional tokens are involved. Tokens in Command Buffer ZAPC–TKN–SNA-NAME token–type ZSPI–TYP–STRING. ZAPC–TKN–SNAX-FILE-NAME token–type ZSPI–TYP–STRING. ZAPC–TKN–AUTO-START token–type ZSPI–TYP–BOOLEAN. ZAPC–TKN–SESS-LIM token–type ZSPI–TYP–INT. ZAPC–TKN–SNAX-MAX-RETRY-COUNT token–type ZSPI–TYP–INT. ZAPC–TKN–SNAX-RETRY-TIMER token–type ZSPI–TYP–INT2.
Commands and Responses ADD LU ZAPC–TKN–SNAX-RETRY-TIMER specifies the amount of time (in milliseconds) before SNAX/APC attempts to reopen the underlying SNAX file (which is the file specified in the SNAX-FILENAME token). Operational Notes If a small value is specified for the ZAPC-TKN-SNAX-RETRY-TIMER token and the underlying access method does not recover from its fault, SNAX/APC may enter a loop temporarily. The default value for ZAPC-TKN-SESS-LIM is 1.
Commands and Responses ADD PTNR-LU ADD PTNR-LU When the ADD command is applied to the object type ZCOM-OBJ-PTNR-LU, the following additional tokens are involved. Tokens in Command Buffer ZAPC–TKN–SNA-NAME token–type ZSPI–TYP–STRING. ZAPC–TKN–PARALLEL-SESS-LU token–type ZSPI–TYP–BOOLEAN. ZAPC–TKN–PERIPHERAL-NODE token–type ZSPI–TYP–BOOLEAN.
Commands and Responses ADD PTNR-MODE ADD PTNR-MODE When the ADD command is applied to the object type ZCOM-OBJ-PTNR-MODE, the following additional tokens are involved.
Commands and Responses ADD PTNR-MODE ZAPC–TKN–D-MIN-CONWINNERS-LIM specifies the number of sessions that the local LU is designated to be the contention winner. ZAPC–TKN–D-SESS-LIM specifies the default maximum number of sessions that the PTNR-MODE object can have. ZAPC–TKN–RCV-PACING-WINDOW specifies the size of the receive pacing window. ZAPC–TKN–SEND-PACING-WINDOW specifies the size of the send pacing window.
Commands and Responses ADD PTNR-MODE The PTNR-MODE object named SNASVCMG has the following default attribute settings: ZAPC-TKN-MODE-NAME = SNASVCMG ZAPC-TKN-D-SESS-LIM = 2 ZAPC-TKN-D-MAXINRUSIZE = MAXINRUSIZE value from process startup or 256 ZAPC-TKN-D-MAXOUTRUSIZE = MAXOUTRUSIZE value from process startup or 256 ZAPC-TKN-D-MIN-CONWINNERS-LIM = 1 ZAPC-D-MIN-CONLOSERS-LIM = 1 ZAPC-TKN-AUTO-ACTIVATE-LIM = 1 ZAPC-TKN-RCV-PACING-WINDOW = 7 ZAPC-TKN-SEND-PACING-WINDOW = 7 The only token values that can be alt
Commands and Responses ADD SESS ADD SESS When the ADD command is applied to the object type ZCOM-OBJ-SESS, no additional tokens are involved. Operational Notes The ZCOM-TKN-OBJNAME is a template with the following format: $apc-process.local-lu.partner-lu.partner-mode.* The asterisk (*) in the command syntax is required and refers to the session ID associated with each session.
Commands and Responses ADD TPN ADD TPN When the ADD command is applied to the object type ZCOM-OBJ-TPN, the following additional tokens are involved. Tokens in Command Buffer ZCMK–TKN–CHMAP-NAME ZAPC–TKN–CHAR-MAPPING-SUPP ZAPC–TKN–GENERAL-TP-RDY-SUPP ZAPC–TKN–REMOTE-ATTACH-DISP ZAPC–TKN–REMOTE-ATTACH-TIMER ZAPC–TKN–REPLY-DELAYED-ON-ERR ZAPC–TKN–SESS-CTRL-PRIV token–type token–type token–type token–type token–type token–type token–type ZSPI–TYP–CHAR50. ZSPI–TYP–BOOLEAN. ZSPI–TYP–BOOLEAN. ZSPI–TYP–ENUM.
Commands and Responses ADD TPN ZAPC–TKN–SESS-CTRL-PRIV specifies whether or not the TPN object is authorized to issue the ACTIVATE_SESSION and DEACTIVATE_SESSION session control verbs. Operational Notes The default value for these optional tokens are: ZAPC-TKN-CHAR-MAPPING-SUPP = FALSE ZAPC-TKN-CHMAP-NAME = character map name from process startup or APCRUN ZAPC-TKN-GENERAL-TP-RDY-SUPP = FALSE ZAPC-TKN-REMOTE-ATTACH-DISP = ZAPC-VAL-REMOTE-ATTACHQUEUE. ZAPC-TKN-REPLY-DELAYED-ON-ERR = FALSE.
Commands and Responses ALTER Command ALTER Command The ALTER command is used to change the attribute settings of the specified object. It is a sensitive command. In addition to the following tokens, which are valid for all object types, an object type can have additional tokens that are valid for that object type only. Such objectdependent tokens are described specifically for each object in a separate subsection.
Commands and Responses ALTER Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses ALTER Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses ALTER LU ALTER LU When the ALTER command is applied to the object type ZCOM-OBJ-LU, the following additional tokens are involved. Tokens in Command Buffer ZAPC-TKN-AUTO-START token-type ZSPI-TYP-BOOLEAN. ZAPC-TKN-SESS-LIM token-type ZSPI-TYP-INT. ZAPC-TKN-SNA-NAME token-type ZSPI-TYP-STRING. ZAPC-TKN-SNAX-FILE-NAME token-type ZSPI-TYP-STRING. ZAPC–TKN–SNAX-MAX-RETRY-COUNT token–type ZSPI–TYP–INT. ZAPC–TKN–SNAX-RETRY-TIMER token–type ZSPI–TYP–INT2.
Commands and Responses ALTER LU ZAPC–TKN–SNAX-MAX-RETRY-COUNT specifies the maximum number of times that SNAX/APC will attempt the open request. ZAPC–TKN–SNAX-RETRY-TIMER specifies specifies the amount of time (in milliseconds) before SNAX/APC attempts to reopen the underlying SNAX file (which is the file specified in the SNAX-FILE-NAME token. Operational Note The target LU can be altered only when it is in the STOPPED state.
Commands and Responses ALTER PROC ALTER PROC When the ALTER command is applied to the object type ZCOM-OBJ-PROC, the following additional tokens are involved. Tokens in Command Buffer ZCMK-MAP-ALTER def ZCMK-DDL-ALTER.
Commands and Responses ALTER PROC ZCMK–TKN–CHMAP-XFNAME specifies the name of the file that is accessed when character translation tables are needed. This file contains the collection of character map tables. ZCMK–TKN–EMS–XFNAME is included to change the primary EMS event collector. ZCMK–TKN–EMS–XFNAME-1 is included to change the first alternate EMS event collector. ZCMK–TKN–EMS–XFNAME-2 is included to change the second alternate EMS event collector.
Commands and Responses ALTER PTNR-LU ALTER PTNR-LU When the ALTER command is applied to the object type ZCOM-OBJ-PTNR-LU, the following additional tokens are involved. Tokens in Command Buffer ZAPC-TKN-PARALLEL-SESS-LU ZAPC-TKN-PERIPHERAL-NODE ZAPC-TKN-SNA-NAME token-type ZSPI-TYP-INT. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-STRING.
Commands and Responses ALTER PTNR-MODE ALTER PTNR-MODE When the ALTER command is applied to the object type ZCOM-OBJ-PTNR-MODE, the following additional tokens are involved. Tokens in Command Buffer ZAPC-TKN-AUTO-ACTIVATE-LIM token–type ZSPI-TYP-INT. ZAPC-TKN-D-MAXINRUSIZE token–type ZSPI-TYP-INT. ZAPC-TKN-D-MAXOUTRUSIZE token–type ZSPI-TYP-INT.!see ZAPC-TKN-D-MIN-CONLOSERS-LIM type ZSPI-TYP-INT.!see ZAPC-TKN-D-MIN-CONWINNERS-LIM type ZSPI-TYP-INT.!see ZAPC-TKN-D-SESS-LIM token–type ZSPI-TYP-INT.
Commands and Responses ALTER PTNR-MODE MODE object is in the STOPPED state. Otherwise, the token is not processed, and the command is rejected with the error ZAPC-ERR-TKN-INV-IN-SUMSTATE. ZAPC-TKN-D-MIN-CONWINNERS-LIM specifies the default number of sessions that the local LU is designated to be the contention winner. This token can be specified only when the specified PTNRMODE object is in the STOPPED state.
Commands and Responses ALTER PTNR-MODE ZAPC-TKN-RESPONSIBLE specifies the LU that is responsible for selecting and deactivating sessions, as a result of a change that decreases the session limit or the maximum number of contention-winner sessions for the source or target LU. This token can be specified only when the specified PTNR-MODE object is in the STARTED state. Otherwise, the command is rejected with the error ZAPC-ERR-TKN-INV-IN-SUMSTATE.
Commands and Responses ALTER TPN ALTER TPN When the ALTER command is applied to the object type ZCOM-OBJ-TPN, the following additional tokens are involved. Tokens in Command Buffer ZCMK–TKN–CHMAP-NAME ZAPC–TKN–CHAR-MAPPING-SUPP ZAPC-TKN-GENERAL-TP-RDY-SUPP ZAPC-TKN-REMOTE-ATTACH-DISP ZAPC-TKN-REMOTE-ATTACH-TIMER ZAPC–TKN–REPLY-DELAYED-ON-ERR ZAPC-TKN-SESS-CTRL-PRIV token–type token–type token–type token–type token–type token–type token–type ZSPI–TYP–CHAR50. ZSPI–TYP–BOOLEAN. ZSPI-TYP-BOOLEAN.
Commands and Responses ALTER TPN ZAPC-TKN-SESS-CTRL-PRIV specifies whether or not the TPN is authorized to issue the ACTIVATE-SESSION and DEACTIVATE- SESSION session control verbs. Operational Note The target TPN can be altered only when it is in the STOPPED state.
Commands and Responses DELETE Command DELETE Command The DELETE command is used to remove an object definition from the SNAX/APC process. It is a sensitive command.
Commands and Responses DELETE Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses DELETE Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses GETVERSION Command GETVERSION The GETVERSION command retrieves the version information about the SNAX/APC Command process. For more information, refer to the SPI Common Extensions Manual. This is a nonsensitive command.
Commands and Responses GETVERSION Command Tokens in Command Buffer ZSPI-TKN-MANAGER contains the name of the SNAX/APC process. This token is required for the GETVERSION command. ZCOM-TKN-CMD-TIMEOUT and ZCOM-TKN-GETVSN-SUPP-PARAMS are standard data communications tokens described in the SPI Common Extensions Manual. (ZSPI-TKN-)MAXRESP, CONTEXT, and ALLOW-TYPE are standard SPI tokens described in the SPI Programming Manual.
Commands and Responses GETVERSION Command ZSPI-TKN-SERVER-BANNER is a string that contains the SNAX/APC product name, number, and release date. Refer to the SPI Programming Manual for further information on this token. ZSPI-TKN-RETCODE indicates whether the command was successful and, if not, the reason for failure. ZSPI-TKN-ERRLIST is a standard SPI error list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST.
Commands and Responses INFO Command INFO Command The INFO command returns the current attribute settings of the specified object. It is a nonsensitive command. In addition to the following tokens, which are valid for all object types, an object type can have additional tokens that are valid for that object type only. Such objectdependent tokens are described specifically for each object in a separate subsection.
Commands and Responses INFO Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses INFO Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses INFO CONVERSATION INFO CONVERSATION When the INFO command is applied to the object type ZCOM-OBJ-CONVERSATION, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCMK-TKN-CHMAP-NAME ZCMK-TKN-CHMAP-NOTE ZAPC-TKN-CHAR-MAPPING-SUPP ZAPC-TKN-CONV-TYPE ZAPC-TKN-RESOURCE-ID ZAPC-TKN-SESS-ID ZAPC-TKN-SYNC-LEVEL ZSPI-TYP-CHAR50. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Commands and Responses INFO CONVERSATION ZAPC–TKN–RESOURCE-ID indicates, in hexadecimal digits, the identifier used by SNAX/APC to identify the conversation and its resources. This token does not exist if the conversation is still in the STARTING state, due to the receipt of an Attach request that is waiting for a TP-READY verb request. ZAPC–TKN–SESS-ID indicates the session on which this conversation is running. This token may not exist if the session has just been lost.
Commands and Responses INFO LU INFO LU When the INFO command is applied to the object type ZCOM-OBJ-LU, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-TKN-AUTO-START ZAPC-TKN-SESS-LIM ZAPC-TKN-SNA-NAME ZAPC-TKN-SNAX-FILE-NAME ZAPC–TKN–SNAX-MAX-RETRY-COUNT ZAPC–TKN–SNAX-RETRY-COUNT ZAPC–TKN–SNAX-RETRY-TIMER token–type token–type token–type token–type token–type token–type token–type ZSPI-TYP-BOOLEAN.!{} ZSPI-TYP-INT.
Commands and Responses INFO LU ZAPC–TKN–SNAX-RETRY-COUNT indicates the number of times that the local LU has attempted to open the underlying SNAX access method. This value is zero (0) when error recovery is not in progress. ZAPC–TKN–SNAX-RETRY-TIMER indicates the amount of time (in milliseconds) SNAX/APC waits before attempting to open the underlying SNAX file (which is the file specified in the SNAX-FILE-NAME token.
Commands and Responses INFO PROC INFO PROC When the INFO command is applied to the object type ZCOM-OBJ-PROC, the following additional tokens are involved. Tokens in Command Buffer ZSPI-TKN-ALLOW token-type ZSPI-TYP-ENUM !o Tokens in Response Buffer ZSPI-TKN-SEGLIST token-type ZCMK-TKN-SEGTYPE token-type ZCMK-TKN-CHFILE-MAPNAME type ZCMK-TKN-CHFILE-MAPNOTE type ZSPI-TKN-ENDLIST token-type ZCMK-MAP-INFO def ZCMK-DDL-INFO. 02 ZDEBUG-ON-ERR 02 ZBKUP-DEBUG 02 ZBKUP-CPU 02 ZBUF-SWAPVOL 02 ZMEM-SWAPVOOL end.
Commands and Responses INFO PROC Tokens in Command Buffer Refer to Section 4, “Common Definitions,” for a detailed description of these tokens. ZSPI-TKN-ALLOW is a standard SPI token described in the SPI Programming Manual. This is an enumerated token with several enumerated values. The only token value of interest to SNAX/APC is ZSPI-VAL-ALLOW-SEGMENTS.
Commands and Responses INFO PROC ZCMK-TKN-CHMAP-FILE-MOD identifies the modification timestamp of the character map translation file (if there is a character map file in use). ZCMK-TKN-CHMAP-NAME identifies the default character map used for data translation. This token is present only if the default character map is not the Tandem standard ASCII-toEBCDIC translation. ZCMK-TKN-CHMAP-NOTE conveys the notes associated with the character map translation table identified by the ZCMK-TKN-CHMAP-NAME token.
Commands and Responses INFO PROC ZCMK-TKN-PROG-FILE-MOD indicates the date upon which the program currently being executed as the SNAX/APC process was last modified. ZAPC-TKN-CONFIG-XFNAME indicates the name of the file that contains the configuration information. ZAPC-TKN-EMS-SUPPRESSION records which events are currently being suppressed by SNAX/APC. ZAPC-TKN-MAXINRUSIZE indicates the maximum number of bytes allowed in an incoming request/response unit (RU).
Commands and Responses INFO PTNR-LU INFO PTNR-LU When the INFO command is applied to the object type ZCOM-OBJ-PTNR-LU, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-TKN-LOCAL-SEC-ACCEPTANCE ZAPC-TKN-PARALLEL-SESS-LU ZAPC-TKN-PERIPHERAL-NODE ZAPC-TKN-REMOTE-SEC-ACCEPTANCE ZAPC-TKN-SNA-NAME token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. !{} ZSPI-TYP-BOOLEAN.!{} ZSPI-TYP-BOOLEAN.!{} ZSPI-TYP-ENUM.
Commands and Responses INFO PTNR-MODE INFO PTNR-MODE When the INFO command is applied to the object type ZCOM-OBJ-PTNR-MODE, the following additional tokens are involved.
Commands and Responses INFO PTNR-MODE ZAPC–TKN–AUTO-ACTIVATE-LIM indicates the number of contention-winner sessions that are activated automatically after the PTNR-MODE object is in the STARTED state. ZAPC–TKN–CUR-MAXINRUSIZE indicates the current maximum size of normal flow request units (RUs) that the local LU receives on the session. ZAPC–TKN–CUR-MAXOUTRUSIZE indicates the current maximum size of normal flow request units (RUs) that the local LU sends on the session.
Commands and Responses INFO PTNR-MODE ZAPC–TKN–D-SESS-LIM indicates the default maximum number of sessions that the PTNR-MODE object can have. The sum of the value returned in all D-SESS-LIM tokens for all PTNRMODE objects subordinate to a local LU must be less than or equal to the SESSLIM token value of the local LU. ZAPC–TKN–MIN-CONLOSERS-LIM indicates the minimum number of contention-loser sessions that the partner mode has.
Commands and Responses INFO SESS INFO SESS When the INFO command is applied to the object type ZCOM-OBJ-SESS, the following additional tokens are involved.
Commands and Responses INFO SESS ZAPC–TKN–CUR-RCV-PACING-CNT indicates the current number of request/response units (RUs) that SNAX/APC can receive from the partner LU before the partner LU must wait for a pacing response from SNAX/APC. This token might not exist if the session is not in the STARTED state. ZAPC–TKN–CUR-SEND-PACING-CNT indicates the current number of request/response units (RUs) that SNAX/APC can send to the partner LU before SNAX/APC must wait for a pacing response from the partner LU.
Commands and Responses INFO SESS ZAPC-TKN-SESS-TYPE indicates the role (primary or secondary) of the local LU in a particular session. ZAPC-TKN-SYNC-LEVEL indicates the synchronization level of an active conversation. This token only exists when a conversation is active.
Commands and Responses INFO TPI INFO TPI When the INFO command is applied to the object type ZCOM-OBJ-TPI, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-TKN-DISPATCHED-IND ZAPC-TKN-LOCAL-ATTACH-IND ZAPC-TKN-LOCAL-TP-PROC-NAME ZAPC-TKN-RESOURCE-ID ZAPC-TKN-TPI-ORIGIN token-type ZSPI-TYP-BOOLEAN. !{} token-type ZSPI-TYP-BOOLEAN. !{} token-type ZSPI-TYP-STRING. !{} type ZSPI-TYP-STRING.!see text token-type ZSPI-TYP-ENUM.
Commands and Responses INFO TPN INFO TPN When the INFO command is applied to the object type ZCOM-OBJ-TPN, the following additional tokens are involved.
Commands and Responses INFO TPN ZAPC–TKN–REMOTE-ATTACH-TIMER specifies the amount of time in milliseconds that SNAX/APC will wait for a remote TP-READY to arrive to satisfy the Attach. ZAPC–TKN–REPLY-DELAYED-ON-ERR indicates whether SNAX/APC should wait until the maximum number of retries is reached before replying with an error to a TP-READY verb that is waiting for the LU to start.
Commands and Responses LISTOBJECTS Command LISTOBJECTS The LISTOBJECTS command returns the object name if an object type other than Command ZCOM-OBJ-NULL is specified in the command. If the object type is ZCOM-OBJNULL, then the LISTOBJECTS command returns the process name and the object names of all subordinate objects. The LISTOBJECTS command is a nonsensitive command.
Commands and Responses LISTOBJECTS Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that contains the name of the SNAX/APC process. This token is required with the object type ZCOM-OBJ-NULL; it is optional with all other object types because the SNAX/APC process name is part of the object name. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.
Commands and Responses LISTOBJECTS Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses LISTOPENS Command LISTOPENS Command The LISTOPENS command returns a list of all file system OPEN calls that apply to the specified object. It is a nonsensitive command.
Commands and Responses LISTOPENS Command ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-MORE-DATA ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. !{} !{} !{} !... token-type token-type token-type token-type ZSPI-TYP-SSCTL. ZSPI-TYP-BOOLEAN. ZSPI-TYP-SSCTL. ZSPI-TYP-BYTESTRING.
Commands and Responses LISTOPENS Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCMK-MAP-LISTOP is a standard data communications extensible structured token that identifies an opener of a process. For this token to be returned in the response, the application must currently be opened.
Commands and Responses LISTOPENS Command ZSPI-TKN-ERRLIST is a standard SPI error list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZSPI-TKN-MORE-DATA provides support for segmented SPI responses, as described in the SPI Programming Manual. ZSPI-TKN-CONTEXT is the standard SPI context token discussed in the SPI Programming Manual.
Commands and Responses RESETSTATS Command RESETSTATS The RESETSTATS command returns the values of the statistics counters and then Command resets them. The RESETSTATS command is a sensitive command.
Commands and Responses RESETSTATS Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses RESETSTATS Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses RESETSTATS LU Command RESETSTATS LU When the RESETSTATS command is applied to the object type ZCOM-OBJ-LU, the following tokens are involved in addition to those described earlier for the generic RESETSTATS command. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-MAP-STATS-LU def ZAPC-DDL-STATS-LU. 02 ZRESET-TIME 02 ZSAMPLE-TIME 02 ZBIU-SENT-CNT 02 ZBIU-RCVD-CNT 02 ZDATA-SENT-CNT 02 ZDATA-RCVD-CNT end.
Commands and Responses RESETSTATS PROC Command RESETSTATS PROC When the RESETSTATS command is applied to the object type ZCOM-OBJ-PROC, the following tokens are involved in addition to those described earlier for the generic RESETSTATS command. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCMK-MAP-STATS-BUF def ZCMK-DDL-POOL-STATS. 02 ZCONFIG 02 ZCURR 02 ZMAX 02 ZRESET-TIME 02 ZSAMPLE-TIME 02 ZFAIL 02 ZCURR-FRAG 02 ZMAX-FRAG 02 ZGROWTH-CNT 02 ZGROWTH-TIME end.
Commands and Responses RESETSTATS PROC Command ZCMK-MAP-STATS-OPNR def ZCMK-DDL-STATS-OPNR. 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. ZCMK-MAP-STATS-RECV def ZCMK-DDL-STATS-RECV. 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.
Commands and Responses RESETSTATS PTNR-MODE Command RESETSTATS PTNR-MODE When the RESETSTATS command is applied to the object type ZCOM-OBJ-PTNRMODE, the following tokens are involved in addition to those described earlier for the generic RESETSTATS command. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-MAP-STATS-PTNR-MODE def ZAPC-DDL-STATS-PTNR-MODE.
Commands and Responses RESESTATS SESS Command RESETSTATS SESS When the RESETSTATS command is applied to the object type ZCOM-OBJ-SESS, the following tokens are involved in addition to those described earlier for the generic RESETSTATS command. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-MAP-STATS-SESSION def ZAPC-DDL-STATS-SESSION.
Commands and Responses START Command START Command The START command initiates the operation of an object. After this command is executed, the final summary state of the object is STARTED. The START command is a sensitive command.
Commands and Responses START Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses START Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses START Command Operational Notes The target object is placed in the STARTED state. SNAX/APC accepts a START command while the parent object of the target object is still in the STARTING state. In this case, the target object is first placed in the STARTING state and then placed in the STARTED state after its parent object is started. When a START LU command is executed, the ZAPC-TKN-SNAX-RETRY-COUNT token counter is reset. This counter keeps track of the retries of the local LU.
Commands and Responses STATISTICS Command STATISTICS Command The STATISTICS command returns the values of the statistics counters. It is a nonsensitive command. In addition to the following tokens, which are valid for all object types, an object type can have tokens that are valid for that object type only. Such object-dependent tokens are described specifically for each object in a separate subsection.
Commands and Responses STATISTICS Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses STATISTICS Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses STATISTICS LU Command STATISTICS LU When the STATISTICS command is applied to the object type ZCOM-OBJ-LU, the following tokens are involved in addition to those described earlier for the generic STATISTICS command. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-MAP-STATS-LU def ZAPC-DDL-STATS-LU. 02 ZRESET-TIME 02 ZSAMPLE-TIME 02 ZBIU-SENT-CNT 02 ZBIU-RCVD-CNT 02 ZDATA-SENT-CNT 02 ZDATA-RCVD-CNT end.
Commands and Responses STATISTICS PROC Command STATISTICS PROC When the STATISTICS command is applied to the object type ZCOM-OBJ-PROC, the following tokens are involved in addition to those described earlier for the generic STATISTICS command. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCMK-MAP-STATS-BUF def ZCMK-DDL-POOL-STATS. 02 ZCONFIG 02 ZCURR 02 ZMAX 02 ZRESET-TIME 02 ZSAMPLE-TIME 02 ZFAIL 02 ZCURR-FRAG 02 ZMAX-FRAG 02 ZGROWTH-CNT 02 ZGROWTH-TIME end.
Commands and Responses STATISTICS PROC Command ZCMK-MAP-STATS-OPNR def ZCMK-DDL-STATS-OPNR. 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. ZCMK-MAP-STATS-RECV def ZCMK-DDL-STATS-RECV. 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.
Commands and Responses STATISTICS PTNR-MODE Command STATISTICS PTNR-MODE When the STATISTICS command is applied to the object type ZCOM-OBJ-PTNRMODE, the following tokens are involved in addition to those described earlier for the generic STATISTICS command. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-MAP-STATS-PTNR-MODE def ZAPC-DDL-STATS-PTNR-MODE.
Commands and Responses STATISTICS SESS Command STATISTICS SESS When the STATISTICS command is applied to the object type ZCOM-OBJ-SESS, the following tokens are involved in addition to those described earlier for the generic STATISTICS command. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZAPC-MAP-STATS-SESSION def ZAPC-DDL-STATS-SESSION.
Commands and Responses STATUS Command STATUS Command The STATUS command returns current status information about the specified object. This command is a nonsensitive command. Additional tokens are returned in the response buffer according to which object the STATUS command is being applied to. The following descriptions of the STATUS command-object pairs describe these additional tokens.
Commands and Responses STATUS Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process, name so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses STATUS Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses STATUS CONVERSATION STATUS CONVERSATION When the STATUS command is applied to the object type ZCOM-OBJCONVERSATION, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCOM-TKN-OBJSTATE token-type ZSPI-TYP-ENUM. ZAPC-TKN-FSM-CONV token-type ZSPI-TYP-ENUM. ZAPC-TKN-RCVD-BYTES-NOT READ token-type ZSPI-TYP-INT.!see ZAPC-TKN-RUS-TO-BE-SENT token-type ZSPI-TYP-INT.!see ZAPC-TKN-SESS-ID token-type ZSPI-TYP-STRING.
Commands and Responses STATUS LU STATUS LU When the STATUS command is applied to the object type ZCOM-OBJ-LU, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCOM-TKN-OBJSTATE token-type ZSPI-TYP-ENUM. !{} ZAPC-TKN-ACTV-CONV-CNT token-type ZSPI-TYP-INT. !{} ZAPC-TKN-ACTV-SESS-CNT token-type ZSPI-TYP-INT. !{} ZAPC-TKN-SNAX-RETRY-COUNT token-type ZSPI-TYP-INT. !{} ZAPC-TKN-TRACE-STATE token-type ZSPI-TYP-ENUM.
Commands and Responses STATUS PROC STATUS PROC When the STATUS command is applied to the object type ZCOM-OBJ-PROC, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCOM-TKN-OBJSTATE ZCMK-TKN-BKUP-STATE ZCMK-TKN-TKOVR-COUNT ZAPC-TKN-CONFIG-STATE ZAPC-TKN-LOG-STATE ZAPC-TKN-TRACE-STATE ZAPC-TKN-TRACE-XFNAME token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TKN-INT.
Commands and Responses STATUS PROC ZAPC-TKN-TRACE-STATE indicates the current state of trace activity for the LU object. ZAPC-TKN-TRACE-XFNAME indicates the name of the file to which trace information is to be written.
Commands and Responses STATUS PTNR-LU STATUS PTNR-LU When the STATUS command is applied to the object type ZCOM-OBJ-PTNR-LU, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCOM-TKN-OBJSTATE token-type ZSPI-TYP-ENUM. !{} Tokens in Response Buffer ZCOM-TKN-OBJSTATE is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.
Commands and Responses STATUS PTNR-MODE STATUS PTNR-MODE When the STATUS command is applied to the object type ZCOM-OBJ-PTNR-MODE, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCOM-TKN-OBJSTATE ZAPC-TKN-ACTV-CONLOSERS-CNT ZAPC-TKN-ACTV-CONWINNERS-CNT ZAPC-TKN-ACTV-SESS-CNT ZAPC-TKN-TERMINATION-CNT token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-INT. ZSPI-TYP-INT. ZSPI-TYP-INT. ZSPI-TYP-INT.
Commands and Responses STATUS SESS STATUS SESS When the STATUS command is applied to the object type ZCOM-OBJ-SESS, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCOM-TKN-OBJSTATE token-type ZSPI-TYP-ENUM. !{} ZAPC-MAP-FSM-STATES token-type ZSPI-TYP-STRUCT. !{} def ZAPC-DDL-FSM-STATES.
Commands and Responses STATUS SESS Tokens in Response Buffer Refer to Section 4, “Common Definitions,” for more information on the following tokens. ZCOM-TKN-OBJSTATE is a standard data communications token that identifies the object name and the SNAX/APC process name. ZAPC-MAP-FSM-STATES is an extensible structured token that returns status information for the SESS object. The tokens tagged with an asterisk (*) may have the value of 0 if the session is not in the STARTED state.
Commands and Responses STATUS SESS ZAPC-TKN-RUS-TO-BE-SENT indicates the number of RUs waiting to be sent to the partner LU. If the session is not in the STARTED state, this token might not be returned. ZAPC-TKN-VERB-IN-PROGRESS indicates the verb that SNAX/APC is processing for the conversation on this session.
Commands and Responses STATUS TPI STATUS TPI When the STATUS command is applied to the object type ZCOM-OBJ-TPI, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCOM-TKN-OBJSTATE token-type ZSPI-TYP-ENUM. !{} Token in Response Buffer ZCOM-TKN-OBJSTATE is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses STATUS TPN STATUS TPN When the STATUS command is applied to the object type ZCOM-OBJ-TPN, the following additional tokens are involved. Tokens in Command Buffer (no additional tokens) Tokens in Response Buffer ZCOM-TKN-OBJSTATE ZSPI-TYP-ENUM. !{} Token in Response Buffer ZCOM-TKN-OBJSTATE is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses STOP Command STOP Command The STOP command terminates the activity of the specified or target objects. After this command is executed, the final summary state for the object is STOPPED. This command is a sensitive command. In addition to the following tokens, which are valid for all object types, an object type can have additional tokens that are valid for that object type only. Such objectdependent tokens are described specifically for each object in a separate subsection.
Commands and Responses STOP Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses STOP Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name. This token is always present in the response buffer.
Commands and Responses STOP PTNR-MODE STOP PTNR-MODE When the STOP command is applied to the object type ZCOM-OBJ-PTNR-MODE, the following additional tokens are involved. Tokens in Command Buffer ZCOM-TKN-CMD-POWER ZAPC-TKN-DRAIN-SOURCE ZAPC-TKN-DRAIN-TARGET ZAPC-TKN-RESPONSIBLE token-type ZSPI-TYP-ENUM. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-ENUM.
Commands and Responses STOP SESS STOP SESS When the STOP command is applied to the object type ZCOM-OBJ-SESS, the following additional tokens are involved. Tokens in Command Buffer ZCOM-TKN-CMD-POWER token-type ZSPI-TYP-ENUM. Tokens in Response Buffer (no additional tokens) Tokens in Response Buffer ZCOM–TKN–CMD-POWER modifies the STOP command. See the SPI Common Extensions Manual for more information about the possible values for this token.
Commands and Responses TRACE Command TRACE Command The TRACE command defines and controls the trace environment for a specified PROC or LU object. It is a sensitive command. For guidance on using this command and formatting the trace output, see the section entitled “Trace Facilities” in the SNAX/APC Planning and Configuration Manual.
Commands and Responses TRACE Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI token that is optional for SNAX/APC. In other subsystems, this token contains the process name; however, for SNAX/APC, object names include the SNAX/APC process name, so this token is not necessary. ZCOM-TKN-OBJNAME is a standard data communications token that identifies the object name and the SNAX/APC process name. SNAX/APC object names have the format $snax/apc-process-name.object-name.
Commands and Responses TRACE Command ZCOM-TKN-SEL-SUMSTATE indicates that the command applies only to objects in a specific summary state. Refer to Section 3, “Elements of SPI Messages for SNAX/APC,” for further information on summary states. (ZSPI-TKN-)MAXRESP, CONTEXT, and ALLOW-TYPE are standard SPI tokens described in the SPI Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the SPI Programming Manual.
Commands and Responses TRACE Command (This page left intentionally blank) 5–114 111813 Tandem Computers Incorporated
6 Event Management The SNAX/APC subsystem provides information about events that occur in the subsystem by issuing event messages. A management application can obtain these event messages by opening an Event Management Service (EMS) distributor process and requesting the messages. The application can also specify that a filter be applied to select certain event messages.
Event Management Subsystem Processes That Report Events 6. Saveabend file—if SNAX/APC abends or hangs, it is important to get the SAVE file of the SNAX/APC server. To accomplish this, when SNAX/APC drops into Inspect, or if it hangs and you invoke Inspect via the DEBUG command, issue the SAVE command. 7.
Event Management Subsystem Processes That Report Events Table 6-1.
Event Management Subsystem Processes That Report Events Table 6-1.
Event Management SNAX/APC Events SNAX/APC Event Summary SNAX/APC generates event messages for events that involve objects under its control. Table 6–2 lists a summary of SNAX/APC event messages. Table 6–2. SNAX/APC Event Messages (Page 1 of 2) Event Number Symbolic Name (ZAPC–EVT–) Description 1 2 3 4 5 6 7 8 9 10 FSM–ERR INV–INIT INV–CONFIG Retired message Retired message INV–OP Retired message Retired message Retired message BID–REJECT An unexpected FSM error. An invalid SNAX/APC startup parameter.
Event Management SNAX/APC Events Table 6–2. SNAX/APC Event Messages (Page 2 of 2) 6–6 Event Number Symbolic Name (ZAPC–EVT–) Description 29 30 CNOS–CMD–REJECTED NEG–RSP–RCVD 31 NEG–RSP–SENT 32 RCVD–RU–XCEED–MAXSIZE 33 34 35 SWITCHING-DB SWITCHING-DB-DONE NO-CFG-FILE 36 37 SWITCHING-DB-FAILED CFG-DB-CONVERTED The remote CNOS command has been rejected. A negative response was received on an SNA session. A negative response has been sent on an SNA session.
Event Management SNAX/APC Events The SNAX/APC events listed in Table 6-2 can also be divided into categories according to the type of event. The following lists the SNAX/APC events according to these categories.
Event Management Potentially Critical Events Potentially Critical Events reported by the SNAX/APC subsystem are divided into two classes: Events potentially critical events and noncritical events. Potentially critical events are those for which the consequences could be serious, such as the loss of a session or the termination of the SNAX/APC process.
Event Management Event Message Descriptions Event Message On the following pages, each event message that can be issued by the SNAX/APC Descriptions subsystem is described in detail. Within each event message description, there is a box that lists all the tokens that can appear in the event message. An application can filter on any token. These tokens are divided into four categories: Unconditional tokens, which are always present in the event message.
Event Management 1: ZAPC-EVT-FSM-ERR 1: ZAPC–EVT–FSM–ERR SNAX/APC encountered an unexpected finite state machine (FSM) error. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-FSM-NAME ZAPC-TKN-STATE ZAPC-TKN-FSM-EVT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-INT. ZSPI-TYP-INT.
Event Management 1: ZAPC-EVT-FSM-ERR ZAPC-TKN-FSM-NAME identifies the name of the finite state machine (FSM). This enumerated token can have one of the following literal values: ZAPC-VAL-FSM-NAME-BIS-BDR is the finite state machine FSM_BIS_BIDDER, which represents the status of a bidder half-session. ZAPC-VAL-FSM-NAME-BIS-FSP is the finite state machine FSM_BIS_FSP, which represents the status of a firstspeaker half-session.
Event Management 1: ZAPC-EVT-FSM-ERR ZAPC-VAL-FSM-NAME-QRI-CHAIN-R is the finite state machine FSM_QRI_CHAIN_RCV_FMP19, which enforces the setting of the Queued Response Indicator (QRI) in the request/response header (RH). ZAPC-VAL-FSM-NAME-RCB-STS-BDR is the finite state machine FSM_RCB_STATUS_BIDDER, which represents the status of a conversation resource associated with a bidder half-session.
Event Management 1: ZAPC-EVT-FSM-ERR Cause SNAX/APC encountered an unexpected finite state machine (FSM) error. Effect The process continues, but some sessions may encounter unpredictable difficulties. Recovery You need to seek additional help. Follow the procedures described at the beginning of this section for collecting relevant information and contacting the appropriate support personnel.
Event Management 2: ZAPC-EVT-INV-INIT 2: ZAPC–EVT–INV–INIT The SNAX/APC startup parameters contained an invalid PARAM. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-INIT-ERR token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. Conditional Tokens ZAPC-TKN-FILE-ERR ZAPC-TKN-PARAM token-type ZSPI-TYP-INIT. token-type ZSPI-TYP-STRING 20.
Event Management 2: ZAPC-EVT-INV-INIT ZAPC-TKN-INIT-ERR identifies the reason for the initialization failure. This is an enumerated token. Its possible values are: ZAPC-VAL-INIT-ERR-PARAM indicates that the error was caused by an invalid parameter. ZAPC-VAL-INIT-ERR-VALUE indicates that the error was caused by an invalid parameter value. Conditional Tokens ZAPC-TKN-PARAM-ERR identifies the name of a parameter that is invalid. ZAPC-TKN-FILE-ERR identifies a file-system error.
Event Management 3: ZAPC-EVT-INV-CONFIG 3: ZAPC–EVT–INV–CONFIG This indicates an invalid configuration file. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-CONFIG-ERR token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. Conditional Tokens ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-INIT.
Event Management 3: ZAPC-EVT-INV-CONFIG ZAPC-TKN-CONFIG-ERR identifies the fault in an invalid configuration file. This is an enumerated token. Possible values are: ZAPC-VAL-CONFIG-ERR-BAD-FILE indicates that the error was caused by an invalid configuration file. ZAPC-VAL-CONFIG-ERR-BAD-CODE indicates that the error was caused by an invalid configuration file code. ZAPC-VAL-CONFIG-ERR-BAD-VSN indicates that the error was caused by a configuration version mismatch.
Event Management 6: ZAPC-EVT-INV-OP 6: ZAPC–EVT–INV–OP An operational failure has been detected by SNAX/APC. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Abending - SNAX/APC internal error Message Parameter Descriptions <1> equals ZCOM–TKN–SUBJ–PROC.
Event Management 10: ZAPC-EVT-BID-REJECT 10: ZAPC–EVT–BID–REJECT A request from a remote LU for a conversation with a local LU was rejected because SNAX/APC could not obtain the resources. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING.
Event Management 11: ZAPC-EVT-BKP-TAKEOVER 11: ZAPC–EVT–BKP–TAKEOVER The process is taken over by the backup CPU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Process takeover by backup Message Parameter Descriptions <1> equals ZCOM–TKN–SUBJ–PROC. Unconditional Tokens ZEMS-TKN-EVENTNUMBER is the event number.
Event Management 12: ZAPC-EVT-DEALLOCATE-ERR 12: ZAPC–EVT–DEALLOCATE–ERR SNAX/APC was not able to deallocate an extended data segment used for tracing. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Deallocate segment error Message Parameter Descriptions <1> equals ZCOM–TKN–SUBJ–PROC.
Event Management 13: ZAPC-EVT-INIT-INFO 13: ZAPC–EVT–INIT–INFO This event provides initialization information. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-INIT-INFO token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. Event-Message Text <1>: <2> Message Parameter Descriptions <1> equals ZCOM–TKN–SUBJ–PROC. <2> equals ZAPC–TKN–INIT–INFO.
Event Management 13: ZAPC-EVT-INIT-INFO ZAPC-TKN-INIT-INFO provides SNAX/APC initialization status information. This enumerated token can have one of the following literal values: ZAPC-VAL-INIT-INFO-INIT-BEG indicates that SNAX/APC initialization has started. ZAPC-VAL-INIT-INFO-INIT-END indicates that SNAX/APC initialization has completed. ZAPC-VAL-INIT-INFO-RE-INIT-END indicates that SNAX/APC reinitialization has completed. Cause SNAX/APC started or ended initialization or reinitialization.
Event Management 14: ZAPC-EVT-LU-DEVINFO-ERR 14: ZAPC–EVT–LU–DEVINFO–ERR A device type inquiry for an LU has failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INIT.
Event Management 14: ZAPC-EVT-LU-DEVINFO-ERR Cause A device type inquiry for an LU failed. Effect The process continues; however, the LU does not start. Recovery Use the file-system error returned in this message to identify why the error occurred, and take appropriate actions. Issue a START LU command to verify the correction.
Event Management 15: ZAPC-EVT-LU-CONNECT-ERR 15: ZAPC–EVT–LU–CONNECT–ERR A connect for an LU failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INIT.
Event Management 15: ZAPC-EVT-LU-CONNECT-ERR Cause A connect for an LU failed. (A connect is a control-11 call to the underlying access method for the LU.) Effect The process continues; however, the LU does not start. Recovery Use the file-system error returned in this message to identify why the error occurred, and take appropriate actions. Issue a START LU command to verify the correction.
Event Management 16: ZAPC-EVT-LU-OPEN-ERR 16: ZAPC–EVT–LU–OPEN–ERR SNAX/APC was unable to open the underlying access method. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INIT.
Event Management 16: ZAPC-EVT-LU-OPEN-ERR Cause SNAX/APC was unable to open the underlying access method. Effect The process continues; however, the LU does not start. Recovery Use the file-system error returned in this message to identify why the error occurred, and take appropriate actions. Issue a START LU command to verify the correction.
Event Management 17: ZAPC-EVT-INV-DEV-TYPE 17: ZAPC–EVT–INV–DEV–TYPE The device type of an LU is invalid for the underlying access method. Either the LU is neither a SNAX/XF LU nor a SNAX/CDF APPL object, or the LU is a parallel-session LU and the access method is not SNAX/APN. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
Event Management 17: ZAPC-EVT-INV-DEV-TYPE Cause An LU device type is invalid. Effect The process continues, but this LU cannot be used. Recovery Specify a correct SNAX file name for the LU and restart the LU. The LU device type must be one of the supported access methods, such as a SNAX/XF LU or a SNAX/CDF APPL object. If the LU is a parallel-session LU, the access method must be SNAX/APN.
Event Management 20: ZAPC-EVT-SNAX-FILE-ERR 20: ZAPC–EVT–SNAX–FILE–ERR SNAX/APC received a file-system error from the underlying access method. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-FILE-ERR token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-INIT.
Event Management 20: ZAPC-EVT-SNAX-FILE-ERR Cause SNAX/APC received a file-system error from the underlying access method. Effect The process continues, but all of the sessions on this LU will be lost and the conversations using theses sessions will be deallocated. A reopen will be issued. If the open fails, the LU and its subordinates will go into the STARTING state. Recovery Use the file-system error returned in this event message to identify why the error occurred, and take appropriate actions.
Event Management 21: ZAPC-EVT-TPREADY-REJECT 21: ZAPC–EVT–TPREADY–REJECT SNAX/APC could not complete a TP-READY request because it could not obtain the necessary resources. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING.
Event Management 21: ZAPC-EVT-TPREADY-REJECT Cause SNAX/APC could not complete a TP-READY request because it could not obtain the necessary resources. The maximum number of conversations on the SNAX/APC process has been reached. Effect The process continues, and the TP-READY request is rejected. Recovery The transaction program should retry the TP-READY request at a later time. If the problem persists, try running an extra SNAX/APC process.
Event Management 22: ZAPC-EVT-UNXP-PAC-RQ 22: ZAPC–EVT–UNXP–PAC–RQ A pacing request was received before SNAX/APC had responded to the last pacing request, or an unexpected pacing request was received. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Event Management 22: ZAPC-EVT-UNXP-PAC-RQ Cause A pacing request was received before SNAX/APC had responded to the last pacing request, or an unexpected pacing request was received. Effect None; the process continues. Recovery Informative message only; no action is required.
Event Management 23: ZAPC-EVT-UNKNOWN-IPC 23: ZAPC–EVT–UNKNOWN–IPC SNAX/APC received an unknown IPC message for processing. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Unknown message received Message Parameter Descriptions <1> equals ZCOM–TKN–SUBJ–PROC.
Event Management 24: ZAPC-EVT-RCVD-RMT-CNOS-CMD 24: ZAPC–EVT–RCVD–RMT–CNOS–CMD A remote CNOS command was received. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Received remote CNOS command Message Parameter Descriptions <1> equals ZCOM–TKN–SUBJ–PTNR–LU.
Event Management 25: ZAPC-EVT-CNOS-CONV-FAIL 25: ZAPC–EVT–CNOS–CONV–FAIL The CNOS conversation failed at the specified conversation verb. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU ZAPC-TKN-CONV-FAILED-AT ZAPC-TKN-RC-RETN ZAPC-TKN-RC-RETN-DETL token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-INT. ZSPI-TYP-INT.
Event Management 25: ZAPC-EVT-CNOS-CONV-FAIL ZAPC-TKN-CONV-FAILED-AT identifies the conversation verb at which the CNOS conversation failed. This enumerated token can have one of the following literal values: ZAPC-VAL-CONV-FAILED-AT-RAW is returned if the CNOS conversation failed at the Receive_and_Wait verb. ZAPC-VAL-CONV-FAILED-AT-SD is returned if the CNOS conversation failed at the Send_Data verb. ZAPC-TKN-RC-RETN identifies the REP–RETURN–CODE of the failed CNOS conversation verb.
Event Management 26: ZAPC-EVT-CNOS-CMD-RACE 26: ZAPC–EVT–CNOS–CMD–RACE A CNOS command race was detected. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event–Message Text <1>: CNOS command race occurred Message Parameter Descriptions <1> equals ZCOM–TKN–SUBJ–PTNR–LU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER is the event number.
Event Management 27: ZAPC-EVT-SESS-LIMIT-CHANGED 27: ZAPC–EVT–SESS–LIMIT–CHANGED The session limits of the specified PTNR–MODE object were changed by either the local or the remote LU. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-MODE ZAPC-TKN-OPERATOR token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM.
Event Management 27: ZAPC-EVT-SESS-LIMIT-CHANGED ZAPC-TKN-OPERATOR identifies if the operator at the local or remote LU initiated the change session limit operation. This enumerated token can have one of the following literal values: ZAPC-VAL-OPERATOR-LOCAL-LU specifies that the command was initiated by the local LU. ZAPC-VAL-OPERATOR-REMOTE-LU specifies that the command was initiated by the partner LU.
Event Management 28: ZAPC-EVT-CNOS-CMD-NEGOTIATED 28: ZAPC–EVT–CNOS–CMD–NEGOTIATED The remote CNOS command is in effect, and the session limits have been negotiated. The CNOS reply was returned to the remote LU with the negotiated session limits. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING.
Event Management 29: ZAPC-EVT-CNOS-CMD-REJECTED 29: ZAPC–EVT–CNOS–CMD–REJECTED The remote CNOS command was rejected due to the specified reason. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PTNR-LU ZAPC-TKN-REASON token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM.
Event Management 29: ZAPC-EVT-CNOS-CMD-REJECTED ZAPC-TKN-REASON identifies the reason the CNOS command was rejected. This enumerated token can have one of the following literal values: ZAPC-VAL-REASON-UNKWN-MODENAME specifies that the partner mode name is not recognized. ZAPC-VAL-REASON-ZERO-SESS-LIM specifies that the session limit is set to 0. Cause The remote CNOS command was rejected for the specified reason. Effect The remote CNOS command is rejected. A reply is returned with the specified reason.
Event Management 30: ZAPC-EVT-NEG-RSP-RCVD 30: ZAPC–EVT–NEG–RSP–RCVD The event indicates the receipt of a negative response on an SNA session.
Event Management 30: ZAPC-EVT-NEG-RSP-RCVD ZCMK-TKN-SNAERR is the first two bytes of sense data. In the message text, argument <2> is shown in hexadecimal, while argument <4> shows an English language explanation of the message for this token. ZAPC-TKN-SENSE2 is the second two bytes of sense data. ZAPC-TKN-MUT is the SNA response RU. Cause A negative response has been received on an SNA session. Effect Inspect the sense data to determine the effect of the negative response.
Event Management 31: ZAPC-EVT-NEG-RSP-SENT 31: ZAPC–EVT–NEG–RSP–SENT This event indicates that a negative response has been sent on an SNA session. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-SESS ZCMK-TKN-SNAERR ZAPC-TKN-SENSE2 ZAPC-TKN-MUT token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
Event Management 31: ZAPC-EVT-NEG-RSP-SENT ZCMK-TKN-SNAERR is the first two bytes of sense data. In the message text, argument <2> is shown in hexadecimal, while argument <4> shows an English language explanation of the message for this token. As much of the session name is supplied as is known at the time the response is sent. For example, if SNAX/APC receives a BIND request, it may reject it before it has located the partner LU (or because it does not recognize the partner LU).
Event Management 32: ZAPC-EVT-RCVD-RU-XCEED-MAXSIZE 32: ZAPC–EVT–RCVD–RU–XCEED–MAXSIZE This event indicates that SNAX/APC received an RU that exceeds the maximum RU size. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-LU-NAME ZAPC-TKN-SESS-ID token-type token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Event Management 32: ZAPC-EVT-RCVD-RU-XCEED-MAXSIZE Cause SNAX/APC received an RU that exceeds the maximum RU size. Effect Upon receipt of an oversized RU, SNAX/APC brings down the session. Any conversation using this session is therefore terminated. Recovery The maximum RU size is decided at the session establishment. No RU should be sent with a size greater than this value. Verify the current RU size setting in the remote LU.
Event Management 33: ZAPC-EVT-SWITCHING-DB 33: ZAPC–EVT–SWITCHING-DB The configuration file is currently being switched to the named file. If the file is temporary, only the name of the VOLUME can be displayed at this time. The name of the new file will be indicated in the event generated at the successful completion of the switch (ZAPC-EVT-SWITCHING-DB-DONE).
Event Management 33: ZAPC-EVT-SWITCHING-DB Cause Either an unexpected file error on the original configuration file or a SPI (or SCF) ALTER PROC command has occurred which initiated a configuration file switch. Effect This is an informational event only; the process continues. Recovery You should wait for the event that follows to determine the success or failure of the switch.
Event Management 34: ZAPC-EVT-SWITCHING-DB-DONE 34: ZAPC–EVT–SWITCHING-DB-DONE The configuration file switching process is complete. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-CONFIG-FILE token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Event Management 34: ZAPC-EVT-SWITCHING-DB-DONE Cause A successful configuration file database switch to the named configuration file has occurred. Effect This is an informational event only; the process continues. Recovery No recovery action is required.
Event Management 35: ZAPC-EVT-NO-CFG-FILE 35: ZAPC–EVT–NO-CFG-FILE A backup takeover occurred when the configuration database file was unuseable or in the process of being switched to a new file. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING.
Event Management 35: ZAPC-EVT-NO-CFG-FILE Cause A backup takeover occurred when the configuration file could not be used because a configuration file switch was in progress. Effect The process terminates abnormally. Recovery If the switch occurred because the file became inaccessible, correct the disk failure before starting the SNAX/APC process. If the switch was due to an ALTER PROC command, the SNAX/APC process can be started using the original configuration file.
Event Management 36: ZAPC-EVT-SWITCHING-DB-FAILED 36: ZAPC–EVT–SWITCHING-DB-FAILED The switch to a new configuration file has failed. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. Event-Message Text <1>: Switching configuration database - FAILED Message Parameter Descriptions <1>equals ZCOM–TKN–SUBJ–PROC.
Event Management 36: ZAPC-EVT-SWITCHING-DB-FAILED Cause A configuration database file switch has failed. Effect If the switch failed because the old configuration database file was inaccessible, SNAX/APC has no current database file. SNAX/APC will continue to perform conversation related activities and to honor CNOS requests from the remote LU. However, SNAX/APC will not honor any sensitive SPI (or SCF) commands. Any such commands will be rejected with the error ZAPC-ERR-CONFIG-IS-BAD.
Event Management 37: ZAPC-EVT-CFG-DB-CONVERTED 37: ZAPC–EVT–CFG-DB-CONVERTED After a warm start, SNAX/APC automatically converts the configuration database specified by the CONFIG attribute value to the current level. Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-PROC ZAPC-TKN-CONFIG-FILE token-type token-type token-type token-type token-type ZSPI-TYP-ENUM. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Event Management 37: ZAPC-EVT-CFG-DB-CONVERTED Cause A warm start has occurred and SNAX/APC has automatically converted the configuration file database to the current level. Effect The original configuration database file is renamed to \node.$volume.subvolume.ZZCFnnnn, where nnnn is a unique number derived from the timestamp and the node, volume, and subvolume values are the same as the node, volume and subvolume names for the new configuration file. Recovery This is an informational message.
Event Management 37: ZAPC-EVT-CFG-DB-CONVERTED (This page left intentionally blank) 6–64 111813 Tandem Computers Incorporated
Appendix A Error Numbers and Error Lists This appendix presents all the error numbers provided by the SNAX/APC subsystem (that is, the values whose symbolic names begin with ZAPC-ERR-) and describes the error lists associated with these error numbers. These error numbers can occur as values of the return token, ZSPI-TKN-RETCODE, and as part of the value of the error token, ZSPI-TKN-ERROR.
Error Numbers and Error Lists Before You Report a Problem 5. EMS logs—include the event (EMS) logs that were active when the problem occurred. 6. Saveabend file—if SNAX/APC abends or hangs, it is important to get the SAVE file of the SNAX/APC server. To accomplish this, when SNAX/APC drops into Inspect, or if it hangs and you invoke Inspect using the DEBUG command, issue the SAVE command. 7.
Error Numbers and Error Lists Notation Used Common Errors: Error messages with the prefix ZCOM- or ZCMK- are common to more than one -00001 Through -00999 Tandem product. The ZCOM- errors have numbers ranging from -00001 through and -32nnn Series -00999. Detailed information on both the ZCOM- and ZCMK- error numbers, including errors that do not involve the SNAX/APC subsystem, can be found in the SPI Common Extensions Manual.
Error Numbers and Error Lists SNAX/APC Errors SNAX/APC Errors SNAX/APC may return the following SNAX/APC errors: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34: 35: 36: 37: 38: 39: 40: 41: 42: ZAPC–ERR–ACTV–FAIL–NO-RETRY ZAPC-ERR-ACTV-FAIL-RETRY ZAPC-ERR-ALLOC-ERR-NO-RETRY ZAPC-ERR-ALLOC-ERR-RETRY ZAPC-ERR-ALLOC-ERR-PGM-NOT-AVL ZAPC-ERR-CMD-FORCED ZAPC-ERR-CMD-INV-DEFT-OBJ ZAPC-ERR-CMD-INV-NOT-PS-LU ZAPC-ERR-CMD-NEGOTIATED ZAPC
Error Numbers and Error Lists 1: ZAPC-ERR-ACTV-FAIL-NO-RETRY 1: ZAPC-ERR-ACTV-FAIL-NO-RETRY The ADD SESS command was rejected. Do not retry until the condition is corrected. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token-type token-type token-type token-type token-type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 2: ZAPC-ERR-ACTV-FAIL-RETRY 2: ZAPC-ERR-ACTV-FAIL-RETRY The ADD SESSION command was rejected due to an error. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 3: ZAPC-ERR-ALLOC-ERR-NO-RETRY 3: ZAPC-ERR-ALLOC-ERR-NO-RETRY The operation failed. Do not retry until the condition is corrected. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 4: ZAPC-ERR-ALLOC-ERR-RETRY 4: ZAPC-ERR-ALLOC-ERR-RETRY The operation failed: retry the operation. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 5: ZAPC-ERR-ALLOC-ERR-PGM-NOT-AVL 5: ZAPC-ERR-ALLOC-ERR-PGM-NOT-AVL Allocation error: the remote CNOS service transaction program is not available. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 6: ZAPC-ERR-CMD-FORCED 6: ZAPC-ERR-CMD-FORCED The CNOS command was processed as a FORCED option. No error list is generated. Cause An error condition prevented the successful exchange of the CNOS request and reply, and the CNOS conversation either failed or was rejected by the partner LU. The selection of the FORCE option forced the local LU to reset its partner-mode session limit.
Error Numbers and Error Lists 7: ZAPC-ERR-CMD-INV-DEFT-OBJ 7: ZAPC-ERR-CMD-INV-DEFT-OBJ This command cannot act upon a default object. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 8: ZAPC-ERR-CMD-INV-NOT-PS-LU 8: ZAPC-ERR-CMD-INV-NOT-PS-LU This command cannot act upon a single-session LU while that LU is in the STARTED state. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 9: ZAPC-ERR-CMD-NEGOTIATED 9: ZAPC-ERR-CMD-NEGOTIATED The CNOS command was processed as negotiated. No error list is generated. Cause The CNOS command was processed as negotiated by the partner LU. The equivalent RETURN_CODE value, as defined in the IBM Transaction Programmer's Reference Manual for LU 6.2, is OK –AS_NEGOTIATED. One of the START, ALTER, STOP, or ABORT PTNR-MODE commands has been processed successfully with parameters negotiated by the partner LU.
Error Numbers and Error Lists 10: ZAPC-ERR-CMD-RACE-REJECT 10: ZAPC-ERR-CMD-RACE-REJECT The command was rejected because a command race occurred. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 11: ZAPC-ERR-CONFIG-IN-PROGRESS 11: ZAPC-ERR-CONFIG-IN-PROGRESS SNAX/APC is still being configured: sensitive commands cannot be processed. No error list is generated. Cause The SNAX/APC process was still in the initial configuration phase when a sensitive command was issued. Effect The sensitive command cannot be processed. Recovery Use the STATUS PROCESS command to retrieve the configuration state. Retry the request after SNAX/APC has been configured.
Error Numbers and Error Lists 12: ZAPC-ERR-DEFT-OBJNAME 12: ZAPC-ERR-DEFT-OBJNAME An error was caused by the use of a reserved object name. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 13: ZAPC-ERR-DRAIN-S-NO-IN-EFFECT 13: ZAPC-ERR-DRAIN-S-NO-IN-EFFECT Drain-Source NO and Session-Limit 0 are in effect. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 14: ZAPC-ERR-DUP-MODENAME 14: ZAPC-ERR-DUP-MODENAME A duplicate MODENAME value was specified. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 15: ZAPC-ERR-INV-DEV-TYPE 15: ZAPC-ERR-INV-DEV-TYPE Either an unknown device type was specified, or the LU is a parallel-session LU but the access method is not SNAX/APN. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL.
Error Numbers and Error Lists 16: ZAPC-ERR-LU-SESS-LIM-XCEEDED 16: ZAPC-ERR-LU-SESS-LIM-XCEEDED The LU session limit was exceeded. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 17: ZAPC-ERR-MODENAME-UNRECOGNIZED 17: ZAPC-ERR-MODENAME-UNRECOGNIZED The specified MODENAME value was unrecognized ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 18: ZAPC-ERR-OBJ-CANNOT-DEL 18: ZAPC-ERR-OBJ-CANNOT-DEL The default object cannot be deleted. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 19: ZAPC-ERR-OTH-MODES-NOT-STOPPED 19: ZAPC-ERR-OTH-MODES-NOT-STOPPED The related PTNR-MODE objects are not in the STOPPED state. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 20: ZAPC-ERR-PARAM-ERR 20: ZAPC-ERR-PARAM-ERR A parameter error occurred. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 21: ZAPC-ERR-REQ-XCEEDS-MAX-LIM 21: ZAPC-ERR-REQ-XCEEDS-MAX-LIM The request exceeds the maximum allowed session limit. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 22: ZAPC-ERR-RES-FAIL-NO-RETRY 22: ZAPC-ERR-RES-FAIL-NO-RETRY A resource failure occurred. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 22: ZAPC-ERR-RES-FAIL-NO-RETRY Effect The CNOS-related command does not execute successfully. Recovery The request should not be retried until the cause of the resource failure is cleared. Check the EMS event log for help in determining the cause of the resource failure.
Error Numbers and Error Lists 23: ZAPC-ERR-SESS-LIM-CLOSED 23: ZAPC-ERR-SESS-LIM-CLOSED The session limit cannot be raised above 0. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 24: ZAPC-ERR-SESS-LIM-NOT-ZERO 24: ZAPC-ERR-SESS-LIM-NOT-ZERO The session limit is already greater than 0. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 25: ZAPC-ERR-SESS-LIM-ZERO 25: ZAPC-ERR-SESS-LIM-ZERO The session limit has not been initialized, and it is still set to 0. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 26: ZAPC-ERR-SNASVCMG-NOT-STARTED 26: ZAPC-ERR-SNASVCMG-NOT-STARTED The default PTNR-MODE object named SNASVCMG was not started. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 27: ZAPC-ERR-SNASVCMG-PARAM-ERR 27: ZAPC-ERR-SNASVCMG-PARAM-ERR Internal Error: SNASVCMG parameter error. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 28: ZAPC-ERR-SUB-NOT-DELETED 28: ZAPC-ERR-SUB-NOT-DELETED Subordinate objects were not deleted. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 29: ZAPC-ERR-SUB-NOT-STOPPED 29: ZAPC-ERR-SUB-NOT-STOPPED Subordinate objects were not stopped. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 30: ZAPC-ERR-TOO-MANY-SUB-OBJ 30: ZAPC-ERR-TOO-MANY-SUB-OBJ Too many subordinate objects have been specified for a single-session LU. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 31: ZAPC-ERR-TRACE-ALREADY-ACTIVE 31: ZAPC-ERR-TRACE-ALREADY-ACTIVE Tracing is already in progress. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 32: ZAPC-ERR-TRACE-NOT-STOPPED 32: ZAPC-ERR-TRACE-NOT-STOPPED Tracing was not stopped. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 33: ZAPC-ERR-TRACE-NOT-TRACING 33: ZAPC-ERR-TRACE-NOT-TRACING Tracing has not been started. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 34: ZAPC-ERR-TRACE-SHUTDOWN-ERROR 34: ZAPC-ERR-TRACE-SHUTDOWN-ERROR Tracing shutdown error. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 35: ZAPC-ERR-UPPER-OBJ-NOT-FOUND 35: ZAPC-ERR-UPPER-OBJ-NOT-FOUND The parent object was not found. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 36: ZAPC-ERR-UPPER-OBJ-NOT-STARTED 36: ZAPC-ERR-UPPER-OBJ-NOT-STARTED The parent object was not started. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 37: ZAPC-ERR-TKN-INV-IN-SUMSTATE 37: ZAPC-ERR-TKN-INV-IN-SUMSTATE The parent object was not started. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 38: ZAPC-ERR-CANNOT-SWITCH TO-SS 38: ZAPC-ERR-CANNOT-SWITCH-TO-SS The attempt to change the session limit of an LU object to 1 failed because the LU is defined as a parallel-session LU. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL.
Error Numbers and Error Lists 39: ZAPC-ERR-CONFIG-IS-BAD 39: ZAPC-ERR-CONFIG-IS-BAD The configuration file is not accessible. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 40: ZAPC-ERR-CONFIG-IS-SWITCHING 40: ZAPC-ERR-CONFIG-IS-SWITCHING The configuration file is currently switching. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 41: ZAPC-ERR-CONFIG-FILE-NAME 41: ZAPC-ERR-CONFIG-FILE-NAME An invalid configuration file name was entered. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 42: ZAPC-ERR-OBJ-IS-STARTING 42: ZAPC-ERR-OBJ-IS-STARTING The object is currently being started. ZSPI–TKN–ERRLIST ZSPI–TKN–ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI–TKN–ENDLIST token–type token–type token-type token-type token–type ZSPI–TYP–LIST. ZSPI–TYP–ERROR. ZSPI-TYP-STRING ZSPI-TYP-STRING ZSPI–TYP–SSCTL. ZSPI–TKN–ERROR is the standard SPI error token, as described in the SPI Programming Manual.
Error Numbers and Error Lists 42: ZAPC-ERR-OBJ-IS-STARTING (This page left intentionally blank) A–48 111813 Tandem Computers Incorporated
Appendix B Programming Example The following example, written in TAL, illustrates the basic tasks that must be performed in an application that sends commands to and receives responses from the SNAX/APC subsystem. The basic steps that are illustrated are: 1. Opening the SCP 2. Building the command buffer 3. Sending the command 4. Retrieving the command 5.
Programming Example ! ! ! ! ************************************************************** * Sample program to demonstrate issuing commands and * * receiving responses * ************************************************************** ?symbols, inspect ?nocode, nomap, nolmap ! The SPI standard definitions ?nolist, source $system.zspidef.zspital ?list ! The EMS standard definitions ?nolist, source $system.zspidef.zemstal ?list ! The data communications standard definitions ?nolist, source $system.zspidef.
Programming Example BEGIN ! This procedure opens $RECEIVE, reads the startup message, ! and then closes $RECEIVE. STRUCT startup^msg; BEGIN ! This is the standard startup message structure.
Programming Example BEGIN ! Handle errors in calls on SPI procedures. END; ! of handle^spi^error ?PAGE "PROC: CALL^SCP" ! ************************************************************** ! * call^scp * ! ************************************************************** INT PROC call^scp; BEGIN ! This procedure sends a command to SCP and retrieves the ! response. The value returned by call^scp is the value of ! the return token in the response.
Programming Example END; ! of call^scp ?PAGE "PROC: BUILD^CMD" ! ************************************************************** ! * build^cmd * ! ************************************************************** PROC build^cmd( cmd, obj^type ); INT cmd, ! the command number obj^type; ! the object type BEGIN INT sserror; ! returned by call on SPI procedure sserror := SSINIT( buffer, zapc^val^buflen, zapc^val^ssid, zspi^val^cmdhdr, cmd,obj^type, 0 ); IF sserror THEN CALL handle^spi^error( sserror ); ! error on
Programming Example INT .
Programming Example END; ! of alter^lu ?PAGE "PROC: INFO^LU" ! ************************************************************** ! * info^lu * ! ************************************************************** PROC info^lu( obj^name ); INT .
Programming Example ! Set up the object name to contain the name of the line to ! be affected by the commands. obj^name[0] := 14; obj^name[1] ':=' ["$AP01.TDMLU001"]; ! Issue commands. CALL info^lu( obj^name CALL stop^lu( obj^name CALL alter^lu( obj^name CALL start^lu( obj^name CALL info^lu( obj^name ); ); ); ); ); ! Close SCP.
Glossary This glossary includes several definitions taken from the IBM Dictionary of Computing, IBM Network Program Products: General Information, VTAM Programming for LU 6.2, and SNA Type 2.1 Node Reference. Please refer to these IBM manuals for IBM terms not included in this glossary. access method. An I/O process that allows applications running on a NonStop system to communicate with other systems or devices.
Glossary BCPU. Backup central processing unit. bidder. In SNA, the LU-LU half-session defined at session activation as having to request and receive permission from the other LU-LU half-session to begin a bracket. Contract with first speaker. BIN. Basic information units transmitted to SNAX/APC. BIS. Bracket initiation stopped. BIU. Basic information unit. BOUT. Basic information units transmitted from SNAX/APC. bracket.
Glossary data definition language (DDL). A language and compiler used to define SPI token codes, token maps, and token types and to generate a DDL definition file and languagespecific definition files; the language-specific files can be included in the source code for management applications or management interfaces that use SPI. DDL. See data definition language. definition files.
Glossary Expand network. A network consisting of Tandem systems interconnected by communication links and supported by Expand software. finite state machine. An algorithm that controls the transition of an object — for example, a SNA session — between a finite number of states, each state transition being generated by one of a finite number of events. first speaker.
Glossary interprocess communication (IPC) message. The basic message unit by which Tandem processes communicate with each other. LEN. Low-entry networking. LEN end node. See low-entry networking end node. local TP. The transaction program running in the node under discussion (usually the Tandem system). logical unit (LU). In SNA, a port by which an end user accesses the network. An LU establishes the connections for the transmission of data between end users in the network.
Glossary network. A group of interconnected computer systems and devices, and the hardware and software used to connect them. network addressable unit (NAU). In SNA, a logical unit, physical unit, or a system services control point. The NAU is the origin or the destination of information transmitted through the network. network node (NN). A type 2.1 node that, besides offering full SNA end-user services, provides intermediate routing services within a type 2.
Glossary PATHMON environment . The servers, server classes, TCPs, terminals, SCREEN COBOL programs, and tell messages that run together under the control of one PATHMON process. Pathway. A group of software tools for developing and monitoring OLTP (on-line transaction processing) applications that use the requester/server model. Requesters can be either SCREEN COBOL programs interpreted by the terminal control process (TCP) or C, C++, COBOL85, Pascal, or TAL programs that use Pathsend procedure calls.
Glossary resource control block (RCB). A control block that represents the connection of a transaction program to a half-session. response unit. In SNA, a message unit that acknowledges a request unit. It may contain additional information in response to the request. return code (RC). A value returned at the completion of a command, indicating whether the command was successful and, if not, the reason for failure. RH. Request/response header. RID. Resource ID. RU. Request/response unit. SCF.
Glossary SNAX/APC. See SNAX/Advanced Program Communications. SNAX/APC Trace Analysis Program (APCTAP). A program that formats the output of the SNAX/APC trace facility into a readable form. SNAX/APN See SNAX/Advanced Peer Networking. SNAX/CDF. See SNAX/Cross Domain Facility. SNAX/Cross Domain facility (SNAX/CDF). A Tandem software product that allows procedures running in a Tandem System to communicate with LUs in other SNA domains. SNAX/Extended Facility (SNAX/XF).
Glossary Subsystem Control Facility (SCF). A Tandem product that is used to configure, control, and collect information about Tandem data communications subsystems. SCF can be used to dynamically configure and manage the entities in the SNAX/XF or SNAX/CDF environment. Subsystem Programmatic Interface (SPI). A Tandem product that presents a common message–based interface used to build and decode messages for communications between requestors on sessions. Generally used for control and enquiry functions.
Glossary transaction program (TP). In SNA LU 6.2 architecture, an application program that communicates via LU 6.2 facilities. More generally, a program that processes transactions. transaction program instance(TPI). In SNA LU 6.2 architecture, a transaction program is an application program that communicates via LU 6.2 facilities. More generally, a program that processes transactions. A TPI is an instance of a transaction program.
Glossary (This page left intentionally blank) Glossary–12 111813 Tandem Computers Incorporated
Index A ABORT command 5-8/12 Access method closing 5-10 name 4-41/42, 5-16, 5-28, 5-49 SNAX/CDF 4-42 SNAX/XF 4-42 ACTIVATE_SESSION control verb 4-39, 5-22, 5-24 Active contention loser sessions 4-19 Active contention winner sessions 4-19 Active conversations 4-19, 5-96 Active sessions 4-19, 5-96 ADD command generic 5-13/15 LU object additional tokens 5-16 PTNR-LU object additional tokens 5-18 PTNR-MODE object additional tokens 5-19 SESS object additional tokens 5-22 TPN object additional tokens 5-23 Address
Index Automatically activating sessions 4-20 Automatically starting LUs 4-20, 5-28 AUTOSTART attribute See ZAPC-TKN-AUTO-START B Backup processor takeover 2-2 BackupCPU number 4-14 BackupDebug flag values 4-14 Basic conversation type 4-22, 5-47, 5-59 BIND requests/responses FSM status 4-60 incoming RU bytes 4-22/24 mode name 4-32 outgoing RU bytes 4-23/24 PCID Control Vector 4-28 Session Instance Identifier 4-39 SNA name 4-41 synchronization level 4-43 BIS protocol 4-56 BIUs sent, received 4-48 Bracket sta
Index CNOS verbs See also individual CNOS verbs CHANGE_SESSION_LIMIT 1-5 equivalents 1-5 INITIALIZE_SESSION_LIMIT 1-5 RESET_SESSION_LIMIT 1-5 Command buffers 5-1 Commands programmatic, introduction to 1-6 security of 1-8 Commands, summary list 5-2 Configuration file 4-21 state 4-21, 5-97 tokens general description of 4-15 CONFIRM, processing count 4-53 CONFIRMED, processing count 4-53 Consumer distributor process 1-8 Contention loser sessions count of active 4-19 minimum 4-31 number designated 4-25 Content
Index CPU backup takeover 2-2 CPU number 4-11 Critical events 6-8 D Data communications standard definitions 4-6/14 Data, number of bytes received 4-49 Data, number of bytes sent 4-49 DDL 3-1 DDL, defining structures 4-1 DEACTIVATE_SESSION control verb 4-39, 5-11, 5-24 DEALLOCATE, processing count 4-53 DebugOnError flag values 4-14 DEFAULTMAXSESSION attribute See ZAPC-TKN-D-SESS-LIM DEFAULTMINCONLOSER attribute See ZAPC-TKN-D-MIN-CONLOSERS-LIM DEFAULTMINCONWINNER attribute See ZAPC-TKN-D-MIN-CONWINNERS-LIM
Index Error handling 1-8 Errors file being accessed 4-11 file system code 4-10 FSM 4-58 SNAX/APC descriptions A-1 tokens, error response general description of 4-15 Event management tasks 1-7 Event message descriptions 6-9 Event messages ZCOM and ZCMK 6-2 Events categories, message 6-7 CNOS operation error 6-7 CNOS operation information 6-7 configuration/startup error 6-7 configuration/startup information 6-7 data communications 6-2 error 6-7 FSM error 6-7 information 6-7 management 6-1/63 messages, introd
Index FSM error 6-10 FSM states 4-56/60 FSM, conversation 4-28 G GENERALTPREADY attribute See ZAPC-TKN-GENERAL-TP-RDY-SUPP GETVERSION command 5-41/43 GET_ATTRIBUTES, processing count 4-53 GET_TYPE, processing count 4-54 H Half-session status 4-59 Hierarchies among SNAX/APC objects 3-3 I INFO command CONVERSATION additional tokens 5-47 generic 5-44/46 LU object additional tokens 5-49 PROC object additional tokens 5-51 PTNR-LU object additional tokens 5-55 PTNR-MODE object additional tokens 5-56 SESS object
Index IPC-RETURN-CODE-DETAIL RC-LU-STOPPED 5-12 RC-TPI-ABORTED 5-12 RC-TPN-STOPPED 5-12 L LISTOBJECTS command 5-65/67 LISTOPENS command 5-68/71 Log file name 4-11 Logging state 4-30, 5-97 ZCMK-TKN-EMS-XFNAME 4-10 LU object names 3-5 LU object type 3-5, 4-8 LU-LU session status 4-60 LUs maximum number of sessions 4-40, 5-28 roles in sessions 4-40 starting automatically 4-20, 5-16, 5-28 LU_MODE_SESSION_LIMIT parameter 4-26, 4-40 M Management functions 1-5 MANAGER token 2-1 Mapped conversation type 4-22, 5-47
Index MC_REQUEST_TO_SEND, processing count 4-55 MC_SEND_DATA, processing count 4-55 MC_SEND_ERROR, processing count 4-55 Memory pool utilization statistics 4-14 Message buffers 4-18 Message file name 4-11 MINCONLOSER attribute See ZAPC-TKN-MIN-CONLOSERS-LIM MINCONWINNER attribute See ZAPC-TKN-MIN-CONWINNERS-LIM MODENAME attribute See ZAPC-TKN-MODE-NAME N NAMES interactive command See LISTOBJECTS command Nonsensitive commands 1-8 NonStop See Fault tolerance NULL object names 3-5 NULL object type 3-5, 4-8 O
Index Objects hierarchies among 3-3 of SNAX/APC subsystem 3-11 referencing 3-12 summary states 3-14 Opener name 4-10 Opener qualifiers 4-10 Openers and SNAX/APC process 2-2 multiple 2-2 number maintained by SNAX/APC process 4-14 security required 2-2 P Pacing 5-20 Pacing responses 4-23, 4-34/35, 4-38, 4-58 Pacing window 4-34, 4-38 Parallel session support 4-33 PARALLEL-SESSION-LU attribute See ZAPC-TKN-PARALLEL-SESS-LU PCID Control Vector 4-28, 5-60 Peripheral node 4-33 PERIPHERAL-NODE attribute See ZAPC-T
Index PTNR-LU object names 3-7 PTNR-LU object type 3-7, 4-8 PTNR-MODE object names 3-8 PTNR-MODE object type 3-8, 4-8 Purging state, BB chains 4-59 Q QRI setting 4-59 R RCB status 4-59 RCVWINDOW attribute See ZAPC-TKN-RCV-PACING-WINDOW RECEIVE_AND_WAIT, processing count 4-53 RECEIVE_IMMEDIATE, processing count 4-54 REMOTEATTACH attribute See ZAPC-TKN-REMOTE-ATTACH-DISP REMOTEATTACHTIMER attribute See ZAPC-TKN-REMOTE-ATTACH-DISP Requestor process identification 4-14 Requests close 2-2 REQUEST_TO_SEND, proce
Index RESET_SESSION_LIMIT (continued) RESPONSIBLE parameter 4-37, 5-11 with ABORT PTNR-MODE 5-11 Response empty 1-8 Response buffers 5-1, 5-6 RESPONSIBLE attribute See ZAPC-TKN-RESPONSIBLE RESPONSIBLE, CHANGE_SESSION_LIMIT parameter 4-37 RESPONSIBLE, RESET_SESSION_LIMIT parameter 4-37, 5-11 Return codes IPC 5-12 RUs incoming number before pacing response 4-23 maximum number of incoming bytes 4-22/24, 4-31, 5-11, 5-54 maximum number of outgoing bytes 4-23/24, 4-31, 5-54 number waiting to be sent 4-38 outgoi
Index Session Instance Identifier 5-60 Session Instance Identifier field (in BINDs) 4-39 SESSIONCONTROL attribute See ZAPC-TKN-SESS-CTRL-PRIV Sessions control verbs 4-39 count of active 4-19, 5-96 current conversations 4-22, 5-102 identification 4-39, 5-60 local LU roles, PLU or SLU 4-40 LU limits 4-40, 5-28 maximum number 4-26, 5-16 number activated automatically 4-20 number to be terminated 4-44 responsible LU 4-37 status 4-60 SLUs 4-33, 4-40, 5-18 SNANAME attribute See ZAPC-TKN-SNA-NAME SNASVCMG abortin
Index SNAX/APC (continued) standard definitions 4-15 tokens, common 4-15 SNAX/APC errors A-4 ZAPC–ERR– ACTV-FAIL-NO-RETRY A-5 ACTV-FAIL-RETRY A-6 ALLOC-ERR-NO-RETRY A-7 ALLOC-ERR-RETRY A-8 ALLOC-PGM-NOT-AVL A-9 CANNOT-SWITCH-TO-SS A-43 CMD-FORCED A-10 CMD-INV-DEFT-OBJ A-11 CMD-INV-NOT-PS-LU A-12 CMD-NEGOTIATED A-13 CMD-RACE-REJECT A-14 CONFIG-FILE-NAME A-46 CONFIG-IN-PROGRESS A-15 CONFIG-IS-BAD A-44 CONFIG-IS-SWITCHING A-45 DEFT-OBJNAME A-16 DRAIN-S-NO-IN-EFFECT A-17 DUP-MODENAME A-18 INV-DEV-TYPE A-19 LU-
Index SNAX/APC errors (continued) ZAPC–ERR– (continued) TRACE-NOT-STOPPED A-37 TRACE-NOT-TRACING A-38 TRACE-SHUTDOWN-ERROR A-39 UPPER-OBJ-NOT-FOUND A-40 UPPER-OBJ-NOT-STARTED A-41 SNAX/APC objects addressed and target 1-5 SNAX/APC process NonStop process pair 2-2 number of unplanned takeovers 4-11 security required for OPEN 2-2 SNAX/APC response buffers 5-6 SNAX/APC subsystem control points 1-2 definition files 3-1 file interface 2-2 interfaces 1-2 introduction 1-1 security 1-8 SNAXFILENAME attribute See Z
Index STATISTICS command date and time 4-48, 4-53 generic 5-84/86 LU object additional tokens 5-87 PROC object additional tokens 5-88 PTNR-MODE object additional tokens 5-90 SESS object additional tokens 5-91 Statistics sampling date and time 4-48, 4-53 resetting the counters 4-48 Statistics tokens See also STATISTICS command general description of 4-15 STATUS command CONVERSATION object additional tokens 5-95 generic 5-92/94 LU object additional tokens 5-96 PROC object additional tokens 5-97 PTNR-LU objec
Index Subsystem Programmatic Interface naming rules for applications 3-1 object summary states 3-14 objects types 3-2 referencing objects 3-12 SUB modifier 3-13 ZCOM–TKN–SUB 3-2, 3-13 Super-group user ID opener of %ZSPI 2-2 SUPER.
Index TP-READY request initiated by DISPATCH-TP 4-26 TPN support 4-29, 5-23 verbs rejected 5-12 TPI object name 3-10 TPI object type 3-10, 4-8 TPI origin 4-44, 5-62 TPN object name 3-11 TPN object type 3-11, 4-8 TRACE command 5-111 Trace file name 4-47, 5-96, 5-98 Trace tokens See also TRACE command general description of 4-15 Tracing allocated pages 4-45 data record length 4-45 information to be collected 4-44 state of activity 4-46, 5-96, 5-98 stopping the current trace 4-46 wrapping when file is full 4-
Index ZAPC-MAPFSM-STATES description of 4-56 in STATUS SESS command 5-102 structure of 4-56 ZFSM-BIS field 4-56 ZFSM-BSM field 4-56 ZFSM-CHAIN-RCV field 4-57 ZFSM-CHAIN-SEND field 4-57 ZFSM-CONVERSATION field 4-57 ZFSM-ERROR-OR-FAILURE field 4-58 ZFSM-PAC-RQ-RCV field 4-58 ZFSM-PAC-RQ-SEND field 4-58 ZFSM-POST field 4-58 ZFSM-QRI-CHAIN-RCV field 4-59 ZFSM-RCB-STATUS field 4-59 ZFSM-RCV-PURGE field 4-59 ZFSM-SCB-STATUS field 4-59 ZFSM-STATUS field 4-60 STATS-LU description of 4-48 in RESETSTATS LU command r
Index ZAPC-MAP- (continued) STATS-SESS description of 4-52 in RESETSTATS SESS command response 5-79 in STATISTICS SESS command response 5-91 structure of 4-52 ZALLOCATE-CNT field 4-53 ZCONFIRMED-CNT field 4-53 ZDEALLOCATE-CNT field 4-53 ZFLUSH-CNT field 4-54 ZGET-ATTR-CNT field 4-53 ZGET-TYPE-CNT field 4-54 ZMC-ALLOCATE-CNT field 4-54 ZMC-CONFIRM-CNT field 4-54 ZMC-CONFIRMED-CNT field 4-54 ZMC-DEALLOCATE-CNT field 4-54 ZMC-FLUSH-CNT field 4-55 ZMC-GET-ATTR-CNT field 4-54 ZMC-PREP-TO-RCV-CNT field 4-55 ZMC-
Index ZAPC-TKN- (continued) ACTV-CONWINNERS-CNT description of 4-19 in INFO PTNR-MODE command 5-56 in STATUS PTNR-MODE command 5-100 ACTV-SESS-CNT description of 4-19 in INFO PTNR-MODE command 5-56 in STATUS LU command 5-96 in STATUS PTNR-MODE command 5-100 AUTO-ACTIVATE-LIM description of 4-20 in ADD PTNR-MODE command 5-19 in ALTER PTNR-MODE command 5-33 in INFO PTNR-MODE command 5-57 AUTO-START description of 4-20 in ADD LU command 5-16 in ALTER LU command 5-28 in INFO LU command 5-49 CHAR-MAPPING-SUPP d
Index ZAPC-TKN- (continued) CONV-TYPE description of 4-22 in INFO CONVERSATION command 5-47 in INFO SESS command 5-59 CUR-MAXINRUSIZE description of 4-22 in INFO PTNR-MODE command 5-57 in INFO SESS command 5-59 CUR-MAXOUTRUSIZE description of 4-23 in INFO PTNR-MODE command 5-57 in INFO SESS command 5-59 CUR-RCV-PACING-CNT description of 4-23 in INFO SESS command 5-60 in STATUS SESS command 5-102 CUR-SEND-PACING-CNT description of 4-23 in INFO SESS command 5-60 in STATUS SESS command 5-102 D-MAXINRUSIZE des
Index ZAPC-TKN- (continued) D-MIN-CONWINNERS-LIM description of 4-25 in ADD PTNR-MODE command 5-20 in ALTER PTNR-MODE command 5-34 in INFO PTNR-MODE command 5-57 D-SESS-LIM description of 4-26 in ADD PTNR-MODE command 5-20 in ALTER PTNR-MODE command 5-34 in INFO PTNR-MODE command 5-58 DISPATCHED-IND description of 4-26 in INFO TPI command 5-62 DRAIN-SOURCE description of 4-26 in INFO PTNR-MODE command 5-57 in STOP PTNR-MODE command 5-109 DRAIN-TARGET description of 4-27 in INFO PTNR-MODE command 5-57 in ST
Index ZAPC-TKN- (continued) LOCAL-ATTACH-IND description of 4-29 in INFO TPI command 5-62 LOCAL-SEC-ACCEPTANCE description of 4-29 in INFO PTNR-LU command 5-55 LOCAL-TP-NAME description of 4-30 in INFO SESS command 5-60 LOCAL-TP-PROC-NAME description of 4-30 in INFO TPI command 5-62 LOG-STATE description of 4-30 in STATUS PROC command 5-97 LU-ERR-NAME 6-17 LU-NAME 6-12 MAXAPPLIOSIZE description of 4-30 in INFO PROC command 5-54 MAXINRUSIZE description of 4-31 in INFO PROC command 5-54 MAXOUTRUSIZE descript
Index ZAPC-TKN- (continued) ONE-STEP-READ description of 4-32 in INFO PROC command 5-54 PARALLEL-SESS-LU description of 4-33 in ADD PTNR-LU command 5-18 in ALTER PTNR-LU command 5-32 in INFO PTNR-LU command 5-55 PARAM-ERR 6-15 PERIPHERAL-NODE description of 4-33 in ADD PTNR-LU command 5-18 in ALTER PTNR-LU command 5-32 in INFO PTNR-LU command 5-55 POLARITY description of 4-34 in INFO SESS command 5-60 RC-RETN 6-41 RCV-PACING-WINDOW description of 4-34 in ADD PTNR-MODE command 5-20 in ALTER PTNR-MODE comman
Index ZAPC-TKN- (continued) REMOTE-SEC-ACCEPTANCE description of 4-36 in INFO PTNR-LU command 5-55 REPLY-DELAYED-ON-ERR description of 4-36 in ADD TPN command 5-23 in ALTER TPN command 5-36 in INFO TPN command 5-64 RESOURCE-ID description of 4-37 in INFO CONVERSATION command 5-48 in INFO TPI command 5-62 RESPONSIBLE description of 4-37 in ALTER PTNR-MODE command 5-35 in INFO PTNR-MODE command 5-58 in STOP PTNR-MODE command 5-109 RETN-DETL 6-41 RUS-TO-BE-SENT description of 4-38 in STATUS CONVERSATION 5-95
Index ZAPC-TKN- (continued) SESS-LIM description of 4-40 in ADD LU command 5-16 in ALTER LU command 5-28 in ALTER PTNR-MODE command 5-35 in INFO LU command 5-49 in INFO PTNR-MODE command 5-58 SESS-TYPE description of 4-40 in INFO SESS command 5-61 SNA-NAME description of 4-41 in ADD LU command 5-16 in ADD PTNR-LU command 5-18 in ALTER LU command 5-28 in ALTER PTNR-LU command 5-32 in INFO LU command 5-49 in INFO PTNR-LU command 5-55 SNAX-FILE-NAME 4-41 description of 4-42 in ADD LU command 5-16 in ALTER LU
Index ZAPC-TKN- (continued) SYNC-LEVEL description of 4-43 in INFO CONVERSATION command 5-48 in INFO SESS command 5-61 TERMINATION-CNT description of 4-44 in INFO PTNR-MODE command 5-58 in STATUS PTNR-MODE command 5-100 TPI-ORIGIN description of 4-44 in INFO TPI command 5-62 TRACE-PAGES description of 4-45 in TRACE command 5-112 TRACE-RECSIZE description of 4-45 in TRACE command 5-112 TRACE-STATE description of 4-46 in STATUS LU command 5-96 in STATUS PROC command 5-98 TRACE-STOP description of 4-46 in TRA
Index ZAPC-TNM-name 4-15 ZAPC-VALMAXBUFLEN 5-1 ZAPC-VAL-CONFIG-ERRBAD-CODE 6-17 BAD-FILE 6-17 BAD-VSN 6-17 FAIL-CVT 6-17 ZAPC-VAL-CONFIG-STATE DONE 4-21 ERROR 4-21 INPROG 4-21 SWITCH 4-21 ZAPC-VAL-CONV-FAILED-ATRAW 6-41 SD 6-41 ZAPC-VAL-CONV-TYPEBASIC 4-22 MAPPED 4-22 ZAPC-VAL-FSM-BISCLOSED 4-56 RCVD 4-56 RESET 4-56 SEND 4-56 ZAPC-VAL-FSM-BSMBETB 4-56 INB 4-56 ZAPC-VAL-FSM-CHAINRCVBETC 4-57 INC 4-57 NG-SENT 4-57 PND-RSP 4-57 PND-SND 4-57 ZAPC-VAL-FSM-CHAINSNDBETC 4-57 INC 4-57 NG-SENT 4-57 PND-RSP 4-57 PND
Index ZAPC-VAL-FSM-CVDEALL-DF 4-28, 4-57 END-CONV 4-28, 4-57 PND-DEALL 4-28, 4-57 PREP-TO-RCV-DF 4-28, 4-57 RCV 4-28, 4-57 RCVD-CNF 4-28, 4-57 RCVD-CNF-DEALL 4-28, 4-57 RCVD-CNF-SEND 4-28, 4-57 RESET 4-28, 4-57 SEND 4-28, 4-57 ZAPC-VAL-FSM-ERRALLOC-FAIL-NR 4-58 ALLOC-FAIL-R 4-58 NO-REQ 4-58 PROTO-ERR 4-58 RCVD-ERR 4-58 SON 4-58 SYNC-NOT-SUPP 4-58 ZAPC-VAL-FSM-NAMEBIS-BDR 6-11 BIS-FSP 6-11 BSM 6-11 CHAIN-RCV 6-11 CHAIN-SEND 6-11 CONV 6-11 ERR 6-11 IRQ-MODE-R 6-11 IRQ-MODE-S 6-11 PAC-RQ-R 6-11 PAC-RQ-S 6-11
Index ZAPC-VAL-FSM-PACRQSNDAWAIT 4-58 RESET 4-58 ZAPC-VAL-FSM-POSTPND-POSTED 4-58 POSTED 4-58 RESET 4-58 ZAPC-VAL-FSM-QRICHAINRCVNOTQR 4-59 QR 4-59 RESET 4-59 ZAPC-VAL-FSM-RCBSTATUSFREE 4-59 INIT 4-59 INUSE 4-59 ZAPC-VAL-FSM-RCVPURGEPURGE 4-59 RESET 4-59 ZAPC-VAL-FSM-SCBSTATUSACT 4-59 FREE 4-59 INUSE 4-59 PNDFH12 4-59 PNDFH5 4-59 ZAPC-VAL-FSM-STACTIVE 4-60 PND-BIN 4-60 PND-BIN-RSP-O 4-60 PND-BIN-RSP-T 4-60 PND-CIN 4-60 PND-INB-RSP 4-60 PND-INIHRSP-T 4-60 PND-INIHSRSP-O 4-60 PND-INIRSP-PLU 4-60 PND-INIRSP-S
Index ZAPC-VAL-INIT-INFOINIT-BEG 6-23 INIT-END 6-23 RE-INIT-END 6-23 ZAPC-VAL-LOG-STATEACTV 4-30 INACTV 4-30 ZAPC-VAL-OPERATORLOCAL-LU 6-44 REMOTE-LU 6-44 ZAPC-VAL-POLARITYBIDDER 4-34 FSP 4-34 ZAPC-VAL-REASONUNKWN-MODENAME 6-47 ZERO-SESS-LIM 6-47 ZAPC-VAL-REMOTE-ATTACHQUEUE 4-35 REJECT 4-35 ZAPC-VAL-RESPONSIBLESOURCE 4-37 TARGET 4-37 ZAPC-VAL-SEC ALRDY-VERIFIED 4-36 CONV 4-36 NONE 4-36 ZAPC-VAL-SECALRDY-VERIFIED 4-29 CONV 4-29 NONE 4-29 ZAPC-VAL-SESS-TYPEPRIMARY 4-40 SECONDARY 4-40 ZAPC-VAL-SSID 4-4 ZAPC-V
Index ZAPC-VAL-TRACE-STATEACTV 4-46 INACTV 4-46 ZAPC-VAL-TRC-OPTALL 4-44 BIU 4-44 BUFFER 4-45 DATA 4-44 DFC 4-45 LNS 4-45 PROC 4-45 PS 4-45 QUEUE 4-45 RM 4-45 SPI 4-45 TASK 4-45 TC 4-45 ZAPC-VAL-VERSION 4-18 ZBIU-RCVD-CNT field, in ZAPC-MAP-STATS-LU 4-48 ZBIU-SENT-CNT field, in ZAPC-MAP-STATS-LU 4-48 ZCMK definition files 3-1 ZCMKdefinitions 4-6/14 event messages 6-2 ZCMK- errors messages A-3 ZCMK-MAPALTER description of 4-14 in ALTER PROC command 5-30 structure of 5-30 INFO description of 4-14 in INFO PRO
Index ZCMK-MAP- (continued) STATS-BUF description of 4-14, 5-77, 5-89 in RESETSTATS command response 5-76 in STATISTICS command response 5-88 structure of 5-76, 5-88 STATS-MEM description of 4-14, 5-77, 5-89 in RESETSTATS command response 5-76 in STATISTICS command response 5-88 structure of 5-76, 5-88 STATS-OPNR description of 4-14, 5-77, 5-89 in RESETSTATS command response 5-76 in STATISTICS command response 5-88 STATS-RECV description of 4-14, 5-77, 5-89 in RESETSTATS command response 5-76 in STATISTICS
Index ZCMK-TKN- (continued) CHMAP-NAME description of 4-10 in ADD TPN command 5-23 in ALTER PROC command 5-30 in ALTER TPN command 5-36 in INFO CONVERSATION command 5-47 in INFO PROC command 5-53 in INFO TPN command 5-63 CHMAP-NOTE description of 4-10 in INFO CONVERSATION command 5-47 in INFO PROC command 5-53 in INFO TPN command 5-63 CHMAP-XFNAME description of 4-10 in ALTER PROC command 5-31 in INFO PROC command 5-53 CMD-CODE description of 4-10 EMS-XFNAME description of 4-10 in ALTER PROC command 5-31 i
Index ZCMK-TKN- (continued) LISTOP-XPNAME description of 4-10 in LISTOPENS command response 5-68 LOG-XFNAME description of 4-11 in ALTER PROC command 5-31 in INFO PROC command 5-53 MSG-XFNAME description of 4-11 in ALTER PROC command 5-31 in INFO PROC command 5-53 PKG-BANNER description of 4-11, 5-42 PRI-CPU description of 4-11 PROG-FILE-MOD description of 4-11 in INFO PROC command 5-54 PROG-XFNAME description of 4-11 in INFO PROC command 5-53 SEGTYPE description of 4-11 in INFO PROC command 5-52 SNAERR de
Index ZCOMdefinitions 4-6/14 event messages 6-2 object types 4-8 values used by SNAX/APC 4-8, 4-9 ZCOM- error messages A-3 ZCOM-CMDABORT 5-8/12 ADD generic 5-13/15 LU object additional tokens 5-16 PTNR-LU object additional tokens 5-18 PTNR-MODE object additional tokens 5-19 SESS object additional tokens 5-22 TPN object additional tokens 5-23 ALTER generic 5-25/27 LU object additional tokens 5-28 PROC object additional tokens 5-30 PTNR-LU object additional tokens 5-32 PTNR-MODE object additional tokens 5-33
Index ZCOM-CMD- (continued) START 5-80/83 STATISTICS generic 5-84/86 LU object additional tokens 5-87 PTNR-MODE object additional tokens 5-90 SESS object additional tokens 5-91 STATISTICS PROC additional tokens 5-88 STATUS CONVERSATION object additional tokens 5-95 generic 5-92/94 LU object additional tokens 5-96 PROC object additional tokens 5-97 PTNR-LU object additional tokens 5-99 PTNR-MODE object additional tokens 5-100 SESS object additional tokens 5-101 TPI object additional tokens 5-104 TPN object
Index ZCOM-TKN- (continued) OBJSTATE 4-12 OBJTYPE 4-12 SEL-SUMSTATE 4-12 SUB 4-12 object addressing 3-2 SUBJ-CONVERSATION 4-13 SUBJ-LU 4-13 SUBJ-PROC 4-13 SUBJ-PTNR-LU 4-13, 6-40 SUBJ-PTNR-MODE 4-13 SUBJ-SESS 4-13 SUBJ-TPI 4-13 SUBJ-TPN 4-13 ZCOM-VALSECUR-SUPP-ALL 4-8, 4-12 TRACE-SUPP-NONE 4-9, 4-12 ZCOM-VAL-SUBALL 3-13, 4-8 NONE 3-13, 4-8 object-type 4-8 ONLY 3-13, 4-8 ZCOM-VAL-SUMSTATESTARTED 4-8 STARTING 4-9 STOPPED 4-9 STOPPING 4-9 ZCOM–TKN– SEL–SUMSTATE 3-12 SUB enumerated values 3-13 ZCONFIRMED-CNT f
Index ZFLUSH-CNT field, in ZAPC-MAP-STATS-SESS 4-54 ZFSM-BIS field, in ZAPC-MAP-FSM-STATES 4-56 ZFSM-BSM field, in ZAPC-MAP-FSM-STATES 4-56 ZFSM-CHAIN-RCV field, in ZAPC-MAP-FSM-STATES 4-57 ZFSM-CHAIN-SEND field, in ZAPC-MAP-FSM-STATES 4-57 ZFSM-CONVERSATION field, in ZAPC-MAP-FSM-STATES 4-57 ZFSM-ERROR-OR-FAILURE field, in ZAPC-MAP-FSM-STATES 4-58 ZFSM-PAC-RQ-RCV field, in ZAPC-MAP-FSM-STATES 4-58 ZFSM-PAC-RQ-SEND field, in ZAPC-MAP-FSM-STATES 4-58 ZFSM-POST-ERR field, in ZAPC-MAP-FSM-STATES 4-58 ZFSM-QRI
Index ZSEND-ERROR-CNT field, in ZAPC-MAP-STATS-SESS 4-54 ZSPI definition files 3-1 ZSPI- definitions 4-1 ZSPI-SSN-ZAPC 4-3 ZSPI-TKNALLOW 4-3 in INFO PROC command 5-52 in LISTOPENS command 5-69 COMMAND 4-3 ERROR 4-3 MANAGER 2-1, 4-3 OBJECT-TYPE 4-3 RETCODE 4-3 SEGLIST 4-3 in INFO PROC command 5-52 SERVER-VERSION 4-3 SSID 4-4 ZSPIDEF subvolume 3-1 Special characters * (asterisk) wild-card character 1-6 ? (question mark) wild-card character 1-6 Index–40 111813 Tandem Computers Incorporated
