DEC SNA Peer Server Installation and Configuration Part Number: AA-Q1P8C-TE December 1994 This document describes how to install and configure the DEC SNA Peer Server software on an Alpha AXP system running the DEC OSF/1 AXP operating system. Revision/Update Information: This is a revised manual. Operating System and Version: DEC OSF/1 V3.0 Software Version: DEC SNA Peer Server V1.2 Digital Equipment Corporation makes no representations that the use of its 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. { Digital Equipment Corporation 1994 All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: Alpha AXP, DEC, DECnet, DECrouter, OpenVMS, POLYCENTER, ULTRIX, VAX, VMS, and the DIGITAL logo. The following are third-party trademarks: Advanced Peer-to-Peer Networking, APPN, IBM, NetView, and OS/2 are registered trademarks of International Business Machines Corporation. AS/400, CICS, DISOSS, Displaywriter, OS/2 EE, OS/400, PROFS, TSO, and VTAM are trademarks of International Business Machines Corporation. MS-DOS is a registered trademark of Microsoft Corporation. OSF and OSF/1 are registered trademarks of the Open Software Foundation, Inc. PostScript is a registered trademark of Adobe Systems, Inc. This manual was produced by Information Design and Consulting. Contents Preface vii 1 Preparing to Install the DEC SNA Peer Server Software 1.1 Inspecting the Distribution Kit 1-1 1.2 System Requirements 1-1 1.2.1 Required Hardware 1-1 1.2.2 Required Software 1-2 1.2.3 Installation Time 1-2 1.3 Preparing to Install 1-3 1.3.1 Obtaining Superuser Privileges 1-3 1.3.2 Verifying Disk Space 1-3 1.3.3 Backing Up Your System 1-4 1.3.4 Deleting Old Versions of the Peer Server 1-4 1.3.5 Registering the Product Authorization Key (PAK) 1-4 1.4 Stopping the Installation 1-5 2 Installing the Peer Server 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-7 2.2 Rebuild the Kernel 2-7 2.3 Reboot the System 2-13 2.4 Configure the System 2-13 3 Configuration Worksheets 3.1 Planning Activities 3-1 3.2 The Access Server Objects Worksheet 3-2 3.3 The SDLC Link Information Worksheet 3-4 3.4 The QLLC Link Information Worksheet 3-6 3.5 The LLC2 SAP Link Information Worksheet 3-8 3.6 The General SNA Information Worksheet 3-10 3.7 The SNA Logical Units (List) Worksheet 3-12 3.8 The SNA Logical Units (Populate) Worksheet 3-14 3.9 The LU Authorizations Worksheet 3-16 3.10 The Access Names Worksheet 3-18 3.11 The Partner LUs Worksheet 3-20 4 Configuring the Peer Server 4.1 Configuration Activities 4-1 4.2 Defining the Peer Server Node to the DECnet Network 4-2 4.3 Configuring the Peer Server Using the Configuration Utility 4-2 4.3.1 Invoking the Configuration Utility 4-3 4.3.2 Input and Output Files 4-5 4.3.3 Section 1: SNA Access Server Configuration 4-6 4.3.4 Section 2: Data Link Layer Configuration 4-9 4.3.4.1 Section 2.1: SDLC Configuration 4-9 4.3.4.2 Section 2.2: QLLC Configuration 4-13 4.3.4.3 Section 2.3: LLC2 Configuration 4-16 4.3.5 Section 3: SNA Logical Unit Services Configuration 4-19 4.3.5.1 Section 3.1: Authorization Information 4-19 4.3.5.2 Section 3.2: Logical Unit Configuration Information 4-22 4.3.5.3 Section 3.3: Access Name Configuration Information 4-28 4.3.5.4 Section 3.4: Partner LU Configuration Information 4-30 4.3.6 Section 4: SNA CP Services Configuration 4-31 4.3.7 Generating an NCL Script File 4-37 4.4 Running the Configuration Scripts 4-37 4.5 Solving Configuration Problems 4-38 4.6 Modifying the Configuration with NCL 4-44 4.7 Reconfiguring the Peer Server 4-44 5 Starting and Shutting Down the Peer Server 5.1 Starting the Peer Server 5-1 5.1.1 Checking the Status of the Startup 5-1 5.2 Shutting Down the Peer Server 5-2 A DEC SNA Peer Server NCL Startup Scripts Examples 4-1 Configuration Example (Section 1) 4-8 4-2 SDLC Configuration Example (Section 2.1) 4-13 4-3 QLLC Configuration Example (Section 2.2) 4-16 4-4 LLC2 Configuration Example (Section 2.3) 4-18 4-5 Configuration of an Authorization (Section 3.1) 4-22 4-6 Configuration Using Populate Option (Section 3.2) 4-26 4-7 Configuration Using List Option (Section 3.2) 4-27 4-8 Configuration of Access Names (Section 3.3) 4-29 4-9 Configuration of a Partner LU (Section 3.4) 4-31 A-1 Mainframe Example (T2.0 Dependent LUs) A-2 A-2 AS/400 Example (T2.1 Independent LUs) A-5 Figures 3-1 The Access Server Objects Worksheet 3-3 3-2 The SDLC Link Information Worksheet 3-5 3-3 The QLLC Link Information Worksheet 3-7 3-4 The LLC2 SAP Link Information Worksheet 3-9 3-5 The General SNA Information Worksheet 3-11 3-6 The SNA Logical Units Worksheet (List Method) 3-13 3-7 The SNA Logical Units Worksheet (Populate Method) 3-15 3-8 The LU Authorizations Worksheet 3-17 3-9 The Access Names Worksheet 3-19 3-10 The Partner LUs Worksheet 3-21 Tables 4-1 Peer Server Configuration Utility Editing Keys 4-4 Preface Digital Equipment Corporation's DEC SNA Peer Server software (hereafter referred to as the Peer Server) allows users of the DECnet] and TCP/IP protocols to communicate with programs running on IBM[ systems. These systems must be part of a network configured according to IBM's Systems Network Architecture (SNA). Objectives DEC SNA Peer Server Installation and Configuration contains information about installing and configuring the Peer Server. Audience This manual is written for anyone responsible for managing and maintaining the Peer Server and related products. Structure This manual consists of the following chapters and an appendix: o Chapter 1 lists prerequisites for installing the Peer Server. o Chapter 2 describes the installation of the Peer Server on your Digital system. o Chapter 3 provides configuration worksheets to gather essential information for configuring the Peer Server. o Chapter 4 describes the configuration of the Peer Server. o Chapter 5 describes how to start and stop the Peer Server. o Appendix A provides example NCL startup script configurations for SDLC in two different environments. A postpaid Reader's Comments form is located at the back of this manual. If you have any comments about this manual, please complete and return this form. Associated Digital Documents The other documents in the Peer Server set are the following: o DEC SNA Peer Server Management o DEC SNA Peer Server NCL Reference o DEC SNA Peer Server Guide to IBM Resource Definition Associated IBM Documents o Enterprise Networking with SNA Type 2.1 Nodes (IBM Order No. G24-3433) o An Introduction to Advanced Program-to-Program Communication (APPC) (IBM Order No. GG24-1584) o LAN Concepts and Products (IBM Order No. GG24-3178) o SNA Type 2.1 Node Reference (IBM Order No. SC30-3422) o Systems Network Architecture Concepts and Products (IBM Order No. GC30-3072) o Systems Network Architecture Reference Summary (IBM Order No. GA27-3136) o Systems Network Architecture Technical Overview (IBM Order No. GC30-3073) Conventions Used in This Guide Special type This special type in examples indicates system output or user input. Boldface Boldface type in examples indicates user input. UPPER/lower-case Uppercase and lowercase letters in command lines or in examples must be entered as shown. lowercase-italics Lowercase italics in command syntax or examples indicate variables for which either the user or the system supplies a value. key Indicates that you press the specified key. Ctrl/X Indicates that you should hold the Control key down and press the key specified by the X. Indicates that you press the Return key. # This is the default superuser prompt. % This is the default user prompt. Acronyms ACF/NCP Advanced Communications Function for Network Control Program (also referred to as IBM's NCP) API DEC SNA VMS Application Programming Interface product APPC/LU6.2 DEC SNA VMS APPC/LU6.2 Programming Interface product CSMA/CD Carrier Sense Multiple Access with Collision Detection DLC Data link control DTF DEC SNA Data Transfer Facility software LLC2 Logical link control - type 2 LU Logical unit LU6.2 Logical unit type 6.2 PLU Primary logical unit PU Physical unit QLLC Qualified logical link control RU Request/response unit SAP Service Access Point SDLC Synchronous Data Link Control SLU Secondary logical unit SNA IBM's Systems Network Architecture 3270 TE DEC SNA VMS 3270 Terminal Emulator software T2.0 SNA node type 2.0 T2.1 SNA node type 2.1 Terminology Interconnect system Refers to the DEC SNA Peer Server software. Interconnect products Refers to the DEC SNA Peer Server software and the DEC SNA access routines. Network manager Refers to the person responsible for installing and managing an interconnect product. (null)(null)(null) 1 Preparing to Install the DEC SNA Peer Server Software This chapter discusses the planning you must do prior to installing the DEC SNA Peer Server product (referred to in this document as the "Peer Server"). Planning issues covered here include an overview of the installation procedure, system requirements, installation choices, software license Product Authorization Key requirements, and other system dependencies. 1.1 Inspecting the Distribution Kit The software Bill of Materials (BOM) that shipped with your Peer Server media distribution kit lists the contents of the kit. Carefully compare the items you received with the items listed in the BOM. If any components are missing or damaged, contact your Digital representative before continuing. Before proceeding with the installation, Digital strongly recommends that you read the release notes which ship as part of the online documentation. 1.2 System Requirements This section lists and describes the hardware and software requirements your site must meet in order to install the Peer Server. 1.2.1 Required Hardware To install the Peer Server successfully, you must have the following minimum hardware configuration: o Alpha AXP workstation or server o 64 MB RAM recommended (minimum) See the Software Support Addendum (SSA) for a list of the processors which support the Peer Server. The SSA is included with the Software Product Description that ships with the Peer Server distribution kit. 1.2.2 Required Software The following software is required to support the Peer Server: o DEC OSF/1 V3.0 o DEC OSF/1 X.25 Version V1.1 (only for QLLC) The following subsets are included in the Peer Server kit. If they are already installed (for example, due to a previous installation of DECnet or X.25 software), setld omits them as subsets that may be selected for installation. o CTF Collector Components (CTABASE130) o DEC OSF/1 WAN Utilities (ZZAUTIL110) o DEC SNA Peer Server (T21SRVR120) o WAN Sync Drivers and Datalinks Base (WDABASE110) o WAN Synchronous Device Drivers (WDADRIVERS110) o CTF User Environment (CTAANAL130) o DEC SNA Peer Server Management (T21MGMT120) o DECnet/OSI Network Management (DNANETMAN300) o DECnet/OSI Datalink Components (DNADLI300) o WAN OSI CONS Datalinks (WDADATALNKS110) See the SSA for a complete list of software required to support the Peer Server. 1.2.3 Installation Time Installation of the Peer Server requires approximately five minutes, not including kernel rebuild and configuration. 1.3 Preparing to Install Before you begin the actual installation, prepare your system for the Peer Server. Preparation includes the following activities: o Obtaining superuser privileges. o Checking for sufficient system disk space. o Optionally, backing up your system disk. Digital strongly recommends that you perform a full system backup before installation. o Registering your Product Authorization Key (PAK). 1.3.1 Obtaining Superuser Privileges To install and configure the Peer Server, you must have superuser privileges. To acquire these privileges, issue the following command followed by the root password. See the DEC OSF/1 system manager documentation for more details. % su Return password: password Return # 1.3.2 Verifying Disk Space Check the free disk space on your system. You must have sufficient free space to install and configure the Peer Server. The installation will fail if there is insufficient space for copying the software from the distribution media or if there is not enough free space to rebuild the DEC OSF/1 kernel. Minimum space requirements (based on the options you select) for the Peer Server are as follows: o 3 MB in the / partition to create a new kernel (in addition to the size of the current kernel). o 8 MB in the /usr partition for the Peer Server, plus 20 MB for the wide-area device drivers and management software if not already installed. o 4 MB in the /var partition for the wide-area device drivers and management software if not already installed. To check the free space in the various partitions, enter the following commands: # df -k / Return # df -k /usr Return # df -k /var Return 1.3.3 Backing Up Your System Before installing the Peer Server, back up your system disk. See the document DEC OSF/1 Guide to System Administration for further details. 1.3.4 Deleting Old Versions of the Peer Server Before you begin the installation, check to see whether a previous version of the Peer Server exists on your system. If it does, you must delete those subsets before you install the new Peer Server software. NCL scripts or answer files previously created will remain in the /var/sna directory for use with the new software version. Use the following command to see whether the Peer Server is installed on your system, where T21 is the subset name prefix of the Peer Server: # setld -i | grep "^T21" The system displays all subsets that are installed. If the word "installed" follows the name of the subset, then that subset is installed. To delete the software from your system, log in as superuser and issue the setld command with the -d option, as follows, where subset is the name of a Peer Server subset: # setld -d subset [subset...] 1.3.5 Registering the Product Authorization Key (PAK) The Peer Server supports the License Management Facility (LMF). You must register your License Product Authorization Key (License PAK) in the License Database (LDB) to use the Peer Server 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. To register the Peer Server license PAK using LMF, proceed as follows: 1. Log on to your system as superuser. % su Return password: password Return # 2. Issue the following command from the su prompt. Press Return after the confirmation message appears: # lmfsetup Return Register PAK (type q or quit to exit) [template] Return 3. After you confirm the procedure, the system prompts you for information related to the fields on your PAK form. This form ships with your Peer Server distribution kit if you ordered the license and media together. Otherwise, Digital ships it separately to a location based on your license order. Using the information from your Peer Server PAK, reply to each question. Any fields left blank in your PAK should be left blank when you key in the data. 4. After you have answered all questions, the system issues the following completion message. Enter quit and press Return: Register PAK (type q or quit to exit) [template] quit Return 5. After leaving lmfsetup, issue the following reset command: # lmf reset Return 6. If you attempted to load a PAK when a previous PAK was already installed, a message similar to the following appears: Combine SNA-PEER-SERVER-USER auth-num with SNA-PEER-SERVER-USER auth-num 7. After completing the LMF procedure, verify your registration: # lmf list Return For further information concerning the use of the LMF software or for more details about obtaining a license and PAK, see the document DEC OSF/1 Guide to Software License Management. You can also reference the lmf and lmfsetup man pages (lmf(8) and lmfsetup(8)). This completes the preinstallation procedure for the Peer Server. Chapter 2 describes the actual Peer Server installation process. 1.4 Stopping the Installation To stop the installation at any time, press Ctrl/C. You must then delete files created up to this point interactively. The directories and files created during Peer Server installation are listed in the release notes. (null)(null)(null) 2 Installing the Peer Server This chapter describes the DEC SNA Peer Server installation procedure. Before installing the Peer Server, 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 Peer Server 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). System input and output during installation will vary for users of the Peer Server software. These variations depend on your current configuration and on the requirements for the configuration. The Configuration utility prompts for an LLC2 configuration will depend on your LAN Station type, Ethernet or Token Ring. If you have DECnet/OSI Network Management software installed on your system, this will not appear on the list of optional subsets. 2.1.1 Installing from a CD-ROM Drive To install the Peer Server subset from the Consolidated Software Distribution CD-ROM, do the following: 1. Determine the location of the Peer Server files on the CD-ROM. See the master index table in the document Consolidated Software Distribution Disk User's Guide 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, issue the following command to list available drives. The drive will be either RRD40 or RRD42. # file /dev/rr*c Return To mount the disk, issue the following command, where dev-name is the block device name of your drive. # mount -r -d /dev/dev-name /mnt Return For example, a character special device of /dev/rrz4c shown by the file command, file /dev/rr*c, would be entered as the block device /dev/rz4c. 3. Install the Peer Server software using the setld command, where T 21110/kit is the name of the directory on the CD-ROM where the Peer Server files are located: # setld -l /mnt/T21120/kit Return After you enter the setld command, the system displays the following messages. When you have read them, press Return to continue. DEC SNA Peer Server for OSF/1 AXP V1.2-0 (Rev. 1) (c) Digital Equipment Corporation 1994. All Rights Reserved. This software is proprietary to and embodies the confidential technology of 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. To install and configure the DEC SNA Peer Server on this system, choose all subsets in the following selection. To install just the management support, select just those subsets in the DEC SNA Peer Server Management section. The installation will complete in 3-5 minutes depending on processor type. Consult the DEC SNA Peer Server Installation & Configuration guide for more details. Hit to continue: Return You now select the combination of optional subsets you wish to install from a menu. You are required to install all of the Peer Server subsets. Further, if you want to select QLLC when you configure the Peer Server, you must install the X.25 software separately prior to configuration. Enter the number of your selection and press Return. The system asks for confirmation. 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. Note The following selection assumes that the CTF Collector Components, WAN components, and DECnet are not already installed on your system. - DEC SNA Peer Server: 1) CTF Collector Components 2) DEC OSF/1 WAN Utilities 3) DEC SNA Peer Server 4) DECnet/OSI Datalink Components 5) WAN OSI CONS Datalinks 6) WAN Sync Drivers and Datalinks Base 7) WAN Synchronous Device Drivers - DEC SNA Peer Server Management: 8) CTF User Environment 9) DEC SNA Peer Server Management 10) DECnet/OSI Network Management Or you may choose one of the following options: 11) ALL of the above 12) CANCEL selections and redisplay menus 13) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 11 Return You are installing the following optional subsets: - DEC SNA Peer Server: CTF Collector Components DEC OSF/1 WAN Utilities DEC SNA Peer Server DECnet/OSI Datalink Components WAN OSI CONS Datalinks WAN Sync Drivers and Datalinks Base WAN Synchronous Device Drivers - DEC SNA Peer Server Management: CTF User Environment DEC SNA Peer Server Management DECnet/OSI Network Management Is this correct? (y/n): y Return Once you have verified your selection, the system installs the subsets and displays a series of in-progress messages. Checking file system space required to install selected subsets: File system space checked OK. DEC OSF/1 WAN Utilities Copying from /mnt/T21120/kit (disk) Verifying WAN Sync Drivers and Datalinks Base Copying from /mnt/T21120/kit (disk) Verifying WAN Synchronous Device Drivers Copying from /mnt/T21120/kit (disk) Verifying WAN OSI CONS Datalinks Copying from /mnt/T21120/kit (disk) Verifying DEC SNA Peer Server Management Copying from /mnt/T21120/kit (disk) Verifying DEC SNA Peer Server Copying from /mnt/T21120/kit (disk) Working....Wed May 9 16:55:09 EST 1994 Verifying DECnet/OSI Network Management Copying from /mnt/T21120/kit (disk) Working....Wed May 9 16:55:57 EST 1994 Verifying DECnet/OSI Datalink Components Copying from /mnt/T21120/kit (disk) Verifying CTF User Environment Copying from /mnt/T21120/kit (disk) Verifying CTF Collector Components Copying from /mnt/T21120/kit (disk) Verifying Installing WAN Utilities V1.1 for DEC OSF/1 Systems (c) Digital Equipment Corporation. 1993. All Rights Reserved. Creating directories and symbolic links for ZZAUTIL110 ... done. Configuring "DEC OSF/1 WAN Utilities " (ZZAUTIL110) Installing WAN Device Drivers for DEC OSF/1 Systems, Base subset (c) Digital Equipment Corporation. 1993. All Rights Reserved. Creating product tc_option_data.c file ... done. Creating directories and symbolic links for WDABASE110 ... done. Configuring "WAN Sync Drivers and Datalinks Base " (WDABASE110) Installing WAN Device Drivers for DEC OSF/1 Systems, Synchronous Device Drivers. (c) Digital Equipment Corporation. 1993. All Rights Reserved. Creating directories and symbolic links for WDADRIVERS110 ... done. Configuring "WAN Synchronous Device Drivers " (WDADRIVERS110) Installing WAN Device Drivers for DEC OSF/1 Systems, OSI CONS Datalinks. (c) Digital Equipment Corporation. 1993. All Rights Reserved. Creating directories and symbolic links for WDADATALNKS110 ... done. Configuring "WAN OSI CONS Datalinks " (WDADATALNKS110) Installing DEC SNA Peer Server for OSF/1 AXP V1.2-0 (Rev. 1) Copyright Digital Equipment Corporation 1994. All Rights Reserved. Creating softlinks for T21MGMT120 ... done. Configuring "DEC SNA Peer Server Management " (T21MGMT120) Installing DEC SNA Peer Server for OSF/1 AXP V1.2-0 (Rev. 1) Copyright Digital Equipment Corporation 1994. All Rights Reserved. Creating softlinks for T21SRVR120 ... done. Configuring "DEC SNA Peer Server " (T21SRVR120) The system next displays some instructions on how to complete the installation procedure. After you have read them, press Return to continue. To complete the installation of the DEC SNA Peer Server software please do the following: - Rebuild the kernel by executing the command # /usr/sbin/t21setup kernel - Reboot the system to load the new kernel. - Configure the DEC SNA Peer Server software by executing the command # /usr/sbin/t21setup configure Refer to the DEC SNA Peer Server Installation Guide for details. Hit to continue: Return Creating directories and symbolic links for DNANETMAN300 ... done. Configuring "DECnet/OSI Network Management " (DNANETMAN300) Creating directories and symbolic links for DNADLI300 ... done. Configuring "DECnet/OSI Datalink Components " (DNADLI300) Installing CTF for DEC OSF/1 Systems User Environment (c) Digital Equipment Corporation. 1993. All Rights Reserved. Creating directories and symbolic links for CTAANAL130 ... done. Configuring "CTF User Environment " (CTAANAL130) Installing CTF for DEC OSF/1 Systems Collector Components (c) Digital Equipment Corporation. 1993. All Rights Reserved. Creating directories and symbolic links for CTABASE130 ... done. WAN Device Drivers Installation Successful ------------------------------------------ To complete the installation, build a new kernel using the following command: # /usr/sbin/wddsetup No further questions. Configuring "CTF Collector Components" (CTABASE120) # Note You should ignore the instruction to execute wddsetup. Follow the steps in Section 2.2 to rebuild the kernel. 2.1.2 Installing over the Local-Area Network with RIS If you are installing the Peer Server over your local-area network, use the Remote Installation Service (RIS) utility. See Sharing Software on a Local Area Network for RIS requirements. Issue the following command, where host-name is the name of the node from which you are loading the software. # setld -l host-name: Return The installation then proceeds as described in the previous section. 2.2 Rebuild the Kernel After you run setld, the system moves the Peer Server software into the appropriate directory and creates all required links. Once the Peer Server is properly installed, you must rebuild the kernel by issuing the following command: # /usr/sbin/t21setup kernel Return The system responds with information concerning the Peer Server and a prompt asking whether you want to rebuild the kernel. Enter y and press Return at the prompt to start rebuilding the kernel. Note The following example configures SDLC using the DEC 3000 built-in serial port (scc). Your installation may vary based on the DLC interface and the specific configuration options selected. DEC SNA Peer Server for OSF/1 AXP V1.2-0 (Rev. 1) Configuration Procedure Copyright Digital Equipment Corporation 1994. All Rights Reserved. There will be a pause while this procedure gathers some information from your system. DEC SNA Peer Server updating dependent products Updating CTF analysis program ... done. Updating Common Agent MIR ... done. This procedure allows you to add DEC SNA Peer Server support to your OSF/1 kernel. This must be done before the DEC SNA Peer Server can be configured on your system. Do you want this procedure to rebuild your kernel now? (y/n/?) [y]: Return The system needs to know what Data Link Control (DLC) interfaces to include in the Peer Server configuration. It prompts you to identify which of these interfaces (SDLC, LLC2, and QLLC) you want to include in the build. The SNA Peer Server must be configured with one or more of the following datalink control interfaces: SDLC (WAN synchronous connect), LLC2 (LAN connect), or QLLC (SNA over X.25). LLC2 is required for SNA over token ring. Do you wish to configure SDLC? (y/n) [n]: y Return You have chosen to include the SDLC datalink Is this correct? (y/n) [y]: Return SDLC included... Do you wish to configure QLLC? (y/n) [n]: Return You have chosen to not include the QLLC datalink Is this correct? (y/n) [y]: Return Do you wish to configure LLC2? (y/n) [n]: Return You have chosen to not include the LLC2 datalink Is this correct? (y/n) [y]: Return DEC SNA Peer Server configuring Wide Area Device Drivers WAN Device Drivers for DEC OSF/1 Configurator. (c) Digital Equipment Corporation. 1993. All Rights Reserved. Configuring "CTF Collector Components " (CTABASE130) Ensuring all underlying dependencies are configured. ++++++++++++++++++++++++++++++ Configuring "DEC OSF/1 WAN Utilities " (ZZAUTIL110) ZZAUTIL101 Configured. ------------------------------ Checking for CTF support in sys/net/netaf_config.c Adding CTF support to sys/net/netaf_config.c ... done. CTABASE120 configured. Configuring "DECnet/OSI Network Management " (DNANETMAN300) Checking for NETMAN support in /sys/net/netaf_config.c Added NETMAN support to /usr/sys/net/netaf_config.c file. Creating /sbin/init.d/netman Now you specify the hardware devices on which you want the WAN Device Drivers and Datalink Protocols (WDA) software to be run. The system displays the devices supported on your system and asks you to choose. The system prompts you for your choice and asks for confirmation before proceeding. You must now specify the hardware device(s) on which you want the WAN Device Drivers and Datalink Protocols (WDA) software to be run. Note that with the LLC2 datalink protocol, no synchronous drivers need to be specified as this protocol operates over a LAN. The synchronous devices supported on your system are: scc - Flamingo/Sandpiper/Pelican synchronous line dsy - TURBOchannel T1/E1 synchronous line option none - No synchronous device driver is required Please specify which device(s) {dsy scc none} are to be used. [scc]: Return The scc driver will be built into the kernel. Is this correct? (y/n) [y]: Return Note The kernel configuration next prompts you to specify which datalink protocols are needed for your Peer Server installation. If you are using only SDLC, you do not need an additional WDADATALNKS Level 2 protocol. So you choose the first option (1) for SDLC. If you are using QLLC, you usually need the HDLC/LAPB Synchronous datalink protocols. You, therefore, choose the second option (2) for QLLC. If you are using LLC2, choose the third option (3). For any combination of QLLC and LLC2, choose the fourth option (4). The example that follows selects an installation option for an SDLC connection. Select one of the following datalink protocol options: 1) No Level 2 datalink protocol is required. 2) The HDLC/LAPB Synchronous datalink protocols are required. 3) The LLC2 (LAN) datalink protocol is required. 4) All datalink protocols (HDLC/LAPB/LLC2) are required. Enter datalink protocol option(s) required [2]: 1 Return You have selected no Level 2 datalink. Is this correct? (y/n) [y]: Return You must now specify which of the synchronous ports you have configured will operate in half-duplex mode. In the following section, devices which are to be used on point-to-point half-duplex lines should be specified as using half-duplex. Note If you have devices that will be used on full-duplex multipoint lines, specify them as full duplex here. The specification of the line as multipoint is made during configuration. See Chapter 4. The ports you have configured on your system are: sscc0 Please specify which port(s) will operate in half-duplex mode. [none]: Return No lines will operate in half-duplex mode. Is this correct? (y/n) [y]: Return The line speed to be used on half-duplex point-to-point and multipoint lines must be entered next. This is used by the Peer Server software to run the half-duplex modem control protocols properly. If a value is not entered for a line, then it is assumed to be running at 1200 bps. Note that the actual clocking on the line is always derived from the DCE. You must enter the line speed for any ports which will be used for IBM multipoint. Line speed must be entered in bits/second. Eg. 19.2Kbits/sec should be entered as "19200". Enter the Line Speed for port sscc0 [no default] : 9600 Return Port sscc0 will run at 9600 BPS. Is this correct? (y/n) [y]: Return Some communication devices utilize NRZI (nonreturn-to-zero-inverted) bit encoding to maintain bit synchronization across longer frames. From the list of device ports displayed, select those that you want to use NRZI encoding. A port should only be selected to use NRZI encoding if its hardware and the remote device(s) are configured to require it. If you are uncertain as to the correct response, check with your network administrator. The ports you have configured on your system are: sscc0 Please specify which port(s) are to use NRZI. [none]: Return No lines will use NRZI encoding. Is this correct? (y/n) [y]: Return After the procedure builds the new kernel, it modifies your system files. This takes approximately five minutes. Before the kernel rebuild procedure edits files, it saves each one to a file in the form filename.savn, where n is a version number that is incremented on each installation. The rest of the procedure may take from 10 minutes up to 2 hours to rebuild your kernel. Starting kernel rebuild... *** KERNEL CONFIGURATION AND BUILD PROCEDURE *** Saving /sys/conf/HOSTNAME as /sys/conf/HOSTNAME.bck Do you want to edit the configuration file? (y/n) [n]: Return *** PERFORMING KERNEL BUILD *** Working....Wed May 9 17:13:52 EST 1994 Working....Wed May 9 17:15:53 EST 1994 Working....Wed May 9 17:17:55 EST 1994 Working....Wed May 9 17:19:56 EST 1994 Working....Wed May 9 17:21:58 EST 1994 Working....Wed May 9 17:24:00 EST 1994 The new kernel is /sys/HOSTNAME/vmunix Kernel built successfully If there is enough space in the root (/) directory, the rebuild procedure saves the current vmunix and moves the new kernel to the root directory as /vmunix: Saving /vmunix Moving /sys/HOSTNAME/vmunix to /vmunix Please reboot the system now, then run /usr/sbin/t21setup CONFIGURE to configure the DEC SNA Peer Server for OSF/1 AXP V1.2-0 (Rev. 1) on this system. t21setup completed successfully. If there is not enough space, the rebuild procedure instructs you on moving the old kernel manually: There is not enough space on your root partition (/) to hold the new kernel. Please make more space available on this partition. The new kernel is approximately 8728 KB in size. Please move your new kernel, /sys/sys-name/vmunix, to the root partition after making more space available. WARNING: if you fail to successfully copy the new kernel to /vmunix the current kernel, because of lack of space, then your system will fail to reboot. Use the command: # more /var/sna/kernel_install_notes.txt to find out more about how to install your new kernel if you are not familiar with OSF kernel installation procedures. Creating /var/sna/kernel_install_notes.txt t21setup terminated. # For information about finishing the procedure see the release notes located in /var/sna/t21_V12-0_release_notes. 2.3 Reboot the System Reboot the system containing the Peer Server software. You can issue either of the following commands: w # shutdown -r now Return w # /sbin/reboot Return 2.4 Configure the System Once the system has been rebooted with the kernel containing the Peer Server software, you must configure the system. Enter the following command: # /usr/sbin/t21setup configure Return This step augments the NCL online help, augments the NCL dictionary with Peer Server entities, and creates and links Peer Server special files. During this step, you can create the initial Peer Server startup configuration and the TN3270 server configuration, and optionally start the product. See Chapter 3 for information on planning your configuration. See Chapter 4 for more information about configuring Peer Server entities. The following series of prompts is displayed. DEC SNA Peer Server for OSF/1 AXP V1.2-0 (Rev. 1) Configuration Procedure Copyright Digital Equipment Corporation 1994. All Rights Reserved. There will be a pause while this procedure gathers some information from your system. DEC SNA Peer Server updating ncl dictionary ... sdlc ... qllc ... sna access server ... sna lu services ... done. DEC SNA Peer Server updating ncl help file ... done. DEC SNA Peer Server creating system startup/shutdown links DEC SNA Peer Server creating streams special files ... done. Do you wish to configure the DEC SNA Peer Server startup now? [y] n Return You are now given the opportunity to configure the TN3270 Server that ships as part of the Peer Server. You can configure the server to listen on multiple TCP/IP ports for incoming TN3270 client requests with each separate port mapped by the TN3270 server to use a specific access name defined in the Peer Server. Do you wish to configure the tn3270 server? [y] n Return Do you wish to start the DEC SNA Peer Server now? [n] Return # Now that you have configured the system, configure Peer Server entities before you start up the Peer Server. See Chapters 3 and 4. If you want to reconfigure the TN3270 Server configuration at some later time, execute the script file /usr/sbin/tn3270_setup. (null)(null)(null) 3 Configuration Worksheets This chapter discusses the information you must gather before configuring the Peer Server into your network environment. 3.1 Planning Activities The following list itemizes the information that you must have before configuring the Peer Server into your network environment: o SNA Access Server object parameters o General SNA information o SNA Logical Unit (LU) parameters o LU Authorization parameters o Access Name parameters o Partner LU parameters o Based on your DLC configuration: - LLC2 SAP information - QLLC Link information - SDLC Link information This chapter contains a series of worksheets intended to provide a convenient way to organize and record this information. Each worksheet lists the information you will need and the order in which you are prompted for it in the Configuration utility dialog. Where applicable, the worksheets list defaults and options. See Chapter 4 for details about each of these parameters. 3.2 The Access Server Objects Worksheet Use the SNA Access Server Objects worksheet (Figure 3-1) to record information about the objects that users can gain access to by way of the SNA Access Server. SNA Access Server Objects are references to non-SNA objects. These objects represent tasks that are available in the network. IBM users connect to one of these tasks by connecting to Peer Server LUs that you link to one of the objects. For each SNA Access Server Object, you must identify the object and its location, as follows: w For DECnet transport, indicate the node where the object resides and the number of the object on the node. The object number can range from 0 to 255. The number 0 is a special case; use this number to identify the object by task name instead of by object number. See the documentation for the access routines you will be using to find the object numbers each access routine uses. The Peer Server requires objects only when communication is initiated from the IBM side. For each object, enter the name of the object, the node, number, and optionally, the task name. o For TCP/IP transport, indicate the IP node name where the object resides and the port number or service of the object. o For local transport, indicate the local user name where the object resides and the name of the object. Repeat the process for all objects the Peer Server supports. Make additional copies of the worksheet if you need more space. Figure 3-1 The Access Server Objects Worksheet Object name: __________________________ Transport (TCPIP, DECnet, local) [TCPIP]: __________________________ Node: _______________ Object/port number (0-32767) [0]: __ __ __ __ __ Object task/name: _______________________________ Object name: __________________________ Transport (TCPIP, DECnet, local) [TCPIP]: __________________________ Node: _______________ Object/port number (0-32767) [0]: __ __ __ __ __ Object task/name: _______________________________ Object name: __________________________ Transport (TCPIP, DECnet, local) [TCPIP]: __________________________ Node: _______________ Object/port number (0-32767) [0]: __ __ __ __ __ Object task/name: _______________________________ Object name: __________________________ Transport (TCPIP, DECnet, local) [TCPIP]: __________________________ Node: _______________ Object/port number (0-32767) [0]: __ __ __ __ __ Object task/name: _______________________________ 3.3 The SDLC Link Information Worksheet Use the SDLC Link Information worksheet (Figure 3-2) to record information about the SDLC Links you will be defining. For each link, you must define the following information: o The SDLC Link name o The Modem Connect Line name o The Configuration type (point-to-point or multipoint) o The Link Station capability (primary, secondary, or negotiable) o The Receive frame size o The maximum number of retries o The SDLC Station name o The SDLC Station address o Group address o The Transfer mode (two-way-alternate or two-way-simultaneous) o The modulo (normal or extended) o The Window size o The Inactivity timer value o The Send frame size Repeat the process for all SDLC Links the Peer Server supports. Make additional copies of the worksheet if you need more space. Figure 3-2 The SDLC Link Information Worksheet SDLC Link name [SDLC-0]: _________________________________ Modem Connect Line: ________________ Configuration [PointToPoint]: ___________________________ (point-to-point, multipoint) Link Station capability [negotiable]: ___________________ (primary, secondary, negotiable) Receive frame (1-32765) [1000]: __________ Retry maximum (0-128) [15]: __________ SDLC Station name [STN-0]: _____________________ Station address (01-FE) [40]: __ __ Group address (00 - FE) [00]: __ __ Transfer mode (twa/tws) [TWA]: _________ Modulo (normal or extended): _____________________ [NORMAL] Window size (1-127) [7]: __ __ __ Inactivity timer (0-7200) [30]: __ __ __ __ Send frame (1-32765) [1000]: __ __ __ __ 3.4 The QLLC Link Information Worksheet Use the QLLC Link Information worksheet (Figure 3-3) to record information about the QLLC Links you will be defining. For each link, you must define the following information: o The QLLC Link name o The Filter name o The Template name o The DTE Class o The QLLC Station name o The QLLC Usage Type (outgoing, incoming, or both) o The Maximum Number of Retries o The Retry Timeout in seconds o The QLLC Station Capability (primary, secondary, or negotiable) o The Remote DTE Address o The Maximum BTU Size Repeat the process for all QLLC Links the Peer Server supports. Make additional copies of the worksheet if you need more space. Figure 3-3 The QLLC Link Information Worksheet QLLC Link name [QLLC-0]: ___________________________ Filter name [FILTER_QLLC]: ___________________________ Template name [TEMPLATE_QLLC]: ___________________________ DTE Class [CLASS_QLLC]: ___________________ QLLC Station name [STN-0]: _____________________ Usage Type [BOTH]: _____________________ (outgoing, incoming, both) Retry Maximum (0 - 255 [4]: _________ Retry Timeout (1 - 600) [10]: _________ Link Station Capability [NEGOTIABLE] _____________________ (primary, secondary, negotiable) Remote DTE Address: _____________________ Maximum BTU Size (128 - 512) [512]: _____________________ 3.5 The LLC2 SAP Link Information Worksheet Use the LLC2 SAP Link Information worksheet (Figure 3-4) to record information about the LLC2 SAP Links you will be defining. For each SAP, you must define the following information: o The LLC2 SAP name o The LAN Station Type o The LAN Station name o The Local LSAP Address o The SAP Link name o The Maximum Receive Data Size o The Remote LSAP Address o The Remote MAC Address (xx-xx-xx-xx-xx-xx) If you plan to configure a Token Ring or CSMA-CD (Ethernet) entity, you will be prompted to enter the following: o Token Ring or CSMA-CD Station Name o Communication Port Name o Token Ring Speed ( 4 or 16 Megabits per second) (You will receive this prompt during Token Ring configuration only.) Repeat the process for all LLC2 links the Peer Server supports. Make additional copies of the worksheet if you need more space. Figure 3-4 The LLC2 SAP Link Information Worksheet LLC2 SAP name [SNA-0]: ______________________________ LAN Station Type [Token Ring]: _____________________ (Token Ring, Ethernet) LAN Station name [TRN-0]:1 _____________________ Local LSAP address (00 - FE) [04]: __ __ SAP Link name [LINK-0]: ______________________________ Maximum Receive Data Size [1028]: ______________________________ Remote LSAP address (00 - FE) [04]: __ __ Remote MAC address (xx-xx-xx-xx-xx-xx) __ __ -__ __ -__ __ -__ __ -__ __ -__ __ Token Ring 2 Station name [TRN-0]:3 ______________________________ Communication port name [TRA0]:4 ______________________________ Token Ring speed [16]: __________ 1 If the LAN Station Type specified is Ethernet, the default LAN Station name is [CSMACD-0]. 2 Ethernet if you are configuring for CSMA/CD. 3 The Ethernet default value is [CSMACD-0]. 4 The Ethernet default value is [ln0]. 3.6 The General SNA Information Worksheet Use the General SNA Information worksheet (Figure 3-5) to record information about the SNA environment in which the Peer Server will operate. The general SNA information you need to collect is as follows: o The network identification of the Peer Server. o The CP name of the Peer Server. o The maximum number of active transmission groups supported by the SNA network. The transmission group information you need to collect is as follows: o Transmission group name o Data link control (DLC) type (SDLC, QLLC, LLC2) o DLC-type Link o DLC-type Station o Dependent LU support (y/n) o Connection type (permanent or temporary) - (If temporary) Disconnect timer o Node ID o Incoming restrictions (y/n) - (If Yes) Required Adjacent Node ID: - (If Yes) Required Adjacent Network ID: - (If Yes) Required Adjacent CP Name: Repeat the process for all Transmission Groups the Peer Server supports. Make additional copies of the worksheet if you need more space. Figure 3-5 The General SNA Information Worksheet Network ID: _________________________ CP name: _________________________ Max active transmission groups: ____________ Transmission Group information Transmission group name [ ]: _________________________ Data link type (SDLC, QLLC, LLC2) [ ]: ______________ DLC-type1 Link2 [ ]: _________________________ DLC-type1 Station3 [ ]: _________________________ Dependent LU support (y/n) [yes]: _____________ Connection type [permanent]: __________________________ (permanent or temporary) (If temporary) Disconnect timer [30]: __________ Node ID [%X00000000]: %X __ __ __ __ __ __ __ __ Incoming restrictions (y/n) [n]: __________ (If Yes) Required Adjacent Node ID: __ __ __ __ __ __ __ __ (If Yes) Required Adjacent Network ID: __________ (If Yes) Required Adjacent CP Name: __________ 1 DLC-type is SDLC, QLLC, or LLC2. 2 If the DLC-type is LLC2, this is SAP instead of Link. 3 If the DLC-type is LLC2, this is Link instead of Station. 3.7 The SNA Logical Units (List) Worksheet Use the SNA Logical Units worksheet to record information about Peer Server logical units (LUs). This manual contains two SNA Logical Units worksheets. One allows you to specify individual LUs; the other allows you to specify a range of LUs with similarities in the LU name. On the first SNA logical units worksheet (Figure 3-6), you must specify each LU name individually or specify a list of LU names. This parallels the List option in the Configuration utility. Start by recording the LU names in the first set. You can specify a single LU name or a list of LU names. For dependent LUs, list the dependent LU transmission group and the LU address. Next, specify the capability you desire for this set of LUs. LUs can act as secondary LUs, primary LUs, or both, depending on the individual sessions they support. If the LUs can assume the role of a primary LU, record the SNA access server object that will handle incoming connection requests. Next, record the list of authorizations you wish to use to limit access to the set of LUs. Repeat the process for as many LU sets that you wish to specify using the list method. Make additional copies of the worksheet if you need more space. Figure 3-6 The SNA Logical Units Worksheet (List Method) Logical Unit name: __________________________ For dependent LU: Transmission group: ___________________________ LU address: ___________________________ Capability: Primary ____ Secondary ____ Both ____ Object name: ____________________________________ Authorizations: ____________________________________ Old name: ___________________________ Logical Unit name: __________________________ For dependent LU: Transmission group: ___________________________ LU address: ___________________________ Capability: Primary ____ Secondary ____ Both ____ Object name: ____________________________________ Authorizations: ____________________________________ Old name: ___________________________ 3.8 The SNA Logical Units (Populate) Worksheet The second SNA Logical Units worksheet (Figure 3-7) allows you to specify LUs by specifying the information needed to construct a range of LUs. This parallels the Populate option in the Configuration utility. In addition to the logical unit information discussed for the list-oriented logical units worksheet, you should record the information necessary to specify the range of LUs included in each set. You specify the range by specifying an LU prefix, an LU base number, the number of LUs in the group, and the LU suffix. The prefix, base number, and suffix cannot exceed 8 characters. You must not begin the prefix with a digit and you must use only the following characters: A-Z, 0-9, $, @, or #. For instance, to specify the LUs LS1900X through LS1950X, start by recording the group prefix as LS. Next, record the base number as 1900. Note that you can use hexadecimal digits for the base numbers if you want. Third, record the number of LUs you want (51). Finally, record the group suffix as X. Repeat the process for as many LU sets that you wish to specify using the Populate method. Make additional copies of the worksheet if you need more space. Figure 3-7 The SNA Logical Units Worksheet (Populate Method) Information for logical units: ___________________________ Group prefix: ______________ Base number: ______________ Number in group: ____________ Group suffix: _______________ Capability: Primary ____ Secondary ____ Both ____ Authorization: ____________________________________ Object: ____________________________________ For dependent LU: Transmission group: ___________________________ Base address: ___________________________ Old name PU-name: ___________________________ Information for logical units: ___________________________ Group prefix: ______________ Base number: ______________ Number in group: ____________ Group suffix: _______________ Capability: Primary ____ Secondary ____ Both ____ Authorization: ____________________________________ Object: ____________________________________ For dependent LU: Transmission group: ___________________________ Base address: ___________________________ Old name PU-name: ___________________________ 3.9 The LU Authorizations Worksheet Use the LU Authorizations worksheet (Figure 3-8) to record information about LU Authorizations that control access to Peer Server LUs. You can specify from two to six fields for each authorization. Any field for which you specify a value causes the Peer Server to check the information a user supplies against that value. If no matches occur using all the authorizations you specified for the LU, the Peer Server denies the user access to the LU. Any field that you leave unspecified allows users specifying any value, including no value, to access the LUs protected by this authorization (unless other authorizations prevent access). Note that you can use wildcards in the terminal name and the user name. Record the first LU authorization. If the transport mode is DECnet, the node name is a DECnet node name. If the transport mode is TCP/IP, the node name is an IP node name. If the transport mode is local, the node name is not used. Repeat the process for as many authorizations as you need. Make additional copies of the worksheet if you need more space. Figure 3-8 The LU Authorizations Worksheet Authorization name: ___________________________________ Transport (TCPIP, DECnet, local): ____________ Node name: _____________ User name: _____________________________________ Terminal name: _____________________________________ Password: _____________________________________ Authorization name: ___________________________________ Transport (TCPIP, DECnet, local): ____________ Node name: _____________ User name: _____________________________________ Terminal name: _____________________________________ Password: _____________________________________ Authorization name: ___________________________________ Transport (TCPIP, DECnet, local): ____________ Node name: _____________ User name: _____________________________________ Terminal name: _____________________________________ Password: _____________________________________ Authorization name: ___________________________________ Transport (TCPIP, DECnet, local): ____________ Node name: _____________ User name: _____________________________________ Terminal name: _____________________________________ Password: _____________________________________ 3.10 The Access Names Worksheet Use the Access Names worksheet (Figure 3-9) to record information about the Peer Server access names. Access names allow Peer Server users to request certain Peer Server LUs by a group name rather than individually. Start by recording the names of the LUs you wish users to access when they use this access name. Second, record the name of the partner LU to which they will connect when they use this access name. If you do not specify a partner LU name, the users must specify it when they initiate a session. Next, record the logon mode that the Peer Server will use when this LU requests a session with the remote LU. If you do not specify a logon mode, the users must specify the logon mode when initiating the session. Finally, record any optional user data you wish to provide to the remote LU. Repeat the process for as many access names as you need. Make additional copies of the worksheet if you need more space. Figure 3-9 The Access Names Worksheet Access name: _________________________ LU list: _____________________________________________ _____________________________________________ Partner LU: ______________________________ Logon mode: _____________________________ User data: _____________________________________________ Access name: _________________________ LU list: _____________________________________________ _____________________________________________ Partner LU: ______________________________ Logon mode: _____________________________ User data: _____________________________________________ Access name: _________________________ LU list: _____________________________________________ _____________________________________________ Partner LU: ______________________________ Logon mode: _____________________________ User data: _____________________________________________ 3.11 The Partner LUs Worksheet Use the Partner LUs worksheet (Figure 3-10) to record information about the partner LUs accessible from the Peer Server. Partner LUs for the Peer Server contain the actual SNA network name and network id of a remote LU for a PLU (Primary Logical Unit) connection from a non-SNA network. Record the partner LU destination name and the destination network ID, and the list transmission groups to connect to the remote LU. Repeat the process for as many partner LUs as you need. Make additional copies of the worksheet if you need more space. Figure 3-10 The Partner LUs Worksheet Partner LU: ______________________ Destination name: ___________ Destination network: ___________ Transmission Groups: _____________________________________________ _____________________________________________ Partner LU: ______________________ Destination name: ___________ Destination network: ___________ Transmission Groups: _____________________________________________ _____________________________________________ Partner LU: ______________________ Destination name: ___________ Destination network: ___________ Transmission Groups: _____________________________________________ _____________________________________________ Partner LU: ______________________ Destination name: ___________ Destination network: ___________ Transmission Groups: _____________________________________________ _____________________________________________ (null)(null)(null) 4 Configuring the Peer Server Once you have installed the DEC SNA Peer Server software, you must configure it. This chapter discusses the Peer Server Configuration utility. 4.1 Configuration Activities To configure the Peer Server, follow these steps: 1. Install the Peer Server software (discussed in Chapter 2). 2. Define the Peer Server node in the non-SNA network. (You should have already done this.) 3. Determine the SNA and DLC parameters needed for operating the Peer Server, and configure the host IBM system (discussed in Chapter 3). 4. Configure the Peer Server and create the NCL script file using the Configuration utility (discussed in this chapter). 5. Copy the startup NCL script to the Peer Server system. (This is required only if configuration is done on a different system.) 6. If necessary, modify the Peer Server configuration with NCL. The documents DEC SNA Peer Server Guide to IBM Resource Definition and DEC SNA Peer Server NCL Reference discuss the configuration of the host IBM systems. See the appropriate installation for the workstation on which you are installing the Peer Server. The following sections detail steps 4 through 6. 4.2 Defining the Peer Server Node to the DECnet Network For other nodes in the DECnet network to use the Peer Server, you must define the Peer Server node name and node address on these other nodes. Node definition is outside the scope of this document. 4.3 Configuring the Peer Server Using the Configuration Utility The Peer Server Configuration utility creates an NCL startup script that the Peer Server uses when it starts. This script contains the commands necessary to create the various Peer Server management entities (such as SDLC links and stations, Logical Units, and Access Names). The Configuration utility prompts you for the information necessary to built the NCL script using a simple command-line interface that you can use from any terminal or terminal emulator that generates ANSI escape sequences. The utility saves your responses in an answer file and can read the answer file to obtain default answers. The utility can read, edit, and resave the answer file, so you can run the utility repeatedly until you are satisfied with the results. By default, the Configuration utility writes the NCL script to a file whose name stems from an output answer file name appended with the .ncl extension. If the output answer file name is t21_answer.ans, then the NCL script file name is t21_answer.ncl. See Section 4.3.7, Generating an NCL Script File. You can then copy this file to the Peer Server startup script (/var/sna/t21_init_sna_server.ncl). In this way, you can manage multiple separate configurations using different answer file names and output NCL script files. For any special commands that are needed that the Configuration utility does not prompt for, you have the option of supplying an additional file containing NCL commands that is appended to the NCL generated by the Configuration utility when the the script file is written. 4.3.1 Invoking the Configuration Utility Before you invoke the Configuration utility, you should set your default directory to the location where you wish to keep the answer files, the NCL startup files, and optional NCL files. (The installation procedure creates the directory /var/sna to store the Peer Server startup NCL script; you might choose to keep the associated files there as well.) To invoke the Configuration utility, enter the following command: # /var/sna/t21icu The utility provides command-line recall and editing. Table 4-1 lists editing keys. Note The Configuration utility provides context-sensitive help for all questions. If you enter a question mark (?) in response to any question, the utility will present you with text to explain the current question or syntax. Table 4-1 Peer Server Configuration Utility Editing Keys Editing Key Function (sometimes labeled "Exit") Exit the program Y , , or Recall previous entry (go up the command stack) B or Go down the command stack A Move cursor left " Move cursor right or Go to beginning of line Go to end of line Delete one character to the left Delete one character to the right Delete one word to the left Delete from cursor to beginning of line or Redisplay line , , or Toggle insert/overstrike mode Toggle CRT/hardcopy mode When you invoke the Configuration utility, it displays the following information. # /var/sna/t21icu DEC SNA Peer Server Configuration Procedure V1.1 (c) Digital Equipment Corporation 1993, 1994. All Rights Reserved. Please respond to the questions that follow, providing configuration input specific to your Peer Server installation. After all the questions are answered, an NCL script file will be created. The configuration questions are grouped into several sections, with the option to repeat each section as you go along. Enter ? at any time for help. Enter F10 at any time to quit. Completed sections are saved in the specified answer file, which can be used for default input values the next time the procedure is run. You can terminate a configuration dialog at any time by entering F10 in response to a question. The Configuration utility will save all your answers through the last completed section. You can continue a terminated session later by using the saved partial answer file as the input answer file in a future run of the Configuration utility. Note When editing your input data, either repeating a section or reading and editing the answer file, you can delete an entity by entering a space and pressing Return. 4.3.2 Input and Output Files The Configuration utility prompts you to enter the name of a saved answer file generated during a previous configuration dialog: Input answer file name : in-filename o If you have saved the Configuration utility answer file and wish to use it, enter the file name; or press Return if you do not have an answer file or do not wish to use it. Answer files created with earlier versions of the Configuration utility are automatically updated to this version of the utility. o If you specify an input answer file, the Configuration utility reads the information in the file until it reaches the end of a section then you are prompted as to whether or not you want to repeat the section. If you answer yes, the section gets repeated without reading the input answer file contents until the next section. o If you are using a saved answer file that you created during an incomplete dialog, the Configuration utility generates a warning message and switches back to prompting you for all information when it reaches the end of the saved answer input file. The Configuration utility prompts you to enter the name of an output answer file that will save the answers you provide. The input answer file name you specified becomes the default name for the output answer file name. If you did not specify an input answer file name, t21_init_sna_server.ans is the default output answer file name. To override the default, you must provide a name. Note the following rules for answer file names. o If you accept the default output answer file name that is the same as the input answer file name, the latter one will be overwritten. Earlier versions will be lost. The original contents will be saved in a backup file with the same name as the original input file name appended with a "~". If the input answer file name is t21_answ.ans, the backup name then becomes t21_answ.ans~. o If you specify an output answer file that is different than the input answer file name, and the file already exists, the original file contents will be saved in a backup file with a name derived from the previous rule. Output answer file name : out-filename 4.3.3 Section 1: SNA Access Server Configuration Section 1 of the configuration dialog lets you create SNA Access Server objects. These are used by the Peer Server to create outbound sessions in the TCP/IP or DECnet network initiated on receipt of a BIND request from the IBM network. You can use the object names in Section 3 when creating Logical Units. If you are not using outbound sessions, you can skip this section by pressing Return at the Object Name prompt. For each object you create, you will be asked for the type of network transport to use to connect to the remote object. You can select TCPIP, DECnet, or LOCAL. For objects residing on TCP/IP nodes, you will be asked for the Internet Nodename and either a Port number or a TCP Service name. If you enter a Port number the Service Name prompt is omitted (since you may set one field or the other but not both). For objects residing on DECnet nodes, you will be asked for the DECnet node name and either a DECnet object number or a Task Name. If you enter an object number the Task Name prompt is omitted (since you may set one field or the other but not both). For objects residing on the local system (the one the Peer Server is running on), you can create TCP/IP or DECnet connections using these configuration steps, or you can use the local transport. In this case, you can specify the command to be issued and the local user name to run the command under. The command specifies the full path of a shell script or program to run. Section 1 - SNA Access Server Configuration. -------------------------------------------- The following questions gather Object information for zero or more Objects. Enter the object name; it must be a name from 1 to 32 characters long. Pressing Return with no object name indicates that no more object names follow. Object name [] : object-name The Configuration utility prompts you to enter the transport protocol used to reach the object. Enter tcpip, decnet, or local; the default is tcpip. Transport [TCPIP] : transport The Configuration utility prompts you to enter the name of the Internet Node to which to connect. Enter an internet host name; the default is none. Internet Node [] : internet-node The Configuration utility prompts you to enter the TCP port number on the remote node. Enter an integer from 0 to 32767; the default is 0. This characteristic should not be set when the service name characteristic is set. Port Number [] : nnnnn The Configuration utility prompts you to enter the name of the TCP service on the remote node. The default is none. This characteristic should not be set when the port characteristic is set. Service Name [] : service-name The Configuration utility repeats this series of prompts for another object. When you have defined all the objects, you can continue to the next section by pressing Return. Object name [] : object-name The utility asks if you wish to repeat the section. Press Return to continue: Do you wish to repeat Section 1, SNA Access Server Configuration [N] ? Example 4-1 uses the Configuration utility to create one object to connect to port 2534 on Internet node gratis.eng.bigcorp.com and another to connect to DECnet object 231 on DECnet node .corp.mynode. Example 4-1 Configuration Example (Section 1) Section 1 - SNA Access Server Configuration. -------------------------------------------- The following questions gather Object information for zero or more Objects. Object name [] : cpicprog Transport [TCPIP] : tcpip Internet Node [] : gratis.eng.bigcorp.com Port Name [] : 2534 Object name [] : dspiprog Transport [TCPIP] : DECnet Node [] : .corp.mynode Object number [0] : 231 Object name [] : Do you wish to repeat Section 1, SNA Access Server Configuration [N] no 4.3.4 Section 2: Data Link Layer Configuration Section 2 of the configuration dialog lets you select the DLC type you will configure. The DLC entities available for configuration are SDLC, QLLC, and LLC2. The Configuration utility prompts you to start a DLC entity configuration. Enter yes, no or skip. If you have not already configured any link, the default is yes. Do you wish to configure dlc-type1 [YES] ? 1. SDLC, QLLC or LLC2 Note Enter YES if you want to configure the data link type currently displayed by the Configuration utility. Enter SKIP if you want to maintain an existing configuration of this data link type, and continue on to the next DLC type or next section. Enter NO if you want to omit this configuration, and at the same time void an existing configuration of this data link type. You will receive the following warning if you enter NO and have a data link configured: WARNING: Your Data Link is already configured; answering NO will void the configuration. The following subsections step you through the Configuration utility for the Data Link Control (DLC) entities. 4.3.4.1 Section 2.1: SDLC Configuration Section 2.1 of the configuration dialog lets you configure SDLC links and stations that connect the Peer Server to the IBM SNA environment. For each SDLC link you configure, you also configure information for one or more (if configured as multipoint) remote SDLC stations on the link. Press Return at the Link Name prompt when you have completed the SDLC Link configuration section. Section 2.1 - SDLC Configuration. ------------------------------- This section gathers information for one or more SDLC links. The Configuration utility prompts you to enter a link name. Enter the name of the SDLC link to configure. Links are named with character strings of 1 to 32 characters; SDLC-0 is the default name of the first link. LINK name [SDLC-0] : link-name The Configuration utility prompts you to enter a modem connect line name. Enter the Modem Connect Line that this SDLC link will use to communicate with the remote system. The Peer Server has physical lines named "Modem Connect Line Line-n," where n is determined by the number and type of synchronous devices available on the system. Enter just the "line-n" part of the name. The default is LINE-0. Modem Connect Line name [LINE-0] : line-name The Configuration utility prompts you to enter the configuration in which this link is to operate. If this link is the only device on the line being used, you can use the default configuration (PointToPoint). If this link is sharing the communication line with other SDLC devices, specify multipoint. You can enter p or m. If "m" is entered for multipoint links, you will be prompted for more than one station name. Configuration [PointToPoint] : configuration The Configuration utility prompts you to enter the capability of the Station subentities for this Link entity. SDLC stations on the link can be either Primary or Secondary stations. On links that negotiate roles, such as NCP attached lines coded with XID=YES or AS/400 controllers, you can use the default (negotiable). For multipoint links, the capability is set to secondary, and you are not prompted for this information. Capability [NEGOTIABLE] : capability The Configuration utility prompts you to enter the maximum receive frame size that can be received by this link. If you are using the built-in synchronous adapter on the Alpha AXP system instead of a DEC WANcontroller 720 (DSYT1), this value cannot exceed 1000 bytes due to hardware limitations. If you are using a DEC WANcontroller 720 line, this value cannot exceed 4000 bytes. Enter a value from 1 to 32765; the default is 1000. Receive frame size [1000] : nnnnn The Configuration utility prompts you to enter the number of times an SDLC frame is retransmitted before the Peer Server declares a fatal error has occurred and resets the link. Enter a value from 0 to128; the default is 15. A value of zero implies unlimited retries. The default value should work for most configurations. Retry maximum [15] : nnn After configuring the Link parameters, you can configure the parameters for a single station per link. The Configuration utility prompts you to enter the station name. Stations are named with character strings of 1 to 32 characters; STN-0 is the default for the first station. STATION name [STN-0] : station-name The Configuration utility prompts you to enter the station address for this station. If the SDLC link is defined as secondary, or it is defined as negotiable and adopts a secondary role at run time, then this parameter represents the station address that will be used by the Peer Server. If the SDLC link is defined as primary, or if it is defined as negotiable and adopts a primary role at run time, then this parameter is not used and the address of the secondary station is determined at run time. Enter the address in the form of two hexadecimal characters from 01 to FE; the default is 40. Station address [40] : hh Enter the group address for this station. This prompt is issued only if the SDLC Link is configured as multipoint. Enter the address in the form of two hexadecimal characters from 00 to FE; the default is 00, which is interpreted as no group address. Group address [00] : hh The Configuration utility prompts you to enter the station's transfer mode. Enter the link level transmit/receive capabilities of the station. TWA (Two-Way Alternate) corresponds to half-duplex communication; TWS (Two-Way Simultaneous) corresponds to full-duplex communication. On links that negotiate roles, such as NCP attached lines coded with XID=YES or AS/400 controllers, the actual type of connection established depends on the capabilities of the two link stations. TWS will only be used if both stations support it. If negotiation is not performed then the value of this parameter must match the configuration of the remote system. A station cannot operate two-way simultaneous over a physical half-duplex line. Transfer mode [TWA] : transfer-mode The Configuration utility prompts you to enter the default modulus to use. Normal modulus uses a modulus-8 numbering system for frames, and thus there can only be a maximum of seven frames outstanding at any time. Extended modulus uses modulus-128 numbering, which allows for up to 127 frames to be outstanding. On links that negotiate roles, such as NCP attached lines coded with XID=YES or AS/400 controllers, the modulus used is determined at run time from the configured window sizes (normal is used unless both systems have window sizes greater than seven). For links that do not perform negotiation, the value of this parameter must match the configuration of the remote system. Modulo [NORMAL] : mode The Configuration utility prompts you to enter the window size to set the number of frames the station can receive before sending an acknowledgement response. The value of this parameter is used to determine the modulus used on links that negotiate roles. Enter a value from 1 to 127; the default is 7. A station with modulo Normal supports the range 1-7; a station with modulo Extended supports the range 1-127. Unless you have a line with a high error rate, you should use the default value. Window size [7] : nnn The Configuration utility prompts you to enter the station's inactivity timer value. This is the number of seconds the Peer Server will wait for a message from the remote system before considering the line to have failed. This timeout is used when the Peer Server is operating as a secondary link station, and reflects the maximum amount of time expected between polls from the primary station. If the timer expires, then the link is disconnected. Enter a value from 0 to 7200 seconds; the default is 30 seconds. A value of zero implies that the station will not time out due to inactivity on the line. Inactivity timer [30] : nnnn The Configuration utility prompts you to enter the maximum size of the frame that the Station can send. This value can differ from Station to Station on the same Link if the Link is defined as multipoint with multiple secondary Stations. Enter a value from 1 to 32765; the default is 1000. Send frame size [1000]: nnnnn The Configuration utility repeats this series of prompts for another link. When you have defined all the links, you can continue to the next section by pressing Return: LINK name [] : The utility asks if you wish to repeat the section. If you want to create a different Link/Station configuration, answer yes; if not, press Return to continue: Do you wish to repeat Section 2.1, SDLC Configuration [N] ? Example 4-2 uses the Configuration utility to configure an SDLC link and station operating over Modem Connect Line line-0. It uses a receive frame size of 265 bytes. Example 4-2 SDLC Configuration Example (Section 2.1) LINK name [SDLC-0] : Modem Connect Line name [LINE-0] : Configuration [PointToPoint] : MultiPoint Receive frame size [1000] : 265 Retry maximum [15] : STATION name [STN-0] : Station address [40] : Group address [00] : Transfer mode [TWA] : Modulo [NORMAL] : Window size [7] : Inactivity timer [30] : Send frame size [1000] : 4.3.4.2 Section 2.2: QLLC Configuration Section 2.2 of the configuration dialog lets you configure QLLC links and stations that connect the Peer Server to the IBM SNA environment. For each QLLC link you configure, you also configure information for one remote QLLC station on the link. Press Return at the Link Name prompt when you have completed the QLLC Link configuration section. Section 2.2 - QLLC Configuration. ------------------------------- This section gathers information for a QLLC link. The Configuration utility prompts you to enter a link name. Enter the name of the QLLC link to configure. Links are named with character strings of 1 to 32 characters; QLLC-0 is the default name of the first link. LINK name [QLLC-0] : link-name The Configuration utility prompts you to enter the filter name to be used for both QLLC incoming and outgoing connections. The name must also match an X25 Access Filter that exists in the node's X.25 configuration. The default name is FILTER_QLLC. Filter name [FILTER_QLLC] : filter-name The Configuration utility prompts you to enter the template name to be used for QLLC outgoing connections. The name must match an X25 Access Template that exists in the node's X.25 configuration. If the name does not match, each outgoing connection attempt will fail. The default name is TEMPLATE_QLLC. Template name [TEMPLATE_QLLC] : template-name The Configuration utility prompts you to enter the DTE Class name. The name must match an X25 Access DTE Class that exists in the node's X.25 configuration. The default is CLASS_QLLC. DTE Class [CLASS_QLLC] : class-name After configuring the Link parameters, the utility prompts you to enter information for one or more Stations that will operate over the Link. Stations are named with character strings of 1 to 32 characters; STN-0 is the default for the first station. Station name [STN-0] : station-name The Configuration utility prompts you to enter the type of connections that will occur over this Station. The values are outgoing, incoming, and both. You should enter incoming, if you will have only IBM initiated DLC connections. You should enter outgoing, If you will have only connections initiated from the Peer Server. You should enter both, if you will have outgoing and incoming connections, or are unsure of the type of connection. The default is both. Usage Type [BOTH] : usage-type The Configuration utility prompts you to enter the maximum number of retries to attempt before disconnecting the connection. Enter a value from 0 to 255; the default is 4. A value of zero implies unlimited retries. The default value should work for most configurations. Retry Maximum [4] : nnn The Configuration utility prompts you to enter the time in seconds to wait between retries. Enter a value from 1 to 600; the default is 10. Retry Timeout [10] : nnn The Configuration utility prompts you to enter the capability of the Station subentities for this Link entity. QLLC stations on the link can be either Primary or Secondary stations. On links that negotiate roles, such as NCP attached lines coded with XID=YES or AS/400 controllers, you can use the default (negotiable). Capability [NEGOTIABLE] : capability The Configuration utility prompts you to enter the Remote DTE Address for this Station. Enter the Remote DTE Address that corresponds to the remote station that this Station will communicate with. For a Peer Server initiated connection, this will be the address that the X.25 call is directed to. For an incoming connection, if the Usage Type of the Station is set to Incoming, then the caller's X.25 Address will be matched against this value and if it does not match, the connection will not be accepted. If you are using a direct X.25 connection, no PSDN, then this parameter is optional. You may press Return or enter a "0". Remote DTE Address [] : dd The Configuration utility prompts you to enter the Maximum BTU (Basic Transmission Unit) Size for this Station. Enter the size that SNA messages should be segmented into before being sent to the X.25 network. (The X.25 network may further segment packets based on the level 2 profile information being used.) Enter a value from 128 to 512; the default is 512. Maximum BTU Size [512] : nnn The utility asks if you wish to repeat the section. If you want to create a different Link/Station configuration, answer yes; if not, press Return to continue: Do you wish to repeat Section 2.2, QLLC Configuration [N] ? Example 4-3 uses the Configuration utility to configure a QLLC link and station. Example 4-3 QLLC Configuration Example (Section 2.2) LINK name [QLLC_0] : Filter name [FILTER_QLLC] : Template name[TEMPLATE_QLLC] : DTE Class [CLASS_QLLC] : STATION name [STN-0] : Usage Type [BOTH] : Retry Maximum [4] : Retry Timeout [10] : Capability [BOTH] : Remote DTE Address [] : 12345 Maximum BTU Size [512] : 4.3.4.3 Section 2.3: LLC2 Configuration Section 2.3 of the configuration dialog lets you configure LLC2 SAPs and links that connect the Peer Server to the SNA environment by LAN. Press Return at the SAP Name prompt when you have completed the LLC2 Link configuration section. Section 2.3 - LLC2 Configuration. ------------------------------- This section gathers information for LLC2 links. The Configuration utility prompts you to enter the SAP (service access point) name. Enter the name of the LLC2 SAP to configure. SAP are named with character strings of 1 to 32 characters. SAP name [SNA-0] : sap-name The Configuration utility prompts you to enter the LAN station type. The supported station types are Token Ring and Ethernet. The default type is Token Ring. LAN Station type [Token Ring] : station-type The Configuration utility prompts you to enter the LAN station to be used by the SAP. LAN Station name [TRN-0] : station-name The Configuration utility prompts you to enter the local LSAP (link service access point) address. The lowest significant bit of the address must be clear, and the address must be unique. Enter the address in the form of two hexadecimal characters; the default is 04. Local LSAP Address [04] : hh The Configuration utility prompts you to enter the SAP Link name. Enter the name of the SAP Link with character strings of 1 to 32 characters. LINK name [LINK-0] : link-name The Configuration utility prompts you to enter the Maximum Data Size that can be received by this Link. Enter a value from 1 to 65531; the default is 1028. Maximum Data Size [1028] : nnnnn The Configuration utility prompts you to enter the destination LSAP (link service access point) address to be used by the link. The lowest significant bit of the address must be clear, and the address must be unique. Enter the address in the form of two hexadecimal characters; the default is 04. Remote LSAP Address [04] : hh The Configuration utility prompts you to enter the destination MAC (medium access control) Address to be used by the Link. Enter the value of a valid LAN address. It is important for the remote MAC address to be specified in canonical format, which is derived by reversing each bit in a byte of the remote MAC address. For example, if the remote MAC address is 40-00-2D-EC-DE-C0, the canonical form of it is 02-00-B4-37-7B-03. Remote MAC Address (xx-xx-xx-xx-xx-xx) [ ] : 08-00-cb-17-14-3c The utility asks if you wish to repeat the section. If you want to create a different SAP/Link configuration, answer yes; if not, press Return to continue: Example 4-4 uses the Configuration utility to configure an LLC2 SAP and Link. Example 4-4 LLC2 Configuration Example (Section 2.3) SAP name [sna-0] : LAN Station type [Token Ring] : LAN Station name [TRN-0] : Local LSAP Address [04] : LINK name [LINK-0] : Maximum Data Size [1028] : Remote LSAP Address [04] : Remote MAC Address (xx-xx-xx-xx-xx-xx)[ ]: 08-00-cb-17-14-3c The LAN module entity (Token Ring or Ethernet), and the station subentity are necessary for LLC2 operation. You will need to configure the creation of these entities while running the Configuration utility, if you have not already done so. You can omit this step if the LAN entity is already configured for use with DECnet or X.25. Before you complete this section, you will be prompted to configure the specified LAN Station entity. If you answer 'yes,' the Configuration utility detects which LAN Station has been listed (Token Ring or Ethernet), and issues the appropriate set of prompts. The Configuration utility displays the LAN Station name used by the SAP. This name matches the one listed in the beginning of Section 2.3 and is in agreement with the LAN Station type (Token Ring or Ethernet). Configuring LAN station: station-name The Configuration utility prompts you to enter a communication port name. If you specified Token Ring as the LAN Station type, the Port name default is tra0, if the LAN Station type specified is Ethernet (CSMA-CD), the Port name default is ln0. Press to accept the default value or enter a name according to the syntax 'ddn,' where 'dd' represents an adapter name, and 'n' represents the number. Communication port name [ ] : port-name If you specified Token Ring as the LAN Station entity, the Configuration utility prompts you to enter a Token Ring speed. You may choose 4 or 16 Megabits per second as the speed. The default value is 16. Token Ring speed [16] : nn The utility asks if you wish to repeat the section. Press to continue: Do you wish to repeat Section 2.3, LLC2 Configuration [N] ? 4.3.5 Section 3: SNA Logical Unit Services Configuration Section 3 of the configuration dialog lets you create the SNA LU Services entities in the Peer Server. These include Authorizations, Logical Units (LUs), Access Names, and Partner LUs. 4.3.5.1 Section 3.1: Authorization Information Section 3.1 of the configuration dialog collects authorization information. This section lets you create Authorization subentities that can be used to secure access to Logical Units (LUs) defined in the Peer Server to specific users or groups of users. The parameters that make up an Authorization are the connecting user's node name (either DECnet or TCP/IP), the type of network the connection arrives on, the remote user's name, the terminal being used for the connection, and a password. Any or all of this information can be defined on the Authorization. Any information that is defined must match successfully with an incoming user's connection request before the Peer Server grants access to the protected LU. Enter Authorization names and their attributes as described in the following paragraphs. Press Return at the Authorization name prompt to complete the section. Section 3 - SNA LU Services Configuration. ------------------------------------------ Section 3.1 - Authorization Configuration. ------------------------------------------ The following questions gather Authorization information for zero or more Authorizations. The Configuration utility prompts you to enter the authorization name. This is the name you will specify when defining the authorization list for an LU. Enter a name of 1 to 255 characters; the default is none. Pressing Return with no authorization name indicates that no more authorizations follow. Authorization name [] : authorization-name The Configuration utility prompts you to enter the transport protocol used to reach the LU. The response local refers to the transport used to connect applications running on the same system that the Peer Server is running on. If you specify decnet, the Node name field is used to match against an incoming connection. If you specify tcpip, the Internet node field is used instead. Transport [] : transport If you specified TCP/IP or DECnet transport in the previous question, the Configuration utility prompts you to enter the name of the DECnet node or Internet node to which to connect. The name is matched with simple text matching to that used in the client connection. Wildcarded names are allowed. Since the Peer Server is a DECnet/OSI end system, most DECnet nodes are specified with namespace names. Ensure that the name you enter is a full name and not just a simple synonym; otherwise, it might not match the string comparison. Enter a node name; the default is none. This example shows the "Internet node" prompt: Internet node [] : internet-node The Configuration utility prompts you to enter the name of an authorized user. Specify the user name that the client must be logged in as on the remote node for access to be granted. Wildcarded names are allowed. Enter the user name; the default is none. If you leave this field blank, no user name checking is performed during authorization checking. User [] : user-name The Configuration utility prompts you to enter the terminal identification of this authorized user. Specify the terminal that the client must use for access to be granted; the default is none. For systems that provide terminal names that map to physical terminals, such as LAT terminal servers or hard-wired lines, you can use this mechanism to restrict access to specific physical terminals. Dynamic terminal names, such as ttypx style names under OSF/1 or RTAnn under OpenVMS, provide no usable means of physical security; for those operating systems you should omit this field. Terminal [] : terminal-id The Configuration utility prompts you to enter the password of this authorized user. Enter a password that the user must supply on the connection to be allowed access to the restricted LU. For those applications that allow specification of the Authorization password, such as 3270 terminal emulators, this provides an additional validation of the client. Enter the password; the default is none. If you leave this field blank, it is not checked against the user's connection parameters. Password [] : password The Configuration utility repeats this series of prompts for another authorization name. When you have defined all the authorization names, you can continue to the next section by pressing Return: Authorization name [] : The utility asks if you wish to repeat the section. Press Return to continue: Do you wish to repeat Section 3.1, Authorization Configuration[N]? Example 4-5 uses the Configuration utility to constrain a successful connection to user fred on node fred.abc.xyz.com making a client connection using TCP/IP and providing the password hillary. Unless all of these conditions match, access is denied and an event is generated to warn of the failure. Note that the internet node, like the DECnet node, is a simple text match. If the internet node is unknown to the Peer Server node, and the Domain Name Service is not able to translate the name, a dotted name form of the node name (for example, a.b.c.d) may be presented for matching. The Peer Server makes no attempt to match a dotted name against a text node name. Example 4-5 Configuration of an Authorization (Section 3.1) Authorization name [] : fred_only Transport [] : TCPIP Internet node [] : fred.abc.xyz.com User [] : fred Terminal [] : Password [] : hillary 4.3.5.2 Section 3.2: Logical Unit Configuration Information This section of the configuration dialog lets you create logical units (LUs). LUs provide clients with access to the SNA network. Depending on the type of IBM environment you are connecting to and the type of SNA client applications you are running, you may need to configure LUs to be capable of dependent sessions or independent sessions. For most of the Digital SNA client applications available today, you will need to configure dependent LUs. You do this by specifying as part of the LU definition the LU address (LOCADDR) and the transmission group name that connects to the IBM system. You can also configure independent LUs. These LUs can be used by client applications that are not dependent on the IBM subarea network, such as those connecting to AS/400 systems or those participating in peer-to-peer applications. You can create LUs individually or in groups using the Populate option. When creating a range of LUs using Populate, the LU name is created using a prefix you supply, a few characters that contain the LU number, and an optional suffix. If you are configuring a dependent LU, the dependent LU address is automatically generated using the base address you supply. You then define the LU capability, an optional outbound object to connect to, Authorizations to secure the LU, and an "old name" prefix. You need only supply the PU-name part of the old name when populating LUs because the session number is again generated using the base address you provide. When creating a single LU using the List option, you are asked most of the same questions as when using Populate. If you are defining a dependent LU, you specify the dependent LU address and also the complete old name, not just the PU-name part. Section 3.2 - LU Configuration. ------------------------------- The following questions gather LU information for zero or more LUs. The Configuration utility prompts you to begin defining information for an LU. Create/Quit [Quit] : create If you want to create LUs, enter create, or quit to skip to the next section.; the default is quit. (You can enter c or q.) You can define LUs using the Populate option or individually using the List option: Populate/List/Quit [Populate] : Enter populate if you wish to define a set of LUs using the Populate feature. Enter list if you wish to define a set of LUs by specifying them individually. Enter quit if you have no more LUs to define. The default is populate. (You can enter p, l, or q.) If you choose to use the Populate option, the Configuration utility prompts you as follows: o The Configuration utility prompts you to enter the character string to be used as a prefix for the LUs you are defining: LU populate, name prefix [] : prefix Enter a value of 1 to 7 characters; there is no default. The value must begin with a letter and contain only the characters A-Z, @, $, or #. The length of the resulting names (prefix + number + suffix) cannot exceed 8 characters. o The Configuration utility prompts you to enter the starting number for the series of LUs. If you enter a decimal base number, then the LU name created also uses decimal numbering; if you enter a hexadecimal base number, then hexadecimal numbering is used in the LU name. LU populate, base number [1] : nnnnnnn Enter a value from 0 to 9999999 or from %X0 to %XFFFFFFF; the default is 1. Preceding the number with "%X", "X", or "0X" indicates that the number is hexadecimal. This determines whether the sequence of numbers used for the LU names will be decimal or hexadecimal. The sum of this number plus the number of LUs to populate, minus 1, cannot exceed 9,999,999 or %XFFFFFFF. The length of the resulting names (prefix + number + suffix) cannot exceed 8 characters. o The Configuration utility prompts you to enter the number of LUs you wish in this set: LU populate, number of LUs [1] : nnnn Enter a value from 1 to 1024. The sum of the starting number plus this number, minus 1, cannot exceed 9,999,999. The length of the resulting names (prefix + number + suffix) cannot exceed 8 characters. o The Configuration utility prompts you to enter the character string to be used as a suffix for the LUs you are defining: LU populate, name suffix [] : name-suffix Enter a value of 0 to 6 characters; the default is none. This string must contain only the characters A - Z, 0 - 9, @, $, or #. The length of the resulting names (prefix + number + suffix) cannot exceed 8 characters. If you are configuring LUs as dependent (that is, connected to an IBM front end processor), enter the name of the CP Services Transmission Group that is connected to the front-end processor. If you are not defining dependent LUs, press Return to leave the entry blank. Dependent LU transmission group (TG) [] : group-name The Configuration utility prompts you to enter the capability of the LU to act as a primary LU, a secondary LU, or both. Enter primary, secondary, or both; the default is secondary. (You can enter p, s, or b.) The LU capability determines whether the LU can be used for Secondary LU or Primary LU connections. If the client applications that use this LU require the ability to send an SNA session start message (BIND), then configure the LU as Primary. If the applications receive BIND messages from the IBM system, as is the case for most existing DEC SNA client applications, you can configure the LU as either Secondary or Both. Capability [Secondary] : capability If you plan to use host-initiated sessions through this LU, you can configure an Access Server object on the LU that will be used when an unsolicited BIND request is received on the LU. If you are not using this, then leave the object name blank. Object name [] : object-name The Configuration utility prompts you to enter the authorization list for the LUs. If you want to restrict access to the LU to specific clients, you can add a single Authorization object or a list of Authorization objects to the LU. You can enter more than one authorization entity name by separating the names with commas. The Authorizations you list must have previously been defined in Section 3.1; otherwise, a warning message appears. Press Return to indicate that any user can access the LU. Authorizations for this LU [] : auth[, auth...] The Configuration utility prompts you to enter an alternative name for this LU. Enter a value from 0 to 6 characters long; the default is none. Old names are of the form of pu-name.session-number pairs. An "old name" is an alternate name for a Peer Server LU. An old name characteristic must be defined for the Peer Server only when the application does not support using an access name for LU specification. Previous DECnet SNA Gateway products named their LUs using a PU name and a local address on the PU, and access routines (for example, 3270 Terminal Emulator) specified a PU name and a session number when connecting. To allow the older applications to continue to work, the Old Name can be used to give a Peer Server LU a name similar to those used for previous Gateways. This name is made up of a PU specifier and a session number. When populating LUs, you need to specify the PU specifier only; the session number is automatically generated by the Configuration utility using the Base Address you specify. A client terminal emulator can stipulate a specific LU to apply by using the PU-name and session number command line arguments. When creating a single LU, you can supply the whole Old Name. Old name [] : pu-name.sess-no Example 4-6 uses the Populate option to configure a group of 128 LUs, named XLU01 to XLU80, with the LU numbering in hexadecimal. Example 4-6 Configuration Using Populate Option (Section 3.2) Populate/List/Quit [Populate] : populate LU populate, name prefix [] : XLU LU populate, base number [1] : %x1 LU populate, number of LUs [1] : 128 LU populate, name suffix [] : Dependent LU transmission group (TG) [] : TG-2 Capability [Secondary] : both Object name [] : Authorizations for this LU [] : Old name [] : SNA-1 To configure an individual LU, or a list of LUs in a series, use the List option. In this mode, you name the LU explicitly that you want to create. If you are configuring the LU to be dependent, you enter the specific Dependent LU address you want to use instead of having it generated. Populate/List/Quit [Populate] : list If you choose to use the List option, the Configuration utility prompts you to enter a single LU name or a list of LU names. Enter one or more LU names. LU names must contain only the characters A - Z, 0 - 9, @, $, or #. They must not begin with a number, and they must not exceed eight characters. Use commas or spaces to separate names. Press Return with no LU name to indicate that no more LUs follow. LU names [] : lu-name If you are configuring LUs as dependent (that is, connected to an IBM front-end processor), enter the name of the CP Services Transmission Group that is connected to the front-end processor. If you are not defining dependent LUs, press Return to leave the entry blank. Dependent LU transmission group (TG) [] : group-name If the LU is a dependent LU, you must enter the Dependent LU address. This corresponds to the LOCADDR parameter on the IBM NCP definitions for the PU being used. Valid addresses are in the range of 1-255 decimal. Entering 0 indicates that the LU is not dependent. If you previously entered a blank name for the Dependent LU Transmission Group, this prompt is skipped. Dependent LU address [] : lu-address Capability [Secondary] : capability Object name [] : object-name Authorizations for this LU [] : auth[, auth...] As previously noted, the Old Name you enter should be made up of both the PU specifier and the session address. When configuring a dependent LU, the session address used in the Old Name should match the Dependent LU address. Old name [] : pu-name.sess-no Example 4-7 uses the List option to configure an LU named T00FE. Example 4-7 Configuration Using List Option (Section 3.2) Populate/List/Quit [Populate] : list LU names [] : T00FE Dependent LU transmission group (TG) [] : TG-1 Dependent LU address [] : 254 Capability [Secondary] : both Object name [] : Authorizations for this LU [] : fred_only Old name [] : SNA-1.254 The Configuration utility repeats this series of prompts to further populate or list LUs. When you have defined all the LUs, you can continue to the next section by pressing Return. The utility asks if you wish to repeat the section; Press Return to continue: Populate/List/Quit [List] : quit Do you wish to repeat Section 3.2, LU Configuration [N] ? 4.3.5.3 Section 3.3: Access Name Configuration Information Section 3.3 of the configuration dialog collects Access Name configuration information. Access Name objects are referenced by client applications to provide such information as which Peer Server LU to use, what IBM application name to connect to, and what Logon Mode name to use. By creating Access Names with this information in them, details about how to connect to a specific IBM application can be kept in a single place and modified later if needed without the clients needing to change. An access name is a simple text name, 1 to 16 characters long. When naming new Access Names, remember that some older DECnet SNA applications allow access names of only up to 8 characters. Section 3.3 - Access Name Configuration. ---------------------------------------- The following questions gather Access Name information for zero or more Access Names. The Configuration utility prompts you to enter an access name. This is the name that client applications specify when connecting to the service named by the parameters in the access name. Enter a name of 1 to 16 characters; the default is none. Press Return to complete the Access Name configuration section. Access name [] : access-name The Configuration utility prompts you to enter a list of SNA LU Services entities accessible using this Access Name entity. Enter a list of LU names separated by commas; the default is none. You can use wildcards or name the entities explicitly. If no LUs are named in the list, then any Peer Server LU will be used when processing an incoming client connection that specifies this access name. LU list [] : lu-name[, lu-name...] The Configuration utility prompts you to enter the optional name of the Partner LU entity that defines the remote LU. Enter an SNA network name; the default is none. The Partner LU parameter definition depends on the type of client connection that is being processed. For Secondary LU connections, the Partner LU specifies the name of the IBM application (the VTAM APPLID) to which the Peer Server should connect. This value should be available from your IBM system administrator. For Primary LU connections (those where the Client application will send a BIND request to a secondary IBM resource), the Partner LU names an entry in the Peer Server Partner LU list. Partner LU [] : partner-lu The Configuration utility prompts you to enter the optional logon mode that you want the Server to use for this access name. Enter a logon mode; the default is none. The Logon Mode parameter specifies an entry in the IBM Logon Mode Table that should be used when the IBM system is generating a BIND request. This value should be available from your IBM system administrator. Logon mode [] : logon-mode The Configuration utility prompts you to enter an optional user-level data string that you want to send the remote LU. Enter a data string of zero to 255 characters, surrounded by quotation marks; the default is none. The data is assumed to be ASCII text and translated to EDCDIC before being sent to the remote LU. User data [] : "user-data-string" Example 4-8 uses the Configuration utility to configure two Access Name objects. In the first, an access name of tso is created that will use any LU in the Peer Server and connect to the IBM application called tsol and specify a logon mode name of mcauto on the session initiation request. In the second, since no IBM application name is specified, this entry is usable only if the client wishes to use a terminal emulator and gain access to the SSCP-LU session screen, otherwise known as the USS screen. Example 4-8 Configuration of Access Names (Section 3.3) Access name [] : tso LU list [] : * Partner LU [] : tsol Logon mode [] : mcauto User data [] : Access name [] : uss LU list [] : xlu* Partner LU [] : Logon mode [] : User data [] : The Configuration utility repeats this series of prompts for another Access Name object. When you have defined all the access names, you can continue to the next section by pressing Return. The utility asks if you wish to repeat the section. Press Return to continue: Access name [] : Do you wish to repeat Section 3.3, Access Name Configuration [N] ? 4.3.5.4 Section 3.4: Partner LU Configuration Information Section 3.4 of the configuration dialog lets you create Partner LU definitions for clients wishing to run Primary LU sessions. If you do not require this ability, skip this section by pressing Return at the Partner LU name prompt. Section 3.4 - Partner LU Configuration. --------------------------------------- The following questions gather Partner LU information for zero or more Partner LUs. The Configuration utility prompts you to enter the name of the default transmission group to use when no partner LU entity is found or if a partner LU with no transmission group defined is found. Enter the name of a transmission group entity that will be defined in Section 4. Default transmission group (TG) name []: tg-name The Configuration utility prompts you to enter a partner LU name. This is the name that a client specifies directly or by using an access name when it wants to set up a Primary LU session with the partner named in this entry. Enter an SNA network name; the default is none. The name must conform to IBM LU naming rules: up to 8 characters long, containing only the characters A-Z, 0-9, $, #, and @, and starting with an alphabetic character. Press Return with no partner LU name to indicate that no more partner LUs follow. Partner LU name [] : partner-lu The Configuration utility prompts you to enter the name of the IBM application or resource to which it is to be connected. Enter an SNA network name; the default is none. Destination name [] : remote-lu The Configuration utility prompts you to enter the name of the network where the Destination Name entered in response to the previous question exists. Enter an SNA network name; the default is none. Destination network [] : network-id The Configuration utility prompts you to enter the transmission group name that should be used when establishing a connection to the remote LU defined previously. You can enter a single name or a list of names if the Peer Server is configured with multiple transmission groups. The default is none. The Peer Server will attempt to contact the partner LU using the first active transmission group in the list. Transmission group list [] : trans-group[, trans-group...] Example 4-9 uses the Configuration utility to configure a Partner LU that will establish communication with the LU named usxxx101.cics17b when a client application uses the Partner LU named cicsplu. Example 4-9 Configuration of a Partner LU (Section 3.4) Partner LU name [] : cicsplu Destination name [] : cics17b Destination network [] : usxxx101 Transmission group list [] : tg-1 The Configuration utility repeats this series of prompts for another partner LU name. When you have defined all the partner LU names, you can continue to the next section by pressing Return. The utility asks if you wish to repeat the section, and then asks if you wish to repeat Section 3.0. Press Return to continue: Partner LU name [] : Do you wish to repeat Section 3.4, Partner LU Configuration [N] ? Do you wish to repeat Section 3, SNA LU Services Configuration[N]? 4.3.6 Section 4: SNA CP Services Configuration Section 4 of the configuration dialog lets you establish and customize SNA CP Services, the SNA Peer Server module responsible for managing the SNA T2.1 node and its resources. SNA CP Services is a single module-level entity instance with one or more subordinate Transmission Group (TG) subentities. A single TG corresponds to an underlying datalink definition, and represents the pairing of a local and remote datalink station to comprise a connection over which sessions flow. In this section you are required to enter one set of parameters for the singular CP Services definition, and then a set of parameters for each TG you wish to define. For DLC connections, you will need a TG defined for each physical link over which sessions are to flow, which is generally one TG for each connection between the SNA Peer Server and each T2.1 peer node. The CP Services-specific parameters consist of the Peer Server's Network ID (NETID), its CP Name, and the maximum number of concurrently active TGs to allow. The Network ID and CP Name are conventional SNA names, each limited to eight characters. The Network ID is common to other T2.1 nodes in the same APPN network, and should therefore be obtained from your SNA network administrator. The CP Name is unique to this installation of the Peer Server, but it too should be coordinated with your overall SNA network administrator since it will be known to other machines as well. The number of maximum active transmission groups serves to limit resource utilization on Peer Servers with multiple, dynamic TGs. This number includes the Intranode TG, so, for example, on a Peer Server with one standard (internode) TG that utilizes the intranode TG as well, a value of 2 (or greater) would be used to allow concurrent use of both TGs. Section 4 - SNA CP Services Configuration. ------------------------------------------ The Configuration utility prompts you to enter the network identifier (NETID) of the T2.1 node. Enter a value; there is no default. The name must conform to SNA naming conventions. You should consult with the SNA administrator about this name. Network ID [] : net-id The Configuration utility prompts you to enter the designated CP name of the T2.1 node. Enter a value; there is no default. The name must conform to SNA naming conventions. You should consult with the SNA administrator about this name. CP name [] : cp-name The Configuration utility prompts you to enter the maximum number of transmission groups (TGs) that can be concurrently active. Enter an integer from 1 to 255; the default is 4. You can change this value while transmission groups are active. This value can include, if selected, the Intranode transmission group. Maximum active transmission groups [4] : nnn The Configuration utility prompts you to indicate whether or not this transmission group should be designated as the Intranode TG. Enter Yes or No; the default is yes. (You can enter y or n.) Intranode, as defined by IBM in the T2.1 node architecture, provides for the routing of PIUs between NAUs that reside in the same (Peer Server) node. Should you elect to define it, the Intranode TG can be used to establish Independent LU SNA sessions between two clients that both reside in the non-SNA network (TCP/IP, DECnet, or local transports). This can be useful, since the same API can be used for both SNA and non-SNA connections. The name of the Intranode TG is INTRANODE. Only one Intranode transmission group instance can exist. Once you answer yes for a transmission group, you cannot designate another group as the Intranode TG unless you repeat the section. Create an Intranode transmission group [Yes] : Following the Intranode TG, the Configuration utility begins a series of prompts for each Transmission Group. You can define up to 255 transmission groups. The sequence for defining a given TG begins with a prompt for a TG name. When the series of parameters required for a TG is complete, the Configuration utility returns to the Transmission Group name prompt for the next TG. Press Return to end both the TG definition sequence and the CP Services section. The Configuration utility prompts you to enter the Transmission Group (TG) name. Enter a value; the default is none. Transmission group names should correspond to those specified in the LU Services LU and LU Services Partner LU definitions in Section 3.2 and 3.4 of this configuration dialog. Transmission group names are local resource names and are not generally registered in the network. Transmission group name [] : tg-name In addition to the entity name, each defined TG requires several characteristic definitions that determine the TG's relationship to the underlying Data Link Control layer, its capabilities, and optional parameters that allow the restriction of incoming TG activation requests. The DLC link and station names provide the correlation between the TG and a specific data link instance, and must uniquely match the link and station name pair as defined in Section 2 (DLC Configuration) of the Configuration utility. The Configuration utility prompts you to enter the data link type. You can configure SDLC, QLLC, or LLC2. You should respond to this prompt using a data link type that you configured in Section 2. (Error checking is performed if you configured SDLC in Section 2, and then you select LLC2 at this prompt as the data link type. Your response will be rejected and you will receive an error message.) The data link type that you provide will prompt you with the appropriate data link and station names. Data link type (SDLC/QLLC/LLC2) [] : dlc_type The Configuration utility prompts you to enter the DLC Link instance name for the designated transmission group (TG). Enter a value. The name must correspond to a DLC Link name specified in Section 2 of the configuration dialog. dlc-name link [] : link-name The Configuration utility prompts you to enter the DLC Station instance name for the designated Transmission Group. Enter a value; the default is STN-0 for the first QLLC or SDLC station name, and LINK-0 for the first LLC2 link name. The name must correspond to a DLC Station name specified in Section 2 of the configuration dialog. dlc-name station [] : station-name The Configuration utility prompts you to indicate whether or not the designated transmission group will support dependent LUs. Enter Yes or No (you can enter y or n.); the default is yes. Specifying Yes will partition the transmission group LFSID address space to include dependent LUs and (providing XID3s are exchanged) request ACTPU from the adjacent node. This designates how the Peer Server should internally partition the TG session address space. Dependent LUs are those requiring SSCP assistance. If you are going to use the Peer Server for 3270 terminal emulation, Remote Job Entry, LU type 0, or general mainframe connectivity of any type that was supported with previous DEC SNA Gateways, you should answer Yes. Note that a TG that supports dependent LUs can also support independent LUs (as used by APPN LU6.2 sessions between peer T2.1 nodes); they are not mutually exclusive. Dependent LU support [yes] :ans The Configuration utility prompts you to indicate the connection type. Enter temporary or permanent; the default is temporary. (You can enter t or p.) Permanent connections are those which retain an active datalink connection even when no sessions are active. Temporary connections activate and deactivate the datalink as necessary on demand of session activity. Note that if the TG was created to support dependent LUs, the SSCP-PU session is included in the "active sessions" criteria, and the datalink connection will remain active as long as the PU corresponding to the temporary TG is active. Connection type [Temporary] : type If you specified Connection type as temporary, the Configuration utility prompts you to enter the Disconnect timer value. This parameter specifies the number of seconds to delay deactivation of the designated Temporary TG's data link connection. The timer is initiated when the last independent LU-LU session exits (or, the SSCP-LU session if dependent LUs are supported). Enter a value from 0 to 3600 seconds; the default is 30 seconds. Disconnect timer [30] : nnnn The Configuration utility prompts you to enter the Node Identifier value for the transmission group. The Node ID is an optional four-byte value that further identifies the local node in XID3 exchanges with the peer node. Enter an octet string of 1 to 8 hexadecimal digits preceded by %X; the default is %X00000000. The Node Identifier is optionally specified in the Format 0 section of the XID. Consult your SNA network administrator for the correct response. If the TG is connected to a mainframe boundary node, this value specifies the IDNUM and IDBLK VTAM parameters. Consult your SNA network administrator to determine what value to use. If in doubt, take the default (%X00000000). Node ID [] : nnnnnnnn The Configuration utility prompts you to specify whether the TG is to include optional parameters that restrict incoming connection requests on the TG to those with a specific Node ID, Network ID, or CP Name. Enter Yes or No (you can enter y or n.); the default is no. This is useful for dynamic TG activations where more than one peer node may be establishing the connection, as with dial-in lines. The Network ID can limit the adjacent node to be one of a specific APPN network; the Node ID and CP Name (together or separately) can limit the incoming connection to a specific node. Note that these are not true security or authentication mechanisms, since an incoming node that has been purposely misconfigured will not be detected. Incoming restrictions [No] : ans If (and only if) you answer Yes, the utility prompts you for additional information, as follows: o The utility prompts you for the name of the adjacent node identification: Required adjacent node ID [] : node-id Enter the Node Identifier for the adjacent node, expressed in one to four bytes as one to eight hexadecimal digits; there is no default. This value is compared with an adjacent node's Node ID. Link activation is disallowed unless it matches. Consult your SNA network administrator if you are uncertain of the response. o The Configuration utility prompts you for the adjacent network identification: Required adjacent network ID [] : net-id Enter the Network Identifier (NETID) of the adjacent T2.1 node; there is no default. The name must conform to SNA naming conventions. The name you supply is compared with an adjacent node's Network ID. Link activation is disallowed unless it matches. Consult your SNA network administrator if you are uncertain of the response. o The Configuration utility prompts you for the adjacent CP name: Required adjacent CP name [] : cp-name Enter the CP name of the adjacent T2.1 node; there is no default. The name must conform to SNA naming conventions. The name is not checked against the network. The name you supply is compared with an adjacent node's CP name; link activation is disallowed unless it matches. Consult your SNA network administrator if you are uncertain of the response. The Configuration utility repeats this series of prompts for another transmission group. You can add more TGs to create additional links between the Peer Server and adjacent nodes. To do so, you must include an underlying DLC Link and Station (or SAP and Link for LLC2) for each TG. When you have defined all the transmission groups, you can continue to the next section by pressing Return. The utility asks if you wish to repeat the section. Press Return to continue. This completes the Peer Server configuration process. Transmission group name [] : Do you wish to repeat Section 4, SNA CP Services Configuration[N]? 4.3.7 Generating an NCL Script File The Configuration utility prompts you for information concerning the NCL script file. If you have manually created a file containing any special NCL commands that need to be included into the Peer Server startup script, you can enter the optional file name here. The file should contain only valid NCL command syntax, because the Configuration utility does not check the validity of the entries. NCL Script File Generation. --------------------------- NCL optional file name [] : optional-ncl-file Enter the name you wish the Configuration utility to give to the NCL script file. If you have no optional file, press Return to skip the question. The Configuration utility now generates a startup NCL script that configures the Peer Server entities that you have defined. By default, the output NCL script is named as the output answer file with the addition of the.ncl extension, but you can give the script a different name. You should keep the file extension .ncl to indicate that the file contains NCL commands. The Configuration utility prompts you to enter the name of the NCL file: NCL file name [answer-file-name.ncl] : ncl-file The Configuration utility displays the following messages and exits: Creating NCL file ncl-file.ncl... Copy this NCL script to /var/sna/t21_init_sna_server.ncl to use this script when the Peer Server is started. End of DEC SNA Peer Server Configuration Procedure V1.1 # This completes the Peer Server Configuration utility dialog. 4.4 Running the Configuration Scripts To run the configuration script created by the Peer Server Configuration utility, enter the following command: # /sbin/init.d/t21_sna_server start See the document DEC SNA Peer Server Management for details about using NCL to configure the Peer Server module entities. 4.5 Solving Configuration Problems You might encounter the following error messages while using the Peer Server Configuration utility: %T21-E-ACCEXIST, Access Name already exists Explanation: You entered an Access Name that has already been specified. User Action: Enter an Access Name that is unique. If you are uncertain which names you specified, type at the Access Name prompt and repeat the entire section 3.3, noting the Access Names listed. %T21-E-ADDROVFL, Dependent LU address overflow Explanation: When populating an LU range, you configured the LUs to be dependent capable (by specifying both an address and a Dependent LU Transmission Group) and calculated Dependent LU Address exceeded 255. If the Base address plus the number of LUs to populate exceeds 255, the remaining LUs that get created are not configured as dependent capable. User Action: Reconfigure the LU population by re-running Section 3.2 of the Configuration utility, or understand that some of the LUs created were not defined as dependent capable. %T21-W-ANSFILEOF, Answer file end of file reached Explanation: You have reached the end of input answer file prior to completing the Configuration utility session. You must have been using an answer file created by an earlier prematurely aborted Configuration utility session. User Action: Continue the Configuration utility session. %T21-E-ANSNOTOPEN, Cannot open answer file Explanation: The Configuration utility could not open the file whose name you entered for either an input or output answer file. Either the file does not exist or you do not have permission to open the file. User Action: Enter the file name with the correct path, or check your access to the file. %T21-E-AUTHEXIST, Authorization already exists Explanation: You entered an Authorization Name that has already been specified for another authorization object. User Action: Enter the Authorization Name that is unique. If you are uncertain which names you specified, type at the Authorization Name prompt and repeat the entire section 3.1 noting the Authorization Names listed. %T21-W-AUTHNOTEXIST, Corresponding Authorization not defined Explanation: You entered the Authorization name that has not been defined in section 3.1, Authorization Information. User Action: Enter the Authorization name that has been specified in Section 3.1. If you are uncertain which names you specified, type at the Authorizations for this LU prompt. You may wish to repeat the entire section 3 and then section 3.1 to view the valid Authorization names. %T21-E-INVAL, Invalid parameter value or invalid answer Explanation: You were prompted to enter a keyword, but your response did not match the expected values, or you were prompted to enter a numeric value within a certain range but your response was outside the range. User Action: Enter the correct value. Enter a ? at the prompt to see the correct data type and range. %T21-E-INVALSTNADDR, Invalid local secondary station address Explanation: You were prompted to enter an SDLC Station address and you entered a hexadecimal value of FF as a response. FF is an invalid station address. User Action: Enter a valid hexadecimal value in the range from 00 to FE. %T21-E-INVALGRPADDR, Invalid group address Explanation: You were prompted to enter an SDLC Group address and you entered a hexadecimal value of FF as a response. FF is an invalid Group address. User Action: Enter a valid hexadecimal value in the range from 00 to FE. %T21-E-INVALLSAPADDR, Invalid LSAP address Explanation: You were prompted to enter a local or remote Link Service Access Point (LSAP) address and you entered a hexadecimal value with the lowest significant bit set. The valid LSAP address is any hexadecimal number in the range from 00 to FE with its lowest significant bit clear, which implies that only even values are correct. User Action: Enter an even hexadecimal number in the range from 00 to FE. %T21-E-INVALMACADDR, Invalid MAC address Explanation: You were prompted to enter a remote MAC address and you entered an invalid string. The MAC address syntax must match the following string: xx-xx-xx-xx-xx-xx, where x is a hexadecimal digit. User Action: Enter a valid MAC address according to its syntax. %T21-E-INVANSVER, Invalid answer file version Explanation: You entered a file name at the "Input answer file" prompt that is not a valid Configuration utility answer file. User Action: Enter the name of a previously saved answer file, or press . %T21-E-LINKLINEEXIST, Link already exists with this Line name Explanation: You were prompted to enter a Modem Connect Line name and you entered a name that has already been specified for another Modem Connect Line. User Action: Enter the Modem Connect Line name that is unique. %T21-E-LLC2LNKEXIST, SAP Link already exists Explanation: You were prompted to enter an LLC2 SAP Link name and you entered a name that has already been specified for another SAP Link. User Action: Enter the SAP Link name that is unique among all Links of the same SAP. %T21-E-LLC2SAPEXIST, SAP already exists Explanation: You were prompted to enter an LLC2 SAP name and you entered a name that has already been specified for another SAP. User Action: Enter the SAP name that is unique. %T21-E-LUEXIST, LUs already exist Explanation: You entered an LU name that has already been configured. In Section 3.2 (LU Configuration) you have two optional ways to configure the LUs. One method is by populating a number of LUs with the same characteristics and another method is by listing one or more LUs with the same characteristics. If you were using the Populate method, some or all of the LUs specified were overlapping those listed in a previous group of LUs. In a List method, you entered an LU name that was previously configured. User Action: In a Populate method, enter the LU name characteristics that is different from the previously configured. If the LU name prefix and suffix are identical, you must ensure that the LU number range does not overlap the range already specified, otherwise specify a different name prefix or suffix. If you are using a List method, enter an LU name that has not been previously configured. %T21-E-NCLNOTOPEN, Cannot open NCL file Explanation: You entered the name of an NCL file, but the Configuration utility could not open it. You may have entered the name or a path incorrectly, or you may not have permission to access the file. User Action: Enter the correct file name; check your access to the file. %T21-E-OBJEXIST, Object already exists Explanation: You entered an Object name that has already been specified for another Access Server object. User Action: Enter the Object name that is unique. If you are uncertain which names you specified, type at the Object name prompt and repeat the entire section 1 noting the Object names listed. %T21-W-OBJNOTEXIST, Corresponding Object not defined Explanation: You were prompted in section 3.2 (LU Configuration) to enter an Object Name and you entered a name of an object that has not been specified in Section 1 (SNA Access Server Configuration). User Action: You may want to repeat section 3.2 to reenter the Object name that matches an Object name listed in Section 1, or enter Space to clear the Object name. %T21-E-QLLCLINKEXIST, Link already exists Explanation: You were prompted to enter a QLLC Link Name and you entered a name that has already been specified for another Link. User Action: Enter the Link Name that is unique. %T21-E-QLLCSTNEXIST, Station already exists Explanation: You were prompted to enter a QLLC Link Station Name and you entered a name that has already been specified for another station. User Action: Enter the Station Name that is unique among all the station names for this particular Link. %T21-E-RLUEXIST, Remote LU already exists Explanation: You were prompted to enter a Partner LU Name and you entered a name that has already been specified for another Partner LU. User Action: Enter the Partner LU Name that is unique. %T21-E-SDLCLINKEXIST, Link already exists Explanation: You were prompted to enter an SDLC Link Name and you entered a name that has already been specified for another Link. User Action: Enter the SDLC Link Name that is unique. %T21-E-SDLCSTNEXIST, Station already exists Explanation: You were prompted to enter an SDLC Link Station Name and you entered a name that has already been specified for another station. User Action: Enter the Station Name that is unique among all the station names for this particular Link. %T21-E-TOOLONG, Parameter value too long Explanation: In section 3.3 (Access Name Configuration), you entered a User Data string longer than 255 ASCII characters. User Action: Enter a User Data string that does not exceed 255 characters. %T21-W-UNDEFLULIST, Undefined LUs in the LU list Explanation: You were prompted to enter an LU list in section 3.3 and you responded with an LU name list that does not match any LU name specified in the section 3.2 - LU Configuration. User Action: If you configured LUs in the section 3.2, repeat section 3.3 and enter the valid LU names or a wildcard character (*). If you did not specify any LU name in the section 3.2, enter . %T21-E-VERNOTSUP, Answer file version Vn.n not supported Explanation: Your input answer file contains a version number (n.n) that is not supported. The support for your file version may have been discontinued, or the version in your saved answer file has been modified. User Action: Create a new answer file by re-running ICU. 4.6 Modifying the Configuration with NCL After you load the Peer Server, you can modify the run-time configuration by using NCL commands. See DEC SNA Peer Server Management for details about using NCL to manage or reconfigure the Peer Server module entities. 4.7 Reconfiguring the Peer Server After the Peer Server has been in service for some time, you may find that you wish to reconfigure it. You can use one of the three methods described to make changes to the configuration: 1. Run the NCL manually. 2. Edit the NCL startup file, t21_init_sna_server.ncl. 3. Rerun the Configuration utility using the answer file created on the last pass. This is the preferred method. You must shutdown and restart the Peer Server to read the new NCL file. Note The new NCL script goes into effect the next time you shutdown and restart the Peer Server. See Chapter 5 for information on restarting the Peer Server. (null)(null)(null) 5 Starting and Shutting Down the Peer Server Once you have installed the DEC SNA Peer Server software, you can start it and shut it down. This chapter describes how to start and shut down the Peer Server. 5.1 Starting the Peer Server Normally the Peer Server is started up as part of the system startup. You can restart the Peer Server by running the startup script file with a parameter of start as follows: # /sbin/init.d/t21_sna_server start The startup procedure displays the following messages: Loading DEC SNA Peer Server modules... t21sd... t21spd... t21sdlc... t21llc... Starting DEC SNA Peer Server daemons... t21mcd... t21smc... 5.1.1 Checking the Status of the Startup The startup script file can take several minutes to complete processing the /var/sna/t21_init_sna_server.ncl file. You can verify that the startup file is still processing, and that the SNA Peer Server daemons are launched and active by typing: # ps ax | grep t21 During the startup process, a log file is created. The log file is located in /var/tmp/t21_init_sna_server.log. If the startup process fails, refer to this file to determine the cause of the problem. You cannot view this file until the startup procedure completes. 5.2 Shutting Down the Peer Server Issue the following command to shut down the Peer Server: # /sbin/init.d/t21_sna_server stop This command will: o Terminate all active sessions. o Terminate all DLC connections to the IBM environment. o Cancel the Peer Server daemons running on the DEC OSF/1 system. See Section 5.1 if you wish to restart the Peer Server. A DEC SNA Peer Server NCL Startup Scripts The DEC SNA Peer Server reads the t21_init_sna_server.ncl ncl startup script from the /var/sna directory at Peer Server startup (typically during system boot time). This appendix provides examples to illustrate t21_init_sna_server.ncl configurations in two typical environments. Example A-1 assumes a conventional connection to an IBM mainframe using traditional dependent LUs as a T2.0 node. Example A-2 assumes a connection to an IBM AS/400 using LUs capable of both dependent and independent LU use, as a T2.1 node. Dependent LUs are capable of only a single session per LU, and the "non-SNA" (client) side of the session is always the secondary logical unit (SLU). Dependent LUs support LU types 0, 1, 2, 3, and 6.2 and are represented by applications such as 3270 Terminal Emulators, Digital's Data Transfer Facility, Digital's 3270 Data Stream Programming Interface, and Remote Job Entry. Independent LUs are capable of multiple and parallel sessions per LU, and either LU in the session may be the primary logical unit (PLU). LU type 6.2 is required to use independent LUs. For clarity, Example A-1 and Example A-2 use a single Transmission Group and the SDLC data link. Example A-1 Mainframe Example (T2.0 Dependent LUs) ! ! Set up SNA Access Server Entity ! create node 0 sna access server ! ! Set up SNA Data Link Entity ! ! Set up SDLC Entity ! create node 0 sdlc create node 0 sdlc link SDLC-0 - line = modem connect line LINE-0, - 1 capability = NEGOTIABLE, - configuration = PointToPoint, receive frame size = 1000, - 2 retry maximum = 15 create node 0 sdlc link SDLC-0 station STN-0 - address = 40, - 3 transfer mode = TWA, - modulo = NORMAL, - window size = 7, - inactivity timer = 30,- send frame size = 1000 ! ! Set up SNA LU Services Entity ! create node 0 sna lu services set node 0 sna lu services default transmission group = TG-1 ! ! Set up SNA LU Services LU Entities ! create node 0 sna lu services lu T01 - dependent lu transmission group = TG-1, - 4 dependent lu address = 1, - capability = Both, - maximum active sessions = 0, - 5 old name = "SNA-0.1" create node 0 sna lu services lu T02 - dependent lu transmission group = TG-1, - dependent lu address = 2, - capability = Both, - maximum active sessions = 0, - old name = "SNA-0.2" . . . . create node 0 sna lu services lu T32 - dependent lu transmission group = TG-1, - dependent lu address = 32, - capability = Both, - maximum active sessions = 0, - old name = "SNA-0.32" ! ! Set up SNA LU Services Access Name Entities ! create sna lu serv acc name CICS - lu list = {T*},- 6 partner lu = CICS17,- 7 logon mode = LU24096 8 create sna lu serv acc name DTF - lu list = {T*},- partner lu = DTFV31,- 1ogon mode = LU24096 create sna lu serv acc name NETVIEW - lu list = {T*},- partner lu = CNM02,- logon mode = MCAUTO ! ! Set up SNA LU Services Authorization Entities ! ! ! Set up SNA LU Services Partner LU Entities ! ! ! Set up SNA CP Services Entities ! create node 0 sna cp services - network id = USDEC101, - 9 cp name = PEERSRVR, - 10 maximum active TGs = 4 create node 0 sna cp services transmission group TG-1 - data link = SDLC link SDLC-0 station STN-0, - 11 intranode = No, - dependent lu support = Yes, - connection type = Permanent, - node id = %XDEC00124 12 ! ! Enable all entities ! enable node 0 sdlc - link SDLC-0 enable node 0 sdlc - link SDLC-0 station * enable node 0 sna lu services lu * enable node 0 sna cp services transmission group * enable node 0 sna access server 1 The line parameter associates the SDLC link with the underlying modem connect entity line. 2 The receive (and, when specified, send) frame sizes will be automatically adjusted on this link (since it is negotiable); however, there are hardware limitations that must be observed (in this case, the scc built-in synchronous communications port limits the size to 1000 bytes). 3 The SDLC station poll address is specified with this parameter; since the link capability is negotiable the address will be conveyed to the adjacent node. 4 The combination of a supplied dependent LU transmission group (TG) and a dependent LU address specifies that this LU is a dependent-capable LU. 5 A maximum active session number of zero indicates an unlimited number of sessions (for dependent LUs, however, only a single session per LU is required). 6 This syntax selects any available defined LU whose name begins with "T". 7 For a dependent LU, the partner LU name is the actual IBM APPLID name to send in the SNA "init self" RU. 8 The logmode name to include in an SNA "init self" RU. 9 The network ID must match that used in the existing SNA subnet; check with your network administrator. 10 The CP name is unique to this node, but is usually assigned by the network administrator. 11 The underlying SDLC link and station, defined near the top of the script. 12 The node ID (XID IDBLK and IDNUM fields); commonly must correspond with the mainframe definition (check with your network administrator). Note - Since there are no IBM initiated ("outbound") sessions needed, no SNA Access Server Objects need to be configured. - Since there are no Independent LU sessions (in which the Digital system is the Primary LU) needed, no SNA LU Services Partner LU definitions need to be configured. Example A-2 AS/400 Example (T2.1 Independent LUs) ! ! Set up SNA Access Server Entity ! create node 0 sna access server create node 0 sna access server object outbound_alpha - transport = TCPIP, - internet node = speedy.banking.company.com, - port = 4567 ! ! Set up SNA Data Link Entity ! ! ! Set up SDLC Entity ! create node 0 sdlc create node 0 sdlc link SDLC-1 - line = modem connect line line-1, - capability = NEGOTIABLE, - configuration = PointToPoint, - receive frame size = 1000, - retry maximum = 15 create node 0 sdlc link SDLC-1 station STN-0 - address = 40, - transfer mode = TWA, - modulo = NORMAL, - window size = 7, - inactivity timer= 30,- send frame size = 1000 ! ! Set up SNA LU Services Entity ! create node 0 sna lu services set node 0 sna lu services default transmission group = TG-AS400 ! ! Set up SNA LU Services LU Entities ! create node 0 sna lu services lu INDEP01 - capability = Both, - 1 maximum active sessions = 0, - object = outbound_alpha 2 ! ! Set up SNA LU Services Access Name Entities ! create sna lu serv acc name AS400ACC - 3 lu list = {INDEP01},- partner lu = AS400APP,- logon mode = LU24096 ! ! Set up SNA LU Services Authorization Entities ! ! ! Set up SNA LU Services Partner LU Entities ! create sna lu serv partner lu AS400APP - destination name = AS4PROG1, - 4 destination network = USDEC101, - 5 transmission group = {TG-AS400} 6 ! ! Set up SNA CP Services Entities ! create node 0 sna cp services - network id = USDEC101, - cp name = PEERSRVR, - maximum active TGs = 4 create node 0 sna cp services transmission group TG-AS400 - data link = SDLC link SDLC-1 station STN-0, - intranode = No, - dependent lu support = yes, - connection type = Permanent ! ! Enable all entities ! enable node 0 sdlc - link SDLC-1 enable node 0 sdlc - link SDLC-1 station * enable node 0 sna lu services lu * enable node 0 sna cp services transmission group * enable node 0 sna access server 1 The value "both" indicates that the LU can be both primary and secondary (PLU and SLU), without restriction. 2 The object name refers to the network object defined above (access server). 3 The application may specify this access name to provide both the LU and partner LU names necessary to establish a session with the AS/400 application "AS4PROG1". 4 The LU name known by the AS/400, to which the session is established. 5 The network ID common with the AS/400. 6 The locally defined Transmission Group used to establish connectivity with the AS/400. Note - Only a single LU is required for bidirectional AS/400 session use, as it is configured for both Digital and IBM-side initiated sessions. - For IBM initiated sessions, a TCP/IP connection is created to TCP/IP port 4567 on node `speedy.banking.company.com' by use of the object name configured in the SNA Access Server configuration section. - This configuration can be combined with the previous one to create a configuration that supports both environments. In that case, you could use one SDLC line to the mainframe, and another to the AS/400.