PAM Management Programming Manual Abstract This manual provides information about the programming interface provided by Tandem for managing the Port Access Method (PAM) subsystem. This interface is based on the Subsystem Programmatic Interface (SPI) and the Event Management Service (EMS). This manual is written for experienced application programmers. Product Version Port Access Method G06 Supported Releases This manual supports G06.
Document History Part Number Product Version Published 136718 Port Access Method G05 February 1998 142481 Port Access Method G06 August 1998 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice.
PAM Management Programming Manual Glossary Index Figures Tables What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xi Who Should Use This Manual What’s in This Manual Other Manuals xi xii xiii Your Comments Invited xiii Notation Conventions xiii 1.
3. SPI Programming Considerations for the PAM Subsystem Contents 3.
4. Common Definitions (continued) Contents 4.
5. Commands and Responses (continued) Contents 5. Commands and Responses (continued) Command Descriptions (continued) RESETSTATS Command 5-32 5-33 START Command STATISTICS Command 5-36 STATISTICS LINE Command 5-39 STATISTICS PORT Command 5-44 STATISTICS SESSION Command STATUS Command 5-50 5-54 STATUS LINE Command 5-56 STATUS MSAP SNATR Command STATUS PORT Command 5-59 STATUS SESSION Command STOP Command 5-61 5-67 SWITCH Command TRACE Command 5-58 5-70 5-72 TRACE LINE Command 5-73 6.
6. Event Messages (continued) Contents 6.
A. Error Numbers and Error Lists (continued) Contents A. Error Numbers and Error Lists (continued) Error-List Descriptions (continued) 17: ZPAM-ERR-INV-CTLR-ATT A-18 18: ZPAM-DATA-LEN-INV A-19 19: ZPAM-ERR-INV-PORT-ATT A-20 20:ZPAM-ERR-PAM-INT-ERR A-21 B. Token Codes and Token Maps C. G-Series Migration Object Type Comparison Command Comparison C-1 C-3 Event Message Comparison C-5 Glossary Index Figures Figure 1-1. PAM Components 1-2 Figure 1-2. PAM Process and EMS Figure 1-3.
Tables (continued) Contents Tables (continued) Table B-1. PAM Token Codes and Token Types (page 1 of 2) Table B-2. PAM Token Maps and DDL Definitions Table C-1. PAM and TLAM Object Comparison (page 1 of 2) Table C-2. PAM Programmatic Commands and Object Types Table C-3. TLAM Programmatic Commands and Object Types Table C-4. PAM Event Messages Table C-5.
Contents PAM Management Programming Manual—142481 viii
What’s New in This Manual Manual Information PAM Management Programming Manual Abstract This manual provides information about the programming interface provided by Tandem for managing the Port Access Method (PAM) subsystem. This interface is based on the Subsystem Programmatic Interface (SPI) and the Event Management Service (EMS). This manual is written for experienced application programmers. Product Version Port Access Method G06 Supported Releases This manual supports G06.
What’s New in This Manual New and Changed Information PAM Management Programming Manual—142481 x
About This Manual This manual provides subsystem-specific information about the management programming interface provided by Tandem for managing the Port Access Method (PAM) subsystem. This interface is based on the Subsystem Programmatic Interface (SPI) and the Event Management Service (EMS).
What’s in This Manual About This Manual What’s in This Manual Table i summarizes the contents of this manual. Table i. Contents Section or Appendix Title Contents 1 Introduction Provides a brief overview of the architecture of the PAM subsystem and the Distributed Systems Management (DSM) facilities.
Other Manuals About This Manual Other Manuals More information about the PAM subsystem and management programming can be found in the following manuals: • • • • • • • • PAM Configuration and Management Manual PAM Programming Manual Data Definition Language (DDL) Reference Manual Distributed Systems Management (DSM) Programming Manual EMS Manual SPI Programming Manual SPI Common Extensions Manual Subsystem Control Point (SCP) Management Programming Manual Your Comments Invited After using this manual, p
General Syntax Notation About This Manual [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may 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.
Notation for Messages About This Manual Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing.
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Notation for Management Programming Interfaces About This Manual Notation for Management Programming Interfaces The following list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters.
Change Bar Notation About This Manual PAM Management Programming Manual—142481 xviii
1 Introduction This section provides an overview of PAM and of the facilities for managing PAM. The following topics are included: • • Overview of Features and Architecture on page 1-1 explains the role of PAM within the system, and the features, standards compliance, and components of PAM. Distributed Systems Management (DSM) Facilities on page 1-7 provides an overview of all aspects of PAM subsystem management.
The PAM Subsystem’s Role Within the System Introduction The PAM Subsystem’s Role Within the System The PAM subsystem consists only of software processes and interfaces and uses the services provided by the SLSA subsystem to access the Ethernet and token-ring LANs connected to the Himalaya S-series server. Figure 1-1 shows the components of PAM and its relationship to other data-communication subsystems. The components and related subsystems are described after Figure 1-1. Figure 1-1.
The PAM Subsystem’s Role Within the System Introduction • • • • • • • • • PAM clients on page 1-3 A file-system interface on page 1-3 for applications that need to access the port A message-system interface (on page 1-3) that enables the SNAX Extended Facility (SNAX/XF) or the SNAX Advanced Peer Networking (SNAX/APN) products to access the TRSA The Subsystem Programmatic Interface (SPI) on page 1-4 for management applications and event management The management interfaces on page 1-3 for interactive cont
The PAM Subsystem’s Role Within the System Introduction SPI transfers SCF commands to the PAM subsystem and also provides an interface for writing management applications that perform control-and-inquiry and event management.This manual describes how to write management applications using SPI. ServerNet LAN Systems Access (SLSA) Subsystem PAM uses the SLSA subsystem to access the Ethernet and token-ring LANs attached to the Himalaya S-series server.
The PAM Subsystem’s Role Within the System Introduction Figure 1-2. PAM Process and EMS Management Application 3 Filter Consumer Distributor 4 Event Log 2 1 Event Collector ($0) Event Messages PAM CDT 002.CDD The event-management activities shown in Figure 1-2 occur as follows: 1. The PAM process reports the event by sending an event message to the local EMS event collector. 2. The EMS event collector sends the event message to the EMS event log. 3.
The PAM Subsystem’s Role Within the System Introduction Figure 1-3. PAMMAN and the Control-and-Inquiry Interfaces Management Application SCP PAM Manager Port Applications PAM SCF SPI Request/Response SCF Obey File Logical Interface to SLSA (LIF) CDT 003.CDD MFIOB (Multifunction I/O Board/Ethernet) The MFIOB is a ServerNet adapter that is integrated into the processor multifunction (PMF) CRU and the I/O multifunction (IOMF) CRU. The MFIOB provides testing functions.
Distributed Systems Management (DSM) Facilities Introduction Distributed Systems Management (DSM) Facilities The PAM subsystem supports the DSM facilities provided by Tandem for subsystem management. DSM provides two types of management interfaces to subsystems: • • Commands are used to perform operations on subsystem objects. This type of management interface is referred to as control-and-inquiry. Event messages are generated to report significant events detected by the subsystem.
Interactive Interfaces Introduction • The Event Management Service (EMS) is an event-management interface that includes printing and compatibility distributor processes that can print or display event messages for operators. SCF Interface SCF provides the interactive interface for PAM. SCF operates on defined objects which correspond to physical or functional entities and which have configurable attributes and adhere to rules of operation such as object hierarchy.
Interactive Interfaces Introduction the PAMMAN process during the system load and any time the processors on which a PAM process is defined come back up after a failure. For more information about the SLSA subsystem and LIFs, refer to the LAN Configuration and Management Manual. For information about the persistence manager, refer to the SCF Reference Manual for the Kernel Subsystem.
Management Commands Introduction Figure 1-5. PAM Programmatic Interfaces Use the File System Interface LLC2 appl. Ethernet appl. SNAX/TR appl. LLC1 appl. PORT Object Uses the Message System Interface LLC1 Ethernet LLC2 Port Interface PORT Object SESSION Object PAM E4SA or FESA TRSA MSAP Object TRSA CDT 004.CDD SESSION Object The SESSION object defines the link station for LLC2-type connections and a SNAX session over a token-ring LAN.
Management Commands Introduction Table 1-1. PAM Management Commands Command Action ABORT Abruptly stops the operation of an object. ADD Defines an object to the subsystem. ALTER Changes the values of an object’s attributes. DELETE Removes an object definition from the subsystem. INFO Returns an object’s current attribute values. LISTOPENS Returns the process IDs of an object’s openers. NAMES Returns the fully-qualified names specified by the object.
Management Commands Introduction • • • • LISTOPENS STATISTICS STATUS VERSION Interactive and Programmatic Command Comparison Table 1-2 shows the correspondence between the interactive commands provided by SCF to control and inquire about the PAM subsystem (listed in Table 1-1) and the corresponding programmatic commands. To make the contrast between the two kinds of commands clear, the programmatic command and object names are shown in the full form you must use in management applications. Table 1-2.
Management Commands Introduction Table 1-2.
Management Commands Introduction Table 1-2.
2 Communicating With the PAM Subsystem This section describes how a management application sends commands to and receives responses from the PAM subsystem and how a management application retrieves Event Management Service (EMS) messages generated by the PAM subsystem. How a management application retrieves EMS event messages generated by the PAM subsystem is described in Section 6, Event Messages.
Running an EMS Consumer Distributor Communicating With the PAM Subsystem Running an EMS Consumer Distributor Before your management application can retrieve event messages generated by the PAM subsystem and other subsystems, you must start an EMS consumer distributor process, open this process for communication, and specify the source of event messages with a CONTROL command. The EMS Manual provides complete instructions for taking these steps.
3 SPI Programming Considerations for the PAM Subsystem Once your subsystem and Event Management Service (EMS) processes are running and your management application has established communication with them, the main business of your management application is to format and send commands, decode responses and act on the results, and interpret event messages and act on their information. The SPI Programming Manual provides general instructions for formatting commands and decoding responses and event messages.
SPI Programming Considerations for the PAM Subsystem Definition Files The definitions in a TAL, C, Pascal, or COBOL85 definition file are grouped into sections, so that only those definitions that are needed can be included in the application. For TACL, the entire definition file must be used. For more information about how definition files are accessed by your application, refer to the SPI Programming Manual.
SPI Programming Considerations for the PAM Subsystem Naming Guidelines for Applications For example, a management application written in TAL that sends commands to the PAM subsystem and retrieves event messages issued by the PAM subsystem would need the following SOURCE statements: ?SOURCE ?SOURCE ?SOURCE ?SOURCE ?SOURCE ?SOURCE ZSPIDEF.ZSPITAL ZSPIDEF.ZCOMTAL ZSPIDEF.ZPAMTAL ZSPIDEF.ZEMSTAL ZSPIDEF.ZGRDTAL ZSPIDEF.
SPI Programming Considerations for the PAM Subsystem Commands Commands The PAM subsystem supports the following commands: ABORT RESETSTATS ADD START ALTER STATISTICS DELETE STATUS INFO STOP LISTOBJECTS SWITCH LISTOPENS TRACE Programmatic commands for the PAM subsystem are identified by command numbers with symbolic names having the form ZCOM-CMD-name, where name identifies the command.
SPI Programming Considerations for the PAM Subsystem Object Names Object Names Most PAM commands and responses contain object-name tokens that, when combined with the object-type information, designate which objects are to be or were affected by the command. Most PAM commands accept up to 30 object names. Object-name templates and the subordinate names option are supported.
SPI Programming Considerations for the PAM Subsystem Other Tokens Simple Tokens Simple tokens—tokens whose values are single fields or fixed structures—are identified by token codes. The token codes for the simple tokens used by the PAM subsystem are represented by symbolic names of the form subsys-TKN-name, where subsys is a the four-character subsystem abbreviation and name identifies the token code.
SPI Programming Considerations for the PAM Subsystem Constructs Involving Multiple Tokens Field Types All the field types used by the PAM subsystem are SPI standard field types, so they are represented by symbolic names of the form ZSPI-DDL-name, where name identifies the field type. For example, the field type ZSPI-DDL-BOOLEAN represents the Boolean data type. Throughout this manual, when a field is described, its field type is given.
SPI Programming Considerations for the PAM Subsystem Receiving and Decoding the Response Message COMMENT is the comment token, described in the SPI Programming Manual. ZCOMTKN-OBJNAME is the object-name token, described in Section 4, Common Definitions. ZCOM-TKN-TRACE-OPT is a token used in the TRACE command, and it is described in Section 5, Commands and Responses. If any of the other tokens in a command appear more than once, an error is given either by the PAM subsystem or by SCP.
SPI Programming Considerations for the PAM Subsystem Security General programming considerations for handling errors that occur when using the management-programming interfaces are discussed in the SPI Programming Manual. Error-handling considerations for specific commands are described in Section 5, Commands and Responses. The error numbers returned by the PAM subsystem are described in Appendix A, Error Numbers and Error Lists. Security PAM subsystem commands are either sensitive or nonsensitive.
SPI Programming Considerations for the PAM Subsystem Event-Management Considerations for the PAM Subsystem 4. Read the response from the distributor using the mechanism appropriate to your programming language (for example, a WRITEREAD in TAL). 5. Repeat the following steps in a loop: a. Format and send a GETEVENT command to the consumer distributor to get the next event message, using the mechanism appropriate to your programming language (for example, a WRITEREAD in TAL). b.
SPI Programming Considerations for the PAM Subsystem Filters To determine whether or not an event message reports a critical event, examine the value of the event message token ZEMS-TKN-EMPHASIS. If the value of this token is true (ZSPI-VAL-TRUE), the event message reports a critical event. If the value of this token is false (ZSPI-VAL-FALSE), the event is not critical. The following types of events are considered critical: • • • • There has been a loss of fault-tolerance capability.
SPI Programming Considerations for the PAM Subsystem PAM Management Programming Manual—142481 3- 12 Filters
4 Common Definitions This section lists the common definitions—those used in several commands, responses, or event messages—for the PAM subsystem. Definitions used in only one or two commands, responses, or event messages are described in the individual command descriptions in Section 5, Commands and Responses, or event-message descriptions in Section 6, Event Messages.
SPI Standard Definitions Common Definitions SPI Standard Definitions Descriptions of the SPI standard definitions as they apply to all subsystems are given in the SPI Programming Manual. All items in the definition files are given symbolic names. Definitions whose names begin with ZSPI- are SPI standard definitions. These definitions are available to all subsystems that support SPI procedures and can be found in the SPI DDL file, ZSPIDEF.ZSPIDDL, and in the corresponding files for other languages.
Header Tokens Common Definitions ZSPI-TKN-RETCODE indicates whether a command completed successfully. If the command completed successfully, the value of this token is ZCOM-ERR-OK. If the command did not complete successfully, the value of this token is one of the common data communications error numbers or an error number specifically defined by the PAM subsystem. It indicates just one of the reasons the command failed. The meaning of each error number is subsystem-specific.
Header Tokens Common Definitions ZSPI-TKN-MAXRESP indicates the maximum number of response records a requester will accept in a response buffer. The requester can specify any of the following values: -1 As many response records as will fit in the response buffer can be returned. Each response record will be enclosed in a data list. 0 Only one response record will be returned. The response record will not be enclosed in a data list. This is the default value.
Value Names Common Definitions Value Names The following SPI standard definitions for value names are used by the PAM subsystem: ZSPI-VAL-TRUE ZSPI-VAL-FALSE ZSPI-VAL-TANDEM ZSPI-SSN-ZPAM The following information about these definitions is specific to the PAM subsystem: ZSPI-VAL-TANDEM indicates that the destination subsystem is a Tandem subsystem. The requester must assign this value to the owner field of the ZSPI-TKN-SSID token before sending a command to a Tandem system.
Data Communications Standard Definitions Common Definitions The following SPI standard definitions for token types are used by the PAM subsystem: ZSPI-TYP-BOOLEAN ZSPI-TYP-BYTE ZSPI-TYP-BYTESTRING ZSPI-TYP-CHAR ZSPI-TYP-CHAR4 ZSPI-TYP-CHAR6 ZSPI-TYP-CHAR8 ZSPI-TYP-CHAR16 ZSPI-TYP-CHAR50 ZSPI-TYP-CRTPID ZSPI-TYP-DEVICE ZSPI-TYP-ENUM ZSPI-TYP-FNAME ZSPI-TYP-FNAME32 ZSPI-TYP-INT ZSPI-TYP-INT2 ZSPI-TYP-INT4 ZSPI-TYP-LIST ZSPI-TYP-MARK ZSPI-TYP-SSCTL ZSPI-TYP-SSID ZSPI-TYP-STRING ZSPI-TYP-TIMESTAMP ZSPI-TYP-UI
Simple Tokens Common Definitions Simple Tokens The following data communications standard definitions for simple tokens are used by the PAM subsystem: ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZCOM-TKN-TRACE-OPT The following information about these definitions is specific to the PAM subsystem: ZCOM-TKN-OBJNAME contains the name of a PAM object. The object name in the command indicates the specific object on which the command is to operate.
Command Numbers Common Definitions ZCOM-MAP-TRACE-MODIF ZCOM-MAP-TRACE-WORK The following information about these definitions is specific to the PAM subsystem: ZCOM-MAP-TRACE-MODIF is the extensible structured token sent in the TRACE command by the requester and contains the trace parameters that control the initiation of the trace file, selection of the trace environment, and termination of trace mode. The initiation and selection is handled in one ZCOM-MAP-TRACE-MODIF token.
Object Types Common Definitions Object Types The following data communications standard definitions for object types are used by the PAM subsystem: ZCOM-OBJ-LINE ZCOM-OBJ-MSAP ZCOM-OBJ-NULL ZCOM-OBJ-PORT ZCOM-OBJ-PROCESS ZCOM-OBJ-SESSION The following information about these definitions is specific to the PAM subsystem: ZCOM-OBJ-NULL does not represent a PAM object. It is used as the object type in commands that do not require an object-name token. Only the LISTOBJECTS command accepts the NULL object.
Header Tokens Common Definitions Header Tokens The following EMS standard definitions for header tokens are used by the PAM subsystem: ZEMS-TKN-CONSOLE-PRINT ZEMS-TKN-CPU ZEMS-TKN-CRTPID ZEMS-TKN-EMPHASIS ZEMS-TKN-EVENTNUMBER ZEMS-TKN-GENTIME ZEMS-TKN-LOGTIME ZEMS-TKN-PIN ZEMS-TKN-SYSTEM ZEMS-TKN-USERID Token Types ZEMS-TYP-OPMSG is the only EMS standard definition for token types used by the PAM subsystem. PAM Definitions Definitions whose names begin with ZPAM- are PAM definitions.
Private Token and Field Types Common Definitions Private Token and Field Types The PAM subsystem does not define any token or field types. Predefined Token and Field Values The PAM subsystem defines the following token and field values for use in more than one command, event message, or error list. ZPAM-VAL-BUFLEN is the recommended buffer size in bytes for command messages sent to the PAM subsystem and for responses in which each reply message contains a single response record.
Extensible Structured Tokens Common Definitions Extensible Structured Tokens Extensible structured tokens that appear in PAM commands and responses are described in Section 5, Commands and Responses. The PAM subsystem uses “is present” (-IP) fields in many extensible structured tokens. These fields are merely flags (ZSPI-TYPBOOLEAN) that indicate whether or not the value in the following field is valid. If the -IP field is equal to ZSPI-VAL-FALSE, the value in the following field should not be used.
Tokens in Event Messages Common Definitions Table 4-1.
Tokens in Event Messages Common Definitions ZPAM-TKN-EVT is the state machine event number that was in error. ZPAM-TKN-EVT-DESCR is a general-purpose event description. This is the only ZPAM token that is conditional. It appears only in events where supporting descriptive data further defines an event. ZPAM-TKN-FILE-SYS-ERR is a file-system error number. ZPAM-TKN-FNAME is the operating system file name in internal file name format.
Tokens in Event Messages Common Definitions ZPAM-VAL-NOT-NOTIF-WIN-OVRFLOW The number of outstanding requests from PAM process to SNAX exceeds SNAX_RX_WINDOW. ZPAM-VAL-NOT-NOTIF-SAP-CLOSED The PAM process received a fatal error when delivering the notification to SNAX. The PAM process aborts and deletes the port encountering the error. ZPAM-VAL-NOT-NOTIF-NO-BUFFER The PAM process has run out of extended memory pool. ZPAM-TKN-NOT-SENT-CAUSE indicates the reason for not sending the request.
Tokens in Event Messages Common Definitions ZPAM-TKN-PORT-CONFIG-ERR is the PORT object configuration error code. ZPAM-TKN-PORT-CONFIG-ERR-PARAM contains information further qualifying the PORT object configuration error code. ZPAM-TKN-PROC-ID is the name of the process that generated the event message. ZPAM-TKN-REPT-ENTITY identifies the host SAP/SCP reporting the problem. ZPAM-TKN-REQ-TYPE indicates the type of notification/reply not delivered to the SNAX line-handler process.
Tokens in Event Messages Common Definitions ZPAM-TKN-SEND-COMPL-ERR indicates the error returned on the SEND operation. ZPAM-TKN-SEV indicates the severity of the event being reported. This token is assigned one of the following values: ZPAM-VAL-EVT-SEV-FATAL indicates that the reporting process is no longer fully operational. ZPAM-VAL-EVT-SEV-WARN indicates the event is only a warning; the process is still functioning. ZPAM-VAL-EVT-SEV-INFO indicates the event is for information purposes.
Tokens in Event Messages Common Definitions PAM Management Programming Manual—142481 4- 18
5 Commands and Responses This section describes the syntax and semantics for all commands and responses in the management programming interface to the PAM subsystem.
Command Descriptions Commands and Responses Table 5-1. PAM Programmatic Commands and Object Types (page 2 of 2) Object Type Programmatic Command Sensitive Command LINE MSAP PORT PROCESS STOP Yes X X X X SWITCH Yes X TRACE Yes X SESSION Command Descriptions Each PAM programmatic command and its response is described in detail in this section.
ABORT Command Commands and Responses ABORT Command ABORT is a sensitive command. It is an unconditional request to immediately stop operation of the specified object. Before reaching the STOPPED summary state, the specified object enters the ABORTING summary state, which is a transitional state between STARTED and STOPPED. Objects receiving an ABORT request are not allowed to delay their deactivation—only enough processing is done to ensure the operational integrity of the subsystem.
ABORT Command Commands and Responses Tokens in Response Buffer The tokens present in the buffer received in response to an ABORT command are also described in Section 4, Common Definitions. Operational Notes There are several things you should remember when using the ABORT command: • You can use the ZCOM-TKN-SUB token to abort the operation of the specified object and/or its subordinate objects, if any.
ADD Command Commands and Responses ADD Command ADD is a sensitive command that is used to create a PORT object, define its attributes, and add it to the subsystem. PAM object types other than PORT are added when the host system is configured. PORT objects define an access point to a particular service, as determined by the object subtype. The defined PORT subtype values are ZPAM-VALPORT-TYPE-ENET and ZPAM-VAL-PORT-TYPE-LLC1. A single adapter can communicate with several ports.
ADD Command Commands and Responses Tokens in Response Buffer ZSPI-TKN-DATALIST ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZPAM-TKN-OBJ-SUBTYPE ZSPI-TKN-RETCODE ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST ZSPI-TKN-ENDLIST ZSPI-TKN-CONTEXT token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-STRING. !r ZSPI-TYP-ENUM. !r ZSPI-TYP-ENUM. !r ZSPI-TYP-ENUM. !r ZSPI-TYP-LIST.
ADD Command Commands and Responses each opener that has a read request posted. The default is parallel. This attribute is not supported for token-ring LLC1 ports. ZMAX-REQ-SIZE is the maximum size (in bytes) of a block of messages that can be written and read by the port. This value cannot be larger than the LINE’s MAXREQUESTSIZE. The minimum value that must be specified in this field is 49 bytes for LLC1-type ports and 32 bytes for Ethernet-type ports. The default value is 32000 bytes.
ADD Command Commands and Responses • • There is no summary state transition associated with the ADD PORT command. PORT objects must be STARTED after they have been added. The ADD command leaves the PORT in the STOPPED summary state. The ZPAM-VAL-PORT-TYPE-ENET subtype is invalid for the Token-Ring ServerNet adapter (TRSA).
ALTER Command Commands and Responses ALTER Command ALTER is a sensitive command that changes the attributes of a PORT or MSAP object. The PORT or MSAP object must be added before it can be altered. The PROCESS, LINE, MSAP, and SESSION objects are added when the subsystem is configured. The PORT object is added by means of an ADD command. LLC2 ports cannot be altered using this interface. The attributes of the PROCESS, LINE, MSAP, and SESSION objects cannot be altered.
ALTER MSAP SNATR Command Commands and Responses ALTER MSAP SNATR Command The ALTER MSAP SNATR command alters the attributes of the specified MSAP SNATR object. Additional Tokens in Command Buffer ZPAM-MAP-ALTER-MSAP-SNATR. def ZPAM-DDL-ALTER-MSAP-SNATR 02 ZMAX-PORTS-IP type ZSPI-DDL-BOOLEAN. 02 ZMAX-PORTS type ZSPI-DDL-INT. end. !r !r ZPAM-MAP-ALTER-MSAP-SNATR is an extensible structured token that contains the attributes for the specified MSAP.
ALTER PORT Command Commands and Responses ALTER PORT Command ALTER PORT is a sensitive command that alters the attributes of the specified port. LLC2 ports are the only ports that cannot be altered using this interface. Additional Tokens in Command Buffer ZPAM-MAP-ALTER-PORT def ZPAM-DDL-ALTER-PORT. 02 ZADDR-IP 02 ZADDR 02 ZMAC-ADDR-IP 02 ZMAC-ADDR type type type type 02 02 02 02 02 02 02 02 end.
ALTER PORT Command Commands and Responses ZDELIV-MODE determines how read requests are queued. If ZPAM-VAL-DELIV-MODE-SRL (serial mode, which is the default mode) is selected, all read requests are placed in a single queue and are serviced in FIFO (first in first out) order. If ZPAM-VALDELIV-MODE-PLLEL (parallel mode) is selected, all read requests are placed in separate queues, one for each opener of the port. Inbound messages are delivered to each opener that has a read request posted.
ALTER PORT Command Commands and Responses Operational Notes There are several things you should remember when using the ALTER command: • The PORT object type requires that you specify an object subtype in the ZPAMTKN-OBJ-SUBTYPE token. The object subtype values are ZPAM-VAL-PORT-TYPE-ENET ZPAM-VAL-PORT-TYPE-LLC1 • You can use the ZCOM-TKN-SEL-SUMSTATE token to alter only objects in a specified summary state.
ALTER PORT Command Commands and Responses ZPAM-ERR-ADDR-ALRDY-DEF is returned from an ALTER PORT command when the LSAP port address specified is in use by another port. You must specify the correct LSAP address. ZCOM-ERR-TKN-CNTXT-VAL-INV is returned when the MAXREQUESTSIZE value specified in an ALTER PORT command is larger than the MAXREQUESTSIZE configured for the associated LINE. You must increase the line’s MAXREQUESTSIZE or decrease the port’s MAXREQUESTSIZE.
DELETE Command Commands and Responses DELETE Command DELETE is a sensitive command that is used to remove PORT objects from the PAM subsystem. LLC2 ports cannot be deleted using this interface. Command ZCOM-CMD-DELETE Object Type ZCOM-OBJ-PORT !r Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZSPI-TKN-MAXRESP ZSPI-TKN-CONTEXT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT token-type ZSPI-TYP-FNAME32. !r token-type ZSPI-TYP-STRING.
DELETE Command Commands and Responses Operational Notes There are several things you should remember when using the DELETE PORT command: • • You can use the ZCOM-TKN-SEL-SUMSTATE token to delete only those PORT objects that are currently in a specified summary state. The only acceptable value for this token is ZCOM-VAL-SUMSTATE-STOPPED. The DELETE command leaves PORT objects in an undefined state.
GETVERSION Command Commands and Responses GETVERSION Command GETVERSION is a nonsensitive command that returns version information for the specified LINE or PROCESS object.(The GETVERSION command is implemented as the VERSION command in SCF).
GETVERSION Command Commands and Responses Tokens in Response Buffer In addition to the tokens described in Section 4, Common Definitions, the following tokens are also present in the response returned for the GETVERSION command: ZSPI-TKN-SERVER-BANNER contains the version information for the software and/or firmware that is running in the specified object.
GETVERSION Command Commands and Responses Error-Handling Notes ZSPI-TKN-RETCODE is the standard SPI return-code token, whose value is a number identifying successful completion (ZCOM-ERR-OK) or an error.
INFO Command Commands and Responses INFO Command INFO is a nonsensitive command that returns information about the attributes of the specified object.
INFO Command Commands and Responses Tokens in Response Buffer Most of the tokens present in the responses returned by the INFO command are described in Section 4, Common Definitions. However, the individual INFO command descriptions that follow provide explanations of the fields in the extensible structured INFO tokens returned for particular objects.
INFO LINE Command Commands and Responses INFO LINE Command INFO LINE is a nonsensitive command that returns the current attribute information for the specified line. Additional Tokens in Response Buffer ZPAM-MAP-INFO-LINE def ZPAM-DDL-INFO-LINE. 02 ZMAX-FS-REQ-SIZE 02 ZLIF-NAME 02 02 ZLIF-TYPE ZLIF-MAC-ADDR type ZSPI-DDL-INT. type ZSPI-DDL-CHAR. occurs 8 times. type ZSPI-DDL-INT. type ZSPI-DDL-BYTE. occurs 6 times. !r !r !r !r end.
INFO MSAP SNATR Command Commands and Responses INFO MSAP SNATR Command INFO MSAP SNATR is a nonsensitive command that returns the current attribute information for the specified message system access point. (MSAP). Additional Tokens in Response Buffer ZPAM-MAP-INFO-MSAP-SNATR def ZPAM-DDL-INFO-MSAP-SNATR. 02 ZMAX-PORTS type ZSPI-DDL-INT. end. !r ZPAM-MAP-INFO-MSAP-SNATR is an extensible structured token that contains the current attribute information for the specified message system access point.
INFO PORT Command Commands and Responses INFO PORT Command INFO PORT is a nonsensitive command that returns the current attribute information for the specified port. Additional Tokens in Response Buffer ZPAM-MAP-INFO-PORT def ZPAM-DDL-INFO-PORT. 02 ZADDR 02 ZMAC-ADDR-IP 02 ZMAC-ADDR 02 02 02 02 02 02 02 02 02 02 end. ZDELIV-MODE-IP ZDELIV-MODE ZMAX-REQ-SIZE ZDATA-FWD-TIME ZDATA-FWD-CNT ZLLC2-ENABLED ZMAX-SESS ZMAX-REQ-SIZE2 ZDATA-FWD-TIME2 ZDATA-FWD-CNT2 type ZSPI-DDL-INT. !r type ZSPI-DDL-BOOLEAN.
INFO PORT Command Commands and Responses ZDELIV-MODE determines how read requests are queued. If ZPAM-VAL-DELIV-MODE-SRL (serial mode, which is the default mode) is selected, all read requests are placed in a single queue and are serviced in FIFO (first in first out) order. If ZPAM-VALDELIV-MODE-PLLEL (parallel mode) is selected, all read requests are placed in separate queues, one for each opener of the port. Inbound messages are delivered to each opener that has a read request posted.
INFO PORT Command Commands and Responses ZMAX-REQ-SIZE2 is the maximum size (in bytes) of a block of messages that can be written and read by the port. This value cannot be larger than the line’s MAXREQUESTSIZE. This attribute is valid only for LLC2 ports. The default value is 32000 bytes. ZDATA-FWD-TIME2 is the maximum amount of time that an inbound message should wait before it is delivered (data forward time). The waiting time is expressed in microseconds.
LISTOBJECTS Command Commands and Responses LISTOBJECTS Command LISTOBJECTS is a nonsensitive command that returns a list of object names for the specified object type that are known to the PAM subsystem. The objects listed depend on the values of the ZSPI-TKN-OBJECT-TYPE and ZCOM-TKN-OBJNAME tokens.
LISTOBJECTS Command Commands and Responses Operational Notes • • • The ZCOM-TKN-OBJNAME token can contain a specific object name or an objectname template, be zero length, or be absent. In some cases, only the object type and/or a single object name are listed because there is only one such object in a PAM subsystem. However, in most cases the ZCOM-TKN-OBJNAME token contains an object-name template, and all objects that meet the template requirements are listed in the response.
LISTOPENS Command Commands and Responses LISTOPENS Command LISTOPENS is a nonsensitive command that returns information about the origin of the link—the opener of the specified object. The LISTOPENS command does not apply to LLC2 ports.
LISTOPENS Command Commands and Responses Tokens in Response Buffer Most of the tokens received in response to the LISTOPENS command are described in Section 4, Common Definitions. However, the following tokens are also present in the response returned for the LISTOPENS command. Additional Tokens in Response Buffer ZPAM-MAP-OPNRS def ZPAM-DDL-OPNRS. 02 ZNODE 02 ZBKUP-CPU 02 ZBKUP-PIN 02 ZPRIM-CPU 02 ZPRIM-PIN 02 ZPROC-NAME end. type type type type type type ZSPI-DDL-INT2. ZSPI-DDL-INT. ZSPI-DDL-UINT.
LISTOPENS Command Commands and Responses Operational Notes There are several things you should remember when using the LISTOPENS command: • You can use the ZCOM-TKN-SUB token to obtain a list of the openers of the specified object and/or its subordinates, if any. The values for this token are as follows: ZCOM-VAL-SUB-ALL lists the openers of the specified object and its subordinate objects, if any.
RESETSTATS Command Commands and Responses RESETSTATS Command RESETSTATS is a sensitive command that returns the current statistical information and then resets the statistics counters to zero. A timestamp is associated with each counter returned, indicating when the sample was taken. Several counters can share the same timestamp. In addition, there is also a second timestamp associated with each resettable counter, recording when the counter was last reset.
START Command Commands and Responses START Command START is a sensitive command that can cause implicit links to be created both to and from the specified object. This command can cause reset or other starting actions required to cause objects to go to the STARTED summary state.
START Command Commands and Responses Operational Notes There are a number of things you should remember when using the START command: • The PORT object returns an object subtype in the ZPAM-TKN-OBJ-SUBTYPE token. The object subtype values are ZPAM-VAL-PORT-TYPE-ENET ZPAM-VAL-PORT-TYPE-LLC1 • You can use the ZCOM-TKN-SUB token to start the specified object and/or subordinate objects.
START Command Commands and Responses Error-Handling Notes ZSPI-TKN-RETCODE is the standard SPI return-code token, whose value is a number identifying successful completion (ZCOM-ERR-OK) or an error. Errors that can occur in response to the START command are as follows: ZCOM-ERR-OBJ-ALRDY-IN-SUMSTATE is returned if the specified object is already in the STARTED summary state, which is normally the end result of the START command.
STATISTICS Command Commands and Responses STATISTICS Command STATISTICS is a nonsensitive command that returns current statistical information for the specified object but does not reset the statistics counters to zero.
STATISTICS Command Commands and Responses Statistics Command continued Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZSPI-TKN-MAXRESP ZSPI-TKN-CONTEXT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT ZSPI-TKN-DATALIST ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZPAM-TKN-OBJ-SUBTYPE ZPAM-MAP-STATS-LINE !LINE ZPAM-MAP-STATS-MESSAGES !LINE ZPAM-MAP-STATS-LIF !LINE ZPAM-MAP-STATS-MEMORY !LINE ZPAM-MAP-STATS-MDS !LINE ZPAM-MAP-STATS-FILE-SYS !LINE ZPAM-MAP-STATS
STATISTICS Command Commands and Responses Tokens in Response Buffer Most of the tokens received in the buffers returned in response to the RESETSTATS and STATISTICS commands are described in Section 4, Common Definitions. However, the individual response descriptions that follow provide explanations of the fields in the extensible structured RESETSTATS or STATISTICS tokens returned for particular objects.
STATISTICS LINE Command Commands and Responses STATISTICS LINE Command STATISTICS LINE is a nonsensitive command that returns current statistics information for the specified line but does not reset the counters. Additional Tokens in Response Buffer ZPAM-MAP-STATS-LINE def ZPAM-DDL-STATS-LINE. 02 ZRESET-TIME 02 ZCURR-TIME end. type ZSPI-DDL-TIMESTAMP.!r type ZSPI-DDL-TIMESTAMP.!r def ZPAM-DDL-STATS-MESSAGES.
STATISTICS LINE Command Commands and Responses Additional Tokens in Response Buffer continued def ZPAM-DDL-STATS-MEMORY. 02 ZCURR-ALLOC 02 ZMAX-ALLOC 02 ZTOTAL-ALLOC 02 ZTOTAL-DEALLOC 02 ZLAST-FAIL-SIZE 02 ZFAIL-CNT end. type type type type type type ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT. ZSPI-DDL-INT. !r !r !r !r !r !r def ZPAM-DDL-STATS-MDS. 02 ZOUT-MDS 02 ZOUT-DUP-MDS 02 ZOUT-RET-MDS 02 ZOUT-MDS-HI-WATER 02 ZIN-MDS 02 ZIN-RET-MDS 02 ZIN-MDS-HI-WATER end.
STATISTICS LINE Command Commands and Responses ZREQS-IN is the number of message system requests received by PAM from other processes such as SNAX and port interface applications. ZREPS-IN is the number of replies to message system requests received by PAM. ZCANCELS-IN is the number of cancels received by PAM to message system requests previously received by PAM. ZREQS-OUT is the number of message system requests sent by PAM to other processes (such as SNAX).
STATISTICS LINE Command Commands and Responses ZFAIL-CNT is the total number of buffer allocation failures. ZOUT-MDS is the number of MD gets to send data from PAM to the LIF or PAMMAN. (MD is an internal QIO data structure.) ZOUT-DUP-MDS is the number of QIO duplicate MD gets to send data from PAM to the LIF. ZOUT-RET-MDS is the number of MDs returned that were acquired to send data out. ZOUT-MDS-HI-WATER is the maximum number of outbound MDs acquired at any given time.
STATISTICS LINE Command Commands and Responses ZLIF-REG-COMPL-FAILS is the number of successful LIF register attempts that failed. ZLIF-DEREG-COMPL-OKS is the number of LIF deregister completion oks received by PAM. ZLIF-DEREG-COMPL-FAILS is the number of LIF deregister requests that failed. ZLIF-PUTS QIO queue puts to the LIF and PAMMAN. (A PUT is a driver call to output data.) ZLIF-PUT-FAILS is the number of QIO queue puts that failed.
STATISTICS PORT Command Commands and Responses STATISTICS PORT Command STATISTICS PORT is a nonsensitive command that returns statistical information for the specified PORT but it does not reset any of the counters. Additional Tokens in Response Buffer ZPAM-MAP-STATS-PORT def ZPAM-DDL-STATS-PORT.
STATISTICS PORT Command Commands and Responses 02 02 02 02 02 02 02 end. ZCHG-REQ ZDEV-INFO-REQ ZSUBDEV-INFO-REQ ZSUBDEV-NAME-REQ ZGETPARAM-REQ ZSETPARAM-REQ ZOTHER-REQ type type type type type type type ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. ZSPI-DDL-INT2. !r !r !r !r !r !r !r ZPAM-MAP-STATS-PORT is an extensible structured token that contains the current statistical information for the specified PORT.
STATISTICS PORT Command Commands and Responses ZOPEN-LS-REQS-REJD is the count of open link stations received by the PAM subsystem from SNAX/XF or SNAX/APN that were rejected by the PAM subsystem. This field is valid only for LLC2 ports. ZCONN-LS-REQS-RECVD is the count of connect link stations requests received by the PAM subsystem from SNAX/XF or SNAX/APN. This field is valid only for LLC2 ports.
STATISTICS PORT Command Commands and Responses ZCONN-LS-NOTIF-REJD is the count of connect LS notifications sent by the PAM subsystem to SNAX/XF or SNAX/APN that were rejected by SNAX/XF or SNAX/APN. This field is valid only for LLC2 ports. ZSTATUS-CHG-NOTIF-SENT is the count of status change notifications sent by the PAM subsystem to SNAX/XF or SNAX/APN. This field is valid only for LLC2 ports.
STATISTICS PORT Command Commands and Responses ZWRITEREAD-REQ is the number of file-system WRITEREAD requests received by the port. ZSETMODE-REQ is the number of file-system SETMODE requests received by the port. ZGETMODE-REQ is the number of file-system GETMODE requests received by the port. ZOPEN-REQ is the number of file-system OPEN requests received by the port. ZCLOSE-REQ is the number of file-system CLOSE requests received by the port.
Commands and Responses STATISTICS PORT Command ZSETPARAM-REQ is the number of file-system SETPARAM requests received by the port. ZOTHER-REQ is the number of other file-system requests received by the port.
STATISTICS SESSION Command Commands and Responses STATISTICS SESSION Command STATISTICS SESSION is a nonsensitive command that returns statistical information for a specified session. Additional Tokens in Response Buffer ZPAM-MAP-STATS-SESS def ZPAM-DDL-STATS-SESS.
STATISTICS SESSION Command Commands and Responses ZI-FRAMES-RECVD specifies the number of I frames received by this session. ZRNR-FRAMES-XMITD specifies the number of RNR frames sent by this session. ZRNR-FRAMES-RECVD specifies the number of RNR frames received by this session. ZREJ-FRAMES-XMITD specifies the number of REJ frames sent by this session. ZREJ-FRAMES-RECVD specifies the number of REJ frames received by this session.
STATISTICS SESSION Command Commands and Responses ZXMIT-ERRS specifies the number of frames transmitted with an error. ZACK-TIMER-EXPS specifies the number of times the ACK timer expired. ZINACTV-TIMER-EXPS specifies the number of times the inactive timer expired. ZMAX-XMIT-Q-CNT specifies the largest size of the transmit queue of this link station since the last RESETSTATS command.
STATISTICS SESSION Command Commands and Responses ZCOM-VAL-SUB-ONLY returns statistical information for subordinate objects, but does not return information for the specified object. • You can use the ZCOM-TKN-SEL-SUMSTATE token to return statistical information for only those objects that are currently in the STARTED summary state.
STATUS Command Commands and Responses STATUS Command STATUS is a nonsensitive command that returns the current status information for the specified object. This command also returns the current summary state and the error number of the last detected error (LASTERROR). This error is the file-system error (FExxx) or any error meaningful to the subsystem that was detected for the specified object.
STATUS Command Commands and Responses Status Command continued Tokens in Command Buffer ZSPI-TKN-MANAGER ZCOM-TKN-OBJNAME ZCOM-TKN-SUB ZCOM-TKN-SEL-SUMSTATE ZSPI-TKN-MAXRESP ZSPI-TKN-CONTEXT ZSPI-TKN-RESPONSE-TYPE ZSPI-TKN-ALLOW-TYPE ZSPI-TKN-COMMENT token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-FNAME32. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-INT-PAIR. ZSPI-TYP-INT. ZSPI-TYP-BYTESTRING. ZSPI-TYP-ENUM. ZSPI-TYP-ENUM. ZSPI-TYP-STRING.
STATUS LINE Command Commands and Responses STATUS LINE Command STATUS LINE is a nonsensitive command that returns current status information for the specified line. Additional Tokens in Response Buffer ZPAM-MAP-STATUS-LINE def ZPAM-DDL-XSTATUS-LINE. 02 ZCURR-STATE 02 ZLOGCL-DEV-NUM 02 ZPCPU 02 ZBCPU 02 ZPPIN 02 ZBPIN 02 ZNUM-OF-PORTS 02 ZTRACE-ON end. type type type type type type type type ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT.
STATUS LINE Command Commands and Responses ZNUM-OF-PORTS is the number of ports (PORT objects) configured on this line. ZTRACE-ON indicates whether or not a trace of this line is active.
STATUS MSAP SNATR Command Commands and Responses STATUS MSAP SNATR Command The STATUS MSAP SNATR command returns current status information for the message-system access point (MSAP). Additional Tokens in Response Buffer ZPAM-MAP-STATUS-MSAP-SNATR def ZPAM-DDL-STATUS-MSAP-SNATR. 02 ZCURR-STATE type ZSPI-DDL-ENUM. 02 ZCURR-NUM-PORTS type ZSPI-DDL-INT. 02 ZCURR-NUM-SESS type ZSPI-DDL-INT. end.
STATUS PORT Command Commands and Responses STATUS PORT Command STATUS PORT is a nonsensitive command that returns current status information for the specified PORT. Additional Tokens in Response Buffer ZPAM-MAP-STATUS-PORT def ZPAM-DDL-STATUS-PORT. 02 ZCURR-STATE 02 ZSDN 02 ZNUM-OF-OPENS 02 ZMAX-SDU-DATA-SIZE 02 ZNUM-OF-SESS 02 ZSNA-RECV-WIN 02 ZSNA-XMIT-WIN end. type type type type type type type ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT. ZSPI-DDL-INT.
STATUS PORT Command Commands and Responses ZSNA-RECV-WIN is the maximum number of RCV-AGSDU requests that the IOP allows to be outstanding to the SNAX process. When the limit is reached, new incoming AGSDUs are queued for the port. This field is valid only for LLC2 type ports. ZSNA-XMIT-WIN is the maximum number of SEND-AGSDU requests that the SNAX process can have outstanding for the port. This field is valid only for LLC2 type ports.
STATUS SESSION Command Commands and Responses STATUS SESSION Command STATUS SESSION is a nonsensitive command that returns current status information for the specified session. Additional Tokens in Response Buffer ZPAM-MAP-STATUS-SESS def ZPAM-DDL-STATUS-SESS.
STATUS SESSION Command Commands and Responses ZSESS-STATE specifies the data transfer state of the session. The valid values for ZPAM-VALSESS-STATE are as follows: ADM Asynchronous Disconnect Mode. AWAIT Data transfer mode; local set timer ready for reply. AWAIT-BUSY Combined effect of AWAIT and BUSY. AWAIT-REJ Combined effect of AWAIT and REJECT. BUSY Data transfer mode, but local may be busy. DISC LLC sent DISC awaiting for reply. ERROR Error detected; FRMR sent await for reply.
STATUS SESSION Command Commands and Responses ZPAM-SESS-ID a unique ID used by the PAM subsystem for this session. ZRMT-MAC-ADDR specifies the MAC address of the remote session. ZRMT-SAP-ADDR specifies the SAP value of the remote session. ZPT-LOST-LINK-NO-ACK specifies that the LS has entered the reset state because of an exhausted retry count. A SABME command has been sent to the remote LS.
STATUS SESSION Command Commands and Responses ZRPT-SABME-FRM-RCVD specifies that the LS has received a SABME frame. Prior to link connect, this notification implies a connect request from the remote station; otherwise, it implies link reset. A CLOSE_LS command may be issued. STATUS_CODE_MOD: None. ZRPT-RESET specifies that the reset procedure initiated from the local link station is accepted by the remote LS and the reset is complete. The LS has returned to normal data transfer state.
STATUS SESSION Command Commands and Responses ZACCESS-PRI specifies which priority to place in the AC field of all frames sent from this session. No default value is specified. ZROUTE-INFO specifies routing information to be added to all frames sent from this session. Up to 36 hexadecimal digits may be displayed. Operational Notes There are a number of things you should remember when using the STATUS command: • The PORT object returns a ZPAM-TKN-OBJ-SUBTYPE token in each response.
STATUS SESSION Command Commands and Responses Error Handling Notes ZSPI-TKN-RETCODE is the standard SPI return code token, whose value is a number identifying successful completion (ZCOM-ERR-OK) or an error. An error can that can occur in response to the STATUS command is as follows: ZPAM-ERR-LIF-DOWN is returned when the LINE specified in a STATUS SESSION command is not started and the adapter is not loaded.
STOP Command Commands and Responses STOP Command STOP is a sensitive command that deletes implicit and explicit links both to and from the object.
STOP Command Commands and Responses Operational Notes There are a number of things you should remember when using the STOP command: • • The STOP command stops the PAM process (it will no longer run). You can use the ZCOM-TKN-SUB token to stop the operation of the specified object and/or subordinate objects. The acceptable values for this token are as follows: ZCOM-VAL-SUB-ALL stops the operation of the specified object and its subordinate objects, if any.
STOP Command Commands and Responses ZPAM-ERR-NO-STOP-OBJ-ACTV is returned if any subordinate object has open requests outstanding. You must stop the activity in progress on the subordinate objects or use the ABORT command instead of the STOP command.
SWITCH Command Commands and Responses SWITCH Command SWITCH is a sensitive command that switches a specified line between the primary processor and the backup processor, or it initiates a planned takeover of the backup processor. The line must be started before it can be switched. (The SWITCH command is implemented as the PRIMARY command in SCF.
SWITCH Command Commands and Responses Tokens in Response Buffer The tokens present in the response buffer returned for the SWITCH command are described in Section 4, Common Definitions. Operational Notes There are a number of things you should remember when using the SWITCH command: • • • • You can use the ZCOM-TKN-SEL-SUMSTATE token to switch only a line that is currently in the STARTED summary state.
TRACE Command Commands and Responses TRACE Command TRACE is a sensitive command that initiates, modifies, or terminates trace mode on the specified object.
TRACE LINE Command Commands and Responses TRACE LINE Command The TRACE LINE command returns trace information for a specified line.
TRACE LINE Command Commands and Responses Error Handling Notes ZSPI-TKN-RETCODE is the standard SPI return code token, whose value is a number identifying successful completion (ZCOM-ERR-OK) or an error. Errors that can occur in response to the TRACE command are as follows: ZCOM-ERR-TKN-REQ is returned when a required token is missing. You must supply all required tokens. ZCOM-ERR-TKN-VAL-INV is returned when a specified field (token and offset) has an incorrect value.
6 Event Messages Event reporting enables the system operator to monitor and control the operation of the PAM subsystem. The Event Management Service (EMS) collects, logs, and distributes event messages that contain information that helps the operator to monitor the network environment, analyze failures, and recognize and handle critical problems. This section describes the content and meaning of all event messages generated by the PAM subsystem.
Subsystem ID (SSID) Event Messages Table 6-1. PAM Event Messages (page 2 of 2) Event Number Symbolic Name (ZPAM-EVT-) 213 TR-NOTIF-NOT-DELIV PAM could not deliver notifications from Token-Ring ServerNet adapter to SNAX linehandler process. 214 TR-REQ-NOT-SENT PAM process could not send requests from SNAX line-handler process to Token-Ring ServerNet adapter 215 BACKUP-STARTUPFAILED PAM backup process cannnot start.
Event Numbers Event Messages Event Numbers An event number is part of the header of an event message. The header token named ZEMS-TKN-EVENTNUMBER contains the event number. The value of the event number is subsystem-specific and is represented by its symbolic name. Because event numbers are not unique across subsystems, you must know both the event number and the four-character abbreviation of the subsystem that created the event.
Tokens in All Event Messages Event Messages ZSPI-TKN-MAX-FIELD-VERSION contains the highest version of any field of any extensible structured token and is supplied by ESP. ZSPI-TKN-USEDLEN contains the real buffer length used and is supplied by ESP for PAM events. ZSPI-TKN-SSID contains ZPAM-VAL-SSID, the subsystem ID of the PAM subsystem. ZPAM-VALSSID has the following structure definition: def ZPAM-VAL-SSID TACL SSID.
Tokens in All Event Messages Event Messages ZEMS-TKN-LOGTIME contains the time when the event was logged. ZEMS-TKN-PIN contains the process ID number (PIN) of the reporting subsystem process. ZEMS-TKN-SYSTEM contains the system number of the reporting subsystem. ZEMS-TKN-USERID contains the user ID of the reporting subsystem process. ZEMS-TKN-SUBJECT-MARK indirectly indicates the subject token, which is ZPAM-TKN-FNAME for PAM events.
Event Message Descriptions Event Messages Event Message Descriptions The remainder of this section explains in detail each event message that can be issued by the PAM subsystem. Each description includes a syntax box that lists all the tokens that the PAM subsystem can place in the message buffer. The common tokens are listed in Table 6-3. Tokens appear in the box if they are present in all PAM event messages or if their values differ from one event message to another.
201: ZPAM-EVT-AGGR-SDU-NOT-DELIV Event Messages 201: ZPAM-EVT-AGGR-SDU-NOT-DELIV This event is generated when an inbound aggregate SDU is delivered to the port module but cannot be delivered to a client (user of a port module).
201: ZPAM-EVT-AGGR-SDU-NOT-DELIV Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VALTRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
201: ZPAM-EVT-AGGR-SDU-NOT-DELIV Event Messages ZPAM-VAL-CAUSE-BAD-ADDR The aggregate SDU contained a bad address. Probable Cause An inbound aggregate SDU was delivered to the port module but could not be delivered to a client (user of a port module). Recommended Action If the aggregate SDU could not be read, the subsystem is able to deliver aggregate SDUs faster than the client can post file-system reads.
202: ZPAM-EVT-BAD-AGGR-SDU Event Messages 202: ZPAM-EVT-BAD-AGGR-SDU This event is generated when the client delivers an aggregate SDU to the subsystem that does not conform to the rules governing the format of these messages.
202: ZPAM-EVT-BAD-AGGR-SDU Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VALTRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
202: ZPAM-EVT-BAD-AGGR-SDU Event Messages Recommended Action The client should isolate the bad message, determine where it deviates from the proper format, and fix the offending code.
203: ZPAM-EVT-CHKPT-FAILED Event Messages 203: ZPAM-EVT-CHKPT-FAILED This event is generated when the backup process cannot process a checkpoint.
203: ZPAM-EVT-CHKPT-FAILED Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VALTRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
203: ZPAM-EVT-CHKPT-FAILED Event Messages Probable Cause The backup process cannot process a checkpoint. Recommended Action Halt and dump the processor of the PAM backup process, then reload.
204: ZPAM-EVT-CPU-SWITCHED Event Messages 204: ZPAM-EVT-CPU-SWITCHED The PAM process switched from the primary to the backup CPU because the associated LIF access is not available in the current primary. All requests owned by the PAM process will be flushed with file-system error 210.
204: ZPAM-EVT-CPU-SWITCHED Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
204: ZPAM-EVT-CPU-SWITCHED Event Messages Recommended Action If the PAM process keeps switching or does not recover, check the status of the associated LIF and PIF by using LANMON commands and change the access of the LIF to the desired processor. Bring up the LIF and PIF if they are down.
205: ZPAM-EVT-DEV-DOWN Event Messages 205: ZPAM-EVT-DEV-DOWN This event is generated when the operator stops the line with a Subsystem Control Facility (SCF) command, or the line stops itself because of a serious error.
205: ZPAM-EVT-DEV-DOWN Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
206: ZPAM-EVT-DEV-UP Event Messages 206: ZPAM-EVT-DEV-UP This event is generated when the operator successfully returns the device to the system through a Subsystem Control Facility (SCF) START command.
206: ZPAM-EVT-DEV-UP Event Messages ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files. ZEMS-TKN-PIN is the process ID number (PIN) of the reporting subsystem process.
207: ZPAM-EVT-INTL-ERR Event Messages 207: ZPAM-EVT-INTL-ERR This event is generated when the PAM subsystem detects a serious internal error. It is generated at the point the PAM subsystem detected the error.
207: ZPAM-EVT-INTL-ERR Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
207: ZPAM-EVT-INTL-ERR Event Messages Recommended Action Halt and dump the processor of the reporting process, then reload.
208: ZPAM-EVT-IO-PROC-ABENDED Event Messages 208: ZPAM-EVT-IO-PROC-ABENDED This event is generated when the PAM process detects an error at process initiation time and is unable to go on.
208: ZPAM-EVT-IO-PROC-ABENDED Event Messages ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message.
208: ZPAM-EVT-IO-PROC-ABENDED Event Messages ZPAM-VAL-ABEND-CONFIG-ERR System configuration error. ZPAM-VAL-ABEND-FUNC-NOT-IMP The PAM process entered into an unexpected function. ZPAM-VAL-ABEND-NSK-PROC-ERR The PAM process received an unexpected error from an NSK function call. ZPAM-VAL-ABEND-INTERNAL-ERR The PAM process received an unexpected internal error. ZPAM-VAL-ABEND-CONFIG-LIF-ERR The associated LIF specified in PAM startup does not exist or returned an error.
208: ZPAM-EVT-IO-PROC-ABENDED Event Messages ZPAM-VAL-ABEND-CONFIG-BRO-INV The backup processor specified while starting PAM was either out of range or the same as the primary processor. Restart PAM with the correct backup processor value. ZPAM-VAL-ABEND-CONFIG-LIF-INV The LIF name was incorrectly specified while starting up PAM. Restart PAM with the correct LIF name. ZPAM-VAL-ABEND-CONFIG-MAX-INV The maximum request size was incorrectly specified while starting up PAM. The valid range is 128-32000.
209: ZPAM-EVT-PORT-CONFIG-ERR Event Messages 209: ZPAM-EVT-PORT-CONFIG-ERR This event is generated when a problem is encountered during communication with the adapter during the START/STOP PORT phase.
209: ZPAM-EVT-PORT-CONFIG-ERR Event Messages ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message.
209: ZPAM-EVT-PORT-CONFIG-ERR Event Messages Recommended Action Recovery depends on the type of problem. If this event is followed by the event ZPAMEVT-PORT-CONFIG-FAILED, the port has not entered the STARTED state. Issue the START command again.
210: ZPAM-EVT-PORT-CONFIG-FAILED Event Messages 210: ZPAM-EVT-PORT-CONFIG-FAILED This event is generated when PAM could not configure a port.
210: ZPAM-EVT-PORT-CONFIG-FAILED Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
Event Messages 210: ZPAM-EVT-PORT-CONFIG-FAILED If your local operating procedures require contacting the Global Customer Support Center, supply your system number and the numbers and versions of all related products as well.
211: ZPAM-EVT-SM-ERR Event Messages 211: ZPAM-EVT-SM-ERR This event is generated when a problem is encountered in one of the state machines in PAM.
211: ZPAM-EVT-SM-ERR Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
211: ZPAM-EVT-SM-ERR Event Messages Recommended Action Reconfigure the PORT or SAP object and continue operation.
212: ZPAM-EVT-UNEXP-CTLR-RESP Event Messages 212: ZPAM-EVT-UNEXP-CTLR-RESP This event is generated when the PAM process receives an invalid response from the Token-Ring ServerNet adapter. The CTLR frame is discarded. The operation continues; however, requests might be lost as the result of this event.
212: ZPAM-EVT-UNEXP-CTLR-RESP Event Messages ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message.
212: ZPAM-EVT-UNEXP-CTLR-RESP Event Messages ZPAM-TKN-CTLR-FUNC is the FUNC field in the received response. ZPAM-TKN-CTLR-MOD is the MOD field in the received response. Probable Cause An unexpected CTLR response was received by the PAM process.
213: ZPAM-EVT-TR-NOTIF-NOT-DELIV Event Messages 213: ZPAM-EVT-TR-NOTIF-NOT-DELIV This event is generated when the PAM process could not deliver notifications from the Token-Ring ServerNet adapter to the SNAX line-handler process.
213: ZPAM-EVT-TR-NOTIF-NOT-DELIV Event Messages ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message.
213: ZPAM-EVT-TR-NOTIF-NOT-DELIV Event Messages Window_Exceeded indicates that the Transmit Window to SNAX is full. SAP_Closed indicates that the SAP (identified by the port name) has already been closed by SNAX. Out_of_Memory indicates that the PAM process ran out of memory, possibly because of heavy traffic. ZPAM-TKN-SEND-COMPL-ERR is the send completion error received by the PAM process when it attempted to send this notification.
214: ZPAM-EVT-TR-REQ-NOT-SENT Event Messages 214: ZPAM-EVT-TR-REQ-NOT-SENT This event is generated when the PAM process could not send requests from the SNAX line-handler process to the Token-Ring ServerNet adapter.
214: ZPAM-EVT-TR-REQ-NOT-SENT Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
214: ZPAM-EVT-TR-REQ-NOT-SENT Event Messages Probable Cause The cause of this error is described in ZPAM-TKN-NOT-SENT-CAUSE. Recommended Action If the cause of the error is LIF Failed, SNAX will be able to reestablish the session when the LIF comes up; no action is necessary.
215: ZPAM-EVT-BACKUP-STARTUP-FAILED Event Messages 215: ZPAM-EVT-BACKUP-STARTUP-FAILED This event is generated when the PAM backup process cannot start.
215: ZPAM-EVT-BACKUP-STARTUP-FAILED Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
Event Messages • • • 215: ZPAM-EVT-BACKUP-STARTUP-FAILED Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operating procedures require contacting the Global Customer Support Center, supply your system number and the numbers and versions of all related products as well.
216: ZPAM-EVT-ERROR-NOTIFICATION Event Messages 216: ZPAM-EVT-ERROR-NOTIFICATION This is a general EMS message from PAM reporting errors encountered in PAM operation, giving context and additional information on errors.
216: ZPAM-EVT-ERROR-NOTIFICATION Event Messages ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message.
216: ZPAM-EVT-ERROR-NOTIFICATION Event Messages ZPAM-TKN-NOTIF-INFO2 provides context pertaining to the error. ZPAM-TKN-MODULE-NAME is the name of the PAM module reporting the error notification. ZPAM-TKN-LINE-NUMBER is the line number in the module reporting the error notification. Probable Cause The cause depends on the notif-func and notif-err.
101: ZPAM-EVT-PAMMAN-ADDOBJ-FAIL Event Messages 101: ZPAM-EVT-PAMMAN-ADDOBJ-FAIL This event is generated when PAMMAN is unable to add an object into its name-space.
101: ZPAM-EVT-PAMMAN-ADDOBJ-FAIL Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
101: ZPAM-EVT-PAMMAN-ADDOBJ-FAIL Event Messages • • The supervisor object is not found in the name-space. There is not enough memory to proceed with this operation. Recommended Action Stop and restart PAMMAN.
102: ZPAM-EVT-PAMMAN-DELOBJ-FAIL Event Messages 102: ZPAM-EVT-PAMMAN-DELOBJ-FAIL This event is generated when PAMMAN is unable to delete an object from its namespace because the name of the object is not found.
102: ZPAM-EVT-PAMMAN-DELOBJ-FAIL Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
102: ZPAM-EVT-PAMMAN-DELOBJ-FAIL Event Messages Recommended Action Stop and restart PAMMAN.
103: ZPAM-EVT-PAMMAN-BAD-FILENAME Event Messages 103: ZPAM-EVT-PAMMAN-BAD-FILENAME This event is generated when the message PAMMAN received through QIO Global Queue contains an object name with a bad file-system naming format.
103: ZPAM-EVT-PAMMAN-BAD-FILENAME Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
103: ZPAM-EVT-PAMMAN-BAD-FILENAME Event Messages Recommended Action Stop and restart PAMMAN.
104: ZPAM-EVT-PAMMAN-BAD-QIOPTR Event Messages 104: ZPAM-EVT-PAMMAN-BAD-QIOPTR This event is generated when PAMMAN receives a bad message descriptor while listening to the QIO Global Queue.
104: ZPAM-EVT-PAMMAN-BAD-QIOPTR Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
104: ZPAM-EVT-PAMMAN-BAD-QIOPTR Event Messages Recommended Action Stop and restart PAMMAN.
105: ZPAM-EVT-PAMMAN-QIOCALL-FAIL Event Messages 105: ZPAM-EVT-PAMMAN-QIOCALL-FAIL This event is generated when PAMMAN detects an error while performing a QIO library operation.
105: ZPAM-EVT-PAMMAN-QIOCALL-FAIL Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
105: ZPAM-EVT-PAMMAN-QIOCALL-FAIL Event Messages Recommended Action This is a serious internal error. Depending on the QIO library function performed, PAMMAN may or may not be able to continue operation.
106: ZPAM-EVT-PAMMAN-FILEOPEN-FAIL Event Messages 106: ZPAM-EVT-PAMMAN-FILEOPEN-FAIL This event is generated when PAM is not responding properly to the FILE_OPEN_ call.
106: ZPAM-EVT-PAMMAN-FILEOPEN-FAIL Event Messages ZEMS-TKN-CONSOLE-PRINT directs the compatibility distributor to process the event message (ZSPI-VAL-TRUE). ZEMS-TKN-CPU is the processor number of the reporting subsystem process. ZEMS-TKN-CRTPID is the CRTPID of the reporting subsystem process. ZEMS-TKN-GENTIME is the time (GMT) that the reporting subsystem created the event message. ZEMS-TKN-LOGTIME is the time (GMT) that the collector wrote the event message to its log files.
Event Messages • • • 106: ZPAM-EVT-PAMMAN-FILEOPEN-FAIL Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable If your local operating procedures require contacting the Global Customer Support Center, supply your system number and the numbers and versions of all related products as well.
Event Messages 106: ZPAM-EVT-PAMMAN-FILEOPEN-FAIL PAM Management Programming Manual—142481 6- 72
A Error Numbers and Error Lists This appendix presents all the error numbers provided by the PAM subsystem (that is, the values whose symbolic names begin with ZPAM-ERR-) and describes the error lists associated with these error numbers. These error numbers can occur as values of the return token, ZSPI-TKN-RETCODE, and as part of the value of the error token, ZSPITKN-ERROR. What error lists are and how they are retrieved from the buffer is described in the SPI Programming Manual.
1: ZPAM-ERR-DEL-SUB-OBJ Error Numbers and Error Lists 1: ZPAM-ERR-DEL-SUB-OBJ A DELETE command was issued to the PAM subsystem for an object that has subordinate objects configured. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
2: ZPAM-ERR-STOP-SUB-OBJ Error Numbers and Error Lists 2: ZPAM-ERR-STOP-SUB-OBJ An ABORT or a STOP command was issued to the PAM subsystem for an object that has active subordinate objects. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
3: ZPAM-ERR-HIGH-OBJ-STATE-EXP Error Numbers and Error Lists 3: ZPAM-ERR-HIGH-OBJ-STATE-EXP A START command was issued to the PAM subsystem for an object that still has a superior object in the ZCOM-VAL-SUMSTATE-STOPPED state. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
4: ZPAM-ERR-SAME-CPU Error Numbers and Error Lists 4: ZPAM-ERR-SAME-CPU A SPI SWITCH command (SCF PRIMARY command) was issued to the PAM subsystem that specified the processor of the current primary PAM process as the target processor. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
5: ZPAM-ERR-NO-STOP-OBJ-ACTV Error Numbers and Error Lists 5: ZPAM-ERR-NO-STOP-OBJ-ACTV A STOP command was issued to the PAM subsystem for an object that has a subordinate object with open requests. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
6: ZPAM-ERR-LIF-DOWN Error Numbers and Error Lists 6: ZPAM-ERR-LIF-DOWN A START LINE, STATUS SESSION, or STATS SESSION command was issued when the LIF was down. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
7: ZPAM-ERR-TRACE-BKUP-UNKWN Error Numbers and Error Lists 7: ZPAM-ERR-TRACE-BKUP-UNKWN The PAM subsystem is unable to trace the backup process for some unknown reason. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
8: ZPAM-ERR-TRACE-IN-PROGRESS Error Numbers and Error Lists 8: ZPAM-ERR-TRACE-IN-PROGRESS A TRACE (start) command was received when the trace was already in progress. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
9: ZPAM-ERR-TRACE-NOT-ACTV Error Numbers and Error Lists 9: ZPAM-ERR-TRACE-NOT-ACTV A TRACE (stop) command was received when the trace was not started. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
10: ZPAM-ERR-TRACE-FUNC-INV Error Numbers and Error Lists 10: ZPAM-ERR-TRACE-FUNC-INV The PAM subsystem received a TRACE command with a trace select function that is not supported. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
11: ZPAM-ERR-ADDR-ALRDY-DEF Error Numbers and Error Lists 11: ZPAM-ERR-ADDR-ALRDY-DEF The PAM subsystem received an ADD PORT or ALTER PORT command with an address already in use by another PORT. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
12: ZPAM-ERR-CMD-INV-IN-SUMSTATE Error Numbers and Error Lists 12: ZPAM-ERR-CMD-INV-IN-SUMSTATE An invalid command was received in the current state of the object. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
13: ZPAM-ERR-REPLY-BUF-TOO-SMALL Error Numbers and Error Lists 13: ZPAM-ERR-REPLY-BUF-TOO-SMALL The PAM subsystem received an ADD PORT or ALTER PORT command with an address already in use by another PORT. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL.
14: ZPAM-ERR-INV-PORT-ADDR Error Numbers and Error Lists 14: ZPAM-ERR-INV-PORT-ADDR A command received an invalid port address. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
15: ZPAM-ERR-INV-LLC2-CMD Error Numbers and Error Lists 15: ZPAM-ERR-INV-LLC2-CMD An SCF command not applicable to LLC2 type ports was issued. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
16: ZPAM-ERR-SNATR-NOT-STOPPED Error Numbers and Error Lists 16: ZPAM-ERR-SNATR-NOT-STOPPED An SCF STOP MSAP #SNATR command was issued when SAPs were open. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
17: ZPAM-ERR-INV-CTLR-ATT Error Numbers and Error Lists 17: ZPAM-ERR-INV-CTLR-ATT An SCF command was issued to add a port type that is incompatible with the type of LIF. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
18: ZPAM-DATA-LEN-INV Error Numbers and Error Lists 18: ZPAM-DATA-LEN-INV An internal data transfer was the wrong-length, probably because of incompatible versions of the PAM software. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
19: ZPAM-ERR-INV-PORT-ATT Error Numbers and Error Lists 19: ZPAM-ERR-INV-PORT-ATT An ADD PORT or ALTER PORT command was received with an invalid attribute. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
20:ZPAM-ERR-PAM-INT-ERR Error Numbers and Error Lists 20:ZPAM-ERR-PAM-INT-ERR An internal error; PAM was unable to perform the PORT command. ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZCOM-TKN-OBJNAME ZCOM-TKN-OBJTYPE ZSPI-TKN-ENDLIST token-type token-type token-type token-type token-type ZSPI-TYP-LIST. ZSPI-TYP-ERROR. ZSPI-TYP-STRING. ZSPI-TYP-ENUM. ZSPI-TYP-SSCTL. Tokens ZSPI-TKN-ERROR is the standard SPI error token, as described in the SPI Programming Manual.
20:ZPAM-ERR-PAM-INT-ERR Error Numbers and Error Lists PAM Management Programming Manual—142481 A -22
B Token Codes and Token Maps Table B-1 is a summary table of all token codes that are specific to the PAM subsystem (token codes that begin with ZPAM-TKN-). For each token code, the token type is given. The symbolic name of the token number of a token code can be derived from the name of the token code by replacing -TKN- with -TNM-; for example, token code ZPAM-TKN-SYSNAME has the token number ZPAM-TNM-SYSNAME. Table B-1.
Token Codes and Token Maps Table B-1.
Token Codes and Token Maps Table B-2.
Token Codes and Token Maps PAM Management Programming Manual—142481 B- 4
C G-Series Migration This appendix is intended for programmers who want to modify Tandem LAN Access Method (TLAM) management applications to manage the PAM subsystem. It is assumed that readers are familiar with the TLAM management programming interface.
Object Type Comparison G-Series Migration Table C-1. PAM and TLAM Object Comparison (page 2 of 2) Object Name PAM TLAM Comments PORT Yes Yes Both subsystems provide the following port types: • Ethernet • LLC1 • LLC2 Only the TLAM subsystem provides the following port types: • SNAP • IPX8022 • IPX8023 • TR8025 In PAM, the TR8025 port type is part of the LLC1 interface.
Command Comparison G-Series Migration Command Comparison The PAM and TLAM subsystems support the same commands; however, because the subsystems support a different set of object types (see Object Type Comparison), the commands accept different object types. Table C-2 lists the PAM programmatic commands and indicates which commands accept which object types. Table C-2.
Command Comparison G-Series Migration Table C-3 lists the TLAM programmatic commands and indicates which commands accept which object types. Table C-3.
Event Message Comparison G-Series Migration Event Message Comparison You must be aware of these differences if you plan to migrate a TLAM management application that retrieves event messages: • • The PAM and TLAM subsystems generate many different event messages. Although some of the event messages generated by the PAM process are similar to those generated by the MLAM process, these messages usually have different event numbers.
Event Message Comparison G-Series Migration The PAM event messages are described in detail in Section 6, Event Messages.
Event Message Comparison G-Series Migration Table C-5 lists all the event messages that can be reported by the MLAM process. Table C-5.
Event Message Comparison G-Series Migration Table C-5. MLAM Event Messages (page 2 of 2) Event Number Symbolic Name (ZLAM-EVT-) 223 INVALID-LB 225 TR-NOTIF-NOT-DELIV 226 TR-REQ-NOT-SENT Note. The event messages generated by MLMUX are not listed in this appendix because they have no PAM subsystem equivalents. Refer to the TLAM Management Programming Manual for more detailed information about the MLAM and MLMUX event messages.
Glossary ABORT command. A sensitive SCF and SPI command that terminates the operation of an object as quickly as possible; only enough processing is done to ensure the subsystem security. ADD command. A sensitive SCF and SPI command that adds an object to the PAM subsystem. Only the PORT object type can be added with the SCF ADD command. All other object types are added when the system is configured. ALTER command.
Distributed Systems Management (DSM) Glossary Distributed Systems Management (DSM). A set of products that supports the integrated management of system and network resources and operation. DSM products include the Subsystem Programmatic Interface (SPI), the Event Management Service (EMS), the Distributed Name Service (DNS), the DSM Template Services, and the Subsystem Control Facility (SCF) for data communications subsystems. E4SA. See Ethernet 4 ServerNet adapter (E4SA). EMS.
LISTDEV command Glossary LISTDEV command. A nonsensitive SCF command that displays information about the specified devices. LISTOBJECTS command. A nonsensitive SPI command that returns the object name and object type of designated objects. Equivalent to the SCF NAMES command. LISTOPENS command. A nonsensitive SCF and SPI command that displays information about the file-system opens that apply to the specified object. LLC1 ports. See logical link control type 1 (LLC1) ports.
PAMMAN Glossary PAMMAN. See PAM Manager (PAMMAN) process. PORT object. A programmatic interface that provides applications with link-level access points (LSAPs). Through the LSAPs, a client or an application process that is running on a server can access a local area network (LAN) through file-system procedure calls. The PORT object provides the following types of LSAPs: Ethernet, LLC1, and LLC2. PROCESS object. Used to define a PAM process.
SLSA subsystem Glossary SLSA subsystem. See ServerNet LAN Systems Access (SLSA) subsystem. SNAX Advanced Peer Networking (SNAX/APN). A software product that enables a Himalaya S-series server to function as a type 2.1 LEN node. The extended version of the product, SNAX/APN-EN, enables a Himalaya S-series server to act as an end node. SNAX/APN. See SNAX Advanced Peer Networking (SNAX/APN). SNAX Extended Facility (SNAX/XF).
Subsystem Control Point (SCP) Glossary Subsystem Control Point (SCP). The management process for all Tandem data communications subsystems. super-ID user. A user who can read, write, execute, and purge most files on the system. A super-ID user is usually a member of a system-supervisor group. a SWITCH. A sensitive SCF and SPI command that causes the backup processor to become the primary processor and the primary processor to become the backup processor. timestamp.
Index A Buffer declaration, PAM 4-10 Buffer size for an event message 3-10 recommended for commands 3-7 recommended for responses 3-8 Building the command buffer 3-7 Commands (continued) interactive vs.
F Index Error numbers A-1 Error token 4-2 Errors See individual error names Event messages buffer size for 3-10 filters for 3-11 issued by PAM subsystem 6-1, 6-2 order of tokens in 6-6 standard header in text of 6-6 text version of 6-6 Events, critical and noncritical 3-10 Extensible structured tokens 3-6 M Features, PAM 1-1 Field types 3-7 File-system interface 1-3 Filters 3-11 Management commands 1-10 Management interface 1-3 Management programming 1-7 Manager token 4-2 Max field version token 4-3 Ma
P Index Object subtypes (continued) in responses (continued) STATUS command 5-65 Object types commands listed by 5-1 of NULL object 4-9 Objects number affected by one command 3-7 number described in one response record 3-8 obtaining status information 5-54 resetting statistics 5-32 Object-name token 4-7 Object-type token 4-4, 4-7 Overview of PAM 1-1 PORT objects subtype Ethernet 1-9 Predefined value names 3-6 PROCESS obtaining statistics from 5-50 tracing 5-73 Process 1-4 Process object 1-8 Programmatic
S Index Response records (continued) number of in one reply message 3-8 number of objects described in 3-8 receiving 3-8 receiving the buffer for 3-8 recommended buffer sizes for 3-8 Responses extensible structured tokens in 3-6 notation used to describe 5-2 Return code token 4-3 Role, of PAM 1-2 S SCF object hierarchy 1-8 SCF objects 1-8/1-10 SEL-SUMSTATE modifier ABORT command 5-4 ALTER command 5-13 DELETE PORT command 5-16 LISTOBJECTS command 5-28 LISTOPENS command 5-31 START command 5-34 STATUS comma
V Index Tokens (continued) token maps 3-6 token types 3-6 Trace options token 4-7 V Value names, predefined 3-6 W Warnings ZCOM-ERR-OBJ-ALRDY-INSUMSTATE ABORT command 5-4 START command 5-35 STOP command 5-68 ZPAM-ERR-CTLR-NOT-LOADED STATUS command 5-66 Z ZCOM-MAP-TRACE-MODIF 4-8 ZCOM-OBJ-NULL 4-9 ZCOM-TKNOBJNAME 4-7 OBJTYPE 4-7 SWITCH-CPU 5-70 TRACE-OPT 4-7 ZEMS-TKNEMPHASIS 3-11 SUBJECT-MARK 6-6 ZPAM subsystem ID 4-11 ZPAM-DDL-MSG-BUFFER 4-10 ZPAM-ERRADDR-ALRDY-DEF A-12, A-14 HIGH-OBJ-STATE-EXP A-4 NO-
Z Index ZPAM-VAL-ABEND (continued) CONFIG-ERR 6-28 CONFIG-LIF-ERR 6-28 CONFIG-LIF-INV 6-29 CONFIG-LIF-NO-D-ACC 6-28 CONFIG-MAX-INV 6-29 CONFIG-QUE-INV 6-29 FUNC-NOT-IMP 6-28 INIT-CHKPT-ERR 6-29 INTERNAL-ERR 6-28 LIF-NO-P-ACC 6-28 NSK-PROC-ERR 6-28 ZSPI-SSNZPAM 4-5 ZSPI-TKNALLOW-TYPE 3-9 COMMAND 4-3 ENDLIST A-1 ERRLIST A-1 ERROR 4-2 MANAGER 4-2 MAXRESP 3-8, 4-4 MAX-FIELD-VERSION 4-3 OBJECT-TYPE 4-4 RETCODE 4-3 SERVER-VERSION 4-4 SSID 3-3, 4-4 ZSPI-TKN-RETCODE ABORT command 5-4 ADD command 5-8 ALTER command
