SNAX/XF LU Network Services Manual

Transcription

1 Networking and Data Communications Library SNAX/XF LU Network Services Manual Abstract Part Number Edition 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. Fifth Published December 1994 Product Version Release ID D30.00 Supported Releases SNAX/XF D30 (T9064D30) This manual supports release D30.00 and all subsequent releases until otherwise indicated in a new edition. Tandem Computers Incorporated

2 Document History Edition Part Number Product Version Earliest Supported Release Published First SNAX/XF C11 C10 March 1989 Second SNAX/XF C20 C20 April 1991 Third SNAX/XF D10/C30 D10.00/C30.00 February 1993 Fourth SNAX/XF D21 D72.00 based on D20.01 April 1994 Fifth SNAX/XF D30 D30.00 December 1994 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a.99 site update tape (SUT). Ordering Information Document Disclaimer Export Statement Examples U.S. Government Customers For manual ordering information: domestic U.S. customers, call ; international customers, contact your local sales representative. Information contained in a manual is subject to change without notice. Please check with your authorized Tandem representative to make sure you have the most recent information. Export of the information contained in this manual may require authorization from the U.S. Department of Commerce. Examples and sample programs are for illustration only and may not be suited for your particular purpose. Tandem does not warrant, guarantee, or make any representations regarding the use or the results of the use of any examples or sample programs in any documentation. You should verify the applicability of any example or sample program before placing the software into productive use. FOR U.S. GOVERNMENT CUSTOMERS REGARDING THIS DOCUMENTATION AND THE ASSOCIATED SOFTWARE: These notices shall be marked on any reproduction of this data, in whole or in part. NOTICE: Notwithstanding any other lease or license that may pertain to, or accompany the delivery of, this computer software, the rights of the Government regarding its use, reproduction and disclosure are as set forth in Section of the FARS Computer Software-Restricted Rights clause. RESTRICTED RIGHTS NOTICE: Use, duplication, or disclosure by the Government is subject to the restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS RESTRICTED RIGHTS LEGEND: Use, duplication or disclosure by the Government is subject to restrictions as set forth in paragraph (b)(3)(b) of the rights in Technical Data and Computer Software clause in DAR (a). This computer software is submitted with restricted rights. Use, duplication or disclosure is subject to the restrictions as set forth in NASA FAR SUP (April 1985) Commercial Computer Software Restricted Rights (April 1985). If the contract contains the Clause at Rights in Data General then the Alternate III clause applies. U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract. Unpublished All rights reserved under the Copyright Laws of the United States.

3 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. A subsection titled The Creator and SNAX Creator-2 Processes has been added to Section 1, Introduction to LUNS. In Section 2, Using LUNS, the subsection titled The ADD APPL Command has been rewritten. There are now four separate subheadings: ADD APPL Command for TACL Processes, ADD APPL Command for the Creator Process, and ADD APPL Command for SNAXUTL. The SCF attribute CRYPTOTYPE has been deleted from Section 2, Using LUNS. This attribute is no longer supported. The SNAXUTL ADD ESSCMD operand TERMSELF ON has been added to Appendix A, SNAX/XF Utility. The use of this operand is also described in Section 2, Using LUNS. The SNAXUTL ADD ESSCMD operand CRYPTOTYPE has been deleted from Appendix A, SNAX/XF Utility. This operand is no longer supported. Appendix B, LUNS Messages and Codes, has been retitled ESS System Messages. The subsection titled LUNS Internal Messages and Codes, has been deleted from it. The messages this subsection contained are now included in the description of EMS event message 81 in the Operator Messages Manual. ESS system message S0052 has been deleted from Appendix B, and ESS system messages S0018, S0053 S0054, and S0055 have been added. Appendix G, D-Series Systems Information, has been deleted. D-series information is now included under the heading Creator Process RUN Command Syntax in Section 2, Using LUNS, and in Appendix C, Creator Process Error Messages. New definitions have been added to the glossary. The index has been updated Tandem Computers Incorporated iii

4 New and Changed Information (This page left intentionally blank) iv Tandem Computers Incorporated

5 Contents About This Manual xi Notation Conventions xiii Section 1 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 Table 1-6 The SET Table 1-9 How LUNS Uses Configuration Tables 1-9 SNAX/XF Utility Overview 1-12 The BIND Table 1-14 What Tandem Provides 1-14 Section 2 Using LUNS Using This Section 2-1 Planning for LUNS 2-2 Creating New Configuration Tables 2-3 Building the ESS Tables 2-4 Logon, Logoff, and Order Records 2-4 Logon Records for Tandem TACL Processes 2-5 The CONCDATA Operand (APPLFILE TACL) 2-6 Logon Records for Pathway Processes 2-8 The CONCDATA Operand (Pathway) 2-8 Logon Records for Processes on a Host System (Passthrough) 2-9 Logoff Records for Logging Off All Processes 2-12 Order Records for Host SSCP-LU Sessions (Static Passthrough) 2-13 Message Records Tandem Computers Incorporated v

6 Contents Modifying ESS Tables Dynamically 2-16 Specifying the SET Table 2-17 Specifying SCF Configuration Parameters 2-18 The ALTER Command 2-18 The ADD APPL Command 2-18 The ABORT APPL Command 2-21 The ADD LINE, PU, and LU Command Attributes 2-22 AUTOLOGON Attribute 2-22 ESSTABLE Attribute 2-23 NOACQ Attribute 2-24 ESS LU Attributes That Override SCF LU Attributes 2-25 BINDENTRY Attribute 2-25 BINDTABLE Attribute 2-25 CHARACTERSET Attribute 2-26 PROTOCOL Attribute 2-27 RECSIZE Attribute 2-27 SCF Attribute Summary 2-28 Using the Tandem Creator Process 2-29 Startup Security Issues 2-29 Creator Process RUN Command Syntax 2-30 Section 3 Application Example Creating the Basic Configuration 3-1 Operational Assumptions 3-2 Configuration Assumptions 3-3 Creating a Command File for SNAXUTL 3-3 Configuring the System Through SCF 3-6 Starting the Tandem Creator Process 3-7 Adding an Application and Terminal to a Second System 3-8 Operational Assumptions 3-10 Configuration Assumptions 3-10 Creating a Command File for SNAXUTL 3-11 Using SCF to Add the New Application and LU to \SYS Starting the Tandem Creator Process on \SYS Updating the ESS Table on \SYS ESS Table Allocation and Performance 3-14 Configuration Suggestion 3-15 vi Tandem Computers Incorporated

7 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 A-20 SNAXUTL BEGIN Command A-23 SNAXUTL DELETE Command A-23 SNAXUTL END Command A-23 SNAXUTL SELECTFILE Command A-24 Appendix B ESS System Messages Finding an Assigned ESS Table B-1 Messages and Codes B-2 Appendix C Creator Process Error Messages Creator Process LOGON and LOGOFF Messages C-1 Numbered Creator Process Messages C-3 Appendix D LUNS High-Level Flow Diagrams Logon and Logoff for a Host Application (LOGON-CHAR) D-2 Logon and Logoff for a Host Application (LOGON-INIT) D-4 Logon and Logoff for a Host Application (INITSELF-RECEIVED) D-5 Static Passthrough D-6 Appendix E SNAXUTL Error Messages SNAXUTL Error Messages E Tandem Computers Incorporated vii

8 Contents Appendix F SNAX/XF Default BIND Default SNAX/XF BIND Bytes and Values F-1 Bytes F-1 Bytes F-2 Glossary Glossary 1 Index Index 1 Figures 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) 1-10 Figure 1-6. The ESS Table and LUNS Processing (Pathway) 1-11 Figure 2-1. LUNS Use of the REPDATA Field in Passthrough 2-11 Figure 2-2. LUNS Use of a Replacement DLU in Passthrough 2-12 Figure 2-3. Logoff Sequence for Passthrough Sessions Where the Logon Record Specified LOGON-CHAR 2-13 Figure 2-4. Order Records in the ESS Table 2-14 Figure 3-1. Application Example, Part Figure 3-2. Application Example, Part Figure A-1. SNAXUTL Command Syntax A-2 Figure D-1. Logon and Logoff Sequences for a Host Application (CMDTYPE LOGON-CHAR and No REPDATA Field) D-2 Figure D-2. Logon and Logoff Sequences for a Host Application (CMDTYPE LOGON-CHAR and REPDATA Field) D-3 Figure D-3. Logon and Logoff Sequences for a Host Application (CMDTYPE LOGON-INIT and USERDATA Field) D-4 Figure D-4. Logon and Logoff Sequences for a Host Application (CMDTYPE INITSELF-RECEIVED and USERDATA Field) D-5 Figure D-5. Static Passthrough D-7 viii Tandem Computers Incorporated

9 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. Presentation Services Profile Bytes 14 Through 25 F Tandem Computers Incorporated ix

10 Contents (This page left intentionally blank) x Tandem Computers Incorporated

11 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. How This Manual Is Organized Related Manuals The manual contains the following sections: Section 1 introduces LUNS. It explains how LUNS processes network-services requests and gives an overview of the configuration tables that LUNS uses in doing this. Section 2 provides information about how to plan and configure for LUNS. It explains how to create all necessary configuration tables using the SNAX/XF Utility (SNAXUTL) and includes information about Subsystem Control Facility (SCF) configuration. Section 3 provides an example of an application. This example implements a simple network configuration that nonetheless illustrates the range of services LUNS offers. The example shows all SNAXUTL and SCF commands needed to create the configuration. Appendix A shows the command syntax for SNAXUTL. Appendix B lists LUNS system messages and error codes. Appendix C lists Creator process error messages and codes. Appendix D consists of high-level flow diagrams that illustrate how LUNS handles unsolicited logons and environment switching. Appendix E lists SNAXUTL error messages. Appendix F contains the SNAX/XF default BIND values. To fulfill configuration and network-management tasks, system programmers and managers may find useful information in the Tandem books listed below, some of which are cited in subsequent sections of this manual: SNAX/XF Application Programming Manual SNAX/XF Configuration and Control Manual SNAX/XF Management Programming Manual SCF Reference Manual for SNAX/XF System Generation Manual for SNAX/XF Tandem Computers Incorporated xi

12 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-2 Configuration and Control Manual For additional information about the D-series operating system refer to the following Tandem documents: Introduction to D-Series Systems D-Series System Migration Planning Guide Guardian Application Conversion Guide In addition to the Tandem manuals listed above, there are various IBM manuals relevant to SNA. Consult your local systems analyst or IBM representative for more information. Your Comments Invited After you have had a chance to use this manual, please take a moment to fill out the Reader Comment Card at the back of this manual and send it to us. Your comments will help us improve future editions. xii Tandem Computers Incorporated

13 General Syntax Notation UPPERCASE LETTERS lowercase italic letters Brackets [ ] Notation Conventions 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 indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name 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. For example: LIGHTS [ ON ] [ OFF ] [ SMOOTH [ num ] ] K [ X D ] address-1 Braces { } Vertical Line A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON OFF } A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } Tandem Computers Incorporated xiii

14 Notation Conventions General Syntax Notation Ellipsis... Punctuation Item Spacing 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 ]... [ - ] { }... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" 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 If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [, attribute-spec ]... xiv Tandem Computers Incorporated

15 Notation Conventions Notation for Messages Notation for Messages Nonitalic text lowercase italic letters The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name Brackets [ ] Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list might be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LDEV ldev [ CU %ccu CU %... ] UP [ (cpu,chan,%ctlr,%unit) ] Braces { } Vertical Line Percent Sign % A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LBU { X Y } POWER FAIL process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK Failed } A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: % P=%p-register E=%e-register Tandem Computers Incorporated xv

16 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. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. xvi Tandem Computers Incorporated

17 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. This manual discusses LUNS from both a conceptual and a practical point of view by: Giving you a general overview of how LUNS works Explaining the preparatory steps you must take to use LUNS Showing, through an application example, how to create the configuration tables necessary for LUNS operation What LUNS Does LUNS allows SNA users on a Tandem system to access processes that run on: That particular Tandem system Other Tandem systems within an Expand network An IBM or equivalent host system. (Note that throughout this manual, host and host system mean an IBM system or its equivalent.) LUNS provides for: Unsolicited logons. Users can start or stop a TACL process or Pathway application by entering character-coded commands. Also, character-coded commands can be used to log on to a host application. For intelligent devices (such as automated teller machines) that use SNA-formatted INIT-SELF and TERM-SELF requests, LUNS allows for unsolicited logons to host programs without having to modify the INIT-SELF request. Environment switching. LUNS allows environment switching without a system operator s intervention. For example, using character-coded commands, a terminal user can log on to a host program, log off, and then log on to a Tandem program or do the reverse-without having to know where in the network the programs are located. Message display. Users can retrieve and display predefined user and system messages at the terminal device. Menu instruction. The ability of LUNS to display messages and other information allows the use of menus for providing instructions to the terminal user Tandem Computers Incorporated 1 1

18 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). This menu explains how to log on to and off from each of the various applications. (In creating both character-coded commands and the menu, the system programmer can employ either the alphabetic or the single-byte Katakana character set.) Figure 1-1 is an example of such a menu as it would appear on a 3278 terminal. (This menu represents the configuration that is implemented in the first part of the application example in Section 3.) For this example, the TACL process and Order Entry applications reside on the Tandem system, while TSO resides on the host. Figure 1-1. HELP Menu Screen TO ACCESS TACL ORDER ENTRY TSO HOST TANDEM ENTER TACL ORDERENTRY TSO HOST TANDEM TO LOGOFF LOGOFF When the terminal is started with the Subsystem Control Facility (SCF) START LU command, it receives an Enhanced System Services (ESS) message 10, consisting of a Tandem logo. A symbol at the bottom of the screen indicates that the terminal is already in an SSCP-LU session. By typing HELP (or another command defined by the system programmer), the terminal user can display the menu and use the appropriate commands to log on to or off from any of the applications. Logging On to Order Entry In this example, the application called ORDER ENTRY is a Pathway application residing on the Tandem system. To log on, the terminal user types in the characters ORDERENTRY and presses the ENTER key. When the session is established, an LU-LU session symbol appears at the bottom of the screen. To log off, the user presses the SYSTEM REQUEST key, then enters the LOGOFF command. The ESS message 10 and the SSCP-LU session symbol reappear Tandem Computers Incorporated

19 Introduction to LUNS Defining Processes to LUNS Logging On to TSO Establishing a Static Passthrough Path 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). The fact that a switch of environments accompanies the switch from one program to the other remains transparent to the terminal user. The terminal user now wishes to log on to the host system to take advantage of its full range of programs. Entering the HOST command causes the host s Unformatted System Services (USS) message 10 to appear on the screen. The user can then log on to any of the host s programs for which security access has been given. A logoff command will cause the host s USS message 10 to reappear, along with an SSCP-LU session symbol at the bottom of the screen. By typing and entering the TANDEM command, the user can return to the Tandem system, receive the Tandem ESS message 10, and log on to ORDER ENTRY or TSO once again. Note The Creator and SNAX Creator-2 Processes If the terminal user initiates a session with a Tandem TACL process, do not press the SYSTEM REQUEST key before a logoff unless the terminal user wanted LUNS to stop the process. Using LUNS for terminal logons to Tandem applications requires that an auxiliary process be present on the system. Tandem provides two such processes: the Creator process and the SNAX Creator-2 process. This manual discuss only the functionality offered by the Creator process. The SNAX Creator-2 process can perform the same functions as the Creator process, but offers more functionality and greater flexibility. Like the Creator process, it can start TACL processes and interface to Pathway Monitor processes. In addition, it can interface to a user-written server process that starts non-pathway processes. Although SNAX Creator-2 is regarded as a process by the operating system, SCF views it as a subsystem. Users can therefore create a database to store configuration parameters entered through SCF commands. As a subsystem, SNAX Creator-2 has its own SCF objects and attributes through which users can exercise control and obtain information. Much of the data that must be entered into the LUNS configuration tables when the Creator process is used can instead be entered through SCF. The same configuration database can be used by multiple instances of the SNAX Creator-2 process. For an overview of SNAX Creator-2 and information on how to configure it for use with LUNS, see the SNAX Creator-2 Configuration. Defining Processes to LUNS To process logons in the manner described previously, LUNS must be made aware of those processes on the Tandem system to which LUNS and the user are to interface. Thus, the Tandem TACL process and the Tandem Creator process must be defined to LUNS by means of an SCF command called ADD APPL (for more detailed information, see Section 2) Tandem Computers Incorporated 1 3

20 Introduction to LUNS LUNS Configuration Tables Starting TACL Processes With the Creator Process Starting Pathway 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. Pathway applications also interface to LUNS by means of the Tandem Creator process. When the user logs on to the Pathway application, the Tandem Creator process receives a request from LUNS and establishes communications with Pathway, passing the terminal name and the name of the Pathway program to the relevant Pathway monitor (PATHMON) process. The PATHMON then instructs the terminal control process (TCP) to open the terminal on behalf of the Pathway program. Note that you need not define Pathway programs to LUNS through an ADD APPL command. LUNS knows how to route the logons because of a field in an ESS table. This field contains the names of a PATHMON and a destination Pathway program. Note At any given time, the Creator process can establish a combined total of 400 TACL and Pathway sessions running C-series system software, 2000 sessions when running the ITI and CRT protocols on D-series system software, or 1000 sessions when running the SNALU protocol on D-series system software. LUNS Configuration Tables Notation Used for Configuration Tables To process character-coded commands and INIT-SELF requests, LUNS must use information derived from the following configuration tables: An Enhanced System Services (ESS) table The Session Establishment (SET) table Using SNAXUTL, systems programmers design and create these tables, tailoring table entries to the needs of their particular networks. Such a task requires an understanding of what these tables are and how they aid in establishing LU-LU sessions. Another aspect of establishing LU-LU sessions is that of the PLU and SLU agreeing on communications rules. LUNS allows these communications rules to be passed from the PLU to the SLU through session parameters sent in a BIND. Through SNAXUTL, LUNS allows users to build BIND entries and place them in BIND tables that are later selected for use at session establishment. The following figure illustrates the conventions used in this manual to depict configuration tables and the various records within. Note that theses figures provide a logical representation of the information; however, the actual records are not stored in exactly this way Tandem Computers Incorporated

21 Introduction to LUNS LUNS Configuration Tables Figure 1-2. Notation Used to Depict Tables ORDERENTRY, PLUNAME #CREATE A table (in this case an ESS table) is represented by a ruled box. Each of the ruled divisions within the larger box represents a record within the table. 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. PLUNAME is an operand name, or keyword, defined by the SNAX Utility. You use these operand names when you create a field within a table record. In this way, the utility knows what type of data you are submitting, because the utility allows you to enter operand data in any order. Although the operand name is not exactly a part of the table itself, it is included here so that you can easily identify the type of field being depicted. #CREATE, following the operand name, represents the actual operand data (parameter). In this case, it is the logical name of the Tandem Creator process, which communicates with a PATHMON to establish a session with a Pathway application. Ellipsis points indicate that optional parameters can be added or that certain required parameters have been omitted for reasons of space or clarity. For a discussion of required and optional parameters within a given table type, see Section 2 and Appendix A. 7 The empty record division with the curving lower edge signifies that other records can exist in or be added to the table Tandem Computers Incorporated 1 5

22 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. This field serves as a key when LUNS searches the table for a particular record. Message Records Message records contain either system messages or messages defined by the user. (Appendix B lists all system messages.) Message text can use either the alphabetic or the single-byte Katakana character set. A message is displayed when a character-coded command is entered at the terminal. Logon Records Logon records are used to start TACL or Pathway processes or to log on to host applications. One type of logon record has in its record-name field a character-coded command matching a character-coded command entered by the terminal user. Such records are used to log on to applications on a Tandem system or to applications on a host. The character-coded commands can use either the alphabetic or the single-byte Katakana character set. The other type of logon record has in its record-name field a Destination Logical Unit (DLU) name matching a DLU name in an INIT-SELF command sent by an intelligent device. Such records can be used to log on to applications on a host system. Logon records also have a field that explicitly identifies a destination process. In most cases, this field is one that is separate from the record-name field. Exceptions are discussed later in this section under Logon Records for Passthrough Sessions. Logon Records for a TACL Process. LUNS knows the Tandem TACL process by its subdevice name as it was specified in an SCF ADD APPL statement. The ESS table entry also contains the subdevice name for the TACL process. LUNS uses this subdevice name to start the process. When establishing a session, LUNS passes NEWPROCESS parameters to the Creator process. These parameters are included in the concatenated data field of the logonrecord (for more information, see Section 2) Tandem Computers Incorporated

23 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. Its subdevice-name field, however, contains not the subdevice name of the application itself, but that of the Tandem Creator process. It is the concatenated-data field that contains the names of a PATHMON and a destination Pathway application. Logon Records for Passthrough Sessions. Records establishing passthrough sessions with a host process can take several forms. All such records are discussed in detail under Building the ESS Tables in Section 2. Below is a brief overview of passthrough records: When such a record has a character-coded command for its record-name field, the field that would otherwise contain a subdevice name either: Contains a DLU name if LUNS is to send the host process an INIT-SELF request. Remains unused if LUNS is to pass the character-coded command to the host. In this case, a destination process on the host need not be explicitly identified, because the host is responsible for interpreting the character-coded command entered by the user. When a Tandem ESS table record has a DLU name for its record-name field, that type record is used to route an INIT-SELF request to the host. The INIT-SELF is routed through a gateway LU as specified in the record. Logoff Records Logoff records allow terminal users to log off from application processes. Order Records To dynamically establish a host SSCP-LU session, the system programmer must include an order record in the ESS table. The SNAXUTL ADD ESSCMD command operand STATIC ON must be specified. To terminate the host SSCP-LU session and reestablish the Tandem SSCP-LU session, the system programmer must include an order record in the ESS table. The SNAXUTL ADD ESSCMD command operand STATIC OFF must be specified Tandem Computers Incorporated 1 7

24 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 ORDERENTRY, PLUNAME #CREATE, CONCDATA "params" TACL, PLUNAME #TACL, CONCDATA "params" INV, SENDHOST Y, GATELINE $G TSO1, SENDHOST Y, GATELINE $G1, PLUNAME TSO HOST, STATIC ON A logon record for a Pathway application (type = LOGON-CHAR). This record relates the character codedcommand ORDERENTRY to the Tandem Creator process's logical name #CREATE. The record also contains a concatenated data field specifying Pathway parameters to be passed to the Creator process. A logon record for a Tandem TACL process (type = LOGON-CHAR). This record relates the character coded command TACL to the application's logical name #TACL. The record also contains a concatenated data field specifying NEWPROCESS parameters to be passed to the Creator process. A logon record for a host application (type = INITSELF-RECEIVED). The DLU name in the record name (INV) identifies a host process. Note that one field (SENDHOST Y) must specify that the logon request should be sent to the host; another specifies a gateway line for the passthrough session. A logon record for a host application (type = LOGON-INIT). This record relates the character-coded command TSO1 to a host process whose DLU name is TSO. Note that one field (SENDHOST Y) must specify that the logon request should be sent to the host; another specifies a gateway line for the passthrough session. An order record (type = ORDER). This record causes LUNS to set up a host SSCP-LU session upon receipt of the character-coded command HOST. 002 Note that more than one active ESS table can exist within a Tandem system. For more information, see the following subsection. Additional parameters and the use of multiple ESS tables are discussed fully under Building the ESS Tables in Section Tandem Computers Incorporated

25 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. For ESS tables, the record can also indicate that a particular table is the default table for the entire system. Figure 1-4 shows the contents of a SET table record for an ESS table. Figure 1-4. Record for an ESS Table in the SET Table ESS1, $SYSTEM.SNAX.ESSTAB1, DEFAULTTABLE Y Record for an ESS table. This record relates the table name ESS1 to the file name $SYSTEM.SNAX.ESSTAB1. The table has been flagged as the default table. 003 On any Tandem system (node), there can be only one active SET table, which is itself defined to LUNS either by means of the service manager SETTABLENAME modifier in the peripherals paragraph (specified in the SYSGEN phase of INSTALL) or through the SETTABLENAME attribute of the SCF ALTER SUBSYS command. How LUNS Uses Configuration Tables When a terminal user enters a character-coded command or an intelligent device sends an INIT-SELF request, LUNS searches that terminal s ESS table for a corresponding record-name field. Upon finding such a name and its associated record, LUNS scans that record s other fields for information needed to set up the LU-LU session. If a passthrough session is specified, LUNS sends the logon either a character-coded command or INIT-SELF directly to the host. If a static passthrough path is specified, LUNS establishes a host SSCP-LU session for the terminal. When the logon record does not specify a passthrough session, LUNS searches it for information needed to set up a session with an application on the Tandem system. Figure 1-5 shows how LUNS uses an ESS table to process a logon request for the TACL process, whose character-coded logon is TACL Tandem Computers Incorporated 1 9

26 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 The terminal operator enters the character-coded command TACL. 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. LUNS knows from its internal control blocks that #TACL has been associated with the Creator process through a SCF ADD APPL command. In the same way, it knows the name of the object file where #TACL can be found. LUNS therefore sends the Creator process a CINIT request with the concatenated data, along with the name of the object file. The Creator creates the TACL and informs it of the logon. The TACL opens the terminal. 004 Figure 1-6 shows how LUNS uses an ESS table to process a logon request for a Pathway application whose character-coded logon is CRED Tandem Computers Incorporated

27 Introduction to LUNS LUNS Configuration Tables Figure 1-6. The ESS Table and LUNS Processing (Pathway) OPEN LU 6 TCP 5 $PATHX 4 Creator Process Terminal CRED 1 LUNS CINIT 3 2 CRED, PLUNAME #CREATE, CONCDATA "PATHWAY NAME $PATHX PROGRAM CREDIT" ESS Table The terminal operator enters the character-coded command CRED. LUNS searches the ESS table for a record named CRED and finds it. LUNS also finds the Tandem Creator process's logical name (#CREATE) and a concatenated data field specifying a PATHMON named $PATHX and a Pathway application program named CREDIT. LUNS sends the Tandem creator process a CINIT request with the concatenated data included. The Creator process sends $PATHX the name of the terminal and of the Pathway application program (CREDIT). $PATHX instructs the terminal control process (TCP) to open the terminal. The TCP opens the terminal on behalf of the Pathway application program (CREDIT). 005 See Appendix D for high-level flow diagrams that show logons and logoffs for host applications and logons and logoffs for static passthrough applications Tandem Computers Incorporated 1 11

28 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. SNAXUTL Command Verbs Verb ADD ALLOCATE BEGIN DELETE END SELECTFILE Function Adds a record to a configuration table Allocates disk space for both the table s source and object files Delimits the beginning of a command block Deletes a record from a configuration table Delimits the end of a command block Selects or names the source file upon which subsequent commands are performed Creating a New ESS Table In creating a new ESS table, you use the SELECTFILE ESS command to give the table a name and the ALLOCATE command to allocate disk space for it. Subsequent ADD commands build each of the table s records. In adding records to an existing table, you use the SELECTFILE command to select the table you wish to augment. A series of ADD commands builds the new records. Within an ADD command, the verb ADD is followed by: A modifier, defined by SNAXUTL syntax, that specifies the type of record being added. An object that you provide as a record-name field and that serves as a key to the record. Operands defining other fields within the record. These operands have two parts: the operand name (a keyword defined by SNAXUTL syntax) and the operand data (specifications you supply). The formal syntax is: verb [ modifier [ object [ operand [, operand...]]]] You enter a series of such commands into an EDIT command file. Input commands are free-format and allow for inclusion of comments. BEGIN and END commands must, however, enclose all command blocks. The following example shows a SNAXUTL command block that creates a new ESS table with character-coded logon records for a TACL process and a Pathway application, both residing on a local Tandem system Tandem Computers Incorporated

29 Introduction to LUNS SNAX/XF Utility Overview BEGIN SELECTFILE $SYSTEM.SNAX.ESSTAB1, TYPE ESS ALLOCATE 10 ADD ESSCMD MYTACL, CMDTYPE LOGON-CHAR, PLUNAME #TACL, PROTOCOL ITI, CONCDATA "TACL, CPU 0" &! verb, modifier, object &! command-type operand &! subdevice-name operand &! protocol operand! concatenated-data! operand ADD ESSCMD CRED, &! verb, modifier, object CMDTYPE LOGON-CHAR, &! command-type operand PLUNAME #PATH, &! subdevice-name operand PROTOCOL CRT, &! protocol operand CONCDATA ("PATHWAY ", &! concatenated- "NAME $PATHX,", &! data operand "PROGRAM CREDIT") END When the command file is complete, you invoke the SNAXUTL program to create the new ESS table: TACL> SNAXUTL/IN command-file, OUT listfile/ Creating or adding to a table involves two files in addition to the command file: 1. The table source file, a key-sequenced file by which SNAXUTL accesses the various records 2. The table object file, an unstructured file into which SNAXUTL copies the table source file and from which LUNS takes the information it needs for processing In the SELECTFILE command that names or selects a table, only the table source file need be specified. When a new table is created, SNAXUTL automatically gives the table object file a name, and the subsequent ALLOCATE command allocates space for both files. When a table is changed through SNAXUTL, both files are updated simultaneously. SNAXUTL also provides a DELETE command. This command is the reverse of the ADD command; it permits the deletion of individual records from a table. Note that SNAXUTL allows you to modify a currently active ESS table dynamically. Dynamic ESS table modification requires that you: Define SNAXUTL as an APPL object through SCF Specify the DEACTIVE operand of the SNAXUTL SELECTFILE command For further details, see Modifying ESS Tables Dynamically in Section 2. For complete SNAXUTL syntax, see Appendix A Tandem Computers Incorporated 1 13

30 Introduction to LUNS The BIND Table The BIND Table What Tandem Provides 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. When SNAXUTL builds the BIND table, it creates a source file and an object file. The object file is used by SNAX/XF to retrieve the BIND image. The source file is a keysequenced file, and the object file is an unstructured file. Use the SCF ADD or ALTER BINDENTRY command to associate BIND images to LUs. When an application opens the LU, the BIND entry name specified with SCF is used to retrieve the BIND image from the BIND table. A BIND table name and/or BIND table entry can also be specified in an ESS table entry. With the SNAX/XF release, Tandem supplies: A Tandem Creator process Two starter ESS tables: $SYSTEM.SNAX.SMLNERRS, an edit command file containing only system messages and a Tandem logo as the ESS message 10 $SYSTEM.SNAX.ESSFILE, an edit command file containing various types of command records and message records A starter SET table with: $SYSTEM.SNAX.SETFILE, a command file containing SNAXUTL commands that creates a SET table and adds to it four ESS table records $SYSTEM.SNAX.SNXSET, a table source file with four records; these records contain entries identical to those that would be created by the SNAXUTL commands in $SYSTEM.SNAX.SETFILE $SYSTEM.SNAX.SNXSETO, a table object file corresponding to the table source file in $SYSTEM.SNAX.SNXSET Tandem Computers Incorporated

31 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. 7. Run the Tandem Creator process. 8. Start the Pathway environment if terminals will be logging on to Pathway applications. Each of the following subsections presents information you need to perform these tasks. Together, they provide information about options, requirements, and limitations that apply to any LUNS implementation. Using This Section In the following discussion of LUNS configuration tables, note the following: The object of the SNAXUTL ADD ESSCMD command is called the commandname field. The object of the SNAXUTL ADD ESSMSG command is called the message-name field. (In Section 1, Introduction to LUNS, the command-name field and the messagename field were included in the generic term record-name field, since both types of fields denote the name of a record within an ESS table.) The various other fields in a given record are referred to by the SNAXUTL operand names (keywords) used to create them. For example, the field that specifies a terminal protocol is called the PROTOCOL field; the field that specifies a subdevice or SNA name is called the PLUNAME field; the field that specifies concatenated data is called the CONCDATA field, and so on Tandem Computers Incorporated 2 1

32 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. Any ESS table you wish to flag as a default table. Note that having a default ESS table is optional. All character-coded commands and DLU entries for logging on to the various applications. These will constitute the command names of the logon or INIT-SELF records within an ESS table. The number, type, and content of the fields within these records depend on: The location of the application receiving the logon (Tandem system or host) The type of terminal logging on (3270-series or intelligent) The type of session to be established (LU-LU or host SSCP-LU) Any Pathway or NEWPROCESS parameters that must be passed to the Creator process. Any user messages you wish to add to the ESS table. Any system messages you wish to change in the ESS table. The extent sizes for all SET and ESS tables you are creating (if you are not using the default size). All SCF attributes for the terminal and gateway LUs. Once you have determined all of the above, you are ready to use SNAXUTL and SCF to create the configuration you require Tandem Computers Incorporated

33 Using LUNS Creating New Configuration Tables Creating New Configuration Tables Within a command file, the SNAXUTL SELECTFILE command names the table source 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.fffffffo Thus, if the SNAXUTL SELECTFILE command were to name a table source file $SYSTEM.SNAX.ESSTAB1, the table object file would automatically be named $SYSTEM.SNAX.ESSTAB1O. Because SNAXUTL creates this file immediately upon creating the table source file, you must make sure that SNAXUTL will not attempt to give it the name of a file that already exists. Otherwise, an allocation failure occurs. To guard against this, Tandem recommends that all LUNS files be placed in a separate subvolume. Immediately after the SELECTFILE command, you must include a SNAXUTL ALLOCATE command. When SNAXUTL is run, space is allocated for both source and object files. The space reserved for each of these files is equal. The ALLOCATE command allows you to specify an extent size, in pages, for any file you allocate. The command syntax is: ALLOCATE extent-size extent-size specifies the number of pages that an individual extent contains. The file system can automatically provide you with as many as 16 extents for any file you allocate. Thus, were you to specify extent-size as 20 pages, your file could contain a maximum of 320 pages (16 * 20 pages). Tandem recommends that you specify 10 pages. If you wish to calculate the extent size yourself, see ALLOCATE Command in Appendix A. When you create an ESS table, you must add a record for it to the SET table with the SNAXUTL ADD SETESS command. See Specifying the SET Table in this section Tandem Computers Incorporated 2 3

34 Using LUNS Building the ESS Tables Building the ESS Tables Logon, Logoff, and Order Records In planning for LUNS, you should determine how many ESS tables you need and how 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. Create one or more tables and associate them with individual terminals through the ESSTABLE attribute of the SCF ADD LU, ADD PU, or ADD LINE command. In this way, only those associated terminals receive the ESS message 10 and use LUNS. 3. Create a default table, but use the ESSTABLE attribute of the SCF ADD LU, ADD PU, or ADD LINE commands to associate certain terminals with different ESS tables. Because the SCF attribute overrides the default table name, LUNS uses the specified tables when processing system requests from these terminals, while continuing to use the default table with the rest. The last two options offer flexibility. Option 2 makes it theoretically possible for each terminal to use a separate ESS table. Thus, you can customize each terminal, allowing it logon access only to those processes you determine. You create all ESS table logon, logoff, and order records with the SNAXUTL ADD ESSCMD command. The format of this command is as follows: ADD ESSCMD command-name, CMDTYPE command-type command-name must contain either a character-coded command or DLU name. (Note that the character-coded command can use either the alphabetic or single-byte Katakana character set.) The CMDTYPE operand command-type must always specify one of the following values: INITSELF-RECEIVED ORDER specifies that the logon request is an SNA-formatted INIT-SELF and the logon record has a command-name field containing a corresponding DLU name. A logon record with a CMDTYPE of INITSELF-RECEIVED is used only for passthrough sessions. specifies that LUNS is to establish or terminate a host SSCP-LU path Tandem Computers Incorporated

35 Using LUNS Building the ESS Tables LOGON-CHAR specifies one of the following cases: LOGON-INIT 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. specifies one of the following cases: LOGOFF 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 (ADDUSERDATA), and LUNS is to send an INIT-SELF to a process on the host. specifies that LUNS is to log a terminal off from whatever process it is logged on to. For all logon records pointing to a host process, you must also specify the SENDHOST operand: SENDHOST { Y N } Specify as Y (yes). The default value for this operand is N (no). The inclusion of other operands depends both on what type of terminal is accessing the process, and whether the process in question resides on the host or the Tandem system. For more information regarding the ADD ESSCMD command, see Appendix A. Logon Records for Tandem TACL Processes To build a logon record that points to a TACL process, specify command-type as either LOGON-CHAR or LOGON-INIT. You must also include the 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 (#). With both command types, you have the option of overriding the terminal protocol specified in the SCF ADD LU command. Note that you can do this only if the protocol specified through SCF is either CRT, ITI, or PRT. Also note that you cannot override the terminal protocol through the ESS table if it has been specified as SNALU through SCF Tandem Computers Incorporated 2 5

36 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. If ASCII is specified, no translation will occur. If EBCDIC is specified, ASCII/EBCDIC translation will take place. If KATAKANA is specified for Japanese-language SNA terminals, JIS 6220 Katakana/EBCDIC Katakana translation will take place. (For EBCDIC terminals that establish sessions with Tandem applications coded in ASCII and do not use the Katakana character set, CHARACTERSET should be specified as EBCDIC.) SNATYPE sna-type specifies the type of SLU support that the terminal will use. Valid values for sna-type are: 0, 1, 2, 3, 4, and 6. The CONCDATA Operand (APPLFILE TACL) For records pointing to applications on a Tandem system, SNAXUTL also provides the CONCDATA operand: CONCDATA concatenated-data The CONCDATA operand is used to specify data that LUNS will concatenate with the CINIT command that is sent to the Creator process. The data can be any string ranging from 1 to 1880 bytes in length. Within the CONCDATA operand, bytes can be specified either as characters or as hexadecimal or octal byte values. When data strings exceed one line, you can use a line continuation sequence (a comma, followed by an ampersand character: &). Note that if you specify CONCDATA in a record pointing to a host process, SNAXUTL will reject it. It is the CONCDATA operand that allows you to specify the necessary NEWPROCESS procedure call parameters the Creator process uses to create an APPLFILE (CRT or ITI process, including TACL) or TACL process and establish the LU-LU session. If either APPLFILE or TACL is specified, the Creator process issues a NEWPROCESS call to the APPLFILE process configured with SCF. It is recommended that the APPLFILE parameter be used for all subsequent non-pathway logon procedures, including TACL logons. However, note that the APPLFILE and TACL parameters are synonymous and if the TACL parameter was used previously, it does not need to be changed. The following shows what can be specified as values for the CONCDATA operand passed to the Creator process Tandem Computers Incorporated

37 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. NAME [ process-name ] specifies the name to be given to the new process. The file-system will assign a name to the process if either the keyword NAME is not specified or if the keyword NAME is specified without including process-name. INSPECT { ON OFF } turns the Inspect utility on or off. The default is ON. MEM memory-pages specifies the number of 1024-word memory pages to be allotted to the new process. The default value is 64. PARM (optional-startup-params) specifies optional APPLFILE startup parameters. PRI [ priority ] specifies the execution priority of the new process. The value specified for priority is an integer in the range 1 through 199. The default value is 150. The example below shows how to code the CONCDATA field so that the appropriate information is passed to the Creator process: CONCDATA "TACL CPU 1/2, NAME $TACL, PRI 155" In this example, a TACL process runs on CPU 1 with the backup process on CPU 2. It receives a process name of $TACL and runs at a priority of Tandem Computers Incorporated 2 7

38 Using LUNS Building the ESS Tables Logon Records for Pathway Processes The CONCDATA Operand (Pathway) 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 (#). With both command types (LOGON-CHAR and LOGON-INIT), you have the option of overriding the terminal protocol specified in the SCF ADD LU command. Note that you can do this only if the protocol specified through SCF is either CRT or ITI. Also note that you cannot override the terminal protocol through the ESS table if it has been specified as SNALU through SCF. For Pathway applications, specify CRT 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, CHARACTERSET, SNATYPE, and CONCDATA. For a description of these operands, see Logon Records for Tandem TACL Processes. It is the CONCDATA operand that allows you to specify a destination PATHMON and Pathway program. LUNS passes this information to the Tandem Creator process. The Tandem Creator process, in turn, communicates with the specified PATHMON to establish the LU-LU session. The following shows what can be specified as values for the CONCDATA operand which are passed to the Creator process. Note that you can specify only the following Pathway parameters. PATHWAY NAME [ \system-name. ] $pathmon-name, PROGRAM pathway-application-name [, PROCESS $process-name ] [, PRINTER name ] NAME [ \system-name. ] $pathmon-name specifies the name of a PATHMON. If the Pathway application resides on a remote system, you must name the PATHMON on that remote system and explicitly specify the system name. This is a required parameter. PROGRAM pathway-application-name specifies the Pathway application program. This is a required parameter. PROCESS process-name specifies the name of a running process for the Pathway application to open instead of SNAX/XF. The process specified in this parameter then opens the SNAX/XF process. The process name must be from one to five characters long, Tandem Computers Incorporated

39 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. PRINTER name specifies the name of a printer that may be accessed by the PRINT-SCREEN command in SCREEN COBOL. The value for name can be either a file name (fully qualified if on a remote system) or be specified as IS-ATTACHED if attached to the same controller. The example below shows how to code the CONCDATA field so that the appropriate information is passed to the Creator process. CONCDATA "PATHWAY NAME \SYS2.$PATHY, PROGRAM INVENTORY" In the example, a Pathway application residing on a remote system is started at a local terminal. PATHMON $PATHY on the remote system is used for the session; hence, the remote system name must also be specified. The initial SCOBOL program to run on the terminal is INVENTORY. Note LUNS closes any OPEN requests to Pathway that have not been used for 30 seconds. This is so that PATHMON does not have all of its allowed OPEN calls used up by multiple Creator processes Logon Records for Processes on a Host System (Passthrough) All logon records pointing to host processes must specify SENDHOST Y (yes). Within such records, you can designate a particular gateway line, PU, or LU for LUNS to use to establish the passthrough session. The relevant operands are GATELINE, GATEPU, and GATELU. These operands are mutually exclusive; if you specify one, you cannot specify either of the others. When gateway lines, PUs, and LUs reside on a local system and you do not specify any gateway parameter, LUNS will establish the session by using the first available gateway LU properly defined for passthrough and subordinate to the available gateway PU and line. A gateway LU is properly defined and available when it is active and the SCF PASSTHRU attribute is specified as ON and when it is not currently in-session, suspended, open, reserved for static passthrough in an ORDER record, or associated with another LU by means of the SCF ASSOCIATE attribute. Note that what you specify for the SCF MAXPTS attribute either on the secondary line or on its subordinate PU s can effect the availability of gateway LUs. For detailed information, see the MAXPTS attribute description in the SCF Reference Manual for SNAX/XF. When the gateway lines, PUs, and LUs reside on a remote system in an Expand network, you must always specify GATELINE, GATEPU, or GATELU explicitly and use the fully qualified name of the line, PU, or LU you choose for the session Tandem Computers Incorporated 2 9

40 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. Optional operands include RECSIZE, CHARACTERSET, and BINDENTRY. If specified, the BINDENTRY operand must name an entry in the host's LOGMODE table. SNAXUTL also allows you the option of specifying a USERDATA operand when the CMDTYPE is LOGON-INIT. With this operand, you can specify user data to be placed in the INIT-SELF built by LUNS. The value can be any string containing from 1 to 256 bytes; these bytes can be specified either as characters or as hexadecimal byte values. In instances where a data string requires more than one line, this operand can be represented using line continuation(s). When the CMDTYPE is LOGON-CHAR, the PLUNAME operand remains unused, and unless you specify otherwise, LUNS takes the character-coded command entered at the terminal (along with any other characters entered on the same line of the screen) and sends it to the host system for processing. If you want a different character-coded command to be sent to the host, you can include it in an operand called REPDATA. (Note that when the command name uses the single-byte Katakana character set, you must use REPDATA to send the charactercoded command by which the host knows the application.) Figure 2-1 shows how LUNS uses the logon record's REPDATA field Tandem Computers Incorporated

41 Using LUNS Building the ESS Tables Figure 2-1. LUNS Use of the REPDATA Field in Passthrough Host USS Table Record 4 A 3 Character-Coded Command: A Tandem ESS Table Record 1 2 CREDIT, LOGON CHAR, SENDHOST Y, REPDATA A After receiving the character-coded command CREDIT from a terminal, LUNS searches the ESS table and finds a corresponding command name field. LUNS then finds A in the REPDATA field. LUNS send the character-coded command "A" to the host. The host searches its USS table and finds A. 006 Other optional operands when the CMDTYPE is LOGON-CHAR include RECSIZE, and CHARACTERSET. All passthrough sessions established with CMDTYPE LOGON-CHAR impose special requirements for logging off. For these requirements, see the next subsection, Logoff Records for Logging Off All Processes. Note Use the SNAXUTL operand MUTLTIPLELOGON to establish passthrough sessions with CMDTYPE LOGON-CHAR. This avoids situations in which a previous unsuccessful logon attempt might prevent further logons by a given Tandem LU. For more information, see ADD ESSCMD in Appendix A, SNAX/XF Utility. When the CMDTYPE is INITSELF-RECEIVED, do not specify a PLUNAME. LUNS establishes the passthrough session by using the DLU name in the INIT-SELF command it receives from the terminal. (Note that this name must match the record's command-name field.) You can, however, use the PLUNAME operand to specify a different DLU name. Figure 2-2 shows how LUNS then processes the networkservices request Tandem Computers Incorporated 2 11

42 Using LUNS Building the ESS Tables Figure 2-2. LUNS Use of a Replacement DLU in Passthrough Host ESS Table Record INIT-SELF DLUname2 1 2 DLUname1, INITSELF-RECEIVED, SENDHOST Y, PLUNAME DLUname2 1 2 LUNS receives an INIT-SELF from the terminal; the DLU name within it (DLUname1) matches a command name field in the ESS table. 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. 007 Optional operands when CMDTYPE is INITSELF-RECEIVED include RECSIZE, CHARACTERSET, BINDENTRY, and USERDATA. As with CMDTYPE LOGON- INIT, the BINDENTRY operand here must point to an entry in the host's LOGMODE table. Note that when the terminal sends LUNS an INIT-SELF command, you can use the USERDATA operand to override what the INIT-SELF command specifies. The INIT-SELF command sent to the host contains what is specified by the ESS table. Note Although SNAXUTL does allow you to specify a terminal protocol in all passthrough logon records, LUNS does not use the protocol you specify. For passthrough sessions, the PROTOCOL operand is irrelevant. Logoff Records for Logging Off All Processes You can create within the ESS table a single, all-purpose logoff record that allows LUNS to log off terminals from a multiplicity of processes, regardless of whether these processes reside on the Tandem system or on the host. You can do this, however, only when LUNS has established these LU-LU sessions by using either: A logon record specifying CMDTYPE LOGON-INIT (for both passthrough and non-passthrough sessions), or A logon record specifying CMDTYPE LOGON-CHAR (for non-passthrough sessions only) Tandem Computers Incorporated

43 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. Consequently, a terminal user on the Tandem system must know and use the host's character-coded logoff command. However, if you choose to make the Tandem command the same as that on the host, the terminal user can enter the same sequence of characters when logging off, no matter how the session was established, and will thus remain completely unaware of any environment switch. Figure 2-3 shows the logoff sequence for a passthrough session that has been established with a logon record that specified CMDTYPE LOGON-CHAR. Figure 2-3. Logoff Sequence for Passthrough Sessions Where the Logon Record Specified LOGON-CHAR Host System LUNS Terminal "LOGOFF" "LOGOFF" UNBIND 008 With terminals that send SNA-formatted TERM-SELF commands, LUNS does not use the ESS table to process logoffs. Thus, for terminals that log on to applications through logon records specifying CMDTYPE INITSELF-RECEIVED, a logoff record is never needed. Order Records for Host SSCP-LU Sessions (Static Passthrough) To allow LUNS to establish and terminate a host SSCP-LU path, you must build two records in the ESS table. In each, you must designate a separate character-coded command for the command-name field and specify the CMDTYPE as ORDER. In the record LUNS uses to establish the path, you must specify STATIC ON. If the gateway lines, PUs, and LUs reside on a remote system within an Expand network, you must also specify either GATELINE, GATEPU, or GATELU, using the fully qualified name of the line, PU, or LU you choose for the session. If the host is not an AS/400 system you need only specify STATIC OFF in the record used to terminate the path Tandem Computers Incorporated 2 13

44 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. The gateway line resides on a remote system; hence GATELINE is specified, explicitly naming the remote system. Figure 2-4 also shows the contents of an order record (ENDIT) used for terminating a session with an AS/400 system Figure 2-4. Order Records in the ESS Table Record for Establishing a Static Path HOST, ORDER, GATELINE \TS.$L1, STATIC ON TANDEM, ORDER, STATIC OFF Record for Terminating a Static Path Record for Terminating a Session with an AS/400 Host ENDIT, ORDER, TERMSELF ON Tandem Computers Incorporated

45 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. You can name a user message whatever you wish, as long as its name does not duplicate that of a system message (for information on system messages, see Records for System Messages below). You place the message text itself in the MSGTEXT operand. This text, enclosed in quotation marks, can be from 1 to 4042 bytes long. Whenever the terminal user enters the name of a user message, that message is displayed on the screen. You can create as many such messages as you wish. Records for System Messages Tandem provides you with a number of system messages in an edit command file called $SYSTEM.SNAX.SYSMSG (for a list of these messages, see Appendix B). Before you run SNAXUTL, you can change the text of any system message by editing the command file. However, after you have made these messages part of an ESS table source file, you can change their text only in the following ways: 1. By purging the table source file and table object file and then running SNAXUTL with an edited version of the original command file 2. By creating and running another command file that uses the SNAXUTL DELETE and ADD commands to delete and add message records A system-message name must begin with the character S, followed by four numeric digits. LUNS displays system messages when an error occurs. The terminal user can also display any system message by entering its system-message name Tandem Computers Incorporated 2 15

46 Using LUNS Modifying ESS Tables Dynamically Modifying ESS Tables Dynamically SNAXUTL allows you to modify a currently active ESS table dynamically: that is, you 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. The example below shows a command file that adds a logon record for a Pathway application: BEGIN SELECTFILE $SYSTEM.TABLES.ESS1,TYPE ESS,DEACTIVATE Y ADD ESSCMD CRED, & CMDTYPE LOGON CHAR, & PLUNAME #CREATE, & PROTOCOL ITI, & CONCDATA "PATHWAY NAME $PATHX,PROGRAM CREDIT" END Deactivation and reactivation of ESS tables does not affect currently active LU-LU sessions. Thus, the table can be deactivated and activated while such sessions exist. However, when a terminal attempts a logon or logoff by means of a deactivated ESS table, it receives an error message and must wait until the table is once again activated. You can also use the DEACTIVATE operand of the SELECTFILE command when you wish to delete the table. To modify ESS tables dynamically, SNAXUTL must establish a connection with LUNS. Your SCF configuration file must therefore include an ADD APPL command that defines SNAXUTL to LUNS. In the ADD APPL command, always specify SNAXUTL both as the object and as the password. Note that the password value for this command must be a quoted string of up to eight characters. If eight characters are not used, the string must be blank-filled to the right. The example below shows the SCF ADD APPL command for defining SNAXUTL: ADD APPL $SSCP.#SNAXUTL, APPLTYPE LUNSAPPL, & PASSWORD "SNAXUTL " If you specify DEACTIVATE Y in a SNAXUTL SELECTFILE command without having added SNAXUTL as an SCF APPL, SNAXUTL returns Error 6420 (see Appendix E for a list and explanation of all SNAXUTL error messages) Tandem Computers Incorporated

47 Using LUNS Specifying the SET Table Specifying the SET Table The SET table identifies all ESS tables to LUNS by defining their table names and 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. Through the SETTAB parameter of the SCF ALTER SUBSYS $SSCP command To specify an active SET table before the SNAX/XF service manager has been started with SCF, you use the SYSGEN configuration modifier SETTABNAME. Within SETTABNAME, you must explicitly specify the rightmost (filename) portion of the SET table source-file name. SETTABNAME has no default value and cannot exceed a length of seven characters. The SET table must reside on the volume and subvolume from which SNAX/XF was loaded (for example, $SYSTEM.SYS01). It is on this volume and subvolume that LUNS looks for the currently active SET table, and it is from this volume and subvolume that LUNS derives the volume and subvolume portions of the SET table's fully qualified file name. If you specify SETTABNAME during system generation, and for some reason the service manager cannot access the SET table, a LUNS error message will be displayed on the system console and logged to the system-error log. Note that SNAX/XF will continue execution, but LUNS will not have been initialized and therefore will not be active. You can rectify this situation by specifying the correct SET table name through the SCF ALTER SUBSYS command: ALTER SUBSYS $SSCP,SETTAB $SYSTEM.SNAX.SET1 To replace one SET table with another dynamically, specify the fully qualified name of the new SET table source file in the SETTAB parameter of the SCF ALTER SUBSYS $SSCP command: ALTER SUBSYS $SSCP,SETTAB $SYSTEM.SNAX.NEWSET You can issue the ALTER command at any time after you start the service manager. Active sessions are not affected by this command and thus sessions need not be deactivated before you issue the command. Note also that when you specify the SET table through the SCF ALTER command, the table source file need not reside on any particular volume or subvolume Tandem Computers Incorporated 2 17

48 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. If you specify the DEFAULTTABLE Y operand, the ESS table becomes the default table for the system. Note Specifying SCF Configuration Parameters The ALTER Command The ADD APPL Command For both the ADD SETESS and ADD SETLOG commands: when you run SNAXUTL on a volume and subvolume different from the ones on which the table source file resides, the file name specified in the FILENAME operand must be fully qualified. Use SCF to: Define with an ADD APPL command those processes with which LUNS will communicate (the Tandem Creator process, SNAXUTL, and the Tandem TACL) Configure all lines, PUs, terminal LUs, and any gateway LUs Issue START commands to all lines, PUs, terminal LUs, and any gateway LUs Each of the object types listed APPL, LINE, PU, and LU has attributes that determine how LUNS operates. The following subsections discuss these attributes. The SCF ALTER command can be used to alter the attributes of any previously added SNAX/XF object. You can alter APPL attributes of the Creator process only if the Creator process has not issued an open to $SSCP. You can alter lines, PUs, and LUs only when those objects are in a stopped state. The following information on attributes of the SCF ADD APPL command also applies to the ALTER command. You must use the ADD APPL command to identify to LUNS all those processes on a Tandem system that must communicate directly with LUNS. This category includes the TACL process, the Creator process, and the SNAX Creator -2 process. If you want to take advantage of dynamic ESS table modification, you must also identify SNAXUTL to LUNS with an ADD APPL command. This subsection describes the required and optional attributes for APPL object representing the following: A TACL process A Creator process A SNAXUTL process The required and optional attributes for an APPL object representing the SNAX Creator-2 process are described in the SCF Reference Manual for SNAX/XF and in the SNAX Creator-2 Configuration and Control Manual Tandem Computers Incorporated

49 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. (In an ESS table logon record for TACL, the subdevice name is specified through the PLUNAME operand; for more information, see Logon Records for Tandem TACL Processes, earlier in this section). The following attributes, all of which are required, apply when an APPL object represents a TACL process: APPLTYPE { LUNSAPPL 5 } specifies the type of application program being defined. For an APPL object representing a TACL process, the valid values for APPLTYPE are LUNSAPPL or the integer value 5. APPLFILE file-name specifies the fully-qualified program file name of the TACL process being defined. For a Creator process to start up a TACL process, the Creator process must know the name of the file in which the application process object code resides. file-name can be in uppercase or lowercase characters. SNAX/XF converts them all to uppercase. Also note that SNAX/XF passes the same text string on to the Creator process and does not expand the file name. CREATOR #subdevice-name specifies the subdevice name of the Tandem Creator process that is to create the TACL process. Note that this attribute can be changed or removed with the ALTER APPL command. subdevice-name can consist of one through eight alphanumeric characters, the first of which must be a pound sign (#). There is no default value for this attribute. Below is an ADD APPL command defining a TACL process. ADD APPL $SSCP.#TACL, APPLTYPE LUNSAPPL, & APPLFILE $SYSTEM.SYSTEM.TACL & CREATOR #CREATE where $SSCP is the required name of the SNAX/XF service manager process Tandem Computers Incorporated 2 19

50 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. When the APPL object represents the Creator process, the following attribute is optional: PASSWORD "string" specifies a password that the Creator process must use when establishing a connection with LUNS. The value for this attribute is a quoted string of up to eight characters. If eight characters are not used, the user must right-fill the string with blank spaces, up to a total of eight characters. The string is case sensitive. There is no default value for the PASSWORD attribute. To change the value for PASSWORD, the application must be deleted using the DELETE command and then re-added. Here is an ADD APPL command defining a Creator process: ADD APPL $SSCP.#CREATE. APPLTYPE LUNSCRE, PASSWORD TARDIS $SSCP is the required name of the SNAX/XF service manager process. Note When the Creator process is used to create a TACL process, you must define an additional APPL object to represent that TACL process (see ADD APPL Command for a TACL Process ). You need not configure an APPL object to represent a Pathway process Tandem Computers Incorporated

51 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. The following attributes, both of which are required, apply when an APPL object represents SNAXUTL: APPLTYPE { LUNSAPPL 5 } For LUNS the valid values for APPLTYPE are LUNSAPPL and LUNSCRE. The integer value for LUNSAPPL is 5, and the integer value for LUNSCRE is 6. PASSWORD "string" specifies the password that SNAXUTL must use when establishing a connection with LUNS. The password must always specified as SNAXUTL. Here is an ADD APPL command defining SNAXUTL: ADD APPL $SSCP.#SNAXUTL, APPLTYPE LUNSAPPL, & PASSWORD "SNAXUTL " $SSCP is the required name of the SNAX/XF service manager process. The ABORT APPL Command You can use the ABORT APPL command to disconnect the Creator process from LUNS, as in the following example. Only the Creator process can be aborted. ABORT APPL $SSCP.#CREATE Tandem Computers Incorporated 2 21

52 Using LUNS The ADD LINE, PU, and LU Command Attributes The ADD LINE, PU, and LU Command Attributes AUTOLOGON Attribute When using SCF to configure lines, PUs, and LUs, you can specify several attributes in an ADD command that directly affect LUNS processing. 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. This record can be a logon command, an order command, or an ESS message. If the record entry contains a logon command, the LU is logged on to the system in the way specified by the command. However, if the record entry corresponds to an ESS message, the message is displayed at the terminal when the LU is started. The record cannot be an INITSELF-RECEIVED request. ADD LINE When the AUTOLOGON attribute is specified by the line object, the value for "esstable-entry-name" serves as a default value for all LUs subordinate to the line, with the following exception: ADD PU The default value is not propagated to those LUs that have an AUTOLOGON value specified by the LU object. When the AUTOLOGON attribute is specified by the PU object, "ess-table-entryname" serves as a default value for those LUs subordinated to that PU, with the following exception: ADD LU The default value is not propagated from the PU to those LUs that have an AUTOLOGON value specified by the LU object with an ADD LU command. When the AUTOLOGON attribute is specified by the LU object, "ess-table-entryname" overrides the value specified by the AUTOLOGON attribute in the line and the PU object. Switched Floating LUs The AUTOLOGON value is not propagated from the line, LU, or PU object to switched floating LUs. For switched floating LUs, the AUTOLOGON value must be specified with an ADD PU command (which propagates the value to the switched floating LU), or with an ADD LU command. Changing an LUs AUTOLOGON Value The AUTOLOGON value for existing LUs can be changed to specify a different record in the ESS table name with the ALTER LU command Tandem Computers Incorporated

53 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 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. If the attribute refers to an INITSELF-RECEIVED request, SNAX/XF issues the ESS system error S0049, and the request fails (see Appendix B for an explanation of these messages). ESSTABLE Attribute The syntax for the ESSTABLE attribute is as follows: ESSTABLE ess-table-name When the LU (terminal) sends an SNA character-coded command or INIT-SELF command, SNAX/XF uses the ess-table-name value to search for the ESS table that should be associated with the LU. ess-table-name must be the name of an existing ESS record in the current LUNS SET table. ADD LINE When the ESSTABLE attribute is specified by the line object, ess-table-name serves as a default value for all LUs subordinate to the line, with the following exception: ADD PU The value is not propagated to those LUs that have an ESSTABLE value specified by the LU object. When the ESSTABLE attribute is specified by the PU object, ess-table-name serves as a default value for those LUs subordinated to that PU, with the following exception: ADD LU The default value is not propagated from the PU to those LUs that have an ESSTABLE value specified be the LU object with an ADD LU command. When the ESSTABLE attribute is specified at the LU level, the ess-table-name overrides any value specified by the ESSTABLE attribute in the line or the PU object. Switched Floating LUs The default value is not propagated from the line, LU, or PU object to switched floating LUs. For switched floating LUs, the ESSTABLE value must be specified with an ADD PU command (which propagates the value to the switched floating LU), or with an ADD LU command. Note that if the ESSTABLE attribute is not specified for switched floating LUs, the default value for the switched floating LUs is OFF Tandem Computers Incorporated 2 23

54 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. Note If the ESSTABLE attribute is not specified for a line, PU, or LU, and a valid ESS table entry exists in the SET table (it must be designated with the SNAXUTL ADD SETESS command as a default table), then that ESS table becomes the table used by the LU. NOACQ Attribute The syntax for the NOACQ attribute is as follows: NOACQ { ON OFF } The value for NOACQ specifies whether an application program (PLU) can acquire a terminal LU (SLU) that is subordinated to the line. NOACQ ON indicates that SNAX/XF rejects any attempt to acquire this terminal LU: that is, the service manager rejects any unsolicited open of an LU from a Tandem process or any unsolicited BIND request from a host process. ADD LINE When the NOACQ attribute is specified by the line object, the value serves as a default value for LUs on the line, with the following exception: ADD PU The value is not propagated to those LUs that have NOACQ specified at the LU level with an ADD LU command. When the NOACQ attribute is specified at the PU level, the value serves as a default value for all LUs subordinated to that PU, with the following exception: ADD LU The value is not propagated to those LUs that have NOACQ specified at the LU level with an ADD LU command. When the NOACQ attribute is specified at the LU level, the value overrides any value specified by the NOACQ attribute for the line or PU. Switched Floating LUs The default value is not propagated from the line to switched floating LUs. For switched floating LUs, the NOACQ value must be specified with an ADD PU command (which propagates the value to the switched floating LUs), or with an ADD LU command Tandem Computers Incorporated

55 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. Do not use the NOACQ attribute for LUs that use Pathway. ESS LU Attributes That Override SCF LU Attributes BINDENTRY Attribute The following SCF attributes specify certain conditions for an LU that are also specified by entries in an ESS table. If what you specify with SCF for these attributes differs from what is specified in the ESS table, LUNS uses the values specified in the ESS table. That is, LUNS will use the ESS table values to set up the session, and these values remain in effect for the duration of the session. The syntax for the BINDENTRY attribute is as follows: BINDENTRY "bind-table-entry-name" "bind-table-entry-name" specifies the record name of a BIND image used by this LU found in either a host LOGMODE table or in a BIND table created using SNAXUTL. If the BINDENTRY 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 BINDENTRY value of the superior object as a default unless it is overridden by a BINDENTRY value specified in an ADD or ALTER LU command for the LU. For switched floating LUs, the BINDENTRY value must be specified in an ADD $SSCP or ALTER $SSCP LU command. The BINDENTRY name can contain from one through eight alphanumeric or special characters ($, #, Note that BINDENTRY names can be specified in uppercase or lowercase letters; SNAX/XF converts all lowercase letters to uppercase. BINDTABLE Attribute The syntax for the BINDTABLE attribute is as follows: BINDTABLE "bind-table-name" "bind-table-name" specifies the name of a BIND table that has been created using SNAXUTL (see SELECTFILE in Appendix A). The BIND table contains the BIND image specified with a BINDENTRY attribute for a primary line and its subordinate objects Tandem Computers Incorporated 2 25

56 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 ($, #, Note that BINDTABLE names can be specified in uppercase or lowercase letters; SNAX/XF converts all lowercase letters to uppercase. CHARACTERSET Attribute The syntax for the CHARACTERSET attribute is as follows: CHARACTERSET { ASCII EBCDIC KATAKANA } This attribute specifies whether SNAX/XF is to perform character translation for the specified LU. The following are valid values for this attribute when specified on an ADD LU command: ASCII EBCDIC KATAKANA specifies that no translation is to take place. This implies that characters are in ASCII format. specifies that translation from ASCII to EBCDIC is to take place. That is, EBCDIC turns translation on so that all data sent from the terminal to a Tandem application will be translated from EBCDIC to ASCII and all data sent from a Tandem application to the terminal is translated from ASCII to EBCDIC. specifies that translation from EBCDIC Katakana to Tandem Katakana is to take place. Note that the value KATAKANA can be specified for the LU only. It cannot be specified in an ADD or ALTER command issued to the PU or LINE object. For LUs permanently subordinated to a line, the CHARACTERSET attribute specified for the line (ASCII or EBCDIC) is used as a default value for the LUs if no CHARACTERSET attribute was specified on an ADD or ALTER LU command. For switched floating LUs, the CHARACTERSET attribute must be specified in an ADD or ALTER LU command for the switched floating LU Tandem Computers Incorporated

57 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. The different protocols that can be specified are as follows: CRT ITI specifies that this LU uses the standard 3270 full-screen block protocol. An application that communicates with this LU must define and expect to receive 3270 data streams that contain screenformatting control characters. specifies that the device expects to converse with Tandem applications using the standard 3270 conversational (line-at-a-time) mode. RECSIZE Attribute The syntax for the RECSIZE attribute is as follows: RECSIZE integer This attribute specifies the length, in bytes, of a terminal or printer line, CRT screen, or RU, depending on the PROTOCOL attribute. The following PROTOCOL dependencies apply: If the PROTOCOL attribute specifies CRT, the RECSIZE attribute specifies the CRT screen or printer buffer size. If the PROTOCOL attribute specifies PRT, the RECSIZE attribute specifies the printer line length plus 5 bytes. If the PROTOCOL attribute specifies ITI, the RECSIZE attribute specifies the terminal line length plus 16 bytes. If the PROTOCOL attribute specifies SNALU, the definition of RECSIZE is in addition to SNALU according to the following guidelines: For LUs subordinate to a primary line, RECSIZE specifies the SNA RU length. For LUs subordinate to a secondary line, RECSIZE specifies the SNA RU length if byte 11 of the SNA BIND request is 0. If byte 11 is not 0, the value of RECSIZE is ignored. The valid range for RECSIZE is from 1 to 4096 bytes. The default value for RECSIZE is 1024 bytes Tandem Computers Incorporated 2 27

58 Using LUNS SCF Attribute Summary SCF Attribute Summary Table 2-1 shows those SCF attributes relevant to LUNS and maps them to the appropriate object types. Table 2-1. How SCF Attributes Relate to LUNS SCF Attribute APPL LU PU LINE ESS Table APPLFILE X APPLTYPE X AUTOLOGON X D1 D2 BINDENTRY X D1 D2 O BINDTABLE X D1 D2 O CHARACTERSET X D1 O CREATOR X ESSTABLE X D1 D2 NOACQ X D1 D2 PASSWORD X PROTOCOL X O RECSIZE X O TYPE (14,x) X SNATYPE x KEY: X Applicable SCF object D1 D2 O SNATYPE x First-level LU default value if not specified for any LU subordinate to the PU or line Second-level LU default value if not specified for any LU or PU subordinate to the line Overrides an LU s SCF specification for the duration of an LU-LU session created by an ESS table record Overrides an LU s SCF type specification of the LU s IBM SLU Type (14,x) for the duration of an LU-LU session created by an ESS table record Tandem Computers Incorporated

59 Using LUNS Using the Tandem Creator Process Using the Tandem Creator Process Startup Security Issues For any non-pathway application that uses LUNS, perform the following SCF 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. The APPLFILE attribute, which must contain the name of the object file where the application can be found For Pathway applications that use LUNS, you need only define the Tandem Creator process. Pathway applications are not defined to LUNS through SCF ADD APPL commands. The Creator process can: Be created by a high-pin process; however, the Creator process cannot create a high-pin process. Communicate with a high-pin server. Run at a high PIN; however, the Creator process defaults to run at a low PIN. Recognize remote eight-character device, volume, and file names (including the $ character). Recognize remote six-character process names (including the $ character). Recognize variable-length string file names. Provide increased functionality for users who log onto a Pathway application. The Creator process allows a user to pass along to Pathway the name of a printer that the SCREEN COBOL program can access using the PRINT-SCREEN command. The printer name can be a file name. If the printer is locally attached to the user s terminal, use the printer name IS-ATTACHED. Any application invoked by the Creator process runs with the following process accessor ID (PAID): If the PROGID option in the object file is specified in the FUP SECURE command, the application has the PAID of the owner of the object file. If the PROGID option in the object file is not specified, the application will have the same PAID as the Creator process. Note If the Creator process is run with the super user ID (255,255), it is suggested that the PROGID option be specified for any application that the Creator process starts Tandem Computers Incorporated 2 29

60 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. [RUN] CREATOR [ /OUT filename, NAME $process-name/ ]; CREATOR #subdevice-name [, MAXPATHMONOPENS Pathway requests ] [, MAXSESSIONS number ] [, PASSWORD password ] [, STATUSOFF ] OUT filename 1. specifies the name of an unstructured and unnumbered LOG file, a SPOOLER file name, or a terminal. If the OUT parameter is not specified, messages are sent to the home terminal of the Creator process. If the OUT file cannot be accessed upon Creator process startup, the Creator process: 1. logs a Log file inaccessible message to the home terminal and to $0 2. logs a Creator terminating message to the home terminal 3. stops If the OUT file is a terminal with an outstanding READ procedure, the Creator process suspends until the message can be written. NAME $process-name designates the symbolic name you are assigning to the Creator process. If you are running the Creator process as NonStop process pair, you must specify this run option Tandem Computers Incorporated

61 Using LUNS Using the Tandem Creator Process CREATOR #subdevice-name specifies the subdevice name of the Tandem Creator process. Note that the name specified here must match: The subdevice name specified in the ADD APPL command that defines the Creator process The subdevice name specified in the CREATOR attribute of the ADD APPL command for the TACL For Pathway applications, the PLUNAME specified in an ESS table entry for a Pathway logon record MAXPATHMONOPENS Pathway-requests specifies the maximum number of outstanding requests to Pathway requests that the Creator process will allow. When this limit is reached, the Creator process does not accept any more requests until Pathway completes at least one of the outstanding requests. Any value within the range 0 through 99 can be specified. Specifying a value of 0 stops any Pathway access. The default value is 50. MAXSESSIONS number specifies the number of Creator-SSCP or Creator-Pathway sessions to support. The value for number can be from 1 to The default value is 400. PASSWORD password specifies the name of the password the Creator process uses when it establishes its connection with LUNS. The password name specified must match the one specified in the SCF ADD APPL command for the Creator process. password is case-sensitive. Use of quotation marks surrounding the value specified for password is optional. STATUSOFF suppresses the logging of valid LOGON and LOGOFF messages. Note Before a request can be made to start any Pathway applications, the system operator or user must configure those applications for the Pathway environment Tandem Computers Incorporated 2 31

62 Using LUNS Using the Tandem Creator Process (This page left intentionally blank) Tandem Computers Incorporated

63 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. The second part illustrates the addition of a remote Tandem system, connected to the first by an Expand link. On this second system resides another application, which terminals on both systems can access through LUNS. All SNAXUTL and SCF commands needed to implement this example are shown. Creating the Basic Configuration Figure 3-1 illustrates the first part of the example. The figure shows an SNA host linked to a Tandem system (\SYS1). Residing on the host is the application TSO. Residing on \SYS1 are the TACL application, a Pathway application called Order Entry, a PATHMON process called $PATHX, and the Tandem Creator process. SCF is used to configure two gateway LUs (LU1 and LU2). These LUs enable LUNS to establish both static and nonstatic passthrough sessions for the two 3278 terminals (LU3 and LU4) attached to \SYS1. Figure 3-1. Application Example, Part 1 Application: TSO Host $G1 Application: ORDER ENTRY TACL Also: CREATOR $PATHX SNAXUTL PU1 LU1 LU2 \SYS1 $P2 PU2 LU3 LU Tandem Computers Incorporated 3 1

64 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. Terminal LUs will initiate all sessions by means of character-coded commands. Therefore, for this example, they can log on to: The TACL process on \SYS1 with the command TACL The Order Entry process on \SYS1 with the command ORDERENTRY The TSO process on the host system with the command TSO For the Order Entry application, LUNS will use the protocol assigned in the ESS table logon record named ORDERENTRY. For this example, the protocol is CRT. Because both terminals will be given the appropriate protocol (ITI) for the TACL application by means of the SCF ADD LU command, it is not necessary to specify a protocol for the TACL process. Because TSO is a host program accessed by means of passthrough, it is not necessary to specify a protocol in this case either. The ESS table will contain a record whose command-name field is the charactercoded command LOGOFF. This command will allow the terminal user to log off from Order Entry and TSO (and the Inventory application when it is added in the second part of the example). The TACL will be associated, through SCF, with the Tandem Creator process. Order Entry s logon record will contain the subdevice name of the Tandem Creator process in its PLUNAME field. The logon records for both processes will contain a CONCDATA field specifying startup parameters. The Creator process uses these parameters when it creates the TACL and when it interfaces with the PATHMON $PATHX to log on LU3 and LU4 to Order Entry. Terminals will receive all Tandem ESS messages. All host USS messages will be presented to a terminal when it is in session with TSO. Terminal users will be able to establish a static passthrough path with the host system by entering the HOST command. They will thereby receive the host s USS message 10. They can return to the Tandem system and receive ESS message 10 by entering the TANDEM command Tandem Computers Incorporated

65 Application Example Creating the Basic Configuration Configuration Assumptions Creating a Command File for SNAXUTL 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. The second part of the application example shows how to do this; see Using SCF to ADD the New Application and LU to \SYS2. ) Only one ESS table will be created. It will have the table name ESS1 and will not be flagged as the default table. SCF ADD APPL commands will define the TACL application, the Tandem Creator process, and SNAXUTL to LUNS, giving these processes subdevice names of #TACL, #CREATE, and #SNAXUTL, respectively. Note that the inclusion of an ADD APPL command for SNAXUTL allows for the dynamic modification of the ESS table. (In the second part of this application example, ESS1 will be modified dynamically; see Updating the ESS Table on \SYS1. ) TSO, and the Pathway application, Order Entry, need not be defined by an ADD APPL statement. Because ESS1 is not a default table, it must be associated with each terminal individually. This is done through the ESSTABLE attribute of the SCF ADD LU command that defines each terminal LU. (Also see Performance Considerations ESS Table Allocation in this section.) Gateway LUs (LU1 and LU2) will have the SCF attribute PASSTHRU ON, but not STATIC ON or ASSOCIATE. In the following edit command file, SNAXUTL commands add: Logon and logoff records in the ESS table A user message record (a HELP menu) in the ESS table A record in the SET table that identifies the ESS table Note that the ESS table is created first. Because a new table is being created, the ALLOCATE command is used Tandem Computers Incorporated 3 3

66 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.$G1 ADD ESSCMD LOGOFF, & CMDTYPE LOGOFF ADD ESSCMD HOST, & CMDTYPE ORDER, & STATIC ON, & GATELINE \SYS1.$G1 ADD ESSCMD TANDEM, & CMDTYPE ORDER, & STATIC OFF ADD ESSMSG HELP, & MSGTEXT (" ", & %H85," PU: ", & %H85," LU: ", & %H85," TO ACCESS ENTER ", & %H85," ", & %H85," TACL TACL ", & %H85," ORDER ENTRY ORDERENTRY ", & %H85," TSO TSO ", & %H85," HOST HOST ", & %H85," TANDEM TANDEM ", & %H85," ", & %H85," TO LOGOFF LOGOFF ") END Tandem Computers Incorporated

67 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. Note also that the New Line control characters are coded in ASCII-hexadecimal format (%H85), rather than in EBCDIC-hexadecimal format (%H15). The characters must be ASCII-hexadecimal because the Tandem service manager translates the entire message from ASCII to EBCDIC automatically. The HELP message also includes @@PUNAME, and@@luname. Inclusion of these keywords in any part of an ESS message results in the display of the Tandem node name, the line name, the PU name, and the terminal LU name respectively. Thus, for LU3, the top portion of the HELP message would display the following: PU: \SYS1.$P2.#PU2 LU: \SYS1.$P2.#LU3 Now that the commands that build the ESS table have been coded, a record for that ESS table must be added to the SET table. This record assigns a name to the ESS table and thereby identifies it to LUNS. It also specifies the name of the file where LUNS can access the table information. BEGIN SELECTFILE $SYSTEM.SYS01.SNXSET, TYPE SET END ADD SETESS ESS1, & FILENAME $SYSTEM.SNAX.ESSTAB1 It is assumed that the SET table referenced through the SELECTFILE command is the starter SET table source file; hence an ALLOCATE command is not included. It is also assumed that the SET table name was specified during stem generation. Thus, the referenced SET table source file resides on the volume and subvolume from which SNAX/XF was cold-loaded. The second part of this application example shows you how to build your own SET table and specify its name through the SETTAB parameter of the ADD/ALTER SUBSYS $SSCP command Tandem Computers Incorporated 3 5

68 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.SNXSET The ADD APPL command is used to assign subdevice names to the Tandem Creator process, the TACL application, and SNAXUTL on \SYS1. The TACL process (#TACL) is associated with the Tandem Creator process through the CREATOR attribute; the APPLFILE attribute is also specified so that the Creator process can locate the object file of the TACL. ADD APPL $SSCP.#CREATE, APPLTYPE LUNSCRE, & PASSWORD "SYZYGY " ADD APPL $SSCP.#TACL, APPLTYPE LUNSAPPL, & APPLFILE $SYSTEM.SYSTEM.TACL, & CREATOR #CREATE ADD APPL $SSCP.#SNAXUTL, APPLTYPE LUNSAPPL, & PASSWORD "SNAXUTL " Note that the Creator process is given the password SYZYGY and SNAXUTL the password SNAXUTL. Remember that the password must be right-filled with blank spaces, up to its total of eight characters. Next, the gateway passthrough logical units are configured. The ADD LINE command is used to define the gateway line ($G1). Then the ADD PU command is used to define the gateway physical unit (PU1). Finally, the ADD LU command is used to define the two gateway LUs (LU1 and LU2): ADD LINE $G1, STATION SECONDARY ADD PU $G1.#PU1, TYPE (13,2),RECSIZE 265,MAXLUS 2, & MAXPTS 2, ADDRESS %HC1 ADD LU $G1.#LU1, TYPE (14,0),PUNAME #PU1,RECSIZE 1024, & PROTOCOL SNALU,PASSTHRU ON,ADDRESS 2 ADD LU $G1.#LU2, TYPE (14,0),PUNAME #PU1,RECSIZE 1024, & PROTOCOL SNALU,PASSTHRU ON,ADDRESS 3 Then the primary line ($P2) and its attached PU and LUs are configured. When the two terminal LUs (LU3 and LU4) are configured, PROTOCOL is specified as ITI. PROTOCOL is a required SCF attribute for any LU. Note, however, that this protocol specified through SCF can be overridden by the protocols specified in the ESS table logon records Tandem Computers Incorporated

69 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, CHARACTERSET EBCDIC, STATION PRIMARY ADD PU $P2.#PU2, TYPE (13,2),RECSIZE 265, & MAXLUS 2,ADDRESS %HC8 ADD LU $P2.#LU3, TYPE (14,2),PUNAME #PU2,RECSIZE 1024, & PROTOCOL ITI,ADDRESS 2,DEVTYPE "3278-2", & ESSTABLE ESS1 ADD LU $P2.#LU4, TYPE (14,2),PUNAME #PU2,RECSIZE 1024, & PROTOCOL ITI,ADDRESS 3,DEVTYPE "3278-2", & ESSTABLE ESS1 Note that CHARACTERSET EBCDIC is specified for the line; this turns translation on for the attached terminal LUs because they do not have CHARACTERSET specified as an LU attribute. Finally, the START command is used to start all lines, PUs, and LUs: START LINE $G1 START PU $G1.#PU1 START LU $G1.#LU1 START LU $G1.#LU2 START LINE $P2 START PU $P2.#PU2 START LU $P2.#LU3 START LU $P2.#LU4 Note that before the host SSCP and TSO application can be accessed, the corresponding objects for LU3 and LU4 must also be started on the host side. Starting the Tandem Creator Process For Tandem applications to use LUNS services, the Creator process must be started. Because a password is required for the Creator process, it must be included as part of the RUN command.: 1> RUN CREATOR /OUT $S.#SPOOL, CPU 1, NAME $CRT, NOWAIT/ 2 ; & CREATOR #CREATE, PASSWORD "SYZYGY " Note that this password was previously specified in the SCF ADD APPL command for the Creator process. The password in the RUN command must match the one specified in the ADD APPL command Tandem Computers Incorporated 3 7

70 Application Example Adding an Application and Terminal to a Second System Adding an Application and Terminal to a Second System In this, the second part of the example, a Pathway application process and a terminal LU, both residing on a second Tandem system, are added to the configuration. As 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. The new Pathway process residing on \SYS2 is called INVENTORY, and the new terminal is designated LU5. This portion of the example is implemented through the following operations: 1. SNAXUTL is used to create an ESS table on \SYS2. 2. An active SET table is created for \SYS2 through the following operations: a. SNAXUTL is used to allocate space for the table and to place within it a record for the new ESS table. b. The SCF ALTER SUBSYS $SSCP command is used to designate it as the active SET table for \SYS2. 3. SCF is used on \SYS2 to: a. ADD LU5 b. ADD the Tandem Creator process as an APPL c. ADD SNAXUTL as an APPL on \SYS2 4. SNAXUTL is used to update the ESS table on \SYS Tandem Computers Incorporated

71 Application Example Adding an Application and Terminal to a Second System Figure 3-2. Application Example, Part 2 Application: TSO Host $G1 Application: ORDER ENTRY TACL PU1 \SYS1 PU2 Also: CREATOR $PATHX SNAXUTL LU1 LU2 LUNS $P2 LU3 LU4 EXPAND Link Application: INVENTORY \SYS2 PU3 Also: CREATOR $PATHY SNAXUTL LUNS $P3 LU Tandem Computers Incorporated 3 9

72 Application Example Adding an Application and Terminal to a Second System Operational Assumptions Configuration 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. When LU5 is started through SCF, it is automatically logged on to the Inventory program. LU3 and LU4 can log off from the Inventory program (just as they can from Order Entry or TSO) and log on to another process. If LU5 logs off, it can log back on only to the Inventory program. LU5 will receive all Tandem ESS messages. The following assumptions are made about configuration: $SSCP has been started on \SYS2, but no SET table has been built or made active. Thus, although SNAX/XF is running, it has not yet initialized the LUNS component of $SSCP. Consequently, a SET table is built using SNAXUTL and specified as active through the SETTAB attribute of the SCF ALTER SUBSYS $SSCP command. One ESS table, named ESS2, is created on \SYS2. Like its counterpart on \SYS1, it will not be flagged as a default table. No protocol will be specified in this table; the terminal will therefore use the protocol specified through SCF, which is CRT. The SCF ADD APPL command is used to give a subdevice name to the Tandem Creator process running on \SYS2. This subdevice name is also placed in the PLUNAME field of Inventory s ESS table logon record, thus associating the application with the Tandem Creator process. ESS1 (the ESS table on \SYS1) is then updated so that it has both a logon record for the Inventory program and an addition to the HELP menu telling the terminal operator how to log on to this new process. Because ESS2 is not a default table, it must be associated with LU5 by means of the ESSTABLE attribute of the SCF ADD LU command. This command also specifies AUTOLOGON INVENTORY so that the terminal is logged on to the Inventory process automatically Tandem Computers Incorporated

73 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. Note also that the necessary Pathway parameters have been included in the CONCDATA field. BEGIN SELECTFILE $SYSTEM.SNAX.ESSTAB2, TYPE ESS ALLOCATE 10 ADD ESSCMD INVENTORY, & CMDTYPE LOGON-CHAR, & PLUNAME #CREATE, & CONCDATA ("PATHWAY NAME $PATHY,", & "PROGRAM INVENTORY") ADD ESSCMD LOGOFF, & CMDTYPE LOGOFF END Next, the SET table for \SYS2 is built. This table includes a record for ESS2. Because it is a new table that is being built, the command block includes an ALLOCATE command. BEGIN SELECTFILE $SYSTEM.SNAX.SNXSET2, TYPE SET ALLOCATE 10 ADD SETESS ESS2, & FILENAME $SYSTEM.SNAX.ESSTAB2 END This SET table is specified as the active one through SCF rather than through SYSGEN; therefore the file does not need to reside on the volume and subvolume from which SNAX/XF was loaded Tandem Computers Incorporated 3 11

74 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. (Although this application example does not show the dynamic modification of ESS2, SNAXUTL is nevertheless added as an APPL object on \SYS2; this is done because the capacity to modify ESS tables dynamically should exist on any system that uses LUNS.) Next, the primary line ($P3) is added, along with the PU subordinate to it (#PU3). When the terminal LU (#LU5) is added, the ADD command specifies PROTOCOL CRT. The ADD command also specifies AUTOLOGON INVENTORY so that the terminal is automatically logged on to the Inventory process when the LU is started. Note that the AUTOLOGON operand specifies the name of a logon record in the ESS table. Note also that the Tandem Creator process must be started before the automatic logon can take place. Because there is no default ESS table for \SYS2, ESS2 is specified as an LU attribute. ALTER SUBSYS $SSCP,SETTAB $SYSTEM.SNAX.SNXSET2 ADD APPL $SSCP.#CREATE, APPLTYPE LUNSCRE, & PASSWORD "TARDIS " ADD APPL $SSCP.#SNAXUTL, APPLTYPE LUNSAPPL, & PASSWORD "SNAXUTL " ADD LINE $P3, CHARACTERSET EBCDIC, & ADD PU $P3.#PU3, TYPE (13,2),RECSIZE 265, & MAXLUS 1,ADDRESS %HC8 ADD LU $P3.#LU5, TYPE (14,2),PUNAME #PU3, & RECSIZE 1024,PROTOCOL CRT, & DEVTYPE "3278-2",ESSTABLE ESS2, & AUTOLOGON "INVENTORY" SCF can now be used to start the line, the PU, and the LU. START LINE $P3 START PU $P3.#PU3 START LU $P3.#LU Tandem Computers Incorporated

75 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. Updating the ESS Table on \SYS1 To enable LU3 and LU4 to log on to the Inventory process, a logon record for this application process must be added to the ESS table on \SYS1. This logon record contains within its PLUNAME field the name of the Tandem Creator process on \SYS1. It is this Creator process that will communicate with the PATHMON process on \SYS2 and pass it the Pathway name of the application. The Pathway application name is placed in the logon record s CONCDATA field. Because the application resides on a remote system, that remote system must be explicitly named in the PATHMON specification (\SYS2.$PATHY). PROTOCOL CRT must also be specified to override the ITI protocol specified through SCF for LU3 and LU4. Otherwise, the two terminals would not be able to access the Inventory process, which uses CRT. For the terminal user s convenience, the HELP menu on \SYS1 will be modified to reflect the existence of the new process; this requires deleting the old HELP menu and defining a new one. Note that the ESS table is modified dynamically through use of the DEACTIVATE operand of SNAXUTL. Because it is an existing table, the ALLOCATE command is omitted Tandem Computers Incorporated 3 13

76 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 HELP, & MSGTEXT (" ", & %H85," PU:@@NDNAME.@@LNNAME.@@PUNAME ", & %H85," LU:@@NDNAME.@@LNNAME.@@LUNAME ", & %H85," TO ACCESS ENTER ", & %H85," ", & %H85," TACL TACL ", & %H85," ORDER ENTRY OE ", & %H85," TSO TSO ", & %H85," INVENTORY INVENTORY ", & %H85," HOST HOST ", & %H85," TANDEM TANDEM ", & %H85," ", & %H85," TO LOGOFF LOGOFF ") END ESS Table Allocation and Performance When an ESS table is needed for an LU during session establishment (SSCP LU, or LU LU) or session termination (LU-LU), LUNS retrieves the table from a diskresident file. ESS tables are cached in extended segments in $SSCP address space. By default, as many as 10 ESS tables may be resident at any given time (one in each of ten different segments). If your configuration requires more than this default number, use the SYSGEN attribute NUMSEGIDS to increase the number of available extended segments to as many as 100. (For more information on the NUMSEGIDS attribute of the SNAX/XF service manager, see the System Generation Manual for SNAX/XF.) If a non-resident ESS table is needed and all available segments are already allocated, the least frequently used segment is deallocated and a new segment is allocated for the new ESS table. Actions such as these require a significant amount of time, because the old file must be closed and the new one must be opened and read in. Therefore, a system configured in such as way as to require a large number of ESS table allocations and/or deallocation (multiple session establishments and/or termination requests) in a short period of time can cause system performance to degrade ($SSCP slows down) Tandem Computers Incorporated

77 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. For this example, most of the ESS tables can be eliminated by specifying the ASSOCIATE attribute with the SCF ADD command for the gateway LU, and specifying a generic ESS table (SCF) for a group of LUs. The example below shows an initial configuration, followed by an example reconfiguration used to decrease the number of ESS tables required for the same number of LUs. Original Configuration Example First, the SCF configuration for secondary objects (gateway to host) and primary objects (connected to terminal): Secondary objects: LINE $ABC123 PU #PU001 LU #T01234, PASSTHRU ON LU #T05678, PASSTHRU ON Primary objects: LINE $DEF456 PU #PU002 LU #T01234, ESSTABLE T01234 LU #T05678, ESSTABLE T05678 The values specified for ESSTABLE T01234 and ESSTABLE T05678 are identical, except for the GATELU specification. The following SNAXUTL commands show how they are configured. For T01234: ADD ESSCMD LOGON, CMDTYPE LOGON-CHAR, SENDHOST Y, GATELU $ABC123.#T01234 and for T05678: ADD ESSCMD LOGON, CMDTYPE LOGON-CHAR, SENDHOST Y, GATELU $ABC123.#T Tandem Computers Incorporated 3 15

78 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 $ABC123 PU #PU001 LU #T01234, PASSTHRU ON, ASSOCIATE $DEF456.#T01234 LU #T05678, PASSTHRU ON, ASSOCIATE $DEF456.#T05678 Primary objects: LINE $DEF456 PU #PU002 LU #T01234, ESSTABLE ESS1 LU #T05678, ESSTABLE ESS1 ESS1 is the generic ESS table with the following values as specified through SNAXUTL: ADD ESSCMD LOGON, CMDTYPE LOGON-CHAR, SENDHOST Y Tandem Computers Incorporated

79 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. Within each command block, a SELECTFILE command specifies the name of a key-sequenced table source file. If the source file doesn t exist, the ALLOCATE command is required. When you run SNAXUTL, each command block serves as input to a given table source file. The table source file, in turn, serves as input to a table object file, which LUNS actually uses to perform services. This object file contains the same information as the table source file, only in unstructured format. It is also given the same name as the table source file, except that the letter O is appended as a final character. Because the table object file is automatically created or updated along with the table source file, you need not concern yourself with it. You must, however, make certain that your installation does not inadvertently delete any table object files. Any time you run SNAXUTL, a listing file is produced. This listing file contains a copy of the input commands and status messages resulting from command processing. This file is specified as the OUT file at run time (see Invoking the Program in this section). SNAXUTL Command Syntax This subsection presents the formal syntax of all SNAXUTL commands. For an example of how to use these commands to create tables for a specific configuration, see Section 3, Application Example Tandem Computers Incorporated A 1

80 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. opdata is any relevant alphanumeric and special-character string, byte value, or bit string of arbitrary length. A Tandem Computers Incorporated

81 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. In the absence of continuation lines, a new line is assumed to signify the start of a new command. SNAXUTL ignores blank lines between commands. Operands All operands have an operand name (or keyword) defined by Tandem. Such names can be followed by operand data. Operand data can be any string of characters that does not contain a blank or comma. The characters can represent either a string of alphanumeric and special characters or a numeric value, depending on the context of the operand. If blanks or commas are to be included in a string of alphanumeric and special characters, the entire string must be enclosed in single ( ) or double ( ) quotation marks. When a single quotation mark is part of the content of such a string, double quotation marks must be used to delimit the string. There are two types of numerical values that must be represented by hexadecimal numbers: byte values and bit strings of arbitrary length. Byte values must be expressed in byte units, with each unit separated from the others by a comma: %HC1, %HC2, %HC3 Each unit can express a value ranging from %H00 to %HFF (0 to 255). Note that byte values can be entered as data within the REPDATA and USERDATA operands of the ADD ESSCMD, or as New Line control characters within the MSGTEXT operand of the ADD ESSMSG command Tandem Computers Incorporated A 3

82 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. Examples of other operand data formats are: (1) CMDTYPE LOGOFF operand data operand name (2) MSGTEXT "save these blanks and commas,,," operand data operand name Some operands support operand data strings that can be several hundred bytes long. Such strings will necessarily exceed the command line and can extend over several lines. You can express this kind of operand data using line continuations, which must obey the following rules: 1. Operand data must be enclosed by parentheses. 2. All lines that are to be continued must be delimited by a comma followed by an ampersand (&). Below is an example of how to use line continuations: operand ( "This is an alphanumeric string ", & "followed by byte data", & %HC1, %HC2, %HFF,! HEXADECIMAL DATA! & "More string data here" ) A Tandem Computers Incorporated

83 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. Note that when the line of code you are commenting is continued on the next line, the comment must be terminated by an exclamation point if that comment is interposed between the code line s final comma and the ampersand. Examples of valid comment lines are: DELETE MSG20! THIS IS A COMMENT ADD ESSCMD TACL, &! ANOTHER COMMENT CMDTYPE LOGON-CHAR ADD ESSCMD TSO,! AND YET ANOTHER! & CMDTYPE LOGON-INIT Command Blocks A command file can contain several command blocks. This enables you to use the same command file to create or update more than one table. Rules for command blocks are: All blocks must begin with the BEGIN command. All blocks must end with the END command. All blocks must use the SELECTFILE command to specify a table source file. If you use the ALLOCATE command, it must immediately follow the SELECTFILE command. Invoking the Program You invoke the SNAXUTL program by entering the following command at the terminal: 1> RUN SNAXUTL /IN cmdfile [, OUT listfile ]/ cmdfile is the name of the edit file containing SNAXUTL input commands, and listfile is the name of the output listing file, which contains a copy of the input commands and system status messages. If listfile is not specified, output is sent to the user s terminal Tandem Computers Incorporated A 5

84 The SNAX/XF Utility SNAXUTL ADD Commands SNAXUTL ADD Commands ADD ESSCMD Command The following is a description of all of the SNAXUTL ADD commands. 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. ADD ESSCMD command-name, CMDTYPE command-type, SENDHOST { Y N }, GATELINE gateway-line, GATEPU gateway-pu, GATELU gateway-lu, MULTIPLELOGON USE_CURRENT_PATH, PLUNAME { dlu-name #plu-name }, SNATYPE sna-type, PROTOCOL protocol, RECSIZE recsize, CHARACTERSET { EBCDIC ASCII KATAKANA }, BINDENTRY bind-entry-name, BINDTABLE bind-table-name, REPDATA replacement-data, CONCDATA concatenated-data, USERDATA user-data, STATIC { ON OFF }, TERMSELF ON... command-name is the name of a command to be added to the ESS table. This operand is required. It is not case-sensitive. The name can be from 1 to 32 characters long. CMDTYPE command-type specifies the type of command being created. Valid values for command-type are: INITSELF-RECEIVED LOGOFF LOGON-CHAR LOGON-INIT ORDER This operand must be specified. SENDHOST { Y N } specifies whether or not the logon is to be sent to an SNA host. The default value is N. A Tandem Computers Incorporated

85 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. This value can be from one to seven alphanumeric characters long, where the first character is alphabetic. device-name is the device name corresponding to the line. This value can be from one to seven alphanumeric characters long, where the first character is alphabetic. Note that GATELINE should not be specified when either GATEPU or GATELU is specified. GATEPU gateway-pu specifies the gateway physical-unit name that is to be used when this command is sent to the SNA host. The format of gateway-pu is: [\system-name.]$device-name.#pu-name where: system-name is the name of the system on which the gateway physical unit resides. This value can be from one to seven alphanumeric characters long, where the first character is alphabetic. device-name is the device name corresponding to the line. This value can be from one to seven alphanumeric characters long, where the first character is alphabetic Tandem Computers Incorporated A 7

86 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.#lu-name where: system-name is the name of the system on which the gateway logical unit resides. This value can be from one to seven alphanumeric characters long, where the first character is alphabetic. device-name is the device name corresponding to the line. This value can be from one to seven alphanumeric characters long, where the first character is alphabetic. lu-name is the device name corresponding to the logical unit. This value can consist of from one to seven alphanumeric characters, where the first character is alphabetic. Note that GATELU should not be specified when either GATELINE or GATEPU is specified. A Tandem Computers Incorporated

87 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. MULTIPLELOGON USE_CURRENT-PATH insures that a terminal LU will not be prevented from logging on to a host program because of a previous failure to establish a passthrough LU-LU session. Such failures occur because the target application is not currently running on the host system. Consequently. problems can arise because: Prior to the attempt to establish a session. SNAX/XF created a path between the terminal LU and a gateway LU. This path continues to exist despite the fact that there is no active LU-LU session. SNAX/XF considered that an LU-LU session is pending on this path. Additional logon attempts by the terminal LU are therefore rejected (unless MUTLTIPLELOGON USE_CURRENT_PATH is specified). When MUTLTIPLELOGON USE_CURRENT_PATH is specified, the terminal LU is able to use the existing path to establish a session, regardless of what is specified in the GATELINE, GATEPU, and GATELU operands. Any data specified in the REPDATA operand of the ESSCMD command is also processed. PLUNAME { dlu-name #plu-name } specifies one of the following: The subdevice name of the PLU process (TACL) that performs primary logical-unit services when the terminal user enters a command The SNA name of the host-system DLU process that performs primary logicalunit services when the terminal user enters a command The subdevice name of the Creator process that establishes communications with Pathway so that a Pathway application can access the terminal When PLUNAME specifies either the subdevice name of a PLU on a Tandem system or the subdevice name of the Tandem Creator process, plu-name can contain from one to seven alphanumeric and special characters immediately preceded by a pound sign (#). When PLUNAME specifies the DLU name of a process on the host, dlu-name can contain from one to eight alphanumeric and special characters. Also note that: A pound sign (#) preceding plu-name is required when plu-name is specified in conjunction with SENDHOST N Tandem Computers Incorporated A 9

88 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. This optional operand has meaning only when SENDHOST N is specified and the CMDTYPE is either LOGON-CHAR or LOGON-INIT. Otherwise, it is ignored. PROTOCOL protocol specifies the type of terminal protocol to be used by the terminal entering this command. Valid values for protocol are CRT and ITI. This is ignored in passthrough mode. RECSIZE recsize specifies the maximum RU size to be used by the terminal entering this command. Valid values for recsize are decimal integers from 1 to This operand is optional. This parameter will be overridden by the MAXRU specified in the BIND. CHARACTERSET { EBCDIC ASCII KATAKANA } specifies whether or not character translation is to occur. EBCDIC turns translation on so that: When necessary, data sent from the terminal to a Tandem application is translated from EBCDIC to ASCII. When necessary, data sent from a Tandem application to the terminal is translated from ASCII to EBCDIC. A Tandem Computers Incorporated

89 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 record to which this name refers contains a BIND image. A valid value for bind-entry-name is any string of alphanumeric and special characters from one to eight characters long. This operand is optional when a CMDTYPE INITSELF-RECEIVED or CMDTYPE LOGON-INIT is specified. Also, this operand is optional when a CMDTYPE LOGON-CHAR and SENDHOST N is specified. Note that when SENDHOST Y is specified, the BINDENTRY bind-entry-name value specifies the name of a record in the host s LOGMODE table. When SENDHOST N is specified, the bind-entry-name value for BINDENTRY specifies the name of a record in the Tandem BIND table. The BINDENTRY operand has no meaning when: SENDHOST Y is specified and the CMDTYPE is LOGON-CHAR. The CMDTYPE is ORDER. The CMDTYPE is LOGOFF. Specifying a value for BINDENTRY bind-entry-name through SNAXUTL overrides any value that may be specified for the line, LU, or PU with an SCF ADD command. BINDTABLE bind-table-name specifies the name of a BIND table to be used when LUNS searches for a BIND image. A valid value for bind-table-name is any string of alphanumeric and special characters from one to eight characters long. The value for bind-table-name is the name of the table as it was specified for the SET table with an ADD SETLOG entry (see the description of the ADD SETLOG command in this appendix). This parameter is optional when SENDHOST N is specified. This parameter has no meaning when SENDHOST Y or CMDTYPE LOGOFF is specified. Specifying a value for BINDTABLE bind-table-name through SNAXUTL overrides any value that may be specified for the line, LU, or PU with an SCF ADD command Tandem Computers Incorporated A 11

90 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). Byte values must be coded in ASCII-hexadecimal format rather than in EBCDIC-hexadecimal format. The REPDATA operand can be specified by a sequence of extended data segments. See Operands earlier in this appendix. Also note that: REPDATA requires that CMDTYPE be LOGON-CHAR. REPDATA is invalid with: CONCDATA USERDATA SENDHOST N CMDTYPE LOGOFF CMDTYPE ORDER CMDTYPE LOGON-INIT CMDTYPE INITSELF-RECEIVED CONCDATA concatenated-data specifies data that is to be concatenated to the CINIT command when LUNS builds that command. The value for concatenated-data can be expressed as any string from 1 to 1880 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). This operand can be specified by a sequence of extended data segments. See Operands earlier in this appendix. Note that CONCDATA is invalid with: REPDATA SENDHOST Y CMDTYPE ORDER CMDTYPE LOGOFF A Tandem Computers Incorporated

91 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. 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). Byte values should be coded in ASCII-hexadecimal format rather than in EBCDIC-hexadecimal format. This operand can be specified by a sequence of extended data segments. See Operands earlier in this appendix. Note that: USERDATA is applicable only when SENDHOST Y is specified and either CMDTYPE LOGON-INIT or CMDTYPE INITSELF-RECEIVED is also specified USERDATA is invalid with REPDATA USERDATA is invalid with CMDTYPE ORDER and CMDTYPE LOGOFF. STATIC { ON OFF } specifies whether the static feature should be turned on or off for this command. This operand is used only when the CMDTYPE is ORDER; in such cases, it must be specified as ON or OFF. TERMSELF ON specifies that the terminal deactivates the static session by causing a TERMSELF request to be sent to the host system. This operand is used only when CMDTYPE is specified as ORDER. It is required for terminating static sessions with LUs on an AS400 system. When specified, the TERMSELF operand must be specified as ON Tandem Computers Incorporated A 13

92 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. MSGTEXT message-text specifies the message text associated with the above message name. The value specified for message-text can contain from 1 to 4042 bytes. Any byte value can be specified. Note that if the message text extends beyond one line in the command file or if any non-character byte values are included, the message must be specified as a sequence of extended data segments. See Operands earlier in this appendix. Also note that any screen-control characters must be coded in ASCII-hexadecimal format. A Tandem Computers Incorporated

93 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. ADD LOGMODENT bind-entry-name, TYPE type-value, FMPROF fm-profile-value, TSPROF ts-profile-value, PRIPROT priprot-value, SECPROT secprot-value, COMPROT comprot-value, SSNDPAC ssndpac-value, SRCVPAC srcvpac-value, PSNDPAC psndpac-value, PSERVIC pservic-value, ENCR encryption-value, PLUNAME plu-name, USERDATA user-data bind-entry-name specifies the name of a record from within the BIND table. The value for bindentry-name can be from one to eight alphanumeric and special characters. Note that LUNS uses the value specified for bind-entry-name as the key to a particular BIND image. Therefore, you should also specify this value as either of the following: Part of the BINDENTRY attribute when using an SCF ADD LINE, ADD PU, or ADD LU command The BINDENTRY attribute in an ESS record TYPE type-value specifies the type of BIND command represented by this BIND image. Any hexadecimal values between %H00 and %H0F can be specified for type-value; however, only 0 and 1 are currently defined, where: %H00 = a negotiable BIND. %H01 = a non-negotiable BIND. (This is the default.) FMPROF fm-profile-value specifies the function management profile (byte 2 of the BIND image). Any hexadecimal number in the range of %H00 to %HFF can be specified for fmprofile-value. The default value is %H Tandem Computers Incorporated A 15

94 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. SECPROT secprot-value specifies the secondary LU protocol (byte 5 of the BIND image). Any hexadecimal number in the range of %H00 to %HFF can be specified for secprot-value. The default value is %H90. COMPROT comprot-value specifies the common LU protocols (bytes 6 and 7 of the BIND image). Any hexadecimal number in the range of %H0000 to %HFFFF can be specified for comprot-value. Note that the required value for 6530 devices is %H7080. The default value is %H3080. SSNDPAC ssndpac-value specifies the secondary receive pacing count (byte 8 of the BIND image). Any hexadecimal number in the range of %H00 to %H3F can be specified for ssndpac-value. The default value is %H00. Note that SNAX/XF does not support pacing. Therefore, any value specified other than the default of %H00 will be treated by SNAX/XF as if the default of %H00 was specified. SRCVPAC srcvpac-value specifies the secondary send pacing count (byte 9 of the BIND image). Any hexadecimal number in the range of %H00 to %H3F can be specified for srcvpac-value. The default value is %H00. Note that SNAX/XF does not support pacing. Therefore, any value specified other than the default of %H00 will be treated by SNAX/XF as if the default of %H00 was specified. A Tandem Computers Incorporated

95 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. Therefore, any value specified other than the default of %H00 will be treated by SNAX/XF as if the default of %H00 was specified. PSERVIC pservic-value specifies the logical unit presentation services profile and usage field (bytes 14 through 25 of the BIND image). The default values for pservic-value are found in Appendix F of this manual. Note that if this command object is not specified, SNAX/XF will generate values for PSERVIC and place them in the BIND image at run time. The values for this command object are entered by first specifying %H, followed by from one to twelve bytes of information. The following example shows all twelve bytes filled: PSERVIC %H AABBCC If less than twelve bytes of information are entered, as in: PSERVIC %H the field in the BIND image will be right-justified with zeros. ENCR encryption-value specifies the type of cryptography that is expected by the LU (byte 26 of the BIND image). Any hexadecimal number in the range of %H00 to %H0F can be specified for encryption-value. The default value is %H00. PLUNAME plu-name if present, plu-name begins at byte 28 of the BIND image. It is specified as a string value and is a maximum of eight bytes long, enclosed in quotes: PLUNAME "CREDIT" PLUNAME "DEPART03" The length of plu-name is found specified at byte 27 (if this command object is not specified, the value found will be %H00). Note that the total length of the BIND image cannot exceed 256 bytes, including what is specified for plu-name and the following command object, user-data Tandem Computers Incorporated A 17

96 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. If neither PLUNAME or USERDATA is specified, then the user-data length byte is not included in the BIND image. In this case, the last byte in the BIND image will be byte 27 (the length of plu-name, which is %H00). The value for user-data is specified as a hexadecimal string enclosed in parenthesis, with a maximum length of 221 bytes. See the following examples: USERDATA (%H40,%H54,%H41,%H4E,%H44,%H45,%H4D,%H40) USERDATA (%HC1,%HC1,"AAAAAA", "BBBB", %HC2, %HC3) Note that the total length of the BIND image cannot exceed 256 bytes, including what is specified for plu-name and the command object that follows it, userdata. Example: Constructing a Bind Image The following is an example BIND image as constructed using LOGMODENT. It resides in $vol.subvol.file. BEGIN SELECTFILE LOGTAB1, TYPE LOGMODE ALLOCATE 10 ADD LOGMODENT bind1, TYPE %H01, & FMPROF %H03, & TSPROF %H03, & PRIPROT %B01, & SECPROT %H90, & COMPROT %H3080, & PSERVIC %H F00, & PSNDPAC %H00, & SRCVPAC %H00, & SSNDPAC %H00, & PLUNAME "APPL1", & USERDATA (%HC1,%HC3,"DEPT 103" ) END A Tandem Computers Incorporated

97 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. ADD SETESS Command The ADD SETESS command adds to the SET table a record representing an ESS table. ADD SETESS ess-table-name, FILENAME filename [, DEFAULTTABLE { Y N } ] ess-table-name is the table name of the ESS table. The value specified for ess-table-name can contain from one to eight alphanumeric and special characters. Note that unless you are designating this table as the default table, you specify the same table name as part of the ESSTABLE attribute when you use the SCF ADD command to add a LINE PU, or LU object. FILENAME filename is the name of the table source file in which the ESS table can be found. If you are running SNAXUTL on a volume and subvolume different from the ones on which the table source file resides, the value specified for filename must be fully qualified. The filename is the same as the one which was used in the SELECTFILE-TYPE ESS command. DEFAULTTABLE { Y N } specifies whether or not the ESS table being defined is to be the default ESS table. If this operand is not specified, the default value is N Tandem Computers Incorporated A 19

98 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. If you are running SNAXUTL on a volume and subvolume different from those on which the table source file resides, the value specified for filename must be fully qualified. This is the same file that was created using the SELECTFILE TYPE LOGMODE command. The following is an example of how to add a BIND table and table source file name to the SET table: BEGIN SELECTFILE snxset, TYPE SET ADD SETLOG BINDTAB1, FILENAME $DATA.TABLES.LOGTAB1 END BINTAB1 is the name of the source BIND table $DATA.TABLES.LOGTAB1. SNAXUTL ALLOCATE Command The ALLOCATE command is used to allocate a new SET, ESS, or BIND table. When the ALLOCATE command is executed, both the source and object files are allocated. The two files will be equal in size. ALLOCATE extent-size extent-size specifies, for the file being allocated, the number of pages, each containing 2048 bytes, that an individual extent will contain. The file system can automatically allocate up to 16 extents for any given file. Thus, were you to specify extentsize as 20, your file could contain a maximum of 320 pages (16 * 20). Tandem recommends that you specify 10 pages. If you wish to calculate extent-size yourself, see the information below. If you know the number and types of records to be contained in a file, you can closely estimate the extent size you need to specify. In the following sections are formulas for calculating the extent size for each of the file types (SET and ESS). Extent sizes do not need to be calculated for BIND tables. A Tandem Computers Incorporated

99 The SNAX/XF Utility SNAXUTL ALLOCATE Command Calculating SET Table Extent Sizes The formula for calculating extent sizes for SET tables is as follows: where a = $ROUNDUP{ ( x)/2048 bytes} a is the SET table extent size in bytes $ROUNDUP x is a function that rounds its argument up to the next highest integer; for example, $ROUNDUP(3.2) = 4 is the number of SET table records that contain ESS or BIND table names. Calculating ESS Table Extent Sizes To compute the extent size for ESS tables, two subcalculations are necessary. The results of the subcalculations are then combined to produce the final extent value. The formula for the first subcalculation is as follows: where a1 = 154x + yz a1 x y z is the number of bytes required for ESS commands is the total number of commands is the number of commands that contain extended data segment operands (such as, REPDATA, CONCDATA, and USERDATA) is the estimated average length in bytes of all extended segment operands Tandem Computers Incorporated A 21

100 The SNAX/XF Utility SNAXUTL ALLOCATE Command The formula for the second subcalculation is as follows: where a2 = (54 + b1)x + (108 + b2)y a2 b1 b2 x y is the number of bytes required for ESS messages is the estimated average length of all ESS messages fewer than 1980 bytes long is the estimated average length of all ESS messages between 1981 bytes and 3720 bytes in length is the number of ESS messages fewer than 1980 bytes long is the number of ESS messages between 1981 bytes and 3720 bytes in length The following formula is used to calculate the extent size, based on the results of the subcalculations: where a = $ROUNDUP{ (132 + a1 + a2)/2048 } a is the extent size to be used in the ALLOCATE command $ROUNDUP a1 a2 is a function that rounds its argument up to the next highest integer (for example, $ROUNDUP(3.2) = 4) is the value derived from the first subcalculation is the value derived from the second subcalculation A Tandem Computers Incorporated

101 The SNAX/XF Utility SNAXUTL END Command SNAXUTL BEGIN Command The BEGIN command delimits the beginning of a command block. BEGIN SNAXUTL DELETE Command The DELETE command deletes individual records from the table selected through the 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 Command The END command delimits the end of a command block. END Tandem Computers Incorporated A 23

102 The SNAX/XF Utility SNAXUTL SELECTFILE Command SNAXUTL SELECTFILE Command The SELECTFILE command defines the source file on which subsequent recordmanipulation commands will be performed. Thus all ALLOCATE, ADD, and 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. The value specified for filename can contain from one to seven characters. If you are running SNAXUTL on a volume and subvolume different from the ones on which the specified table source file resides, filename must be fully qualified. TYPE filetype refers to the type of file specified. Valid values for filetype are SET, ESS, and LOGMODE. DEACTIVATE { Y N } instructs LUNS to deactivate the named ESS table when DEACTIVATE Y is specified. In this way, SNAXUTL can access and update it. When SNAXUTL has completed the update, LUNS reactivates the table. If you use the SELECTFILE command to select an active ESS table for updating and either omit DEACTIVATE Y or specify DEACTIVATE N, SNAXUTL will receive a file-system error 12 (file in use) when it attempts the update. The default value for this operand is DEACTIVATE N. A Tandem Computers Incorporated

103 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. The name of a system message in the ESS table is Snnnn, where nnnn is some decimal number. Messages in the range S0000 through S0012 are equivalent in meaning to USS messages 0 through 12 in the IBM USS tables. Throughout this appendix, character-coded data entered on a display terminal is referred to as a command. Finding an Assigned ESS Table Problem isolation might require finding the name of the ESS table currently assigned to a terminal. To find the name, issue an SCF INFO LU terminal-lu-name command. If an ESS table was not assigned to the terminal s LU using SCF or if the currently active SET table does not contain a default ESS table, the terminal does not have an ESS table assigned, and it will not be able to use LUNS. The following is a discussion of ESS table assignment that might prove useful in correcting problems involving the assignment of an ESS table to a terminal. An ESS table is assigned to a terminal either explicitly, using SCF, or by default in the currently active SET table. A SCF assignment takes precedence over a SET table default designation. If assigned explicitly with SCF, the terminal s ESS table name can be specified using the ESSTABLE attribute in an SCF ADD LU or ALTER LU command. It can also be specified for LUs subordinate to a line by using the ESSTABLE attribute in an SCF ADD/ALTER LINE or ADD/ALTER PU command. Once an ESS table name has been specified for either a line or a PU, it is used, as a default table, for any LU that is added to that line or PU, provided that the ADD LU command does not include an ESSTABLE attribute. An ESS table can be defined as a default table in a LUNS SET table by using the DEFAULTTABLE Y operand in an ADD SETESS command. This default ESS table applies to any LU that has not had an ESS table defined using SCF Tandem Computers Incorporated B 1

104 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. If you use an ESS table without system messages or if a system message that LUNS is attempting to send does not exist in the ESS table, the following message is displayed: " MESSAGE NOT FOUND - Snnnn " where nnnn is the system-message number that was not found. " LOGON / LOGOFF IN PROGRESS --> S0000 " Cause Effect The last command requested a logon or logoff of a Tandem process, the request is being processed by LUNS, and this message is displayed until the logon or logoff is completed. This message is not displayed during logging on to or off from a host application. The logon/logoff command is being processed. Recovery If the logon or logoff is not completed in a reasonable period of time, abort the terminal s LU using SCF or stop the Tandem process for which the logon or logoff is pending. B Tandem Computers Incorporated

105 ESS System Messages Messages and Codes " ESS TABLE RECORD NOT FOUND FOR THIS COMMAND --> S0002 " Cause Effect An ESS table record whose record name matches the failing command was not found in the terminal s ESS table. 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. If the command is being entered correctly, the ESS table currently assigned to the terminal is either the wrong table or it does not contain a record whose record name matches the failing command. If necessary, see Finding an Assigned ESS Table earlier in this appendix. If the correct ESS table was assigned to the terminal, use SNAXUTL to add the desired record to the terminal s ESS table. If the wrong ESS table was assigned to the terminal, temporarily assign the correct one using the SCF ALTER LU terminal-lu-name, ESSTABLE ess-tablename command. A permanent correction might be necessary to the SCF ADD LU command that created the LU. If line or PU default values are employed for the ESSTABLE attribute of the LU, check the ADD PU and ADD LINE commands which created the LU s PU and line and correct them if necessary. " SEQUENCE ERROR--> S0006 " Cause Effect The failing command was not in the correct sequence. For example, the command requested a logoff and the terminal was not logged on to an application. The failing command is ignored and the terminal s keyboard is reset to allow the entry of a valid command. Recovery Enter a valid command Tandem Computers Incorporated B 3

106 ESS System Messages Messages and Codes " SESSION NOT BOUND --> S0007 " Cause Effect LUNS was unable to process the failing command because of a resource problem. 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). Recovery Check EMS event message 81 for LUNS error code 2305, 2307, 2309, 2311, 2320, 2325, or 2326 and consult its description in the Operator Messages Manual for the appropriate recovery action. " INSUFFICIENT STORAGE--> S0008 " Cause Effect LUNS was unable to process the failing command because it was unable to allocate a memory segment or get a buffer from the buffer pool. 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 2307). Recovery Check EMS event message 81 for LUNS error code 2307 and consult its description in the Operator Messages Manual for the appropriate recovery action. B Tandem Computers Incorporated

107 ESS System Messages Messages and Codes ( User-defined, or Tandem supplied, LOGO or MENU ) ( System Message 10 ) Cause Effect 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. The terminal s keyboard is reset to allow the entry of a command. Recovery No recovery action is necessary. " COMMAND IS TOO LONG ---- MAX 32--> S0014 " Cause Effect The failing command was longer than the 32-character maximum. The failing command is ignored and the terminal s keyboard is reset to allow the entry of a valid command. Recovery Enter a command whose length is 32 characters or less. " BLANK STRING ENTERED--> S0015 " Cause Effect The failing command was a null string. The most likely cause is that the terminal operator pressed the ENTER key without having first typed in any characters. The failing command is ignored and the terminal s keyboard is reset to allow the entry of a valid command. Recovery Enter a valid command Tandem Computers Incorporated B 5

108 ESS System Messages Messages and Codes " CANNOT PERFORM OPERATION -- LOGON PENDING --> S0016 " Cause Effect 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). The failing command is ignored, the terminal s keyboard is reset to allow the entry of another command, and LUNS continues processing the logon command. Recovery If the pending logon does not complete in a reasonable period of time, abort the terminal s LU using SCF or stop the Tandem process for which the logon is pending. " CANNOT PERFORM OPERATION -- INVALID REQUEST--> S0018" Cause The operation requested is not supported. Effect No operation is performed. Recovery None. B Tandem Computers Incorporated

109 ESS System Messages Messages and Codes " INVALID ENTRY FOUND IN ESS TABLE--> S0019 " Cause Effect 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. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command. Depending upon the extent of the table s corruption, LUNS might not be able to process any additional commands until recovery has been completed. Recovery Save the terminal s corrupted ESS table object file by renaming it and noting its new name. The name of the ESS table s object file is the ESS table name with the letter O appended (for example, ESSTAB1 s object file name is ESSTAB1O). If necessary, see Finding an Assigned ESS Table earlier in this appendix. Rebuild the ESS table using SNAXUTL and retry the command. If the problem persists with a new ESS table object file, the table s corruption is a persistent problem and requires immediate attention. In either case, inform your Tandem representative Tandem Computers Incorporated B 7

110 ESS System Messages Messages and Codes " UNABLE TO ALLOCATE GATEWAY LU --> S0020 " Cause Effect 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. 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, 2311, or Recovery Check EMS event message 81 for LUNS error code 2305, 2311, or 2325 and consult its description in the Operator Messages Manual for the appropriate recovery action. " INTERNAL LINK ERROR --> S0021 " Cause Effect During processing of the failing command, an error occurred when an interprocess message was sent to a SNAX/XF line-handler process. 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 2307 or 2309). Recovery Check EMS event message 81 for LUNS error code 2307 or 2309 and consult its description in the Operator Messages Manual for the appropriate recovery action. B Tandem Computers Incorporated

111 ESS System Messages Messages and Codes " CANNOT TURN STATIC ON WHILE IN SESSION--> S0022 " Cause Effect 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. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command. Recovery If you wish to execute the failing command, enter a command that causes a logoff, and then reissue the command. " CANNOT TURN STATIC OFF WHILE IN SESSION --> S0023 " Cause Effect 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 OFF attribute was entered. This caused LUNS to attempt to take down a static path to the host, which cannot be done while in an LU-LU session. The failing command is ignored, the terminal remains in session and the terminal s keyboard is reset to allow the entry of another command. Recovery If you wish to execute the failing command, enter a command that causes a logoff, and then reissue the command Tandem Computers Incorporated B 9

112 ESS System Messages Messages and Codes " LOGON REJECTED -- LOGOFF THEN LOGON --> S0024 " Cause Effect 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. 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. Recovery If you wish to execute the failing command, enter a command that causes a logoff, and then reissue the command. If you wish to continue with the session in progress, press the SYSTEM REQUEST key to return to the LU-LU session. " ESS TABLE NOT FOUND --> S0025 " Cause Effect An ESS table has been assigned for use by this terminal, but LUNS was unable to locate its object file as named in the currently active SET table. Therefore, LUNS could not search the ESS table for a record whose record name matches the failing command. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command, but the terminal will not be able to use LUNS until the problem is corrected. Additional information, including the ESS table name, can be found in EMS event message 81 (LUNS error code 2310, 2311, 2312, or 2313). Recovery Check EMS event message 81 for LUNS error code 2310, 2311, 2312, or 2313 and consult its description in the Operator Messages Manual for the appropriate recovery action. B Tandem Computers Incorporated

113 ESS System Messages Messages and Codes " ESS ENTRY NOT FOUND END-OF-TABLE MARKER MISSING--> S0026 " Cause Effect 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. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command, but the terminal might not be able to use LUNS until the problem is corrected. Recovery Save the terminal s corrupted ESS table object file by renaming it and noting its new name. The name of the ESS table object file is the ESS table name with the letter O appended (for example, ESSTAB1 s object file name is ESSTAB1O). If necessary, see Finding an Assigned ESS Table earlier in this appendix. Rebuild the ESS table using SNAXUTL and retry the command. If the problem persists with a new ESS table object file, the table s corruption is a persistent problem and requires more immediate attention. In either case, inform your Tandem representative. " APPLICATION NOT DEFINED --> S0027 " Cause Effect An attempt was made to log on to a Tandem application that has not been defined by an SCF ADD APPL command. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command. Recovery Check the terminal s ESS table for an ESSCMD record whose command name matches the failing command. That record should contain a PLUNAME specification that begins with a pound sign (#), and this is the name of the application that has not been properly defined to LUNS by an SCF ADD APPL command. If necessary, see Finding an Assigned ESS Table earlier in this appendix. Either use SNAXUTL to correct the PLUNAME specified in the ESSCMD record or define the application to LUNS using an SCF ADD APPL command Tandem Computers Incorporated B 11

114 ESS System Messages Messages and Codes " CREATOR NOT DEFINED --> S0029 " Cause Effect 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. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command. Recovery Use the SCF INFO APPL application-subdevice-name command to display the CREATOR attribute for the application. The application-subdevicename is specified in the PLUNAME field of the ESSCMD record. If necessary, see Finding an Assigned ESS Table earlier in this appendix. Either correct the CREATOR attribute or define the Creator process to LUNS using an SCF ADD APPL command. " CREATOR NOT CONNECTED --> S0030 " Cause Effect 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 issued a CONNECT request to LUNS. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command. Recovery Use the SCF INFO APPL application-subdevice-name command to display the CREATOR attribute for the application. The application-subdevicename is specified in the PLUNAME field of the ESSCMD record. If necessary, see Finding an Assigned ESS Table earlier in this appendix. Check that the Creator process has been started. If the Creator process was active at the time of the failure, contact your Tandem representative. B Tandem Computers Incorporated

115 ESS System Messages Messages and Codes " CREATOR PROCESS DISCONNECTED--> S0040 " Cause Effect The Creator process has issued a CLOSE or a DISCONNECT, or it has stopped or abended, causing LUNS to simulate a Creator DISCONNECT. 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. " UNABLE TO ASSIGN REMOTE LU--> S0045 " Cause Effect 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 in a remote Tandem node. When the gateway line resides in the same node as the terminal, system message S0020 is returned to the terminal. 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 2333). Recovery Check EMS event message 81 for LUNS error code 2333 and consult its description in the Operator Messages Manual for the appropriate recovery action Tandem Computers Incorporated B 13

116 ESS System Messages Messages and Codes " SESSION NOT BOUND -GUARDIAN 90 USESEGMENT ERROR--> S0046 " Cause Effect 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. 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). Recovery Check EMS event message 81 for LUNS error code 2311 and consult its description in the Operator Messages Manual for the appropriate recovery action. Problem isolation might require that you consult your Tandem representative. " INVALID ESS ENTRY FOR A CHARACTER CODED LOGON -> S0049 " Cause Effect The failing command matches the command name of an ESSCMD record in the terminal s ESS table, but the record s CMDTYPE is INITSELF-RECEIVED. Such a record can be referenced only by an SNA INIT-SELF request from a terminal not by a character-coded SNA request. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command. Recovery Check that the ESSCMD record in the terminal s ESS table whose command name matches the failing command is defined as you intended. If necessary, see Finding an Assigned ESS Table earlier in this appendix. B Tandem Computers Incorporated

117 ESS System Messages Messages and Codes " CANNOT PERFORM OPERATION -- LOGOFF PENDING--> S0050 " Cause Effect 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). The failing command is ignored, the terminal s keyboard is reset to allow the entry of another command, and LUNS continues processing the logoff command. Recovery If the pending logoff is not completed in a reasonable period of time, abort the terminal s LU using SCF or stop the Tandem process for which the logoff is pending. " LOGON REJECTED BY APPLICATION --> S0051 " Cause Effect The application you tried to log on to has rejected your logon. The failing command is ignored and the terminal s keyboard is reset to allow the entry of another command. Recovery Consult your system manager for the proper way to log on to the application. " BIND REJECTED BY SLU--> S0053 " Cause The SLU has rejected the BIND request from the Tandem PLU. Effect No LU-LU session is created. Recovery Determine whether the BIND parameters sent are the correct ones Tandem Computers Incorporated B 15

118 ESS System Messages Messages and Codes " CANNOT ISSUE TERMSELF WHEN NOT IN SESSION WITH A HOST-->S0054" Cause Effect 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. No TERMSELF request is sent, and no logoff occurs. Recovery The terminal should use a character coded logoff command intended for use with sessions between terminals and Tandem applications, " GATEWAY LU NOT AVAILABLE--> S0055" Cause Effect LUNS was unable to find an available gateway LU. No LU-LU session is established. Recovery Retry the operation. If the problem persists, have the system operator determine whether or not there are an adequate number of gateway LUs configured. B Tandem Computers Incorporated

119 Appendix C Creator Process Error Messages Creator Process LOGON and LOGOFF Messages The following Creator process messages are displayed during Pathway and TACL logon and logoff sequences. This appendix includes messages common to both 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. In such cases, follow the standard procedures at your site for contact appropriate support personnel. These procedures might involve contacting the Tandem National Support Center or your local Tandem support representative. Collect any relevant information for the support personnel, including details from the error message, a description of the problem and accompanying symptoms, and supporting documentation such as EMS logs, trace files, a CPU dump (if applicable). If your operating procedures require contacting the Tandem National Support Center, please supply your system number and the numbers and versions of all related products. Creator Process Pathway Logon Message PATHWAY $PATHMON-name program started at Tandem-name Pathway-term Cause Effect The Pathway application has successfully started. The $PATHMON-name value is the name of the PATHMON. The Tandem-name value is returned in the form $line-name.#lu-name. The Pathway-term value is the Pathway terminal name. Recovery This is an informational message only; no action is required Tandem Computers Incorporated C 1

120 Creator Process Error Messages Creator Process LOGON and LOGOFF Messages Creator Process APPLFILE Logon Message APPLFILE $name created at Tandem-name Cause Effect The APPLFILE application has successfully started. 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 Pathway Logoff Message PATHWAY $PATHMON-name program stopped at Tandem-name Pathway-term Cause Effect The Pathway application has successfully stopped. The $PATHMON-name value is the name of the PATHMON. The Tandem-name value is returned in the form $line-name.#lu-name. The Pathway-term value is the Pathway terminal name. Recovery This is an informational message only; no action is required. C Tandem Computers Incorporated

121 Creator Process Error Messages Numbered Creator Process Messages Creator Process APPLFILE Logoff Message APPLFILE $name stopped at Tandem-name Cause Effect The APPLFILE application has successfully stopped. 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. Numbered Creator Process Messages The following Creator process messages are numbered and are logged to the OUT file specified in the Creator process RUN command. If no OUT file is specified, messages are logged to the home terminal of the Creator process. Creator Process Error 000 This error message is no longer used. Creator Process Error 001 This error message is no longer used. Creator Process Error 002 This error message is no longer used. Creator Process Error 003 This error message is no longer used. Creator Process Error 004 This error message is no longer used. Creator Process Error 005 This error message is no longer used Tandem Computers Incorporated C 3

122 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 006MIS CP006MIS Creator terminating ++++ Cause Effect This is probably due to incorrect startup parameters. 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 007 This error message is no longer used. Creator Process Error 008NEW CP008NEW - CPU number too large or CPU parm is incorrect Data = user-data Tandem Name = Tandem-name Cause Effect A user tried to start a new TACL, but the CPU number specified in the logon record is either incorrect or too large. 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. Have the user restart the TACL process. C Tandem Computers Incorporated

123 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 Effect The operating system could not create the new process requested by the Creator process. The error field values are bits <0:7> and <8:15> that are returned in the error parameter of the PROCESS_CREATE procedure call (when using D-series system software). The program-filename value is the fully qualified program file name of the process as specified through the APPLFILE attribute of the SCF ADD APPL command. A display of the current CONCDATA field parameters from the logon record of the ESS table is returned as user-data. The Tandemname value is returned in the form $line-name.#lu-name. Recovery See the syntax description of the PROCESS_CREATE procedure call in the Guardian Procedure Calls Reference Manual for an explanation of the file-system error code, and take appropriate action Tandem Computers Incorporated C 5

124 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 010INI CP010INI - Creator is not nonstop because it is not named Cause Effect A process name was not specified in the NAME parameter of the RUN command for the Creator process. 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. If you want the Creator process to run as a NonStop process, stop the running Creator process and reissue the RUN command, and include a valid process name in the NAME parameter. Creator Process Error 011INI CP011INI - Creator is not nonstop because the backup CPU number is invalid Cause Effect A backup CPU number was not specified or was incorrectly specified in the RUN command for the Creator process. No backup CPU will run. Recovery If you do not want the Creator process to run as a NonStop process pair, disregard this message. If you want the Creator process to run as a NonStop process pair, stop the running Creator process and reissue the RUN command with a valid backup CPU number. Creator Process Error 012 This error message not applicable for SNAX/XF. C Tandem Computers Incorporated

125 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 Effect The Creator process cannot send a startup message to the APPLFILE process it has created. The error value is the file-system error code. The program-filename value is the fully qualified program file name of the process as specified through the APPLFILE parameter of the SCF ADD APPL command. The process-name value is the process identifier of the process. 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 $linename.#lu-name. Recovery Refer to the Guardian Procedure Errors and Messages Manual for an explanation of the file-system error code. Reissue the command that generated this message. If the problem persists, save the information returned in this message and follow the procedure described at the beginning of this appendix for collecting information and contacting support personnel Tandem Computers Incorporated C 7

126 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 015PAT CP015PAT - NAME keyword missing Data = user-data Tandem Name = Tandem-name Cause Effect The required NAME value (the PATHMON name) was not specified for this Pathway application. 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. Have the Pathway user reissue the logon. Creator Process Error 016PAT CP016PAT - PATHWAY program name missing Data = user-data Tandem Name = Tandem-name Cause Effect The Pathway application name was not specified in the logon record. 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. Have the Pathway user reissue the logon. C Tandem Computers Incorporated

127 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 Effect The Creator process is unable to open the PATHMON named $PATHMON-name. The error value is the file-system error code. 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 $linename.#lu-name. Recovery Refer to the Guardian Procedure Errors and Messages Manual for an explanation of the file-system error code and take appropriate action. Creator Process Error 019 This error message is no longer used. Creator Process Error 020 This error message is no longer used Tandem Computers Incorporated C 9

128 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 Effect An interprocess communication to the PATHMON named $PATHMON-name has failed. The error value is the file-system error code. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery Refer to the Guardian Procedure Errors and Messages Manual for an explanation of the file-system error code. Perform appropriate action as needed. Creator Process Error 022NEW CP022NEW - Expecting APPLFILE or PATHWAY as the first entry in the data field. Data = user-data Tandem Name = Tandem-name Cause Effect Something other than APPLFILE (or TACL) or Pathway is specified as the first entry in the logon record. 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. Have the Pathway or APPLFILE user reissue the logon. C Tandem Computers Incorporated

129 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 Effect The program name was not added to the Pathway configuration file. The $PATHMON-name value is the name of the PATHMON. The program-name value is the Pathway object name. The error and info values contain additional information about the Pathway error. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery Verify that the names specified for Pathway in the logon record are the same as were specified in the Pathway configuration file. Refer to the PATHWAY PATHCOM Reference Manual for information on the error and info values. Perform appropriate action as needed. Creator Process Error 024MIS CP024MIS - Takeover by backup Creator CHECKPOINT Status <0:7> = status-field CHECKPOINT Status <8:15> = status-field Cause Effect The primary Creator process has failed, and the backup Creator process has taken control. The status field values are bits <0:7> and <8:15> that are returned in the status parameter of the CHECKPOINT procedure call. For explanations of these status codes, consult the syntax description in the Guardian Procedure Calls Reference Manual. Recovery This is an informational message only; no action is necessary Tandem Computers Incorporated C 11

130 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 025INI CP025INI - File Error - connecting to SNAX File Error = error Cause Effect Usually, this message means that the Creator process password was incorrectly specified in the PASSWORD parameter of the Creator RUN command. 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. For any other error value, refer to the Guardian Procedure Errors and Messages Manual for an explanation of the file-system error code and take appropriate action. Creator Process Error 026 This error message is no longer used. Creator Process Error 027INI CP027INI - File error - opening SNAX File Error = error File Name = Creator-name Cause Effect The Creator process subdevice name specified in the CREATOR #subdevicename parameter of the Creator RUN command does not match the name specified in the SCF ADD APPL command, or another Creator process has opened $SSCP under the same name. The error value is the file-system error code. The value returned for Creatorname is the subdevice name value specified for the CREATOR #subdevicename parameter in the RUN command. C Tandem Computers Incorporated

131 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 029MIS This error message is no longer used. Creator Process Error 030NEW This error message is no longer used. Creator Process Error 031 This error message is no longer used. Creator Process Error 032NEW CP032NEW - Duplicate keyword in user data Data = user-data Tandem Name = Tandem-name Cause Effect There are duplicate keyword parameters in the logon record. 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. Have the user reissue the logon. Creator Process Error 033 This error message is no longer used Tandem Computers Incorporated C 13

132 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 Effect An internal error has occurred. The Creator process stops running. Recovery Save the ABEND file and the SNAX trace (if there is one), and follow the procedure described at the beginning of this appendix for collecting information and contacting support personnel. Creator Process Error 035MIS CP035MIS - FILE_OPEN_CHKPT_ error File Error = error Status = cause of file error File Name = filename Cause Effect The CHECKOPEN call has failed on the backup Creator process. The error and cause of file error values are parameters of the FILE_OPEN_CHKPT_ procedure call. The filename value is the name of the designated file that was to be opened by the FILE_OPEN_CHKPT_ procedure (when using D-series system software). Note that the Creator process will continue to run without a backup. Recovery See the syntax description of the FILE_OPEN_CHKPT_ procedure call in the Guardian Procedure Calls Reference Manual for an explanation of the file-system error code and take appropriate action as needed. If you want to run the Creator C Tandem Computers Incorporated

133 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 Effect Either a disk log file does not exist or the spooler is full. The error value is the file-system error code. The filename value is the name of the log file for the Creator process as specified by the OUT parameter of the Creator RUN command. Recovery Refer to the Guardian Procedure Errors and Messages Manual for an explanation of the file-system error code. Create the file or empty the spooler. Creator Process Error 037MIS CP037MIS - No room to add Session Control Blocks Maximum Sessions = value Data = user-data Tandem Name = Tandem-name Cause Effect The Creator process cannot find the resources to start another new session. The number of sessions specified for MAXSESSIONS is returned as value. 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 Wait until one session ends before starting another Tandem Computers Incorporated C 15

134 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 038INI CP038INI - Parameter too long Error Data Tandem Name = error-data = Tandem-name Cause Effect A parameter value specified in either the Creator RUN command or the logon record in the ESS table contains too many characters. If a parameter value specified in the Creator RUN command contains too many characters, this message returns only the error-data value. The error-data value is the parameter in the RUN command that contains the error. If a parameter value specified in the logon record of the ESS table contains too many characters, this message returns the error-data value and the Tandemname value. The Tandem-name value is returned in the form $line-name.#lu-name. The value for $line-name.#lu-name identifies the terminal user who attempted to log on to the application that is linked to the incorrectly specified logon record parameter. Recovery Reissue a corrected Creator RUN command, or correct the logon record in the ESS table and have the user reissue the logon. Creator Process Error 039 This error message is no longer used. Creator Process Error 040 This error message is no longer used. Creator Process Error 041 This error message is no longer used. Creator Process Error 042 This error message is no longer used. Creator Process Error 043 This error message is no longer used. C Tandem Computers Incorporated

135 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. Cause Effect The Creator process has received an invalid response to its CONNECT request. The Creator process cannot connect to SNAX and stops running. Recovery Restart the Creator process. If the problem persists, save the ABEND file and the SNAX trace (if there is one) and follow the procedure described at the beginning of this appendix for collecting information and contacting support personnel Tandem Computers Incorporated C 17

136 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 048SSCP CP048SSCP - Unable to disconnect from SSCP, too many negative replies Cause Effect The Creator process has repeatedly received negative responses to its DISCONNECT requests. 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 051INI CP051INI - Invalid subdevice name File Name = filename Cause Effect The value specified for the CREATOR parameter of the RUN command is not in the proper form. The value can consist of 1 through 7 alphanumeric characters preceded by a pound sign (#). The filename value is the user-supplied parameter that contains the error. Recovery Reissue the RUN command, specifying a correct value for the CREATOR parameter. C Tandem Computers Incorporated

137 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 Effect 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. In this case, the Creator process stops execution. The error value is the filesystem error code. The filename value is the subdevice name of the Creator process. Recovery Refer to the Guardian Procedure Errors and Messages Manual for an explanation of the file-system error code and take appropriate action. Restart the Creator process. Creator Process Error 054INI CP054INI - Syntax error - quote mismatch Cause: Effect A user-supplied quotation mark is missing from either the beginning or end of the PASSWORD parameter in the Creator process RUN command. The Creator process is not started. Recovery The inclusion of quotation marks surrounding the password is optional but, if used, must be balanced. Either add the missing quotation mark or eliminate the quotation marks altogether Tandem Computers Incorporated C 19

138 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 055INI CP055INI - Invalid CREATOR RUN keyword Error Data = error-data Cause Effect 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. The error-data value contains the parameter in error. Recovery Reissue the Creator process RUN command, using the correct keyword parameter. Creator Process Error 056INI CP056INI - Missing semicolon in startup command Cause Effect The required semicolon has been omitted from the Creator process RUN command. The Creator process does not start. Recovery Use the correct form of the Creator process RUN command. Creator Process Error 057 This error message is no longer used. C Tandem Computers Incorporated

139 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 058INI CP058INI - Duplicate keyword on startup Cause Effect A keyword parameter was used more than once in the Creator process RUN command. The Creator process is not started. Recovery Omit the duplicate keyword parameter and reissue the Creator process RUN command. Creator Process Error 059NEW CP059NEW - Invalid keyword in user data Data = user-data Error Data = error-data Tandem Name = Tandem-name Cause Effect An invalid keyword parameter has been found in the logon record for a TACL or a Pathway application. The only acceptable keyword parameters allowed in the logon record are as follows: NAME, CPU, and PRI (for a TACL logon record) NAME and PROGRAM (for a Pathway logon record) A display of the current CONCDATA field parameters from the logon record of the ESS table is returned as user-data. The error-data value is the parameter that is in error. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery Use SNAXUTL to correct the logon data record. Have the user reissue the logon Tandem Computers Incorporated C 21

140 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 Effect A comma was found as the last item in the logon record. The comma must be followed by another parameter or excluded. 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. Have the user reissue the logon. Creator Process Error 061NEW CP061NEW - Expecting dollar sign as the first character in the process name Data = user-data Tandem Name = Tandem-name Cause Effect The process name specified in the DATA field of the logon record does not begin with a dollar sign ($). 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. Recovery Use SNAXUTL to correct the logon record. Have the user reissue the logon. C Tandem Computers Incorporated

141 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 Effect The user included the parameter PROCESS in the data field of an APPLFILE or TACL logon record. 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. Recovery If an APPLFILE (including TACL) logon is desired, use SNAXUTL to omit the PROCESS parameter in the logon record. Have the user reissue the logon. Creator Process Error 063NEW CP063NEW - PROCESS name invalid Data = user-data Tandem Name = Tandem-name Cause Effect The process name specified in the DATA field of the logon record is not a valid name. A valid process name should be from one to five characters proceeded by a dollar sign ($) and of the form $axxxx, where a is an alphabetic character and xxxx can be any alphabetic character or digit. 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. Recovery Use SNAXUTL to correct the logon record with the correct form of the process name. Have the user reissue the logon Tandem Computers Incorporated C 23

142 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 064NEW CP064NEW - PROCESS not running Data = user-data Tandem Name = Tandem-name Cause Effect The process name specified with the PROCESS parameter in DATA field of the logon record is not running. 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. Recovery Either start the process specified in the PROCESS parameter of the logon record or specify a running process in the logon record. Have the user reissue the logon. Creator Process Error 065PAT CP065PAT - PATHWAY not configured or other internal error Internal Error = error-number PATHMON Name = $PATHMON-name Tandem Name = Tandem-name Cause Effect Either the PATHMON named $PATHMON-name is running but is not configured, or an internal error has been encountered. The error-number value is the internal error designation. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery Configure Pathway. If Pathway is already configured, retain the error-number value and follow the procedure described at the beginning of this appendix for collecting information and contacting support personnel. C Tandem Computers Incorporated

143 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 066MIS CP066MIS - CHECKPOINT error, backup is stopped File error = error Cause Effect The backup CPU is stopped. 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 067NEW CP067NEW - PATHMON name invalid, expecting $xxxxx or \xxxxxxx.$xxxxx Data = user-data Tandem Name = Tandem-name Cause Effect An invalid PATHMON name has been specified in the logon record. When using D-series system software: $xxxxx represents a one-character to five-character PATHMON name. \xxxxxxx.$xxxxx represents a one-character to seven-character system name, followed by a one-character to five-character PATHMON name. 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 a valid PATHMON name. A valid name has from one to five characters preceded by a dollar sign ($). The first character must be alphabetic, while the remaining characters can be alphabetic or alphanumeric. Use SNAXUTL to correct the logon record. Have the Pathway user reissue the logon Tandem Computers Incorporated C 25

144 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: Effect Invalid data was received from the SNAX/XF process. 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. Follow the procedure described at the beginning of this appendix for collecting information and contacting support personnel. Creator Process Error 069MIS CP069MIS - No record of session. The Creator was restarted since the original LOGON request. Tandem Name = Tandem-name Cause Effect If the Creator process is stopped and restarted, this message occurs when the user logs off from the Pathway or APPLFILE session. A Pathway or APPLFILE session started through the Creator process continues to run even though the Creator process has stopped. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery This is an informational message only; no action is required. C Tandem Computers Incorporated

145 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 070SSCP CP070SSCP - Duplicate LOGON received from SNAX Tandem Name = Tandem-name Cause Effect A LOGON command received from a user was misread by the Creator process as currently in session. The Tandem-name value is returned in the form $line-name.#lu-name. Recovery If the problem persists, save the information returned in this message and follow the procedure described at the beginning of this appendix for collecting information and contacting support personnel. Creator Process Error 071NEW CP071NEW - APPLFILE name invalid, expecting $xxxxx Data = user-data Tandem Name = Tandem-name Cause Effect The NAME parameter was incorrectly specified. 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 Specify a valid process name; a dollar sign ($), followed by up to five alphanumeric characters Tandem Computers Incorporated C 27

146 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 072INI CP072INI - GUARDIAN version must be at least D00 Cause Effect An attempt was made to run the SNAX/XF Creator process on a version earlier than the D00 release of the operating system. The Creator process is not started. Recovery Obtain a C-series version of the SNAX/XF Creator process. Creator Process Error 073INI CP073INI - File is not SNAX/CDF or SNAX/XF File Name = filename Cause Effect The file name used as the CREATOR parameter was not $SSCP (SNAX/XF) or the name of a running SNAX/CDF process. filename is the file name used as the CREATOR parameter for startup. Recovery Specify the name $SSCP or the name of a running SNAX/CDF process. C Tandem Computers Incorporated

147 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 074INI CP074INI - No keyword after comma in startup command Cause: Effect 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. 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 075PAT CP075PAT - Printer name invalid Data = user-data Tandem Name = Tandem-name Cause Effect The printer name was incorrectly specified for the PRINTER keyword. A display of the current CONCDATA field parameters from the logon record of the ESS table is returned as user-data. Tandem-name is returned in the form $line-name.#lu-name. Recovery Specify a valid printer name Tandem Computers Incorporated C 29

148 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 076INI CP076INI - MAXPATHMONOPENS value not between 0 and 99 Cause Effect A MAXPATHMONOPENS value was specified that was not a number between 0 and 99. 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 077NEW CP077NEW - Pathway access not allowed, MAXPATHMONOPENS = 0 Cause Effect The Creator process was started with a MAXPATHMONOPENS value of 0. The user then tried to log on to a Pathway application. The user was not allowed to log on to a Pathway application. Recovery Either restart the Creator process with a MAXPATHMONOPENS value greater than 0, or inform the user that Pathway access is not allowed. Creator Process Error 078 This error message is no longer used. Creator Process Error 079 This error message is no longer used. C Tandem Computers Incorporated

149 Creator Process Error Messages Numbered Creator Process Messages Creator Process Error 080INI CP080INI - MAXSESSIONS value not between 1 and Cause Effect The parameter for MAXSESSIONS was not between 1 and 2000 when using D-series system software. 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. (The value should be between 1 and 2000 when using the CRT and ITI protocols, and between 1 and 1000 when using the SNALU protocol.) Creator Process Error 081INI CP081INI - ALLOCATESEGMENT failure Status = error field Cause Effect The disk from which the Creator process was taken is out of space. The value for error field is the error code returned from the call to ALLOCATESEGMENT. Recovery Move the object file to another disk, or use the SWAP disk keyword on startup Tandem Computers Incorporated C 31

150 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 Effect The disk from which the Creator process was taken is out of space. 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. Recovery Move the object file to another disk, or use the SWAP disk keyword on startup. Creator Process Error 083 This message is not used. Creator Process Error 084NEW CP084NEW - Unable to communicate with APPLFILE File Error = error Program File Name = program-filename Data = user-data Tandem Name = Tandem-name Cause The newly started process quit before it could be opened. Effect error is the file-system error code. program-filename is the fully qualified program file name of the TACL process as specified through the APPLFILE parameter of the SCF ADD APPL command. A display of the current CONCDATA field parameters from the logon record of the ESS table is returned as user-data. Tandem-name is returned in the form $line-name.#luname. C Tandem Computers Incorporated

151 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 Tandem Computers Incorporated C 33

152 Creator Process Error Messages Numbered Creator Process Messages (This page left intentionally blank) C Tandem Computers Incorporated

153 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 INITSELF- RECEIVED A static passthrough application In the illustrations, the logon and logoff sequences flow counter-clockwise that is, from the terminal at the right, to LUNS, then to the various processes, and back again to the terminal Tandem Computers Incorporated D 1

154 LUNS High-Level Flow Diagrams Logon and Logoff for a Host Application (LOGON-CHAR) Logon and Logoff for a Host Application (LOGON-CHAR) Figure D-1 shows a terminal logging on to and logging off from a host application. The logon record in the ESS table specifies CMDTYPE LOGON-CHAR but does not use the REPDATA field. Figure D-1. Logon and Logoff Sequences for a Host Application (CMDTYPE LOGON-CHAR and No REPDATA Field) Host LUNS Terminal Logon applid(tso) Logon applid(tso) BIND BIND Logoff Logoff UNBIND UNBIND 012 D Tandem Computers Incorporated

155 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. Logon and Logoff Sequences for a Host Application (CMDTYPE LOGON-CHAR and REPDATA Field) Host LUNS Terminal Logonapplid(tso) data(jones/jones) TSOJON BIND BIND Logoff Logoff UNBIND UNBIND Tandem Computers Incorporated D 3

156 LUNS High-Level Flow Diagrams Logon and Logoff for a Host Application (LOGON-INIT) Logon and Logoff for a Host Application (LOGON-INIT) Figure D-3 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 INITJON, specifies CMDTYPE LOGON-INIT. The record also has a PLUNAME field of TSO and a USERDATA field of jones/jones. Figure D-3. Logon and Logoff Sequences for a Host Application (CMDTYPE LOGON-INIT and USERDATA Field) Host INIT-SELF dlu = TSO userdata = LUNS Terminal jones/jones INITJON BIND BIND Logoff Logoff UNBIND UNBIND 014 D Tandem Computers Incorporated

157 LUNS High-Level Flow Diagrams Logon and Logoff for a Host Application (INITSELF-RECEIVED) Logon and Logoff for a Host Application (INITSELF-RECEIVED) Figure D-4 shows a terminal logging on to and logging off from a host application. In the ESS table, the logon record, whose DLU command name is IBM1, specifies 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. Logon and Logoff Sequences for a Host Application (CMDTYPE INITSELF-RECEIVED and USERDATA Field) Host LUNS Terminal INIT-SELF cmd dlu = TSO userdata = jones/jones INIT-SELF cmd dlu = IBM1 BIND BIND TERM-SELF cmd TERM-SELF cmd UNBIND UNBIND Tandem Computers Incorporated D 5

158 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. The STATIC parameter is specified ON Another order record, whose character-coded command is TANDEM and whose STATIC parameter is specified OFF, serves to take down the static path. D Tandem Computers Incorporated

159 LUNS High-Level Flow Diagrams Static Passthrough Figure D-5. Static Passthrough Host LUNS Terminal NOTIFY (Disable) HOST NOTIFY (Enable) Host USS Message 10 Host USS Message 10 Logon applid(tso) Bind Logoff UNBIND Host USS Message 10 Host USS Message 10 CICS Bind Logoff UNBIND Host USS Message 10 NOTIFY (Disable) Host USS Message 10 TANDEM NOTIFY (Enable) Tandem ESS Message 10 Host USS Message Tandem Computers Incorporated D 7

160 LUNS High-Level Flow Diagrams Static Passthrough (This page left intentionally blank) D Tandem Computers Incorporated

161 Appendix E SNAXUTL Error Messages SNAXUTL Error Messages SNAXUTL error messages ordinarily appear in the user s listing file. If the listing file 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 NUMBER: 0060 A GETPOOL error occurred during an attempt to allocate an operand block. SNAXUTL ERROR NUMBER: 0080 A GETPOOL error occurred during an attempt to allocate an object block. SNAXUTL ERROR NUMBER: 0100 A GETPOOL error occurred during an attempt to allocate an operand block. SNAXUTL ERROR NUMBER: 0120 An invalid terminator for a numeric value was encountered. SNAXUTL ERROR NUMBER: 0140 A NUMIN error occurred during the conversion of a numeric value. SNAXUTL ERROR NUMBER: 0160 An invalid terminator following string data was encountered. SNAXUTL ERROR NUMBER: 0180 A command-table data string is too long. SNAXUTL ERROR NUMBER: 0200 A command-table name is too long. SNAXUTL ERROR NUMBER: 0220 Unrecognizable data was found following suboperand parameters in the command table. SNAXUTL ERROR NUMBER: 0240 A command-table parameter for a suboperand is not of the correct data type (that is, it is not %TYPE). SNAXUTL ERROR NUMBER: 0260 A keyword in the command table is too long. SNAXUTL ERROR NUMBER: 0280 An invalid character was found following operand attributes in the command table. SNAXUTL ERROR NUMBER: 0300 Invalid characters were found following an operand name in the command table. SNAXUTL ERROR NUMBER: 0320 An unrecognized parameter for a command object was found in the command table Tandem Computers Incorporated E 1

162 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 NUMBER: 0420 A GETPOOL error occurred during allocation of a queue head for a command table. SNAXUTL ERROR NUMBER: 0460 A premature EOF was encountered during initialization of the input record buffers. SNAXUTL ERROR NUMBER: 0480 An I/O error was encountered during an attempt to create a temporary file for holding process messages. One possible cause of this problem is that there is not enough space on the default volume used when running the SNAXUTL program. SNAXUTL ERROR NUMBER: 0500 An I/O error was encountered during an attempt to open the temporary file used for holding process messages. SNAXUTL ERROR NUMBER: 0520 An OPEN failure occurred on the $RECEIVE file. SNAXUTL ERROR NUMBER: 0540 A READ error occurred during an attempt to read the $RECEIVE file. SNAXUTL ERROR NUMBER: 0560 An I/O error occurred during an attempt to open the command input file. Possible causes are that the file does not exist or that it is not an edit file. SNAXUTL ERROR NUMBER: 0580 An I/O error occurred during the open of a command file. SNAXUTL ERROR NUMBER: 0600 A failure occurred during the initialization of edit file control blocks for the command file. SNAXUTL ERROR NUMBER: 0620 A failure occurred during the open of the listing file. SNAXUTL ERROR NUMBER: 0640 A USESEGMENT failure occurred during initialization of extended storage. E Tandem Computers Incorporated

163 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 NUMBER: 0720 An I/O error occurred on a write to the listing file during error-message processing. The error message might not be displayed. SNAXUTL ERROR NUMBER: 0740 An I/O error occurred during a read of a command record. SNAXUTL ERROR NUMBER: 0760 The record length of a command record is too long. The maximum length is 80 characters. SNAXUTL ERROR NUMBER: 0780 An I/O error occurred when a command record was copied to a listing file. SNAXUTL ERROR NUMBER: 0800 Quotation marks surround a string that has no data. SNAXUTL ERROR NUMBER: 0820 A quoted text string contains no ending quotation mark. That is, the end of the current text line was reached before an ending quotation mark was encountered. Correct the error and rerun the program. SNAXUTL ERROR NUMBER: 0840 An I/O error occurred during a write of a command record to the listing file. SNAXUTL ERROR NUMBER: 0860 An I/O error occurred during a write of a command record to the listing file. SNAXUTL ERROR NUMBER: 0870 An error occurred on an input command record that is being continued. An ampersand (&), the continuation character, was detected, but the last significant character preceding the ampersand was not a comma. Commas must be used to separate operands or the lines of a command that is contained on multiple lines. SNAXUTL ERROR NUMBER: 0880 Nonblank characters were found following an ampersand (&) on a command record. SNAXUTL ERROR NUMBER: 0900 A specified keyword does not match any of the valid keywords for the given operand Tandem Computers Incorporated E 3

164 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. A system name must begin with a backslash (\) followed by an alphabetic character, and then followed by from zero to six alphanumeric characters. SNAXUTL ERROR NUMBER: 0980 An error occurred during processing of the system-name portion of a file name. The first character following the backslash (\) must be alphabetic. SNAXUTL ERROR NUMBER: 1000 An error occurred during processing of the system-name portion of a file name. The first character of the system name must be a backslash (\). SNAXUTL ERROR NUMBER: 1020 An error occurred during processing of the system-name portion of a file name. The system name is too long. The system name must be specified by a backslash (\) followed by an alphabetic character, and then followed by from zero to six alphanumeric characters. SNAXUTL ERROR NUMBER: 1040 One or more characters specified in the volume-name portion of a file name are not valid alphanumeric characters. A volume name must begin with a dollar sign ($) followed by an alphabetic character, and then followed by from zero to six alphanumeric characters. SNAXUTL ERROR NUMBER: 1060 An error occurred during processing of the volume-name portion of a file name. The first character following the dollar sign ($) must be alphabetic. SNAXUTL ERROR NUMBER: 1080 An error occurred during processing of the volume-name portion of a file name. The first character of the volume name must be a dollar sign ($). SNAXUTL ERROR NUMBER: 1100 An error occurred during processing of the volume-name portion of a file name. The length of the volume name is incorrect. The volume name must be specified by a dollar sign ($) followed by an alphabetic character, and then followed optionally by up to six alphanumeric characters. SNAXUTL ERROR NUMBER: 1120 One or more characters specified in the subvolume-name portion of a file name are not valid alphanumeric characters. A subvolume name must begin with an alphabetic character, followed by from zero to seven alphanumeric characters. E Tandem Computers Incorporated

165 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 NUMBER: 1180 One or more characters specified in the rightmost (filename) portion of the file name is not a valid alphanumeric characters. This name must begin with an alphabetic character, followed by from zero to seven alphanumeric characters. SNAXUTL ERROR NUMBER: 1200 An error occurred during processing of the rightmost (filename) portion of a file name. The first character must be alphabetic. SNAXUTL ERROR NUMBER: 1220 An error occurred during processing of the rightmost (filename) portion of a file name. This name is too long. The name must begin with an alphabetic character, followed by from zero to seven alphanumeric characters. SNAXUTL ERROR NUMBER: 1240 An error occurred during the processing of operand text. The text string is too long for the current operand. SNAXUTL ERROR NUMBER: 1260 An error occurred during the scanning of text for the current operand. The operand text contains invalid characters. Only alphanumeric characters, the at sign (@), the pound sign (#), and the dollar sign ($) can be specified. SNAXUTL ERROR NUMBER: 1265 The operand text contained in quotation marks either is too long or represents a null string. Consult the manual for the current operand to determine the correct length. SNAXUTL ERROR NUMBER: 1280 An error occurred during the processing of hexadecimal data for the current operand. An invalid hexadecimal character was detected. Valid characters are 0 through 9 and A through F. SNAXUTL ERROR NUMBER: 1300 An error occurred during the processing of hexadecimal-byte data for the current operand. The specified hexadecimal string is either too short or too long. A valid byte value is specified as %Hnn, where n represents a hexadecimal character Tandem Computers Incorporated E 5

166 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 through SNAXUTL ERROR NUMBER: 1337 A numeric string is too long. Numeric strings that represent integers must consist of from one to five characters (not counting the plus or minus sign) and be within the range through SNAXUTL ERROR NUMBER: 1340 A NUMIN error occurred during the conversion of numeric-string input data. The specified input must be within the range through SNAXUTL ERROR NUMBER: 1380 A system name does not begin with a backslash (\). SNAXUTL ERROR NUMBER: 1400 The first character following the backslash (\) in a system name is not alphabetic. SNAXUTL ERROR NUMBER: 1420 A system name is too long. SNAXUTL ERROR NUMBER: 1440 A nonalphanumeric character was encountered in a system name. SNAXUTL ERROR NUMBER: 1460 A device name does not begin with a dollar sign ($). SNAXUTL ERROR NUMBER: 1480 The first character following the dollar sign ($) in a device name is not alphabetic. SNAXUTL ERROR NUMBER: 1500 The device name is too long. SNAXUTL ERROR NUMBER: 1520 An invalid character was encountered in a device name. SNAXUTL ERROR NUMBER: 1540 The first character of a subdevice name is not a pound sign (#). SNAXUTL ERROR NUMBER: 1560 The first character following the pound sign (#) in a subdevice name is not alphabetic. SNAXUTL ERROR NUMBER: 1580 A subdevice name is too long. SNAXUTL ERROR NUMBER: 1600 An invalid character was encountered in a subdevice name. E Tandem Computers Incorporated

167 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. The first character following the pound sign (#) must be alphabetic. SNAXUTL ERROR NUMBER: 1688 A process name is invalid. The process name contains one or more nonalphanumeric characters. SNAXUTL ERROR NUMBER: 1720 An error occurred during the processing of a hexadecimal-byte string value for the current operand. The string value contains too many characters. SNAXUTL ERROR NUMBER: 1740 An error occurred during the processing of a hexadecimal-byte string value for the current operand. An invalid hexadecimal character was detected. Valid values are 0 through 9 and A through F. SNAXUTL ERROR NUMBER: 1760 An error occurred during the processing of a hexadecimal-byte string value for the current operand. The string value contains an invalid prefix. The hexadecimal characters should be preceded by the prefix %H. SNAXUTL ERROR NUMBER: 1780 An invalid operand data type was encountered. SNAXUTL ERROR NUMBER: 1800 An invalid operand data type was encountered. SNAXUTL ERROR NUMBER: 1820 An EOF was encountered during the reading of operand text. SNAXUTL ERROR NUMBER: 1840 Operand text is not a text block. SNAXUTL ERROR NUMBER: 1860 More than two hexadecimal characters were specified. SNAXUTL ERROR NUMBER: 1880 An invalid hexadecimal digit was specified Tandem Computers Incorporated E 7

168 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 NUMBER: 1980 A premature EOF was encountered during the scan for a suboperand delimiter. SNAXUTL ERROR NUMBER: 2000 An invalid token was retrieved during the scan for a suboperand delimiter. SNAXUTL ERROR NUMBER: 2060 A premature EOF was received during the scan for a left parenthesis before the first suboperand. SNAXUTL ERROR NUMBER: 2080 The maximum number of characters or bytes that can be specified for the current operand has been exceeded. SNAXUTL ERROR NUMBER: 2100 A premature EOF occurred during a scan for an operand name. SNAXUTL ERROR NUMBER: 2120 An error occurred as operands were being scanned for the current command. The specified operand name is invalid. SNAXUTL ERROR NUMBER: 2140 An error occurred as operands were being scanned for the current command. The specified operand name is not unique. SNAXUTL ERROR NUMBER: 2160 An error occurred as operands were being scanned for the current command. An operand name was expected, but some other data was retrieved. Check for duplicate commas, a missing ampersand (&), a premature end of input in the command file, and so on. SNAXUTL ERROR NUMBER: 2180 A premature EOF was encountered during a search for operand text. SNAXUTL ERROR NUMBER: 2184 Parentheses are present for an operand that should not have parentheses. SNAXUTL ERROR NUMBER: 2200 Invalid operand text was encountered. SNAXUTL ERROR NUMBER: 2220 A premature EOF was encountered during a scan for a command object. E Tandem Computers Incorporated

169 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 NUMBER: 2300 An error occurred during processing of the current command. The specified command name is not unique. SNAXUTL ERROR NUMBER: 2320 A premature EOF occurred during a scan for a command name. This problem is usually caused by a missing END command. SNAXUTL ERROR NUMBER: 2340 An invalid command name was found. SNAXUTL ERROR NUMBER: 2360 A premature EOF was encountered during a scan for a command modifier. SNAXUTL ERROR NUMBER: 2380 A premature EOF was encountered during a scan of a command. SNAXUTL ERROR NUMBER: 2400 A required command object is not specified. SNAXUTL ERROR NUMBER: 2420 A command object that is specified should not be present. SNAXUTL ERROR NUMBER: 2440 A premature EOF was encountered during the read of a command. SNAXUTL ERROR NUMBER: 2460 A premature EOF was encountered during the read of a command. SNAXUTL ERROR NUMBER: 2480 An invalid character was found between operands. This character should be a comma. SNAXUTL ERROR NUMBER: 2500 A premature EOF was encountered during the scan for a command delimiter. SNAXUTL ERROR NUMBER: 2520 An invalid token was found following a command. SNAXUTL ERROR NUMBER: 2540 The first command in a command group is not the BEGIN command Tandem Computers Incorporated E 9

170 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. At least one executable command must be placed in a command group following the SELECTFILE command. SNAXUTL ERROR NUMBER: 2575 A command group containing more than one BEGIN command has been encountered. That is, two BEGIN commands have been detected before an END command was detected. SNAXUTL ERROR NUMBER: 2580 The maximum available buffer space for a command group processing has been exceeded. Break up the commands specified in the current command group into multiple groups. SNAXUTL ERROR NUMBER: 2600 Multiple SELECTFILE commands have been detected within the same command group. Only one SELECTFILE command can be specified within a command group, and it must be specified as the first command in the group following the BEGIN command. SNAXUTL ERROR NUMBER: 2605 Multiple BEGIN commands have been detected within the same command group. Only one BEGIN command can be specified within a command group, and it must be the first command in the group. SNAXUTL ERROR NUMBER: 2620 A GETPOOL error occurred during allocation of a buffer to hold internal commands. SNAXUTL ERROR NUMBER: 2640 Duplicate operands were detected in a SELECTFILE command. SNAXUTL ERROR NUMBER: 2660 The required TYPE operand was not specified in the SELECTFILE command. SNAXUTL ERROR NUMBER: 2680 An undefined operand was detected in a SELECTFILE command. SNAXUTL ERROR NUMBER: 2700 An I/O error occurred during an attempt to read an ESS header record for a keysequenced file during a copy operation. E Tandem Computers Incorporated

171 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 NUMBER: 2780 An I/O error occurred during a write of an ESS record to an unstructured file during a copy operation. SNAXUTL ERROR NUMBER: 2800 An error occurred during an open of an ESS key-sequenced file before a copy operation. SNAXUTL ERROR NUMBER: 2820 An error occurred during an open of an ESS unstructured file before a copy operation. SNAXUTL ERROR NUMBER: 2840 An error occurred during an open of a key-sequenced file before a copy operation. SNAXUTL ERROR NUMBER: 2860 An error occurred during an open of an unstructured file before a copy operation. SNAXUTL ERROR NUMBER: 2880 An I/O error occurred during a read of a key-sequenced file during a copy operation. SNAXUTL ERROR NUMBER: 2900 An I/O error occurred during a write to an unstructured file during a copy operation. SNAXUTL ERROR NUMBER: 2920 When an ALLOCATE command was being processed, an error occurred during an attempt to create the key-sequenced file for the SET table. The file specified in the SELECTFILE command already exists. SNAXUTL ERROR NUMBER: 2940 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to create the key-sequenced file for the SET table. SNAXUTL ERROR NUMBER: 2960 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to open the key-sequenced version of the SET table Tandem Computers Incorporated E 11

172 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 NUMBER: 3020 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to create the object version of the SET table. The file already exists. SNAXUTL ERROR NUMBER: 3040 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to create the object version of the SET table. SNAXUTL ERROR NUMBER: 3060 When an ALLOCATE command was being processed, an error occurred during an attempt to create a key-sequenced file. The file specified in the SELECTFILE command already exists. SNAXUTL ERROR NUMBER: 3080 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to create a key-sequenced file. SNAXUTL ERROR NUMBER: 3100 When an ALLOCATE command was being processed, an error occurred during an attempt to open the key-sequenced file. SNAXUTL ERROR NUMBER: 3120 When an ALLOCATE command was being processed, an error occurred during an attempt to write the header record to the key-sequenced file. SNAXUTL ERROR NUMBER: 3140 When an ALLOCATE command was being processed, an error occurred during an attempt to write the trailer record to the key-sequenced file. SNAXUTL ERROR NUMBER: 3160 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to create the unstructured file. The object file already exists. SNAXUTL ERROR NUMBER: 3180 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to create the unstructured file. E Tandem Computers Incorporated

173 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 NUMBER: 3240 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to open the key-sequenced file. SNAXUTL ERROR NUMBER: 3260 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to write the header record to the key-sequenced file. SNAXUTL ERROR NUMBER: 3280 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to write the trailer record to the key-sequenced file. SNAXUTL ERROR NUMBER: 3300 When an ALLOCATE command was being processed, an error occurred during an attempt to create the unstructured file. The unstructured file corresponding to the key-sequenced file specified in the SELECTFILE command already exists. SNAXUTL ERROR NUMBER: 3320 When an ALLOCATE command was being processed, an I/O error occurred during an attempt to create the unstructured file. SNAXUTL ERROR NUMBER: 3340 Too many operands were specified in the ALLOCATE command. SNAXUTL ERROR NUMBER: 3360 The extent size specified in an ALLOCATE command is invalid. Valid values are from 1 through SNAXUTL ERROR NUMBER: 3380 An unrecognized file type was encountered during the processing of an ALLOCATE command. Contact your systems programmer for assistance. SNAXUTL ERROR NUMBER: 3400 Duplicate operands were detected in an ADD ESSCMD command. SNAXUTL ERROR NUMBER: 3420 An error occurred during the processing of the ADD ESSCMD command. The required CMDTYPE operand was not specified. SNAXUTL ERROR NUMBER: 3421 An error occurred during the processing of the ADD ESSCMD command. CMDTYPE ORDER was specified, but neither the STATIC operand nor the TERMSELF operand were specified. Either the STATIC operand or the TERMSELF operand is required with CMDTYPE ORDER Tandem Computers Incorporated E 13

174 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 NUMBER: 3460 An error occurred during the processing of the ADD ESSCMD command. The GATEPU operand is invalid when either GATELINE or GATELU has been specified. SNAXUTL ERROR NUMBER: 3461 An error occurred during the processing of the ADD ESSCMD command. The GATEPU operand was specified with SENDHOST N. This combination is invalid unless CMDTYPE ORDER is specified. SNAXUTL ERROR NUMBER: 3480 An error occurred during the processing of the ADD ESSCMD command. The GATELU operand is invalid when either GATELINE or GATEPU has been specified. SNAXUTL ERROR NUMBER: 3481 An error occurred during the processing of the ADD ESSCMD command. The GATELU operand was specified with SENDHOST N. This combination is invalid unless CMDTYPE ORDER is specified. SNAXUTL ERROR NUMBER: 3500 An error occurred during the processing of the ADD ESSCMD command. The pound sign (#) on the PLUNAME operand is invalid with SENDHOST Y. SNAXUTL ERROR NUMBER: 3520 An error occurred during the processing of the ADD ESSCMD command. A pound sign (#) on the PLUNAME operand is required with SENDHOST N. SNAXUTL ERROR NUMBER: 3540 An error occurred during the processing of the ADD ESSCMD command. The PLUNAME operand is invalid with SENDHOST Y and CMDTYPE LOGON- CHAR. SNAXUTL ERROR NUMBER: 3560 An error occurred during the processing of the ADD ESSCMD command. The PLUNAME operand is invalid with CMDTYPE ORDER. SNAXUTL ERROR NUMBER: 3580 An error occurred during the processing of the ADD ESSCMD command. The PLUNAME operand is invalid with CMDTYPE LOGOFF. E Tandem Computers Incorporated

175 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. The BINDENTRY operand is invalid when SENDHOST Y and CMDTYPE LOGON- CHAR are both specified. SNAXUTL ERROR NUMBER: 3740 An error occurred during the processing of the ADD ESSCMD command. The BINDENTRY operand is invalid with CMDTYPE ORDER. SNAXUTL ERROR NUMBER: 3760 An error occurred during the processing of the ADD ESSCMD command. The BINDENTRY operand is invalid with CMDTYPE LOGOFF. SNAXUTL ERROR NUMBER: 3780 An error occurred during the processing of the ADD ESSCMD command. The REPDATA operand is invalid with USERDATA. SNAXUTL ERROR NUMBER: 3840 An error occurred during the processing of the ADD ESSCMD command. The REPDATA operand requires CMDTYPE LOGON-CHAR. SNAXUTL ERROR NUMBER: 3860 An error occurred during the processing of the ADD ESSCMD command. The REPDATA operand is invalid with SENDHOST N. SNAXUTL ERROR NUMBER: 3880 An error occurred during the processing of the ADD ESSCMD command. The REPDATA operand is invalid with CONCDATA. SNAXUTL ERROR NUMBER: 3900 An error occurred during the processing of the ADD ESSCMD command. The CONCDATA operand is invalid with SENDHOST Y. SNAXUTL ERROR NUMBER: 3920 An error occurred during the processing of the ADD ESSCMD command. CONCDATA is invalid with CMDTYPE ORDER. SNAXUTL ERROR NUMBER: 3940 An error occurred during the processing of the ADD ESSCMD command. CONCDATA is invalid with CMDTYPE LOGOFF. SNAXUTL ERROR NUMBER: 3960 An error occurred during the processing of the ADD ESSCMD command. The CONCDATA text length is too large. The combined text lengths of the CONCDATA and USERDATA operands cannot exceed 1880 bytes Tandem Computers Incorporated E 15

176 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 INITSELF- RECEIVED must be specified with SENDHOST Y. SNAXUTL ERROR NUMBER: 4100 An error occurred during the processing of the ADD ESSCMD command. Both the STATIC and TERMSELF operands require CMDTYPE ORDER. SNAXUTL ERROR NUMBER: 4120 An error occurred during the processing of the ADD ESSCMD command. The value specified for the RECSIZE operand is invalid. Valid values are from 1 through 4096 bytes. SNAXUTL ERROR NUMBER: 4140 A GETPOOL error occurred during processing of the REPDATA operand for the ADD ESSCMD command. SNAXUTL ERROR NUMBER: 4160 A GETPOOL error occurred during processing of the REPDATA operand for the ADD ESSCMD command. SNAXUTL ERROR NUMBER: 4180 A GETPOOL error occurred during processing of the CONCDATA operand for the ADD ESSCMD command. SNAXUTL ERROR NUMBER: 4200 A GETPOOL error occurred during processing of the CONCDATA operand for the ADD ESSCMD command. SNAXUTL ERROR NUMBER: 4220 A GETPOOL error occurred during processing of the USERDATA operand for the ADD ESSCMD command. SNAXUTL ERROR NUMBER: 4320 When an ADD ESSCMD command was being processed, an I/O error occurred during an attempt to open the key-sequenced file. SNAXUTL ERROR NUMBER: 4340 When an ADD ESSCMD command was being processed, an I/O error occurred during an attempt to perform a KEYPOSITION of a key-sequenced file to the location of the header record. SNAXUTL ERROR NUMBER: 4360 When an ADD ESSCMD command was being processed, an I/O error occurred during an attempt to perform a READUPDATE on a key-sequenced file to read in the header record. E Tandem Computers Incorporated

177 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 NUMBER: 4400 When an ADD ESSCMD command was being processed, an I/O error occurred during an attempt to write an ESS record to the key-sequenced file. SNAXUTL ERROR NUMBER: 4420 When an ADD ESSCMD command was being processed, an error occurred during an attempt to perform a KEYPOSITION on a key-sequenced file before writing the updated header record back into the file. SNAXUTL ERROR NUMBER: 4440 When an ADD ESSCMD command was being processed, an I/O error occurred during an attempt to rewrite the ESS header record back into the key-sequenced file. SNAXUTL ERROR NUMBER: 4460 An invalid operand was detected in an ADD ESSCMD command. SNAXUTL ERROR NUMBER: 4480 An invalid operand was detected in an ADD ESSCMD command. SNAXUTL ERROR NUMBER: 4500 Invalid operand combinations were detected in an ADD ESSCMD command. SNAXUTL ERROR NUMBER: 4510 An I/O error occurred during processing of the ADD ESSMSG command. The message name being added already exists. SNAXUTL ERROR NUMBER: 4520 An I/O error occurred during an attempt to write an ESS message record to the ESS file. This error occurs when an ESS table has exceeded its allocated space. This message might also be issued when other file-system errors occur. SNAXUTL ERROR NUMBER: 4530 When an ADD ESSMSG command was being processed, the ESS message was found to have the same name as an existing ESS character-coded command. An ESS message cannot have the same name as an ESS command. SNAXUTL ERROR NUMBER: 4540 When an ADD ESSMSG command was being processed, an I/O error occurred on an attempt to open the ESS key-sequenced file. SNAXUTL ERROR NUMBER: 4560 When an ADD ESSMSG command was being processed, an error occurred during Tandem Computers Incorporated E 17

178 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 NUMBER: 4620 When an ADD ESSMSG command was being processed, an I/O error occurred during an attempt to perform a WRITEUPDATE to rewrite the updated header record back into the key-sequenced file. SNAXUTL ERROR NUMBER: 4640 Duplicate operands were detected in the ADD ESSMSG command. SNAXUTL ERROR NUMBER: 4660 The MSGTEXT operand was not specified for the ADD ESSMSG command. This operand is required. SNAXUTL ERROR NUMBER: 4680 An invalid operand was detected in the ADD ESSMSG command. SNAXUTL ERROR NUMBER: 4700 An invalid operand was detected in the ADD ESSMSG command. SNAXUTL ERROR NUMBER: 5020 When the ADD SETESS command was being processed, an I/O error occurred during an attempt to open the SET table file. SNAXUTL ERROR NUMBER: 5040 When an ADD SETESS command was being processed, an I/O error occurred during an attempt to read the header record from the SET table file. SNAXUTL ERROR NUMBER: 5060 When an ADD SETESS command was being processed, an I/O error occurred during an attempt to read records from the SET table file. SNAXUTL ERROR NUMBER: 5080 An error occurred during processing of the DEFAULTTABLE operand of the ADD SETESS command. A default ESS table was specified for the current SET table when another default ESS table has already been specified. Only one default ESS table can be specified within a SET table. SNAXUTL ERROR NUMBER: 5100 When an ADD SETESS command was being processed, an I/O error occurred during the open of the key-sequenced file. E Tandem Computers Incorporated

179 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 NUMBER: 5160 When an ADD SETESS command was being processed, an I/O error occurred on an attempt to write a record to the key-sequenced file. The record being added already exists. SNAXUTL ERROR NUMBER: 5180 When an ADD SETESS command was being processed, an I/O error occurred on an attempt to write a record to the key-sequenced file. SNAXUTL ERROR NUMBER: 5200 When an ADD SETESS command was being processed, an error occurred during a KEYPOSITION of the key-sequenced file to the header record. SNAXUTL ERROR NUMBER: 5220 When an ADD SETESS command was being processed, an I/O error occurred during the WRITEUPDATE of a header record to the key-sequenced file. SNAXUTL ERROR NUMBER: 5240 Duplicate operands were detected in the ADD SETESS command. SNAXUTL ERROR NUMBER: 5260 An error occurred during processing of the ADD SETESS command. The required FILENAME operand was omitted. SNAXUTL ERROR NUMBER: 5280 An unrecognized operand was detected in the ADD SETESS command. SNAXUTL ERROR NUMBER: 5300 An unrecognized operand was detected in the ADD SETESS command. SNAXUTL ERROR NUMBER: 5660 An error occurred during processing of the DELETE command. An attempt was made to delete the header record for the file specified in the SELECTFILE command, but this is an invalid operation. SNAXUTL ERROR NUMBER: 5680 An error occurred during processing of the DELETE command. An attempt was made to delete the trailer record for the file specified in the SELECTFILE command, but this is an invalid operation. SNAXUTL ERROR NUMBER: 5700 When a DELETE command was being processed, an open failure occurred on the key-sequenced SET table Tandem Computers Incorporated E 19

180 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 NUMBER: 5760 When a DELETE command was being processed, an I/O error occurred during a KEYPOSITION to position SET table file pointers to a record to be deleted. SNAXUTL ERROR NUMBER: 5780 When a DELETE command was being processed, an attempt was made to delete a nonexistent record from the SET table. SNAXUTL ERROR NUMBER: 5800 When a DELETE command was being processed, an I/O error occurred during an attempt to delete a record from the SET table. SNAXUTL ERROR NUMBER: 5820 When a DELETE command was being processed, an I/O error occurred during a KEYPOSITION to position file pointers to the header record in the SET table. SNAXUTL ERROR NUMBER: 5840 When a DELETE command was being processed, an I/O error occurred during an attempt to update the header record in the SET table. SNAXUTL ERROR NUMBER: 5860 When a DELETE command was being processed, an I/O error occurred during a KEYPOSITION of the ESS file to a record that is to be deleted. SNAXUTL ERROR NUMBER: 5880 When a DELETE command was being processed, an I/O error occurred during a read of an ESS record to be deleted. The error might have been caused by an attempt to delete a record that does not exist. SNAXUTL ERROR NUMBER: 5900 A record in the ESS table that was to be deleted by a DELETE command does not exist. SNAXUTL ERROR NUMBER: 5920 When the DELETE command was being processed, an I/O error occurred during a KEYPOSITION of the ESS table to a record that is to be deleted. SNAXUTL ERROR NUMBER: 5940 When a DELETE command was being processed, an I/O error occurred on an attempt to delete a record from the ESS table. SNAXUTL ERROR NUMBER: 5960 When a DELETE command was being processed, an I/O error occurred during a KEYPOSITION of the file to an ESS message record. E Tandem Computers Incorporated

181 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 NUMBER: 6040 When a DELETE command was being processed, an I/O error occurred during a KEYPOSITION of the ESS table to the header record. SNAXUTL ERROR NUMBER: 6060 When a DELETE command was being processed, an I/O error occurred on a read of the header record of the ESS table. SNAXUTL ERROR NUMBER: 6080 When a DELETE command was being processed, an I/O error occurred during a KEYPOSITION of the ESS table to the header record. SNAXUTL ERROR NUMBER: 6100 When a DELETE command was being processed, an I/O error occurred during an update of the header record of the ESS file. SNAXUTL ERROR NUMBER: 6280 Multiple operands were detected in the DELETE command. Only the name of the record to be deleted can be specified. SNAXUTL ERROR NUMBER: 6300 An invalid operand was detected in the DELETE command. Only the name of the record to be deleted can be specified. SNAXUTL ERROR NUMBER: 6320 The file specified in the SELECTFILE command is not of type SET or ESS. This is an internal error. SNAXUTL ERROR NUMBER: 6340 An I/O error occurred during an attempt to write an error message to the program listing file. The error message might not be displayed. SNAXUTL ERROR NUMBER: 6360 An invalid command was detected. SNAXUTL ERROR NUMBER: 6380 An I/O error occurred on the temporary message file during an attempt to copy process messages from the temporary file to the listing file. SNAXUTL ERROR NUMBER: 6400 An error occurred during the open of an unstructured file after LUNS deactivation had been requested Tandem Computers Incorporated E 21

182 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. Check that SNAXUTL was added as an APPL with PASSWORD SNAXUTL Remember that passwords must be right-filled with blank spaces, up to a total of eight characters. SNAXUTL ERROR NUMBER: 6440 LUNS has returned an error in response to a CONNECT request. Check that SNAXUTL was added as an APPL with APPLTYPE LUNSAPPL. SNAXUTL ERROR NUMBER: 6450 A WRITEREAD error occurred while a deactivation request was being sent to LUNS. Try the operation again. If the problem persists, consult your Tandem representative. SNAXUTL ERROR NUMBER: 6460 LUNS returned an error in response to a deactivation request. Check that the ESS file named on the SELECTFILE command does not conflict with file names that are not ESS table file names. SNAXUTL ERROR NUMBER: 6470 A WRITEREAD error occurred while an activation request was being sent to LUNS. Try the operation again. If the problem persists, consult your Tandem representative. SNAXUTL ERROR NUMBER: 6480 LUNS returned an error in response to an activation request. Try to use the ESS table named in the SELECTFILE command. If the message ESS TABLE TEMPORAILY DEACTIVATED BY SNAXUTL is displayed, issue the following SCF command: ALTER SUBSYS $SSCP,SETTAB table-name where table-name is the name of the currently active SET table. If the problem persists, consult your Tandem representative. E Tandem Computers Incorporated

183 Appendix F SNAX/XF Default BIND Default SNAX/XF BIND Bytes and Values SNAX/XF sends a default BIND if a BINDENTRY parameter is not specified in an SCF 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. Summary of Default SNAX/XF BIND Values Byte Value Explanation 0 %H31 BIND command 1 %H01 BIND type and format 2 %H03 FMPROF 3 %H03 TSPROF 4 %HB1 PRIPROT 5 %H90 SECPROT 6-7 %H3080 %H7080 COMPROT (SNA devices) (6530 devices) 8 %H00 SSNDPAC 9 %H00 SRCVPAC RUSIZES (see Bytes below) 12 %H00 PSNDPAC 13 %H00 reserved PSERVIC (see Bytes below) 26 %H00 ENCR 27 %H00 PLUNAME length Bytes The values for RUSIZES specify the maximum length of data (in bytes) that can be sent by primary and secondary LUs. The values exist as four hexadecimal digits. The two leftmost digits apply to the secondary LU, and the two rightmost digits apply to the primary LU. SNAX/XF always uses internal default values for calculating the maximum send and receive lengths Tandem Computers Incorporated F 1

184 SNAX/XF Default BIND Default SNAX/XF BIND Bytes and Values Bytes 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. %H70 (6530 CRT protocol) %H71 (6530 ITI protocol) %H %H (6530 ITI or CRT protocol) %H (6530 PRT protocol) %H (3178 all models) %H F (3262, 3268, 3284, 3286, 3287, 3288, 3289 all models.) (For values pertaining to devices 3275, 3276, 3277, and 3278, see charts below.) %H (3279 models 2A, 2B, S2A, S2B, and O2X) %H F (3279 models 3A, 3B, S3G, and O3X) %H F (5100 all models) 25 %H00 PSERVIC Values for 3275 and 3276 Devices Byte Device/Model(s) 3275/ / /2/ /3/ /4/14 20 %H0C %H18 %H18 %H18 %H18 21 %H28 %H50 %H50 %H50 %H50 22 %H0C %H18 %H18 %H20 %H2B 23 %H50 %H50 %H50 %H50 %H50 24 %H7F %H02 %H7F %H02 %H7F PSERVIC Values for 3277 and 3278 Devices Byte Device/Model 3277/1 3277/2 3278/1 3278/2 3278/3 3278/4 3278/5 20 %H0C %H18 %H0C %H18 %H18 %H18 %H18 21 %H50 %H50 %H28 %H50 %H50 %H50 %H50 22 %H0C %H18 %H0C %H18 %H20 %H2B %H1B 23 %H50 %H50 %H50 %H50 %H50 %H50 %H84 24 %H7F %H02 %H7F %H02 %H7F %H7F %H7F F Tandem Computers Incorporated

185 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. For most IBM SNA abbreviations in this glossary, only the spelling of the abbreviation is given; refer to the IBM manuals noted above for more information about IBM terms. abend. Abnormal termination or abnormal end of task. ACTLU. Activate logical unit. APPL object type. A Tandem object type that defines an object as an application logical unit. application program. A software program written for or by a user to fulfill a specific purpose. APC. See SNAX/APC. ASCII. American National Standard Code for Information Interchange. An 8-bit code representing characters and control codes. One of two major codes used to represent and exchange data. See also EBCDIC. BIND. An SNA command that establishes a session between two logical units. BIND image. A description of session parameters passed by the SSCP to the PLU. BIND table. A table containing one or more BIND images. BIU. Basic information unit. block mode. A mode of operation in which computer programs and devices exchange data in quantities greater than the line size of the particular device. boundary function. The functionality of a subarea node that provides for the support of locally attached peripheral nodes. character set. A defined collection of character representations valid for a particular program, printer, or language. Characters may be stored in ASCII or EBCDIC, and may be displayed on-screen or printed in a variety of languages. In SNAX/XF or other codes, characters must be stored in EBCDIC to implement National Character Support. CICS. Customer Information Control System. CINIT. Control initiate, an SNA request. cluster controller. A device that controls access to a group of terminals or printers. command file. A file that serves as a source for command input Tandem Computers Incorporated Glossary 1

186 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. A device that directs the transmission of data over the data links of a network. Its operation may be controlled by a program executed in a processor to which the controller is connected, or it may be controlled by a program executed within the device. condition code. A mechanism within the Tandem NonStop system that indicates, upon completion of each file system procedure call, whether or not the call was completed successfully. The three condition code states include: condition code less than (CCL or <), condition code equal (CCE or =), and condition code greater than (CCG or >). configuration. The definition or alteration of characteristics of an object. Creator process. An ancillary process to SNAX/XF that can accept session establishment requests for TACL and Pathway application processes. CRIF. Creator interface. CRT protocol. A high-level 3270 protocol that supports block-mode communications with display terminals and printers. The CRT protocol allows the calling process to communicate with a device as if the device were an ordinary file. CTERM. SNA Control terminate request. DBCS. Double Byte Character Set; a character set in which each character in the set is represented by two bytes (for example, Kanji is a double-byte character set). Destination Logical Unit. (DLU) An LU that receives an SNA command. DFC. Data flow control (one of the SNA functional layers). Distributed Systems Management (DSM). A set of software tools used to manage Tandem NonStop systems and Expand networks. DSM provides a uniform interface for monitoring and controlling all components of a Tandem network. DSM tools include the Viewpoint console application, the Subsystem Control Facility (SCF) for data communications subsystems, the Subsystem Programmatic Interface (SPI), the Event Management Service (EMS), the Distributed Name Service (DNS), and token-oriented programmatic interfaces to the management processes for various Tandem subsystems. DLU. See Destination Logical Unit. Enhanced System Services table (ESS table). Similar to IBM USS tables, a configuration table used by SNAX/XF with additional functionality that allows a system programmer to set up a particular SNA configuration. error. A condition that causes a command or other operation to fail. Glossary Tandem Computers Incorporated

187 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). A Tandem product comprised of a collection of processes, tools, and interfaces that support the reporting and retrieval of event information. It provides for different event descriptions for interactive and programmatic interfaces, lets an operator or application select specific event-message data, and allows flexible distribution of event messages within a system or network. event message. An SPI message that describes an event occurring in the system or network. Compare command message or response message. Extended Binary Coded Decimal Interchange Code. An 8-bit coded character set. One of two major codes used to represent and exchange data. See also ASCII. Expand network. A network consisting of Tandem systems interconnected by communication links and supported by Expand software. fault-tolerant. An attribute of the Tandem NonStop system whereby a processor failure does not result in loss of data or function. hexadecimal. A numerical value in base 16; digits go from 0 to F. Tandem prefaces hexadecimal notation with %H. high-level SNA 3270 interface. A SNAX/XF application interface that provides for the establishment of LU-LU sessions. High-level SNA 3270 interface supports the CRT and ITI protocols, which simplify communications between an application process and an SNA 3270-type device. high PIN. A process identification number (PIN) that is greater than 255. See also low PIN. HLS. See SNAX/HLS. host. A general-purpose processor, such as an IBM 3033, that contains an SSCP, PU Type 5 logic, and one or more LUs representing different applications or application subsystems. INIT-SELF command. An SNA command issued by an initiating LU to request SSCP assistance in establishing an LU-LU session with the named destination LU. I/O process. A system process that manages I/O hardware. Applications use the file system to send requests to I/O processes. IMS. IBM Information Management System. ITI protocol. See Interactive Terminal Interface protocol. Interactive Terminal Interface protocol. A high-level 3270 protocol that simplifies communications between an application process and a 3270-type device. The ITI Tandem Computers Incorporated Glossary 3

188 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). An entity representing a logical port that provides access to the services of an SNA network, typically for communications between end users such as terminals, printers, or application programs. Each LU supports a session between two end users (LU-LU session). SNA categorizes LUs according to the type of end-user services that the LU provides. low PIN. A process identification number that ranges from 0 through 254. See also high PIN. LU. Logical unit. LUNS. LU Network Services. National Character Support (NCS). An implementation within National Language Support where one character set may be translated to another. These sets may be machinedependent (such as ASCII to EBCDIC) or language-dependent (such as Katakana to Swedish). National Language Support (NLS). An architecture that defines how a system operates independently of language constraints, as well as how to create a particular language version for that system. The architecture may also define how multiple language versions of the system may run simultaneously on the same node or network, with the application end-user choosing the language. NAU. Network addressable unit. NC. Network control. NCS. National character support. network. A group of interconnected computer systems and devices, and the hardware and software used to connect them. network address. In SNA, an address, consisting of subarea and element fields, that identifies a network addressable unit. Subarea nodes use network addresses; peripheral nodes use local addresses. The boundary function in the subarea node to which a peripheral node is attached transforms local addresses to network addresses and vice versa. NLS. National language support. node. In SNA, an end point of a link or junction common to two or more links in a network. There are peripheral and subarea nodes. Nodes include host processors, communication controllers, cluster controllers, or terminals, and vary in routing and other functional capabilities. Each SNA node must contain at least one NAU. There are five Node Types. Glossary Tandem Computers Incorporated

189 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. In Tandem terminology, an object is an entity that can be configured, controlled, and inquired about by the operator. passthrough. A function of the SNAX/XF line access software that allows a 3270 terminal attached to a Tandem system to switch between Tandem and IBM applications. Passthrough lets a host application program communicate with SNA devices connected to a Tandem system as though the devices were connected to a cluster controller. Passthrough is enabled by configuration and startup procedures; it is never directly invoked by application software. Passthrough can also be used to perform service or management tasks that are incidental to SNA applications on a Tandem system. Passthrough sessions. An SNA session used in Passthrough. Pathway. A transaction processing system that supplies the programs, procedures, and structures necessary to produce user-written applications. The CRT protocol is used by Pathway. PC. Path control. PDN. Public Data Network. peripheral node. A node consisting of a physical unit type 1 (node type 1) or a physical unit type 2 (node type 2) device that is directly connected and under the control of an adjacent subarea node. Routing to a peripheral node occurs through the local address only and is not affected by the network addressing scheme. Boundary function assistance is provided by the adjacent subarea node. physical connection. The media (hardware and software) through which data is passed between origin and destination subareas. Physical connections between a host processor and a communication controller in an SNA network can be made by either an SDLC link or a channel attachment. physical unit (PU). That part of a device (hardware or software) that provides control functions for its own node and for the other less intelligent device nodes attached to the PU. Every device or logical unit in an SNA network is associated with a physical unit. PID. Process identifier. PLU. Primary logical unit Tandem Computers Incorporated Glossary 5

190 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. The The Tandem NonStop Kernel is a collection of cooperating processes that use a common message system. process identification number (PIN). An unsigned integer that identifies a process in a particular processor. process pair. Two processes that include an active primary process, and a secondary backup process in another CPU that is ready to take over if the primary process fails. programmatic interface. A means for a program to communicate with another program. PRT. See PRT protocol. PRT protocol. A high-level 3270 protocol that allows a calling process to send information one line at a time to an SNA 3270-type printer. The calling process sends text only; SNAX/XF adds any necessary printer control characters to the outgoing text. PS. Presentation services (one of the SNA functional layers). PU. See physical unit. PUCP. Physical unit control point. PU object type. A Tandem object type that defines the various adjacent SNA physical units with which SNAX/CDF can communicate. PVC. Permanent virtual circuit. QLLC. IBM Qualified Logical-Link Control protocol. response message. An SPI message sent from a subsystem to an application program in reaction to a command message. A message always contains entire response records (a single response record cannot be split across multiple messages). If there are multiple records in a response message, each record is enclosed in a data list. return code. A value returned at the completion of a command, indicating whether the command was successful and, if not, the reason for failure. SCF. See Subsystem Control Facility. SCP. See Subsystem Control Point. SDLC. Synchronous data link control. secondary logical unit (SLU). One of the two LUs involved in an LU-LU session. The SLU functions under the control of the PLU, and accepts an incoming BIND request from a PLU. session. An SNA session is a temporary data path consisting of a physical and a logical connection between two LUs in separate domains for information exchange. To Glossary Tandem Computers Incorporated

191 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. SNAX Application Logical Unit. A SNAX/XF application protocol that provides the functions of the lower two SNA layers (data link control and path SNAX/APC. SNAX/APC is a high-level programmatic interface that allows Tandem applications to communicate with LU 6.2 applications running in an SNA network. SNAX Creator-2 process. An ancillary process to SNAX/XF that can accept session-establishment requests for TACL and Pathway application processes. The SNAX Creator-2 process allows users to create a configuration database by using SCF. SNAX/HLS. SNAX/HLS is a Tandem interface that allows Tandem applications to communicate with non-3270 intelligent SNA devices and IBM host-resident software products. SNAXLink. A Tandem product comprised of both hardware and software that provides a direct channel link between a Tandem system and several types of IBM systems. SNAXLink can also be used with IBM channel-compatible systems that contain VTAM and SNA support. SNAX/XF. SNAX/XF is a Tandem communications access method that implements part of the IBM Systems Network Architecture (SNA). SNAX/XF allows applications on a Tandem system to communicate with attached SNA devices and with programs residing on a host system. SNP. See subarea node process. SPI. See Subsystem Programmatic Interface. SPI message. A message specially formatted by the SPI procedures for communication between a management application and a subsystem, or between one subsystem and another. The message consists of a collection of tokens. Note that an SPI message is a single block of information sent at one time as one interprocess message. There are two types of SPI messages, distinguished by different sets of tokens in the header: command and response messages, and event messages. spooler. A process and storage area used when information is gathered faster than it can be used. For example, a print spooler holds large amounts of information to be printed and then sends it to the printer one unit at a time. SSCP. See system services control point. structure. A data item with multiple fields, possibly of different types Tandem Computers Incorporated Glossary 7

192 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. The SNP provides the equivalent cross-domain support of an SNA SSCP in addition to the path control functions required of an adjacent subarea node. The SNP provides the functions of all the SNA layers except the Data Link Control layer. subsystem. A process or collection of processes that give users access to a set of related resources or services. A subsystem typically controls a cohesive set of objects. Subsystem Control Facility (SCF). A Tandem interface product that allows users to configure, control, and examine the status and configuration of selected Tandem data communications subsystems. Subsystem Control Point (SCP). A process that receives and redistributes Subsystem Programmatic Interface messages to targeted data communications subsystems. Subsystem Programmatic Interface (SPI). Part of the DSM family of software products. A standard set of programmatic message formats and protocols that can be used to exchange event information and commands between various subsystems and userwritten or Tandem-written processes. SUT. See site update tape. SVC. Switched virtual circuit. system generation (SYSGEN). Tandem s system generation program that allows a system operator to tailor the operating system to the requirements of an installation for a specific hardware and software configuration. The SYSGEN process can be divided into three phases: configuring the system, generating the operating system, and installing the operating system. system services control point (SSCP). The focal point within an SNA subarea network for managing the configuration, coordinating network-operator and problemdetermination requests, and providing directory support and other session services for end users of the network. Multiple SSCPs, cooperating as peers, can divide the network into domains of control, with each SSCP having a hierarchical control relationship to the physical units (PUs) and logical units (LUs) within its domain. SYSGEN. See system generation. TACL. See Tandem Advanced Command Language. Tandem Advanced Command Language (TACL). A Tandem product that provides the user interface to the operating system. The ITI protocol is used by the Tandem command interpreter TACL. Glossary Tandem Computers Incorporated

193 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. In event messages, a token normally represents an item of information about an event or about the event message itself. TS. Transmission subsystem; also transmission services. UNBIND. An SNA command that deactivates a session between two logical units. VTAM. Virtual Telecommunications Access Method. X.25. A CCITT recommendation for the interface between data terminal equipment and packet-switching networks; it is also referred to as Recommendation X.25. XID. Exchange identification Tandem Computers Incorporated Glossary 9

194 Glossary (This page left intentionally blank) Glossary Tandem Computers Incorporated

195 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-8 Adding BIND table records to the SET table 2-18 Adding ESS table records to the SET table 2-18 Adding system messages 2-15 Adding user messages 2-15 All-purpose logoff record 2-12 ALTER command (SCF) SETTAB attribute 2-17 SUBSYS attribute 2-17 activate SET table example 2-17 replace SET table example 2-17 Application example 3-1/14 ASSOCIATE attribute example Tandem Computers Incorporated Index 1

196 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 tables creating new tables 2-3 Enhanced System Services table 1-4 how LUNS uses 1-9 Session Establishment Table 1-4 table object file 2-3 table source file 2-3 Index Tandem Computers Incorporated

197 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-30 PASSWORD specification 2-30 process accessor ID 2-29 RUN command 2-30 security issues 2-29 starting 2-29 startup security issues 2-29 STATUSOFF specification 2-30 subdevice name specification 2-30 symbolic name specification 2-30 using 2-29 CRT protocol Pathway 2-8 D Default BIND image F-1 Destination Logical Unit 1-6, 1-7, 2-2, 2-4, 2-10, 2-11 Devices intelligent 1-1 Disconnecting the Creator process from LUNS example 2-21 DLU See Destination Logical Unit Tandem Computers Incorporated Index 3

198 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 , 2-4 ESS system messages B-1 ESS table See Enhanced System Services table ESSMSG modifier MSGTEXT operand 2-15 Establishing a host SSCP-LU path 2-13 Example application activating the SET table (Part 2) 3-12 ADD APPL command (Part 1) 3-6 ADD APPL usage (Part 2) 3-12 ADD ESSCMD usage (Part 1) 3-3 ADD ESSCMD usage (Part 2) 3-11 ADD ESSMSG usage(part 1) 3-3 ADD LINE usage (Part 1) 3-6 ADD LINE usage (Part 2) 3-12 ADD LU usage (Part 1) 3-6 ADD LU usage (Part 2) 3-12 ADD PU usage (Part 1) 3-6 ADD PU usage (Part 2) 3-12 Index Tandem Computers Incorporated

199 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 file for SNAXUTL (Part 1) 3-3 command file for SNAXUTL (Part 2) 3-11 components (Part 1) 3-1 configuration assumptions (Part 1) 3-3 configuration assumptions (Part 2) 3-10 configuring the primary line (Part 1) 3-6 configuring the system (Part 1) 3-6 creating the ESS table (Part 1) 3-3 defining the gateway line (Part 1) 3-6 dynamic modification ESS table 3-13 EXPAND link 3-8 modifying the ESS table 3-13 modifying the HELP menu 3-13 operational assumptions (Part 1) 3-2 operational assumptions (Part 2) 3-10 Part 1 3-1/7 Part 2 3-8/13 PATHWAY 3-8 PATHWAY parameters (Part 2) 3-11 PROTOCOL attribute usage (Part 1) 3-6 RUN command (Part 1) 3-7 RUN command (Part 2) 3-13 sample coding (Part 1) 3-3 sample HELP menu (Part 1) 3-3 SELECTFILE command (Part 1) 3-3, 3-5 SELECTFILE command (Part 2) Tandem Computers Incorporated Index 5

200 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 segments 2-10 F Finding an assigned ESS table B-1 G GATELINE operand format 2-10 GATELU operand format 2-10 GATEPU operand format 2-10 Gateway lines local system 2-9 remote system 2-9 General information SNAX/XF Utility A-1 H Host character-coded logoff command 2-13 Host system logon records 2-9 Index Tandem Computers Incorporated

201 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-RECEIVED) D-5 host application (LOGON-CHAR) D-2 host application (LOGON-INIT) D-4 static passthrough D-6 Logon records 1-6 creating 2-4 Destination Logical Unit 1-6 GATELINE operand 2-9 GATELU operand 2-9 GATEPU operand 2-9 Pathway 1-7, 2-8 TACL 1-6 to host Tandem Computers Incorporated Index 7

202 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 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) Katakana and A-11 LUNS See LU Network Services M Menus 1-1 Message display 1-1 Message records 1-6, 2-15 user messages 2-15 N Naming user messages 2-15 Index Tandem Computers Incorporated

203 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 operand 2-10 CMDTYPE operand 2-10 INITSELF-RECEIVED value 2-10 LOGON-CHAR value 2-10 LOGON-INIT value 2-10 LOGMODE table 2-10 logon records 2-9 PLUNAME operand 2-10 RECSIZE operand 2-10 REPDATA operand 2-10 Replacement DLU 2-11 USERDATA operand 2-10 Passthrough sessions 1-7 Password Creator process Tandem Computers Incorporated Index 9

204 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 ABORT APPL command 2-21 ADD APPL command 2-18 APPLFILE attribute 2-19 APPLTYPE attribute 2-19/21 CREATOR attribute 2-19 PASSWORD attribute 2-20, 2-21 ADD command AUTOLOGON attribute 2-22 ESSTABLE attribute 2-23 NOACQ attribute 2-24 ADD LINE, PU and LU attributes 2-22 ALTER command 2-18 Index Tandem Computers Incorporated

205 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/13 ADD ESSMSG command syntax summary A-14 ADD LOGMODENT command A-15 ADD SETESS command 2-18 DEFAULTTABLE operand 2-18 FILENAME operand 2-18 syntax summary A-19 ADD SETLOG command 2-18, A-20 FILENAME operand 2-18 ALLOCATE command 1-12, 1-13 extent size calculation A-20 syntax summary A-20 use 2-3 APPL definition for 2-21 BEGIN command syntax summary A-23 command blocks A-5 command modifier A-3 command object A-3 command syntax A Tandem Computers Incorporated Index 11

206 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-12 table object file 1-13 table source file 1-13 Specifying configuration parameters through SCF 2-18 Starting Pathway processes 1-4 Starting TACL processes 1-4 Static passthrough 2-13 CMDTYPE operand 2-13 ORDER value 2-13 GATELINE operand 2-13 GATELU operand 2-13 GATEPU operand 2-13 STATIC operand 2-13 TERMSELF operand 2-13, A-13 Static path establishing 2-13 terminating 2-13 Index Tandem Computers Incorporated

207 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 SSCP-LU path 2-13 U Unsolicited logons 1-1 User message records 2-15 User message text See MSGTEXT operand User messages adding 2-15 naming 2-15 Using LUNS summary steps Tandem Computers Incorporated Index 13