Networking and Data Communications Library Tandem OSI/AS Management Programming Manual Product Version OSI/AS C30 Release ID C30.08/D10 Edition Print Date Part Number Abstract July 1992 056785 This manual describes the DSM programmatic interfaces (SPI-format commands, responses, and event messages) to the Tandem OSI/AS subsystem. It is intended for programmers writing management applications that communicate with OSI/AS.
Document History Edition Part Number Product Version Release ID Print Date First Edition Second Edition 24503 056785 OSI/AS C21 OSI/AS 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/AS Management Programming Manual. This manual documents the interactive interface to the C30 release of the Open Systems Interconnection/Application Services (OSI/AS). This manual also contains additional enhancements to the previous edition. The following subsection summarizes these changes.
New and Changed Information Manual Enhancements Appendix D, “OSI/AS SCF Attribute Name Changes,” was added to summarize attribute name changes made to improve usability. The abbreviations and glossary sections have been updated.
Contents About This Manual xiii Notation Conventions Section 1 xxi Introduction Why Management Programming for OSI/AS? 1-1 OSI/AS Subsystem Architecture 1-2 Control-and-Inquiry Interface 1-4 Event-Management Interface 1-6 Programmatic Commands 1-8 Object Types 1-8 SUBSYS 1-8 PROCESS 1-8 ENTRY 1-8 SERVICE 1-8 PROFILE 1-9 SU 1-10 Hierarchy of Object Types 1-10 Management Functions Provided 1-12 Commands 1-12 Event Messages 1-15 C-Series and D-Series Compatibility 1-16 C30 OSI/AS Running in a D-Series
Contents Section 3 SPI Programming Considerations for OSI/AS Definition Files 3-1 Templates and Labels 3-3 Naming Guidelines for Applications 3-3 Message Elements for the OSI/AS Subsystem Commands 3-4 Object Types 3-4 Object Names 3-5 Event Numbers 3-6 Subjects of Event Messages 3-7 Other Tokens 3-7 Data Lists and Error Lists 3-7 3-4 Using SPI to Build Commands and Decode Responses 3-7 Building and Sending a Command Message 3-7 Discontinuing a Command in Progress 3-8 Receiving and Decoding a Respo
Contents Summary States for PROCESS Objects Summary States for SU Objects 4-15 EMS Standard Definitions 4-15 GUARDIAN 90 Definitions File-System Definitions 4-14 4-16 4-17 OSI/AS Definitions 4-18 Buffer Declarations 4-18 Fixed Structures and Character Strings 4-20 Fixed Structures 4-20 Character Strings 4-22 Predefined Token and Field Values 4-24 Tokens 4-24 Section 5 Commands and Responses Commands by Object Type 5-1 Sensitive and Nonsensitive Commands 5-6 Command Descriptions 5-7 ABORT PROCES
Contents INFO PROFILE Command 5-125 INFO SERVICE Command 5-137 INFO SUBSYS Command 5-160 LISTOBJECTS NULL Command 5-163 LISTOBJECTS ENTRY Command 5-165 LISTOBJECTS PROCESS Command 5-167 LISTOBJECTS PROFILE Command 5-170 LISTOBJECTS SERVICE Command 5-172 LISTOBJECTS SU Command 5-174 LISTOBJECTS SUBSYS Command 5-176 LISTOPENS PROCESS Command 5-179 LISTOPENS SU Command 5-183 RESETSTATS PROCESS Command 5-187 RESETSTATS SERVICE Command 5-191 RESETSTATS SU Command 5-210 RESETSTATS SUBSYS Command 5-214 START PROC
Contents 4: ZOSI-EVT-BKUP-DOWN 6-16 5: ZOSI-EVT-BKUP-CREATE-FAIL 6-18 6: ZOSI-EVT-CHKPT-FAIL 6-22 7: ZOSI-EVT-PROC-CREATE-FAIL 6-24 8: ZOSI-EVT-SM-ERR 6-27 9: ZOSI-EVT-INIT-L4-SU-OPEN-FAIL 6-28 10: ZOSI-EVT-ACSE-THLD 6-30 11: ZOSI-EVT-L6-THLD 6-35 12: ZOSI-EVT-L5-THLD 6-39 Appendix A Errors and Error Lists ZCOM Errors Returned by OSI/AS Notation Used A-1 A-1 Descriptions of ZOSI Errors A-2 1: ZOSI-ERR-ZGRD-ERR A-3 2: ZOSI-ERR-BOUNDS-ERR A-5 3: ZOSI-ERR-OBJ-ACTV A-6 4: ZOSI-ERR-UNKWN-SERVR-ERR Appendi
Contents Appendix D Abbreviations Attribute Name Changes Abbreviations-1 Glossary Glossary–1 Index Figures Index–1 Figure 0-1. Documentation Road Map Figure 1-1. OSI/AS Subsystem Architecture Figure 1-2. Management Interfaces to OSI/AS: Control and Inquiry 1-5 Figure 1-3. Management Interfaces to OSI/AS: Event Management 1-7 Figure 1-4. Hierarchy of Object Types Figure 1-5. High PIN to Low PIN Communication in D-Series Systems 1-17 Figure 1-6.
Contents Table 4-10. Data Communications Standard Definitions for Extensible Structured Tokens 4-5 Table 4-11. EMS Standard Definitions for Header Tokens Table 4-12. EMS Standard Definitions for Other Simple Tokens Table 4-13. GUARDIAN 90 Definitions for Simple Tokens Table 4-14. GUARDIAN 90 Definitions for Value Names Table 4-15. File-System Definitions for Simple Tokens Table 4-16. File-System Definitions for Value Names Table 4-17. OSI/AS Definitions for Fixed Structures Table 4-18.
Contents xii 056785 Tandem Computers Incorporated
About This Manual About the OSI/AS and The OSI/AS subsystem and the OSI/TS subsystem together provide core services that OSI/TS Manual Set 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. Overview of Contents of OSI/AS and OSI/TS Manuals Is Provided by This Manual and Other Manuals in the OSI Manual Set ..
About This Manual The Purpose of This Manual The Tandem OSI/AS Management Programming Manual provides subsystem-specific information about the management programming interfaces to the Tandem OSI/AS 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/AS subsystem. The 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/AS subsystem and how a management application fits into it (Section 1) The types of objects managed by OSI/AS and the operations necessary to manage these objects (Section 1) The kinds of events reported by OSI/AS (Section 1) How to set up communications with the OSI/AS subsystem, including how to start the OSI manager
About This Manual What Related The other publications related to this manual fall into three categories: standards Publications Are documents, with which you should first be familiar; prerequisite manuals, which you Available? should read before you read this manual; and other Tandem OSI manuals.
About This Manual Figure 0-1. Documentation Road Map Introduction to Tandem NonStop Systems Introduction to Tandem NonStop Systems Distributed Systems Management (DSM) Programming Manual Introduction to Distributed Systems Management (DSM) Event Management Service (EMS) Manual Guardian 90 Operating System Programmer's Guide 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 X25AM Management Programming Manual describes the management programming interface to the X.25 Access Method (X25AM) subsystem. Since OSI/AS relies on either X25AM or TLAM for lower-layer functions, a program written to manage OSI/AS may also need to send commands to X25AM or to handle X25AM event messages. TLAM Management Programming Manual describes the management programming interface to the Tandem LAN Access Method (TLAM) subsystem.
About This Manual xx 056785 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/AS (Open Systems Interconnection/Application Services) subsystem provides a Session Layer, Presentation Layer, and Association Control Service Element (ACSE) interface to OSI networks. OSI/AS requires Tandem OSI/TS, plus one of the following Tandem access methods: X.
Introduction OSI/AS Subsystem Architecture Information obtained through programmatic interfaces can be translated directly into procedures, reports, and so forth. An application that uses the programmatic interfaces to subsystems can perform tasks that once required the use of several different interactive interfaces. In addition, the capability to write your own management applications allows you to tailor them to the needs and configuration of your network.
Introduction OSI/AS Subsystem Architecture Figure 1-1.
Introduction OSI/AS Subsystem Architecture Control-and-Inquiry Interface Figure 1-2 illustrates the management interface to OSI/AS for commands and responses. For management of the OSI/AS subsystem, the Subsystem Control Point (SCP) process is required. This process provides control-and-inquiry management interfaces to a number of Tandem data communications subsystems.
Introduction OSI/AS Subsystem Architecture Figure 1-2. Management Interfaces to OSI/AS: Control and Inquiry SCF Mgmt.
Introduction OSI/AS Subsystem Architecture Event-Management Interface Event messages from OSI/AS 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 interfaces to OSI/AS and related subsystems.
Introduction OSI/AS Subsystem Architecture Figure 1-3.
Introduction Programmatic Commands Programmatic Like all other subsystems that support DSM, OSI/AS defines a set of object types—the Commands kinds of objects that can be managed by OSI/AS—and a set of commands that can be performed on objects of these types. Object Types The OSI/AS object types are: SUBSYS PROCESS ENTRY SERVICE PROFILE SU In addition, a null object type is provided for those commands that do not require specification of a particular object type.
Introduction Programmatic Commands The ACSE SERVICE, for ACSE thresholds You can neither add nor delete SERVICE objects. SERVICE objects define configurations that affect all connections within their respective layers. However, within the Network, Transport, and Session Layers, you can configure particular SNPAs, NSAPs, and TSELs with values that override the default SERVICE values by assigning PROFILE objects (discussed in the next subsection) to these addresses.
Introduction Programmatic Commands SU An SU (subdevice) object is a subdevice created in response to an application request for OSI services. When a communications application requests establishment of a connection (called an association for ACSE) by calling APS_ASSOC_CONNECTREQ_ or APS_ASSOC_ATTACH_ , OSI/AS causes SU objects to be created in the NSP, TSP, and TAPS processes that service the connection. There are two types of SUs: static and dynamic.
Introduction Programmatic Commands process or directly through their associated TAPS processes. These SERVICE objects can be altered only through the OSI manager process. L3 and L4 PROCESS or SERVICE objects can be inquired about and altered either indirectly through the OSI manager process or directly through their associated TSP processes. However, it is recommended that these SERVICE attributes be altered only through the OSI manager process.
Introduction Programmatic Commands Management Functions Provided The OSI/AS subsystem provides your application with the capability to do the following: Add processes, profiles, and entries to an OSI/AS subsystem Delete processes, profiles, and entries from an OSI/AS subsystem Change certain characteristics, or attributes, of the subsystem and its processes, services, profiles, and entries Obtain information about the current attributes of the subsystem and its processes, services, profiles, and entries O
Introduction Programmatic Commands Table 1-1 Programmatic Commands and Interactive (SCF) Commands (Page 1 of 2) Programmatic Command Programmatic Object Type Interactive (SCF) Command Interactive (SCF) Object Type ZCOM-CMD-ABORT ZCOM-OBJ-PROCESS ZCOM-OBJ-SU ZCOM-OBJ-PROCESS ZCOM-OBJ-ENTRY ZCOM-OBJ-PROCESS ZCOM-OBJ-PROFILE ZCOM-OBJ-PROCESS ZCOM-OBJ-ENTRY ZCOM-OBJ-PROCESS ZCOM-OBJ-PROFILE ZCOM-OBJ-SERVICE ZCOM-OBJ-SUBSYS ZCOM-OBJ-ENTRY ZCOM-OBJ-PROCESS ZCOM-OBJ-PROFILE ZCOM-OBJ-ENTRY ZCOM-OBJ-PROCESS ZC
Introduction Programmatic Commands Table 1-1 Programmatic Commands and Interactive (SCF) Commands (Page 2 of 2) Programmatic Command Programmatic Object Type Interactive (SCF) Command Interactive (SCF) Object Type ZCOM-CMD-STATUS ZCOM-OBJ-PROCESS ZCOM-OBJ-SU ZCOM-OBJ-SUBSYS ZCOM-OBJ-PROCESS ZCOM-OBJ-SU ZCOM-OBJ-PROCESS ZCOM-OBJ-PROCESS ZCOM-OBJ-PROCESS ZCOM-OBJ-NULL ZCOM-OBJ-PROCESS ZCOM-OBJ-SUBSYS STATUS PROCESS SU SUBSYS PROCESS SU PROCESS PROCESS PROCESS NULL PROCESS PROCESS ZCOM-CMD-STOP ZCOM-C
Introduction Event Messages Event Messages OSI/AS subsystem processes generate event messages when they detect significant events, such as a trap caused by a hardware or software error, a failure to establish communication with the Transport Layer, 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.
Introduction C-Series and D-Series Compatibility C-Series and D-Series This C30 version of OSI/AS is able to run at a high PIN (process identification Compatibility number) 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/AS-Specific Compatibility Information It is assumed, in this case, that the application, OSI/AS, 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/AS version C21).
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/AS Running in Mixed C-Series and D-Series Expand Networks The following subsections contain OSI/AS-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.
Introduction C-Series and D-Series Compatibility Managing C21 OSI/AS (in a C-Series System) Using C30 SCF or SCP (in a D-Series System) New DSM functionality provided by the C30 version of SCF is available only with C30 or later versions of OSI/AS. This means that new information fields provided by the C30 SCF are not recognized by C21 OSI/AS (C21 OSI/AS does not supply information for these fields). C30 SCF commands containing new attributes are rejected by C21 OSI/AS.
2 Communicating With the OSI/AS 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/AS subsystem. Communicating To manage the OSI/AS subsystem, your application sends commands to be performed Through SCP by the OSI manager, TAPS, TSP, and NSP processes.
Communicating with the OSI/AS Processes Running the OSI/AS Subsystem Processes Running the OSI/AS Before your management application can send commands to OSI/AS through SCP, Subsystem Processes you must first install your NSP processes using the Tandem system generation program SYSGEN. For instructions, refer to the sections on configuration of X25AM and TLAM in the System Generation Manual. The Tandem OSI/AS Configuration and Management Manual also provides information on installing NSP processes.
Communicating with the OSI/AS Processes Running the OSI/AS Subsystem Processes You can use an implicit RUN command (that is, omit the word RUN) if your OSIMGR file resides on the subvolume $SYSTEM.SYSTEM or $SYSTEM.SYSnn.
Communicating with the OSI/AS Processes Running an EMS Consumer Distributor Your management application can then add PROCESS or other objects to the MIB, or change existing MIB entries, by sending OSI/AS ADD and ALTER programmatic commands. Finally, your application must send START PROCESS commands, using the indirectprocess-name (described under ZCOM-OBJ-PROCESS in Section 4), to start the configured TAPS and TSP processes in the OSI/AS environment.
3 SPI Programming Considerations for OSI/AS Once your subsystem and EMS processes are running and your management application has established communication with them, the main business of your management application is to format and send commands, decode responses and act on the results, and interpret event messages and act on their information.
SPI Programming Considerations for OSI/AS Definition Files Definition files are named according to the following convention: ZSPIDEF.ZsubsysC ZSPIDEF.ZsubsysCOB ZSPIDEF.ZsubsysDDL ZSPIDEF.ZsubsysTACL ZSPIDEF.ZsubsysTAL ZSPIDEF.ZsubsysP subsys is a three-character code identifying the subsystem or other software component to which these definitions belong. This code is OSI for Tandem OSI/AS. The last characters of each file name denote the language in which the definitions in this file are coded.
SPI Programming Considerations for OSI/AS Naming Guidelines for Applications Likewise, a management application written in C that sends commands to and retrieves event messages issued by the OSI/AS subsystem would need the following include statements: #include #include #include #include #include #include "zspidef.zspic" "zspidef.zcomc" "zspidef.zosic" "zspidef.zemsc" "zspidef.zgrdc" "zspidef.
SPI Programming Considerations for OSI/AS Message Elements for the OSI/AS Subsystem Tokens that start with a ZX____ are for D-series systems only. They are either new tokens or a replacement for a token similarly named (but without the "X") for C-series systems. Information will be returned in the D-series token and also in the C-series equivalent if the information fits (the field is otherwise left null).
SPI Programming Considerations for OSI/AS Message Elements for the OSI/AS Subsystem PROCESS PROFILE SERVICE SU SUBSYS All commands and responses contain an object-type token in the header. For the OSI/AS subsystem, object types are identified in programs by symbolic names of the form ZCOM-OBJ-name, where name identifies the object type. For example, the ENTRY object type is represented by the name ZCOM-OBJ-ENTRY. The object-type header token, ZSPI-TKN-OBJECT-TYPE, always has one of these values.
SPI Programming Considerations for OSI/AS Message Elements for the OSI/AS Subsystem Table 3-1. Wild-Card Support for OSI/AS Programmatic Commands (Page 2 of 2) For This Wild-Card Character... This Command... Supports Wild-Cards for This Object-Type...
SPI Programming Considerations for OSI/AS Using SPI to Build Commands and Decode Responses In these event messages, the event-number header token (ZEMS-TKNEVENTNUMBER) can assume any one of the set of event numbers for OSI/AS, which are listed at the beginning of Section 6. The OSI/AS event messages are described in Section 6. The OSI/AS subsystem also generates common data communications (ZCOM) event messages. These are described in the Communications Management Programming Manual.
SPI Programming Considerations for OSI/AS Using SPI to Build Commands and Decode Responses 6. Send the command message using the mechanism appropriate to your programming language (for example, a WRITEREAD call in TAL). The recommended buffer size (in bytes) for all commands sent to the OSI/AS subsystem is ZOSI-VAL-BUFLEN. The maximum buffer size that OSI/AS accepts is ZOSI-VAL-MAX-BUFLEN. The OSI/AS subsystem does not support multiple commands in a single request message.
SPI Programming Considerations for OSI/AS 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/AS Retrieving and Decoding Event Messages Error Handling Each response returned by OSI/AS includes a return token (ZSPI-TKN-RETCODE), whose value indicates whether an error occurred when OSI/AS 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/AS Retrieving and Decoding Event Messages appropriate to your programming language (for example, a WRITEREAD call in TAL). 4. Read the response from the distributor using the mechanism appropriate to your programming language (for example, a WRITEREAD call in TAL). 5. Repeat the following steps in a loop: a.
SPI Programming Considerations for OSI/AS Retrieving and Decoding Event Messages compatible mode, to the OPRLOG and any $AOPR process. The threshold event messages, of concern only to applications that monitor thresholds, have ZEMS-TKNCONSOLE-PRINT set to ZSPI-VAL-FALSE and so are not sent to the console, OPRLOG, or $AOPR. You can override the value of ZEMS-TKN-CONSOLE-PRINT using the OVERRIDE option of the DSM template compiler, as described in the DSM Template Services Manual.
SPI Programming Considerations for OSI/AS Retrieving and Decoding Event Messages The Event Management Service (EMS) Manual provides information on how to code, compile, load, and replace filters.
4 Common Definitions This section lists the common definitions—those used in several commands, responses, or event messages—for the OSI/AS subsystem. Definitions used in only one or two commands, responses, or event messages are described under the 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 describe their use by OSI/AS. Subsystem-specific information for those two definitions is given in the following paragraphs. ZSPI-TKN-SSID When used in OSI/AS commands, the header token ZSPI-TKN-SSID has the value ZOSI-VAL-SSID, which identifies the OSI/AS subsystem. ZOSI-VAL-SSID is actually a set of three values defined as a structure. Its definition is given under “OSI/AS Definitions” later in this section.
Common Definitions Data Communications Standard Definitions Table 4-7. Data Communications Standard Definitions for Object Types Object Types ZCOM-OBJ-ENTRY ZCOM-OBJ-NULL ZCOM-OBJ-PROCESS ZCOM-OBJ-PROFILE ZCOM-OBJ-SERVICE ZCOM-OBJ-SU ZCOM-OBJ-SUBSYS Table 4-8.
Common Definitions Data Communications Standard Definitions Object Types and Object Names This section describes the syntax rules for object-specs. An object-spec is a combination of an object-type and an object-name. The syntax for each programmatic command contains the variable object-spec. ZCOM-TKN-OBJNAME identifies, by name, an object or a wild card representing a set of objects on which the command is to be performed.
Common Definitions Data Communications Standard Definitions An NSAP entry-name identifies a network service access point (NSAP). It is used to configure a TSP server process for a local NSAP, as well as the subnetwork point of attachment (SNPA) for both local and remote NSAPs. NSAP ENTRY objects make up the routing table for the OSI end system. An NSAP entry-name is a string of hexadecimal digits. Its maximum length is 40 hexadecimal digits (20 octets).
Common Definitions Data Communications Standard Definitions For the LISTOBJECTS command, no object name is specified for the null object type. For the GETVERSION command, if an object name is specified, it must be of the form: $process-name process-name is the Guardian 90 process name of an OSI manager or TAPS process. Wild-Card Support Wild cards are not supported for the null object. ZCOM-OBJ-PROCESS A PROCESS object identifies a specific process.
Common Definitions Data Communications Standard Definitions The indirect-process-name identifies a TAPS, TSP, or NSP process through its associated OSI manager process. This format is allowed only in commands directed to the OSI manager process—that is, commands in which the value of either ZSPI-TKNMANAGER or ZCOM-TKN-XMGR is the name of the OSI manager process. The object-name for the PROCESS object for indirect-process-name has the following format: $osi-mgr-name.#process-type.
Common Definitions Data Communications Standard Definitions The object-name for the PROCESS object for process-name has the following format: $process-name process-name is the Guardian 90 process name of the specified OSI manager or TAPS process. Examples $OMGR $TAPS ZCOM-OBJ-PROFILE ZCOM-OBJ-PROFILE defines a template that contains configuration parameters for dynamic subdevices. Names of PROFILE objects have the following form: $osi-mgr-name.#profile-type.
Common Definitions Data Communications Standard Definitions Examples $MGR.#L5.REMOTE1 $MGR.#L5.REMOTE* $MGR.#L4.LOCAL1 $MGR.#L3.REMOTE2 $MGR.#L?.REMOTE2 ZCOM-OBJ-SERVICE ZCOM-OBJ-SERVICE defines attributes to be associated with a specific service element or protocol layer. Names of SERVICE objects have the following form: $process-name.#service-name $process-name is the Guardian 90 process name of the OSI manager process or TAPS process associated with the specified SERVICE object.
Common Definitions Data Communications Standard Definitions configuration used by the first connection. You specify the SU type with the ZDELTIME attribute. It has a name of the following form: $process-name.#su-name $process-name is the Guardian 90 process name of the TAPS process that manages the specified subdevice. #su-name is a pound sign followed by up to 7 alphanumeric characters identifying a particular SU. The first character after the pound sign must be alphabetic.
Common Definitions Data Communications Standard Definitions Examples $MGR Simple Tokens The ZCOM simple tokens include subjects of event messages and various other simple tokens. Subjects of Event Messages Each OSI/AS event message includes one of the following tokens to identify the subject of the event message. ZCOM-TKN-SUBJ-PROC identifies a PROCESS as the subject of an event message. Its value is the Guardian 90 name of the OSI/AS subsystem process that detected the event.
Common Definitions Data Communications Standard Definitions systems is the ZSPI-TKN-MANAGER token. See Table 4-2 “SPI Standard Definitions for Other Simple Tokens,” earlier in this section. Value Names The Value Name tokens describe summary states. For OSI/AS, ZCOM summary states apply to PROCESS and SU (subdevice) objects. Summary States for PROCESS Objects The following states apply to OSI manager and TAPS processes.
Common Definitions EMS Standard Definitions summary states, refer to the management programming manuals for the OSI/TS, X25AM, and TLAM subsystems. Summary States for SU Objects ZCOM-VAL-SUMSTATE-ABORTING means that the subdevice is in transition to the STOPPED state because an ABORT command was issued for that subdevice. The subdevice will not accept any requests from applications. ZCOM-VAL-SUMSTATE-STARTED means that the subdevice is ready to support an application connection or is already doing so.
Common Definitions Guardian 90 Definitions Descriptions of the EMS standard definitions as they apply to all subsystems are given in the Event Management Service (EMS) Manual. The information in that manual suffices to describe the use of some of the definitions listed in Tables 4-11 and 4-12; for others, additional subsystem-specific considerations apply. OSI/AS subsystemspecific considerations for EMS definitions are given in the following paragraphs.
Common Definitions File-System Definitions Table 4-13. Guardian 90 Definitions for Simple Tokens Simple Tokens ZGRD-TKN-BINDTIMESTAMP ZGRD-TKN-CPU ZGRD-TKN-CRTPID ZGRD-TKN-ENTRYPOINTLABEL ZGRD-TKN-EREGISTER ZGRD-TKN-ERROR ZGRD-TKN-LREGISTER ZGRD-TKN-OBJECTFILE ZGRD-TKN-PREGISTER ZGRD-TKN-PRIORITY ZGRD-TKN-PROCESSNAME ZGRD-TKN-SREGISTER ZGRD-TKN-STACKENV ZGRD-TKN-LREGISTER ZGRD-TKN-SWAPFILE XGRD-TKN-ZCPU ZGRD-TKN-XOBJECTFILE ZGRD-TKN-XPROCESSNAME ZGRD-TKN-XSWAPFILE ZGRD-TKN-PROCESSDESCR Table 4-14.
Common Definitions OSI/AS Definitions For descriptions of these definitions, refer to the System Procedure Errors and Messages Manual. OSI/AS Definitions Definitions whose names begin with ZOSI are OSI/AS definitions. These definitions consist of simple tokens and extensible structured tokens used in OSI/AS commands and responses. They are provided in the ZSPIDEF.ZOSIDDL file and in the corresponding files for other languages.
Common Definitions OSI/AS Definitions ZOSI-DDL-MAX-MSG-BUF is a message buffer of the maximum allowable size. It has the following structure: def ZOSI-DDL-MAX-MSG-BUF. 02 Z-MSGCODE type ZSPI-DDL-INT. 02 Z-BUFLEN type ZSPI-DDL-INT. 02 Z-OCCURS type ZSPI-DDL-INT. 02 Z-FILLER type ZSPI-DDL-BYTE occurs 0 to ZOSI-VAL-MAX-BUFLEN times depending on Z-OCCURS. end. ZOSI-VAL-MAX-BUFLEN is the same size as ZCOM-VAL-MAX-BUF-LEN, the maximum buffer size for data communications subsystems.
Common Definitions OSI/AS Definitions Fixed Structures and Character Strings Tables 4-17 and 4-18 list the fixed (nonextensible) structures and the character strings defined by the OSI/AS subsystem. Table 4-17. OSI/AS Definitions for Fixed Structures Fixed Structures ZOSI-DDL-AE-TITLE ZOSI-DDL-NSAP ZOSI-DDL-OBJ-ID ZOSI-DDL-OSINAME ZOSI-DDL-PSEL ZOSI-DDL-SNPA ZOSI-DDL-SSEL ZOSI-DDL-TSEL Table 4-18.
Common Definitions OSI/AS Definitions ZOSI-VAL-AE-TITLE-FORMAT0 No application entity title is used. ZOSI-VAL-AE-TITLE-FORMAT2 A format-2 application entity title is present in ZAE-TITLE-FORMAT2. OSI/AS supports only format-2 application entity titles. ZAE-TITLE-FORMAT2 defines the structure of a format-2 application entity title. ZAE-QUALIFIER-ISPRESENT indicates whether an application entity qualifier is present in ZAEQUALIFIER.
Common Definitions OSI/AS Definitions ZOBJ-ID is an array of up to 16 integers, representing up to 16 levels in the object identifier hierarchy. ZOSI-DDL-OSINAME is the common name by which the application is known to the local subsystem. The OSI name is defined locally only. Its definition is as follows: ZOSI-DDL-OSINAME type ZSPI-DDL-CHAR128. ZOSI-DDL-PSEL is a presentation selector (PSEL). It is defined as follows: ZOSI-DDL-PSEL type ZSPI-DDL-CHAR16.
Common Definitions OSI/AS Definitions def ZOSI-DDL-CHAR12. 02 Z-C 02 Z-S redefines Z-C. 03 Z-I 02 Z-B redefines Z-C end. pic x(12) spi-null " ". type binary 16 pic x occurs 6 times. occurs 12 times. ZOSI-DDL-CHAR20 is a 20-character structure whose fields are addressable either as string-type or as integer-type values. Its definition is as follows: def ZOSI-DDL-CHAR20. 02 Z-C 02 Z-S redefines Z-C. 03 Z-I 02 Z-B redefines Z-C end. pic x(20) spi-null " ". type binary 16 pic x occurs 10 times.
Common Definitions OSI/AS Definitions Predefined Token and Field Values The OSI/AS subsystem defines three values for use in tokens and token fields in several commands, event messages, or error lists. These values are listed in Tables 419 and 4-20.
5 Commands and Responses This section describes the syntax and semantics for all commands and responses in the management programming interface to OSI/AS. 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 the OSI/AS programmatic commands.
Commands and Responses Commands by Object Type Table 5-1.
Commands and Responses Commands by Object Type Table 5-1.
Commands and Responses Commands by Object Type Table 5-2.
Commands and Responses Commands by Object Type Table 5-2.
Commands and Responses Sensitive and Nonsensitive Commands Sensitive and Commands are divided into two groups: sensitive commands and nonsensitive Nonsensitive commands. A command is classified as either sensitive or nonsensitive based on its Commands impact on the subsystem and on whether a user must have proper security to use it.
Commands and Responses Command Descriptions Command Each OSI/AS programmatic command and its response is described in detail on the Descriptions following pages. The command descriptions are presented in alphabetical order; for commands that can be applied to more than one object type, a separate description is given for each command object-type pair.
Commands and Responses Command Descriptions Table 5-3.
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 places the specified process in the STOPPED state. This is a sensitive command.
Commands and Responses ABORT PROCESS Command ZCOM-TKN-OBJNAME can occur only once, and it must be the name of that TAPS process. If you are sending the command to the OSI manager process, ZCOMTKN-OBJNAME can occur multiple times. The process-name format depends on the type of process, as follows: If the object is the OSI manager process, use process-name. If the object is a TSP process, use indirect-process-name. If the object is a TAPS process, use indirect-process-name.
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 subdevice, and then terminates the operation of the subdevice. This is a sensitive command.
Commands and Responses ABORT SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses ACTIVATE PROCESS Command ACTIVATE PROCESS Command The ACTIVATE command changes the state of a suspended (SUSP) process to STARTED. This is a sensitive command.
Commands and Responses ACTIVATE PROCESS Command that TAPS process. If you are sending the command to the OSI manager process, ZCOM-TKN-OBJNAME can occur multiple times. The process-name format depends on the type of process, as follows: If the object is the OSI manager process, use process-name. If the object is a TSP process, use indirect-process-name. If the object is a TAPS process, use indirect-process-name. ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual.
Commands and Responses ADD ENTRY Command ADD ENTRY Command The ADD ENTRY command creates the specified ENTRY object, defines its attributes, and adds it to the OSI/AS subsystem. You can use this command to add an APPL, NSAP, SNPA, or TSEL ENTRY. This is a sensitive command. Command ZCOM-CMD-ADD Object Type ZCOM-OBJ-ENTRY 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.
Commands and Responses ADD ENTRY Command Tokens in Command Buffer (continued) 02 ZNETADDR-MODE 02 ZL3-PROF end. type ZSPI-DDL-ENUM. type ZSPI-DDL-FNAME32. ZOSI-MAP-ADD-ENTRY-SNPA def ZOSI-DDL-ADD-ENTRY-SNPA. 02 ZL3-SERVR 02 ZL3-PROF end. ZOSI-MAP-ADD-ENTRY-TSEL def ZOSI-DDL-ADD-ENTRY-TSEL. 02 ZL5-SERVR 02 ZL5-PROF 02 ZL4-PROF end. ZCOM-TKN-CMD-TIMEOUT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT type ZSPI-DDL-FNAME32. type ZSPI-DDL-FNAME32. type ZSPI-DDL-FNAME32. type ZSPI-DDL-FNAME32.
Commands and Responses ADD ENTRY Command Depending on the type of ENTRY specified in ZCOM-TKN-OBJNAME, you must include one of the following tokens in the command: ZOSI-MAP-ADD-ENTRY-APPL to add an application ENTRY ZOSI-MAP-ADD-ENTRY-NSAP to add an NSAP ENTRY ZOSI-MAP-ADD-ENTRY-SNPA to add an SNPA ENTRY ZOSI-MAP-ADD-ENTRY-TSEL to add a TSEL ENTRY ZOSI-MAP-ADD-ENTRY-APPL is an extensible structured token that contains attributes of the application being added to the OSI/AS subsystem’s Management In
Commands and Responses ADD ENTRY Command ZSSEL-LEN is the length (in bytes) of the SSEL address in ZSSEL. The range of values is 0 through 16 bytes. ZSSEL is the SSEL address for the application being added. The SSEL address is a binary-encoded string of an even number of hexadecimal digits. SSEL addresses are administered locally. ZPSEL-LEN is the length (in bytes) of the PSEL address in ZPSEL. The range of values is 0 through 16 bytes. ZPSEL is the PSEL address for the application being added.
Commands and Responses ADD ENTRY Command ZL3-SERVR is the indirect-process-name of the NSP process. It has precedence over the L3 server configured with the SNPA. ZL4-SERVR is the indirect-process-name of the TSP process. It has precedence over the L4 server configured with the NSAP. ZL5-SERVR is the indirect-process-name of the TAPS process. It has precedence over the L5 server configured with the TSEL.
Commands and Responses ADD ENTRY Command ZOSI-MAP-ADD-ENTRY-NSAP is an extensible structured token that contains the attributes for the specified NSAP. ZOSI-DDL-ADD-ENTRY-NSAP contains the following fields: ZL4-SERVR is the indirect-process-name of the TSP process that services the NSAP being added. ZL4-PROF is the name of the Layer 4 PROFILE to be used when a TSP subdevice is configured for communication through the NSAP being added. ZSNPA-LEN is the length (in bytes) of the SNPA in ZSNPA.
Commands and Responses ADD ENTRY Command ZL3-PROF is the name of the Layer 3 PROFILE to be used when an NSP subdevice is configured for communication through the SNPA being added. ZOSI-MAP-ADD-ENTRY-TSEL is an extensible structured token that contains the attributes for the specified TSEL ENTRY. ZOSI-DDL-ADD-ENTRY-TSEL contains the following fields: ZL5-SERVR is the indirect-process-name of the TAPS process that services the TSEL being added.
Commands and Responses ADD ENTRY Command Operational Notes In order to decide where to specify servers and profiles, the reader must understand how the OSI manager process establishes connections. The following discussion explains this process. After reading this discussion, read the considerations for the ENTRY object to see where to specify servers and profiles.
Commands and Responses ADD ENTRY Command 2. The OSI manager selects the TAPS, TSP, and NSP server process: #L5 Server (TAPS process) 1. Local #APPL ENTRY 2. Local #TSEL ENTRY #L4 Server (TSP process) 1. Local #APPL ENTRY 2. Local #NSAP ENTRY #L3 Server (NSP process) 1. Local #APPL ENTRY 2. Local #SNPA ENTRY 3. The OSI manager determines which set of protocol-related attributes will be used to define connection parameters for TAPS and TSP subdevices: a.
Commands and Responses ADD ENTRY Command #L3 (network) values: 1. 2. 3. 4. 5. 6. 7. 4. #L3 PROFILE in remote #APPL ENTRY #L3 PROFILE in remote #NSAP ENTRY #L3 PROFILE in remote #SNPA ENTRY #L3 PROFILE in local #APPL ENTRY #L3 PROFILE in local #NSAP ENTRY #L3 PROFILE in local #SNPA ENTRY Local #L3 SERVICE After obtaining the appropriate protocol-related attributes, the OSI manager passes these values to the TAPS and TSP processes.
Commands and Responses ADD ENTRY Command Multiple sets of TAPS, TSP, and NSP processes or profiles can be assigned to one OSI address. To do this, configure multiple #APPL entries for the same OSI address and assign different servers and/or profiles as desired to each #APPL entry. The following example shows the two applications (LWAN1 and LWAN2) sharing the same OSI address (NSAP, TSEL, SSEL, and PSEL) but using different TAPS, TSP, and NSP processes. ADD ENTRY #APPL.
Commands and Responses ADD PROCESS Command ADD PROCESS Command The ADD PROCESS command adds the specified PROCESS object, with its associated attributes, to the OSI/AS subsystem. You can use this command to add a TAPS, TSP, or NSP process. This is a sensitive command. Command ZCOM-CMD-ADD Object Type ZCOM-OBJ-PROCESS Tokens in Command Buffer ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZOSI-MAP-ADD-PROC def ZOSI-DDL-ADD-PROC.
Commands and Responses ADD 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 OSI manager process to which SCP is to send this command. This token is optional and can occur only once in the command. ZCOM-TKN-OBJNAME is the indirect-process-name of the TAPS, TSP, or NSP process to be added. This token is required and can occur only once.
Commands and Responses ADD PROCESS Command ZPRIM-CPU is the number of the CPU in which the primary process (of the new process pair) will run. The range of values is 0 through 15. The default value is the number of the CPU in which the primary OSI manager process is running. ZBKUP-CPU is the number of the CPU in which the backup process (of the new process pair) will run. The range of values is 0 through 15. The default value is the number of the CPU in which the backup OSI manager process is running.
Commands and Responses ADD PROCESS Command ZSPI-VAL-TRUE indicates that the process will be started with a high PIN. The default value is ZSPI-VAL-TRUE. This attribute is valid only for Guardian 90 D series systems. ZXNAME specifies a TAPS, TSP, or NSP Guardian 90 process name of the server. This attribute is for D series systems only. The equivalent token for C series systems is ZNAME. It is used to run a process or to try to establish communication with a process that is already running.
Commands and Responses ADD PROCESS Command Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list. These tokens enclose the other response tokens only if the value of the header token ZSPI-TKN-MAXRESP is nonzero. Because only one object-name token is allowed in the command, no more than one data list can appear in the response.
Commands and Responses ADD PROFILE Command ADD PROFILE Command The ADD PROFILE command creates the specified PROFILE object, defines its attributes, and adds it to the OSI/AS subsystem. You can use this command to add a Layer 3, Layer 4, or Layer 5 PROFILE. This is a sensitive command. Command ZCOM-CMD-ADD Object Type ZCOM-OBJ-PROFILE Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME ZOSI-MAP-ADD-PROF-L3 def ZOSI-DDL-ADD-PROF-L3.
Commands and Responses ADD PROFILE Command Tokens in Command Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 end. ZL4-WIN ZNETTYPE ZCLASS ZALT-CLASS ZTPDU-SIZE ZXSUM ZEXT-FRMT ZMULTIPLEX ZREXMIT-TIMEOUT ZREF-TIMEOUT ZMAX-REXMIT ZINACTV-TIMEOUT ZWIN-TIMEOUT ZTTR-TIMEOUT ZTWR-TIMEOUT ZCONN-TIMEOUT ZDISCONN-TIMEOUT ZEXPEDITED ZOSI-MAP-ADD-PROF-L5 def ZOSI-DDL-ADD-PROF-L5. 02 ZDISCONN-TIMER 02 ZVSN1 02 ZVSN2 end.
Commands and Responses ADD PROFILE 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 OSI manager process to which SCP is to send this command. This token is optional and can occur only once in the command. ZCOM-TKN-OBJNAME is the name of the PROFILE to be added. This token is required and can occur only once.
Commands and Responses ADD PROFILE Command ZX25NEGOT-L3-WIN, ZX25NEGOT-PKTSIZE, and ZX25NEGOT-THRUPUT (in X.25 networks) specify the action to be taken when a call request containing an unacceptable value for one of these attributes is received. If an attribute has been defined as negotiable (its value set to ZSPI-VAL-TRUE) and an unacceptable value is received, then a call-accept packet containing an acceptable value is sent to the network.
Commands and Responses ADD PROFILE Command ZOSI-VAL-X25-NETID-DDXP Remote network is DDXP. ZOSI-VAL-X25-NETID-X25NP No port number to be used. ZOSI-VAL-X25-NETID-X25UD Port number is in user data field. ZOSI-VAL-X25-NETID-X25XA Extended address format is used. ZOSI-VAL-X25-NETID-X25SA Subaddress is used. The default for the ZX25REMOTENET field is the NETID value from the appropriate X.25 line. ZX25THRUPUT specifies the throughput class limit for X.25 networks.
Commands and Responses ADD PROFILE Command ZX25CUG-TYPE specifies the type of closed user group (CUG) facility. This attribute is used only for X.25 networks.
Commands and Responses ADD PROFILE Command ZOSI-MAP-ADD-PROF-L4 is an extensible structured token that contains attributes of the Layer 4 PROFILE being added. ZOSI-DDL-ADD-PROF-L4 contains the following fields: ZSEND-SECUR contains a user-defined password that is included in connect request transport protocol data units (CR-TPDUs) and connect confirm transport protocol data units (CC-TPDUs). This field applies only to class 1, 2, 3, or 4 communication.
Commands and Responses ADD PROFILE Command ZNETTYPE is the quality of network service. The default value is ZOSI-VAL-NETTYPEA. The values for this field are as follows: ZOSI-VAL-NETTYPE-A The network connection has an acceptable residual error rate, not signaled by disconnects or resets, and has an acceptable rate of signaled errors. ZOSI-VAL-NETTYPE-B The network connection has an acceptable residual error rate, not signaled by disconnects or resets, but has an unacceptable rate of signaled errors.
Commands and Responses ADD PROFILE Command ZALT-CLASS is the alternative protocol class to be used if the class specified in ZCLASS is not supported by the remote system. If ZCLASS has the value ZOSI-VAL-CLASS-0, then ZALT-CLASS is not applicable. The values for this field are the same as for ZCLASS.
Commands and Responses ADD PROFILE Command attempted; if it is set to ZSPI-VAL-FALSE, multiplexing is not attempted. The default value is ZSPI-VAL-FALSE. Multiplexing requires that two or more transport connections have the same local and remote NSAP addresses; have ZCLASS set to 2, 3, or 4; and have ZMULTIPLEX set to ZSPI-VAL-TRUE. If these conditions are met, the maximum number of outgoing transport connections that can be multiplexed is determined by the Layer 3 SERVICE attribute ZX25NCON-MULTIPLEX.
Commands and Responses ADD PROFILE Command reassignment is attempted when the network connection has failed. Request for reassignment is indicated by a nonzero value in the CR-TPDU. No reassignment attempt is made if the CR-TPDU contains a value of 0.) This field applies only to protocol class 1 or 3 communication. The waiting time is expressed in hundredths of a second (0.01 seconds per increment). The values range from 0 (0 seconds) through 18000 (180 seconds). The default value is 9000 (90 seconds).
Commands and Responses ADD PROFILE Command ZOSI-MAP-ADD-PROF-L5 is an extensible structured token that contains attributes of the Layer 5 PROFILE being added. ZOSI-DDL-ADD-PROF-L5 contains the following fields: ZDISCONN-TIMER is the maximum amount of time the session service provider should wait for a transport-disconnect indication after issuing a session release or abort service request.
Commands and Responses ADD PROFILE Command Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list. These tokens enclose the other response tokens only if the value of the header token ZSPI-TKN-MAXRESP is nonzero. Because only one object-name token is allowed in the command, no more than one data list can appear in the response.
Commands and Responses ALLOWOPENS PROCESS Command ALLOWOPENS PROCESS Command The ALLOWOPENS command cancels the effect of the FORBIDOPENS command. ALLOWOPENS allows data communications applications to open one or more specified processes. This is a sensitive command.
Commands and Responses ALLOWOPENS PROCESS Command OSI manager process, ZCOM-TKN-OBJNAME can occur only once, and it must be the name of that TAPS process. If you are sending the command to the OSI manager process, ZCOM-TKN-OBJNAME can occur multiple times. The processname format depends on the type of process, as follows: If the object is the OSI manager process, use process-name. If the object is a TAPS process, use indirect-process-name.
Commands and Responses ALTER ENTRY Command ALTER ENTRY Command The ALTER ENTRY command changes the values of one or more attributes of the specified ENTRY object. An ENTRY object must be known to the OSI/AS subsystem (that is, it must have been added with an ADD command) before it can be altered. ALTER ENTRY is a sensitive command. Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-ENTRY Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-XMGR ZCOM-TKN-OBJNAME token-type ZSPI-TYP-FNAME32.
Commands and Responses ALTER ENTRY Command Tokens in Command Buffer (continued) 02 02 02 03 end. ZSNPA-LEN ZSNPA ZNETADDR-MODE ZL3-PROF type type type type ZSPI-DDL-INT. ZOSI-DDL-SNPA. ZSPI-DDL-ENUM. ZSPI-DDL-FNAME32. ZOSI-MAP-ALTER-ENTRY-SNPA def ZOSI-DDL-ALTER-ENTRY-SNPA. 02 ZL3-SERVR type ZSPI-DDL-FNAME32. 02 ZL3-PROF type ZSPI-DDL-FNAME32. end. ZOSI-MAP-ALTER-ENTRY-TSEL def ZOSI-DDL-ALTER-ENTRY-TSEL. 02 ZL5-SERVR type ZSPI-DDL-FNAME32. 02 ZL5-PROF type ZSPI-DDL-FNAME32.
Commands and Responses ALTER ENTRY Command ZCOM-TKN-OBJNAME is the name of the ENTRY to be altered. This token is required and can occur only once.
Commands and Responses ALTER ENTRY Command ZTSEL is the TSEL address for the application being altered. The TSEL address is a binary-encoded string of an even number of hexadecimal digits. TSEL addresses are administered locally. ZSSEL-LEN is the length (in bytes) of the SSEL address in ZSSEL. The range of values is 0 through 16 bytes. ZSSEL is the SSEL address for the application being altered. The SSEL address is a binary-encoded string of an even number of hexadecimal digits.
Commands and Responses ALTER ENTRY Command ZL5-PROF is the name of the Layer 5 PROFILE to be used. It has precedence over the L3 profile configured with the #TSEL entry. ZL3-SERVR is the indirect-process-name of the NSP process. ZL4-SERVR is the indirect-process-name of the TSP process. ZL5-SERVR is the indirect-process-name of the TAPS process. ZDEL-TIME indicates whether or not an SU created from this application entry will be deleted or saved after the connection is completed.
Commands and Responses ALTER ENTRY Command ZOSI-MAP-ALTER-ENTRY-NSAP is an extensible structured token that contains the attributes for the specified NSAP. ZOSI-DDL-ALTER-ENTRY-NSAP contains the following fields: ZL4-SERVR is the indirect-process-name of the TSP process that services the NSAP being altered. ZL4-PROF is the name of the Layer 4 PROFILE to be used when a TSP subdevice is configured for communication through the NSAP being altered. ZSNPA-LEN is the length (in bytes) of the SNPA in ZSNPA.
Commands and Responses ALTER ENTRY Command ZL3-PROF is the name of the Layer 3 PROFILE to be used when a TSP subdevice is configured for communication through the SNPA being altered. ZOSI-MAP-ALTER-ENTRY-TSEL is an extensible structured token that contains the attributes for the specified TSEL ENTRY. ZOSI-DDL-ALTER-ENTRY-TSEL contains the following fields: ZL5-SERVR is the indirect-process-name of the TAPS process that services the TSEL being altered.
Commands and Responses ALTER ENTRY Command Operational Note Before issuing the ALTER ENTRY command, you must call SSNULL to initialize the appropriate extensible structure, and then set at least one of the fields in the structure to a non-null value.
Commands and Responses ALTER PROCESS Command ALTER PROCESS Command The ALTER PROCESS command changes the values of one or more attributes of an existing PROCESS object. You can use this command to alter the attributes of the NSP, TSP, and TAPS processes. A PROCESS object must be known to the OSI/AS subsystem (that is, it must have been added with an ADD command) before it can be altered. This is a sensitive command.
Commands and Responses ALTER PROCESS Command Tokens in Response Buffer ZSPI-TKN-DATALIST ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . . ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-SSCTL.
Commands and Responses ALTER PROCESS Command $TSP10 $TSP20 $TSP30 TSP processes on D-series systems that communicate with applications on remote C-series systems can have names up to 5 characters (the $ sign followed by 4 characters). For example: $TSP1 $TSP2 ZPRIM-CPU is the number of the CPU in which the primary process (of the process pair) is to run. The range of values is 0 through 15. ZBKUP-CPU is the number of the CPU in which the backup process (of the process pair) is to run.
Commands and Responses ALTER PROCESS Command ZHIGH-PIN This field determines whether the process indicated will be started by the specified OSI manager process with a high PIN or a low PIN. The possible values are: ZSPI-VAL-TRUE ZSPI-VAL-FALSE ZSPI-VAL-TRUE indicates that the process will be started with a high PIN. The default value is ZSPI-VAL-TRUE. This attribute is valid only for Guardian 90 D series systems. ZXNAME specifies a TAPS, TSP, or NSP Guardian 90 D-series system process name of the server.
Commands and Responses ALTER PROCESS Command ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list. These tokens enclose the other response tokens only if the value of the header token ZSPI-TKN-MAXRESP is nonzero.
Commands and Responses ALTER PROFILE Command ALTER PROFILE Command The ALTER PROFILE command changes the values of one or more attributes of the specified PROFILE. You can use this command to alter a Layer 3, Layer 4, or Layer 5 PROFILE. A PROFILE object must be known to the OSI/AS subsystem (that is, it must have been added with an ADD command) before it can be altered. This is a sensitive command.
Commands and Responses ALTER PROFILE Command Tokens in Command Buffer (continued) ZOSI-MAP-ALTER-PROF-L4 def ZOSI-DDL-ALTER-PROF-L4. 02 ZSEND-SECUR 02 ZRECV-SECUR 02 ZTCON-PRI 02 ZL4-WIN 02 ZNETTYPE 02 ZCLASS 02 ZALT-CLASS 02 ZTPDU-SIZE 02 ZXSUM 02 ZEXT-FRMT 02 ZMULTIPLEX 02 ZREXMIT-TIMEOUT 02 ZREF-TIMEOUT 02 ZMAX-REXMIT 02 ZINACTV-TIMEOUT 02 ZWIN-TIMEOUT 02 ZTTR-TIMEOUT 02 ZTWR-TIMEOUT 02 ZCONN-TIMEOUT 02 ZDISCONN-TIMEOUT 02 ZEXPEDITED end. ZOSI-MAP-ALTER-PROF-L5 def ZOSI-DDL-ALTER-PROF-L5.
Commands and Responses ALTER PROFILE Command Tokens in Response Buffer ZSPI-TKN-DATALIST ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . . ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-SSCTL.
Commands and Responses ALTER PROFILE Command CUG ID of the associated X25AM line. To clear a previously specified CUG ID, assign the value ZOSI-VAL-CUG-RESET to this field. ZX25DESTADDR is the network address to be used by the subdevice as the called address in outgoing call-request packets in X.25 networks. The network address is a string of up to 15 decimal digits (0 through 9).
Commands and Responses ALTER PROFILE Command ZX25REMOTENET specifies the addressing convention you want used when building the called address in the call-request packet. The values for this field are as follows: ZOSI-VAL-X25-NETID-VANILLA Remote network is ISO 8208. ZOSI-VAL-X25-NETID-DATAPAC Remote network is DATAPAC. ZOSI-VAL-X25-NETID-TELENET Remote network is TELENET. ZOSI-VAL-X25-NETID-TRANSPAC Remote network is TRANSPAC. ZOSI-VAL-X25-NETID-TYMNET Remote network is TYMNET.
Commands and Responses ALTER PROFILE Command ZIP-X25-SNDCF controls the the subnetwork dependent convergence facility (SNDCF). This parameter is meaningful only if the Transport Layer protocol uses the OSI internet protocol (IP) to communicate, via the SNDCF, with an X.25 network. If this field is set to ZSPI-VAL-TRUE, the SNDCF is enabled; if it is set to ZSPIVAL-FALSE, the SNDCF is disabled. See “Operational Notes” for further information.
Commands and Responses ALTER PROFILE Command ZX25TRANSIT-DELAY specifies 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). To clear a previously specified TRANSIT-DELAY, assign the value ZOSI-VAL-TRANSIT-DELAYRESET. ZOSI-MAP-ALTER-PROF-L4 is an extensible structured token that contains attributes of the Layer 4 PROFILE being altered.
Commands and Responses ALTER PROFILE Command entity without waiting for an acknowledgment (in other words, it specifies the initial credit allocation used by the remote transport entity). The range of values for ZL4-WIN is 0 through 15. ZL4-WIN is not applicable for class 0. ZNETTYPE is the quality of network service.
Commands and Responses ALTER PROFILE Command ZALT-CLASS is the alternative protocol class to be used if the class specified in ZCLASS is not supported by the remote system. If ZCLASS has the value ZOSI-VALCLASS-0, then ZALT-CLASS is not applicable. The values for this field are the same as for ZCLASS.
Commands and Responses ALTER PROFILE Command maximum number of outgoing transport connections that can be multiplexed is determined by the Layer 3 SERVICE attribute ZX25NCON-MULTIPLEX. ZREXMIT-TIMEOUT is the maximum amount of time that the transport entity should wait for an acknowledgment before resending the TPDU. This field applies only to protocol class 4 communication. The waiting time is expressed in hundredths of a second (0.01 seconds per increment).
Commands and Responses ALTER PROFILE Command ZTWR-TIMEOUT is the maximum amount of time that the responding transport entity should wait for reassignments to be completed before releasing the connection. (A reassignment is attempted when the network connection has failed. Request for reassignment is indicated by a nonzero value in the CR-TPDU. No reassignment attempt is made if the CR-TPDU contains a value of 0.) This field applies only to protocol class 1 or 3 communication.
Commands and Responses ALTER PROFILE Command ZVSN1 specifies whether the application using this PROFILE can operate over a session protocol version 1 connection. If this field is set to ZSPI-VAL-TRUE, the application can operate over protocol version 1; if it is set to ZSPI-VALFALSE, the application cannot operate over protocol version 1. At least one of the two protocol version fields (ZVSN1 and ZVSN2) must be set to ZSPI-VALTRUE.
Commands and Responses ALTER PROFILE Command Operational Notes Before issuing the ALTER PROFILE command, you must call SSNULL to initialize the appropriate extensible structure, and then set at least one of the fields in the structure to a non-null value.
Commands and Responses ALTER SERVICE Command ALTER SERVICE Command The ALTER SERVICE command changes the values of one or more attributes of the specified 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. ZOSI-MAP-ALTER-SERV-L3 def ZOSI-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 02 02 02 02 end.
Commands and Responses ALTER SERVICE Command Tokens in Command Buffer (continued) 02 ZOUTBOUND-CR-CONF-ERR-THLD type 02 ZINBOUND-CR-PROTO-ERR-THLD type 02 ZOUTBOUND-CR-ERR-THLD type 02 ZINBOUND-TPDU-PROTO-ERR-THLD type ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZOSI-MAP-ALTER-SERV-L6 def ZOSI-DDL-ALTER-SERV-L6. 02 ZCPRPPDURECVTRANSIENTGROUPTHLD type ZSPI-DDL-INT2. 02 ZCPRPPDURECVPERMANENTGROUPTHLD type ZSPI-DDL-INT2. 02 ZCPRPPDUSENTPERMANENTGROUPTHLD type ZSPI-DDL-INT2.
Commands and Responses ALTER SERVICE Command Tokens in Response Buffer ZSPI-TKN-DATALIST ZCOM-TKN-OBJTYPE ZCOM-TKN-OBJNAME ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . . ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ENUM. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-SSCTL.
Commands and Responses ALTER SERVICE Command ZX25CUG is the optional closed user group identifier (CUG ID) that is sent in call-request packets in X.25 networks. The range of values is 0 through 9999. The default value is null (that is, no CUG ID specified), which directs X25AM to send the CUG ID of the associated X25AM line. To clear a previously specified CUG ID, assign the value ZOSI-VAL-CUG-RESET to this field.
Commands and Responses ALTER SERVICE Command ZX25REMOTENET specifies the addressing convention you want used when building the called address in the call-request packet. The values for this field are as follows: ZOSI-VAL-X25-NETID-VANILLA Remote network is ISO 8208. ZOSI-VAL-X25-NETID-DATAPAC Remote network is DATAPAC. ZOSI-VAL-X25-NETID-TELENET Remote network is TELENET. ZOSI-VAL-X25-NETID-TRANSPAC Remote network is TRANSPAC. ZOSI-VAL-X25-NETID-TYMNET Remote network is TYMNET.
Commands and Responses ALTER SERVICE Command full subset of the IP is enabled. The value initially set by the OSI manager is ZSPI-VAL-FALSE. See “Operational Notes” for further information. ZIP-X25-SNDCF controls the the subnetwork dependent convergence facility (SNDCF). This parameter is meaningful only if the Transport Layer protocol uses the OSI internet protocol (IP) to communicate, via the SNDCF, with an X.25 network.
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 ZESISNOTIFY-IS is set to ZSPI-VAL-TRUE, the configuration is reported; if it is set to ZSPI-VAL-FALSE, the configuration is not reported. The value initially set by the OSI manager is ZSPI-VAL-FALSE.
Commands and Responses ALTER SERVICE Command ZSPI-VAL-FALSE, a checksum is not included. The value initially set by the OSI manager is ZSPI-VAL-FALSE. ZIP-DISCARD-GEN-THLD is the threshold value that the IP entity compares to the OSI/TS Layer 3 counter ZIP-DISCARD-GEN. This counter records the number of times the IP entity discards a protocol data unit (PDU) for some reason other than congestion, unrecognized address, expiration of lifetime, unsupported protocol version or option, or failure in reassembly.
Commands and Responses ALTER SERVICE Command messages are never generated for this counter. The value initially set by the OSI manager is 0. ZIP-DISCARD-UNSUP-THLD is the threshold value that the IP entity compares to the OSI/TS Layer 3 counter ZIP-DISCARD-UNSUP. This counter records the number of times the IP entity discards a PDU because of an unsupported protocol version or option.
Commands and Responses ALTER SERVICE Command ZX25CUG-TYPE specifies the type of closed user group (CUG) facility. This attribute is used only for X.25 networks.
Commands and Responses ALTER SERVICE Command 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). The default is 6000 (60 seconds) The value initially set by the OSI manager is null. ZIPX25-SNDCF-1980-ADDR specifies whether 1980 addressing will be used when using SNDCF.
Commands and Responses ALTER SERVICE Command reached among the implementors concerning this attribute, Tandem OSI does not currently process this field. ZL4-WIN has different meanings depending on the transport class of service. If the negotiated transport service protocol class is class 1, this field specifies the number of data transport protocol data units (DT-TPDUs) that can be received before an acknowledgment is required.
Commands and Responses ALTER SERVICE Command ZCLASS is the preferred transport protocol class to be used. The values for this field are as follows: ZOSI-VAL-CLASS-0 ZOSI-VAL-CLASS-1 ZOSI-VAL-CLASS-2 ZOSI-VAL-CLASS-3 ZOSI-VAL-CLASS-4 For LAN networks, and for X.25 networks when the Layer 3 attribute ZIP-X25SNDCF is set to ZSPI-VAL-TRUE, ZCLASS must be ZOSI-VAL-CLASS-4.
Commands and Responses ALTER SERVICE Command For X.25 subnetworks: OSI/TS will adjust the value of ZTPDU-SIZE to not exceed the value of the X25AM SYSGEN attribute MAXIOSIZE. The value initially set by the OSI manager is 512 bytes. ZXSUM specifies whether the checksum field is added to each TPDU. This field applies only to protocol class 4 communication. If this field is set to ZSPI-VAL-TRUE, the checksum field is added; if it is set to ZSPI-VAL-FALSE, the checksum is not added.
Commands and Responses ALTER SERVICE Command ZMAX-REXMIT is the maximum number of times unacknowledged TPDUs are retransmitted before the connection is terminated. This field applies only to protocol class 4 communication. The values range from 1 through 8. The value initially set by the OSI manager is 3. ZINACTV-TIMEOUT is the maximum amount of time that the transport entity should wait without receiving any TPDUs before terminating the connection.
Commands and Responses ALTER SERVICE Command ZCONN-TIMEOUT is the maximum amount of time that the transport entity should wait for a response to a CR-TPDU before releasing the connection. The waiting time is expressed in hundredths of a second (0.01 seconds per increment). The values range from 300 (3 seconds) through 18000 (180 seconds). The value initially set by the OSI manager is 12000 (120 seconds).
Commands and Responses ALTER SERVICE Command ZOUTBOUND-CR-CONF-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZOUTBOUND-CR-CONF-ERR. This counter records the number of times the Transport Layer receives a disconnect request transport protocol data unit (DR-TPDU) refusing a connect request because of negotiation failure, duplicate source reference, mismatched references, reference overflow, network connection refused, session entity not attached to TSAP, or address unknown.
Commands and Responses ALTER SERVICE Command never generated for this counter. The value initially set by the OSI manager is 0. ZOUTBOUND-TPDU-PROTO-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZOUTBOUND-TPDU-PROTO-ERR. This counter records the number of times the Transport Layer receives a DR-TPDU or an error transport protocol data unit (ER-TPDU) as the response to any TPDU it initiated (other than the CRTPDU).
Commands and Responses ALTER SERVICE Command ZPASV-MUX specifies indicates the sharing of X25AM SUs for attaching TSP SUs in anticipation of multiplexing performed by the remote transport entity.The possible values are: ZSPI-VAL-TRUE ZSPI-VAL-FALSE The default value is ZSPI-VAL-FALSE. If this attribute and the ZMULTIPLEX attribute are set (ZSPI-VAL-TRUE), the TSP process will assume that the remote transport entity will multiplex all transport connections destined to the same X.25 port (same DTE address).
Commands and Responses ALTER SERVICE Command TRUE. The value initially set by the OSI manager for ZVSN2 is ZSPI-VALFALSE. The version is negotiated between the session entities at each end of the connection. If an application using OSI/AS initiates the connection, OSI/AS will propose either or both versions, depending on the settings of ZVSN1 and ZVSN2.
Commands and Responses ALTER SERVICE Command ZOSI-MAP-ALTER-SERV-L6 is an extensible structured token that contains the attributes of the Layer 6 SERVICE being altered. ZOSI-DDL-ALTER-SERV-L6 contains the following fields: ZCPRPPDURECVTRANSIENTGROUPTHLD is the threshold value that the Presentation Layer compares to the Layer 6 counter ZCPRPPDURECVTRANSIENTGROUP, described under the STATISTICS SERVICE command.
Commands and Responses ALTER SERVICE Command ZOSI-MAP-ALTER-SERV-ACSE is an extensible structured token that contains the attributes of the ACSE SERVICE being altered. ZOSI-DDL-ALTER-SERV-ACSE contains the following fields: ZACPMREJECTSRECVTHLD is the threshold value that ACSE compares to the counter ZACPMREJECTSRECV, described under the STATISTICS SERVICE command.
Commands and Responses ALTER SERVICE Command 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, ACSE-THLD event messages are never generated for this counter. The value initially set by the OSI manager is 0. ZACPMASSOCPREJECTSTHLD is the threshold value that ACSE compares to the counter ZACPMASSOCPREJECTS, described under the STATISTICS SERVICE command.
Commands and Responses ALTER SERVICE Command You can alter attributes of the L5, L6, and ACSE SERVICE objects only through the OSI manager process. The following conditions, based on settings of fields in the Layer 3 SERVICE and PROFILE tokens, determine whether the full subset of the OSI internet protocol (IP) is enabled: For X25AM lines, the full subset of the IP is enabled if ZIP-X25-SNDCF is set to ZSPI-VAL-TRUE; it is disabled if ZIP-X25-SNDCF is set to ZSPI-VALFALSE.
Commands and Responses ALTER SUBSYS Command ALTER SUBSYS Command The ALTER SUBSYS command changes the values of one or more attributes of the specified SUBSYS object. Only one OSI/AS subsystem can be altered in each ALTER SUBSYS command. This is a sensitive command. Command ZCOM-CMD-ALTER Object Type ZCOM-OBJ-SUBSYS 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.
Commands and Responses ALTER SUBSYS 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 OSI manager process to which SCP is to send this command. This token is optional and can occur only once in the command. ZCOM-TKN-OBJNAME is the name of the subsystem to be altered.
Commands and Responses ALTER SUBSYS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses DELETE ENTRY Command DELETE ENTRY Command The DELETE ENTRY command removes one or more ENTRY objects from the OSI/AS subsystem. It is a sensitive command. Command ZCOM-CMD-DELETE Object Type ZCOM-OBJ-ENTRY 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 ENTRY Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses DELETE PROCESS Command DELETE PROCESS Command The DELETE PROCESS command removes one or more PROCESS objects from the OSI/AS subsystem. It is a sensitive command.
Commands and Responses DELETE PROCESS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses DELETE PROFILE Command DELETE PROFILE Command The DELETE PROFILE command removes one or more PROFILE objects from the OSI/AS subsystem. It is a sensitive command.
Commands and Responses DELETE PROFILE Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses FORBIDOPENS PROCESS Command FORBIDOPENS PROCESS Command FORBIDOPENS prohibits data communications applications from opening one or more specified processes. This command does not affect current opens, and it does not prohibit management programming (#ZSPI) opens. The FORBIDOPENS command cancels the effect of the ALLOWOPENS command. It is a sensitive command.
Commands and Responses FORBIDOPENS PROCESS Command name). If you are sending the command directly to a TAPS process, bypassing the OSI manager process, ZCOM-TKN-OBJNAME can occur only once, and it must be the name of that TAPS process. If you are sending the command to the OSI manager process, ZCOM-TKN-OBJNAME can occur multiple times. The processname format depends on the type of process, as follows: If the object is the OSI manager process, use process-name.
Commands and Responses GETVERSION NULL Command GETVERSION NULL Command The GETVERSION NULL command returns a product version banner identifying the version level of the specified process.
Commands and Responses GETVERSION PROCESS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
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. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses GETVERSION SUBSYS Command GETVERSION SUBSYS Command The GETVERSION SUBSYS command returns a product version banner identifying the version level of the OSI manager process for the specified subsystem.
Commands and Responses GETVERSION SUBSYS Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, and ZSPI-TKNCOMMENT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses INFO ENTRY Command INFO ENTRY Command The INFO ENTRY command returns the current values of the attributes for the specified ENTRY object. The response contains the configuration information established when the ENTRY was created with an ADD command or was last modified with an ALTER command.
Commands and Responses INFO ENTRY Command Tokens in Response Buffer (continued) 02 ZL4-SERVR type 02 ZL5-SERVR type 02 ZDEL-TIME type 02 ZLOOPBACK type ZOSI-MAP-INFO-ENTRY-NSAP def ZOSI-DDL-INFO-ENTRY-NSAP. 02 ZL4-SERVR type 02 ZL4-PROF type 02 ZSNPA-LEN type 02 ZSNPA type 02 ZNETADDR-MODE type 02 ZL3-PROF type end. ZSPI-DDL-FNAME32. ZSPI-DDL-FNAME32. ZSPI-DDL-INT2. ZSPI-DDL-BOOLEAN. ZSPI-DDL-FNAME32. ZSPI-DDL-FNAME32. ZSPI-DDL-INT. ZOSI-DDL-SNPA. ZSPI-DDL-ENUM. ZSPI-DDL-FNAME32.
Commands and Responses INFO ENTRY Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses INFO ENTRY Command ZNSAP is the NSAP address for the application . For LAN networks , the NSAP address must be an even number of hexadecimal digits. For X.25 networks, the NSAP address can be an even or odd number of hexadecimal digits. If you supply an odd length NSAP value, the field is padded internally to make an even number of bytes. For example, if your NSAP address is “ABC,” you would enter ”ABC,” internally the number is represented as “ABC0.
Commands and Responses INFO ENTRY Command ZNSAP-NIBBLE is the length of the NSAP address specified in ZNSAP-LEN. The range of values is 0 through 40 nibbles. You must use this field when using odd length NSAPs. For example, if the NSAP address is “ABC”. The ZNSAP value would be “ABC0”. The NSAP-LEN field would be “2” and the NSAP-NIBBLE field would be “3.” ZL3-PROF is the L3 profile that was specified when the #APPL entry name was configured.
Commands and Responses INFO ENTRY Command ZOSI-MAP-INFO-ENTRY-NSAP is an extensible structured token that contains the current attributes for the specified NSAP. ZOSI-DDL-INFO-ENTRY-NSAP contains the following fields: ZL4-SERVR is the indirect-process-name of the TSP process that services the specified NSAP. ZL4-PROF is the name of the Layer 4 PROFILE used when a TSP subdevice is configured for communication to or from the specified NSAP. ZSNPA-LEN is the length (in bytes) of the SNPA in ZSNPA.
Commands and Responses INFO ENTRY Command ZOSI-MAP-INFO-ENTRY-TSEL is an extensible structured token that contains the current attributes for the specified TSEL ENTRY. ZOSI-DDL-INFO-ENTRY-TSEL contains the following fields: ZL5-SERVR is the indirect-process-name of the TAPS process that services the specified TSEL. ZL5-PROF is the name of the Layer 5 PROFILE associated with the specified TSEL. ZL4-PROF is the name of the Layer 4 PROFILE associated with the the specified TSEL.
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 configuration information established when the PROCESS object was added with an ADD command 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 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 INFO PROCESS Command ZCOM-TKN-OBJTYPE and ZCOM-TKN-OBJNAME are described in the Communications Management Programming Manual. ZOSI-MAP-INFO-PROC 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 ZOSI-MAP-INFO-PROC token is returned for each process. ZOSI-DDLINFO-PROC contains the following fields: ZNAME is the name of the process being queried.
Commands and Responses INFO PROCESS Command ZHIGH-PIN shows whether the process indicated will be started by the specified OSI manager process with a high PIN or a low PIN. If the process name was specified in processname format, this field shows the actual current value of the process. If the process name was specified in indirect-process-name format, this field shows how the process was or will be configured. ZXNAME is the name of the process being queried. This attribute is for D-series systems only.
Commands and Responses INFO PROFILE Command INFO PROFILE Command The INFO PROFILE command returns the current values of the attributes for the specified PROFILE. This command requests information on Layer 3, Layer 4, or Layer 5 PROFILEs. The response contains the configuration information established when the PROFILE was created with an ADD command or was last modified with an ALTER command.
Commands and Responses INFO PROFILE Command Tokens in Response Buffer (continued) 02 02 02 02 02 02 02 ZIP-NULL-LAYER ZIP-X25-SNDCF ZX25CUG-TYPE ZX25BCUG ZX25RPOA ZX25RPOA-DNIC-CNT ZX25TRANSIT-DELAY type type type type type type type ZSPI-DDL-BOOLEAN. ZSPI-DDL-BOOLEAN. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT2. type type type type type type type type type type type type type type type type type type type type type ZSPI-DDL-CHAR16. ZSPI-DDL-CHAR16. ZSPI-DDL-INT.
Commands and Responses INFO PROFILE 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 INFO PROFILE Command ZCOM-TKN-OBJTYPE and ZCOM-TKN-OBJNAME are described in the Communications Management Programming Manual.
Commands and Responses INFO PROFILE Command ZX25PRICALL used only for the DATAPAC network, controls the ability to make priority calls. If this field is set to ZSPI-VAL-TRUE, the priority call capability is enabled; if it is set to ZSPI-VAL-FALSE, the capability is disabled. For networks other than DATAPAC, this field is always ZSPI-VAL-FALSE. ZX25REVERSECHG controls, for X.25 networks, whether an outgoing call request asks that the recipient pay the charges.
Commands and Responses INFO PROFILE Command ZX25PVC is the channel number of the permanent virtual circuit (PVC) to which the specified X.25 subdevice is bound. The range of values is 1 through 4095 for all network types except TRANSPAC. The range of values for TRANSPAC networks is 0 through 4095. ZIP-NULL-LAYER controls the generation of the header for the inactive subset (the null Network Layer) of the OSI internet protocol (IP).
Commands and Responses INFO PROFILE Command ZX25RPOA-DNIC-CNT specifies the number of DNICs in the ZX25RPOA integer list. The value is an integer from 0 through 7. ZX25TRANSIT-DELAY specifies 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).
Commands and Responses INFO PROFILE Command entity without waiting for an acknowledgment (in other words, it specifies the initial credit allocation used by the remote transport entity). The range of values for ZL4-WIN is 0 through 15. ZL4-WIN is not applicable for class 0. ZNETTYPE is the quality of network service.
Commands and Responses INFO PROFILE Command ZALT-CLASS is the alternative protocol class to be used if the class specified in ZCLASS is not supported by the remote system. If ZCLASS has the value ZOSI-VALCLASS-0, then ZALT-CLASS is not applicable. The values for this field are the same as for ZCLASS.
Commands and Responses INFO PROFILE Command maximum number of outgoing transport connections that can be multiplexed is determined by the Layer 3 SERVICE attribute ZX25NCON-MULTIPLEX. ZREXMIT-TIMEOUT is the maximum amount of time that the transport entity should wait for an acknowledgment before resending the TPDU. This field applies only to protocol class 4 communication. The waiting time is expressed in hundredths of a second (0.01 seconds per increment).
Commands and Responses INFO PROFILE Command ZTWR-TIMEOUT is the maximum amount of time that the responding transport entity should wait for reassignments to be completed before releasing the connection. (A reassignment is attempted when the network connection has failed. Request for reassignment is indicated by a nonzero value in the CR-TPDU. No reassignment attempt is made if the CR-TPDU contains a value of 0.) This field applies only to protocol class 1 or 3 communication.
Commands and Responses INFO PROFILE Command ZVSN1 specifies whether the application using this PROFILE can operate over a session protocol version 1 connection. If this field is set to ZSPI-VAL-TRUE, the application can operate over protocol version 1; if it is set to ZSPI-VALFALSE, the application cannot operate over protocol version 1. ZVSN2 specifies whether the application using this PROFILE can operate over a session protocol version 2 connection.
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, Layer 4, Layer 5, Layer 6, or ACSE SERVICE. The response contains the configuration information established when the SERVICE object was created initially by OSI/AS or was last modified with an ALTER command.
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 02 02 02 02 02 02 02 02 02 02 02 02 02 ZX25THRUPUT type ZX25PVC type ZIP-NULL-LAYER type ZIP-X25-SNDCF type ZESIS-ENABLE type ZESIS-ES-CONF-TIME type ZESIS-ES-GROUP-MAC-ADDR type ZESIS-IS-GROUP-MAC-ADDR type ZESIS-NOTIFY-IS type ZESIS-XSUM type ZESIS-QUERY-TIME type ZESIS-QUERY-RETRY type ZIP-LIFETIME type ZIP-XSUM type ZIP-DISCARD-GEN-THLD type ZIP-DISCARD-CONG-THLD type ZIP-D
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 02 02 02 ZL4-WIN ZNETTYPE ZCLASS ZALT-CLASS ZTPDU-SIZE ZXSUM ZEXT-FRMT ZMULTIPLEX ZREXMIT-TIMEOUT ZREF-TIMEOUT ZMAX-REXMIT ZINACTV-TIMEOUT ZWIN-TIMEOUT ZTTR-TIMEOUT ZTWR-TIMEOUT ZCONN-TIMEOUT ZDISCONN-TIMEOUT ZEXPEDITED ZINBOUND-CR-CONG-THLD type type type type type type type type type type type type type type type type type type ZSPI-DDL-INT. ZSPI-DDL-ENUM. ZSPI-DDL-ENUM.
Commands and Responses INFO SERVICE Command Tokens in Response Buffer (continued) 02 ZVSN2 type ZSPI-DDL-BOOLEAN. 02 ZRFSPDURECVPERMANENTTHLD type ZSPI-DDL-INT2. 02 ZRFSPDUSENTPERMANENTTHLD type ZSPI-DDL-INT2. 02 ZRFSPDURECVTEMPORARYTHLD type ZSPI-DDL-INT2. 02 ZABSPDUSENTPROTERRORTHLD type ZSPI-DDL-INT2. end. ZOSI-MAP-INFO-SERV-L6 def ZOSI-DDL-INFO-SERV-L6. 02 ZCPRPPDURECVTRANSIENTGROUPTHLD type ZSPI-DDL-INT2. 02 ZCPRPPDURECVPERMANENTGROUPTHLD type ZSPI-DDL-INT2.
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 OSI manager or TAPS process to which SCP is to send this command. This token is optional and can occur only once in the command. ZCOM-TKN-OBJNAME is the name of the SERVICE for which you want information.
Commands and Responses INFO SERVICE Command ZOSI-MAP-INFO-SERV-L3 is an extensible structured token that contains the current attributes of the specified Layer 3 SERVICE. ZOSI-DDL-INFO-SERV-L3 contains the following fields: ZX25ACCEPTCHG controls whether the recipient pays the charge for incoming calls on X.25 networks, if requested by the incoming call request.
Commands and Responses INFO SERVICE Command call request asks the recipient to pay the charge; if it is set to ZSPI-VAL-FALSE, the recipient is not asked to pay the charge. ZX25REMOTENET specifies the addressing convention you want used when building the called address in the call-request packet. The values for this field are as follows: ZOSI-VAL-X25-NETID-VANILLA Remote network is ISO 8208. ZOSI-VAL-X25-NETID-DATAPAC Remote network is DATAPAC. ZOSI-VAL-X25-NETID-TELENET Remote network is TELENET.
Commands and Responses INFO SERVICE Command ZIP-X25-SNDCF controls the the subnetwork dependent convergence facility (SNDCF). This parameter is meaningful only if the Transport Layer protocol uses the OSI internet protocol (IP) to communicate, via the SNDCF, with an X.25 network. If this field is set to ZSPI-VAL-TRUE, the SNDCF is enabled; if it is set to ZSPIVAL-FALSE, the SNDCF is disabled. See “Operational Notes” for further information.
Commands and Responses INFO SERVICE Command set to ZSPI-VAL-TRUE. If ZESIS-XSUM is set to ZSPI-VAL-TRUE, a checksum is included; if it is set to ZSPI-VAL-FALSE, a checksum is not included. 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.
Commands and Responses INFO SERVICE Command ZIP-DISCARD-CONG-THLD is the threshold value that the IP entity compares to the OSI/TS Layer 3 counter ZIP-DISCARD-CONG. This counter records the number of times the IP entity discards a PDU because of congestion. OSI/TS generates a ZOS4EVT-L3-THLD event message 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 ZESIS-ENABLE is set to ZSPI-VAL-TRUE.
Commands and Responses INFO SERVICE Command a ZOS4-EVT-L3-THLD event message 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 ZESIS-ENABLE is set to ZSPI-VAL-TRUE. The values range from 0 through 65535. If the threshold is set to 0, L3-THLD event messages are never generated for this counter. ZX25DISCONN-DELAY is the amount of time the TSP process should wait on an idle (unused) X.
Commands and Responses INFO SERVICE Command 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 DNICs in the X25RPOA integer list. ZX25RPOA-DNIC-CNT specifies the number of DNICs in the ZX25RPOA integer list. The value is an integer from 0 through 7. ZX25TRANSIT-DELAY specifies the transit delay in the facility field of a call-request packet. This attribute is used only for X.25 networks.
Commands and Responses INFO SERVICE Command communication. Note that not all transport protocol implementations support this attribute. The field can contain any ASCII string of up to 16 characters. ZTCON-PRI specifies the Layer 4 connection priority to be used when transport connections are reassigned. However, because an agreement has not yet been reached among the implementors concerning this attribute, Tandem OSI does not currently process this field.
Commands and Responses INFO SERVICE Command For LAN networks, and for X.25 networks when the Layer 3 attribute ZIP-X25SNDCF is set to ZSPI-VAL-TRUE, ZCLASS is always ZOSI-VAL-CLASS-4. ZALT-CLASS is the alternative protocol class to be used if the class specified in ZCLASS is not supported by the remote system. If ZCLASS has the value ZOSI-VAL-CLASS-0, then ZALT-CLASS is not applicable. The values for this field are the same as for ZCLASS.
Commands and Responses INFO SERVICE Command ZREF-TIMEOUT is the maximum amount of time that the transport entity should wait before reusing any reference or sequence number. The waiting time is expressed in hundredths of a second (0.01 seconds per increment). The values range from 300 (3 seconds) through 18000 (180 seconds). ZMAX-REXMIT is the maximum number of times unacknowledged TPDUs are retransmitted before the connection is terminated. This field applies only to protocol class 4 communication.
Commands and Responses INFO SERVICE Command This field applies only to protocol class 1 or 3 communication. The waiting time is expressed in hundredths of a second (0.01 seconds per increment). The values range from 0 (0 seconds) through 18000 (180 seconds). ZCONN-TIMEOUT is the maximum amount of time that the transport entity should wait for a response to a CR-TPDU before releasing the connection. The waiting time is expressed in hundredths of a second (0.01 seconds per increment).
Commands and Responses INFO SERVICE Command ZOUTBOUND-CR-CONF-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZOUTBOUND-CR-CONF-ERR. This counter records the number of times the Transport Layer receives a disconnect request transport protocol data unit (DR-TPDU) refusing a connect request because of negotiation failure, duplicate source reference, mismatched references, reference overflow, network connection refused, session entity not attached to TSAP, or address unknown.
Commands and Responses INFO SERVICE Command ZOUTBOUND-TPDU-PROTO-ERR-THLD is the threshold value that the Transport Layer compares to the counter ZOUTBOUND-TPDU-PROTO-ERR. This counter records the number of times the Transport Layer receives a DR-TPDU or an error transport protocol data unit (ER-TPDU) as the response to any TPDU it initiated (other than the CRTPDU).
Commands and Responses INFO SERVICE Command ZDISCONN-TIMER is the maximum amount of time the session service provider should wait for a transport-disconnect indication after issuing a request for session release or abort service. If a transport-disconnect indication is not received within this time interval, the session service provider issues a transport-disconnect request. The waiting time is expressed in microseconds (0.000001 seconds per increment).
Commands and Responses INFO SERVICE Command the threshold is set to 0, L5-THLD event messages are never generated for this counter. ZRFSPDURECVTEMPORARYTHLD is the threshold value that the Session Layer compares to the Layer 5 counter ZRFSPDURECVTEMPORARY, described under the STATISTICS SERVICE command. OSI/AS generates a ZOSI-EVT-L5-THLD event message 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 ZCPRPPDUSENTPERMANENTGROUPTHLD is the threshold value that the Presentation Layer compares to the Layer 6 counter ZCPRPPDUSENTPERMANENTGROUP, described under the STATISTICS SERVICE command. OSI/AS generates a ZOSI-EVT-L6-THLD event message 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.
Commands and Responses INFO SERVICE Command command. OSI/AS generates a ZOSI-EVT-ACSE-THLD event message 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, ACSE-THLD event messages are never generated for this counter. ZACPMABORTSSENTTHLD is the threshold value that ACSE compares to the counter ZACPMABORTSSENT, described under the STATISTICS SERVICE command.
Commands and Responses INFO SERVICE Command If ZESIS-ENABLE is set to ZSPI-VAL-TRUE, the full subset of the IP is enabled and the ZIP-NULL LAYER field is ignored. If ZESIS-ENABLE is set to ZSPI-VAL-FALSE, the full subset of the IP is enabled if ZIP-NULL-LAYER is set to ZSPI-VAL-FALSE, and is disabled if ZIP-NULL-LAYER is set to ZSPI-VAL-TRUE. The ZIP-X25-SNDCF field is ignored for TLAM lines. ZIP-NULL-LAYER and ZX25-SNDCF can be set in the Layer 3 SERVICE and in individual Layer 3 PROFILEs.
Commands and Responses INFO SUBSYS Command INFO SUBSYS Command The INFO SUBSYS command returns the current values of the attributes for the specified subsystem. The response contains the configuration information established when the specified OSI/AS subsystem was started or was last modified with an ALTER command.
Commands and Responses INFO SUBSYS 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 OSI manager process to which SCP is to send this command. This token is optional and can occur only once in the command. ZCOM-TKN-OBJNAME is the name of the subsystem for which you want information.
Commands and Responses INFO SUBSYS Command ZMAX-TAPS is the maximum number of TAPS process pairs that can be configured. The range of values is 1 through 32767. ZMIB is the fully qualified Guardian 90 name of the file that contains the Management Information Base (MIB). ZTSP-CODEFILE is the fully qualified Guardian 90 name of the code file for a TSP process. ZTAPS-CODEFILE is the fully qualified Guardian 90 name of the code file for a TAPS process.
Commands and Responses LISTOBJECTS NULL Command LISTOBJECTS NULL Command The LISTOBJECTS NULL command returns a list of all object types and object names subordinate to the OSI manager or TAPS process to which the command is sent.
Commands and Responses LISTOBJECTS NULL Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses LISTOBJECTS ENTRY Command LISTOBJECTS ENTRY Command The LISTOBJECTS ENTRY command returns a list of all ENTRY objects in the subsystem that match the specified object-name token.
Commands and Responses LISTOBJECTS ENTRY Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses LISTOBJECTS PROCESS Command LISTOBJECTS PROCESS Command The LISTOBJECTS PROCESS command returns the name of one or more processes and/or the names of objects subordinate to those processes in the OSI/AS object hierarchy.
Commands and Responses LISTOBJECTS PROCESS Command name). If a process name is specified, its format depends on the type of process, as follows: If the object is the OSI manager process, use process-name. If the object is a TAPS process, use indirect-process-name. If the object is a TSP or NSP process, use indirect-process-name.
Commands and Responses LISTOBJECTS PROCESS Command specified with a value other than ZCOM-TKN-SUB-NONE. In addition, multiple response messages can be returned. ZCOM-TKN-OBJTYPE and ZCOM-TKN-OBJNAME are described in the Communications Management Programming Manual. One ZCOMTKN-OBJNAME token is included for each subordinate object returned. ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses LISTOBJECTS PROFILE Command LISTOBJECTS PROFILE Command The LISTOBJECTS PROFILE command returns the names of all PROFILE objects of a given type (Layer 3, Layer 4, or Layer 5), or of all types, in an OSI/AS subsystem.
Commands and Responses LISTOBJECTS PROFILE Command COM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
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. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses LISTOBJECTS SU Command LISTOBJECTS SU Command The LISTOBJECTS SU command returns a list of the names of all the currently existing subdevices subordinate to the specified TAPS process.
Commands and Responses LISTOBJECTS SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses LISTOBJECTS SUBSYS Command LISTOBJECTS SUBSYS Command The LISTOBJECTS SUBSYS command returns the name of the specified subsystem (that is, the name of its OSI manager process) and/or the names of objects subordinate to it in the OSI/AS object hierarchy.
Commands and Responses LISTOBJECTS SUBSYS Command must be the same as the OSI manager process name specified in either ZSPI-TKNMANAGER or ZCOM-TKN-XMGR. ZCOM-TKN-SUB specifies whether LISTOBJECTS is to return the name of the specified subsystem (that is, the name of its OSI manager process), the names of its subordinate objects in the OSI/AS object hierarchy, or both. The possible values are as follows: ZCOM-VAL-SUB-ALL Select the named subsystem and all of its subordinate objects.
Commands and Responses LISTOBJECTS SUBSYS Command ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses LISTOPENS PROCESS Command LISTOPENS PROCESS Command The LISTOPENS PROCESS command returns information about all currently existing opens (for data communications) of the specified process. Management programming (#ZSPI) opens are not listed.
Commands and Responses LISTOPENS PROCESS 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 PROCESS Command ZOSI-MAP-LISTOP is an extensible structured token that contains the current information about one open of the specified process. This token can occur multiple times. ZOSI-DDLLISTOP contains the following fields: ZDEVNAME is the Guardian 90 C-series system process name of the opener. ZPRIM-CPU is the number of the CPU in which the primary process (of the process pair) of the opener is running. The range of values is 0 through 15.
Commands and Responses LISTOPENS PROCESS Command ZCEPI is the connection endpoint identifier (CEPI) associated with the open. ZXDEVNAME-LEN is the Guardian 90 D-series system process name of the opener. ZXDEVNAME contains the device name of the process opener. ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Operational Note The backup PID defines the backup opener.
Commands and Responses LISTOPENS SU Command LISTOPENS SU Command The LISTOPENS SU command returns information about all currently existing opens of one or more OSI/AS 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 ZOSI-MAP-LISTOP is an extensible structured token that contains the current information about one open of a subdevice. This token can occur multiple times. ZOSI-DDL-LISTOP contains the following fields: ZDEVNAME is the Guardian 90 C-series system process name of the opener of the subdevice. ZPRIM-CPU is the number of the CPU in which the primary process (of the process pair) of the opener is running. The range of values is 0 through 15.
Commands and Responses LISTOPENS SU Command ZCEPI is the connection endpoint identifier (CEPI) associated with the open. ZXDEVNAME-LEN contains the length of the device name. ZXDEVNAME is the Guardian 90 D-series system process name of the opener of the subdevice. ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses RESETSTATS PROCESS Command RESETSTATS PROCESS Command The RESETSTATS PROCESS command returns 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/AS subsystem objects.
Commands and Responses RESETSTATS PROCESS Command Tokens in Response Buffer (continued) 02 ZINUSE-RCBS 02 ZMAX-INUSE-RCBS end. ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . . ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST type ZSPI-DDL-INT. type ZSPI-DDL-INT. token-type ZSPI-TYP-ENUM. token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-SSCTL. token-type ZSPI-TYP-SSCTL.
Commands and Responses RESETSTATS PROCESS Command ZOSI-MAP-STATS-PROC is an extensible structured token that contains current statistics for the specified process. ZOSI-DDL-STATS-PROC contains the following fields: ZRESET-TMSTP is the time and date when the statistics were last reset. ZSAMPLE-TMSTP is the time and date when this statistics sample was taken. ZFS-OPEN-REQS is the number of OPEN file-system requests that have been handled by the specified process.
Commands and Responses RESETSTATS PROCESS Command ZFS-DEVICEINFO-REQS is the number of DEVICEINFO file-system requests that have been handled by the specified process. ZFS-WRITEREAD-REQS is the number of WRITEREAD file-system requests that have been handled by the specified process. ZINUSE-OCBS is the number of open control blocks (OCBs) that are currently in use within the specified process. ZMAX-INUSE-OCBS is the maximum number of OCBs that were ever simultaneously in use within this process.
Commands and Responses RESETSTATS SERVICE Command RESETSTATS SERVICE Command The RESETSTATS SERVICE command returns statistics for the specified SERVICE from a designated TAPS process, and also resets the statistics counters to zero. This is a sensitive command; however, it does not change the state of any OSI/AS subsystem objects.
Commands and Responses RESETSTATS SERVICE 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 end. ZRFSPDURECVOTHER type ZSPI-DDL-INT2. ZRFSPDUSENTOTHER type ZSPI-DDL-INT2. ZABSPDURECVNOREASON type ZSPI-DDL-INT2. ZABSPDUSENTNOREASON type ZSPI-DDL-INT2. ZABSPDURECVPROTERROR type ZSPI-DDL-INT2. ZABSPDUSENTPROTERROR type ZSPI-DDL-INT2. ZABSPDUSENTPROTERRORTHLD type ZSPI-DDL-INT2. ZABSPDURECVOTHER type ZSPI-DDL-INT2.
Commands and Responses RESETSTATS SERVICE Command Tokens in Response Buffer (continued) 02 ZCPRPPDUSENTPERMANENTGROUP type ZSPI-DDL-INT2. 02 ZCPRPPDURECVOTHER type ZSPI-DDL-INT2. 02 ZCPRPPDUSENTOTHER type ZSPI-DDL-INT2. 02 ZARPPPDURECVNOREASON type ZSPI-DDL-INT2. 02 ZARPPPDUSENTNOREASON type ZSPI-DDL-INT2. 02 ZARPPPDURECVPROTERRORGROUP type ZSPI-DDL-INT2. 02 ZARPPPDUSENTPROTERRORGROUP type ZSPI-DDL-INT2. 02 ZARPPPDURECVOTHER type ZSPI-DDL-INT2. 02 ZARPPPDUSENTOTHER type ZSPI-DDL-INT2.
Commands and Responses RESETSTATS SERVICE Command Tokens in Response Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 ZAPABORTS type ZAPABORTSTHLD type ZACPMASSOCPREJECTS type ZACPMASSOCPREJECTSTHLD type ZAPDUSENT type ZAPDURECV type ZAARQ-APDUS-RECV type ZAARQ-APDUS-SENT type ZAARE-ACCEPT-APDUS-RECV type ZAARE-ACCEPT-APDUS-SENT type ZRLRQ-APDUS-RECV type ZRLRQ-APDUS-SENT type ZRLRE-ACCEPT-APDUS-RECV type ZRLRE-ACCEPT-APDUS-SENT type ZRLRE-REJECT-APDUS-RECV type ZRLRE-REJECT-APDUS-SENT t
Commands and Responses RESETSTATS SERVICE Command For each ZCOM-TKN-OBJNAME token, the response also includes one of the following tokens: ZOSI-MAP-STATS-SERV-L5 for the Layer 5 SERVICE ZOSI-MAP-STATS-SERV-L6 for the Layer 6 SERVICE ZOSI-MAP-STATS-SERV-ACSE for the ACSE SERVICE ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual.
Commands and Responses RESETSTATS SERVICE Command is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535. ZRFSPDURECVPERMANENT is the number of times the Session Layer has received an RF-SPDU with a reason code of “SSAP identifier unknown (129)” or “proposed protocol versions not supported (132).” The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535.
Commands and Responses RESETSTATS SERVICE Command counter value by the threshold value leaves a remainder of zero. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. If the threshold is set to 0, L5-THLD event messages are never generated for this counter. ZRFSPDUSENTTEMPORARY is the number of times the Session Layer has sent or has attempted to send an RF-SPDU with a reason code of “SS user not attached to SSAP (130)” or “SPM congestion at connect time (131).
Commands and Responses RESETSTATS SERVICE Command The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535. ZABSPDUSENTPROTERROR is the number of times the Session Layer has sent or has attempted to send an AB-SPDU in which the transport disconnect parameter bit 3 is set to 1, indicating a protocol error. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use.
Commands and Responses RESETSTATS SERVICE Command ZSPDU-USERDATA-SENT is the number of bytes of user data that have been sent over the specified Layer 5 SERVICE. The range of values is 0 through 2,147,483,647. The counter wraps around when it exceeds 2,147,483,647. ZSPDU-BYTES-RECV is the total number of bytes of information that have been received over the specified Layer 5 SERVICE. This total includes both user data and session control information. The range of values is 0 through 2,147,483,647.
Commands and Responses RESETSTATS SERVICE Command layer sent, or attempted to send, a disconnect (DN) SPDU. This counter wraps around upon overflow. The range of values is 0 through 65535. ZFN-SPDU-RECV contains the number of times the session layer received a Finish (FN) SPDU. This counter wraps around upon overflow. The range of values is 0 through 65535. ZFN-SPDU-SENT contains the number of times the session layer sent, or attempted to send, a Finish (FN) SPDU. This counter wraps around upon overflow.
Commands and Responses RESETSTATS SERVICE Command more connections are established by the TAPS process. This field will not be reset when RESET is specified. ZOSI-MAP-STATS-SERV-L6 is an extensible structured token that contains current statistics for the Layer 6 SERVICE. ZOSI-DDL-STATS-SERV-L6 contains the following fields: ZRESET-TMSTP is the time and date when the statistics were last reset. ZSAMPLE-TMSTP is the time and date when this statistics sample was taken.
Commands and Responses RESETSTATS SERVICE Command ZCPRPPDUSENTPERMANENTGROUP is the number of times the Presentation Layer has sent or has attempted to send a CPR-PPDU with a reason code of “local limit exceeded (2),” “called presentation address unknown (3),” “protocol version not supported (4),” “default context not supported (5),” or “user data not readable (6).” The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535.
Commands and Responses RESETSTATS SERVICE Command ZARPPPDUSENTPROTERRORGROUP is the number of times the Presentation Layer has sent or has attempted to send an ARP-PPDU with a reason code of “unrecognized PPDU (1),” “unexpected PPDU (2),” “unexpected session service primitive (3),” “unrecognized PPDU parameter (4),” “unexpected PPDU parameter (5),” or “invalid PPDU parameter value (6).” The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use.
Commands and Responses RESETSTATS SERVICE Command THLD event message whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. If the threshold is set to 0, L6-THLD event messages are never generated for this counter. ZARPPPDUSENTPROTERRORGROUPTHLD is the threshold value that the Presentation Layer compares to the counter ZARPPPDUSENTPROTERRORGROUP.
Commands and Responses RESETSTATS SERVICE Command ZOSI-MAP-STATS-SERV-ACSE is an extensible structured token that contains current statistics for the ACSE SERVICE. ZOSI-DDL-STATS-SERV-ACSE contains the following fields: ZRESET-TMSTP is the time and date when the statistics were last reset. ZSAMPLE-TMSTP is the time and date when this statistics sample was taken.
Commands and Responses RESETSTATS SERVICE Command ZAGGREGATEASSOCREJECTSRECV is the number of times the ACSE SERVICE has received an AARE-APDU with a result field of “rejected permanent (1),” or “rejected temporary (2)” and a result source field of the ACSE service provider or the ACSE service user. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535.
Commands and Responses RESETSTATS SERVICE Command ZAPABORTS is the number of times the association control protocol machine (ACPM) has issued an application process abort (AP-ABORT) indication. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535. ZAPABORTSTHLD is the threshold value that the ACSE SERVICE compares to the counter ZAPABORTS.
Commands and Responses RESETSTATS SERVICE Command ZAARQ-APDUS-SENT contains the number of times the ACSE service sends, or attempts to send, an ACSE Associate ReQuest (AARQ) APDU. This counter wraps around upon overflow. The range of values is 0 through 65535. ZAARE-ACCEPT-APDUS-RECV contains the number of times the ACSE service receives an ACSE Associate REsponse Accept (AARE+) APDU. This counter wraps around upon overflow. The range of values is 0 through 65535.
Commands and Responses RESETSTATS SERVICE Command ZRLRE-REJECT-APDUS-SENT contains the number of times the ACSE service sends, or attempts to send, a ReLease REsponse Reject (RLRE-) APDU. This counter wraps around upon overflow. The range of values is 0 through 65535. ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses RESETSTATS SU Command RESETSTATS SU Command The RESETSTATS SU command returns statistics for the specified subdevice, and also resets the statistics counters to zero. This is a sensitive command; however, it does not change the state of any OSI/AS subsystem objects.
Commands and Responses RESETSTATS 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 RESETSTATS SU Command buffer, then one of these tokens is returned for each subdevice name. ZOSI-DDLSTATS-SU-L5 contains the following fields: ZRESET-TMSTP is the time and date when the statistics were last reset. ZSAMPLE-TMSTP is the time and date when this statistics sample was taken. ZSPDUS-SENT is the number of session protocol data units (SPDUs) that have been sent over the specified subdevice. The range of values is 0 through 2,147,483,647.
Commands and Responses RESETSTATS SU Command ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Operational Notes The RESETSTATS SU command must be sent to a TAPS process; it cannot be handled by the OSI manager process. A timestamp is associated with each counter returned, indicating when the sample was taken. Several counters can share the same timestamp.
Commands and Responses RESETSTATS SUBSYS Command RESETSTATS SUBSYS Command The RESETSTATS SUBSYS command returns statistics for the specified subsystem, and also resets the statistics counters to zero. This is a sensitive command; however, it does not change the state of any OSI/AS subsystem objects.
Commands and Responses RESETSTATS SUBSYS Command Tokens in Response Buffer (continued) 02 ZMAX-EVER-NSAP-ENTRIES type 02 ZCURR-NSAP-ENTRIES type 02 ZMAX-EVER-SNPA-ENTRIES type 02 ZCURR-SNPA-ENTRIES type 02 ZMAX-EVER-L3-PROFS type 02 ZCURR-L3-PROFS type 02 ZMAX-EVER-L4-PROFS type 02 ZCURR-L4-PROFS type 02 ZREG-REQS-RECV type 02 ZREG-REQS-PASS type 02 ZREG-REQS-FAIL type 02 ZREG-FAIL-LOC-NAME type 02 ZREG-FAIL-RMT-NAME type 02 ZREG-FAIL-LOC-TSEL type 02 ZREG-FAIL-LOC-NSAP type 02 ZREG-FAIL-RMT-NSAP type 02 Z
Commands and Responses RESETSTATS SUBSYS 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 OSI manager 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 subsystem for which the statistics counters are to be reset.
Commands and Responses RESETSTATS SUBSYS Command ZMAX-EVER-NSP-PROCS is the maximum number of NSP process pairs that have been configured simultaneously in the specified subsystem. ZCURR-NSP-PROCS is the number of NSP process pairs that are currently configured in the specified subsystem. ZMAX-EVER-TSP-PROCS is the maximum number of TSP process pairs that have been configured simultaneously in the specified subsystem.
Commands and Responses RESETSTATS SUBSYS Command ZCURR-NSAP-ENTRIES is the number of NSAP ENTRY objects that are currently configured in the specified subsystem. ZMAX-EVER-SNPA-ENTRIES is the maximum number of SNPA ENTRY objects that have been configured simultaneously in the specified subsystem. ZCURR-SNPA-ENTRIES is the number of SNPA ENTRY objects that are currently configured in the specified subsystem.
Commands and Responses RESETSTATS SUBSYS Command ZREG-FAIL-LOC-NAME is the number of register requests that failed because the local name was not found. ZREG-FAIL-RMT-NAME is the number of register requests that failed because the remote name was not found. ZREG-FAIL-LOC-TSEL is the number of register requests that failed because the local TSEL was not found. ZREG-FAIL-LOC-NSAP is the number of register requests that failed because the local NSAP was not found.
Commands and Responses RESETSTATS SUBSYS Command ZREG-FAIL-L4-PROF is the number of register requests that failed because the Layer 4 PROFILE was not found. ZREG-FAIL-L3-PROF is the number of register requests that failed because the Layer 3 PROFILE was not found. ZREG-FAIL-INTL is the number of register requests that failed because of an internal error. ZMAX-EVER-L5-PROFS is the maximum number of Layer 5 PROFILE objects that have been configured simultaneously in the specified subsystem.
Commands and Responses START PROCESS Command START PROCESS Command The START command initiates the operation of the specified process. The exact actions performed by this command depend on the kind of process (OSI manager or TAPS) to which it is sent and the kind of process specified as the object. This is a sensitive command.
Commands and Responses START PROCESS Command the command directly to a TAPS process, bypassing the OSI manager process, ZCOM-TKN-OBJNAME must occur only once, and it must be the name of that TAPS process. If you are sending the command to the OSI manager process, ZCOM-TKN-OBJNAME can occur multiple times.
Commands and Responses START PROCESS Command ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Operational Note The OSI/AS START command is not valid for NSP processes. To start an NSP process in the OSI/AS environment, you must send a START LINE command to the appropriate subsystem (X25AM or TLAM), as described in the management programming manual for that subsystem.
Commands and Responses STATISTICS PROCESS Command STATISTICS PROCESS Command The STATISTICS PROCESS command returns statistics for the specified process but does not reset the statistics counters.
Commands and Responses STATISTICS 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 OSI manager or TAPS process to which SCP is to send this command.
Commands and Responses STATISTICS PROCESS Command ZRESET-TMSTP is the time and date when the statistics were last reset. ZSAMPLE-TMSTP is the time and date when this statistics sample was taken. ZFS-OPEN-REQS is the number of OPEN file-system requests that have been handled by the specified process. ZFS-CLOSE-REQS is the number of CLOSE file-system requests that have been handled by the specified process.
Commands and Responses STATISTICS PROCESS Command ZFS-WRITEREAD-REQS is the number of WRITEREAD file-system requests that have been handled by the specified process. ZINUSE-OCBS is the number of open control blocks (OCBs) that are currently in use within the specified process. ZMAX-INUSE-OCBS is the maximum number of OCBs that were ever simultaneously in use within this process. ZINUSE-RCBS is the number of request control blocks (RCBs) that are currently in use within the specified process.
Commands and Responses STATISTICS SERVICE Command STATISTICS SERVICE Command The STATISTICS SERVICE command returns statistics for the specified SERVICE from a designated TAPS process, but does not reset the statistics counters.
Commands and Responses STATISTICS SERVICE 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 end.
Commands and Responses STATISTICS SERVICE Command Tokens in Response Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 end. ZCPRPPDUSENTOTHER type ZSPI-DDL-INT2. ZARPPPDURECVNOREASON type ZSPI-DDL-INT2. ZARPPPDUSENTNOREASON type ZSPI-DDL-INT2. ZARPPPDURECVPROTERRORGROUP type ZSPI-DDL-INT2. ZARPPPDUSENTPROTERRORGROUP type ZSPI-DDL-INT2. ZARPPPDURECVOTHER type ZSPI-DDL-INT2. ZARPPPDUSENTOTHER type ZSPI-DDL-INT2. ZCPRPPDURECVTRANSIENTGROUPTHLD type ZSPI-DDL-INT2.
Commands and Responses STATISTICS SERVICE Command Tokens in Response Buffer (continued) 02 02 02 02 02 02 02 02 02 02 02 02 02 ZACPMASSOCPREJECTSTHLD type ZSPI-DDL-INT2. ZAPDUSENT type ZSPI-DDL-INT2. ZAPDURECV type ZSPI-DDL-INT2. ZAARQ-APDUS-RECV type ZSPI-DDL-INT2. ZAARQ-APDUS-SENT type ZSPI-DDL-INT2. ZAARE-ACCEPT-APDUS-RECV type ZSPI-DDL-INT2. ZAARE-ACCEPT-APDUS-SENT type ZSPI-DDL-INT2. ZRLRQ-APDUS-RECV type ZSPI-DDL-INT2. ZRLRQ-APDUS-SENT type ZSPI-DDL-INT2. ZRLRE-ACCEPT-APDUS-RECV type ZSPI-DDL-INT2.
Commands and Responses STATISTICS SERVICE Command ZCOM-TKN-OBJNAME is the name of the SERVICE for which you want statistics. This token is required, can occur multiple times, and can be an object-name template (wild card name).
Commands and Responses STATISTICS SERVICE Command ZRFSPDUSENTNOREASON is the number of times the Session Layer has sent or has attempted to send an RF-SPDU with a reason code of “reason not specified (0).” The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535.
Commands and Responses STATISTICS SERVICE Command ZRFSPDURECVTEMPORARYTHLD is the threshold value that the Session Layer compares to the counter ZRFSPDURECVTEMPORARY. OSI/AS generates a ZOSI-EVT-L5-THLD event message whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use.
Commands and Responses STATISTICS SERVICE Command ZABSPDURECVPROTERROR is the number of times the Session Layer has received an AB-SPDU in which the transport disconnect parameter bit 3 is set to 1, indicating a protocol error. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535.
Commands and Responses STATISTICS SERVICE Command ZSPDU-BYTES-SENT is the total number of bytes of information that have been sent over the specified Layer 5 SERVICE. This total includes both user data and session control information. The range of values is 0 through 2,147,483,647. The counter wraps around when it exceeds 2,147,483,647. ZSPDU-USERDATA-SENT is the number of bytes of user data that have been sent over the specified Layer 5 SERVICE. The range of values is 0 through 2,147,483,647.
Commands and Responses STATISTICS SERVICE Command ZDN-SPDU-RECV is the number of times the session layer received a disconnect (DN) SPDU. The range of values is 0 through 65535. The counter wraps around when it exceeds 65535. ZDN-SPDU-SENT is the number of times the session layer sent, or attempted to send, a disconnect (DN) SPDU. The range of values is 0 through 65535. The counter wraps around when it exceeds 65535. ZFN-SPDU-RECV is the number of times the session layer received a Finish (FN) SPDU.
Commands and Responses STATISTICS SERVICE Command is, they have been created with a ZDEL-TIME of -1D. A static SU that has been disconnected but has not been reused for an attach or a connect request will increment this field by 1. This field will not be reset when RESET is specified. ZAVAIL-SU is the number of subdevices that are available for use in the specified TAPS process. It indicates the number of connections that can still be established. The range is from ZMAXCONNS to 0.
Commands and Responses STATISTICS SERVICE Command ZCPRPPDURECVPERMANENTGROUP is the number of times the Presentation Layer has received a CPR-PPDU with a reason code of “local limit exceeded (2),” “called presentation address unknown (3),” “protocol version not supported (4),” “default context not supported (5),” or “user data not readable (6).” The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535.
Commands and Responses STATISTICS SERVICE Command ZARPPPDURECVPROTERRORGROUP is the number of times the Presentation Layer has received an ARP-PPDU with a reason code of “unrecognized PPDU (1),” “unexpected PPDU (2),” “unexpected session service primitive (3),” “unrecognized PPDU parameter (4),” “unexpected PPDU parameter (5),” or “invalid PPDU parameter value (6).” The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. The counter wraps around when it exceeds 65535.
Commands and Responses STATISTICS SERVICE Command counter value by the threshold value leaves a remainder of zero. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. If the threshold is set to 0, L6-THLD event messages are never generated for this counter. ZCPRPPDUSENTPERMANENTGROUPTHLD is the threshold value that the Presentation Layer compares to the counter ZCPRPPDUSENTPERMANENTGROUP.
Commands and Responses STATISTICS SERVICE Command ZCPA-PPDU-SENT is the number of times the Presentation layer sent, or attempted to send, a Connect Propose Accept (CPA) PPDU. The range of values is 0 through 65535. The counter wraps around when it exceeds 65535. ZCPA-PPDU-RECV is the number of times the Presentation layer received a Connect Propose Accept (CPA) PPDU.The range of values is 0 through 65535. The counter wraps around when it exceeds 65535.
Commands and Responses STATISTICS SERVICE Command ZACPMREJECTSSENTTHLD is the threshold value that the ACSE SERVICE compares to the counter ZACPMREJECTSSENT. OSI/AS generates a ZOSI-EVT-ACSE-THLD event message whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. If the threshold is set to 0, ACSE-THLD event messages are never generated for this counter.
Commands and Responses STATISTICS SERVICE Command ZACPMABORTSSENTTHLD is the threshold value that the ACSE SERVICE compares to the counter ZACPMABORTSSENT. OSI/AS generates a ZOSI-EVT-ACSE-THLD event message whenever the counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero. The range of values is 0 through 65535; 16 bits of the field is reserved for Tandem use. If the threshold is set to 0, ACSE-THLD event messages are never generated for this counter.
Commands and Responses STATISTICS SERVICE Command ZAPDURECV is the number of APDUs that have been received over the specified ACSE SERVICE. The range of values is 0 through 2,147,483,647. The counter wraps around when it exceeds 2,147,483,647. ZAARQ-APDUS-RECV is the number of times the ACSE service receives an ACSE Associate ReQuest (AARQ) APDU. The range of values is 0 through 65535. The counter wraps around when it exceeds 65535.
Commands and Responses STATISTICS SERVICE Command ZRLRE-ACCEPT-APDUS-SENT is the number of times the ACSE service sends, or attempts to send, a ReLease REsponse Accept (RLRE+) APDU. The range of values is 0 through 65535. The counter wraps around when it exceeds 65535. ZRLRE-REJECT-APDUS-RECV is the number of times the ACSE service receives a ReLease REsponse Reject (RLRE-) APDU. The range of values is 0 through 65535. The counter wraps around when it exceeds 65535.
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 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 STATISTICS SU Command buffer, then one of these tokens is returned for each subdevice name. ZOSI-DDLSTATS-SU-L5 contains the following fields: ZRESET-TMSTP is the time and date when the statistics were last reset. ZSAMPLE-TMSTP is the time and date when this statistics sample was taken. ZSPDUS-SENT is the number of session protocol data units (SPDUs) that have been sent over the specified subdevice. The range of values is 0 through 2,147,483,647.
Commands and Responses STATISTICS SU Command ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Operational Notes The STATISTICS SU command must be sent to a TAPS process; it cannot be handled by the OSI manager process. To calculate the total counts for all subdevices under a given TAPS process, you must specify the subdevices individually and add together the individual subdevice counts.
Commands and Responses STATISTICS SUBSYS Command STATISTICS SUBSYS Command The STATISTICS SUBSYS command returns statistics for the specified subsystem, but does not reset the statistics counters. Command ZCOM-CMD-STATISTICS Object Type ZCOM-OBJ-SUBSYS 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 STATISTICS SUBSYS Command Tokens in Response Buffer (continued) 02 ZMAX-EVER-NSAP-ENTRIES type 02 ZCURR-NSAP-ENTRIES type 02 ZMAX-EVER-SNPA-ENTRIES type 02 ZCURR-SNPA-ENTRIES type 02 ZMAX-EVER-L3-PROFS type 02 ZCURR-L3-PROFS type 02 ZMAX-EVER-L4-PROFS type 02 ZCURR-L4-PROFS type 02 ZREG-REQS-RECV type 02 ZREG-REQS-PASS type 02 ZREG-REQS-FAIL type 02 ZREG-FAIL-LOC-NAME type 02 ZREG-FAIL-RMT-NAME type 02 ZREG-FAIL-LOC-TSEL type 02 ZREG-FAIL-LOC-NSAP type 02 ZREG-FAIL-RMT-NSAP type 02 Z
Commands and Responses STATISTICS SUBSYS 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 OSI manager 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 subsystem for which you want statistics.
Commands and Responses STATISTICS SUBSYS Command ZMAX-EVER-NSP-PROCS is the maximum number of NSP process pairs that have been configured simultaneously in the specified subsystem. ZCURR-NSP-PROCS is the number of NSP process pairs that are currently configured in the specified subsystem. ZMAX-EVER-TSP-PROCS is the maximum number of TSP process pairs that have been configured simultaneously in the specified subsystem.
Commands and Responses STATISTICS SUBSYS Command ZCURR-NSAP-ENTRIES is the number of NSAP ENTRY objects that are currently configured in the specified subsystem. ZMAX-EVER-SNPA-ENTRIES is the maximum number of SNPA ENTRY objects that have been configured simultaneously in the specified subsystem. ZCURR-SNPA-ENTRIES is the number of SNPA ENTRY objects that are currently configured in the specified subsystem.
Commands and Responses STATISTICS SUBSYS Command ZREG-FAIL-LOC-NAME is the number of register requests that failed because the local name was not found. ZREG-FAIL-RMT-NAME is the number of register requests that failed because the remote name was not found. ZREG-FAIL-LOC-TSEL is the number of register requests that failed because the local TSEL was not found. ZREG-FAIL-LOC-NSAP is the number of register requests that failed because the local NSAP was not found.
Commands and Responses STATISTICS SUBSYS Command ZREG-FAIL-L4-PROF is the number of register requests that failed because the Layer 4 PROFILE was not found. ZREG-FAIL-L3-PROF is the number of register requests that failed because the Layer 3 PROFILE was not found. ZREG-FAIL-INTL is the number of register requests that failed because of an internal error. ZMAX-EVER-L5-PROFS is the maximum number of Layer 5 PROFILE objects that have been configured simultaneously in the specified subsystem.
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 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.
Commands and Responses STATUS PROCESS Command Tokens in Response Buffer (continued) 02 ZCREATE-TIME 02 ZXDEVNAME 02 ZXDEVNAME-LEN end. ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST . . . ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT type ZSPI-DDL-TIMESTAMP. type ZOSI-DDL-CHAR36. type ZSPI-DDL-INT. 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 STATUS PROCESS Command Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list. These tokens enclose the other response tokens only if the value of the header token ZSPI-TKN-MAXRESP is nonzero. ZCOM-TKN-OBJTYPE, ZCOM-TKN-OBJNAME, and ZCOM-TKN-OBJSTATE are described in the Communications Management Programming Manual.
Commands and Responses STATUS PROCESS Command ZCOM-VAL-SUMSTATE-STARTED The process is started. ZCOM-VAL-SUMSTATE-STARTING The process is starting. ZCOM-VAL-SUMSTATE-STOPPED The process is stopped. ZCOM-VAL-SUMSTATE-STOPPING The process is stopping. ZCOM-VAL-SUMSTATE-SUSP The process is suspended. ZCOM-VAL-SUMSTATE-SUSPENDING The process is suspending. ZCOM-VAL-SUMSTATE-UNKWN The process state is unknown.
Commands and Responses STATUS PROCESS Command ZOSI-VAL-TRACE-SEL-L6-USER Presentation user requests and events ZOSI-VAL-TRACE-SEL-L6-PROV Presentation provider requests and events ZOSI-VAL-TRACE-SEL-L6 Presentation state machine, presentation user requests and events, and presentation provider requests and events ZOSI-VAL-TRACE-SEL-ACSE-SM ACSE state machine ZOSI-VAL-TRACE-SEL-ACSE-USER ACSE user requests and events ZOSI-VAL-TRACE-SEL-ACSE-PROV ACSE provider requests and events ZOSI-VAL-TRACE-S
Commands and Responses STATUS PROCESS Command ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are 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 ZCALLING-ADDR 04 ZNAME-LEN 04 ZNAME 04 ZNSAP-LEN 04 ZNSAP 04 ZTSEL-LEN 04 ZTSEL 04 ZSSEL-LEN 04 ZSSEL 04 ZPSEL-LEN 04 ZPSEL 04 ZAE-TITLE 02 ZCALLED-ADDR 04 ZNAME-LEN 04 ZNAME 04 ZNSAP-LEN 04 ZNSAP 04 ZTSEL-LEN 04 ZTSEL 04 ZSSEL-LEN 04 ZSSEL 04 ZPSEL-LEN 04 ZPSEL 04 ZAE-TITLE 02 ZRESPONDING-ADDR 04 ZNAME-LEN 04 ZNAME 04 ZNSAP-LEN 04 ZNSAP 04 ZTSEL-LEN 04 ZTSEL 04 ZSSEL-LEN 04 ZSSEL 04 ZPSEL-LEN 04 ZPSEL 04 ZAE-TITLE 02 ZSERV-L
Commands and Responses STATUS SU Command Tokens in Response Buffer (continued) 02 ZTSP-TCON-STATE-AT-LAST-ERR type ZSPI-DDL-INT. 02 ZTSP-TCON-SUBSTATE-AT-LAST-ERR type ZSPI-DDL-INT. end. ZOSI-MAP-STATUS-SU-L5 def ZOSI-DDL-STATUS-SU-L5. 02 ZLAST-ERR 02 ZLAST-ERR-SUBCODE 02 ZVACT 02 ZVNEXTACT 02 ZVSC 02 ZVA 02 ZVM 02 ZVR 02 ZPMSTATE 02 ZL4-SUNAME 02 ZLOC-ADDR. 04 ZNAME-LEN 04 ZNAME 04 ZNSAP-LEN 04 ZNSAP 04 ZTSEL-LEN 04 ZTSEL 04 ZSSEL-LEN 04 ZSSEL 04 ZPSEL-LEN 04 ZPSEL 02 ZRMT-ADDR.
Commands and Responses STATUS SU Command Tokens in Response Buffer (continued) 02 ZIN-MAX-TSDU-SIZE 02 ZOUT-MAX-TSDU-SIZE 02 ZREL 02 ZDATA 02 ZMINOR-SYNC 02 ZMAJOR-SYNC 02 ZACTIVITY 02 ZFU-HDUX 02 ZFU-DUX 02 ZFU-EXCPT 02 ZFU-TYPED-DATA 02 ZFU-NEG-REL 02 ZFU-MINOR-SYNC 02 ZFU-MAJOR-SYNC 02 ZFU-RESYNC 02 ZFU-EXPEDITED 02 ZFU-ACTIVITY 02 ZFU-CAP-DATA 02 ZDISCONN-TIMER 02 ZPROTO-VSN 02 ZVTEXP 02 ZLOOPBACK-ENABLED 02 ZL4-SUNAME32 end. ZOSI-MAP-STATUS-SU-L6 def ZOSI-DDL-STATUS-SU-L6.
Commands and Responses STATUS 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 TAPS 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 subdevice for which you want status information. This token is required, can occur multiple times, and can be an object-name template (wild card name).
Commands and Responses STATUS SU Command ZOSI-MAP-STATUS-SU is an extensible structured token that contains current status information for the specified subdevice. If multiple subdevice names are specified in the response buffer, then one of these tokens is returned for each subdevice name. ZOSI-DDL-STATUS-SU contains the following fields: ZSUMSTATE is the summary state of the specified subdevice.
Commands and Responses STATUS SU Command ZLAST-SL-ERR-SOURCE is the source of the last communications error detected by a TAPS process. This field has meaning only if the value of ZLAST-SL-ERR is nonzero.
Commands and Responses STATUS SU Command ZTSEL-LEN is the length (in bytes) of the calling TSEL address in ZTSEL. The range of values is 0 through 32 bytes. ZTSEL is the calling TSEL address for the specified subdevice. The TSEL address is a binary-encoded string of an even number of hexadecimal digits. TSEL addresses are administered locally. ZSSEL-LEN is the length (in bytes) of the calling SSEL address in ZSSEL. The range of values is 0 through 16 bytes.
Commands and Responses STATUS SU Command ZSERV-LEV indicates the layer of the connection supported by the specified subdevice. Possible values are as follows: ZOSI-VAL-SERV-LEVEL-L5 Session Layer ZOSI-VAL-SERV-LEVEL-L6 Presentation Layer ZOSI-VAL-SERV-LEVEL-ACSE ACSE The value of this token indicates which of the following layer status tokens will be meaningful in the response. If the value is ZOSI-VAL-SERV-LEVELL5, only ZOSI-MAP-STATUS-SU-L5 will be meaningful.
Commands and Responses STATUS SU Command ZTSP-TCON-STATE-AT-LAST-ERR This field is present only if ZTSP-LAST-FS-ERRCODE is non zero. It records the TSP state (as described in the OSI/TS STATUS SU command) at the time of that error. ZTSP-TCON-SUBSTATE-AT-LAST-ERR This field is present only if ZTSP-LAST-FS-ERRCODE is non zero. It records the TSP substate (as described in the OSI/TS STATUS SU command) at the time of that error.
Commands and Responses STATUS SU Command ZVA is the V(A) session protocol variable, which is the lowest serial number to which a synchronization point confirmation is expected. No confirmation is expected when ZVA equals ZVM. ZVM is the V(M) session protocol variable, which is the next serial number to be used. ZVR is the V(R) session protocol variable, which is the lowest serial number to which resynchronization restart is permitted. ZPMSTATE is the current state of the session protocol machine.
Commands and Responses STATUS SU Command ZCALLING-ADDR, ZCALLED-ADDR, and ZRESPONDING-ADDR fields of ZOSI-MAP-STATUS-SU. ZIN-SEGM controls segmentation for inbound SSDUs. Since OSI/AS does not support segmentation, this field always has the value ZSPI-VAL-FALSE. ZOUT-SEGM controls segmentation for outbound SSDUs. Since OSI/AS does not support segmentation, this field always has the value ZSPI-VAL-FALSE.
Commands and Responses STATUS SU Command ZACTIVITY is the state of the session synchronize major token. Note that the ZMAJORSYNC field and the ZACTIVITY field reference the same data element. The values are the same as for ZREL. ZFU-HDUX controls the half-duplex functional unit. The interpretation of this field depends on which connection phase is active. During connection establishment, the value ZSPI-VAL-TRUE means the feature is selected, and ZSPI-VAL-FALSE means it is not selected.
Commands and Responses STATUS SU Command ZFU-MINOR-SYNC controls the minor synchronize functional unit. The interpretation of this field depends on which connection phase is active. During connection establishment, the value ZSPI-VAL-TRUE means the feature is selected, and ZSPI-VAL-FALSE means it is not selected. During data transfer, the value ZSPI-VAL-TRUE means the feature has been negotiated, and ZSPI-VALFALSE means it has not been negotiated.
Commands and Responses STATUS SU Command ZDISCONN-TIMER is the maximum amount of time the session service provider waits for a transport disconnect indication after issuing a request for session release or abort service. If a transport disconnect indication is not received within this time interval, the session service provider issues a transport disconnect request. The waiting time is expressed in microseconds (0.000001 seconds per increment).
Commands and Responses STATUS SU Command ZPMSTATE is the current state of the presentation protocol machine. See the ISO 8823 standard specification for a description of each of the states. The acceptable values are as follows: ZOSI-VAL-L6STATE-STAI0 ZOSI-VAL-L6STATE-STAI1 ZOSI-VAL-L6STATE-STAI2 ZOSI-VAL-L6STATE-STAAC0 ZOSI-VAL-L6STATE-STAAC1 ZOSI-VAL-L6STATE-STAAC2 ZOSI-VAL-L6STATE-STAT0 ZNORMAL-MODE indicates the current Layer 6 mode of operation.
Commands and Responses STATUS SU Command ZOSI-VAL-ACSTATE-STAL02 The connection has been released or aborted. ZNORMAL-MODE indicates the current ACSE mode of operation. If this field is set to ZSPI-VALTRUE, ACSE is operating in normal mode; if it is set to ZSPI-VAL-FALSE, it is operating in X.410 1984 mode. ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPITKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual.
Commands and Responses STATUS SUBSYS Command STATUS SUBSYS Command The STATUS SUBSYS command returns current information about the specified subsystem. Command ZCOM-CMD-STATUS Object Type ZCOM-OBJ-SUBSYS 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 SUBSYS 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 OSI manager process to which SCP is to send this command.
Commands and Responses STATUS SUBSYS Command ZDEVNAME is the Guardian 90 name of the OSI manager process for which this structured token contains status information. ZPRIM-CPU is the number of the CPU in which the primary process (of the OSI manager process pair) is running. The range of values is 0 through 15. ZPRIM-PIN is the process identification number of the OSI manager primary process.
Commands and Responses STATUS SUBSYS Command ZTAPS-CONFIGED is the number of TAPS processes that have been configured for the specified subsystem. ZTAPS-STARTED is the number of TAPS processes that are currently in the STARTED state in the specified subsystem. ZOPEN-CNT is the current number of opens of the specified OSI manager process. ZSUMSTATE contains the state of the subsystem. Once the subsystem has been created, it always returns a ZSUMSTATE of STARTED.
Commands and Responses STOP PROCESS Command STOP PROCESS Command The STOP PROCESS command terminates the operation of the specified process in an orderly manner, if the process is not in use, and places it in the STOPPED state. It is a sensitive command.
Commands and Responses STOP PROCESS Command must occur only once, and it must be the name of that TAPS process. If you are sending the command to the OSI manager process, ZCOM-TKN-OBJNAME can occur multiple times. The process-name format depends on the type of process, as follows: If the object is the OSI manager process, use process-name. If the object is a TSP process, use indirect-process-name. If the object is a TAPS process, use indirect-process-name.
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. It is a sensitive command. Command ZCOM-CMD-STOP 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 STOP SU Command ZCOM-TKN-CMD-TIMEOUT is described in the Communications Management Programming Manual. ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT, and ZSPI-TKN-CONTEXT are described in the Distributed Systems Management (DSM) Programming Manual. Tokens in Response Buffer ZSPI-TKN-DATALIST introduces a data list, as described in the Distributed Systems Management (DSM) Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list.
Commands and Responses SUSPEND PROCESS Command SUSPEND PROCESS Command The SUSPEND command changes the summary state of a STARTED process into the suspended (SUSP) state, reversing the effect of the ACTIVATE command. The process is not terminated. This is a sensitive command.
Commands and Responses SUSPEND PROCESS Command process, ZCOM-TKN-OBJNAME must occur only once, and it must be the processname of that TAPS process. If you are sending the command to the OSI manager process using an indirect-process-name, ZCOM-TKN-OBJNAME can occur multiple times.
Commands and Responses TRACE PROCESS Command TRACE PROCESS Command The TRACE command initiates, modifies, or terminates the gathering of trace information by the specified OSI manager or TAPS process. OSI/AS 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-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 OSI manager or TAPS 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 process-name of the OSI manager or TAPS process to be traced. This token is required and must occur only once.
Commands and Responses TRACE PROCESS Command ZOSI-VAL-TRACE-SEL-ACSE ACSE state machine, ACSE user requests and events, and ACSE provider requests and events ZOSI-VAL-TRACE-SEL-ASN1 ASN.1 encoding and decoding of the presentation and ACSE protocol information ZOSI-VAL-TRACE-SEL-MEM, ZOSI-VAL-TRACE-SEL-SYSMSG, ZOSI-VALTRACE-SEL-DSM, and ZOSI-VAL-TRACE-SEL-MSG apply when tracing either an OSI manager process or a TAPS process. All other values apply only when tracing a TAPS process.
Commands and Responses TRACE PROCESS Command ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, and ZSPI-TKN-ENDLIST are described in the Distributed Systems Management (DSM) Programming Manual. Operational Notes To trace an NSP or TSP process, refer to the management programming manual for the appropriate lower-layer subsystem (X25AM, TLAM, or OSI/TS). OSI/AS does not support the SCP trace backup option.
6 Event Messages This section describes the contents and meaning of all event messages generated by OSI/AS. In this section, command numbers, 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. Subsystem Processes Within the OSI/AS subsystem, the OSI manager process and TAPS processes generate That Report Events event messages.
Event Messages Tokens in All 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/AS event messages are listed in Table 6-3. Tokens that appear only in certain event messages are listed and described in the individual message descriptions in the remainder of this section.
Event Messages Event-Message Descriptions Event-Message Descriptions The following pages explain in detail each event message that can be issued by the OSI/AS subsystem. The descriptions appear in ascending order by event number; that is, in ascending order by the ZOSI-EVT- or ZCOM-EVT- values. Each description includes a syntax box containing the tokens that OSI/AS can place in the message buffer in addition to the common tokens listed in Table 6-2.
Event Messages -1: ZCOM-EVT-CPU-SWITCH -1: ZCOM-EVT-CPUSWITCH A subsystem issues this event message when there has been a CPU switch. In the following ZCOM-EVT-event descriptions, event messages are ordered by event number. ZCOM-TKN-SUBJ-objecttype tokens represent ZCOM event subjects. If objecttype is represented as PROC, a process is the subject of the event. Otherwise, a communications object of the type objecttype is the subject of the event.
Event Messages -1: ZCOM-EVT-CPU-SWITCH ZCOM-TKN-OLD-CPU The token type is ZSPI-TYP-INT. This token specifies the CPU where the primary process ran before the switch. It can have a value from 0 through 15.
Event Messages -3: ZCOM-EVT-SUMSTATE-CHG -3: ZCOM-EVT-SUMSTATECHG A subsystem issues this event message when there has been a summary-state change for an object. Common Event-Message Tokens Token: Key: Value: ZEMS-TKN-EVENTNUMBER ZEMS-TKN-EMPHASIS ZCOM-TKN-SUBJ-objecttype 1 ZCOM-EVT-SUMSTATE-CHG ZSPI-VAL-FALSE.
Event Messages -3: ZCOM-EVT-SUMSTATE-CHG ZCOM-TKN-OBJSTATE The token type is ZSPI-TYP-ENUM. This token specifies the current summarystate of an object following a state change.
Event Messages 1: ZOSI-EVT-INTL-ERR 1: ZOSI-EVT-INTL-ERR This is a critical event. The OSI/AS subsystem detected an unrecoverable internal error. The affected OSI/AS process terminates abnormally.
Event Messages 1: ZOSI-EVT-INTL-ERR subsystem ID in the Z-SSID field and the NEWPROCESS or PROCESS_CREATE_ error number in the Z-ERROR field. ZGRD-TKN-OBJECTFILE for C-series systems, is the program file name of the OSI manager or TAPS process. ZGRD-TKN-ENTRYPOINTLABEL is the internal procedure entry-point label of the trapping procedure (IPIL entry). ZGRD-TKN-BINDTIMESTAMP is the BIND timestamp of the OSI manager or TAPS object file.
Event Messages 1: ZOSI-EVT-INTL-ERR Consideration Both OSI manager and TAPS processes issue this event message.
Event Messages 2: ZOSI-EVT-TRAP 2: ZOSI-EVT-TRAP This is a critical event. The OSI/AS subsystem detected a trap caused by a hardware or software error. The affected OSI/AS process terminates abnormally.
Event Messages 2: ZOSI-EVT-TRAP ZSPI-TKN-ERROR is the standard SPI error token described in the Distributed Systems Management (DSM) Programming Manual. It contains the Guardian 90 subsystem ID in the Z-SSID field and the Guardian 90 trap number in the Z-ERROR field. ZSPI-TKN-PROC-ERR has the value ZGRD-VAL-TRAPOUT. ZGRD-TKN-OBJECTFILE for C-series systems, is the program file name of the OSI manager or TAPS process.
Event Messages 2: ZOSI-EVT-TRAP 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 and, in compatible mode, to the OPRLOG and any $AOPR process. Probable Cause OSI/AS detected a trap caused by a hardware or software error. Recommended Action Contact your Tandem representative. Provide a log of the error. Consideration Both OSI manager and TAPS processes issue this event message.
Event Messages 3: ZOSI-EVT-BKUP-UP 3: ZOSI-EVT-BKUP-UP This is not a critical event. The primary process has successfully started the backup process. Additional Unconditional Tokens ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZOSI-TKN-CPU token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-UINT.
Event Messages 3: ZOSI-EVT-BKUP-UP Consideration Both OSI manager and TAPS processes issue this event message.
Event Messages 4: ZOSI-EVT-BKUP-DOWN 4: ZOSI-EVT-BKUP-DOWN This is a critical event. The primary process detected that the backup process is down. The primary process attempts to create a new backup process unless the backup CPU is down; in that case, it attempts to create a new backup when the CPU is reloaded. Additional Unconditional Tokens ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZOSI-TKN-LOST-CAUSE ZOSI-TKN-CPU* * token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-BOOLEAN.
Event Messages 4: ZOSI-EVT-BKUP-DOWN ZOSI-TKN-LOST-CAUSE is the reason for loss of the backup. It has one of the following values: ZOSI-VAL-CAUSE-STOP ZOSI-VAL-CAUSE-ABEND ZOSI-VAL-CAUSE-CPU-DOWN ZOSI-VAL-CAUSE-UNKWN Backup stopped Backup abended Backup CPU is down Backup process is down; cause unknown ZOSI-TKN-CPU is the backup CPU number that went down. This conditional token is present only if the value of ZOSI-TKN-LOST-CAUSE is ZOSI-VAL-CAUSE-CPU-DOWN.
Event Messages 5: ZOSI-EVT-BKUP-CREATE-FAIL 5: ZOSI-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 try again when the CPU is reloaded. Otherwise, the message indicates that the primary process has exhausted the retry count for starting the backup process.
Event Messages 5: ZOSI-EVT-BKUP-CREATE-FAIL Event-Message Text for D-series systems process-name, Unable To Create BACKUP Process, PROCESS_CREATE_ Error=%error, File=objectfile, Swapvol=swapvol, Priority=priority, CPU=cpu, Name:processname Token Descriptions ZCOM-TKN-SUBJ-PROC is the Guardian 90 process name of the process that caused the event. It is the subject of the message.
Event Messages 5: ZOSI-EVT-BKUP-CREATE-FAIL ZGRD-TKN-CRTPID is the process ID returned by NEWPROCESS or PROCESS_CREATE_. IF ZGRDTKN-CRTPID is 0, no process was created. ZGRD-TKN-PROCESSNAME for C-series systems, is the new process name. ZGRD-TKN-XCPU for D-series systems, is the processor number requested for the backup process. ZGRD-TKN-XPROCESSNAME for D-series systems, is the new process name. ZGRD-TKN-XOBJECTFILE for D-series systems,is the program file name of the OSI manager or TAPS process.
Event Messages 5: ZOSI-EVT-BKUP-CREATE-FAIL Probable Cause OSI/AS reports this event for one of the following reasons: Insufficient resources in backup CPU Insufficient space on swap disk Backup CPU down Recommended Action If the backup CPU is down, it must be reloaded before the backup process can be brought up. Consideration Both OSI manager and TAPS processes issue this event message.
Event Messages 6: ZOSI-EVT-CHKPT-FAIL 6: ZOSI-EVT-CHKPT-FAIL This is a critical event. A checkpoint I/O message returned an error. The primary process stops the backup process and tries to create a new one.
Event Messages 6: ZOSI-EVT-CHKPT-FAIL ZFIL-TKN-FILENAME for C-series systems, is the name of the file on which the error occurred. ZFIL-TKN-XFILENAME for D-series systems, is the name of the file on which the error occurred. ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE, indicating that this is a critical event.
Event Messages 7: ZOSI-EVT-PROC-CREATE-FAIL 7: ZOSI-EVT-PROCCREATE-FAIL This is a critical event. A NEWPROCESSNOWAIT or PROCESS_CREATE_ call issued by the OSI manager process failed to start one of the subsystem processes. The OSI manager process continues to function, but the process that could not be created with NEWPROCESSNOWAIT or PROCESS_CREATE_ remains in the STOPPED state.
Event Messages 7: ZOSI-EVT-PROC-CREATE-FAIL Token Descriptions ZCOM-TKN-SUBJ-PROC is the Guardian 90 process name of the 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 7: ZOSI-EVT-PROC-CREATE-FAIL ZGRD-TKN-XPROCESSNAME for D-series systems, is the new process name. ZGRD-TKN-XOBJECTFILE for D-series systems,is the program file name of the OSI manager process. ZGRD-TKN-XSWAPFILE for D-series systems, is the data swap-file name requested for the 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 8: ZOSI-EVT-SM-ERR 8: ZOSI-EVT-SM-ERR This is not a critical event. The OSI/AS subsystem detected an internal state-machine error. The connection identified in the ZCOM-TKN-SUBJ-SU token has been aborted. Additional Unconditional Tokens ZCOM-TKN-SUBJ-SU ZOSI-TKN-SM* ZOSI-TKN-SM-STATE* ZOSI-TKN-SM-EVT* ZOSI-TKN-SM-ACT* ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-INT.
Event Messages 9: ZOSI-EVT-INIT-L4-SU-OPEN-FAIL 9: ZOSI-EVT-INIT-L4-SUOPEN-FAIL This is not a critical event. The session service could not initiate communication with the specified transport subdevice.
Event Messages 9: ZOSI-EVT-INIT-L4-SU-OPEN-FAIL ZFIL-TKN-XFILENAME for D-series systems, is the name of the TSP subdevice to which access failed. ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-FALSE, indicating that this is not a critical event. 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 and, in compatible mode, to the OPRLOG and any $AOPR process.
Event Messages 10: ZOSI-EVT-ACSE-THLD 10: ZOSI-EVT-ACSE-THLD This is not a critical event. An ACSE network-management counter has reached a predefined threshold. Additional Unconditional Tokens ZCOM-TKN-SUBJ-SERV ZOSI-TKN-ACSE-EVENT ZOSI-TKN-THLD-VAL ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT token-type token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-UINT. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
Event Messages 10: ZOSI-EVT-ACSE-THLD Additional Conditional Tokens (continued) ZOSI-MAP-RESP-AE-TITLE def ZOSI-DDL-AE-TITLE. 02 ZAE-TITLE-TYPE type 02 ZAE-TITLE-FORMAT2. 03 ZAE-QUALIFIER-ISPRESENT type 03 ZAE-QUALIFIER type 03 ZAP-TITLE type end.
Event Messages 10: ZOSI-EVT-ACSE-THLD ZOSI-TKN-ACSE-EVENT indicates which ACSE counter has reached a threshold. The values are as follows: ZOSI-VAL-ACPM-REJECTS-RECV ZOSI-VAL-ACPM-REJECTS-SENT ZOSI-VAL-L6-REJECTS ZOSI-VAL-ACPM-ABORTS-RECV ZOSI-VAL-ACPM-ABORTS-SENT ZOSI-VAL-AP-ABORTS ZOSI-TKN-THLD-VAL is the predefined threshold value that was reached. ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-FALSE, indicating that this is not a critical event.
Event Messages 10: ZOSI-EVT-ACSE-THLD ZOSI-TKN-RESP-AE-TITLE is the application entity title of the responding application entity. ZOSI-TKN-RESP-AP-IID is the application process invocation ID of the responding application entity. ZOSI-TKN-RESP-AE-IID is the application entity invocation ID of the responding application entity. ZOSI-TKN-CALLING-PSEL is the PSEL component of the calling address. ZOSI-TKN-CALLING-SSEL is the SSEL component of the calling address.
Event Messages 10: ZOSI-EVT-ACSE-THLD ZOSI-TKN-RESP-NSAP is the NSAP component of the responding address. ZOSI-TKN-PDU-CONTENTS contains up to 1500 bytes of the application protocol data unit (APDU), minus the user data, that caused the event to be reported. Probable Cause OSI/AS reports this event each time an ACSE threshold is reached. Recommended Action No special action is required. This event is of interest only in applications that monitor threshold events.
Event Messages 11: ZOSI-EVT-L6-THLD 11: ZOSI-EVT-L6-THLD This is not a critical event. A Presentation Layer network-management counter has reached a predefined threshold. Additional Unconditional Tokens ZCOM-TKN-SUBJ-SERV ZOSI-TKN-L6-EVENT ZOSI-TKN-THLD-VAL ZOSI-TKN-REASON-CODE ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT token-type token-type token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-UINT ZSPI-TYP-INT. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
Event Messages 11: ZOSI-EVT-L6-THLD Token Descriptions ZCOM-TKN-SUBJ-SERV is the subject of the event. ZOSI-TKN-L6-EVENT indicates which Presentation Layer counter has reached a threshold. The values are as follows: ZOSI-VAL-CPR-RECV-TRANSIENT ZOSI-VAL-CPR-RECV-PERMANENT ZOSI-VAL-CPR-SENT-PERMANENT ZOSI-VAL-ARP-SENT-PROT-ERR ZOSI-TKN-THLD-VAL is the predefined threshold value that was reached. ZOSI-TKN-REASON-CODE is the reason code that caused the threshold to be reached.
Event Messages 11: ZOSI-EVT-L6-THLD ZOSI-TKN-CALLING-NSAP is the NSAP component of the calling address. ZOSI-TKN-CALLED-PSEL is the PSEL component of the called address. ZOSI-TKN-CALLED-SSEL is the SSEL component of the called address. ZOSI-TKN-CALLED-TSEL is the TSEL component of the called address. ZOSI-TKN-CALLED-NSAP is the NSAP component of the called address. ZOSI-TKN-RESP-PSEL is the PSEL component of the responding address. ZOSI-TKN-RESP-SSEL is the SSEL component of the responding address.
Event Messages 11: ZOSI-EVT-L6-THLD Considerations Thresholds can be adjusted by the OSI subsystem administrator to increase or decrease the frequency of event messages, or to suppress event-message generation entirely. Only the TAPS process issues this event message. Conditional fields are present when the information is available to the code that generates the event. ZOSI-TKN-EVENT-ID is present only when ZOSI-TKN-L6-EVENT is set to ZOSIVAL-ARP-SENT-PROT-ERR.
Event Messages 12: ZOSI-EVT-L5-THLD 12: ZOSI-EVT-L5-THLD This is not a critical event. A Session Layer network-management counter has reached a predefined threshold. Additional Unconditional Tokens ZCOM-TKN-SUBJ-SERV ZOSI-TKN-L5-EVENT ZOSI-TKN-THLD-VAL ZOSI-TKN-PDU-CONTENTS ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT token-type token-type token-type token-type token-type token-type ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-UINT. ZSPI-TYP-STRING. ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN.
Event Messages 12: ZOSI-EVT-L5-THLD Token Descriptions ZCOM-TKN-SUBJ-SERV is the subject of the event. ZOSI-TKN-L5-EVENT indicates which Session Layer counter has reached a threshold. The values are as follows: ZOSI-VAL-RF-RECV-PERMANENT ZOSI-VAL-RF-SENT-PERMANENT ZOSI-VAL-RF-RECV-TEMPORARY ZOSI-VAL-AB-SENT-PROT-ERR ZOSI-TKN-THLD-VAL is the predefined threshold value that was reached.
Event Messages 12: ZOSI-EVT-L5-THLD ZOSI-TKN-CALLED-TSEL is the TSEL component of the called address. ZOSI-TKN-CALLED-NSAP is the NSAP component of the called address. ZOSI-TKN-RESP-SSEL is the SSEL component of the responding address. ZOSI-TKN-RESP-TSEL is the TSEL component of the responding address. ZOSI-TKN-RESP-NSAP is the NSAP component of the responding address. ZOSI-TKN-REASON-CODE is the reason code that caused the threshold to be reached.
Appendix A Errors and Error Lists This appendix presents all the error numbers defined by the OSI/AS subsystem—that is, the values whose symbolic names begin with ZOSI-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 Descriptions of ZOSI Errors are not described here. For more information about these tokens, refer to the Distributed Systems Management (DSM) Programming Manual. Descriptions of ZOSI The the following pages provide descriptions of the errors defined by the OSI/AS Errors subsystem. They are given in ascending order by error number.
Errors and Error Lists 1: ZOSI-ERR-ZGRD-ERR 1: ZOSI-ERR-ZGRD-ERR The OSI/AS subsystem encountered a Guardian 90 error. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZGRD-TKN-OBJECTFILE ZGRD-TKN-PRIORITY ZGRD-TKN-CPU ZGRD-TKN-PROCESSNAME ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST.
Errors and Error Lists 1: ZOSI-ERR-ZGRD-ERR ZSPI-TKN-PROC-ERR identifies the Guardian 90 error that occurred. If the value of this field is ZGRD-VAL-NEWPROCESS, ZGRD-VAL-PROCESS-CREATE, ZGRD-VALNEWPROCESSNOWAIT, or ZGRD-VAL-TRAPOUT, refer to the System Procedure Errors and Messages Manual for descriptions of the other tokens in the error list. If this field has some other value, record the values of all tokens in this error list and the enclosing error list to report to your Tandem representative.
Errors and Error Lists 2: ZOSI-ERR-BOUNDS-ERR 2: ZOSI-ERR-BOUNDS-ERR An internal bounds error occurred in the OSI/AS subsystem. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR is the standard SPI error token, as described in the Distributed Systems Management (DSM) Programming Manual.
Errors and Error Lists 3: ZOSI-ERR-OBJ-ACTV 3: ZOSI-ERR-OBJ-ACTV The command could not be performed because the specified object was in use. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR is the standard SPI error token, as described in the Distributed Systems Management (DSM) Programming Manual.
Errors and Error Lists 4: ZOSI-ERR-UNKWN-SERVR-ERR 4: ZOSI-ERR-UNKWNSERVR-ERR An internal error occurred in the OSI/AS subsystem. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Token Descriptions ZSPI-TKN-ERROR is the standard SPI error token, as described in the Distributed Systems Management (DSM) Programming Manual.
Appendix B Token Codes and Token Maps Table of Token Codes Table B-1 is a summary of all token codes specific to the OSI/AS subsystem (that is, all token codes whose names begin with ZOSI-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 ZOSI-TKN-EVENT-ID has the token number ZOSITNM-EVENT-ID. Table B-1.
Token Codes and Token Maps Table B-1. OSI/AS Token Codes and Token Types (Page 2 of 2) ZOSI-TKN-SM-ACT ZOSI-TKN-SM-EVT ZOSI-TKN-SM-STATE ZOSI-TKN-THLD-VAL ZOSI-TKN-TIME-LAST-REPT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-UINT ZSPI-TYP-TIMESTAMP Table of Token Maps Table B-2 is a summary of all token maps specific to the OSI/AS subsystem (that is, all token maps whose names begin with ZOSI-MAP-). For each token map, the symbolic name of the DDL definition is given.
Token Codes and Token Maps Table B-2.
Appendix C Sample Programs This appendix includes a sample management program for C-series systems that sends commands to the OSI/AS subsystem, four sample event-message filters for users of OSI/AS, and a sample program that retrieves event messages generated by OSI/AS. Source code files for all the examples described in this appendix are provided as part of the OSI/AS software. They reside (by default) in the volume and subvolume $SYSTEM.ZOSIAS.
Sample Programs Management Program Example --SPI TAL definitions ? NOLIST, SOURCE $dsv.zspidef.zSpiTAL ? LIST -Data communications TAL definitions ? NOLIST, SOURCE $dsv.zspidef.zComTAL ? LIST -OSI/AS subsystem-specific TAL definitions ? NOLIST, SOURCE $dsv.zspidef.zOsiTAL ? LIST ? PAGE "Global variables " --- Tandem data communications variables ---- Declare a variable to hold the subsystem ID of the OSI/AS -- subsystem, initializing it with the proper values. -INT .
Sample Programs Management Program Example --------INT INT INT ---INT INT INT ------INT INT INT INT INT INT INT INT the original with any context that we may receive in the response. Our buffers will be the minimum size for communication with the OSI/AS subsystem. We declare the buffer as an array of words, so we must divide the minimum byte count by two. .Spi^Buffer [0: (zOsi^Val^Min^BufLen/2) ]; -- spi request/reply Buffer Minimum size .
Sample Programs Management Program Example --- External declarations for SPI procedures -? NOLIST, SOURCE $system.system.extdecs0( SSGet, ? SSGetTkn, ? SSInit, ? SSMove, ? SSMoveTkn, ? SSNULL, ? SSPut, ? SSPutTkn ) ? LIST ? PAGE "Process Startup Sequence" --------------------------------------------------------------- STARTUP: --GLOBALS: None -INPUT: None -OUTPUT: None --- Purpose: Perform the standard process startup sequence.
Sample Programs Management Program Example INT INT INT .receive^name [0:11] := ["$RECEIVE", 8 * [" rcv^num; count^read; "]]; CALL Open( receive^name, rcv^num ); IF <> THEN CALL Debug; CALL Read( rcv^num, Startup^msg, $LEN( Startup^msg ), Count^Read ); IF <> THEN CALL Debug; CALL Close( rcv^num ); END; -- PROC Startup ? PAGE "Open SCP process" --------------------------------------------------------------- Open^SCP - Open the SCP $ZNET process.
Sample Programs Management Program Example -with Osi^Val^SSID and MAXRESP = -1.
Sample Programs Management Program Example --- The buffer length is the second word in the SPI buffer. -Spi^Buffer [1] := $min ( Spi^Buffer [1], zOsi^Val^Min^BufLen ); Init^Buffer := zSpi^Val^Initial^Buffer; SSErr := SSPutTkn ( Spi^Buffer, zSpi^Tkn^Initial^Position, Init^Buffer ); IF (SSErr <> zSpi^Err^OK) THEN CALL Debug; END; -- PROC Reset^SpiBuf ? PAGE "Send command to OSI/AS Subsystem" --------------------------------------------------------------- SEND^SPICMD - Send command to OSI/AS through SCP.
Sample Programs Management Program Example --GLOBALS: Term^fn -Term^Buf -Osi^Mgr^Name -INPUT: None -OUTPUT: None -------------------------------------------------------------PROC Get^OsiM^Name; BEGIN INT INT INT STRING STRING got^it := zSpi^Val^False; Count^Read; Character^Count; .s^Term^buf; -- string pointer to terminal buffer .end^of^text; -- string pointer to last character -- of terminal text WHILE ( got^it = zSpi^Val^False ) DO BEGIN --- Prompt user for OSI manager name.
Sample Programs Management Program Example END; END; CALL ShiftString (s^term^buf, Character^Count, 0); IF (Character^Count > 0) THEN BEGIN Osi^Mgr^Name[0] := Character^Count; Osi^Mgr^Name[1] ':=' s^Term^buf FOR Character^Count BYTES; S^Mgr^Tkn^Name[10] ':=' Osi^Mgr^Name[1] FOR Osi^Mgr^Name[0] BYTES; got^it := zSpi^Val^True; END; END; -- while -- PROC Get^OsiM^Name ? PAGE "GetResponse^Loop" --------------------------------------------------------------- GETRESPONSE^LOOP - Get responses from OSI/AS conti
Sample Programs Management Program Example zOsi^Val^Min^BufLen BYTES; complete := zSpi^Val^False; WHILE ( complete = zSpi^Val^False ) DO BEGIN -- Send the command to the OSI/AS subsystem. CALL Send^SpiCmd; CALL Reset^SpiBuf; -- Count number of response records in the reply. token^id := zSpi^Tkn^DataList; SSErr := SSGetTkn( Spi^Buffer, zSpi^Tkn^Count, token^id, 1, DataList^Count ); IF (SSErr <> zSpi^Err^OK) THEN CALL Debug; FOR DataList^Index := 1 TO DataList^Count DO BEGIN -- Open the first response list.
Sample Programs Management Program Example END; CALL Write( Term^fn, Objectnm6 [1], Objectnm6 [0] ); -- case -- Count number of OBJNAME tokens in response. token^id := zCom^tkn^ObjName; SSErr := SSGetTkn( Spi^Buffer, zSpi^Tkn^Count, token^id, 1, ObjName^Count ); IF (SSErr <> zSpi^Err^OK) THEN CALL Debug; -- Retrieve the OBJNAME tokens and print them.
Sample Programs Management Program Example -Spi^Buffer ':=' Spi^Buffer^Copy FOR zOsi^Val^Min^BufLen BYTES ELSE -- There is no context token. We are done. -complete := zSpi^Val^True; END; -- while complete = zSpi^Val^False RETURN (RetCode); END; -- PROC GetResponse^Loop; ? PAGE "add L4 profile for class 4 " --------------------------------------------------------------- ADD^L4PFILE4 - Add #L4 PROFILE "TSTPFILE" to the -OSI/AS subsystem.
Sample Programs Management Program Example zSpi^Tkn^Manager, Mgr^Tkn^Name[1] ); IF (SSErr <> zSpi^Err^OK) THEN CALL Debug; SSErr := SSPutTkn( Spi^Buffer, zCom^tkn^ObjName, ObjName ); IF (SSErr <> zSpi^Err^OK) THEN CALL Debug; --- Initialize the PROFILE structure to null values. -SSErr := SSNULL( Add^Prof^L4^map, Add^Prof^L4 ); IF (SSErr <> zSpi^Err^OK) THEN CALL Debug; -- Set structure fields with the following attributes: -CLASS 3, ALTCLASS 0, MULTIPLEX ON, -REXMITTIMEOUT 30.
Sample Programs Management Program Example SSErr := SSGetTkn( Spi^Buffer, zSpi^Tkn^RetCode, RetCode ); CASE RetCode OF BEGIN zCom^Err^FS^Err -> CALL Write( Term^fn, Message4[1], Message4[0] ); OTHERWISE -> CALL Write( Term^fn, Message6[1], Message6[0] ); END; RETURN (RetCode); END ELSE -- unexpected SPI error CALL Debug; END; -- if SSErr <> zSpi^Err^OK -- Get return token.
Sample Programs Management Program Example END; -- Add^L4Pfile4; ? PAGE "ListObjects Subsys " --------------------------------------------------------------- LISTOBJ^SUBSYS - Send LISTOBJECTS SUBSYS command to list -name of OSI manager.
Sample Programs Management Program Example --- LISTOBJ^NULL - Send LISTOBJECTS NULL command to list names -of all objects in this OSI/AS subsystem.
Sample Programs Management Program Example -- Get terminal name and open terminal. CALL MyTerm ( Term^name ); CALL Open ( Term^name, Term^fn ); IF <> THEN GOTO exit; -- Process the startup sequence. CALL Startup; -- Open SCP as the management process. FS^Error := Open^SCP; IF (FS^Error <> 0) THEN GOTO exit; -- Get OSI manager name from terminal. CALL Get^OsiM^Name; -- ADD PROFILE [osimgrp].#L4.
Sample Programs Sample Event-Message Filters Sample EventMessage Filters Note The Event Management Service (EMS) distributor takes in event messages from the subsystems that are 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.
Sample Programs Sample Event-Message Filters PASS; END; Filter Example: OSI/AS Process Started Messages The following filter selects the event messages that reflect “process started” events originating from OSI/AS on system \MYSYS: == File: EXFLT2 == == This EMS filter selects those event messages, == originating from OSI/AS on system \MYSYS, that == reflect "process started" events. == filter procstarted^msgs; begin --initialize subsystem IDs. [#set zosi^val^ssid [zspi^val^tandem].[zspi^ssn^zosi].
Sample Programs Sample Event-Message Filters Filter Example: Internal and State-Machine Errors The following filter selects all event messages that report internal and state-machine errors originating from OSI/AS on system \MYSYS. These event messages should be reported to your Tandem analyst. == File: EXFLT4 == == This EMS filter selects those event messages, == originating from OSI/AS on system \MYSYS, that == report internal and state-machine errors.
Sample Programs Event-Retrieval Example 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 this example is provided as part of the OSI/AS software.
Sample Programs Event-Retrieval Example Example in TAL The following pages give the source code for the event-retrieval program in TAL. --------------------------------------------------------------File: EXEMST1 --This program demonstrates how to retrieve an event -message produced by the OSI/AS subsystem and handle it -appropriately.
Sample Programs Event-Retrieval Example STRUCT default; BEGIN INT vol [0:3]; INT subvol [0:3]; END; STRUCT infile; BEGIN INT vol [0:3]; INT subvol [0:3]; INT name [0:3]; END; STRUCT outfile; BEGIN INT vol [0:3]; INT subvol [0:3]; INT name [0:3]; END; STRUCT parameter; BEGIN STRING bytes[0:99]; END; END; -- Startup^msg INT INT .term^name[0:11]; term; INT INT INT .Distr^name [0:11] := [ 12*[" "] ]; Distr^fn; .Distr^prog^file[0:11] := ["$SYSTEM SYSTEM EMSDIST "]; INT INT SSError; Ems^err; INT STRUCT .
Sample Programs Event-Retrieval Example STRUCT .SPI^Error( zSpi^DDL^Error^def ); ? NoList, Source $SYSTEM.SYSTEM.
Sample Programs Event-Retrieval Example RETURN Error; END; CALL Read( Rcv^Fn, Startup^msg, $LEN( Startup^msg ), Count^Read ); IF <> THEN BEGIN CALL Debug; CALL FileInfo ( Rcv^Fn, Error ); RETURN Error; END; CALL Close( Rcv^Fn ); RETURN 0; END; -- PROC Startup ? PAGE "get^filter^name" --------------------------------------------------------------- GET^FILTER^NAME - Get user input of filter name from the -startup message RUN parameters.
Sample Programs Event-Retrieval Example CALL WriteRead( term, term^buf, text^len, 32, input^len ); IF > THEN -- EOF from terminal CALL Stop ELSE IF < THEN -- Some unusual condition BEGIN -- Check whether to retry IF NOT FileError( Term ) THEN BEGIN CALL Stop; END; END ELSE IF ( input^len > 0 ) THEN BEGIN -- Move user input to filter name. -s^term^buf [input^len] := 0; filter^name^length := FnameExpand ( s^term^buf [0], filt^name, Startup^Msg.
Sample Programs Event-Retrieval Example -- Start the distributor process. -CALL NewProcess( Distr^prog^file, , , , , error, Distr^name ); IF ( ERROR.<0:7> > 0 ) THEN BEGIN CALL Debug; RETURN error; END; --- Open the distributor to write the startup message. -CALL Open( Distr^name, Distr^Fn ); IF <> THEN BEGIN CALL Debug; CALL FileInfo ( Distr^Fn, Error ); RETURN Error; END; --- Write the startup message.
Sample Programs Event-Retrieval Example --- This procedure returns ZSPI^VAL^TRUE or ZSPI^VAL^FALSE, -- depending on whether the GETEVENT response contains an -- error list with the warning token ZEMS^WRN^EOF. -- TRUE indicates that the distributor has read all event -- messages up to the present time. --- input - none -- output - warning -------------------------------------------------------------INT PROC get^warning; BEGIN INT warning; --- Return right away if no error list.
Sample Programs Event-Retrieval Example RETURN ( warning ); END; -- proc get^warning ? PAGE "send^spi^cmd" --------------------------------------------------------------- SEND^SPI^Cmd --- This procedure puts the finishing touches on an SPI -- command that has been prepared by another procedure, -- such as the SPI^Cmd^SET^Source procedure that follows. -- The SEND^SPI^Cmd procedure subsequently sends the command -- to the distributor and checks the response.
Sample Programs Event-Retrieval Example -SSError := SSGetTkn( Spi^Buffer, zSpi^Tkn^RetCode, Ems^err, 1 ); IF ( SSError <> zSpi^Err^OK ) THEN CALL Debug ELSE IF ( Ems^err <> 0 ) THEN BEGIN IF ( Ems^err = zEms^Err^Flt^Load ) OR ( Ems^err = zEms^Err^Flt^Form ) THEN BEGIN --- Separate out the filter-load error, since it -- is common to have a typographical error in the -- filter name.
Sample Programs Event-Retrieval Example --- Place the connect-source-collector token in the buffer. -SSError := SSPutTkn( Spi^Buffer, zEms^Tkn^Connect^Src^Coll, coll^name ); IF ( SSError <> zSpi^Err^OK ) THEN CALL Debug; --- Send the command to the distributor.
Sample Programs Event-Retrieval Example -- Send the command to the distributor. -SSError := send^spi^cmd; RETURN SSError; END; -- proc spi^cmd^load^filter ? PAGE "spi^cmd^set^position" --------------------------------------------------------------- SPI^Cmd^SET^POSITION --- This procedure builds an SPI command that sets the -- position within the log file at which the distributor -- will start to retrieve event messages.
Sample Programs Event-Retrieval Example END; -- proc spi^cmd^set^position ? PAGE "displ^event" --------------------------------------------------------------- DISPL^EVENT --- This procedure displays, at your terminal, the event -- message just retrieved. --- input - event^buf -- output - none -------------------------------------------------------------PROC displ^event( event^buf ); INT .
Sample Programs Event-Retrieval Example actual^len [i] ); IF <> THEN BEGIN IF NOT FileError( term ) THEN CALL Stop; END ELSE Written := zSpi^Val^True; END; -- if actual^len END; END; END; -- for -- proc displ^event ? PAGE "getevent^loop" --------------------------------------------------------------- GetEvent^LOOP --- This procedure consists of a loop to retrieve event -- messages. Each time through the loop, the procedure -- gets an event message and calls DISPL^EVENT to display -- it at your terminal.
Sample Programs Event-Retrieval Example --- Include the EOFSTOP token, which will cause the -- distributor to send an ZEMS^WRN^EOF token when it has -- read all currently available event messages. -ivalue := zSpi^Val^True; SSError := SSPutTkn( Spi^Buffer, zEms^Tkn^EofStop, ivalue ); IF ( SSError <> zSpi^Err^OK ) THEN CALL Debug; --- Save the original command. -Spi^Buffer^Copy ':=' Spi^Buffer FOR $len(Spi^Buffer^Copy) BYTES; --- Begin loop that gets and displays event messages.
Sample Programs Event-Retrieval Example 1 ); IF ( SSError <> zSpi^Err^OK ) THEN CALL Debug; IF ( Ems^err ) THEN CALL Debug; -- Check for EOF warning. IF get^warning THEN RETURN; -- Look in GETEVENT response for a PassVal of 0. passval := -1; SSError := EmsGetTkn( Spi^Buffer, zEms^Tkn^PassVal, passval, 1, , zEms^Val^SSID ); IF ( SSError <> zSpi^Err^OK ) AND ( SSError <> zSpi^Err^MisTkn ) THEN CALL Debug; -- Find event message within the GETEVENT response.
Sample Programs Event-Retrieval Example END; END; -- while -- proc getevent^loop; ? PAGE "dist^intfc" --------------------------------------------------------------zOsi^EMS^Example - Interface to an EMS distributor --This MAIN procedure starts an EMS consumer distributor -and calls procedures that use SPI commands to connect a -source collector, to load a filter, and to position the -distributor within the log files. Then the procedure -calls GetEvent^LOOP to retrieve and process event -messages.
Sample Programs Event-Retrieval Example -- (must open the #ZSPI subdevice). -Distr^Name [4] ':=' "#ZSPI "; CALL Open( Distr^name, Distr^Fn ); IF <> THEN BEGIN CALL FileInfo ( Distr^Fn, Error ); CALL Debug; GOTO Exit; END; --- 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.
Sample Programs Event-Retrieval Example 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/AS 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 Event-Retrieval Example #include "$system.zspidef.ZOSIC" nolist #pragma PAGE "Globals and defines" /* 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 Event-Retrieval Example 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; zosi_val_ssid_def zosi_val_ssid; char coll_name[25] = "$0 char filt_name[25]; "; #pragma PAGE "init_startup()" /* -------- init_startup -----------------------* Recreate the startup structure discarded by C. * C retains the information we need, and it can be accessed * by GETENV().
Sample Programs Event-Retrieval Example * Return: filt_name[] */ void get_filter_name() { int errval; int got_it = FALSE; int len_vol, len_subvol, len_filenm, i; char vol[8], subvol[8], filenm[8]; while ( !got_it ) { retry: printf("\nEnter the filter name ($vol subvol filter)?: "); errval = scanf("%s %s %s", &vol, &subvol, &filenm); len_vol = strlen( &vol[0]); len_subvol = strlen( &subvol[0]); len_filenm = strlen( &filenm[0]); if(( len_vol > 8) || (len_subvol > 8) || (len_filenm > 8)){ printf("Illegal file
Sample Programs Event-Retrieval Example DEBUG(); /* Send the used part to the distributor. */ ccval = WRITEREAD( distr, (int *)spi_buf, used_len, ZEMS_VAL_BUFLEN ); if (ccval != CCE) DEBUG(); /* Reset the buffer length to what was declared for * spi_buf. */ spi_err = SSPUTTKN( (int *)spi_buf, ZSPI_TKN_RESET_BUFFER, (char *)ibuflen ); if (spi_err != ZSPI_ERR_OK) DEBUG(); /* Response is in the buffer--check for return token.
Sample Programs Event-Retrieval Example } #pragma PAGE "spi_cmd_load_filter()" /* ---------- spi_cmd_load_filter --------------------------* Builds an SPI command that loads a filter into the * distributor. */ int spi_cmd_load_filter(void) { /* Initialize spi_buf for distributor CONTROL command. */ spi_err = SSINIT( (int *)spi_buf, ZEMS_VAL_BUFLEN, (int *)&zems_val_ssid, ZSPI_VAL_CMDHDR, ZEMS_CMD_CONTROL ); if (spi_err != ZSPI_ERR_OK) DEBUG(); /* Place load-filter token in buffer.
Sample Programs Event-Retrieval Example movmem(&evt_text_buf[i*EVT_TEXT_LEN], text, actual_len[i]); text[ actual_len[i] ] = 0; /* Add null to conform to * C convention. */ printf("%s\n", text); } } } #pragma PAGE "getevent_loop()" /* ---------- getevent_loop() ------------------------------* This procedure consists of a loop to retrieve event * messages. Each time through the loop, the procedure gets * an event message and calls displ_event to display it at * the terminal.
Sample Programs Event-Retrieval Example event_buf = (EMSBUFDEF *)((char *)(spi_buf) + byteoffset + 2); /* Display the event message at your terminal. */ displ_event( event_buf ); /* Save context token from this GETEVENT response for */ /* the next GETEVENT request. */ spi_err = SSMOVETKN(ZSPI_TKN_CONTEXT, (int *)spi_buf, 1, /* source */ (int *)sav_buf, 1); /* destination */ if (spi_err != ZSPI_ERR_OK) DEBUG(); /* Move the updated command to spi_buf for next time */ /* through the loop.
Sample Programs Event-Retrieval Example if (sav_buf == NULL) DEBUG(); err_buf = (SPIERRDEF *) malloc( sizeof(SPIERRDEF) ); if (err_buf == NULL) DEBUG(); /* Not necessary to open home terminal in C. */ /* Not necessary to read startup message from C. */ /* It is stored in environment pointers. */ /* Initialize to spaces the startup structure areas that * will contain volume and subvolume names to for passing * to NEWPROCESS. */ startup = init_startup(); /* Create a name for the distributor process.
Sample Programs Event-Retrieval Example movmem( zspi_name, distr_qual, 5 ); ccval = OPEN( (int *)distr_proc_name, (int *)&distr ); if (ccval != CCE) { printf(" Open of %s returned non-zero ccval: %d.\n", distr_proc_name,ccval); DEBUG(); } /* Tell collector to use log files as source for * event messages. */ if ((error = spi_cmd_set_source()) != 0) goto eexit; /* Load filter into distributor.
Appendix D Attribute Name Changes Some attribute names were changed in this release (OSI/AS 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 ZOSI-DDL-ALTER-ENTRY-NSAP PREVIOUS FIELD NAME NEW FIELD NAME ZSERVR ZPROF ZL4-SERVR ZL4-PROF def ZOSI-DDL-ALTER-ENTRY-SNPA PREVIOUS FIELD NAME NEW FIELD NAME ZSERVR ZPROF ZL3-SERVR ZL3-PROF def ZOSI-DDL-ALTER-ENTRY-TSEL PREVIOUS FIELD NAME NEW FIELD NAME ZSERVR ZPROF ZL5-SERVR ZL5-PROF def ZOSI-DDL-ALTER-PROC PREVIOUS FIELD NAME NEW FIELD NAME ZSWAPVOL ZSWAP def ZOSI-DDL-ALTER-PROF-L4 PREVIOUS FIELD NAME NEW FIELD NAME ZREXMIT-TIME ZREF-TIME ZINACTV-TIME ZWIN-TI
Attribute Name Changes def ZOSI-DDL-ALTER-SERV-L3 PREVIOUS FIELD NAME NEW FIELD NAME ZX25DISCONN-DELAY-TIME ZPROTO-VSN-2-ALLOWED ZX25DISCONN-DELAY ZVSN2 def ZOSI-DDL-ALTER-SERV-L4 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 ZOSI-DDL-ALTER-SERV-L5 PREVIOUS FIELD
Attribute Name Changes def ZOSI-DDL-INFO-PROC PREVIOUS FIELD NAME NEW FIELD NAME ZSWAPVOL ZSWAP def ZOSI-DDL-INFO-PROF-L4 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 ZOSI-DDL-INFO-PROF-L5 PREVIOUS FIELD NAME NEW FIELD NAME ZPROTO-VSN-1-ALLOWED ZPROTO-VSN-2-ALL
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 LINE command, for NSP processes 5-10 ABORT PROCESS command operational notes 5-10 structure 5-9 tokens in command buffer 5-9/10 tokens in response buffer 5-10 Abort SPDUs See SPDUs, abort ABORT SU command 5-12 operational notes 5-12 structure 5-11 tokens in command buffer 5-11/12 tokens in response buffer 5-12 ABORTING summary state 4-14, 4-15 ACSE counters See also ZAPABORTS and ZACPMASSOCPREJECTS fields not valid for X.
Index ADD PROFILE command example C-1, C-17 operational notes 5-43 structure 5-31/32 tokens in command buffer 5-33/42 tokens in response buffer 5-43 Addresses, required entries in the MIB 5-22 Addressing mode See ZIPX25-SNDCF-1980-ADDR, and ZNETADDR-MODE AE title structure 4-20 Allow-type token 3-8 ALLOWOPENS PROCESS command operational notes 5-45 structure 5-44 tokens in command buffer 5-44/45 tokens in response buffer 5-45 ALTER ENTRY command operational notes 5-53 structure 5-46/47 tokens in command buf
Index ALTER SUBSYS command 5-99 operational notes 5-99 structure 5-97 tokens in command buffer 5-98/99 tokens in response buffer 5-99 API 1-3 APPL ENTRY object 4-6 Application programmatic interface 1-3 Architecture 1-2/7 ASN.
Index Commands building and sending 3-7 control-and-inquiry interface 1-4 discontinuing 3-8 event-management interface 1-6/7 header tokens, table of 5-8 in OSI/AS, list of 1-13/14, 3-4 nonsensitive 5-6 notation used to describe 5-7 numbers for 3-4 object types for, table of 5-1/3 programmatic, overview 1-8, 1-12 sensitive 5-6 sensitive vs.
Index D Data communications definition file 3-2 standard definitions 4-4/15 Data lists 3-7 Data-portion tokens, in OSI/AS event messages 6-2 DBFUP input file 2-2 DDL DEF statements 4-1 definitions and token maps, summary table of B-2/3 Declaring tokens and data items 3-1 Decoding event messages 3-10/11 Decoding response messages 3-9 Definition files 3-1/3 Definitions DDL, and token maps, summary table of B-2/3 EMS standard 4-16 example C-1, C-17, C-22/38 DELETE ENTRY command operational notes 5-101 structu
Index Distributors,EMS C programming example C-39/48 consumer 1-6 Documentation road map xvi DSM definition file 3-1 overview 1-1 Dynamic subdevices 1-10 E Empty response record 3-10 EMS command file to compile filters, example C-20 CONTROL command 3-10 definition file 3-1 event buffer size 3-12 event log 1-6 event management considerations 3-11/12 event management interface 1-6/7 event messages 1-15 event retrieval, example program in C C-39/48 event retrieval, example program in TAL C-22/38 filter exampl
Index ENTRY object (continued) obtaining lists of See LISTOBJECTS ENTRY command overview 1-8 selection hierarchy 5-23 servers and profiles, table of 5-24 specifying null entries 5-25 ZCOM-OBJ-ENTRY token 4-6/7 Errors 1, Guardian 90 A-3/4 2, internal bounds A-5 3, object in use A-6 4, unknown server A-7 error lists 3-7 handling 3-10 lists in event messages 6-3 warnings, comparison to 3-10 ZCOM, list of A-1 Event messages 1, internal error 6-8/10 10, ACSE threshold reached 6-29/33 11, Presentation threshold
Index Event numbers 3-6 Events, critical 3-12 Extensible structured tokens defined by data communications 4-5 in commands 3-8 in responses 3-9 F Fault tolerance of OSI/AS processes 2-4 Fault tolerance of processes 2-2 Field name changes, list of D-1/4 File-system definition file 3-2 standard token definitions 4-17 Filters, EMS compiling, example command file C-20 examples C-18/20 loading 3-10, C-22/38, C-39/48 using 3-12 when to install 2-4 FORBIDOPENS PROCESS command operational notes 5-107 structure 5-10
Index Guardian 90 definition file 3-2 error A-3/4 standard token definitions 4-16 value name definitions 4-17 H Handling errors 3-10 Header tokens 3-1 defined by EMS 4-15 defined by SPI 4-2 in OSI/AS event messages 6-2 table of 5-8 Hierarchy of object types 1-10/11 High PIN processes 1-16 HIGHPIN option in TACL RUN command 2-2 I Indirect-process-name 4-8/9 INFO ENTRY command structure 5-114/115 tokens in command buffer 5-115 tokens in response buffer 5-116/120 INFO PROCESS command operational notes 5-124 s
Index Initial L4 Subdevice ...
Index LISTOBJECTS SERVICE command structure 5-172 tokens in command buffer 5-172/173 tokens in response buffer 5-173 LISTOBJECTS SU command operational notes 5-175 structure 5-174 tokens in command buffer 5-174/175 tokens in response buffer 5-175 LISTOBJECTS SUBSYS command example C-1, C-17 structure 5-176 tokens in command buffer 5-176/177 tokens in response buffer 5-177/178 LISTOPENS PROCESS command operational notes 5-182 structure 5-179/180 tokens in command buffer 5-180 tokens in response buffer 5-180
Index Manager token 4-4 MIB creating 2-2 how the OSI manager process selects information from the MIB 5-22 overview 1-3 relationship to ENTRY objects 1-8 N NAME option in TACL RUN command 2-2 Names command numbers 3-4 definition files 3-2 ENTRY objects 4-6/7 event numbers 3-6 guidelines for, in applications 3-3 null objects 4-7/8 object types 3-5 object-name spec 4-6 objects 3-5 PROCESS objects 4-8/10 PROFILE objects 4-10/11 SERVICE objects 4-11 SU objects 4-11/12 SUBSYS objects 4-12 Network Layer standard
Index NSP processes ABORT command not valid 5-10 ACTIVATE command not valid 5-14 ALLOWOPENS command not valid 5-45 closing and stopping 2-4 defining and starting 2-3/4 FORBIDOPENS command not valid 5-107 installing 2-2 overview 1-2 RESETSTATS command not valid 5-190 START command not valid 5-223 STATISTICS command not valid 5-227 STOP command not valid 5-286 SUSPEND command not valid 5-290 null object obtaining lists of opens See LISTOBJECTS NULL command obtaining version levels See GETVERSION NULL command
Index Object-specs, syntax rules 4-6/13 Objects commands for each type, table of 5-1/3 OSI manager process ADD command not valid 5-30 ALTER command not valid 5-58 DELETE command not valid 5-103 overview 1-2 running interactively 2-2 running programmatically 2-3 startup actions of 2-3 stopping 2-4 OSI Reference Model, layers supported 1-2/7 OSI standards, implemented xvi OSI/AS subsystem architecture 1-2/7 definition file 3-2 flowchart of related manuals xvi management functions provided 1-12 overview of ma
Index PROCESS object aborting See ABORT PROCESS command activating See ACTIVATE command adding See ADD PROCESS command allowing opens to See ALLOWOPENS PROCESS command altering attributes of See ALTER PROCESS command deleting See DELETE PROCESS command name examples 4-9 obtaining configuration information for See INFO PROCESS command obtaining lists of See LISTOBJECTS PROCESS command obtaining lists of opens of See LISTOPENS PROCESS command obtaining statistics from See STATISTICS PROCESS command obtaining
Index Process-name 4-8/10 Processes closing and stopping 2-4 communicating through SCP 2-1 defining and starting 2-3/4 high PIN 1-16 reporting OSI/AS events 6-1 running OSI manager 2-2/3 startup sequence, programming example C-1, C-17, C-22/38, C-39/48 types provided by OSI/AS 1-2 version compatibility 1-16 PROCESS_CREATE_ error, event message 6-18 PROCESS_CREATE_ procedure 2-3 PROFILE object adding See ADD PROFILE command altering attributes of See ALTER PROFILE command deleting See DELETE PROFILE command
Index Programming considerations commands and responses 3-7/10 definition files 3-1/3 event messages 3-10/13 message elements 3-4/7 names in applications 3-3 running an EMS consumer distributor 2-4 running OSI/AS processes 2-2/4 templates and labels 3-3 using SCP 2-1 Protocol-related attributes, value selection by OSI manager process 5-23 R Receiving response messages 3-9 RESETSTATS PROCESS command operational notes 5-190 structure 5-187/188 tokens in command buffer 5-188 tokens in response buffer 5-188/19
Index Responses (continued) records returned by OSI/AS 3-9 response records 3-5 Retrieving event messages 3-10/11 Return token 3-10 RUN command 2-2 S SCF commands, table of 1-13/14 general 1-1 version compatibility 1-21 SCP startup sequence, example C-1, C-17 using for control and inquiry 1-4 using to communicate to OSI/AS 2-1, 2-2/4 version compatibility 1-21 Security command usage 3-10 Sending command messages 3-7 Sensitive commands 3-10, 5-6 Server error A-7 Servers in ENTRY objects, table of 5-24 selec
Index Session Layer standards implemented xvi threshold reached, event message 6-38/40 Simple tokens defined by data communications 4-5, 4-13/15 defined by EMS 4-15 defined by Guardian 90 4-17 defined by SPI 4-2 defined by the file system 4-17 SNPA ENTRY object 4-7 SOURCE statements, example C-1, C-17, C-22/38 SPI commands, table of 1-13/14 definition file 3-1 initializing buffers, programming example C-1, C-17 overview 1-4 standard definitions 4-2/4 SPI programming considerations commands and responses 3-
Index START PROCESS command operational notes 5-223 structure 5-221 tokens in command buffer 5-221/222 tokens in response buffer 5-222 STARTED summary state 4-14, 4-15 Starting processes 2-3/4 STARTING summary state 4-14 Startup message 2-3, C-22/38, C-39/48 State machine error event message 6-26 Static subdevices 1-10 STATISTICS PROCESS command operational notes 5-227 structure 5-224/225 tokens in command buffer 5-225 tokens in response buffer 5-225/227 STATISTICS SERVICE command operational notes 5-246 s
Index STATUS SUBSYS command 5-284 structure 5-281/282 tokens in command buffer 5-282 tokens in response buffer 5-282/284 STOP LINE command, for NSP processes 5-286 STOP PROCESS command operational notes 5-286 structure 5-285 tokens in command buffer 5-285/286 tokens in response buffer 5-286 STOP SU command operational notes 5-288 structure 5-287 tokens in command buffer 5-287/288 tokens in response buffer 5-288 STOPPED summary state 4-14, 4-15, 5-12 Stopping processes 2-4 STOPPING summary state 4-14, 4-15
Index SUBSYS object altering attributes of 5-99 See ALTER SUBSYS command name example 4-13 obtaining configuration information for See INFO SUBSYS command obtaining lists of See LISTOBJECTS SUBSYS command obtaining statistics from See STATISTICS SUBSYS command obtaining status information for 5-284 See STATUS SUBSYS command obtaining version level of 5-113 See GETVERSION SUBSYS command overview 1-8 resetting statistics for See RESETSTATS SUBSYS command ZCOM-OBJ-SUBSYS token 4-12 Summary states PROCESS obje
Index T TACL definition file 3-1 TAL definition file 3-1 Tandem internal tokens 6-3 TAPS processes closing and stopping 2-4 defining and starting 2-3/4 overview 1-2 Templates event-message 3-3 object-name 3-5/6 Thresholds ACSE in STATISTICS SERVICE command 5-244 routing event messages 3-11 TLAM version compatibility 1-21 Tokens allow-type 3-8 commands 3-4 common to all OSI/AS event messages 6-2 defined by data communications 4-4/15 defined by EMS 4-15 defined by file system 4-17 defined by Guardian 90 4-16
Index Tokens (continued) ZEMS simple 4-15 ZFIL simple 4-17 ZGRD simple 4-17 ZSPI simple 4-2 TRACE command operational notes 5-294 structure 5-291 tokens in command buffer 5-292/293 tokens in response buffer 5-293 Transport Layer standards implemented xvi Trap event message 6-11/13 TSEL ENTRY object 4-7 TSP processes ALLOWOPENS command not valid 5-45 closing and stopping 2-4 defining and starting 2-3/4 FORBIDOPENS command not valid 5-107 overview 1-2 RESETSTATS command not valid 5-190 STATISTICS command not
Index W Warnings 3-10 Wild card support ENTRY objects 4-7 null objects 4-8 object names 3-5/6 PROCESS objects 4-9 PROFILE objects 4-10 SERVICE objects 4-11 SU objects 4-12 X X25AM enabling IP 5-43, 5-71, 5-96 version compatibility 1-21 Z ZAARE-ACCEPT-APDUS-RECV field 5-208 ZAARE-ACCEPT-APDUS-SENT field 5-208 ZAARQ-APDUS-RECV field 5-207 ZAARQ-APDUS-SENT field 5-208 ZAARQ-xxx fields ACCEPT-APDUS-RECV 5-245 ACCEPT-APDUS-SENT 5-245 APDUS-RECV 5-245 APDUS-SENT 5-245 ZABSPDURECVNOREASON field 5-197, 5-234 ZABSP
Index ZACPMABORTSSENTTHLD field 5-94, 5-158, 5-206, 5-244 ZACPMASSOCPREJECTS field 5-207, 5-244 ZACPMASSOCPREJECTSTHLD field 5-95, 5-158, 5-207, 5-244 ZACPMREJECTSRECV field 5-205, 5-242 ZACPMREJECTSRECVTHLD field 5-94, 5-157, 5-205, 5-242 ZACPMREJECTSSENT field 5-205, 5-242 ZACPMREJECTSSENTTHLD field 5-94, 5-157, 5-205, 5-243 ZACTIVE-SU field 5-200, 5-237 ZACTIVITY field 5-276 ZAEQUALIFIER field 4-21 QUALIFIER-ISPRESENT field 4-21 TITLE-FORMAT2 field 4-21 TITLE-TYPE field 4-20 ZAE-TITLE field 5-18, 5-49,
Index ZCN-SPDU-RECV field 5-199 ZCN-SPDU-SENT field 5-199 ZCN-xxx fields SPDU-RECV 5-236 SPDU-SENT 5-236 ZCODEFILE field 5-28, 5-56, 5-123 ZCOLL-CPU field 5-262 ZCOLL-PIN field 5-262 ZCOM definition file 3-2 ZCOM definitions 4-4/15 ZCOM-CMDdefinitions, table of 4-4 prefix described 3-4 ZCOM-DDLTRACE-MODIF 5-291 ZCOM-ERREMPT-RSP 3-10 OK 3-10 ZCOM-ERR-xxx errors, list of A-1 ZCOM-EVTCPU-SWITCH 6-4 SUMSTATE-CHG 6-6 table of 6-1 ZCOM-MAPTRACE-MODIF structure 5-291 TRACE-MODIF, considerations for OSI/AS 5-293 Z
Index ZCOM-TKNCAUSE-CPU-SWITCH 4-13 CAUSE-SUMSTATE-CHG 4-13 definitions, table of 4-5 OBJNAME 4-6 OBJTYPE 3-5, 4-6 SUBJ-PROC 4-13 SUBJ-SERV 4-13 SUBJ-SU 4-13 SUBJ-xxx 3-7 XMGR 4-13 ZCOM-VALBUF-LEN 4-18, 4-19 definitions, table of 4-5 HW 4-13 MAX-BUF-LEN 4-19 SUB 5-177 SUB-xxx 5-168 SUMSTATE-xxx 4-14/15 TKOVR 4-13 UNKWN 4-13 ZCOM-xxx, tables of 4-4/5 ZCON-WAIT-TIME field See ZCONN-TIMEOUT field ZCONN-TIMEOUT field 5-41, 5-69, 5-88, 5-135, 5-152 ZCP-PPDU-RECV field 5-204 ZCP-PPDU-SENT field 5-204 ZCP-xxx fie
Index ZCPRPPDURECVTRANSIENTGROUP field 5-201, 5-238 ZCPRPPDURECVTRANSIENTGROUPTHLD field 5-93, 5-156, 5-203, 5-240 ZCPRPPDUSENTNOREASON field 5-201, 5-238 ZCPRPPDUSENTOTHER field 5-202, 5-239 ZCPRPPDUSENTPERMANENTGROUP field 5-202, 5-239 ZCPRPPDUSENTPERMANENTGROUPTHLD field 5-93, 5-157, 5-203, 5-241 ZCPRPPDUSENTTRANSIENTGROUP field 5-201, 5-238 ZCREATE-TIME field 5-262 ZCURR-xxx fields APPL-ENTRIES 5-217, 5-254 L3-PROFS 5-218, 5-255 L4-PROFS 5-218, 5-255 L5-PROFS 5-220, 5-257 NSAP-ENTRIES 5-218, 5-255 NSP-
Index ZEMS-TKNCONSOLE-PRINT 3-11, 4-16, 6-2 CPU 6-2 CRTPID 6-2 definitions, tables of 4-15 EMPHASIS 3-12, 4-16, 6-2 EVENT 3-10 EVENTNUMBER 3-7, 4-16, 6-2 GENTIME 6-2 LOGTIME 6-2 PIN 6-2 SUBJECT-MARK 4-16, 6-2 SYSTEM 6-2 USERID 6-2 ZESIS-xxx fields ENABLE 5-43, 5-71, 5-78, 5-96, 5-136, 5-144, 5-158 ES-CONF-TIME 5-78, 5-144 ES-GROUP-MAC-ADDR 5-78, 5-144 HOLD-TIME 5-83, 5-148 IS-GROUP-MAC-ADDR 5-78, 5-144 NOTIFY-IS 5-79, 5-144 QUERY-RETRY 5-79, 5-145 QUERY-TIME 5-79, 5-145 XSUM 5-79, 5-144 ZEXPEDITED field 5-
Index ZFS-xxx fields CANCEL-REQS 5-189, 5-226 CLOSE-REQS 5-189, 5-226 CONTROL-REQS 5-189, 5-226 CONTROLBUF-REQS 5-189, 5-226 DEVICEINFO-REQS 5-190, 5-226 OPEN-REQS 5-189, 5-226 RESETSYNC-REQS 5-189, 5-226 SETMODE-REQS 5-189, 5-226 SETPARAM-REQS 5-189, 5-226 WRITEREAD-REQS 5-190, 5-227 ZFU-xxx fields ACTIVITY 5-277 CAP-DATA 5-277 DUX 5-276 EXCPT 5-276 EXPEDITED 5-277 HDUX 5-276 MAJOR-SYNC 5-277 MINOR-SYNC 5-277 NEG-REL 5-276 RESYNC 5-277 TYPED-DATA 5-276 ZGRD definition file 3-2 definitions 4-16 ZGRDTKN-xxx
Index ZINBOUND-xxx fields CR-CONF-ERR-THLD 5-88 CR-CONG-THLD 5-88 CR-PROTO-ERR-THLD 5-89 TPDU-PROTO-ERR-THLD 5-89 TPDU-XSUM-ERR-THLD 5-90 ZINITIATOR field 5-270 ZINUSE-OCBS field 5-190, 5-227 ZINUSE-RCBS field 5-190, 5-227 ZIP-X25-SNDCF field 5-71 ZIP-xxx fields DISCARD-ADDR-THLD 5-80, 5-146 DISCARD-CONG-THLD 5-80, 5-146 DISCARD-GEN-THLD 5-80, 5-145 DISCARD-LIFE-THLD 5-80, 5-146 DISCARD-REASM-THLD 5-81, 5-146 DISCARD-UNSUP-THLD 5-81, 5-146 LIFETIME 5-79, 5-145 NULL-LAYER 5-35, 5-43, 5-63, 5-71, 5-77, 5-96,
Index ZLANDFT attribute, altering 5-58 ZLAST-xxx fields ERR 5-273 ERR-SUBCODE 5-273 SL-ERR 5-269 SL-ERR-SOURCE 5-270 SL-ERR-SUBCODE 5-269 ZLOC-ADDR field 5-274 ZLOOPBACK field 5-19, 5-50, 5-118 ZLOOPBACK-ENABLED field 5-278 ZMAJOR-SYNC field 5-275 ZMAX-xxx fields CONNS 5-28, 5-56, 5-123 EVER-APPL-ENTRIES 5-217, 5-254 EVER-L3-PROFS 5-218, 5-255 EVER-L4-PROFS 5-218, 5-255 EVER-L5-PROFS 5-220, 5-257 EVER-NSAP-ENTRIES 5-217, 5-254 EVER-NSP-PROCS 5-217, 5-254 EVER-SNPA-ENTRIES 5-218, 5-255 EVER-TAPS-PROCS 5-217
Index ZNF-xxx fields SPDU-RECV 5-237 SPDU-SENT 5-237 ZNORMAL-MODE field 5-279, 5-280 ZNSAP field 5-17, 5-48, 5-117, 5-270 ZNSAP-LEN field 5-17, 5-48, 5-116, 5-270 ZNSAP-NIBBLE field 5-18, 5-49, 5-118 ZNSP-PROCS field 5-162 ZNSPS-CONFIGED field 5-283 ZNSPS-STARTED field 5-283 ZNUM-ELEMENTS field 4-21 ZOBJ-ID field 4-22 ZOPEN-CNT field 5-261, 5-269, 5-284 ZOPEN-DEPTH field 5-181, 5-185 ZOPEN-FLAGS field 5-181, 5-185 ZOPENER field 5-272 ZOPENER-LEN field 5-272 ZOPENID field 5-181, 5-185 ZOPENS-ALLOWED field 5
Index ZOSI-DDL- (continued) ALTER-SERV-ACSE 5-74, 5-94/95 ALTER-SERV-L3 5-72/73, 5-75/83 ALTER-SERV-L4 5-73, 5-83/91 ALTER-SERV-L5 5-91/92 ALTER-SERV-L6 5-74, 5-93 ALTER-SUBSYS 5-97, 5-98 CHAR12 4-22 CHAR20 4-23 CHAR36 4-23 INFO-ENTRY-APPL 5-114, 5-116/118 INFO-ENTRY-NSAP 5-115, 5-119 INFO-ENTRY-SNPA 5-115, 5-119 INFO-ENTRY-TSEL 5-115, 5-120 INFO-PROC 5-121, 5-123/124, 5-131 INFO-PROF-L3 5-125/126, 5-128 INFO-PROF-L4 5-126, 5-131/135 INFO-PROF-L5 5-126, 5-135 INFO-SERV-ACSE 5-140, 5-157/158 INFO-SERV-L3 5-
Index ZOSI-DDL- (continued) STATUS-SU-ACSE 5-267, 5-279 STATUS-SU-L5 5-266/267, 5-273/278 STATUS-SU-L6 5-267, 5-278 STATUS-SUBSYS 5-281, 5-282/284 summary table of B-2/3 TSEL 4-22 ZOSI-DDL-xxx definitions, table of 4-20 ZOSI-ERRBOUNDS-ERR A-5 OBJ-ACTV A-6 UNKWN-SERVR-ERR A-7 ZGRD-ERR A-3/4 ZOSI-EVTACSE-THLD 6-29/33 BKUP-CREATE-FAIL 6-18/21 BKUP-DOWN 6-16/17 BKUP-UP 6-14/15 CHKPT-FAIL 6-21/22 INIT-L4-SU-OPEN-FAIL 6-27/28 INTL-ERR 6-8/10 L5-THLD 6-38/40 L6-THLD 6-34/37 PROC-CREATE-FAIL 6-23/25 SM-ERR 6-26 ta
Index ZOSI-MAP- (continued) ADD-PROC description 5-27/29 structure 5-26 ADD-PROF-L3 description 5-33/36 structure 5-31 ADD-PROF-L4 description 5-37/41 structure 5-31/32 ADD-PROF-L5 description 5-42 structure 5-32 ALTER-ENTRY-APPL description 5-48/50 structure 5-46 ALTER-ENTRY-NSAP description 5-51 structure 5-46 ALTER-ENTRY-SNPA description 5-51 structure 5-47 ALTER-ENTRY-TSEL description 5-52 structure 5-47 ALTER-PROC description 5-55/57 structure 5-54 ALTER-PROF-L3 description 5-61/65 structure 5-59 ALTE
Index ZOSI-MAP- (continued) ALTER-SERV-L3 description 5-75/83 structure 5-72/73 ALTER-SERV-L4 description 5-83/91 structure 5-73 ALTER-SERV-L5 description 5-91/92 ALTER-SERV-L6 description 5-93 structure 5-74 ALTER-SUBSYS description 5-98 structure 5-97 CALLED-AE-TITLE structure 6-29 CALLING-AE-TITLE structure 6-29 INFO-ENTRY-APPL description 5-116/118 structure 5-114 INFO-ENTRY-NSAP description 5-119 structure 5-115 INFO-ENTRY-SNPA description 5-119 structure 5-115 INFO-ENTRY-TSEL description 5-120 struct
Index ZOSI-MAP- (continued) INFO-SERV-L3 description 5-142/148 structure 5-137/138 INFO-SERV-L4 description 5-148/154 structure 5-138/139 INFO-SERV-L5 description 5-154/156 structure 5-139/140 INFO-SERV-L6 description 5-156/157 structure 5-140 INFO-SUBSYS description 5-161/162 structure 5-160 LISTOP description 5-181/182, 5-185/186 structure 5-179, 5-183 RESP-AE-TITLE structure 6-30 STATS-PROC description 5-189/190, 5-225/227 structure 5-187/188, 5-224 STATS-SERV-ACSE description 5-205/209, 5-242/246 struc
Index ZOSI-MAP- (continued) STATUS-SU description 5-269/273 structure 5-264/266 STATUS-SU-ACSE description 5-279 structure 5-267 STATUS-SU-L5 description 5-273/278 structure 5-266/267 STATUS-SU-L6 description 5-278 structure 5-267 STATUS-SUBSYS description 5-282/284 structure 5-281 summary table of B-2/3 ZOSI-TKNACSE-EVENT 6-31 CALLED-AE-IID 6-31 CALLED-AE-TITLE 6-31 CALLED-AP-IID 6-31 CALLED-NSAP 6-32, 6-36, 6-40 CALLED-PSEL 6-32, 6-36 CALLED-SSEL 6-32, 6-36, 6-39 CALLED-TSEL 6-32, 6-36, 6-40 CALLING-AE-I
Index ZOSI-TKN- (continued) RESP-AP-IID 6-32 RESP-NSAP 6-33, 6-36, 6-40 RESP-PSEL 6-32, 6-36 RESP-SSEL 6-32, 6-36, 6-40 RESP-TSEL 6-32, 6-36, 6-40 SM-xxx 6-26 SUBJ-SU 6-26 summary table of B-1/2 THLD-VAL 6-31, 6-35, 6-39 TIME-LAST-REPT 6-31, 6-35, 6-39 ZOSI-VALAB-SENT-xxx 6-39 ACPM-ABORTS-xxx 6-31 ACPM-AP-ABORTS 6-31 ACPM-REJECTS-xxx 6-31 ACSTATE-xxx 5-279 AE-TITLE-FORMAT0 4-21 AE-TITLE-FORMAT2 4-21 ARP-SENT-xxx 6-35 BUFLEN 3-8, 3-9, 4-18 CAUSE-xxx 6-17 CLASS-xxx 5-38, 5-66, 5-85, 5-132, 5-149 CPR-RECV-xxx
Index ZOSI-VAL- (continued) X25-NETID-xxx 5-34, 5-63, 5-77, 5-129, 5-143 X25CUG-TYPE-xxx 5-36, 5-64, 5-82, 5-130, 5-147 ZOSI-VAL-xxx definitions 4-24 ZOSIDB and ZOSIDB0 files 2-2 ZOUT-MAX-TSDU-SIZE field 5-275 ZOUT-SEGM field 5-275 ZOUTBOUND-CR-CONF-ERR-THLD field 5-153 ZOUTBOUND-CR-ERR-THLD field 5-153 ZOUTBOUND-TPDU-PROTO-ERR-THLD field 5-154 ZOUTBOUND-xxx fields CR-CONF-ERR-THLD 5-89 CR-ERR-THLD 5-89 TPDU-PROTO-ERR-THLD 5-90 ZOWNERID field 5-261, 5-283 ZPASV-MUX field 5-91, 5-154 ZPMSTATE field 5-274, 5
Index ZREG-xxx fields FAIL-ADD-SU-FS 5-219, 5-256 FAIL-ADD-SU-FS-TAPS 5-220, 5-257 FAIL-ADD-SU-SPI 5-219, 5-256 FAIL-ADD-SU-SPI-TAPS 5-220, 5-257 FAIL-INTL 5-220, 5-257 FAIL-L3-PROF 5-220, 5-257 FAIL-L4-PROF 5-220, 5-257 FAIL-L5-PROF 5-220, 5-257 FAIL-LOC-NAME 5-219, 5-256 FAIL-LOC-NSAP 5-219, 5-256 FAIL-LOC-SNPA 5-219, 5-256 FAIL-LOC-TSEL 5-219, 5-256 FAIL-NSP 5-219, 5-256 FAIL-RMT-NAME 5-219, 5-256 FAIL-RMT-NSAP 5-219, 5-256 FAIL-TAPS 5-219, 5-256 FAIL-TSP 5-219, 5-256 REQS-FAIL 5-218, 5-255 REQS-PASS 5-
Index ZRLRE-ACCEPT-APDUS-RECV field 5-208 ZRLRE-ACCEPT-APDUS-SENT field 5-208 ZRLRE-REJECT-APDUS-RECV field 5-208 ZRLRE-REJECT-APDUS-SENT field 5-209 ZRLRE-xxx fields ACCEPT-APDUS-RECV 5-245 ACCEPT-APDUS-SENT 5-246 REJECT-APDUS-RECV 5-246 REJECT-APDUS-SENT 5-246 ZRLRQ-APDUS-RECV field 5-208 ZRLRQ-APDUS-SENT field 5-208 ZRLRQ-xxx fields APDUS-RECV 5-245 APDUS-SENT 5-245 ZRMT-ADDR field 5-274 ZSAMPLE-TMSTP field 5-189, 5-195, 5-201, 5-205, 5-212, 5-216, 5-226, 5-232, 5-238, 5-242, 5-249, 5-253 ZSEND-SECUR fi
Index ZSPI-TKNALLOW-TYPE 3-8 BUFLEN 5-8 CHECKSUM 5-8 COMMAND 3-4, 5-8 CONTEXT 3-9 DATALIST 3-9 definitions, tables of 4-2/3 ERRLIST 3-9 HDRTYPE 5-8, 6-2 header tokens, table of 5-8 LASTERR 5-8 LASTERRCODE 5-8 LASTPOSITION 5-8 MANAGER 4-4 MAX-FIELD-VERSION 5-8, 6-2 MAXRESP 3-9, 5-8 OBJECT-TYPE 3-5, 5-8 POSITION 5-8 RESPONSE-TYPE 3-9 RETCODE 3-10 SERVER-VERSION 5-8 SSID 4-4, 5-8, 6-2 USEDLEN 5-8, 6-2 ZSPI-TYP-xxx definitions, table of 4-3 ZSPI-VAL-xxx definitions, table of 4-3 ZSPIDEF definition files 3-2 ZS
Index ZTRACE-FILE field 5-262 ZTRACE-MASK field 5-261/262 ZTSEL field 5-17, 5-49, 5-117, 5-271 ZTSEL-LEN field 5-17, 5-48, 5-117, 5-271 ZTSP-xxx fields CODEFILE 5-98, 5-162 LAST-FS-ERRCODE 5-272 PROCS 5-162 TCON-STATE-AT-LAST-ERR 5-273 TCON-SUBSTATE-AT-LAST-ERR 5-273 ZTSPS-xxx fields CONFIGED 5-283 STARTED 5-283 ZTTR-TIMEOUT field 5-40, 5-68, 5-87, 5-134, 5-151 ZTWR-TIMEOUT field 5-41, 5-69, 5-87, 5-135, 5-151 ZUSER-ID field 5-272 ZUSERID field 5-181, 5-185 ZVA field 5-274 ZVACT field 5-273 ZVM field 5-274
Index ZX25REMOTENET field 5-34, 5-63, 5-77, 5-129, 5-143 ZX25REVERSECHG field 5-34, 5-62, 5-76, 5-129, 5-142 ZX25RPOA field 5-36, 5-64, 5-82, 5-130, 5-147 ZX25RPOA-DNIC-CNT field 5-36, 5-64, 5-82, 5-131, 5-148 ZX25THRUPUT field 5-35, 5-63, 5-77, 5-129, 5-143 ZX25TRANSIT-DELAY field 5-36, 5-65, 5-82, 5-131, 5-148 ZXDEVNAME field 5-182, 5-262 ZXDEVNAME-LEN field 5-182, 5-186, 5-262 ZXDEVNAMEfield 5-186 ZXNAME field 5-29, 5-57, 5-124 ZXNAME-LEN field 5-29, 5-57, 5-124 ZXSUM field 5-39, 5-67, 5-86, 5-133, 5-15
