Networking and Data Communications Library Tandem OSI/TS Management Programming Manual Product Version OSI/TS C30 Release ID C30.08/D10 Edition Print Date Part Number Abstract July 1992 056786 This manual describes the DSM programmatic interfaces (SPI-format commands, responses, and event messages) to the Tandem OSI/TS subsystem. It is intended for programmers writing management applications that communicate with OSI/TS.
Document History Edition Part Number Product Version Release ID Print Date First Edition Second Edition 24502 056786 OSI/TS C21 OSI/TS C30 C20 C30.08/D10 March 1990 July 1992 New editions incorporate any updates issued since the previous edition. Release ID Note Release ID specifies the release in which the software functions described in an edition are the first available on a standard SUT (site update tape). Copyright Copyright © 1992 by Tandem Computers Incorporated. All rights reserved.
New and Changed Information This is the second edition of the Tandem OSI/TS Management Programming Manual. This manual documents interactive interface to the C30 release of the Tandem Open Systems Interconnection/Transport Services (OSI/TS). This manual also contains additional enhancements to the previous edition. The following subsection summarizes these changes.
New and Changed Information iv 056786 Tandem Computers Incorporated
Contents About This Manual xiii Notation Conventions Section 1 xxi Introduction Why Management Programming for OSI/TS? 1-1 OSI/TS Subsystem Architecture 1-2 Control-and-Inquiry Interface 1-3 Event-Management Interface 1-4 Programmatic Commands 1-5 Object Types 1-5 PROCESS 1-5 SERVICE 1-5 SU 1-5 ROUTE 1-6 Hierarchy of Object Types 1-6 Management Functions Provided 1-7 Commands 1-7 Event Messages 1-9 C-Series and D-Series Compatibility 1-10 C30 OSI/TS Running in a D-Series System 1-10 C30 OSI/TS Runn
Contents Naming Guidelines 3-3 Message Elements for the OSI/TS Subsystem Commands 3-4 Object Types 3-4 Object Names 3-5 Event Numbers 3-6 Subjects of Event Messages 3-6 Other Tokens 3-6 Data Lists and Error Lists 3-6 3-4 Using SPI to Build Commands and Decode Responses 3-6 Building and Sending a Command Message 3-6 Discontinuing a Command in Progress 3-7 Receiving and Decoding a Response Message 3-8 Error Handling 3-9 Security 3-9 Retrieving and Decoding Event Messages 3-10 Event-Management Considerati
Contents Buffer Declarations 4-15 Character Strings 4-16 Predefined Token and Field Values Section 5 4-18 Commands and Responses Commands by Object Type 5-1 Sensitive and Nonsensitive Commands 5-3 Command Descriptions 5-4 ABORT PROCESS Command 5-6 ABORT SU Command 5-8 ACTIVATE PROCESS Command 5-11 ADD SU Command 5-13 AGGREGATE PROCESS Command 5-29 ALLOWOPENS SU Command 5-32 ALTER PROCESS Command 5-34 ALTER SERVICE Command 5-38 ALTER SU Command 5-56 DELETE SU Command 5-69 FORBIDOPENS SU Command 5-72
Contents STATUS SU Command 5-184 STOP PROCESS Command 5-192 STOP SU Command 5-194 SUSPEND PROCESS Command 5-197 SWITCH PROCESS Command 5-199 TRACE PROCESS Command 5-201 Section 6 Event Messages Subsystem Processes that Report Events Tokens in All Event Messages 6-1 6-3 Event-Message Descriptions 6-4 66: OS4-EVT-SM-ERR 6-5 74: OS4-EVT-INTL-ERR 6-6 90: OS4-EVT-PROC-ABEND 6-7 106: OS4-EVT-INSUFF-BUF 6-8 301: OS4-EVT-TKOVR 6-9 302: OS4-EVT-BKUP-UP 6-11 303: OS4-EVT-BKUP-DOWN 6-12 304: OS4-EVT-BKUP-CREATE-
Contents Appendix B Appendix C Token Codes and Token Maps Table of Token Codes B-1 Table of Token Maps B-2 Sample Programs Management Program Example C-1 Sample Event-Message Filters C-15 Filter Example: All OSI-Related Messages C-15 Filter Example: Messages Reporting DSM Errors from NSP Processes C-16 Command File to Compile Filter Examples C-16 Event-Retrieval Example C-17 Example in TAL C-17 Example in C C-27 Appendix D Attribute Name Changes Appendix E Status SU Attribute Values ZX25-DISC-RE
Contents Figure 1-6. Communication Permitted Between Mixed C-Series and DSeries Expand Networks 1-13 Figure 1-7. Restrictions on C-Series Communication with D-Series Systems 1-14 Tables Table 0-2. x Overview of Contents of OSI/AS and OSI/TS Manuals xiii Table 1-2. Programmatic Commands and Interactive (SCF) Commands 1-8 Table 3-1. Wildcard Support for OSI/TS Programmatic Commands Table 4-1. SPI Standard Definitions for Header Tokens Table 4-2.
Contents Table 5-2. Commands and Their Symbolic Names Table 5-3. Header Tokens in Commands and Responses Table 5-4. OSI/TS Protocol Selection for X.25 Wide Area Networks Table 5-5. OSI/TS Protocol Selection for Local Area Networks Table 6-1. 6-OSI/TS Event Messages Table 6-2. 6-Tokens that Appear in All OSI/TS Event Messages Table B-1. B-OSI/TS Token Codes and Token Types Table B-2. B-OSI/TS Token Maps and DDL Definitions Table F-1. Reasons for Circuit Disconnection Table F-2.
Contents xii 056786 Tandem Computers Incorporated
About This Manual About the OSI/AS and OSI/TS Manual Set The OSI/AS subsystem and the OSI/TS subsystem together provide core services that support the seven-layer OSI Reference Model. The manuals for these two products are listed in Table 0-1. The table lists the tasks that the OSI/AS and OSI/TS manuals are designed to support and the type of information provided in each manual. Table 0-1.
About This Manual Purpose of This Manual The Tandem OSI/TS Management Programming Manual provides subsystem-specific information about the management programming interfaces to the Tandem OSI/TS subsystem. These interfaces are based on the Subsystem Programmatic Interface (SPI) and the Event Management Service (EMS). They allow applications to send commands to, and monitor events reported by, the OSI/TS subsystem. This manual serves as both a reference manual and a programmer’s guide.
About This Manual What's in This Manual? Sections 1 through 3 of this manual give background information and programming considerations, including the following: The architecture of the OSI/TS subsystem and how a management application fits into it (Section 1) The types of objects managed by OSI/TS and the operations necessary to manage these objects (Section 1) The kinds of events reported by OSI/TS (Section 1) How to set up communications with the OSI/TS subsystem, including how to start the TSP process
About This Manual What Related Publications Are Available? The other publications related to this manual fall into three categories: standards documents, with which you should first be familiar; prerequisite manuals, which you should read before you read this manual; and other Tandem OSI manuals.
About This Manual Figure 1. Documentation Road Map Introduction to Tandem NonStop Systems Introduction to Tandem NonStop Systems Introduction to Distributed Systems Management (DSM) Guardian 90 Operating System Programmer's Guide System Procedure Calls Reference Manual Manual(s) for Your Programming Language X25AM Management Programming Manual TLAM Management Programming Manual Distributed Systems Management (DSM) Programming Manual Event Management Service (EMS) Manual Comm.
About This Manual Here is a description of each of the manuals included in the Documentation Road Map: Introduction to Tandem NonStop Systems describes the application environment, architecture, and networking of NonStop systems and explains basic concepts, terms, and entities in the NonStop environment. Introduction to Distributed Systems Management (DSM) introduces the set of software products collectively called Distributed Systems Management.
About This Manual TLAM Management Programming Manual describes the management programming interface to the Tandem LAN Access Method (TLAM) subsystem. Since OSI/TS relies on either X25AM or TLAM for lower-layer functions, a program written to manage OSI/TS may also need to send commands to TLAM or to handle TLAM event messages. Other Tandem OSI Manuals In addition to the prerequisite manuals shown in the diagram, you may need to be familiar with some of the other manuals in the Tandem OSI manual set.
About This Manual xx 056786 Tandem Computers Incorporated
Notation Conventions The following list summarizes the conventions for syntax presentation in this manual. Notation Meaning UPPERCASE LETTERS Uppercase letters represent keywords and reserved words; enter these items exactly as shown. Lowercase italic letters represent variable items that you supply. Parentheses, commas, semicolons, and other symbols not described above must be entered precisely as shown.
1 Introduction The Tandem OSI/TS (Open Systems Interconnection/Transport Services) subsystem provides a Transport Layer interface to OSI networks. OSI/TS requires one of the following Tandem access methods to provide the services of layers below the Transport Layer: X.25 Access Method, X25AM (for wide area networks) Tandem LAN Access Method, TLAM (for local area networks) OSI/TS supports Tandem’s Distributed Systems Management (DSM) facilities for subsystem management.
Introduction OSI/TS Subsystem Architecture OSI/TS Subsystem The OSI/TS subsystem provides Transport Layer services to OSI networks. Figure 1-1 Architecture shows the relationships among the various components of the OSI/TS subsystem. Figure 1-1. OSI/TS Subsystem Architecture Layer Transport OSI/TS Subsystem Network Data Link X25AM Subsystem TLAM Subsystem Controllers Controllers RS-232C, RS-449, X.21, V.
Introduction OSI/TS Subsystem Architecture Control-and-Inquiry Interface Figure 1-2 illustrates the control-and-inquiry interface to OSI/TS—that is, the interface that provides commands and responses. Figure 1-2. Control-and-Inquiry Interface to OSI/TS Management Application Programmatic Commands and Responses Interactive Commands and Displayed Responses SCP TSP Process 015 To manage the OSI/TS subsystem, the Subsystem Control Point (SCP) process is required.
Introduction OSI/TS Subsystem Architecture Event-Management Interface Event messages from OSI/TS are made available to management applications by the Event Management Service (EMS). EMS collects, logs, and distributes event messages that provide information to help you monitor the network environment, analyze failures, and recognize and handle critical problems. Figure 1-3 illustrates the event-management interface to OSI/TS. Figure 1-3.
Introduction Programmatic Commands 5. An application installs an EMS filter specifying the selection of event messages it wants to receive. (Filters are optional but recommended. If no filter is installed, all event messages will be delivered to the application.) 6. The application opens an EMS consumer distributor and requests an event message. 7. The distributor reads the log and returns to the application the next event message that satisfies the conditions of the filter. 8.
Introduction Programmatic Commands addresses and configuration used by the first connection. You specify the SU type with the ZDEL-TIME attribute. A value of 0 indicates a dynamic SU and a value of -1D indicates a static SU. Information about a previous connection (including error information) is available until the static SU is deleted or reused. This is useful for problem diagnosis. NSP subdevices (that is, SU objects for X25AM and TLAM) are handled somewhat differently from TSP (OSI/TS) subdevices.
Introduction Programmatic Commands Management Functions Provided The OSI/TS subsystem provides your application with the capability to do the following: Obtain information about the current attributes of the subsystem Obtain a list of the currently defined subsystem objects of a given type or a list of those subordinate to a specified process Stop a specified subdevice Suspend and reactivate TSP processes Forbid or allow opens of TSP subdevices Obtain information about the opens of a specified subdevice O
Introduction Programmatic Commands Table 1-1.
Introduction Event Messages Event Messages OSI/TS subsystem processes generate event messages when they detect significant events, such as a trap caused by a hardware or software error, or a management counter reaching a threshold. The subsystem processes send these event messages, in SPI format, to the Event Management Service (EMS), which makes them available to management applications upon request. Section 6 of this manual describes in detail the contents of the event messages that TSP processes issue.
Introduction C-Series and D-Series Compatibility C-Series and D-Series This C30 version of OSI/TS is able to run at a high PIN (process identification number) Compatibility in D-series systems (version D00 or later); it can run only at a low PIN in C-series systems (version C21 or later). Since the application interface is not version controlled, the functions available through the application interface are available to any application regardless of the software version.
Introduction C-Series and D-Series Compatibility Figure 1-5. High PIN to Low PIN Communication Permitted in D-Series Systems Network View From a D-Series High PIN Process ($PRO1) D-Series D-Series $PRO1 $PRO3 C-Series $PRO2 $PRO4 $PRO5 Legend High PIN Low PIN 030 OSI/TS-Specific Compatibility Information It is assumed, in this case, that the application, OSI/TS, and X25AM or TLAM are all running on D-series systems in an Expand network.
Introduction C-Series and D-Series Compatibility Mixed C-Series and D-Series Expand Networks Some Expand networks may have some D-series systems, some C30-version systems, and some C20-version systems (OSI/TS version C21). In addition, it is possible that the application, OSI/TS, and either X25AM or TLAM are each running in a different node at a different version level (the application may, perhaps, be running in a D00 system, OSI/TS running in a C30 system, and X25AM running in a C21 system).
Introduction C-Series and D-Series Compatibility Figure 1-6 illustrates a process in a C-series system communicating with processes in a D-series system: Figure 1-6.
Introduction C-Series and D-Series Compatibility Figure 1-7 illustrates restrictions on processes in a C-series system communicating with processes in a D-series system: Figure 1-7.
Introduction C-Series and D-Series Compatibility OSI/TS Running in Mixed C-Series and D-Series Expand Networks The following subsections contain OSI/TS-specific information for communicating with processes having various combinations of version levels. In all cases, the version compatibility rules described earlier apply between any two processes, regardless of whether the processes are running in the same system or on different systems in an Expand network.
2 Communicating With the OSI/TS Processes This section describes how a management application sends Subsystem Programmatic Interface (SPI) messages to, receives SPI responses from, and retrieves event messages generated by the processes in the OSI/TS subsystem. Communicating To manage the OSI/TS subsystem, your application sends commands to the TSP Through SCP processes, through the Subsystem Control Point (SCP).
Communicating with OSI/TS (TSP) Processes Running a TSP Process Running TSP Interactively With a RUN Command The TSP process code is contained in an object file called TSPOBJ. To run this process interactively, enter a RUN command from either TACL or SCF. For the syntax of the RUN command, refer to the TACL Reference Manual. You must be logged on as a member of the Guardian 90 super group (group ID 255) when you enter the RUN command to run the TSP process.
Communicating with OSI/TS (TSP) Processes Running a TSP Process The TSP process also supports a number of PARAM commands. Refer to the OSI/TS Manual for details. Running TSP Programmatically With a NEWPROCESS or PROCESS_CREATE_ Call An application can create the TSP process by calling the NEWPROCESS or NEWPROCESSNOWAIT procedure provided by the Guardian 90 C-series system operating system; for D-series systems the equivalent procedure is the PROCESS_CREATE_ procedure.
Communicating with OSI/TS (TSP) Processes Running an EMS Consumer Distributor establish a new connection. You can also send PARAM messages to the TSP process. Refer to the Tandem OSI/TS Manual for details. Closing and Stopping a TSP Process Since your application does not open the TSP process directly, it does not need to close it when finished. It need only close the SCP, as described in the Communications Management Programming Manual.
3 SPI Programming Considerations for OSI/TS Once your subsystem and EMS processes are running and your management application has established communication with them, the main business of your application is to format and send commands, decode responses and act on the results, and interpret event messages and act on the information they contain.
SPI Programming Considerations for OSI/TS Definition Files Definition files are named according to the following convention: ZSPIDEF.ZsubsysTAL ZSPIDEF.ZsubsysCOB ZSPIDEF.ZsubsysC ZSPIDEF.ZsubsysTACL ZSPIDEF.ZsubsysDDL ZSPIDEF.ZsubsysP subsys is a three-character code identifying the subsystem or other software component to which these definitions belong. This code is OS4 for Tandem OSI/TS. The last characters of each file name denote the language in which the definitions in this file are coded.
SPI Programming Considerations for OSI/TS Naming Guidelines Likewise, a management application written in C that sends commands to and retrieves event messages issued by the OSI/TS subsystem would need the following #include statements: #include #include #include #include #include #include
SPI Programming Considerations for OSI/TS Message Elements for the OSI/TS Subsystem Message Elements for The following subsections provide subsystem-specific information about elements of the OSI/TS Subsystem OSI/TS commands, responses, and event messages.
SPI Programming Considerations for OSI/TS Message Elements for the OSI/TS Subsystem ZCOM-OBJ-name, where name identifies the object type. (The separator character varies with the language; hyphens are shown throughout this and other DSM manuals because hyphens are used in DDL.) For example, the subdevice object type is represented by the name ZCOM-OBJ-SU. The object-type header token, ZSPI-TKNOBJECT-TYPE, always has one of these values.
SPI Programming Considerations for OSI/TS Using SPI to Build Commands and Decode Responses Many commands also support multiple object-name tokens. The descriptions of the individual commands in Section 5 indicate which commands support multiple objectname tokens. Event Numbers All event messages contain a header token identifying the event by number. This event number, in combination with the subsystem ID header token, uniquely identifies the kind of event being reported.
SPI Programming Considerations for OSI/TS Using SPI to Build Commands and Decode Responses 5. If you are resending a command to retrieve the next response message in a series, call SSMOVE or SSMOVETKN to move the context token from the previous response buffer into the command buffer. 6. Send the command message using the mechanism appropriate to your programming language (for example, a WRITEREAD call in TAL).
SPI Programming Considerations for OSI/TS Using SPI to Build Commands and Decode Responses Receiving and Decoding a Response Message The following is a summary of the steps your application must take to receive and decode a response message: 1. Declare a buffer of appropriate size. 2. Read the response message using the mechanism appropriate to your programming language (for example, a WRITEREAD call in TAL). 3.
SPI Programming Considerations for OSI/TS Using SPI to Build Commands and Decode Responses Error Handling Each response returned by OSI/TS includes a return token (ZSPI-TKN-RETCODE), whose value indicates whether an error occurred when OSI/TS attempted to perform the command. An error is a serious condition that prevents the command from being completed. If the command completed with no errors, the value of the return token is ZCOM-ERR-OK.
SPI Programming Considerations for OSI/TS Retrieving and Decoding Event Messages Retrieving and The following is a summary of the steps your application must take to retrieve and act Decoding Event upon event messages: Messages 1. Declare a buffer of appropriate size for the Event Management Service (EMS) GETEVENT command and its response. (For recommended sizes, see the “Event-Management Considerations for OSI/TS” subsection that follows.) 2.
SPI Programming Considerations for OSI/TS Retrieving and Decoding Event Messages The Event Management Service (EMS) Manual provides information on how to retrieve tokens from an event message. The Communications Management Programming Manual provides additional information, specific to data communications subsystems. Refer to those manuals for details.
SPI Programming Considerations for OSI/TS Retrieving and Decoding Event Messages It is recommended that your application always use a filter when retrieving event messages. Otherwise, the application will receive all the event messages sent to the event log on the local system. You can use any of the tokens contained in event messages to select which event messages will be returned to your application.
4 Common Definitions This section lists the common definitions—those used in several commands, responses, or event messages—for the OSI/TS subsystem. Definitions used in only one or two commands, responses, or event messages are described along with that individual command or event message in Section 5 or Section 6, respectively. Sections 5 and 6 also provide any additional considerations for the common definitions as they apply to the particular command or event message being described.
Common Definitions SPI Standard Definitions SPI Standard All items in the definition files are given symbolic names. Definitions whose names Definitions begin with ZSPI are SPI standard definitions. These definitions are available to all subsystems that support the SPI procedures; they are provided in the SPI DDL file ZSPIDEF.ZSPIDDL and in the corresponding files for other languages.
Common Definitions SPI Standard Definitions Table 4-3. SPI Standard Definitions for Token Types Token Types ZSPI-TYP-ALLOW-TYPE ZSPI-TYP-BOOLEAN ZSPI-TYP-BYTE ZSPI-TYP-BYTE-PAIR ZSPI-TYP-BYTESTRING ZSPI-TYP-CHAR50 ZSPI-TYP-CRTPID ZSPI-TYP-ENUM ZSPI-TYP-ERROR ZSPI-TYP-FNAME ZSPI-TYP-FNAME32 ZSPI-TYP-INT ZSPI-TYP-INT2 ZSPI-TYP-LIST ZSPI-TYP-MARK ZSPI-TYP-RESPONSE-TYPE ZSPI-TYP-SSCTL ZSPI-TYP-SSID ZSPI-TYP-STRING ZSPI-TYP-STRUCT ZSPI-TYP-TIMESTAMP ZSPI-TYP-UINT ZSPI-TYP-VERSION Table 4-4.
Common Definitions Data Communications Standard Definitions Descriptions of the SPI standard definitions as they apply to all subsystems are given in the Distributed Systems Management (DSM) Programming Manual. For all but two of the definitions listed in Tables 4-1 and 4-2, the information in that manual suffices to describe their use by OSI/TS. Subsystem-specific information for those two definitions is given in the following paragraphs.
Common Definitions Data Communications Standard Definitions Table 4-6.
Common Definitions Data Communications Standard Definitions Table 4-8. Data Communications Standard Definitions for Simple Tokens Simple Tokens ZCOM-TKN-CAUSE-CPU-SWITCH ZCOM-TKN-CMD-CODE ZCOM-TKN-CMD-TIMEOUT ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJSTATE ZCOM-TKN-SUB ZCOM-TKN-GETVSN-LVL ZCOM-TKN-SUBJ-PROC ZCOM-TKN-SUBJ-SERV ZCOM-TKN-SUBJ-SU ZCOM-TKN-SWITCH-CPU ZCOM-TKN-TRACE-BKUP ZCOM-TKN-TRACE-OPT ZCOM-TKN-XMGR Table 4-9.
Common Definitions Data Communications Standard Definitions $process-name Wild-Card Support Wild cards are not supported for the null object. Examples The following are valid object-names for the null object: $TSP1 $TSP2 ZCOM-OBJ-PROCESS ZCOM-OBJ-PROCESS identifies a specific TSP process within an OSI/TS subsystem. Names of PROCESS objects have the following form: $process-name $process-name is the Guardian 90 process name. Wild-Card Support Wild cards are not supported for the PROCESS object.
Common Definitions Data Communications Standard Definitions #NSAP is the NSAP routing identifier. nsap-addr is the NSAP address. Wild-Card Support Wild cards are supported for the INFO ROUTE command. You can specify wild cards in the nsap-address field. Examples of the nsap-address field with wild cards are: .* .? .abc* .a?c* Examples The following are valid object-names for the ROUTE object: $TSP4.#NSAP.49000308008E000010FE01 $TSP4.#NSAP.* $TSP2.#NSAP.
Common Definitions Data Communications Standard Definitions Examples The following are valid object-names for the SERVICE object: $TSP4.#L3 $TSP4.#L4 $TSP4.#L? $TP4.* ZCOM-OBJ-SU ZCOM-OBJ-SU defines a subdevice subordinate to an OSI/TS subsystem process. There are two types of SUs: static and dynamic. A static SU object is temporary, it is added dynamically and lasts only as long as the connection exists.
Common Definitions Data Communications Standard Definitions Note The preceding description applies to TSP subdevices as defined by the OSI/TS subsystem. Subdevices have somewhat different meanings for, and are treated differently by, the X25AM and TLAM subsystems. For information about subdevices defined by lower-layer subsystems, refer to the manuals covering those subsystems. Simple Tokens The ZCOM simple tokens include subjects of event messages and various other simple tokens.
Common Definitions Data Communications Standard Definitions Summary States for Subdevices ZCOM-VAL-SUMSTATE-ABORTING means that the subdevice is in transition to the STOPPED state because an ABORT command was received. The subdevice will not accept connection requests from applications. ZCOM-VAL-SUMSTATE-STARTED means that the subdevice is ready to support an application connection or is already doing so. ZCOM-VAL-SUMSTATE-STOPPED means that the subdevice has been aborted or stopped.
Common Definitions EMS Standard Definitions EMS Standard Definitions Definitions whose names begin with ZEMS are EMS standard definitions. They are provided in the ZSPIDEF.ZEMSDDL file and in the corresponding files for other languages. Tables 4-11 and 4-12 list EMS standard definitions used in event messages issued by the OSI/TS subsystem.
Common Definitions Guardian 90 Definitions ZEMS-TKN-SUBJECT-MARK immediately precedes the subject token, ZCOM-TKN-SUBJ-SERV. Additional information specific to particular event messages is provided in the individual event-message descriptions in Section 6. Guardian 90 Definitions Definitions whose names begin with ZGRD are Guardian 90 operating system definitions. They are provided in the ZSPIDEF.ZGRDDDL file and in the corresponding files for other languages.
Common Definitions File-System Definitions File-System Definitions whose names begin with ZFIL are Guardian 90 file-system definitions. Definitions They are provided in the ZSPIDEF.ZFILDDL file and in the corresponding files for other languages. Tables 4-16 through 4-18 list the file-system definitions used in event messages and error lists returned by the OSI/TS subsystem. Table 4-16. File-System Definitions for Simple Tokens Simple Tokens ZFIL-TKN-FILENAME ZFIL-TKN-XFILENAME Table 4-17.
Common Definitions OSI/TS Definitions OSI/TS Definitions Definitions whose names begin with ZOS4 are OSI/TS definitions. These definitions consist of simple tokens and extensible structured tokens used in OSI/TS commands and responses. They are provided in the ZSPIDEF.ZOS4DDL file and in the corresponding files for other languages. The OSI/TS definitions that appear in several commands, responses, or event messages are described in the following subsections.
Common Definitions OSI/TS Definitions ZOS4-VAL-MAX-BUFLEN is the same size as ZCOM-VAL-MAX-BUFLEN, the maximum buffer size for data communications subsystems. ZOS4-DDL-MIN-MSG-BUF is a message buffer of the minimum size recommended for OSI/TS commands, responses, and event messages. def ZOS4-DDL-MIN-MSG-BUF. 02 Z-MSGCODE 02 Z-BUFLEN 02 Z-OCCURS 02 Z-FILLER type ZSPI-DDL-INT. type ZSPI-DDL-INT. type ZSPI-DDL-INT. type ZSPI-DDL-BYTE occurs 0 to ZOS4-VAL-MIN-BUFLEN times depending on Z-OCCURS. end.
Common Definitions OSI/TS Definitions ZOS4-DDL-CHAR14 is a 14-character structure whose fields are addressable either as string-type or as integer-type values. It is defined as follows: def ZOS4-DDL-CHAR14. 02 Z-C 02 Z-S redefines Z-C. 04 Z-I 02 Z-B redefines Z-C end. pic x(14) spi-null " ". type binary 16 pic x occurs 7 times. occurs 14 times. ZOS4-DDL-CHAR40 is a 40-character structure whose fields are addressable either as string-type or as integer-type values.
Common Definitions OSI/TS Definitions Predefined Token and Field Values The OSI/TS subsystem defines several named values for use in tokens and token fields in several commands, event messages, or error lists. These values are listed in Tables 4-20 and 4-21. Table 4-20. OSI/TS Predefined Values for Simple Values Simple Values ZOS4-VAL-SERVER-BANNER ZOS4-VAL-VERSION Table 4-21.
Common Definitions OSI/TS Definitions OSI/TS defines several simple tokens that appear in OSI/TS event messages. These are described in Section 6 under the individual event messages in which they appear.
5 Commands and Responses This section describes the syntax and semantics for all commands and responses in the management programming interface to OSI/TS. In this section, the names and structures of commands, object types, and all tokens and their values are represented in DDL. For a quick explanation of DDL, refer to the appendix “Overview of DDL for SPI” in the Distributed Systems Management (DSM) Programming Manual. Commands by Object Table 5-1 lists all of the OSI/TS programmatic commands.
Commands and Responses Commands by Object Type Table 5-1. OSI/AS Commands and Object Types (Page 2 of 2) Object Types/ Commands Sensitive Command SUSPEND SWITCH TRACE Yes Yes Yes NULL PROCESS ROUTE SERVICE SU X X X Table 5-2.
Commands and Responses Sensitive and Nonsensitive Commands Table 5-2.
Commands and Responses Command Descriptions SWITCH Starts the takeover of the backup process. TRACE Generates trace records for an object. Nonsensitive commands do not affect the operation or status of an object; therefore these commands can be issued by any user. The nonsensitive OSI/TS commands and their functions are as follows: AGGREGATE Returns the count of the objects in a given state. GETVERSION Returns an object’s software-release version information.
Commands and Responses Command Descriptions Descriptions of simple tokens in this section do not identify their token numbers. However, the symbolic names of the token numbers can be derived from the token names by simply replacing -TKN- with -TNM-. For example, the token number of the ZSPI-TKN-MANAGER token is ZSPI-TNM-MANAGER. The syntax boxes do not include the SPI header tokens, which are always present in every command and response buffer.
Commands and Responses ABORT PROCESS Command ABORT PROCESS Command The ABORT PROCESS command immediately terminates all pending requests for the subdevices subordinate to the specified process, deletes those subdevices, and then stops the specified process. This is a sensitive command.
Commands and Responses ABORT PROCESS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses ABORT SU Command ABORT SU Command The ABORT SU command immediately terminates all pending file-system I/O requests for the specified subdevices, and then terminates the operation of the subdevices. This is a sensitive command.
Commands and Responses ABORT SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses ABORT SU Command Operational Note Executing the ABORT SU command causes any existing transport connection on the specified subdevice to be terminated and places the subdevice in the STOPPED state.
Commands and Responses ACTIVATE PROCESS Command ACTIVATE PROCESS Command The ACTIVATE PROCESS command changes the state of a suspended (SUSP) or suspending process to the STARTED state. It is a sensitive command.
Commands and Responses ACTIVATE PROCESS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses ADD SU Command ADD SU Command The ADD SU command creates a new SU (subdevice) object, defines its attributes, and adds it to the OSI/TS subsystem. This is a sensitive command. Command ZCOM-CMD-ADD Object Type ZCOM-OBJ-SU Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZOS4-MAP-ADD-SU-TSP def ZOS4-DDL-ADD-SU-TSP.
Commands and Responses ADD SU Command Tokens in Command Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 ZEXTENDED-FRMT ZMULTIPLEX ZEXPEDITED ZREXMIT-TIMEOUT ZREF-TIMEOUT ZMAX-REXMIT ZINACTV-TIMEOUT ZWIN-TIMEOUT ZTTR-TIMEOUT ZTWR-TIMEOUT ZCONN-TIMEOUT ZDISCONN-TIMEOUT ZX25PVC ZIP-NULL-LAYER ZIP-X25-SNDCF ZX25CUG-TYPE ZX25BCUG ZX25RPOA ZX25RPOA-DNIC-CNT ZX25TRANSIT-DELAY type type type type type type type type type type type type type type type type type type type type ZSPI-
Commands and Responses ADD SU Command ZCOM-TKN-OBJNAME is the name of the subdevice to be added. This token is required and must occur only once. ZOS4-MAP-ADD-SU-TSP specifies an extensible structured token that contains the desired values for the attributes. The individual fields are described below. ZNSP-DEV specifies the name of the SYSGEN-configured X25AM or TLAM I/O process controlling access to the subnetwork. This parameter is required.
Commands and Responses ADD SU Command applies to transport classes 1, 2, 3, and 4 only. This value is an ASCII string up to 16 characters long. The default value is all blanks. ZRECV-SECUR specifies whether security checking is performed on incoming CR-TPDUs. If security checking is specified, only incoming CR-TPDUs that have matching characters in the protection field are accepted. If you do not provide a value, no security checking is performed.
Commands and Responses ADD SU Command ZX25CUG specifies the closed user group ID (CUG ID) that is sent in every call-request packet. If no CUG ID is specified, X25AM sends the CUG ID of the associated X25AM line. Acceptable values range from 0 through 9999. No default value is provided. ZX25DESTADDR specifies the network address that is used as the called address in an outgoing call request packet. The address is a string of decimal digits (0 through 9), up to a maximum of 15 digits.
Commands and Responses ADD SU Command ZX25REMOTENET specifies the addressing conventions to be used when building the called address in the call request packet.
Commands and Responses ADD SU Command calling TSAP-ID. This string should contain an even number of hexadecimal digits. If you supply an odd number of digits, a hexadecimal “F” is added to the end, making an even number of digits. The default value is blanks. ZRMT-TSEL specifies the remote transport service access point selector. It is a string of hexadecimal digits (0 through 9 and A through F) up to 64 digits maximum. OSI/TS uses this field to build the calling TSAP-ID field of the CR-TPDU.
Commands and Responses ADD SU Command ZCLASS specifies the preferred transport protocol class to be used. Acceptable values are: ZOS4-VAL-CLASS-0 ZOS4-VAL-CLASS-1 ZOS4-VAL-CLASS-2 ZOS4-VAL-CLASS-3 ZOS4-VAL-CLASS-4 If not specified, the value of ZCLASS is determined by the settings of the parameters ZNETTYPE and ZMULTIPLEX, according to the matrix below: ZNETTYPE ZMULTIPLEX ZCLASS A A B B C C TRUE FALSE TRUE FALSE TRUE FALSE 2 0 3 1 4 4 For LAN networks, ZCLASS must be ZOS4-VAL-CLASS-4. For X.
Commands and Responses ADD SU Command 3 4 0 or 1 or 2 or 3 0 or 1 or 2 or 3 or 4 The default value of this parameter is the value of the ZCLASS attribute. ZTPDU-SIZE specifies the maximum length of a transport protocol data unit (TPDU) in bytes. Acceptable values are 128, 256, 512, 1024, 2048, 4096, and 8192 bytes. The values 4096 and 8192 are valid only when ZCLASS is 1, 2, 3, or 4. For X.
Commands and Responses ADD SU Command ZREXMIT-TIMEOUT specifies the time, in units of 0.01 seconds, before which an unacknowledged TPDU is retransmitted. Acceptable values range from 100 (1 second) through 3000 (30 seconds), with a default value of 1000 (10 seconds). This parameter is applicable only for protocol class 4. ZREF-TIMEOUT specifies the time, in units of 0.01 seconds, that the transport entity waits before reusing any reference or sequence number.
Commands and Responses ADD SU Command for protocol classes 1 and 3 only. Acceptable values range from 0 (0 seconds) through 18000 (180 seconds), with a default value of 12000 (120 seconds). ZCONN-TIMEOUT specifies the time, in 0.01-second units, that the transport entity waits for a response to a connect request transport protocol data unit. Acceptable values range from 300 (3 seconds) through 18000 (180 seconds), with a default value of 12000 (120 seconds). ZDISCONN-TIMEOUT specifies the time, in 0.
Commands and Responses ADD SU Command If no value is provided for ZX25CUG, ZX25CUG-TYPE will default to ZOS4VAL-X25CUG-TYPE-BASIC. If ZX25CUG is 0 to 99, ZX25CUG-TYPE can be any of the four values, and will default to ZOSI-VAL-X25CUG-TYPE-BASIC. If ZX25CUG is 100 to 9999, ZX25CUG-TYPE must be ZOS4-VAL-X25CUGTYPE-EXT or ZOS4-VAL-X25CUG-TYPE-EXTOA, and will default to ZOS4VAL-X25CUG-TYPE-EXT. If you do not provide a value, the value of the CUGTYPE attribute in X25AM is used.
Commands and Responses ADD SU Command Tokens in Response Buffer ZSPI-TKN-DATALIST and the final ZSPI-TKN-ENDLIST enclose a data list, as described in the Distributed Systems Management (DSM) Programming Manual. These tokens enclose the other response tokens only if the value of the header token ZSPI-TKN-MAXRESP is nonzero. No more than one data list can appear in the response. ZCOM-TKN-OBJTYPE specifies the type of object named in ZCOM-TKN-OBJNAME. The token value is ZCOM-OBJ-SU.
Commands and Responses ADD SU Command When you add a subdevice and do not specify a value for one of these attributes, that attribute is added with the corresponding ALTER SERVICE attribute value. When you add a subdevice and do specify a value for one of these attributes, that value overrides the corresponding ALTER SERVICE attribute value. Once a subdevice is added, changing the corresponding ALTER SERVICE attributes has no effect on the existing subdevice.
Commands and Responses ADD SU Command Table 5-4. OSI/TS Protocol Selection for X.25 Wide Area Networks Protocol Choice/Attribute X.25 Network X.25 Network with SNDCF and Full IP ZNSPDEV ZCLASS ZX25DESTADDR Specifies an X.25 line 0-4 1 Ignored for incoming calls 2 Required for outgoing calls OFF Ignored Ignored 1 Optional for 1984 X.25 2 Do not configure this attribute for 1980 X.25 1 Optional for incoming calls 2 Do not configure this attribute for 1980 X.25 Specifies an X.
Commands and Responses ADD SU Command Table 5-5.
Commands and Responses AGGREGATE PROCESS Command AGGREGATE PROCESS Command The AGGREGATE PROCESS command indicates the state of the specified process and returns the number of its associated subdevices that are in each possible state.
Commands and Responses AGGREGATE PROCESS Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of the process to be queried.
Commands and Responses AGGREGATE PROCESS Command ZPROC-STOPPED contains the number of processes in the STOPPED state. This field should always be 0. ZPROC-OTHER contains the number of processes in a state other than STARTED or STOPPED. ZSU-STARTED contains the number of subdevices, associated with the specified process, that are in the STARTED state. ZSU-STOPPED contains the number of subdevices, associated with the specified process, that are in the STOPPED state.
Commands and Responses ALLOWOPENS SU Command ALLOWOPENS SU Command The ALLOWOPENS SU command cancels the effect of the FORBIDOPENS SU command. It permits subsequent opens of the specified subdevices to complete successfully. This is a sensitive command.
Commands and Responses ALLOWOPENS SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses ALTER PROCESS Command ALTER PROCESS Command The ALTER PROCESS command changes the values of one or more attributes of a PROCESS object. This is a sensitive command. Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-FNAME32. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-STRING. ZOS4-MAP-ALTER-PROC-TSP def ZOS4-DDL-ALTER-PROC-TSP.
Commands and Responses ALTER PROCESS Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of the process whose attributes are to be altered.
Commands and Responses ALTER PROCESS Command ZLANDFT specifies the maximum number of seconds to do blocking of incoming Layer 2 frames. The value is an integer in the range of 01 through 100 (.01 through 1.00 seconds). The default is 03 (.03 seconds). ZLAN-IO-SIZE specifies the size of the I/O buffer sent to TLAM. The value is an integer in the range of 4000 through 32000 bytes.
Commands and Responses ALTER PROCESS Command ZCOM-TKN-OBJTYPE specifies the type of object named in ZCOM-TKN-OBJNAME. The token value is ZCOM-OBJ-PROCESS. ZCOM-TKN-OBJNAME is the name of the process whose attributes were to be altered. ZSPI-TKN-RETCODE indicates whether or not the command was successful. If the command failed, this token supplies the reason for the failure. Its use is described further in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses ALTER SERVICE Command ALTER SERVICE Command The ALTER SERVICE command changes the values of one or more attributes of the specified Layer 3 or Layer 4 SERVICE object. This is a sensitive command. Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-SERVICE Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-FNAME32. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-STRING. ZOS4-MAP-ALTER-SERV-L3 def ZOS4-DDL-ALTER-SERV-L3.
Commands and Responses ALTER SERVICE Command Tokens in Command Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 end. ZIP-DISCARD-UNSUP-THLD ZIP-DISCARD-REASM-THLD ZIP-X25-SNDCF ZX25DISCONN-DELAY ZX25NCON-MULTIPLEX ZX25CUG-TYPE ZX25BCUG ZX25RPOA ZX25RPOA-DNIC-CNT ZX25TRANSIT-DELAY ZESIS-HOLD-TIME ZIP-X25-SNDCF-1980-ADDR type type type type type type type type type type type type ZOS4-MAP-ALTER-SERV-L4 def ZOS4-DDL-ALTER-SERV-L4.
Commands and Responses ALTER SERVICE Command Tokens in Command Buffer (continued) 02 ZOUTBOUND-CR-ERR-THLD type 02 ZINBOUND-TPDU-PROTO-ERR-THLD type 02 ZOUTBOUND-TPDU-PROTO-ERR-THLD type 02 ZINBOUND-TPDU-XSUM-ERR-THLD type 02 ZL4-TIMEOUT-THLD type 02 ZCHECK-TSEL type 02 ZPASV-MUX type end. ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-BOOLEAN. ZSPI-DDL-BOOLEAN.
Commands and Responses ALTER SERVICE Command ZOS4-MAP-ALTER-SERV-L3 is an extensible structured token specifying the desired values for the Layer 3 service attributes. ZOS4-DDL-ALTER-SERV-L3 contains the following fields: ZX25ACCEPTCHG specifies whether an incoming call request that contains a request for the recipient to pay the charge is accepted. ZSPI-VAL-TRUE means that collect calls are accepted. ZSPI-VAL-FALSE means that collect calls are not accepted. The default is ZSPI-VAL-FALSE.
Commands and Responses ALTER SERVICE Command ZX25PVC specifies the channel number of the permanent virtual circuit (PVC) with which the X25AM subdevice to be created is bound. The value of ZX25PVC must be compatible with the values of the X25AM attributes PVCRANGE and SVCRANGE. Refer to the X25AM Management Programming Manual for information about how to set up an X.25 line as a PVC line. The range is 1 to 4095. For TRANSPAC networks, the range is 0 through 4095. The default is no PVC assigned.
Commands and Responses ALTER SERVICE Command provided. If you do not supply a value, the SYSGEN value of the X25AM line is used. The SYSGEN default value of X25AM is 4 (for both integers). 3 4 5 6 7 8 9 10 11 12 75 150 300 600 1200 2400 4800 9600 19200 48000 Note that these values are based on the CCITT X.25 recommendations for 1980 and 1984. ZESIS-ENABLE controls the ES-IS protocol. If set to ZSPI-VAL-TRUE, the protocol is enabled; if set to ZSPI-VAL-FALSE, the protocol is disabled.
Commands and Responses ALTER SERVICE Command ZESIS-NOTIFY-IS controls whether the ES-IS protocol reports its configuration whenever it determines that a new intermediate system is first available. This field is applicable only if ZESIS-ENABLE is set to ZSPI-VAL-TRUE. If ZESIS-NOTIFY-IS is set to ZSPI-VAL-TRUE, the configuration is reported; if set to ZSPI-VAL-FALSE, it is not reported. The default value is ZSPI-VALFALSE.
Commands and Responses ALTER SERVICE Command ZIP-XSUM controls whether a checksum is included in the outgoing IPDUs. This field is applicable only if the full IP subset is enabled. If ZIP-XSUM is set to ZSPI-VAL-TRUE, a checksum is included; if set to ZSPI-VAL-FALSE, a checksum is not included. The default value is ZSPI-VAL-FALSE. ZIP-DISCARD-GEN-THLD is the threshold value that the IP entity compares to the counter ZIPDISCARD-GEN.
Commands and Responses ALTER SERVICE Command enabled. The values range from 0 through 65535. If the threshold is set to 0, events are never generated. The default value is 0. ZIP-DISCARD-REASM-THLD is the threshold value that the IP entity compares to the counter ZIPDISCARD-REASM. An L3-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. This field is applicable only if the full IP subset is enabled.
Commands and Responses ALTER SERVICE Command ZOS4-VAL-X25CUG-TYPE-EXTOA Extended CUG format with outgoing access If no value is provided for ZX25CUG, ZX25CUG-TYPE will default to ZOS4VAL-X25CUG-TYPE-BASIC. If ZX25CUG is 0 to 99, ZX25CUG-TYPE can be any of the four values, and will default to ZOSI-VAL-X25CUG-TYPE-BASIC. If ZX25CUG is 100 to 9999, ZX25CUG-TYPE must be ZOSI-VAL-X25CUGTYPE-EXT or ZOS4-VAL-X25CUG-TYPE-EXTOA, and will default to ZOS4VAL-X25CUG-TYPE-EXT.
Commands and Responses ALTER SERVICE Command The default is ZSPI-VAL-TRUE . ZSPI-VAL-TRUE specifies 1980 addressing ; ZSPI-VAL-FALSE, specifies 1984 addressing. This attribute is used only for X.25 networks. ZOS4-MAP-ALTER-SERV-L4 is an extensible structured token specifying the desired values for the Layer 4 service attributes. ZOS4-DDL-ALTER-SERV-L4 contains the following fields: ZSEND-SECUR specifies the content of the protection field for CR-TPDUs and CC-TPDUs.
Commands and Responses ALTER SERVICE Command ZNETTYPE specifies network services in terms of quality. Possible values are: ZOS4-VAL-NETTYPE-A Network connection with an acceptable residual error rate: not signaled by disconnect or reset, with an acceptable rate of errors. ZOS4-VAL-NETTYPE-B Network connection with an acceptable residual error rate: not signaled by disconnect or reset, with an unacceptable rate of errors. ZOS4-VAL-NETTYPE-C Network connection with an unacceptable residual error rate.
Commands and Responses ALTER SERVICE Command ZALT-CLASS is the alternative protocol class used if the class specified in ZCLASS is not supported by the remote system. If ZCLASS has the value ZOS4-VAL-CLASS0, then ZALT-CLASS is not applicable. The values for this field are the same as for ZCLASS: ZOS4-VAL-CLASS-0 ZOS4-VAL-CLASS-1 ZOS4-VAL-CLASS-2 ZOS4-VAL-CLASS-3 ZOS4-VAL-CLASS-4 This parameter is not applicable if the preferred class is 0. Only one alternative class may be specified.
Commands and Responses ALTER SERVICE Command ZMULTIPLEX specifies whether more than one outgoing transport connection is mapped to one network connection (ZSPI-VAL-TRUE) or not (ZSPI-VAL-FALSE). The default value is ZSPI-VAL-FALSE. To be able to multiplex, two or more subdevices must have ZMULTIPLEX ON (ZSPI-VAL-TRUE) and have the same local and remote NSAPs.
Commands and Responses ALTER SERVICE Command ZWIN-TIMEOUT specifies the amount of time to wait before retransmitting up-to-date window information. This parameter is applicable to protocol class 4 only. Acceptable values range from 100 (1 second) through 25000 (250 seconds), with a default value of 1000 (10 seconds). ZTTR-TIMEOUT specifies the maximum amount of time to try reassignments after network connection failures. If the value is 0 seconds, no reassignment is performed.
Commands and Responses ALTER SERVICE Command ZINBOUND-CR-CONF-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZINBOUND-CR-CONF-ERR. An L4-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. The values range from 0 through 65535. If the threshold is set to 0, events are never generated. The default value is 0.
Commands and Responses ALTER SERVICE Command ZINBOUND-TPDU-XSUM-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZINBOUND-TPDU-XSUM-ERR. An L4-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. The values range from 0 through 65535. If the threshold is set to 0, events are never generated. The default value is 0.
Commands and Responses ALTER SERVICE Command ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed. Tokens in Response Buffer ZSPI-TKN-DATALIST and the final ZSPI-TKN-ENDLIST enclose a data list, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses ALTER SU Command ALTER SU Command The ALTER SU command changes the values of one or more attributes of an SU (subdevice) object. The SU object must be known to the OSI/TS subsystem (that is, it must have been added with an ADD command) before it can be altered. This is a sensitive command. Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-SU Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-FNAME32. token-type ZSPI-TYP-STRING.
Commands and Responses ALTER SU Command Tokens in Command Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 end.
Commands and Responses ALTER SU Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of a subdevice whose attributes are to be altered. This token is required, can occur multiple times, and can be an object-name template (wild-card name).
Commands and Responses ALTER SU Command making an even number of digits. NSAP values are administered by a central addressing authority. See the considerations for the ADD SU command (concerning protocol selection) for information on when to use this attribute. To reset this field to its default value set the first byte to ZOS4-VALADDR-RESET-BYTE. ZSEND-SECUR specifies the content of the protection field for CR-TPDUs and CC-TPDUs. If you do not provide a value, the protection field is omitted.
Commands and Responses ALTER SU Command the local LAN station address. This string should contain an even number of hexadecimal digits. If you supply an odd number of digits, a hexadecimal “F” is added to the end, making an even number of digits. See the considerations for the ADD SU command (concerning protocol selection) for information on when to use this attribute. To reset this field to its default value, set the first byte to ZOS4-VAL-ADDR-RESET-BYTE.
Commands and Responses ALTER SU Command ZX25REVERSECHG specifies whether an outgoing call request asks the recipient to pay the charges. ZSPI-VAL-TRUE indicates that the recipient is requested to pay the charges. ZSPI-VAL-FALSE indicates that the recipient is not requested to pay the charges. ZX25REMOTENET specifies the addressing conventions to be used when building the called address in the call request packet.
Commands and Responses ALTER SU Command ZLOC-TSEL specifies the local transport service access point selector; a string of hexadecimal digits (0 through 9 and A through F) up to 64 digits maximum. OSI/TS uses this field to build the called TSAP-ID field of the CR-TPDU. If the content of the field is blanks the CR-TPDU does not contain the called TSAP-ID. This string should contain an even number of hexadecimal digits.
Commands and Responses ALTER SU Command ZOS4-VAL-NETTYPE-B Network connection with an acceptable residual error rate: not signaled by disconnect or reset, with an unacceptable rate of errors. ZOS4-VAL-NETTYPE-C Network connection with an unacceptable residual error rate. The default value is ZOS4-VAL-NETTYPE-A. ZCLASS specifies the preferred transport protocol class used.
Commands and Responses ALTER SU Command ZTPDU-SIZE specifies the maximum length of a transport protocol data unit (TPDU) in bytes. Acceptable values are 128, 256, 512, 1024, 2048, 4096, and 8192. The values 4096 and 8192 are valid only when ZCLASS is 1, 2, 3, or 4. For X.25 subnetworks: OSI/TS will adjust the value of ZTPDU-SIZE to not exceed the value of the X25AM SYSGEN attribute MAXIOSIZE. Use the STATUS SU command to determine the actual ZTPDU-SIZE used when the connection was established.
Commands and Responses ALTER SU Command ZREF-TIMEOUT specifies the time, in units of 0.01 seconds, that the transport entity waits before reusing any reference or sequence number. Acceptable values range from 300 (3 seconds) through 18000 (180 seconds). ZMAX-REXMIT specifies the number of times unacknowledged transport protocol data units are retransmitted before shutting down the connection. This parameter is applicable only to protocol class 4. Acceptable values range from 1 through 8.
Commands and Responses ALTER SU Command the connection. Acceptable values range from 300 (3 seconds) through 18000 (180 seconds). ZX25PVC specifies the channel number of the permanent virtual circuit (PVC) with which the X25AM subdevice to be created is bound. The value of ZX25PVC must be compatible with the values of the X25AM attributes PVCRANGE and SVCRANGE. Refer to the X25AM Management Programming Manual for information about how to set up an X.25 line as a PVC line. The range is 1 to 4095.
Commands and Responses ALTER SU Command ZX25RPOA specifies the Recognized Private Operating Agency (RPOA) transit network(s) in the facility field of a call-request packet. This attribute is used only for X.25 networks. An RPOA transit network is indicated by the Data Network Identification Code (DNIC), which is an integer with the range 0 through 9999. There can be 0 through 7 DNIC's in the X25RPOA integer list. ZX25RPOA-DNIC-CNT specifies the number of DNIC's in the ZX25RPOA integer list.
Commands and Responses ALTER SU Command ZCOM-TKN-OBJNAME is the name of a subdevice whose attributes were to be altered. ZSPI-TKN-RETCODE indicates whether or not the command was successful. If the command failed, this token supplies the reason for the failure. Its use is described further in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses DELETE SU Command DELETE SU Command The DELETE SU command removes the specified subdevice (SU) object from the OSI/TS subsystem. It is a sensitive command. Command ZCOM-CMD-DELETE Object Type ZCOM-OBJ-SU Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32.
Commands and Responses DELETE SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses DELETE SU Command Operational Note For the DELETE SU command to be successful, the specified subdevices must be in the STOPPED state.
Commands and Responses FORBIDOPENS SU Command FORBIDOPENS SU Command The FORBIDOPENS SU command prevents subsequent attempts to open the specified subdevices from completing successfully. It cancels the effect of the ALLOWOPENS SU command. This is a sensitive command.
Commands and Responses FORBIDOPENS SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses GETVERSION NULL Command GETVERSION NULL Command The GETVERSION NULL command returns a product version banner identifying the version level of the OSI/TS subsystem. Command ZCOM-CMD-GETVERSION Object Type ZCOM-OBJ-NULL Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32. ZSPI-TYP-STRING.
Commands and Responses GETVERSION NULL Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses GETVERSION PROCESS Command GETVERSION PROCESS Command The GETVERSION PROCESS command returns a product version banner identifying the version level of the specified process. Command ZCOM-CMD-GETVERSION Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32.
Commands and Responses GETVERSION PROCESS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses INFO PROCESS Command INFO PROCESS Command The INFO PROCESS command returns the current values of the attributes for the specified process. The response contains the attributes established when the process was run (with a RUN command or a call to NEWPROCESS) or was last modified with an ALTER command.
Commands and Responses INFO PROCESS Command Tokens in Response Buffer (continued) ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . . ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST token-type ZSPI-TYP-ENUM. token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-SSCTL. Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command.
Commands and Responses INFO PROCESS Command ZOS4-MAP-INFO-PROC-TSP is an extensible structured token that contains the current attributes for the specified process. If multiple processes are specified in the response buffer, then one of these tokens is returned for each process. ZOS4-DDL-INFO-PROC-TSP contains the following fields: ZPRI is the Guardian 90 process priority. ZPROG-FNAME is the name of the code file run to create the process.
Commands and Responses INFO PROCESS Command ZLANDFT specifies the maximum number of seconds to do blocking of incoming Layer 2 frames. The value is an integer in the range of 01 through 100 (.01 through 1.00 seconds). ZLAN-IO-SIZE specifies the size of the I/O buffer sent to TLAM. The value is an integer in the range of 4000 through 32000 bytes. ZLAN-EXPAND-IO-SIZE specifies the size of the I/O buffer sent to TLAM when TLAM resides in another node.
Commands and Responses INFO ROUTE Command INFO ROUTE Command The INFO ROUTE command returns the current mapping and the NSAP address and associated information used to route the network protocol data units for a specified NSAP.
Commands and Responses INFO ROUTE Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of an NSAP route entry to be queried. This token is required, can occur multiple times, and can be an object-name template (wild-card name).
Commands and Responses INFO ROUTE Command these tokens is returned for each route. ZOS4-DDL-INFO-ROUTE-L3 contains the following fields: ZESIS-TYPE specifies the type of route entry. Some of the entries are deleted after a period of time. In the following descriptions, this is referred to as “aging out.” The other entries do not age out, this is referred to as a static entry.
Commands and Responses INFO ROUTE Command ZESIS-NSP-DEV specifies the I/O process that controls access to the subnetwork. ZESIS-HOLD-TIME is the total amount of time that route information is held. For entries that age out, the time value is displayed. For entries that are static, the value 0 is returned instead of a time value. The time is expressed in 0.01-second units. ZESIS-REMAIN-TIME is the amount of time remaining for the route information to be held.
Commands and Responses INFO SERVICE Command INFO SERVICE Command The INFO SERVICE command returns the current values of the attributes for the specified SERVICE object. This command requests information on a Layer 3 service, a Layer 4 service, or both. The response contains the configuration information established when the SERVICE object was created initially by OSI/TS or was last modified with an ALTER command.
Commands and Responses INFO SERVICE Command Tokens in Response Buffer (continued) 02 ZESIS-ES-CONF-TIME type ZSPI-DDL-INT2. 02 ZESIS-ES-GROUP-MAC-ADDR type ZOS4-DDL-CHAR12. 02 ZESIS-IS-GROUP-MAC-ADDR type ZOS4-DDL-CHAR12. 02 ZESIS-NOTIFY-IS type ZSPI-DDL-BOOLEAN. 02 ZESIS-XSUM type ZSPI-DDL-BOOLEAN. 02 ZESIS-QUERY-TIME type ZSPI-DDL-INT2. 02 ZESIS-QUERY-RETRY type ZSPI-DDL-UINT. 02 ZIP-NULL-LAYER type ZSPI-DDL-BOOLEAN. 02 ZIP-LIFETIME type ZSPI-DDL-INT2. 02 ZIP-XSUM type ZSPI-DDL-BOOLEAN.
Commands and Responses INFO SERVICE Command Tokens in Response Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 ZALT-CLASS ZTPDU-SIZE ZXSUM ZEXT-FRMT ZMULTIPLEX ZEXPEDITED ZREXMIT-TIMEOUT ZREF-TIMEOUT ZMAX-REXMIT ZINACTV-TIMEOUT ZWIN-TIMEOUT ZTTR-TIMEOUT ZTWR-TIMEOUT ZCONN-TIMEOUT ZDISCONN-TIMEOUT ZINBOUND-CR-CONG-THLD type type type type type type type type type type type type type type type ZSPI-DDL-ENUM. ZSPI-DDL-INT. ZSPI-DDL-BOOLEAN. ZSPI-DDL-BOOLEAN. ZSPI-DDL-BOOLEAN.
Commands and Responses INFO SERVICE Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of the SERVICE object for which you are requesting information.
Commands and Responses INFO SERVICE Command ZOS4-MAP-INFO-SERV-L3 ZOS4-MAP-INFO-SERV-L4 for the Layer 3 service for the Layer 4 service ZOS4-MAP-INFO-SERV-L3 is an extensible structured token that contains the current attributes of the specified Layer 3 service. ZOS4-DDL-INFO-SERV-L3 contains the following fields: ZX25ACCEPTCHG specifies whether an incoming call request that contains a request for the recipient to pay the charge is accepted. ZSPI-VAL-TRUE means that collect calls are accepted.
Commands and Responses INFO SERVICE Command ZX25PVC specifies the channel number of the permanent virtual circuit (PVC) with which the X25AM subdevice to be created is bound. The value of ZX25PVC must be compatible with the values of the X25AM attributes PVCRANGE and SVCRANGE. Refer to the X25AM Management Programming Manual for information about how to set up an X.25 line as a PVC line. The range is 1 to 4095. For TRANSPAC networks, the range is 0 through 4095.
Commands and Responses INFO SERVICE Command 7 8 9 10 11 12 1200 2400 4800 9600 19200 48000 Note that these values are based on the CCITT X.25 recommendations for 1980 and 1984. ZESIS-ENABLE controls the end system to intermediate system (ES-IS) protocol. If set to ZSPIVAL-TRUE, the protocol is enabled; if set to ZSPI-VAL-FALSE, the protocol is disabled. ZESIS-ES-CONF-TIME is the length of the interval at which the protocol must report its configuration to the subnetwork.
Commands and Responses INFO SERVICE Command ZESIS-QUERY-TIME is the maximum amount of time the ES-IS protocol should wait for a reply to its inquiry of NSAP-SNPA mapping before retrying or terminating its inquiry. This field is applicable only if ZESIS-ENABLE is set to ZSPI-VAL-TRUE. The waiting time is expressed in hundredths of a second (0.01 seconds per increment). The values range from 1 (0.01 second) through 65500 (655 seconds).
Commands and Responses INFO SERVICE Command a remainder of zero. This field is applicable only if the full IP subset is enabled. The values range from 0 through 65535. If the threshold is set to 0, events are never generated. ZIP-DISCARD-ADDR-THLD is the threshold value that the IP entity compares to the counter ZIPDISCARD-ADDR. An L3-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero.
Commands and Responses INFO SERVICE Command of X.25 virtual circuits in use increases with the number of open network connections. Therefore, this timer should be kept as short as possible to avoid resource problems. The waiting time is expressed in hundredths of a second (0.01 seconds per increment). The values range from 0 (immediate disconnect request) through 30000 (300 seconds).
Commands and Responses INFO SERVICE Command ZX25TRANSIT-DELAY shows the transit delay in the facility field of a call-request packet. This attribute is used only for X.25 networks. The value is in timestamp format between 0 through 6553 (hundredths of a second). ZESIS-HOLD-TIME specifies the interval at which the protocol keeps its configuration information. This attribute is valid only when ZESISENABLE is ON. The value is in a timestamp format from 100 to 65500 (hundredths of a second).
Commands and Responses INFO SERVICE Command attribute, Tandem OSI does not currently process this field. The values range from 0 through 32767 (0 being the highest priority). ZL4-WIN specifies the initial credit allocation to the remote transport entity. This is the number of TPDUs that can be sent by the remote transport entity without acknowledgment. This attribute is valid only when ZCLASS is ZOS4-VALCLASS-1, ZOS4-VAL-CLASS-2, ZOS4-VAL-CLASS-3, or ZOS4-VAL-CLASS-4.
Commands and Responses INFO SERVICE Command C C TRUE FALSE 4 4 ZALT-CLASS is the alternative protocol class used if the class specified in ZCLASS is not supported by the remote system. If ZCLASS has the value ZOS4-VAL-CLASS0, then ZALT-CLASS is not applicable.
Commands and Responses INFO SERVICE Command subdevices must have ZMULTIPLEX ON (ZSPI-VAL-TRUE) and have the same local and remote NSAPs. If these conditions are met, the maximum number of outgoing transport connections that are multiplexed together is determined by the value of the Layer 3 service attribute ZX25NCONMULTIPLEX. This attribute is valid only when ZCLASS is ZOS4-VALCLASS-2, ZOS4-VAL-CLASS-3, or ZOS4-VAL-CLASS-4. This attribute is used only for outgoing connections on X.25 networks.
Commands and Responses INFO SERVICE Command Only nonzero values are transmitted in the CR-TPDU. This parameter is applicable for protocol classes 1 and 3 only. Acceptable values range from 0 (0 seconds) through 18000 (180 seconds), with a default value of 9000 (90 seconds). ZTWR-TIMEOUT specifies the amount of time to wait for reassignment after network connection failures. If the value is 0 seconds, no reassignment is performed. Only nonzero values are transmitted in the CR-TPDU.
Commands and Responses INFO SERVICE Command ZINBOUND-CR-PROTO-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZINBOUND-CR-PROTO-ERR. An L4-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. The values range from 0 through 65535. If the threshold is set to 0, events are never generated.
Commands and Responses INFO SERVICE Command ZCHECK-TSEL specifies whether checksum fields are added to CC-TPDUs.This attribute is valid only when ZCLASS is 4. The possible values are: ZSPI-VAL-TRUE ZSPI-VAL-FALSE ZSPI-VAL-TRUE specifies to add checksum fields. The default is ZSPI-VALFALSE. ZPASV-MUX specifies indicates the sharing of X25AM SUs for attaching TSP SUs in anticipation of multiplexing performed by the remote transport entity.
Commands and Responses INFO SU Command INFO SU Command The INFO SU command returns the current values of the attributes for the specified subdevice. The response contains the configuration information established when the SU object was created with an ADD command or was last modified with an ALTER command.
Commands and Responses INFO SU Command Tokens in Response Buffer (continued) 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.
Commands and Responses INFO SU Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of a subdevice for which you are requesting information. This token is required, can occur multiple times, and can be an object-name template (wild card name).
Commands and Responses INFO SU Command ZOS4-MAP-INFO-SU-TSP is an extensible structured token containing the returned information for the subdevice identified in ZCOM-TKN-OBJNAME. ZOS4-DDL-INFO-SU-TSP contains the following fields: ZNSP-DEV shows the name of the SYSGEN-configured X25AM or TLAM I/O process controlling access to the subnetwork. ZDEL-TIME shows whether the TSP process will delete a subdevice after its last opener closes it.
Commands and Responses INFO SU Command The remaining 12 digits are the media access control (MAC) address. The MAC address specifies the local LAN station address. ZLAN-RMT-SNPA shows the remote LAN subnetwork address. This address is a hexadecimal string (0-9 and A-F) up to 14 digits long and is made up of two components. The first two hexadecimal digits are the link-level service access point selector (LSAP selector or LSEL); for OSI/TS, this value must be “FE.
Commands and Responses INFO SU Command ZX25REVERSECHG shows whether an outgoing call request asks the recipient to pay the charges. ZSPI-VAL-TRUE indicates that the recipient is requested to pay the charges. ZSPI-VAL-FALSE indicates that the recipient is not requested to pay the charges. ZX25REMOTENET shows the addressing conventions to be used when building the called address in the call request packet.
Commands and Responses INFO SU Command ZLOC-TSEL specifies the local transport service access point selector. It is a string of hexadecimal digits (0 through 9 and A through F) up to a maximum of 64 digits. OSI/TS uses this field to build the calling TSAP-ID field of the CR-TPDU. If the content of the field is blanks, the CR-TPDU will not contain the calling TSAP-ID. ZRMT-TSEL shows the remote transport service access point selector.
Commands and Responses INFO SU Command ZOS4-VAL-NETTYPE-C Network connection with an unacceptable residual error rate. ZCLASS shows the preferred transport protocol class. The values for this field are: ZOS4-VAL-CLASS-0 ZOS4-VAL-CLASS-1 ZOS4-VAL-CLASS-2 ZOS4-VAL-CLASS-3 ZOS4-VAL-CLASS-4 ZALT-CLASS shows the alternative protocol class used if the class specified in ZCLASS is not supported by the remote system. If ZCLASS has the value ZOS4-VALCLASS-0, then ZALT-CLASS is not applicable.
Commands and Responses INFO SU Command ZEXTENDED-FRMT shows whether the credit and sequence number of transport protocol data units should be in the extended format. If the parameter value is ZSPI-VALTRUE, extended format is used. If the parameter value is ZSPI-VAL-FALSE, the normal format is used. This parameter is meaningful only for transport protocol classes 2, 3, and 4.
Commands and Responses INFO SU Command applicable only for protocol class 4 communication. The waiting time is expressed in hundredths of a second (0.01 seconds per increment). The values range from 100 (1 second) through 5000 (50 seconds). ZWIN-TIMEOUT shows the amount of time to wait before retransmitting up-to-date window information. This parameter is applicable to protocol class 4 only. Acceptable values range from 100 (1 second) through 25000 (250 seconds).
Commands and Responses INFO SU Command ZIP-NULL-LAYER shows the generation of the header for the inactive subset (the null network layer) of the OSI internet protocol (IP). If set to ZSPI-VAL-TRUE, the header is enabled; if set to ZSPI-VAL-FALSE, the header is disabled. ZIP-X25-SNDCF shows whether the subnetwork conversion function (SNDCF) is to be used. This attribute is used only for X.25 networks. If set to ZSPI-VAL-TRUE, SNDCF is enabled; if set to ZSPI-VAL-FALSE, SNDCF is disabled.
Commands and Responses INFO SU Command ZSPI-TKN-RETCODE shows whether or not the command was successful. If the command failed, this token supplies the reason for the failure. Its use is described further in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses LISTOBJECTS NULL Command LISTOBJECTS NULL Command The LISTOBJECTS NULL command returns a controllable list of object types and object names for the specified process, its related services, and its associated subdevices. Command ZCOM-CMD-LISTOBJECTS Object Type ZCOM-OBJ-NULL Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE TYPE.
Commands and Responses LISTOBJECTS NULL Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses LISTOBJECTS NULL Command ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-CONTEXT used in returning multiple response messages, is described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses LISTOBJECTS PROCESS Command LISTOBJECTS PROCESS Command The LISTOBJECTS PROCESS command returns the name of the specified TSP process.
Commands and Responses LISTOBJECTS PROCESS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZCOM-TKN-SUB specifies that the command is to return the names of objects (of all types) subordinate to the specified process. The only value supported is ZCOM-VALSUB-ALL. If this token is present, the effect of this command is the same as that of the LISTOBJECTS NULL command.
Commands and Responses LISTOBJECTS PROCESS Command ZSPI-TKN-RETCODE indicates whether or not the command was successful. If the command failed, this token supplies the reason for the failure. Its use is described further in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses LISTOBJECTS SERVICE Command LISTOBJECTS SERVICE Command The LISTOBJECTS SERVICE command returns the names of the SERVICE objects supported by the specified process.
Commands and Responses LISTOBJECTS SERVICE Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses LISTOBJECTS SERVICE Command ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-CONTEXT used in returning multiple response messages, is described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses LISTOBJECTS SU Command LISTOBJECTS SU Command The LISTOBJECTS SU command returns a controllable list of names of subdevices in the specified OSI/TS subsystem.
Commands and Responses LISTOBJECTS SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses LISTOBJECTS SU Command ZSPI-TKN-CONTEXT used in returning multiple response messages, is described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses LISTOPENS SU Command LISTOPENS SU Command The LISTOPENS SU command returns information about all currently existing opens of one or more TSP subdevices. Command ZCOM-CMD-LISTOPENS Object Type ZCOM-OBJ-SU Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32.
Commands and Responses LISTOPENS SU Command Tokens in Response Buffer (continued) ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . . ZSPI-TKN-ENDLIST 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-SSCTL. token-type ZSPI-TYP-BYTESTRING.
Commands and Responses LISTOPENS SU Command Multiple data lists can appear in the response, each containing information about the opens of a different subdevice. In addition, multiple response messages can be returned. ZCOM-TKN-OBJTYPE specifies the type of object named in ZCOM-TKN-OBJNAME. The token value is ZCOM-OBJ-SU. ZCOM-TKN-OBJNAME is the name of a subdevice whose opens were requested.
Commands and Responses LISTOPENS SU Command ZUSERID is the Guardian 90 user identifier that the opening process was running at the time of the open. ZPRIM-CPU is the number of the CPU in which the primary process of the opener is running. ZPRIM-PIN is the process identification number of the primary process of the opener, or 0 if the primary process of the opener is not running. ZBKUP-CPU is the number of the CPU in which the backup process of the opener is running.
Commands and Responses RESETSTATS PROCESS Command RESETSTATS PROCESS Command The RESETSTATS PROCESS command returns the current statistics for the specified process, then resets the statistics counters to zero. This is a sensitive command; however, it does not change the state of any OSI/TS subsystem objects.
Commands and Responses RESETSTATS PROCESS Command Tokens in Response Buffer (continued) 02 ZNCB-TBL-MIN-EVER-FREE 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. type ZSPI-DDL-INT. ZNCB-TBL-ENTRY-CNT type ZSPI-DDL-INT. ZNCB-TBL-ENTRY-SIZE type ZSPI-DDL-INT. ZSCB-TBL-FREE-CNT type ZSPI-DDL-INT. ZSCB-TBL-ALLOC-FAIL type ZSPI-DDL-INT. ZSCB-TBL-MIN-EVER-FREE type ZSPI-DDL-INT. ZSCB-TBL-ENTRY-CNT type ZSPI-DDL-INT. ZSCB-TBL-ENTRY-SIZE type ZSPI-DDL-INT.
Commands and Responses RESETSTATS PROCESS Command ZCOM-TKN-OBJNAME is the name of the process for which the statistics counters are to be reset. This token is required, must occur only once, and must be the same as the TSP process name specified in either ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR. ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed.
Commands and Responses RESETSTATS PROCESS Command ZTCB-TBL-ALLOC-FAIL contains the number of failed attempts to allocate a TCB. ZTCB-TBL-MIN-EVER-FREE is the minimum number of TCB entries ever available for allocation. ZTCB-TBL-ENTRY-CNT contains the total number of TCB entries in the table. ZTCB-TBL-ENTRY-SIZE contains the size of a TCB entry, in octets. ZRCB-TBL-FREE-CNT contains the number of request control block (RCB) entries available for allocation.
Commands and Responses RESETSTATS PROCESS Command ZSCB-TBL-FREE-CNT is the number of subdevice control block (SCB) entries available for allocation. ZSCB-TBL-ALLOC-FAIL contains the number of failed attempts to allocate an SCB. ZSCB-TBL-MIN-EVER-FREE contains the minimum number of SCB entries ever available for allocation. ZSCB-TBL-ENTRY-CNT contains the total number of SCB entries in the table. ZSCB-TBL-ENTRY-SIZE contains the size of an SCB entry, in octets.
Commands and Responses RESETSTATS PROCESS Command ZPOOL-MAX-FRAG contains the maximum number of pool fragments. ZRIOCBS-CURR shows the number of request I/O control blocks currently allocated and being used. These control blocks are used to process system and user requests and responses. ZRIOCBS-MAX shows the largest number of request I/O control blocks allocated and being used at once, since the last time the statistics were reset.
Commands and Responses RESETSTATS PROCESS Command ZSPI-TKN-RETCODE indicates whether or not the command was successful. If the command failed, this token supplies the reason for the failure. Its use is described further in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses RESETSTATS SERVICE Command RESETSTATS SERVICE Command The RESETSTATS SERVICE command returns the current statistics for the specified SERVICE object(s) from the designated TSP process, then resets the statistics counters to zero. This is a sensitive command; however, it does not change the state of any OSI/TS subsystem objects.
Commands and Responses RESETSTATS SERVICE Command Tokens in Response Buffer (continued) 02 ZIP-DISCARD-CONG-THLD type ZSPI-DDL-INT2. 02 ZIP-DISCARD-ADDR-THLD type ZSPI-DDL-INT2. 02 ZIP-DISCARD-LIFE-THLD type ZSPI-DDL-INT2. 02 ZIP-DISCARD-UNSUP-THLD type ZSPI-DDL-INT2. 02 ZIP-DISCARD-REASM-THLD type ZSPI-DDL-INT2. end. ZOS4-MAP-STATS-SERV-L4 def ZOS4-DDL-STATS-SERV-L4.
Commands and Responses RESETSTATS SERVICE Command Tokens in Response Buffer (continued) 02 ZMAX-EVER-CONN type ZSPI-DDL-INT2. 02 ZINBOUND-CR-CONG-THLD type ZSPI-DDL-INT2. 02 ZINBOUND-CR-CONF-ERR-THLD type ZSPI-DDL-INT2. 02 ZOUTBOUND-CR-CONF-ERR-THLD type ZSPI-DDL-INT2. 02 ZINBOUND-CR-PROTO-ERR-THLD type ZSPI-DDL-INT2. 02 ZOUTBOUND-CR-ERR-THLD type ZSPI-DDL-INT2. 02 ZINBOUND-TPDU-PROTO-ERR-THLD type ZSPI-DDL-INT2. 02 ZOUTBOUND-TPDU-PROTO-ERR-THLD type ZSPI-DDL-INT2.
Commands and Responses RESETSTATS SERVICE Command ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed. ZSPI-TKN-CONTEXT is used to get the next response message if multiple response messages are returned, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses RESETSTATS SERVICE Command ZIP-PDUS-RECV contains the number of internet protocol data units (IPDUs) received by the OSI internet protocol (IP) entity. ZIP-PDUS-SENT contains the number of IPDUs sent by the IP entity. ZIP-OCTETS-RECV contains the number of octets of user data received by the IP entity. ZIP-OCTETS-SENT contains the number of octets of user data sent by the IP entity.
Commands and Responses RESETSTATS SERVICE Command zero. If the threshold is zero, events are never generated. The default is zero. This parameter is applicable only if the full subset of the IP is enabled. ZIP-DISCARD-CONG-THLD contains the threshold value that the IP entity compares the counter ZIPDISCARD-CONG. An L3-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero.
Commands and Responses RESETSTATS SERVICE Command ZOS4-MAP-STATS-SERV-L4 is an extensible structured token that contains the current statistics for the Layer 4 SERVICE, as they were before being reset. This token is present only if Layer 4 statistics were to be reset. ZOS4-DDL-STATS-SERV-L4 contains the following fields: ZRESET-TMSTP is the timestamp indicating when the counters were last reset. ZSAMPLE-TMSTP is the timestamp indicating when the current sample was taken.
Commands and Responses RESETSTATS SERVICE Command ZINBOUND-CR-CONF-ERR is the number of times OSI/TS refuses a transport connection request due to negotiation failure, duplicate source reference, mismatched references, reference overflow, refusal on the network connection, non-attachment of session entity to TSAP, or unknown address.
Commands and Responses RESETSTATS SERVICE Command ZOPEN-CONN is the number of currently open transport connections. This number is modified every time a transport connection is established or released. ZWIN-TIMEOUT is the time, in 0.01-second units, that the transport entity will wait before retransmission of up-to-date window information. This parameter is applicable only to protocol class 4. ZLOC-REXMIT-TIME is the time, in 0.
Commands and Responses RESETSTATS SERVICE Command ZOUTBOUND-CR-CONF-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZOUTBOUND-CR-CONF-ERR. An L4-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. If the threshold is zero, events are never generated. Acceptable values range from 0 through 65535, with a default of 0.
Commands and Responses RESETSTATS SERVICE Command ZL4-TIMEOUT-THLD is the threshold value that the Transport Layer compares to the counter ZL4TIMEOUT. An L4-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. If the threshold is zero, events are never generated. Acceptable values range from 0 through 65535, with a default of 0. ZSPI-TKN-RETCODE indicates whether or not the command was successful.
Commands and Responses RESETSTATS SU Command RESETSTATS SU Command The RESETSTATS SU command returns the current statistics for the specified subdevice, then resets the statistics counters to zero. This is a sensitive command; however, it does not change the state of any OSI/TS subsystem objects.
Commands and Responses RESETSTATS SU Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of a subdevice for which the statistics counters are to be reset.
Commands and Responses RESETSTATS SU Command ZOS4-MAP-STATS-SU-TSP is an extensible structured token that contains the current statistics for a subdevice, as they were before being reset. One of these tokens is present for every subdevice specified in the ZCOM-TKN-OBJNAME token(s) in the command. ZOS4-DDLSTATS-SU-TSP contains the following fields: ZRESET-TMSTP is the timestamp indicating when the counters were last reset. ZSAMPLE-TMSTP is the timestamp indicating when the current sample was taken.
Commands and Responses RESETSTATS SU Command ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-CONTEXT used in returning multiple response messages, is described in the Distributed Systems Management (DSM) Programming Manual. Operational Note The RESETSTATS command updates the reset timestamp counters after the response is sent.
Commands and Responses START PROCESS Command START PROCESS Command The START PROCESS command places the specified process in the STARTED state. This is a sensitive command. Command ZCOM-CMD-START Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Commands and Responses START PROCESS Command ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed. Tokens in Response Buffer ZSPI-TKN-DATALIST and the final ZSPI-TKN-ENDLIST enclose a data list, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses START SU Command START SU Command The START SU command initiates the operation of the specified subdevice and places it in the STARTED state. This is a sensitive command.
Commands and Responses START SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses STATISTICS PROCESS Command STATISTICS PROCESS Command The STATISTICS PROCESS command returns the current statistics for the specified process, but does not reset the statistics counters.
Commands and Responses STATISTICS PROCESS Command Tokens in Response Buffer (continued) 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. ZNCB-TBL-ENTRY-CNT type ZSPI-DDL-INT. ZNCB-TBL-ENTRY-SIZE type ZSPI-DDL-INT. ZSCB-TBL-FREE-CNT type ZSPI-DDL-INT. ZSCB-TBL-ALLOC-FAIL type ZSPI-DDL-INT. ZSCB-TBL-MIN-EVER-FREE type ZSPI-DDL-INT. ZSCB-TBL-ENTRY-CNT type ZSPI-DDL-INT. ZSCB-TBL-ENTRY-SIZE type ZSPI-DDL-INT. ZTLE-TBL-FREE-CNT type ZSPI-DDL-INT.
Commands and Responses STATISTICS PROCESS Command ZCOM-TKN-OBJNAME is the name of the process for which statistics are to be returned. This token is required, must occur only once, and must be the same as the TSP process name specified in either ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR. ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed.
Commands and Responses STATISTICS PROCESS Command ZTCB-TBL-ALLOC-FAIL contains the number of failed attempts to allocate a TCB. ZTCB-TBL-MIN-EVER-FREE is the minimum number of TCB entries ever available for allocation. ZTCB-TBL-ENTRY-CNT contains the total number of TCB entries in the table. ZTCB-TBL-ENTRY-SIZE contains the size of a TCB entry, in octets. ZRCB-TBL-FREE-CNT contains the number of request control block (RCB) entries available for allocation.
Commands and Responses STATISTICS PROCESS Command ZSCB-TBL-FREE-CNT is the number of subdevice control block (SCB) entries available for allocation. ZSCB-TBL-ALLOC-FAIL contains the number of failed attempts to allocate an SCB. ZSCB-TBL-MIN-EVER-FREE contains the minimum number of SCB entries ever available for allocation. ZSCB-TBL-ENTRY-CNT contains the total number of SCB entries in the table. ZSCB-TBL-ENTRY-SIZE contains the size of an SCB entry, in octets.
Commands and Responses STATISTICS PROCESS Command ZPOOL-MAX-FRAG contains the maximum number of pool fragments. ZRIOCBS-CURR shows the number of request I/O control blocks currently allocated and being used. These control blocks are used to process system and user requests and responses. ZRIOCBS-MAX shows the largest number of request I/O control blocks allocated and being used at once, since the last time the statistics were reset.
Commands and Responses STATISTICS PROCESS Command ZSPI-TKN-RETCODE indicates whether or not the command was successful. If the command failed, this token supplies the reason for the failure. Its use is described further in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses STATISTICS SERVICE Command STATISTICS SERVICE Command The STATISTICS SERVICE command returns the current statistics for the specified SERVICE object(s) from the designated TSP process, but does not reset the statistics counters.
Commands and Responses STATISTICS SERVICE Command Tokens in Response Buffer (continued) 02 ZIP-DISCARD-ADDR-THLD type ZSPI-DDL-INT2. 02 ZIP-DISCARD-LIFE-THLD type ZSPI-DDL-INT2. 02 ZIP-DISCARD-UNSUP-THLD type ZSPI-DDL-INT2. 02 ZIP-DISCARD-REASM-THLD type ZSPI-DDL-INT2. end. ZOS4-MAP-STATS-SERV-L4 def ZOS4-DDL-STATS-SERV-L4.
Commands and Responses STATISTICS SERVICE Command Tokens in Response Buffer (continued) 02 ZINBOUND-CR-CONF-ERR-THLD type ZSPI-DDL-INT2. 02 ZOUTBOUND-CR-CONF-ERR-THLD type ZSPI-DDL-INT2. 02 ZINBOUND-CR-PROTO-ERR-THLD type ZSPI-DDL-INT2. 02 ZOUTBOUND-CR-ERR-THLD type ZSPI-DDL-INT2. 02 ZINBOUND-TPDU-PROTO-ERR-THLD type ZSPI-DDL-INT2. 02 ZOUTBOUND-TPDU-PROTO-ERR-THLD type ZSPI-DDL-INT2. 02 ZINBOUND-TPDU-XSUM-ERR-THLD type ZSPI-DDL-INT2. 02 ZL4-TIMEOUT-THLD type ZSPI-DDL-INT2. end.
Commands and Responses STATISTICS SERVICE Command ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed. ZSPI-TKN-CONTEXT is used to get the next response message if multiple response messages are returned, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses STATISTICS SERVICE Command ZIP-PDUS-RECV contains the number of internet protocol data units (IPDUs) received by the OSI internet protocol (IP) entity. ZIP-PDUS-SENT contains the number of IPDUs sent by the IP entity. ZIP-OCTETS-RECV contains the number of octets of user data received by the IP entity. ZIP-OCTETS-SENT contains the number of octets of user data sent by the IP entity.
Commands and Responses STATISTICS SERVICE Command default is zero. This parameter is applicable only if the full subset of the IP is enabled. ZIP-DISCARD-CONG-THLD contains the threshold value that the IP entity compares the counter ZIPDISCARD-CONG. An L4-THLD event is generated whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. If the threshold is zero, events are never generated. The default is zero.
Commands and Responses STATISTICS SERVICE Command ZOS4-MAP-STATS-SERV-L4 is an extensible structured token that contains the current statistics for the Layer 4 SERVICE. This token is present only if Layer 4 statistics were to be reset. ZOS4DDL-STATS-SERV-L4 contains the following fields: ZRESET-TMSTP is the timestamp indicating when the counters were last reset. ZSAMPLE-TMSTP is the timestamp indicating when the current sample was taken.
Commands and Responses STATISTICS SERVICE Command ZINBOUND-CR-CONF-ERR is the number of times OSI/TS refuses a transport connection request due to negotiation failure, duplicate source reference, mismatched references, reference overflow, refusal on the network connection, nonattachment of session entity to TSAP, or unknown address.
Commands and Responses STATISTICS SERVICE Command ZOPEN-CONN is the number of currently open transport connections. This number is modified every time a transport connection is established or released. ZWIN-TIMEOUT is the time, in 0.01-second units, that the transport entity waits before retransmission of up-to-date window information. This parameter is applicable only to protocol class 4. ZLOC-REXMIT-TIME is the time, in 0.
Commands and Responses STATISTICS SERVICE Command ZOUTBOUND-CR-CONF-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZOUTBOUND-CR-CONF-ERR. An L4-THLD event is generated whenever the counter value is nonzero dividing the counter value by the threshold value leaves a remainder of zero. If the threshold is zero, events are never generated. Acceptable values range from 0 through 65535, with a default of 0.
Commands and Responses STATISTICS SERVICE Command ZL4-TIMEOUT-THLD is the threshold value that the Transport Layer compares to the counter ZL4TIMEOUT. An L4-THLD event is generated whenever the counter value is nonzero dividing the counter value by the threshold value leaves a remainder of zero. If the threshold is zero, events are never generated. Acceptable values range from 0 to 65535, with a default of 0. ZSPI-TKN-RETCODE indicates whether or not the command was successful.
Commands and Responses STATISTICS SU Command STATISTICS SU Command The STATISTICS SU command returns statistics for the specified subdevice, but does not reset the statistics counters.
Commands and Responses STATISTICS SU Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of a subdevice for which statistics are to be returned.
Commands and Responses STATISTICS SU Command ZOS4-MAP-STATS-SU-TSP is an extensible structured token that contains the current status information for a subdevice. One of these tokens is present for each subdevice specified in the ZCOM-TKN-OBJNAME token(s) in the command. ZOS4-DDL-STATS-SU-TSP contains the following fields: ZRESET-TMSTP is the timestamp indicating when the statistics were last reset. ZSAMPLE-TMSTP is the timestamp indicating when the current sample was taken.
Commands and Responses STATISTICS SU Command ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. ZSPI-TKN-CONTEXT used in returning multiple response messages, is described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses STATUS PROCESS Command STATUS PROCESS Command The STATUS PROCESS command returns current information about the specified process. Command ZCOM-CMD-STATUS Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32. ZSPI-TYP-STRING. ZSPI-TYP-STRING. ZSPI-TYP-TIMESTAMP.
Commands and Responses STATUS PROCESS Command Tokens in Response Buffer (continued) ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . . ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST token-type ZSPI-TYP-ENUM. token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-SSCTL. Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command.
Commands and Responses STATUS PROCESS Command ZCOM-TKN-OBJSTATE is described in the Communications Management Programming Manual. ZOS4-MAP-STATUS-PROC-TSP is an extensible structured token that contains the current status information for the specified process. ZOS4-DDL-STATUS-PROC contains the following fields: ZPPID contains the PID (CPU and PIN) of the primary TSP process. ZBPID contains the PID (CPU and PIN) of the backup TSP process. If there is no backup process, ZBPID contains zero.
Commands and Responses STATUS PROCESS Command ZOS4-VAL-TRACE-OPT-TSP-NETIO I/O operations to the Network Layer I/O process ZCOLL-PID is the process identification number of the trace collector process. ZTRACE-FILE is the fully qualified Guardian 90 file name in which the trace records for the specified process are stored. ZOWNERID is the owner ID currently being used by the specified process. ZCREATE-TMSTP is the process creation timestamp.
Commands and Responses STATUS PROCESS Command ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses STATUS SU Command STATUS SU Command The STATUS SU command returns current information about the specified subdevice. Command ZCOM-CMD-STATUS Object Type ZCOM-OBJ-SU Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-CONTEXT token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32. ZSPI-TYP-STRING. ZSPI-TYP-STRING.
Commands and Responses STATUS SU Command Tokens in Response Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 end. ZX25PORT ZLAN-LOC-SNPA ZLAN-RMT-SNPA ZX25DISC-REASON ZX25CLEAR-CAUSE ZX25-DIAGCODE ZNSP-SUBSYS ZNSP-FS-ERRCODE ZNSP-DSM-RETCODE ZNSP-DSM-SUBCODE1 ZNSP-DSM-SUBCODE2 ZCREATE-TMSTP ZLST-OPEN-TMSTP ZLST-CLOSE-TMSTP ZLST-ALTER-TMSTP ZOPENER ZOPENER-LEN ZUSER-ID ZDEL-TIME ZRCV-CDT-WIN ZSND-CDT-WIN ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . .
Commands and Responses STATUS SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses STATUS SU Command ZCOM-VAL-SUMSTATE-STOPPED ZCOM-VAL-SUMSTATE-STOPPING Subdevice is stopped. Subdevice is stopping. ZOPEN-CNT is the current number of opens of the specified subdevice. ZOPENS-ALLOWED indicates whether the specified subdevice is currently allowing opens to be successfully completed. The ALLOWOPENS SU and the FORBIDOPENS SU commands change the value of this field. ZLAST-ERR is the last error returned to the application process using this subdevice.
Commands and Responses STATUS SU Command ZOS4-VAL-DISC-FROM-NET-DISC ZOS4-VAL-DISC-FROM-NET-RESET ZOS4-VAL-DISC-INTERNAL-ERR ZOS4-VAL-DISC-FROM-ABORT-CMD The values for substates of ZTCON-STATE = ZOS4-VAL-DR-RECEIVED are: ZOS4-VAL-REASON-NONE ZOS4-VAL-REASON-CONG-TSAP ZOS4-VAL-REASON-NO-L5-ENTITY ZOS4-VAL-REASON-ADDR-UNKWN ZOS4-VAL-REASON-USER-INITIATED ZOS4-VAL-REASON-CONG-L4-ENTITY ZOS4-VAL-REASON-NEGOT-FAILED ZOS4-VAL-REASON-DUP-SREF-NSAPS ZOS4-VAL-REASON-REFS-MISMATCH ZOS4-VAL-REASON-PROTOCOL-ERR ZOS4-
Commands and Responses STATUS SU Command ZNSP-SU shows the name of the network I/O process subdevice created by TSP to convey transport protocol data units (TPDUs). The name shows either a network I/O process subdevice currently in use for an active transport connection or for receiving a connection, or the name is the network I/O process subdevice last used by the TSP to convey TPDUs over this subdevice. ZLOC-NSAP shows the local network service access point.
Commands and Responses STATUS SU Command ZNSP-FS-ERRCODE shows the Guardian 90 file-system error code returned by the NSP process if an error has occurred. ZNSP-DSM-RETCODE shows for the NSP process, the DSM return code of the last DSM event. ZNSP-DSM-SUBCODE1 hows for the NSP process, the DSM subcode 1 value, which indicates the number of the token in error. ZNSP-DSM-SUBCODE2 shows for the NSP process, the DSM subcode 2 value, which indicates the offset to the token in error.
Commands and Responses STATUS SU Command ZDEL-TIME shows whether subdevice is deleted after the last opener closes it. ZRCV-CDT-WIN shows the number of credits granted to the remote transport entity for the current transport connection (only for connections using transport class 3 or 4). These credits are conveyed in the credit field of AK-APDUs sent to the remote transport entity. Receive Credit can fluctuate but will never exceed the configured L4WINDOW size.
Commands and Responses STOP PROCESS Command STOP PROCESS Command The STOP PROCESS command stops the specified process in an orderly manner, if it is not in use. Once this command has completed successfully, the process will no longer exist. This is a sensitive command.
Commands and Responses STOP PROCESS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses STOP SU Command STOP SU Command The STOP SU command terminates the operation of the specified subdevice, if the subdevice is not open, and places it in the STOPPED state. This is a sensitive command.
Commands and Responses STOP SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. These tokens are optional and, with the exception of ZSPI-TKN-COMMENT, duplicate occurrences are not allowed.
Commands and Responses STOP SU Command Operational Note If there is an opener for the specified subdevice, the state of the subdevice will be STOPPING. After the last opener has closed the SU, the state will be STOPPED.
Commands and Responses SUSPEND PROCESS Command SUSPEND PROCESS Command The SUSPEND PROCESS command changes the summary state of a STARTED process to the suspending state until the suspension is complete, and finally to the suspended (SUSP) state. The process is not terminated. The attributes of a process can be changed (with the ALTER PROCESS command) only if the process is in the suspended state. This command reverses the effect of the ACTIVATE PROCESS command. It is a sensitive command.
Commands and Responses SUSPEND PROCESS Command ZCOM-TKN-OBJNAME is the name of the process to be suspended. This token is required, must occur only once, and must be the same as the TSP process name specified in either ZSPITKN-MANAGER or ZCOM-TKN-XMGR. ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed.
Commands and Responses SWITCH PROCESS Command SWITCH PROCESS Command The SWITCH PROCESS command initiates a takeover by the backup TSP process. This is a sensitive command. Command ZCOM-CMD-SWITCH Object Type ZCOM-OBJ-PROCESS Object Type ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-SWITCH-CPU ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32.
Commands and Responses SWITCH PROCESS Command ZCOM-TKN-SWITCH-CPU specifies the CPU number of the process to be switched. This token is required; duplicate occurrences of this token are not allowed. ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. This token is optional; duplicate occurrences are not allowed. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses TRACE PROCESS Command TRACE PROCESS Command The TRACE PROCESS command initiates, modifies, or terminates the gathering of trace information by the specified process. OSI/TS uses the tracing facilities provided by the Subsystem Control Point (SCP). This is a sensitive command. Command ZCOM-CMD-TRACE Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZCOM-TKN-TRACE-OPT ZCOM-TKN-TRACE-BKUP ZCOM-MAP-TRACE-MODIF def ZCOM-DDL-TRACE-MODIF.
Commands and Responses TRACE PROCESS Command Tokens in Command Buffer ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system (ZCOM-TKN-XMGR) process name of the TSP process to which SCP is to send this command. This token is optional and must occur only once in the command. ZCOM-TKN-OBJNAME is the name of the process to be traced.
Commands and Responses TRACE PROCESS Command The default value of ZREC-SIZE may not be large enough to allow complete formatting of trace records using PTrace. Formatting of DSM commands and responses (using the formatted or LABEL facility in PTrace) requires a large ZREC-SIZE to accommodate the entire SPI buffer. If you are using this feature, you should specify a ZREC-SIZE of between 1000 and 4000 bytes. ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual.
6 Event Messages This section describes the contents and meaning of all event messages generated by the OSI/TS subsystem. In this section, command numbers, object types, and all tokens and their values are represented in the Data Definition Language (DDL). For a quick explanation of DDL, refer to the appendix “Overview of DDL for SPI” in the Distributed Systems Management (DSM) Programming Manual.
Event Messages Table 6-1.
Event Messages Tokens in All Event Event-message buffers, like any other SPI buffers, contain header tokens and dataMessages portion tokens. The header and data-portion tokens that appear in all OSI/TS event messages are listed in Table 6-2. Tokens that appear only in certain event messages are listed and described with the individual messages, in the remainder of this section. Tokens that start with a ZX____ are for D-series systems only.
Event Messages Event-Message Descriptions Event-Message Descriptions The following pages explain in detail each event message that can be issued by the OSI/TS subsystem. The descriptions appear in ascending order by event number; that is, in ascending order by the ZOS4-EVT- values. Each description includes a box containing the tokens that OSI/TS can place in the message buffer in addition to the common tokens listed in Table 6-2.
Event Messages Event-Message Descriptions 66: ZOS4-EVT-SM-ERR This is a critical event. The OSI/TS subsystem detected an internal state-machine error. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-CRTPID. Tandem Internal Tokens ZOS4-TKN-SMID ZOS4-TKN-SM-STATE ZOS4-TKN-SM-EVT ZOS4-TKN-SM-ACT token-type token-type token-type token-type ZSPI-TYP-UINT. ZSPI-TYP-UINT. ZSPI-TYP-UINT.
Event Messages Event-Message Descriptions 74: ZOS4-EVT-INTL-ERR This is a critical event. The OSI/TS subsystem detected an unrecoverable internal error. The affected OSI/TS process abends. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-CRTPID. Tandem Internal Tokens ZOS4-TKN-CODE-SEG ZGRD-TKN-PREGISTER ZGRD-TKN-EREGISTER token-type ZSPI-TYP-UNIT. token-type ZSPI-TYP-UINT.
Event Messages Event-Message Descriptions 90: ZOS4-EVT-PROCABEND The TSP process, primary or backup, terminated abnormally due to an unrecoverable error. If the primary abends, the backup takes over. If the backup abends, the primary attempts to create a new process. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-CRTPID.
Event Messages Event-Message Descriptions 106: ZOS4-EVT-INSUFFBUF A request for buffer space was not satisfied. This is normally a recoverable condition; it does not cause an abend. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-CRTPID. Tandem Internal Tokens ZOS4-TKN-CODE-SEG ZGRD-TKN-PREGISTER ZGRD-TKN-EREGISTER ZOS4-TKN-REQ-SIZE token-type token-type token-type token-type ZSPI-TYP-UNIT.
Event Messages Event-Message Descriptions 301: ZOS4-EVT-TKOVR The backup process has taken over from the primary process. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC ZOS4-TKN-TKOVR-CAUSE Conditional Token token-type token-type token-type token-type ZOS4-TKN-CPU Event-Message Text token-type ZSPI-TYP-UINT. process-name, Takeover By Backup: { { { { { ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-CRTPID. ZSPI-TYP-ENUM.
Event Messages Event-Message Descriptions ZOS4-VAL-CAUSE-SWITCH The operator issued the SCF PRIMARY command. ZOS4-VAL-CAUSE-UNKWN Some other cause resulted in a takeover. ZOS4-TKN-CPU is a conditional token, present if the value of ZOS4-TKN-TKOVR-CAUSE is ZOS4VAL-CAUSE-CPU. It contains the CPU number of the primary CPU that went down. Probable Cause The reason for the takeover is reported by the ZOS4-TKN-TKOVR-CAUSE token.
Event Messages Event-Message Descriptions 302: ZOS4-EVT-BKUP-UP The primary process successfully started the backup process. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC ZOS4-TKN-CPU token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-CRTPID. ZSPI-TYP-UINT Event-Message Text process-name, Backup Up in CPU cpu Token Descriptions ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-FALSE, indicating that this is not critical event.
Event Messages Event-Message Descriptions 303: ZOS4-EVT-BKUPDOWN The primary process detected that the backup process is down. This is a critical event. The primary attempts to create a new backup, unless the backup CPU is down; in that case, the primary process waits until the CPU is reloaded. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC ZOS4-TKN-LOST-CAUSE token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-CRTPID. ZSPI-TYP-ENUM.
Event Messages Event-Message Descriptions ZOS4-VAL-CAUSE-STOP Backup process stopped ZOS4-TKN-CPU is a conditional token, present if the value of ZOS4-TKN-TKOVR-CAUSE is ZOS4VAL-CAUSE-CPU. It contains the CPU number of the backup CPU that went down. Probable Cause The primary process detects that the backup has stopped or terminated abnormally, or that the backup CPU is down. Recommended Action No action is required. This message is informational only.
Event Messages Event-Message Descriptions 304: ZOS4-EVT-BKUPCREATE-FAIL This is a critical event. The primary process was unable to create a backup process. If the backup CPU is down, the primary process will wait for the CPU RELOADED system message before trying again. Otherwise, the primary process will continue trying until a backup is created. It does not report unsuccessful retries.
Event Messages Event-Message Descriptions ZCOM-TKN-SUBJ-PROC is the name of the TSP process that caused the event. It is the subject of the message. ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. The contents of this error list provide information about the NEWPROCESS or PROCESS_CREATE_ error that occurred.
Event Messages Event-Message Descriptions ZGRD-TKN-XSWAPFILE for D-series systems, is the data swap-file name requested for the backup process. ZGRD-TKN-PROCESSDESCR for D-Series systems, is the process descriptor returned by PROCESS_CREATE_ . If its length is 0, no process was created.
Event Messages Event-Message Descriptions 305: ZOS4-EVT-CHKPTFAIL This is a critical event. A checkpoint I/O message returned an error. The primary process stops the backup and tries to create a new one. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-LIST.
Event Messages Event-Message Descriptions ZSPI-TKN-PROC-ERR identifies the file-system procedure that reported the error. It has one of the following values: ZFIL-VAL-OPEN ZFIL-VAL-WRITEREAD Probable Cause A checkpoint I/O message returned an error. The problem may be an internal logic error or insufficient resources. Recommended Action Provide a log of the error to your Tandem representative for suspected internal logic errors.
Event Messages Event-Message Descriptions 306: ZOS4-EVT-CHKPTINCOMPLETE The backup process detected that it might not have received all the checkpoint messages that should have been sent by the primary. This message is a warning of a possible subsequent problem. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-STRING.
Event Messages Event-Message Descriptions 307: ZOS4-EVT-ALLOCSEG-ERR This is a critical event. The TSP process could not allocate the extended data segment.
Event Messages Event-Message Descriptions ZSPI-TKN-PROC-ERR has the value ZGRD-VAL-ALLOCATESEGMENT. ZGRD-TKN-SEGMENTID is the segment ID requested for the extended segment. ZGRD-TKN-SEGMENTSIZE is the size, in bytes, requested for the extended segment. ZGRD-TKN-FILENAME for C-series systems, is the swap-file name requested for the extended segment. ZGRD-TKN-XFILENAME for D-series systems, is the swap-file name requested for the extended segment.
Event Messages Event-Message Descriptions 308: ZOS4-EVT-TRAP This is a critical event. The OSI/TS subsystem detected a trap caused by a hardware or software error. The affected TSP process terminates abnormally.
Event Messages Event-Message Descriptions ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. The contents of this error list provide information about the trap error that occurred. ZSPI-TKN-ERROR is the standard SPI error token described in the Distributed Systems Management (DSM) Programming Manual.
Event Messages Event-Message Descriptions ZGRD-TKN-XOBJECTFILE for D-series systems, is the program file name of the TSP process. ZOS4-TKN-CODE-SEG contains the code segment number. Probable Cause OSI/TS detected a trap caused by a hardware or software error. Recommended Action Provide a SAVE-ABEND dump of the process contents to your Tandem representative.
Event Messages Event-Message Descriptions 309: ZOS4-EVT-ACCESSERR This is not a critical event. The OSI/TS subsystem issues this message when it cannot access an NSP subdevice (X25AM or TLAM) or a DSM server (such as $ZNET). Any transport connections that have been established over the indicated NSP subdevice will be disconnected.
Event Messages Event-Message Descriptions ZSPI-TKN-ERROR is the standard SPI error token described in the Distributed Systems Management (DSM) Programming Manual. It contains the subsystem ID of the file system in the Z-SSID field and the file-system error number in the Z-ERROR field. ZSPI-TKN-PROC-ERR identifies the file-system procedure on which the error occurred.
Event Messages Event-Message Descriptions 310: ZOS4-EVT-NSP-DSMERR The OSI/TS subsystem failed to add, start, abort, or delete a subdevice to or from an X25AM or TLAM I/O process. Failure to add or start a subdevice causes the associated transport connection to be disconnected; outstanding transport service requests are returned with an error. No further action is taken for abort or delete failure.
Event Messages Event-Message Descriptions ZCOM-TKN-SUBJ-SU is the fully qualified subdevice name. ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. The contents of this error list provide information about the error that occurred. ZSPI-TKN-ERROR is the standard SPI error token described in the Distributed Systems Management (DSM) Programming Manual.
Event Messages Event-Message Descriptions 311: ZOS4-EVT-TLEALLOC-FAIL The OSI/TS subsystem could not allocate a time list element (TLE) from the Guardian 90 operating system. The process abends. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC ZOS4-TKN-CPU token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-CRTPID. ZSPI-TYP-UINT.
Event Messages Event-Message Descriptions 400: ZOS4-EVT-TSPDISCONN The OSI/TS subsystem disconnected the transport connection because of an error other than a protocol error or an unknown address. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-SU token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-FNAME.
Event Messages Event-Message Descriptions 401: ZOS4-EVT-TSP-DESTNOT-EXIST The OSI/TS subsystem failed in its attempt to initiate a transport connection. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-SU token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-FNAME. Event-Message Text su-name, Invalid Destination Address Token Descriptions ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-FALSE, indicating that this is not a critical event.
Event Messages Event-Message Descriptions 402: ZOS4-EVT-TSPPROTO-VIOL The OSI/TS subsystem detected a transport protocol violation. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-SU token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-BOOLEAN. token-type ZSPI-TYP-FNAME. Event-Message Text su-name, Protocol Violation Token Descriptions ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-FALSE, indicating that this is not a critical event.
Event Messages Event-Message Descriptions 403: ZOS4-EVT-L3-THLD A Network Layer network-management counter in the OSI/TS subsystem has reached a predefined threshold. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-SERV ZOS4-TKN-THLD-ID ZOS4-TKN-THLD-VAL ZOS4-TKN-REPT-ADDR ZOS4-TKN-DISCARD-CAUSE ZOS4-TKN-PDU-HDR token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-UINT.
Event Messages Event-Message Descriptions ZOS4-VAL-NPDU-DISCARD-CONG ZOS4-VAL-NPDU-DISCARD-LIFE ZOS4-VAL-NPDU-DISCARD-ADDR ZOS4-VAL-NPDU-DISCARD-UNSUP ZOS4-VAL-NPDU-DISCARD-REASM ZOS4-VAL-NPDU-DISCARD-GEN ZOS4-TKN-THLD-VAL is the predefined threshold value reached. ZOS4-TKN-REPT-ADDR is the address of the node reporting the event. ZOS4-TKN-DISCARD-CAUSE contains the reason code for discarding the PDU that triggered this threshold.
Event Messages Event-Message Descriptions 404: ZOS4-EVT-L4-THLD A Transport Layer network-management counter in the OSI/TS subsystem has reached a predefined threshold. Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-SERV ZOS4-TKN-THLD-ID ZOS4-TKN-THLD-VAL token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-UINT.
Event Messages Event-Message Descriptions ZEMS-TKN-CONSOLE-PRINT has the value ZSPI-VAL-TRUE, indicating that the EMS compatibility distributor will route the event message to the designated operator console. ZEMS-TKN-EVENTNUMBER is the event number. The value is ZOS4-EVT-L4-THLD (404). ZEMS-TKN-SUBJECT-MARK marks the token that follows it in the event message buffer as a subject of the event message. ZCOM-TKN-SUBJ-SERV is the name of the Layer 4 service that is the subject of the message.
Event Messages Event-Message Descriptions ZOS4-TKN-RSP-TSAP is the TSAP component of the responding address. ZOS4-TKN-DR-CODE is the disconnect reason code, as contained in the DR-TPDU of the connection that reported the event. ZOS4-TKN-ER-CODE is the error reason code, as contained in the ER-TPDU of the connection that reported the event. ZOS4-TKN-PDU-HDR contains the header information of the PDU that caused the event to be reported.
Appendix A Errors and Error Lists This appendix presents all the error numbers defined by the OSI/TS subsystem— that is, the values whose symbolic names begin with ZOS4-ERR-—and describes the error list associated with each error number. These error numbers occur as values of the return token, ZSPI-TKN-RETCODE, and also as the value of the Z-ERROR field of the error token, ZSPI-TKN-ERROR, within the error list.
Errors and Error Lists ZCOM Errors Returned by OSI/AS 11: ZOS4-ERR-OBJ-ACTV This error is returned to the STOP PROCESS command when the TSP process still has one or more subdevices opened by an application. Tokens in Error List 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-SSSCTL.
Errors and Error Lists ZCOM Errors Returned by OSI/AS 13: ZOS4-ERR-NO-BKUP This error is returned to the SWITCH PROCESS command when the TSP process has no backup process running. Tokens in Error List 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-SSSCTL.
Appendix B Token Codes and Token Maps Table of Token Codes Table B-1 summarizes all token codes specific to the OSI/TS subsystem (that is, all token codes whose names begin with ZOS4-TKN-). For each token code, the table gives the corresponding token type. The symbolic name of the token number for a token code can be derived from the name of the token code by replacing -TKN- with -TNM-; for example, token code ZOS4-TKN-CALLED-TSP has the token number ZOS4-TNM-CALLED-TSP. Table B-1.
Token Codes and Token Maps Table of Token Maps Table B-2 summarizes all token maps specific to the OSI/TS subsystem (that is, all token maps whose names begin with ZOS4-MAP-). For each token map, the symbolic name of the DDL definition is given. The symbolic name of the token number for a token map can be derived from the name of the token map by replacing -MAP- with -TNM-; for example, token map ZOS4-MAP-ADD-SU-TSP has the token number ZOS4-TNM-ADD-SU-TSP. Table B-2.
Appendix C Sample Programs This appendix includes a sample management program for C-series systems that sends commands to the OSI/TS subsystem, two sample event-message filters for users of OSI/TS, and a sample program that retrieves event messages generated by OSI/TS. Source code files for all of the examples described in this appendix are provided as part of the OSI/TS software. They reside (by default) in the volume and subvolume $SYSTEM.ZOSITS.
Sample Programs ! Data communications standard definitions ?nolist, source $system.zspidef.zcomtal ?list ! OSI/TS subsystem definitions ?nolist, source $system.zspidef.zos4tal ?list ! Global declarations ! OSI/TS subsystem ID STRUCT .zos4^val^ssid(zspi^ddl^ssid^def); ! SPI-related variables INT scp^file^num, ! SCP file number spi^err, ! error code from call to SPI procedure .sta^value[0:(zos4^val^buflen/2) -1], ! status value .tkn^value[0:(zos4^val^buflen/2) -1], ! token value .
Sample Programs ?PAGE ! *********************************************************** ! * start^up * ! *********************************************************** ! This procedure reads the startup message in $RECEIVE.
Sample Programs ! ! This procedure opens the SCP process named $ZNET and checks for any OPEN errors.
Sample Programs END; ! send^spi^cmd ?PAGE ! *********************************************************** ! * reset^spi^buf * ! *********************************************************** ! This procedure resets the SPI buffer position. PROC reset^spi^buf; BEGIN INT init^buffer; ! Reset SPI buffer length. os4^buf[1] := zos4^val^buflen; ! Reset position to initial position of SPI buffer.
Sample Programs CALL DEBUG; ! Put allow-type token in buffer. tkn^value := zspi^val^err^warn^and^norm; spi^err := SSPUTTKN(os4^buf,zspi^tkn^allow^type, tkn^value^s); IF spi^err THEN CALL DEBUG; END; ! *********************************************************** ! * add^su * ! *********************************************************** INT PROC add^su(obj^name); INT .obj^name; BEGIN INT return^token; ! object name of SU to be added ! value of return token INT .
Sample Programs ! Put extensible structured token in command buffer. spi^err := SSPUT(os4^buf,zos4^map^add^su^tsp^req, tkn^value); IF spi^err THEN CALL DEBUG; ! Send ADD SU command and retrieve response. CALL send^spi^cmd; ! Reset the SPI buffer pointer. CALL reset^spi^buf; ! Extract ZSPI^TKN^DATALIST token and check return token.
Sample Programs ! Get end-list token. spi^err := SSGETTKN(os4^buf,zspi^tkn^endlist); IF spi^err THEN CALL DEBUG; RETURN(return^token); END; ! *********************************************************** ! * start^su * ! *********************************************************** INT PROC start^su(obj^name); INT .obj^name; BEGIN INT return^token, ! value of return token datalist^count, ! count of ZSPI^TKN^DATALIST datalist^index, ! index of ZSPI^TKN^DATALIST complete; ! flag, SPI response buffer STRUCT .
Sample Programs ! Get object-name token and put in tkn^value. spi^err := SSGETTKN(os4^buf, zcom^tkn^objname, tkn^value); IF spi^err THEN CALL DEBUG; ! Display object name on terminal. CALL WRITE(term^file^num,tkn^value[1],tkn^value[0]); ! Get return token (ZSPI^TKN^RETCODE).
Sample Programs message2[0]); ZCOM^ERR^OBJ^NOT^FOUND -> CALL WRITE(term^file^num, message9[1], message9[0]); ZCOM^ERR^OBJ^ALRDY^DEF -> CALL WRITE(term^file^num, message4[1], message4[0]); OTHERWISE -> CALL WRITE(term^file^num, message3[1], message3[0]); END; ! Get end-list token. spi^err := SSGETTKN(os4^buf, zspi^tkn^endlist); IF spi^err THEN CALL DEBUG; datalist^index := datalist^index + 1; END; ! Save context token for the next command by moving it ! from the response to the original command buffer.
Sample Programs save^buf ':=' os4^buf FOR ZOS4^VAL^BUFLEN BYTES; CALL WRITE(term^file^num, LF, 1); CALL WRITE(term^file^num, message7[1], message7[0]); complete := ZSPI^VAL^FALSE; WHILE (complete = ZSPI^VAL^FALSE) DO BEGIN ! Send STATUS SU command and retrieve response. CALL send^spi^cmd; ! Reset the SPI buffer pointer. CALL reset^spi^buf; ! Process the response. ! Get ZSPI^TKN^COUNT of data list and put in ! datalist^count.
Sample Programs messageA[0]); OTHERWISE -> CALL WRITE(term^file^num, messageB[1], messageB[0]); END; ! Extract return token (ZSPI^TKN^RETCODE).
Sample Programs ! Get terminal name and open terminal. CALL MYTERM(term^name); CALL OPEN(term^name, term^file^num); ! Get the startup message. CALL start^up; ! Open SCP process. error := open^scp; IF error THEN CALL DEBUG; ! Set up object name for first ADD SU command. obj^name[0] := 12; obj^name[1] ':=' ["$TT01.#S6000"]; ! Issue first ADD SU command. error := add^su(obj^name); IF error THEN goto exit; ! Set up object name for second ADD SU command. obj^name[0] := 12; obj^name[1] ':=' ["$TT01.
Sample Programs END; C–14 056786 Tandem Computers Incorporated
Sample Programs Sample EventMessage Filters The Event Management Service (EMS) distributor collects event messages from the subsystems running in your system or network, stores them in an event log, and returns to your application only those that pass the filter you have installed. By using filters, you can limit the event messages your application receives to those of interest. Note If you do not install a filter, EMS returns all event messages it receives from subsystems running on your local system.
Sample Programs PASS; END; Filter Example: Messages Reporting DSM Errors from NSP Processes The following filter selects the event messages, originating from OSI/TS on system \MYSYS, that reflect failure to establish a transport connection because of a DSM error generated by X25AM or TLAM.
Sample Programs Event-Retrieval The remainder of this appendix presents an event-retrieval program that does the Example following: Starts and opens an EMS consumer distributor Installs the filter whose object-file name you type in at your home terminal Retrieves event messages that pass the filter Displays these messages on the home terminal The program is coded both in TAL and in C. The source code file for these examples are provided as part of the OSI/TS software. They reside (by default) in $SYSTEM.
Sample Programs ?NOCODE ! *********************************************************** ! * Global declarations and definitions * ! *********************************************************** ! SPI standard definitions ?NOLIST, SOURCE $system.zspidef.zspital ?LIST ! EMS standard definitions ?NOLIST, SOURCE $system.zspidef.zemstal ?LIST ! OSI/TS subsystem definitions ?NOLIST, SOURCE $system.zspidef.zos4tal ?LIST ! Global declarations LITERAL true = 1; LITERAL false = 0; INT .
Sample Programs LITERAL LITERAL INT INT evt^text^len = 78; num^evt^lines = 2; .evt^text^buf[0:(evt^text^len/2)*num^evt^lines]; .actual^len[0:num^evt^lines]; ! SPI-related definitions ! SSID declarations ! EMS subsystem ID STRUCT .zems^val^ssid(zems^val^ssid^def); ! OSI/TS subsystem ID STRUCT .zos4^val^ssid(zspi^val^ssid^def); ! Filter name-related variables INT .coll^name[0:11] := ["$0",11*[" "]], .
Sample Programs IF < THEN ! some unusual condition BEGIN ! check whether to retry IF FILEERROR (term^file^num) THEN CALL DEBUG; END; GOTO retry; ! Move user input filter name to filt^name[].
Sample Programs IF spi^err <> ZSPI^ERR^OK THEN CALL DEBUG; IF (ems^err <> 0) THEN BEGIN IF (ems^err = ZEMS^ERR^FLT^LOAD) THEN BEGIN CALL WRITE(term^file^num, message[1], message[0]); return( ems^err ); END ELSE CALL DEBUG; END; return( spi^err ); END; ?PAGE ! *********************************************************** ! * spi^cmd^set^source * ! *********************************************************** ! This procedure builds an SPI command that directs the ! distributor to use a collector as the source o
Sample Programs ! Initialize spi^buf for distributor CONTROL command. spi^err := SSINIT (spi^buf, ZEMS^VAL^BUFLEN, zems^val^ssid, ZSPI^VAL^CMDHDR, ZEMS^CMD^CONTROL); IF spi^err <> ZSPI^ERR^OK THEN CALL DEBUG; ! Place load-filter token in the buffer. spi^err := SSPUTTKN(spi^buf, ZEMS^TKN^FILTERFILE, filt^name); IF spi^err <> ZSPI^ERR^OK THEN CALL DEBUG; ! Send the command to the distributor.
Sample Programs retry1: CALL WRITE (term^file^num, evt^text^buf[i*evt^text^len/2], actual^len[i]); IF <> THEN BEGIN IF FILEERROR(term^file^num) THEN GOTO retry1; CALL DEBUG; END; END; END; END; ?PAGE ! *********************************************************** ! * getevent^loop * ! *********************************************************** ! ! ! ! ! ! ! ! ! ! This procedure consists of a loop to retrieve event messages.
Sample Programs spi^err := SSGETTKN ( spi^buf, ZSPI^TKN^ADDR, tkn, 1, @event^buf); IF spi^err <> ZSPI^ERR^OK THEN CALL DEBUG; ! Move past length part (variable-length token). @event^buf := @event^buf + 2D; ! Display the event message at your terminal. CALL displ^event(event^buf); ! Save context token from this GETEVENT response for ! the next GETEVENT request.
Sample Programs ! Open $RECEIVE file. CALL OPEN (rcv^name, rcv, , 1); IF <> THEN CALL DEBUG; ! Read startup message from $RECEIVE. CALL READUPDATE (rcv, startup^msg, $LEN(startup^msg), ct^rd); IF <> THEN CALL DEBUG; CALL REPLY ( , , , , 0 ); IF <> THEN CALL DEBUG; ! Create a name for the distributor process.
Sample Programs ! Tell distributor to use collector log files as the ! source of event messages. error := spi^cmd^set^source; IF error THEN goto exit; ! Load filter into distributor. error := spi^cmd^load^filter; IF error THEN goto exit; ! Retrieve and display event messages.
Sample Programs Example in C The following pages give the source code for the event-retrieval program in C. /************************************************************ * * * File: EXEMSC1 * * * * This program demonstrates how to retrieve an event * * message produced by the OSI/TS subsystem and handle * * it appropriately. It does the following: * * * * - Starts and opens an EMS consumer distributor. * * * * - Prompts you at your terminal for a filter file * * name.
Sample Programs * ZSPIDEF subvolume exists. */ #include "$system.zspidef.ZSPIC" #include "$system.zspidef.ZEMSC" #include "$system.zspidef.ZOS4C" nolist nolist nolist #pragma PAGE "Globals and definitions" /* The following defines are used for ZEMS structures to * shorten names. */ #define EMSBUFDEF zems_ddl_msg_buffer_def #define SPIERRDEF zspi_ddl_error_def #define FALSE 0 #define TRUE (!FALSE) /* The following structure is used to pass a startup * message to the process started by NEWPROCESS.
Sample Programs #define EVT_TEXT_LEN #define NUM_EVT_LINES 78 2 char evt_text_buf[EVT_TEXT_LEN * NUM_EVT_LINES]; int actual_len[NUM_EVT_LINES]; /* Declare subsystem IDs. */ zems_val_ssid_def zems_val_ssid; zos4_val_ssid_def zos4_val_ssid; char coll_name[25] = "$0 char filt_name[25]; "; #pragma PAGE "init_startup()" /************************************************************ * init_startup * ************************************************************ * * Recreate the startup structure discarded by C.
Sample Programs } #pragma PAGE /************************************************************ * get_filter_name * ************************************************************ * * Prompts the user for a filter name.
Sample Programs * Puts the finishing touches on an SPI command that has * been prepared by another procedure. Sends the command to * the distributor and checks the response. */ int send_spi_cmd(void) { int ccval; /* for CC return from WRITEREAD */ /* Determine how much buffer space was used. */ spi_err = SSGETTKN( (int *)spi_buf, ZSPI_TKN_USEDLEN, (char *)&used_len ); if (spi_err != ZSPI_ERR_OK) DEBUG(); /* Send the used part to the distributor.
Sample Programs (int *)&zems_val_ssid, ZSPI_VAL_CMDHDR, ZEMS_CMD_CONTROL ); if (spi_err != ZSPI_ERR_OK) DEBUG(); /* Place connect-source-collector token in buffer.*/ spi_err = SSPUTTKN( (int *)spi_buf, ZEMS_TKN_CONNECT_SRC_COLL, coll_name ); if (spi_err != ZSPI_ERR_OK) DEBUG(); /* Send command to distributor.
Sample Programs unsigned long etxt_stat; # define high(x) (x >> 16) # define low(x) (x & 0xFFFF) char int text[EVT_TEXT_LEN+1]; /* needed for printf() call */ i; /* Generate display text from event message. */ etxt_stat = EMSTEXT( (int *)event_buf, evt_text_buf, EVT_TEXT_LEN, /* displayable line length */ NUM_EVT_LINES, /* number of display lines */ actual_len,0,0, /* line length to display */ 1); /* console-compatible */ /* Check for EMSTEXT calling errors.
Sample Programs if (spi_err != ZSPI_ERR_OK) DEBUG(); /* Save the original command. */ movmem( (char *)spi_buf, (char *)sav_buf, sizeof(EMSBUFDEF) ); /* Begin loop that gets and displays event messages. */ while ( (msgcount < msglimit) || (msglimit == 0) ) { msgcount++; /* Send GETEVENT command to distributor. */ send_spi_cmd(); /* Extract event message from GETEVENT response. */ tkn = ZEMS_TKN_EVENT; /* Return offset of the event in SPI buffer * via event_buf_loc.
Sample Programs * retrieve and process event messages. */ main(int argc, char *argv[]) { CISTART *startup; /* local pointer to startup message * structure */ char *cptr; char *cptr1; int ccval = 0; static char zspi_name[] = "#ZSPI"; /* Initialize subsystem IDs. */ cptr = strncpy(zems_val_ssid.u_z_filler.z_filler, ZSPI_VAL_TANDEM, 8); zems_val_ssid.z_number = ZSPI_SSN_ZEMS; zems_val_ssid.z_version = ZEMS_VAL_VERSION; cptr1 = strncpy(zos4_val_ssid.u_z_filler.z_filler, ZSPI_VAL_TANDEM, 8); zos4_val_ssid.
Sample Programs } /* Open the new process to send it the startup message. */ ccval = OPEN( (int *)distr_proc_name, (int *)&distr ); if (ccval != CCE) { printf(" Open returned non-zero ccval: %d.\n",ccval); DEBUG(); } /* Add "TYPE CONSUMER" to startup message to send to * EMSDIST. */ strcat(startup->params, "TYPE CONSUMER"); /* Now write the startup structure.
Appendix D Attribute Name Changes Some attribute names were changed in this release (OSI/TS C30 product version) to improve product usability. All changes maintain backward compatibility with your existing programs or TACL macros. The following tables list the terms that were changed.
Attribute Name Changes def ZOS4-DDL-ALTER-SU-TSP PREVIOUS FIELD NAME NEW FIELD NAME ZREXMIT-TIME ZREF-TIME ZINACTV-TIME ZWIN-TIME ZREASSIGN-SYNCH-TRY-TIME ZREASSIGN-SYNCH-WAIT-TIME ZCON-WAIT-TIME ZDISCONN-WAIT-TIME ZREXMIT-TIMEOUT ZREF-TIMEOUT ZINACTV-TIMEOUT ZWIN-TIMEOUT ZTTR-TIMEOUT ZTWR-TIMEOUT ZCONN-TIMEOUT ZDISCONN-TIMEOUT def ZOS4-DDL-INFO-SERV-L3 PREVIOUS FIELD NAME NEW FIELD NAME ZX25DISCONN-DELAY-TIME ZX25DISCONN-DELAY def ZOS4-DDL-INFO-SERV-L4 PREVIOUS FIELD NAME NEW FIELD NAME ZREXMIT-
Attribute Name Changes def ZOS4-DDL-STATS-SERV-L4 PREVIOUS FIELD NAME NEW FIELD NAME ZWIN-TIME ZWIN-TIMEOUT 056786 Tandem Computers Incorporated D–3
Appendix E Status SU Attribute Values This appendix provide the possible values for three attributes in the STATUS SU DDL structure, Z0S4-DDL-STATUS-SU-TSP. The three fields are ZX25-DISC-REASON, ZX25CLEAR-CAUSE, and ZX25DIAGCODE. ZX25-DISC-REASON Table E-1 is taken form Table 4-12, “reasons for Circuit Disconnection,” from the Tandem X.25 Access Method (X25AM) Manual, Part no. 17464. Table E-1.
Status SU Attribute Values ZX25-CLEAR-CAUSE ZX25-CLEAR-CAUSE Table E-2 and the associated notes at the end of the tables is copied from ISO 8208, “Telecommunications and Information Exchange Between Systems” (Table 5, “Coding of the Clearing Cause Field in Clear Indication Packets”). Table E-2.
Status SU Attribute Values ZX25-DIAAGCODE ZX25-DIAGCODE Table E-3 and the associated notes at the end of the table are copied from ISO 8208, “Telecommunications and Information Exchange Between Systems” (Table 14-B, “Coding of the Diagnostic Code Field”). Table E-3 Diagnostic Field Codes (Page 1 of 6) Bits Decimal 8 7 6 5 4 3 2 1 Value Applicable Packets (Note 1) No Additional Information Invalid P(S) Invalid P(R) 0 0 0 . 0 0 0 0 . 0 0 0 0 . 0 0 0 0 . 0 0 0 0 . 1 0 0 0 . 1 0 0 1 . 1 0 1 0 .
Status SU Attribute Values ZX25-DIAAGCODE Table E-3.
Status SU Attribute Values ZX25-DIAAGCODE Table E-3.
Status SU Attribute Values ZX25-DIAAGCODE Table E-3.
Status SU Attribute Values ZX25-DIAAGCODE Table E-3.
Status SU Attribute Values ZX25-DIAAGCODE Table E-3.
Abbreviations The following list defines abbreviations and acronyms used in this manual and in the other Tandem OSI/AS and Tandem OSI/TS manuals. Not all terms listed here are used in this particular manual. AA-SPDU. Abort accept SPDU AARE-APDU. A-associate response APDU AARQ-APDU. A-associate request APDU AB-SPDU. Abort SPDU ABRT-APDU. A-abort APDU AC-PPDU. Alter context PPDU AC-SPDU. Accept SPDU ACA-PPDU. Alter context acknowledge PPDU ACPM. Association control protocol machine ACSE.
Abbreviations CPA-PPDU. Connect presentation accept PPDU CPR-PPDU. Connect presentation reject PPDU CR-PPDU. Connect request PPDU CSMA. Carrier sense multiple access CSMA/CD. CSMA with collision detection CUG. Closed user group DC-TPDU. Disconnect confirm TPDU DCB. Data control block DDL. Data Definition Language DN-SPDU. Disconnect SPDU DR-TPDU. Disconnect request TPDU DSC. Dynamic System Configuration DSM. Distributed Systems Management DSP. Directory system protocol DSP.
Abbreviations IPPDU. IP protocol data unit IS. Intermediate system ISO. International Organization for Standardization LAN. Local area network LAPB. Link access protocol—balanced LDIB. Local Directory Information Base LLC1. Logical link control type 1 LMIB. Local Management Information Base LSAP. Link layer service access point MAC. Media access control MCB. Message control block MCW. Message control word MFM. Module file management MIB. Management Information Base MLAM. Multilan access method NCB.
Abbreviations PVC. Permanent virtual circuit RCB. Request control block RF-SPDU. Refuse SPDU RJ-TPDU. Reject TPDU RLRE-APDU. A-release response accept APDU RLRQ-APDU. A-release request APDU RS-PPDU. Resynchronize PPDU RSA-PPDU. Resynchronize acknowledge PPDU SAP. Service access point SCB. Subdevice control block SCF. Subsystem Control Function SCP. Subsystem Control Point SDU. Service data unit SNDCF. Subnetwork dependent convergence function SNPA. Subnetwork point of attachment SPDU.
Abbreviations TMDS. Tandem Maintenance and Diagnostic Subsystem TPDU-NR. A TPDU field that contains the DT-TPDU number TPDU. Transport protocol data unit TSAP. Transport service access point TSDU. Transport service data unit TSEL. Transport selector TSP. Transport service provider TTD-PPDU. Presentation typed data PPDU TTR. Time-to-resynchronize timer TWR. Time-to-wait-for resynchronize timer WAN. Wide area network X25AM. X.
Glossary The following glossary defines terms used both in this manual and in the other Tandem OSI/AS and Tandem OSI/TS manuals. Not all terms listed here are used in this particular manual. Abstract syntax. A representation of the way in which components of information are to be specified in a communication. It defines a set of primitive elements whose range of values is fully defined—for example, integers, characters, and Boolean values—and ways of combining these elements. See also transfer syntax.
Glossary Application entity. The part of an application process that interacts with a remote application process. In an OSI application itself, the application entity is the part that represents the communication functionality necessary for interoperation. Application entity title. The name, used with ACSE, that identifies an application entity to the OSI network. See also application entity. Contrast application name. Application Layer. Layer 7 of the OSI Reference Model.
Glossary Basic concatenation. A feature of the Session Layer protocol that allows two SPDUs to be contained in one TSDU. This feature is available through the APS procedures, which allows applications to invoke a give token primitive or a please token primitive to be concatenated with the requested primitive. See also PDU. C-series system. A system running any Cxx version of the Guardian 90 operating system, such as C21 or C30. Called address. The address to which a connect request is addressed.
Glossary Collector. An EMS process that accepts event messages from subsystems and logs them in the event log. See EMS. Compare distributor. Command interpreter. For OSI/AS and OSI/TS, an general term that refers to the Tandem Advanced Command Language (TACL). Command message. An SPI message, containing a command, sent from an application program to a subsystem. See also SPI message. Compare response message or event message. Common definition.
Glossary Connectionless mode. A type of communication in which all the packets of data (over the duration of the communications session) are treated independently and in which functions such as error recovery and flow control are not practical. Contrast connection mode. Consumer distributor. An EMS distributor process that returns selected event messages to management applications upon request. See also distributor. Context. See application context. Context token.
Glossary Data communications standard definitions. In DSM, the set of declarations provided by Tandem for use in all management programs that manage or retrieve event messages from Tandem data communications subsystems. The names of these definitions start with either ZCOM or ZCMK. See also definition or definition files. Compare SPI standard definitions or EMS standard definitions. Data Link Layer. Layer 2 in the OSI Reference Model.
Glossary Distributor. An EMS process that distributes event messages from event logs to requesting management applications, to Guardian 90 console message destinations, or to a collector on another node. See also consumer distributor, compatibility distributor, forwarding distributor, or printing distributor. Contrast collector. DNS (Distributed Name Service).
Glossary Error list. In DSM programmatic interfaces, a group of tokens used within a response record to provide error and warning information. An error list consists of a list token that denotes an error list (different from the token that starts a data list or a generic list), followed by an error token, other tokens explaining the error (optional), and an end-list token. Error lists can be nested within other error lists. The return token cannot be included in an error list. See also return token.
Glossary Expedited data. Data that bypasses normal flow-control procedures and is controlled by separate, specially designated procedures. Data normally flows from one end system to another in an orderly, first-in-first-out (FIFO) fashion. Expedited data moves through the system, overtaking previously submitted data, to reach the end system as fast as possible. Extensible structure. In DSM programmatic interfaces, a structure declared for the value of an extensible structured token.
Glossary Header. The initial part of an SPI message. The first word of this header always contains the value -28; the remainder of the header contains descriptive information about the SPI message, most of which is accessible as header tokens. The tokens in an SPI message header differ according to the type of message: the header of a message that contains a command or response differs somewhat from the header of an event message.
Glossary Interface. (1) With respect to the OSI Reference Model, a set of rules by which a given layer passes information to the adjoining layer below or above. (2) With respect to Tandem products, a set of rules by which a human operator or a program interacts with a hardware or software product, such as Tandem OSI/AS. Intermediate system. Any combination of subnetworks and relay systems used to connect two or more end systems. Tandem systems are not used as intermediate systems. See also end system.
Glossary Major activity token. One of the four types of Session Layer tokens that are associated with functional units. See Token and Functional unit. Major synchronization. In the Session Layer, the separation of the exchange of data into a series of dialog units. A major synchronization point indicates the end of one dialog unit and the beginning of the next. Each major synchronization point is confirmed explicitly. Compare minor synchronization. Management application.
Glossary Network service access point. See NSAP or NSAP address. Noncritical event. A DSM event not to crucial to system or network operations. Each subsystem determines which of its events are noncritical, by setting the value of the emphasis token to FALSE. Compare critical event. Nonsensitive command. A DSM command that can be issued by any user or program allowed access to the target subsystem—that is, a command on which the subsystem imposes no further security restrictions.
Glossary Object-name template. In DSM, a name that stands for more than one object. Such a name includes one or more wild-card characters, such as * and ?. See also wild-card character. Octet. Eight bits or one byte. Open system. Any computer system that adheres to the OSI standards. OSI (Open Systems Interconnection). A set of standards used for the interconnection of heterogeneous computer systems, thus providing universal connectivity. OSI address.
Glossary PDU (protocol data unit). Information delivered as a unit between peer entities that contains data and/or control and address information.
Glossary Presentation default context name. For Tandem OSI/AS, a structure that contains the default abstract syntax and transfer syntax to be used if the presentation context definition list is not present. Presentation default context result. For Tandem OSI/AS, a parameter that indicates the called application’s acceptance or rejection of the presentation default context name. Presentation Layer. Layer 6 in the OSI Reference Model.
Glossary PSAP (presentation service access point). A network-unique, physical address in the Presentation Layer through which connections are established and maintained. Also called presentation address. PSEL (presentation selector). A logical address in the Presentation Layer through which presentation services are made available. A single PSEL can service one or more connections simultaneously. PTrace. A Tandem program used to display trace files created through the use of the CMI or SCF Trace commands.
Glossary Response record. In DSM programmatic interfaces, a set of response tokens, usually describing the results of performing a command on one object. Every response record in a response from a Tandem subsystem contains a return token; a response record can also contain error lists that include error tokens. A response can consist of multiple response records, spread across one or more response messages. A response record cannot be split between two response messages.
Glossary Service primitive. An abstract, implementation-independent interaction between a service user and a service provider. Service primitives describe the sequences of events between adjacent layers that occur through the service access point (SAP). There are four types of service primitives; see confirm primitive, indication primitive, request primitive, or response primitive. See also SAP. Session. (1) In the context of OSI data transmission, the period during which two entities can exchange data.
Glossary SPI procedures. In DSM, the set of Guardian 90 procedures used to build and decode buffers for use in system and network management and in certain other applications. These procedures are SSINIT, SSNULL, SSPUT, SSPUTTKN, SSGET, SSGETTKN, SSMOVE, and SSMOVETKN. SPI standard definitions. In DSM programmatic interfaces, the set of declarations available for use with the SPI procedures, regardless of the subsystem.
Glossary Subnetwork dependent convergence function. See SNDCF. Subnetwork. One or more intermediate systems that provide relaying and through which end open systems may establish network connections. See also intermediate system or end system. Subordinate names option. In DSM interfaces to Tandem data communications subsystems, the designation that the object name given in a command stands not just for itself but also for the names of objects at lower levels in a hierarchy.
Glossary Synchronization point. A marker that a Session Layer application can insert into the data it is transmitting, to structure the exchange of data. There are two types: major synchronization points and minor synchronization points. See also major synchronization or minor synchronization. Synchronize minor token. One of the four types of Session Layer tokens that are associated with functional units. See Token and Functional unit. SYSGEN.
Glossary Token bus. The IEEE 802.4 standard for the both Data Link Layer (media access control sublayer only) and Physical Layer of the OSI Reference Model, which defines a tokenpassing bus access method for connections over LAN networks. See also CSMA/CD. Token code. In DSM programmatic interfaces, a 32-bit value that identifies a token. A token code consists of a token type (16 bits) and a token number (16 bits).
Glossary Transport Layer. Layer 4 in the OSI Reference Model. This layer provides reliable, transparent transfer of data between end systems and ensures that the data arrives at the correct destination. It provides reliable data transfer independent of the underlying Network Layer, but does, however in the CONS case, depend on the Network Layer to provide the network connection. Transport protocol data unit. See PDU. Transport selector. See TSEL. Transport service access point. See TSAP.
Glossary Warning. In DSM interfaces, a condition, encountered in performing a command or other operation, that can be significant but does not cause the command or operation to fail. A warning is less serious than an error. Compare error. Wild-card character. A character that stands for any possible character(s) in a search string or in a name applying to multiple objects.
Index A ABORT PROCESS command operational notes 5-7 structure 5-6 tokens in command buffer 5-6/7 tokens in response buffer 5-7 ABORT SU command operational notes 5-10 structure 5-8 tokens in command buffer 5-8/9 tokens in response buffer 5-9 ABORTING summary state 4-10, 4-11 Action events not reported 3-11 ACTIVATE PROCESS command operational notes 5-12 structure 5-11 tokens in command buffer 5-11/12 tokens in response buffer 5-12 ADD SU command operational notes 5-25 programming example C-1/14 structure 5-
Index ALTER SERVICE command operational notes 5-55 structure 5-38/40 tokens in command buffer 5-40/55 tokens in response buffer 5-55 ALTER SU command operational notes 5-68 structure 5-56/57 tokens in command buffer 5-58/67 tokens in response buffer 5-67/68 Architecture 1-2/5 Attribute name changes, list of D-1/3 AUTOSTOP parameter 1-3 B Backup CPU in startup message 2-3 in TACL RUN command 2-2 Backup error A-3 Backup events backup down message 6-12/13 backup takeover process message 6-9/10 backup up messa
Index Checkpoint incomplete message 6-19 Checksums See ZCHECK-TSEL, ZESIS-XSUM, ZIP-XSUM, and ZXSUM fields Circuit disconnect reasons, table of E-1 Class See ZALT-CLASS and ZCLASS fields Clear cause codes, table of E-2 Closed user group attributes See ZX25BCUG, ZX25CUG, and ZX25CUG-TYPE fields Closing processes 2-4 COBOL85 definition file 3-1 Code file names See ZPROG-FNAME field Collector, EMS 1-4 Command file to compile EMS filters, example C-16 Commands building and sending 3-6 control-and-inquiry inter
Index Communications, standard definitions 4-4/11 Compatibility, version 1-10 Compiling EMS filters 3-11, C-16 Conditional tokens 6-4 Connections See ZCONN-TIMEOUT, ZTCON-STATE, ZDISCONN-TIMEOUT, ZMAX-CONNS, ZMAX-EVER-CONN, ZMULTIPLEX, ZOPENCONN, ZTCON-SUB-STATE, ZTTR-TIMEOUT, ZTWR-TIMEOUT, ZX25DISCONN-DELAY, and ZX25NCON-MULTIPLEX fields Consumer distributor, in EMS 1-5, 3-10 Control blocks See ZNCB-TBL-xxx, ZNIOCBS-xxx, ZNTIOCBS-xxx, ZRCB-TBL-xxx, ZRIOCBS-xxx, ZSCB-TBL-xxx, ZTCB-TBL-xxx, and ZTPDUCBS-xxx
Index Decoding event messages 3-10/11 Decoding response messages 3-8 Default values, SU attributes 5-55 Definition files 3-1/3 Definitions DDL, and token maps, table of B-2 EMS standard 4-13 example C-1/14, C-17/26 DELETE SU command operational notes 5-71 structure 5-69 tokens in command buffer 5-69/70 tokens in response buffer 5-70 Destination address invalid 6-31 Diagnostic field codes, table of E-3/8 Disconnect reasons for X.
Index E Empty response record 3-9 EMS See also Distributors and Event ...
Index ES-IS protocol See ZESIS-ES-CONF-TIME, ZESIS-ENABLE, ZESIS-ES-GROUPMAC-ADDR, ZESIS-HOLD-TIME, ZESIS-IS-GROUP-MAC-ADDR, ZESIS-NOTIFY-IS, ZESIS-NSAP, ZESIS-NSP-DEV, contd See ZESIS-QUERY-RETRY, ZESIS-QUERY-TIME, ZESIS-REMAINTIME, ZESIS-TYPE, and ZESIS-XSUM fields Event messages 106, insufficient buffer space error 6-8 301, takeover by backup 6-9/10 302, backup up error 6-11 303, backup down 6-12/13 304, unable to create backup process 6-14/16 305, checkpoint failure 6-17/18 306, incomplete checkpoint b
Index Expedited data transfer See ZEXP-BYTES-xxx, ZEXPEDITED, and ZL4-EXPEDITED fields Extensible structured tokens defined by data communications 4-6 in commands 3-7 in responses 3-8 F Fault tolerance of processes 2-2 Field name changes, list of D-1/3 File cannot be accessed message 6-25/26 File-system definition file 3-2 standard token definitions 4-14 filenames parameter, in NEWPROCESS and NEWPROCESSNOWAIT 2-3 Filters, EMS compiling, example command file C-16 examples C-15/16 loading 3-10, C-27/36 using
Index Guardian 90 definition file 3-2 standard token definitions 4-13 value name definitions 4-13 Guardian time-list-element allocation failed message 6-29 H Header tokens 3-1 defined by EMS 4-12 defined by SPI 4-2 in OSI/TS event messages 6-3 table of 5-5 Hierarchy of object types 1-6 High PIN processes 1-10 HIGHPIN option in TACL RUN command 2-2 I I/O buffers See Buffers I/O control blocks See ZNIOCBS-xxx and ZRIOCBS-xxx fields Incomplete checkpoint by primary event message 6-19 INFO PROCESS command stru
Index Installing EMS filters 3-10, 3-11 Insufficient buffer space message 6-8 Interactive commands, table of 1-8 Interactive interfaces, DSM 1-1 Interfaces control-and-inquiry 1-3 DSM 1-1 event-management 1-4/5 programmatic management, reasons for 1-1 Internal error message 6-6 Internal tokens 6-4 Internet protocol, OSI See IP Invalid destination address message 6-31 IP See also IP-DISCARD-xxx, ZIP-LIFETIME, ZIP-NULL-LAYER, ZIPOCTETS-xxx, ZIP-PDUS-xxx, ZIP-X25-SNDCF, ZIPX25-SNDCF1980-ADDR, and ZIP-XSUM fie
Index LISTOBJECTS SU command structure 5-124 tokens in command buffer 5-124/125 tokens in response buffer 5-125/126 LISTOPENS SU command operational notes 5-130 structure 5-127/128 tokens in command buffer 5-128 tokens in response buffer 5-128/130 Loading EMS filters 3-10, 3-11 M MAC station group address See ZESIS-ES-GROUP-MAC-ADDR, ZESIS-IS-GROUP-MAC-ADDR, and ZESIS-MAC-ADDR fields Management application, reasons for 1-1 example event retrieval program in C C-27/36 example event retrieval program in TAL
Index Names (continued) objects 3-5 PROCESS objects 4-7 ROUTE objects 4-7/8 SERVICE objects 4-8/9 SU objects 4-9 NCB See ZNCB-TBL-xxx and ZNIOCBS-xxx fields Network control blocks See NCB Network Layer standards implemented xvi threshold reached message 6-33/34 Network service provider processes See NSP processes Network service quality See ZNETTYPE field NEWPROCESS procedure failure 6-14/16 general 2-3 NEWPROCESSNOWAIT procedure 2-3 Noncritical events 3-11 Nonsensitive commands 3-9, 5-4 NonStop process pa
Index O Object names general 3-5 specifying multiple 3-7 Object types definitions, table of 4-5 hierarchy 1-6 in OSI/TS, list of 3-4 null 4-6/7 overview 1-5/6 PROCESS 4-7 ROUTE 4-7/8 SERVICE 4-8/9 SU 4-9 Object-specs, syntax rules 4-6/10 Objects commands for each type, table of 5-1 Opens See ZBPID, ZOPEN-CNT, ZOPENER, ZOPENER-LEN, ZOPENFLAGS, ZOPENID, ZOPENS-ALLOWED, ZPPID, ZPROCID, ZSYNCDEPTH, ZUSERID, ZXPROCID, and ZXPROCID-LEN fields OSI Reference Model, layers supported 1-2/5 OSI standards, implemented
Index Port See ZX25PORT field PORT object, in TLAM, failure to add 6-28 Printing distributors 1-9 Priority See ZPRI, ZTCON-PRI, and ZX25PRICALL fields Process abended message 6-7 PROCESS object aborting See ABORT PROCESS command activating See ACTIVATE PROCESS command altering attributes of See ALTER PROCESS command name examples 4-7 obtaining configuration information for See INFO PROCESS command obtaining lists of See LISTOBJECTS PROCESS command obtaining statistics from See STATISTICS PROCESS command ob
Index Processes See also NSP-xxx, ZOWNERID, ZPOOL-SIZE, ZPRIM-CPU, ZPRIMPIN, ZPROCID, ZPROC-xxx, ZUSERID, ZXPROCID, and ZXPROCID-LEN fields closing and stopping 2-4 communicating through SCP 2-1 high PIN 1-10 reporting OSI/TS events 6-1 startup sequence, programming example C-27/36 TSP, running interactively 2-2 TSP, running programmatically 2-3 types 1-2 version compatibility 1-10 PROCESS_CREATE_ procedure failure 6-14/16 PROCESS_CREATE_ procedure general 2-3 Programmatic commands 1-7, 1-8 overview 1-5 Pr
Index Protocol violation message 6-32 PVC channel number See ZX25PVC field R RCB See ZRCB-TBL-xxx fields Receive messages See ZRECV-DEPTH field Receiving response messages 3-8 Requests See ZINBOUND-xxx, ZRCB-TBL-xxx, ZRECV-DEPTH, ZRECV-SIZE, and ZRIOCBS-xxx fields Required software for OSI/TS 1-1 RESETSTATS PROCESS command operational notes 5-137 structure 5-131/132 tokens in command buffer 5-132/133 tokens in response buffer 5-133/137 RESETSTATS SERVICE command operational notes 5-148 structure 5-138/140
Index ROUTE object name examples 4-8 obtaining NPDU information See INFO ROUTE command overview 1-6 ZCOM-OBJ-ROUTE token 4-7/8 RPOA See ZX25RPOA and ZX25RPOA-DNIC-CNT fields RUN command 2-2 S SCB See ZSCB-TBL-xxx fields SCF commands, table of 1-8 general 1-1 version compatibility 1-15 SCP reporting OSI/TS events 6-1 using for control and inquiry 1-3 using to communicate to OSI/AS 2-1 using to communicate to OSI/TS 2-1/4 version compatibility 1-15 Security See ZRECV-SECUR and ZSEND-SECUR fields command usag
Index SERVICE object (continued) relationship to SU attributes 5-25 resetting statistics for See RESETSTATS SERVICE command ZCOM-OBJ-SERVICE token 4-8/9 Simple tokens defined by data communications 4-6, 4-10, 4-11 defined by EMS 4-12 defined by Guardian 90 4-13 defined by SPI 4-2 defined by the file system 4-14 SNDCF See ZIP-X25-SNDCF and ZIPX25-SNDCF-1980-ADDR fields SNPA See ROUTE object and ZLAN-LOC-SNPA and ZLAN-RMT-SNPA fields Software requirements for OSI/TS 1-1 SPI commands, table of 1-8 standard de
Index START SU command programming example C-1/14 structure 5-155 tokens in command buffer 5-155/156 tokens in response buffer 5-156 STARTED summary state 4-10, 4-11 Startup message programming example C-1/14, C-27/36 when to issue 2-3 State machine error message 6-5 State-machine error message 6-5 Static subdevices 1-5 See Subdevices and ZDEL-TIME field STATISTICS PROCESS command structure 5-157/158 tokens in command buffer 5-158/159 tokens in response buffer 5-159/163 STATISTICS SERVICE command structure
Index STOP SU command operational notes 5-196 structure 5-194 tokens in command buffer 5-194/195 tokens in response buffer 5-195 STOPPED summary state 4-11 Stopping processes 2-4 STOPPING summary state 4-10, 4-11 SU object aborting See ABORT SU command access error 6-25/26 adding See ADD SU command allowing opens of See ALLOWOPENS SU command altering attributes of See ALTER SU command command failure, in X25AM or TLAM 6-27/28 deleting See DELETE SU command name examples 4-9 obtaining configuration informat
Index SU object (continued) ZCOM-OBJ-SU token 4-9 Subdevice control blocks See ZSCB-TBL-xxx fields Subdevices See SU object and ZDEL-TIME, ZLST-xxx, ZNSP-SU, ZOPENER, ZOPENS-ALLOWED, ZSCB-TBL-xxx, and ZSU-xxx fields control blocks See ZSCB-TBL-xxx fields objects open error A-2 Subjects of event messages 4-11 Subordinate names option 3-7 Subsystem Control Facility See SCF Subsystem Control Point See SCP Subsystem Programmatic Interface See SPI Summary states PROCESS objects, descriptions of 4-10 SU objects,
Index Symbolic names command numbers 3-4 commands and object types, table 5-2/3 event numbers 3-6 object names 3-5 object types 3-4 T TACL definition file 3-1 Takeover by backup, message 6-9/10 TAL definition file 3-1 Tandem internal tokens 6-4 Tandem LAN Access Method See TLAM TCB See ZTCB-TBL-xxx, ZNTIOCBS-xxx, and ZTPDUCBS-xxx fields Templates event-message 3-3 object-name 3-5 Thresholds Layer 3 See also ZIP-DISCARD-xxx fields event messages 6-33/34 Layer 4 See also ZINBOUND-xxx, ZL4-TIMEOUT-THLD, and Z
Index Timestamps See also ZCREATE-TMSTP, ZLST-xxx, ZRESET-TMSTP, and ZSAMPLE-TMSTP fields resetting counters 5-137, 5-148 TLAM version compatibility 1-15 TLAM subsystem See also LAN attributes and ZNSP-DEV field NSP process provider 1-2 TLE See also ZTLE-TBL-xxx fields allocation failure 6-29 Tokens allow-type 3-7 commands 3-4 common to all OSI/TS event messages 6-3 defined by data communications 4-4/11 defined by EMS 4-12 defined by file system 4-14 defined by Guardian 90 4-13 defined by OSI/TS 4-15/19 de
Index TPDUs See ZEXP-BYTES-xxx, ZEXTENDED-FRMT, ZEXT-FRMT, ZINACTV-TIMEOUT, ZINBOUND-xxx, ZL4-EXT-FRMT, ZL4TIMEOUT, ZMAX-REXMIT, ZOUTBOUND-xxx, ZREXMITTIMEOUT, ZTPDUCBS-xxx, ZTPDUS-RECV, contd See ZTPDUS-REXMIT, ZTPDUS-SENT, and ZTPDU-SIZE fields TRACE PROCESS command operational notes 5-203 structure 5-201 tokens in command buffer 5-202/203 tokens in response buffer 5-203 Traces See also ZCOLL-xxx and ZTRACE-xxx fields Transport address invalid 6-31 Transport connection requests See ZINBOUND-xxx and ZOUTB
Index U Unable to allocate segment, message 6-20/21 Unable to create backup process event message 6-14/16 Unable to perform command, message 6-27/28 Unconditional tokens 6-4 User data See ZEXP-BYTES-xxx and ZUSER-BYTES-xxx fields User requests See Requests V Value names defined by data communications 4-6 defined by Guardian 90 4-13 defined by OSI/AS 4-18 defined by SPI 4-3 defined by the file system 4-14 general 4-10 Values, predefined 4-18 ViewPoint 1-1 W Warnings 3-9 Wild card support null objects 4-7 ob
Index X X.25 clear cause codes, table of E-2 diagnostic field codes, table of E-3/8 X.
Index ZCOM-MAPdefinitions, table of 4-6 TRACE-MODIF considerations for OSI/TS 5-202 structure 5-201 ZCOM-OBJdefinitions, table of 4-5 NULL 4-6/7 prefix described 3-4 PROCESS 4-7 ROUTE 4-7/8 SERVICE 4-8/9 SU 4-9 ZCOM-TKNdefinitions, table of 4-6 OBJTYPE 3-5 SUBJ-PROC 4-11 SUBJ-ROUTE 4-11 SUBJ-SERV 4-11 SUBJ-SU 4-11 SUBJ-xxx 3-6 TRACE-BKUP, considerations for OSI/TS 5-202 ZCOM-VALdefinitions, table of 4-6 SUMSTATE-xxx 4-10/11 ZCOM-xxx, tables of 4-4/6 ZCON-WAIT-TIME field See ZCONN-TIMEOUT field ZCONN-TIMEOU
Index ZEMS-TKNCONSOLE-PRINT 3-11, 4-12, 6-3 CPU 6-3 CRTPID 6-3 definitions, tables of 4-12 EMPHASIS 3-11, 4-12, 6-3 EVENT 3-10 EVENTNUMBER 3-6, 4-12, 6-3 GENTIME 6-3 LOGTIME 6-3 PIN 6-3 SUBJECT-MARK 4-13, 6-3 SYSTEM 6-3 USERID 6-3 ZESIS-xxx fields ENABLE 5-43, 5-92 relationship to other fields 5-26 ES-CONF-TIME 5-43, 5-92 ES-GROUP-MAC-ADDR 5-43, 5-92 HOLD-TIME 5-47, 5-85, 5-96 IS-GROUP-MAC-ADDR 5-43, 5-92 MAC-ADDR 5-84 NOTIFY-IS 5-44, 5-92 NSAP 5-84 NSP-DEV 5-85 QUERY-RETRY 5-44, 5-93 QUERY-TIME 5-44, 5-93
Index ZFIL-VAL-xxx definitions, table of 4-14 in ZSPI token 6-18, 6-26 ZGRD definition file 3-2 definitions 4-13 ZGRD-TKN-xxx definitions, tables of 4-13 ZGRD-VALALLOCATESEGMENT 6-21 definitions, table of 4-13 NEWPROCESS 6-15 TRAPOUT 6-23 ZINACTIVITY-TIME field 5-146, 5-172 ZINACTV-TIME field See ZIMACTV-TIMEOUT field ZINACTV-TIMEOUT field 5-22, 5-51, 5-65, 5-99, 5-111 ZINBOUND-xxx fields CR-CONF-ERR-THLD 5-53, 5-100, 5-146, 5-172 CR-CONG 5-144, 5-170 CR-CONG-ERR 5-145, 5-171 CR-CONG-THLD 5-52, 5-100, 5-14
Index ZIP-xxx fields (continued) DISCARD-REASM-THLD 5-46, 5-94, 5-143, 5-169 DISCARD-UNSUP 5-142, 5-168 DISCARD-UNSUP-THLD 5-45, 5-94, 5-143, 5-169 LIFETIME 5-44, 5-93 NULL-LAYER 5-23, 5-44, 5-66, 5-93, 5-113 OCTETS-RECV 5-142, 5-168 OCTETS-SENT 5-142, 5-168 PDUS-RECV 5-142, 5-168 PDUS-SENT 5-142, 5-168 X25-SNDCF 5-23, 5-46, 5-66, 5-94, 5-113 XSUM 5-45, 5-93 ZIPX25-SNDCF-1980-ADDR field 5-47, 5-96 ZL4-xxx fields EXPEDITED 5-188 EXT-FRMT 5-188 TIMEOUT 5-145, 5-171 TIMEOUT-THLD 5-54, 5-101, 5-148, 5-174 WIN
Index ZMAX-EVER-CONN field 5-146, 5-172 ZMAX-REXMIT field 5-22, 5-51, 5-65, 5-99, 5-111, 5-146, 5-172 ZMULTIPLEX field 5-21, 5-51, 5-64, 5-98, 5-111 ZNCB-TBL-xxx fields ALLOC-FAIL 5-134, 5-160 ENTRY-CNT 5-134, 5-160 ENTRY-SIZE 5-134, 5-160 FREE-CNT 5-134, 5-160 MIN-EVER-FREE 5-134, 5-160 ZNETTYPE field description 5-19, 5-49, 5-62, 5-97, 5-109 relationship to other attribute fields 5-26 ZNIOCBS-CURR field 5-136, 5-162 ZNIOCBS-MAX field 5-136, 5-162 ZNSP-DEV field description 5-15, 5-58, 5-106 relationship
Index ZOS4-DDLADD-SU-TSP 5-13/14, 5-15/24 AGGR-PROC-TSP 5-29, 5-30/31 ALTER -SERV-L3 5-41 ALTER-PROC-TSP 5-34, 5-35/36 ALTER-SERV-L3 5-38/39, 5-47 ALTER-SERV-L4 5-39/40, 5-48/54 ALTER-SU-TSP 5-56/57, 5-58/67 CHAR12 4-16 CHAR14 4-17 CHAR40 4-17 CHAR64 4-17 definitions, table of 4-16 INFO-PROC-TSP 5-78, 5-80/81 INFO-ROUTE-L3 5-82, 5-83/85 INFO-SERV-L3 5-86/87, 5-90/96 INFO-SERV-L4 5-87/88, 5-96/102 INFO-SU-TSP 5-103/104, 5-106/113 LISTOP-SU-TSP 5-127, 5-129/130 MAX-MSG-BUF 4-15 MIN-MSG-BUF 4-16 MSG-BUFFER 4-
Index ZOS4-EVT- (continued) L3-THLD 6-33/34 L4-THLD 6-35/37 NSP-DSM-ERR 6-27/28 PROC-ABEND 6-7 SM-ERR 6-5 table of 6-2 TKOVR 6-9/10 TRAP 6-22/24 TSP-DEST-NOT-EXIST 6-31 TSP-DISCONN 6-30 TSP-PROTO-VIOL 6-32 ZOS4-MAPADD-SU-TSP description 5-15/24 structure 5-13/14 AGGR-PROC-TSP description 5-30/31 structure 5-29 ALTER -SERV-L3 description 5-41 ALTER-PROC-TSP description 5-35/36 structure 5-34 ALTER-SERV-L3 description 5-47 structure 5-38/39 ALTER-SERV-L4 description 5-48/54 structure 5-39/40 ALTER-SU-TSP str
Index ZOS4-MAP- (continued) INFO-SERV-L4 structure 5-87/88, 5-96/102 INFO-SU-TSP structure 5-103/104, 5-106/113 LISTOP-SU-TSP structure 5-127, 5-129/130 STATS-PROC-TSP structure 5-131/132, 5-133/136, 5-157/158, 5-159/162 STATS-SERV-L3 description 5-141/143, 5-167/169 structure 5-138/139, 5-164/165 STATS-SERV-L4 description 5-144/148, 5-170/174 structure 5-139/140, 5-165/166 STATS-SU-TSP description 5-149, 5-151, 5-175, 5-177 STATUS-PROC-TSP structure 5-179, 5-181/182 STATUS-SU-TSP description 5-184/185, 5-
Index ZOS4-TKN- (continued) THLD-ID 6-33, 6-36 THLD-VAL 6-34, 6-36 TIME-LAST-REPT 6-34, 6-37 TKOVR-CAUSE 6-9 ZOS4-VALBUF-LEN 4-15 BUFLEN 3-8 CAUSE-xxx 6-9, 6-12 CLASS-xxx 5-20, 5-49, 5-50, 5-63, 5-97, 5-110 CMD-xxx 6-27 CONN-xxx 5-187 definitions 4-18 DISC-xxx 5-187 DISCONN-IN-PRGRSS 5-187 DR-RECEIVED 5-187 INBOUND-xxx 6-36 L4-TIMEOUT 6-36 LOCAL-INITIATED 5-187 MAX-BUFLEN 3-8, 4-16 MIN-BUFLEN 4-16 NETTYPE-xxx 5-19, 5-49, 5-62, 5-97, 5-109 NO-CONN-EVER 5-187 NPDU-DISCARD-xxx 6-33 OUTBOUND-xxx 6-36 REASON-xx
Index ZOUTBOUND-xxx fields CR-CONF-ERR-THLD 5-53, 5-100, 5-147, 5-173 CR-CONG-ERR 5-145, 5-171 CR-ERR 5-145, 5-171 CR-ERR-THLD 5-53, 5-101, 5-147, 5-173 TPDU-PROTO-ERR 5-145, 5-171 TPDU-PROTO-ERR-THLD 5-53, 5-101, 5-147, 5-173 ZOWNERID field 5-182 ZPASV-MUX field 5-54, 5-102 ZPOOL-xxx fields CURR-ALLOC 5-135, 5-161 CURR-FRAG 5-135, 5-161 MAX-ALLOC 5-135, 5-161 MAX-FRAG 5-136, 5-162 SIZE 5-80, 5-135, 5-161 ZPPID field 5-129, 5-181 ZPRI field 5-35, 5-80 ZPRIM-CPU field 5-130, 5-182 ZPRIM-PIN field 5-130, 5-1
Index ZREF-TIME field See ZREF-TIMEOUT field ZREF-TIMEOUT field 5-22, 5-51, 5-65, 5-99, 5-111 ZRESET-TMSTP field 5-133, 5-141, 5-144, 5-151, 5-159, 5-167, 5-170, 5-177 ZREXMIT-TIME field See ZREXMIT-TIMEOUT field ZREXMIT-TIMEOUT field 5-22, 5-51, 5-64, 5-99, 5-111 ZRIOCBS-CURR field 5-136, 5-162 ZRIOCBS-MAX field 5-136, 5-162 ZRMT-NSAP field 5-15, 5-58, 5-106, 5-189 relationship to other attribute fields 5-26 ZRMT-TSEL field 5-19, 5-62, 5-109, 5-188 ZSAMPLE-TMSTP field 5-133, 5-141, 5-144, 5-151, 5-159, 5-
Index ZSPI-TKN- (continued) MANAGER 4-4 MAX-FIELD-VERSION 5-5, 6-3 MAXRESP 5-5 OBJECT-TYPE 3-4, 5-5 POSITION 5-5 RESPONSE-TYPE 3-8 RETCODE 3-9 SERVER-VERSION 5-5 SSID 4-4, 5-5, 6-3 USEDLEN 5-5, 6-3 ZSPI-TYP-xxx definitions, table of 4-3 ZSPI-VAL-xxx definitions, table of 4-3 ZSPIDEF definition files 3-2 ZSU-xxx fields OTHER 5-31 STARTED 5-31 STOPPED 5-31 ZSUMSTATE field 5-181, 5-186 ZSWAPVOL field 5-80 ZSYNCDEPTH field 5-129 ZTCB-TBL-xxx fields ALLOC-FAIL 5-134, 5-160 ENTRY-CNT 5-134, 5-160 ENTRY-SIZE 5-13
Index ZTPDUS-xxx fields RECV 5-144, 5-151, 5-170, 5-177 REXMIT 5-144, 5-151, 5-170, 5-177 SENT 5-144, 5-151, 5-170, 5-177 ZTRACE-FILE field 5-182 ZTRACE-MASK field 5-181 ZTTR-TIMEOUT field 5-22, 5-52, 5-65, 5-99, 5-112 ZTWR-TIMEOUT field 5-22, 5-52, 5-65, 5-100, 5-112 ZUSER-BYTES-RECV field 5-144, 5-151, 5-170, 5-177 ZUSER-BYTES-SENT field 5-144, 5-151, 5-170, 5-177 ZUSER-ID field 5-190 ZUSERID field 5-130 ZWIN-TIME field 5-172 See ZWIN-TIMEOUT field ZWIN-TIMEOUT field 5-22, 5-52, 5-65, 5-99, 5-112, 5-146
Index ZX25REMOTENET field 5-18, 5-42, 5-61, 5-91, 5-108 ZX25REVERSECHG field 5-17, 5-42, 5-61, 5-91, 5-108 ZX25RPOA field 5-24, 5-47, 5-67, 5-95, 5-113 ZX25RPOA-DNIC-CNT field 5-24, 5-47, 5-67, 5-95, 5-113 ZX25THRUPUT field 5-18, 5-42, 5-61, 5-91, 5-108 ZX25TRANSIT-DELAY field 5-24, 5-47, 5-67, 5-96, 5-113 ZXPROCID field 5-130 ZXPROCID-LEN field 5-130 ZXSUM field 5-21, 5-50, 5-64, 5-98, 5-110, 5-188 Index–40 056786 Tandem Computers Incorporated
