DIGITAL SNA APPC/LU6.2 Programming Interface for_DIGITAL_UNIX____________________________________ Installation Part Number: AA-QQW4B-TE April 1997 This document describes how to install the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software on a DIGITAL Alpha system running the DIGITAL UNIX operating system. Revision/Update Information: This is a revised manual. Operating System and Version: DIGITAL UNIX V3.2c through V4.0x Software Version: DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX V3.1 Electronic Data Systems Corporation and Digital Equipment Corporation make no representations that the use of their products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. The information in this document is subject to change without notice and should not be construed as a commitment from Electronic Data Systems Corporation or Digital Equipment Corporation. Electronic Data Systems Corporation and Digital Equipment Corporation assume no responsibility for any errors that may appear in this document. DIGITAL conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. Copyright © 1997 Electronic Data Systems Corporation. All Rights Reserved. Copyright © 1995 Digital Equipment Corporation. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: DEC, DIGITAL SNA Domain Gateway, DECnet, DIGITAL, OpenVMS, VAX, VAXcluster, VMS, VMScluster, the AlphaGeneration logo, and the DIGITAL logo. The following are third-party trademarks: IBM is a registered trademark of International Business Machines Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. This document is available on CD-ROM. _________________________________________________________________ Contents Preface................................................... ix 1 Preparing for Installation 1.1 The DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Software Environment................................... 1-1 1.1.1 The DIGITAL SNA APPC/LU6.2 Server Subset (SNAL62S310).............................. 1-2 1.1.2 The DIGITAL SNA APPC/LU6.2 Programming Interfaces Subset (SNAL62S310)............ 1-2 1.2 Inspecting the Distribution Kit............... 1-2 1.3 Preparing the IBM SNA Environment............. 1-2 1.4 System Requirements........................... 1-3 1.4.1 Required Software......................... 1-3 1.4.2 Installation Time......................... 1-4 1.5 Preparing for the Installation................ 1-4 1.5.1 Obtaining Superuser Privileges............ 1-4 1.5.2 Deleting Any Currently Installed DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Software..................... 1-4 1.5.3 Checking for Sufficient System Disk Space..................................... 1-5 1.5.4 Backing Up Your System Disk............... 1-6 1.5.5 Reading the Release Notes................. 1-6 1.5.6 Registering Your Product Authorization Key (PAK)..................................... 1-6 1.6 Stopping the Installation..................... 1-9 iii 2 Installing the APPC Software 2.1 Installation from the CD-ROM or Your Network....................................... 2-1 2.1.1 Installing from a CD-ROM Drive............ 2-1 2.1.2 Installing over the Local Area Network with RIS.................................. 2-4 2.2 Possible Installation Errors.................. 2-5 3 After the Installation 3.1 Running the APPC Software Installation Verification Procedures (IVPs)................ 3-1 3.1.1 Running the DIGITAL SNA APPC/LU6.2 Programming Interfaces Subset Installation Verification Procedure (IVP).............. 3-1 3.1.2 Running the DIGITAL SNA APPC/LU6.2 Server Subset Installation Verification Procedure (IVP)..................................... 3-2 3.1.3 IVP Error Messages........................ 3-2 3.2 Accessing the APPC Software Man Pages......... 3-3 3.3 Deleting the APPC Software from Your System... 3-3 3.4 Determining and Reporting Problems............ 3-3 4 Preparing the LU6.2 Server Software 4.1 Declaring the LU6.2 Server's TCP/IP Service Names......................................... 4-1 4.2 Declaring the Attach Manager Daemon's TCP/IP Service Name.................................. 4-2 4.3 Granting the LU6.2 Server Access to the /var/run Directory............................ 4-3 4.4 Creating LU6.2 Server Access Validation Files......................................... 4-3 4.5 Starting and Stopping the LU6.2 Server........ 4-4 4.6 Server Startup Error Messages................. 4-6 4.7 Server Messages in the System Log File........ 4-7 iv 5 Preparing the LU6.2 Client Software 5.1 Declaring the LU6.2 Server's Client TCP/IP Service Name.................................. 5-1 5.2 Declaring the Attach Manager Daemon's TCP/IP Service Name.................................. 5-2 5.3 Granting the Attach Manager Daemon Access to the /var/run Directory........................ 5-2 5.4 Creating the Attach Manager Daemon's Access Validation File............................... 5-2 5.5 Starting and Stopping the Attach Manager Daemon........................................ 5-3 5.6 Attach Manager Daemon Startup Error Messages...................................... 5-5 5.7 Attach Manager Daemon Messages in the System Log File...................................... 5-7 6 Defining the LU6.2 Interface 6.1 The APPC Control Operator Functions........... 6-1 6.2 Managing the LU6.2 Interface.................. 6-2 6.3 Running the LU6.2 Manager Utility............. 6-3 6.4 Using the LU6.2 Manager's Main Window Menu Bar........................................... 6-3 6.4.1 The File Menu............................. 6-3 6.4.2 The Define Menu........................... 6-6 6.4.3 The Display Menu.......................... 6-6 6.4.4 The Delete Menu........................... 6-7 6.4.5 The Session Menu.......................... 6-7 6.4.6 The Help Menu............................. 6-8 6.5 DIGITAL SNA Gateway Considerations............ 6-8 7 A Complete Configuration Example 7.1 The Sample Configuration...................... 7-2 7.2 Configuring the DIGITAL SNA Gateway........... 7-5 7.2.1 Displaying the Peer Server's Control Point Information............................... 7-6 7.2.2 Defining the LU6.2 Server's SNA Access Server Object............................. 7-7 7.2.3 Defining the Peer Server Local LU......... 7-8 7.2.4 Enabling the Peer Server Local LU......... 7-8 7.2.5 Displaying the Peer Server's Transmission Group Information......................... 7-9 v 7.2.6 Defining the Peer Server Partner (Remote) LU........................................ 7-10 7.3 Preparing the LU6.2 Server Environment........ 7-11 7.4 Preparing the LU6.2 Client Environment........ 7-12 7.5 Configuring the LU6.2 Server.................. 7-13 7.5.1 Selecting the LU6.2 Server................ 7-13 7.5.2 Defining the LU6.2 Server's Local LU...... 7-14 7.5.3 Defining the LU6.2 Server's Remote LU..... 7-15 7.5.4 Defining the LU6.2 Server's Mode.......... 7-16 7.5.5 Defining the Transaction Program.......... 7-17 7.5.6 Initializing the Session Limits........... 7-18 7.5.7 Saving the Configuration.................. 7-19 7.6 Configuring the CPI-C Interface............... 7-19 7.7 Building the APINGD sample program............ 7-20 7.8 Invoke APING under VTAM....................... 7-20 7.9 Troubleshooting............................... 7-21 8 Troubleshooting 8.1 No Contact with LU6.2 Server.................. 8-2 8.2 Server Configuration Not What Expected........ 8-4 8.3 Unable to Initialize Session Limits........... 8-5 8.4 Unable to Activate Sessions................... 8-6 8.5 Unable to Activate Transaction Programs Using the Attach Manager Daemon..................... 8-8 8.6 APPC Programs Function Correctly but CPI-C Programs Do Not............................... 8-9 A Sample Installation Dialog B Files Installed on Your System B.1 Files Created................................. B-1 B.2 Softlinks Created............................. B-2 C Using the Text-Based LU6.2 Server Configuration Utility C.1 Running the LU6.2 Server Configuration Utility....................................... C-2 C.2 Specifying an LU6.2 Server.................... C-2 C.3 Defining the Local LU......................... C-4 C.4 Defining the Remote LU........................ C-8 C.5 Defining the Mode Name........................ C-10 vi C.6 Defining the Transaction Program Name......... C-13 C.7 Displaying the List of Local LUs.............. C-16 C.8 Initializing the Mode Session Limits.......... C-22 C.9 Resetting the Mode Session limits............. C-24 C.10 Activating a Session.......................... C-25 C.11 Deleting an LU6.2 Interface Entity............ C-26 C.12 Loading a Configuration File.................. C-28 C.13 Parsing a Configuration File.................. C-29 C.14 Saving a Server's Configuration in a Configuration File............................ C-29 D The LU6.2 Server Configuration File Syntax D.1 Basic Syntax Rules............................ D-1 D.1.1 Whitespace and Comment Lines.............. D-2 D.1.2 Keywords.................................. D-2 D.2 Conventions................................... D-2 D.3 Sample LU6.2 Server Configuration File........ D-3 D.4 Configuration File Operators.................. D-5 ACTIVATE_SESSION.................................... D-6 ADD_SECUR_ACC_INFO.................................. D-8 ADD_SECUR_INFO...................................... D-10 CHANGE_SESSION_LIMIT................................ D-11 DEFINE_LOCAL_LU..................................... D-15 DEFINE_MODE......................................... D-19 DEFINE_REMOTE_LU.................................... D-25 DEFINE_TP........................................... D-29 INITIALIZE_SESSION_LIMIT............................ D-36 SELECT_SERVER....................................... D-40 E Using the LU6.2 Script Processor E.1 Running the LU6.2 Script Processor............ E-2 E.2 Basic Syntax Rules............................ E-2 E.2.1 Whitespace and Comment Lines.............. E-2 E.2.2 Keywords.................................. E-3 E.3 Rerunning a Script to Reactivate Sessions..... E-3 E.4 Sample Script File............................ E-3 E.5 Script Language Operators..................... E-4 vii ACT_MODE............................................ E-6 ACT_SVC............................................. E-7 EXIT................................................ E-8 HELP................................................ E-9 IDS................................................. E-10 INT_MODE............................................ E-12 INT_SVC............................................. E-14 LOCAL............................................... E-15 MODE................................................ E-16 NOTE................................................ E-19 REMOTE.............................................. E-20 SHOW................................................ E-21 Index Figures 1-1 The DIGITAL SNA APPC/LU6.2 Programming Interfaces for DIGITAL UNIX Environment... 1-2 viii _________________________________________________________________ Preface Purpose of This Guide The DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product enables DIGITAL[TM] applications to exchange messages with cooperating applications on an IBM® host. This guide explains how to install the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software on Alpha processors that are running the DIGITAL UNIX operating system. Keep this document with your distribution kit. You will need it to install maintenance updates or to reinstall the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software for any other reason. Intended Audience This manual is written for the system manager responsible for planning and installing the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software. Document Structure This manual has the following chapters and appendices: o Chapter 1 lists prerequisites for installing the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software. o Chapter 2 provides a step-by-step process for installing the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software. ix o Chapter 3 describes various procedures you can use after installing the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software. o Chapter 4 discusses the preparations you must make before using the LU6.2 Server software. o Chapter 5 discusses the preparations you must make before using the LU6.2 client software. o Chapter 6 discusses how to invoke and use the LU6.2 Manager utility to manage an LU6.2 Server. o Chapter 7 provides a complete walk-through example of how to configure the DIGITAL SNA gateway, the LU6.2 Server, the LU6.2 client, and the CPI-C side information. o Chapter 8 discusses various problems you might encounter with the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software and how you diagnose the problems. o Appendix A contains a sample installation dialog for the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software. o Appendix B lists the files installed during the installation process. o Appendix C discusses the use of the text-based LU6.2 Server Configuration Utility. o Appendix D describes the syntax of the configuration file that the LU6.2 Manager and LU6.2 Server Configuration Utility use to save a LU6.2 Server's current configuration. o Appendix E discusses the use of the LU6.2 Script Processor. x Associated DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Documents The other documents in the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX documentation set are the following: o DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Programming o DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX CPI-C Implementation Specifics Associated DIGITAL Documents You should have the following DIGITAL UNIX documents available for reference: o DIGITAL UNIX Programmer's Guide o DIGITAL UNIX Guide to Programming Support Tools o DIGITAL UNIX Guide to DECthreads o DIGITAL UNIX Network Programmer's Guide If you are accessing the IBM SNA network through DIGITAL SNA Peer Server software, you should have the following DIGITAL documents available for reference: o DIGITAL SNA Peer Server Installation and Configuration o DIGITAL SNA Peer Server Management o DIGITAL SNA Peer Server Network Control Language Reference o DIGITAL SNA Peer Server Guide to IBM Resource Definition If you are accessing the IBM SNA network through DIGITAL SNA Domain Gateway[TM] software, you should have the following DIGITAL documents available for reference: o DIGITAL SNA Domain Gateway Planning and Configuration o DIGITAL SNA Domain Gateway Management o DIGITAL SNA Domain Gateway NCL Reference o DIGITAL SNA Domain Gateway Guide to IBM Resource Definition xi If you are accessing the IBM SNA network through DECnet SNA Gateway for Synchronous Transport or DECnet SNA Gateway for Channel Transport software, you should have the following DIGITAL documents available for reference: o DECnet SNA Gateway for Channel Transport Gateway for Synchronous Transport, Management o DECnet SNA Gateway for Channel Transport, Problem Solving or DECnet SNA Gateway for Synchronous Transport, Problem Solving o DECnet SNA Gateway for Channel Transport, Guide to IBM Parameters or DECnet SNA Gateway for Synchronous Transport, Guide to IBM Parameters Associated IBM Documents You should have the following IBM documents available for reference: o Systems Network Architecture Concepts and Products (IBM Order No. GC30-3072) o Systems Network Architecture Technical Overview (IBM Order No. GC30-3073) o Systems Network Architecture Reference Summary (IBM Order No. GA27-3136) o Systems Network Architecture - Sessions Between Logical Units (IBM Order No. GC20-1868) Conventions This manual uses the following conventions: xii ___________________________________________________________ Convention__________Meaning________________________________ Special type Indicates: o Names of interface verbs. o Names of UNIX commands, options, files, directories, and utilities. o UNIX user input or system output. o Names of UNIX hosts and users. UPPERCASE TEXT Represents constant values, or symbols. Code these as specified. lowercase italics Represent variables for which you must supply a value. [ ] Enclose parameters or symbols that are either optional or conditional. Specify the parameter and value if you want the condition to apply. Do not type the brackets in the line of code. The following rules generally apply to parameters: o You can code or omit an optional parameter. Omitting an optional parameter can impact a related parameter or can cause a default value to be specified. o You can code or omit a conditional parameter. Your choice is determined by how other parameters, in the same or different procedures, are coded. ( ) Enclose a group of values you must specify for a parameter. Type these values in the line of code in the order indicated. Type parentheses exactly where they must appear in a line of code. xiii ___________________________________________________________ Convention__________Meaning________________________________ Numbers Represent decimal numbers unless otherwise noted. Indicates that you should press the Return key. Unless otherwise specified, end every command line by pressing the Return key. Indicates a control character where x is an alphabetic character. Press the Ctrl key and the indicated character key simultaneously. % Represents the default user prompt. # Represents the default superuser ____________________prompt.________________________________ Acronyms This manual uses the following acronyms: BOM Bill of Materials CNOS change-number-of-session COPR control operator IVP Installation Verification Procedure LDB LMF's License Database LMF DIGITAL's License Management Facility LU logical unit PAK Product Authorization Key PIP program initialization parameters PU physical unit RIS Remote Installation Services RU request unit SCS SNA character strings SNA IBM's Systems Network Architecture SPD Software Product Description TG transmission group xiv 1 _________________________________________________________________ Preparing for Installation This chapter tells you how to prepare for installing the DIGITAL SNA APPC/LU6.2 Programming Interface product (hereafter called the APPC software) on the DIGITAL UNIX operating system. Issues covered in this chapter include: o The DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX environment (see Section 1.1). o Inspecting the distribution kit (see Section 1.2). o Preparing the IBM SNA environment (see Section 1.3). o System requirements (see Section 1.4). o Preparing for the installation (see Section 1.5). o Stopping the installation (see Section 1.6). 1.1 The DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Software Environment The DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software uses the client/server model. You install the software as two subsets: a server subset and a client subset. When you install the DIGITAL SNA APPC/LU6.2 Server subset (SNAL62S310), you are installing the LU6.2 Server, the LU6.2 Manager, the LU6.2 Server Configuration Utility, and the LU6.2 Script Processor. When you install the DIGITAL SNA APPC/LU6.2 Programming Interfaces subset (SNALU62310), you are installing the client software (this includes the Attach Manager daemon, see Chapter 5). Figure 1-1 shows the relationship between the APPC software subsets, the DIGITAL SNA gateway, and the IBM host. Preparing for Installation 1-1 1.1.1 The DIGITAL SNA APPC/LU6.2 Server Subset (SNAL62S310) The DIGITAL SNA APPC/LU6.2 Server software is a DIGITAL SNA access routine. Like other DIGITAL SNA access routines, the DIGITAL SNA APPC/LU6.2 Server uses one or more DIGITAL SNA gateways to access the IBM SNA network. Together, the LU6.2 Server and the DIGITAL SNA gateway maintain the local LU and the communication link between the local LU and the remote LU in the IBM SNA network. You can install the server software on as many nodes as you feel necessary to support your load and availability requirements. You can also run multiple copies of the LU6.2 Server on a single system. 1.1.2 The DIGITAL SNA APPC/LU6.2 Programming Interfaces Subset (SNAL62S310) The DIGITAL SNA APPC/LU6.2 Programming Interfaces software is a client of the DIGITAL SNA APPC/LU6.2 Server software. The DIGITAL SNA APPC/LU6.2 Programming Interfaces software is a set of callable routines that, when linked together with your program, communicates with the LU6.2 Server over TCP/IP or DECnet connections. The DIGITAL SNA APPC/LU6.2 Programming Interfaces subset includes the CPI-C client routines discussed in the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX CPI-C Implementation Specifics manual. 1.2 Inspecting the Distribution Kit The software Bill of Materials (BOM) included with your distribution kit shows the contents of the kit. Carefully compare the items you received against the BOM. Report any missing or damaged components to Digital Equipment Corporation before continuing with the installation. 1.3 Preparing the IBM SNA Environment Before you can use the APPC software, you must prepare certain software components in the IBM environment, as follows: o The DIGITAL SNA Peer Server Guide to IBM Resource Definition explains the IBM parameters to define for 1-2 Preparing for Installation successful communication between the IBM host and the DIGITAL SNA Peer Server software. o The DIGITAL SNA Domain Gateway Guide to IBM Resource Definition explains the IBM parameters to define for successful communication between the IBM host and the DIGITAL SNA Domain Gateway software. o The DECnet SNA Gateway for Channel Transport Guide to IBM Parameters explains the IBM parameters to define for successful communication between the IBM host and the DECnet SNA Gateway for Channel Transport software. o The DECnet SNA Gateway for Synchronous Transport Guide to IBM Parameters explains the IBM parameters to define for successful communication between the IBM host and the DECnet SNA Gateway for Synchronous Transport software. You should view the DIGITAL documentation as an adjunct to the IBM documentation; the IBM documentation remains the authoritative source for IBM software concepts and procedures. ________________________ Note ________________________ Since IBM system programmers generally reconfigure and generate their systems according to a set schedule, give them as much advance notice as possible. ______________________________________________________ 1.4 System Requirements This section lists and describes the software requirements your site must meet in order to install the APPC software. 1.4.1 Required Software The APPC software requires DIGITAL UNIX, versions 3.2c through 4.0x. See the Software Product Description (SPD) for a complete list of software required to support the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product. Preparing for Installation 1-3 1.4.2 Installation Time Installation of the APPC software requires 5 to 30 minutes, depending on the installation medium used. 1.5 Preparing for the Installation Before you begin the installation, prepare your system for the APPC software. Preparation includes the following activities: 1. Obtaining superuser privileges. 2. Deleting any currently installed DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software. 3. Checking for sufficient system disk space. 4. Optionally, backing up your system disk. DIGITAL strongly recommends that you perform a full system backup before installation. 5. Reading the product's Release Notes. 6. Registering your Product Authorization Key (PAK). 1.5.1 Obtaining Superuser Privileges To install the APPC software, you must have superuser privileges. To acquire these privileges, enter the following command followed by the root password. See the DIGITAL UNIX system manager documentation for more details. % su password: password # 1.5.2 Deleting Any Currently Installed DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Software You must delete any existing DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software subsets before installing a new version of the software. Before deleting the software, you should verify that the software you are about to install has a higher version level than any existing APPC software. To check the version of the currently installed APPC software, use the following command: 1-4 Preparing for Installation # setld -i | grep "^SNAL" Look for the lines beginning with "DIGITAL SNA APPC/LU6.2 Programming Interface" and "DIGITAL SNA APPC/LU6.2 Server". The version number appears at the end of these lines. If the setld display shows that the APPC software is installed (look for the words installed or corrupt), and the installed software has a lower version, you should proceed to delete the installed APPC software subsets. To delete the DIGITAL SNA APPC/LU6.2 Programming Interfaces subset's files from your system, log in as superuser and enter the following setld command using the -d option: # setld -d SNALU62300 To delete the DIGITAL SNA APPC/LU6.2 Server subset's files from your system, log in as superuser and enter the following setld command using the -d option: # setld -d SNAL62S300 _______________________ Warning _______________________ If you are deleting a previous version of the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software and you have changed the CPI-C side information file (/etc/cpic.conf), create a copy of this file. The APPC software deletion script removes this file. For more information on this file, see the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX CPI-C Implementation Specifics manual. ______________________________________________________ 1.5.3 Checking for Sufficient System Disk Space Check the free disk space on your system. You must have sufficient free space to install the APPC software. The installation will fail if there is insufficient space for copying the software from the distribution media. Minimum space requirements for the APPC software are as follows: o 2 Mb in the /usr partition. Preparing for Installation 1-5 To check the free space in the /usr partition, enter the following command: # df -k /usr 1.5.4 Backing Up Your System Disk Before installing the APPC software, you should back up your system disk. See the document DIGITAL UNIX Guide to System Administration for further details. 1.5.5 Reading the Release Notes Before you install the APPC software, you should read the product's Release Notes. To access the Release Notes, do the following: 1. Determine the location of the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX files on the Consolidated Software Distribution CD-ROM. See the master index that accompanies the CD-ROM for the directory containing the files. 2. Insert the CD-ROM into the drive and mount the disk using the drive's device name. If you do not know the device name, enter the following command to list available drives. The drive is either RRD40 or RRD42. # file /dev/rr*c To mount the disk, enter the following command, where dev-name is the device name of your drive. # mount -r -d /dev/dev-name /mnt 3. Search the directory on the CD-ROM where the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product files are located for the file SNALU62310.release_notes. 1.5.6 Registering Your Product Authorization Key (PAK) The APPC software supports the License Management Facility (LMF). You must register your license PAK in the License Database (LDB) to use the APPC software on a newly licensed node. LMF maintains a file of registered software license PAKs. Also, LMF keeps a library of functions used by DIGITAL licensed software. 1-6 Preparing for Installation ________________________ Note ________________________ The following licenses are available for the DIGITAL SNA APPC/LU6.2 Programming Interfaces for DIGITAL UNIX software: o SNA-APPC-LU6.2-UA-DEV o SNA-APPC-LU6.2-UA-D-USER o SNA-APPC-LU6.2-UA-RT o SNA-APPC-LU6.2-UA-R-USER o SNA-APPC-LU6.2 o SNA-APPC-LU6.2-USER o SNA-APPC-LU6.2-RT o SNA-APPC-LU6.2-RT-USER o SNA-APPC-LU6.2-TK o SNA-APPC-LU6.2-TK-USER o CICS-CELL-SERVER o CICS-CLIENT o CICS-SERVER The software checks the licenses in the order shown. If no license is installed, the software displays an error message using the last PAK in the list. ______________________________________________________ To register one of the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software license PAKs using LMF, proceed as follows: 1. Log on to your system as superuser. % su password: password # 2. Enter the following command from the superuser prompt. Press the Return key after the confirmation message appears: Preparing for Installation 1-7 # lmfsetup Register PAK (type q or quit to exit) [template] 3. After you confirm the procedure, the system prompts you for information related to the fields on your PAK form. If you ordered the license and media together, this form ships with your DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX software distribution kit. Otherwise, DIGITAL ships it separately to a location based on your license order. Using the information from your APPC software PAK, reply to each question. Any fields left blank in your PAK should be left blank when you enter the data. 4. After you have answered all questions, the system displays the following completion message. Enter quit and press the Return key: Register PAK (type q or quit to exit) [template] quit 5. After leaving lmfsetup, enter the following reset command: # lmf reset 6. If you attempt to load a PAK when a previous PAK is already installed, an informational message similar to the following appears: Combine SNA-APPC-LU62-UA-DEV auth-num with SNA-APPC-LU62-UA-DEV auth 7. After completing the LMF procedure, verify your registration: # lmf list For further information concerning the use of the LMF software or for more details about obtaining a license and PAK, see the document DIGITAL UNIX Guide to Software License Management. You can also reference the lmf and lmfsetup man pages (lmf(8) and lmfsetup(8)). This completes the preinstallation activities for the APPC software. Chapter 2 describes the installation process. 1-8 Preparing for Installation 1.6 Stopping the Installation To stop the installation at any time, press Ctrl/C. You must then delete files created up to this point interactively. Appendix B lists the directories and files created during the APPC software installation. Preparing for Installation 1-9 2 _________________________________________________________________ Installing the APPC Software This chapter describes the procedure for installing the APPC software and discusses possible errors encountered during installation. ________________________ Note ________________________ Before installing the software, you must register your software license PAK using LMF (see Chapter 1 for details). ______________________________________________________ 2.1 Installation from the CD-ROM or Your Network You can install the APPC software from two locations: the Consolidated Software Distribution CD-ROM or a remote node in your local area network using the Remote Installation Service (RIS). 2.1.1 Installing from a CD-ROM Drive To install the APPC software from the Consolidated Software Distribution CD-ROM, do the following: 1. Determine the location of the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX files on the CD- ROM. See the master index that accompanies the CD-ROM for the directory containing the files. 2. Insert the CD-ROM into the drive and mount the disk using the drive's device name. If you do not know the device name, enter the following command to list available drives. The drive is either RRD40 or RRD42. # file /dev/rr*c Installing the APPC Software 2-1 To mount the disk, enter the following command, where dev-name is the device name of your drive. # mount -r -d /dev/dev-name /mnt 3. Install the APPC software using the setld command, where snalu62 is the name of the directory on the CD-ROM where the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX files are located: # setld -l /mnt/snalu62 After you enter the setld command, the system displays the following messages: DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1-0 (c) Electronic Data Systems Corporation 1997. All Rights Reserved. (c) Digital Equipment Corporation 1994. All Rights Reserved. This software is proprietary to and embodies the confidential technology of Electronic Data Systems Corporation and Digital Equipment Corporation. Possession, use, duplication or dissemination of this software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation or an authorized sublicensor. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) DIGITAL SNA APPC/LU6.2 Programming Interfaces 2) DIGITAL SNA APPC/LU6.2 Server Or you may choose one of the following options: 3) ALL of the above 4) CANCEL selections and redisplay menus 5) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. 2-2 Installing the APPC Software 4. Install the desired APPC software subsets by responding to the following prompt: Choices (for example, 1 2 4-6): 3 In this example, we are installing both the DIGITAL SNA APPC/LU6.2 Programming Interfaces subset (the client interface) and the DIGITAL SNA APPC/LU6.2 Server subset. To install only the client interface select 1. The system displays the following messages: ________________________ Note ________________________ If you are installing the server subset (SNAL62S310), you must have already installed the client subset (SNALU62310) or you must select option 3 and install both subsets at the same time. ______________________________________________________ You are installing the following optional subsets: DIGITAL SNA APPC/LU6.2 Programming Interfaces DIGITAL SNA APPC/LU6.2 Server If the displayed subsets are correct, answer the next prompt positively: Is this correct? (y/n): y The system displays the following messages: Checking file system space required to install selected subsets: File system space checked OK. 2 subset(s) will be installed. Loading 1 of 2 subset(s).... DIGITAL SNA APPC/LU6.2 Programming Interfaces Copying from . (disk) Verifying Loading 2 of 2 subset(s).... DIGITAL SNA APPC/LU6.2 Server V3.1 Copying from . (disk) Verifying 2 of 2 subset(s) installed successfully. Installing the APPC Software 2-3 5. Run the IVP for the DIGITAL SNA APPC/LU6.2 Programming Interface V3.1 subset by responding y to the following prompt: DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1-0 (c) Electronic Data Systems Corporation 1997. All Rights Reserved. (C) Digital Equipment Corporation 1994. All Rights Reserved. Would you like to run IVP for SNALU62310? (y/n) [y]: The system displays the following messages: Beginning the IVP for (SNALU62310) IVP for (SNALU62310) has successfully completed. Installation of (SNALU62310) has successfully completed. Configuring "DIGITAL SNA APPC/LU6.2 Programming Interfaces" (SNALU62310) 6. Run the IVP for the DIGITAL SNA APPC/LU6.2 Server V3.1 subset by responding y to the following prompt: DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1-0 (c) Electronic Data Systems Corporation 1997. All Rights Reserved. (c) Digital Equipment Corporation 1994. All Rights Reserved. Would you like to run IVP for SNAL62S310? (y/n) [y]: The system displays the following messages: Beginning the IVP for (SNAL62S310) IVP for (SNAL62S310) has successfully completed. Installation of (SNAL62S310) has successfully completed. Configuring "DIGITAL SNA APPC/LU6.2 Server" (SNAL62S310) 2.1.2 Installing over the Local Area Network with RIS If you are installing the APPC software over your local area network, use the Remote Installation Service (RIS) utility. See the reference pages in Section 8 of the document Guide to Sharing Software on LAN for RIS requirements. Enter the following command, where host-name is the name of the node from which you are loading the software. # setld -l host-name: 2-4 Installing the APPC Software The installation then proceeds as described in the previous section. 2.2 Possible Installation Errors If an error occurs during the installation procedure, the system displays one of the following four failure messages: This subset (subset-name) requires that subset (subset- name) be installed first This error occurs when you select the server subset (SNAL62S310) without also selecting the client subset (SNALU62310). The server subset requires that the client subset be already installed or that it's installation coincide with the client subset's installation. File system space check This error indicates that the installation script did not find enough space in the /usr partition. You should increase the available space to at least 2 Mb and retry the installation. Unknown machine type: machine-name You must install the APPC software on an Alpha processor. This error indicates that the installation script detected a processor other than an Alpha processor. Missing dependencies, cannot install The APPC software must be installed on the DIGITAL UNIX operating system version 3.2c through 4.0x. This error indicates that the installation script detected a processor running an earlier or later version of the DIGITAL UNIX operating system. Installing the APPC Software 2-5 3 _________________________________________________________________ After the Installation This chapter describes miscellaneous tasks associated with the installation process. These tasks include the following: o Running the APPC software Installation Verification Procedures (IVPs) and interpreting IVP error messages (see Section 3.1). o Accessing the APPC software man pages (see Section 3.2). o Deleting the files created during the installation (see Section 3.3). o Determining and reporting problems to DIGITAL (see Section 3.4). 3.1 Running the APPC Software Installation Verification Procedures (IVPs) Usually, you request the installation script to automatically run the APPC software IVPs during the installation process. In this case, the installation process installs each subset and then verifies the installation using its IVP. You can also run the IVPs after the installation to verify that each subset is installed and working properly. 3.1.1 Running the DIGITAL SNA APPC/LU6.2 Programming Interfaces Subset Installation Verification Procedure (IVP) To run the DIGITAL SNA APPC/LU6.2 Programming Interfaces subset IVP, enter the following command: # setld -v SNALU62310 After the Installation 3-1 After you enter the setld command, the system displays the following messages: DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1-0 (Rev. 0) (c) Electronic Data Systems Corporation 1997. All Rights Reserved. (c) Digital Equipment Corporation 1994. All Rights Reserved. Beginning the IVP for (SNALU62310) IVP for (SNALU62310) has successfully completed. 3.1.2 Running the DIGITAL SNA APPC/LU6.2 Server Subset Installation Verification Procedure (IVP) To run the DIGITAL SNA APPC/LU6.2 Server subset IVP, enter the following command: # setld -v SNAL62S310 After you enter the setld command, the system displays the following messages: DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1-0 (Rev. 0) (c) Electronic Data Systems Corporation 1997. All Rights Reserved. (c) Digital Equipment Corporation 1994. All Rights Reserved. Beginning the IVP for (SNAL62S310) IVP for (SNAL62S310) has successfully completed. 3.1.3 IVP Error Messages If the IVP detects an error condition, it displays the following line: DIGITAL SNA APPC/LU6.2 Programming Interface V3.1 for DIGITAL UNIX IVP failed This line is preceded by one of the following error messages: The IVP for SNALU62310 failed The IVP for the DIGITAL SNA APPC/LU6.2 Programming Interface subset failed to run. Check that the LMF PAK (see Section 1.5.6) is installed and retry. If the IVP fails again, reinstall the product. If this fails to correct the problem, see Section 3.4. 3-2 After the Installation The IVP for SNAL62S310 failed The IVP for the DIGITAL SNA APPC/LU6.2 Server subset failed to run. Check that the LMF PAK (see Section 1.5.6) is installed and retry. If the IVP fails again, reinstall the product. If this fails to correct the problem, see Section 3.4. 3.2 Accessing the APPC Software Man Pages The DIGITAL SNA APPC/LU6.2 Programming Interfaces subset (SNALU62310) includes man pages for each LU6.2 verb. To access a verb's man page, enter the command man verb-name. For example, to access the man page for snalu62_allocate, enter the following command: # man snalu62_allocate 3.3 Deleting the APPC Software from Your System You may find it necessary to delete the APPC software from your system. To delete the DIGITAL SNA APPC/LU6.2 Programming Interfaces subset from your system, log in as superuser and enter the setld command with the -d option, as follows: # setld -d SNALU62310 To delete the DIGITAL SNA APPC/LU6.2 Server subset from your system, log in as superuser and enter the setld command with the -d option, as follows: # setld -d SNAL62S310 3.4 Determining and Reporting Problems If you encounter a problem while using the APPC software, report it to DIGITAL. First, determine the version of the APPC software (see Section 1.5.2) and the DIGITAL UNIX operating system software. Then, depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call DIGITAL if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). After the Installation 3-3 Review the Software Product Description (SPD) and Warranty Addendum for an explanation of the warranty. If you encounter a problem during the warranty period, report the problem as indicated or follow alternate instructions provided by DIGITAL for reporting SPD nonconformance problems. 3-4 After the Installation 4 _________________________________________________________________ Preparing the LU6.2 Server Software This chapter discusses preparing the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX server software environment. Before you use the LU6.2 Server, you must prepare the LU6.2 Server's environment by doing the following: 1. For TCP/IP networks, declare the server's TCP/IP service names (see Section 4.1). 2. For TCP/IP networks, declare the service name for any Attach Manager daemons used by the server (see Section 4.2). 3. Grant the server access to the /var/run directory (see Section 4.3). 4. Create the server's access validation files (see Section 4.4). 5. Start the LU6.2 Server (see Section 4.5). 6. If necessary, read the LU6.2 Server's startup error messages (see Section 4.6). 7. If necessary, read the LU6.2 Server's syslog messages (see Section 4.7). 4.1 Declaring the LU6.2 Server's TCP/IP Service Names Each LU6.2 Server has a name. This name must be unique within the same system. However, across a network, many LU6.2 Servers can have the same name. The combination of the node or host name and the LU6.2 Server's name differentiates each LU6.2 Server. Preparing the LU6.2 Server Software 4-1 When the LU6.2 Server first starts, it attempts to declare itself as two DECnet objects: server-name_CLI (for incoming client connections) and server-name_SES (for incoming DIGITAL SNA gateway connections). It then attempts to declare itself as two TCP/IP services with the same names. At least one of these declaration attempts must be successful. If both of these declarations fail, the LU6.2 Server image exits. For the LU6.2 Server to be able to declare itself as a TCP/IP service, you must specify the server-name_CLI and server-name_SES service name definitions in the DIGITAL UNIX /etc/services file. The interface uses the server- name_CLI service name for client-to-server connections and the server-name_SES service name for gateway-to- server connections. Any non-local client that wishes to use a LU6.2 Server must contain a matching server-name_ CLI definition in its /etc/services file (that is, the same port and service name, see Section 5.1). Also, the DIGITAL SNA gateway used by the LU6.2 Server must contain a matching server-name_SES definition in its /etc/services file. All service names are restricted to uppercase alphabetic characters and the underscore character. ________________________ Note ________________________ By default, a DIGITAL UNIX system with the DIGITAL SNA APPC/LU6.2 Server subset installed starts one server with the name LU62_SRV. You can create multiple servers or you can rename the single default server. See Section 4.5. ______________________________________________________ 4.2 Declaring the Attach Manager Daemon's TCP/IP Service Name Each Attach Manager daemon in a TCP/IP network declares itself as a TCP/IP service, using the name LU62_AMD. When the server accesses the Attach Manager daemon, it uses this name. You must supply the LU62_AMD definition in the local /etc/services file. The port number and service name must match the port number and service name defined in the /etc/services file on the Attach Manager daemon's node. For more information about the Attach Manager daemon's service name, see Section 5.2. 4-2 Preparing the LU6.2 Server Software 4.3 Granting the LU6.2 Server Access to the /var/run Directory You must grant the LU6.2 Server process access to the /var/run directory. The server creates the file lu62_ server.server-name.pid in this directory. This file contains information about the server's running process. On DIGITAL UNIX systems with multiple LU6.2 Servers, there is a unique lu62_server.server-name.pid file for each server. 4.4 Creating LU6.2 Server Access Validation Files If you intend to allow management of the LU6.2 Server from any non-local hosts, you must set up one or more LU6.2 Server access validation files. An LU6.2 Server access validation file contains a list of DECnet node names and TCP/IP host names that are allowed to manage the LU6.2 Server. The server checks these files each time it receives one of the following requests: snalu62_activate_session snalu62_deactivate_conv_group snalu62_deactivate_session snalu62_define_local_lu snalu62_define_mode snalu62_define_remote_lu snalu62_define_tp snalu62_delete snalu62_change_session_limit snalu62_initialize_sess_limit snalu62_reset_session_limit snalu62_process_session_limit When the LU6.2 Server receives one of these requests, it performs the following verification steps: 1. Checks if the request came from the local node. If so, the LU6.2 Server processes the request. 2. If the request is from a remote host or node, the LU6.2 Server checks for the existence of a server- specific access validation file with the name /usr/lib/sna/server-name.lu62hosts. a. If the request came from a host or node listed in this file, the LU6.2 Server processes the request. Preparing the LU6.2 Server Software 4-3 b. If the request came from a host or node not listed in this file, then the LU6.2 Server denies the request. 3. If the file /usr/lib/sna/server-name.lu62hosts does not exist, the LU6.2 Server checks for the existence of a global access validation file with the name /usr/lib/sna/.lu62hosts. a. If the request came from a host or node listed in this file, the LU6.2 Server processes the request. b. If the request came from a host or node not listed in this file, then the LU6.2 Server denies the request. 4. If the file /usr/lib/sna/.lu62hosts does not exist, the LU6.2 Server denies the request. ________________________ Notes ________________________ The names of TCP/IP hosts in the access validation file are case sensitive. The names of DECnet node names are not case sensitive. You cannot use any wildcard characters in the host or node names. You can use simple names for TCP/IP hosts. However, be aware of the possibility of two hosts having the same simple name (for example, apll1.bos.cmp.com and apll1.ny.cmp.com). The LU6.2 Server will accept requests from all nodes having the same simple name. Place the pound sign (#) in the first column of a line in the access validation file to indicate that the line is a comment line. ______________________________________________________ 4.5 Starting and Stopping the LU6.2 Server Normally, the LU6.2 Server starts automatically whenever you reboot the server's operating system. To start the LU6.2 Server manually, use the following command at the root prompt: # /sbin/init.d/lu62_startup start 4-4 Preparing the LU6.2 Server Software By default, this command invokes the executable image /usr/sbin/lu62_server and assigns it the process name LU62_SRV. You must edit the /sbin/init.d/lu62_startup script file if you wish to assign another name to the default LU6.2 Server or if you wish to run multiple copies of the LU6.2 Server (see the description of the variable SRV_LIST in the file). Server names must always be uppercase. By default, the LU6.2 Server starts without any configuration. After the LU6.2 Server initializes itself, it attempts to start the LU6.2 Manager and sends it a request to load the configuration file with the name /usr/lib/sna/server-name.cfg. If this file exists, the LU6.2 Manager uses it to configure the server. Otherwise, the LU6.2 Server remains unconfigured. You can create this configuration file using the LU6.2 Manager (see Section 6.1), the LU6.2 Server Configuration Utility (see Appendix C), or any text editor. Appendix D describes the syntax of this file. If you wish to load the server with a configuration file other than the default, you must use either the LU6.2 Manager or the LU6.2 Configuration Utility to configure the server. ________________________ Note ________________________ If the client interface is installed along with the server, this command also invokes the Attach Manager daemon's executable image /usr/sbin/lu62_amd and assigns it the process name LU62_AMD. For more information about the function of the Attach Manager daemon and how you can use it to start transaction programs, see the "Implementation Specifics" chapter in the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Programming manual. ______________________________________________________ Preparing the LU6.2 Server Software 4-5 To stop the LU6.2 Server, use the following command: # /sbin/init.d/lu62_startup stop ________________________ Note ________________________ This command uses the kill -9 command to stop all processes running the /usr/sbin/lu62_server executable image. To stop an individual server, locate the individual process and use the appropriate kill command. If the client interface is installed along with the server, this command also uses the kill command to stop the process running the /usr/sbin/lu62_amd executable image. ______________________________________________________ 4.6 Server Startup Error Messages When the server encounters an error during its startup phase, the server writes an error message to its standard error output. The following list describes the server startup error messages: Failed to access pid file, errno = errno Explanation: The LU6.2 Server located its pid file, /var/run/lu62_server.server-name.pid, but could not open it for reading. User Action: Use the errno value to determine the cause of the error. Correct the indicated problem and restart the LU6.2 Server. Failed to read a record from the PID file, errno = errno Explanation: The LU6.2 Server successfully located and open its pid file, /var/run/lu62_server.server-name.pid. The server encountered a system error while attempting to read the first piece of information, the process ID, from the file. User Action: Delete the pid file and restart the LU6.2 Server. If the error recurs, use the errno value to determine the cause of the error. Correct the indicated problem and restart the LU6.2 Server. 4-6 Preparing the LU6.2 Server Software PID file format invalid, reading 'string-from-pid-file' Explanation: The LU6.2 Server attempted to read the information from its pid file, /var/run/lu62_server.server- name.pid. The pid file contains a process ID and a system boot timestamp. The format of the process ID information was invalid. User Action: Delete the pid file and restart the LU6.2 Server. Failed to access LU6.2 server server-name, errno = errno Explanation: The LU6.2 Server detected another process with the same pid as specified in its pid file, /var/run/lu62_ server.server-name.pid. While attempting to determine if the other process was still running, a system error occurred. User Action: Use the errno value to determine the cause of the error. Correct the indicated problem and restart the LU6.2 Server. Note that this may cause another error indicating that another server with the same server name is already running. See the next message. LU6.2 server server-name already running Explanation: The LU6.2 Server detected another process running with the name server-name. Only one server with a particular name can run on the same system at the same time. User Action: None, the requested LU6.2 Server is already running. Failed to fork the LU6.2 Server server-name, errno = errno Explanation: A system error occurred when the server attempted to fork the LU6.2 Server process. User Action: Use the errno value to determine the cause of the error. Correct the indicated problem and restart the LU6.2 Server. 4.7 Server Messages in the System Log File Once it successfully starts, the LU6.2 Server records error conditions using the DIGITAL UNIX syslog system routine. This routine uses the syslogd daemon to write messages to the log files defined in the etc/syslog.conf file. The server uses the LOG_DAEMON facility code on all its syslog calls. On most DIGITAL UNIX systems, this causes the Preparing the LU6.2 Server Software 4-7 syslogd daemon to write the server's messages to the file /var/adm/syslog.dated/daemon.log. The messages have the following format: timestamp node-name server-name[process-id]: message-string 4-8 Preparing the LU6.2 Server Software 5 _________________________________________________________________ Preparing the LU6.2 Client Software This chapter discusses configuring the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX client software environment. Before you use the LU6.2 client programming interface, you must prepare the LU6.2 client software by doing the following: 1. For TCP/IP networks, declare the TCP/IP service name for the LU6.2 Server's client port (see Section 5.1). 2. For TCP/IP networks, declare the TCP/IP service name for the Attach Manager daemon (see Section 5.2). 3. Grant the Attach Manager daemon access to the /var/run directory (see Section 5.3). 4. Create the Attach Manager daemon's access validation file (see Section 5.4). 5. Start the Attach Manager daemon (see Section 5.5). 6. If necessary, read the Attach Manager's startup error messages (see Section 5.6). 7. If necessary, read the Attach Manager's syslog messages (see Section 5.7). 5.1 Declaring the LU6.2 Server's Client TCP/IP Service Name Each LU6.2 Server in a TCP/IP network declares itself as a TCP/IP service, using the names server-name_CLI and server- name_SES. When the client interface accesses the LU6.2 Server, it uses the name server-name_CLI. You must supply the server-name_CLI definition in the local /etc/services file. The port number and service name must match the port number and service name defined in the /etc/services file on the LU6.2 Server's node. For more information about the LU6.2 Server's service names, see Section 4.1. Preparing the LU6.2 Client Software 5-1 5.2 Declaring the Attach Manager Daemon's TCP/IP Service Name When the Attach Manager first starts, it attempts to declare itself as the DECnet object LU62_AMD. It then attempts to declare itself as a TCP/IP service with the same name. At least one of these declaration attempts must be successful. If both of these declarations fail, the Attach Manager daemon exits. For the Attach Manager to be able to declare itself as a TCP/IP service, you must specify the LU62_AMD service name definition in the DIGITAL UNIX /etc/services file. Any LU6.2 Server that wishes to use this Attach Manager must contain a matching LU62_AMD definition in its /etc/services file (that is, the same port and service name). In most cases, all LU6.2 Servers and Attach Manager daemons within a network should use the same port number. Use different port numbers when you wish to isolate a group of servers and Attach Manager daemons from the remaining servers and daemons. 5.3 Granting the Attach Manager Daemon Access to the /var/run Directory You must grant the Attach Manager daemon access to the /var/run directory. The Attach Manager daemon creates the file lu62_amd.pid in this directory. This file contains information about the daemon's running process. 5.4 Creating the Attach Manager Daemon's Access Validation File Before using the Attach Manager daemon, you must set up the daemon's access validation file /usr/lib/sna/lu62_ amd.access. This file contains a list of LU6.2 Servers that are allowed to use the daemon. Associated with each server is a list of local user names under which that server may request the daemon to start transaction programs. Each entry in the file has the following format: node-name::transport::server-name::user-list 5-2 Preparing the LU6.2 Client Software where node-name specifies the DECnet node name or TCP/IP host name where the server is running. transport specifies the case insensitive name of transport used between the server and the daemon. Specify either DECnet or TCPIP. server- specifies the name of the server as defined in name the SRV_LIST variable in the /sbin/init.d/lu62_ startup script file (see Section 4.5). user-list specifies the list of local user names under which this server is allowed to request the daemon to start transaction programs. The list consists of user names separated by commas. The following example allows the LU6.2 Server LU62_SRV on DECnet node LU62SV and the LU6.2 Server JON_SRV on Internet node lu62test.usa.cmp.com access to the local Attach Manager daemon. This server is allowed to request that transaction programs be invoked under the user names Paul, Samantha, and Malcolm. LU62SV::DECnet::LU62_SRV::Paul,Samantha,Malcolm lu62test.usa.cmp.com::TCPIP::JON_SRV::Paul,Samantha,Malcolm ________________________ Note ________________________ To have the Attach Manager's access validation take effect, you must stop and restart the Attach Manager daemon. See the next section for for instructions on how to start and stop the Attach Manager. ______________________________________________________ 5.5 Starting and Stopping the Attach Manager Daemon Normally, the Attach Manager daemon starts automatically whenever you reboot the client's operating system. To start the Attach Manager daemon manually, use the following command at the root prompt: # /sbin/init.d/lu62_startup start This command invokes the executable image /usr/sbin/lu62_ amd. Preparing the LU6.2 Client Software 5-3 For more information about the function of the Attach Manager daemon and how you can use it to start transaction programs, see the "Implementation Specifics" chapter in the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Programming manual. ________________________ Note ________________________ If the server is installed along with the client interface, this command also invokes the executable image /usr/sbin/lu62_server. See Section 4.5 about assigning server names and starting multiple servers. ______________________________________________________ 5-4 Preparing the LU6.2 Client Software To stop the Attach Manager Daemon, use the following command: # /sbin/init.d/lu62_startup stop ________________________ Note ________________________ This command uses the kill command to stop the process running the /usr/sbin/lu62_amd executable image. If the server is installed along with the client interface, this command also uses the kill -9 command to stop all processes running the /usr/sbin/lu62_ server executable image. ______________________________________________________ 5.6 Attach Manager Daemon Startup Error Messages When the Attach Manager daemon encounters an error during its startup phase, the daemon writes an error message to its standard error output. The following list describes the Attach Manager daemon startup error messages: Failed to access pid file, errno = errno Explanation: The Attach Manager daemon found its pid file, /var/run/lu62_amd.pid, but could not open it for reading. User Action: Use the errno value to determine the cause of the error. Correct the indicated problem and restart the Attach Manager daemon. Failed to read a record from the PID file, errno = errno Explanation: The Attach Manager daemon successfully located and open its pid file, /var/run/lu62_amd.pid. The Attach Manager daemon encountered a system error while attempting to read the first piece of information, the process ID, from the file. User Action: Delete the pid file and restart the Attach Manager daemon. If the error recurs, use the errno value to determine the cause of the error. Correct the indicated problem and restart the Attach Manager daemon. Preparing the LU6.2 Client Software 5-5 PID file format invalid, reading 'string-from-pid-file' Explanation: The Attach Manager daemon attempted to read the information from its pid file, /var/run/lu62_amd.pid. The pid file contains a process ID and a system boot timestamp. The format of the process ID information was invalid. User Action: Delete the pid file and restart the Attach Manager daemon. Failed to access LU6.2 Attach Manager Daemon LU62_AMD, errno = errno Explanation: The Attach Manager daemon detected another process with the same pid as specified in its pid file, /var/run/lu62_amd.pid. While attempting to determine if the other process was still running, a system error occurred. User Action: Use the errno value to determine the cause of the error. Correct the indicated problem and restart the Attach Manager daemon. Note that this may cause another error indicating that the Attach Manager daemon is already running. See the next message. LU6.2 Attach Manager Daemon LU62_AMD already running Explanation: The Attach Manager daemon detected another Attach Manager daemon process already running. Only one Attach Manager daemon can run on the same system at the same time. User Action: None, the Attach Manager daemon is already running. Failed to fork the LU6.2 Attach Manager Daemon LU62_AMD, errno = errno Explanation: A system error occurred when the Attach Manager daemon attempted to fork the Attach Manager daemon process. User Action: Use the errno value to determine the cause of the error. Correct the indicated problem and restart the Attach Manager daemon. 5-6 Preparing the LU6.2 Client Software 5.7 Attach Manager Daemon Messages in the System Log File Once it successfully starts, the Attach Manager daemon records error conditions using the DIGITAL UNIX syslog system routine. This routine uses the syslogd daemon to write messages to the log files defined in the etc/syslog.conf file. The Attach Manager daemon uses the LOG_DAEMON facility code on all its syslog calls. On most DIGITAL UNIX systems, this causes the syslogd daemon to write the Attach Manager daemon's messages to the file /var/adm/syslog.dated/daemon.log. The messages have the following format: timestamp node-name LU62_AMD[process-id]: message-string Refer to the "Implementation Specifics" chapter in the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Programming manual for a list of syslog messages and their meanings. Preparing the LU6.2 Client Software 5-7 6 _________________________________________________________________ Defining the LU6.2 Interface This chapter discusses how to define the LU6.2 interface entities required for LU6.2 transaction program message exchange. This chapter discusses the following topics: o The APPC Control Operator Functions (see Section 6.1). o Managing the LU6.2 interface (see Section 6.2). o Running the LU6.2 Manager utility (see Section 6.3). o Using the LU6.2 Manager's main window menu bar (see Section 6.4). o DIGITAL SNA gateway considerations (see Section 6.5). 6.1 The APPC Control Operator Functions Before you use an LU6.2 Server for LU6.2 communication, you must define the LU6.2 interface. The LU6.2 programming interface described in IBM's document Systems Network Architecture Transaction Programmer's Reference Manual for LU Type 6.2 includes a set of verbs (called LU definition verbs) that allow APPC programmers to define their LU6.2 interface. The LU6.2 programming interface also includes two more sets of verbs: the change number of session (CNOS) verbs and the session activation and deactivation verbs. The CNOS verbs allow APPC programmers to initialize and change session limit parameters for local and remote LUs. The session activation verbs allow APPC programmers to force an activation or deactivation of a session. Together these three sets of verbs are known as the Control Operator (COPR) verbs. Defining the LU6.2 Interface 6-1 6.2 Managing the LU6.2 Interface The APPC server software includes an easy-to-use graphical user interface called the LU6.2 Manager that implements the COPR verbs. This allows APPC programmers to concentrate on writing LU6.2 transaction programs and to leave the management of the LU6.2 interface to a designated network manager. You can use use the LU6.2 Manager to manage any LU6.2 Server visible to the manager over the TCP/IP or DECnet network. The manager provides a scroll region that allows you to have management sessions open to several servers simultaneously. ________________________ Notes ________________________ DIGITAL's APPC programming interface software includes the COPR verbs in case advanced transaction programs want to manage the LU6.2 Server themselves. This chapter discusses the graphics-based LU6.2 Manager utility. For backward compatibility, the APPC software also contains the text-based LU6.2 Server Configuration Utility provided in previous versions of the software. See Appendix C for a discussion on how to use this utility to manage the LU6.2 Server. Use the LU6.2 Server Configuration Utility when you don't have access to a graphics terminal but you do have access to a video terminal. The APPC software also includes the LU6.2 Script Processor provided in previous versions of the software. The Script Processor provides a set of operators that allow you to create a minimal server configuration. See Appendix E for a discussion on how to use this utility to manage the LU6.2 Server. Use the LU6.2 Script Processor when you don't have access to either a graphics terminal or a video terminal but you do have access to a hardcopy terminal. ______________________________________________________ 6-2 Defining the LU6.2 Interface 6.3 Running the LU6.2 Manager Utility To run the LU6.2 Manager utility, enter the following command: # /usr/lib/sna/lu62_manager 6.4 Using the LU6.2 Manager's Main Window Menu Bar After you start the LU6.2 Manager, the manager displays its main window. The main window contains a menu bar with the following options: File Use this menu to access options to add and delete LU6.2 Servers and to manipulate server configuration files. Define Use this menu to define new entities on the selected LU6.2 Server. Display Use this menu to display existing entities on the selected LU6.2 Server. Delete Use this menu to delete existing entities on the selected LU6.2 Server. Session Use this menu to change session limits and activate and deactivate sessions. Help Use this menu to access the LU6.2 Manager's online help. The sections that follow give a brief introduction to the options available on each menu. Invoking each option brings up a unique management window. For more information about these management windows, use the online help for the window and the context-sensitive online help for the window's option. 6.4.1 The File Menu The file menu has the following options: Add Server Use this option to add a server to the list of servers that you can manage with this LU6.2 Manager window. The server you select is added to the list of servers and becomes the current server. Defining the LU6.2 Interface 6-3 ________________________ Note ________________________ When you use this option, the LU6.2 Manager connects to the server and displays the current configuration of the server. If you wish to load a predefined configuration onto the server, you must then use the Load Configuration option. ______________________________________________________ Load Configuration File Use this option to load a saved configuration from a configuration file. When you choose this option, the LU6.2 Manager uses a standard file selection pop-up menu to prompt for the file name. _______________________ Caution _______________________ Using this option completely overwrites any existing configuration information on the LU6.2 Server. ______________________________________________________ You can create a configuration file by using an editor or by executing the Save Configuration File option. For information about the syntax used in the configuration file, see the appendix entitled "The LU6.2 Server Configuration File Syntax" in the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Installation manual. Parse Configuration File Use this option to parse an LU6.2 Server configuration file. When you choose this option, the LU6.2 Manager uses a standard file selection pop-up menu to prompt for the file name. The LU6.2 Manager reads the indicated file and verifies that it conforms to the syntax requirements for LU6.2 Server configuration files. ________________________ Note ________________________ This option does not load the configuration. Use this option when you have created the configuration file using an editor, or you have modified an existing configuration file and wish to verify that it still conforms to the proper syntax. ______________________________________________________ 6-4 Defining the LU6.2 Interface You can create a configuration file by using an editor or by executing the Save Configuration File option. For information about the syntax used in the configuration file, see the appendix entitled "The LU6.2 Server Configuration File Syntax" in the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Installation manual. Save Configuration File Use this option to save all the changes you made to the current LU6.2 Server in a new LU6.2 server configuration file. When you choose this option, the LU6.2 Manager uses a standard file selection pop-up menu to prompt for the file name. ________________________ Note ________________________ You should select this option BEFORE selecting a new current server if you wish to save the existing configuration. ______________________________________________________ For information about the syntax used in the configuration file, see the appendix entitled "The LU6.2 Server Configuration File Syntax" in the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Installation manual. Remove Server Use this option to remove the current server from the list of servers you can manage with this LU6.2 Manager window. ________________________ Note ________________________ This does not affect the operation of the associated LU6.2 Server. The server continues to operate with the configuration as it exists when you use this option. ______________________________________________________ To manage the server again, you must use the Add Server option and reestablish a management connection to the server. Defining the LU6.2 Interface 6-5 Exit Use this option to exit the LU6.2 Manager program. ______________________ Important ______________________ If you have made changes to the server's configuration and you do not save these changes using the Save Configuration File option, the server reverts to the last saved configuration when you restart the server. ______________________________________________________ 6.4.2 The Define Menu The Define menu has the following options: Local LU Use this option to create a new local LU definition. This option brings up the Define Local LU Window. Remote LU Use this option to create a new remote LU definition. This option brings up the Define Remote LU Window. Mode Name Use this option to create a new mode name definition. This option brings up the Define Mode Window. TP Name Use this option to create a new TP name definition. This option brings up the Define Transaction Program Window. 6.4.3 The Display Menu The Display menu has the following options: Local LU Use this option to display an existing local LU definition. This option brings up the Display Local LU Window. Remote LU Use this option to display an existing remote LU definition. This option brings up the Display Remote LU Window. Mode Name Use this option to display an existing mode name definition. This option brings up the Display Mode Window. 6-6 Defining the LU6.2 Interface TP Name Use this option to display an existing transaction program name definition. This option brings up the Display Transaction Program Window. 6.4.4 The Delete Menu The Delete menu has the following options: Local LU Use this option to delete an existing local LU definition. This option brings up the Delete Local LU Window. Remote LU Use this option to delete an existing remote LU definition. This option brings up the Delete Remote LU Window. Mode Name Use this option to delete an existing mode definition. This option brings up the Delete Mode Window. TP Name Use this option to delete an existing transaction program name definition. This option brings up the Delete Transaction Program Window. 6.4.5 The Session Menu The Session menu has the following options: Activate Use this option to activate a new session for a given remote LU/mode pair. This option brings up the Activate Session Window. Deactivate Use this option to deactivate an existing session for a given remote LU/mode pair. This option brings up the Deactivate Session Window. Change Limit Use this option to change the number of sessions allowed for a given remote LU/mode pair and to change the contention-winner ratio between the source and target LU. This option brings up the Session Change Window. Defining the LU6.2 Interface 6-7 Reset Limit Use this option to reset one or more remote LU/mode pairings. This resets to zero the maximum session limit allowed for the LU/mode pair. This option brings up the Session Reset Window. 6.4.6 The Help Menu The LU6.2 Manager Help menu includes the following options: Getting Provides a path through the help text that Started allows you to minimally configure an LU6.2 Server. Overview Provides a method for accessing help information based on what entity you are trying to manage. Main Provides help on using the main window of the Window LU6.2 Manager. Using Help Provides help on using the DECwindows Help system. Error Provides information about the LU6.2 Manager's Messages error messages. Product Provides product version information and Information product copyright notices. Context- Provides a special cursor that can be dropped Sensitive on any field to obtain information specific to Help that field. 6.5 DIGITAL SNA Gateway Considerations This section discusses issues you must consider when you define a local LU on the LU6.2 Server and when you define its associated LU on the gateway. o Choosing the LU name on the LU6.2 Server The fully-qualified LU name you choose on the LU6.2 Server must be unique in the SNA network name. When the LU's capability is Primary or Secondary, the fully- qualified LU name on the LU6.2 Server must replicate the gateway's LU name exactly. When the LU's capability is Secondary (or the LU is implemented by the DECnet SNA Gateway for Channel Transport or DECnet SNA Gateway for 6-8 Defining the LU6.2 Interface Synchronous Transport product), you can choose any valid unique LU name. o Specifying the gateway information on the LU6.2 Server When you define a local LU on the LU6.2 Server you must provide information about the gateway where the LU is implemented. You must indicate the gateway's node name and the transport that the LU6.2 Server should use to reach the gateway. In addition to identifying the gateway that implements the LU you must identify the gateway LU that you wish the gateway to use. - For LUs with a capability of Secondary, you can use an existing access name to select an LU on the gateway. Access names allow you to specify the LU name, the remote LU, and optional user data all with a single reference. You can also explicitly select an LU on the gateway. For the DECnet SNA Gateway for Channel Transport and DECnet SNA Gateway for Synchronous Transport products, you specify this name using the format pu-name.session-address. pu- name is the name of a physical unit (PU) defined on the gateway. session-address is the name of an LU defined on the gateway. If you specify the gateway's LU name explicitly, it overrides the LU names in the gateway's access name. - For LUs with a capability of Primary or Secondary, you must always explicitly select an LU on the gateway. You can define optional user data that the LU6.2 Server should transmit when it establishes a session. If you specify user data explicitly, it overrides the user data in the gateway's access name. o Setting the LU session limit on the gateway The local LU definition in the gateway should have no session limit specified. If it does, it should be a value greater than or equal to 44. o Creating the LU6.2 Server's SNA access server object on the gateway Defining the LU6.2 Interface 6-9 For LUs with a capability of Primary or Secondary, the gateway's LU definition should also reference an SNA Access Server Object entity on the gateway. The gateway's object definition must contain the node or host name of the LU6.2 Server associated with the corresponding local LU and either the server's DECnet task name or TCP/IP service name. The task name or service name must match the object or service definitions the LU6.2 Server declares for itself (see Section 4.1). If the gateway does not support service name translation facilities, use the LU6.2 Server's port number. o Using LU6.2 sessions within a DIGITAL SNA Peer Server If communication between one or more LU6.2 Servers is going to take place using a single DIGITAL SNA Peer Server, you must create and enable an intranode Transmission Group (TG) on the Peer Server. Refer to the Peer Server documentation for more information on defining an intranode TG. If you use the intranode TG, you must create and enable a SNA LU Services Partner LU entity with indicates the Destination Name (same as the LU Name), the Destination Network (same as the NETID) and the Transmission Group to use (the intranode TG must be specified). The other DIGITAL SNA gateways do not support session establishment between LUs defined in the gateway. 6-10 Defining the LU6.2 Interface 7 _________________________________________________________________ A Complete Configuration Example This chapter provides a complete example of how to configure the LU6.2 Server and a DIGITAL SNA gateway to provide the communication path and LU6.2 interface environment necessary to allow a DIGITAL UNIX transaction program to communicate with an IBM transaction program. The chapter discusses the following: o The sample configuration (see Section 7.1) o Configuring the DIGITAL SNA gateway (see Section 7.2). o Preparing the LU6.2 Server environment (see Section 7.3). o Preparing the LU6.2 client environment (see Section 7.4). o Configuring the LU6.2 Server (see Section 7.5). o Configuring the CPI-C interface (see Section 7.6). o Building the APINGD sample program (see Section 7.7). o Invoking APING under VTAM (see Section 7.8). A Complete Configuration Example 7-1 7.1 The Sample Configuration Figure 7-1 shows the sample configuration used for the example described in this chapter. The subsections that follow discuss the information in the figure. 7-2 A Complete Configuration Example IBM System The example uses VTAM's DISPLAY NET,APING command. This command invokes VTAM's APING program. The APING program is a program you can use to test for connectivity between two LU6.2 logical units. A companion program, APINGD, serves the role of server to APING's client request. Depending on the options the user chooses when invoking APING, APINGD either echoes the data sent to it or provides a confirmation that it received the data. The table below shows the information about the SNA system pertinent to this example: SNA network ID USDEC001 Local LU name NETVW001 Remote LU name LU62S001 Transaction program APING name DIGITAL SNA Gateway This example uses the DIGITAL SNA Peer Server gateway. The DIGITAL SNA Peer Server is a member of DIGITAL's family of SNA transport products which, when suitably configured, connects DIGITAL DECnet or TCP/IP networked systems to an IBM SNA environment. The Peer Server gateway is a layered product running on DIGITAL UNIX. The Peer Server represents a SNA Type 2.1 node and can connect to the SNA network using SDLC, LLC2, or QLLC data links. The table below shows the information about the Peer Server pertinent to this example: Gateway node type TCP/IP Gateway node name peer01.usa.cmp.com SNA network ID USDEC001 Gateway local LU LU62S001 name Gateway remote LU NETVW001 name A Complete Configuration Example 7-3 SNA Access Server LU62SRV Object ________________________ Note ________________________ This example assumes that you have already configured a transmission group and its underlying data link. The LU6.2 interface imposes no configuration constraints on these management entities. ______________________________________________________ LU6.2 Server The LU6.2 Server is a DIGITAL SNA access routine. The server provides logical unit Type 6.2 connectivity between transaction programs in the IBM SNA network and transaction programs on DIGITAL UNIX systems. The table below shows the information about the LU6.2 Server pertinent to this example: LU6.2 Server node TCP/IP type LU6.2 Server node lu62srv1.usa.cmp.com name LU6.2 Server name LU62_SRV Local LU name USDEC001.LU62S001 Remote LU name USDEC001.NETVW001 Mode name MODELU62 Transaction program APINGD LU6.2 Client The LU6.2 client is the DIGITAL UNIX transaction program that uses the LU6.2 Server to communicate with the IBM LU6.2 transaction program. The client interface is a set of callable C routines that are linked with a user- written transaction program (in this case a supplied sample program) to form an executable image. The LU6.2 Server supports, through a daemon called the Attach Manager, the automatic initiation of a DIGITAL UNIX transaction program as a result of an allocation request from a requesting transaction program. Because APINGD is 7-4 A Complete Configuration Example requested by the IBM APING program, this example makes use of the Attach Manager daemon. The DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product actually supports two programming interfaces: the LU6.2 protocol boundary described in IBM's Systems Network Architecture Transaction Programmer's Reference Manual for LU Type 6.2 and the CPI-C programming interface described in CPI Communications V1.2 Communications. This example uses a CPI-C version of the APINGD program. The table below shows the information about the LU6.2 client pertinent to this example: Client node name lu62srv1.usa.cmp.com Client user account user01 Client transaction /usr/users/user01/apingd program ________________________ Note ________________________ Although this example describes a DIGITAL UNIX transaction program that resides on the same node as the LU6.2 Server, this is not a requirement of the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product. In general, the configuration for a separate client node is identical; the discussion notes where there are differences. ______________________________________________________ 7.2 Configuring the DIGITAL SNA Gateway You configure the Peer Server gateway using DIGITAL's Network Control Language (NCL). NCL commands consist of a verb followed by a management entity upon which the verb acts. In this example, you will use the following NCL verbs: CREATE Creates a new Peer Server entity DISPLAY Displays the current attributes of a Peer Server entity A Complete Configuration Example 7-5 ENABLE Enables a Peer Server entity for operation SET Changes the attributes of a Peer Server entity In NCL, the entity name consists of the node name followed by the entity on that node. For example, create node peer01 sna lu services lu l0001s creates the entity sna lu services lu l0001s on node peer01. To reference the local node, use the special node name 0 or omit the node name entirely. NCL is a DECnet utility; therefore, if you use NCL to manage the Peer Server you must either be logged in on the Peer Server's DIGITAL UNIX system or you must access the Peer Server from another DECnet node. All Peer Server NCL commands in this example assume that you are executing them on the Peer Server's local node peer01.usa.cmp.com. 7.2.1 Displaying the Peer Server's Control Point Information This example assumes that you have already defined the Peer Server's control point, transmission group, and data link information. If you have not already done this, see the DIGITAL SNA Peer Server Management manual for information about how to define this information. The control point (CP) on the Peer Server is known by the full entity name of SNA CP SERVICES. Later in this example, you will create LU definitions on the LU6.2 Server. To create these LU definitions, you will need to know the Peer Server's network ID. To display the Peer Server's network ID, enter the following NCL command on the Peer Server node: # ncl ncl> show sna cp services all characteristics This command results in the following display: Node 0 SNA CP Services AT 1997-01-13-14:03:09.000-05:00I----- Characteristics Version = V1.0.0 Network ID = USDEC101 CP Name = PEERCP Maximum Active TGs = 10 7-6 A Complete Configuration Example Note the string displayed for the Network ID characteristic for later use. 7.2.2 Defining the LU6.2 Server's SNA Access Server Object To support connection requests originating in the SNA network, the Peer Server includes an SNA access server. The access server directs these connection requests to the appropriate DIGITAL SNA access routines using the information in its object entities. The object entity on the Peer Server is known by the full entity name of SNA ACCESS SERVER OBJECT. To create the example object on the Peer Server, enter the following NCL command on the Peer Server node: # ncl ncl> create sna access server object lu62srv - _ncl> internet node = lu62srv1.usa.cmp.com, - _ncl> port = 8001, - _ncl> transport = tcpip ________________________ Note ________________________ Use either the service attribute service = LU62_SRV_ SES, or the port attribute, not both. Because you have not yet defined the service name in the etc/services file, the example uses the port attribute. ______________________________________________________ This command defines the SNA access server object lu62srv. When the gateway receives a session initiation request for this object, it passes the request to the LU6.2 Server listening on port 8001 (or the LU6.2 Server represented by the TCP/IP service name LU62_SRV_SES) on internet node lu62srv1.usa.cmp.com. ______________________ Important ______________________ The value you specify for the port or service parameter must match the information you define for the server-name_SES service name on the LU6.2 Server (see Section 7.3). ______________________________________________________ A Complete Configuration Example 7-7 7.2.3 Defining the Peer Server Local LU The local LU entity on the Peer Server is known by the full entity name of SNA LU SERVICES LU. To create the example local LU on the Peer Server, enter the following NCL command on the Peer Server node: # ncl ncl> create sna lu services lu lu62s001 - _ncl> access = unrestricted, - _ncl> capability = both, - _ncl> maximum active sessions = 0, - _ncl> object = LU62SRV This command defines the local LU lu62s001. This LU accepts all SNA access routine requests, has the capability to function as a primary or secondary LU, and has no maximum session limit. When initiating a session as a secondary LU, the LU uses the information in the SNA access server object LU62SRV. ______________________ Important ______________________ The value you specify for the object parameter must match the name you used when you created the SNA access server object. Generally, you should set the maximum active sessions parameter to 0 and specify the true number of active sessions when defining the local LU on the LU6.2 Server (see Section 7.5.2). ______________________________________________________ 7.2.4 Enabling the Peer Server Local LU When you create a local LU on the Peer Server, it is not available for service. To make the LU available for use by SNA access routines, you must enable the LU. To enable the example local LU on the Peer Server, enter the following NCL command on the Peer Server node: # ncl ncl> enable sna lu services lu lu62s001 7-8 A Complete Configuration Example 7.2.5 Displaying the Peer Server's Transmission Group Information This example assumes that you have already defined the Peer Server's control point, transmission group, and data link information. If you have not already done this, see the DIGITAL SNA Peer Server Management manual for information about how to define this information. To define the remote LU on the Peer Server, you will need to reference a transmission group on the Peer Server. To display the Peer Server's transmission groups, enter the following NCL command on the Peer Server node: # ncl ncl> show sna cp services transmission group * name This command results in a display similar to the following: Node 0 SNA CP Services Transmission Group Intranode AT 1997-01-20-10:29:54.221-05:00I0.088 Identifiers Name = Intranode _______ Node 0 SNA CP Services Transmission Group tgsdlc0 AT 1997-01-20-10:29:54.231-05:00I0.088 Identifiers Name = tgsdlc0 Determine which transmission group you wish to use when defining the remote LU on the Peer Server. After you select a transmission group, you should verify the status of the transmission group. To verify the transmission group's status, enter the following NCL command on the Peer Server node: # ncl ncl> show sna cp services transmission group tgsdlc0 - _ncl> all status A Complete Configuration Example 7-9 This command results in the following display: Node 0 SNA CP Services Transmission Group tgsdlc0 AT 1997-02-10-10:58:00.000-05:00I----- Status UID = C3F1112E-7FD2-11D0-8010-08002B2FF31B State = On Protocol State = Connected-PU Active INIT_SELF Supported = No BIND Supported = No Adjacent Node BIND Assembly = Unsupported BIND Pacing Support = No Dependent LU BIND Pacing = No SSCP Mediated Sessions = No Adjacent Station Node ID = '00000000'H Adjacent Network ID = "" Adjacent Station CP Name = "" Adjacent Station PU Name = "" Adjacent Station ALS Name = "" ______________________ Important ______________________ Verify that the State value is On and that the Protocol State value is Connected-PU Active. ______________________________________________________ 7.2.6 Defining the Peer Server Partner (Remote) LU The remote LU entity on the Peer Server is known by the full entity name of SNA LU SERVICES PARTNER LU. To create the example remote LU on the Peer Server, enter the following NCL command on the Peer Server node: # ncl ncl> create sna lu services partner lu netvw001 - _ncl> destination name = netvw001, - _ncl> destination network = usdec001, - _ncl> transmission group = { tgsdlc0 } This command defines the remote LU netvw001. This LU is used to establish sessions with LU netvw001 in network usdec001. The communication takes place over TG tgsdlc0. 7-10 A Complete Configuration Example ______________________ Important ______________________ The name you use for the remote LU must match the LU's name on the IBM system. ______________________________________________________ This completes the preparation of the Peer Server gateway. 7.3 Preparing the LU6.2 Server Environment To prepare the LU6.2 Server environment after installation, do the following on the LU6.2 Server's node: 1. Using an editor, enter the following LU6.2 Server TCP/IP service names in the DIGITAL UNIX system's /etc/services file: LU62_SRV_SES = 8001/tcp LU62_SRV_CLI = 8000/tcp 2. Also, enter the following Attach Manager service name in the /etc/services file: LU62_AMD = 8101/tcp 3. In this example, you will be managing the LU6.2 Server from the node on which the server software is installed. If you will be managing the server from some other node, you should create a server access validation file at this time. 4. If the server is not already started, start the server by executing the following command: # /sbin/init.d/lu62_startup start See Chapter 4 for more detailed information about each of these operations. ______________________ Important ______________________ The information you specify for the LU6.2 Server's server-name_SES service name must match the information you specify for the port or service parameter when you define the gateway's SNA Access Server Object entity (see Section 7.2.2). If you were configuring a separate client node, the information you would specify for the LU6.2 Server's A Complete Configuration Example 7-11 server-name_CLI and LU62_AMD service names would have to match the information you specify for the these service names on the client node (see Section 7.4). ______________________________________________________ 7.4 Preparing the LU6.2 Client Environment To prepare the LU6.2 client environment after installation, do the following on the client node: 1. In this example, the LU6.2 Server's node and the LU6.2 client's node are the same node. Therefore, you have already defined the service name needed by the LU6.2 client interface. However, if the client software was on a different node, you would need to enter the following LU6.2 Server TCP/IP service name in the DIGITAL UNIX system's /etc/services file on the client node: LU62_SRV_CLI = 8000/tcp 2. In this example, the LU6.2 Server's node and the LU6.2 client's node are the same node. Therefore, you have already defined the service name for the Attach Manager daemon. However, if the client software was on a different node, you would need to enter the following Attach Manager service name in the /etc/services file on the client node: LU62_AMD = 8101/tcp 3. Create the Attach Manager's access validation file in /usr/lib/sna/lu62_amd.access and insert the following line: lu62srv1.usa.cmp.com::TCPIP::LU62_SRV::user01 4. To have the Attach Manager's access validation take effect, you must stop and restart the Attach Manager daemon. If the Attach Manager daemon is already running, stop the daemon by executing the following command: # /sbin/init.d/lu62_startup stop Next, start the daemon by executing the following command: # /sbin/init.d/lu62_startup start 7-12 A Complete Configuration Example See Chapter 5 for more detailed information about each of these operations. ______________________ Important ______________________ If you were configuring a separate client node, the information you would specify for the client's server-name_CLI and LU62_AMD service names would have to match the information you specified for the these service names on the LU6.2 Server's node (see Section 7.3). ______________________________________________________ 7.5 Configuring the LU6.2 Server As discussed in this manual, the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product provides several methods to manage the LU6.2 Server. The example in this chapter does not show exactly how to enter the information, rather it describes the information that you must enter. For exact information about how to enter the information, see the online help for the LU6.2 Manager or Appendix C for the LU6.2 Configuration Utility. 7.5.1 Selecting the LU6.2 Server The first step to managing an LU6.2 Server is to make the management interface aware of the server you wish to manage. Using the LU6.2 Manager's Add Server option on the File menu, or the LU6.2 Server Configuration Utility's Specify the LU6.2 Server option, enter the following information about the LU6.2 Server: Server name LU62_SRV Server node 0 (indicates the server is on the local node) Transport TCPIP This information specifies the LU6.2 Server LU62_SRV on the local TCP/IP node. A Complete Configuration Example 7-13 7.5.2 Defining the LU6.2 Server's Local LU You must begin the interface definition by defining a local LU on the server. Using the LU6.2 Manager's Local LU option on the Define menu, or the LU6.2 Server Configuration Utility's Define Local LU option, enter the following information about the local LU: Fully-qualified USDEC001.LU62S001 local LU name Alias name LU62S001 Maximum session 0 limit Security None Session activation No (Option 2 in the LU6.2 Server Configuration Utility) Maximum Confirm synchronization Gateway node peer01.usa.cmp.com Gateway transport TCP/IP LU session Primary or Secondary capability Gateway LU None authorization password Gateway access name None Gateway LU name None User data None This information defines the local LU USDEC001.LU62S001. The LU has the alias LU62S001. The LU has no session limit and requires no security information to establish sessions. The LU does not require that the snalu62_attach_ listen verb be issued before establishing sessions. The LU is supported by the LU LU62S001 on the Peer Server at node peer01.usa.cmp.com. The LU supports both primary and secondary sessions. The access name, gateway LU name, and user data options are not used. 7-14 A Complete Configuration Example ______________________ Important ______________________ The name you specify for the local LU must have as its first component the Network ID parameter of the Peer Server's SNA CP Services entity (see Section 7.2.1). The second component of the LU name must match the name you specified for the LU on the Peer Server (see Section 7.2.3). ______________________________________________________ 7.5.3 Defining the LU6.2 Server's Remote LU Next, define a remote LU associated with the local LU. Using the LU6.2 Manager's Remote LU option on the Define menu, or the LU6.2 Configuration Utility's Define Remote LU option, enter the following information about the remote LU: Local LU name LU62S001 Fully-qualified USDEC001.NETVW001 remote LU name Remote LU alias NETVW001 Initiate type Initiate Only Parallel session Yes support CNOS support Yes LU-LU password None Security acceptance None This information defines the remote LU USDEC001.NETVW001 with an alias of NETVW001. The remote LU is associated with the local LU LU62S001. The remote LU's SSCP should process any session initiation request immediately or return an error if this is not possible. The remote LU supports parallel session and change-number-of-session (CNOS) processing. Requests from this remote LU do not need any security information. ______________________ Important ______________________ The name you specify for the remote LU must have as its first component the Network ID parameter of the Peer Server's SNA CP Services entity (see Section 7.2.1). The second component of the remote A Complete Configuration Example 7-15 LU name must match the name you specified for the remote LU on the Peer Server (see Section 7.2.6). ______________________________________________________ 7.5.4 Defining the LU6.2 Server's Mode The specification of the local LU and the remote LU does not define all the information about how the server creates a particular session. To specify the remainder of this session information, a transaction program specifies a mode name. Using the LU6.2 Manager's Mode Name option on the Define menu, or the LU6.2 Server Configuration Utility's Define Mode Name option, enter the following information about the mode: Local LU name LU62S001 Remote LU name NETVW001 Mode name MODELU62 Send lower max RU 1024 size Send upper max RU 1024 size Send preferred max 1024 RU size Recv lower max RU 1024 size Recv upper max RU 1024 size Recv preferred max 1024 RU size Single session Undefined reinitiation Conwinner auto 0 activate limit Local LU/mode 8 session limit This information defines the mode MODELU62. This mode is associated with the remote LU NETVW001 which in turn is associated with the local LU LU62S001. The requested maximum RU size for both send and receive is 1024. The upper and lower bounds for the maximum RU sizes are also 7-16 A Complete Configuration Example 1024. Because this mode is for a multi-session mode, the single session reinitiation is undefined. The mode has a session limit of 8 of which none are automatically activated during session limit initiation processing. ______________________ Important ______________________ The name you specify for the mode must match a mode name on the IBM system. ______________________________________________________ 7.5.5 Defining the Transaction Program If your transaction program accepts unsolicited incoming requests you must define the transaction program. This example uses such a transaction program, the APINGD transaction program included in the distribution kit. Using the LU6.2 Manager's TP Name option on the Define menu, or the LU6.2 Server Configuration Utility's Define TP Name option, enter the following information about the transaction program: Local LU name LU62S001 TP name APINGD Status Enabled Conversation type Basic and Mapped Synchronization None and Confirm level Security required None Security access info None PIP data No Instance limit 1 Attach Manager node lu62srv1.usa.cmp.com name Attach Manager user user01 ID Attach Manager /usr/users/user01/apingd command string A Complete Configuration Example 7-17 Attach Manager Yes started This information defines the transaction program APINGD. It is associated with the local LU LU62S001. It is enabled and therefore available for incoming allocation requests. The program accepts both basic and mapped conversations with synchronizations level of both none and confirm. The program does not require nor supply any security information. The program expects no Program Initialization Parameter (PIP) data. Only one concurrent copy of the program can run on the DIGITAL UNIX system. The program is started by the Attach Manager daemon on node lu62srv1.usa.cmp.com under the user user01 using the command /usr/users/user01/apingd. 7.5.6 Initializing the Session Limits Defining the LU6.2 Server entities does not actually cause the LU6.2 Server to establish any sessions or to exchange any session limit information with the IBM system. To do this, you must initialize the mode's session limits. You must initialize a special predefined mode, SNASVCMG, before you initialize any other modes. In most cases, the LU6.2 Server uses the SNASVCMG mode sessions to negotiate the session limits for all other modes. Using the LU6.2 Manager's Change Limits option on the Session menu, or the LU6.2 Server Configuration Utility's Change Session Limit option, enter the following information about the mode SNASVCMG: Mode Session Limit 2 (hard coded value) Min Conwinners 1 (hard coded value) Source Min Conwinners 1 (hard coded value) Target This information initializes the mode SNASVCMG. It sets the mode's session limit at the architected limit of 2 with 1 contention winner for the source LU and 1 for the target LU. 7-18 A Complete Configuration Example Using the LU6.2 Manager's Change Limits option on the Session menu, or the LU6.2 Server Configuration Utility's Change Session Limit option, enter the following information about the mode MODELU62: Mode Session Limit 8 Min Conwinners 4 Source Min Conwinners 4 Target Responsibility Source This information initializes the mode MODELU62. It sets the mode's session limit to 8 with 4 contention winner for the source LU and 4 for the target LU. 7.5.7 Saving the Configuration After entering a configuration for an LU6.2 Server, you may wish to save this configuration for future use. During server startup, the server automatically configures itself if it finds a saved configuration file. Using the LU6.2 Manager's Save Configuration File option on the File menu, or the LU6.2 Server Configuration Utility's Save Configuration option, enter the following information: File name /usr/lib/sna/LU62_SRV.cfg This information causes the management program to save the server's current configuration to the file /usr/lib/sna/LU62_SRV.cfg. When the server is restarted at a later time, it will find this file and load the configuration present in the file. 7.6 Configuring the CPI-C Interface The CPI-C interface uses a file called the side information file to specify the default information about a transaction program's conversation characteristics. In most cases, you would create a separate entry for your transaction program and the program would reference that entry when it allocates a conversation. However, in the case of the APINGD program, the program does not specify a local TP name. Therefore, you must modify the DEFAULT entry in the side file. The installation procedure installs a sample side information file in the file /etc/cpic.conf. A Complete Configuration Example 7-19 To configure the CPI-C side information file, do the following: 1. Copy the file /etc/cpic.conf to your home directory under the name cpic.conf. 2. Using an editor, change the local_lu_name line under the DEFAULT entry to the following: local_lu_name = USDEC001.LU62S001 ______________________ Important ______________________ The name you specify for the local_lu_name must match the name you specified when you defined the local LU on the LU6.2 Server (see Section 7.5.2). ______________________________________________________ 7.7 Building the APINGD sample program The installation script installs several sample transaction programs in the directory usr/lib/sna/examples. To prepare the APINGD program, do the following: 1. Copy the files in the usr/lib/sna/examples directory to the home directory for user01. 2. Build the APINGD program in the user01 directory using the following command: # make -f makefile.cpic 7.8 Invoke APING under VTAM This example uses VTAM's DISPLAY NET,APING command to send test data to the APINGD program you just built. For the purposes of this example, you should specify the following command options: ID LU62S001 LOGMODE MODELU62 In addition, you can use the following options to control how much test data is sent, how many times the data is sent, and whether the test data is returned to the APING program. 7-20 A Complete Configuration Example SIZE Specifies the number of data bytes to send. The default is 100. CONSEC Specifies the number of consecutive transmissions. The default is 1. ITER Specifies the number of times to send the consecutive transmissions specified by the CONSEC and SIZE keywords. The default is 2. ECHO Indicates whether you wish the data returned. The default is ECHO=YES. For example, to send 2 consecutive transmissions of 300 bytes each 10 times and receive back all the data sent, enter the following command: DISPLAY NET,APING,ID=LU62S001,LOGMODE=MODELU62,SIZE=300,CONSEC=2,ITER=10 For additional information about the APING program available under VTAM, see the appropriate VTAM Operation manual. ______________________ Important ______________________ The ID (LU62S001) must match the local LU you defined on the Peer Server (see Section 7.2.3). The LOGMODE (MODELU62) must match the mode you defined on the LU6.2 Server (see Section 7.5.4). ______________________________________________________ 7.9 Troubleshooting If VTAM returns an error message check the following items: o Verify that the file apingd is in the home directory for user01. o Verify that there is a cpic.conf file in the home directory for user01. Verify that its local_lu_name definition is USDEC001.LU62S001. o Using the LU6.2 Manager, select the LU6.2 Server LU62_ SRV on the local node. Select the local LU LU62S001 and the remote LU LU62S001. Verify that the active sessions window shows at least two active sessions: one for the mode SNASVCMG and one for MODELU62. If you do not see A Complete Configuration Example 7-21 any active sessions, you may have forgotten to enable the LU on the Peer Server. o Select the TP Name APINGD. Verify that you have set up the Attach Manager data correctly. o Verify that you have made the correct entry in the Attach Manager's access validation file. Check for the correct node name and user name. This information must match the Attach Manager information you defined for the transaction program. o Verify that you have defined the TCP service names in the /etc/services file. The LU62_SRV_SES definition must match the port number defined in the Peer Server's SNA access server object. 7-22 A Complete Configuration Example 8 _________________________________________________________________ Troubleshooting This chapter provides help in diagnosing problems that you may encounter while using the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product. The problems are presented in the order that you are likely to encounter them. The following problems are discussed: o No contact with LU6.2 Server (see Section 8.1). o Server configuration not what expected (see Section 8.2). o Unable to initialize session limits (see Section 8.3). o Unable to activate sessions (see Section 8.4). o Unable to activate DIGITAL UNIX transaction programs using the Attach Manager daemon (see Section 8.5). o APPC/LU6.2 programs function correctly but CPI-C programs do not (see Section 8.6). Troubleshooting 8-1 8.1 No Contact with LU6.2 Server Problem Statement: You have successfully installed the server and client software subsets. You have prepared the client and server software as described in Chapter 4 and Chapter 5. When you invoke the LU6.2 Manager (or any other transaction program) to manage the server, you are not successful in reaching the server. Diagnostic 1: You receive the following messages: %SNALU62-E-PRGPARCHK, Program parameter check -SNALU62-E-NOPRIV, for verb snalu62_display_xxxx, the process must be in the system group to execute this verb Your process does not have system group privileges. You are required to have system group privileges to execute any Control Operator (COPR) verbs. When the manager accesses a server, the first operation it attempts is a set of display verbs to gather the server's current configuration information. Because these display verbs are COPR verbs, the operation fails if the user is not in the system group. Diagnostic 2: You receive a set of error messages beginning with the following three messages: %SNALU62-E-UNSUC, LU6.2 verb did not execute successfully -SNALU62-E-COMERR, connection to server has failed -SNALU62-E-FAICONSRV, failed to establish connection with the server These messages indicate that the manager was not able to contact the server. The messages above are followed by a message describing the reason for the failure. The following are the most common messages: -SYS-?-NONAME, No such file or directory -SYS-?-NONAME, No such process For the TCP/IP transport, receiving either of these errors indicates that the TCP/IP service name (server- name_CLI) for the server you are using is not defined in the manager node's /etc/services file. -SYS-?-NONAME, Connection refused 8-2 Troubleshooting For TCP/IP transports, this error indicates either that the TCP/IP service name (server-name_CLI) for the server is not properly defined in the server's /etc/services file or that the server is properly defined but is not currently running. -SYS-?-NONAME, Bad file number For the DECnet transport, this error indicates that the server's object is not known on the server node. This means the server is not currently running. Diagnostic 3: You receive a set of error messages that either consists entirely of the following two lines or one that begins with the following two lines: %SNALU62-E-UNSUC, LU6.2 verb did not execute successfully -SNALU62-E-NOCLIACC, client not authorized to modify the server This error indicates that your process has system group privileges, that the server names are defined correctly, and that the server is currently running. However, you are not listed in the server's access validation file. If, in addition to the preceding two lines, you also receive the following error: -SNALU62-E-NOHOSTFILE, server access validation file could not be read the server's access validation file does not exist or could not be read by the LU6.2 Server. Troubleshooting 8-3 8.2 Server Configuration Not What Expected Problem Statement: When you invoke the LU6.2 Manager to display the server or when you use the server in transaction programs, the server's configuration is not what is expected. Diagnostic 1: For TCP/IP transports, this condition can occur when you are referencing a defined TCP/IP port on the server's node but the port does not reference the correct server. For example, the manager's node may have LU62_SRV_CLI defined as port 8001 and the server node may have MY_SRV_CLI defined as 8001. In this case, all management connection request to the server LU62_SRV actually connect to the server MY_SRV. In addition, for DECnet and TCP/IP transports, a server name can be used on multiple nodes. It is the combination of a node name and server name that uniquely identifies a server. You could be referencing the correct server name but the wrong node name. Diagnostic 2: You may have modified a server's configuration but forgotten to save the changed configuration before you left the manager. Verify whether other changes you made in your last management session are also missing. Diagnostic 3: Other managers or transaction programs may have changed the server's configuration. ________________________ Note ________________________ The LU6.2 Manager does not perform dynamic updates of the server's configuration. Therefore, if another program (or another manager) has made a change to the configuration, you will not see this change. You can refresh the manager's status for a server by clicking on the server's line in the display area in the upper left of the manager's main window. ______________________________________________________ 8-4 Troubleshooting 8.3 Unable to Initialize Session Limits Problem Statement: You are able to access the requested server for most management functions. However, you are unable to initialize the session limits for a mode. Diagnostic 1: You receive the following messages: %SNALU62-E-RESFNO, resource failure no retry -SNALU62-E-NOCNOS, no sessions available to conduct CNOS session limit negotiation These errors indicate that you have not yet initialized the session limits for the SNASVCMG mode. These session limits must be set first in order for any CNOS processing to take place using other modes. These messages could also be returned if the remote LU is not in a state to start a session or if the remote LU is unknown. Diagnostic 2: The error conditions for session initialization also include the session activation errors described in the next section. Troubleshooting 8-5 8.4 Unable to Activate Sessions Problem Statement: You are able to access the requested server for most management functions. However, you cannot activate a session. Diagnostic 1: ) You receive the following messages: %SNALU62-E-PARERR, parameter error, routine snalu62_activate -SNA-E-UNKLOGMOD, the logon mode specified does not exist These messages indicate that you have tried to activate a session with a mode name unknown to the LU6.2 Server. Diagnostic 2: You receive the following messages: %SNALU62-E-RESFNO, resource failure no retry -SNALU62-E-GATCOM, error communicating with gateway node -SNA-E-INVREMLU, The gateway LU name specified (DESTUNIT) is invalid These messages indicate that you have tried to activate a session using a remote LU on the LU6.2 Server that has no corresponding remote or partner LU on the gateway. See Section 7.2.6 for an example of how to create the remote LU definition on the gateway. Diagnostic 3: You receive the following messages: %SNALU62-E-RESFNO, resource failure no retry -SNALU62-E-GATCOM, error communicating with gateway node -SNA-E-UNKLU, The requested gateway LU (DESTMOD) does not exist These messages indicate that you have tried to activate a session using a local LU on the LU6.2 Server that has no corresponding local LU on the gateway. See Section 7.2.3 for an example of how to create the local LU definition on the gateway. See Section 6.5 for detailed information about items you must consider when defining the local LU on the gateway and when defining the local LU on the LU6.2 Server. 8-6 Troubleshooting Diagnostic 4: You receive the following messages: %SNALU62-E-RESFNO, resource failure no retry -SNALU62-E-BINDSENSE, BIND request rejected with sense code 0X080F6051 These messages indicate that you have tried to activate a session using a local LU on the LU6.2 Server that has an LU-LU password that does not agree with the password set on the IBM system. Diagnostic 5: You receive the following messages: %SNALU62-E-RESFNO, resource failure no retry -SNALU62-E-GATCOM, error communicating with gateway node -SNALU62-E-CONREJREQ, connect request rejected by IBM host sense code 0X087D0001 These messages indicate that you have tried to activate a session using a remote LU on the LU6.2 Server that, although properly defined on the gateway, corresponds to a LU that is not defined on the IBM system. Diagnostic 6: You receive the following messages: %SNALU62-E-RESFNO, resource failure no retry -SNALU62-E-GATCOM, error communicating with gateway node -SNALU62-E-NOSUCPU, no such physical unit These messages indicate that you have tried to activate a secondary session using a local LU on the LU6.2 Server that references an SNA old-style name (pu-name.session-address) that is not defined on the gateway. See the discussion of old-style names in Section 6.5 and in the DIGITAL SNA Peer Server Management manual. Troubleshooting 8-7 8.5 Unable to Activate Transaction Programs Using the Attach Manager Daemon Problem Statement: You are able to use transaction programs that you initiate on the DIGITAL UNIX system but transaction programs invoked on the IBM system that request DIGITAL UNIX transaction programs fail with the sense code 1008600B. You have set up the requested DIGITAL UNIX transaction programs to be automatically started by an Attach Manager daemon. Diagnostics: The Attach Manager daemon records errors in the syslog file. See the Attach Manager section in the "Implementation Specifics" chapter of the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Programming manual for an explanation of these messages. 8-8 Troubleshooting 8.6 APPC Programs Function Correctly but CPI-C Programs Do Not Problem Statement: You are able to successfully run transaction programs that use the LU6.2/APPC interface (the snalu62_xxxxx calls), but you are unable to run transaction programs that use the CPI-C interface. Diagnostic 1: You receive the following messages: filename: line nn: syntax error CM_PROGRAM_PARAMETER_CHECK These messages indicate that the CPI-C side information file referenced by the environment variable CPIC_SYM_FILE (filename does not conform to the guidelines for CPI-C side information file syntax. If you receive only the CM_ PROGRAM_PARAMETER_CHECK error message, the environment variable CPIC_SYM_FILE probably points to a non-existent file. ________________________ Note ________________________ If you have not defined the CPIC_SYM_FILE environment variable, the CPI-C interface attempts to use the default file /etc/cpic.conf created by the installation procedure. ______________________________________________________ Diagnostic 2: You receive the following messages: CM_PARAMETER_ERROR This message frequently indicates that the CPI-C side information file referenced by the environment variable CPIC_SYM_FILE references a local or remote LU not defined on the LU6.2 Server. This is a general error message used by CPI-C. Therefore, it may mean a general parameter error on any call. See the CPI Communications V1.2 Communications manual for more information. Troubleshooting 8-9 A _________________________________________________________________ Sample Installation Dialog This appendix contains a sample installation dialog for the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1 software. # setld -l /mnt/snalu62 DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1-0 (Rev.0) (c) Electronic Data Systems Corporation 1997. All Rights Reserved. (c) Digital Equipment Corporation 1994. All Rights Reserved. This software is proprietary to and embodies the confidential technology of Electronic Data Systems Corporation and Digital Equipment Corporation. Possession, use, duplication or dissemination of this software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation or an authorized sublicensor. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) DIGITAL SNA APPC/LU6.2 Programming Interfaces 2) DIGITAL SNA APPC/LU6.2 Server Or you may choose one of the following options: 3) ALL of the above 4) CANCEL selections and redisplay menus 5) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Sample Installation Dialog A-1 Choices (for example, 1 2 4-6): 3 You are installing the following optional subsets: DIGITAL SNA APPC/LU6.2 Programming Interfaces DIGITAL SNA APPC/LU6.2 Server Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 2 subset(s) will be installed. Loading 1 of 2 subset(s).... DIGITAL SNA APPC/LU6.2 Programming Interfaces Copying from . (disk) Verifying Loading 2 of 2 subset(s).... DIGITAL SNA APPC/LU6.2 Server Copying from . (disk) Verifying 2 of 2 subset(s) installed successfully. DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1-0 (Rev.0) (c) Electronic Data Systems Corporation 1997. All Rights Reserved. (c) Digital Equipment Corporation 1994. All Rights Reserved. Would you like to run IVP for (SNALU62310)? (y/n) [y]: Beginning the IVP for (SNALU62310) IVP for (SNALU62310) has successfully completed. Configuring "DIGITAL SNA APPC/LU6.2 Programming Interfaces V3.1" (SNALU62310) DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, V3.1-0 (Rev.0) (c) Electronic Data Systems Corporation 1997. All Rights Reserved. (c) Digital Equipment Corporation 1994. All Rights Reserved. Would you like to run IVP for (SNAL62S310)? (y/n) [y]: Beginning the IVP for (SNAL62S310) IVP for (SNAL62S310) has successfully completed. Configuring "DIGITAL SNA APPC/LU6.2 Server V3.1" (SNAL62S310) # A-2 Sample Installation Dialog B _________________________________________________________________ Files Installed on Your System This appendix lists the files and softlinks created when you install the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, Version 3.1 software. B.1 Files Created When you install the DIGITAL SNA APPC/LU6.2 Programming Interface subset (SNALU62310), the installation procedure creates the following files: /etc/cpic.conf /sbin/init.d/lu62_startup /usr/include/sna/cpic.h /usr/include/sna/snatprmdf.h /usr/lib/libcpic.a /usr/lib/libsnatprm.a /usr/lib/sna/examples/aping.c /usr/lib/sna/examples/apingd.c /usr/lib/sna/examples/arexec.c /usr/lib/sna/examples/arexecd.c /usr/lib/sna/examples/atell.c /usr/lib/sna/examples/atelld.c /usr/lib/sna/examples/cpiccmc.h /usr/lib/sna/examples/cpicdefs.h /usr/lib/sna/examples/cpicerr.c /usr/lib/sna/examples/cpicerr.h /usr/lib/sna/examples/cpicinit.c /usr/lib/sna/examples/cpicinit.h /usr/lib/sna/examples/cpicportc.c /usr/lib/sna/examples/cpicportc.h /usr/lib/sna/examples/makefile.cpic /usr/lib/sna/examples/sample_receive_pip.c /usr/lib/sna/examples/sample_send_pip.c /usr/lib/sna/examples/sample_setup.c /usr/lib/sna/snatprm_msg.bin Files Installed on Your System B-1 /usr/shlib/libcpic.so /usr/shlib/libsnatprm.so When you install the DIGITAL SNA APPC/LU6.2 Server subset (SNAL62S310), the installation procedure creates the following files: /usr/lib/sna/lu62_manager /usr/lib/sna/lu62_config /usr/lib/sna/lu62_script /usr/lib/sna/examples/sample.setup /usr/sbin/lu62_server /usr/sbin/lu62_amd B.2 Softlinks Created When you install the DIGITAL SNA APPC/LU6.2 Programming Interface subset (SNALU62310), the installation procedure creates the following softlink: /sbin/rc3.d/S91_lu62_server When you install the DIGITAL SNA APPC/LU6.2 Server subset (SNAL62S310), the installation procedure creates no softlinks. B-2 Files Installed on Your System C _________________________________________________________________ Using the Text-Based LU6.2 Server Configuration Utility This appendix describes the procedures for using the text- based LU6.2 Server Configuration Utility to configure the LU6.2 Server. This text-based utility allows you to do the following: 1. Specify the LU6.2 Server (see Section C.2). 2. Define one or more local LUs (see Section C.3). 3. Define one or more remote LUs associated with a particular local LU (see Section C.4). 4. Define one or more mode names associated with a particular remote LU (see Section C.5). 5. Define one or more transaction programs associated with a particular local LU (see Section C.6). 6. Display a list of local LUs and their associated remote LUs and transaction programs (see Section C.7). 7. Initialize the mode session limits (see Section C.8). 8. Reset the mode session Limits (see Section C.9). 9. Activate a session (see Section C.10). 10. Delete LU6.2 interface entities (see Section C.11). 11. Load, parse, and create LU6.2 Server configuration files (see Sections C.12 through Section C.14). For a general description of the LU6.2 Server configuration process, see the chapter entitled "Controlling the APPC/LU6.2 Programming Interface" in the manual DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, Programming. For information specific to the interface provided by the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product, see the chapter entitled "Implementation Specifics" in the same manual. Using the Text-Based LU6.2 Server Configuration Utility C-1 C.1 Running the LU6.2 Server Configuration Utility To run the LU6.2 Server Configuration Utility, use the following command: # /usr/lib/sna/lu62_config After you enter the /usr/lib/sna/lu62_config command, the system displays the following menu screen and prompt: LU6.2 Server Configuration Utility 1 Exit 2 Specify the LU6.2 Server LU6.2 Cfg> To specify an LU6.2 Server, enter 2 at the LU6.2 Cfg> prompt and press the Return key (see Section C.2 for more information). To exit the LU6.2 Server Configuration Utility, enter 1 at the LU6.2 Cfg> prompt and press the Return key. C.2 Specifying an LU6.2 Server To start an LU6.2 Server specification, enter 2 at the LU6.2 Cfg> prompt and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about the LU6.2 Server. Specify an LU6.2 Server To define the LU6.2 Server, do the following: 1. Specify the transport used to communicate with the LU6.2 Server. Which transport should be used to communicate with the LU6.2 Server? 1 1 DECnet) 2 TCP/IP) The transport mechanism can be either DECnet or TCP/IP. Enter your selection and press the Return key. For example, enter 1 to choose DECnet and press the Return key. C-2 Using the Text-Based LU6.2 Server Configuration Utility ________________________ Note ________________________ If you press the Return key in response to any field, the system returns you to the LU6.2 Server Configuration Utility menu. You will need to re-enter your menu option and start again. ______________________________________________________ 2. Specify the node name on which the LU6.2 Server is running. What is the node name on which the LU6.2 Server is running? STRLOG For example, enter STRLOG and press the Return key. Enter 0 to access the local node. 3. Specify the name of the LU6.2 Server. What is the name of the LU6.2 Server? LU62_SRV For example, enter LU62_SRV and press the Return key. If you enter an LU6.2 Server name in lowercase letters, the system automatically adjusts the letters to uppercase. The system attempts to connect to the LU6.2 Server you specified. If the server is not running on the node you specified, the system displays an error message and returns you to the LU6.2 Server Configuration Utility menu to specify another LU6.2 Server. If the server is running on the node you specified, the LU6.2 Server Configuration Utility displays the following expanded main menu. LU6.2 Server Configuration Utility Node: STRLOG Transport: DECnet Server Name: LU62_SRV Using the Text-Based LU6.2 Server Configuration Utility C-3 1 Exit 2 Specify the LU6.2 Server 3 Define Local LU 4 Define TP Name 5 Define Remote LU 6 Define Mode Name 7 Display list of local LUs 8 Display Local LU 9 Display TP Name 10 Display Remote LU 11 Display Mode Name 12 Change Session Limit 13 Reset Session Limit 14 Activate Session 15 Delete 16 Load Configuration 17 Parse Configuration 18 Save Configuration LU6.2 Cfg> C.3 Defining the Local LU After you specify the LU6.2 Server, you can now define a local LU. The system displays the following screen title, then displays a series of prompts requesting information about the LU6.2 Server. To begin a local LU definition, enter 3 at the LU6.2 Cfg> prompt on the utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about the local LU. Define Local LU Node: STRLOG Transport: DECnet Server Name: LU62_SRV To define the local LU, do the following: 1. Specify the fully-qualified LU name. What is the fully-qualified LU name? NETID.OSFLU62 C-4 Using the Text-Based LU6.2 Server Configuration Utility For example, enter NETID.OSFLU62 and press the Return key. If you enter the fully-qualified LU name in lowercase letters, the system automatically adjusts the letters to uppercase. ________________________ Note ________________________ If you press the Return key in response to any field, the system returns you to the LU6.2 Server Configuration Utility's expanded main menu. You will need to re-enter your menu option and start again. ______________________________________________________ 2. Specify the local LU's alias name. What is the local LU alias name? osflu62 For example, enter osflu62 and press the Return key. Note that, unlike the fully-qualified LU name, the alias is case sensitive. 3. Specify the local LU's session limit. What is the maximum sessions allowed for the Local LU? 0 For example, enter 0 for an infinite number of sessions and press the Return key. 4. Specify whether you want to add security information. Would you like to add some security information? 2 1 Yes) 2 No ) For example, enter 2 for No and press the Return key. When you are defining a new local LU, you can only add security information. When you are modifying an existing LU, you can add and delete security information. ________________________ Note ________________________ If you enter Yes or No to this prompt and press the Return key, the system clears the prompt field. You must enter a numeric value, either 1 for Yes or 2 for No. ______________________________________________________ Using the Text-Based LU6.2 Server Configuration Utility C-5 5. Specify the session activation flag to be either True or False. Is session activation prevented until CICS is started? 2 1 True) 2 False ) For example, enter 2 for False and press the Return key. 6. Specify the maximum synchronization level; either None, Confirm, or Syncpt, and press the Return key. What is the maximum synchronization level? 1 1 None) 2 Confirm) 3 Syncpt) For example, enter 1 for None and press the Return key. 7. Specify the gateway's node name. What is the node name of the gateway? SNAGWY For example, enter SNAGWY and press the Return key. 8. Specify the transport used to communicate with the gateway. What transport should be used to communicate with the gateway? 1 1 DECnet) 2 TCP/IP) For example, enter 1 for DECnet, and press the Return key. 9. Specify the session capability of the local LU; either Primary or Secondary, or Secondary, and press the Return key. What is the session capability of the local LU? 1 1 Primary or Secondary) 2 Secondary) For example, enter 1 for Primary or Secondary and press the Return key. C-6 Using the Text-Based LU6.2 Server Configuration Utility 10. Specify the gateway LU's authorization password, if one is used, and press the Return key. What is the gateway LU authorization password? For example, if no gateway LU authorization password is used, press the Return key. 11. Specify the gateway access name for this LU, if one is used, and press the Return key. This prompt only appears if you selected Secondary for the LU session capability. What is the access name to use in the gateway? For example, if no gateway access name is used, press the Return key. 12. Specify the gateway LU name for this LU, if one is used, and press the Return key. This prompt only appears if you selected Secondary for the LU session capability. What is the LU name to use in the gateway? For example, if no gateway LU name is used, press the Return key. 13. Specify the user data for this LU, if any, and press the Return key. This prompt only appears if you selected Secondary for the LU session capability. What is the user-data to send when requesting a session? For example, if no user data is used, press the Return key. The system defines the specified local LU. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. No local LU is defined. If successful, the system displays the following screen: Define Local LU Node: STRLOG Transport: DECnet Server Name: LU62_SRV Defining Local LU: NETID.OSFLU62 The call to define the local LU succeeded. Hit to continue. Using the Text-Based LU6.2 Server Configuration Utility C-7 Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C.4 Defining the Remote LU After you define a local LU, you can define a remote LU associated with the local LU. To initiate a remote LU definition, enter 5 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about the remote LU. Define Remote LU Node: STRLOG Transport: DECnet Server Name: LU62_SRV To define the remote LU, do the following: 1. Specify the name of the local LU under which the remote LU is to be defined. What is the name of the parent local LU? osflu62 For example, enter osflu62 and press the Return key. You can enter either the fully-qualified local LU name or the local LU alias name at this prompt. If you enter the fully-qualified LU name in lowercase letters, the system automatically adjusts the letters to uppercase. ________________________ Note ________________________ If you press the Return key in response to any field, the system returns you to the LU6.2 Server Configuration Utility's expanded main menu. You will need to re-enter your menu option and start again. ______________________________________________________ 2. Specify the fully-qualified remote LU name. What is the fully-qualified remote LU name? NETID.REMOTELU For example, enter NETID.REMOTELU and press the Return key. If you enter the fully-qualified remote LU name in lowercase letters, the system automatically adjusts the letters to uppercase. C-8 Using the Text-Based LU6.2 Server Configuration Utility 3. Specify the remote LU's alias name. What is the remote LU alias name? remotelu For example, enter remotelu and press the Return key. Note that, unlike the fully-qualified LU name, the alias is case sensitive. 4. Specify the session initiate type; either Initiate Only, or Initiate or Queue, and press the Return key. How should sessions be initiated? 1 1 Initiate Only) 2 Initiate or Queue) For example, enter 1 for Initiate Only and press the Return key. 5. Specify whether this remote LU supports parallel sessions and CNOS verbs, and press the Return key. Are parallel sessions and CNOS supported? 1 1 True) 2 False) For example, enter 1 for True and press the Return key. 6. Specify the LU-LU authorization password, if one is used, and press the Return key. What is the LU-LU password? For example, if no LU-LU authorization password is used, press the Return key. 7. Specify the security acceptance required from this LU; either None, Conversation, Already Verified, Persistent Verification, or Already Verified and Persistent Verification, and press the Return key. What type of security acceptance is required from this LU? 2 1 None) 2 Conversation) 3 Already Verified) 4 Persistent Verification) 5 Already Verified and Persistent Verification) Using the Text-Based LU6.2 Server Configuration Utility C-9 For example, enter 2 for Conversation and press the Return key. The system defines the specified remote LU. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. No remote LU is defined. If successful, the system displays the following screen: Define Remote LU Node: STRLOG Transport: DECnet Server Name: LU62_SRV For Local LU: NETID.OSFLU62 Defining Remote LU: NETID.REMOTELU The call to define the remote LU succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C.5 Defining the Mode Name After you define a remote LU, you can define a mode name associated with the remote LU. To initiate a mode name definition, enter 6 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about the mode name. Define Mode Name Node: STRLOG Transport: DECnet Server Name: LU62_SRV To define the mode name, do the following: 1. Specify the name of the local LU under which the mode is to be defined. What is the name of the parent local LU? osflu62 C-10 Using the Text-Based LU6.2 Server Configuration Utility For example, enter osflu62 and press the Return key. You can enter either the fully-qualified local LU name or the local LU alias name at this prompt. If you enter the fully-qualified LU name in lowercase letters, the system automatically adjusts the letters to uppercase. ________________________ Note ________________________ If you press the Return key in response to any field, the system returns you to the LU6.2 Server Configuration Utility's expanded main menu. You will need to re-enter your menu option and start again. ______________________________________________________ 2. Specify the name of the remote LU under which the mode is to be defined. What is the name of the parent remote LU? remotelu For example, enter remotelu and press the Return key. You can enter either the fully-qualified remote LU name or the remote LU alias name at this prompt. If you enter the fully-qualified LU name in lowercase letters, the system automatically adjusts the letters to uppercase. 3. Specify the mode name. What is the mode name? modelu62 For example, enter modelu62 and press the Return key. If you enter the mode name in lowercase letters, the system automatically adjusts the letters to uppercase. 4. Specify the lower bound for the maximum send request unit (RU) size. What is the maximum send RU size lower bound? 512 For example, enter 512 and press the Return key. 5. Specify the upper bound for the maximum send RU size. What is the maximum send RU size upper bound? 1024 For example, enter 1024 and press the Return key. 6. Specify the preferred send RU size. What is the preferred maximum send RU size? 512 For example, enter 512 and press the Return key. Using the Text-Based LU6.2 Server Configuration Utility C-11 7. Specify the lower bound for the maximum receive RU size. What is the maximum receive RU size lower bound? 512 For example, enter 512 and press the Return key. 8. Specify the upper bound for the maximum receive RU size. What is the maximum receive RU size upper bound? 1024 For example, enter 1024 and press the Return key. 9. Specify the preferred maximum receive RU size. What is the preferred receive RU size? 512 For example, enter 512 and press the Return key. 10. Specify how many contention winner sessions should be automatically activated. How many contention winner sessions should be auto activated? 4 For example, enter 4 and press the Return key. 11. Specify the local maximum session limit for this mode. What is the local maximum session limit for this mode? 8 For example, enter 8, and press the Return key. The system defines the specified mode name. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. No mode name is defined. If successful, the system displays the following screen: Define Mode Name Node: STRLOG Transport: DECnet Server Name: LU62_SRV For Local LU: osflu62 Remote LU: remotelu Defining Mode Name: MODELU62 The call to define the mode name succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C-12 Using the Text-Based LU6.2 Server Configuration Utility C.6 Defining the Transaction Program Name After you define a local LU, you can define a transaction program (TP) associated with the local LU. To initiate a transaction program definition, enter 4 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about the transaction program. Define TP Name Node: STRLOG Transport: DECnet Server Name: LU62_SRV To define the TP, do the following: 1. Specify the name of the local LU under which the TP name is to be defined. What is the name of the parent local LU? osflu62 For example, enter osflu62 and press the Return key. You can enter either the fully-qualified local LU name or the local LU alias name at this prompt. If you enter the fully-qualified LU name in lowercase letters, the system automatically adjusts the letters to uppercase. ________________________ Note ________________________ If you press the Return key in response to any field, the system returns you to the LU6.2 Server Configuration Utility's expanded main menu. You will need to re-enter your menu option and start again. ______________________________________________________ 2. Specify the name of the TP. What is the name of the transaction program? apingd For example, enter apingd and press the Return key. 3. Specify the status of the TP; either Enabled, Temporarily Disabled, or Permanently Disabled, and press the Return key. Using the Text-Based LU6.2 Server Configuration Utility C-13 What is the status of the TP? 1 1 Enabled) 2 Temporarily Disabled) 3 Permanently Disabled) For example, enter 1 for Enabled, and press the Return key. 4. Specify the conversation types supported by the TP; either Basic, Mapped, or Basic or Mapped, and press the Return key. What conversation types are supported by the TP? 1 1 Basic) 2 Mapped) 3 Basic or Mapped) For example, enter 1 for Basic, and press the Return key. 5. Specify the synchronization levels supported by the TP; either None, Confirm, Syncpoint, None or Confirm, None or Syncpoint, Confirm or Syncpoint, or None or Confirm or Syncpoint, and press the Return key. What synchronization levels are supported by the TP? 1 1 None) 2 Confirm) 3 Syncpoint) 4 None or Confirm) 5 None or Syncpoint) 6 Confirm or Syncpoint) 7 None or Confirm or Syncpoint) For example, enter 1 for None, and press the Return key. 6. Specify the security information required from the remote TP; either None, Conversation, User ID, Profile, User ID and Profile, User ID and Remote LU Name, or User ID, Profile, and Remote LU Name, and press the Return key. C-14 Using the Text-Based LU6.2 Server Configuration Utility What security information is required from the remote TP? 1 1 None) 2 Conversation) 3 User ID) 4 Profile) 5 User ID and Profile) 6 User ID and Remote LU Name) 7 User ID, Profile and Remote LU Name) For example, enter 1 for None and press the Return key. 7. Specify whether you would like to add security information. Would you like to add some security information? 2 1 Yes) 2 No) For example, enter 2 for No, and press the Return key. 8. Specify whether Program Initialization Parameters (PIP) information is required. Are Program Initialization Parameters (PIP) information required? 2 1 Yes) 2 No) 3 Not Verified) For example, enter 2 for No, and press the Return key. 9. Specify the number of copies of this TP that can be allocated at any given time. How many copies of this TP can be allocated at any given time? 1 For example, enter 1, and press the Return key. 10. Specify whether the Attach Manager should start a process to receive conversations for this transaction program. Should the Attach Manager start a process for receive conversations? 1 1 Yes) 2 No) For example, enter 1 for Yes, and press the Return key. Using the Text-Based LU6.2 Server Configuration Utility C-15 11. Specify on which node the process should be started. On which node should the process be started? STRLOG For example, enter STRLOG, and press the Return key. 12. Specify the user ID under which the process should be created. Under what user ID should the process be created? USERNAME For example, enter USERNAME, and press the Return key. 13. Specify the command that the process on the remote node should execute to start the transaction program. What command should the process execute to accept the conversation? /usr/lib/sna/examples/apingd For example, enter /usr/lib/sna/examples/apingd and press the Return key. The system defines the specified transaction program. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. No transaction program is defined. If successful, the system displays the following screen: Define TP Name Node: STRLOG Transport: DECnet Server Name: LU62_SRV Defining TP Name: apingd The call to define the TP name definition succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C.7 Displaying the List of Local LUs After you define local LUs, remote LUs, mode names, and transaction programs, you can use the LU6.2 Server Configuration Utility's expanded main menu to display the various definitions in the LU6.2 Server. For example, you can display any of the following: o The list of local LUs and their associated remote LUs, mode names, and transaction programs C-16 Using the Text-Based LU6.2 Server Configuration Utility o A particular local LU o A particular mode name o A particular remote LU o A particular TP name This section describes how to display the list of local LUs, then how to use this list to display their associated remote LUs, mode names, and transaction programs. ________________________ Note ________________________ The entity-specific display options (8, 9, 10, and 11) are similar except that you must first specify the particular item you wish to display. ______________________________________________________ 1. To display the list of local LUs, enter 7 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. For example, based on the definitions in this appendix the system would display the following: Display an LU6.2 Server Node: STRLOG Transport: DECnet Server Name: LU62_SRV List of Local LUs: 1) NETID.OSFLU62 (osflu62) main list to see more info LU6.2 Cfg> 2. To display information about a particular local LU, enter the number displayed next to the local LU. For example, for information about local LU NETID.OSFLU62 (alias osflu62), enter 1 at the LU6.2 Cfg> prompt and press the Return key. Based on the definitions in this appendix, the system would display the following: Using the Text-Based LU6.2 Server Configuration Utility C-17 Display a Local LU Node: STRLOG Transport: DECnet Server Name: LU62_SRV Fully Qualified LU Name: NETID.OSFLU62 Local LU Alias: osflu62 LU Session Limit: 0 LU Session count: 1 Security Information count: 1 Remote LU count: 1 TP Name count: 1 Session activation: False Maximum Synchronization Level: None Gateway Information: Transport: DECnet Capability: Primary or Secondary Authorization Password: Node Name: SNAGWY LU Name: Access Name: User Data: main list "B" top of display "R" for Remote LUs "T" for TP Names "S" for Security Info "A" for Active Sessions LU6.2 Cfg> 3. To display a list of remote LUs associated with a given local LU, enter R at the LU6.2 Cfg> prompt and press the Return key. Based on the definitions in this appendix, the system would display the following: List of Remote LUs: Node: STRLOG Transport: DECnet Server Name: LU62_SRV For Local LU: NETID.OSFLU62 1) NETID.REMOTELU (remotelu) Display Local LU to see more info "R" main list LU6.2 Cfg> C-18 Using the Text-Based LU6.2 Server Configuration Utility 4. To display information about a particular remote LU, enter the number displayed next to the remote LU. For example, for information about remote LU NETID.REMOTELU (alias remotelu), enter 1 at the LU6.2 Cfg> prompt and press the Return key. Based on the definitions in this appendix, the system would display the following: Display a Remote LU Node: STRLOG Transport: DECnet Server Name: LU62_SRV Local LU Name: NETID.OSFLU62 Fully Qualified LU Name: NETID.REMOTELU Remote LU Alias: remotelu Initiate Type: Initiate Only Parallel Session Support: True CNOS Support: True Local LU Security Acceptance: Conversation Remote LU Security Acceptance: None Mode Name count: 8 Display Local LU "M" for Mode Names LU6.2 Cfg> 5. To display a list of mode names associated with a given remote LU, enter M at the LU6.2 Cfg> prompt and press the Return key. Based on the definitions in this appendix, the system would display the following: List of Mode Names: Node: STRLOG Transport: DECnet Server Name: LU62_SRV For Local LU: NETID.OSFLU62 For Remote LU: NETID.REMOTELU 1) ' ' 2) #BATCH 3) #INTER 4) #BATCHSC 5) #INTERSC 6) CPSVCMG 7) SNASVCMG 8) MODELU62 Using the Text-Based LU6.2 Server Configuration Utility C-19 Display Remote LU to see more info "R" Display Local LU LU6.2 Cfg> 6. To display information about a particular mode name, enter the number displayed next to the mode name. For example, for information about mode name MODELU62, enter 8 at the LU6.2 Cfg> prompt and press the Return key. Based on the definitions in this appendix, the system would display the following: Display a Mode Name Node: STRLOG Transport: DECnet Server Name: LU62_SRV Local LU Name: NETID.OSFLU62 Remote LU Name: NETID.REMOTELU Mode Name: MODELU62 Send Maximum RU Size Lower Bound: 512 Preferred Send RU Size: 1024 Send Maximum RU Size Upper Bound: 1024 Receive Maximum RU Size Lower Bound: 512 Preferred Receive RU Size: 1024 Receive Maximum RU Size Upper Bound: 1024 Single Session Re-initiation: Undefined Contention Winner Auto-Activate Limit: 4 Local Maximum Session Limit: 8 LU,Mode Session Limit: 2 LU,Mode Session Count: 2 Contention Winner Session Count: 1 Contention Loser Session Count: 1 Minimum Contention Winner Sessions: 1 Minimum Contention Loser Sessions: 1 Termination Count: 0 Drain Local LU: False Drain Remote LU: False Display Remote LU "B" top of display "C" for Change Session Limit "S" For Active Sessions "R" for Reset Session Limit LU6.2 Cfg> 7. Press the Return key at the LU6.2 Cfg> prompt to return to the mode name's associated remote LU display. C-20 Using the Text-Based LU6.2 Server Configuration Utility 8. Press the Return key at the LU6.2 Cfg> prompt to return to the remote LU's local LU display. 9. To display a list of transaction programs associated with a given local LU, enter T at the LU6.2 Cfg> prompt and press the Return key. Based on the definitions in this appendix, the system would display the following: List of Transaction Program Names: Node: STRLOG Transport: DECnet Server Name: LU62_SRV For Local LU: NETID.OSFLU62 1) apingd Display Local LU to see more info "R" main list LU6.2 Cfg> 10. To display information about a particular transaction program, enter the number displayed next to the transaction program. For example, for information about transaction program apingd, enter 1 at the LU6.2 Cfg> prompt and press the Return key. Based on the definitions in this appendix, the system would display the following: Display a Transaction Program Node: STRLOG Transport: DECnet Server Name: LU62_SRV Local LU Name: NETID.OSFLU62 Transaction Program Name: apingd Status: Enabled Conversation Type(s): Basic Synchronization Level(s): None Security Required: None Security Access Count: 1 Program Initialization Parameters: None allowed Instance Limit: 1 Instance Count: 0 Attach Manager Information: Attach Manager Started: True Node Name: strlog User ID: username Command String: /usr/lib/sna/examples/apingd Using the Text-Based LU6.2 Server Configuration Utility C-21 Display Local LU "S" for Access Security Information LU6.2 Cfg> 11. Press the Return key at the LU6.2 Cfg> prompt to return to the transaction program's associated local LU display. 12. Press the Return key to return to LU6.2 Server Configuration Utility's expanded main menu. C.8 Initializing the Mode Session Limits After you define your local LUs, remote LUs, and mode names, you need to initialize the session limit information for the remote LU/mode name pair. To initialize this session information, enter 12 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about which session limits to initialize and how they should be initialized. Change Number of Sessions Node: STRLOG Transport: TCP/IP Server Name: LU62_SRV To initialize or change session limits, do the following: 1. Specify the name of the local LU with which this request is associated. What is the name of the Local LU? osflu62 2. Specify the name of the remote LU with which this request is associated. What is the name of the Remote LU? remotelu 3. Specify the mode name with which this request is associated. What is the name of the mode name? modelu62 4. Specify the maximum number of sessions you want to allow for this mode. This number must be less than or equal to the session limit you defined for the mode name. What is the maximum number of sessions for this mode? 20 C-22 Using the Text-Based LU6.2 Server Configuration Utility 5. Specify the number of sessions that should be contention winners. How many of those are to be contention winner sessions? 4 6. Specify the number of sessions that should be contention losers. How many of those are to be contention loser sessions? 4 7. Specify which LU is responsible for session deactivation if the new limit you are specifying is below the current limit. Who is responsible for session deactivation (if needed)? 1 1) the Local LU (Source) 2) the Remote LU (Target) The system initializes or changes the specified session limits. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. No session limits are modified. If successful, the system displays the following screen: Change Number of Sessions Node: STRLOG Transport: TCP/IP Server Name: LU62_SRV For Local LU: OSFLU62 Remote LU: REMOTELU Mode Name: MODELU62 The call to change the session limit succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. Using the Text-Based LU6.2 Server Configuration Utility C-23 C.9 Resetting the Mode Session limits Some time later you may need to reset the session limit information for a remote LU/mode name pair (that is, return the limits to zero). To reset this session information, enter 13 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about which session limits to reset and how they should be reset. Reset Number of Sessions Node: STRLOG Transport: TCP/IP Server Name: LU62_SRV To reset session limits, do the following: 1. Specify the name of the local LU with which this request is associated. What is the name of the Local LU? osflu62 2. Specify the name of the remote LU with which this request is associated. What is the name of the Remote LU? remotelu 3. Specify the mode name with which this request is associated. What is the name of the mode name? modelu62 4. Specify which LU is responsible for session deactivation. Who is responsible for session deactivation? 1 1) the Local LU (Source) 2) the Remote LU (Target) 5. Indicate whether the local LU can drain its allocation requests. Can the Local LU (source) drain its allocation requests? 1) Yes 2) No C-24 Using the Text-Based LU6.2 Server Configuration Utility 6. Indicate whether the remote LU can drain its allocation requests. Can the Remote LU (target) drain its allocation requests? 1) Yes 2) No The system resets the specified session limits. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. No session limits are reset. If successful, the system displays the following screen: Reset Number of Sessions Node: STRLOG Transport: TCP/IP Server Name: LU62_SRV For Local LU: OSFLU62 Remote LU: REMOTELU Mode Name: MODELU62 The call to reset the session limit succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C.10 Activating a Session Normally, you would allow sessions to activate automatically either as a result of CNOS processing or as a result of transaction program allocation requests. To activate a session manually, enter 14 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about the session you wish to activate. Activate a Session Node: STRLOG Transport: TCP/IP Server Name: LU62_SRV Using the Text-Based LU6.2 Server Configuration Utility C-25 To activate a session, do the following: 1. Specify the name of the local LU with which this request is associated. What is the name of the Local LU? osflu62 2. Specify the name of the remote LU with which this request is associated. What is the name of the Remote LU? remotelu 3. Specify the mode name with which this request is associated. What is the name of the mode name? modelu62 The system activates a session from the specified local LU to the specified remote LU using the indicated mode name. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. No session is activated. If successful, the system displays the following screen: Activate a Session Node: STRLOG Transport: TCP/IP Server Name: LU62_SRV For Local LU: OSFLU62 Remote LU: REMOTELU Mode Name: MODELU62 The call to activate session succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C.11 Deleting an LU6.2 Interface Entity To delete an LU6.2 interface entity, enter 15 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a series of prompts requesting information about the entity you wish to delete. C-26 Using the Text-Based LU6.2 Server Configuration Utility Delete Node: STRLOG Transport: TCP/IP Server Name: LU62_SRV To delete an interface entity, do the following: 1. Specify the name of the local LU you wish to delete or the local LU associated with the entity you wish to delete. What is the name of the Local LU? osflu62 2. Specify the name of the remote LU you wish to delete or the remote LU associated with the mode name entities you wish to delete. If you press the Return key in response to this question, the utility skips the mode name question and displays the TP name question. What is the name of the Remote LU? remotelu 3. Specify the mode name you wish to delete. If you press the Return key in response to this question, the utility deletes the remote LU and all its associated mode names. What is the name of the mode name? modelu62 4. Specify the transaction program you wish to delete. If you press the Return key in response to this question, the utility deletes the local LU and all its associated remote LUs, mode names, and transaction program names. What is the name of the Transaction Program? apingd The system deletes the specified interface entity. All subentities associated with the entity being deleted are also deleted. For example, if you delete a remote LU entity all mode names associated with the remote LU are also deleted. Deleting a local LU deletes all entities associated with the local LU (that is, all remote LUs, mode names, and TP names). If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. No entities are deleted. If successful, the system displays the following screen: Using the Text-Based LU6.2 Server Configuration Utility C-27 Delete Node: STRLOG Transport: TCP/IP Server Name: LU62_SRV For Local LU: OSFLU62 Remote LU: REMOTELU Deleting Mode Name: MODELU62 The call to delete the Mode Name succeeded. Hit to continue. C.12 Loading a Configuration File You can use the LU6.2 Server Configuration Utility to load an LU6.2 Server configuration file. To load an LU6.2 Server configuration file, enter 16 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a prompt requesting the name of the configuration file. Load Configuration Node: STRLOG Transport: DECnet Server Name: LU62_SRV Name of configuration file to load? strlog_test.cfg If the utility cannot find the requested file, it displays an error message and gives you another chance to enter the correct file name. If the utility finds the requested file, the system loads the requested configuration file. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. If successful, the utility displays the following screen: Loading Configuration From: strlog_test.cfg Loading the configuration succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C-28 Using the Text-Based LU6.2 Server Configuration Utility C.13 Parsing a Configuration File You can use the LU6.2 Server Configuration Utility to parse (but not load) an LU6.2 Server configuration file. To parse an LU6.2 Server configuration file, enter 17 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a prompt requesting the name of the configuration file. Parse Configuration Node: STRLOG Transport: DECnet Server Name: LU62_SRV Name of configuration file to parse? strlog_test.cfg If the utility cannot find the requested file, it displays an error message and gives you another chance to enter the correct file name. If the utility finds the requested file, the system parses the requested configuration file. If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. If successful, the utility displays the following screen: Parsing Configuration: strlog_test.cfg Parsing the configuration succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C.14 Saving a Server's Configuration in a Configuration File You can use the LU6.2 Server Configuration Utility to save a server's current configuration in an LU6.2 Server configuration file. To save a server's current configuration in an LU6.2 Server configuration file, enter 18 at the LU6.2 Cfg> prompt on the LU6.2 Server Configuration Utility's expanded main menu and press the Return key. The system displays the following screen title, then displays a prompt requesting the name of the configuration file. Using the Text-Based LU6.2 Server Configuration Utility C-29 Save Configuration Node: STRLOG Transport: DECnet Server Name: LU62_SRV Name of the file to which to save configuration? strlog_test.cfg If unsuccessful, the system displays an error message, and returns you to the LU6.2 Server Configuration Utility's expanded main menu. If successful, the utility displays the following screen: Saving Configuration To: strlog_test.cfg Saving the configuration succeeded. Hit to continue. Press the Return key to return to the LU6.2 Server Configuration Utility's expanded main menu. C-30 Using the Text-Based LU6.2 Server Configuration Utility D _________________________________________________________________ The LU6.2 Server Configuration File Syntax This appendix describes the syntax required by the LU6.2 Manager and the LU6.2 Server Configuration Utility for a LU6.2 Server configuration file. Under normal circumstances, you create this file by selecting the Save Configuration File option on the File menu bar of the LU6.2 Manager's main window or the Save Configuration option of the LU6.2 Server Configuration Utility's expanded main menu. However, there may be times when you wish to either edit an existing LU6.2 Server configuration file or create a new configuration file without using the LU6.2 Manager or LU6.2 Server Configuration Utility. D.1 Basic Syntax Rules The LU6.2 Server configuration file consists of a series of definitions. Each definition in the configuration file should have the following syntax: #Possible general comment line. operator{ #possible operator comment here qualifier=value, qualifier=value, # possible per-qualifier comments here . . . qualifier=value, qualifier=value } # possible operator comment here All operators have one or more qualifiers. If there is more than one qualifier, each qualifier except the last must end with a comma. Although the LU6.2 Manager saves each qualifier on a separate line, the configuration file syntax does not require this. The LU6.2 Server Configuration File Syntax D-1 The brace characters ({ }) are required. They signal the beginning and end of the definition. D.1.1 Whitespace and Comment Lines Configuration files can contain blank lines. All lines can contain one or more space and tab characters with the exception that neither the qualifier nor its value can include space or tab characters. You can place comments on their own lines or at the end of all other lines. All comments must begin with the number character (#). D.1.2 Keywords The configuration file syntax uses several keywords for qualifier values. You can specify all keyword values in uppercase, lowercase, or mixed-case. Be careful not to use any space or tab characters within a keyword. You can abbreviate any keyword value (such as the decnet and tcpip keyword values for the gateway_node_transport qualifier of the DEFINE_LOCAL_LU operator) to the minimum string required to differentiate between the possible keyword values. For example, decnet could be abbreviated to decne, decn, dec, de, or d. D.2 Conventions Because the configuration file syntax includes both the brace characters ({ }) and the OR character (|), this appendix uses conventions that are different then those used in the rest of this manual. When a qualifier can take on a single value from a set of possible values, the syntax descriptions use the stacked list: session_activation=true false When a qualifier can take on multiple values from a set of possible values, the syntax descriptions use the OR list: conversation_type=basic | mapped, D-2 The LU6.2 Server Configuration File Syntax When specifying multiple options from an OR list, you must do the following: o Always use entire keywords, never use abbreviations. o Separate each keyword with the OR character as shown in the syntax. o Treat the keyword sequence as a single qualifier value; that is, do not use spaces anywhere within the keyword sequence. o Always specify the keywords in the order shown in the syntax descriptions. If you omit one of the keywords, omit one of the OR characters. D.3 Sample LU6.2 Server Configuration File The following sample LU6.2 Server configuration file defines the local LU LOCAL1 and an associated remote LU REM1 on the LU6.2 Server LU62_SRV on TCP/IP node lu62server. It then initializes the session limit information for the SNASVCMG mode name. Finally, it defines the associated mode name MODELU62. The LU6.2 Server Configuration File Syntax D-3 # SNALU62_MANAGER - Save Configuration - 22-Apr-1997 15:33:39 DST SELECT_SERVER{ server_name=LU62_SRV, server_node=lu62server, server_transport=TCPIP } DEFINE_LOCAL_LU{ fq_local_lu_name=NET101.LOCAL1, local_lu_alias=LOCAL1, lu_session_limit=0, session_activation=false, max_sync_level=confirm, gateway_node_name=snagwy, gateway_transport=TCPIP, lu_capability=primary_or_secondary } DEFINE_REMOTE_LU{ fq_local_lu_name=NET101.LOCAL1, fq_remote_lu_name=NET101.REM1, partner_lu_alias=REM1, initiate_type=initiate_only, parallel_support=true, cnos_support=true, security_acceptance=none } INITIALIZE_SESSION_LIMIT{ fq_local_lu_name=NET101.LOCAL1, fq_remote_lu_name=NET101.REM1, mode_name=SNASVCMG, lu_mode_session_limit=2, min_conwinners_source=1, min_conwinners_target=1 } DEFINE_MODE{ fq_local_lu_name=NET101.LOCAL1, fq_remote_lu_name=NET101.REM1, mode_name=MODELU62, send_max_ru_size_lower_bound=1024, send_max_ru_size_upper_bound=1024, recv_max_ru_size_lower_bound=1024, recv_max_ru_size_upper_bound=1024, single_session_reinitiation=undefined, conwinner_auto_activate_limit=1, D-4 The LU6.2 Server Configuration File Syntax preferred_recv_ru_size=1024, preferred_send_ru_size=1024, local_max_session_limit=8 } # End of Saved Server Configuration File D.4 Configuration File Operators The remainder of this appendix describes the configuration file operators. The following 10 operators are available: o ACTIVATE_SESSION o ADD_SECUR_ACC_INFO o ADD_SECUR_INFO o CHANGE_SESSION_LIMIT o DEFINE_LOCAL_LU o DEFINE_MODE o DEFINE_REMOTE_LU o DEFINE_TP o INITIALIZE_SESSION_LIMIT o SELECT_SERVER The LU6.2 Server Configuration File Syntax D-5 ACTIVATE_SESSION _________________________________________________________________ ACTIVATE_SESSION Activates a session between the specified LUs using the specified mode name. Format ACTIVATE_SESSION{ fq_local_lu_name=lu-name, fq_remote_lu_name=lu-name, mode_name=mode-name } Arguments fq_local_lu_name=lu-name Specifies the fully-qualified network name of the local LU associated with the session being activated. A fully- qualified network LU name is composed of two 1- to 8- character fields separated by the period character. The first field is the SNA network ID. The uppercase alphanumeric value must match the network ID of the SNA network to which the DIGITAL SNA gateway is connected. The second field is the name of the LU. LU names must be uppercase alphanumeric with a leading alphabetic character. For LUs with a capability of secondary, this field can be any legal LU name. For LUs with a capability of primary_ or_secondary, this field must match the LU name on the gateway. fq_remote_lu_name=lu-name Specifies the fully-qualified network name of the remote LU associated with the session being activated. A fully- qualified network LU name is composed of two 1- to 8- character fields separated by the period character. The first field is the SNA network ID. This uppercase alphanumeric value must match the network ID of SNA network containing the remote LU. The second field is the name of the remote LU. LU names must be uppercase alphanumeric with a leading alphabetic character. D-6 The LU6.2 Server Configuration File Syntax ACTIVATE_SESSION ________________________ Note ________________________ In the case of passive connections using the DECnet SNA Gateway for Synchronous Transport and DECnet SNA Gateway for Channel Transport products, the interface performs the usual syntax check on this qualifier. However, it does not check the value specified in this qualifier against what the interface receives in the BIND request. ______________________________________________________ mode_name=mode-name Specifies the 1- to 8-character local mode name to use when activating the session. The name can consist of any uppercase alphanumeric characters. Mode names must be uppercase alphanumeric. Description This operator must follow the definitions of the local LU, remote LU, and mode name referenced in this operator. Note that SNA-architected mode names do not require a DEFINE_ MODE operator. In addition, the ACTIVATE_SESSION operator should follow any INITIALIZE_SESSION_LIMIT and CHANGE_ SESSION_LIMIT operators for the referenced mode name. The LU6.2 Server Configuration File Syntax D-7 ADD_SECUR_ACC_INFO _________________________________________________________________ ADD_SECUR_ACC_INFO Adds access security information to a transaction program's resource-access authorization list. Format ADD_SECUR_ACC_INFO{ sec_acc_func=add, sec_acc_user_id=user-id, sec_acc_profile=profile, sec_acc_remote_lu=lu-name } Arguments sec_acc_func=add Specifies that the information in the other qualifiers should be added to the transaction program's resource- access authorization list. sec_acc_user_id=user-id Specifies a 1- to 10-character alphanumeric user ID to add to the resource-access authorization list. sec_acc_profile=profile Specifies a 1- to 10-character alphanumeric profile associated with the user ID. sec_acc_remote_lu=lu-name Specifies a fully-qualified remote LU name associated with the user ID. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. This uppercase alphanumeric value must match the network ID of SNA network containing the remote LU. The second field is the name of the remote LU. LU names must be uppercase alphanumeric with a leading alphabetic character. D-8 The LU6.2 Server Configuration File Syntax ADD_SECUR_ACC_INFO Description You can invoke this definition as many times as needed to create the desired resource-access authorization list. This operator must follow the DEFINE_TP operator that created the transaction program name whose resource-access authorization list is being modified. The LU6.2 Server Configuration File Syntax D-9 ADD_SECUR_INFO _________________________________________________________________ ADD_SECUR_INFO Adds access security information to a local LU's conversation-level security verification list. Format ADD_SECUR_INFO{ secur_type=add, secur_user_id=user-id, secur_password=password, secur_profile=profile } Arguments secur_type=add Specifies that the information in the other qualifiers should be added to the LU's conversation-level security verification list. secur_user_id=user-id Specifies a 1- to 10-character alphanumeric user ID to add to the conversation-level security verification list. secur_password=password Specifies a 1- to 10-character alphanumeric password associated with the user ID. secur_profile=profile Specifies a 1- to 10-character alphanumeric profile associated with the user ID. Description You can invoke this definition as many times as needed to create the desired conversation-level security verification list. This operator must follow the DEFINE_LOCAL_LU operator that created the local LU whose conversation-level security verification list is being modified. D-10 The LU6.2 Server Configuration File Syntax CHANGE_SESSION_LIMIT _________________________________________________________________ CHANGE_SESSION_LIMIT Changes the LU/mode session limit and contention-winner polarities for parallel- and single-session connections. Format CHANGE_SESSION_LIMIT{ fq_local_lu_name=lu-name, fq_remote_lu_name=lu-name, mode_name=mode-name, responsible=source, target, lu_mode_session_limit=number, min_conwinners_source=number, min_conwinners_target=number } Arguments fq_local_lu_name=lu-name Specifies the fully-qualified network name of the local LU. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. The uppercase alphanumeric value must match the network ID of the SNA network to which the DIGITAL SNA gateway is connected. The second field is the name of the LU. LU names must be uppercase alphanumeric with a leading alphabetic character. For LUs with a capability of secondary, this field can be any legal LU name. For LUs with a capability of primary_ or_secondary, this field must match the LU name on the gateway. fq_remote_lu_name=lu-name Specifies the fully-qualified network name of the remote LU. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. This uppercase alphanumeric value must match the network ID of SNA network containing the remote LU. The second field is the name of The LU6.2 Server Configuration File Syntax D-11 CHANGE_SESSION_LIMIT the remote LU. LU names must be uppercase alphanumeric with a leading alphabetic character. mode_name=mode-name Specifies the 1- to 8-character local mode name to use when changing the session limits. responsible=source target Specifies which LU is responsible for selecting and deactivating sessions if this operator results in a change that decreases the session limit or the maximum number of contention-winner sessions for the source or target. If no sessions need to be deactivated, this parameter is ignored. Specify one of the following values: o source Specifies that the source LU is responsible. o target Specifies that the target LU is responsible. The target LU can negotiate with the source LU and request that the source LU be the responsible party. The responsible LU deactivates the session when both LUs are finished using the session. It cannot deactivate active sessions. lu_mode_session_limit=number Specifies the new session limit for this LU/mode pair. Specify a value greater than zero and greater than or equal to the sum of the values specified in the min_conwinners_ source and min_conwinners_target qualifiers. For single-session connections, specify a limit of 1. When the mode_name qualifier specifies either SNASVCMG or CPSVCMG, specify a limit of 2. min_conwinners_source=number Specifies the new minimum number of sessions for which the source LU is the contention winner. min_conwinners_target=number Specifies the new minimum number of sessions for which the target LU is the contention winner. D-12 The LU6.2 Server Configuration File Syntax CHANGE_SESSION_LIMIT Description This definition applies to the group of sessions with the specified mode name between the source LU and the target LU. The new LU/mode session limit and contention-winner polarities are enforced until changed by a subsequent CNOS action. As a consequence of changing the session limit, one or more LU-LU sessions with the specified mode name may be activated. The LU/mode session limit for a single-session connection is changed only locally at the source LU; a CNOS request and reply are not exchanged between the two LUs. Thus, the change session request must be used at both LUs before either LU can activate the corresponding session. From each LU's perspective, each is the source LU for the processing of this request. All the parallel sessions between two LUs can be partitioned into groups, with all sessions in a group having the same mode name. Use this operator to change the maximum number of active parallel sessions that can exist concurrently within a mode-name group between the source LU and target LU. The limits imposed on the number of active parallel sessions within a mode-name group are: o The number of active sessions cannot exceed the LU/mode session limit. o The number of active contention-winner sessions for the source LU cannot exceed the LU/mode session limit minus the minimum number of contention-winner sessions for the target LU. o The number of active contention-winner sessions for the target LU cannot exceed the LU/mode session limit minus the minimum number of contention-winner sessions for the source LU. As a result of using this operator, parallel sessions may be activated to conform to the new limits. If the local LU was defined with the session_activation parameter set to true, the interface does not negotiate the session limits immediately. When a transaction program makes the first call to the snalu62_attach_listen The LU6.2 Server Configuration File Syntax D-13 CHANGE_SESSION_LIMIT verb specifying the local LU, the interface negotiates all remote LU/mode session limits that have any saved information. D-14 The LU6.2 Server Configuration File Syntax DEFINE_LOCAL_LU _________________________________________________________________ DEFINE_LOCAL_LU Defines a local LU and initializes parameters that control the operation of the local LU. Format DEFINE_LOCAL_LU{ fq_local_lu_name=lu-name, local_lu_alias=lu-alias, lu_session_limit=number, session_activation=true false, max_sync_level=none confirm syncpt, gateway_node_name=node-name, gateway_transport=decnet tcpip, lu_capability=primary_or_secondary, secondary authorization_password=password, access_name=access-name, lu_name=lu-name, user_data=data, } Arguments fq_local_lu_name=lu-name Specifies the fully-qualified network name of the local LU being defined. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. The uppercase alphanumeric value must match the network ID of the SNA network to which the DIGITAL SNA gateway is connected. The second field is the name of the LU. LU names must be uppercase alphanumeric with a leading alphabetic character. For LUs with a capability of secondary, this field can be any legal LU name. For LUs with a capability of primary_or_secondary, this field must match the LU name on the gateway. The LU6.2 Server Configuration File Syntax D-15 DEFINE_LOCAL_LU local_lu_alias=lu-alias Specifies the 1- to 64-character locally-known alias of the local LU being defined. lu_session_limit=number Specifies the LU-LU session limit for the total number of sessions for the local LU. A value of zero indicates that no limit is defined. If this qualifier has a non- zero value, specify a value greater than or equal to 44 to accommodate the SNA-defined mode names. session_activation=true false Specifies whether activation of any LU-LU sessions (including CNOS sessions) should be prevented before an snalu62_attach_listen verb is called. A value of true indicates that LU-LU activation should be prevented when an snalu62_attach_listen verb has not been called. See the implementation chapter of the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX Programming manual for more information about the effects of specifying true for this qualifier. max_sync_level=none confirm syncpt Specifies the maximum synchronization level allowed for all sessions using this local LU. Specify one of the following values: o none (the default) Specifies that all conversations on this LU cannot use any confirmation verbs or sync-point processing. o confirm Specifies that all conversations on this LU have the option of using confirmation verbs. o syncpt Specifies that all conversations on this LU have the option of using both confirmation verbs and sync-point processing. D-16 The LU6.2 Server Configuration File Syntax DEFINE_LOCAL_LU gateway_node_name=node-name Specifies the node name of the gateway with which this local LU is associated. gateway_transport=decnet tcpip Specifies the transport used to reach the gateway with which this local LU is associated. You can specify tcp/ip instead of tcpip. lu_capability=primary_or_secondary secondary Specifies the capability of the LU as defined on the gateway with which this local LU is associated. Specify one of the following: o primary_or_secondary Specifies that a call to snalu62_activate_session causes the interface to send a BIND to the specified remote LU. o secondary Specifies that a call to snalu62_activate_session causes the interface to wait for a BIND from the specified remote LU. If you are using a DECnet SNA Gateway for Synchronous Transport or DECnet SNA Gateway for Channel Transport system, you should always set this qualifier to secondary. authorization_password=password Specifies a 1- to 32-character authorization password that the interface should use when connecting to the DIGITAL SNA gateway. This password must match the authorization password defined for the LU on the gateway. access_name=access-name Specifies a 1- to 8-character access name that the interface should use when connecting to the DIGITAL SNA gateway. The gateway uses this access name to retrieve information about the proposed session. You should only use this qualifier for LUs whose capability qualifier is set to secondary. The LU6.2 Server Configuration File Syntax D-17 DEFINE_LOCAL_LU lu_name=lu-name Specifies a 1- to 8-character LU name that overrides any LU names specified in the gateway's access name. You should only use this qualifier for LUs whose capability qualifier is set to secondary. user_data=data Specifies between 1 and 128 bytes of user data that overrides any user data specified in the gateway's access name. You should only use this qualifier for LUs whose capability qualifier is set to secondary. Description Use this operator prior to any definitions that reference this LU. D-18 The LU6.2 Server Configuration File Syntax DEFINE_MODE _________________________________________________________________ DEFINE_MODE Defines the parameters that control the operation of the local LU in conjunction with a group of sessions to the specified remote LU, the session group being identified by a mode name. Format DEFINE_MODE{ fq_local_lu_name=lu-name, fq_remote_lu_name=lu-name, mode_name=mode-name, send_max_ru_size_lower_bound=number, send_max_ru_size_upper_bound=number, recv_max_ru_size_lower_bound=number, recv_max_ru_size_upper_bound=number, single_session_reinitiation=undefined operator plu slu plu_or_slu, conwinner_auto_activate_limit=number, preferred_recv_ru_size=number, preferred_send_ru_size=number, local_max_session_limit=number } Arguments fq_local_lu_name=lu-name Specifies the fully-qualified network name of the local LU with which this mode is associated. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. The uppercase alphanumeric value must match the network ID of the SNA network to which the DIGITAL SNA gateway is connected. The second field is the name of the LU. LU names must be uppercase alphanumeric with a leading alphabetic character. For LUs with a capability of secondary, this field can be any legal LU name. For LUs The LU6.2 Server Configuration File Syntax D-19 DEFINE_MODE with a capability of primary_or_secondary, this field must match the LU name on the gateway. fq_remote_lu_name=lu-name Specifies the fully-qualified network name of the remote LU with which this mode is associated. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. This uppercase alphanumeric value must match the network ID of SNA network containing the remote LU. The second field is the name of the remote LU. LU names must be uppercase alphanumeric with a leading alphabetic character. ________________________ Note ________________________ In the case of passive connections using the DECnet SNA Gateway for Synchronous Transport and DECnet SNA Gateway for Channel Transport products, the interface performs the usual syntax check on this qualifier. However, it does not check the value specified in this qualifier against what the interface receives in the BIND request. ______________________________________________________ mode_name=mode-name Specifies the 1- to 8-character alphanumeric name of the mode name being defined. Do not specify any of the following SNA-architected mode names: o default (see Note) o #BATCH o #INTER o #BATCHSC o #INTERSC o CPSVCMG D-20 The LU6.2 Server Configuration File Syntax DEFINE_MODE o SNASVCMG ________________________ Note ________________________ The default name is encoded as eight space (X'20') characters. ______________________________________________________ send_max_ru_size_lower_bound=number Specifies the lower bound for the maximum size of normal- flow requests that the local LU sends on its sessions. Specify a value less than or equal to the value specified on the send_max_ru_size_upper_bound qualifier. The local LU uses these lower- and upper-bound values to determine the value for its send maximum RU size specified in its BIND requests and responses. send_max_ru_size_upper_bound=number Specifies the upper bound for the maximum size of normal- flow requests that the local LU sends on its sessions. Specify a value greater than or equal to the value specified on the send_max_ru_size_lower_bound qualifier. The local LU uses these lower- and upper-bound values to determine the value for its send maximum RU size specified in its BIND requests and responses. recv_max_ru_size_lower_bound=number Specifies the lower bound for the maximum size of normal- flow requests that the local LU receives on its sessions. Specify a value less than or equal to the value specified on the recv_max_ru_size_upper_bound qualifier. The local LU uses these lower- and upper-bound values to determine the value for its receive maximum RU size specified in its BIND requests and responses. recv_max_ru_size_upper_bound=number Specifies the upper bound for the maximum size of normal- flow requests that the local LU receives on its sessions. Specify a value greater than or equal to the value specified on the recv_max_ru_size_lower_bound qualifier. The local LU uses these lower- and upper-bound values to determine the value for its receive maximum RU size specified in its BIND requests and responses. The LU6.2 Server Configuration File Syntax D-21 DEFINE_MODE single_session_reinitiation=undefined operator plu slu plu_or_slu Specifies the responsibility for session reinitiation when the remote LU does not support parallel sessions. The local LU uses this parameter to determine the indication for session reinitiation that it specifies in its BIND requests and responses. Specify one of the following values: o undefined Use this value when the remote LU supports parallel sessions. o operator For single session LUs, specifies that neither LU should automatically attempt to reinitiate the session in the case of a session failure. Both sides require operator intervention. D-22 The LU6.2 Server Configuration File Syntax DEFINE_MODE o plu For single session LUs, specifies that the primary LU (PLU) should automatically attempt to reinitiate the session in the case of a failure. o slu For single session LUs, specifies that the secondary LU (SLU) should automatically attempt to reinitiate the session in the case of a failure. o plu_or_slu For single session LUs, specifies that either the PLU or the SLU should automatically attempt to reinitiate the session in the case of a failure. conwinner_auto_activate_limit=number Specifies the limit for the number of contention-winner sessions that the local LU can automatically activate when the minimum number of contention-winner sessions for the local LU increases (as a result of CNOS processing). A value of zero specifies that the local LU should not automatically activate any sessions. If no automatic- activation limit is defined, the local LU does not automatically activate any sessions. preferred_recv_ru_size=number Specifies the preferred maximum size of normal-flow requests that the local LU receives on its sessions. This value must be less than or equal to the value specified on the recv_max_ru_size_upper_bound qualifier and greater than or equal to the recv_max_ru_size_lower_bound qualifier. preferred_send_ru_size=number Specifies the preferred maximum size of normal-flow requests that the local LU sends on its sessions. This value must be less than or equal to the value specified on the send_max_ru_size_upper_bound qualifier and greater than or equal to the send_max_ru_size_lower_bound qualifier. local_max_session_limit=number Specifies the session limit that the local LU can use during CNOS processing for the mode's session limit. A value of zero indicates that no mode session limit can be negotiated, either by a remote CNOS request or by local The LU6.2 Server Configuration File Syntax D-23 DEFINE_MODE execution of a CNOS verb. If this qualifier specifies a non-zero value, the lu_session_limit qualifier of the mode's local LU must be large enough to include this value. The local LU's lu_session_limit value must be greater than or equal to the sum of the local_max_session_limit qualifier values for all mode names that reference the local LU (including the SNA-defined mode names). Description Use this operator following the DEFINE_LOCAL_LU and DEFINE_ REMOTE_LU operators that created the local LU and remote LU referenced in the fq_local_lu_name and fq_remote_lu_name qualifiers. D-24 The LU6.2 Server Configuration File Syntax DEFINE_REMOTE_LU _________________________________________________________________ DEFINE_REMOTE_LU Defines a remote LU and initializes the parameters that control the operation of the local LU when in session with the remote LU. Format DEFINE_REMOTE_LU{ fq_local_lu_name=lu-name, fq_remote_lu_name=lu-name, partner_lu_alias=lu-alias, initiate_type=initiate_only initiate_or_queue, parallel_session_support=true false, cnos_support=true false, security_acceptance=none conversation already_veri persist_veri av_and_pv } Arguments fq_local_lu_name=lu-name Specifies the fully-qualified network name of the local LU with which this remote LU is associated. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. The uppercase alphanumeric value must match the network ID of the SNA network to which the DIGITAL SNA gateway is connected. The second field is the name of the LU. LU names must be uppercase alphanumeric with a leading alphabetic character. For LUs with a capability of secondary, this field can be any legal LU name. For LUs with a capability of primary_or_secondary, this field must match the LU name on the gateway. The LU6.2 Server Configuration File Syntax D-25 DEFINE_REMOTE_LU fq_remote_lu_name=lu-name Specifies the fully-qualified network name of the remote LU being defined. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. This uppercase alphanumeric value must match the network ID of SNA network containing the remote LU. The second field is the name of the remote LU. LU names must be uppercase alphanumeric with a leading alphabetic character. ________________________ Note ________________________ In the case of passive connections using the DECnet SNA Gateway for Synchronous Transport and DECnet SNA Gateway for Channel Transport products, the interface performs the usual syntax check on this qualifier. However, it does not check the value specified in this qualifier against what the interface receives in the BIND request. ______________________________________________________ partner_lu_alias=lu-alias Specifies the 1- to 64-character locally-known alias of the remote LU being defined. initiate_type=initiate_only initiate_or_queue Specifies the session initiation type that the local LU should use in the initiate request. Specify one of the following values: o initiate_only Specifies that session-initiation requests should indicate that no queuing be done if the request cannot be serviced. o initiate_or_queue Specifies that session-initiation requests should indicate that queuing be done if the request cannot be serviced. D-26 The LU6.2 Server Configuration File Syntax DEFINE_REMOTE_LU parallel_session_support=true false Specifies whether the local LU supports parallel sessions with this remote LU. A value of true indicates the local LU supports parallel sessions. cnos_support=true false Specifies whether the local LU supports the exchange of CNOS requests and replies with this remote LU. A value of true indicates the local LU supports CNOS requests. Support for exchanging CNOS requests and replies requires parallel session support. security_acceptance=none conversation already_veri persist_veri av_and_pv Specifies the level of access security information that the local LU accepts on allocation requests it receives from the remote LU. Specify one of the following values: o none Specifies that the interface should not accept security information on incoming allocation requests from this remote LU. o conversation Specifies that the interface should accept conversation- level security information on incoming allocation requests from this remote LU. This information must consist of at least a user ID and a password and may optionally include a profile. o already_veri Specifies that the interface should accept conversation- level security information on incoming allocation requests from this remote LU. This information must consist of at least a user ID and a password and may optionally include a profile. In addition, the interface should accept requests with the already-verified indicator set, but should reject requests with the persistent-verification indicator set. The LU6.2 Server Configuration File Syntax D-27 DEFINE_REMOTE_LU o persist_veri Specifies that the interface should accept conversation- level security information on incoming allocation requests from this remote LU. This information must consist of at least a user ID and a password and may optionally include a profile. In addition, the interface should accept requests with the persistent-verification indicator set, but should reject requests with the already-verified indicator set. o av_and_pv Specifies that the interface should accept conversation- level security information on incoming allocation requests from this remote LU. This information must consist of at least a user ID and a password and may optionally include a profile. In addition, the interface should accept requests with either the persistent- verification indicator set or the already-verified indicator set. Description If no locally-known name of the remote LU is defined at the local LU, local transaction programs may specify the remote LU's fully-qualified LU name on the remote_lu_name parameter of the snalu62_allocate verb. The DEFINE_REMOTE_ LU operator must follow the definition of the local LU referenced by the fq_local_lu_name qualifier and precede any operators that reference this remote LU. D-28 The LU6.2 Server Configuration File Syntax DEFINE_TP _________________________________________________________________ DEFINE_TP Defines a transaction program and initializes parameters that control the operation of the transaction program. Format DEFINE_TP{ fq_local_lu_name=lu-name, tp_name=tp-name, status=enable temp_disable perm_disable, conversation_type=basic | mapped, sync_level=none | confirm | syncpt, security_required=none conversation user profile user_profile user_rem_lu user_prof_rem_lu, pip_type=no yes not_verified, pip_number=number, instance_limit=number, a_nodename=node-name, a_user_id=user-id, a_command_string=string, a_mgr_started=true false } Arguments fq_local_lu_name=lu-name An ASCII string specifying the fully-qualified network name of the local LU with which this transaction program is associated. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. The The LU6.2 Server Configuration File Syntax D-29 DEFINE_TP uppercase alphanumeric value must match the network ID of the SNA network to which the DIGITAL SNA gateway is connected. The second field is the name of the LU. LU names must be uppercase alphanumeric with a leading alphabetic character. For LUs with a capability of secondary, this field can be any legal LU name. For LUs with a capability of primary_or_secondary, this field must match the LU name on the gateway. tp_name=tp-name An ASCII string specifying the transaction program name being defined. status=enable temp_disable perm_disable Specifies the status that the interface returns to a remote transaction program when the local LU receives an allocation request naming the program. Specify one of the following values: o enable (the default) Specifies that the interface should accept the allocation request and, if no errors occur, should return a success status to the remote transaction program. o temp_disable Specifies that the interface should return an indication to the remote program that the requested local program is temporarily unavailable. The remote program can retry the request later. o perm_disable Specifies that the interface should return an indication to the remote program that the requested local program is permanently unavailable. The remote program should not retry the request. conversation_type=basic | mapped Specifies the type of conversations that the transaction program allows on allocation requests. D-30 The LU6.2 Server Configuration File Syntax DEFINE_TP sync_level=none | confirm | syncpt Specifies the type of synchronization levels that the transaction program allows on allocation requests. Specify one or more of the following: o none Specifies that this program supports conversations with no synchronization. The LU6.2 Server Configuration File Syntax D-31 DEFINE_TP o confirm Specifies that this program supports conversations with confirmation synchronization. o syncpt Specifies that this program supports conversations with sync-point synchronization. security_required=none conversation user profile user_profile user_rem_lu user_prof_rem_lu Specifies the type of security verification to be performed on incoming allocation requests that designate the transaction program. Specify one of the following values: o none The interface should accept all allocation requests for this program. If conversation-level security information is supplied, the interface should verify the information. The interface should not perform any resource-access verification. o conversation The interface should perform conversation-level security verification on all allocation requests for this program. All allocation requests for this program must supply at least a user ID and either a password or an already-verified indication. The interface should not perform resource-access security verification. o user o profile o user_profile o user_rem_lu o user_prof_rem_lu D-32 The LU6.2 Server Configuration File Syntax DEFINE_TP The interface should perform conversation-level security verification on all allocation requests for this program. All allocation requests for this program must supply at least a user ID and either a password or an already-verified indication. The interface should also perform resource-access security verification based on the value supplied: - user specifies that the interface should compare only the supplied user ID against the program's resource- access authorization list. - profile specifies that the interface should compare only the supplied profile against the program's resource-access authorization list. - user_profile specifies that the interface should compare only the supplied user ID and profile against the program's resource-access authorization list. - user_rem_lu specifies that the interface should compare only the supplied user ID and remote LU against the program's resource-access authorization list. - user_prof_rem_lu specifies that the interface should compare the user ID, profile, and remote LU against the program's resource-access authorization list. pip_type=no yes not_verified Specifies whether program initialization parameters (PIP) data is required on allocation requests. Specify one of the following: o no Specifies that the interface should verify that allocation requests for this transaction program contain no PIP data elements. o yes Specifies that the interface should verify that allocation requests for this transaction program contain the number of PIP data elements specified by the pip_ number qualifier. The LU6.2 Server Configuration File Syntax D-33 DEFINE_TP o not_verified Specifies that the interface should not verify either the existence of or the number of PIP data elements. pip_number=number Specifies the number of PIP data elements required on allocation requests. instance_limit=number A value specifying the maximum number of instances of the transaction program that are allowed to be invoked concurrently. Specify a value greater than zero. a_nodename=node-name Specifies the name of the node where an Attach Manager daemon is to create a process to execute this transaction program. If the node name ends in a single colon (:), the interface uses the TCP/IP transport. If the node name ends in a double colon (::), the interface uses the DECnet transport. Otherwise, the interface tries both transports. a_user_id=user-id Specifies the user ID under which the Attach Manager daemon is to create a process to execute this transaction program. a_command_string=string Specifies the command string that the Attach Manager daemon should use to create a process to execute this transaction program. This string should include a complete and valid path statement and can optionally include command flags and stdin and stdout redirections. ________________________ Note ________________________ If the command string includes characters other than a to z, A to Z, 0 to 9, or \, you must enclose the string in double quotes. ______________________________________________________ a_mgr_started=true false Specifies whether the interface should use an Attach Manager daemon to create a process to execute this transaction program. D-34 The LU6.2 Server Configuration File Syntax DEFINE_TP Description The values specified on the parameters of this operator take effect at the next invocation of the transaction program. The LU6.2 Server Configuration File Syntax D-35 INITIALIZE_SESSION_LIMIT _________________________________________________________________ INITIALIZE_SESSION_LIMIT Initializes the LU/mode session limit and contention-winner polarities for parallel- and single-session connections. Format INITIALIZE_SESSION_LIMIT{ fq_local_lu_name=lu-name, fq_remote_lu_name=lu-name, mode_name=mode-name, lu_mode_session_limit=number, min_conwinners_source=number, min_conwinners_target=number } Arguments fq_local_lu_name=lu-name An ASCII string specifying the fully-qualified network name of the local LU. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. The uppercase alphanumeric value must match the network ID of the SNA network to which the DIGITAL SNA gateway is connected. The second field is the name of the LU. LU names must be uppercase alphanumeric with a leading alphabetic character. For LUs with a capability of secondary, this field can be any legal LU name. For LUs with a capability of primary_or_secondary, this field must match the LU name on the gateway. fq_remote_lu_name=lu-name An ASCII string specifying the fully-qualified network name of the remote LU. A fully-qualified network LU name is composed of two 1- to 8-character fields separated by the period character. The first field is the SNA network ID. This uppercase alphanumeric value must match the network ID of SNA network containing the remote LU. The second field is the name of the remote LU. LU names must be uppercase alphanumeric with a leading alphabetic character. D-36 The LU6.2 Server Configuration File Syntax INITIALIZE_SESSION_LIMIT ________________________ Note ________________________ In the case of passive connections using the DECnet SNA Gateway for Synchronous Transport and DECnet SNA Gateway for Channel Transport products, the interface performs the usual syntax check on this qualifier. However, it does not check the value specified in this qualifier against what the interface receives in the BIND request. ______________________________________________________ mode_name=mode-name An ASCII string specifying the name of the mode for which this session limit initiation is being made. lu_mode_session_limit=number A value specifying the session limit for this LU/mode pair. Specify a value greater than zero and greater than or equal to the sum of the values specified in the min_conwinners_ source and min_conwinners_target qualifiers. For single-session connections, specify a limit of 1. When the mode_name qualifier specifies either SNASVCMG or CPSVCMG, specify a limit of 2. min_conwinners_source=number A value specifying the minimum number of sessions for which the source LU is the contention winner. min_conwinners_target=number A value specifying the minimum number of sessions for which the target LU is the contention winner. Description This definition applies to the group of sessions with the specified mode name between the source LU and the target LU. The new LU/mode session limit and contention-winner polarities are enforced until changed by a subsequent CNOS verb. As a consequence of initializing the session limit, one or more LU-LU sessions with the specified mode name may be activated. The LU6.2 Server Configuration File Syntax D-37 INITIALIZE_SESSION_LIMIT The LU/mode session limit for a single-session connection is initialized only locally at the source LU; a CNOS request and reply are not exchanged between the two LUs. Thus, the snalu62_initialize_sess_limit verb must be called at both LUs before either LU can activate the corresponding session. From each LU's perspective, each is the source LU for the processing of this verb. All the parallel sessions between two LUs can be partitioned into groups, with all sessions in a group having the same mode name. Use this operator to initialize the maximum number of active parallel sessions that can exist concurrently within a mode-name group between the source LU and target LU. The limits imposed on the number of active parallel sessions within a mode-name group are: o The number of active sessions cannot exceed the LU/mode session limit. o The number of active contention-winner sessions for the source LU cannot exceed the LU/mode session limit minus the minimum number of contention-winner sessions for the target LU. o The number of active contention-winner sessions for the target LU cannot exceed the LU/mode session limit minus the minimum number of contention-winner sessions for the source LU. As a result of calling this operator, parallel sessions may be activated to conform to the new limits. ________________________ Note ________________________ When a remote LU (like CICS) fails, its underlying communication system automatically deactivates the remote LU's sessions. When the communication system restarts the remote LU, it sets all the LU's mode session limits to zero. If you attempt to establish a conversation to a remote transaction program using the remote LU, the session activation request will fail because the mode session limits are not initialized. You should use one or more of the CNOS verbs to negotiate new session limits. ______________________________________________________ D-38 The LU6.2 Server Configuration File Syntax INITIALIZE_SESSION_LIMIT Restrictions If the local LU was defined with the session_activation parameter set to true, the interface does not negotiate the session limits immediately. The interface saves the requested limits and returns a status of SNALU62_S_OK. When a transaction program makes the first call to the snalu62_ attach_listen verb specifying the local LU, the interface negotiates all remote LU/mode session limits that have any saved information. The LU6.2 Server Configuration File Syntax D-39 SELECT_SERVER _________________________________________________________________ SELECT_SERVER Specifies the LU6.2 Server affected by the remaining operators in the configuration file. Format SELECT_SERVER{ server_name=server-name, server_node=node-name, server_transport=tcpip decnet } Arguments server_name=server-name Specifies the 1- to 8-character name of the LU6.2 Server with which this configuration file is associated. server_node=node-name Specifies the node name of the LU6.2 Server with which this configuration file is associated. server_transport=decnet tcpip Specifies the transport used to reach the LU6.2 Server with which this configuration file is associated. You can specify tcp/ip instead of tcpip. Description This operator must precede all other operators. There must be only one occurrence of this operator in each configuration file. D-40 The LU6.2 Server Configuration File Syntax E _________________________________________________________________ Using the LU6.2 Script Processor This appendix describes the procedures for using the LU6.2 Script Processor. The LU6.2 Script Processor allows you to do the following: o Define the server's name, node name, and transport and the gateway's node name and transport. o Define one or more local LUs. o Define one or more remote LUs associated with a particular local LU. o Define one or more mode names associated with a particular remote LU. o Define one or more transaction programs associated with a particular local LU. o Initialize the session limits of the SNASVCMG mode name. o Initialize the sessions limits associated with a particular mode name. o Activate a session associated with the SNASVCMG mode name. o Activate a session associated with a particular mode name. o Display current parameter settings. For a general description of the LU6.2 Server configuration process, see the chapter entitled "Controlling the APPC/LU6.2 Programming Interface" in the manual DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX, Programming. For information specific to the interface provided by the DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX product, see the chapter entitled "Implementation Specifics" in the same manual. Using the LU6.2 Script Processor E-1 E.1 Running the LU6.2 Script Processor To run the LU6.2 Script Processor, use the following command: # /usr/lib/sna/lu62_script After you enter the /usr/lib/sna/lu62_script command, the system displays the following message and prompt: Type HELP for lu62_script commands and parameters Command: You can enter operators interactively at the Command: prompt, or you can direct the processor to read a file using the < operator. For example, the following command invokes the Script Processor using the script file setup.scp: # /usr/lib/sna/lu62_script E.2 Basic Syntax Rules The LU6.2 script language consists of a series of definitions. Each definition in the script language should have the following syntax: operator [parameter ... parameter] Most operators have one or more parameters. If there is more than one parameter, the parameters must be separated by at least 1 space or TAB character. To default a parameter that is last on the line, simply omit the parameter. To default other parameters, use a pair of single quotes or double quotes ('' or ""). E.2.1 Whitespace and Comment Lines Script files can contain blank lines. All lines can contain one or more space and tab characters with the exception that a parameter cannot include space or tab characters. The script language supports comment lines. All comments must begin with the number character (#), two number characters (##), or the operator NOTE. E-2 Using the LU6.2 Script Processor E.2.2 Keywords The script language uses several keywords for parameter values. You can specify all keyword values in all uppercase or all lowercase; the Script Processor does not recognize mixed-case keywords. Be careful not to use any space or tab characters within a keyword. E.3 Rerunning a Script to Reactivate Sessions If active LU6.2 sessions are lost due to network problems, the LU6.2 architecture states that the LU6.2 Server should not automatically reactivate these sessions. Therefore, you may wish to use the script file that you used to configure the server to reactivate the sessions after a session loss. Invoke the LU6.2 Script Processor using the same script file that you used to configure the server. This action reinitializes the mode session limits and reactivates any sessions that were initially activated by the script file. Note that any sessions activated as a result of transaction program allocation calls are not restarted. E.4 Sample Script File A sample script file is shown below: IDS DG_SRV 0 SNAGWY TCP DECNET # LOCAL NET01 LOCAL1 REMOTE NET01 REMOTE1 MODE MODE1 6 INT_MODE MODE1 2 1 MODE MODE2 10 512 1024 1024 512 1024 1024 3 INT_MODE MODE2 7 2 # SHOW # EXIT This sample script file does the following: o Establishes the name and the node name of the LU6.2 Server (DG_SRV on the local node) and node name of the gateway (SNAGWY). The interface should use the TCP transport to communicate with the LU6.2 Server and the server should use the DECNET transport to communicate with the DIGITAL SNA gateway. Using the LU6.2 Script Processor E-3 o Defines the local LU LOCAL1. o Defines the remote LU REMOTE1. o Defines the mode name MODE1. MODE1 has a session limit of 6, default send and receive RU sizes of 256 (lower), 1024 (higher), and 512 (preferred), and a default auto activation limit of 0. o Initializes the session limits for mode MODE1 with 2 contention winning sessions and 1 contention losing session. o Defines the mode name MODE2. MODE2 has a session limit of 10, send and receive RU sizes of 512 (lower), 1024 (higher), and 1024 (preferred), and a default auto activation limit of 3. o Initializes the session limits for mode MODE2 with 7 contention winning sessions and 2 contention losing session. o Displays the current settings o Exits E.5 Script Language Operators The remainder of this appendix describes the script language operators. The following 12 operators are available: o ACT_MODE - activate a session for the specified mode o ACT_SVC - activate a session for the mode SNASVCMG o EXIT - leave the LU6.2 Script Processor o HELP - get help online o IDS - define server and gateway information o INT_MODE - initialize the specified mode limits o INT_SVC - initialize the SNASVCMG limits o LOCAL - define a local LU o MODE - define a mode o NOTE - provide a comment E-4 Using the LU6.2 Script Processor o REMOTE - define a remote LU o SHOW - display the current settings Using the LU6.2 Script Processor E-5 ACT_MODE _________________________________________________________________ ACT_MODE Activates a single session between the current LUs using the specified mode name. Format ACT_MODE mode-name Arguments mode-name Specifies the 1- to 8-character local mode to use when activating the session. Mode names must be uppercase alphanumeric. Description This operator must follow the definitions of the local LU, remote LU, and mode referenced by this operator. In addition, the ACT_MODE operator must follow the INT_MODE operator. To activate more than 1 session for the mode name include multiple ACT_MODE operators in the script file. E-6 Using the LU6.2 Script Processor ACT_SVC _________________________________________________________________ ACT_SVC Activates a single session between the current LUs using the SNASVCMG mode name. Format ACT_SVC Arguments None. Description This operator must follow the definitions of the local LU and remote LU referenced by this operator. In addition, the ACT_SVC operator must follow the INT_SVC operator. To activate more than 1 session for the SNASVCMG mode name include multiple ACT_SVC operators in the script file. A maximum of two SNASVCMG sessions may be started. Using the LU6.2 Script Processor E-7 EXIT _________________________________________________________________ EXIT Terminates the script processing session. Format EXIT Arguments None. Description This operator terminates the script file processing. E-8 Using the LU6.2 Script Processor HELP _________________________________________________________________ HELP Displays a brief overview of the LU6.2 Script Processor's operator syntax. Format HELP Arguments None. Description This operator displays a brief list of the LU6.2 Script Processor operators followed by a list of the parameters for each operator. Using the LU6.2 Script Processor E-9 IDS _________________________________________________________________ IDS Defines the LU6.2 Server and gateway node names. Format IDS server-name server-node-name gateway-node-name server-transport gateway-transport Arguments server-name Specifies the name of the LU6.2 Server on which this local LU is being defined. The default server name is LU62_SRV. server-node-name Specifies the node name of the LU6.2 Server on which this local LU is being defined. The default node name (0) is the node on which the Script Processor is running. gateway-node-name Specifies the node name of the gateway with which this local LU is associated. The default node name (0) is the node on which the Script Processor is running. server-transport Specifies the transport used to reach the LU6.2 Server on which this local LU is being defined. You can specify TCP or DECNET. The default transport is TCP. gateway-transport Specifies the transport used to reach the gateway with which this local LU is associated. You can specify TCP or DECNET. The default transport is TCP. E-10 Using the LU6.2 Script Processor IDS Description This operator defines the LU6.2 Server that you want affected by the remaining operators in the script file. Use this operator prior to any other operators. Using the LU6.2 Script Processor E-11 INT_MODE _________________________________________________________________ INT_MODE Initializes the contention-winner polarities for parallel- and single-session connections. Format INT_MODE mode-name min-conwinners-source min-conwinners-target Arguments mode-name Specifies the 1- to 8-character local mode name to use when initializing the session limits. min-conwinners-source Specifies the minimum number of sessions for which the source LU is the contention winner. min-conwinners-target Specifies the minimum number of sessions for which the target LU is the contention winner. Description This operator applies to the group of sessions with the specified mode name between the source LU and the target LU. The contention-winner polarities are enforced until changed by a subsequent CNOS action. As a consequence of changing the session limit, one or more LU-LU sessions with the specified mode name may be activated. The LU/mode session limit for a single-session connection is changed only locally at the source LU; a CNOS request and reply are not exchanged between the two LUs. Thus, the change session request must be used at both LUs before either LU can activate the corresponding session. From each LU's perspective, each is the source LU for the processing of this request. E-12 Using the LU6.2 Script Processor INT_MODE All the parallel sessions between two LUs can be partitioned into groups, with all sessions in a group having the same mode name. Use this operator to change the maximum number of active parallel sessions that can exist concurrently within a mode-name group between the source LU and target LU. The limits imposed on the number of active parallel sessions within a mode-name group are: o The number of active sessions cannot exceed the LU/mode session limit. o The number of active contention-winner sessions for the source LU cannot exceed the LU/mode session limit minus the minimum number of contention-winner sessions for the target LU. o The number of active contention-winner sessions for the target LU cannot exceed the LU/mode session limit minus the minimum number of contention-winner sessions for the source LU. As a result of using this operator, parallel sessions may be activated to conform to the new limits. Using the LU6.2 Script Processor E-13 INT_SVC _________________________________________________________________ INT_SVC Initializes the contention-winner polarities for the SNASVCMG mode name. Format INT_SVC Arguments None. Description This operator applies to the group of sessions with the SNASVCMG mode name between the source LU and the target LU. E-14 Using the LU6.2 Script Processor LOCAL _________________________________________________________________ LOCAL Defines a local LU and initializes parameters that control the operation of the local LU. Format LOCAL network-name lu-name Arguments network-name Specifies the network ID of the network that contains the local LU being defined. The uppercase alphanumeric value must match the network ID of the SNA network to which the DIGITAL SNA gateway is connected. lu-name Specifies the name of the local LU. LU names must be uppercase alphanumeric with a leading alphabetic character. For LUs with a capability of Secondary, this field can be any legal LU name. For LUs with a capability of Primary or Secondary, this field must match the LU name on the gateway. Description Use this operator prior to any definitions that reference this local LU. Using the LU6.2 Script Processor E-15 MODE _________________________________________________________________ MODE Defines the parameters that control the operation of the local LU in conjunction with a group of sessions to the specified remote LU, the session group being identified by a mode name. Format MODE mode-name mode-session-limit send-max-ru-size-lower-bound send-max-ru-size-upper-bound preferred-send-ru-size recv-max-ru-size-lower-bound recv-max-ru-size-upper-bound preferred-recv-ru-size conwinner-auto-activate-limit Arguments mode-name Specifies the 1- to 8-character alphanumeric name of the mode name being defined. Do not specify any of the following SNA-architected mode names: o default (see Note) o #BATCH o #INTER o #BATCHSC o #INTERSC o CPSVCMG o SNASVCMG ________________________ Note ________________________ The default name is encoded as eight space (X'20') characters. ______________________________________________________ E-16 Using the LU6.2 Script Processor MODE mode-session-limit Specifies the session limit that the local LU can use during CNOS processing for the session limit. A value of zero indicates that no session limit can be negotiated, either by a remote CNOS request or by local execution of a CNOS verb. If this parameter specifies a non-zero value, the session limit of the local LU must be large enough to include this value. The LU's session limit must be greater than or equal to the sum of the mode-session- limit parameter values for all mode names that reference the local LU (including the SNA-architected mode names). send-max-ru-size-lower-bound Specifies the lower bound for the maximum size of normal- flow requests that the local LU sends on its sessions. Specify a value less than or equal to the value specified on the send-max-ru-size-upper-bound parameter. The local LU uses these lower- and upper-bound values to determine the value for its send maximum RU size specified in its BIND requests and responses. send-max-ru-size-upper-bound Specifies the upper bound for the maximum size of normal- flow requests that the local LU sends on its sessions. Specify a value greater than or equal to the value specified on the send-max-ru-size-lower-bound parameter. The local LU uses these lower- and upper-bound values to determine the value for its send maximum RU size specified in its BIND requests and responses. preferred-send-ru-size Specifies the preferred maximum size of normal-flow requests that the local LU sends on its sessions. This value must be less than or equal to the value specified on the send-max-ru-size-upper-bound parameter and greater than or equal to the send-max-ru-size-lower-bound parameter. recv-max-ru-size-lower-bound Specifies the lower bound for the maximum size of normal- flow requests that the local LU receives on its sessions. Specify a value less than or equal to the value specified on the recv-max-ru-size-upper-bound parameter. The local LU Using the LU6.2 Script Processor E-17 MODE uses these lower- and upper-bound values to determine the value for its receive maximum RU size specified in its BIND requests and responses. recv-max-ru-size-upper-bound Specifies the upper bound for the maximum size of normal- flow requests that the local LU receives on its sessions. Specify a value greater than or equal to the value specified on the recv-max-ru-size-lower-bound parameter. The local LU uses these lower- and upper-bound values to determine the value for its receive maximum RU size specified in its BIND requests and responses. preferred-recv-ru-size Specifies the preferred maximum size of normal-flow requests that the local LU receives on its sessions. This value must be less than or equal to the value specified on the recv_max-ru-size-upper-bound parameter and greater than or equal to the recv-max-ru-size-lower-bound parameter. conwinner-auto-activate-limit Specifies the limit for the number of contention-winner sessions that the local LU can automatically activate when the minimum number of contention-winner sessions for the local LU increases (as a result of CNOS processing, for example, the processing of an INT_MODE operator). A value of zero specifies that the local LU should not automatically activate any sessions. If no automatic- activation limit is defined, the local LU does not automatically activate any sessions. Description Use this operator following the LOCAL and REMOTE operators that created the local LU and remote LU referenced by this operator. E-18 Using the LU6.2 Script Processor NOTE _________________________________________________________________ NOTE Places a comment in a script file. Format NOTE comment-text Arguments comment-text Specifies the comment text that you wish to place in script file. Description Use this operator to comment a script file. You can also use the single number sign (#) or the double number sign (##). Using the LU6.2 Script Processor E-19 REMOTE _________________________________________________________________ REMOTE Defines a remote LU and initializes parameters that control the operation of the local LU when accessing this remote LU. Format REMOTE network-name lu-name Arguments network-name Specifies the network ID of the network that contains the remote LU being defined. lu-name Specifies the name of the remote LU. LU names must be uppercase alphanumeric with a leading alphabetic character. ________________________ Note ________________________ In the case of passive connections using the DECnet SNA Gateway for Synchronous Transport and DECnet SNA Gateway for Channel Transport products, the interface performs the usual syntax check on this qualifier. However, it does not check the value specified in the parameter against what the interface receives in the BIND request. ______________________________________________________ Description The REMOTE operator must follow the definition of the local LU referenced by this operator and must precede any operators that reference this remote LU. E-20 Using the LU6.2 Script Processor SHOW _________________________________________________________________ SHOW Displays the current LU6.2 Script Processor settings. Format SHOW Arguments None. Description This operator displays the informations entered by the IDS operator and the information entered for the last LOCAL, REMOTE, and MODE operators. The following is a sample display: LU62_SERVER Node Name LU62SRV LU62_SERVER ID LU62_SRV Transport to LU6.2 Server TCP DIGITAL SNA Gateway Node SNAGWY Transport to SNA Gateway DECnet Local LU Network USNET101 Local LU Name LOCAL1 Remote LU Network USNET101 Remote LU Name REMOTE1 MODE Name MODE1 Conwinner Auto Activate Limit 3 Send RU Sizes 512, 1024, 1024 Receive RU Sizes 512, 1024, 1024 Session Max, Winners, Losers 10, 7, 2 Using the LU6.2 Script Processor E-21 _________________________________________________________________ Index A______________________________ B______________________________ Access validation files Backing up your system, 1-6 for the Attach Manager daemon Bill of Materials (BOM), 1-2 , 5-2 for the LU6.2 Server, 4-3 C______________________________ sample Attach Manager file, CD-ROM 7-12 installing from, 2-1 ACTIVATE_SESSION configuration CHANGE_SESSION_LIMIT file operator, D-6 configuration file operator, ACT_MODE script file operator, D-11 E-6 Configuration ACT_SVC script file operator, APPC/LU6.2 environment, 1-1 E-7 preparing the client ADD_SECUR_ACC_INFO environment, 5-1 configuration file operator, preparing the server D-8 environment, 4-1, 6-1 ADD_SECUR_INFO configuration Configuration file file operator, D-10 blank lines in, D-2 Attach Manager daemon definition operators, D-5 access validation file, 5-2 ACTIVATE_SESSION, D-6 declaring the TCP/IP service ADD_SECUR_ACC_INFO, D-8 name, 4-2, 5-2 ADD_SECUR_INFO, D-10 disk access requirements, CHANGE_SESSION_LIMIT, 5-2 D-11 messages in system log files, DEFINE_LOCAL_LU, D-15 5-7 DEFINE_MODE, D-19 problems using, 8-8 DEFINE_REMOTE_LU, D-25 starting, 5-3 DEFINE_TP, D-29 startup error messages, 5-5 INITIALIZE_SESSION_LIMIT, stopping, 5-5 D-36 SELECT_SERVER, D-40 keywords in, D-2 Index-1 Configuration file (cont'd) loading E______________________________ with the Configuration Errors during installation, Utility, C-28 2-5 with the LU6.2 Manager, EXIT script file operator, E-8 6-4 parsing F______________________________ with the Configuration Files installed on your system Utility, C-29 SNAL62S310 subset, B-2 with the LU6.2 Manager, SNALU62310 subset, B-1 6-4 sample of, D-3 G saving _______________________________ with the Configuration Gateway considerations, 6-8 Utility, C-29 defining local LUs, 7-8 with the LU6.2 Manager, defining the LU6.2 Server's 6-5 SNA Access Object, 7-7 syntax rules, D-1 defining the partner LU, CPI-C interface 7-10 problems when using, 8-9 displaying the gateway's network ID, 7-6 D______________________________ displaying the transmission DEFINE_LOCAL_LU configuration groups, 7-9 file operator, D-15 enabling the local LU, 7-8 DEFINE_MODE configuration file H operator, D-19 _______________________________ DEFINE_REMOTE_LU configuration HELP script file operator, E-9 file operator, D-25 DEFINE_TP configuration file I______________________________ operator, D-29 IDS script file operator, E-10 Deleting files from your INITIALIZE_SESSION_LIMIT system, 3-3 configuration file operator, Deleting LU6.2 Server entities D-36 with the Configuration Installation Utility, C-26 errors, 2-5 with the LU6.2 Manager, 6-7 from a CD-ROM drive, 2-1 Determining and reporting over the local area network, problems, 3-3 2-4 Disk space, 1-5 preparing the IBM environment Distribution kit, 1-2 for, 1-2 privileges required for, 1-4 sample dialog, A-1 time required, 1-4 verifying Index-2 Installation LU6.2 client (cont'd) verifying (cont'd) Attach Manager service names the client, 3-1 required for, 5-2 the server, 3-2 defined, 1-2 Installation Verification environment, 5-1 Program (IVP), 3-1 LU6.2 Server service names error messages, 3-2 required for, 5-1 for the client interface, sample preparation of, 7-12 3-1 LU6.2 Manager for the server, 3-2 Define menu, 6-6 INT_MODE script file operator, Delete menu, 6-7 E-12 Display menu, 6-6 INT_SVC script file operator, exiting, 6-6 E-14 File menu, 6-3 Help menu, 6-8 L main window, 6-3 _______________________________ running, 6-3 Local LU Session menu, 6-7 defining use of, 6-1 with the Configuration LU6.2 Server Utility, C-4 access validation file, 4-3 with the LU6.2 Manager, declaring TCP/IP service 6-6 names, 4-1, 5-1 with the Script Processor, defined, 1-2 E-15 disk access requirements, deleting 4-3 with the Configuration environment, 4-1, 6-1 Utility, C-26 gateway considerations, 6-8 with the LU6.2 Manager, management, 6-1 6-7 messages in system log files, displaying 4-7 with the Configuration problems contacting, 8-2 Utility, C-16 problems with configuration, with the LU6.2 Manager, 8-4 6-6 sample preparation of, 7-11 with the Script Processor, specifying during server E-21 configuration, 6-3, 7-13, gateway considerations, 6-8 C-2, E-10 sample definition of, 7-14 starting, 4-4 LOCAL script file operator, startup error messages, 4-6 E-15 stopping, 4-6 LU6.2 client LU6.2 Server configuration Attach Manager daemon access activating sessions, 6-7, validation files, 5-2 C-25 changing session limits, 6-7 Index-3 LU6.2 Server configuration (cont'd) M______________________________ deactivating sessions, 6-7 Management defining local LUs, 6-6, of server, 6-1 7-14, C-4 Man pages, 3-3 defining mode names, 6-6, Mode name 7-16, C-10 defining defining remote LUs, 6-6, with the Configuration 7-15, C-8 Utility, C-10 defining TP names, 6-6, with the LU6.2 Manager, 7-17, C-13 6-6 deleting local LUs, 6-7 with the Script Processor, deleting management entities, E-16 C-26 deleting deleting mode names, 6-7 with the Configuration deleting remote LUs, 6-7 Utility, C-26 deleting TP names, 6-7 with the LU6.2 Manager, displaying local LUs, 6-6, 6-7 C-16 displaying displaying mode names, 6-6, with the Configuration C-16 Utility, C-16 displaying remote LUs, 6-6, with the LU6.2 Manager, C-16 6-6 displaying the list of local with the Script Processor, LUs, C-16 E-21 displaying TP names, 6-7, sample definition of, 7-16 C-16 MODE script file operator, initializing session limits, E-16 6-7, 7-18, C-22 loading a configuration file, N______________________________ 6-4, C-28 NOTE script file operator, parsing a configuration file, E-19 6-4, C-29 resetting session limits, P 6-8, C-24 _______________________________ saving a configuration file, Preparing the IBM environment 6-5, 7-19, C-29 for the installation, 1-2 specifying an LU6.2 Server, Preparing the LU6.2 client 6-3, 7-13, C-2 software, 7-12 Preparing the LU6.2 client Software, 5-1 Index-4 Preparing the LU6.2 Server Required software, 1-3 software, 4-1, 7-11 Running the LU6.2 Manager Preparing to install, 1-4 Utility, 6-3 backing up system, 1-6 Running the LU6.2 Script deleting any installed Processor, E-2 software, 1-4 Running the LU6.2 Server obtaining superuser Configuration Utility, C-2 privileges, 1-4 reading release notes, 1-6 S______________________________ registering PAK, 1-6 Script file verifying disk space, 1-5 operators Privileges required for ACT_MODE, E-6 installation, 1-4 ACT_SVC, E-7 Product Authorization Key EXIT, E-8 (PAK), 1-6 HELP, E-9 R IDS, E-10 _______________________________ INT_MODE, E-12 Release notes INT_SVC, E-14 accessing and reading, 1-6 LOCAL, E-15 Remote LU MODE, E-16 defining NOTE, E-19 with the Configuration REMOTE, E-20 Utility, C-8 SHOW, E-21 with the LU6.2 Manager, Script Processor 6-6 operators, E-4 with the Script Processor, running, E-2 E-20 sample script file, E-3 deleting syntax rules, E-2 with the Configuration using blank lines in, E-2 Utility, C-26 using keywords in, E-3 with the LU6.2 Manager, using to reactivate sessions, 6-7 E-3 displaying SELECT_SERVER configuration with the Configuration file operator, D-40 Utility, C-16 Service names, 4-1, 4-2, 5-1, with the LU6.2 Manager, 5-2, 7-11 6-6 Session limits with the Script Processor, changing E-21 with the LU6.2 Manager, sample definition of, 7-15 6-7 REMOTE script file operator, initializing E-20 with the Configuration Utility, C-22 Index-5 Session limits System requirements, 1-3 initializing (cont'd) with the Script Processor, T______________________________ E-12 TCP/IP service names, 4-1, initializing with the Script 4-2, 5-1, 5-2 Processor, E-14 TP name problems initializing, 8-5 defining resetting with the Configuration with the Configuration Utility, C-13 Utility, C-24 with the LU6.2 Manager, with the LU6.2 Manager, 6-6 6-8 deleting Sessions with the Configuration activating Utility, C-26 with the Configuration with the LU6.2 Manager, Utility, C-25 6-7 with the LU6.2 Manager, displaying 6-7 with the Configuration with the Script Processor, Utility, C-16 E-6 with the LU6.2 Manager, activating with the Script 6-7 Processor, E-7 with the Script Processor, activation problems, 8-6 E-21 deactivating sample definition of, 7-17 with the LU6.2 Manager, Troubleshooting 6-7 Attach Manager daemon reactivating problems, 8-8 with the Script Processor, CPI-C program problems, 8-9 E-3 during installation, 3-3 SHOW script file operator, no contact with server, 8-2 E-21 server configuration problems Softlinks created on your , 8-4 system session activation problems, SNAL62S310 subset, B-2 8-6 Starting the Attach Manager session initialization daemon, 5-3 problems, 8-5 Starting the LU6.2 Server, 4-4 syslog messages Stopping the Attach Manager for Attach Manager, 5-7 daemon, 5-5 for LU6.2 Server, 4-7 Stopping the installation, 1-9 Stopping the LU6.2 Server, 4-6 syslog messages Attach Manager, 5-7 LU6.2 Server, 4-7 Index-6 V______________________________ Verifying the installation, 3-1 programming interface software, 3-1 server software, 3-2 Index-7