______________________________________________ VMS AXP 2780/3780 Protocol Emulator Installation Guide Order Number: AA-QZZRC-TE June 1999 This document describes how to install the VMS AXP 2780/3780 Protocol Emulator, Version 2.0. The document also explains how to read the online release notes before and after installing the product. Revision/Update Information: Revision 2.0. Operating System and Version: OpenVMS Version 6.2 or 7.1 Software Version: VMS AXP 2780/3780 Protocol Emulator Version 2.0 __________________________________________________________ June 1999 © Digital Equipment Corporation 1989, 1999. All rights reserved. The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such a license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. The following are trademarks of Digital Equipment Corporation: DEC, DEC SNA Domain Gateway, DECnet, OpenVMS, ULTRIX, VAX, and the Digital logo. The following are third-party trademarks: IBM is a registered trademark of International Business Machines Corporation. This manual was produced by Information Design and Consulting. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. v 1 Preparing for Installation 1.1 Open VMS System Requirements.................... 1-1 1.1.1 Open VMS Supported Processors ................ 1-1 1.1.2 Checking the Distribution Kit ................ 1-1 1.1.3 Accessing the Online Release Notes ........... 1-1 1.1.4 VMS AXP Communications Device Requirements ... 1-2 1.1.5 VMScluster Considerations .................... 1-2 1.1.6 Prerequisite Software ........................ 1-3 1.1.7 OpenVMS License Management Facility Requirements.................................. 1-3 1.1.8 OpenVMS Tailor Requirements .................. 1-4 1.1.9 VMSINSTAL Requirements ....................... 1-4 1.1.10 Backing Up Your System Disk .................. 1-5 1.1.11 Privileges ................................... 1-5 1.1.12 Disk Space ................................... 1-5 1.2 Communications Equipment........................ 1-6 1.2.1 Modem Requirements ........................... 1-7 1.3 Remote System Requirements...................... 1-8 2 Installing 2.1 The Installation Procedure...................... 2-1 2.1.1 Invoking VMSINSTAL ........................... 2-1 2.1.2 Installation Questions ....................... 2-3 2.1.3 Installation Verification Procedure Message .. 2-9 2.1.4 Completing the Installation Procedure ........ 2-9 2.2 Postinstallation Considerations................. 2-9 2.2.1 Running the Installation Verification Procedure..................................... 2-10 iii 2.2.2 Loading the Protocol Emulator ................ 2-10 2.2.3 Cluster Setups ............................... 2-11 2.2.4 Diagnostic Loopback Tests .................... 2-11 2.2.5 Files and Logical Names Added to the System .. 2-11 2.2.6 Device Protection ............................ 2-13 2.3 Error Recovery.................................. 2-13 2.3.1 Installation Verification Procedure Errors ... 2-14 3 De-Installing 3.1 The De-Installation Procedure................... 3-1 3.1.1 Invoking AXP2780_DEINSTAL .................... 3-1 3.1.2 De-Installation Question ..................... 3-2 Index Tables 1-1 Prerequisite Software ........................ 1-3 1-2 Disk Space Requirements ...................... 1-6 1-3 Modems Used by the Protocol Emulator ......... 1-7 2-1 Files Added by the Installation .............. 2-12 iv ________________________________________________________________ Preface The VMS AXP 2780/3780 Protocol Emulator, referred to as the Protocol Emulator, allows a Open VMS system to communicate with other systems that are using the Binary Synchronous Communications protocol. Manual Objectives This manual tells you how to install and load the Protocol Emulator software on a VMS AXP system. Use this manual in conjunction with the VMS AXP 2780/3780 Protocol Emulator User's Guide and other Digital Equipment Corporation and IBM documentation. Intended Audience This manual is for system managers and network managers responsible for the installation of the Protocol Emulator software. Document Structure Chapter 1 Provides introductory information about the Protocol Emulator. Hardware and software requirements are outlined in this chapter. Chapter 2 Describes the installation process and Installation Verification Procedure (IVP). It also contains a sample installation procedure. v Associated Documents o VMS AXP 2780/3780 Software Product Description o VMS AXP 2780/3780 Protocol Emulator User's Guide o OpenVMS I/O User's Reference Manual o OpenVMS System Services Reference Manual o OpenVMS System Messages and Recovery Procedures Reference Manual o Site Management Guide (provided by Digital with your VMS AXP system) Conventions Used in This Manual vi __________________________________________________________ Convention__Meaning_______________________________________ Special This special type indicates an example of type system output or user input. In interactive examples, system output is in plain type, and user input is in bold type. UPPERCASE Uppercase letters in command syntax indicate words that you enter. You can enter these words in either uppercase or lowercase. Lowercase Lowercase italics in command syntax or italics examples indicate variables for which either the user or the system supplies a value. [ ] Square brackets in command syntax statements indicate that the enclosed value(s) are optional. Default values apply for unspecified options. (Do not type the brackets.) In the installation procedure, square brackets enclose the default answer for a question. Simply press to choose the default. ( ) In the installation procedure, parentheses enclose the possible options or range of values that you can specify in response to a question. hh:mm:ss Indicates hours, minutes, and seconds. This symbol indicates a key that you should press. For example, means that you should press the RETURN key. This notation means that you should hold down the CTRL key and press the key specified by x at the same time. (Your screen displays this ____________key_combination_as_^x.)_______________________ You must press to enter all commands. vii 1 ________________________________________________________________ Preparing for Installation Before you install the VMS AXP 2780/3780 Protocol Emulator software, referred to as the Protocol Emulator, you should prepare your system, the communication components, and the remote system to ensure proper software operation. 1.1 Open VMS System Requirements This section discusses the Open VMS system features you need for the Protocol Emulator. 1.1.1 Open VMS Supported Processors Refer to the Software Product Description (SPD) for the latest official list of supported processors. 1.1.2 Checking the Distribution Kit Your bill of materials (BOM) specifies the number and contents of your media. Compare the items listed in the BOM with the items in your distribution list. If your kit is damaged or if parts are missing, contact your Digital Equipment Corporation representative before continuing the installation. 1.1.3 Accessing the Online Release Notes Online release notes are provided with this product. You should review the release notes before installing the product. They contain the latest enhancements to the product, which may include changes to the installation procedure. If you specify OPTIONS N with VMSINSTAL, you are prompted for how you would like to see the release notes. After installing the product, you can read the release notes in the file SYS$HELP:AXPBSCPTPvvu.RELEASE_ NOTES , where vv is the major version number, and u is the minor version number. Preparing for Installation 1-1 Preparing for Installation 1.1 Open VMS System Requirements 1.1.4 VMS AXP Communications Device Requirements Your VMS AXP system is attached to the IBM environment through a Digital Equipment Corporation communications device, a line, a modem, and an IBM communications controller. Your system must have one or more of the following Digital communications hardware devices installed. o DSY-T1 The DSY-T1 is a dual-line synchronous device for machines with the turbo-channel bus. The Protocol Emulator can communicate at speeds up to 9.6 Kbps per line for two line operation, and 19.2 Kbps for one line operation. o PBXDP The PBXDP is a multi-line synchronous device which can be ordered in any of its 2/4/8 line variants. It can be used on all machines using the PCI internal bus. Transmission characteristics (such as speed and mode of operation) can vary to satisfy different performance requirements. For additional information about supported communications devices, see the SPD for the Protocol Emulator. 1.1.5 VMScluster Considerations This layered product is fully supported when installed on any valid and licensed VMScluster configuration with the following restrictions: o The VMS AXP 2780/3780 Protocol Emulator must be installed and run on each node in the VMScluster containing a synchronous communications interface connected to an IBM system. o When you run the Protocol Emulator in interactive mode, you must run it from a node with a synchronous device interface and the product locally installed. 1-2 Preparing for Installation Preparing for Installation 1.1 Open VMS System Requirements o When you run the Protocol Emulator in shared mode, the batch queue must reside on a node with a synchronous device interface and the product locally installed. However, jobs can be submitted to this queue from any node in the cluster. Refer to the VMScluster documentation for information on setting up queues across a cluster and using cluster batch queues. 1.1.6 Prerequisite Software Depending on the configuration of the system where you are installing the Protocol Emulator, it must necessary to first install the Wide Area Network Device Drivers (WANDDs) and DECnet/OSI. Table 1-1 shows the required softwares for different versions of OpenVMS. Table_1-1_Prerequisite_Software___________________________ OpenVMS Version_______Software____________________________________ Version 6.2 OpenVMS WANDD Version V1.0-G Version 6.2 DECnet/OSI for OpenVMS Version V6.3 Version 7.1 OpenVMS WANDD Version V1.1-B Version 7.1 DECnet/OSI for OpenVMS ______________Version_V7.1________________________________ 1.1.7 OpenVMS License Management Facility Requirements Before you install this product, you should register your Product Authorisation Key (PAK) with the License Management Facility (LMF). The PAK, which contains information about the license, is a paper certificate shipped with the product. Preparing for Installation 1-3 Preparing for Installation 1.1 Open VMS System Requirements During the installation, you are asked if you have registered the Protocol Emulator License and loaded the appropriate authorization key (PAK). If you have not already done so, you can complete the installation and run the Installation Verification Procedure (IVP). The Protocol Emulator will not run if you have not registered the license or loaded the PAK. Once you perform the license registration and load the PAK, you will be able to run the Protocol Emulator. To register and load the license, log in to the system manager's account. Then type the following command: $ @SYS$UPDATE:VMSLICENSE.COM When you are prompted for information, enter the data from you PAK. For more informations on LMF, see the OpenVMS License Management Utility Manual. 1.1.8 OpenVMS Tailor Requirements The required classes are: OpenVMS Required Save Set and Utilities. Be certain these classes are installed on your system before installing the product. Refer to OpenVMS Tailor documentation in the VMS documentation set for more information. 1.1.9 VMSINSTAL Requirements Installing the Protocol Emulator on an OpenVMS system involves running the VMSINSTAL procedure. The dialogue is self-explanatory. The system tells you to answer questions and waits for you to tell it to continue. When you invoke VMSINSTAL, it checks that: o You are logged in to a privileged account. o You have adequate quotas for installation. The Protocol Emulator installation requires the OpenVMS default minimum quotas. o All users are logged off. 1-4 Preparing for Installation Preparing for Installation 1.1 Open VMS System Requirements If VMSINSTAL detects any violations to these conditions at the beginning of the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process, enter NO or press . Then change the condition and restart the installation. 1.1.10 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you back up your system disk before installing any software on top of the operating system. Use the backup procedures that have been established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS documentation set. 1.1.11 Privileges To install the Protocol Emulator, you must be logged in to an account that has SETPRV or at least the following privileges: o CMKRNL o WORLD o SYSPRV Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. 1.1.12 Disk Space Table 1-2 summarizes the storage requirements for the Protocol Emulator. Preparing for Installation 1-5 Preparing for Installation 1.1 Open VMS System Requirements Table_1-2_Disk_Space_Requirements_________________________ Blocks Needed OpenVMS_Versions____to_Install_______Blocks_Needed_to_Run_ OpenVMS Version 2770 1420 6.2 OpenVMS Version 2780 1490 7.1_______________________________________________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1.2 Communications Equipment Each communications link connecting a remote system to the Protocol Emulator consists of the following: o A pair of synchronous modems with an RS-232-C or CCITT V.24 interface (or hardware performing the function of two modems if the two systems are in close proximity). o A full- or half-duplex point-to-point communications line running between the modems. The connection can be switched (dial-up) or nonswitched (leased or private). Multipoint (multidrop) operations are not supported. ________________________Note ________________________ Although the Protocol Emulator does operate in half- duplex mode, a full-duplex line is recommended for faster line turnaround. _____________________________________________________ Multiple lines can be connected to the Protocol Emulator, depending upon processor type. The transmission char- acteristics - speed, mode of operation and so on - can vary as necessary among the lines to satisfy different transmission requirements. The Protocol Emulator can 1-6 Preparing for Installation Preparing for Installation 1.2 Communications Equipment support transmission speeds from 1200 bits/second to 19200 bits/second. Depending on the data transfer rate selected, you need a pair of the following modems or equivalent for each line. Table 1-3 shows compatible modems. Table_1-3_Modems_Used_by_the_Protocol_Emulator____________ MODEM_______SPEED_________________________________________ Bell 201C 2400 bits/second (half duplex, switched line) Bell 208A 4800 bits/second (full duplex, leased line) Bell 208B 4800 bits/second (full duplex, switched line) Bell_209A___9600_bits/second_(full_duplex,_leased_line)___ 1.2.1 Modem Requirements If you use modems from manufacturers other than Digital or Bell, be sure that they meet the following "handshaking" requirements. o When the user issues a command to allocate and activate a line, the line interface sets on the data terminal ready (DTR) signal. It does this regardless of whether the connection is established by dialing or by auto- answering. The Protocol Emulator looks for data set ready (DSR) and does not consider the line active until the modem presents the DSR signal. o Before starting to transfer data (either by placing data in a send buffer or by taking data out of a receive buffer) the Protocol Emulator checks DSR to determine whether the line is up. If the DSR signal is not set, the operation is abnormally terminated, and a message is sent to SYS$OUTPUT. o Whenever a transmission is attempted, request to send (RTS) is set by the Protocol Emulator and pads (hex FFs) are transmitted until the clear to send (CTS) signal is given. If CTS is not set, the transmission times out and appropriate actions (error logging, retries, posting fatal error messages) are taken. If the transmission completes normally, RTS is cleared if the line is half duplex; or if the line is full duplex it is left active to avoid CTS delays. Preparing for Installation 1-7 Preparing for Installation 1.2 Communications Equipment o Receive operations look for character synchronization; they do not monitor any modem signals except DSR. o When the user issues a command to shut down a line, DTR is dropped. (See the description of the Protocol Emulator's SET command in Chapter 3 of the VMS AXP 2780 /3780 Protocol Emulator User's Guide.) 1.3 Remote System Requirements The Protocol Emulator is designed to communicate with IBM or other systems that communicate with IBM 2780/3780 Remote Job Entry Stations. Some examples of these systems are: o An IBM System/360 or System/370 computer set up to communicate with an IBM 2780 or 3780 Remote Job Entry Station. o An IBM 2780 or 3780 remote job entry station (RJE station). o A computer system, other than an OpenVMS system, that is operating a standard 2780/3780 point-to-point BSC protocol emulator. IMPORTANT The Protocol Emulator is only certified against remote systems listed in the SPD. 1-8 Preparing for Installation 2 ________________________________________________________________ Installing This chapter describes how to install the VMS AXP 2780 /3780 Protocol Emulator, referred to in this chapter as the Protocol Emulator. It contains a step-by-step description of the installation procedure and covers postinstallation considerations. The final section contains an actual system log of an installation using PAK information and VMSINSTAL. 2.1 The Installation Procedure The Protocol Emulator installation process consists of a series of questions and informational messages; the process takes between 3 and 5 minutes to complete. 2.1.1 Invoking VMSINSTAL Digital Equipment Corporation recommends that you use a hard-copy terminal for installing the Protocol Emulator if you would like a copy of the installation process. If you do not have a hard-copy terminal, you can produce a copy of the installation procedure in a file by typing: $ SET HOST 0/LOG=filename where filename is the name of the file in which you want the log file stored. To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. Next, invoke VMSINSTAL. Use the following syntax to invoke VMSINSTAL: @SYS$UPDATE:VMSINSTAL product-name device-name OPTIONS N Installing 2-1 Installing 2.1 The Installation Procedure where product-name is the installation name for the component. For the Protocol Emulator, type AXPBSCPTPvvu, where AXPBSCPTP is the name of the product you are installing, vv is the major version number (2 digits), and u is the update number (1 digit). For example: AXPBSCPTP020 is the name for Version 2.0 of the product. device-name is the name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. OPTIONS N is an optional parameter that indicates you want to be prompted to display or print the release notes, or copy them to SYS$HELP. If you do not include the OPTIONS N parameter, VMSINSTAL does not prompt you to display, print, or copy the release notes. Please read the release notes before proceeding with this installation. Command Example The following example displays the command to invoke VMSINSTAL to install the Protocol Emulator from tape drive MTA0: and the system response. This example uses the OPTIONS N parameter for printing or displaying release notes. $ @SYS$UPDATE:VMSINSTAL AXPBSCPTP020 MTA0: OPTIONS N OpenVMS Software Product Installation Procedure V6.2 It is 15-FEB-1996 at 15:06. Enter a question mark (?) at any time for help. 2-2 Installing Installing 2.1 The Installation Procedure 2.1.2 Installation Questions This section discusses the questions that appear during the installation. Each question in the installation is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example, [YES]. If you want the default response, press . You must press to enter any response. For help, enter a question mark as your response. _____________ Aborting the Installation _____________ To abort the installation procedure at any time, press . When you press , the installation procedure deletes all the files it created up to that point and exits. You can then start the installation again. _____________________________________________________ 1. System backup VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press RETURN. If not, enter NO to stop the installation. After you back up your system disk, you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? 2. Mounting the media You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing the Protocol Emulator has been mounted on the specified device and that the installation has begun. For example: Installing 2-3 Installing 2.1 The Installation Procedure Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, AXPBSCPTP020 MOUNTED ON _MTA0: The following products will be processed: AXPBSCPTP V2.0 Beginning installation of AXPBSCPTP V2.0 at 15:07 %VMSINSTAL-I-RESTORE, Restoring product saveset A... If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to "Are you ready?". To abort the installation for other reasons, press . 3. Release Notes If you specified OPTIONS N when you invoked VMSINSTAL, the installation procedure prompts you for a release notes option. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes. * Select option [2]: If you select option 1, VMSINSTAL displays the release notes immediately on your terminal. You can terminate the display at any time by pressing . If you select option 2 or 3, VMSINSTAL prompts you for a print queue name: * Queue name [SYS$PRINT]: Enter a queue name or press RETURN to send the file to the default output print device, SYS$PRINT. 2-4 Installing Installing 2.1 The Installation Procedure If you did not specify OPTIONS N when you invoked VMSINSTAL, the release notes are automatically placed in SYS$HELP upon conclusion of the installation. No matter which option you select, VMSINSTAL then asks you if you want to continue the installation. Answer YES to continue or NO to exit VMSINSTAL. * Do you want to continue the installation ?: YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. 4. Wandd The product checks the Wandd version which is installed on the system. If an older version is detected, the system prompts you with one of the following: This installation requires a more recent version of sys$loadable_images:x25$l1.exe (from the wandd kit and elsewhere) than the one present on your system. If you answer yes to the following question then a version of this file compatible with AXP2780 will be installed in place of the current file. If you answer no then this installation will terminate. You may then install a version of wandd compatible with this product before recommencing the installation. * Do you wish to install the version of X25$L1.EXE in this kit [Y]? Yes or If you intend to run 2780 over a PBXDP device then a more recent version of the WANDD file sys$loadable_images:x25$zwdriver.exe (from the wandd kit or elsewhere) than the one present on your system is required. If you answer yes to the following question then a version of this file compatible with AXP2780 will be installed in place of the current file. If you answer no then you will be unable to use PBXDP devices to run 2780. * Do you wish to install the version of X25$ZWDRIVER.EXE in this kit [Y]? Yes Installing 2-5 Installing 2.1 The Installation Procedure 5. Choosing to purge files You have the option to purge files from previous versions of the Protocol Emulator that are superseded by this installation. Purging is recommended because it saves disk space. During this installation, new files will be provided to replace existing versions. You may purge older versions to save disk space, or keep them if you feel they may be of use. Purging is strongly recommended! * Do you want to purge files replaced by this installation [YES]? 6. Choosing to run the Installation Verification Procedure (IVP) The system now asks if you want to have the IVP run automatically at the end of the installation. The IVP for the Protocol Emulator checks to be sure that the installation is successful. You should run the IVP immediately after installation. * Do you want to run the IVP after the installation [YES]? 7. Creating a log file directory The system needs a directory to store detached process log files. Either specify a directory, or press for the default. A directory is created if it does not already exist, and the logical BSC$MANAGER is defined to point to it. * Directory for log files [SYS$COMMON:[BSC$MGR]]: 8. Selecting the alternative translation table If you answer NO, the Protocol Emulator uses the standard OpenVMS translation table. If you answer YES, the Protocol Emulator uses the alternative translation table. See Appendix H of the VMS AXP 2780/3780 Protocol Emulator User's Guide for more information on the translation table supplied with the Protocol Emulator. * Do you want the alternative translation table [NO]? 9. RJE startup file 2-6 Installing Installing 2.1 The Installation Procedure The RJE$CONFIG command file is invoked at this point to create an initial version of the RJE$STARTUP command file. The RJE configuration command procedure will now be invoked to allow you to define the lines that are to be used for 2780/3780 on your system RJE configuration generation 10. Altering the default timeout When the Protocol Emulator is receiving a file, it waits a specified time for successive blocks of data to arrive. If no data is received within that time, it assumes that the connection with the remote system is lost, and exits. If the remote system frequently pauses for longer than 50 seconds (the default value), you can change the default value. The system prompts you with the following: If you wish to override the default receive timeout value then enter a valid delta time here. Suggested values are "0-00:05:00" = five minutes "0-01:00:00" = one hour "1-00:00:00" = one day "9999-00:00:00" = never (in effect) * What value do you wish to use (return for default): 11. Name of lines supported Now enter the names of the RJE lines as they would appear to NCL (and are printed out below if you are running this procedure on the target machine). Eg: PBXDP-0-0, DNSES-0-0 or DSY-0-0. Type ? if you would like to see the list of detected hardware again. When all lines have been defined just type return to the prompt. After each device you will be prompted for an optional system logical name that will be defined at startup to refer to this line. Type return if you don't want a name defined. Checking for known 2780 capable device units on the current system: Installing 2-7 Installing 2.1 The Installation Procedure DSY-0-0 DSY-0-1 DSY-1-0 DSY-1-1 Number of units found: 4 * Device name of first 2780/3780 line: DSY-0-0 * Logical name for this rje line if any ( for none): LINE_ONE * Device name of the next 2780/3780 line: DSY-0-1 * Logical name for this rje line if any ( for none): * Device name of the next 2780/3780 line: You must enter a device name for DSY-T1 or PBXDP which are installed on your system. PBXDP-x-x for a PBXDP device or DSY-x-x for a DSY-T1 device, where x-x are respectively the device number and the line number. An optional system logical name may be entered to refer to each line. When all the device names are entered the system displays the following message: Device DSY-0-0 will be known to VMS as NZA0 and also by the logical name LINE_ONE Device DSY-0-1 will be known to VMS as NZA1 Installation continuing, please wait ... VMS AXP 2780/3780 Protocol Emulator V2.0 *** VMS AXP 2780/3780 Protocol Emulator Installation Successful *** (pending successful IVP) The system displays the following message: The DSY-T1 and DNS-ES device drivers are shipped in the WAN Device Drivers kit. Please install the WANDD V1.0-G for openVMS Alpha 6.2 or WANDD 1.1-B for OpenVMS Alpha 7.1 software from X25 before loading the product if you are using any of these devices. If a previous copy of the AXP OpenVMS 2780/3780 Protocol Emulator is already loaded, then reboot the system before running the load procedure SYS$STARTUP:RJE$STARTUP.COM. 2-8 Installing Installing 2.1 The Installation Procedure There are no further questions, except for any that apply to the IVP. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories and updates the help files. If you asked for files to be purged, that is done now. The following message is displayed: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... 2.1.3 Installation Verification Procedure Message If you chose to run the IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display: BSCPTP$IVP-S, Starting VMS AXP 2780/3780 PE V2.0 IVP BSCPTP$IVP-S, VMS AXP 2780/3780 PE V2.0 IVP Successful 2.1.4 Completing the Installation Procedure The following messages indicate that the entire installa- tion procedure is complete: Installation of AXPBSCPTP V2.0 completed at 09:37 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]AXPBSCPTP020.VMI_DATA VMSINSTAL procedure done at 09:37 Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. At this point, you should load the Protocol Emulator and test the communication link. 2.2 Postinstallation Considerations This section shows files and logical names added to the system, information on loading the Protocol Emulator, running the IVP, and configuring for cluster operation. Installing 2-9 Installing 2.2 Postinstallation Considerations 2.2.1 Running the Installation Verification Procedure The Installation Verification Procedure (IVP) verifies the success of the installation. It checks that the new files were transferred to their proper locations and that files are not in the wrong location. If you encounter problems using the Protocol Emulator, you should run the IVP as a first step in finding a solution. The IVP is designed to catch problems with missing and old files left on your system. To run the IVP after you install the product, invoke the command: @SYS$TEST:AXPBSCPTP$IVP.COM If the IVP fails, correct the situation, and run the IVP again. Section Section 2.3.1 describes IVP failures in more detail. 2.2.2 Loading the Protocol Emulator This section discusses loading the Protocol Emulator into the OpenVMS system. Before loading, you should have completed the following: o Installed any drivers from the WAN Device Drivers Kit (if needed) o Installed this product o Run the IVP successfully o Rebooted the system if the drivers or product was already installed To make the Protocol Emulator available to users, you must invoke the RJE$STARTUP command procedure each time the OpenVMS system is set in operation. This can be done automatically by adding the command: @SYS$STARTUP:RJE$STARTUP to the file SYS$MANAGER:SYSTARTUP.COM. This file is executed each time the OpenVMS system is set in operation. 2-10 Installing Installing 2.2 Postinstallation Considerations 2.2.3 Cluster Setups Install and load the product on each node that has communications devices; then test the physical links to each communications device. Refer to Section 1.1.5 of this manual for specific information on how to set up your cluster for Protocol Emulator use. 2.2.4 Diagnostic Loopback Tests After installing and initializing (loading) the Protocol Emulator, refer to Chapter 4 of the VMS AXP 2780/3780 Protocol Emulator User's Guide for the procedure to test the physical links. 2.2.5 Files and Logical Names Added to the System Table 2-1 lists files added during the installation and their directories. Installing 2-11 Installing 2.2 Postinstallation Considerations Table_2-1_Files_Added_by_the_Installation_________________ File_Name___________________Location______________________ AXP2780_DEINSTAL.COM SYS$COMMON:[SYSMGR] AXPBSCPTP$IVP.COM SYS$COMMON:[SYSTEST] AXPBSCPTP020.RELEASE_NOTES SYS$COMMON:[SYSHLP] BSCPTPDET.EXE SYS$COMMON:[SYSEXE] BSCPTPGBL.EXE SYS$COMMON:[SYSEXE] BSC$DSY-MICROCODE.EXE SYS$COMMON:[SYS$LDR] BSC$DNS-MICROCODE.EXE SYS$COMMON:[SYS$LDR] EBCDEF.MAR SYS$COMMON:[SYSLIB] NYACP.EXE SYS$COMMON:[SYSEXE] NYDRIVER.EXE SYS$COMMON:[SYS$LDR] NZDRIVER.EXE SYS$COMMON:[SYS$LDR] NZDRIVER.SYB SYS$COMMON:[SYS$LDR] REMOTE.EXE SYS$COMMON:[SYSEXE] RJEDEF.FOR SYS$COMMON:[SYSLIB] RJEDEF.MAR SYS$COMMON:[SYSLIB] RJEGLOBAL_TV.EXE SYS$COMMON:[SYSLIB] RJEGLOBAL.IIF SYS$COMMON:[SYSLIB] RJE$ACP_NCL.COM SYS$COMMON:[SYSEXE] RJE$BSCTRAN.COM SYS$COMMON:[SYSMGR] RJE$CONFIG.COM SYS$COMMON:[SYSMGR] RJE$STARTUP.COM SYS$SYSROOT:[SYS$STARTUP] SETDEF.FOR SYS$COMMON:[SYSLIB] SETDEF.MAR SYS$COMMON:[SYSLIB] XJDEF.FOR SYS$COMMON:[SYSLIB] XJDEF.MAR SYS$COMMON:[SYSLIB] Additional_WANDD_files______SYS$COMMON:[SYS$LDR]__________ The system logical names added during installation are BSC$MANAGER, which points to a detached process log files directory, and RJEGLOBAL, which points to SYS$LIBRARY:RJEGLOBAL_TV.EXE. These files are defined when RJE$STARTUP is run. 2-12 Installing Installing 2.2 Postinstallation Considerations 2.2.6 Device Protection The protocol emulator devices used by NYdriver and NZdriver are created with system level protection applied. If users other than those with system privileges need to use the 2780/3780 Protocol Emulator, please refer to Chapter 4 of the 2780/3780 Protocol Emulator User's Guide to change device protection. 2.3 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays error messages. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A prerequisite software version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The OpenVMS help library is currently in use. o The product is not properly licensed. o Your system has insufficient disk space. For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If any of these conditions exist, you should take the appropriate action as described in the message. (You might need to change a system parameter or increase an authorized quota value.) These requirements are part of the installation requirements in Chapter 1 of this manual. Installing 2-13 Installing 2.3 Error Recovery 2.3.1 Installation Verification Procedure Errors This section is designed to help you if your IVP fails. When an error is detected, a message is displayed telling you how to correct the situation. IVP error messages can be divided into these categories: File is in the wrong directory In this case, a file or files are in the wrong directo- ries. To avoid problems where incompatible versions of the same file reside in different directories, delete the file specified in the error message and rerun the IVP. Be sure you delete the specified file; note the directory specification, such as SYS$COMMON: or SYS$SPECIFIC:. After deleting the file, run the IVP again to check for further errors. The format for these error messages is: BSCPTP$IVP-E, filename is in directory. Please delete this file and rerun the IVP. The following is an example of these messages: BSCPTP$IVP-E, NYDRIVER.EXE is in SYS$SPECIFIC:[SYSEXE]. Please delete this file and rerun the IVP. File does not exist In this case, a file or files do not exist. You must reinstall the product to correct the situation. The format for these error messages is: BSCPTP$IVP-E, filename does not exist. Please reinstall the product. The following is an example of these messages: BSCPTP$IVP-E, SYS$COMMON:[SYSEXE]REMOTE.EXE does not exist. Please reinstall the product. Console output of IVP that failed The following is a sample of an IVP that shows errors. 2-14 Installing Installing 2.3 Error Recovery $ @sys$test:bscptp$ivp BSCPTP$IVP-S, Starting VMS AXP 2780/3780 PE V2.0 IVP BSCPTP$IVP-E, SYS$COMMON:[SYSEXE]BSCPTPDET.EXE does not exist. Please reinstall the product. BSCPTP$IVP-E, SYS$COMMON:[SYSEXE]BSCPTPGBL.EXE does not exist. Please reinstall the product. BSCPTP$IVP-E, SYS$COMMON:[SYSEXE]REMOTE.EXE does not exist. Please reinstall the product. BSCPTP$IVP-E, SYS$COMMON:[SYSEXE]RJEGLOBAL.EXE does not exist. Please reinstall the product. BSCPTP$IVP-E, NYDRIVER and UFDRIVER do not exist. Please reinstall the product. BSCPTP$IVP-E, VMS AXP 2780/3780 PE V2.0 IVP Failed with 5 errors. $ Installing 2-15 3 ________________________________________________________________ De-Installing This chapter describes how to de-install the VMS AXP 2780 /3780 Protocol Emulator, referred to in this chapter as the Protocol Emulator. It contains a step-by-step description of the de-installation procedure. 3.1 The De-Installation Procedure The Protocol Emulator de-installation process, deletes the latest version of the files installed during the Protocol Emulator installation procedure. The two drivers and NYACP will be unloaded only by shutting down and restarted the system. The de-installation procedure displays informational messages and poses one question. 3.1.1 Invoking AXP2780_DEINSTAL Digital Equipment Corporation recommends that you use a hard-copy terminal for installing the Protocol Emulator if you would like a copy of the de-installation process. If you do not have a hard-copy terminal, you can produce a copy of the de-installation procedure in a file by typing: $ SET HOST 0/LOG=filename where filename is the name of the file in which you want the log file stored. To start the de-installation, invoke the AXP2780_DEINSTAL command procedure from a privileged account with the SETPRV privilege, such as the SYSTEM account as follows: @SYS$STARTUP:AXP2780_DEINSTAL De-Installing 3-1 De-Installing 3.1 The De-Installation Procedure Command Example The following example displays the command to invoke AXP2780_DEINSTAL command procedure to install the Protocol Emulator. $ @SYS$STARTUP:AXP2780_DEINSTAL VMS AXP 2780/3780 Protocol Emulator de-installation started... VMS AXP 2780/3780 Protocol Emulator de-installation Successful Please, reboot your system to unload the protocol emulator drivers and delete the NYACP process. 3.1.2 De-Installation Question This section discusses the question that appear during the de-installation. The question shows the default response in brackets, for example, [YES]. If you want the default response, press . You must press to enter any response. ____________Aborting the De-Installation ____________ To abort the de-installation procedure at any time, press . You can then start the de- installation again. In this case, warning messages will be displayed which indicate that the previously deleted files are not found. _____________________________________________________ 1. Reboot De-installation asks if you want to reboot your system now. This action is necessary to unload the protocol emulator drivers and to delete the NYACP process. If you enter "YES" the system will reboot automatically. If you enter "NO", the De-Installation is not terminated, the NYACP process is still running and the protocol emulator drivers are still loaded. Only installed files and logical names are deleted. 3-2 De-Installing De-Installing 3.1 The De-Installation Procedure Do you want to reboot the system now (YES or NO) [YES] ?: De-Installing 3-3 ________________________________________________________________ Index A__________________________ F__________________________ Aborting the Installation, Files added to system 2-3 (table), 2-11 B__________________________ H__________________________ Backup copy of system disk, Hardware requirements 1-5 devices, 1-2 C__________________________ I__________________________ CMKRNL privilege, 1-5 IBM system requirements for Communications devices Protocol Emulator, 1-8 descriptions of, 1-2 Installation Conventions used in this aborting, 2-3 manual, vi disk space requirements, 1-5 D__________________________ invoking VMSINSTAL, 2-1 De-Installation Open VMS system step-by-step, 3-1 requirements, 1-1 Default time, 2-7 preparing for, 1-1 Devices processor support, 1-1 see Communications release notes, 1-1 devices required communications Disk space, 1-6 devices, 1-2 requirements, 1-5 step-by-step, 2-1 Distribution kit, checking, IVP 1-1 error messages, 2-14 invoking, 2-10 running after installation, 2-9 Index-1 Privileges required for L__________________________ Protocol Emulator Log files - Directory, 2-6 installation, 1-5 Logicals added to system Purging files, 2-6 (table), 2-11 Loopback test, 2-11 R__________________________ Release Notes M__________________________ accessing, 1-1 Memory requirements, 1-5 to display or print, 2-4 Modems S characteristics of, 1-6 ___________________________ requirements, 1-7 SYS$UPDATE, as default, table of, 1-7 1-4 SYSPRV privilege, 1-5 O__________________________ OpenVMS T__________________________ VMScluster Support, 1-2 Tailor Requirements, 1-4 Testing, 2-11 P__________________________ Postinstallation V__________________________ cluster setups, 2-11 VMSINSTAL files and logical names command line, 2-2 added, 2-11 general requirements, 1-4 IVP failure message, 2-13 privileges, 1-5 loading the Protocol Emulator, 2-10 W__________________________ Loopback tests, 2-11 WORLD privilege, 1-5 Printer queue name, 2-4 Index-2