DECnet/SNA VMS Gateway Management Installation Order Number: AA-LU44B-TE This document describes how to install the DECnet/SNA VMS Gateway Management software. It also explains how to read the on-line release notes before or after installing the product. Revision/Update Information: This is a revised manual. Operating System and Version: VMS V5.2 or V5.3 Software Version: DECnet/SNA VMS Gateway Management V2.1 ________________________ July 1990 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-701. Copyright (C)1988, 1990 Digital Equipment Corporation All Rights Reserved Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXcluster DECUS UNIBUS VMS DECnet VAX DIGITAL IBM is a registered trademark of International Business Machines Corporation. PostScript is a registered trademark of Adobe Systems, Inc. This manual was produced by Networks and Communications Publications. _______________________________________________________ Contents _________________________________________________ PREFACE v _______________________________________________________ CHAPTER 1 PREPARING FOR INSTALLATION 1-1 _________________________________________________ 1.1 INSPECTING THE DISTRIBUTION KIT 1-1 _________________________________________________ 1.2 VERIFYING THE REQUIRED VMS VERSION 1-2 _________________________________________________ 1.3 VERIFYING REQUIRED DISK SPACE 1-2 _________________________________________________ 1.4 VERIFYING NECESSARY PRIVILEGES 1-2 _________________________________________________ 1.5 VERIFYING REQUIRED PROCESS ACCOUNT QUOTAS 1-3 _________________________________________________ 1.6 BACKING UP YOUR SYSTEM DISK 1-4 _________________________________________________ 1.7 REGISTERING AND LOADING YOUR PAK 1-4 _______________________________________________________ CHAPTER 2 INSTALLING THE GATEWAY MANAGEMENT SOFTWARE 2-1 _________________________________________________ 2.1 EXAMPLE OUTPUT 2-1 iii Contents _________________________________________________ 2.2 EXPLANATION OF EXAMPLE OUTPUT 2-4 _________________________________________________ 2.3 FILES INSTALLED 2-8 _________________________________________________ 2.4 ERROR RECOVERY 2-10 _________________________________________________ 2.5 MAINTENANCE UPDATES 2-11 _______________________________________________________ INDEX _______________________________________________________ TABLES 1-1 Process Quotas for the Installing Account ____________ 1-3 iv _______________________________________________________ Preface This manual describes how to install DECnet/SNA VMS Gateway Management software on VMS[R] operating systems. In order to use this manual you should be familiar with VMS system management. The DECnet/SNA VMS Gateway Management software is required on all nodes that are load hosts for the DECnet/SNA Gateway for Channel Transport (Gateway-CT) or the DECnet/SNA Gateway for Synchronous Transport (Gateway-ST). Load hosts are VMS systems on which Gateway-CT or Gateway-ST software is installed for loading onto Gateways. In addition to installing Gateway Management software on load hosts, Digital Equipment Corporation strongly recommends that you install the Gateway Management software on any nodes which use program development access routines. This installation is recommended because programmers will need to perform gateway management tasks as they develop their applications. The program development access routines are: o DECnet/SNA VMS APPC/LU6.2 Programming Interface o DECnet/SNA VMS 3270 Data Stream Programming Interface o DECnet/SNA VMS Application Programming Interface Keep this document with your distribution kit. You may need to refer to it if you reinstall the DECnet/SNA VMS Gateway Management software. This document does not contain printed release notes; instead, release notes are provided on-line. Release notes contain important information about the Gateway Management software that may not be included in this manual. You are asked during the installation v Preface procedure whether you wish to print or display the release notes. __________________________________________________________________ Associated Documents You may find the following VMS manuals helpful when you are installing DECnet/SNA VMS Gateway Management: o VMS License Management Utility Manual o VMS System Manager's Manual o VMS System Messages and Recovery Procedures Reference Manual Once you have installed Gateway Management, refer to DECnet/SNA Gateway Management for information on how to use this product. __________________________________________________________________ Conventions This manual uses the following conventions: _______________________________________________________ Convention__________Meaning____________________________ SNANCP> SET LINE In both command and syntax line-id examples, uppercase letters represent text that you must enter exactly as shown. Lowercase letters represent variables for which you must substitute specific information. vi Preface _______________________________________________________ Convention__________Meaning____________________________ A symbol with a one- to three- character abbreviation indicates that you press a key on the terminal (in this example, the Return key). Unless otherwise stated, end every command line by pressing . This symbol indicates that you press and hold down the key labeled Ctrl while simultaneously pressing another key (for example, _____________________or_)._____________ vii _______________________________________________________ 1 Preparing for Installation DECnet/SNA VMS Gateway Management is a set of software tools that allow you to manage the DECnet/SNA Gateway for Channel Transport (Gateway-CT) and the DECnet/SNA Gateway for Synchronous Transport (Gateway-ST). These tools enable you to modify Gateway configurations, monitor Gateway activity, and trace data flows between a Gateway and an IBM[R] system. This chapter describes the preparations you must make before you install Gateway Management software. __________________________________________________________________ 1.1 Inspecting the Distribution Kit The Software Bill of Materials (BOM) included with your distribution kit specifies the contents of the distribution kit. Carefully compare the items you received with the items listed in the BOM. If any components are missing or damaged, contact your Digital representative before continuing with the installation. 1-1 Preparing for Installation __________________________________________________________________ 1.2 Verifying the Required VMS Version Your VAX[R] system must be running VMS V5.2 or V5.3 (use the SHOW SYSTEM command to determine the current version). If you do not have the required version, you must install it before you install the Gateway Management software. The VMS System Manager's Manual explains how to install VMS[R] software. __________________________________________________________________ 1.3 Verifying Required Disk Space Installing Gateway Management requires 1700 free blocks on the system disk (use the SHOW DEVICE command to check available disk space). The Gateway Management software supports VMS tailoring for installation on systems that have limited system disk space. The Gateway Management Software Product Description (SPD) explains VMS tailoring and lists the necessary VMS system classes. The VMS SPD provides more information on classes and VMS tailoring. __________________________________________________________________ 1.4 Verifying Necessary Privileges To install Gateway Management, you must be logged in to an account that has SYSPRV (use the SHOW PROCESS/PRIVILEGES command to check privileges). 1-2 Preparing for Installation __________________________________________________________________ 1.5 Verifying Required Process Account Quotas To install Gateway Management, the account you use must have sufficient quotas. Table 1-1 summarizes the required process quotas. Table_1-1__Process_Quotas_for_the_Installing_Account___ _______Quota_________________Value_____________________ ASTLM 24 BIOLM 18 BYTLM 18,000 DIOLM 18 ENQLM 30 _______FILLM_________________20________________________ Use the VMS Authorize Utility (AUTHORIZE) to compare the current values of these quotas with the requirements for installing Gateway Management. 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 VMS Authorize Utility's MODIFY command. For more information, see the VMS System Manager's Manual. 1-3 Preparing for Installation __________________________________________________________________ 1.6 Backing Up Your System Disk Before you start an installation that involves writing to your system disk, Digital Equipment Corporation recommends that you make a backup copy of your system disk. The System Manager's Manual explains how to back up your system disk. __________________________________________________________________ 1.7 Registering and Loading Your PAK Gateway Management V2.1 supports the License Management Facility (LMF) features provided by the VMS system. LMF requires that a Product Authorization Key (PAK) be registered and loaded before starting the Gateway Management product. The license registration information you need is contained on the PAK sheet that is shipped with the Gateway Management product. To register a license number under VMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration, at the DCL prompt: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your PAK. or o Issue the LICENSE REGISTER command with the appropriate qualifiers that correspond to PAK information. If you plan to use Gateway Management V2.1 on more than one node in a VAXcluster[TM], you will need to perform a license load on each of the nodes. For complete information on using LMF, see the VMS License Management Utility Manual. 1-4 _______________________________________________________ 2 Installing the Gateway Management Software You use the utility VMSINSTAL to install Gateway Management software. When you invoke VMSINSTAL, it displays a series of questions about the installation process. This chapter explains how to answer each of those questions. If you have done the preparations described in Chapter 1, the installation procedure should take no more than 15 minutes. Each question in VMSINSTAL has a default answer which is shown in brackets at the end of the question. To accept the default, press . Otherwise, enter your answer and then press . If you want to stop the installation process before its completion, press . __________________________________________________________________ 2.1 Example Output This section shows example output from VMSINSTAL. An explanation of the output follows in Section 2.2. There are numbers at the end of lines in the example output that correspond to numbers in the explanation section. For example, the 2 at the end of the following line indicates that you can find further explanation at item 2 in Section 2.2. $ SET DEFAULT SYS$UPDATE 2 2-1 Installing the Gateway Management Software Username: SYSTEM 1 Password: password $ SET DEFAULT SYS$UPDATE 2 $ @VMSINSTAL SNAGM021 ddcu: OPTIONS N 3 VAX/VMS Software Product Installation Procedure V5.3 It is 23-JUN-1990 at 13:41. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: WILLIAMS * Do you want to continue anyway [NO]? 4 * Are you satisfied with the backup of your system disk [YES]? 5 The following products will be processed: SNAGM V2.1 Beginning installation of SNAGM V2.1 at 13:41 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 6 * Queue name [SYS$PRINT]: * Do you want to continue with the installation [NO]? 7 %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. 2-2 Installing the Gateway Management Software Product: SNA-GATEWAY-MGMT Producer: DEC Version: 2.1 Release Date: 01-JUN-1990 * Does this product have an authorization key registered and loaded? 8 You will be prompted to run the IVP as part of this installation, but you may also manually invoke the IVP at any time by issuing the command: $ @SYS$TEST:SNAGM$IVP * Do you want to run the IVP after the installation [YES]? 9 * Do you want to purge files replaced by this installation [YES]? 10 * Do you want to start the event logger on this node [YES]? 11 No more questions... Add the following command to your system startup procedures: $ @SYS$STARTUP:SNAGM$STARTUP 12 You can edit SNAGM$STARTUP.COM if you wish to change whether or not the DECnet/SNA Event Logger is run on this node or cluster. 13 %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... DECnet/SNA VMS Gateway Management V2.1 Installation Verification Procedure. 14 The IVP checks that the files have been correctly installed from the kit. Executing the IVP... Files ok... IVP for DECnet/SNA VMS Gateway Management V2.1 completed successfully. Installation of SNAGM V2.1 completed at 13:44 2-3 Installing the Gateway Management Software VMSINSTAL procedure done at 13:44 $ LOGOUT 15 __________________________________________________________________ 2.2 Explanation of Example Output The numbered items in this section correspond to the numbers at the end of lines in the example output shown in the previous section. 1 Log in to the system manager's account. You can run VMSINSTAL from a user's account; however, you are not guaranteed of having all the necessary privileges. If you invoke VMSINSTAL from an account other than the system account, a message will appear pointing this out and asking whether or not you wish to continue with the installation. 2 Set your default device and directory to SYS$UPDATE; this is the directory from which to run VMSINSTAL. 3 Invoke VMSINSTAL as shown. SNAGM021 is the product name and version number. Replace ddcu with the device from which you are installing the software, where dd=device code, c=controller id, u=unit number; for example, MTA0. Enter OPTIONS N so that VMSINSTAL will prompt you to print or display the release notes. See the VMS System Manager's Manual if you want information on other VMSINTAL options. 4 If users are logged in, you are asked whether you want to continue the installation. To continue, type YES and press . To stop the installation, press . Active users on the system could interfere with the installation process. For example, if a user is accessing the VMS HELP library at the same time VMSINSTAL is 2-4 Installing the Gateway Management Software trying to update it, the installation will fail and you will have to start it again. 5 Before you proceed with the installation, make sure you have an up-to-date backup copy of your system disk. 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. 6 This prompt and its options appear only if you specified OPTIONS N when you invoked VMSINSTAL. (If you did not choose OPTIONS N, you can access the release notes later - VMSINSTAL will copy them to SYS$HELP:SNAGM021.RELEASE_NOTES.) Option 1 displays the release notes on your screen. You can terminate the display anytime by pressing . Option 2 sends the release notes to a printer. At the prompt for a queue name, either enter a queue name and press or press to send the file to the default printer. Option 3 both displays and prints the release notes. Option 4 neither displays nor prints the release notes. 7 To continue the installation, type YES and press . To stop here press . Whether or not you stop at this point, the release notes will be copied to SYS$HELP. 8 Registering and loading the product authorization key (PAK) is part of the preparation steps covered in Chapter 1. Answer YES to this question if you have already loaded the PAK. If you answer NO to this question, the system reminds you to perform this step. If you have not yet loaded your PAK, you may still continue with the installation; however, 2-5 Installing the Gateway Management Software you will not be able to run the Gateway Management software until you register and load the PAK. 9 The Installation Verification Procedure (IVP) checks whether the installation procedure was successful. Digital recommends that you run this procedure. Press to run the IVP after the installation. If you do not want to run the IVP, type NO and press in response to the prompt. 10 The system might contain previous versions of Gateway Management software. The files in these directories are replaced during the installation with new files, 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 and press to keep them. The system HELP files are updated in either case. 11 The SNA event logger must be running for a DECnet[TM] node to log SNA Gateway event messages. Digital recommends that you start the event logger at this time so that event logging is started before you begin using the gateway. At the prompt, press to start event logging or, if you want to manually start event logging later, type NO and press . 12 Add this command to your system startup file so that event logging and NETTRACE are started automatically whenever you start your system. 2-6 Installing the Gateway Management Software 13 The SNA Event Logging program must be initialized for a DECnet node to log SNA Gateway event messages. Digital recommends that event logging be initialized as part of your system startup procedure. To accomplish this, SNAGM$STARTUP.COM contains the following command: $ @SYS$STARTUP:SNAGM$EVL_STARTUP If you responded NO to the prompt to start the event logger (item 11), the above command is disabled in SNAGM$STARTUP.COM (by the insertion of an exclamation point (!) in front of the command). To enable the command you must edit SNAGM$STARTUP.COM and remove the exclamation point. 14 If you responded YES to the prompt at 9, the installation procedure now calls the IVP to verify that the Gateway Management software was successfully installed. 15 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 want to restore those symbols, you should log out and log in again. 2-7 Installing the Gateway Management Software __________________________________________________________________ 2.3 Files Installed VMSINSTAL creates or modifies the following files during the installation process: o SYS$HELP:SNAGM021.RELEASE_NOTES Gateway Management release notes o SYS$HELP:SNANCP.HLB SNANCP HELP library o SYS$HELP:SNATRACE.HLB SNATRACE HELP library o SYS$HELP:TRACEHLP.HLB NETTRACE HELP library o SYS$LIBRARY:NETTRACE$KEY.INIT NETTRACE key definitions o SYS$LIBRARY:NETTRACE$CHAN_ANALYZE.EXE NETTRACE channel trace analyzer o SYS$LIBRARY:NETTRACE$SDLC_ANALYZE.EXE NETTRACE SDLC trace analyzer o SYS$LIBRARY:NETTRACE$PU_ANALYZE.EXE NETTRACE PU trace analyzer o SYS$LIBRARY:NETTRACE$ETHERNET_ANALYZE.EXE NETTRACE ETHERNET trace analyzer o SYS$LIBRARY:NETTRACE$NSP_ANALYZE.EXE NETTRACE NSP trace analyzer o SYS$LIBRARY:SNATRAPRE.MAR Translation table prefix file o SYS$LIBRARY:SNATRATBL.MAR Translation table template 2-8 Installing the Gateway Management Software o SYS$MANAGER:NETTRACE_INSTALL.COM Command procedure for starting NETTRACE o SYS$MESSAGE:NETTRACE_MESSAGES.EXE NETTRACE message file o SYS$MESSAGE:SNAEVLMSG.EXE SNAEVL message file o SYS$MESSAGE:SNANCPMSG.EXE SNANCP message file o SYS$MESSAGE:SNAPMSG.EXE SNAP message file o SYS$MESSAGE:SNATRCMSG.EXE SNATRACE message file o SYS$STARTUP:SNAGM$EVL_STARTUP.COM Command procedure for starting SNAEVL o SYS$STARTUP:SNAGM$STARTUP.COM Gateway Management startup procedure o SYS$SYSTEM:NETLTC.EXE NETTRACE trace collector image o SYS$SYSTEM:NETTRACE.EXE NETTRACE utility o SYS$SYSTEM:SNAEVL.EXE SNA event logging program o SYS$SYSTEM:SNANCP.EXE SNA network control program o SYS$SYSTEM:SNAP.EXE SNAP utility o SYS$SYSTEM:SNATRACE.EXE SNATRACE utility o SYS$TEST:SNAGM$IVP.COM Installation verification procedure 2-9 Installing the Gateway Management Software __________________________________________________________________ 2.4 Error Recovery If the installation procedure fails for any reason, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of SNAGM V2.1 has failed. If the IVP fails for any reason, the following messages are displayed: File filename was not found. DECnet/SNA VMS Gateway Management V2.1 IVP failed. %VMSINSTAL-E-IVPFAIL, The IVP for SNAGM V2.1 has failed. Any of the file names listed in Section 2.3 might appear in the first line of the message. An error during installation can occur if you use an incorrect version of the VMS operating system or if one or more of the following conditions exist: o Disk quotas are insufficient for successful installation. You need at least 1700 free blocks on the system disk for installation. o Process quotas required by VMSINSTAL are incorrect (see Section 1.5 in Chapter 1). o The VMS HELP library is currently in use. (Make sure no user tries to access on-line HELP during installation.) For descriptions of the error messages generated by these conditions, see the VMS System Messages and Recovery Procedures Reference Manual and the VMS System Manager's Manual. If the installation fails, you can restart the installation procedure after you have made the 2-10 Installing the Gateway Management Software appropriate changes. If the installation fails due to an IVP failure, contact Digital Customer Service. After Gateway Management software is installed, you can run the IVP independently to verify that the software is available on your system. You might need to do so, for example, after a system failure to verify that users can access the Gateway Management software. To run IVP independently, enter the following command: $ @SYS$TEST:SNAGM$IVP __________________________________________________________________ 2.5 Maintenance Updates Digital Equipment Corporation might periodically issue maintenance updates of Gateway Management software. Each update will consist of an installation kit. You should install the new kit as described in this document or in any documentation that accompanies the maintenance update. You can successfully install and run a maintenance update on your system even if no previous version has been installed. The maintenance update usually includes release notes that describe any changes that have been made to Gateway Management software since the previous release. These updated release notes are provided on line. You should read the release notes before you install a Gateway Management maintenance release. Release notes are also accessible after the product is installed. To read the release notes before installing a maintenance release, run the installation procedure using OPTIONS N. VMSINSTAL will then prompt you to print or display the release notes. To read the release notes after installing the product, display or print the file SYS$HELP:SNAGMnnn.RELEASE_NOTES. 2-11 _________________________________________________________________ Index _______________________________ _______________________________ A D _______________________________ _______________________________ Access routines DECnet/SNA VMS Gateway and Gateway Management, v Management software Account quotas, 1-3 defined, 1-1 Active processes, 2-5 Default answers, 2-1 Application development Default directory, 2-4 and Gateway Management, v Device designation, 2-4 ASTLM quota, 1-3 DIOLM quota, 1-3 Authorization key, 1-4 Disk space prompt, 2-6 requirements for installation Authorize Utility, 1-3 , 1-2 _______________________________ Distribution kit, 1-1 B _______________________________ _______________________________ E Backing up disks, 1-4 _______________________________ prompt, 2-5 ENQLM quota, 1-3 Bill of Materials (BOM), 1-1 Error recovery, 2-10 BIOLM quota, 1-3 Event logging Brackets prompt, 2-6 showing default answers, 2-1 startup command, 2-7 BYTLM quota, 1-3 _______________________________ _______________________________ F C _______________________________ _______________________________ Failure message, 2-10 Commands Files installed, 2-8 SNAGM$EVL_STARTUP, 2-7 FILLM quota, 1-3 SNAGM$IVP, 2-11 _______________________________ VMSINSTAL, 2-4 Continuing the installation H prompt, 2-5 _______________________________ Help, accessing, 2-2 Index-1 Index _______________________________ I License Management Facility _______________________________ (LMF) (Cont.) Installation prompt, 2-6 and HELP library, 2-10 Loading the authorization key, and symbol tables, 2-7 1-4 authorization key, 2-6 Logging in, 2-4 continuing, 2-5 _______________________________ default directory, 2-4 M device designation, 2-4 _______________________________ error recovery, 2-10 Maintenance update installa- event logging prompt, 2-6 tion, 2-11 files installed, 2-8 help, 2-2 _______________________________ logging in, 2-4 N logging out, 2-7 _______________________________ of maintenance updates, 2-11 NETLTC.EXE file, 2-9 OPTIONS N, 2-4 NETTRACE$CHAN_ANALYZE.EXE privileges required, 2-4 file, 2-8 procedure, 2-1 NETTRACE$KEY.INIT file, 2-8 product name, 2-4 NETTRACE$PU_ANALYZE.EXE file, purging files, 2-6 2-8 queue name prompt, 2-5 NETTRACE$SDLC_ANALYZE.EXE starting, 2-4 file, 2-8 stopping, 2-1 NETTRACE.EXE file, 2-9 system startup procedure NETTRACE_INSTALL.COM file, 2-9 prompt, 2-6 NETTRACE_MESSAGES.EXE file, Installation Verification 2-9 Procedure (IVP), 2-7 NETTRACT$ETHERNET_ANALYZE.EXE failure message, 2-10 file, 2-8 prompt, 2-6 NETTRACT$NSP_ANALYZE.EXE file, running after installation, 2-8 2-11 _______________________________ _______________________________ L O _______________________________ _______________________________ License Management Facility OPTIONS N, 2-4 (LMF), 1-4 Index-2 Index _______________________________ P SNAGM$EVL_STARTUP.COM file, _______________________________ 2-9 Privileges SNAGM$EVL_STARTUP command, 2-7 see VMS system privileges SNAGM$IVP.COM file, 2-9 Processes still active, 2-5 SNAGM$IVP command, 2-11 Process quotas, 1-3 SNAGM$STARTUP.COM file, 2-9 Product Authorization Key SNAGM$STARTUP command, 2-6 (PAK), 1-4 editing, 2-7 prompt, 2-6 SNAGM021.RELEASE_NOTES file, Product name for installation, 2-8 2-4 SNAGM021 product name, 2-4 Program development SNANCP.EXE file, 2-9 and Gateway Management, v SNANCP.HLB file, 2-8 Purging files, 2-6 SNANCPMSG.EXE file, 2-9 SNAP.EXE file, 2-9 _______________________________ SNAPMSG.EXE file, 2-9 Q SNATRACE.EXE file, 2-9 _______________________________ SNATRACE.HLB file, 2-8 Queue name prompt, 2-5 SNATRAPRE.MAR file, 2-8 Quotas, 1-3 SNATRATBL.MAR file, 2-8 SNATRCMSG.EXE file, 2-9 _______________________________ Software Product Description R (SPD), 1-2 _______________________________ Starting Registering the authorization event logging, command, 2-7 key, 1-4 event logging, prompt, 2-6 Release notes Gateway Management, 2-6 and maintenance updates, 2-11 installation, 2-4 and OPTIONS N, 2-4 Stopping installation, 2-1 options, 2-5 SYS$UPDATE directory, 2-4 SYSPRV privileges, 1-2 _______________________________ SYSTEM account, 2-4 S System disk backup, 1-4 _______________________________ prompt, 2-5 Service Update PAK (SUP), 1-4 System startup procedures, 2-6 SNAEVL.EXE file, 2-9 SNAEVLMSG.EXE file, 2-9 Index-3 Index _______________________________ T required version, 1-2 _______________________________ system privileges, 1-2 TRACEHLP.HLB file, 2-8 VMS Authorize Utility, 1-3 VMS HELP library _______________________________ and installation, 2-10 V VMSINSTAL _______________________________ see also Installation VAXcluster VMSINSTAL command, 2-4 and Gateway Management, 1-4 VMSINSTAL utility, 2-1 VMS VMSLICENSE utility, 1-4 VMS tailoring, 1-2 Index-4