HP NonStop TCP/IP Management Programming Manual Abstract This manual is for programmers and describes the control-and-inquiry and Event Management Service (EMS) interfaces available to an application program for communicating with the HP NonStop™ TCP/IP process. Product Version NonStop TCP/IP G05 Supported Release Version Updates (RVUs) This publication supports G05.00 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 31424 Tandem TCP/IP C20 September 1990 111636 Tandem TCP/IP D30 January 1995 114690 Tandem TCP/IP D30 July 1995 137203 Tandem NonStop TCP/IP G05 February 1998 529636-001 NonStop TCP/IP G05 March 2005
HP NonStop TCP/IP Management Programming Manual Glossary Index What’s New in This Manual vii Manual Information vii New and Changed Information Figures Tables viii About This Manual ix Audience ix Organization of This Manual ix Where to Go for More Information Notation Conventions xi xi 1.
3. Elements of SPI Messages (continued) Contents 3. Elements of SPI Messages (continued) Common Syntax Elements for the Subsystem 3-4 Command Numbers 3-4 Object Types 3-5 Object Names 3-5 Object-Name Templates 3-6 Event Numbers 3-7 Subjects of Event Messages 3-7 Tokens 3-8 Constructs Involving Multiple Tokens 3-9 Components of a Command, a Response, or an Event Message 4.
6. Commands and Responses (continued) Contents 6. Commands and Responses (continued) ADD Command 6-8 ALTER Command 6-16 DELETE Command 6-25 GETVERSION Command 6-28 INFO Command 6-31 LISTOBJECTS Command 6-42 LISTOPENS Command 6-45 RESETSTATS Command 6-50 START Command 6-70 STATISTICS Command 6-73 STATUS Command 6-100 STOP Command 6-107 TRACE Command 6-110 7.
7. Event Management (continued) Contents 7.
Figures Contents Figures Figure 1-1. Figure 1-2. Figure 2-1. Relationship of TCP/IP Subsystem to SLSA and X25AM Subsystems 1-5 TCP/IP Subsystem Architecture 1-7 How an Application Fits Into the TCP/IP Subsystem Architecture Tables Table 2-1. Table 2-2. Table 5-1. Table 5-2. Table 5-3. Table 6-1. Table 7-1.
Contents HP NonStop TCP/IP Management Programming Manual—529636-001 vi
What’s New in This Manual Manual Information HP NonStop TCP/IP Management Programming Manual Abstract This manual is for programmers and describes the control-and-inquiry and Event Management Service (EMS) interfaces available to an application program for communicating with the HP NonStop™ TCP/IP process. Product Version NonStop TCP/IP G05 Supported Release Version Updates (RVUs) This publication supports G05.00 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
What’s New in This Manual New and Changed Information New and Changed Information In Section 5, Common Definitions, deleted the reference to the token ZTCI-DDL-MSGMAXBUFFER in Buffer Declarations on page 5-15.
About This Manual The HP NonStop TCP/IP subsystem provides a file-system interface to the TCP, User Datagram Protocol (UDP), and IP layers of the TCP/IP process structure. This manual provides subsystem-specific information for application programmers using the management-programming interfaces to manage the NonStop TCP/IP subsystem. The management-programming interfaces are based on the Subsystem Programmatic Interface (SPI) of Distributed Systems Management (DSM).
Organization of This Manual About This Manual Section Description (page 2 of 2) Section 4, SPI Programming Considerations Describes SPI programming considerations for the TCP/IP subsystem. This description includes information about building the command buffer, canceling commands, receiving and decoding response buffers, error handling, version compatibility, security, dynamic routing, and the relationship of the TCP/IP SUBNET object to the SLSA subsystem and the X25AM LINE object.
Where to Go for More Information About This Manual Where to Go for More Information To use this manual, you should be familiar with HP NonStop system architecture and DSM; have a reading knowledge of DDL; and have a working knowledge of the TCP, IP, UDP, Internet Control Message Protocol (ICMP), and the language in which you are working: TAL, C, COBOL, or TACL. The TCP/IP Configuration and Management Manual is considered the introductory manual for all of the NonStop TCP/IP manuals.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [ , attribute-spec ]... !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program).
Notation for Management Programming Interfaces About This Manual A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list might be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LDEV ldev [ CU %ccu | CU %... ] UP [ (cpu,chan,%ctlr,%unit) ] { } Braces.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
About This Manual Change Bar Notation HP NonStop TCP/IP Management Programming Manual—529636-001 xvi
1 Introduction This section introduces the TCP/IP subsystem and describes management concepts applicable to the TCP/IP subsystem. Some of the concepts discussed are the types of objects controlled by the TCP/IP subsystem and the monitoring and control functions available. Brief Overview of TCP/IP The TCP/IP protocols are a family of data communications protocols that allow communication between heterogeneous systems in a multinetwork environment known as the Internet.
SUBNET Object Introduction Subsystem Control Point (SCP). The PROC object must be a NonStop Kernel named process. A NonStop system can support multiple TCP/IP processes. Each process has a unique IP address and is handled as a separate subsystem. Typically, a NonStop system attached to a TCP/IP network has only one TCP/IP process.
Required Management Functions Introduction gateway that contains a more comprehensive routing table, determines the best path for the datagram. A subnet has at least one route associated with it, but you can add as many routes as resources allow. In addition, routes can be dynamically redirected by the TCP/IP subsystem. For instance, when a SUBNET object enters the STOPPED summary state, any routes associated with that subnet are automatically redirected by the subsystem to another available subnet.
Relationship With Other Subsystems Introduction • Taking remedial action, if necessary, in response to event information previously retrieved Relationship With Other Subsystems The TCP/IP subsystem provides a file-system interface to the TCP, UDP, and IP of the TCP/IP family. TCP or UDP provides services at the Transport Layer (Layer 4 in the OSI model), and IP provides services at the Network Layer (Layer 3). The TCP/IP subsystem relies on the SLSA subsystem for the Link and Physical Layers.
Logical Interface Introduction Figure 1-1. Relationship of TCP/IP Subsystem to SLSA and X25AM Subsystems Processor TCP/IP Applications Socket Library File System Interface SCF QIO Shared Memory Segment LANMAN TCP/IP LANMON LIF filters LAN Drivers, Interrupt handlers (DIHs) Y Fabric X Fabric E4SA or TRSA LIF PIF SAC LIF LIF SAC LIF LIF PIF PIF PIF PIF SAC LIF LIF PIF PIF SAC LIF PIF LAN VST0101.
Ethernet 4 ServerNet Adapter (E4SA) and Token Ring ServerNet Adapter (TRSA) Introduction PORT objects used in systems prior to the ServerNet architecture in the sense that filters are the final destination for data received from the LAN. The NonStop TCP/IP process in NonStop S-series systems registers ARP and IP filters through a LIF.
Subsystem Architecture Introduction an application program to send commands to the subsystem to control the subsystem or to obtain information. • The Event Management Service (EMS) interface, which provides event-management capability to an application program. This interface allows an application program to retrieve event messages previously sent to EMS by the subsystem. Figure 1-2 illustrates the architecture of the TCP/IP subsystem and the various interfaces to the subsystem. Figure 1-2.
Introduction Subsystem Architecture HP NonStop TCP/IP Management Programming Manual—529636-001 1 -8
2 Management Programming You can manage the TCP/IP subsystem interactively or programmatically. For the TCP/IP subsystem, the SCF and ViewPoint provide interactive subsystem management, while the control-and-inquiry and Event Management Service (EMS) interfaces provide programmatic subsystem management. The division of management tasks between operator control and programmatic control depends upon the subsystem configuration environment and your needs as a subsystem user.
Management Programming How a Management Application Fits Into the Architecture subsystem. The subsystem then returns the appropriate response to the application through SCP. This means that the exchange of a command and response between your application and the subsystem is bidirectional and occurs synchronously. The commands available to you for managing the TCP/IP subsystem are listed in Table 2-1 on page 2-4. The EMS interface requires the subsystem to initiate the communication.
Commands Management Programming Figure 2-1.
Commands Management Programming communicate with data communications subsystems in general, see the SPI Common Extensions Manual. Table 2-1.
Commands Management Programming Table 2-2.
Management Programming Event Messages Event Messages An event message describes an anomaly that has occurred in a subsystem, such as a hardware or software error. All event messages are in an SPI message format. All event messages issued by the TCP/IP subsystem are sent to the EMS collector process ($0). These event messages are then placed into the user-specified log files.
Management Programming Communicating With the TCP/IP Subsystem 5. Check for error codes and handle any errors. 6. Decode the response. 7. Take appropriate action and return to Step 2, if necessary. 8. Terminate communication with the SCP or the EMS distributor process. All data communications subsystems must use the same message protocol for communicating with SCP. For details on this protocol, see the SPI Common Extensions Manual and the SPI Programming Manual.
Management Programming Communicating With the TCP/IP Subsystem HP NonStop TCP/IP Management Programming Manual—529636-001 2 -8
3 Elements of SPI Messages The SPI procedures facilitate communication between a management application and the TCP/IP subsystem. These procedures allow a management application to build commands in an SPI message format to be sent through SCP to the subsystem. These procedures also allow a management application to decode the responses from the subsystem that have been sent through SCP in an SPI message format.
Definition Files Elements of SPI Messages To include the definition files in your management application, use the mechanism that is appropriate for the programming language in which the application is written. The mechanisms are: • • • • In TAL, use the $SOURCE compiler directive to include the definition files in your program. In C, use the #INCLUDE compiler directive to include the definition files in your program. In COBOL, use COPY statements to copy the definition files into your program.
Naming Rules and Guidelines for Applications Elements of SPI Messages An example of the definition files needed by a TCP/IP application written in C that retrieves event messages is: ZSPIDEF.ZSPIC SPI definitions ZSPIDEF.ZEMSC EMS definitions ZSPIDEF.ZCOMC Data communications definitions ZSPIDEF.ZTCIC TCP/IP definitions An example of the definition files needed by a TCP/IP application written in COBOL that retrieves event messages is: ZSPIDEF.ZSPICOB SPI definitions ZSPIDEF.
Common Syntax Elements for the Subsystem Elements of SPI Messages by HP, do not begin any name you define in your application with uppercase or lowercase Z. Common Syntax Elements for the Subsystem The remainder of this section contains subsystem-specific information about syntax elements of commands, responses, and event messages. These elements are in token form and are referred to by their symbolic names.
Elements of SPI Messages Object Types Object Types Object-type numbers represent the object type (or class) of an object. The value of an object-type number is subsystem-specific and has a symbolic name. The symbolic name is of the form ZCOM-OBJ-type, where type identifies the object type. For example, ZCOM-OBJ-SUBNET identifies the subnet object type in all data communications subsystems, including the TCP/IP subsystem. Note that object-type numbers are part of the header of each command and response.
Elements of SPI Messages Object-Name Templates process is $ZTC0. If the process name is more than four characters long, the process cannot be accessed from remote systems. Note. In the TCP/IP subsystem, a TCP/IP process can have more than one IP address associated with it. However, each process must have a NonStop OS process name, and each IP address must be unique within the network. (For more information about IP addresses, see the TCP/IP Configuration and Management Manual.
Elements of SPI Messages Event Numbers You can use wild-card characters in any combination. You can use object-name templates in these commands: • • • • • • • • • ABORT DELETE INFO LISTOBJECTS RESETSTATS START STATISTICS STATUS STOP Note that object-name templates cannot be specified for the PROC object type. There is only one PROC object, and it must be fully specified. Event Numbers Event numbers identify event messages issued by the TCP/IP subsystem.
Elements of SPI Messages Tokens Tokens The TCP/IP subsystem uses tokens for parameters and responses to commands, and for elements of event messages. Each token has a token code and token value associated with it. The token code is the identifying tag that programs use to refer to the token by name. The token value is the actual data item that is assigned to the token code.
Elements of SPI Messages Constructs Involving Multiple Tokens value names. For more information on the form of these predefined value names, see Predefined Value Names on page 3-9. Note that extensible structured tokens do not appear in any event message issued by the TCP/IP subsystem. For more information on all the token maps defined by the TCP/IP subsystem, see Section 5, Common Definitions.
Elements of SPI Messages Components of a Command, a Response, or an Event Message For details on these two constructs, see the SPI Programming Manual. Components of a Command, a Response, or an Event Message For general information about the components of a command, a response, or an event message, see the SPI Common Extensions Manual. For information about the tokens associated with each TCP/IP command, response, and event message, see Section 6, Commands and Responses, and Section 7, Event Management.
4 SPI Programming Considerations The SPI Common Extensions Manual discusses general programming considerations for writing applications that use the SPI to communicate with data communications subsystems like the TCP/IP subsystem. This section discusses SPI programming considerations specific to the TCP/IP subsystem. Building the Command Buffer The following programming considerations apply when an application builds the command buffer for a TCP/IP command.
SPI Programming Considerations Discontinuing a Command in Progress Discontinuing a Command in Progress General programming considerations for discontinuing a command in progress are discussed in the SPI Common Extensions Manual. The TCP/IP subsystem supports the use of the token ZSPI-TKN-ALLOW-TYPE, which allows an application to specify, in a command operating on multiple objects, whether this subsystem should continue immediately to the next object if an operation failed on the previous object.
SPI Programming Considerations Error Handling Error Handling General programming considerations for handling errors that occur when using the management-programming interfaces are discussed in the SPI Common Extensions Manual. In the programmatic control-and-inquiry interface to the TCP/IP subsystem, there are two values for the return token (ZSPI-TKN-RETCODE) that indicate that the response record does not contain an error list. One value, ZCOM-ERR-OK, means that no error or warning occurred.
SPI Programming Considerations Relationship to X25AM LINE Object HP NonStop TCP/IP Management Programming Manual—529636-001 4 -4
5 Common Definitions The management-programming interfaces to the TCP/IP subsystem use definitions from four sources: SPI standard definitions, EMS standard definitions, data communications standard definitions, and TCP/IP subsystem-specific definitions. Many of the definitions are used in multiple commands, responses, event messages, or error lists. This section contains general information that applies to all uses of the common definitions in the interfaces to the TCP/IP subsystem.
SPI Standard Definitions Common Definitions Table 5-1.
Common Definitions SPI Standard Definitions ZSPI-TKN-ALLOW-TYPE within a command buffer indicates the conditions under which processing of a set of objects will continue. This token applies to only those commands that accept object-name templates. The ALLOW-TYPE token controls whether the subsystem continues to the next object of a set when there is an error or a warning during processing of an object. It does not control the response when the tokens within a command message are incorrect or missing.
Common Definitions SPI Standard Definitions been specified for a command or the NULL object has been specified for the LISTOBJECTS command. The server places information in this token, which the server requires to continue execution of the command at the next object. When a requester receives a response containing the context token, the requester copies the context token into a duplicate of the original command message and sends this command message to the server.
Common Definitions SPI Standard Definitions specific error numbers described in Appendix A, Error Numbers and Error Lists. This token is always present in an error list. ZSPI-TKN-HDRTYPE indicates whether the SPI buffer is for an event message or a command. If the buffer is for a command, the value of this token is ZSPI-VAL-CMDHDR; if the buffer is for an event, the value of this token is ZSPI-VAL-EVTHDR.
Common Definitions SPI Standard Definitions Note that if the empty response (ZCOM-ERR-EMPT-RSP) is returned, the value of this token is nonzero, although the command has been completed successfully. If the command was not completed successfully, the value of this token indicates the reason the command failed. The meaning of each error number can be subsystem-specific and possibly command-specific.
EMS Standard Definitions Common Definitions value is compared with the count-read value supplied by the file system. If the value of ZSPI-TKN-USEDLEN is greater than the count-read value, then the TCP/IP subsystem rejects the command because the command was too long. ZSPI-VAL-CMDHDR indicates that the SPI buffer is for a command. It is one of the two possible values of the ZSPI-TKN-HDRTYPE token. ZSPI-VAL-EVTHDR indicates that the SPI buffer is for an event message.
Common Definitions EMS Standard Definitions Table 5-2. EMS Standard Definitions (page 2 of 2) ZEMS-TKN-CRTPID ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-GENTIME ZEMS-TKN-LOGTIME ZEMS-TKN-PIN ZEMS-TKN-SYSTEM ZEMS-TKN-USERID EMS standard definitions specific to the TCP/IP subsystem are described below. ZEMS-TKN-CONSOLE-PRINT specifies whether the event message in which it appears is processed by the compatibility distributor. The value of this token for the TCP/IP subsystem is ZSPI-VAL-TRUE.
Common Definitions Data Communications Standard Definitions ZEMS-TKN-LOGTIME is the time, in GMT, that the collector wrote the event message to its log files. ZEMS-TKN-PIN is the process identification number (PIN) of the subsystem that reported the event. ZEMS-TKN-SUBJECT-MARK indicates that the token that follows is the subject token. The TCP/IP subsystem uses two subject tokens in event messages: ZCOM-TKN-SUBJ-PROC and ZCOM-TKN-SUBJ-SUBNET. For more details, see Section 7, Event Management.
Common Definitions Data Communications Standard Definitions Table 5-3.
Common Definitions Data Communications Standard Definitions ZCOM-MAP-REQID is legally specified, SCP performs a security check based on the user ID included in the token. The contents of the token are: ZCOM-MAP-REQID def ZCOM-MAP-REQID. 02 ZCRTPID 02 ZPAID end. type ZSPI-DDL-CRTPID. type ZSPI-DDL-INT. ZCOM-MAP-TRACE-MODIF is the extensible structured token sent in the TRACE command by the requester.
Common Definitions Data Communications Standard Definitions ZCOM-OBJ-SUBNET is the point of attachment for the Internet Protocol (IP) Layer through which the IP Layer can send or receive data. The valid summary states are STARTED and STOPPED. ZCOM-TKN-CAUSE-SUMSTATE-CHG is an enumerated value that indicates the reason the summary state of an object has changed. This token is returned in the event message ZTCI-EVT-SUMSTATECHG. For details about the event message, see Section 7, Event Management.
Common Definitions Data Communications Standard Definitions and is unique within a process. As many as eight subnets can be added to one TCP/IP process. The NULL object has no object name. The object name of the PROC object is the object name of the TCP/IP process. ZCOM-TKN-OBJSTATE is the summary state of a subnet after a summary-state change has taken place. This token is returned in the event message ZTCI-EVT-SUMSTATE-CHG. For details on this event message, see Section 7, Event Management.
Common Definitions Common Definitions for the TCP/IP Subsystem ZCOM-TKN-SUBJ-SUBNET indicates the name of the TCP/IP subnet that is the subject of an event message. ZCOM-TKN-TRACE-OPT indicates what items are to be traced by the TRACE command. For information on the possible values of this token, see the TRACE Command on page 6-110. The SCP creates a bit mask from the trace options specified and sends it to the TCP/IP subsystem.
Common Definitions Buffer Declarations Buffer Declarations The TCP/IP subsystem provides the following buffer declarations for message buffers that can be used with the SPI procedures. All applications should use one of these declarations for a buffer of the recommended size. ZTCI-DDL-MSG-BUFFER is a message buffer whose size is the size recommended for command messages and for responses in which each response message contains a single response record. DEF zTCI-ddl-msg-buffer.
Common Definitions TCP/IP Predefined Token and Field Values ZTCI-TYP-TRACE defines the token type of the values of the ZCOM-TKN-TRACE-OPT token (the TRACE command options) as enumerated values. ZTCI-TYP-XFER defines the token type of the values of the ZTCI-TKN-XFER-UOW token as enumerated values.
Common Definitions TCP/IP Predefined Token and Field Values (ZTCI-VAL-CAUSE-) ERR, OP, and RECOV are the possible values of the token ZCOM-TKN-CAUSE-SUMSTATE-CHG in the event message ZTCI-EVT-SUMSTATE-CHG. These values indicate the cause of the summary state change for an object. For more information, see Section 7, Event Management.
TCP/IP Simple Tokens Common Definitions (ZTCI-VAL-TCP-STATE-) CLOSING, CLOSE-WAIT, ESTAB, FIN-WAIT-1, FIN-WAIT-2, LAST-ACK, LISTEN, SYNC-RECV, SYNC-SENT, and TIMEWAIT are the possible values of the field ZNET-STATUS-STATE in the ZTCI-MAP-STATUS-PROTO extensible structured token. For more details, see STATUS Command on page 6-100.
TCP/IP Tokens in Error Lists Common Definitions These tokens are described with the commands and responses in which they appear. For more information, see Section 7, Event Management. TCP/IP Tokens in Error Lists The TCP/IP subsystem returns standard error lists and does not define any subsystem-specific tokens that are found in error lists. The error numbers defined by the NonStop TCP/IP subsystem are described in Appendix A, Error Numbers and Error Lists.
Common Definitions TCP/IP Tokens in Event Messages HP NonStop TCP/IP Management Programming Manual—529636-001 5- 20
6 Commands and Responses This section describes each of the commands and responses in the programmatic control-and-inquiry interface to the TCP/IP subsystem. Each description includes the syntax, object types, command tokens, response tokens, and operational notes associated with the commands. In this section, command numbers, types, tokens, and values are represented in DDL. For a brief explanation of DDL as it applies to SPI, see the SPI Programming Manual.
Sensitive and Nonsensitive Commands Commands and Responses The TCP/IP subsystem accepts the PROC object type only in these control-and-inquiry interface commands: ALTER RESETSTATS GETVERSION STATISTICS INFO STATUS LISTOPENS TRACE The TCP/IP subsystem accepts the SUBNET object type only in these control-and-inquiry interface commands: ABORT RESETSTATS ADD START ALTER STATISTICS DELETE STATUS INFO STOP LISTOBJECTS TRACE The TCP/IP subsystem accepts the ROUTE object type only in these con
Sensitive and Nonsensitive Commands Commands and Responses The sensitive commands available to a TCP/IP subsystem user are: ABORT RESETSTATS ADD START ALTER STOP DELETE TRACE The nonsensitive commands available to a TCP/IP subsystem user are: GETVERSION LISTOPENS INFO STATISTICS LISTOBJECTS STATUS Table 6-1.
Command Descriptions Commands and Responses Table 6-1. Commands and Their Symbolic Names (page 2 of 2) Command Symbolic Name of Command Symbolic Name of Object STATISTICS ZCOM-CMD-STATISTICS ZCOM-OBJ-PROC ZCOM-OBJ-ROUTE ZCOM-OBJ-SUBNET STATUS ZCOM-CMD-STATUS ZCOM-OBJ-PROC ZCOM-OBJ-ROUTE ZCOM-OBJ-SUBNET STOP ZCOM-CMD-STOP ZCOM-OBJ-ROUTE ZCOM-OBJ-SUBNET TRACE ZCOM-CMD-TRACE ZCOM-OBJ-PROC ZCOM-OBJ-SUBNET Command Descriptions This section describes each command and its response in detail.
ABORT Command Commands and Responses whether or not the token or field must be or is always present in the command, and other dependencies. For a description of the notation scheme, see Notation Conventions on page xi. Error lists are indicated in the box by following the token ZSPI-TKN-ERRLIST by an ellipsis (...) and the token ZSPI-TKN-ENDLIST.
ABORT Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-SSID ZSPI-TKN-SERVER-VERSION ZSPI-TKN-DATALIST ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-SSID. ZSPI-TYP-UINT. ZSPI-TYP-LIST. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. !{} !{} !... !{} !{} !{} !... token-type ZSPI-TYP-SSCTL.
Commands and Responses ABORT Command ZSPI-TKN-DATALIST indicates the beginning of a data list. The ZSPI-TKN-MAXRESP token must have a value other than 0 for data lists to be included in the response. For more details, see SPI Standard Definitions on page 5-1. ZCOM-TKN-OBJNAME specifies the name of a TCP/IP subnet or route terminated by the command. Unless there is an error that prevents the ABORT command from being attempted at all, this token is present in every response record.
Commands and Responses ADD Command ZCOM-ERR-CMD-TOO-LARGE (-8) ZCOM-ERR-CMD-NOT-SUPP (-5) ZSPI-TKN-ERRLIST indicates the beginning of an error list. Within the error list, the object that experienced the error is listed. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-ENDLIST indicates the end of a data list or an error list. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-CONTEXT specifies whether there are more response messages to be received for a response.
Commands and Responses ADD Command does not exceed the limit defined for each object type. If either of these checks fails, the TCP/IP subsystem returns an error. The maximum number of subnets you can add is 17 (4 Ethernet, 8 SNAP (4 token ring and 4 Ethernet), 4 X.25, and 1 loopback). Adding routes is optional because the Note. For information on NonStop availability considerations, see the TCP/IP Configuration and Management Manual. TCP/IP subsystem automatically adds a route when you add a subnet.
ADD Command Commands and Responses Tokens in Command Buffer ZSPI-TKN-SSID ZTCI-MAP-ADD-SUBNET token-type ZSPI-TYP-SSID. !{} !{A} !OBJ-SUBNET def ZTCI-DDL-ADD-SUBNET. 02 ZTYPE 02 ZIP-ADDR 02 ZIOPNAME 02 ZSU-NAME-IP 02 ZSU-NAME 02 ZFORCE-QIO-IP 02 ZFORCE-QIO 02 ZUSE-IRDP-IP 02 ZUSE-IRDP end. type type type type type type type type type ZTCI-MAP-ADD-ROUTE !{A} !OBJ-ROUTE def ZTCI-DDL-ADD-ROUTE. 02 ZDEST-IP-ADDR 02 ZGW-IP-ADDR 02 ZIF-HOST end. type ZSPI-DDL-INT2. type ZSPI-DDL-INT2.
Commands and Responses ADD Command Tokens in Command Buffer ZSPI-TKN-SSID specifies the subsystem ID, which your management application must pass to SSINIT. This token is described in SPI Standard Definitions on page 5-1, and in the SPI Programming Manual. ZTCI-MAP-ADD-SUBNET is the extensible structured token that defines the configurable attributes for a subnet to be added. It has the token number ZTCI-TNM-ADD-SUBNET and the DDL definition ZTCI-DDL-ADD-SUBNET.
Commands and Responses ADD Command ZIOPNAME is a 32-byte internal file name that specifies the name of the SLSA LIF or the X25AM device with which the subnet interfaces. The TCP/IP subsystem automatically adds a route with a destination address equal to the value specified in the network portion of the ZIP-ADDR field converted to its broadcast form, and a gateway address equal to the value specified as the IP address of the subnet in the ZIP-ADDR field whenever a subnet is added. Note.
Commands and Responses ADD Command indicate either a single host that can be reached through the gateway specified in the ZGW-IP-ADDR field, an entire network that can be reached through the gateway specified in the ZGW-IP-ADDR field, or that the ZGW-IP-ADDR field that follows is the default gateway. To specify a host, specify the complete IP address. To specify a network, assign the local portion of the IP address a value of zero.
Commands and Responses ADD Command The fields in the ZTCI-MAP-ADD-ADDRMAP token are: ZIP-ADDR is an integer that specifies the Internet address in dotted decimal format. An Internet address is a 4-octet (32-bit) numeric value identifying a particular network (network address portion) and a local host on that network (local address portion) as defined in RFC1010. 25 address table. ZX121-ADDR is a 16-character string that specifies the X.25 address.
Commands and Responses ADD Command ZSPI-TKN-RETCODE specifies whether the command has been completed successfully. The value of this token remains zero (ZCOM-ERR-OK) when the command is completed successfully with or without a warning. If the command is not completed successfully, the value of this token indicates the reason the command failed. Always check the contents of the error list to determine the token or value in error.
Commands and Responses ALTER Command ZSPI-TKN-ERRLIST indicates the beginning of an error list. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-ENDLIST indicates the end of a data list or an error list. For more details, see SPI Standard Definitions on page 5-1. Operational Notes • • • • ADD is a sensitive command. When the ADD command is successfully completed, the subnet or route is placed in the STOPPED summary state.
ALTER Command Commands and Responses Object Type ZCOM-OBJ-PROC or ZCOM-OBJ-SUBNET or ZCOM-OBJ-ADDRMAP Tokens in Command Buffer ZSPI-TKN-SSID ZTCI-MAP-ALTER-ADDRMAP token-type ZSPI-TYP-SSID. def ZTCI-DDL-ALTER-ADDRMAP 02 02 02 02 end. ZIP-ADDR-IP ZIP-ADDR ZX121-ADDR-IP ZX121-ADDR def ZTCI-DDL-ALTER-PROC. 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.
ALTER Command Commands and Responses ZTCI-MAP-ALTER-SUBNET def ZTCI-DDL-ALTER-SUBNET. 02 02 02 02 02 02 02 02 ZIP-ADDR-IP ZIP-ADDR ZSUBNET-MASK-IP ZSUBNET-MASK ZSU-NAME-IP ZSU-NAME ZUSE-IRDP-IP ZUSE-IRDP !{A} !OBJ-SUBNET !Specify at least one set !of field values. type ZSPI-DDL-BOOLEAN. type ZSPI-DDL-INT2. type ZSPI-DDL-BOOLEAN. type ZSPI-DDL-INT2. type ZSPI-DDL-BOOLEAN. type ZSPI-DDL-CHAR8. type ZSPI-DDL-BOOLEAN. type ZSPI-DDL-BOOLEAN. end.
Commands and Responses ALTER Command must be specified if the ALTER command is to be effective. The fields in the ZTCI-MAP-ALTER-PROC extensible structured token are: Zxxx-IP is a Boolean variable that specifies whether the succeeding field is to be altered, where xxx specifies the attribute field. The possible values are: ZSPI-VAL-TRUE indicates that the succeeding attribute field is to be altered. ZSPI-VAL-FALSE indicates that the succeeding attribute field is not to be altered.
Commands and Responses ALTER Command ZSPI-VAL-TRUE specifies that an ACK for a TCP packet should be delayed until the TCP receive window is completely filled, or one interval as defined by ZDELAY-ACKS-TIME has expired, whichever occurs first. By delaying the ACK, more than one packet can be acknowledged with a single ACK, thereby reducing network traffic. This is the default. If this value is set, see the ZDELAY-ACKS-TIME field for the time interval between ACKs.
Commands and Responses ALTER Command ZTCP-KEEPINTVL is an integer that specifies the time interval in seconds between retransmissions of unacknowledged keep-alive packets. The default is 45 seconds. The range is 10 through 1260 seconds. ZDEBUG-ENABLE is a Boolean variable that specifies whether the debug option will be enabled. This option is used internally by HP Support and Development personnel to enable the display of more TCP internal information for debugging purposes.
Commands and Responses ALTER Command Zxxx-IP is a Boolean variable that specifies whether the succeeding field is to be altered, where xxx specifies the attribute field. The possible values are: ZSPI-VAL-TRUE indicates that the succeeding attribute field is to be altered. ZSPI-VAL-FALSE indicates that the succeeding attribute field is not to be altered. ZIP-ADDR is a 32-bit integer that specifies the address of the subnet or the loopback address. Either value is specified as an IP address.
Commands and Responses ALTER Command ZCOM-TKN-OBJNAME specifies the process or subnet to be altered. Your application must provide this token in the command. The object name cannot be an object-name template. This token is described more fully in Data Communications Standard Definitions on page 5-9. (ZSPI-TKN-) MAXRESP and COMMENT are standard SPI tokens that your application can provide. These tokens are described in SPI Standard Definitions on page 5-1.
Commands and Responses ALTER Command If the command is not completed successfully, the value of this token indicates the reason the command failed. Always check the contents of the error list to determine the token or value in error. For details on the ZCOM return codes, see the SPI Common Extensions Manual. For details on the ZTCI return codes, see Appendix A, Error Numbers and Error Lists.
DELETE Command Commands and Responses DELETE Command The DELETE command removes subnets and routes from the TCP/IP subsystem. You cannot delete a process. When using the DELETE command, the subnet(s) or route(s) to be deleted must be in the STOPPED summary state. In addition, when your management application issues the DELETE command, the TCP/IP subsystem checks for object-name templates. For more information on using object-name templates, see Object-Name Templates on page 3-6.
Commands and Responses DELETE Command ZCOM-TKN-OBJNAME specifies the subnet or route to be deleted. Your application must provide this token in the command. The object name can include wild-card characters. Using wild-card characters allows the command to affect multiple objects. This token is described more fully in Data Communications Standard Definitions on page 5-9. (ZSPI-TKN-) MAXRESP, CONTEXT, ALLOW-TYPE, and COMMENT are standard SPI tokens that your application can provide.
Commands and Responses DELETE Command If the command was not completed successfully, the value of this token indicates the reason the command failed. Always check the contents of the error list to determine the token or value in error. For details on the return codes, see the SPI Common Extensions Manual.
GETVERSION Command Commands and Responses • To add subnets or routes, use the ADD command. GETVERSION Command The GETVERSION command causes the TCP/IP subsystem to return its server version and server-banner string. The server-banner string reflects the product name, product number, release date, and the date the TCP/IP code was compiled. The string can be a maximum of 50 bytes in length. Your management application can issue the GETVERSION command with the NULL or PROC object type.
Commands and Responses GETVERSION Command Tokens in Command Buffer ZSPI-TKN-SSID specifies the subsystem ID, which your management application must pass to SSINIT. This token is described in SPI Standard Definitions on page 5-1, and in the SPI Programming Manual. ZCOM-TKN-OBJNAME specifies the name of the TCP/IP process to return the version information. Your application must provide this token only if the value ZCOM-OBJ-PROC has been specified.
Commands and Responses GETVERSION Command ZCOM-TKN-OBJTYPE specifies the type of object for which information was requested. The value of this token can be ZCOM-OBJ-PROC or ZCOM-OBJ-NULL. For more details, see Data Communications Standard Definitions on page 5-9. ZSPI-TKN-RETCODE specifies whether the command has been completed successfully. The value of this token remains zero (ZCOM-ERR-OK) when the command is completed successfully with or without a warning.
INFO Command Commands and Responses • The GETVERSION command is valid only for the PROC or NULL objects. INFO Command The INFO command causes the TCP/IP subsystem to return the values of the configurable attributes of the specified object(s). These values are returned in the ZTCI-MAP-INFO-PROC, ZTCI-MAP-INFO-SUBNET, and ZTCI-MAP-INFO-ROUTE extensible structured tokens. When your management application issues the INFO command for a subnet or route, the subsystem checks for an object-name template.
INFO Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-SSID ZSPI-TKN-SERVER-VERSION ZSPI-TKN-DATALIST ZTCI-MAP-INFO-PROC token-type ZSPI-TYP-SSID. token-type ZSPI-TYP-UINT. token-type ZSPI-TYP-LIST. def ZTCI-DDL-INFO-PROC.
INFO Command Commands and Responses ZTCI-MAP-INFO-SUBNET !{A} !OBJ-SUBNET def ZTCI-DDL-INFO-SUBNET !All fields are present. 02 ZIP-ADDR type ZSPI-DDL-INT2. 02 ZSUBNET-MASK type ZSPI-DDL-INT2. 02 ZIOPNAME type ZSPI-DDL-FNAME32. 02 ZTYPE type ZSPI-DDL-ENUM. 02 ZSU-NAME type ZSPI-DDL-CHAR8. 02 ZFORCE-QIO type ZSPI-DDL-BOOLEAN. 02 ZUSE-IRDP type ZSPI-DDL-BOOLEAN. end. ZTCI-MAP-INFO-ROUTE def ZTCI-DDL-INFO-ROUTE 02 ZDEST-IP-ADDR 02 ZGW-IP-ADDR 02 ZIF-HOST 02 ZIF-GW 02 ZSUBNET 02 ZIF-IRDP end.
Commands and Responses INFO Command Tokens in Response Buffer ZSPI-TKN-SSID is an echo of the subsystem ID value provided in the command by your application. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-SERVER-VERSION indicates the software release version of the TCP/IP subsystem. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-DATALIST indicates the beginning of a data list.
Commands and Responses INFO Command ZSPI-VAL-TRUE specifies that an ACK for a TCP packet should be delayed until the TCP receive window is completely filled, or one interval as defined by ZDELAY-ACKS-TIME has expired, whichever occurs first. By delaying the ACK, more than one packet can be acknowledged with a single ACK, thereby reducing network traffic. This is the default. If this value is set, see the ZDELAY-ACKS-TIME field for the time interval between ACKs.
Commands and Responses INFO Command ZQIO-LIMIT is the value of the QIOLIMIT TCP/IP process startup parameter. Valid values are 20 to 100 percent. The default is 100 percent. ZTCP-KEEPIDLE is an integer that specifies the amount of time, in seconds, before TCP will issue a keep-alive packet on sockets that have enabled this option. The default is 45 seconds. The range is 10 through 7200 seconds.
Commands and Responses INFO Command ZSPI-VAL-FALSE indicates that the QIO segment is not to be saved when the TCP/IP process abends. ZALLNETSARELOCAL is a Boolean variable; ON causes TCP to use the interface MTU as a base for determining the TCP Maximum Segment Size (MSS) for each non-local TCP connection. A non-local TCP connection is one that goes to another network (not just another subnetwork).
Commands and Responses INFO Command ZIOPNAME is a 32-byte internal file name that specifies the name of the SLSA LIF or the X25AM device with which the subnet interfaces. The TCP/IP subsystem automatically adds a route with a destination address equal to the value specified in the network portion of the ZIP-ADDR field converted to its broadcast form, and a gateway address equal to the value specified as the IP address of the subnet in the ZIP-ADDR field, whenever a subnet is added. Note.
Commands and Responses INFO Command ZSPI-VAL-FALSE indicates that the SUBNET object is not to use the QIO direct interface to the controller. ZUSE-IRDP is a Boolean variable that specifies whether the SUBNET object should enable its router discovery interface. The default is disabled. ZSPI-VAL-TRUE indicates that the SUBNET object is to use the router discovery interface. ZSPI-VAL-FALSE indicates that the SUBNET object is to not use the router discovery interface.
Commands and Responses INFO Command ZSPI-VAL-TRUE indicates that the route connects to the destination address by means of a gateway. ZSPI-VAL-FALSE indicates that the route does not go through a gateway. ZSUBNET is an eight-character field that specifies the name of the subnet interface used by the specific route. ZIF-IRDP is a variable that specifies whether ICMP Router Discovery Protocol (IRDP) has been enabled on the subnet. The default is OFF.
Commands and Responses INFO Command The possible nonzero values of RETCODE in response to the INFO command are: ZCOM-ERR-TKN-REQ (-29) ZCOM-ERR-TKN-DUP (-27) ZCOM-ERR-TKN-CODE-INV (-26) ZCOM-ERR-SSID-INV (-24) ZCOM-ERR-SPI-ERR (-23) ZCOM-ERR-OBJ-NOT-SUPP (-18) ZCOM-ERR-OBJ-NOT-FOUND (-17) ZCOM-ERR-CMD-TOO-LARGE (-8) ZCOM-ERR-CMD-NOT-SUPP (-5) ZSPI-TKN-ERRLIST indicates the beginning of an error list. For more details, see SPI Standard Definitions on page 5-1.
LISTOBJECTS Command Commands and Responses LISTOBJECTS Command The LISTOBJECTS command lists the names of objects known to the TCP/IP subsystem. The objects listed depend on the value of the ZSPI-TKN-OBJECT-TYPE and ZCOM-TKN-OBJNAME tokens. When your management application specifies the NULL object, all object types and object names known to the TCP/IP subsystem are listed. In this case, the OBJNAME token must either have a zero length or be absent.
LISTOBJECTS Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-SSID ZSPI-TKN-SERVER-VERSION ZSPI-TKN-DATALIST ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-SSID. ZSPI-TYP-UINT. ZSPI-TYP-LIST. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. !{} !{} !... !... !{} !{} !... token-type ZSPI-TYP-SSCTL.
Commands and Responses LISTOBJECTS Command ZCOM-TKN-OBJNAME specifies the name of a TCP/IP object being listed by the command. Unless there is an error that prevents the LISTOBJECTS command from being attempted at all, this token is present in every response record. There can be multiple ZCOM-TKN-OBJNAME tokens in a single response record. ZCOM-TKN-OBJNAME is described in Data Communications Standard Definitions on page 5-9. ZCOM-TKN-OBJTYPE specifies the type of object listed.
LISTOPENS Command Commands and Responses ZSPI-TKN-CONTEXT specifies whether the response continues with more response messages. If this token is present, the response continues. If this token is not present, this response message is the last of the response. For more details, see SPI Standard Definitions on page 5-1. Operational Notes • • • LISTOBJECTS is a nonsensitive command. When the LISTOBJECTS command is completed, the objects remain in the same summary state as before the command was executed.
LISTOPENS Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-SSID token-type ZSPI-TKN-SERVER-VERSION token-type ZSPI-TKN-DATALIST token-type ZTCI-MAP-OPENS-INET def ZTCI-DDL-OPENS-INET !All 02 ZBKUP-CPU type 02 ZBKUP-PIN type 02 ZBKUP-FNUM type 02 ZPRIM-CPU type 02 ZPRIM-PIN type 02 ZPRIM-FNUM type 02 ZPROTO type 02 ZPROCNAME type 02 ZLPORT type 02 ZLOC-ADDR type 02 ZLPORT type 02 ZFORGN-ADDR type 02 ZSTATE type 02 ZSEND type 02 ZRECV type end. ZSPI-TYP-SSID. ZSPI-TYP-UINT. ZSPI-TYP-LIST.
Commands and Responses LISTOPENS Command Tokens in Response Buffer ZSPI-TKN-SSID is an echo of the subsystem ID value provided in the command by your application. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-SERVER-VERSION indicates the software release version of the TCP/IP subsystem. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-DATALIST indicates the beginning of a data list.
Commands and Responses LISTOPENS Command ZPRIM-FNUM is an integer that specifies the primary file number assigned to the opener when the OPEN procedure was called. Note that the file number is equivalent to the socket number. ZPROTO is an integer that specifies which protocol module has been opened. The possible values are: 0 indicates the #ZSPI module has been opened. 6 indicates the TCP protocol module has been opened. 1 7 indicates the UDP protocol module has been opened.
Commands and Responses LISTOPENS Command this token is present in every response record. ZCOM-TKN-OBJNAME is described in Data Communications Standard Definitions on page 5-9. ZCOM-TKN-OBJTYPE specifies the type of object queried. This token has the value ZCOM-OBJ-PROC. For more details, see Data Communications Standard Definitions on page 5-9. ZSPI-TKN-RETCODE specifies whether the command has been completed successfully.
RESETSTATS Command Commands and Responses ZSPI-TKN-CONTEXT specifies whether the response continues with more response messages. If this token is present, the response continues. If this token is not present, this response message is the last of the response. For more details, see SPI Standard Definitions on page 5-1. Operational Notes • • LISTOPENS is a nonsensitive command. When the LISTOPENS command is completed, the PROC object remains in the same summary state as before the command was executed.
Commands and Responses RESETSTATS Command Tokens in Response Buffer ZSPI-TKN-SSID ZSPI-TKN-SERVER-VERSION ZSPI-TKN-DATALIST ZTCI-MAP-TCP-STATS def 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 token-type ZSPI-TYP-SSID. token-type ZSPI-TYP-UINT. token-type ZSPI-TYP-LIST. !{} !{} !... !{} !OBJ-PROC ZTCI-DDL-TCP-STATS. !All fields are present. ZSTATS-TCP-BAD-XSUM type ZSPI-DDL-INT2. ZSTATS-TCP-BAD-OFF type ZSPI-DDL-INT2.
RESETSTATS Command Commands and Responses 02 ZSTATS-TCP-RCV-OUT-BYTE 02 ZSTATS-TCP-RCV-WIN-PACK 02 ZSTATS-TCP-RCV-WIN-BYTE 02 ZSTATS-TCP-RCV-AFTER-CLOSE 02 ZSTATS-TCP-RCV-WIN-PROBE 02 ZSTATS-TCP-RCV-DUP-ACK 02 ZSTATS-TCP-RCV-ACK-TOO-MUCH 02 ZSTATS-TCP-RCV-ACK-PACK 02 ZSTATS-TCP-RCV-ACK-BYTE 02 ZSTATS-TCP-RCV-WIN-UPDATE end. ZTCI-MAP-UDP-STATS def ZTCI-DDL-UDP-STATS.
RESETSTATS Command Commands and Responses ZTCI-MAP-ROUTE-STATS def 02 02 02 02 02 02 02 ZTCI-DDL-ROUTE-STATS. ZSTATS-ROUTE-BAD-REDIR ZSTATS-ROUTE-DYN ZSTATS-ROUTE-NEW-GW ZSTATS-ROUTE-NOT-REACH ZSTATS-ROUTE-WILD-CARD ZSTATS-ROUTE-CURR-TIME ZSTATS-ROUTE-RESET-TIME !All type type type type type type !{} !OBJ-PROC fields are present. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-TIMESTAMP. type ZSPI-DDL-TIMESTAMP. end.
Commands and Responses RESETSTATS Command ZTCI-MAP-SMEM-STATS def 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 !{} !OBJ-STATS ZTCI-MAP-SMEM-STATS . !All fields are present. ZSTATS-SMEM-DATA-MDS type ZSPI-DDL-INT2. ZSTATS-SMEM-MAX-DATA-MDS type ZSPI-DDL-INT2. ZSTATS-SMEM-DUP-MDS type ZSPI-DDL-INT2. ZSTATS-SMEM-MAX-DUP-MDS type ZSPI-DDL-INT2. ZSTATS-SMEM-NO-DATA-MDS type ZSPI-DDL-INT2. ZSTATS-SMEM-NO-DUP-MDS type ZSPI-DDL-INT2.
RESETSTATS Command Commands and Responses ZTCI-MAP-STATS-SUBNET def 02 02 02 02 02 ZTCI-DDL-STATS-SUBNET. ZSTATS-SUBNET-OUT-PKTS ZSTATS-SUBNET-IN-PKTS ZSTATS-SUBNET-OUT-ERRS ZSTATS-SUBNET-IN-ERRS ZSTATS-SUBNET-CURR-TIME !All type type type type !{} !OBJ-SUBNET fields are present. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. type ZSPI-DDL-TIMESTAMP. 02 ZSTATS-SUBNET-RESET-TIME type ZSPI-DDL-TIMESTAMP. end. ZTCI-MAP-STATS-ROUTE def 02 02 02 ZTCI-DDL-STATS-ROUTE.
Commands and Responses RESETSTATS Command Tokens in Response Buffer ZSPI-TKN-SSID is an echo of the subsystem ID value provided in the command by your application. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-SERVER-VERSION is the software release version of the TCP/IP subsystem. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-DATALIST indicates the beginning of the data list.
Commands and Responses RESETSTATS Command ZSTATS-TCP-BAD-SEGS is the number of packets with an invalid segment size received by the TCP Layer of the TCP/IP subsystem during the sample period. This field is reserved for future use. ZSTATS-TCP-NOT-ACK is the number of packets, received by the TCP Layer of the TCP/IP subsystem during the sample period, that the subsystem has not acknowledged. This field is reserved for future use.
Commands and Responses RESETSTATS Command ZSTATS-TCP-OUT-PKTS is the number of outgoing packets sent by the TCP Layer of TCP/IP subsystem during the sample period. ZSTATS-TCP-NO-PORT is the number of packets received by the TCP Layer of the TCP/IP subsystem during the sample period for a connection that has been closed or does not exist. This event can be a normal occurrence or it can be caused by a TCP/IP implementation that does not conform to the TCP/IP state table.
Commands and Responses RESETSTATS Command ZSTATS-TCP-TIMEOUT-DROP the number of connections dropped in a retransmit timeout. ZSTATS-TCP-REXMT-TIMEOUT the number of retransmit timeouts. ZSTATS-TCP-PERSIST-TIMEOUT the number of persistent timeouts. ZSTATS-TCP-KEEP-TIMEOUT the number of keep-alive timeouts. ZSTATS-TCP-KEEP-PROBE the number of keep-alive probes sent. ZSTATS-TCP-KEEP-DROPS the number of connections dropped in keep-alive timeout. ZSTATS-TCP-SND-PACK the total number of data packets sent.
Commands and Responses RESETSTATS Command ZSTATS-TCP-RCV-PCK the number of packets received in sequence. ZSTATS-TCP-RCV-BYTE the number of bytes received in sequence. ZSTATS-TCP-RCV-DUP-PACK the number of duplicate packets received. ZSTATS-TCP-RCV-DUP-BYTE the number of duplicate bytes received. ZSTATS-TCP-RCV-PART-DUP-PACK the number of packets received with some duplicate data. ZSTATS-TCP-RCV-PART-DUP-BYTE the number of duplicate bytes received in partially duplicate packets.
Commands and Responses RESETSTATS Command ZSTATS-TCP-RCV-ACK-PACK the number of ACK packets received. ZSTATS-TCP-RCV-ACK-BYTE the number of ACK bytes acknowledged by received ACKs. ZSTATS-TCP-RCV-WIN-UPDATE the number of window update packets received. ZTCI-MAP-UDP-STATS is the extensible structured token that lists the statistics counters maintained for the UDP Layer during the sample period. These statistics are returned only for the PROC object.
Commands and Responses RESETSTATS Command ZSTATS-UDP-CURR-TIME is the time at which the TCP/IP process read the UDP Layer statistics counters. This time indicates the end of the sample period. ZSTATS-UDP-RESET-TIME is the time at which the UDP Layer statistics counters were last reset. This time indicates the beginning of the sample period. ZTCI-MAP-IP-STATS is the extensible structured token that lists the statistics counters maintained for the IP Layer during the sample period.
Commands and Responses RESETSTATS Command ZSTATS-IP-BAD-LEN is the number of packets received by the IP Layer of the TCP/IP subsystem during the sample period with a packet length that was shorter than expected. This error is very similar to ZSTATS-IP-BAD-HDR-LEN and is usually caused by similar conditions. ZSTATS-IP-FRAG is the number of packet fragments received by the IP Layer of the TCP/IP subsystem during the sample period.
Commands and Responses RESETSTATS Command ZSTATS-IP-OUT-PKTS is the number of outgoing packets sent by the IP Layer of the TCP/IP subsystem during the sample period. ZSTATS-IP-CURR-TIME is the time at which the TCP/IP process read the IP Layer statistics counters. This time indicates the end of the sample period. ZSTATS-IP-RESET-TIME is the time at which the IP Layer statistics were last reset. This time indicates the beginning of the sample period.
RESETSTATS Command Commands and Responses ZSTATS-ROUTE-CURR-TIME is the time at which the TCP/IP process read the routing statistics counters. This time indicates the end of the sample period. ZSTATS-ROUTE-RESET-TIME is the time at which the routing statistics counters were last reset. This time indicates the beginning of the sample period. ZTCI-MAP-ICMP-STATS is the extensible structured token that lists the statistics counters maintained for the ICMP Layer during the sample period.
RESETSTATS Command Commands and Responses Type 11 Time Exceeded Type 12 Parameter Problem Type 13 Timestamp Type 14 Timestamp Reply Type 15 Information Request Type 16 Information Reply For more detailed descriptions of these messages, see the STATISTICS command. This field is reserved for future use. ZSTATS-ICMP-BADCODE is the number of packets, received by the ICMP Layer of the TCP/IP subsystem during the sample period, that contain an invalid ICMP packet type code in the header.
RESETSTATS Command Commands and Responses TCP/IP subsystem has received from the network. Statistics are maintained in this histogram for these messages: Type 0 Echo Reply Type 3 Destination Unreachable Type 4 Source Quench Type 5 Redirect Type 8 Echo Type 11 Time Exceeded Type 12 Parameter Problem Type 13 Timestamp Type 14 Timestamp Reply Type 15 Information Request Type 16 Information Reply For detailed descriptions of these messages, see the STATISTICS Command on page 6-73.
Commands and Responses RESETSTATS Command ZSTATS-SUBNET-OUT-ERRS is the number of errors that occurred while the subnet interface was sending packets during the sample period. Each output error also generates one of these event messages: ZTCI-EVT-IOP-READ-ERR, ZTCI-EVT-IOP-WRITE-ERR, or ZTCI-EVT-IOP-AWAITIO-ERR. ZSTATS-SUBNET-IN-ERRS is the number of errors that occurred while the subnet interface was receiving packets during the sample period.
Commands and Responses RESETSTATS Command ZCOM-TKN-OBJNAME is described in Data Communications Standard Definitions on page 5-9. ZCOM-TKN-OBJTYPE specifies the type of object for which information was requested. For more details, see Data Communications Standard Definitions on page 5-9. ZSPI-TKN-RETCODE specifies whether the command has been completed successfully. The value of this token remains zero (ZCOM-ERR-OK) when the command is completed successfully with or without a warning.
START Command Commands and Responses ZSPI-TKN-CONTEXT specifies whether the response continues with more response messages. If this token is present, the response continues. If this token is not present, this response message is the last of the response. For more details, see SPI Standard Definitions on page 5-1. Operational Notes • • • • RESETSTATS is a sensitive command. When the RESETSTATS command is completed, the object remains in the same summary state as before the command was executed.
START Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-SSID ZSPI-TKN-SERVER-VERSION ZSPI-TKN-DATALIST ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-SSID. ZSPI-TYP-UINT. ZSPI-TYP-LIST. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. !{} !{} !... !{} !{} !{} !... token-type ZSPI-TYP-SSCTL.
Commands and Responses START Command ZCOM-TKN-OBJNAME specifies the name of the TCP/IP subnet or route started by the command. Unless there is an error that prevents the START command from being attempted at all, this token is present in every response record. If you have used an object-name template, a separate ZCOM-TKN-OBJNAME token is returned for each subnet or route that meets the template requirements. ZCOM-TKN-OBJNAME is described in Data Communications Standard Definitions on page 5-9.
Commands and Responses STATISTICS Command ZSPI-TKN-ERRLIST indicates the beginning of an error list. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-ENDLIST indicates the end of a data list or an error list. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-CONTEXT specifies whether the response continues with more response messages. If this token is present, the response continues. If this token is not present, this response message is the last of the response.
STATISTICS Command Commands and Responses Command ZCOM-CMD-STATISTICS Object Type ZCOM-OBJ-PROC or ZCOM-OBJ-SUBNET or ZCOM-OBJ-ROUTE or ZCOM-OBJ-ADDRMAP Tokens in Command Buffer ZSPI-TKN-SSID ZCOM-TKN-OBJNAME token-type ZSPI-TYP-SSID. token-type ZSPI-TYP-STRING. ZSPI-TKN-MAXRESP ZSPI-TKN-CONTEXT ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT token-type token-type token-type token-type !{} !{} ZSPI-TYP-INT. ZSPI-TYP-BYTESTRING. ZSPI-TYP-ENUM. ZSPI-TYP-STRING.
STATISTICS Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-SSID ZSPI-TKN-SERVER-VERSION ZSPI-TKN-DATALIST token-type ZSPI-TYP-SSID. token-type ZSPI-TYP-UINT. token-type ZSPI-TYP-LIST. ZTCI-MAP-TCP-STATS def 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 ZTCI-DDL-TCP-STATS.
STATISTICS Command Commands and Responses 02 ZSTATS-TCP-RCV-WIN-PACK type ZSPI-DDL-INT2 02 ZSTATS-TCP-RCV-WIN-BYTE type ZSPI-DDL-INT2 02 ZSTATS-TCP-RCV-AFTER-CLOSE type ZSPI-DDL-INT2 02 ZSTATS-TCP-RCV-WIN-PROBE type ZSPI-DDL-INT2 02 ZSTATS-TCP-RCV-DUP-ACK type ZSPI-DDL-INT2 02 ZSTATS-TCP-RCV-ACK-TOO-MUCH type ZSPI-DDL-INT2 02 ZSTATS-TCP-RCV-ACK-PACK type ZSPI-DDL-INT2 02 ZSTATS-TCP-RCV-ACK-BYTE type ZSPI-DDL-INT2 02 ZSTATS-TCP-RCV-WIN-UPDATE type ZSPI-DDL-INT2 end.
STATISTICS Command Commands and Responses ZTCI-MAP-SMEM-STATS def 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 !{} !OBJ-PROC ZTCI-DDL-SMEM-STATS. !All fields are present.
Commands and Responses STATISTICS Command ZTCI-MAP-ICMP-STATS def 02 02 02 02 !{} !OBJ-PROC ZTCI-DDL-ICMP-STATS. !All fields are present. ZSTATS-ICMP-ERR type ZSPI-DDL-INT2. ZSTATS-ICMP-OLD-SHORT type ZSPI-DDL-INT2. ZSTATS-ICMP-OLD-ICMP type ZSPI-DDL-INT2. ZSTATS-ICMP-OUT-HIST type ZSPI-DDL-INT2 occurs 17 times. ZSTATS-ICMP-BADCODE type ZSPI-DDL-INT2. ZSTATS-ICMP-TOO-SHORT type ZSPI-DDL-INT2. ZSTATS-ICMP-XSUM type ZSPI-DDL-INT2. ZSTATS-ICMP-BAD-LEN type ZSPI-DDL-INT2.
Commands and Responses ZTCI-DDL-STATS-ADDRMAP STATISTICS Command !{} !OBJ-ADDRMAP ZSPI-DDL-INT2 ZSPI-DDL-CHAR16 ZSPI-DDL-INT2 ZSPI-DDL-INT2 ZSPI-DDL-TIMESTAMP ZSPI-DDL-TIMESTAMP ZSPI-DDL-TIMESTAMP 02 ZIP-ADDR-LOCAL type 02 ZX121-ADDR-LOCAL type 02 ZSTATS-ADDRMAP-IN-CALLS type 02 ZSTATS-ADDRMAP-OUT-CALLS type 02 ZSTATS-ADDRMAP-LAST-USED type 02 ZSTATS-ADDRMAP-CURR-TIME type 02 ZSTATS-ADDRMAP-RESET-TIME type end. ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !{} ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM.
Commands and Responses STATISTICS Command ZSPI-TKN-DATALIST indicates the beginning of a data list. The ZSPI-TKN-MAXRESP token must have a value other than zero for data lists to be included in the response. For more details, see SPI Standard Definitions on page 5-1. ZTCI-MAP-TCP-STATS is the extensible structured token that lists the statistics counters maintained for the TCP Layer during the sample period. These statistics are returned only for the PROC object.
Commands and Responses STATISTICS Command ZSTATS-TCP-REXMIT is the number of packets retransmitted during the sample period. Packets are retransmitted when a packet is not acknowledged within a certain time interval.
Commands and Responses STATISTICS Command exist. This event can be a normal occurrence or it can be caused by a TCP/IP implementation that does not conform to the TCP/IP specification’s state table. ZSTATS-TCP-URGENT is the number of incoming packets with the urgent bit set received by the TCP Layer of the TCP/IP subsystem during the sample period. ZSTATS-TCP-CURR-TIME is the time at which the TCP/IP process read the TCP Layer statistics counters. This time indicates the end of the sample period.
Commands and Responses STATISTICS Command ZSTATS-TCP-PERSIST-TIMEOUT the number of persistent timeouts. ZSTATS-TCP-KEEP-TIMEOUT the number of keep-alive timeouts. ZSTATS-TCP-KEEP-PROBE the number of keep-alive probes sent. ZSTATS-TCP-KEEP-DROPS the number of connections dropped in keep-alive timeouts. ZSTATS-TCP-SND-PACK the total number of data packets sent. ZSTATS-TCP-SND-BYTE the total number of data bytes sent. ZSTATS-TCP-SND-REXMIT-BYTE the number of bytes retransmitted.
Commands and Responses STATISTICS Command ZSTATS-TCP-RCV-DUP-PACK the number of duplicate packets received. ZSTATS-TCP-RCV-DUP-BYTE the number of duplicate bytes received. ZSTATS-TCP-RCV-PART-DUP-PACK the number of packets received with some duplicate data. ZSTATS-TCP-RCV-PART-DUP-BYTE the number of duplicate bytes received in partially duplicate packets. ZSTATS-TCP-RCV-OUT-PACK the number of out-of-order packets received. ZSTATS-TCP-RCV-OUT-BYTE the number of out-of-order bytes received.
Commands and Responses STATISTICS Command ZSTATS-TCP-RCV-WIN-UPDATE the number of window update packets received. ZTCI-MAP-UDP-STATS is the extensible structured token that lists the statistics counters maintained for the UDP Layer during the sample period. These statistics are returned only for the PROC object. This token has the token number ZTCI-TNM-UDP-STATS and the DDL definition ZTCI-DDL-UDP-STATS. Each counter is defined in a separate field.
Commands and Responses STATISTICS Command ZTCI-MAP-IP-STATS is the extensible structured token that lists the statistics counters, which have been maintained for the IP Layer during the sample period. These statistics are returned only for the PROC object. This token has the token number ZTCI-TNM-IP-STATS and the DDL definition ZTCI-DDL-IP-STATS. Each counter is defined in a separate field.
Commands and Responses STATISTICS Command ZSTATS-IP-FRAG is the number of packet fragments received by the IP Layer of the TCP/IP subsystem during the sample period. Usually, a packet is fragmented when the size of the packet is too large for a particular gateway or network. This statistic might indicate that the sender’s maximum segment size is too large for the connection. ZSTATS-IP-FRAG-DROP is the number of packet fragments dropped by the IP Layer of the TCP/IP subsystem during the sample period.
Commands and Responses STATISTICS Command ZSTATS-IP-CURR-TIME is the time at which the TCP/IP process read the IP Layer statistics counters. This time indicates the end of the sample period. ZSTATS-IP-RESET-TIME is the time at which the IP Layer statistics counters were last reset. This time indicates the beginning of the sample period. ZTCI-MAP-ROUTE-STATS is the extensible structured token that lists the routing statistics counters maintained for the IP Layer during the sample period.
STATISTICS Command Commands and Responses ZSTATS-ROUTE-RESET-TIME is the time at which the routing statistics counters were last reset. This time indicates the beginning of the sample period. ZTCI-MAP-ICMP-STATS is the extensible structured token that lists the statistics counters maintained for the ICMP Layer during the sample period. These statistics are returned only for the PROC object. This token has the token number ZTCI-TNM-ICMP-STATS and the DDL definition ZTCI-DDL-ICMP-STATS.
STATISTICS Command Commands and Responses A Destination Unreachable message is sent to the source host by the TCP/IP subsystem (functioning as a host) when the destination host or port is unreachable. This message is sent by the TCP/IP subsystem (functioning as a gateway) when the destination network or host is unreachable, fragmentation is needed and the Don’t Fragment flag is set, or the source route failed. Type 4 is the Source Quench message.
STATISTICS Command Commands and Responses The TCP/IP subsystem (functioning as a host or gateway) sends this message in reply to a Timestamp message. This message indicates the time in the original Timestamp message and the time at which the message was received by the destination. The Timestamp facility is used to obtain the network time. Special applications can be written to use this facility. Type 15 is the Information Request message.
STATISTICS Command Commands and Responses specified in the header. This error, usually caused by a noisy link, is rarely reported because the checksum routine also detects this problem. ZSTATS-ICMP-REFLECT is the number of ICMP packets received by the ICMP Layer of the TCP/IP subsystem during the sample period that have been sent a response. Note that not all ICMP packets require a response. ZSTATS-ICMP-IN-HIST is the input histogram of ICMP messages recorded during the sample period.
STATISTICS Command Commands and Responses A gateway sends this message to the TCP/IP subsystem to indicate that the gateway is receiving datagrams more quickly than it can process them. When the TCP/IP subsystem receives this message, it reduces the rate at which it is sending the datagrams by implementing a slow start. To implement a slow start, the TCP/IP subsystem first stops sending any datagrams at all and then gradually increases the number of datagrams sent.
STATISTICS Command Commands and Responses This message indicates the time in the original Timestamp message and the time at which the Timestamp message was received by the destination. The Timestamp facility is used to obtain the network time. Special applications can be written to use this facility. Type 15 is the Information Request message.
Commands and Responses STATISTICS Command ZSTATS-SUBNET-OUT-ERRS is the number of errors that occurred while the subnet interface was sending packets during the sample period. Each output error also generates one of these event messages: ZTCI-EVT-IOP-READ-ERR, ZTCI-EVT-IOP-WRITE-ERR, or ZTCI-EVT-IOP-AWAITIO-ERR. ZSTATS-SUBNET-IN-ERRS is the number of errors that occurred while the subnet interface was receiving packets during the sample period.
Commands and Responses STATISTICS Command returned only for the PROCESS object. This token has the token number ZTCI-TNM-SMEM-STAT and the DDL definition ZTCI-DDL-SMEM-STAT. ZSTATS-SMEM-DATA-MDS is an integer that specifies the current number of data message descriptors (MDs) in use by the process. ZSTATS-SMEM-MAX-DATA-MDS is an integer that specifies the maximum number of data MDs that have been in use.
Commands and Responses STATISTICS Command ZSTATS-SMEM-MAX-POOL-SPACE is an integer that specifies the maximum pool space used. ZSTATS-SMEM-POOL-FAILS is an integer that specifies the number of times a pool space request failed. ZSTATS-SMEM-TOTAL-MBUFS is an integer that specifies the total number of memory buffers available. ZSTATS-SMEM-CURR-MBUF-INUSE is an integer that specifies the current number of memory buffers in use.
Commands and Responses STATISTICS Command ZSTATS-SMEM-SIZE-2048 is an integer that specifies the count of socket sends between 1025 and 2048 bytes. ZSTATS-SMEM-SIZE-4096 is an integer that specifies the count of socket sends between 2049 and 4096 bytes. ZSTATS-SMEM-SIZE-8192 is an integer that specifies the count of socket sends between 4097 and 8192 bytes. ZSTATS-SMEM-SIZE-12288 is an integer that specifies the count of socket sends between 8193 and 12288 bytes.
Commands and Responses STATISTICS Command ZSPI-TKN-RETCODE specifies whether the command has been completed successfully. The value of this token remains zero (ZCOM-ERR-OK) when the command is completed successfully with or without a warning. Note that if the empty response is returned, the value of this token is nonzero, although the command is completed successfully. If the command is not completed successfully, the value of this token indicates the reason the command failed.
STATUS Command Commands and Responses Operational Notes • • • STATISTICS is a nonsensitive command; any valid user on the system can issue this command. The summary state of the object does not prevent the successful completion of the STATISTICS command. To initialize the statistics counters after the response message is built, use the RESETSTATS command. STATUS Command The STATUS command returns information about the current summary state and other status information about the specified object(s).
STATUS Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-SSID ZSPI-TKN-SERVER-VERSION ZSPI-TKN-DATALIST token-type ZSPI-TYP-SSID. token-type ZSPI-TYP-UINT. token-type ZSPI-TYP-LIST. ZTCI-MAP-STATUS-PROC !{} !{} !... def ZTCI-DDL-STATUS-PROC. 02 ZINET-PROC-STATE end. !{} !OBJ-PROC !All fields are present. type ZSP-DDL-ENUM.
STATUS Command Commands and Responses ZTCI-MAP-STATUS-ADDRMAP def 02 02 .....02 02 ZTCI-DDL-STATUS-ADDRMAP. ZIP-ADDR-REMOTE ZX121-ADDR-REMOTE ZSTATUS-ADDRMAP-LAST-USED ZSTATUS-LAST-LDEV-USED end. ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type token-type token-type token-type !All type type type type !{A} !OBJ-ADDRMAP fields are present. ZSPI-DDL-INT2. ZSPI-DDL-CHAR16. ZSPI-DDL-TIMESTAMP. ZSPI-DDL-CHAR50.
Commands and Responses STATUS Command ZSPI-TKN-DATALIST indicates the beginning of a data list. The ZSPI-TKN-MAXRESP token must have a value other than 0 for data lists to be included in the response. For more details, see SPI Standard Definitions on page 5-1. ZTCI-MAP-STATUS-PROC is the extensible structured token that lists the summary state of the PROC object. This token has the token number ZTCI-TNM-STATUS-PROC and the DDL definition ZTCI-DDL-STATUS-PROC.
Commands and Responses STATUS Command LISTEN indicates that the TCP Layer is waiting for a connection request from any remote TCP Layer. SYNC-SENT indicates that the TCP Layer has sent a SYN packet and is waiting for a SYN-ACK response. SYNC-RECV indicates that the TCP Layer has received a SYN packet, responded with a SYN-ACK, and is now waiting for an ACK. STATE-ESTAB indicates that there is an open connection. The TCP Layer can deliver data to the user that it has received from the remote.
Commands and Responses STATUS Command TIME-WAIT indicates that the connection has been closed on both sides, but that the TCP Layer continues to maintain the protocol control block for a short time to trap stray packets. ZNET-STATUS-SEND is the number of bytes of data currently in the send queue for the socket. ZNET-STATUS-RECV is the number of bytes of data currently in the receive queue for the socket.
Commands and Responses STATUS Command ZCOM-TKN-OBJTYPE specifies the type of object for which information was requested. The possible values are ZCOM-OBJ-PROC, ZCOM-OBJ-SUBNET, and ZCOM-OBJ-ROUTE. This token is present in every response record. The value of the ZCOM-TKNOBJTYPE token is the same as the value of the ZSPI-TKN-OBJECT-TYPE token in the header. For more details, see Data Communications Standard Definitions on page 5-9.
STOP Command Commands and Responses ZSPI-TKN-CONTEXT specifies whether the response continues with more response messages. If this token is present, the response continues. If this token is not present, this response message is the last of the response. For more details, see SPI Standard Definitions on page 5-1. Operational Notes • • • STATUS is a nonsensitive command; any user on the system can issue this command. When the STATUS command is completed, the object remains in the same summary state.
STOP Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-SSID ZSPI-TKN-SERVER-VERSION ZSPI-TKN-DATALIST ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ... ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-SSID. ZSPI-TYP-UINT. ZSPI-TYP-LIST. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-LIST. !{} !{} !... !{} !{} !{} !... token-type ZSPI-TYP-SSCTL.
Commands and Responses STOP Command ZCOM-TKN-OBJNAME specifies the name of a TCP/IP subnet or route stopped by the command. Unless there is an error that prevents the STOP command from being attempted at all, this token is present in every response record. If you have used an object-name template, a separate ZCOM-TKN-OBJNAME token is returned for each subnet or route that meets the template requirements. ZCOM-TKN-OBJNAME is described in Data Communications Standard Definitions on page 5-9.
Commands and Responses TRACE Command ZSPI-TKN-ERRLIST indicates the beginning of an error list. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-ENDLIST indicates the end of a data list or an error list. For more details, see SPI Standard Definitions on page 5-1. ZSPI-TKN-CONTEXT specifies whether there are more response messages to be received for a response. If this token is present, the response will continue to the next response message.
TRACE Command Commands and Responses subsystem uses this bit mask to determine the records that have been selected by the management application. The bit mask is 32 bits long. Note. The trace operation can significantly increase CPU useage by the TCP/IP process. To avoid problems with other processes in the processor, it is recommended that you lower the priority of the TCP/IP process before you issue the TRACE command.
Commands and Responses TRACE Command Tokens in Command Buffer ZSPI-TKN-SSID specifies the subsystem ID, which your management application must pass to SSINIT. This token is described in SPI Standard Definitions on page 5-1 and in the SPI Programming Manual. ZCOM-MAP-TRACE-MODIF is a standard data communications token described in the SPI Common Extensions Manual. This token is required in the command, and duplicate occurrences are not allowed.
Commands and Responses TRACE Command UDP-DETL-IN traces UDP Layer input detail. UDP-DETL-OUT traces UDP Layer output detail. UDP-IN traces UDP Layer input. UDP-OUT traces UDP Layer output. UDP-USER-REQ traces UDP user requests. ZCOM-TKN-OBJNAME specifies the process or subnet to be traced. Your application must provide this token in the command. The object name cannot be an object-name template. This token is described in Data Communications Standard Definitions on page 5-9.
Commands and Responses TRACE Command attempted at all, this token is present in every response record. ZCOM-TKN-OBJNAME is described in Data Communications Standard Definitions on page 5-9. ZCOM-TKN-OBJTYPE specifies the type of object for which a trace was started or stopped. This token has the value ZCOM-OBJ-PROC or ZCOM-OBJ-SUBNET. For more details, see Data Communications Standard Definitions on page 5-9. ZSPI-TKN-RETCODE specifies whether the command has been completed successfully.
Commands and Responses TRACE Command ZCOM-ERR-TRACE-ATTR-INV (-801) ZCOM-ERR-TKN-REQ (-29) ZCOM-ERR-TKN-DUP (-27) ZCOM-ERR-TKN-CODE-INV (-26) ZCOM-TKN-SSID-INV (-24) ZCOM-ERR-SPI-ERR (-23) ZCOM-ERR-SECUR-VIOL (-22) ZCOM-ERR-OBJ-NOT-SUPP (-18) ZCOM-ERR-OBJ-NOT-FOUND (-17) ZCOM-ERR-CMD-TOO-LARGE (-8) ZCOM-ERR-CMD-SEQ-INV (-6) ZCOM-ERR-CMD-NOT-SUPP (-5) ZSPI-TKN-ERRLIST indicates the beginning of an error list. For more details, see SPI Standard Definitions on page 5-1.
Commands and Responses HP NonStop TCP/IP Management Programming Manual—529636-001 6 -116 TRACE Command
7 Event Management The TCP/IP subsystem reports information about events it detects by issuing event messages. A management application can obtain these event messages by opening an Event Management Service (EMS) distributor process and requesting the messages. The application can also specify that a filter be applied to select certain event messages.
Critical Events Event Management Table 7-1.
Event-Management Programming Event Management ZTCI-TKN-SEV. If the value is ZTCI-VAL-SEV-FATAL, the TCP/IP process is no longer operational. If the value is ZTCI-VAL-SEV-WARN, it is only a warning message. If the value is ZTCI-VAL-SEV-INFO, it is an informational message only. The ZTCI-VAL-SEVINFO value is present if the ZEMS-TKN-EMPHASIS token has a value of ZSPI-VAL-FALSE.
1: ZTCI-EVT-NO-MEM Event Management information. (For further information on the standard header, see the EMS Manual.) The text shown in the box follows this standard header. When you use the EMSTEXT procedure to get the text version of an event message, you request either the display-format version or the console-compatible-format version, as described in the EMS Manual. In the case of TCP/IP event messages, there is no difference between the two versions (except possibly the standard header).
1: ZTCI-EVT-NO-MEM Event Management ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZTCI-EVT-NO-MEM (1). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC contains the name of the TCP/IP process that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event.
2: ZTCI-EVT-IOP-READ-ERR Event Management 2: ZTCI-EVT-IOP-READ-ERR A READ operation to the X.25 (X25AM) I/O process failed. This can cause the I/O process to be closed if too many or certain critical failures occur. If this event results in the I/O process being closed, the TCP/IP process attempts to reopen the I/O process at one-minute intervals. Note. This event is only valid for the X25AM subsystem. It does not apply to the SLSA subsystem. This event is critical.
2: ZTCI-EVT-IOP-READ-ERR Event Management ZCOM-TKN-SUBJ-SUBNET contains the name of the TCP/IP subnet that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized.
3: ZTCI-EVT-IOP-WRITE-ERR Event Management 3: ZTCI-EVT-IOP-WRITE-ERR A WRITE operation to the X.25 (X25AM) I/O process failed. This can cause the I/O process to be closed if too many or certain critical failures occur. If this event results in the I/O process being closed, the TCP/IP process attempts to reopen the I/O process at one-minute intervals. Note. This event is only valid for the X25AM subsystem. It does not apply to the SLSA subsystem. This event is critical.
3: ZTCI-EVT-IOP-WRITE-ERR Event Management ZCOM-TKN-SUBJ-SUBNET contains the name of the TCP/IP subnet that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized.
4: ZTCI-EVT-IOP-AWAITIO-ERR Event Management 4: ZTCI-EVT-IOP-AWAITIO-ERR The TCP/IP process called the AWAITIO procedure during communication with the X.25 (X25AM) I/O process but an error occurred before the operation completed. This can cause the I/O process to be closed if too many or certain critical failures occur. If this event results in the I/O process being closed, the TCP/IP process attempts to reopen the I/O process at one-minute intervals. Note.
4: ZTCI-EVT-IOP-AWAITIO-ERR Event Management ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-SUBNET. ZCOM-TKN-SUBJ-SUBNET contains the name of the TCP/IP subnet that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event.
5: ZTCI-EVT-SUMSTATE-CHG Event Management required. However, if the attempt to reopen fails, the operator must check the X25AM line (for X.25 subnets) to verify that the problem is not at the port or line level. 5: ZTCI-EVT-SUMSTATE-CHG The summary state of a TCP/IP subnet has changed as a result of a command or an error on the subnet interface. This event is a noncritical event. The event message is reported to the EMS collector ($0).
5: ZTCI-EVT-SUMSTATE-CHG Event Management ZCOM-TKN-SUBJ-SUBNET contains the name of the TCP/IP subnet that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-FALSE, indicating that this is not a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized.
6: ZTCI-EVT-INTL Event Management ZTCI-VAL-CAUSE-RECOV indicates the change occurred because of a recovery operation. Event-Message Text In the text message, subname corresponds to the value in ZCOM-TKN-SUBJ-SUBNET, iopname corresponds to the value in ZTCI-TKN-IOPNAME, old-state corresponds to the value in ZCOM-TKN-OLD-OBJSTATE, new-state corresponds to the value in ZCOM-TKN-OBJSTATE, and cause corresponds to the value in ZCOM-TKN-CAUSE-SUMSTATE-CHG. Cause.
6: ZTCI-EVT-INTL Event Management Unconditional Tokens ZSPI-TKN-SSID is a header token that specifies the subsystem ID. The value used for the TCP/IP subsystem is ZTCI-VAL-SSID. ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZTCI-EVT-INTL (6). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC contains the name of the TCP/IP subsystem that is the subject of this event message.
7: ZTCI-EVT-DUP-IP-ADDR Event Management 7: ZTCI-EVT-DUP-IP-ADDR The Address Resolution Protocol (ARP) module of the TCP/IP process has detected that another machine on the network is broadcasting the same IP address. If this were to continue, each of the two machines might receive packets intended for the other and would function improperly. This event is critical. It is reported to the EMS collector ($0).
7: ZTCI-EVT-DUP-IP-ADDR Event Management ZCOM-TKN-SUBJ-PROC contains the name of the TCP/IP subsystem that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized.
8: ZTCI-EVT-BCAST-ENET-ADDR Event Management 8: ZTCI-EVT-BCAST-ENET-ADDR The Address Resolution Protocol (ARP) module of the TCP/IP process has detected that another machine on the Ethernet LAN is using the broadcast address FF.FF.FF.FF.FF.FF as its Ethernet address. This causes all packets sent to the broadcast address to be received by all machines on the Ethernet LAN. Performance of all machines is adversely affected.
8: ZTCI-EVT-BCAST-ENET-ADDR Event Management ZCOM-TKN-SUBJ-PROC contains the name of the TCP/IP subsystem that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized.
9: ZTCI-EVT-MAX-DEV Event Management 9: ZTCI-EVT-MAX-DEV The TCP/IP process cannot open any more X25AM subdevices. This event is noncritical. It is reported to the EMS collector ($0).
9: ZTCI-EVT-MAX-DEV Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-INFO. This value indicates that ZTCI-EVT-MAXDEV is an informational message only.
10: ZTCI-EVT-CONN-ESTAB Event Management 10: ZTCI-EVT-CONN-ESTAB An X.25 connection has been established with a remote TCP/IP process. This message is for informational purposes only. This event is noncritical. It is reported to the EMS collector ($0).
11: ZTCI-EVT-CONN-TIMEOUT Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-FALSE, indicating that this is a noncritical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. See Section 5, Common Definitions, for a description of these tokens. For details on any of the EMS tokens, see the EMS Manual.
11: ZTCI-EVT-CONN-TIMEOUT Event Management This event is noncritical. It is reported to the EMS collector ($0).
12: ZTCI-EVT-DEV-NOT-AVAIL Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-INFO. This value indicates that ZTCI-EVT-CONN-TIMEOUT is an informational message only.
12: ZTCI-EVT-DEV-NOT-AVAIL Event Management This event is critical. It is reported to the EMS collector ($0).
12: ZTCI-EVT-DEV-NOT-AVAIL Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-WARN. This value indicates that ZTCI-EVT-DEV-NOT-AVAIL is only a warning message.
13: ZTCI-EVT-SYN-ERR Event Management 13: ZTCI-EVT-SYN-ERR A syntax error has been detected in the IP-to-X.25 address file. The number of the line where the error occurred is returned in the message. This event is noncritical. It is reported to the EMS collector ($0).
16: ZTCI-EVT-CONF-FILE-ACC-ERR Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-FALSE, indicating that this is a noncritical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
16: ZTCI-EVT-CONF-FILE-ACC-ERR Event Management This event is critical. It is reported to the EMS collector ($0).
16: ZTCI-EVT-CONF-FILE-ACC-ERR Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-WARN when this event is generated by the X.
17: ZTCI-EVT-CONF-FILE-SYN-ERR Event Management 17: ZTCI-EVT-CONF-FILE-SYN-ERR A configuration file contains a syntax error. This message is generated by SMTP or the Domain Name Server. The name of the file and the number of the line where the error occurred are returned in the message. The line containing the syntax error is ignored. This event is critical. It is reported to the EMS collector ($0).
17: ZTCI-EVT-CONF-FILE-SYN-ERR Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
19: ZTCI-EVT-NEW-PROC-ERR Event Management 19: ZTCI-EVT-NEW-PROC-ERR An attempt by the LISTNER process to start a server for a user request failed. A NEWPROCESS error that indicates the reason the server process could not be started is returned in the event message. The user is sent a connection refused message. This event is critical. It is reported to the EMS collector ($0).
19: ZTCI-EVT-NEW-PROC-ERR Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
20: ZTCI-EVT-XFER-ERR Event Management 20: ZTCI-EVT-XFER-ERR An error has occurred during a TRANSFER request. This message is reported by SMTP. This event is critical. It is reported to the EMS collector ($0).
20: ZTCI-EVT-XFER-ERR Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
20: ZTCI-EVT-XFER-ERR Event Management ZTCI-VAL-XFER-CREATE-ITEM indicates the error occurred during the processing of a request containing a CREATE-ITEM UOW. ZTCI-VAL-XFER-ATTACH-COMPNT indicates the error occurred during the processing of a request containing an ATTACH-COMPNT-A01 UOW. ZTCI-VAL-XFER-GET-ITEM-REC indicates the error occurred during the processing of a request containing a GET-ITEM-REC UOW.
21: ZTCI-EVT-PARAM-ERR Event Management For more detailed descriptions of these UOWs, including descriptions of the operations they perform, see the TRANSFER Programming Manual. ZTCI-TKN-XFER-ERR contains the error code value reported by TRANSFER. For descriptions of the values reported, see the TRANSFER Programming Manual. ZTCI-TKN-XFER-ERR-DETL contains any additional error detail values reported with the TRANSFER error.
21: ZTCI-EVT-PARAM-ERR Event Management This event is critical. It is reported to the EMS collector ($0).
21: ZTCI-EVT-PARAM-ERR Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-WARN. This value indicates that ZTCI-EVT-PARAM-ERR is only a warning message.
22: ZTCI-EVT-ADDR-ERR Event Management 22: ZTCI-EVT-ADDR-ERR A configuration file contains an address error. This event is critical. It is reported to the EMS collector ($0).
22: ZTCI-EVT-ADDR-ERR Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. for a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
23: ZTCI-EVT-SOCK-ERR Event Management 23: ZTCI-EVT-SOCK-ERR A socket error was returned on a socket request. The error and the socket operation being performed when the error occurred are returned in the message. This event is critical. It is reported to the EMS collector ($0).
23: ZTCI-EVT-SOCK-ERR Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
24: ZTCI-EVT-PROTO-ERR Event Management 24: ZTCI-EVT-PROTO-ERR A configuration file contains a prototype error. This message is generated by SMTP or the Domain Name Server. The name of the file and the number of the line where the error occurred are returned in the message. The line containing the parameter error is ignored. This event is critical. It is reported to the EMS collector ($0).
24: ZTCI-EVT-PROTO-ERR Event Management ZCOM-TKN-SUBJ-PROC contains the name of the TCP/IP subsystem that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized.
25: ZTCI-EVT-RECV-OPEN-FAIL Event Management 25: ZTCI-EVT-RECV-OPEN-FAIL TCP/IP process could not open $RECEIVE. This event is critical. It is reported to the EMS collector ($0).
25: ZTCI-EVT-RECV-OPEN-FAIL Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
26: ZTCI-EVT-SSINT-FAILED Event Management 26: ZTCI-EVT-SSINT-FAILED This is an SPI buffer initialization error. This event is critical. It is reported to the EMS collector ($0).
26: ZTCI-EVT-SSINT-FAILED Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
27: ZTCI-EVT-CANT-HANDLE-AF Event Management 27: ZTCI-EVT-CANT-HANDLE-AF The protocol is not supported. This event is critical. It is reported to the EMS collector ($0).
27: ZTCI-EVT-CANT-HANDLE-AF Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
28: ZTCI-EVT-OUT-OF-MBUF Event Management 28: ZTCI-EVT-OUT-OF-MBUF There is no buffer space for the request. This event is critical. It is reported to the EMS collector ($0).
29: ZTCI-EVT-TRACE-STOP-ERR Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-WARN. This value indicates that ZTCI-EVT-ADDR-ERR is only a warning message.
29: ZTCI-EVT-TRACE-STOP-ERR Event Management Unconditional Tokens ZSPI-TKN-SSID is a header token that specifies the subsystem ID. The value used for the TCP/IP subsystem is ZTCI-VAL-SSID. ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZTCI-EVT-ADDR-ERR (22). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-PROC.
30: ZTCI-EVT-SSINIT-FAILED1 Event Management Event-Message Text In the text message, err-num corresponds to the value in ZTCI-TKN-ERR-NUM. Cause. A TCP/IP call to DSM_TRACE_ failed. Effect. There is a problem in stopping the trace. Recovery. The operation may be retried. Recovery depends on the trace collector. 30: ZTCI-EVT-SSINIT-FAILED1 There was an SPI initialization failure. This event is critical. It is reported to the EMS collector ($0).
30: ZTCI-EVT-SSINIT-FAILED1 Event Management ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC contains the name of the TCP/IP subsystem that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event.
31: ZTCI-EVT-NEW-CL-MBUF Event Management 31: ZTCI-EVT-NEW-CL-MBUF There is no buffer space for the request. This event is critical. It is reported to the EMS collector ($0).
32: ZTCI-EVT-NON-ZERO-RUN-SOCK Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-WARN. This value indicates that ZTCI-EVT-ADDR-ERR is only a warning message.
32: ZTCI-EVT-NON-ZERO-RUN-SOCK Event Management Unconditional Tokens ZSPI-TKN-SSID is a header token that specifies the subsystem ID. The value used for the TCP/IP subsystem is ZTCI-VAL-SSID. ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZTCI-EVT-ADDR-ERR (22). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-PROC.
33: ZTCI-EVT-NO-BACKUP Event Management Effect. TCP/IP will abend. Recovery. Restart the TCP/IP process. 33: ZTCI-EVT-NO-BACKUP TCP/IP no longer has a backup process. This event is critical. It is reported to the EMS collector ($0).
33: ZTCI-EVT-NO-BACKUP Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
34: ZTCI-EVT-INVALID-CPU-NUM Event Management 34: ZTCI-EVT-INVALID-CPU-NUM An invalid backup CPU was specified. This event is critical. It is reported to the EMS collector ($0). Unconditional Tokens ZSPI-TKN-SSID ZEMS-TKN-EVENTNUMBER ZEMS-TKN-SUBJECT-MARK ZCOM-TKN-SUBJ-PROC ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-CPU ZEMS-TKN-CRTPID ZEMS-TKN-GENTIME ZEMS-TKN-LOGTIME ZEMS-TKN-PIN ZEMS-TKN-SYSTEM ZEMS-TKN-USERID ZTCI-TKN-SEV ZTCI-TKN-ERR-NUM token-type ZSPI-TYP-SSID. token-type ZSPI-TYP-ENUM.
34: ZTCI-EVT-INVALID-CPU-NUM Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
35: ZTCI-EVT-CANT-START-BACKUP Event Management 35: ZTCI-EVT-CANT-START-BACKUP TCP/IP could not start a new backup process. This event is critical. It is reported to the EMS collector ($0).
35: ZTCI-EVT-CANT-START-BACKUP Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
36: ZTCI-EVT-BACKUP-IS DEAD Event Management 36: ZTCI-EVT-BACKUP-IS DEAD The backup process has abended. This event is critical. It is reported to the EMS collector ($0).
36: ZTCI-EVT-BACKUP-IS DEAD Event Management ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event. (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual.
37: ZTCI-EVT-BACKUP-IS STARTED Event Management 37: ZTCI-EVT-BACKUP-IS STARTED TCP/IP has successfully started its backup process. This event is critical. It is reported to the EMS collector ($0).
38: ZTCI-EVT-CONN-ESTAB-GATE Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-WARN. This value indicates that ZTCI-EVT-ADDR-ERR is only a warning message.
38: ZTCI-EVT-CONN-ESTAB-GATE Event Management Event-Message Text CONNECTION ESTABLISHED WITH source-ipaddress USING GATEWAY gateway-ipaddress Unconditional Tokens ZSPI-TKN-SSID is a header token that specifies the subsystem ID. The value used for the TCP/IP subsystem is ZTCI-VAL-SSID. ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZTCI-EVT-ADDR-ERR (22).
39: ZTCI-EVT-CHKPT-FAILED Event Management ZTCI-TKN-IP-ADDR-5 through ZTCI-TKN-IP-ADDR-8 contains the IP address of the gateway being used. Event-Message Text In the text message, source-ipaddress corresponds to the values of ZTCI-TKN-IPADDR-1.ZTCI-TKN-IP-ADDR-2.ZTCI-TKN-IP-ADDR-3.ZTCI-TKN-IP-ADDR-4 and gateway-ipaddress corresponds to the values of ZTCI-TKN-IP-ADDR-5.ZTCI-TKNIP-ADDR-6.ZTCI-TKN-IP-ADDR-7.ZTCI-TKN-IP-ADDR-8. Cause. An X.25 connection was established to a remote TCP/IP host. Effect.
39: ZTCI-EVT-CHKPT-FAILED Event Management ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZTCI-EVT-ADDR-ERR (22). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC contains the name of the TCP/IP subsystem that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event.
40: ZTCI-EVT-NO-BACKUP-CPU Event Management 40: ZTCI-EVT-NO-BACKUP-CPU No backup processor was specified. This event is critical. It is reported to the EMS collector ($0).
41: ZTCI-EVT-IOP-QIO-ERR Event Management (ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, and USERID are automatically placed in the header when the EMSINIT procedure is called and the event message buffer is initialized. For a description of these tokens, see Section 5, Common Definitions. For details on any of the EMS tokens, see the EMS Manual. ZTCI-TKN-SEV contains the value ZTCI-VAL-SEV-WARN. This value indicates that ZTCI-EVT-ADDR-ERR is only a warning message.
41: ZTCI-EVT-IOP-QIO-ERR Event Management Unconditional Tokens ZSPI-TKN-SSID is a header token that specifies the subsystem ID. The value used for the TCP/IP subsystem is ZTCI-VAL-SSID. ZEMS-TKN-EVENTNUMBER is a header token that contains the event number. Its value is ZTCI-EVT-ADDR-ERR (22). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-PROC.
42: ZTCI-EVT-QIOMODE-ON Event Management Event-Message Text In the text message, err-num corresponds to the value in ZTCI-TKN-ERR-NUM and iop-name corresponds to the value in ZTCI-TKN-IOPNAME. Cause. A QIO driver error has occurred. Effect. This message is for informational purposes only. Recovery. The TCP/IP process will close and attempt to reopen the I/O process. 42: ZTCI-EVT-QIOMODE-ON The subnet is now using QIO direct mode. This event is critical. It is reported to the EMS collector ($0).
42: ZTCI-EVT-QIOMODE-ON Event Management ZEMS-TKN-SUBJECT-MARK is the standard EMS token that always immediately precedes the subject token here, ZCOM-TKN-SUBJ-PROC. ZCOM-TKN-SUBJ-PROC contains the name of the TCP/IP subsystem that is the subject of this event message. ZEMS-TKN-EMPHASIS is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a critical event.
Event Management 42: ZTCI-EVT-QIOMODE-ON HP NonStop TCP/IP Management Programming Manual—529636-001 7- 80
A Error Numbers and Error Lists This appendix describes the error numbers and associated error lists defined by the TCP/IP subsystem (that is, the error values whose symbolic names begin with ZTCI-ERR-). These error numbers occur as values of the ZSPI-TKN-RETCODE and ZSPI-TKN-ERROR tokens. These errors cannot occur for all commands. To determine which commands return these TCP/IP-specific errors, see the following descriptions of each of the error numbers.
1: ZTCI-ERR-INV-FNAME Error Numbers and Error Lists 1: ZTCI-ERR-INV-FNAME The ADD SUBNET command has been issued but cannot be executed because an invalid I/O process name has been specified for the ZIOPNAME field. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-ENUM. token-type ZSPI-TYP-SSCTL.
6: ZTCI-ERR-ENET-ADDR-NOT-AVAIL Error Numbers and Error Lists Tokens ZSPI-TKN-ERROR is the standard SPI error token described in the SPI Programming Manual. Its value consists of the TCP/IP subsystem ID and the error number ZTCI-ERR-ATTROUT-OF-RANGE. This token is always present in the error list. ZCOM-TKN-OBJNAME is the object name on which the error occurred in the command.
Error Numbers and Error Lists 7: ZTCI-ERR-DUP-ADDR name, this token is present in the error list. Otherwise, this token is omitted from the list. ZCOM-TKN-OBJTYPE is the object type provided with the command on which the error occurred. Its value defines the type of object against which the command was issued. Its only possible value is ZCOM-OBJ-SUBNET. Recommended Action Either the subsystem is not operational or the SCP process ($ZNET) is not running.
8: ZTCI-ERR-NET-UNREACH Error Numbers and Error Lists Recommended Action Reissue the ADD SUBNET or ALTER SUBNET command with another IP address. 8: ZTCI-ERR-NET-UNREACH An ADD ROUTE command has been issued but cannot be executed because the gateway specified for the route is unavailable. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-ENUM. token-type ZSPI-TYP-SSCTL.
10: ZTCI-ERR-SNAP-MTU-NOT-AVAIL Error Numbers and Error Lists 10: ZTCI-ERR-SNAP-MTU-NOT-AVAIL The ADD SUBNET command has been issued for a SNAP subnet but could not be executed because the SLSA LAN interface did not report the frame size that could be sent over the line. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type ZSPI-TYP-LIST. token-type ZSPI-TYP-ERROR. token-type ZSPI-TYP-STRING. token-type ZSPI-TYP-ENUM. token-type ZSPI-TYP-SSCTL.
Glossary This glossary defines terms used both in this manual and in other NonStop TCP/IP manuals. Both industry-standard terms and HP terms are included. Because this glossary for NonStop TCP/IP as a whole, not all of the terms listed here appear in this manual. address mask. A bit mask used to select bits from an Internet address for subnet addressing. The mask is 32 bits long and selects the network portion of the Internet address and one or more bits from the local portion. address resolution.
bridge Glossary bridge. A router that connects two or more networks and forwards packets among them. Usually, bridges operate at the physical network level. For example, an Ethernet bridge connects two physical Ethernet cables and forwards from one cable to the other exactly those packets that are not local. Bridges differ from repeaters; bridges store and forward complete packets, while repeaters forward electrical signals. broadband.
Glossary compatibility distributor compatibility distributor. An EMS distributor process that filters event messages according to fixed (rather than user-specified) criteria, obtains text for these messages that is compatible with the operator console of Guardian operating system versions earlier than C00, and writes the text to the standard Guardian console-message destinations. See also distributor. conditional token.
Defense Advanced Projects Research Agency (DARPA) Glossary Defense Advanced Projects Research Agency (DARPA). Formerly called ARPA. The government agency that funded research and experimentation with the ARPANET and DARPA Internet. 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.
Domain Name Server (DNS) Glossary Domain Name Server (DNS). A method for naming resources. The basic function of the domain name server is to provide information about network objects by answering queries. Domain. In the Internet, a part of the naming hierarchy. Syntactically, a domain name consists of a sequence of names (labels) separated by periods (dots). DSM. See Distributed Systems Management (DSM). E4SA. See Ethernet 4 ServerNet adapter (E4SA). ECHO.
Ethernet Glossary error lists to explain the error further. The token code for the error token is ZSPI-TKNERROR. Its value is a structure consisting of the subsystem ID and an error number identifying the error. See also error list, error number, or return token. Ethernet. A popular local area network technology invented at the Xerox Corporation Palo Alto Research Center. An Ethernet itself is a passive coaxial cable; the interconnections all contain active components.
extensible structure Glossary extensible structure. In DSM programmatic interfaces, a structure declared for the value of an extensible structured token. See also extensible structured token. Compare fixed structure. extensible structured token. In DSM programmatic interfaces, a token consisting of a token code and a value that is an extensible structure. Extensible structures can be extended by adding new fields at the end in later RVUs.
full-duplex mode Glossary full-duplex mode. The communication mode in which data can be transferred in both directions simultaneously. In the Session Layer, no data token is needed. gateway. A special-purpose, dedicated computer that attaches to two or more networks and routes packets from one to the other. In particular, an Internet gateway routes IP datagrams among the networks to which is connected.
hop count Glossary datagram reaches a gateway that can deliver it directly. Subnetting introduces additional levels of hierarchical routing. hop count. A measure of distance between two points in the Internet. A hop count of n means that n gateways separate the source destination. ICMP. See Internet Control Message Protocol (ICMP). IEEE. See Institute of Electrical and Electronics Engineers (IEEE). IEN. See Internet Engineering Note (IEN). IGP. See Interior Gateway Protocol (IGP).
Internet Engineering Note (IEN) Glossary datagram. ICMP also includes an echo request/reply used to test whether a destination is reachable and responding. Internet Engineering Note (IEN). A series of notes developed in parallel to RFCs and available across the Internet from the INIC. IENs contain many of the early theories on the Internet. Internet Protocol (IP).
Level 2 Glossary Level 2. A reference to LINK LEVEL communication (for example, frame formats) or linklevel connections derived from the ISO 7-layer reference model. For long-haul networks, level 2 refers to the communication between a host computer and a network packet switch (for example, HDLC/LAPB). For local area networks, level 2 refers to physical packet transmission. Thus, a level 2 address is a physical hardware address. Level 3.
MFIOB Glossary MFIOB. See multifunction I/O board (MFIOB). MILNET (Military Network). Originally part of the ARPANET, MILNET was partitioned in 1984 to make it possible for military installations to have reliable network service, while the ARPANET continues to be used for research. MILNET uses exactly the same hardware and protocol technology as ARPANET, and there are several interconnection points between the two. Thus, under normal circumstances, MILNET sites are part of the Internet. multicast.
object-name template Glossary communications line $X2502. An object typically has a name and a type known to the controlling subsystem. 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. object type.
PIF Glossary the Physical Layer include rules for the transmission of bits across the physical medium and rules for connectors and wiring. PIF. See physical interface (PIF). PING. See PING. predefined value. A commonly used value, for instance, a value for a token or a field in a token that is given a name in a set of definition files. process. A running entity that is managed by the operating system, as opposed to a program, which is a collection of code and data.
return token Glossary return token. In DSM programmatic interfaces, the token that indicates whether a command was successful and, if not, why it failed. The token code for the return token is ZSPI-TKN-RETCODE. Its value consists of a single integer field. Compare error token. RFC. See Request for Comments (RFC). SAC. See ServerNet addressable controller (SAC). SCF. See Subsystem Control Facility (SCF). SCP. See Subsystem Control Point (SCP). sensitive command.
Simple Mail Transfer Protocol (SMTP) Glossary Simple Mail Transfer Protocol (SMTP). The Internet standard protocol for transferring electronic mail messages from one machine to another. SMTP specifies how two mail systems interact, and specifies the format of control messages the two mail systems exchange to transfer mail. simple token.
subnetwork Glossary subnetwork. One or more intermediate systems that provide relaying and through which end open systems may establish network connections. Subnetwork Access Protocol (SNAP). In order to run the TCP/IP protocol suite over IEEE networks, the Subnetwork Access Protocol (SNAP) defines the interface between the IP layer and the LLC layer.
SWAN concentrator Glossary information about the object. Second, summary states are defined the same way for all NonSotp data communications subsystems, whereas the set of possible states differs from subsystem to subsystem. The management programming interfaces to NonStop data communications subsystems refer to summary states rather than to states. Examples of summary states are STARTED, STOPPED, SUSPENDED, and ABORTING. SWAN concentrator. See ServerNet wide area network (SWAN) concentrator.
token ring LAN Glossary token ring LAN. A ring network that allows unidirectional data transmission between data stations, by a token passing procedure, such that the transmitted data return to the transmitting station. token ring ServerNet adapter. A ServerNet adapter that provides access to token ring LANs. token type. In DSM programmatic interfaces, the part of a DSM token code that identifies the data type and length of the token value. The token type and the token number together form the token code.
wide area network (WAN) Glossary assigned to echo servers, time servers, remote login (TELNET) servers, and file transfer (FTP) servers. wide area network (WAN). A network that operates over a larger geographical area than a local area network (LAN)—typically, an area with a radius greater than one kilometer. The elements of a WAN may be separated by distances great enough to require telephone communications. Contrast with local area network (LAN). wide area network (WAN) subsystem.
Index A ABORT command 6-5 Action events 7-3 ADD command 6-8 Allow-Type token 5-3 ALTER command 6-16 Applications naming rules and guidelines for 3-3 obtaining event messages 7-1 using letter Z 3-4 B Buffer declarations,TCP/IP 5-15 Buffer size recommended for commands 4-1 recommended for responses 4-2 Building the command buffer 4-1 C Checksum token 5-3 Command buffer, building 4-1 Command numbers 3-4 Commands ABORT 6-5 ADD 6-8 ALTER 6-16 building the buffer for 4-1 by object type 6-1 compared to SCF comma
E Index Data list token 5-4 Data lists description of 3-9 representation in responses 6-5 Decoding the response buffer 4-2 Definition files 3-1 Definitions common 5-1 data communications standard 5-9 EMS standard 5-7 files 3-1 SPI standard 5-1 TCP/IP subsystem 5-14 DELETE command 6-25 Discontinuing a command 4-2 Dynamic route switching 4-3 E Elements of SPI messages 3-1 Empty response record 4-3 EMS standard definitions 5-7 End list token 5-4 Error handling 4-3 Error list token 5-4 Error lists, descripti
L Index L Letter Z, using in applications 3-4 LIF, definition of 1-5 LISTOBJECTS command 6-42 LISTOPENS command 6-45 Lists data lists 3-9 error lists 3-9 Logical device name 3-7 Logical device number 3-7 M Maximum field version token 5-5 Maximum response token 5-5 Maximum values for ZTCI token values 5-17 MAXRESP token 5-5 Minimum values for ZTCI token values 5-17 Monitoring statistics 6-73 Multiple objects, in commands 3-6 Multiple tokens, constructs involving 3-9 N Names of objects See Object names of
R Index Process altering 6-16 creating 1-2 current status 6-100 event messages reported 7-1 format of object name 3-5 monitoring statistics 6-73 object names 5-13 obtaining statistics 6-50 resetting statistical counters 6-50 tracing 6-110 Process object 5-11 Processes that report events 7-1 Programming considerations 4-1 Programming for event management 7-3 R Receiving the response buffer 4-2 Release version 6-28 RESETSTATS command 6-50 Response buffer, receiving and decoding 4-2 Response records duplica
T Index STATUS command 6-100 STOP command 6-107 Structured tokens See Extensible structured tokens Subject token 3-7 Subjects of event messages 3-7 Subnet object 5-12 Subnets aborting 6-5 adding 6-8 altering 6-16 commands affecting 6-2 current status 6-100 deleting 6-25 format of object names 3-6 monitoring statistics 6-73 object names 5-13 obtaining statistics 6-50 resetting statistics counters 6-50 starting 6-70 stopping 6-107 terminating operation 6-5 tracing 6-110 Subsystem identifier 5-17 Syntax elem
V Index Types of fields 3-9 of objects 3-5 of tokens 3-9 V Value names, predefined 3-9 Z ZCOM-CMDABORT 6-5 ADD 6-9 ALTER 6-16 DELETE 6-25 GETVERSION 6-28 INFO 6-31 LISTOBJECTS 6-42 LISTOPENS 6-45 RESETSTATS 6-50 START 6-70 STATISTICS 6-74 STATUS 6-100 STOP 6-107 TRACE 6-111 ZCOM-MAPREQID 5-11 TRACE-MODIF 5-11 ZCOM-OBJNULL 5-11 PROC 5-11 ROUTE 5-11 SUBNET 5-12 ZCOM-TKNCAUSE-SUMSTATE-CHG 5-12 OBJNAME 5-12 OBJSTATE 5-13 OBJTYPE 5-13 OLD-OBJSTATE 5-13 SUBJ-PROC 5-13 ZCOM-TKN- (continued) SUBJ-SUBNET 5-14 T
Z Index ZSPI-VALCMDHDR 5-7 EVTHDR 5-7 NORM-ONLY 5-7 TANDEM 5-7 ZTCI subsystem ID 5-17 ZTCI-DDL-MSG-BUFFER 5-15 ZTCI-ERRATTR-OUT-OF-RANGE A-2 DUP-ADDR A-4 ENET-ADDR-NOT-AVAIL A-3 INV-FNAME A-2 NET-UNREACH A-5 SNAP-MTU-NOT-AVAIL A-6 ZTCI-EVTADDR-ERR 7-42 BACKUP-IS-DEAD 7-68 BACKUP-IS-STARTED 7-70 BCAST-ENET-ADDR 7-18 CANT-HANDLE-AF 7-52 CANT-START-BACKUP 7-66 CHKPT-FAILED 7-73 CONF-FILE-ACC-ERR 7-30 CONF-FILE-SYN-ERR 7-32 CONN-ESTAB 7-22 CONN-ESTAB-GATE 7-71 CONN-TIMEOUT 7-24 DEV-NOT-AVAIL 7-25 DUP-IP-ADDR
Z Index ZTCI-VAL- (continued) MIN-TCP-STATE 5-17 MIN-TRACE 5-17 MIN-XFER 5-17 SEV-FATAL 5-17 SEV-INFO 5-17 SEV-WARN 5-17 SSID description 5-17 structure definition 5-6 SUBNET-TYPE-ENET 5-17 SUBNET-TYPE-LOOP 5-17 SUBNET-TYPE-SNAP 5-17 SUBNET-TYPE-X25 5-17 TCP-STATE-CLOSE-WAIT 5-18 TCP-STATE-CLOSING 5-18 TCP-STATE-ESTAB 5-18 TCP-STATE-FIN-WAIT-1 5-18 TCP-STATE-FIN-WAIT-2 5-18 TCP-STATE-LAST-ACK 5-18 TCP-STATE-LISTEN 5-18 TCP-STATE-SYNC-RECV 5-18 TCP-STATE-SYNC-SENT 5-18 TCP-STATE-TIME-WAIT 5-18 TRACE-IPC-CM
