Compaq SNA Server For_OpenVMS___________________________________ Installation and Configuration Part Number: AA-RJ1NA-TE January 2000 This guide contains the information necessary for installing and configuring the Compaq SNA Server for OpenVMS product. Revision/Update Information: This is a new manual. Operating System and Version: OpenVMS for Alpha V7.1 and V7.2-1 Software Version: Compaq SNA Server for OpenVMS, V1.0 Electronic Data Systems Corporation and Compaq Computer Corporation make no representations that the use of their products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Copyright © 1999 Electronic Data Systems Corporation. All Rights Reserved. Copyright © 1999 Compaq Computer Corporation Compaq, the Compaq logo, and the DIGITAL logo are registered in the U.S. Patent and Trademark Office. Alpha, DEC, DECnet, DECnet-Plus, DIGITAL SNA Domain Gateway, OpenVMS, VMS, and VMScluster are trademarks of Compaq Computer Corporation. The following are third-party trademarks: Advanced Peer-to-Peer Networking, and IBM are registered trademarks of International Business Machines Corporation. CICS, DISOSS, and VTAM are trademarks of International Business Machines Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. This document is available on CD-ROM. ________________________________________________________________ Contents Preface.................................................. vii 1 Preparing for Installation 1.1 SNA Concepts................................. 1-1 1.2 Preparing the IBM Environment................ 1-2 1.3 Installation Requirements.................... 1-4 1.3.1 Disk Space............................... 1-4 1.3.2 Privileges............................... 1-4 1.3.3 Required SYSGEN Parameters............... 1-5 1.3.3.1 Dynamic Nonpaged Memory................ 1-5 1.3.3.2 Channel Count.......................... 1-6 1.3.4 DECnet Transport Connections............. 1-8 1.3.5 TCP/IP Transport Connections............. 1-8 1.4 VMS License Management Facility.............. 1-8 1.5 Hardware Requirements........................ 1-9 1.5.1 Compaq Communications Devices............ 1-9 1.5.2 Modems................................... 1-9 1.6 Software Requirements........................ 1-10 1.6.1 OpenVMS Operating System for Alpha....... 1-11 1.6.2 WANDD Drivers............................ 1-11 1.6.3 Compaq SNA Access Routines............... 1-12 1.6.4 Optional Software........................ 1-12 1.7 Considerations for OpenVMS Cluster Systems... 1-12 iii 2 Installing the SNA Server 2.1 Accessing the On-Line Release Notes.......... 2-1 2.2 Using VMSINSTAL.............................. 2-2 2.3 Installing SNA Server Software............... 2-3 3 Configuring the SNA Server 3.1 Configuration Requirements................... 3-1 3.1.1 Configuration Questionnaire.............. 3-2 3.1.1.1 Configuration Parameters for SDLC Lines.................................. 3-3 3.1.1.2 Configuration Parameters for X.25 Lines.................................. 3-7 3.1.2 Access Names............................. 3-11 3.1.3 Access Name Parameters................... 3-12 3.2 The SNA Server Configuration Dialog.......... 3-18 3.3 After Configuration.......................... 3-29 3.3.1 Authorizing Users........................ 3-29 3.3.2 Configuring SNA Server for Other Cluster Nodes.................................... 3-30 3.3.3 Updating DCL Tables...................... 3-30 3.3.4 Starting SNA Server...................... 3-30 3.3.5 Running the Installation Verification Procedure................................ 3-31 3.3.6 User Account Quotas and Privileges....... 3-33 3.3.7 Editing the System Startup File.......... 3-33 3.3.8 Editing the Configuration File........... 3-34 A Files Installed During Installation B Sample Installation and Configuration B.1 Sample Installation.......................... B-1 B.2 Sample Configuration (SDLC Lines)............ B-3 B.3 Sample Configuration (X.25 Lines)............ B-7 iv Index Figures 3-1 SNA Server Configuration ................ 3-29 Tables 1-1 Disk Space Requirements.................. 1-4 1-2 Required Nonpaged Pool Resources......... 1-5 3-1 Configuration Questionnaire (SDLC Lines)................................... 3-3 3-2 Communications Devices and Configuration Parameters............................... 3-6 3-3 Configuration Questionnaire (X.25 Lines)................................... 3-7 3-4 Configuration Questionnaire (Access Names)................................... 3-13 3-5 File Locations After Configuration....... 3-24 A-1 Files Added During Installation of SNA Server................................... A-1 v ________________________________________________________________ Preface Compaq SNA Server for OpenVMS, (from hereon referred to as the SNA Server) is a Compaq Computer Corporation software product that allows an OpenVMS user to communicate with programs running on an IBM SNA networked system. These systems must be part of a network configuration designed according to IBM's Virtual Telecommunication Access Method (VTAM) and Advanced Communications Function for Network Control Program (ACF/NCP). This manual presents the information needed to install and configure SNA Server on OpenVMS systems. Intended Audience This manual is intended for OpenVMS Alpha system managers or users who are going to install and configure the SNA Server software. You should be familiar with installation concepts, and you must have knowledge of IBM's ACF/NCP and VTAM or have access to someone with this knowledge. Keep this document with your distribution kit. You will need to refer to it again if you receive any maintenance updates or need to reinstall SNA Server. Structure Compaq SNA Server for OpenVMS Installation and Configuration is divided into three chapters and two appendices. vii Chapter 1 Provides introductory information about SNA Server, describes all required and optional SNA Server components, describes the IBM parameters with which you must be familiar, and describes installation requirements. Chapter 2 Describes the installation process. Chapter 3 Describes the configuration process. Appendix A Shows the files installed during installation. Appendix B Provides a sample installation procedure, a sample SDLC configuration procedure, and a sample QLLC configuration procedure. Associated Documents The following manuals are part of the SNA Server documentation kit: o Compaq SNA Server for OpenVMS Installation and Configuration o Compaq SNA Server for OpenVMS Management o Compaq SNA Server for OpenVMS Problem Solving o Compaq SNA Server for OpenVMS Guide to IBM Parameters Additional Recommended Documentation The following lists of additional documentation may be useful: o X.25 manuals o Access routine manuals o OpenVMS manuals o IBM Documentation viii X.25 Manuals If you are communicating with the IBM host over an X.25 Packet Switched Data Network (PSDN), you might find the following X.25 for OpenVMS Alpha Systems manuals useful: o X.25 for OpenVMS Software Product Description (SPD) Version 1.3 or later o X.25 for OpenVMS Release Notes Version 1.3 or later o X.25 for OpenVMS Configuration o X.25 for OpenVMS Management Guide o X.25 for OpenVMS Problem Solving Guide o DECnet/OSI for VMS VAX WANDD Programming Manual as amended by the current X.25 for OpenVMS Release Notes Access Routine Manuals In addition to the SNA Server base communication system, Compaq Computer Corporation provides the following access routine products that run on OpenVMS and use SNA Server to access IBM systems: o Bulk Data Transfer - DIGITAL SNA Data Transfer Facility for OpenVMS - DIGITAL SNA Remote Job Entry for OpenVMS - DIGITAL SNA Printer Emulation for OpenVMS o Programming Interface - DIGITAL SNA APPC/LU6.2 Programming Interface for OpenVMS - DIGITAL SNA 3270 Data Stream Programming for OpenVMS - DIGITAL SNA Application Programming Interface for OpenVMS o Interactive Access - DIGITAL SNA 3270 Terminal Emulator for OpenVMS - DECWindows 3270 Terminal Emulator ix OpenVMS Manuals You might find the following OpenVMS manuals useful: o DECnet OpenVMS Networking Manual o DECnet-Plus for OpenVMS Introduction and User's Guide o DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration Manual o DECnet-Plus Network Control Language Reference o OpenVMS System Management Utilities Reference Manual o OpenVMS System Manager's Manual o OpenVMS System Messages and Recovery Procedures o OpenVMS Guide to System Security IBM Documentation Refer to Appendix A of the Compaq SNA Server for OpenVMS Guide to IBM Parameters for a list of IBM manuals that you should have available for reference. Acronyms The following acronyms are used throughout this manual: ACF/NCP IBM's Advanced Communications Facility/Network Control Program Alpha Refers to any one of the systems listed in the Software Product Description (SPD) but not to a particular system. CTF Common Trace Facility DCE Data-circuit terminating equipment DCL DIGITAL Command Language DTE Data terminal equipment LU Logical unit NCL Network Control Language NCP Network Control Program x NPSI IBM's X.25 NCP Packet Switching Interface PLU Primary logical unit PSDN Packet switching data network PU Physical unit QLLC Qualified Logical Link Control SDLC Synchronous data link control SLU Secondary logical unit SNA Systems Network Architecture SNANCP SNA Server Network Control Program SSCP System Services Control Point SVC Switched virtual circuit VTAM IBM's Virtual Telecommunications Access Method X.25 CCITT Recommendation for DTE/DCE interface for PSDNs xi Graphic Conventions This manual uses the following graphic conventions for SNANCP and NCL commands. Command examples show system output SNANCP> SET LINE line-d user input in black monospaced id type. In both command and syntax examples, uppercase letters represent text that you must enter exactly as shown. Lowercase letters in italics represent variables for which you must substitute specific information. [opt-arg] Square brackets enclose optional parts of a command. { ACTIVE LINES } Braces indicate that you must choose { KNOWN LINES } only one of the command words or { LINE line-id } arguments in the list. { } Unless otherwise specified, every command line is terminated by pressing the RETURN key. This symbol indicates that you press and hold down the key labeled CTRL while simultaneously pressing another key (for example, or ). circuit-id A string of characters whose exact syntax is that for an SNA circuit identification. SDLC circuits are identified by a string in the form SDLC-n, where n indicates the number of the circuit. QLLC circuits are identified by a string in the form QLLC-n, where n indicates the number of the circuit. xii line-id A string of characters whose exact syntax is that for an SNA line identification. A line is identified in the following form: devcu where: dev is the device name. c is an alphabetic character (A- Z) designating the device's hardware controller. u is a decimal number (0 or a positive integer) designating a unit on the device's hardware controller, if the controller supports more than one unit. The default is 0. lu-id A string of characters whose exact syntax is that for logical unit (LU) identification. An LU is identified in the form SNA-nnn.mmm, where nnn is the number of the PU and mmm is the number of the LU. node-id Either a node-name or a node-address. node-name A string of up to 6 alphanumeric characters containing at least 1 alphabetic character. pu-id A string of characters whose exact syntax is that for physical unit (PU) identification. A PU is identified in the form SNA-nnn, where nnn is the number of the PU. When you issue NCL and SNANCP commands, many component names, parameters, and qualifiers require additional information. In most cases, the syntax of this additional information follows a standard set of rules. (Exceptions to these rules are noted where appropriate.) All numeric values are in decimal and have a range of 0 to 65,535 unless otherwise specified. xiii 1 ________________________________________________________________ Preparing for Installation The Compaq SNA Server for OpenVMS software, (from hereon referred to as the SNA Server) is a set of programs and routines that implements the IBM SNA network protocol for programs running on a Compaq OpenVMS Alpha system under the OpenVMS operating system. The Compaq SNA access routines, such as the DIGITAL SNA 3270 Terminal Emulator for OpenVMS, use SNA Server to access applications and programs on the IBM system. This chapter describes the preparations you must make before you install and configure SNA Server. SNA Server supports configurations for SDLC leased or dial-up lines, or via a Packet Switched Data Network (PSDN). Figure 1-1 shows an OpenVMS system connected to an IBM host through an SDLC leased or dial-up line. Figure 1-2 shows an OpenVMS system connected to an IBM host through a packet switched data network (PSDN). 1.1 SNA Concepts An IBM SNA network perceives all communications with SNA Server in terms of logical connections called sessions. An application running on an OpenVMS system and an application running on an IBM host-linked together in a session-are identified as logical units (LUs). When a session is established, the IBM host designates one LU as the primary logical unit (PLU) and one as the secondary logical unit (SLU). The SLU resides on your OpenVMS system; the PLU resides on the IBM host. Communication between an SNA Server SLU and an IBM PLU is accomplished by means of a software component in SNA Server known as a physical unit (PU). Preparing for Installation 1-1 1.2 Preparing the IBM Environment IBM SNA software components must be configured before you can use the SNA Server communications software. The Compaq SNA Server for OpenVMS Guide to IBM Parameters discusses the IBM parameters required for successful communication between the IBM system and your OpenVMS Alpha system. Your IBM systems programmer should pay special attention to the following macros and operands: o ACF/NCP GROUP Macro DIAL LNCTL REPLYTO o ACF/NCP LINE Macro DUPLEX NRZI PAUSE SPEED o ACF/NCP PU Macro ADDR DATMODE MAXDATA PUTYPE o ACF/NCP LU Macro BATCH LOCADDR PACING o X.25 NPSI Macros (for X.25 communication) o VTAM Operands PATH Statement (for X.25 communication) DIALNO 1-2 Preparing for Installation GRPNM o VTAM Operands GROUP Statement ANSWER CALL DIAL DLOGMOD MODETAB o VTAM Operands PU Macro ADDR DLOGMOD IDBLK IDNUM MAXDATA MAXOUT MODETAB PACING PUTYPE o VTAM Operands LU Macro DLOGMOD LOCADDR MODETAB PACING o VTAM Logon Mode Table LOGMODE RUSIZE You should regard the Compaq documentation as an adjunct to the IBM documentation; the IBM documentation remains the authoritative source for IBM software concepts and procedures. In most cases, the IBM parameters you use with the SNA Server software are compatible with the Compaq SNA Gateway-ST or Gateway-CT software. Preparing for Installation 1-3 1.3 Installation Requirements The following sections discuss the various requirements for installing SNA Server. 1.3.1 Disk Space Installing SNA Server requires a certain amount of free storage disk space during the installation. Once SNA Server is installed, less storage space is required. Table 1-1 summarizes the storage requirements. Table_1-1_Disk_Space_Requirements_________________________ Blocks During Blocks After Kit______________Installation__________Installation_______ SNA_Server_V1.0__8,000_________________6,500______________ 1.3.2 Privileges To install SNA Server you must be logged in to an account that has SETPRV or at least the following privileges: o ACNT o CMKRNL o DETACH o EXQUOTA o LOG_IO o OPER o PHY_IO o PRMMBX o SYSNAM o SYSPRV o WORLD 1-4 Preparing for Installation 1.3.3 Required SYSGEN Parameters This section describes dynamic nonpaged memory require- ments and how to change the SYSGEN parameters by adding channel count requirements and the DECnet Transport connections. 1.3.3.1 Dynamic Nonpaged Memory You must ensure that your system has enough dynamic nonpaged pool space allocated before installing and starting SNA Server. Table 1-2 provides an estimate of the amount of system nonpaged pool resources required. Table_1-2_Required_Nonpaged_Pool_Resources________________ Task_or_Object_____________Memory_Required________________ Load, configure, and 180 KB start SNA Server Each access name 192 bytes Receive buffers[1] number of receive buffers*(864 bytes + PU segment size) Each "active" LU (# 1 KB started) Each "in session" LU (# 10 KB available) Each LU authorization 272 bytes record [1]For_SDLC_lines_only._Use_SNANCP_to_display_or_modify___ this value __________________________________________________________ For example, a system with 64 active LUs, 16 "in session" LUs, and a receive buffer size of 521 bytes needs approximately 450 KB of nonpaged pool. This amount increases as you increase the number of access names and authorized users. To see the current dynamic nonpaged pool resources, run the SYSGEN utility and use the SHOW NPAGEDYN command: Preparing for Installation 1-5 $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SHOW NPAGEDYN Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- NPAGEDYN 2050000 300032 16384 -1 Bytes Changing the NPAGEDYN value To increase the NPAGEDYN system value, use the AUTOGEN command procedure. AUTOGEN automatically adjusts values for parameters associated with the ones you reset manually. To change system parameters with AUTOGEN, edit the following file: SYS$SYSTEM:MODPARAMS.DAT For example, to change the setting for the NPAGEDYN system parameter, add this line to the file: ADD_NPAGEDYN = nnn where nnn is the amount you calculated. Now, run the AUTOGEN procedure to recalculate your system parameters (you may wish to wait until you have read the next section). Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT AUTOGEN performs an automatic system shutdown and reboots when it has finished. Rebooting your system makes the new parameter values active. For more information about using AUTOGEN, see the instructions on modifying system parameters in the OpenVMS documentation on system management and operations. 1.3.3.2 Channel Count To have the maximum sessions, make sure that there are sufficient I/O channels available. (The SNA Server uses 3 channels per active session.) When the number of I/O channels is insufficient, the SNA application fails to establish a communication link to the Gateway. Usually, this failure is accompanied by the following system message: %SYSTEM-F-NOIOCHAN, No IO channel available 1-6 Preparing for Installation This error usually indicates that the SYSGEN parameter CHANNELCNT has been exceeded. To display the maximum number of channels ever used by a process, use the following procedure: 1. Log into a privileged account. 2. Run SDA: $ ANALYZE/SYSTEM SDA> SET PROCESS/ID=process-id SDA> EVALUATE @CTL$GL_CHINDX CHANNELCNT is a special SYSGEN parameter which can be listed with the following SYSGEN command: SYSGEN> SHOW/SPECIAL Changing the CHANNELCNT value To increase the value of CHANNELCNT, use the following procedure: 1. Log into a privileged account. 2. Run SYSGEN: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SET CHANNELCNT value SYSGEN> WRITE CURRENT 3. To document the change (and prevent AUTOGEN from changing CHANNELCNT), edit the SYS$SYSTEM:MODPARAMS.DAT file to include the following line: CHANNELCNT = value 4. Reboot the system If the preceding actions do not fix the problem, the process-specific FILLM quota may be set higher than the CHANNELCNT value. To modify the value of FILLM, use the following procedure: 1. Log into a privileged account. 2. Set default to SYS$SYSTEM: $ SET DEFAULT SYS$SYSTEM Preparing for Installation 1-7 3. Run AUTHORIZE: $ RUN AUTHORIZE UAF> MODIFY username/FILLM=value UAF> EXIT 1.3.4 DECnet Transport Connections DECnet-Plus sets the maximum number of OSI transport logical links to 201. If you want to change the defaults, use net$configure.com. For more details, refer to the DECnet-Plus for OpenVMS- Applications Installation and Advanced Configuration manual. 1.3.5 TCP/IP Transport Connections TCP/IP Services defines the port used by the SNA Server to be 108. If you want to change the defaults, use tcpip$config.com. For more details, refer to the TCP/IP for OpenVMS- Installation and Configuration manual. 1.4 VMS License Management Facility Before installing SNA Server, you must register your software license. The license registration information is contained in the Product Authorization Key (PAK) that is shipped with SNA Server. The PAK is a paper certificate that contains information about the license you need to run a particular piece of software. You should register your SNA Server license before you perform the installation, configuration, and startup. During the installation, you are asked if you have registered the SNA Server license and loaded the appropriate authorization key. If you have not registered and loaded the PAK information, you can complete the installation; however, you will not be able to start the product or run the Installation Verification Program (IVP). After you register the license and load an authorization key, you can start the product and run the IVP. 1-8 Preparing for Installation Register the license information by using either the OpenVMS License command procedure (VMSLICENSE) or the LICENSE REGISTER command, as described in the VMS License Management Utility Manual. When registering the SNA Server PAK information, use the product name SNA-Server. 1.5 Hardware Requirements Your single OpenVMS Alpha system is attached to the SNA network through a Compaq hardware communications device, a communications line, an IBM communications controller, and modems (if not directly attached to the IBM communications controller). The following sections discuss only the Compaq communications device and modem requirements. 1.5.1 Compaq Communications Devices Compaq communications devices support half-duplex point- to-point, half-duplex multipoint, full-duplex point-to- point, and full-duplex multipoint SDLC communications. ________________________Note ________________________ The words multipoint and multidrop have the same meaning and are used interchangeably in this manual. _____________________________________________________ Transmission characteristics (such as speed and mode of operation) can vary to satisfy different performance requirements. For a list of supported communications devices and characteristics, see the Software Product Description (SPD) for the current version of SNA Server. 1.5.2 Modems If your OpenVMS system is not directly attached to the IBM communications controller, the communications line between your OpenVMS system and the IBM host system requires a pair of synchronous modems or a modem eliminator (hardware that performs the function of two modems if the communicating systems are in close proximity). Modems can be full-duplex or half-duplex. The type of modem or modem eliminator that you need for each SNA Server line depends on the data transfer rate. Preparing for Installation 1-9 Refer to the current X.25 for OpenVMS Software Product Description for a description of the synchronous controller characteristics. ________________________Note ________________________ The EIA-232-D interface replaces the RS-232- C interface. If you are using RS-232-C modem eliminators, you need a special adapter. Refer to the SNA Server release notes for additional information. _____________________________________________________ For a complete range of modem options or for help in selecting a modem, consult your Compaq network specialist. 1.6 Software Requirements SNA Server product installation requires the following software components: o OpenVMS operating system for Alpha o DECnet-Plus for OpenVMS o Wide Area Networked Device Drivers (WANDD) from the X.25 for OpenVMS product o Required Compaq SNA access routines Depending on the SNA Server configuration, the SNA Server product uses the following optional software components: o If you are communicating with the IBM host over X.25 lines, the full X.25 for OpenVMS Alpha product is required. o If Compaq SNA access routines use TCP/IP protocols to access the SNA Server, the TCP/IP Services for OpenVMS product is required. When the SNA Server installation is complete, you can add one or more Compaq SNA access routines if they are not already installed. 1-10 Preparing for Installation 1.6.1 OpenVMS Operating System for Alpha You must have the required version of the OpenVMS operating system software on your OpenVMS system (see the title page for the correct version of OpenVMS). If you do not have the required version, you must install it before you install the SNA Server software. For information on how to install OpenVMS software, refer to the OpenVMS Management Utilities Reference Manual. SNA Server also requires the Network class in addition to the OpenVMS Required Saveset class. When you are installing SNA Server software on an OpenVMS system, you must enable OPCOM to receive information about circuit changes that occur during SNA Server startup. If OPCOM is not enabled, you will not receive information needed to resolve problems. See Compaq SNA Server for OpenVMS Problem Solving for information about event messages logged by OPCOM. To enable OPCOM when using an OpenVMS system, either issue the command manually or edit the SYS$MANAGER:SYSTARTUP_ VMS.COM file and remove the comment character (!) in front of the @SYS$SYSTEM:STARTUP OPCOM command. After you remove the comment character, restart the system or run the commands in SYS$MANAGER:SYSTARTUP_VMS.COM by issuing the following command: $ @SYS$SYSTEM:STARTUP OPCOM 1.6.2 WANDD Drivers Install the device drivers with the following command: $ product install WANDD/source=kit-location After the Alpha WAN device drivers are loaded, do the following: $ sys$startup:wandd$configure.com $ sys$startup:wandd$startup Preparing for Installation 1-11 For more information, refer to the X.25 for OpenVMS Configuration and the X.25 for OpenVMS Release Notes. ________________________Note ________________________ If you are using X.25 data lines, skip this step and install the complete X.25 for OpenVMS product (see Section 1.6.4). _____________________________________________________ 1.6.3 Compaq SNA Access Routines Compaq SNA access routines allow you to communicate with programs running on the IBM system. Each access routine is installed separately. This manual provides instructions for installing only the base SNA Server communications software. For a complete list of access routines and individual user guides containing product installation information, see the SPD for the current version of SNA Server and Compaq SNA Server for OpenVMS Management. 1.6.4 Optional Software If you are communicating with the IBM host over X.25 lines, the full X.25 for OpenVMS product is required. In this case, you should follow the product's instructions for installing and configuring the full product. If the SNA Server supports Compaq SNA access routine connections over a TCP/IP network, the TCP/IP Services for OpenVMS product is required. Follow the product's instructions for installation and configuration. By default, the SNA Server uses the well-known port 108 to listen for incoming requests from the access routines. 1.7 Considerations for OpenVMS Cluster Systems A cluster is a group of OpenVMS systems that communicate over a high-speed communications connection. OpenVMS cluster systems have all the functions of single-node OpenVMS cluster systems and have the ability to share CPU resources, queues, and disk storage. 1-12 Preparing for Installation To install SNA Server software on an OpenVMS cluster system, use the following guidelines: o Install SNA Server once for the entire OpenVMS cluster. o For SDLC circuits, install a hardware communications device on each node that is to have the SNA Server software configured and used. o For QLLC circuits, you do not have to install a hardware communications device on each node that is to have the SNA Server software configured and used. For example, if you use the X.25 Relay facility, you connect to the relay node that has the appropriate communications device installed (see X.25 for OpenVMS Configuration for information). o Configure the SNA Server software on each node that is to use the software. When configuring the SNA Server software, you must specify the name of the system on which to configure the SNA Server software. Preparing for Installation 1-13 2 ________________________________________________________________ Installing the SNA Server This chapter explains how to install your Compaq SNA Server for OpenVMS (SNA Server) software. You should not attempt the installation until you have installed the required hardware and software and prepared the IBM SNA environment. SNA Server installation and configuration should take no longer than 20 minutes, depending on the type of installation media you use. The estimated installation time does not include preparation time or time consumed by problems resulting from failure to prepare properly. For general background information on installing optional software products on an OpenVMS Alpha system, refer to the OpenVMS System Management Utilities Reference Manual. 2.1 Accessing the On-Line Release Notes The SNA Server software provides on-line release notes. The prompt to display or print the release notes before installation appears in step 4 of the installation procedure when you run VMSINSTAL with the OPTIONS N parameter. To obtain the release notes after installation, display or print the file SYS$HELP:SNAVMS$010.RELEASE_NOTES. On-line help also directs you to the release notes file. After installation, type the following: $ HELP SNA_VMS RELEASE_NOTES Installing the SNA Server 2-1 2.2 Using VMSINSTAL After you log in to a privileged account to install the SNA Server software, set the default to SYS$UPDATE; then run VMSINSTAL, the command procedure that installs this product. An example of this procedure is shown in steps 1 and 2 (see Section 2.3). $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL SNASERV010 ddcu: [OPTIONS N] The command parameters are described in the next paragraphs. If you do not supply the first two parameters, VMSINSTAL prompts you for the product and device names. If you want to be prompted for the product name, device name, and installation options, type the following: $ @SYS$UPDATE:VMSINSTAL ddcu: Represents a device name where the distribution kit will be mounted for the SNA Server installation media, where dd is the device, c is the controller ID, and u is the unit number. It is not necessary to use the console drive to install SNA Server. If you do use the console drive, you should replace any media you removed from the drive. CSA1: is the device name used in examples in this document. OPTIONS N Is an optional parameter you should provide if you want to be prompted to display or print the release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not prompt you to display or print the release notes. Note that VMSINSTAL permits the use of several other options. For more information on the other options, refer to your processor-specific installation/operations guide. When you run VMSINSTAL, it checks the following: o Whether you logged in to a privileged account. Compaq Computer Corporation recommends that you install software from the system manager's account [SYSTEM] with your default device and directory set to SYS$UPDATE. 2-2 Installing the SNA Server o Whether you have adequate quotas for installation. VMSINSTAL checks for the following quota values: - ASTLM = 24 - BIOLM = 18 - BYTLM = 18000 - DIOLM = 18 - ENQLM = 30 - FILLM = 20 o Whether the following conditions exist: - DECnet is up and running. - Users are logged in to the system. If VMSINSTAL detects either of these conditions, you are asked whether you want to continue the installation. To continue, type YES. To stop the installation, press . 2.3 Installing SNA Server Software This section contains excerpts from the installation procedure and explains each step. Default answers appear in brackets throughout the installation procedure. To accept a default answer, press in response to the question. To abort the installation procedure at any time, press . The installation procedure deletes all files it has created up to that point and then returns to DCL level. To retry the installation procedure after pressing , you must start at step 2. Step 1: Log in to a privileged account, and set your default device and directory to SYS$UPDATE. Username: SYSTEM Password: password $ SET DEFAULT SYS$UPDATE Make sure you have backed up the system disk and that you have more than 8000 free blocks on the system disk. Installing the SNA Server 2-3 Step 2: Run VMSINSTAL. $ @VMSINSTAL SNASERV010 CSA1: OPTIONS N OpenVMS AXP Software Product Installation Procedure V7.1 It is 17-JAN-2000 at 12:20. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Before you proceed with an installation that will write to your system disk, make sure you have a good backup copy. If you are satisfied with the backup of your system disk, press . If you do not have a good backup copy, type NO and press to end the installation. Step 3: Insert the first installation kit volume. Please mount the first volume of the set on CSA1:. * Are you ready? YES The following products will be processed: SNASERV V1.0 Beginning installation of SNASERV at 12:20 %VMSINSTAL-I-RESTORE, Restoring product saveset A... To continue the installation, mount volume 1, type YES, and then press . Step 4: Select a release notes option. This step applies only if you specified OPTIONS N in step 2. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the release notes on line immediately. You can terminate the display at any time by pressing . 2-4 Installing the SNA Server If you select option 2, VMSINSTAL prompts you for a queue name. Either type a queue name, or press to send the file to the default output print device. * Queue name [SYS$PRINT]: If you select option 3, VMSINSTAL displays the release notes on line immediately and then prompts you for a queue name. If you select option 4, VMSINSTAL does not display or print the release notes. Regardless of the option you choose, VMSINSTAL copies the release notes to SYS$HELP:SNAVMS$010.RELEASE_NOTES. Next, VMSINSTAL displays the following prompt: * Do you want to continue the installation [N]?: YES To continue the installation, type YES and press . If you type NO or press , VMSINSTAL ends the installation. In either case, VMSINSTAL moves the release notes to SYS$HELP. Step 5: Respond to LMF queries. This product supports the OpenVMS License Management Facility (LMF). For more information about LMF, see the OpenVMS License Management Utility Manual. Product: SNA-Server Producer: DEC Version: 1.0 Release Date: 01-JAN-2000 * Does this product have an authorization key registered and loaded? Y If the Product Authorization Key (PAK) information is registered and loaded, type YES and press . If the information is not registered and loaded, type NO and press . In either case, the installation procedure continues. ________________________Note ________________________ Be sure to register and load the PAK information before starting SNA Server. _____________________________________________________ Installing the SNA Server 2-5 Step 6: Select installation options. * Do you want to purge files replaced by this installation [YES]? The directories SYS$COMMON:[SNAVMS$], SYS$HELP, SYS$LIBRARY, SYS$MESSAGE, SYS$SYSTEM, and SYS$LOADABLE_IMAGES could contain previous versions of SNA Server files. These files are replaced with new files during the installation, but the old files are not automatically purged. Purging is recommended. In response to the purging prompt, press to purge the files, or type NO to keep them. Either way, the installation continues. VMSINSTAL then displays the following message: %VMSINSTAL-I-RESTORE, Restoring product saveset B... Step 7: Insert subsequent installation kit volumes. %BACKUP-I-READYREAD, mount volume 2 on _CSA1: for reading Enter "YES" when ready: YES If necessary, VMSINSTAL prompts you to insert the next volume and waits for you to type YES after inserting it. If you type NO, VMSINSTAL displays the prompt again. Step 8: Read informational messages. %SNAVMS-I-NOMORQUES, there are no more questions %SNAVMS-I-PLEASE_WAIT, installation may take up to twenty minutes to complete Then, the SNA Server installation procedure produces a number of informational messages that report on the progress of the installation. The following message tells you that all files have been copied from the installation media: %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... The SYS$HELP:HELPLIB.HLB file is updated to include the new versions of the SNA_VMS HELP text. If the installation procedure is successful, the new or modified files are moved to their target directories. Appendix A lists the files and their location. 2-6 Installing the SNA Server If you typed YES in response to the prompt that requests a file purge (step 6), previous versions of the SNA Server files are now purged. Step 9: End the installation procedure. Installation of SNASERV completed at 12:34 VMSINSTAL procedure done at 12:34 $ LOGOUT SYSTEM logged out at 17-JAN-2000 12:34:00.00 When the product installation procedure is complete, you can install more products, run the SNA Server configuration program, or log out (as shown here.) If you removed any media from the console drive before the installation, you should replace it now. Appendix B contains a sample installation procedure. VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are continuing to use the system manager's account and want to restore these symbols, log out and log in again. Installing the SNA Server 2-7 3 ________________________________________________________________ Configuring the SNA Server After installation is complete, you then configure the SNA Server software. This chapter explains how to configure your Compaq SNA Server for OpenVMS (SNA Server) software. 3.1 Configuration Requirements After SNA Server is installed, you configure the software by running the configuration procedure. Before configuring SNA Server, fill out the configuration questionnaires with the following information: o Node name. The node name of the cluster member on the OpenVMS cluster system. Has a maximum of 6 letters. o Line characteristics. For SDLC lines, defines the physical characteristics (such as line duplex and signalling) of the communications line connecting your OpenVMS system to the IBM communications controller. The values for these parameters must match those used on the IBM system. Refer to the Compaq SNA Server for OpenVMS Guide to IBM Parameters or your IBM systems programmer for additional information. For X.25 lines, line definition is done using the X.25 for OpenVMS software product. The X.25 for OpenVMS configuration must be compatible with your network subscription and the IBM NPSI configuration (see the X.25 for OpenVMS Configuration manual and the DECnet- Plus Management Guide). o Circuit characteristics. For SDLC lines, defines the characteristics of the SDLC circuit, such as tributary address and XID number. The values for these parameters must match those used on the IBM system. Refer to the Compaq SNA Server for OpenVMS Guide to Configuring the SNA Server 3-1 IBM Parameters or your IBM systems programmer for additional information. For X.25 lines, defines the characteristics of the X.25 virtual circuit, such as local and remote DTE, network name, type of calls and reverse charging. The values for these parameters must match those defined in X.25 for OpenVMS and on the IBM system. Refer to the X.25 for OpenVMS Configuration manual, Compaq SNA Server for OpenVMS Guide to IBM Parameters, and your IBM systems programmer for additional information. o PU characteristics. Defines the characteristics of the SNA Server physical unit (PU), such as maximum session number and maximum segment size. The values for these parameters must match those used on the IBM system. Refer to the Compaq SNA Server for OpenVMS Guide to IBM Parameters or your IBM systems programmer for additional information. Note: these parameters are entered in the line characteristics configuration dialog. o Access names. Defines the session establishment parameters, such as IBM application name, LUs used for the session, logon mode table name, and user data. Refer to the Compaq SNA Server for OpenVMS Guide to IBM Parameters or your IBM systems programmer for additional information. 3.1.1 Configuration Questionnaire The configuration procedure asks you different questions depending on the type of communication line you choose. The following two sections list the configuration options for each line type followed by a discussion of the configuration options. Use the tables to record your responses that you will enter during the SNA Server configuration procedure. 3-2 Configuring the SNA Server 3.1.1.1 Configuration Parameters for SDLC Lines Table 3-1 is a blank configuration questionnaire for you to copy and fill out if you are using SDLC lines. Table_3-1_Configuration_Questionnaire_(SDLC_Lines)________ Configuration_Prompt__Sample_Response____Your_Response____ Which cluster member local node _______________ will run SNA Server? (OpenVMS Alpha cluster only) Will this node NO NO communicate over an X.25 network? How many LU 16 _______________ addresses available to this PU? What is the PU 265 _______________ segment size (decimal)? What is the circuit FULL _______________ duplex (HALF, FULL)? What is the station 40 _______________ address (2-digit hex)? What is the exchange DEC03790 _______________ ID (XID) number (8-digit hex)? What is the line- ZWcu, ZScu, ZYcu, _______________ id specification ZEcu, ZRA0 (devcu)? What is the line FULL _______________ duplex (HALF, FULL)? What is the line 19200 _______________ speed ? (continued on next page) Configuring the SNA Server 3-3 Table 3-1 (Cont.) Configuration Questionnaire (SDLC __________________Lines)__________________________________ Configuration_Prompt__Sample_Response____Your_Response____ Is the line a NO _______________ multidropped line? Is the line a NRZI- NO _______________ signalling line? (for all except DNSES)____________________________________________________ Cluster node name If you are installing and configuring SNA Server on an Alpha system on an OpenVMS cluster, write the node name of the system. X.25 network Always write NO if you are using SDLC lines to communicate with the IBM host. LU addresses available Write the highest LU address that the IBM host can activate for the PU. The maximum session number is a decimal number in the range of 1 to 255. It must correspond to the LU address as defined in the IBM LU macro LOCADDR operand, following the PU that describes SNA Server. Set the number only as high as you need. The higher the number you specify, the more OpenVMS system resources you will use. The SET ACCESS NAME LU LIST command defines a session or range of sessions for a given access name. The maximum session is this range must be equal to or less than the number defined by this parameter. PU segment size Write the maximum size of the SDLC frames, in bytes, that are sent between your OpenVMS system and the IBM communications controller. This value must be greater than or equal to the IBM ACF/NCP PU macro MAXDATA parameter. The larger the size, the more system memory will be used. 3-4 Configuring the SNA Server Circuit duplex Write FULL if the circuit will send and receive SDLC frames simultaneously. Write HALF if the circuit will send frames after the IBM host finishes sending the frames. The value you specify must correspond to the IBM ACF/NCP PU macro DATMODE parameter. Station address Write the SDLC station address for the PU. The station address value is a 2-digit hexadecimal number. It must correspond to the SDLC station address as defined in the IBM ACF/NCP PU macro ADDR parameter for leased lines, or in VTAM for dial-up lines. If you do not know what value to use, consult your IBM systems programmer. Exchange ID If you have a dial-up line, write the SDLC exchange ID (XID) associated with the circuit. The XID is exchanged between SNA Server and the IBM host before the PU is activated. This value is an 8-digit hexadecimal number and corresponds to the value of the IDBLK and IDNUM parameters on the IBM VTAM PU macro together, in that order. Line ID Write the line ID for the communications device using the following format: devcu dev Represents the device name (ZW, ZS, ZY, ZE, or ZR). c Represents the device's hardware controller. An alphabetic character (A-Z) corresponds to OpenVMS controllers A, B, and C, respectively. u Represents the device unit number (0, 1, 2, . . .). Table 3-2 contains valid line IDs for the Compaq communication devices. Configuring the SNA Server 3-5 Table 3-2 Communications Devices and Configuration __________Parameters______________________________________ Communications Device Duplex Signalling Device__________Name______Line_ID___Values____Values______ PBXDP ZWA0: ZWA0 FULL NORMAL ZWA1: ZWA1 HALF NRZI ZWA2: ZWA2 ZWA3: ZWA3 ZWA4: ZWA4 ZWA5: ZWA5 ZWA6: ZWA6 ZWA7: ZWA7 PBXDI ZSA0: ZSA0 FULL NORMAL ZSA1: ZSA1 NRZI ZSA2: ZSA2 ZSA3: ZSA3 DSYTI ZYA0: ZYA0 FULL NORMAL ZYA1: ZYA1 NRZI DNSES ZEA0: ZEA0 NORMAL SCC ZRA0: ZRA0 FULL NORMAL ______________________________________________NRZI________ Line duplex Write HALF if your line modem hardware and related line are configured for half-duplex. Half-duplex is typically found with dial-up lines. Write FULL if the line is dedicated to point-to-point, two-way, simultaneous connections using full-duplex modem hardware. Table 3-2 contains valid DUPLEX parameter values for the Compaq communications devices. Line speed Write in the speed of your line modem hardware and related line. Enter the line speed in bits per second. 3-6 Configuring the SNA Server NRZI signalling Write YES if the SDLC communications line will operate in NRZI (non-return-to-zero-inverted) mode. That is, the signals are interpreted as NRZI. If the line will operate in NRZI mode, the modems must also support NRZI operation. Write NO if the SDLC communications line will operate in normal (NRZ) mode. The value you specify must correspond with the IBM ACF/NCP LINE macro, NRZI operand. Table 3-2 contains valid SIGNALLING parameter values for the Compaq communications devices. Multidropped line Write YES if your SNA Server system is a multidrop configuration (multiple SDLC stations on a physical line). Write NO if your SNA Server system is the only device on the line. 3.1.1.2 Configuration Parameters for X.25 Lines Table 3-3 is a blank configuration questionnaire for you to copy and fill out if you are using X.25 lines. Table_3-3_Configuration_Questionnaire_(X.25_Lines)________ Configuration_Prompt__Sample_Response____Your_Response____ Which cluster member local node _______________ node will run SNA Server? (OpenVMS Alpha Cluster only) Will this node YES YES communicate over an X.25 network? How many LU 16 _______________ addresses available to this PU? What is the PU 265 _______________ segment size (decimal)? (continued on next page) Configuring the SNA Server 3-7 Table 3-3 (Cont.) Configuration Questionnaire (X.25 __________________Lines)__________________________________ Configuration_Prompt__Sample_Response____Your_Response____ Which calling OUTGOING _______________ direction? (INCOMING,OUTGOING) What is the network X25NET _______________ name? What is the address 38112 _______________ of the local DTE? What is the group GROUP1 _______________ name for the local DTE? (OUTGOING only) What is the address 91144 _______________ of the remote DTE? What is the exchange DEC03790 _______________ ID (XID) number (8-digit hex)? Will reverse NO _______________ charging be applied to outgoing calls? (OUTGOING_only)___________________________________________ Cluster node name If you are installing and configuring SNA Server on a system on an OpenVMS cluster, write the node name of the system. X.25 network Always write YES if you are using a packet switched data network (PSDN) to communicate with the IBM host. LU addresses available Write the highest LU address that the IBM host can activate for the PU (circuit). The maximum session number is a decimal number in the range of 1 to 255. It must correspond to the LU address as defined in the IBM LU macro LOCADDR operand, following the PU that describes SNA Server. Set the number as high as you need but no higher. A higher number uses more OpenVMS system resources. 3-8 Configuring the SNA Server PU segment size Write the maximum size of the SNA Path Information Units (PIU), in bytes, that are sent between your OpenVMS system and the IBM communications controller. This value must be greater than or equal to the IBM VTAM PU macro MAXDATA parameter. The larger the size, the more system memory will be used. Calling direction Write INCOMING if the X.25 virtual circuit will be used to establish an incoming SNA Server QLLC circuit. Write OUTGOING if the X.25 virtual circuit will be used to establish an outgoing SNA Server QLLC circuit. X.25 network name Write the name of the X.25 Access DTE Class entity supporting the connection. This DTE class should have a single member with a DTE address that matches the DTE address specified in the Local DTE Address parameter (see the next parameter description). The network name can consist of 1 to 16 characters. The value you specify must match a DTE Class entity you defined when you used SYS$SYSTEM:X25$CONFIGURE.COM to generate the X.25 NCL scripts. For outgoing calls, this name must also match an existing Template entity. For incoming calls, this name must also match an existing Filter entity. Local DTE address If defining the virtual circuit for incoming calls, write the network address of the local DTE. The DTE address value can consist of 1 to 16 characters. The value you specify must match the Called DTE value in the IBM VTAM PATH definition statement DIALNO operand. This DTE address must also match the single DTE in the DTE Class entity referenced by the X.25 network name parameter. If you are using the X.25 Relay facility, the local DTE address is the network address of the DTE used by the X.25 for OpenVMS Multihost node or X25router node for connection to the PSDN. You must specify either the local DTE address or the group name; you can also specify both. For outgoing calls, the local DTE address is for informational purposes only. Configuring the SNA Server 3-9 Group name If defining the virtual circuit for outgoing calls, write the name of the closed user group (CUG) to which the local DTE belongs. The group name value can consist of 1 to 16 characters. The value you specify must match the group parameter you defined when you used SYS$SYSTEM:X25$CONFIGURE.COM to generate the X.25 NCL scripts. For incoming circuits, specify the CUG in the X.25 Filter entity. Some PSDNs remove the CUG selection facility from the Incoming Call Packet under certain conditions. Consult your PSDN authority for more information. You must specify either the local DTE address or the group name; you can also specify both. Remote DTE address If defining the virtual circuit for outgoing calls, write the network address of the remote DTE. The DTE address value can consist of 1 to 16 characters. The local DTE uses this value to make outgoing calls. The value you specify must match the Calling DTE value in the IBM VTAM PATH definition statement DIALNO operand. Exchange ID Write the exchange ID (XID) associated with the circuit. The XID is exchanged between SNA Server and the IBM host before the PU is activated. This value is an 8- digit hexadecimal number and corresponds to the value of the IDBLK and IDNUM parameters on the IBM VTAM PU macro together, in that order. Reverse charging If defining the virtual circuit for outgoing calls, write YES if the remote DTE will be charged for calls placed by the local DTE. Write NO if the local DTE is charged for all outgoing calls to the remote DTE. ________________________Note ________________________ To control the acceptance or rejection of re- verse charging for any incoming calls, use X.25 for OpenVMS security. See the X.25 for OpenVMS 3-10 Configuring the SNA Server Configuration manual and the DECnet-Plus Management Guide. _____________________________________________________ 3.1.2 Access Names An access name is an optional name you define in the configuration file. Access name represents the session parameters required for access to an IBM system resource. Similar in function to an OpenVMS logical name, an access name provides an easy way for Compaq SNA access routine users to establish an SNA session. When an access name is specified by a Compaq SNA access routine, the corresponding session parameters are used to establish an SNA session; the access routine user must remember only the access name. An access routine can also specify an access name and explicit session parameters. In this case, the specified session parameters override the parameter values defined for the access name. Access names are defined in the configuration file SNAVMS$CFG_node-name.COM or in any alternate configuration file that you create and specify at startup. When SNA Server is started, the access names and their parameters are read from the configuration file and added to the SNA Server database. An access name and parameters remain in the database until one of the following events occurs: o You delete the access name by using the SNA Network Control Program (SNANCP) utility. o You restart SNA Server. Restarting SNA Server modifies an access name if an existing access name and the modified parameters are defined in the configuration file. o You reboot the OpenVMS operating system. Rebooting OpenVMS deletes all access names. If the access name is defined in the configuration file, the name and parameters are added to the database. Configuring the SNA Server 3-11 3.1.3 Access Name Parameters The configuration procedure asks you to supply information about access names. Table 3-4 is a blank access name questionnaire for you to copy and fill in. Record the access name parameters you will enter during the SNA Server configuration procedure as they are discussed in the following pages. If you do not enter any access names during the con- figuration procedure, you can add access names after configuration by editing the configuration file. ________________________Note ________________________ The configuration procedure always creates one access name, SNAVP. Do not delete this access name because it is used by the SNA Server Installation Verification Program. _____________________________________________________ 3-12 Configuring the SNA Server Table_3-4_Configuration_Questionnaire_(Access_Names)______ Configuration_Prompt__Sample_Response____Your_Response____ Access name? (1-16 TSO _______________ characters) LU list for this 3,6-10 _______________ access name? (numbers or ranges) Application name? TSOL _______________ (1-8 characters) Logon mode table? DECLOG _______________ (1-8 characters) User data? (quoted "password" _______________ string, 1-32 characters) Access name? (1-16 TSO _______________ characters) LU list for this 3,6-10 _______________ access name? (numbers or ranges) Application name? TSOL _______________ (1-8 characters) Logon mode table? DECLOG _______________ (1-8 characters) User data? (quoted "password" _______________ string, 1-32 characters) Access name? (1-16 TSO _______________ characters) LU list for this 3,6-10 _______________ access name? (numbers or ranges) (continued on next page) Configuring the SNA Server 3-13 Table 3-4 (Cont.) Configuration Questionnaire (Access __________________Names)__________________________________ Configuration_Prompt__Sample_Response____Your_Response____ Application name? TSOL _______________ (1-8 characters) Logon mode table? DECLOG _______________ (1-8 characters) User data? (quoted "password" _______________ string, 1-32 characters)_______________________________________________ 3-14 Configuring the SNA Server The following list describes the access name keyword parameters; ACCESS NAME is the only required parameter. Access name The access name represents a list of session establishment parameters. The access name is a string of up to 16 characters that can include alphanumeric characters and the following special characters: dollar sign ($) and underscore (_). Some Compaq SNA access routines limit you to a maximum of 8 characters in an access name. PU The PU name identifies the PU that is used when estab- lishing a session. For SNA Server, the PU name is always SNA-0. LU list The LU list parameter represents a list of possible LUs that can be assigned to a Compaq SNA access routine participating as a SLU in a session with an IBM host. When you establish a session, the first available session address is assigned. You can specify (in decimal) up to eight separate addresses, or ranges of addresses. Each address or range of addresses is separated from the next one by a comma (no space); for example, 9-10,1,11-24. The list you define should correspond with the list defined for the IBM PLU on the physical unit with which you are communicating. The values you supply must also be consistent with the LU LIST parameter to the SET PU command in the configuration file. You can specify up to 255 LUs for each access name. You can specify the same LU address under multiple access names. IBM addresses might be assigned to specific applications. Check with your IBM systems programmer for the correct ranges. Application The application name represents the VTAM application name of the program on the IBM system that you want to access. This name is identical to the PLU name on the IBM host. The application name is a string of up to 8 characters that can include alphanumeric characters and the following special characters: dollar sign ($), pound sign (#), and Configuring the SNA Server 3-15 at sign (@). The first character in an application name should not be a numeral. 3-16 Configuring the SNA Server Logon mode The logon mode name represents the name of the entry in the logon mode table defined on the IBM host. The name is sent to the IBM host to obtain redefined characteristics for the session being established. The logon mode name has the same format as the application name. See the Compaq SNA Server for OpenVMS Guide to IBM Parameters or your IBM systems programmer for further information. User data The user data represents access control information that is sent to the IBM host for the session being established. Typically, the user data parameter contains privileged information, usually a password. The information you enter depends on the IBM application with which you are communicating. The user data is a string of up to 32 characters that can include alphanumeric characters and the following special characters: dollar sign ($), pound sign (#), and at sign (@). If you need to specify characters other than those listed, you must enclose the characters in double quotation marks (for example, "&&"). ________________________Note ________________________ The use of the data field might compromise the security of your SNA Server-to-IBM connection. In the form of a password, user data provides access to a specified account. _____________________________________________________ Note Specifies additional information (up to 30 characters) that is part of the SHOW SUMMARY display. You can use the note to provide information about the IBM application to which the access name refers. Specify the text of your note within double quotation marks. You should confer with an IBM systems programmer to determine what values you need to specify for most of the access name parameters. Some IBM applications do not require you to specify all the parameters to connect to Configuring the SNA Server 3-17 the IBM system. Once you have determined the values you need, keep a printed copy for future reference. 3.2 The SNA Server Configuration Dialog This section contains excerpts from the configuration procedure and explains each step. To abort the configuration procedure at any time, press . When you press , the configuration procedure returns you to DCL level. If you want to retry the configuration procedure after pressing , you must proceed from step 2. Most questions are followed by a default value. To accept the default value, press . If the default is empty ( [] ), this indicates that the parameter has no default but does not need to be specified. If no default is shown, you must enter a value. ________________________Note ________________________ If upgrading to a new version of SNA Server, you must run the configuration procedure. _____________________________________________________ Step 1: Log in to a privileged account, and set your default device and directory to SYS$COMMON:[SNAVMS$]. Username: SYSTEM Password: $ SET DEFAULT SYS$COMMON:[SNAVMS$] Step 2: Run the configuration procedure. ________________________Note ________________________ WANDRIVER and Network device drivers must be loaded before starting the SNAVMS$CONGIGURE. _____________________________________________________ 3-18 Configuring the SNA Server $ @SNAVMS$CONFIGURE Command file to configure the SNA Server product Executing on 17-JAN-2000 12:34:32.42. Enter a question mark (?) at any time for help. Enter CONTROL-Z at any time to abort. Step 3: Select the cluster node. Which OpenVMS Alpha cluster member node will run SNA Server? [local system] : If you are installing SNA Server software on an OpenVMS Alpha cluster system, the configuration procedure requires you to identify the node in the OpenVMS Alpha cluster on which the communications device is installed and on which SNA Server will run. Press if the local system node name (the system you are currently logged in to) is correct, or type the node name of the system you want. Step 4 (SDLC Lines): Select configuration options. The configuration procedure prompts you for site-specific information about the connection between your SNA Server node and the IBM SNA network. Use the information you entered on the configuration questionnaire (see Table 3-1) as the responses to the following prompts. Will this node communicate over an X.25 network? [NO] : Press because your node will not communicate with the IBM host over an X.25 network. How many LU addresses available to this PU? [128] : Press if the number of LU addresses is correct, or type the correct number of LU addresses. What is the PU segment size (decimal)? [265] : Press if the segment size from SNA Server to the IBM host is correct, or type the correct segment size. What is the circuit duplex (HALF, FULL)? [FULL] : Specify how the data is transferred over the circuit. Press if the default circuit duplex is correct, or type the correct circuit duplex. What is the station address (2-digit hex)? [40] : Configuring the SNA Server 3-19 Press if the station address is valid for the SNA Server PU, or type the correct station address. What is the exchange ID (XID) number (8-digit hex)? [] : If you are using a point-to-point communications line, press . If you are using a dial-up communications line, type the XID and press . Available Synchronous Communications Ports: 1. ZYA0 - DSY-0-0 2. ZYA1 - DSY-0-1 3. ZRA0 - SSCC-0-0 What is the line-id specification ? [ZYA0] : Press if the default communications device is valid or type the communications device you choose to use, for example ZYA1 or ZRA0. If you have not installed the WANDD device drivers prior to running the configuration procedure, the procedure will not display any synchronous communication devices. You must install the WANDD device drivers prior to running the configuration procedure (see Section 1.6.2). What is the line duplex (HALF, FULL)? [FULL] : Specify the physical characteristics of the line connecting your OpenVMS system to the IBM host. Press if the default line duplex is correct, or type the correct line duplex. What is the line speed? : Specify the speed of the line in bits per second. For example, for 19.2Kb per second line, enter the value 19200. There is no default for this value, you must enter a value. Is the line a multidropped line? [NO] : 3-20 Configuring the SNA Server The SNA Server software can communicate on the same line as other IBM devices. Type YES and press if SNA Server is multidropped on a line, or press if it is the only device on the line. Is the line a NRZI-signalling line? [NO] : Press if the line will not be operated in non- return-to-zero-inverted (NRZI) mode. Type YES if you are using NRZI signalling on the communications line. Step 4 (X.25 Lines): Select configuration options. The configuration procedure prompts you for site-specific information about the connection between your SNA Server node and the IBM SNA network. Use the information you entered on the configuration questionnaire (see Table 3-3) as the responses to the following prompts. Which cluster member node will run SNA Server [local system] : If you are installing SNA Server software on a cluster system, the configuration procedure requires you to identify the node in the VMScluster on which the communications device is installed and on which SNA Server will run. Press if the local system node name (the system you are currently logged in to) is correct, or type the node name of the system you want. Will this node communicate over an X.25 network? [NO] : YES Type YES and press because your node will communi- cate with the IBM host over an X.25 network. How many LU addresses available to this PU? [128] : Press if the number of LU addresses is correct, or type the correct number of LU addresses. What is the PU segment size (decimal)? [265] : Press if the segment size from SNA Server to the IBM host is correct, or type the correct segment size. Which calling direction (INCOMING,OUTGOING)? [OUTGOING] : Configuring the SNA Server 3-21 Press if the X.25 circuit will make outgoing calls. Type INCOMING and and press if the X.25 circuit will accept incoming calls. What is the network name? : Type the name of the X.25 Access DTE Class entity supporting the connection. This DTE class should have a single member with a DTE address that matches the DTE address specified in the Local DTE Address parameter (see the next parameter description). The network name can consist of 1 to 16 characters. ________________________Note ________________________ The value you specify must match a DTE Class entity you defined when you used SYS$SYSTEM:X25$CONFIGURE.COM to generate the X.25 NCL scripts. Also, the name of the DTE Class entity, the Filter entity, and the Template entity must be identical. _____________________________________________________ What is the address of the local DTE? [] : Type the network address of the local DTE receiving incoming calls, and press . This DTE address must match the single DTE in the DTE Class entity referenced by the X.25 network name parameter. For outgoing calls, this parameter is for informational purposes only. What is the group name for the local DTE? : Type the name of the closed user group (CUG) to which the local DTE belongs, and press . The configuration procedure does not ask this question for incoming calls. What is the address of the remote DTE? [] : For outgoing calls, type the address of the remote DTE you are calling, and press . For incoming calls, this parameter is for informational purposes only. What is the exchange ID (XID) number (8-digit hex)? : 3-22 Configuring the SNA Server Type the correct XID to exchange with the IBM host when establishing a session, and press . Will reverse charging be applied to outgoing calls? [NO] : Press if the local DTE will not make outgoing calls or if you want to charge the local DTE for outgoing calls. Type YES if you want to charge the remote DTE for outgoing calls from the remote DTE. Step 5: Specify access name information. Next, the configuration procedure displays the following message: You may now enter any access names that you wish to create. Enter RETURN at the ACCESS NAME prompt when finished. Access name? (1-16 characters) [] : Type an access name with which to associate a set of session establishment parameters, and press . If you are finished entering access names or do not want to enter any at this time, press . In this case, the configuration procedure skips to file cleanup (see step 6). Sessions for this access name? (numbers or ranges) [1-128] : Type the LUs available for the access name, and press . The LUs are numbers or ranges of numbers separated by commas; for example, 1-4,6,8,10-15. Press if you do not want to designate specific LUs for this access name. Application name? (1-8 characters) [] : Type the application name for the access name, and press . Press if you do not want to specify an application name for this access name. Logon mode table? (1-8 characters) [] : Type the name of the entry in the logon mode table for the access name, and press . Configuring the SNA Server 3-23 Press if you do not want to specify a logon mode table name for this access name. User data? (quoted string, 1-32 characters) [] : Type any user data for the access name, and press . Enclose any user data in double quotation marks; for example, "PASSWORD". Press if you do not want to specify user data for this access name. Next, the configuration procedure displays the following message: The configuration file SYS$COMMON:[SNAVMS$]SNAVMS$CFG_node-name.COM;1 was created on 17-JAN-2000 12:58:32.42. The configuration file was created. Step 6: Clean up old versions of the configuration file. During configuration, the files listed in Table 3-5 are placed on your system. You can find them in the indicated directory. Table_3-5_File_Locations_After_Configuration______________ File_Name_________Location______Description_______________ SNAVMS$AUTHORIZE_ SYS$COMMON: SNANCP user authorization node-name.COM [SNAVMS$] file. SNAVMS$CFG_ SYS$COMMON: SNA Server configuration node-name.COM [SNAVMS$] file, containing line, circuit, and access name specifications. This file is used by default when starting SNA Server. (continued on next page) 3-24 Configuring the SNA Server Table_3-5_(Cont.)_File_Locations_After_Configuration______ File_Name_________Location______Description_______________ SNAVMS$DATALINK_ SYS$COMMON: Command procedure for STARTUP_node- [SNAVMS$] creating the Frame link name.COM entity and modem connect line during SNA Server startup. (This file is empty for systems using ________________________________X.25_data_lines.)_________ The value node-name is the SNA Server node name you typed in response to the first configuration prompt. In a non- OpenVMS Alpha cluster environment, the value of node-name can be 0. If the SYSGEN parameter SCSNODE is changed any time after initially configuring SNA Server (for example, a stand- alone node is now an OpenVMS Alpha cluster node), rerun the SNAVMS$CONFIGURE.COM procedure and type the correct node name. Alternatively, you can rename the configuration command procedure, load device command procedure and authorization command procedure with the correct node name. For example, you might rename the file SNAVMS$CFG_ 0.COM file SNAVMS$CFG_MYNODE.COM. All three files must use the same value for node-name. If previous versions of the SNAVMS$CFG_node-name.COM file are on your system, the following question is displayed: Earlier versions of SYS$COMMON:[SNAVMS$]SNAVMS$CFG_node-name.COM exist. Do you wish to purge these files [NO]? Press to keep the files, or type YES to purge them. Next, SNA Server displays the following message to indicate that the command procedure to load the device driver was created: The modem startup file SYS$COMMON:[SNAVMS$]SNAVMS$DATALINK_ STARTUP_node-name.COM;1 was created on 17-JAN-2000 13:05:32.42. Configuring the SNA Server 3-25 If previous versions of the SNAVMS$DATALINK_STARTUP_node- name.COM file are on your system, the following question is displayed: Earlier versions of SYS$COMMON:[SNAVMS$]SNAVMS$DATALINK_ STARTUP_node-name.COM exist. Do you wish to purge these files [NO]? Press to keep the files, or type YES to purge them. Next, SNA Server displays the following message to indicate that the authorization file was created: The authorization file SYS$COMMON:[SNAVMS$]SNAVMS$AUTHORIZE_node-name.COM;1 was created on 17-JAN-2000 13:10:32.42. If a previous version of the SNAVMS$AUTHORIZE_node- name.COM file is on your system, the following message is displayed: The authorization file SYS$COMMON:[SNAVMS$]SNAVMS$AUTHORIZE_node-name.COM exists; no new authorization file is created. Step 7: Start the SNA Server. Next, the configuration procedure displays the following prompt: Do you wish to start the SNA Server product now [YES]?: Press to start SNA Server if all of the following apply: 1. You have started DECnet. 2. You configured and loaded the desired WANDRIVER and WAN device drivers. 3. You are running the configuration procedure from the SYSTEM account or are an authorized user (see the chapter on SNA Server security in Compaq SNA Server for OpenVMS Management). 4. You are satisfied with the responses you gave to the previous questions If you do not want to start SNA Server at this time, type NO and press ; this ends the configuration procedure. 3-26 Configuring the SNA Server If you chose to start the SNA Server product, the configuration procedure now calls the start-up procedure. @SYS$COMMON:[SNAVMS$]SNAVMS$STARTUP.COM Compaq SNA Server for OpenVMS V1.0 Startup begins : 17-JAN-2000 13:11:32.42 Node 0 Frame Link ZYA0 at 2000-01-17-14:11:57.587-04:00I1.537 . . . %LES-I-LOADING, loading SNAVMS$ component SNA$DECNET_ALT from SYS$COMMON:[SNAVMS $]SNA$DECNET_ALT.EXE;58 %LES-I-LOADING, loading SNAVMS$ component SNA$DR from SYS$COMMON:[SNAVMS$]SNAVMS $DR.EXE;57 %LES-I-LOADING, loading SNAVMS$ component SNA$SDLC from SYS$COMMON:[SNAVMS$]SNAV MS$SDLC.EXE;36 %LES-I-LOADING, loading SNAVMS$ component SNA$QLLC from SYS$COMMON:[SNAVMS$]SNAV MS$QLLC.EXE;28 %LES-I-LOADING, loading SNAVMS$ component SNA$PC from SYS$COMMON:[SNAVMS$]SNAVMS $PC.EXE;25 %SNAACP-S-STARTED, SNA Server V1.0, device _SNA0: mounted SNA Server V1.0 Startup complete: 17-JAN-2000 13:15:32.42 Step 8: Run the Installation Verification Procedure. After SNA Server is started, the configuration procedure asks the following question: Do you wish to run the SNAVMS$IVP program now [YES]? The Installation Verification Procedure (IVP) runs tests; these check whether the installation and configuration procedures were successful and verify the connection between the SNA Server software and the IBM SNA network. Press to run the IVP. The IBM host must activate the SNA Server line, PU, and LUs before you can run the IVP. If you do not want to run the IVP, type NO. If you chose to run the IVP, the configuration procedure now calls the IVP to verify the connection between the SNA Server software and the IBM SNA network. Configuring the SNA Server 3-27 @SYS$COMMON:[SYSTEST]SNAVMS$IVP.COM SNA Server V1.0 Installation Verification Procedure (C) 1999 Electronic Data Systems Corporation. All Right Reserved. (C) 1999 Digital Equipment Corporation. All Rights Reserved. THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED . . . CONREQREJ The connection to VTAM was successful; however, the session was rejected because VTAM did not recognize the application selected. The SNAVMS$IVP program ran successfully and connected to VTAM. Checking of other Compaq SNA access routine products should now proceed. If the IVP does not run successfully, see Section 3.3.5. Step 9: End the configuration procedure. The configuration procedure completes with a reminder to insert the software startup file in SYS$MANAGER:SYSTARTUP_ VMS.COM. You should add the following command to SYS$MANAGER:SYSTARTUP_VMS.COM: $ @SYS$COMMON:[SNAVMS$]SNAVMS$STARTUP Finished SNA Server product configuration At 17-JAN-2000 13:20:32.42 $ LOGOUT SYSTEM logged out at 17-JAN-2000 13:20:35.42. When the product configuration is complete, you can do other work, or you can log out (as shown in the preceding example). 3-28 Configuring the SNA Server Figure 3-1 is a graphic summary of the SNA Server con- figuration. Appendix B contains two sample configuration procedures: one for SDLC lines and one for QLLC lines. 3.3 After Configuration SNA Server is now configured and is available for use with the DECnet SNA access routines. After configuration, you need to do the following tasks: o Authorize users. o Configure SNA Server for other nodes in the cluster. o Update DCL tables for all nodes that have SNA Server configured. o Start SNA Server, if not done during configuration or for other nodes in the cluster. o Run the IVP, if not done during configuration or for other nodes in the cluster. o Set user account quotas. You might also perform other tasks: o Edit the system startup file. o Edit the configuration file. 3.3.1 Authorizing Users SNA Server uses privileged usernames to control access to certain functions. See the chapter on SNA Server security in Compaq SNA Server for OpenVMS Management. Configuring the SNA Server 3-29 3.3.2 Configuring SNA Server for Other Cluster Nodes If you are going to use SNA Server on other nodes in a cluster, each node must have the following: o a hardware communications device o SNA Server configured See Section 3.2 for instructions on configuring the SNA Server software. 3.3.3 Updating DCL Tables After installing SNA Server on the OpenVMS Alpha cluster system, update the DCL tables on each node in the cluster that will run SNA Server. Type the following command line: $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES 3.3.4 Starting SNA Server If you want to run the SNA Server start-up procedure separately, you must have completed the following: 1. Logged into the SYSTEM account or be an authorized user (see the chapter on SNA Server security in Compaq SNA Server for OpenVMS Management. 2. Started DECnet. 3. Configured and started the WAN device drivers. Then type the following command line: $ @SYS$COMMON:[SNAVMS$]SNAVMS$STARTUP.COM file-spec file-spec Represents the name of the configuration file of your choice. The default file is SYS$COMMON:[SNAVMS$]SNAVMS$CFG_ node-name.COM. If you try to start SNA Server on a node in an OpenVMS Alpha cluster other than the node on which the SNA Server hardware device is installed, the following error message is displayed: SNA Server is not configured for this node. Execute SNAVMS$STARTUP from these nodes: node-list 3-30 Configuring the SNA Server node-list Refers to the node(s) on which the SNA Server commu- nications hardware device and SNA Server software are installed. If SNA Server has been started and you want to restart it, run the start-up procedure. If any error messages are displayed during startup, see Compaq SNA Server for OpenVMS Problem Solving for a list of error messages and solutions. If you are unable to start the product, follow the troubleshooting steps in Chapter 2 of Compaq SNA Server for OpenVMS Problem Solving. 3.3.5 Running the Installation Verification Procedure The Installation Verification Procedure (IVP) is usually run at configuration. Compaq recommends, however, that you run the IVP after you make changes to the physical connection (for example, adding new modems) or after the IBM systems programmer makes changes to the host system software. The program verifies the connection between the SNA Server software and the IBM SNA network. To run the IVP, type the following command: $ @SYS$TEST:SNAVMS$IVP If you receive either of the following messages, the verification program has completed successfully: CONREQREJ CONREQREJ is a normal completion code for SNAVMS$IVP. It indicates that your line is active and that SNAVMS$IVP has succeeded in making a connection to VTAM. The connect request is rejected because the default $DIGITAL application is selected, and no application named $DIGITAL is normally available on the IBM host. The application name $DIGITAL is the default application name used by SNAVMS$IVP. Configuring the SNA Server 3-31 NORMAL The connection to VTAM was successful and the application name used by the IVP was recognized by VTAM. If the IVP is not successful, you must solve the problem before continuing with the installation. The following default values used by the IVP might be the source of your problem: __________________________________________________________ Parameter________Default_Value____________________________ SESSION 1 APPLICATION $DIGITAL PU SNA-0 ACCESS_NAME______SNAVP____________________________________ For example, if you receive an error message stating that a session is not available (SESNOTAVA), you might override the default value of 1 for a session in the IVP. In this case, perform the following steps: 1. Select a session number that you know has not been assigned, and change the session default with a logical name as follows: $ DEFINE SNA$VP_SESSION n 2. Run the IVP to see whether the session default change solved your problem. You can also use a logical name to change the default application name from $DIGITAL to another application name. To determine whether an application is available through VTAM, change the default name of $DIGITAL to the name of the application you want to check, as follows: $ DEFINE SNA$VP_APPLICATION newname Then run the IVP. If you receive a NORMAL message, you know that the application is available through VTAM. If you receive a CONREQREJ message, you know that the application is not available through VTAM. If you are still unable to run the IVP successfully, refer to Compaq SNA Server for OpenVMS Problem Solving. 3-32 Configuring the SNA Server 3.3.6 User Account Quotas and Privileges To use SNA Server, each Compaq SNA access routine user must have TMPMBX and NETMBX privileges and the following minimum requirements: o AST limit (ASTLM): 20 o Buffered I/O quota limit (BIOLM): 130 o Buffered I/O byte count quota limit (BYTLM): 76,800 o Direct I/O quota limit (DIOLM): 130 Use the OpenVMS Authorize Utility (AUTHORIZE) to compare the current values of these quotas with the requirements for SNA Server. For example, the account used in the following example is the SYSTEM account: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM To change the values of these quotas, use the OpenVMS Authorize Utility's MODIFY command. For more information, see the OpenVMS System Management Utilities Reference Manual. 3.3.7 Editing the System Startup File You must edit the system startup file to provide for automatic startup of SNA Server when your system is rebooted. Add the command line that starts SNA Server to the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM. You must position this new command line after the line that invokes the network startup command procedure. The following example shows the network startup command line followed by the startup command line for SNA Server: ________________________Note ________________________ In the DECnet-Plus environment the network starts automatically before you execute the startup command. _____________________________________________________ Configuring the SNA Server 3-33 $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$COMMON:[SNAVMS$]SNAVMS$STARTUP.COM 3.3.8 Editing the Configuration File You must edit the SNA Server configuration file to add information or to correct any errors that you discover during the configuration procedure. After you edit the configuration file, run the start-up procedure to start SNA Server. Compaq SNA Server for OpenVMS Management describes the editing procedure, provides a sample configuration file, and discusses the reconfiguration and restart process. 3-34 Configuring the SNA Server A ________________________________________________________________ Files Installed During Installation Table_A-1_Files_Added_During_Installation_of_SNA_Server_________ File_Name_______________Location________________Description_____ SNA$DECNET.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNA$DECNET_ALT.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$CIRCUIT.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$CONFIGURE.COM SYS$COMMON:[SNAVMS$] Command procedure for configuring SNA Server SNAVMS$CONFIGURE.TLB SYS$COMMON:[SNAVMS$] Configuration procedure HELP text file SNAVMS$DR.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$EVC.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$EVL_STARTUP.COM SYS$COMMON:[SNAVMS$] Command procedure to start event log listener (continued on next page) Files Installed During Installation A-1 Table_A-1_(Cont.)_Files_Added_During_Installation_of_SNA_Server_ File_Name_______________Location________________Description_____ SNAVMS$GASVMS_ SYS$COMMON:[SNAVMS$] Command STARTUP.COM procedure to start the TCP/IP adaptor. SNAVMS$GASVMS.EXE SYS$SYSTEM Process image for the TCP/IP adaptor. SNAVMS$HS.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$LINE.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$LUSVC.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$NDM.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$NML.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$PC.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$PUSVC.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$GAS.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$QLLC.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$SDLC.EXE SYS$COMMON:[SNAVMS$] Internal module loaded by ACP SNAVMS$SNDRIVER.EXE SYS$COMMON:[SNAVMS$] SNA Server software driver SNAVMS$STARTUP.COM SYS$COMMON:[SNAVMS$] Command procedure to start SNA Server (continued on next page) A-2 Files Installed During Installation Table_A-1_(Cont.)_Files_Added_During_Installation_of_SNA_Server_ File_Name_______________Location________________Description_____ SNAVMS$IVP.COM SYS$COMMON:[SYSTEST] Verification command procedure SNAVMS$IVP.EXE SYS$COMMON: Verification [SYSTEST.SNAVMS$IVP] program SNAVMS$IVP.HLB SYS$COMMON: HELP library [SYSTEST.SNAVMS$IVP] for verification program SNAVMS$IVPMSG.EXE [SYSTEST.SNAVMS$IVP] Verification program message file SNANCP.HLB SYS$HELP SNANCP HELP library SNAVMS$010.RELEASE_ SYS$HELP Release notes NOTES for SNA Server CTF$PU_ANALYZE.EXE SYS$LIBRARY CTF PU trace analyzer CTF$QLLC_ANALYZE.EXE SYS$LIBRARY CTF QLLC trace analyzer CTF$SDLC_ANALYZE.EXE SYS$LIBRARY CTF SDLC trace analyzer CTF$SNAVMS_ TRACEPOINTS.SYS$LIBRARY SNA Server CTF tracepoints SNAVMS$LIB.EXE SYS$LIBRARY Internal module loaded by ACP SNAEVLMSG.EXE SYS$MESSAGE Event log listener message file SNANCPMSG.EXE SYS$MESSAGE SNANCP message file SNAVMS$LIBMSG.EXE SYS$MESSAGE SNA Server message file (continued on next page) Files Installed During Installation A-3 Table_A-1_(Cont.)_Files_Added_During_Installation_of_SNA_Server_ File_Name_______________Location________________Description_____ SNAEVL.EXE SYS$SYSTEM Process image for event log listener SNANCP.EXE SYS$SYSTEM SNA Network Control Program utility (SNANCP) SNAVMS$LES_CONTROL.DAT SYS$SYSTEM Internal module ________________________________________________loaded_by_ACP___ A-4 Files Installed During Installation B ________________________________________________________________ Sample Installation and Configuration This appendix contains a sample Compaq SNA Server for OpenVMS (SNA Server) installation, a sample SNA Server configuration for SDLC lines, and a sample SNA Server configuration for QLLC lines. Sometimes, the installation procedure and the configuration procedure are modified in maintenance updates of this product. Because this installation guide is not usually revised for maintenance updates, be sure to read the release notes before you install and configure this product. The release notes describe any significant changes in the installation and configuration that vary from these samples. B.1 Sample Installation The following is a sample installation for SNA Server. $ set default sys$update $ @vmsinstal snaserv010 CSA1 OPTIONS N OpenVMS AXP Software Product Installation Procedure V7.1 It is 7-JAN-2000 at 18:16. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: SNASERV V1.0 Beginning installation of SNASERV V1.0 at 18:16 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: Sample Installation and Configuration B-1 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: * Queue name [SYS$PRINT]: Job SNAVMS$010 (queue SYS$PRINT, entry 142) started on LPA0 * Do you want to continue the installation [NO]? yes %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Product: SNA-SERVER Producer: DEC Version: 1.0 Release Date: 01-JANUARY-2000 * Does this product have an authorization key registered and loaded? YES * Do you want to purge files replaced by this installation [YES]? %SNASERV-I-NOMORQUES, there are no more questions %SNASERV-I-PLEASE_WAIT, installation may take up to twenty minutes to complete %SNASERV-I-CLEANUP, deleting previous versions of SNA Server files %SNASERV-I-INSTALL, adding new SNA Server files %VMSINSTAL-I-RESTORE, Restoring product save set B ... The Compaq SNA Server for OpenVMS files have been copied to the system disk. If you have not installed the communication hardware for the connection to the IBM SNA network, please do so now. After the communication hardware has been installed, SNA Server must be configured. You should execute the following command to configure SNA Server: @SYS$COMMON:[SNAVMS$]SNAVMS$CONFIGURE This step creates the SNA Server configuration files, completing the installation. You can start SNA Server and execute the Installation Verification Procedure (SNAVMS$IVP) at the end of the configuration procedure; the procedure will prompt you. For current information about Compaq SNA Server for OpenVMS, type or print the file SNAVMS$010.RELEASE_NOTES, which is supplied by this installation. B-2 Sample Installation and Configuration %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of SNASERV V1.0 completed at 18:19 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]SNASERV010.VMI_DATA VMSINSTAL procedure done at 18:20 $ B.2 Sample Configuration (SDLC Lines) The following is a sample SNA Server configuration for SDLC lines. The answers to each prompt are for demonstration purposes only and will probably differ from the answers that you supply during your configuration procedure. $ set default sys$common: [SNAVMS$] $ @snasvms$configure Command file to configure the SNA Server product Executing on 7-JAN-2000 10:14:21.76. Enter a question mark (?) at any time for help. Enter CONTROL-Z at any time to abort. Will this node communicate over an X.25 network? [NO] : How many LU addresses available to this PU? [128] : What is the PU segment size (decimal)? [265] : What is the circuit duplex (HALF, FULL)? [FULL] : What is the station address (2-digit hex)? [40] : What is the exchange ID (XID) number (8-digit hex)? : Available Synchronous Communication Ports: 1. ZYA0 - DSY-0-0 2. ZYA1 - DSY-0-1 3. ZRA0 - SSCC-0-0 What is the line-id specification ? [ZYA0] : What is the line duplex (HALF, FULL)? [FULL] : What is the line speed? : 9600 Is the line a multidropped line? [NO] : Is the line a NRZI-signalling line? [NO] : Sample Installation and Configuration B-3 You may now enter any access names that you wish to create. Enter RETURN at the ACCESS NAME prompt when finished. Access name? (1-16 characters) [] : TSO Sessions for this access name? (numbers or ranges) [1-128] : Application name? (1-8 characters) [] : TSOL Logon mode table? (1-8 characters) [] : DSILGMOD User data? (quoted string, 1-32 characters) [] : Access name? (1-16 characters) [] : The configuration file SYS$COMMON:[SNAVMS$]SNAVMS$CFG_VOYGER.COM;1 was created on 7-JAN-2000 14:11:45.94 The modem startup file SYS$COMMON:[SNAVMS$]SNAVMS$DATALINK_STARTUP_VOYGER.COM;1 was created on 7-JAN-2000 14:11:46.49 The authorization file SYS$COMMON:[SNAVMS$]SNAVMS$AUTHORIZE_VOYGER.COM;1 was created on 7-JAN-2000 14:11:46.80 Do you wish to start the SNA Server product now? [YES] : @SYS$COMMON:[SNAVMS$]SNAVMS$STARTUP.COM Compaq SNA Server for OpenVMS V1.0 Startup begins : 7-JAN-2000 14:11:56.36 Node 0 Frame Link ZYA0 at 2000-01-07-14:11:57.587-04:00I1.537 command failed due to: no such object instance Node 0 Frame Link ZYA0 at 2000-01-07-14:11:58.736-04:00I1.538 command failed due to: no such object instance Node 0 Modem Connect Line SDLC-0 at 2000-01-07-14:11:58.774-04:00I1.538 with Communications Port = ZYA0 Node 0 Modem Connect Line SDLC-0 at 2000-01-07-14:11:58.788-04:00I1.538 with Communications Port = ZYA0 Node 0 Modem Connect Line ZYA0 at 2000-01-07-14:11:58.799-04:00I1.538 B-4 Sample Installation and Configuration command failed due to: no such object instance Node 0 Modem Connect Line ZYA0 at 2000-01-07-14:11:58.810-04:00I1.538 command failed due to: no such object instance Node 0 Modem Connect at 2000-01-07-14:11:58.989-04:00I1.538 command failed due to: process failure Modem Connect Module entity already created Node 0 Modem Connect Line ZYA0 at 2000-01-07-14:11:59.003-04:00I1.538 Node 0 Modem Connect Line ZYA0 at 2000-01-07-14:11:59.342-04:00I1.538 Node 0 Modem Connect Line ZYA0 at 2000-01-07-14:11:59.352-04:00I1.538 Node 0 Modem Connect Line ZYA0 at 2000-01-07-14:11:59.361-04:00I1.538 Node 0 Modem Connect Line ZYA0 at 2000-01-07-14:11:59.369-04:00I1.538 Node 0 Frame at 2000-01-07-14:11:59.378-04:00I1.538 command failed due to: process failure The Frame Module already exists Node 0 Frame at 2000-01-07-14:11:59.386-04:00I1.538 Node 0 Frame Link ZYA0 at 2000-01-07-14:11:59.394-04:00I1.538 Sample Installation and Configuration B-5 Node 0 Frame Link ZYA0 at 2000-01-07-14:11:59.519-04:00I1.538 Characteristics Physical Line = Modem Connect Line ZYA0 Node 0 Frame Link ZYA0 at 2000-01-07-14:11:59.534-04:00I1.538 Characteristics Local Station Address = 40 Node 0 Frame Link ZYA0 at 2000-01-07-14:11:59.555-04:00I1.538 Characteristics Buffer Size = 265 Node 0 Frame Link ZYA0 at 2000-01-07-14:11:59.610-04:00I1.538 Node 0 Session Control Application 58 at 2000-01-07-14:12:30.684-04:00I1.541 Characteristics Incoming Alias = False %LES-I-LOADING, loading SNAVMS$ component SNA$DECNET_ALT from SYS$COMMON:[SNAVMS $]SNA$DECNET_ALT.EXE;3 %LES-I-LOADING, loading SNAVMS$ component SNA$DR from SYS$COMMON:[SNAVMS$]SNAVMS $DR.EXE;3 %LES-I-LOADING, loading SNAVMS$ component SNA$SDLC from SYS$COMMON:[SNAVMS$]SNAV MS$SDLC.EXE;3 %LES-I-LOADING, loading SNAVMS$ component SNA$PC from SYS$COMMON:[SNAVMS$]SNAVMS $PC.EXE;3 %SNAACP-S-STARTED, SNA Server V1.0, device _SNA0: mounted SNA Server V1.0 Startup complete: 7-JAN-2000 14:12:34.14 Do you wish to run the SNAVMS$IVP program now? [YES] : @SYS$COMMON:[SYSTEST]SNAVMS$IVP.COM SNA Server V1.0 Installation Verification Procedure B-6 Sample Installation and Configuration (C) 1999 Electronic Data Systems Corporation. All Right Reserved. (C) 1999 Digital Equipment Corporation. All Rights Reserved. THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED. THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICES AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY COMPAQ COMPUTER CORPORATION. COMPAQ ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY COMPAQ. CONREQREJ The connection to VTAM was successful; however, the session was rejected because VTAM did not recognize the application selected. The SNAVMS$IVP program ran successfully and connected to VTAM. Checking of other Compaq SNA access routine products should now proceed. You should add the following command to SYS$MANAGER:SYSTARTUP_VMS.COM: $ @SYS$COMMON:[SNAVMS$]SNAVMS$STARTUP Finished SNA Server product configuration At 7-JAN-2000 14:19:50.69 $ B.3 Sample Configuration (X.25 Lines) The following is a sample SNA Server configuration for communication over a packet switched data network (PSDN). The answers to each prompt are for demonstration purposes only and will probably differ from the answers that you supply during your configuration procedure. $ set default sys$common: [SNAVMS$] $ @SNAVMS$CONFIGURE.COM Command file to configure the SNA Server product Executing on 16-JAN-2000 12:35:26.42. Enter a question mark (?) at any time for help. Enter CONTROL-Z at any time to abort. Sample Installation and Configuration B-7 Will this node communicate over an X.25 network? [NO] : yes How many LU addresses available to this PU? [128] : What is the PU segment size (decimal)? [265] : Which calling direction (INCOMING,OUTGOING)? [OUTGOING] : What is the network name? : mainframe What is the address of the local DTE? [] : 1212121212 What is the group name for the local DTE? [] : What is the address of the remote DTE? [] : 3106001983 What is the exchange ID (XID) number (8-digit hex)? : DEC99004 Will reverse charging be applied to outgoing calls? [NO] : You may now enter any access names that you wish to create. Enter RETURN at the ACCESS NAME prompt when finished. Access name? (1-16 characters) [] : TSO Sessions for this access name? (numbers or ranges) [1-128] : Application name? (1-8 characters) [] : TSOL Logon mode table? (1-8 characters) [] : DSILGMOD User data? (quoted string, 1-32 characters) [] : Access name? (1-16 characters) [] : The configuration file SYS$COMMON:[SNAVMS$]SNAVMS$CFG_VOYGER.COM;1 was created on 16-JAN-2000 12:36:16.28 The modem startup file SYS$COMMON:[SNAVMS$]SNAVMS$DATALINK_STARTUP_VOYGER.COM;1 was created on 16-JAN-2000 12:36:22.09 The authorization file SYS$COMMON:[SNAVMS$]SNAVMS$AUTHORIZE_VOYGER.COM;1 was created on 16-JAN-2000 12:36:23.04 Do you wish to start the SNA Server product now? [YES] : @SYS$COMMON:[SNAVMS$]SNAVMS$STARTUP.COM Compaq SNA Server for OpenVMS V1.0 Startup begins : 16-JAN-2000 12:36:34.49 Node 0 Session Control Application 58 at 2000-01-16-12:37:06.723-04:00Iinf Characteristics Incoming Alias = False B-8 Sample Installation and Configuration %LES-I-LOADING, loading SNAVMS$ component SNA$DECNET_ALT from SYS$COMMON:[SNAVMS $]SNA$DECNET_ALT.EXE;13 %LES-I-LOADING, loading SNAVMS$ component SNA$DR from SYS$COMMON:[SNAVMS$]SNAVMS $DR.EXE;12 %LES-I-LOADING, loading SNAVMS$ component SNA$SDLC from SYS$COMMON:[SNAVMS$]SNAV MS$SDLC.EXE;12 %LES-I-LOADING, loading SNAVMS$ component SNA$QLLC from SYS$COMMON:[SNAVMS$]SNAV MS$QLLC.EXE;176 %LES-I-LOADING, loading SNAVMS$ component SNA$PC from SYS$COMMON:[SNAVMS$]SNAVMS $PC.EXE;12 %SNAACP-S-STARTED, SNA Server T1.0, device _SNA0: mounted SNA Server V1.0 Startup complete: 16-JAN-2000 12:37:11.13 Do you wish to run the SNAVMS$IVP program now? [YES] : @SYS$COMMON:[SYSTEST]SNAVMS$IVP.COM SNA Server V1.0 Installation Verification Procedure (C) 1999 Electronic Data Systems Corporation. All Right Reserved. (C) 1999 Digital Equipment Corporation. All Rights Reserved. THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED. THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICES AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY COMPAQ COMPUTER CORPORATION. COMPAQ ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY COMPAQ. CONREQREJ The connection to VTAM was successful; however, the session was rejected because VTAM did not recognize the application selected. The SNAVMS$IVP program ran successfully and connected to VTAM. Checking of other Compaq SNA access routine products should now proceed. You should add the following command to SYS$MANAGER:SYSTARTUP_VMS.COM: $ @SYS$COMMON:[SNAVMS$]SNAVMS$STARTUP Sample Installation and Configuration B-9 Finished SNA Server product configuration At 16-JAN-2000 12:39:50.69 B-10 Sample Installation and Configuration ________________________________________________________________ Index A__________________________ B__________________________ Access control information BIOLM quota, 3-33 specifying, 3-17 BYTLM quota, 3-33 Access name definition, 3-11 C keyword parameters, 3-15 ___________________________ to 3-18 Calling direction specifying, 3-15 configuration prompt, used by verification 3-22 program, 3-32 specifying, 3-9 ACCESS NAME parameter, CHANNELCNT, 1-6 3-15 Channel Count, 1-6 Access routines Circuit characteristics, required for installation 3-4 to 3-5, 3-8 to 3-9 , 1-12 Circuit duplex Address configuration prompt, station, 3-5 3-19 Alpha cluster system specifying, 3-5 configuration prompt, Circuit name 3-19 used by verification Application name program, 3-32 specifying, 3-15 cluster system used by verification configuration prompt, program, 3-32 3-21 APPLICATION parameter, Cluster system 3-15 installing software on a, ASTLM quota, 3-33 1-12 Communications device configuration parameters, 3-4 to 3-7 Index-1 Communications line DTE address (remote) characteristics, 3-5 to configuration prompt, 3-7 3-22 line ID, 3-20 specifying, 3-10 Configuration DTE group name completion message, 3-28 specifying, 3-10 procedure, 3-18 to 3-29 questionnaire, 3-2 E__________________________ sample (SDLC lines), B-3 Error messages to B-7 during verification sample (X.25 lines), B-7 program, 3-32 SNAVMS$CFG_node-name.COM Exchange identification file, 3-24 number (XID) SNAVMS$LOAD_DEVICE_node- configuration prompt, name.COM file, 3-24 3-20, 3-22 Configuration (SDLC lines) parameters required for, F 3-4 to 3-7 ___________________________ Configuration (X.25 lines) File names parameters required for, when to change, 3-25 3-7 Files CONREQREJ completion code, created during 3-31 configuration, 3-24 Control and status register to 3-25 (CSR) address installed during configuration prompt, installation, A-1 3-22 purged during configuration, 3-25 D__________________________ purged during DATA Parameter, 3-17 installation, 2-6 Device driver G required for installation ___________________________ , 1-10 Group name DIOLM quota, 3-33 configuration prompt, Disk space 3-22 requirements for installation, 1-4 I__________________________ DTE address (local) IBM configuration prompt, parameters, 1-2 to 1-3 3-22 SNA concepts, 1-1 specifying, 3-9 IBM application password specifying, 3-17 Index-2 Identification number LU LIST parameter, 3-15 See SDLC exchange corresponding with SET PU identification number command, 3-15 (XID) Installation M__________________________ hardware required for, Maximum session number 1-9 to 1-10 specifying, 3-4, 3-8 procedure, 2-3 to 2-7 Memory requirements, 1-5 sample, B-1 to B-3 Modem software required for, guidelines for selecting, 1-10 to 1-13 1-9 system requirements for, required for NRZI 1-4 to 1-8 operation, 3-7 verifying, 3-31 to 3-32 Modem eliminator, 1-9 Installation Verification Multidrop line Procedure (IVP) specifying during running from the configuration, 3-7 configuration procedure , 3-27 N__________________________ running separately, 3-31 Network name L configuration prompt, ___________________________ 3-22 Line duplex Nonpaged pool configuration prompt, changing the value, 1-6 3-20 requirements, 1-5 specifying during NORMAL completion code, configuration, 3-6 3-32 Line ID, 3-20 NOTE parameter, 3-17 Line speed NRZI signalling, 3-7 specifying during configuration, 3-6 O__________________________ Logical unit (LU) OPCOM See LU enabling, 1-11 Logon mode name OpenVMS Alpha cluster specifying, 3-17 system LOGON MODE parameter, 3-17 configuration prompt, LU 3-19 definition, 1-1 Operating system specifying, 3-15 required for installation LU addresses , 1-10 configuration prompt, 3-19, 3-21 Index-3 Signalling P__________________________ configuration prompt, Physical unit (PU) 3-21 See PU specifying, 3-7 Primary logical unit (PLU), Starting SNA Server 1-1 from the command line, Privileges 3-30 from the configuration see OpenVMS system procedure, 3-26 privileges SNAVMS$STARTUP.COM file, PU 3-30 definition, 1-1 Station address specifying, 3-15 configuration prompt, PU segment size 3-20 See also segment size specifying, 3-5 configuration prompt, SYSGEN Parameters, 1-5 3-19 SYSGEN parameter SCSNODE PU Segment size effect on configuration configuration prompt, files, 3-25 3-21 U__________________________ R__________________________ User process quotas, 3-33 Release notes, 2-1 Reverse charging V__________________________ configuration prompt, Verifying the SNA Server 3-23 installation specifying, 3-10 CONREQREJ completion S code, 3-31 ___________________________ NORMAL completion code, SDLC exchange 3-32 identification number running the verification (XID) procedure, 3-31 specifying, 3-5, 3-10 VMS SDLC frame size installing a new version MAXDATA parameter, 3-4, of, 1-11 3-9 memory requirements, 1-5 Secondary logical unit system privileges, 1-4 (SLU), 1-1 VMSINSTAL utility Segment size running, 2-3 specifying, 3-4, 3-9 specifying the OPTIONS N Session address parameter, 2-2 used by verification program, 3-32 Index-4 configuration prompt, W__________________________ 3-19, 3-21 WANDD, 1-11 specifying, 3-4, 3-8 Wide Area Networked Device X.25 network name Drivers, 1-11 configuration prompt, 3-22 X specifying, 3-9 ___________________________ XID X.25 network See SDLC exchange identification number (XID) Index-5