Networking and Data Communications Library SNAX/XF LU Network Services Manual Abstract Part Number Edition Published Product Version Release ID Supported Releases This manual is directed to systems managers and systems programmers and describes how to configure the LU network services (LUNS) interface to SNAX/XF and the Creator process. 105782 Fifth December 1994 SNAX/XF D30 (T9064D30) D30.00 This manual supports release D30.00 and all subsequent releases until otherwise indicated in a new edition.
Document History Edition Part Number Product Version Earliest Supported Release Published First Second Third Fourth Fifth 084247 052965 069610 097841 105782 SNAX/XF C11 SNAX/XF C20 SNAX/XF D10/C30 SNAX/XF D21 SNAX/XF D30 C10 C20 D10.00/C30.00 D72.00 based on D20.01 D30.00 March 1989 April 1991 February 1993 April 1994 December 1994 New editions incorporate any updates issued since the previous edition.
New and Changed Information In addition to editorial changes, the following information has been changed in this manual: Throughout the manual, the term “logical name” has been replaced. Where logical name referred to a Tandem subdevice name, it has been replaced by the term “subdevice name.” Where logical name referred to a name configured on a host system, it has been replaced by the term “SNA name.
New and Changed Information (This page left intentionally blank) iv 097841 Tandem Computers Incorporated
Contents About This Manual xi Notation Conventions Section 1 xiii Introduction to LUNS What LUNS Does 1-1 Terminal Interface to LUNS 1-2 Logging On to Order Entry 1-2 Logging On to TSO 1-3 Establishing a Static Passthrough Path 1-3 The Creator and SNAX Creator-2 Processes 1-3 Defining Processes to LUNS 1-3 Starting TACL Processes With the Creator Process 1-4 Starting Pathway Processes With the Creator Process 1-4 LUNS Configuration Tables 1-4 Notation Used for Configuration Tables 1-4 The ESS Tab
Contents Modifying ESS Tables Dynamically Specifying the SET Table 2-16 2-17 Specifying SCF Configuration Parameters The ALTER Command 2-18 The ADD APPL Command 2-18 The ABORT APPL Command 2-21 2-18 The ADD LINE, PU, and LU Command Attributes AUTOLOGON Attribute 2-22 ESSTABLE Attribute 2-23 NOACQ Attribute 2-24 ESS LU Attributes That Override SCF LU Attributes BINDENTRY Attribute 2-25 BINDTABLE Attribute 2-25 CHARACTERSET Attribute 2-26 PROTOCOL Attribute 2-27 RECSIZE Attribute 2-27 SCF Attribute Summ
Contents Appendix A The SNAX/XF Utility Introduction A-1 SNAXUTL Command Syntax A-1 General Syntax A-2 Invoking the Program A-5 SNAXUTL ADD Commands A-6 ADD ESSCMD Command A-6 ADD ESSMSG Command A-14 ADD LOGMODENT Command A-15 ADD SETESS Command A-19 ADD SETLOG Command A-20 SNAXUTL ALLOCATE Command SNAXUTL BEGIN Command A-23 SNAXUTL DELETE Command SNAXUTL END Command A-23 A-23 SNAXUTL SELECTFILE Command Appendix B A-24 ESS System Messages Finding an Assigned ESS Table Messages and Codes Appendi
Contents Appendix F SNAX/XF Default BIND Default SNAX/XF BIND Bytes and Values Bytes 10-11 F-1 Bytes 14-25 F-2 F-1 Glossary Glossary–1 Index Figures Index–1 Figure 1-1. HELP Menu Screen 1-2 Figure 1-2. Notation Used to Depict Tables 1-5 Figure 1-3. ESS Table Logon and Order Records 1-8 Figure 1-4. Record for an ESS Table in the SET Table 1-9 Figure 1-5. The ESS Table and LUNS Processing (Non-Pathway) Figure 1-6. The ESS Table and LUNS Processing (Pathway) 1-10 1-11 Figure 2-1.
Contents Tables Table 1-1. SNAXUTL Command Verbs 1-12 Table 2-1. How SCF Attributes Relate to LUNS 2-28 Table F-1. Summary of Default SNAX/XF BIND Values F-1 Table F-2.
Contents (This page left intentionally blank) x 097841 Tandem Computers Incorporated
About This Manual LU Network Services (LUNS) is a component of the SNAX/XF Service Manager. LUNS allows users to: Start a TACL or Pathway application using character-coded commands. Dynamically establish a static path to a host system. Retrieve and display user-defined messages at a terminal. This manual is directed to system managers and system programmers. It provides information about how to configure a network that uses LUNS as a part of SNAX/XF, both with and without the use of passthrough.
About This Manual Your Comments Invited SNAX/CNM Manual Expand Reference Manual Introduction to Pathway Pathway PATHCOM Reference Manual Pathway SCREEN COBOL Reference Manual Pathway System Manager's Guide Introduction to Nonstop System Operations Operator Messages Manual SPI Programming Manual Subsystem Control Facility (SCF) Reference Manual Guardian Procedure Errors and Messages Manual Those who use the SNAX Creator-2 process in place of the Creator process should read the following manual: SNAX Creator
Notation Conventions General Syntax Notation UPPERCASE LETTERS The following list summarizes the notation conventions for syntax presentation in this manual. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
Notation Conventions General Syntax Notation Ellipsis ... An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char...
Notation Conventions Notation for Messages Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. 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 Conventions Change Bar Notation Change Bar Notation Change Bar | Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information.
1 Introduction to LUNS As a component of the SNAX/XF service manager, SNAX/XF LU Network Services (LUNS) provides Tandem users a way of handling system requests with the functionality normally found in System Network Architecture (SNA) environments.
Introduction to LUNS Terminal Interface to LUNS Terminal Interface to LUNS LUNS makes it possible for the terminal user to switch from one application program to another. In planning the network, the system programmer devises a series of character-coded commands that the terminal user will enter when logging on or logging off. The system programmer can also create a menu that will be displayed whenever the terminal user enters a certain command (for example, HELP).
Introduction to LUNS Defining Processes to LUNS Logging On to TSO Establishing a Static Passthrough Path Note Having logged off from ORDER ENTRY, the terminal user now wants to log on to the TSO application. In this example, TSO resides on the host, yet the method for logging on and off is the same as that used with ORDER ENTRY. The only difference is the character-coded command employed (in this case, TSO).
Introduction to LUNS LUNS Configuration Tables Starting TACL Processes With the Creator Process TACL processes are started by the Tandem Creator process. When a user wants to start a TACL process, the Creator process receives a request to establish a session from LUNS, creates the TACL process, and informs the TACL process of the terminal name. Starting Pathway Processes With the Creator Process Pathway applications also interface to LUNS by means of the Tandem Creator process.
Introduction to LUNS LUNS Configuration Tables Figure 1-2. Notation Used to Depict Tables 1 3 2 4 5 6 ORDERENTRY, PLUNAME #CREATE . . . . . 7 1 A table (in this case an ESS table) is represented by a ruled box. 2 Each of the ruled divisions within the larger box represents a record within the table. 3 ORDERENTRY is the record-name field in the record. In this case, it is a character-coded command. Notice that it is separated from the second field by a comma.
Introduction to LUNS LUNS Configuration Tables The ESS Table To use LUNS for establishing sessions, a terminal must be associated with an ESS table. Tandem’s ESS tables are similar in form and function to IBM USS tables. For a discussion of USS tables, see the IBM VTAM™ Resource Definition Reference. ESS tables hold four types of records: message records, logon records, logoff records, and order records. All such records are identified by a record-name field.
Introduction to LUNS LUNS Configuration Tables Logon Records for Pathway Programs. LUNS does not know Pathway applications by their subdevice names, because no subdevice names are specified for them through SCF ADD APPL commands. Logon records for Pathway applications therefore take a different form than those for a TACL process. Like a logon record for a TACL process, a logon record for a Pathway application has a character-coded command within its record-name field.
Introduction to LUNS LUNS Configuration Tables Sample ESS Table Records Figure 1-3 shows an ESS table containing several types of logon records and an order record. Note that logon records might contain fields that specify additional session parameters. Figure 1-3. ESS Table Logon and Order Records 1 ORDERENTRY, PLUNAME #CREATE, CONCDATA "params" . . . . . . . . . . . 2 TACL, PLUNAME #TACL, CONCDATA "params" . . . . . . . . . . . . . . . . . . . . . . 3 INV, SENDHOST Y, GATELINE $G1 . . . . . . . . .
Introduction to LUNS LUNS Configuration Tables The SET Table Just as LUNS must be aware of processes, it must know of all ESS and BIND tables. The SET table defines each of these tables to LUNS by assigning a unique table name. The table name appears in the record-name field of one of the SET table’s records. Such a record serves to relate that table name to a file where LUNS can find the relevant table data.
Introduction to LUNS LUNS Configuration Tables Figure 1-5. The ESS Table and LUNS Processing (Non-Pathway) OPEN LU 5 TACL NEWPROCESS 4 Creator Process Terminal TACL 1 LUNS CINIT 3 2 TACL, PLUNAME #TACL, CONCDATA "TACL CPU1/2" ESS Table 1 The terminal operator enters the character-coded command TACL. 2 LUNS searches the ESS table for a record named TACL and finds it. LUNS also finds the application's logical name (#TACL) and a concatenated data field specifying NEWPROCESS parameters.
Introduction to LUNS LUNS Configuration Tables Figure 1-6. The ESS Table and LUNS Processing (Pathway) OPEN LU $PATHX TCP 6 5 4 Creator Process Terminal CRED 1 LUNS CINIT 3 2 CRED, PLUNAME #CREATE, CONCDATA "PATHWAY NAME $PATHX PROGRAM CREDIT" ESS Table 1 The terminal operator enters the character-coded command CRED. 2 LUNS searches the ESS table for a record named CRED and finds it.
Introduction to LUNS SNAX/XF Utility Overview SNAX/XF Utility Overview The SNAX/XF utility program (SNAXUTL) supplied with LUNS provides the means for creating and maintaining the ESS, SET and BIND tables. With it, you can create a new table or add and delete records in an existing table. Table 1-1 is a summary of SNAXUTL command verbs. Table 1-1.
Introduction to LUNS SNAX/XF Utility Overview BEGIN SELECTFILE $SYSTEM.SNAX.
Introduction to LUNS The BIND Table The BIND Table Before an LU-LU session can be established, the PLU and the SLU must agree on “communication rules.” The PLU communicates these rules to the SLU by means of session parameters that are sent to the SLU in a BIND request. The SNAX/XF Utility (SNAXUTL) allows the user to build individual BIND images and place them into BIND tables. Use the ADD LOGMODENT to create the BIND table. Use the ADD SETLOG command to add a bind table record to the SET table.
2 Using LUNS Before LUNS can become fully operational, you must: 1. Plan the overall configuration. 2. Build the SET table, ESS tables, and BIND table with SNAXUTL. 3. Use SCF to START $SSCP. 4. Use the SCF ADD APPL command to identify the Tandem Creator process and the TACL process to LUNS. 5. Use the SCF ADD APPL command to identify SNAXUTL to LUNS if you want the ability to modify ESS tables dynamically. 6. ADD and START all lines, Physical Units (PUs), and Logical Units (LUs) in your network.
Using LUNS Planning for LUNS Planning for LUNS Preparation for LUNS usage involves the creation of both a SNAXUTL command file and an SCF configuration file. Before creating these files, you should determine: Subdevice names for such Tandem processes as the TACL process and the Creator process. The password that the Creator process must pass to LUNS when it establishes a connection. The table names of all ESS tables and the file names of their table source files.
Using LUNS Creating New Configuration Tables Creating New Within a command file, the SNAXUTL SELECTFILE command names the table source Configuration Tables file for a new SET or ESS table. Table source file names should be of the following form: $vvvvvvv.sssssss.fffffff fffffff can consist of from one through seven characters. SNAXUTL gives the corresponding table object file the same name, but appends the letter O: $vvvvvvv.sssssss.
Using LUNS Building the ESS Tables Building the ESS In planning for LUNS, you should determine how many ESS tables you need and how Tables you want to configure them. You have three options: 1. Create a single ESS table and specify it as the default table when a record for it is added to the SET table. If a default ESS table exists, all SNA terminals on a Tandem system receive the ESS message 10 and use LUNS. 2.
Using LUNS Building the ESS Tables LOGON-CHAR specifies one of the following cases: The terminal logs on with a character-coded logon command, and LUNS is to send a CINIT to the Creator process so that it can create the designated Tandem process. The terminal logs on with a character-coded logon command, and LUNS is to pass that command (or replacement data) to the host.
Using LUNS Building the ESS Tables For a TACL, specify ITI as the protocol. Note that any protocol you specify in the ESS table record will remain in effect only for that LU-LU session. Other optional operands that override SCF LU attributes include: RECSIZE recsize specifies the length, in bytes, of a line, screen, or RU, depending on the terminal protocol chosen. CHARACTERSET { EBCDIC | ASCII | KATAKANA } specifies whether or not character translation should occur.
Using LUNS Building the ESS Tables { APPLFILE | TACL } [, [, [, [, [, CPU pri-cpu [ / backup-cpu ] NAME [ process-name ] ] INSPECT { ON | OFF } ] MEM memory-pages ] PARM (optional-startup-params) ] PRI [ priority ] CPU pri-cpu [ / backup-cpu ] specifies the CPU on which the new process runs. You can optionally select a backup CPU. If the keyword CPU is not specified, the next available, active CPU (in numeric order) is used, and no backup is assigned.
Using LUNS Building the ESS Tables Logon Records for Pathway Processes To build a logon record that points to a Pathway application, you must specify CMDTYPE as LOGON-CHAR. You must also include the Tandem Creator process's subdevice name within the PLUNAME operand. This name can consist of from one to seven alphanumeric and special characters, preceded by a pound sign (#).
Using LUNS Building the ESS Tables preceded by a dollar sign ($), and in the form , $axxxx where a is an alphabetic character and xxxx is alphanumeric characters or digits. This parameter is primarily used to allow the manipulation of the Pathway data stream by the specified process before the data stream is sent to SNAX/XF. The Creator process, SNAX/XF, and the process named in the PROCESS parameter must reside in the same Tandem Expand node. The running PATHMON process can reside in a remote node.
Using LUNS Building the ESS Tables Thus, for the GATELINE operand, the format would be: \system-name.$line-name For the GATEPU operand, the format would be: \system-name.$line-name.#pu-name For the GATELU operand, the format would be: \system-name.$line-name.#lu-name In creating records for passthrough sessions, you can specify CMDTYPE as either LOGON-INIT, LOGON-CHAR, or INITSELF-RECEIVED. When the CMDTYPE is LOGON-INIT, the PLUNAME operand data is the name of a PLU on the host.
Using LUNS Building the ESS Tables Figure 2-1. LUNS’ Use of the REPDATA Field in Passthrough Host USS Table Record 4 A 3 Tandem ESS Table Record Character-Coded Command: A 1 2 CREDIT, LOGON–CHAR, SENDHOST Y, REPDATA A 1 After receiving the character-coded command CREDIT from a terminal, LUNS searches the ESS table and finds a corresponding command name field. 2 LUNS then finds A in the REPDATA field. 3 LUNS send the character-coded command "A" to the host.
Using LUNS Building the ESS Tables Figure 2-2. LUNS’ Use of a Replacement DLU in Passthrough Host INIT-SELF ESS Table Record DLUname2 1 2 DLUname1, INITSELF-RECEIVED, SENDHOST Y, PLUNAME DLUname2 1 LUNS receives an INIT-SELF from the terminal; the DLU name within it (DLUname1) matches a command name field in the ESS table. 2 LUNS finds another DLU name (DLUname2) in the record's PLUNAME field. LUNS replaces DLUname1 with this new name before sending the INIT-SELF to the host.
Using LUNS Building the ESS Tables Such a logoff record must have a character-coded command for its command-name field, and CMDTYPE must be specified as LOGOFF. No further operands need be included. Passthrough sessions established using CMDTYPE LOGON-CHAR cannot serve as an all-purpose logoff record. The host establishes all such sessions through its own USS table and terminates them in the same way.
Using LUNS Building the ESS Tables If the host is an AS/400 system, you must specify TERMSELF ON in the record used to terminate the path (instead of the STATIC operand). Specifying TERMSELF ON in the order record causes the gateway LU to send a TERMSELF request to the AS/400 host. Figure 2-4 shows the contents of two order records whose command-name fields contain the character-coded commands HOST and TANDEM. HOST is used for establishing a static path, and TANDEM is used for terminating it.
Using LUNS Building the ESS Tables Message Records You can create your own user or system message records with the SNAXUTL ADD ESSMSG command. The message text can consist of either alphabetic or single-byte Katakana characters. Records for User Messages To add a user message to the ESS table, you must first place its character-coded name in the message-name field of the ADD ESSMSG command.
Using LUNS Modifying ESS Tables Dynamically Modifying ESS Tables SNAXUTL allows you to modify a currently active ESS table dynamically: that is, you Dynamically can modify the table after LUNS has already allocated it. For this purpose, SNAXUTL provides a SELECTFILE command operand called DEACTIVATE. In the command file you submit to the utility, the SELECTFILE command specify DEACTIVATE Y (yes). Your subsequent ADD and DELETE commands modify the table. Once the table has been updated, LUNS reactivates it.
Using LUNS Specifying the SET Table Specifying the The SET table identifies all ESS tables to LUNS by defining their table names and SET Table specifying the source files in which they can be found. In any one Tandem system (node) employing LUNS, there can be only one active SET table. There are two ways of specifying to LUNS the SET table that you wish to be active: 1. Through the system generation SETTABNAME configuration modifier 2.
Using LUNS Specifying SCF Configuration Parameters Use SNAXUTL to add the necessary records for all ESS tables and BIND tables to the SET table. To add a record for an ESS table, you use the ADD SETESS command. To add a record for a BIND table, you use the ADD SETLOG command. Note that the FILENAME operand that follows the object must contain the name of the table source file where LUNS can find the table information.
Using LUNS Specifying SCF Configuration Parameters ADD APPL for a TACL Process If the Creator process is to create a TACL process, an ADD APPL command must define that TACL process. In the ADD APPL command, the TACL process is a given a subdevice name (for example, #TACL). This subdevice name must match the subdevice name specified in the ESS table logon record for TACL.
Using LUNS Specifying SCF Configuration Parameters ADD APPL Command for a Creator Process When the APPL object represents the Creator process, the following attribute is required: APPLTYPE { LUNSCRE | 6 } specifies the type of application program being defined. For an APPL object representing a Creator process, the valid values for APPLTYPE are LUNSCRE or the integer value 6.
Using LUNS Specifying SCF Configuration Parameters ADD APPL Command for SNAXUTL To modify ESS tables dynamically, SNAXUTL must establish a connection with LUNS. The SCF configuration file must therefore include an APPL object definition for SNAXUTL. In the ADD APPL command, SNAXUTL must always be given the subdevice name #SNAXUTL. For further information on dynamic modification of ESS tables, see “Modifying ESS Tables Dynamically” earlier in this section.
Using LUNS The ADD LINE, PU, and LU Command Attributes The ADD LINE, PU, When using SCF to configure lines, PUs, and LUs, you can specify several attributes in and LU Command an ADD command that directly affect LUNS processing. Attributes AUTOLOGON Attribute The syntax for the AUTOLOGON attribute is as follows: AUTOLOGON "ess-table-entry-name" "ess-table-entry-name" is the name of a record in the ESS table that SNAX/XF processes when an LU is started.
Using LUNS The ADD LINE, PU, and LU Command Attributes Removing the AUTOLOGON Value The AUTOLOGON value can be removed from the line, PU, and LU with an ALTER command by specifying a null string (””) as the value for AUTOLOGON. Caution ESSTABLE Attribute Do not use use the AUTOLOGON attribute to specify a logoff record. If AUTOLOGON specifies either a LOGOFF ESS record or an ORDER ESS record with STATIC OFF specified, SNAX/XF issues the ESS system error S0006 and the request fails.
Using LUNS The ADD LINE, PU, and LU Command Attributes Changing an LUs ESSTABLE Value The ESSTABLE value for existing LUs can be changed with the ALTER LU command. Removing the ESSTABLE Value The ESSTABLE value can be removed from the line, PU, and LU with an ALTER command by specifying a null string (“”) as the value for ESSTABLE.
Using LUNS ESS LU Attributes That Override SCF LU Attributes Note that if the NOACQ attribute is not specified for switched floating LUs, the default value for the switched floating LUs is OFF. Changing an LUs NOACQ Value The NOACQ value for existing LUs can be changed with the ALTER LU command. Removing the NOACQ Value The NOACQ value can be removed from the line, PU, and LU with an ALTER command by specifying a null string (“”) as the value for NOACQ. Caution Pathway acquires terminal LUs.
Using LUNS ESS LU Attributes That Override SCF LU Attributes If the BINDTABLE attribute is specified in an ADD or ALTER LINE command (primary line only) or an ADD or ALTER PU command to which this LU is permanently subordinated, the LU uses the BINDTABLE value of the superior object as a default unless it is overridden by a BINDTABLE value specified in an ADD or ALTER LU command for the LU. The BINDTABLE name can contain from one through eight alphanumeric or special characters ($, #, or @).
Using LUNS ESS LU Attributes That Override SCF LU Attributes PROTOCOL Attribute The syntax for the PROTOCOL attribute is as follows: PROTOCOL { CRT | ITI } This attribute specifies the application interface protocol that SNAX/XF uses when communicating with the corresponding LU. If the LU is a terminal attached to a 6600 controller, the protocol selected must be either CRT or ITI. This attribute is required for the LU object type.
Using LUNS SCF Attribute Summary SCF Attribute Table 2-1 shows those SCF attributes relevant to LUNS and maps them to the Summary appropriate object types. Table 2-1.
Using LUNS Using the Tandem Creator Process Using the Tandem For any non-Pathway application that uses LUNS, perform the following SCF Creator Process configuration steps: 1. Define the Creator process through an ADD APPL command, specifying APPLTYPE LUNSCRE. 2. Define the application through an ADD APPL command that also specifies the following APPL attributes: a. The CREATOR attribute, which must contain the name of the Tandem Creator process b.
Using LUNS Using the Tandem Creator Process Creator Process RUN Command Syntax The run command syntax is given below. If the Creator process is to run as a NonStop process-pair, you must give it a symbolic name through the NAME run option. Note also that you can specify any other run options (for example, NOWAIT, PRI, CPU, and so on). For a list of these options, see the Guardian Operating System Utilities Manual.
Using LUNS Using the Tandem Creator Process CREATOR #subdevice-name specifies the subdevice name of the Tandem Creator process.
Using LUNS Using the Tandem Creator Process (This page left intentionally blank) 2–32 097841 Tandem Computers Incorporated
3 Application Example Section 2 presented concepts for planning a LUNS configuration; these concepts are applied to an example application presented in this section. The example has two parts. The first part illustrates the implementation of a configuration that allows terminal users on a Tandem system to log on to applications both on their own system and on the host and to establish a static passthrough session with the host.
Application Example Creating the Basic Configuration Operational Assumptions The following are operational assumptions: Only two terminals on \SYS1 will use LUNS. While other SNA terminals might be connected to \SYS1, they will remain unaffected by LUNS operation. Both terminals will receive Tandem’s ESS message 10 (banner message) when they are started with SCF. When HELP is entered on a terminal, that terminal will receive a menu that has been created with the SNAXUTL ADD ESSMSG command.
Application Example Creating the Basic Configuration Configuration Assumptions The following are configuration assumptions: The starter SET table provided by Tandem has been made active through SYSGEN. SNAX/XF has thus already initialized the LUNS component of $SSCP. (Most users will prefer to build their own SET table and specify the SET table name through the SETTAB parameter of the SCF ADD/ALTER SUBSYS $SSCP command.
Application Example Creating the Basic Configuration BEGIN SELECTFILE $SYSTEM.SNAX.ESSTAB1, TYPE ESS ALLOCATE 10 ADD ESSCMD TACL, CMDTYPE LOGON-CHAR, PLUNAME #TACL, CONCDATA "TACL, CPU 0" & & & ADD ESSCMD ORDERENTRY, CMDTYPE LOGON-CHAR, PROTOCOL CRT, PLUNAME #CREATE, CONCDATA ("PATHWAY NAME $PATHX,", "PROGRAM ORDER-ENTRY") & & & & & ADD ESSCMD TSO, CMDTYPE LOGON-INIT, SENDHOST Y, PLUNAME TSO, GATELINE \SYS1.
Application Example Creating the Basic Configuration The HELP menu includes “new line” control characters so that the display will be properly formatted. (For a discussion of New Line control characters, see the IBM 3270 Information Display System 3274 Control Unit Description and Programmer’s Guide.) Note that New Line is the only control character accepted on the SSCP-LU session.
Application Example Creating the Basic Configuration Configuring the System Through SCF In the previous subsection, SNAXUTL modified the SET table source file and SET table object file to include a record for ESS1. In configuring the system, the SETTAB attribute of the SCF ALTER SUBSYS $SSCP command must be specified so that LUNS will use the modified version of the SET table and be aware of ESS1: ALTER SUBSYS $SSCP,SETTAB $SYSTEM.SYS01.
Application Example Creating the Basic Configuration Note also that the ESS table is being specified as an attribute of each LU. This table, here identified by its table name, will be searched when LU3 or LU4 attempts to log on: ADD LINE $P2, ADD PU $P2.#PU2, ADD LU $P2.#LU3, ADD LU $P2.
Application Example Adding an Application and Terminal to a Second System Adding an Application In this, the second part of the example, a Pathway application process and a terminal and Terminal to a LU, both residing on a second Tandem system, are added to the configuration. As Second System Figure 3-2 illustrates, this system, called \SYS2, communicates with \SYS1 through an Expand link. The PATHMON process on \SYS2 is named $PATHY. Note that LUNS will be running on both systems.
Application Example Adding an Application and Terminal to a Second System Figure 3-2.
Application Example Adding an Application and Terminal to a Second System Operational Assumptions The following assumptions are made about operation: LU3 and LU4 on \SYS1 can access the Inventory program on \SYS2. However, LU5 on \SYS2 is a factory floor terminal used only for inventory purposes and can access only the Inventory program on \SYS2. LU3 and LU4 can initiate sessions with the Inventory program on \SYS2 through the character-coded command INVENTORY.
Application Example Adding an Application and Terminal to a Second System Creating a Command File for SNAXUTL First, an ESS table is created for \SYS2. The command file contains only one logon record, because the single terminal being configured on this system will have access only to the Inventory process. Note that SCF has been used to specify that the terminal be automatically logged on to this one process; hence, a HELP menu is not necessary.
Application Example Adding an Application and Terminal to a Second System Using SCF to Add the New Application and LU to \SYS2 Because this example assumes that no SET table has been made active on \SYS2, the SETTAB attribute of the ALTER SUBSYS $SSCP command is used to make active the SET table built in the previous subsection ($SYSTEM.SNAX.SNXSET2). The ADD APPL command is then used to define the Tandem Creator process and SNAXUTL to LUNS.
Application Example Adding an Application and Terminal to a Second System Starting the Tandem Creator Process on \SYS2 The Tandem Creator process must be started on \SYS2 just as it was on \SYS1. Because a password is required for the Creator process, it must be included in the RUN command: 1> RUN CREATOR /OUT $S.#SPOOL, CPU 1, NAME $CRT, NOWAIT/ 2 ; CREATOR #CREATE, PASSWORD "TARDIS " & Note that this same password was specified in the SCF ADD APPL command for the Creator process.
Application Example Performance Consideration - ESS Table Allocation BEGIN SELECTFILE $SYSTEM.SNAX.ESSTAB1, TYPE ESS, DEACTIVATE Y ADD ESSCMD INVENTORY, CMDTYPE LOGON-CHAR, PROTOCOL CRT, PLUNAME #CREATE, CONCDATA ("PATHWAY", "NAME \SYS2.$PATHY ,", "PROGRAM INVENTORY") DELETE HELP ADD ESSMSG %H85," %H85," %H85," %H85," %H85," %H85," %H85," %H85," %H85," %H85," %H85," %H85," HELP, MSGTEXT (" PU:@@NDNAME.@@LNNAME.@@PUNAME LU:@@NDNAME.@@LNNAME.
Application Example Performance Consideration - ESS Table Allocation Configuration Suggestion It is desirable to keep the number of ESS tables used to a minimum. An installation requiring what might seem to be many ESS tables that, for example, differ only in the LU’s GATELU specification can be configured so that the number of ESS tables required drops dramatically.
Application Example Performance Consideration - ESS Table Allocation Reconfiguration Example The ESS tables configured in the previous example can be replaced by a single generic table by reconfiguring as follows: Secondary objects: LINE PU LU LU $ABC123 #PU001 #T01234, PASSTHRU ON, ASSOCIATE $DEF456.#T01234 #T05678, PASSTHRU ON, ASSOCIATE $DEF456.
Appendix A The SNAX/XF Utility Introduction The SNAX/XF Utility (SNAXUTL) allows you to create and update the configuration tables that LUNS uses when establishing or terminating sessions. These configuration tables include: The Enhanced System Services (ESS) tables The Session Establishment (SET) table The BIND table To create or update one of these tables, you enter one or more command blocks into an edit command file. Interactive use is not supported. Input is free-format.
The SNAX/XF Utility SNAXUTL Command Syntax General Syntax Figure A-1 shows the syntax for all SNAXUTL commands. Figure A-1. SNAXUTL Command Syntax verb [modifier [object [operand [,operand ...]]]] where verb is a SNAXUTL command verb. modifier is any command-verb modifier. object is the object of the command verb (and any modifier). operand is any operand that pertains to the given command. operand format is: opname {opdata | (opdata [,opdata ... ] )} where: opname is the operand name.
The SNAX/XF Utility SNAXUTL Command Syntax Commands Commands begin with a command verb and might also require a command modifier and a command object. For example: ADD ESSCMD ORDERENTRY command object command modifier command verb Commands can be followed by one or more operands, separated by commas. Commands are separated from other commands either by a new line or by semicolons. Thus, if multiple commands are to be placed on the same line, they must be separated by a semicolon.
The SNAX/XF Utility SNAXUTL Command Syntax All such byte values must be coded in ASCII-hexadecimal format rather than in EBCDIC-hexadecimal format (Tandem’s SSCP translates these table values from ASCII to EBCDIC automatically). For example, the New Line control character for 3270 devices is %H15 in EBCDIC. In the ESS table, this must be coded as %H85, which is the ASCII translation of %H15.
The SNAX/XF Utility SNAXUTL Command Syntax Comments Comments can appear at any point within a command, except within alphanumeric strings enclosed by quotation marks. You place an exclamation point (!) before the comment. The comment must be terminated either by the end of the current line or by another exclamation point.
The SNAX/XF Utility SNAXUTL ADD Commands SNAXUTL ADD The following is a description of all of the SNAXUTL ADD commands. Commands ADD ESSCMD Command The ADD ESSCMD command is used to add either logon (character-coded), logoff (DLU), or order commands to the ESS table. These parameters are ordered by the frequency in which they are most commonly used.
The SNAX/XF Utility SNAXUTL ADD Commands GATELINE gateway-line specifies the gateway line to be used when communicating with the SNA host. This parameter is required if the SENDHOST parameter is specified and the SNA host is a remote system; if the line is connected to a local system, this parameter is optional. The format for gateway-line is: [\system-name.]$device-name where: system-name is the name of the system on which the gateway line resides.
The SNAX/XF Utility SNAXUTL ADD Commands pu-name is the device name corresponding to the physical unit. This value can be from one to seven alphanumeric characters long, where the first character is alphabetic. Note that GATEPU should not be specified when either GATELINE or GATELU is specified. GATELU gateway-lu is the gateway logical-unit name that is to be used when this command is sent to the SNA host. The format of gateway-lu is: [\system-name.]$device-name.
The SNAX/XF Utility SNAXUTL ADD Commands MULTIPLELOGON USE_CURRENT_PATH specifies that a terminal LU residing on a Tandem system can use this ESS table record to log on to a host program by means of an existing path established through an earlier character-coded command. This operand is supported only when the command type is LOGON-CHAR and SENDHOST is specified as Y.
The SNAX/XF Utility SNAXUTL ADD Commands A pound sign (#) preceding dlu-name is invalid when dlu-name is specified in conjunction with SENDHOST Y. The PLUNAME operand is invalid with: CMDTYPE ORDER CMDTYPE LOGOFF CMDTYPE LOGON-CHAR when SENDHOST Y is also specified. SNATYPE sna-type specifies the type of SNA SLU support that is to be emulated by the terminal entering this command. Valid values for sna-type are 0, 1, 2, 3, 4, and 6.
The SNAX/XF Utility SNAXUTL ADD Commands Specifying KATAKANA turns translation on so that: When necessary, data sent from the terminal to a Tandem application is translated from EBCDIC Katakana to JIS 6220 Katakana. When necessary, data sent from a Tandem application to the terminal is translated from JIS 6220 Katakana to EBCDIC Katakana. ASCII turns translation off. The default value is ASCII. This operand is optional. BINDENTRY bind-entry-name specifies the name of a record in the BIND table.
The SNAX/XF Utility SNAXUTL ADD Commands REPDATA replacement-data specifies the data used to replace the current request (RU) data. The value expressed for replacement-data may be any string from 1 to 256 bytes long. Bytes can be specified as either characters or hexadecimal numbers. When byte values are specified as hexadecimal numbers, they must be expressed in byte units, with each unit separated from the others by a comma (for example: %HC1, %HC2, %HC3).
The SNAX/XF Utility SNAXUTL ADD Commands The CONCDATA operand is used to pass Pathway or NEWPROCESS parameters to the Tandem Creator process. For a full discussion, see the subsections under “Building the ESS Tables” in Section 2, “Using LUNS.” USERDATA user-data specifies user data that is to be placed into the CINIT command. The value for user-data can be expressed as any string from 1 to 256 bytes long. Bytes may be specified as either characters or hexadecimal numbers.
The SNAX/XF Utility SNAXUTL ADD Commands ADD ESSMSG Command The ADD ESSMSG command adds messages to the ESS table. These can be either system or user messages. ADD ESSMSG message-name , MSGTEXT message-text message-name is the name of the record containing the message. The value specified for message-name can contain from 1 to 32 alphanumeric and special characters. The first character of a system message name must be the letter S, followed by four digits. This operand is not case-sensitive.
The SNAX/XF Utility SNAXUTL ADD Commands ADD LOGMODENT Command This command is used to define a record in a Tandem BIND table. Each record represents a BIND image.
The SNAX/XF Utility SNAXUTL ADD Commands TSPROF ts-profile-value specifies the transmission services profile (byte 3 of the BIND image). Any hexadecimal number in the range of %H00 to %HFF can be specified for tsprofile-value. The default value is %H03. PRIPROT priprot-value specifies the primary LU protocol (byte 4 of the BIND image). Any hexadecimal number in the range of %H00 to %HFF can be specified for priprot-value. The default value is %HB1.
The SNAX/XF Utility SNAXUTL ADD Commands PSNDPAC psndpac-value specifies the secondary send pacing count (byte 12 of the BIND image). Any hexadecimal number in the range of %H00 to %H3F can be specified for psndpac-value. Primary receive pacing count (byte 13 of the BIND image) is also set to the value set for PSNDPAC. The default value is %H00. Note that SNAX/XF does not support pacing.
The SNAX/XF Utility SNAXUTL ADD Commands USERDATA user-data If a value for plu-name is not present, the length specified for user-data will be found at byte 28, and the user-data value(s) will begin at byte 29. If a value for plu-name has been specified, then the length for user-data will be found at the next byte past plu-name, and the user-data value(s) will follow. If a value for plu-name has been specified, and USERDATA user-data is not specified, then the USERDATA length byte will be %H00.
The SNAX/XF Utility SNAXUTL ADD Commands For example, run SNAXUTL using the following command: RUN SNAXUTL /IN $vol.subvol.file/ A source file named LOGTAB1 and an object file named LOGTAB1O will be allocated. Based on the above example, SNAXUTL builds the BIND image and places it in both files as a record named bind1. SNAX/XF retrieves the BIND image after reading the object file (LOGTAB1O) into extended memory.
The SNAX/XF Utility SNAXUTL ALLOCATE Command ADD SETLOG Command This command is used to add to the SET table a record representing a BIND table. ADD SETLOG bind-table-name , FILENAME filename bind-table-name is the table name of the BIND table. The value specified for bind-table-name can contain from one to eight alphanumeric and special characters. FILENAME filename is the name of the table source file in which the BIND table can be found.
The SNAX/XF Utility SNAXUTL ALLOCATE Command Calculating SET Table Extent Sizes The formula for calculating extent sizes for SET tables is as follows: a = $ROUNDUP{ (76 + 64x)/2048 bytes} where a is the SET table extent size in bytes $ROUNDUP is a function that rounds its argument up to the next highest integer; for example, $ROUNDUP(3.2) = 4 x is the number of SET table records that contain ESS or BIND table names.
The SNAX/XF Utility SNAXUTL ALLOCATE Command The formula for the second subcalculation is as follows: a2 = (54 + b1)x + (108 + b2)y where a2 is the number of bytes required for ESS messages b1 is the estimated average length of all ESS messages fewer than 1980 bytes long b2 is the estimated average length of all ESS messages between 1981 bytes and 3720 bytes in length x is the number of ESS messages fewer than 1980 bytes long y is the number of ESS messages between 1981 bytes and 3720 bytes in length The f
The SNAX/XF Utility SNAXUTL END Command SNAXUTL BEGIN The BEGIN command delimits the beginning of a command block. Command BEGIN SNAXUTL DELETE The DELETE command deletes individual records from the table selected through the Command SELECTFILE command. DELETE name name is the record name, message name, bind-entry-name, or ESS table name of the individual record to be deleted. SNAXUTL END The END command delimits the end of a command block.
The SNAX/XF Utility SNAXUTL SELECTFILE Command SNAXUTL The SELECTFILE command defines the source file on which subsequent recordSELECTFILE manipulation commands will be performed. Thus all ALLOCATE, ADD, and Command DELETE commands within the same command block reference the file specified in the SELECTFILE command. SELECTFILE filename , TYPE filetype [ , DEACTIVATE { Y | N } ] filename specifies the name of the table source file to be created or changed by subsequent commands within the command block.
Appendix B ESS System Messages When an error occurs during session establishment or termination or when the user needs to be informed of an event relevant to session establishment or termination, system messages from the ESS table are displayed at the user’s terminal. These messages can be modified or deleted by the user through the SNAX/XF Utility, SNAXUTL. System messages can also be displayed by the user by entering the message name.
ESS System Messages Messages and Codes Messages and Codes Within the boxes that follow, messages are shown much as they appear on the terminal user’s screen. (In some cases, spacing has been reduced so that the message will fit within the manual’s margins.) Note that currently unassigned numbers are reserved for future Tandem messages.
ESS System Messages Messages and Codes " ESS TABLE RECORD NOT FOUND FOR THIS COMMAND --> S0002 " Cause An ESS table record whose record name matches the failing command was not found in the terminal’s ESS table. Effect The failing command is ignored and the terminal’s keyboard is reset to allow the entry of another command. Recovery Verify that the command is being entered correctly and correct it if not.
ESS System Messages Messages and Codes " SESSION NOT BOUND --> S0007 " Cause LUNS was unable to process the failing command because of a resource problem. Effect The failing command is ignored and the terminal’s keyboard is reset to allow the entry of another command. Additional information can be found in EMS event message 81 (LUNS error code 2305, 2307, 2309, 2311, 2320, 2325, or 2326).
ESS System Messages Messages and Codes ( User-defined, or Tandem supplied, LOGO or MENU ) ( System Message 10 ) Cause This message is the logo or banner that is displayed when Tandem’s $SSCP (SNAX/XF Service Manager process) is in an SSCP-LU session with the LU. Typically, this message is displayed when a terminal is activated and when a session ends. Effect The terminal’s keyboard is reset to allow the entry of a command. Recovery No recovery action is necessary.
ESS System Messages Messages and Codes " CANNOT PERFORM OPERATION -- LOGON PENDING --> S0016 " Cause A logon to a Tandem application is being processed by LUNS as the result of a previous command from this terminal. The failing command requested an operation, such as logon or logoff, that is not valid during logon processing. The only commands valid at this time are ones that cause a user message to be displayed (such as HELP, DIRECTORY, and so on).
ESS System Messages Messages and Codes " INVALID ENTRY FOUND IN ESS TABLE--> S0019 " Cause While searching the terminal’s ESS table for a record whose record name matches the failing command, an invalid record was found in the ESS table. This indicates that the table’s object file has been corrupted. Effect The failing command is ignored and the terminal’s keyboard is reset to allow the entry of another command.
ESS System Messages Messages and Codes " UNABLE TO ALLOCATE GATEWAY LU --> S0020 " Cause The failing command matches the command name of an ESSCMD record in the terminal’s ESS table, and that record contains SENDHOST Y. In attempting to establish a passthrough session with a host application, LUNS was unable to find an available gateway LU as was specified in the ESSCMD record. When the gateway line resides in a different node from the terminal, system message S0045 is returned to the terminal.
ESS System Messages Messages and Codes " CANNOT TURN STATIC ON WHILE IN SESSION--> S0022 " Cause During an LU-LU session with an application in either the Tandem system or the host system, the SYSTEM REQUEST key was pressed and an Order command with a STATIC ON attribute was entered. This caused LUNS to attempt to establish a static path to the host, which cannot be done while in an LU-LU session.
ESS System Messages Messages and Codes " LOGON REJECTED -- LOGOFF THEN LOGON --> S0024 " Cause During an LU-LU session, the SYSTEM REQUEST key was pressed, and then the failing command was entered. The failing command caused LUNS to attempt to log on to a new application, which cannot be done while in session. Effect The failing command is ignored, the terminal remains in the SSCP-LU session with LUNS, and the terminal’s keyboard is reset to allow the entry of another command.
ESS System Messages Messages and Codes " ESS ENTRY NOT FOUND END-OF-TABLE MARKER MISSING--> S0026 " Cause When the terminal’s ESS table was searched for a record whose record name matches the failing command, the record was not found, nor was the end of table marker found. This indicates that the table’s object file has been corrupted.
ESS System Messages Messages and Codes " CREATOR NOT DEFINED --> S0029 " Cause A Tandem Creator process has been defined for this TACL or Pathway application through the CREATOR attribute in an SCF ADD/ALTER APPL command. An attempt has been made to communicate with the Creator process to have it start the TACL or Pathway application; however, the Creator process has not been defined by an SCF ADD APPL command.
ESS System Messages Messages and Codes " CREATOR PROCESS DISCONNECTED--> S0040 " Cause The Creator process has issued a CLOSE or a DISCONNECT, or it has stopped or abended, causing LUNS to simulate a Creator DISCONNECT. Effect The failing command is ignored and the terminal’s keyboard is reset to allow the entry of another command. Recovery Determine whether the operator has issued an ABORT APPL $SSCP.#CREATE command.
ESS System Messages Messages and Codes " SESSION NOT BOUND -GUARDIAN 90 USESEGMENT ERROR--> S0046 " Cause During processing of the failing command, an error was returned when LUNS issued a USESEGMENT call to place a previously allocated extended-memory segment into use. Effect The failing command is ignored and the terminal’s keyboard is reset to allow the entry of another command. Additional information can be found in EMS event message 81 (LUNS error code 2311).
ESS System Messages Messages and Codes " CANNOT PERFORM OPERATION -- LOGOFF PENDING--> S0050 " Cause A logoff from a Tandem application is being processed by LUNS as the result of a previous command from this terminal. The failing command requested an operation, such as logon or logoff, that is not valid during logoff processing. The only commands valid at this time are ones that cause a user message to be displayed (for example, HELP, DIRECTORY, and so on).
ESS System Messages Messages and Codes " CANNOT ISSUE TERMSELF WHEN NOT IN SESSION WITH A HOST-->S0054" Cause The terminal operator used a character coded command to log off. The ESS table logoff record represented by this character coded command was intended for use in a static session with an AS/400 host, which requires a TERMSELF request. However, the SLU was not in session with an AS/400 host. Effect No TERMSELF request is sent, and no logoff occurs.
Appendix C Creator Process Error Messages Creator Process The following Creator process messages are displayed during Pathway and TACL LOGON and LOGOFF logon and logoff sequences. This appendix includes messages common to both Messages C-series and D-series system software; it also includes new messages used with D-series system software. Some error messages may not be easily recoverable and require you to seek additional assistance.
Creator Process Error Messages Creator Process LOGON and LOGOFF Messages Creator Process APPLFILE Logon Message APPLFILE $name created at Tandem-name Cause The APPLFILE application has successfully started. Effect The $name value is the APPLFILE process name. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery This is an informational message only; no action is required.
Creator Process Error Messages Numbered Creator Process Messages Creator Process APPLFILE Logoff Message APPLFILE $name stopped at Tandem-name Cause The APPLFILE application has successfully stopped. Effect The $name is the APPLFILE process name. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery This is an informational message only; no action is required.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 006MIS CP006MIS - ++++ Creator terminating ++++ Cause This is probably due to incorrect startup parameters. Effect The Creator process is in a state from which it cannot recover. Note that this message is accompanied by another message containing informative user data. Recovery Examine the accompanying message and correct any parameters that are in error. Restart the Creator process.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 009NEW CP009NEW - Unable to start APPLFILE PROCESS_CREATE Error PROCESS_CREATE Detail Program File Name Data Tandem Name = = = = = error-field error-field program-filename user-data Tandem-name Cause The operating system could not create the new process requested by the Creator process.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 010INI CP010INI - Creator is not nonstop because it is not named Cause A process name was not specified in the NAME parameter of the RUN command for the Creator process. Effect The Creator process is not running as a NonStop process pair. Recovery If you do not want the Creator process to run as a NonStop process, disregard this message.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 013 This error message is no longer used. Creator Process Error 014NEW CP014NEW - Unable to communicate with APPLFILE File error = error Program File Name = program-filename Proc ID = process-name Data = user-data Tandem Name = Tandem-name Cause The Creator process cannot send a startup message to the APPLFILE process it has created. Effect The error value is the file-system error code.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 015PAT CP015PAT - NAME keyword missing Data = user-data Tandem Name = Tandem-name Cause The required NAME value (the PATHMON name) was not specified for this Pathway application. Effect A display of the current CONCDATA field parameters from the logon record of the ESS table is returned as user-data. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery Use SNAXUTL to correct the logon record.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 017 This error message is no longer used. Creator Process Error 018PAT CP018PAT - OPEN error - unable to OPEN PATHMON File Error = error PATHMON Name = $PATHMON-name Data = user-data Tandem Name = Tandem-name Cause The Creator process is unable to open the PATHMON named $PATHMON-name. Effect The error value is the file-system error code.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 021PAT CP021PAT - File error - sending request to PATHMON File Error = error PATHMON Name = $PATHMON-name Tandem Name = Tandem-name Cause An interprocess communication to the PATHMON named $PATHMON-name has failed. Effect The error value is the file-system error code. The Tandem-name value is returned in the form $line-name.#lu-name.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 023PAT CP023PAT - PATHWAY RUN PROGRAM error PATHMON Name = $PATHMON-name Program Name = program-name PATHWAY Error = error PATHWAY Info = info Tandem Name = Tandem-name Cause The program name was not added to the Pathway configuration file. Effect The $PATHMON-name value is the name of the PATHMON. The program-name value is the Pathway object name.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 025INI CP025INI - File Error - connecting to SNAX File Error = error Cause Usually, this message means that the Creator process password was incorrectly specified in the PASSWORD parameter of the Creator RUN command. Effect The error value returned is the file-system error code. Recovery If the error value is 48 (security violation), make sure that the password in the Creator process RUN command is correctly specified.
Creator Process Error Messages Numbered Creator Process Messages Recovery Refer to the Guardian Procedure Errors and Messages Manual for an explanation of the file-system error code. Make sure that the subdevice name used in the RUN command is present and that this subdevice name is the same as the one used in the SCF ADD APPL command. Also make sure that another Creator process has not opened $SSCP under the same name. Creator Process Error 028 This error message is no longer used.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 034MIS CP034MIS - The Creator has encountered an internal error. Save the ABEND file and the SNAX trace (if there is one). Contact your Tandem representative Cause An internal error has occurred. Effect The Creator process stops running.
Creator Process Error Messages Numbered Creator Process Messages process as a NonStop process pair, stop the Creator process and issue a new RUN command specifying another CPU. Creator Process Error 036INI CP036INI - Log file inaccessible File Error = error File Name = filename Cause Either a disk log file does not exist or the spooler is full. Effect The error value is the file-system error code.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 038INI CP038INI - Parameter too long Error Data = error-data Tandem Name = Tandem-name Cause A parameter value specified in either the Creator RUN command or the logon record in the ESS table contains too many characters. Effect If a parameter value specified in the Creator RUN command contains too many characters, this message returns only the error-data value.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 044 This error message is no longer used. Creator Process Error 045 This error message is no longer used. Creator Process Error 046 This error message is no longer used. Creator Process Error 047SSCP CP047SSCP - Unable to connect to SNAX, restart the Creator. If the problem persists save the ABEND file and the SNAX trace (if there is one). Contact your Tandem Representative.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 048SSCP CP048SSCP - Unable to disconnect from SSCP, too many negative replies Cause The Creator process has repeatedly received negative responses to its DISCONNECT requests. Effect The Creator process stops running. Recovery Restart the Creator process by reissuing the RUN command. Creator Process Error 049 This error message is no longer used. Creator Process Error 050 This error message is no longer used.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 052NEW This error message is no longer used. Creator Process Error 053MIS CP053MIS - File system error File Error File Name = error = filename Cause A file system error has occurred. It is possible that both the primary and backup processors have failed, making it impossible for the Creator process to communicate with $SSCP. Effect In this case, the Creator process stops execution.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 055INI CP055INI - Invalid CREATOR RUN keyword Error Data = error-data Cause An invalid Creator keyword parameter has been entered in the Creator process RUN command. The only acceptable keyword parameters allowed in the Creator process RUN command are CREATOR and PASSWORD. Effect The error-data value contains the parameter in error. Recovery Reissue the Creator process RUN command, using the correct keyword parameter.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 058INI CP058INI - Duplicate keyword on startup Cause A keyword parameter was used more than once in the Creator process RUN command. Effect The Creator process is not started. Recovery Omit the duplicate keyword parameter and reissue the Creator process RUN command.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 060NEW CP060NEW - No keyword after comma in user data Data = user-data Tandem Name = Tandem-name Cause A comma was found as the last item in the logon record. The comma must be followed by another parameter or excluded. Effect A display of the current CONCDATA field parameters from the logon record of the ESS table is returned as user-data. The Tandem-name value is returned in the form $line-name.#lu-name.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 062NEW CP062NEW - PROCESS is not a valid keyword for APPLFILE or TACL Data = user-data Tandem Name = Tandem-name Cause The user included the parameter PROCESS in the data field of an APPLFILE or TACL logon record. Effect The user-data value is the user-supplied parameters from the DATA field in the logon record. The Tandem-name value is returned in the form $linename.#lu-name.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 064NEW CP064NEW - PROCESS not running Data = user-data Tandem Name = Tandem-name Cause The process name specified with the PROCESS parameter in DATA field of the logon record is not running. Effect The user-data value is the user-supplied parameters from the DATA field in the LOGON record. The Tandem-name value is returned in the form $linename.#lu-name.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 066MIS CP066MIS - CHECKPOINT error, backup is stopped File error = error Cause The backup CPU is stopped. Effect The error value returned is the file-system error code. Recovery Refer to the Guardian Procedure Errors and Messages Manual for an explanation of the file-system error code. If the backup CPU was not intentionally stopped, then some system condition (such as CPU down) has occurred.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 068SSCP CP068SSCP - Invalid data received from SNAX. Save the ABEND file, the log file and the SNAX trace (if there is one). Contact your Tandem representative. Request^info = info Cause: Invalid data was received from the SNAX/XF process. Effect The info value is the invalid data received by the Creator process. Recovery Save the ABEND file, the log file, the trace (if there is one), and the info value information.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 070SSCP CP070SSCP - Duplicate LOGON received from SNAX Tandem Name = Tandem-name Cause A LOGON command received from a user was misread by the Creator process as currently in session. Effect The Tandem-name value is returned in the form $line-name.#lu-name.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 072INI CP072INI - GUARDIAN version must be at least D00 Cause An attempt was made to run the SNAX/XF Creator process on a version earlier than the D00 release of the operating system. Effect The Creator process is not started. Recovery Obtain a C-series version of the SNAX/XF Creator process.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 074INI CP074INI - No keyword after comma in startup command Cause: A comma was included as the last item in the user-supplied startup parameters of the Creator process RUN command. The comma must either be followed by another parameter or excluded. Effect The Creator process is not started. Recovery Either insert a parameter after the ending comma or remove the comma. Reissue the Creator process RUN command.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 076INI CP076INI - MAXPATHMONOPENS value not between 0 and 99 Cause A MAXPATHMONOPENS value was specified that was not a number between 0 and 99. Effect The user was not allowed to log on to a Pathway application. Recovery Restart the Creator process using a value that is between 0 and 99.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 080INI CP080INI - MAXSESSIONS value not between 1 and 2000. Cause The parameter for MAXSESSIONS was not between 1 and 2000 when using D-series system software. Effect The Creator process logs the message and then stops executing. Recovery At startup, specify a value for the keyword MAXSESSIONS that is between 1 and 2000 when using D-series system software.
Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 082INI CP082INI - CHECKALLOCATESEGMENT error, backup is stopped File Error Code = error field Segment ID = segment-id Cause The disk from which the Creator process was taken is out of space. Effect The value for error field is the error code returned from the call to CHECKALLOCATESEGMENT. The value for segment-id is the segment ID value.
Creator Process Error Messages Numbered Creator Process Messages Recovery Refer to the Guardian Procedure Errors and Messages Manual for an explanation about file-system error codes. Determine the reason that the process quit, fix the problem, and log on again.
Creator Process Error Messages Numbered Creator Process Messages (This page left intentionally blank) C–34 097841 Tandem Computers Incorporated
Appendix D LUNS High-Level Flow Diagrams This appendix contains flow diagrams showing logon and logoff sequences for: A host application for which the ESS table specifies CMDTYPE LOGON-CHAR, but not REPDATA A host application for which the ESS table specifies CMDTYPE LOGON-CHAR and REPDATA A host application for which the ESS table specifies CMDTYPE LOGON-INIT A host application for which the ESS table specifies CMDTYPE INITSELFRECEIVED A static passthrough application In the illustrations, the logon and l
LUNS High-Level Flow Diagrams Logon and Logoff for a Host Application (LOGON-CHAR) Logon and Logoff for a Figure D-1 shows a terminal logging on to and logging off from a host application. Host Application The logon record in the ESS table specifies CMDTYPE LOGON-CHAR but does not (LOGON-CHAR) use the REPDATA field. Figure D-1.
LUNS High-Level Flow Diagrams Logon and Logoff for a Host Application (LOGON-CHAR) Figure D-2 shows a terminal logging on to and logging off from a host application. In the ESS table, the logon record, whose character-coded command name is TSOJON, specifies CMDTYPE LOGON-CHAR. The record also has a REPDATA field of “Logon applid(tso) data(jones/jones)”. Figure D-2.
LUNS High-Level Flow Diagrams Logon and Logoff for a Host Application (LOGON-INIT) Logon and Logoff for a Figure D-3 shows a terminal logging on to and logging off from a host application. In Host Application the ESS table, the logon record, whose character-coded command name is INITJON, (LOGON-INIT) specifies CMDTYPE LOGON-INIT. The record also has a PLUNAME field of “TSO” and a USERDATA field of “jones/jones”. Figure D-3.
LUNS High-Level Flow Diagrams Logon and Logoff for a Host Application (INITSELF-RECEIVED) Logon and Logoff for a Figure D-4 shows a terminal logging on to and logging off from a host application. In Host Application the ESS table, the logon record, whose DLU command name is IBM1, specifies (INITSELF-RECEIVED) CMDTYPE INITSELF-RECEIVED. The record also has a PLUNAME field containing the DLU name “TSO” and a USERDATA field of “jones/jones”. Figure D-4.
LUNS High-Level Flow Diagrams Static Passthrough Static Passthrough Figure D-5 shows a terminal establishing a static passthrough session with the host, logging on to and logging off from two host applications (TSO and CICS) and then terminating the static passthrough session. Note that in the last sequence, LUNS discards the USS message from the host and does not send it to $SSCP. To establish the static path, LUNS uses an ESS table order record in which: 1. The character-coded command name is HOST 2.
LUNS High-Level Flow Diagrams Static Passthrough Figure D-5.
LUNS High-Level Flow Diagrams Static Passthrough (This page left intentionally blank) D–8 097841 Tandem Computers Incorporated
Appendix E SNAXUTL Error Messages SNAXUTL Error SNAXUTL error messages ordinarily appear in the user’s listing file. If the listing file Messages cannot be opened (because of an I/O error, for example), error messages are sent to the user’s home terminal. SNAXUTL ERROR NUMBER: 0020 A GETPOOL error occurred during an attempt to allocate a suboperand block. SNAXUTL ERROR NUMBER: 0040 A GETPOOL error occurred during an attempt to allocate a keyword block.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 0340 Invalid data was found following object parameters in the command table. SNAXUTL ERROR NUMBER: 0360 An invalid character was found following a command attribute in the command table. SNAXUTL ERROR NUMBER: 0380 An invalid character was found following a command operand in the command table. SNAXUTL ERROR NUMBER: 0400 An invalid character was found following a command in the command table.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 0660 A DEFINEPOOL failure occurred during initialization of the extended storage buffer pool. SNAXUTL ERROR NUMBER: 0680 An ALLOCATESEGMENT failure occurred during an attempt to allocate extended storage. SNAXUTL ERROR NUMBER: 0700 An I/O error occurred on a write to the listing file during error message processing. An error message might not be displayed.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 0920 A specified keyword is not unique. Enough characters must be specified to distinguish it from all other keywords for the given operand. SNAXUTL ERROR NUMBER: 0940 The specified operand text is too long to be a valid file name. SNAXUTL ERROR NUMBER: 0960 One or more characters specified in the system-name portion of a file name are not valid alphanumeric characters.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 1140 An error occurred during processing of the subvolume-name portion of a file name. The first character must be alphabetic. SNAXUTL ERROR NUMBER: 1160 An error occurred during processing of the subvolume-name portion of a file name. The subvolume name is too long. The name must begin with an alphabetic character, followed by from zero to seven alphanumeric characters.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 1320 An error occurred during the processing of hexadecimal-byte data for the current operand. An invalid prefix for the hexadecimal value was detected. The valid prefix is “%H”. SNAXUTL ERROR NUMBER: 1335 A numeric string is too long. Numeric strings that represent integers must consist of from one to six characters (including a plus or minus sign) and be within the range -32768 through +32767.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 1620 A device name is too long. SNAXUTL ERROR NUMBER: 1640 Invalid data was encountered following a device name. SNAXUTL ERROR NUMBER: 1660 A device name is too long. SNAXUTL ERROR NUMBER: 1680 No subdevice name was found following a device name. SNAXUTL ERROR NUMBER: 1686 A process name does not begin with a pound sign (#). A pound sign is required. SNAXUTL ERROR NUMBER: 1687 A process name is invalid.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 1900 An invalid hexadecimal prefix was found on a hexadecimal string. The prefix should be “%H”. SNAXUTL ERROR NUMBER: 1920 The percent sign (%) was not specified with a hexadecimal string. SNAXUTL ERROR NUMBER: 1940 A premature EOF was encountered during retrieval of a suboperand. SNAXUTL ERROR NUMBER: 1960 An invalid token was specified as a suboperand.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 2240 An error occurred during processing of the current command The modifier specified for the current command is invalid. SNAXUTL ERROR NUMBER: 2260 An error occurred during processing of the current command. The specified command or modifier is not unique. SNAXUTL ERROR NUMBER: 2280 An error occurred during processing of the current command. The specified command name is invalid.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 2560 The first command following the BEGIN command is not the SELECTFILE command. SNAXUTL ERROR NUMBER: 2570 Two adjacent SELECTFILE commands have been encountered within the same command group. Only one SELECTFILE command can be specified in a command group. SNAXUTL ERROR NUMBER: 2573 A command group with no executable commands has been encountered. That is, only BEGIN, SELECTFILE, and END commands have been specified.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 2720 An I/O error occurred during an attempt to write an ESS header record to an unstructured file during a copy operation. SNAXUTL ERROR NUMBER: 2740 An I/O error occurred during a read of an ESS record from a key-sequenced file during a copy operation. SNAXUTL ERROR NUMBER: 2760 An I/O error occurred during a read of an ESS message-segment record from a key-sequenced file during a copy operation.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 2980 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to write the header record for the key-sequenced version of the SET table SNAXUTL ERROR NUMBER: 3000 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to write the trailer record for the key-sequenced version of the SET table.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 3200 When an ALLOCATE command was being processed, an error occurred during an attempt to allocate the key-sequenced file. The file specified in the SELECTFILE command already exists. SNAXUTL ERROR NUMBER: 3220 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to create a key-sequenced file.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 3440 An error occurred during the processing of the ADD ESSCMD command. The GATELINE operand is invalid when either GATEPU or GATELU has been specified. SNAXUTL ERROR NUMBER: 3441 An error occurred during the processing of the ADD ESSCMD command. The GATELINE operand was specified with SENDHOST N. This combination is invalid unless CMDTYPE ORDER is specified.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 3600 An error occurred during the processing of the ADD ESSCMD command. The SNATYPE operand is invalid with SENDHOST Y. SNAXUTL ERROR NUMBER: 3620 An error occurred during the processing of the ADD ESSCMD command. The SNATYPE operand is invalid with CMDTYPE LOGOFF. SNAXUTL ERROR NUMBER: 3720 An error occurred during the processing of the ADD ESSCMD command.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 3980 An error occurred during the processing of the ADD ESSCMD command. USERDATA requires CMDTYPE LOGON-INIT or CMDTYPE LOGON-CHAR when SENDHOST N is specified. SNAXUTL ERROR NUMBER: 4000 An error occurred during the processing of the ADD ESSCMD command. When USERDATA is specified, CMDTYPE LOGON-INIT or CMDTYPE INITSELFRECEIVED must be specified with SENDHOST Y.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 4380 When an ADD ESSCMD command was being processed, an error occurred during an attempt to write an ESS record to the key-sequenced file. The record already exists. SNAXUTL ERROR NUMBER: 4390 When an ADD ESSCMD command was being processed, the ESS character-coded command was found to have the same name as an existing ESS message. An ESS command cannot have the same name as an ESS message.
SNAXUTL Error Messages SNAXUTL Error Messages an attempt to perform a KEYPOSITION for a header record in a key-sequenced file. SNAXUTL ERROR NUMBER: 4580 When an ADD ESSMSG command was being processed, an I/O error occurred during an attempt to perform a READUPDATE to read the header record from the key-sequenced file. SNAXUTL ERROR NUMBER: 4600 When an ADD ESSMSG command was being processed, an error occurred during an attempt to perform a KEYPOSITION for the header record in the keysequenced file.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 5120 When an ADD SETESS command was being processed, an I/O error occurred during a KEYPOSITION of the key-sequenced file to the header record. SNAXUTL ERROR NUMBER: 5140 When an ADD SETESS command was being processed, an I/O error occurred during an attempt to read a header record from the key-sequenced file.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 5720 When a DELETE command was being processed, an I/O error occurred during a KEYPOSITION to position file pointers to the header record of the SET table. SNAXUTL ERROR NUMBER: 5740 When a DELETE command was being processed, an I/O error occurred during a read of the header record of the key-sequenced SET table.
SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL ERROR NUMBER: 5980 When a DELETE command was being processed, an I/O error occurred on an attempt to delete an ESS message record. SNAXUTL ERROR NUMBER: 6000 When a DELETE command was being processed, an I/O error occurred on an attempt to read an ESS message segment from the ESS file. SNAXUTL ERROR NUMBER: 6020 When a DELETE command was being processed, an I/O error occurred during the open of the key-sequenced version of the ESS table.
SNAXUTL Error Messages SNAXUTL Error Messages Try the operation again. If the problem persists, consult your Tandem representative. SNAXUTL ERROR NUMBER: 6420 An error occurred during the open of $SSCP.#SNAXUTL. Check to see that SNAXUTL has been added through an ADD APPL command (such as ADD APPL $SSCP.#SNAXUTL, APPLTYPE LUNSAPPL, PASSWORD “SNAXUTL”). SNAXUTL ERROR NUMBER: 6430 A WRITEREAD error occurred during a CONNECT request to LUNS.
Appendix F SNAX/XF Default BIND Default SNAX/XF BIND SNAX/XF sends a default BIND if a BINDENTRY parameter is not specified in an SCF Bytes and Values ADD LINE, PU, or LU command, or if not specified in an ESS table entry. Table F-1 contains a summary of BIND byte numbers and default values. Table F-1.
SNAX/XF Default BIND Default SNAX/XF BIND Bytes and Values Bytes 14-25 The following table contains presentation services (PSERVIC) values for different devices and protocols. Table F-2. Presentation Services Profile — Bytes 14 Through 25 Byte Value 14 If non-6530, set to IBM SLU type from SCF ADD LU statement.
Glossary This glossary defines terms used in the SNAX/XF LU Network Services Manual. For abbreviations of terms specific to SNAX/XF and Tandem products, the definition consists of a cross-reference to the spelled-out term. In addition, several definitions have been taken from the IBM Dictionary of Computing and the IBM Network Program Products: General Information manual.
Glossary command interpreter. A direct interface between users and the operating system. Users at on-line terminals interact with the command interpreter by entering commands, and the command interpreter translates input to commands that a Tandem system executes. command message. An SPI message, containing a command, sent from an application program to a subsystem. See also SPI message. Compare event message or response message. communication controller.
Glossary error code. A value indicating the reason for the error. ESS table. See Enhanced System Services table. event. A significant change in some condition in the system or network. Events can be operational errors, notifications of limits exceeded, requests for action, notifications of lines and other objects becoming available, and so on. Note that an event is not always an error. Event Management Service (EMS).
Glossary protocol supports a single character stream; ITI translates the message and encloses it in the 3270 envelope. Katakana. The double-byte Japanese character set used with Japanese-language SNA terminals and printers. leased line. A connection between systems or devices that does not have to be made by dialing. Synonymous with nonswitched line. logical unit (LU).
Glossary NonStop operation. A Tandem system behavior characterized by continued operation even when a component fails, when equipment is being repaired or replaced, or while new processors or peripheral devices are being added to the system. Legally used only to describe the Tandem NonStop system or its features, such as NonStop process pairs. NS. Network services (one of the SNA functional layers). NSH. Network services header. OBEY file. A file that serves as a source for command input. object.
Glossary primary logical unit (PLU). The logical unit (LU) that controls an LU-LU session. Within each LU-LU session, one of the LUs is the primary and the other is the secondary. The most important control that the PLU exerts is the formatting and sending of the BIND request that initiates the session. process. Within the context of the Tandem NonStop system, a process is a unique execution of a program code module.
Glossary establish a data path between two LUs in separate domains for data exchange, four types of sessions must exist: SSCP-SSCP, SSCP-PU, SSCP-LU, and LU-LU. session passthrough. A SNAX/XF feature that allows the SNA host to control SNA devices on Tandem NonStop systems as if they were directly connected to the host. site update tape (SUT). The means by which Tandem software is distributed to all user sites. SLU. See secondary logical unit. SNA. Systems Network Architecture. SNALU.
Glossary subarea. In SNA, a portion of the SNA network consisting of a subarea node and its associated resources. Within a subarea node, all network addressable units and adjacent link stations that are addressable share a common subarea address and have distinct element addresses. subarea node. A node containing an SSCP or an NCP. A node type 5 and a node type 4 physical unit are subarea nodes. subarea node process (SNP). An internal SNAX/XF nonprivileged, major process that the user can run.
Glossary TAL. Transaction Application Language. TC. Transmission control (one of the SNA functional layers). TCP. Terminal control process. token. A distinguishable unit in an SPI message. A token has two parts: an identifying code, or token code, and a token value. In command and response messages, a token normally represents a parameter to a command, an item of information in a response, or control information for the subsystem.
Glossary (This page left intentionally blank) Glossary–10 097841 Tandem Computers Incorporated
Index A Active SET table 2-17 ADD command (SCF) ESSTABLE attribute 2-4 ADD command (SNAXUTL) CHARACTERSET operand 2-6, 2-8 CMDTYPE operand 2-4 passthrough 2-10 Pathway 2-8 specifications 2-4 TACL 2-5 CONCDATA operand APPLFILE |TACL 2-6 Pathway 2-8 ESSCMD modifier 2-4 GATELINE operand 2-9 GATELU operand 2-9 GATEPU operand 2-9 usage 2-4 ESSMSG modifier 2-15 usage 2-15 modifier 1-12 object 1-12 operand 1-12 PLUNAME operand Pathway 2-8 TACL 2-5 RECSIZE operand 2-6, 2-8 SETESS modifier 2-3 SNATYPE operand 2-6, 2
Index B Basic configuration example 3-1 BIND image default F-1 BIND images 1-4 BIND table purpose and function 1-14 Building the ESS tables options 2-4 C Character-coded logon records Pathway 1-12 TACL 1-12 CONCDATA operand example Pathway 2-9 TACL 2-7 CONCDATA operand syntax APPLFILE|TACL parameter 2-6 CPU parameter 2-6 INSPECT parameter 2-6 MEM parameter 2-6 NAME parameter 2-6 PARM parameter 2-6 Pathway 2-8 PRI parameter 2-6 PRINTER parameter 2-8 PROCESS parameter 2-8 PROGRAM parameter 2-8 Configuration
Index Creator error messages invalid data received from SNAX C-26 NEWPROCESS procedure call C-5 no keyword after comma in startup command C-29 PROCESS_CREATE procedure call C-5 syntax error—quote mismatch C-19 Creator process 2-29 ADD APPL definition for 2-20 command syntax 2-30 CREATOR specification 2-30 MAXPATHMONOPENS specification 2-30 MAXSESSIONS specification 2-30 NAME specification 2-30 NonStop operation 2-29 out file specification 2-30 OUT specification 2-30 PAID processor access ID 2-29 password 2
Index Dynamic modification ESS table 2-16 ADD APPL command 2-16 Pathway example 2-16 SCF configuration file 2-16 E Enhanced System Services table 1-4, 2-1, 2-4, 2-16 activation 2-16 allocation 3-14 creating 1-12 creating or adding to 1-13 deactivation 2-16 deleting 2-16 dynamic modification 2-16 logoff records 1-7 logon records 1-6 message records 1-6 order records 1-7 purpose and function 1-6 sample command block 1-12 Environment switching 1-1 ESS message 10 1-2, 2-4 ESS system messages B-1 ESS table See
Index Example application (continued) ADD SETESS usage (Part 1) 3-5 adding a PATHWAY application 3-8 adding a terminal LU 3-8 adding the ESS record (Part 1) 3-5 adding the primary line (Part 2) 3-12 ALLOCATE command (Part 1) 3-3 ALLOCATE command (Part 2) 3-11 ALTER SUBSYS usage (Part 1) 3-6 assigning Creator password 3-6 assigning Creator subdevice name 3-6 assigning the modified SET table (Part 1) 3-6 AUTOLOGON usage (Part 2) 3-12 basic configuration 3-1 CHARACTERSET specification (Part 1) 3-7 command fil
Index Example application (continued) SETTAB usage (Part 1) 3-6 specifying the SET table 3-11 START command usage (Part 1) 3-7 START command usage (Part 2) 3-12 START line (Part 1) 3-7 START LINE (Part 2) 3-12 START LU (Part 2) 3-12 START PU (Part 2) 3-12 Starting the Creator process (Part 1) 3-7 starting the Creator process (Part 2) 3-13 starting the lines (Part 1) 3-7 starting the primary line (Part 2) 3-12 updating the ESS table 3-13 using SCF 3-6 EXPAND network lines 2-9 LUs 2-9 PUs 2-9 Extended data s
Index I ITI protocol Pathway 2-8 ITI protocol (TACL) 2-6 K Katakana 2-4, 2-15, A-11 See Passthrough, REPDATA operand L Local system lines 2-9 LUs 2-9 PUs 2-9 Logoff processing CMDTYPE operand INITSELF-RECEIVED value 2-13 SNA-formatted TERM-SELF command 2-13 Logoff record non-passthrough 2-13 Logoff records 1-7 all-purpose 2-12 creating 2-4 Logoff sequence for passthrough session 2-13 Logoff terminals 2-12 Logon and logoff sequences flow diagrams D-7 high-level flow diagrams D-1 host application (INITSELF-R
Index Logons/logoffs character-coded 1-1 LU Network Services configuration tables creating new tables 2-3 table object file 2-3 table source file 2-3 Creator process NonStop operation 2-29 starting 2-29 using 2-29 ESS message 10 2-4 ESS tables logoff records 2-12 how LUNS processes Network-Service Requests 1-4 how terminals interface to LUNS 1-2 planning for 2-2 software that Tandem provides 1-14 starter ESS tables 1-14 starter SET table 1-14 static path establishing 2-13 LU Network Services (LUNS) Katakan
Index O Order record contents example 2-14 Order records 1-7, 2-13 creating 2-4 Overriding BINDENTRY attribute 2-25 Overriding BINDTABLE attribute 2-25 Overriding CHARACTERSET attribute 2-26 Overriding PROTOCOL attribute 2-27 Overriding RECSIZE attribute 2-27 Overriding SCF commands LOGON-CHAR value Pathway 2-8 TACL 2-5 LOGON-INIT value Pathway 2-8 TACL 2-5 Pathway 2-8 TACL 2-5 Overriding SCF LU attributes 2-25 P PAID processor access ID creator process 2-29 Passthrough BINDENTRY operand 2-10 CHARACTERSET
Index PATHMON 1-4 Pathway OPENS closing OPEN requests 2-9 Pathway process CRT protocol 2-8 example adding application 3-8 interface to LUNS 1-4 ITI protocol 2-8 PRT protocol 2-8 starting 1-4 Performance configuration example 3-15 Performance consideration 3-14 Performance reconfiguration example 3-16 Processor access ID PAID 2-29 PRT protocol Pathway 2-8 R Remote system lines 2-9 LUs 2-9 PUs 2-9 REPDATA field in passthrough 2-10 S SCF attribute summary object types 2-28 SCF configuration parameters 2-18 AB
Index SCF LU attributes overriding 2-25 SELECTFILE command (SNAXUTL) DEACTIVATE operand 2-16 DEACTIVE modifier 1-13 Session Establishment Table 1-4 SET table See Session Establishment Table before starting $SSCP 2-17 building 2-17 how to activate 2-17 purpose and function 1-9 replacing dynamically 2-17 specifying as active 2-17 specifying through SYSGEN 2-17 SNAX Creator-2 process functionality 1-3 SNAX/XF Service Manager 2-17 SNAX/XF Utility ADD command 1-12, 2-3, 2-4 ADD ESSCMD command syntax summary A-6
Index SNAX/XF Utility (continued) command verb A-3 command verb summary 1-12 comment usage A-5 defining to LUNS example 2-16 DELETE command 1-13 syntax summary A-23 dynamic ESS table modification 1-13 Edit command file 1-12 END command syntax summary A-23 error messages E-1 extended data segments A-4 general information A-1 invoking the program A-5 operand definitions A-3 RUN command A-5 RUN command syntax 1-13 sample command block 1-12 SELECTFILE command 1-12, 1-13, 2-3, 2-16 syntax summary A-24 syntax 1-
Index Subsystem Control Facility ADD command 2-4 ALTER command 2-17 specifying configuration parameters 2-18 System generation SETTABNAME modifier 2-17 System messages 2-15 adding 2-15 changing text 2-15 format 2-15 provided by Tandem 2-15 T Table object file 2-3 Table source file 2-3 TACL process APPL definition for 2-19 interface to LUNS 1-4 TCP See Terminal Control Process Terminal configuration planning example 3278 HELP menu 1-2 Terminal Control Process 1-4 Terminal interface 1-2 Terminating a host SS
