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