Networking and Data Communications Library EXPAND Management Programming Manual ™ Abstract Part Number This manual is for programmers. It describes the management-programming interfaces to the EXPAND subsystem and how to use them.
Document History Edition Part Number Product Version Operating System Version Date First Edition Second Edition 84109 11169 EXPAND C00 EXPAND C10 GUARDIAN 90 C00 GUARDIAN 90 C10 November 1987 May 1988 New editions incorporate any updates issued since the previous edition. Copyright All rights reserved. No part of this document may be reproduced in any form, including photocopying or translation to another language, without the prior written consent of Tandem Computers Incorporated.
CONTENTS PREFACE ...................................................... ix NOTATION CONVENTIONS ......................................... xi SECTION 1. INTRODUCTION .................................... Objects Controlled by the EXPAND Subsystem ................ Required Management Functions ............................. Relationship with Other Subsystems ........................ Architecture of the EXPAND Subsystem ...................... 1-1 1-1 1-2 1-2 1-3 SECTION 2.
CONTENTS SECTION 5. SPI PROGRAMMING CONSIDERATIONS FOR THE EXPAND SUBSYSTEM ....................................... Building the Command Buffer ............................... Discontinuing a Command in Progress ....................... Receiving and Decoding the Response Buffer ................ Error Handling ............................................ Security .................................................. 5-1 5-1 5-2 5-3 5-4 5-4 SECTION 6. COMMON DEFINITIONS ..............................
CONTENTS SECTION 8. EVENT MANAGEMENT ................................ 8-1 Subsystem Processes That Report Events .................... 8-1 Critical Events ........................................... 8-3 Event-Management Programming .............................. 8-4 Event-Message Descriptions ................................ 8-4 3: ZEXP-EVT-IO-BUS-ERR .................................. 8-7 4: ZEXP-EVT-DEV-ERR .................................... 8-10 6: ZEXP-EVT-DEV-UP .....................................
CONTENTS APPENDIX C. LINE ATTRIBUTES BY LINE-HANDLER TYPE ........... C-1 INDEX ................................................... Index-1 FIGURES 1-1. 2-1. Architecture of the EXPAND Subsystem .................. 1-3 How an Application Uses the Management-Programming Interfaces ............................................ 2-3 TABLES 2-1. 2-2. 2-3. 2-4. 2-5. 2-6. 6-1. 6-2. 6-3. 7-1. 8-1. 8-2. B-1. B-2. C-1. viii EXPAND Programmatic Commands ..........................
PREFACE This manual is for you if you are an experienced application programmer in one of the following categories: • TAL programmers, and COBOL85 programmers using ENTER TAL, who are writing applications that control or monitor the EXPAND subsystem. • TACL users who are writing macros or routines that control or monitor the EXPAND subsystem. This manual provides subsystem-specific programming information about the management-programming interface provided by Tandem for managing the EXPAND subsystem.
PREFACE • An example in TAL that illustrates giving commands and retrieving responses. • Several example event-message filters for use with the EXPAND subsystem, and an example in TAL that illustrates retrieving an EXPAND event message and taking appropriate corrective action.
NOTATION CONVENTIONS The following list summarizes the conventions for syntax notation in this manual. Notation Meaning UPPERCASE LETTERS Uppercase letters represent keywords and reserved words; enter these items exactly as shown. italics Lowercase italic letters represent variable items that you supply. Brackets [] Brackets enclose optional syntax items. A group of vertically aligned items enclosed in brackets represents a list of selections from which you can choose one or none.
SECTION 1 INTRODUCTION The EXPAND network-operating software is a communications subsystem that links together as many as 255 geographically distributed Tandem NonStop computer systems to create a network having the same reliability, capacity to preserve database integrity, and potential for modular expansion as a single system. OBJECTS CONTROLLED BY THE EXPAND SUBSYSTEM An EXPAND network consists of two or more Tandem NonStop systems connected by data-communications paths.
INTRODUCTION Required Management Functions REQUIRED MANAGEMENT FUNCTIONS To manage the objects that make up the EXPAND subsystem, you must be provided with the capability to do the following: • Define certain characteristics, or attributes, of lines, paths, and processes. • Find out the current values of the attributes of lines, paths, and processes. • Obtain information about the current paths from other systems to a selected system. • Determine the current states of lines and paths.
INTRODUCTION Architecture of the EXPAND Subsystem ARCHITECTURE OF THE EXPAND SUBSYSTEM The EXPAND subsystem consists of the EXPAND manager process, the Network Control Process (NCP), the Network Utility Process ($ZNUP), and one or more line-handler processes. ($ZNUP performs some statistics collection functions that were formerly performed by the NCP.) Figure 1-1 illustrates the architecture of the EXPAND subsystem and the various interfaces to the subsystem.
INTRODUCTION Architecture of the EXPAND Subsystem You can communicate with the EXPAND subsystem through both interactive and programmatic interfaces. The interactive interfaces to the EXPAND subsystem are the following: • The Subsystem Control Facility (SCF), which you can use to configure, control, and collect information from the EXPAND subsystem. SCF communicates with the EXPAND manager process through the Subsystem Control Point (SCP), a programmatic command interface that is described below.
INTRODUCTION Architecture of the EXPAND Subsystem Applications other than management applications use EXPAND for access to remote files, devices, and applications. They do so by referring to network file names and process names and by calling GUARDIAN 90 file-system procedures. For more information, refer to the EXPAND Reference Manual, the GUARDIAN Operating System Programmer’s Guide, and the System Procedure Calls Reference Manual.
SECTION 2 MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM As seen in the previous section, there are several different interfaces, both interactive and programmatic, to the EXPAND subsystem.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM restart terminals on that remote system. As another example, if your EXPAND network contains an X.25 virtual circuit, you could write an application that monitors the events reported by the X25AM subsystem as well as those reported by the EXPAND subsystem. This application could also send requests to both the X25AM subsystem and the EXPAND subsystem to manage the network.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM How Applications Fit Into the Architecture Responses Control-andInquiry Interface EXPAND Manager Process SCP Commands Management Application Line-Handler Process $ZNUP EMS Filter EventManagement Interface NCP Event Messages EMS Consumer Distributor EMS Collector ($0) Event Messages Event Messages Event Messages Other Subsystems Event Log S7012-002 Figure 2-1.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Table 2-1. EXPAND Programmatic Commands Terminates the operation of lines or paths immediately. ALTER Changes the values of attributes of lines, paths, or line-handler processes. GETVERSION Returns the server version of the EXPAND manager process.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Tables 2-2, 2-3, 2-4, 2-5, and 2-6 show the correspondence between the interactive commands you use to control and inquire about the EXPAND subsystem and the corresponding programmatic commands you send to the EXPAND subsystem.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Table 2-2.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Table 2-2.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Table 2-3.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Table 2-3.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Table 2-4.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Table 2-5.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Commands an Application Can Issue Table 2-6.
MANAGEMENT PROGRAMMING FOR THE EXPAND SUBSYSTEM Prerequisite Manuals PREREQUISITE MANUALS This manual provides subsystem-specific information about using the programmatic control-and-inquiry interface to communicate with the EXPAND subsystem and about the event messages generated by the EXPAND subsystem.
SECTION 3 COMMUNICATING WITH THE EXPAND MANAGER PROCESS This section describes how a management application sends commands to and receives responses from the EXPAND subsystem. Obtaining event messages from the EXPAND subsystem is described in Section 8, "Event Management." COMMUNICATING THROUGH SCP To manage the EXPAND subsystem, an application communicates with the EXPAND manager process.
COMMUNICATING WITH THE EXPAND MANAGER PROCESS Communicating Through SCP 6. If the request is directed to the EXPAND manager process itself, that process responds to the request. If the request is directed to the NCP or to $ZNUP, the EXPAND manager process forwards it to that process, which in turn sends its response back to the EXPAND manager process.
COMMUNICATING WITH THE EXPAND MANAGER PROCESS Using a RUN Command Using a RUN Command The syntax of the command-interpreter RUN command used to create the EXPAND manager process is as follows. RUN object-file / run-option-list / [ backup-cpu-number ] object-file is the name of the object file for the EXPAND manager process. The name of this file is $SYSTEM.SYSnn.OZEXP, where $SYSTEM.SYSnn is the currently used system subvolume and nn is a two-digit octal integer that identifies that subvolume.
COMMUNICATING WITH THE EXPAND MANAGER PROCESS Using a RUN Command NOWAIT means that the initiating command interpreter does not wait while the EXPAND manager process runs but returns a command input prompt after sending the startup message to the process. If this option is omitted, the command interpreter pauses while the process runs. PRI priority is the execution priority of the EXPAND manager process. priority is an integer in the range 1 through 199.
SECTION 4 ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM The Subsystem Programmatic Interface (SPI) is used for building commands to, decoding responses from, and obtaining event messages issued by the EXPAND subsystem. The procedures used by an application to perform these tasks are described in the Distributed Systems Management (DSM) Programming Manual. Using SPI messages to communicate with the EXPAND subsystem through SCP is described in the Communications Management Programming Manual.
ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM Definition Files DEFINITION FILES Every token or other type of definition needed by an application that uses SPI is defined in definition files provided by Tandem. Each source of definitions, such as a subsystem or an operatingsystem component, has associated with it a set of four definition files: one in TAL; one in COBOL85; one in TACL; and one in DDL, from which the other three definition files are derived.
ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM Naming Rules and Guidelines for Applications Management Programming Manual, respectively. tions are described in this manual. The EXPAND defini- NAMING RULES AND GUIDELINES FOR APPLICATIONS By convention, Tandem uses names beginning with the letter Z for all definitions and all component fields of structures in its definition files.
ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM Object Types Object Types In addition to the object-type header token found in all commands and responses, some EXPAND response records contain an objecttype token that describes the object the response record relates to. In the EXPAND subsystem, object types are represented by symbolic names of the form ZCOM-OBJ-name, where name identifies the object type.
ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM Event Numbers Event Numbers Event numbers for event messages issued by the EXPAND subsystem are represented by symbolic names of the form ZEXP-EVT-name, where name identifies the event. EXPAND event numbers and their associated event messages are described in Section 8, "Event Management.
ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM Other Tokens A table of all the token codes defined by the EXPAND subsystem (token codes with names of the form ZEXP-TKN-name) can be found in Appendix B. Token Types The token types used by the EXPAND subsystem are represented by symbolic names of the form subsys-TYP-name, where subsys is a four-character subsystem abbreviation and name identifies the token type. For example, the token type ZSPI-TYP-CHAR8 represents a string of eight ASCII characters.
ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM Other Tokens Extensible structured tokens do not appear in any event message or error list issued by the EXPAND subsystem. Throughout this manual, when an extensible structured token is described, its DDL definition, including the definitions and types of all fields, is also given.
ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM Components of a Response Components of a Response This topic is discussed in the Communications Management Programming Manual. Each EXPAND response and the tokens it contains are described in this manual in Section 7, "Commands and Responses." Considerations for retrieving and decoding EXPAND response buffers are described in this manual in Section 5, "SPI Programming Considerations for the EXPAND Subsystem.
SECTION 5 SPI PROGRAMMING CONSIDERATIONS FOR THE EXPAND SUBSYSTEM The Communications Management Programming Manual discusses general programming considerations for writing applications that use the Subsystem Programmatic Interface (SPI) to communicate with data-communications subsystems like the EXPAND subsystem. This section discusses SPI programming considerations that are specific to the EXPAND subsystem.
SPI PROGRAMMING CONSIDERATIONS FOR THE EXPAND SUBSYSTEM Building the Command Buffer an operation will be performed if a field contains a value other than its null value. For example, in the ALTER LINE command, if a field of the extensible structured token that describes the line attributes contains a value other than its null value, that value is assigned to the attribute corresponding to that field.
SPI PROGRAMMING CONSIDERATIONS FOR THE EXPAND SUBSYSTEM Receiving and Decoding the Response Buffer RECEIVING AND DECODING THE RESPONSE BUFFER The following programming considerations apply when an application receives and decodes the response buffer for an EXPAND response. In responses to EXPAND commands that operate on objects, a response record always contains response information for the operation of the command on a single object.
SPI PROGRAMMING CONSIDERATIONS FOR THE EXPAND SUBSYSTEM Error Handling ERROR HANDLING General programming considerations for handling errors that occur when using the management-programming interfaces are discussed in the Communications Management Programming Manual. In the programmatic control-and-inquiry interface to the EXPAND subsystem, there are two values for the return token that indicate that the response record does not contain an error list.
SECTION 6 COMMON DEFINITIONS The management-programming interfaces to the EXPAND subsystem make use of definitions from four different sources: the SPI standard definitions, the EMS standard definitions, the datacommunications standard definitions, and the EXPAND definitions. This section discusses the definitions from these four sources that can be used in a management application to communicate with the EXPAND subsystem.
COMMON DEFINITIONS SPI Standard Definitions all applications using SPI; token and field values; and fixed structures and token types used in other definitions. This table does not list SPI error numbers or definitions that are used only in error lists associated with those error numbers, nor does it list all the SPI token values that can be used in an application. For information about these definitions, refer to the Distributed Systems Management (DSM) Programming Manual. Table 6-1.
COMMON DEFINITIONS SPI Standard Definitions Table 6-1.
COMMON DEFINITIONS SPI Standard Definitions ZSPI-TKN-RETCODE is the return token, which contains one of the EXPAND or common data-communications error numbers. For descriptions of all EXPAND error numbers and their associated error lists, refer to Appendix A. For descriptions of all common data-communications error numbers and their associated error lists, refer to the Communications Management Programming Manual. ZSPI-TKN-SERVER-VERSION contains the server version of the EXPAND manager process.
COMMON DEFINITIONS EMS Standard Definitions Table 6-2.
COMMON DEFINITIONS Data-Communications Standard Definitions This table does not list data-communications error numbers or definitions that are used only in error lists associated with those error numbers. For information about these definitions, refer to the Communications Management Programming Manual. Table 6-3.
COMMON DEFINITIONS Data-Communications Standard Definitions ZCOM-OBJ-LINE is an EXPAND line. In the EXPAND subsystem, a line is the smallest entity that carries units of data between two neighboring nodes. A line can be, for instance, a copper wire, a fiber-optic cable, or a satellite link. Since a path between neighboring nodes can consist of one or more lines, lines are subordinate to paths in the hierarchy of objects. ZCOM-OBJ-NULL refers to the EXPAND manager process.
COMMON DEFINITIONS Data-Communications Standard Definitions ZCOM-TKN-SWITCH-PATH indicates that the SWITCH command is to switch processes between Communications Interface Unit (CIU) paths. It has one of the following values: ZCOM-VAL-PATH-A The processes are to be switched to path A. ZCOM-VAL-PATH-B The processes are to be switched to path B. For more information, refer to the SWITCH command in Section 7. ZCOM-TKN-TRACE-OPT indicates what items are to be traced by the TRACE command.
COMMON DEFINITIONS Common Definitions for the EXPAND Subsystem Information about EXPAND definitions that is specific to particular commands, responses, or event messages is discussed in Section 7, "Commands and Responses," and in Section 8, "Event Management." Buffer Declarations The EXPAND subsystem provides the following buffer declarations for message buffers that can be used with the SPI procedures. All applications should use one of these declarations for a buffer of the recommended size.
COMMON DEFINITIONS Private Token and Field Types Private Token and Field Types The EXPAND subsystem does not define any token or field types. Predefined Token and Field Values The EXPAND subsystem defines the following token and field values for use in more than one command, event message, or error list. ZEXP-VAL-ASCII represents the ASCII character set.
COMMON DEFINITIONS Predefined Token and Field Values structured tokens ZEXP-MAP-ALTER-LINE, ZEXP-MAP-INFO-LINE-HDLC, and ZEXP-MAP-INFO-LINE-CSM. For more information, see the ALTER LINE and INFO LINE commands in Section 7. ZEXP-VAL-RS422 represents the RS-422 hardware interface. It can occur as a value of the field ZINTERF of the extensible structured tokens ZEXP-MAP-ALTER-LINE, ZEXP-MAP-INFO-LINE-HDLC, and ZEXP-MAP-INFO-LINE-CSM.
COMMON DEFINITIONS Simple Tokens The following simple tokens appear in several EXPAND event messages. They are described later in this section under "Tokens in Event Messages." ZEXP-TKN-CIU-PATH indicates the CIU path. ZEXP-TKN-SYS-MSG-MODE indicates what software component the event message relates to. ZEXP-TKN-SYSNAME contains a system name. ZEXP-TKN-SYSNUM contains a system number. Extensible Structured Tokens The following extensible structured tokens appear in multiple EXPAND responses.
COMMON DEFINITIONS Extensible Structured Tokens 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 end.
COMMON DEFINITIONS Extensible Structured Tokens ZS-FRAMES-SENT contains the total number of S-frames sent. ZS-FRAMES-RECV contains the total number of S-frames received. ZU-FRAMES-SENT contains the total number of U-frames sent. ZU-FRAMES-RECV contains the total number of U-frames received. The following fields of ZEXP-MAP-STATS-LINE-CSM (fields ZBCC-ERRS through ZFRAMES-ERR) relate to the numbers of errors in received frames.
COMMON DEFINITIONS Extensible Structured Tokens ZL2-I-FRAMES-RECV contains the total number of I-frames without the poll bit set that have been received. ZL2-I-FRAMES-RECV-P contains the total number of I-frames with the poll bit set that have been received. ZL2-RR-FRAMES-SENT contains the total number of RR frames sent. ZL2-RNR-FRAMES-SENT contains the total number of RNR frames sent. ZL2-REJ-FRAMES-SENT contains the total number of REJ frames sent.
COMMON DEFINITIONS Extensible Structured Tokens ZL2-SREJ-FRAMES-SENT contains the total number of SREJ frames sent. ZL2-SREJ-FRAMES-RECV contains the total number of SREJ frames received. The following fields of ZEXP-MAP-STATS-LINE-CSM (fields ZL2-FCSERRS through ZL2-STATE-DSR) contain counts of errors on frames received from the modem that are reported by the HDLC protocol running in the CLIP. ZL2-FCS-ERRS contains the total number of FCS errors detected in driver frames received.
COMMON DEFINITIONS Extensible Structured Tokens def ZEXP-DDL-STATS-LINE-NCSM. 02 ZLAST-RESETSTATS-TMSTP 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 end.
COMMON DEFINITIONS Extensible Structured Tokens The following fields of ZEXP-MAP-STATS-LINE-NCSM (fields ZI-FRAMES-SENT through ZU-FRAMES-RECV) contain counts of the numbers of level-2 frames sent and received. ZI-FRAMES-SENT contains the total number of I-frames sent. ZI-FRAMES-RECV contains the total number of I-frames received. ZS-FRAMES-SENT contains the total number of S-frames sent. ZS-FRAMES-RECV contains the total number of S-frames received.
COMMON DEFINITIONS Extensible Structured Tokens The following fields of ZEXP-MAP-STATS-LINE-NCSM (fields ZL2-IFRAMES-SENT through ZL2-SREJ-FRAMES-RECV) contain a more detailed breakdown of the numbers of level-2 frames sent and received. ZL2-I-FRAMES-SENT contains the total number of I-frames without the poll bit set that have been sent. ZL2-I-FRAMES-SENT-P contains the total number of I-frames with the poll bit set that have been sent.
COMMON DEFINITIONS Extensible Structured Tokens ZL2-DM-FRAMES-SENT contains the total number of DM frames sent. ZL2-DM-FRAMES-RECV contains the total number of DM frames received. ZL2-RECV-OVERRUN contains the total number of frames received that were longer than the maximum frame size specified. ZL2-MODEM-ERRS contains the total number of modem errors. ZL2-SREJ-FRAMES-SENT contains the total number of SREJ frames sent. ZL2-SREJ-FRAMES-RECV contains the total number of SREJ frames received.
COMMON DEFINITIONS Extensible Structured Tokens 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 end.
COMMON DEFINITIONS Extensible Structured Tokens The following fields of ZEXP-MAP-STATS-PATH (fields ZL4-PKTSSENT through ZL4-REQ-RECV-ENQ) contain information about level-4 processing, which is related to the sending and receiving of requests and responses. ZL4-PKTS-SENT contains the total number of packets sent on this path. ZL4-PKTS-RECV contains the total number of packets received on this path.
COMMON DEFINITIONS Extensible Structured Tokens ZL4-REQ-RECV-NCP contains the total number of NCP messages received. ZL4-REQ-RECV-LRQ contains the total number of LRQ requests received. ZL4-REQ-RECV-LCMP contains the total number of LCMP requests received. ZL4-REQ-RECV-CANCEL contains the total number of cancel requests received. ZL4-REQ-RECV-ACK contains the total number of ACKs received. ZL4-REQ-RECV-NAK contains the total number of NAKs received.
COMMON DEFINITIONS Extensible Structured Tokens ZFRAMES-LE-4096 contains the number of messages sent and received by this node over this path whose size is less than or equal to 4096 bytes. ZFRAMES-GT-4096 contains the number of messages sent and received by this node over this path whose size is greater than 4096 bytes. ZOUT-OF-SEQ-POOL-CURR-USED contains the number of words of outof-sequence buffer pool currently being used.
COMMON DEFINITIONS Tokens in Error Lists ZEXP-TKN-LH-ERR-NUM contains a file-system error number returned by a line-handler process. ZEXP-TKN-NCP-ERR-NUM contains a file-system error number returned by the NCP. Tokens in Event Messages The following tokens appear in several event messages issued by the EXPAND subsystem. The EXPAND event messages are described in Section 8, "Event Management." ZEXP-TKN-CIU-PATH is a token that indicates the CIU path.
SECTION 7 COMMANDS AND RESPONSES This section describes the syntax and semantics for all commands and responses in the programmatic control-and-inquiry interface to the EXPAND subsystem.
COMMANDS AND RESPONSES Table 7-1.
COMMANDS AND RESPONSES Table 7-1.
COMMANDS AND RESPONSES Commands by Object Type The following commands accept the PATH object type: ABORT ALTER INFO RESETSTATS START STATISTICS STATUS STOP The following commands accept the PROCESS object type: ALTER GETVERSION INFO PROBE STATISTICS SWITCH TRACE SENSITIVE AND NONSENSITIVE COMMANDS Commands are divided into two groups based on whether or not a user must have proper security to be able to use the command. These two groups are called sensitive commands and nonsensitive commands.
COMMANDS AND RESPONSES Command Descriptions COMMAND DESCRIPTIONS On the following pages, each EXPAND command and its response is described in detail. The command descriptions appear in alphabetical order. Within each command description, there is a box that contains the symbolic name of the command number, the symbolic names of all object types accepted by the command, a list of tokens that can be present in the command buffer, and a list of tokens that can be present in the response buffer.
COMMANDS AND RESPONSES Command Descriptions Data lists and error lists are indicated in the box by following each of the tokens ZSPI-TKN-DATALIST and ZSPI-TKN-ERRLIST, respectively, by an ellipsis (...) and the token ZSPI-TKNENDLIST. The token ZSPI-TKN-ENDLIST is indented to show that it is present only if the list token is present. For more information on data lists and error lists, refer to the Distributed Systems Management (DSM) Programming Manual.
COMMANDS AND RESPONSES ABORT Command ABORT Command The ABORT command terminates the operation of one or more lines or paths as quickly as possible--only enough processing is done to ensure the integrity of the subsystem. Command ZCOM-CMD-ABORT Object Type ZCOM-OBJ-LINE or ZCOM-OBJ-PATH Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID.
COMMANDS AND RESPONSES ABORT Command ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process. This token must be present in the command, and duplicate occurrences are not allowed. ZSPI-TKN-MANAGER is described in the Distributed Systems Management (DSM) Programming Manual.
COMMANDS AND RESPONSES ABORT Command ZCOM-TKN-OBJTYPE is an object-type token that indicates the type of the object named in ZCOM-TKN-OBJNAME. This token can have the following values: ZCOM-OBJ-LINE The object is a line. ZCOM-OBJ-PATH The object is a path. ZCOM-TKN-OBJTYPE is present in every response record, and it is described in Section 6, "Common Definitions." ZSPI-TKN-RETCODE is the standard SPI return token described in the Distributed Systems Management (DSM) Programming Manual.
COMMANDS AND RESPONSES ABORT Command line or lines. If the object type is ZCOM-OBJ-PATH, execution of this command terminates activity on all lines associated with the specified path or paths. • The lines or paths are placed in the STOPPED summary state, and the CLIP remains loaded. • All activities being performed by the lines or paths are halted, and files and listings can be left in an inconsistent or incomplete state.
COMMANDS AND RESPONSES ALTER LINE Command ALTER LINE Command The ALTER LINE command changes the values of the attributes of one or more lines. Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-LINE Tokens in Command Buffer ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !r ZEXP-MAP-ALTER-LINE !r def ZEXP-DDL-ALTER-LINE. 02 ZADDR type ZSPI-DDL-INT-PAIR. 02 ZASSOC-DEV type ZSPI-DDL-DEVICE. 02 ZASSOC-SUBDEV type ZSPI-DDL-DEVICE. 02 ZAUTOLOAD type ZSPI-DDL-BOOLEAN. 02 ZCHARSET type ZSPI-DDL-ENUM.
COMMANDS AND RESPONSES ALTER LINE Command 02 02 end. ZXMIT-WINDOW ZWINDOW ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT type ZSPI-DDL-INT. type ZSPI-DDL-INT. !o !o token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID. 02 ZCRTPID 02 ZPAID end. ZSPI-TKN-MAXRESP ZSPI-TKN-CONTEXT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT !o type ZSPI-DDL-CRTPID. type ZSPI-DDL-INT. token-type token-type token-type token-type token-type !r !r ZSPI-TYP-INT.
COMMANDS AND RESPONSES ALTER LINE Command number ZEXP-TNM-ALTER-LINE and the DDL definition ZEXP-DDL-ALTERLINE. This token must be present in the command, and duplicate occurrences are not allowed. The attribute changes described by ZEXP-MAP-ALTER-LINE apply to all the lines whose names appear in the command. There is a field in ZEXP-MAP-ALTER-LINE for each line attribute that can be altered by the ALTER LINE command.
COMMANDS AND RESPONSES ALTER LINE Command ZCHARSET specifies the character set for the line. can have the following values: This field ZEXP-VAL-ASCII The character set for the line is ASCII. ZEXP-VAL-EBCDIC The character set for the line is EBCDIC. The character set is ASCII by default. This field corresponds to the SYSGEN modifiers ASCII and EBCDIC. ZCHARSET is valid for all line handlers except NAM line handlers. ZDELAY specifies the amount of time in microseconds between transmissions.
COMMANDS AND RESPONSES ALTER LINE Command ZPROG specifies the file name of the CLIP program to be downloaded. The default name is $SYSTEM.CSSnn.C9311P00. This field corresponds to the SYSGEN modifier PROGRAM. ZPROG is valid only for line handlers that are configured as HDLC Normal for 6100 CSS. ZREAD-BUFFS specifies the number of read buffers to allocate. This value must be in the range 1 through 7, except for satellite-efficient lines, where the range is from 1 to 63.
COMMANDS AND RESPONSES ALTER LINE Command corresponds to the SYSGEN modifier CLBSTATUSPROBETIME. ZTESTINTVL is valid only for line handlers that are configured as HDLC Normal for 6100 CSS. ZTHRES specifies the number of frames that must be sent and received before line quality is checked. This value must be in the range 100 through 16384, and the default value is 500. This field corresponds to the SYSGEN modifier LINEQUALITYTHRESHOLD.
COMMANDS AND RESPONSES ALTER LINE Command to the SYSGEN modifier TIMERRECONNECT. only for NAM line handlers. ZTIMER-RECONN is valid ZXMIT-WINDOW specifies the number of EXPAND packets the line handler can send to the NAM before it receives a reply. This value must be in the range 2 through 7. The default value is 7 for NETCLUSTER (FOX) lines and 2 for NETNAM (X.25) lines. This field corresponds to the SYSGEN modifier TXWINDOW. ZXMIT-WINDOW is valid only for NAM line handlers.
COMMANDS AND RESPONSES ALTER LINE Command ZSPI-TKN-RETCODE is the standard SPI return token described in the Distributed Systems Management (DSM) Programming Manual. Some values of RETCODE that are likely to occur in response to the ALTER LINE command are the following: 1 (ZEXP-ERR-TOO-MANY-OBJNAMES): were in the command. More than 30 object names 2 (ZEXP-ERR-NEG-LH-RSP): negative response. 3 (ZEXP-ERR-EMPT-RSP): returned. The empty response record is being 4 (ZEXP-ERR-TKN-CONFL): command.
COMMANDS AND RESPONSES ALTER LINE Command Error-Handling Notes • The error number ZEXP-ERR-NEG-LH-RSP can signify either of the following two errors: -- An attempt was made to alter an attribute that is not valid for the line. Refer to Appendix C for a table that lists the applicable line attributes for the different types of line handlers. -- The line was not in the STOPPED summary state when the ALTER LINE command was issued.
COMMANDS AND RESPONSES ALTER PATH Command ALTER PATH Command The ALTER PATH command changes the values of the attributes of one or more paths. Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-PATH Tokens in Command Buffer ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !r ZEXP-MAP-ALTER-PATH !r def ZEXP-DDL-ALTER-PATH. 02 ZCMPRSS type ZSPI-DDL-BOOLEAN. 02 ZNEXT-SYS type ZSPI-DDL-INT spi-null 255. 02 ZOUT-OF-SEQ-SPACE type ZSPI-DDL-INT. 02 ZOUT-OF-SEQ-TIMEOUT type ZSPI-DDL-TIMESTAMP.
COMMANDS AND RESPONSES ALTER PATH Command ZSPI-TKN-COMMENT token-type ZSPI-TYP-STRING. !o Tokens in Response Buffer ZSPI-TKN-DATALIST ... ZSPI-TKN-ENDLIST ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type ZSPI-TYP-LIST. token-type token-type token-type token-type token-type ZSPI-TYP-SSCTL. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING.
COMMANDS AND RESPONSES ALTER PATH Command ZEXP-MAP-ALTER-PATH contains the following fields: ZCMPRSS specifies whether or not compression of outgoing messages is to be enabled. ZCMPRSS can have the following values: ZSPI-VAL-TRUE Enable compression of outgoing messages. ZSPI-VAL-FALSE Disable compression of outgoing messages. Compression of outgoing messages is enabled by default. This field corresponds to the SYSGEN modifiers COMPRESS and NOCOMPRESS.
COMMANDS AND RESPONSES ALTER PATH Command (ZSPI-TKN-) MAXRESP, CONTEXT, RESPONSE-TYPE, ALLOW-TYPE, and COMMENT are standard SPI tokens described in the Distributed Systems Management (DSM) Programming Manual. With the exception of ZSPI-TKN-COMMENT, duplicate occurrences of these tokens are not allowed. Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST.
COMMANDS AND RESPONSES ALTER PATH Command ZSPI-TKN-CONTEXT is the standard SPI context token described in the Distributed Systems Management (DSM) Programming Manual. Operational Notes • ALTER PATH is a sensitive command. • The path must be in the STOPPED summary state. • To obtain the current values of the attributes of a path, use the INFO PATH command. • No summary-state transition is associated with this command.
COMMANDS AND RESPONSES ALTER PROCESS Command ALTER PROCESS Command The ALTER PROCESS command changes the values of the attributes of one or more EXPAND line-handler processes. Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !r ZEXP-MAP-ALTER-PROC !r def ZEXP-DDL-ALTER-PROC. 02 ZDEBUG type ZSPI-DDL-BOOLEAN. end. ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT !o token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP.
COMMANDS AND RESPONSES ALTER PROCESS Command ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... 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 ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process.
COMMANDS AND RESPONSES ALTER PROCESS Command altered. This token must be present in the command, and from 1 through 30 object names are allowed. ZCOM-TKN-OBJNAME is described in Section 6, "Common Definitions." ZCOM-TKN-CMD-TIMEOUT and ZCOM-MAP-REQID are standard datacommunications tokens that are described in the Communications Management Programming Manual. Duplicate occurrences of these tokens are not allowed.
COMMANDS AND RESPONSES ALTER PROCESS Command For command-specific information about these error numbers, see "Error-Handling Notes" below. For descriptions of all EXPAND error numbers and their associated error lists, refer to Appendix A. ZSPI-TKN-ERRLIST is a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST.
COMMANDS AND RESPONSES GETVERSION Command (EXPAND Manager Process) GETVERSION Command (EXPAND Manager Process) This version of the GETVERSION command returns the server version and server-banner string of the EXPAND manager process. Command ZCOM-CMD-GETVERSION Object Type None or ZCOM-OBJ-NULL Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !o token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID.
COMMANDS AND RESPONSES GETVERSION Command (EXPAND Manager Process) ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process. This token must be present in the command, and duplicate occurrences are not allowed. ZSPI-TKN-MANAGER is described in the Distributed Systems Management (DSM) Programming Manual.
COMMANDS AND RESPONSES GETVERSION Command (EXPAND Manager Process) ZSPI-TKN-RETCODE is the standard SPI return token described in the Distributed Systems Management (DSM) Programming Manual. Some values of RETCODE that are likely to occur in response to this version of the GETVERSION command are the following: 1 (ZEXP-ERR-TOO-MANY-OBJNAMES): were in the command. 2 (ZEXP-ERR-NEG-LH-RSP): negative response. 3 (ZEXP-ERR-EMPT-RSP): returned.
COMMANDS AND RESPONSES GETVERSION Command (Lines and Paths) GETVERSION Command (Lines and Paths) This version of the GETVERSION command returns the server version of the EXPAND manager process and the server-banner string of one or more lines or paths. Command ZCOM-CMD-GETVERSION Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP.
COMMANDS AND RESPONSES GETVERSION Command (Lines and Paths) Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process. This token must be present in the command, and duplicate occurrences are not allowed. ZSPI-TKN-MANAGER is described in the Distributed Systems Management (DSM) Programming Manual. ZCOM-TKN-OBJNAME is an object-name token that contains the name of a line or path whose server-banner string is to be returned.
COMMANDS AND RESPONSES GETVERSION Command (Lines and Paths) 3 (ZEXP-ERR-EMPT-RSP): returned. The empty response record is being For descriptions of all EXPAND error numbers and their associated error lists, refer to Appendix A. ZSPI-TKN-ERRLIST is a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST.
COMMANDS AND RESPONSES INFO LINE Command INFO LINE Command The INFO LINE command returns the current values of the attributes of one or more lines. Command ZCOM-CMD-INFO Object Type ZCOM-OBJ-LINE Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID. 02 ZCRTPID 02 ZPAID end.
COMMANDS AND RESPONSES INFO LINE Command 02 02 02 02 02 02 02 02 02 02 02 end. ZFRAME-SIZE ZIDLE-TIMEOUT ZINTERF ZREAD-BUFFS ZRETRIES ZSPEED ZSYNCS ZTHRES ZTIMEOUT ZWINDOW ZTYPE type type type type type type type type type type type ZSPI-DDL-INT. ZSPI-DDL-INT2. ZSPI-DDL-ENUM. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT2. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT2. ZSPI-DDL-INT. ZSPI-DDL-INT-PAIR. def ZEXP-DDL-INFO-LINE-CSM.
COMMANDS AND RESPONSES INFO LINE Command 02 02 02 02 02 02 02 end. ZTIMEOUT ZTIMER-BIND ZTIMER-INACTV ZTIMER-PROBE ZTIMER-RECONN ZXMIT-WINDOW ZTYPE ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT type type type type type type type ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT. ZSPI-DDL-INT-PAIR. token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST.
COMMANDS AND RESPONSES INFO LINE Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZEXP-MAP-INFO-LINE-HDLC, ZEXP-MAP-INFO-LINE-CSM, and ZEXP-MAPINFO-LINE-NAM are all extensible structured tokens that contain the current values of the attributes of a line. Only one of these tokens is present in each response record.
COMMANDS AND RESPONSES INFO LINE Command This field corresponds to the SYSGEN modifiers RS232 and RS422. It does not apply to lines attached to a multifunction controller. ZREAD-BUFFS contains the number of read buffers allocated. This field corresponds to the SYSGEN modifier READBUFFERS. ZRETRIES contains the number of level-2 retries that are attempted before a failure is reported. This field corresponds to the SYSGEN modifier L2RETRIES. ZSPEED contains the baud rate of the line handler.
COMMANDS AND RESPONSES INFO LINE Command ZSPI-VAL-FALSE Automatic downloading of the CLIP is disabled. This field corresponds to the SYSGEN modifiers AUTOLOAD and NOAUTOLOAD. ZCHARSET contains a value indicating the character set for the line. This field can have the following values: ZEXP-VAL-ASCII The character set for the line is ASCII. ZEXP-VAL-EBCDIC The character set for the line is EBCDIC. This field corresponds to the SYSGEN modifiers ASCII and EBCDIC.
COMMANDS AND RESPONSES INFO LINE Command ZRETRIES contains the number of level-2 retries that are attempted before a failure is reported. This field corresponds to the SYSGEN modifier L2RETRIES. ZSPEED contains the baud rate of the line handler. corresponds to the SYSGEN modifier LINESPEED. This field ZSYNCS contains the number of leading sync characters transmitted before each frame. This field corresponds to the SYSGEN modifier SYNCS.
COMMANDS AND RESPONSES INFO LINE Command ZMAX-RECONNS contains the maximum number of times a network connection is attempted. This field corresponds to the SYSGEN modifier MAXRECONNECTS. ZRETRY-PROBE contains the number of times the line handler will retry its probe of the NAM before it considers the network to be unavailable. This field corresponds to the SYSGEN modifier RETRYPROBE.
COMMANDS AND RESPONSES INFO LINE Command ZCOM-TKN-OBJTYPE is an object-type token that contains the value ZCOM-OBJ-LINE. This token is present in every response record, and it is described in Section 6, "Common Definitions." ZSPI-TKN-RETCODE is the standard SPI return token described in the Distributed Systems Management (DSM) Programming Manual. Some values of RETCODE that are likely to occur in response to the INFO LINE command are the following: 1 (ZEXP-ERR-TOO-MANY-OBJNAMES): were in the command.
COMMANDS AND RESPONSES INFO LINE Command • Using the token ZSPI-TKN-RESPONSE-TYPE in the command to request the return of only those response records for lines on which errors or warnings occurred can result in no information being returned. • No summary-state transition is associated with this command.
COMMANDS AND RESPONSES INFO PATH Command INFO PATH Command The INFO PATH command returns the current values of the attributes of one or more paths. Command ZCOM-CMD-INFO Object Type ZCOM-OBJ-PATH Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID. 02 ZCRTPID 02 ZPAID end.
COMMANDS AND RESPONSES INFO PATH Command 02 02 02 02 02 02 end. ZOUT-OF-SEQ-SPACE type ZOUT-OF-SEQ-TIMEOUT type ZRETRIES type ZTIME-FACT type ZTIMEOUT type ZTYPE type ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT ZSPI-DDL-INT. ZSPI-DDL-INT2. ZSPI-DDL-INT. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT-PAIR. token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL.
COMMANDS AND RESPONSES INFO PATH Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZEXP-MAP-INFO-PATH is an extensible structured token that contains the current values of the attributes of the path. It has the token number ZEXP-TNM-INFO-PATH and the DDL definition ZEXPDDL-INFO-PATH. This token is present in every response record.
COMMANDS AND RESPONSES INFO PATH Command ZTYPE is a pair of integers containing the device type and subtype of the path. The two integers of ZTYPE correspond to the SYSGEN modifiers TYPE and SUBTYPE. ZCOM-TKN-OBJNAME is an object-name token that contains the name of the path whose attribute values are returned in this response record. This token is present in every response record. ZCOMTKN-OBJNAME is described in Section 6, "Common Definitions.
COMMANDS AND RESPONSES INFO PATH Command • To obtain statistical information about a path, use the STATISTICS PATH command or the RESETSTATS PATH command. • Using the token ZSPI-TKN-RESPONSE-TYPE in the command to request the return of only those response records for paths on which errors or warnings occurred can result in no information being returned. • No summary-state transition is associated with this command.
COMMANDS AND RESPONSES INFO PROCESS Command INFO PROCESS Command The INFO PROCESS command performs one of two functions: • It provides network map and/or path map information about a specified system (the selected system) as seen from another system (the called system). • It returns the current values of the attributes of one or more EXPAND line-handler processes. Command ZCOM-CMD-INFO Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.
COMMANDS AND RESPONSES INFO PROCESS Command Tokens in Response Buffer ZSPI-TKN-DATALIST ... ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. ZEXP-MAP-INFO-NCP-NETMAP def ZEXP-DDL-INFO-NCP-NETMAP. 02 ZCALLED-SYS type ZSPI-DDL-INT. 02 ZSEL-SYS type ZSPI-DDL-INT. 02 ZNUM-OF-PATH type ZSPI-DDL-INT. 02 ZNSCB-TOSVERSION type ZSPI-DDL-INT. 02 ZCONN-PATH type ZSPI-DDL-INT. 02 ZCONN-STATE type ZSPI-DDL-ENUM. 02 ZSYS-DIST-ENT occurs 40 times. 03 ZPATH-NUM type ZSPI-DDL-INT.
COMMANDS AND RESPONSES INFO PROCESS Command ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... 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 ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process.
COMMANDS AND RESPONSES INFO PROCESS Command meaningless and must not be present. not allowed. Duplicate occurrences are ZCOM-TKN-OBJNAME is an object-name token. If ZEXP-TKN-INFO-NCPOPT is present, this token must contain the process name "$NCP". If ZEXP-TKN-INFO-NCP-OPT is not present, this token contains the object name of a line-handler process whose attribute values are to be returned.
COMMANDS AND RESPONSES INFO PROCESS Command ZCONN-PATH is the path number of the path through which the called system and the selected system are currently connected or are connecting, depending on the value of ZCONN-STATE. A value of 0 means that there is no path between the two systems. ZCONN-STATE is the connection state of the path identified in ZCONN-PATH. This field can have the following values: ZEXP-VAL-PATH-CONNECTED The path is in the connected state.
COMMANDS AND RESPONSES INFO PROCESS Command ZPATH-ENT (path entry) is a structure that contains information describing a particular path to the called system. This structure is repeated 40 times. It contains the following fields: ZPATH-NUM is the path number of this path. ZNOPASS-THRU is reserved for Tandem use only. ZNEIGHBOR-NUM is the system number of the system immediately adjacent to the called system over this path. ZPATH-LDEV is the logical device (LDEV) number of this path.
COMMANDS AND RESPONSES INFO PROCESS Command ZEXP-MAP-INFO-PROC is an extensible structured token that contains the current values of the attributes of the line-handler process. It has the token number ZEXP-TNM-INFO-PROC and the DDL definition ZEXP-DDL-INFO-PROC. This token is present if and only if ZEXP-TKN-INFO-NCP-OPT was not present in the command. ZEXP-MAP-INFO-PROC contains the following fields: ZDEBUG indicates whether or not the CLIP DEBUG interface is enabled.
COMMANDS AND RESPONSES INFO PROCESS Command ZSPI-TKN-ERRLIST is a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZSPI-TKN-CONTEXT is the standard SPI context token described in the Distributed Systems Management (DSM) Programming Manual. Operational Notes • All users can issue the INFO PROCESS command. • To change the values of the attributes of a line-handler process, use the ALTER PROCESS command.
COMMANDS AND RESPONSES LOAD Command LOAD Command The LOAD command causes downloading of the CLIP associated with an EXPAND line. Command ZCOM-CMD-LOAD Object Type ZCOM-OBJ-LINE Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID. 02 ZCRTPID 02 ZPAID end.
COMMANDS AND RESPONSES LOAD Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process. This token must be present in the command, and duplicate occurrences are not allowed. ZSPI-TKN-MANAGER is described in the Distributed Systems Management (DSM) Programming Manual. ZCOM-TKN-OBJNAME is an object-name token that contains the name of a line to be loaded.
COMMANDS AND RESPONSES LOAD Command 2 (ZEXP-ERR-NEG-LH-RSP): negative response. The EXPAND line handler returned a 3 (ZEXP-ERR-EMPT-RSP): returned. 5 (ZEXP-ERR-OBJ-TYPE-NAME-MISMATC): A conflict exists between the object type and an object name. The empty response record is being For descriptions of all EXPAND error numbers and their associated error lists, refer to Appendix A.
COMMANDS AND RESPONSES PROBE Command PROBE Command The PROBE command returns information about the current paths from other systems to a selected system. Command ZCOM-CMD-PROBE Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !r ZEXP-TKN-CALLED-SYS ZEXP-TKN-SEL-SYS token-type ZSPI-TYP-INT. token-type ZSPI-TYP-INT. !r !r ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP.
COMMANDS AND RESPONSES PROBE Command ZEXP-MAP-PROBE-NCP def ZEXP-DDL-PROBE-NCP. 02 ZTRIP-TIME type ZSPI-DDL-INT2. 02 ZNUM-OF-SYS type ZSPI-DDL-INT. 02 ZSYS-LIST type ZSPI-DDL-INT occurs ZEXP-VAL-MAX-SYSTEMS times. 02 ZCALLED-SYS type ZSPI-DDL-INT. 02 ZSEL-SYS type ZSPI-DDL-INT. end. ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... 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.
COMMANDS AND RESPONSES PROBE Command ZCOM-TKN-CMD-TIMEOUT and ZCOM-MAP-REQID are standard datacommunications tokens that are described in the Communications Management Programming Manual. Duplicate occurrences of these tokens are not allowed. (ZSPI-TKN-) MAXRESP, CONTEXT, RESPONSE-TYPE, ALLOW-TYPE, and COMMENT are standard SPI tokens described in the Distributed Systems Management (DSM) Programming Manual. With the exception of ZSPI-TKN-COMMENT, duplicate occurrences of these tokens are not allowed.
COMMANDS AND RESPONSES PROBE Command ZCOM-TKN-OBJNAME is an object-name token that contains the process name "$NCP". This token is always present in the response. ZCOM-TKN-OBJNAME is described in Section 6, "Common Definitions." ZCOM-TKN-OBJTYPE is an object-type token that contains the value ZCOM-OBJ-PROCESS. This token is always present in the response, and it is described in Section 6, "Common Definitions.
COMMANDS AND RESPONSES RESET Command RESET Command The RESET command causes the CLIP associated with an EXPAND line to be placed in the boot state for downloading. Command ZCOM-CMD-RESET Object Type ZCOM-OBJ-LINE Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID. 02 ZCRTPID 02 ZPAID end.
COMMANDS AND RESPONSES RESET Command Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process. This token must be present in the command, and duplicate occurrences are not allowed. ZSPI-TKN-MANAGER is described in the Distributed Systems Management (DSM) Programming Manual. ZCOM-TKN-OBJNAME is an object-name token that contains the name of a line to be reset.
COMMANDS AND RESPONSES RESET Command 2 (ZEXP-ERR-NEG-LH-RSP): negative response. The EXPAND line handler returned a 3 (ZEXP-ERR-EMPT-RSP): returned. 5 (ZEXP-ERR-OBJ-TYPE-NAME-MISMATC): A conflict exists between the object type and an object name. The empty response record is being For descriptions of all EXPAND error numbers and their associated error lists, refer to Appendix A.
COMMANDS AND RESPONSES RESETSTATS LINE Command RESETSTATS LINE Command The RESETSTATS LINE command returns statistical information about the execution history of one or more lines--dynamic information such as request counts, numbers of errors, and so forth--and then restores the statistics counters to their initial values. Command ZCOM-CMD-RESETSTATS Object Type ZCOM-OBJ-LINE Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32.
COMMANDS AND RESPONSES RESETSTATS LINE Command ZEXP-MAP-STATS-LINE-CSM def ZEXP-DDL-STATS-LINE-CSM.
COMMANDS AND RESPONSES RESETSTATS LINE Command 02 02 02 end. ZL2-STATE-DSR ZLINE-PPID ZLINE-BPID type ZSPI-DDL-BYTE. type ZSPI-DDL-INT-PAIR. type ZSPI-DDL-INT-PAIR. ZEXP-MAP-STATS-LINE-NCSM def ZEXP-DDL-STATS-LINE-NCSM.
COMMANDS AND RESPONSES RESETSTATS LINE Command ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... 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 ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process.
COMMANDS AND RESPONSES RESETSTATS LINE Command ZEXP-MAP-STATS-LINE-CSM and ZEXP-MAP-STATS-LINE-NCSM are extensible structured tokens that contain the statistical information for a line. Only one of these tokens is present in each response record. ZEXP-MAP-STATS-LINE-CSM is present when the line handler is configured as HDLC Normal for 6100 CSS; otherwise, ZEXP-MAPSTATS-LINE-NCSM is present. These tokens are fully described in Section 6, "Common Definitions.
COMMANDS AND RESPONSES RESETSTATS LINE Command Operational Notes • RESETSTATS LINE is a sensitive command. • The statistical information returned by the RESETSTATS LINE command for FOX (NETCLUSTER) and X.25 (NETNAM) lines is always all zeros, because the EXPAND subsystem does not control level-2 operations on such lines. • The RESETSTATS LINE command updates the reset-timestamp counters when it clears the statistics counters.
COMMANDS AND RESPONSES RESETSTATS PATH Command RESETSTATS PATH Command The RESETSTATS PATH command returns statistical information about the execution history of one or more paths--dynamic information such as request counts, numbers of errors, and so forth--and then restores the statistics counters to their initial values. Command ZCOM-CMD-RESETSTATS Object Type ZCOM-OBJ-PATH Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32.
COMMANDS AND RESPONSES RESETSTATS PATH Command ZEXP-MAP-STATS-PATH def ZEXP-DDL-STATS-PATH.
COMMANDS AND RESPONSES RESETSTATS PATH Command 02 02 02 02 end. ZLOC-POOL-FAILS ZKNOWN-SYS ZPATH-PPID ZPATH-BPID ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT type type type type token-type token-type token-type token-type ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT-PAIR. ZSPI-DDL-INT-PAIR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING.
COMMANDS AND RESPONSES RESETSTATS PATH Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZEXP-MAP-STATS-PATH is an extensible structured token that contains the statistical information for the path. This token is present in every response record, and it is fully described in Section 6, "Common Definitions.
COMMANDS AND RESPONSES RESETSTATS PATH Command Operational Notes • RESETSTATS PATH is a sensitive command. • The RESETSTATS PATH command updates the reset-timestamp counters when it clears the statistics counters. • To obtain statistical information about a path without clearing the statistics counters, use the STATISTICS PATH command. • To obtain information about the current state of a path, use the STATUS PATH command.
COMMANDS AND RESPONSES START Command START Command The START command initiates the operation of one or more lines or paths. Command ZCOM-CMD-START Object Type ZCOM-OBJ-LINE or ZCOM-OBJ-PATH Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID. 02 ZCRTPID 02 ZPAID end.
COMMANDS AND RESPONSES START Command ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process. This token must be present in the command, and duplicate occurrences are not allowed. ZSPI-TKN-MANAGER is described in the Distributed Systems Management (DSM) Programming Manual.
COMMANDS AND RESPONSES START Command ZCOM-TKN-OBJTYPE is an object-type token that indicates the type of the object named in ZCOM-TKN-OBJNAME. This token can have the following values: ZCOM-OBJ-LINE The object is a line. ZCOM-OBJ-PATH The object is a path. ZCOM-TKN-OBJTYPE is present in every response record, and it is described in Section 6, "Common Definitions." ZSPI-TKN-RETCODE is the standard SPI return token described in the Distributed Systems Management (DSM) Programming Manual.
COMMANDS AND RESPONSES START Command ZCOM-OBJ-PATH, all lines associated with the specified path or paths are started. • Successful completion of the START command leaves the lines or paths in the STARTED summary state. Unsuccessful completion of the START command leaves the lines or paths in the STOPPED summary state. • If the CLIP is in the boot state, a download of the CLIP software is performed.
COMMANDS AND RESPONSES STATISTICS LINE Command STATISTICS LINE Command The STATISTICS LINE command returns statistical information about the execution history of one or more lines--dynamic information such as request counts, numbers of errors, and so forth. Command ZCOM-CMD-STATISTICS Object Type ZCOM-OBJ-LINE Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP.
COMMANDS AND RESPONSES STATISTICS LINE Command ZEXP-MAP-STATS-LINE-CSM def ZEXP-DDL-STATS-LINE-CSM.
COMMANDS AND RESPONSES STATISTICS LINE Command 02 02 02 end. ZL2-STATE-DSR ZLINE-PPID ZLINE-BPID type ZSPI-DDL-BYTE. type ZSPI-DDL-INT-PAIR. type ZSPI-DDL-INT-PAIR. ZEXP-MAP-STATS-LINE-NCSM def ZEXP-DDL-STATS-LINE-NCSM.
COMMANDS AND RESPONSES STATISTICS LINE Command ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... 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 ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process.
COMMANDS AND RESPONSES STATISTICS LINE Command response record. ZEXP-MAP-STATS-LINE-CSM is present if the line handler is configured as HDLC Normal for 6100 CSS; otherwise, ZEXP-MAP-STATS-LINE-NCSM is present. These tokens are fully described in Section 6, "Common Definitions." ZCOM-TKN-OBJNAME is an object-name token that contains the name of the line whose statistics are returned in this response record. This token is present in every response record.
COMMANDS AND RESPONSES STATISTICS LINE Command • To obtain statistical information about a line and then restore the statistics counters to their initial values, use the RESETSTATS LINE command. • To obtain information about the current state of a line, use the STATUS LINE command. • To obtain the values of the attributes of a line, use the INFO LINE command.
COMMANDS AND RESPONSES STATISTICS PATH Command STATISTICS PATH Command The STATISTICS PATH command returns statistical information about the execution history of one or more paths--dynamic information such as request counts, numbers of errors, and so forth. Command ZCOM-CMD-STATISTICS Object Type ZCOM-OBJ-PATH Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP.
COMMANDS AND RESPONSES STATISTICS PATH Command ZEXP-MAP-STATS-PATH def ZEXP-DDL-STATS-PATH.
COMMANDS AND RESPONSES STATISTICS PATH Command 02 02 02 02 02 end. ZLOC-POOL-PAGES ZLOC-POOL-FAILS ZKNOWN-SYS ZPATH-PPID ZPATH-BPID ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT type type type type type token-type token-type token-type token-type ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT-PAIR. ZSPI-DDL-INT-PAIR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL.
COMMANDS AND RESPONSES STATISTICS PATH Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZEXP-MAP-STATS-PATH is an extensible structured token that contains the statistical information for the path. This token is present in every response record, and it is fully described in Section 6, "Common Definitions.
COMMANDS AND RESPONSES STATISTICS PATH Command Operational Notes • All users can issue the STATISTICS PATH command. • To obtain statistical information about a path and then restore the statistics counters to their initial values, use the RESETSTATS PATH command. • To obtain information about the current state of a path, use the STATUS PATH command. • To obtain the values of the attributes of a path, use the INFO PATH command.
COMMANDS AND RESPONSES STATISTICS PROCESS Command STATISTICS PROCESS Command The STATISTICS PROCESS command returns statistical information from the Network Utility Program, $ZNUP (this information was formerly collected by the NCP), concerning one of the following: • The communication between two specified systems • Network traffic passing through a specified system Command ZCOM-CMD-STATISTICS Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.
COMMANDS AND RESPONSES STATISTICS PROCESS Command Tokens in Response Buffer ZSPI-TKN-DATALIST ... ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. ZEXP-MAP-SYS-STATS-NCP def ZEXP-DDL-SYS-STATS-NCP. 02 ZLINK-SENT type 02 ZLINK-RECV type 02 ZPKTS-SENT type 02 ZPKTS-RECV type 02 ZCALLED-SYS type 02 ZSEL-SYS type end. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT. ZSPI-DDL-INT. ZEXP-MAP-PKTS-STATS-NCP def ZEXP-DDL-PKTS-STATS-NCP.
COMMANDS AND RESPONSES STATISTICS PROCESS Command ZEXP-TKN-STATS-NCP-OPT, if present, specifies whether the command is to return statistics about the communication between two specified systems or statistics about network traffic passing through a specified system. It has the token number ZEXP-TNMSTATS-NCP-OPT and the token type ZSPI-TYP-ENUM. This token must be present in the command, and duplicate occurrences are not allowed.
COMMANDS AND RESPONSES STATISTICS PROCESS Command ZEXP-MAP-SYS-STATS-NCP is an extensible structured token that contains statistics information about the communication between the called system and the selected system. It has the token number ZEXP-TNM-SYS-STATS-NCP and the DDL definition ZEXP-DDLSYS-STATS-NCP. This token is present if and only if ZEXP-TKNSTATS-NCP-OPT was present in the command and had a value of ZEXPVAL-SYS-STATS.
COMMANDS AND RESPONSES STATISTICS PROCESS Command ZCOM-TKN-OBJNAME is an object-name token that contains the process name "$NCP". This token is always present in the response. ZCOM-TKN-OBJNAME is described in Section 6, "Common Definitions." ZCOM-TKN-OBJTYPE is an object-type token that contains the value ZCOM-OBJ-PROCESS. This token is always present in the response, and it is described in Section 6, "Common Definitions.
COMMANDS AND RESPONSES STATUS LINE Command STATUS LINE Command The STATUS LINE command returns information about the current state of one or more lines--information such as the summary state of the line, the CLIP path being used, and so forth. Command ZCOM-CMD-STATUS Object Type ZCOM-OBJ-LINE Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID.
COMMANDS AND RESPONSES STATUS LINE Command 02 02 02 02 02 02 02 end. ZPATH type ZPRIM-SUBCHNL-ADDR type ZBKUP-SUBCHNL-ADDR type ZCSM-LDEV type ZPATH-LDEV type ZLINE-PPID type ZLINE-BPID type ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT-PAIR. ZSPI-DDL-INT-PAIR. token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM.
COMMANDS AND RESPONSES STATUS LINE Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZEXP-MAP-STATUS-LINE is an extensible structured token that describes the current state of the line. It has the token number ZEXP-TNM-STATUS-LINE and the DDL definition ZEXP-DDL-STATUS-LINE. This token is present in every response record.
COMMANDS AND RESPONSES STATUS LINE Command ZCOM-TKN-OBJNAME is an object-name token that contains the name of the line whose status is returned in this response record. This token is present in every response record. ZCOM-TKN-OBJNAME is described in Section 6, "Common Definitions." ZCOM-TKN-OBJTYPE is an object-type token that contains the value ZCOM-OBJ-LINE. This token is present in every response record, and it is described in Section 6, "Common Definitions.
COMMANDS AND RESPONSES STATUS LINE Command • Using the token ZSPI-TKN-RESPONSE-TYPE in the command to request the return of only those response records for lines on which errors or warnings occurred can result in no information being returned. • No summary-state transition is associated with this command.
COMMANDS AND RESPONSES STATUS PATH Command STATUS PATH Command The STATUS PATH command returns information about the current state of one or more paths--information such as the summary state of the path, the number of lines in the path, and so forth. Command ZCOM-CMD-STATUS Object Type ZCOM-OBJ-PATH Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP.
COMMANDS AND RESPONSES STATUS PATH Command 02 02 02 02 02 end. ZCLIP ZTOTAL-LINES ZLDEV ZPATH-PPID ZPATH-BPID ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT type ZSPI-DDL-BOOLEAN. type ZSPI-DDL-INT. type ZSPI-DDL-INT occurs 8 times. type ZSPI-DDL-INT-PAIR. type ZSPI-DDL-INT-PAIR. token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING.
COMMANDS AND RESPONSES STATUS PATH Command Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZEXP-MAP-STATUS-PATH is an extensible structured token that describes the current state of the path. It has the token number ZEXP-TNM-STATUS-PATH and the DDL definition ZEXP-DDL-STATUS-PATH. This token is present in every response record.
COMMANDS AND RESPONSES STATUS PATH Command ZSPI-TKN-RETCODE is the standard SPI return token described in the Distributed Systems Management (DSM) Programming Manual. Some values of RETCODE that are likely to occur in response to the STATUS PATH command are the following: 1 (ZEXP-ERR-TOO-MANY-OBJNAMES): were in the command. More than 30 object names 2 (ZEXP-ERR-NEG-LH-RSP): negative response. 3 (ZEXP-ERR-EMPT-RSP): returned.
COMMANDS AND RESPONSES STOP Command STOP Command The STOP command terminates the operation of one or more lines or paths if they have no connections to other systems. Command ZCOM-CMD-STOP Object Type ZCOM-OBJ-LINE or ZCOM-OBJ-PATH Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING. !r token-type ZSPI-TYP-TIMESTAMP. !o ZCOM-MAP-REQID def ZCOM-DDL-REQID. 02 ZCRTPID 02 ZPAID end.
COMMANDS AND RESPONSES STOP Command ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process. This token must be present in the command, and duplicate occurrences are not allowed. ZSPI-TKN-MANAGER is described in the Distributed Systems Management (DSM) Programming Manual.
COMMANDS AND RESPONSES STOP Command ZCOM-TKN-OBJTYPE is an object-type token that indicates the type of the object named in ZCOM-TKN-OBJNAME. This token can have the following values: ZCOM-OBJ-LINE The object is a line. ZCOM-OBJ-PATH The object is a path. ZCOM-TKN-OBJTYPE is present in every response record, and it is described in Section 6, "Common Definitions." ZSPI-TKN-RETCODE is the standard SPI return token described in the Distributed Systems Management (DSM) Programming Manual.
COMMANDS AND RESPONSES STOP Command ZCOM-OBJ-PATH, all lines associated with the specified path or paths are stopped. • The lines or paths are left in the STOPPED summary state. • The only lines affected by the execution of this command are those for which the level-2 state is not READY. • To terminate lines or paths immediately, without waiting for processing to complete and regardless of whether or not there are connections to other systems, use the ABORT command.
COMMANDS AND RESPONSES SWITCH Command SWITCH Command The SWITCH command switches one or more line-handler processes either between two processors or between two Communications Interface Unit (CIU) paths. Command ZCOM-CMD-SWITCH Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-SWITCH-CPU ZCOM-TKN-SWITCH-PATH ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-INT. !(see text) token-type ZSPI-TYP-ENUM.
COMMANDS AND RESPONSES SWITCH Command ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type ZSPI-TYP-ENUM. token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-BYTESTRING. Tokens in Command Buffer ZSPI-TKN-MANAGER is a standard SPI manager token that contains the file name of the EXPAND manager process. This token must be present in the command, and duplicate occurrences are not allowed.
COMMANDS AND RESPONSES SWITCH Command (ZSPI-TKN-) MAXRESP, CONTEXT, RESPONSE-TYPE, ALLOW-TYPE, and COMMENT are standard SPI tokens described in the Distributed Systems Management (DSM) Programming Manual. With the exception of ZSPI-TKN-COMMENT, duplicate occurrences of these tokens are not allowed. Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST.
COMMANDS AND RESPONSES SWITCH Command ZSPI-TKN-CONTEXT is the standard SPI context token described in the Distributed Systems Management (DSM) Programming Manual. Operational Notes • SWITCH is a sensitive command. • To determine which processor is currently being used by a process, use the PUP command LISTDEV. • To determine which CIU path is currently being used by a process, use the STATUS LINE command. • No summary-state transition is associated with this command.
COMMANDS AND RESPONSES TRACE Command (EXPAND Manager Process) TRACE Command (EXPAND Manager Process) This form of the TRACE command initiates, modifies, or terminates trace mode on the EXPAND manager process. When trace mode is started on an object, trace data, as specified in the TRACE command, is collected in a special trace file. This data can later be formatted and displayed using the PTRACE program, as described in the PTRACE Reference Manual.
COMMANDS AND RESPONSES TRACE Command (EXPAND Manager Process) 02 02 end. ZCOLL ZFNAME ZCOM-TKN-TRACE-OPT ZSPI-TKN-MAXRESP ZSPI-TKN-CONTEXT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT type ZSPI-DDL-BOOLEAN. type ZSPI-DDL-FNAME32. token-type token-type token-type token-type token-type token-type !r !r ZSPI-TYP-ENUM. !r ZSPI-TYP-INT. !o ZSPI-TYP-BYTESTRING.!o ZSPI-TYP-ENUM. !o ZSPI-TYP-ENUM. !o ZSPI-TYP-STRING. !o Tokens in Response Buffer ZSPI-TKN-DATALIST ...
COMMANDS AND RESPONSES TRACE Command (EXPAND Manager Process) ZCOM-MAP-TRACE-MODIF is a standard data-communications extensible structured token described in the Communications Management Programming Manual. This token must be present in the command, and duplicate occurrences are not allowed. ZCOM-TKN-TRACE-OPT is a standard data-communications token described in the Communications Management Programming Manual. This token must be present in the command.
COMMANDS AND RESPONSES TRACE Command (EXPAND Manager Process) Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is an object-name token that contains the name of the EXPAND manager process. This token is always present in the response. ZCOM-TKN-OBJNAME is described in Section 6, "Common Definitions.
COMMANDS AND RESPONSES TRACE Command (EXPAND Manager Process) Operational Notes • TRACE is a sensitive command. • Only one object can be traced at a time; therefore, you cannot use this command while a trace of the NCP process, a line, or a path is in progress. • No summary-state transition is associated with this command.
COMMANDS AND RESPONSES TRACE Command (NCP Process, Lines, and Paths) TRACE Command (NCP Process, Lines, and Paths) This form of the TRACE command initiates, modifies, or terminates trace mode on the NCP process, a line, or a path. When trace mode is started on an object, trace data, as specified in the TRACE command, is collected in a special trace file. This data can later be formatted and displayed using the PTRACE program, as described in the PTRACE Reference Manual, or by using SCF in PTRACE mode.
COMMANDS AND RESPONSES TRACE Command (NCP Process, Lines, and Paths) 02 02 02 end. ZXDS-PAGES ZCOLL ZFNAME ZCOM-TKN-TRACE-OPT ZSPI-TKN-MAXRESP ZSPI-TKN-CONTEXT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT type ZSPI-DDL-INT. type ZSPI-DDL-BOOLEAN. type ZSPI-DDL-FNAME32. token-type token-type token-type token-type token-type token-type !r !r !r ZSPI-TYP-ENUM. !r ZSPI-TYP-INT. !o ZSPI-TYP-BYTESTRING.!o ZSPI-TYP-ENUM. !o ZSPI-TYP-ENUM. !o ZSPI-TYP-STRING.
COMMANDS AND RESPONSES TRACE Command (NCP Process, Lines, and Paths) ZCOM-MAP-TRACE-MODIF is a standard data-communications extensible structured token described in the Communications Management Programming Manual. This token must be present in the command, and duplicate occurrences are not allowed. ZCOM-TKN-TRACE-OPT is a standard data-communications token described in the Communications Management Programming Manual. This token must be present in the command.
COMMANDS AND RESPONSES TRACE Command (NCP Process, Lines, and Paths) Tokens in Response Buffer ZSPI-TKN-DATALIST is a standard SPI data list, as described in the Distributed Systems Management (DSM) Programming Manual. The list ends with the token ZSPI-TKN-ENDLIST. ZCOM-TKN-OBJNAME is an object-name token that contains the name of the NCP ("$NCP") or of a line or path that was affected by the command. This token is always present in the response.
COMMANDS AND RESPONSES Examples of Commands and Responses EXAMPLES OF COMMANDS AND RESPONSES The following example program, written in TAL, illustrates the basic tasks that must be performed in an application that sends commands to and retrieves responses from the EXPAND subsystem.
COMMANDS AND RESPONSES Examples of Commands and Responses ! External declarations for GUARDIAN procedures ?nolist, source $system.system.extdecs(OPEN, CLOSE, WRITEREAD, ? DEBUG, FILEINFO, INITIALIZER); ?list ! External declarations for SPI procedures ?nolist, source $system.system.
COMMANDS AND RESPONSES Examples of Commands and Responses ! *************************************************************** ! * 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.
COMMANDS AND RESPONSES Examples of Commands and Responses ! *************************************************************** ! * build^cmd * ! *************************************************************** PROC build^cmd(cmd, obj^type); INT cmd, ! command number obj^type; ! object type BEGIN INT spi^err, ! returned by call on SPI procedure zexp^manager[0:15] := ! name of EXPAND manager ! process ["\MYSYS $ZEXP "]; spi^err := SSINIT(exp^buf,zexp^val^buflen,zexp^val^ssid, zspi^val^cmdhdr,cmd,obj^type,0); IF
COMMANDS AND RESPONSES Examples of Commands and Responses ! Put the called-system token in the buffer spi^err := SSPUTTKN(exp^buf, zexp^tkn^called^sys, called^sys); IF spi^err THEN CALL handle^spi^error(spi^err); ! error on the call ! Put the selected-system token in the buffer spi^err := SSPUTTKN(exp^buf, zexp^tkn^sel^sys, sel^sys); IF spi^err THEN CALL handle^spi^error(spi^err); ! error on the call return^token := call^scp; IF return^token <> zcom^err^ok THEN ! an error occurred BEGIN ! Handle the possib
COMMANDS AND RESPONSES Examples of Commands and Responses ! Initialize the command buffer CALL build^cmd(zcom^cmd^info, zcom^obj^process); ! Put the object-name token ("$NCP") in the buffer i^ncp^name[0] := 4; ! lenght of the string s^ncp^name[2] ':=' ["$NCP"]; ! value of the string spi^err := SSPUTTKN(exp^buf, zcom^tkn^objname, i^ncp^name); IF spi^err THEN CALL handle^spi^error(spi^err); ! error on the call ! Put the NCP option token in the buffer; ! select both network map and path map information ncp^ma
COMMANDS AND RESPONSES Examples of Commands and Responses ! Make the information accessible @info^ncp^pathmap^value := @tkn^value; END; !of info^ncp ! *************************************************************** ! * start^line * ! *************************************************************** PROC start^line(obj^name); INT .
COMMANDS AND RESPONSES Examples of Commands and Responses ! *************************************************************** ! * alter^line * ! *************************************************************** PROC alter^line(obj^name); INT .obj^name; ! object name of line whose ! attributes are to be altered BEGIN INT spi^err, ! returned by call on SPI procedure return^token; ! value of return token INT .zexp^map^alter^line^req[0:zexp^map^alter^line^wln-1] := zexp^map^alter^line; INT .
COMMANDS AND RESPONSES Examples of Commands and Responses ! *************************************************************** ! * info^line^hdlc * ! *************************************************************** PROC info^line^hdlc(obj^name); INT .obj^name; ! object name of line whose ! attribute values are to be returned BEGIN INT spi^err, ! returned by call on SPI procedure return^token; ! value of return token INT .
COMMANDS AND RESPONSES Examples of Commands and Responses ! *************************************************************** ! * main program * ! *************************************************************** PROC m MAIN; BEGIN INT error, called^sys, sel^sys, obj^name[0:8]; ! ! ! ! error upon opening SCP sys # of called sys for net cmds sys # of selected sys for net cmds object name of line for line cmds ! Set up the EXPAND subsystem ID zexp^val^ssid ':=' [zspi^val^tandem, zspi^ssn^zexp, zexp^val^versio
SECTION 8 EVENT MANAGEMENT The EXPAND subsystem provides information about events that it detects 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 Table 8-1 lists the event messages that the line-handler processes can issue, and Table 8-2 lists the event messages that the NCP can issue. Table 8-1.
EVENT MANAGEMENT Subsystem Processes That Report Events Table 8-2.
EVENT MANAGEMENT Event-Management Programming EVENT-MANAGEMENT PROGRAMMING The buffer size for an EXPAND event message is 128 words. EXPAND event messages are made up of individual tokens, each containing one piece of information about the event. There are no extensible structured tokens or lists in EXPAND event messages. All EXPAND event messages are reported to EMS and none are reported to the Tandem Maintenance and Diagnostic System (TMDS).
EVENT MANAGEMENT Event-Message Descriptions Within each event-message description, there is a box that lists all the tokens that can appear in the event message. Header tokens are listed here, because an application can filter event messages on header tokens as well as on other tokens. These tokens are divided into four categories: 1. Unconditional tokens (tokens that are always present in the event message). 2. Conditional tokens (tokens that might be present in the event message). 3.
EVENT MANAGEMENT Event-Message Descriptions The descriptions in this section of the simple tokens defined by the EXPAND subsystem (that is, the simple tokens whose symbolic names begin with ZEXP-TKN-) do not identify the token numbers of the tokens. However, the symbolic names of the token numbers can be derived from the token names by replacing -TKN- with -TNM-. For example, the token number of the token ZEXP-TKN-LINE-QUAL is ZEXP-TNM-LINE-QUAL.
EVENT MANAGEMENT 3: ZEXP-EVT-IO-BUS-ERR 3: ZEXP-EVT-IO-BUS-ERR An I/O-bus error occurred, and an I/O path switch took place. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 03.
EVENT MANAGEMENT 3: ZEXP-EVT-IO-BUS-ERR Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. IO-BUS-ERR (3). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 3: ZEXP-EVT-IO-BUS-ERR Probable Cause An I/O-bus error occurred during a data transfer with the indicated device on a channel controlled by the sender CPU, and an I/O path switch took place. The system retries the operation, then retries the other path. If the file-system error number in the token ZEXP-TKN-IO-BUS-ERR is in the range 210 through 229, the operation might have been switched to the other CPU.
EVENT MANAGEMENT 4: ZEXP-EVT-DEV-ERR 4: ZEXP-EVT-DEV-ERR An error occurred on the indicated line, and the I/O retry did not succeed. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 04.
EVENT MANAGEMENT 4: ZEXP-EVT-DEV-ERR Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. DEV-ERR (4). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME. ZEMS-TKN-LDEVNAME is the logical device name of the line on which the error occurred.
EVENT MANAGEMENT 4: ZEXP-EVT-DEV-ERR If a modem loss was detected or, for a read unit, if a vertical redundancy check error was reported, bits 7 through 15 of the status word have the following meanings: Bit ----.7 .8 .9 .10 .11 .12 .13 .14 .
EVENT MANAGEMENT 4: ZEXP-EVT-DEV-ERR Bit ----.0 .1 .2 .3 .4 .5 .6 .7 Meaning (Autopoll) -----------------0 Channel underrun Channel abort Channel parity error Modem loss Autopoll terminated Transmit underrun 0 Meaning (Modem Control) ----------------------0 0 0 0 0 0 Data set ready interrupt 0 If a modem loss was detected, bits 8 through 15 of the status word indicate modem status as follows: Bit ----.8 .9 .10 .11 .12 .13 .14 .
EVENT MANAGEMENT 4: ZEXP-EVT-DEV-ERR For the multifunction controller, the status word can be interpreted as two bytes whose values identify the cause of the controller interrupt, as follows: Bits 0-7 -------0 Bits 8-15 --------0 1 3 4 5 6 7 8 9 10 2 All values Error in data transfer to or from Tandem system Transfer aborted by channel Data buffer DMA error Peripheral port chip (PPC) error Read parity error T-bus sequence error Port transfer error Data overrun Data underrun Controller ownership error Po
EVENT MANAGEMENT 4: ZEXP-EVT-DEV-ERR Bits 0-7 -------9 Bits 8-15 --------1 2 10 Meaning ------No controller internal buffer available No buffer for port task (to transmit data to, or receive data from, Tandem system) No buffer for driver task (to receive data from line) Tandem system attempted another write to controller before the first write was completed ZEXP-TKN-DEV-STATUS corresponds to the value dev-status in the text message.
EVENT MANAGEMENT 4: ZEXP-EVT-DEV-ERR Probable Cause An error occurred on the indicated line, and the I/O retry did not succeed. The tokens ZEXP-TKN-DEV-STATUS and ZEXP-TKN-DEVSTATUS-MASK supply information about the error. If the error involves a controller ownership switch, the line handler retries for up to three ownership switches; if the error persists, it brings down the line. For any other error (for instance, a modem error), the line handler waits for the error to clear, and then retries.
EVENT MANAGEMENT 6: ZEXP-EVT-DEV-UP 6: ZEXP-EVT-DEV-UP The indicated line has been brought up. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 06.
EVENT MANAGEMENT 6: ZEXP-EVT-DEV-UP Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. DEV-UP (6). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME. ZEMS-TKN-LDEVNAME is the logical device name of the line that was brought up.
EVENT MANAGEMENT 6: ZEXP-EVT-DEV-UP Recommended Action This event message is an informative message only; no corrective action is necessary.
EVENT MANAGEMENT 7: ZEXP-EVT-DEV-DOWN 7: ZEXP-EVT-DEV-DOWN The indicated line has been brought down. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 07.
EVENT MANAGEMENT 7: ZEXP-EVT-DEV-DOWN Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. DEV-DOWN (7). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME. ZEMS-TKN-LDEVNAME is the logical device name of the line that was brought down.
EVENT MANAGEMENT 7: ZEXP-EVT-DEV-DOWN Probable Cause This error probably occurred for one of the following reasons: • An operator removed the indicated line from the system. • The line handler brought the line down because more than three ownership switches occurred. • The line handler brought the line down because a run-time error occurred. In this case, this event message is preceded by event message 91, ZEXP-EVT-NET-RUN-TIME-ERR.
EVENT MANAGEMENT 33: ZEXP-EVT-NET-LINE-QUAL 33: ZEXP-EVT-NET-LINE-QUAL A change in line quality has occurred on the indicated line. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 33.
EVENT MANAGEMENT 33: ZEXP-EVT-NET-LINE-QUAL Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-LINE-QUAL (33). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 33: ZEXP-EVT-NET-LINE-QUAL Probable Cause The Network Control Process (NCP) reported a change in the line quality of the indicated line. This report is made whenever a change greater than or equal to 5% occurs. After this event message is issued, the system continues processing.
EVENT MANAGEMENT 43: ZEXP-EVT-NET-DISCONN 43: ZEXP-EVT-NET-DISCONN The connection to the indicated system has been lost. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 43.
EVENT MANAGEMENT 43: ZEXP-EVT-NET-DISCONN Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-DISCONN (43). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEXP-TKN-SYSNAME.
EVENT MANAGEMENT 43: ZEXP-EVT-NET-DISCONN Event-Message Text The following correspondences exist between values in the text message and tokens in the event message. Value -----ldev nnn xxx Token ---------------------ZEMS-TKN-LDEV ZEXP-TKN-SYSNUM ZEXP-TKN-DISCONN-CAUSE Probable Cause The connection to the indicated system has been lost due to the cause given by the token ZEXP-TKN-DISCONN-CAUSE.
EVENT MANAGEMENT 44: ZEXP-EVT-NET-LINE-READY 44: ZEXP-EVT-NET-LINE-READY The indicated line is now ready to accept network requests. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 44.
EVENT MANAGEMENT 44: ZEXP-EVT-NET-LINE-READY Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-LINE-READY (44). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 44: ZEXP-EVT-NET-LINE-READY For a direct-connect line handler, this event occurs after both line handlers (local and remote) have exchanged reset sequences. For the X.25 interface, this event occurs when the line handler is informed that a virtual circuit has been established, or when the line handler learns of the virtual circuit by querying the X.25 access process. Recommended Action This event message is an informative message only; no corrective action is necessary.
EVENT MANAGEMENT 45: ZEXP-EVT-NET-LINE-NOT-READY 45: ZEXP-EVT-NET-LINE-NOT-READY The indicated line has become not ready. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 45.
EVENT MANAGEMENT 45: ZEXP-EVT-NET-LINE-NOT-READY Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-LINE-NOT-READY (45). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 45: ZEXP-EVT-NET-LINE-NOT-READY Probable Cause The operator brought the indicated line down, or an error occurred that brought it down. The specific cause of the event is given by the token ZEXP-TKN-LINE-NOT-READY-ERR. The line handler is not ready to accept further network requests, and the NCP must find an alternate communication path. Recommended Action Appropriate recovery depends on the file-system error that occurred and on the line type.
EVENT MANAGEMENT 46: ZEXP-EVT-NET-CONN 46: ZEXP-EVT-NET-CONN A connection has been made with the NCP on the indicated remote system. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 46.
EVENT MANAGEMENT 46: ZEXP-EVT-NET-CONN Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-CONN (46). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEXP-TKN-SYSNAME.
EVENT MANAGEMENT 46: ZEXP-EVT-NET-CONN Probable Cause A successful connect exchange occurred with the NCP at the indicated remote system. After this event message is issued, the system continues processing. Recommended Action This event message is an informative message only; no corrective action is necessary.
EVENT MANAGEMENT 47: ZEXP-EVT-NET-TIMEOUT 47: ZEXP-EVT-NET-TIMEOUT A line handler did not receive an end-to-end acknowledgment from the indicated system within the configured L4TIMEOUT time. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 47.
EVENT MANAGEMENT 47: ZEXP-EVT-NET-TIMEOUT Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-TIMEOUT (47). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEXP-TKN-SYSNAME.
EVENT MANAGEMENT 47: ZEXP-EVT-NET-TIMEOUT Probable Cause A line handler did not receive an end-to-end acknowledgment from the indicated system within the configured L4TIMEOUT time. The line handler sent a request for the acknowledgment and again did not receive it within the configured L4TIMEOUT time. The line handler retried the request the number of times given by the configured L4RETRIES value before this event message was issued. The connection to the indicated system is lost.
EVENT MANAGEMENT 48: ZEXP-EVT-NET-CPU-STATUS 48: ZEXP-EVT-NET-CPU-STATUS A change in processor status has occurred at the indicated system. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 48.
EVENT MANAGEMENT 48: ZEXP-EVT-NET-CPU-STATUS Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-CPU-STATUS (48). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEXP-TKN-SYSNAME.
EVENT MANAGEMENT 48: ZEXP-EVT-NET-CPU-STATUS Probable Cause A change in processor status has occurred at the indicated system. This event is reported only by an NCP with Network Monitor Center status. After this event message is issued, the system continues processing. Recommended Action This event message is an informative message only; no corrective action is necessary.
EVENT MANAGEMENT 49: ZEXP-EVT-NET-NO-RSP 49: ZEXP-EVT-NET-NO-RSP The NCP has not received a status message from the NCP at the indicated system for three time periods. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 49.
EVENT MANAGEMENT 49: ZEXP-EVT-NET-NO-RSP Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-NO-RSP (49). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEXP-TKN-SYSNAME.
EVENT MANAGEMENT 49: ZEXP-EVT-NET-NO-RSP Probable Cause The NCP has not received a status message from the NCP at the indicated system for a specified time period. The NCP automatically seeks an alternate path. After this event message is issued, the system continues processing. Recommended Action This event message is an informative message only; no corrective action is necessary unless other related event messages appear--for instance, ZEXP-EVT-NET-LINE-NOT-READY (45) messages for that line.
EVENT MANAGEMENT 90: ZEXP-EVT-NET-BAD-SYSGEN 90: ZEXP-EVT-NET-BAD-SYSGEN The EXPAND subsystem detected a missing, incorrect, or inconsistent SYSGEN parameter. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 90.
EVENT MANAGEMENT 90: ZEXP-EVT-NET-BAD-SYSGEN Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-BAD-SYSGEN (90). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 90: ZEXP-EVT-NET-BAD-SYSGEN parameter is omitted from a line that is meant to be part of a logical path. 6 A logical path had no physical lines. This error can occur when the MULTI parameter is omitted from all the lines that were meant to be part of the logical path, or when the MULTI parameter refers to another LINE logical device.
EVENT MANAGEMENT 90: ZEXP-EVT-NET-BAD-SYSGEN Probable Cause The EXPAND subsystem detected a missing, incorrect, or inconsistent SYSGEN parameter, as described by the value of the token ZEXP-TKN-BAD-SYSGEN-CAUSE. If the error pertains to the configuration of a line handler, the line handler stops and cannot be used. Otherwise, the indicated line or path cannot be used. Recommended Action Specific recovery information for some of the possible values of ZEXP-TKN-BAD-SYSGEN-CAUSE is given below.
EVENT MANAGEMENT 90: ZEXP-EVT-NET-BAD-SYSGEN 9 The frame size must be the same for all line handlers in the network. Reduce the L2WINDOW size, the number of READBUFFERS, and/or the FRAMESIZE. Change the FRAMESIZE for all line handlers simultaneously. 10 Increase the LINEBUFFERSIZE, decrease the L2WINDOW size, or specify the number of READBUFFERS. 11-14 If the processor does not have sufficient physical memory for the line handler to run, contact your Tandem representative.
EVENT MANAGEMENT 91: ZEXP-EVT-NET-RUN-TIME-ERR 91: ZEXP-EVT-NET-RUN-TIME-ERR An EXPAND line handler or the NCP detected an internally inconsistent condition. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 91.
EVENT MANAGEMENT 91: ZEXP-EVT-NET-RUN-TIME-ERR Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-RUN-TIME-ERR (91). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 91: ZEXP-EVT-NET-RUN-TIME-ERR 7 Line handler level 3 received a packet from level 2, and this packet was invalid because it was too small. The invalid packet is discarded. 10 The line handler was unable to BIND to (OPEN) the associated IPB monitor process or the X25AM line handler, or it was unable to successfully send a request to its associated process. The line will go down by itself. ZEXP-TKN-RUN-TIME-ERR-CAUSE corresponds to the value nn in the text message.
EVENT MANAGEMENT 117: ZEXP-EVT-NET-REQ-ABORT 117: ZEXP-EVT-NET-REQ-ABORT Network traffic has been aborted. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 117.
EVENT MANAGEMENT 117: ZEXP-EVT-NET-REQ-ABORT Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. NET-REQ-ABORT (117). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEXP-TKN-SYSNAME.
EVENT MANAGEMENT 117: ZEXP-EVT-NET-REQ-ABORT ZEXP-TKN-REQ-ABORT-CAUSE corresponds to the value nn in the text message. Event-Message Text In the text message, nn corresponds to the value of ZEXP-TKN-REQABORT-CAUSE. Probable Cause An event occurred that caused network traffic to be aborted. The specific cause of the abort is given by the token ZEXP-TKN-REQABORT-CAUSE. An event message is generated for each system where traffic was aborted.
EVENT MANAGEMENT 141: ZEXP-EVT-CLIP-DWLOADED 141: ZEXP-EVT-CLIP-DWLOADED The Communications Line Interface Processor (CLIP) associated with an EXPAND line was successfully downloaded. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 141.
EVENT MANAGEMENT 141: ZEXP-EVT-CLIP-DWLOADED Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. CLIP-DWLOADED (141). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 141: ZEXP-EVT-CLIP-DWLOADED Probable Cause The CLIP was successfully downloaded. If this event occurs repeatedly, the cause may be a configuration, hardware, or software problem. Recommended Action If this event occurs once, no corrective action is necessary. However, if it occurs repeatedly, check first for related hardware problems with the CLIP; also check for configuration problems.
EVENT MANAGEMENT 146: ZEXP-EVT-CSS-UNIT-ERROR 146: ZEXP-EVT-CSS-UNIT-ERROR The 6100 family controller hardware failed while attempting to download the Communications Line Interface Processor (CLIP) or the Communications Interface Unit (CIU) associated with an EXPAND line. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 146.
EVENT MANAGEMENT 146: ZEXP-EVT-CSS-UNIT-ERROR Console-Compatible Format: LDEV ldev [ CU %ccu ] X25: CSS DOWNLOAD UNIT ERROR, CIU path #param3 [ %param4 ] Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number, as described in the Event Management Service (EMS) Manual. Its value is ZEXP-EVTCSS-UNIT-ERROR (146).
EVENT MANAGEMENT 146: ZEXP-EVT-CSS-UNIT-ERROR Event-Message Text In the text message, ldev corresponds to the value of ZEMS-TKNLDEV and ccu corresponds to the value of ZEMS-TKN-CU. The values path, param3, and param4 do not correspond to the values of tokens in the event message. Probable Cause The 6100 family controller hardware failed while attempting to download the CLIP or the CIU. The CLIP or CIU is not downloaded and remains in the starting and boot states.
EVENT MANAGEMENT 146: ZEXP-EVT-CSS-UNIT-ERROR 1023 CSM received an attribute value that was invalid for one or more of the following reasons: 1. The value exceeded the allowed range. 2. An integer or string value was expected but not received. 3. The values are out of sequence in a multivalue attribute. 1025 The CIU needed to be in the DIAGNOSE state to perform the requested operation. 1100 An I/O error occurred while the CSM was attempting the requested operation.
EVENT MANAGEMENT 146: ZEXP-EVT-CSS-UNIT-ERROR Recommended Action Analyze the failure by looking at the CSM error code given by param3 in the text message and at the accompanying event or error message. Then issue a STOP command against the line before trying to start it again.
EVENT MANAGEMENT 147: ZEXP-EVT-CSS-STATUS-PROBE-ERR 147: ZEXP-EVT-CSS-STATUS-PROBE-ERR The Communications Subsystem Manager (CSM) or the I/O process received a status-probe response from the Communications Line Interface Process (CLIP) associated with an EXPAND line. The probe indicates that this CLIP is in the boot state instead of the run state. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 147.
EVENT MANAGEMENT 147: ZEXP-EVT-CSS-STATUS-PROBE-ERR Console-Compatible Format: LDEV ldev [ CU %ccu ] CSS STATUS PROBE ERROR, CIU path %param3 %param4 Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. CSS-STATUS-PROBE-ERR (147).
EVENT MANAGEMENT 147: ZEXP-EVT-CSS-STATUS-PROBE-ERR ZEXP-TKN-CLIP-STATUS is the CLIP status byte. If the value of this token is %377 or less, the rightmost byte of the value is interpreted as follows: Bit: 0 1 Not Owner In Boot 2 3 4 5 6 7 Error If the Not Owner bit is equal to 1, the status was received from the backup port, which does not respond to a large number of commands. If the In Boot bit is equal to 1, the CLIP is operating from the bootstrap, where the command set is limited.
EVENT MANAGEMENT 147: ZEXP-EVT-CSS-STATUS-PROBE-ERR ZEXP-TKN-CLIP-STATUS corresponds to the value param3 in the text message. Event-Message Text The following correspondences exist between values in the text message and tokens in the event message.
EVENT MANAGEMENT 152: ZEXP-EVT-CSS-CLB-CMD-REJ 152: ZEXP-EVT-CSS-CLB-CMD-REJ A command to the CIU-to-LIU Bus (CLB) of a 6100 Communications Subsystem (CSS) associated with an EXPAND line was rejected, indicating that the Break Out Board (BOB) was not properly synchronized with the host system. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 152.
EVENT MANAGEMENT 152: ZEXP-EVT-CSS-CLB-CMD-REJ Console-Compatible Format: LDEV ldev [ CU %ccu ] CSS CLB COMMAND REJECT, CIU path %param3 %param4 %param5 (BELL) Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. CSS-CLB-CMD-REJ (152).
EVENT MANAGEMENT 152: ZEXP-EVT-CSS-CLB-CMD-REJ ZEXP-TKN-SEQNUM-CAUSE contains the sequence number and the cause of the error. The sequence number is stored in the most significant eight bits of the token value. The cause of the command reject is stored in the least significant eight bits of the token value, and is indicated by one of the following values: 0 The message checksum was invalid. 1 The command sequence number was invalid. 2 The command code was invalid. 3 A command parameter was invalid.
EVENT MANAGEMENT 156: ZEXP-EVT-CSS-NO-RSP 156: ZEXP-EVT-CSS-NO-RSP The Communications Line Interface Processor (CLIP) associated with an EXPAND line failed to respond to a periodic probe by a line-handler process, and a NO RESPONSE message was received. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 156.
EVENT MANAGEMENT 156: ZEXP-EVT-CSS-NO-RSP Console-Compatible Format: LDEV ldev [ CU %ccu ] CSS NO RESPONSE, CIU path STATE %param3 EVENT %param4 Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. CSS-NO-RSP (156).
EVENT MANAGEMENT 156: ZEXP-EVT-CSS-NO-RSP ZEXP-TKN-CLIP-SEND-STATE is the state of the CLIP. can have the following values: This token 0 The CLIP is not loaded. 1 The CLIP and CAP are in DIAGNOSE mode. 2 The CLIP is being downloaded, and the CSM has control. 3 The CLIP has been downloaded and is activating the path. 4 The CLIP has been downloaded and is started. 5 The CLIP has been downloaded and is stopped. This token corresponds to the value param3 in the text message.
EVENT MANAGEMENT 156: ZEXP-EVT-CSS-NO-RSP Recommended Action If this event occurs once, no corrective action is necessary. However, if it occurs repeatedly, note the values of ZEXPTKN-CLIP-SEND-STATE and ZEXP-TKN-CLIP-RECV-STATE and contact your Tandem representative.
EVENT MANAGEMENT 157: ZEXP-EVT-CSS-FRAME-ERR 157: ZEXP-EVT-CSS-FRAME-ERR An invalid frame was received by the 6100 family controller associated with an EXPAND line. This event is not a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 157.
EVENT MANAGEMENT 157: ZEXP-EVT-CSS-FRAME-ERR Console-Compatible Format: LDEV ldev [ CU %ccu ] CSS FRAME ERROR, CIU path ERROR=#nn A,C=%param1 T,S=%param2 Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. CSS-FRAME-ERR (157).
EVENT MANAGEMENT 157: ZEXP-EVT-CSS-FRAME-ERR ZEXP-TKN-FRAME-ERR contains the reason for the error.
EVENT MANAGEMENT 157: ZEXP-EVT-CSS-FRAME-ERR Probable Cause An invalid frame was received. It is normal for this event to occur during a path switch. Generally, the EXPAND software recovers from this event automatically; if it cannot recover, it brings down the line. Recommended Action If this event did not occur during a path switch, note the values of ZEXP-TKN-FRAME-ERR, ZEXP-TKN-FRAME-A-C, and ZEXP-TKN-FRAME-T-S and contact your Tandem representative.
EVENT MANAGEMENT 158: ZEXP-EVT-CSS-UNEXP-BRKPT 158: ZEXP-EVT-CSS-UNEXP-BRKPT The Communications Line Interface Processor (CLIP) associated with an EXPAND line encountered an unexpected breakpoint. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 158.
EVENT MANAGEMENT 158: ZEXP-EVT-CSS-UNEXP-BRKPT Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. CSS-UNEXP-BRKPT (158). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 158: ZEXP-EVT-CSS-UNEXP-BRKPT Event-Message Text The following correspondences exist between values in the text message and tokens in the event message. Value ------ldev ccu path param Token ------------------ZEMS-TKN-LDEV ZEMS-TKN-CU ZEXP-TKN-CIU-PATH ZEXP-TKN-FUNC-MODIF Probable Cause The CLIP encountered an unexpected breakpoint and stopped. Recommended Action Note the value of ZEXP-TKN-FUNC-MODIF and contact your Tandem representative.
EVENT MANAGEMENT 160: ZEXP-EVT-CSS-LIU-CONFIG-ERR 160: ZEXP-EVT-CSS-LIU-CONFIG-ERR The Communications Line Interface Processor (CLIP) associated with an EXPAND line received a line configuration different from that in the I/O process. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 160.
EVENT MANAGEMENT 160: ZEXP-EVT-CSS-LIU-CONFIG-ERR Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. CSS-LIU-CONFIG-ERR (160). Its value is ZEXP-EVT- ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token--here, ZEMS-TKN-LDEVNAME.
EVENT MANAGEMENT 160: ZEXP-EVT-CSS-LIU-CONFIG-ERR Event-Message Text The following correspondences exist between values in the text message and tokens in the event message. Value -----ldev ccu path nn Token ------------------ZEMS-TKN-LDEV ZEMS-TKN-CU ZEXP-TKN-CIU-PATH ZEXP-TKN-FUNC-MODIF The values param1 and param2 do not correspond to the values of tokens in the event message. Probable Cause The CLIP received a line configuration different from that in the I/O process. The line does not come up.
EVENT MANAGEMENT 164: ZEXP-EVT-CSS-LINE-ERR 164: ZEXP-EVT-CSS-LINE-ERR The Communications Line Interface Processor (CLIP) associated with an EXPAND line responded to the I/O process with an invalid function modifier. This event is a critical event, and the event message is reported to the EMS collector, $0. This event message is equivalent to console message 164.
EVENT MANAGEMENT 164: ZEXP-EVT-CSS-LINE-ERR Console-Compatible Format: LDEV ldev [ CU %ccu ] CSS LINE ERROR, CIU path F,M=%param1 ERROR=%param2 %param3 Unconditional Tokens ZSPI-TKN-SSID is the EXPAND subsystem ID, and its value is ZEXPVAL-SSID. This token is described in the Distributed Systems Management (DSM) Programming Manual. ZEMS-TKN-EVENTNUMBER is the event number. CSS-LINE-ERR (164).
EVENT MANAGEMENT 164: ZEXP-EVT-CSS-LINE-ERR ZEXP-TKN-CSS-LINE-ERR-TYPE is the CSS line-error type. This token corresponds to the value param2 in the text message. ZEXP-TKN-CSS-LINE-ERR is the CSS line-error value. This token corresponds to the value param3 in the text message. Event-Message Text The following correspondences exist between values in the text message and tokens in the event message.
EVENT MANAGEMENT Examples of Filters EXAMPLES OF FILTERS The following two examples illustrate simple filters that could be created to select EXPAND event messages. For both examples, the following assumptions have been made: 1. All EXPAND definitions used in the filters have been loaded into TACL before compilation. 2. Tokens and subsystems that you have created have been defined and loaded before compilation. 3.
EVENT MANAGEMENT Example 2 Example 2 The following filter selects all critical EXPAND event messages that have a particular device as their subject. -- Filter that selects only critical EXPAND event messages -- that have as their subject token a particular device name [#SET zexp^val^ssid [zspi^val^tandem].[zspi^ssn^zexp].
EVENT MANAGEMENT Example of Event-Message Retrieval EXAMPLE OF EVENT-MESSAGE RETRIEVAL The following example is presented as modifications to the example of retrieving event messages in Appendix C of the Event Management Service (EMS) Manual. To use this example, you will need to begin with the example in that manual and its accompanying text.
EVENT MANAGEMENT Modifications to Example in EMS Manual Modifications to Example in EMS Manual To modify the basic example in the Event Management Service (EMS) Manual, follow the instructions given below. In the instructions for running the TAL version, insert the following lines immediately after the line "LDQ $SYSTEM.ZSPIDEF.ZEMSTACL": LDQ $SYSTEM.ZSPIDEF.ZCOMTACL LDQ $SYSTEM.ZSPIDEF.
EVENT MANAGEMENT Modifications to Example in EMS Manual In the SOURCE $SYSTEM.SYSTEM.EXTDECS0 statement following the declarations, add the following procedures to the list: EMSINIT, EMSADDTOKENS, WRITEREADX, FNAMECOLLAPSE, FNAMEEXPAND, and NUMOUT. In place of the get^cpu^num procedure, substitute the following procedures, in the order listed: • The procedures open^scp, handle^spi^error, call^scp, build^cmd, and abort^line from the example at the end of Section 7.
EVENT MANAGEMENT Filter Source File Filter Source File The filter for this example is as follows: == File MYAPFS [#SET zexp^val^ssid [zspi^val^tandem].[zspi^ssn^zexp].[zexp^val^version]] [#SET myap^val^ssid [myap^val^owner].[myap^ssn^myap].[myap^val^version]] -- Return EXPAND events of low line quality.
EVENT MANAGEMENT Additional TAL Source Modules retry: ! Prompt for and read line quality threshold CALL WRITEREAD ( term, term^buf, text^len, 14, input^len); IF > THEN ! EOF from terminal CALL STOP; IF < THEN ! Some unusual condition BEGIN ! Check whether to retry IF FILEERROR ( term ) THEN GOTO retry; CALL DEBUG; END; ! Terminate input with a null s^term^buf[input^len] := 0; ! Translate number to internal integer CALL NUMIN ( S^TERM^BUF, line^quality^threshold , 10, ERROR); IF ( ( ERROR = 0 ) AND ( line^q
EVENT MANAGEMENT Additional TAL Source Modules ! Get name of line whose quality is so low it should be ! brought down spi^err := EMSGETTKN ( event^buf, ZEMS^TKN^LDEVNAME , ldev^name, 1); IF (spi^err) THEN CALL DEBUG; ! Translate internal name ! to variable-length external string line^name.len := FNAMECOLLAPSE ( ldev^name.z^localname , line^name.
EVENT MANAGEMENT Additional TAL Source Modules CALL WRITEREADX ( collector, exp^buf, event^len, 0 ); CALL CLOSE ( collector ); END; 8-98 ! abort^low^qual^line
APPENDIX A ERROR NUMBERS AND ERROR LISTS This appendix presents all the error numbers provided by the EXPAND subsystem (that is, the values whose symbolic names begin with ZEXP-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 Error-List Descriptions The notation used in the box for simple tokens is a shorthand version of the essential information given in the DDL TOKEN-CODE statement. Following the box, each token in the error list except ZSPITKN-ERRLIST and ZSPI-TKN-ENDLIST is described in the same order in which it appeared in the box. These two tokens serve the same function in all error lists, so they are not described here.
ERROR NUMBERS AND ERROR LISTS 1: ZEXP-ERR-TOO-MANY-OBJNAMES 1: ZEXP-ERR-TOO-MANY-OBJNAMES Too many object names were given in a command to the EXPAND subsystem. 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-ENUM. ZSPI-TYP-SSCTL.
ERROR NUMBERS AND ERROR LISTS 1: ZEXP-ERR-TOO-MANY-OBJNAMES Recommended Action Reduce the number of object names in the command to 30 or fewer names.
ERROR NUMBERS AND ERROR LISTS 2: ZEXP-ERR-NEG-LH-RSP 2: ZEXP-ERR-NEG-LH-RSP The EXPAND line handler returned a negative response because a file-system error occurred. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZEXP-TKN-LH-ERR-NUM ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
ERROR NUMBERS AND ERROR LISTS 2: ZEXP-ERR-NEG-LH-RSP ZCOM-TKN-OBJNAME is the name of the object on which the error occurred. This token is always present in the error list, and it is described in Section 6, "Common Definitions." ZCOM-TKN-OBJTYPE is the object type provided with the command on which the error occurred. Its possible values are ZCOM-OBJ-LINE, ZCOM-OBJ-NULL, ZCOM-OBJ-PATH, and ZCOM-OBJ-PROCESS.
ERROR NUMBERS AND ERROR LISTS 3: ZEXP-ERR-EMPT-RSP 3: ZEXP-ERR-EMPT-RSP This error number indicates an empty response record. list is associated with this error number. No error Probable Cause This error number is returned if, for example, you have assigned the value ZSPI-VAL-ERR-AND-WARN to the token ZSPI-TKN-RESPONSETYPE (meaning that you want to see a response only if there is an error or warning), and no errors or warnings occurred during processing of the command.
ERROR NUMBERS AND ERROR LISTS 4: ZEXP-ERR-TKN-CONFL 4: ZEXP-ERR-TKN-CONFL A token in a command conflicts with the values or presence of other tokens in the command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-PARM-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-PARM-ERR. ZSPI-TYP-SSCTL.
ERROR NUMBERS AND ERROR LISTS 4: ZEXP-ERR-TKN-CONFL in the command. For example, this error is given if the ALTER LINE command contains the token ZEXP-MAP-ALTER-PATH. This error is given for the SWITCH command if both of the tokens ZCOM-TKN-SWITCH-CPU and ZCOM-TKN-SWITCH-PATH are present in the command. Recommended Action Correct the token that caused the error.
ERROR NUMBERS AND ERROR LISTS 5: ZEXP-ERR-OBJ-TYPE-NAME-MISMATC 5: ZEXP-ERR-OBJ-TYPE-NAME-MISMATC A conflict exists between the object type given in an EXPAND command and an object name in that command. 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-ENUM. ZSPI-TYP-SSCTL.
ERROR NUMBERS AND ERROR LISTS 5: ZEXP-ERR-OBJ-TYPE-NAME-MISMATC Recommended Action Correct the object name or object type that caused the error.
ERROR NUMBERS AND ERROR LISTS 6: ZEXP-ERR-TRACE-NOT-STARTED 6: ZEXP-ERR-TRACE-NOT-STARTED An error occurred during the processing of a TRACE command that traces the EXPAND manager process, so the tracing 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-ENUM. ZSPI-TYP-SSCTL.
ERROR NUMBERS AND ERROR LISTS 9: ZEXP-ERR-NEG-NCP-RSP 9: ZEXP-ERR-NEG-NCP-RSP The NCP returned a negative response because a file-system error occurred. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZEXP-TKN-NCP-ERR-NUM ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-INT. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
ERROR NUMBERS AND ERROR LISTS 9: ZEXP-ERR-NEG-NCP-RSP ZCOM-TKN-OBJTYPE is the object type provided with the command on which the error occurred. Its value is always ZCOM-OBJPROCESS. This token is always present in the error list, and it is described in the Communications Management Programming Manual. Probable Cause The cause of this error is given by the file-system error number in ZEXP-TKN-NCP-ERR-NUM. For information on file-system errors, refer to the System Procedure Errors and Messages Manual.
ERROR NUMBERS AND ERROR LISTS 10: ZEXP-ERR-BAD-NETTRACE-RCVD 10: ZEXP-ERR-BAD-NETTRACE-RCVD An internal error occurred during execution of the PROBE command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZEXP-TKN-CALLED-SYS ZEXP-TKN-SEL-SYS ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-INT. ZSPI-TYP-INT. ZSPI-TYP-SSCTL.
ERROR NUMBERS AND ERROR LISTS 10: ZEXP-ERR-BAD-NETTRACE-RCVD Probable Cause An internal error occurred in Tandem software. completed. The probe is not Recommended Action Note the values of ZEXP-TKN-CALLED-SYS and ZEXP-TKN-SEL-SYS and contact your Tandem representative.
ERROR NUMBERS AND ERROR LISTS 11: ZEXP-ERR-INV-VALUE 11: ZEXP-ERR-INV-VALUE An invalid value was specified in a token for a command. Either the value given was not valid for the corresponding attribute, or a non-null value was given for an attribute that did not apply to the given object name. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-PARM-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR.
ERROR NUMBERS AND ERROR LISTS 11: ZEXP-ERR-INV-VALUE Probable Cause An invalid value was specified in a token for a command. Either the value given was not valid for the corresponding attribute, or a non-null value was given for an attribute that did not apply to the given object name. Recommended Action In the first case, supply a legal value for the attribute. In the second case, do not supply any value for attributes that do not apply to the named object, or correct the object name.
APPENDIX B TOKEN CODES AND TOKEN MAPS Table B-1 is a summary table of all token codes that are specific to the EXPAND subsystem (that is, token codes whose names begin with ZEXP-TKN-). For each token code, the token type is given. The symbolic name of the token number of a token code can be derived from the name of the token code by replacing -TKN- with -TNM-; for example, token code ZEXP-TKN-SYSNAME has the token number ZEXP-TNM-SYSNAME.
TOKEN CODES AND TOKEN MAPS Table B-1.
TOKEN CODES AND TOKEN MAPS Table B-1.
TOKEN CODES AND TOKEN MAPS Table B-2.
APPENDIX C LINE ATTRIBUTES BY LINE-HANDLER TYPE Table C-1 lists all of the attributes of EXPAND line objects that can be altered or inquired about in an application that uses the management-programming interfaces. It indicates which line attributes are valid for lines controlled by the various types of line handlers.
LINE ATTRIBUTES BY LINE-HANDLER TYPE Table C-1.
LINE ATTRIBUTES BY LINE-HANDLER TYPE Table C-1.
LINE ATTRIBUTES BY LINE-HANDLER TYPE Table C-1.
INDEX ABORT command 7-7 Access to remote systems 1-5 Action events 8-4 ALTER LINE command 7-11 ALTER PATH command 7-20 ALTER PROCESS command 7-25 Applications naming rules and guidelines for 4-3 obtaining event messages in 8-1 programmatic commands used by 2-3 relationship to architecture of 2-2 suggestions for 2-1 using letter Z in 4-3 Architecture of EXPAND subsystem 1-3 relationship of application to 2-2 Bad SYSGEN, event message 8-47 Buffer declarations 6-9 Buffer size for an event message 8-4 recommen
INDEX Commands (continued) building the buffer for 5-1 by object type 7-3 command numbers of 4-3 compared to CMI commands 2-8 compared to CUP commands 2-11 compared to NETMON commands 2-10 compared to PUP commands 2-12 compared to SCF commands 2-6 components of 4-7 continuation of 5-1 discontinuing 5-2 duplicate occurrences of tokens in 5-2 examples of 7-125/134 extensible structured tokens in 4-6 GETVERSION of EXPAND manager process 7-29 of lines and paths 7-32 INFO LINE 7-35 INFO PATH 7-45 INFO PROCESS 7
INDEX Communicating through SCP 3-1 Communications Management Interface See CMI Communications Utility Program See CUP Conditional tokens 8-5 Configuration attributes 7-6 for line-handler processes 7-56 for lines 7-12, 7-38 for paths 7-21, 7-47 Connection lost, event message 8-26 Connection made, event message 8-35 Console messages 8-5 Constructs involving multiple tokens 4-7 Continuation of commands 5-1 of responses 5-3 Control-and-inquiry interface 1-4, 2-2 CPU status change, event message 8-41 Creating
INDEX EMS 1-4, 8-1/98 examples of event-message retrieval 8-92/98 examples of filters 8-90 standard definitions 6-4 See also Event messages EMSTEXT procedure 8-5 Error handling 5-4 Error lists 4-7, A-1/18 extensible structured tokens in 4-7 issued by EXPAND subsystem A-1/18 notation used to describe A-1 order of tokens in A-1 representation of, in responses 7-6 Error numbers issued by EXPAND subsystem A-1/18 with no error lists 5-4 Error token 6-3 Event management 1-4, 8-1/98 examples of event-message ret
INDEX Event numbers 4-5 Event-number token 6-5 Events 2-12, 8-1/98 action 8-4 critical 8-3 noncritical 8-3 processes that report 8-1 Examples of commands and responses 7-125/134 of event-message retrieval 8-92/98 of filters 8-90 EXPAND definitions 6-8/25 buffer declarations 6-9 extensible structured tokens 6-12 field types 6-10 field values 6-10 simple tokens 6-11 token types 6-10 token values 6-10 tokens in error lists 6-24 tokens in event messages 6-25 EXPAND line See Lines EXPAND line-handler process Se
INDEX EXPAND subsystem (continued) definitions used by 6-1/25 elements of SPI messages for 4-1 EMS definitions used by 6-4 error handling in 5-4 error lists issued by A-1/18 error numbers issued by A-1/18 event messages issued by 8-1/98 event-message subjects issued by 4-5 format of object names for 4-4 interfaces to 1-4 management programming for 2-1 network map information for 7-53 object types supported by 4-4 objects controlled by 1-1 path map information for 7-54 programming considerations for 5-1/4 r
INDEX GETVERSION command for EXPAND manager process for lines and paths 7-32 Hierarchy of object types 7-29 6-7 I/O bus error 8-7 INFO LINE command 7-35 INFO PATH command 7-45 INFO PROCESS command 7-50 Initializing structured tokens Interactive interfaces 1-4 Interfaces to EXPAND subsystem 5-1 1-4 Letter Z, using in applications 4-3 Line error 8-10 Line not ready, event message 8-32 LINE object See Lines Line ready, event message 8-29 Line-handler processes 1-1 changing attribute values of 7-25 event
INDEX Lists data lists 4-7 error lists 4-7 in event messages 8-4 LIU configuration error 8-84 LOAD command 7-58 Management applications See Applications Management functions, required 1-2 Management programming 2-1 Manager token 6-3 Manuals, prerequisite x, 2-13 Multiple tokens, constructs involving 4-7 Names of objects, See Object names of values 4-6 Naming rules and guidelines 4-3 NCP 1-1 event messages reported by 8-3 in architecture of EXPAND subsystem 1-3 object name of 6-7 PROCESS object type for 6
INDEX Object names (continued) of EXPAND manager process 6-7 of line-handler processes 6-7 of lines 6-7 of NCP 6-7 of NULL object 6-7 of paths 6-7 of PROCESS object 6-7 Object types 4-4 commands listed by 7-3 of EXPAND manager process 6-7 of line-handler processes 6-7 of lines 6-7 of NCP 6-7 of NULL object 6-7 of paths 6-7 of PROCESS object 6-7 Object-name token 6-7 Object-type header token 6-3 Object-type token 6-7 Objects controlled by EXPAND subsystem 1-1 format of names of 4-4 number affected by one co
INDEX PROBE command 7-61 Probe information 7-63 Procedures, file-system 1-5 PROCESS object See Processes Processes commands affecting 7-4 EXPAND manager 1-1, 1-3 format of object names of 4-4 in EXPAND subsystem 1-3 line-handler 1-1, 1-3 NCP 1-1 NULL object type for 6-7 object names of 6-7 PROCESS object type for 6-7 that report events 8-1 $ZNUP 1-3 Processor status change, event message 8-41 Programmatic access to remote systems 1-5 Programmatic commands See Commands Programmatic interfaces 1-4 advantages
INDEX Responses (continued) recommended buffer sizes for 5-3 selecting response records returned in that describe multiple objects 5-3 Return token 6-4 Run-time error 8-52 5-3 SCF 1-4 corresponding commands in 2-6 SCP 3-1 communicating through 3-1 Security 5-4 Sensitive commands 7-4 Simple tokens 4-5 SPI 4-1 messages, elements of 4-1 programming considerations 5-1/4 standard definitions 6-1 SSNULL procedure 5-1 START command 7-79 Statistics for communication between two systems 7-97 for network traffic
INDEX Tokens 4-1 categories of, in event messages 8-5 conditional 8-5 constructs involving multiple 4-7 duplicate occurrences of in commands 5-2 extensible structured 4-6 in one response record 7-5 optional 7-5 order of in commands 7-5 in error lists A-1 in event messages 8-5 in responses 7-5 predefined value names for 4-6 required 7-5 simple 4-5 symbolic names of token numbers of B-1 Tandem internal 8-5 token codes 4-5 token maps 4-6 token numbers, symbolic names of B-1 token types 4-6 unconditional 8-5 v
INDEX ZCOM-CMD- (continued) STOP 7-108 SWITCH 7-112 TRACE 7-116, 7-121 ZCOM-DDLREQID 6-6 TRACE-MODIF 6-6 ZCOM-ERROBJ-ALRDY-IN-SUMSTATE in ABORT command 7-10 in START command 7-82 in STOP command 7-111 in SWITCH command 7-115 ZCOM-MAPREQID 6-6 TRACE-MODIF 6-6 for EXPAND manager process 7-118 for lines, paths, and the NCP 7-123 ZCOM-OBJLINE 6-7 NULL 6-7 PATH 6-7 PROCESS 6-7 ZCOM-TKNCMD-TIMEOUT 6-6 OBJNAME 6-7 OBJTYPE 6-7 SWITCH-CPU 7-113 SWITCH-PATH 7-113 TRACE-OPT for EXPAND manager process 7-118 for lines,
INDEX ZEXP-DDL- (continued) INFO-PROC 7-51 MSG-BUFFER 6-9 MSG-BUFFER-MAXLEN 6-9 PKTS-STATS-NCP 7-95 PROBE-NCP 7-62 STATS-LINE-CSM 6-12 STATS-LINE-NCSM 6-17 STATS-PATH 6-20 STATUS-LINE 7-99 STATUS-PATH 7-104 SYS-STATS-NCP 7-95 ZEXP-ERRBAD-NETTRACE-RCVD A-15 EMPT-RSP 5-4, A-7 INV-VALUE A-17 NEG-LH-RSP A-5 in ALTER LINE command 7-18, 7-19 in ALTER PATH command 7-24 NEG-NCP-RSP A-13 OBJ-TYPE-NAME-MISMATC A-10 TKN-CONFL A-8 in ALTER LINE command 7-19 in ALTER PATH command 7-24 in ALTER PROCESS command 7-28 in S
INDEX ZEXP-MAPALTER-LINE description of 7-12 structure of 7-11 ZADDR field 7-13 ZASSOC-DEV field 7-13 ZASSOC-SUBDEV field 7-13 ZAUTOLOAD field 7-13 ZCHARSET field 7-14 ZDELAY field 7-14 ZDSR-TIMEOUT field 7-14 ZIDLE-TIMEOUT field 7-14 ZINTERF field 7-14 ZMAX-RECONNS field 7-14 ZPROG field 7-15 ZREAD-BUFFS field 7-15 ZRECV-WINDOW field 7-15 ZRETRIES field 7-15 ZRETRY-PROBE field 7-15 ZSPEED field 7-15 ZSYNCS field 7-15 ZTEST-INTVL field 7-15 ZTHRES field 7-16 ZTIMEOUT field 7-16 ZTIMER-BIND field 7-16 ZTIME
INDEX ZEXP-MAPINFO-LINE-CSM (continued) ZFRAME-SIZE field 7-40 ZIDLE-TIMEOUT field 7-40 ZINTERF field 7-40 ZPROG field 7-40 ZPROTOID field 7-40 ZREAD-BUFFS field 7-40 ZRETRIES field 7-41 ZSPEED field 7-41 ZSYNCS field 7-41 ZTEST-INTVL field 7-41 ZTHRES field 7-41 ZTIMEOUT field 7-41 ZTYPE field 7-41 ZWINDOW field 7-41 INFO-LINE-HDLC description of 7-38 structure of 7-35 ZADDR field 7-38 ZCHARSET field 7-38 ZDELAY field 7-38 ZFRAME-SIZE field 7-38 ZIDLE-TIMEOUT field 7-38 ZINTERF field 7-38 ZREAD-BUFFS fiel
INDEX ZEXP-MAP- (continued) INFO-NCP-NETMAP description of 7-53 structure of 7-51 ZCALLED-SYS field 7-53 ZCONN-PATH field 7-54 ZCONN-STATE field 7-54 ZHOP-COUNT field 7-54 ZNSCB-TOSVERSION field 7-53 ZNUM-OF-PATH field 7-53 ZPATH-NUM field 7-54 ZSEL-SYS field 7-53 ZSYS-DIST-ENT field 7-54 ZTRAVEL-TIME field 7-54 INFO-NCP-PATHMAP description of 7-54 structure of 7-51 ZCALLED-SYS field 7-54 ZDOWN-CAUSE field 7-55 ZLINE-LDEV field 7-55 ZLINE-STATUS field 7-55 ZNEIGHBOR-NUM field 7-55 ZNOPASS-THRU field 7-55 Z
INDEX ZEXP-MAPPKTS-STATS-NCP (continued) ZPKTS-RECV field 7-97 ZPKTS-SENT field 7-97 PROBE-NCP description of 7-63 structure of 7-62 ZCALLED-SYS field 7-63 ZNUM-OF-SYS field 7-63 ZSEL-SYS field 7-63 ZSYS-LIST field 7-63 ZTRIP-TIME field 7-63 STATS-LINE-CSM description of 6-12 structure of 6-12 ZALLOC-ERRS field 6-14 ZBCC-ERRS field 6-14 ZFRAMES-ERR field 6-14 ZFRAMES-TOTAL field 6-14 ZI-FRAMES-RECV field 6-13 ZI-FRAMES-SENT field 6-13 ZL2-ADDR-ERRS field 6-16 ZL2-CMDR-FRAMES-RECV field 6-15 ZL2-CMDR-FRAMES
INDEX ZEXP-MAPSTATS-LINE-CSM (continued) ZL2-UA-FRAMES-SENT field 6-15 ZLAST-RESETSTATS-TMSTP field 6-13 ZLINE-BPID field 6-16 ZLINE-PPID field 6-16 ZQUAL-ERRS field 6-14 ZS-FRAMES-RECV field 6-14 ZS-FRAMES-SENT field 6-14 ZSTATS-CURR-TMSTP field 6-13 ZU-FRAMES-RECV field 6-14 ZU-FRAMES-SENT field 6-14 STATS-LINE-NCSM description of 6-16 structure of 6-17 ZALLOC-ERRS field 6-18 ZBCC-ERRS field 6-18 ZFRAMES-ERR field 6-18 ZFRAMES-TOTAL field 6-18 ZI-FRAMES-RECV field 6-18 ZI-FRAMES-SENT field 6-18 ZL2-CMDR-
INDEX ZEXP-MAPSTATS-LINE-NCSM (continued) ZU-FRAMES-SENT field 6-18 STATS-PATH description of 6-20 structure of 6-20 ZFRAMES-GT-4096 field 6-24 ZFRAMES-LE-1024 field 6-23 ZFRAMES-LE-128 field 6-23 ZFRAMES-LE-2048 field 6-23 ZFRAMES-LE-256 field 6-23 ZFRAMES-LE-4096 field 6-24 ZFRAMES-LE-512 field 6-23 ZFRAMES-LE-64 field 6-23 ZKNOWN-SYS field 6-24 ZL4-FWD-RECV field 6-22 ZL4-FWD-SENT field 6-22 ZL4-LINK-REQ-RECV field 6-22 ZL4-LINK-REQ-SENT field 6-22 ZL4-PKTS-RECV field 6-22 ZL4-PKTS-SENT field 6-22 ZL4-R
INDEX ZEXP-MAP- (continued) STATUS-LINE description of 7-101 structure of 7-99 ZBKUP-SUBCHNL-ADDR field 7-101 ZCSM-LDEV field 7-101 ZLAST-ERR field 7-101 ZLINE-BPID field 7-101 ZLINE-PPID field 7-101 ZPATH field 7-101 ZPATH-LDEV field 7-101 ZPRIM-SUBCHNL-ADDR field 7-101 ZSTATE field 7-101 STATUS-PATH description of 7-106 structure of 7-104 ZCLIP field 7-106 ZLAST-ERR field 7-106 ZLDEV field 7-106 ZPATH-BPID field 7-106 ZPATH-PPID field 7-106 ZSTATE field 7-106 ZTOTAL-LINES field 7-106 SYS-STATS-NCP descri
INDEX ZEXP-TKN- (continued) LINE-QUAL 8-24 NCP-ERR-NUM A-13 REQ-ABORT-CAUSE 8-56 RUN-TIME-ERR-CAUSE 8-53 SEL-SYS 6-11 SEQNUM-CAUSE 8-72 STATS-NCP-OPT 7-96 SYS-MSG-MODE 6-25 SYSNAME 6-25 SYSNUM 6-25 ZEXP-VALASCII 6-10 BUFLEN 5-1, 5-3, 6-10 EBCDIC 6-10 MAX-NUM-OF-PATHS 6-10 MAX-SYS-NUMBER 6-10 MAX-SYSTEMS 6-10 MAXBUFLEN 5-3, 6-10 MIN-SYS-NUMBER 6-10 NCP-MAPS 7-52 NCP-PATHS 7-52 NOT-READY 7-55 PATH-CONNECTED 7-54 PATH-CONNECTING 7-54 PATH-DISCONNECTED 7-54 PKTS-STATS 7-96 READY 7-55 RS232 6-11 RS422 6-11 SSID
INDEX ZSPI-TKN- (continued) SERVER-BANNER for EXPAND manager process for lines and paths 7-33 SERVER-VERSION 6-4 SSID 6-4 7-30 $ZNUP in architecture of EXPAND subsystem 1-3 Index-23
