__________________________________________________________________ 1 Updating the VMS Operating System to Version 5.4-2 VMS Version 5.4-2 supports the KFMSA adapter, the VAX 4000 Model 200 series, optionally installable Local Area Transport (LAT) software, and various peripheral devices. This document describes updating to VMS Version 5.4-2 and installing optional LAT software. Note: If you installed the LAT software provided with VMS Version 5.4-1, you must install the updated VMS Version 5.4-2 LAT software. The updated Version 5.4-2 LAT software contains additional software corrections. The KFMSA adapter lets you add a DSSI peripherals to your VAX 6000 series system (for example, RF-series disk drives). If you need to create an RF-series system disk on a VAX 6000 series system, you have two options: o Install VMS Version T5.4-0K on the RF drive, and then update to VMS Version 5.4-2. o Update a non-RF disk to VMS Version 5.4-2, and then use VMSKITBLD or standalone BACKUP to create the RF-series system disk. Update to VMS Version 5.4-2 if your system is already running one of the following VMS Versions: Version 5.4 Version 5.4-0A Version T5.4-0K Version 5.4-1 Version 5.4-1A You can update to VMS Version 5.4-2 if your system is already running one of the following VMS Versions: Version 5.4 Version 5.4-0A Version T5.4-0K Version 5.4-1 1 Version 5.4-1A If your system is not running at least VMS Version 5.4, you must first upgrade to at least VMS Version 5.4. If you do not have the media and documentation for VMS Version 5.4, please consult your local Digital representative for ordering information. The VMS Version 5.4-2 kit is available on tape cartridge, magnetic tape, and compact disc. ___________________________ 1.1 Preparing to Update Your System Before performing the update, follow the steps in this section. 1 Make a backup copy of the system disk. When you update to Version 5.4-2, apply the update to the backup copy. Backing up the system disk preserves the original system disk in case the update fails. For more information, see the upgrade and installation supplement for your VAX computer. CAUTION: A system failure at a critical point in the update procedure might corrupt the contents of the system disk. Back up the system disk so that you will always have a working copy. 2 If you are not updating a VAX 6000 series computer, continue with step 4. If you are updating a VAX 6000 series computer, make sure it has the correct version of console microcode. To determine what version your system uses, look at the "EEPROM = x.x/n.n" portion of the self-test display. The value n.n indicates the version of console microcode installed on your system. The following table lists the minimum required versions for VMS Version 5.4-2: 2 Table_1__Required_Console_Microcode_Versions___________ Minimum Required ________Version_Number_______ VAX_6000___________ Scalar Vector Platform Enhancements (PLEN)[1]____ Model 200 Series 3.8 5.1 Model 300 Series 4.7 6.1 Model 400 Series 1.03 2.02 3.01 Model 500 Series 2.02 2.02 2.02 _______________________________________________________ [1]PLEN is a hardware enhancement to the backplane of your system. If you are not sure whether your system includes PLEN, see your sales or customer service representative. If your system includes PLEN, your console microcode must be upgraded to at least the version listed in this column. _______________________________________________________ If the minimum version of the console microcode is not installed on your system, you should upgrade the console microcode before you continue. If you do not receive regular console microcode updates, contact your customer service representative to obtain the version you need. For more information on upgrading console microcode, refer to your hardware documentation. 3 Log in to the SYSTEM account. 4 Make sure the system disk has enough free blocks. The VMS Version 5.4-2 update requires either 19,000 free blocks (for peak disk block utilization) in order to use deferred file movement, which is 3 highly desirable, or a minimum of 10,000 free blocks on the system disk. To determine how many free blocks are available, enter the following command: $ SHOW DEVICE SYS$SYSDEVICE: If your system disk has a sufficient number of free blocks, go to step 5. If your system disk does not have sufficient free blocks, create free space by doing the following: a. Delete or purge all unwanted files from the system disk. b. If there still are not enough free blocks, copy the following files to another disk or tape and delete them from the system disk: o All files with file types of JNL, MAP, and LOG o All files in SYS$EXAMPLES and SYS$TEST 5 Use the VMS Authorize Utility as follows to make sure that the SYSTEM account has sufficient quotas and limits: a. Log in to the SYSTEM account. b. Enter the following commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM c. Compare the SYSTEM account's limits and quotas to the following minimum required values: Open file quota (FILLM) 100 Buffered I/O limit (BIOLM) 18 4 Direct I/O limit (DIOLM) 18 AST limit (ASTLM) 24 Enqueue quota (ENQLM) 200 Buffered byte quota count (BYTLM) 32768 d. If necessary, adjust the limits and quotas, until they are equal to, or greater than the required values. You can change each value by entering a command in the following format: MODIFY SYSTEM/limit=new_value For example: UAF> MODIFY SYSTEM/DIOLM=18 e. Exit the Authorize Utility by entering the following command: UAF> EXIT If you adjusted any of the SYSTEM account's values, log out and log in again so that the new values take effect. 6 Once you are logged in to the SYSTEM account, make sure that you are the only user logged in by doing the following: a. Notify current users that they must log out by entering the following command: $REPLY/ALL/BELL/SHUTDOWN "Log out for VMS V5.4-2 update please..." b. Prevent nonprivileged users from logging in by entering the following command: $ SET LOGINS/INTERACTIVE=0 5 7 If you are updating using the InfoServer, skip this step and continue with Section 1.2. You are not required to shut the network down. To check whether your system includes DECnet-VAX software, enter the following command: $ SHOW NETWORK If the system displays the following message, skip to Section 1.2: %SHOW-I-NONET, network unavailable If your system includes DECnet-VAX software and you want to shut it down, enter the following commands: $ RUN SYS$SYSTEM:NCP NCP> SET EXECUTOR STATE OFF NCP> EXIT ___________________________ 1.2 Updating Using the InfoServer If you are not using the InfoServer, skip to Section 1.3. If you are using the InfoServer for your update, you must start the InfoServer Client software and make the CD drive accessible to your system. This section describes these tasks. To start the InfoServer Client software, complete the following steps: 1 If you use DECnet software, make sure it is already started. To check the status of your DECnet software, enter the DCL command SHOW NETWORK. If the system displays the following message, DECnet has not been started: %SHOW-I-NONET, network unavailable 6 2 If you are not using DECnet software on your system, you must define the System Generation Utility (SYSGEN) parameter SCSNODE. To see if SCSNODE is defined on your system, enter the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW SCSNODE If the SYSGEN displays a value for SCSNODE, skip to the next step. If SYSGEN does not display a value for SCSNODE, enter the following commands (where node is a 1 to 6 character unique DECnet node name): SYSGEN> SET SCSNODE node SYSGEN> WRITE CURRENT SYSGEN> EXIT After you set SCSNODE, you must reboot the system. For more information about booting the system, see the VMS upgrade and installation supplement for you VAX computer. 3 Start the InfoServer software by entering the following command: $ @SYS$STARTUP:ESS$STARTUP CLIENT Note: If the InfoServer Client software does not find the DECnet node name of your system, it will not start. The CLIENT parameter loads the client driver, ESS$DADDRIVER.EXE, and the InfoServer transport driver, ESS$LASTDRIVER.EXE. 4 To start the InfoServer Client software each time the system boots, add the following line to SYS$MANAGER:SYSTARTUP_V5.COM: $ @SYS$STARTUP:ESS$STARTUP CLIENT 7 5 As the startup procedure executes, it displays the following messages: %LASTCP-I-VERSION, LASTDRIVER X1.5 is stopped %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyy After you start the InfoServer Client software, you must make the CD drive accessible to your system as follows: 1 Insert the distribution CD in the CD drive that is connected to the InfoServer 100. 2 Enter the following commands: $ RUN SYS$SYSTEM:ESS$LADCP LADCP> BIND VMSU2054 %LADCP-I-BIND, service bound to logical unit DAD$VMSU2054 (_DADn:) LADCP> EXIT Make note of the device name DADn: in the previous display. You will have to specify this device name during the update. ___________________________ 1.3 How to Proceed Different system configurations require slightly different update procedures. The following list indicates the possible system configurations and the section to which you should refer: o Standalone system-Section 1.7 o VAXcluster environment (not including mixed-version VAXclusters and local area VAXclusters with one boot server and two system disks)-Section 1.4 o Mixed-version VAXcluster environment (for example, one that combines Version 5.4 and Version 5.4-2 systems)-Section 1.5 8 o Local area VAXcluster environment with one boot server and two system disks-Section 1.6 ___________________________ 1.4 Updating VAXcluster Environments Use the following procedure to update VAXcluster environments (not including mixed-version VAXclusters and local area VAXclusters with one boot server and two system disks): Note: After completing this procedure, all the systems in your VAXcluster environment will be running the same version of the VMS operating system. If you want to run different versions of the VMS operating system in the same cluster, see Section 1.5. 1 Make sure that you have prepared your system for the update, as described in Section 1.1. 2 Log in to the SYSTEM account on a node that uses the system disk that you are updating. 3 Shut down all other nodes in the cluster that boot from this system disk. 4 Apply the update according to the instructions in Section 1.7. 5 If the VAXcluster environment uses several system disks, repeat steps 1 through 4 for each system disk in the VAXcluster environment. 6 After the update is complete, follow the steps in Section 1.8. 9 ___________________________ 1.5 Performing a Rolling Update for Mixed-Version VAXcluster Environments You perform a rolling update when you want nodes in a VAXcluster environment to run different versions of the VMS operating system. Since you apply the update to only certain system disks, the systems that are not being updated remain available to users. For example, during the Version 5.4-2 rolling update, Version 5.4 systems are available to users. A rolling update is not appropriate for clusters in which all systems boot from a single system disk. For such clusters, you must follow the instructions in Section 1.4. Note: Only Version 5.3, 5.3-1, 5.3-2, 5.4, T5.4-0K, 5.4-1, and 5.4-1A systems are supported in mixed- version VAXcluster environments. To perform a rolling update, complete the following steps: 1 Make sure you have prepared your system for the update, as described in Section 1.1. 2 Log in to the SYSTEM account on a node that uses the system disk you are updating. 3 Shut down all other nodes in the cluster that boot from this system disk. 4 Apply the update as described in Section 1.7. Note that while you update the system, users can remain logged in to any systems in the VAXcluster environment that are not being updated. 5 If you are updating several system disks, repeat steps 1 through 4 for each system disk that you are updating. 6 Follow the steps in Section 1.8. 10 ___________________________ 1.6 Updating a Local Area VAXcluster System with One Boot Server and Two System Disks To update a local area VAXcluster with one boot server and two system disks, complete the following steps: 1 Log in to the SYSTEM account on the boot server. 2 Shut down all other nodes in the cluster that boot from the first system disk. 3 Follow the steps in Section 1.1 to prepare your system for the update. 4 Apply the update to the first system disk, as described in Section 1.7. 5 To update the second disk, follow these steps: a. Log in to the SYSTEM account on a satellite node that boots from the second system disk. b. Shut down all other nodes in the cluster that boot from the second system disk. c. Apply the update as described in Section 1.7. 6 Follow the steps in Section 1.8. ___________________________ 1.7 Applying the Version 5.4-2 Update To update the VMS operating system to Version 5.4-2, complete the following steps: 1 Place the distribution media in the drive. (If you are using the InfoServer, you should have already inserted the CD and completed the steps in Section 1.2). 2 To start the VMSINSTAL command procedure, enter the following command: CAUTION: Do not specify an asterisk (*) in place of the product name VMSU2054. Although specifying an asterisk (*) as the product name usually installs 11 all products on the media, in this case it does not work correctly. $ @SYS$UPDATE:VMSINSTAL VMSU2054 ddcu: OPTIONS N where ddcu is the device name of the source drive that holds the update distribution media. If your are updating from a CD drive connected to an InfoServer, the device name is DADn. The n part of the device name was displayed when you bound to the distribution CD as described in Section 1.2. The OPTIONS N portion of the command indicates that you want to display the release notes option menu. For more information about the format of device names on your system, see the installation and operations guide for your VAX computer. For example, if you are updating from a CD drive connected to an InfoServer that has the device name DAD1, enter the following command: $ @SYS$UPDATE:VMSINSTAL VMSU2054 DAD1: OPTIONS N The following example shows the command line you enter if your distribution media is loaded on a TK50 tape cartridge drive on controller B, with unit number 6, and you are updating to Version 5.4-2: $ @SYS$UPDATE:VMSINSTAL VMSU2054 MUB6: OPTIONS N If the VMSINSTAL command fails, check to see if either of the following conditions occurred: o You typed the letter O and not the number zero in the product name. VMSINSTAL displays the following message: %VMSINSTAL-E-NOPRODS, None of the specified products were found 12 o You specified an incorrect name for the source device. VMSINSTAL displays an "invalid device" error message and prompts you until you enter the name of a source device that exists on the system. Remember to put a colon (:) after the device name. 3 As the update procedure begins, VMSINSTAL displays the following messages: Note: If you are updating using the InfoServer, the procedure may display error messages about the BYTLM quota being set too low. If you set the BYTLYM quota to 32768 before the update (as described in Section 1.1), you can ignore these messages. VAX/VMS Software Product Installation Procedure V5.4 It is 5-MAR-1991 at 13:30. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? If you backed up the system disk, press Return and continue. If you have not yet backed up your system disk, do the following: a. Type NO and press Return. VMSINSTAL returns to DCL level to permit you to perform the backup. b. Back up and restore your system disk (see step 2 in Section 1.1). c. When the backup is complete, restart the update procedure at step 1. 4 The procedure displays the following message: Please mount the first volume of the set on ddcu: * Are you ready? 13 Make sure the distribution media is in the correct drive, and enter YES. 5 VMSINSTAL continues with the following display: %MOUNT-MOUNTED, VMSU2 mounted on ddcu: The following products will be processed: VMSU2 V5.4 Beginning installation of VMSU2 V5.4 at 13:31. %VMSINSTAL-I-RESTORE, Restoring product save set A... 6 The procedure then displays the following message: 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]: Enter the number of the option you want. The system displays the following message: * Do you want to continue the installation? [no] %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. If you want to continue with the update, type YES and press Return. If you want to abort the update procedure, type NO and press Return. In either case, if you select option 1, 2, or 3, the release notes will be displayed or printed. 14 7 Depending on the number of free global pages your system has, the procedure might display a message similar to the following: This installation requires 367 free global pages and only n exist. This will result in an error message at the end of the update procedure stating that DCLtables could not be replaced. This error is not fatal if you reboot immediately after the update completes. Digital recommends that you do not abort the installation to modify the system parameters. Version 5.4-2 does not place greater demands on your system than the previous VMS version. The global pages are used only during the update to replace DCL tables in memory. After this warning occurs, new users cannot log in to the system. Rebooting after the update will rectify the shortage of global pages. 8 The procedure displays the following message: To complete the installation of this product, you should reboot the system. If it is not convenient to reboot at this time, then enter NO to the following question. If you enter NO, the installation procedure will terminate. *Will you allow a system shutdown after this product is installed [YES]? If you cannot boot the system after the update, answer No to this question and the installation procedure stops. If you answer Yes, the procedure continues and displays the following questions about the shutdown that will occur after the update: 15 *How many minutes for system shutdown [0]? *Do you want to do an automatic system reboot [YES]? *Do you want to purge files replaced by this installation [YES]? Purging files deletes multiple copies of files and increases space on the system disk. If you want to purge files replaced by the update, press Return. If you do not want to purge these files, type NO and press Return. 9 The procedure displays the following messages: Completion of this update requires a system reboot. This procedure will automatically shut down the node being updated. Any other VAXcluster nodes using this system disk should be shut down before the installation. Please ignore any messages you see at the end of the installation from INSTALL concerning the failure to REPLACE an entry. The "global page table full" messages accompanying the INSTALL messages should be ignored as well. These messages do not affect the installation, and conditions causing them will be corrected on reboot. If you installed LAT V5.4-1, you must install LAT V5.4-2 after completing the VMS V5.4-2 update. LAT V5.4-2 is provided as a part of this kit. Please refer to the 'Cover Letter for VMS Version 5.4-2' for LAT V5.4-2 installation instructions. Please press Return to continue. 10 Press Return after you have read the display. The procedure displays the following messages: No more questions will be asked... Now applying the updates... (If reapplying the update, ignore any ECOSET messages, and the subsequent NOFILE messages. These are normal and simply mean that the fix has already been applied.) 16 A description of these updates will be placed in file SYS$UPDATE:VMSU2054.TXT at installation completion. %VMSINSTAL-I-RESTORE, Restoring product save set B...) You will see a series of installation messages identifying the files being modified. Note: When updating a tailored system, some files might not be present. Because the update might attempt to repair these files, you should do the following: o Ignore any "file not found" error messages that appear during the application of a VMS maintenance update. o If you use VMSTAILOR or DECW$TAILOR to restore these files at any time, reapply the update after restoring the files. Digital recommends that you back up and restore the system disk before reapplying the update. For more information about using VMSINSTAL and DECW$TAILOR, see the VMS System Manager's Manual. If you are updating a tailored system or reapplying the update, the procedure displays the following message: %VMSUn-E-ERRORS, Of the nnn fixes listed above, the following mm should be reviewed: In the previous message, n is the version number, nnn is the total number of patches, and mm is the number of patches that may have failed. These errors can be related to tailoring your system or reapplying the update; if so, they can be ignored. 17 11 Once the update has been applied, the procedure displays the following message: A description of these changes will be in SYS$UPDATE:VMSU2054.TXT After rebooting, you may wish to run @SYS$UPDATE:VMSU2054-PURGE.COM, which purges old copies of files generated by this installation. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Writing boot block for new VMB... 12 VMSINSTAL creates a journal file (with the file type JNL) for each image that is patched during the update process. (See Section 1.10 for additional information about the JNL files produced by the update.) When VMSINSTAL completes the update, it displays the following message: Installation of VMSU2 V5.4 completed at 13:51 %VMSINSTAL-I-SHUTDOWN, This product requires that the system be rebooted. 13 If your system uses console media, the procedure displays the following message: * Do you want to mount the console volume on ddcu: [NO]? In this message, ddcu represents the device name of the console device, for example, MUA0. Remove the the distribution media from the drive, and insert the console volume. Type YES and press Return. 14 The procedure will now shut down the system. 15 Reboot the updated system disk. If you have a VAXcluster environment, reboot the nodes that use the newly updated system disk. When each node reboots, it will be running Version 5.4-2 of the VMS operating system. 18 ___________________________ 1.8 Tasks to Perform after the Update After you apply a maintenance update to your system, Digital recommends that you perform the following tasks: 1 After the update, you will notice that the space used on the system disk has increased by approximately 7,000 blocks or more (net disk block utilization). Use the following procedure to recover some of this space: Note: Do not use this procedure until you have rebooted the updated system disk and any nodes that use the updated system disk (see Section 1.7). a. If you want to see the patches, go to Section 1.10. b. Display the free block count by entering the following command: $ SHOW DEVICE SYS$SYSDEVICE: c. To purge files that the update procedure could not purge, use the VMSU2054-PURGE.COM command procedure. For example, to purge files produced by a Version 5.4-2 update, enter the following command: $ @SYS$UPDATE:VMSU2054-PURGE You can use the VMS Analyze Utility to determine whether the update procedure purged files completely. For more information, see the VMS Analyze/Disk_Structure Utility Manual. 19 ___________________________ 1.9 Installing Optional LAT Software Note: The LAT software provided with VMS Version 5.4-2 is an update to the LAT software that was provided with VMS Version 5.4-1. If you installed the LAT software provided with VMS Version 5.4-1, you should install the updated VMS Version 5.4- 2 LAT software. The updated LAT software contains software corrections. Skip this section if you are not installing LAT software. The new optional LAT software supersedes LTDRIVER V5.4 and provides the following new functionality: o The SET HOST/LAT command enables you to connect to a LAT service on the same local area network (LAN) or on an extended LAN. o The updated LAT software provides an enhanced and extended $QIO interface. If you choose to install LAT software, you must first update your system to at least VMS Version 5.4-2. To install the LAT software, do the following: 1 Back up the system disk. Although the LAT Version 5.4-2 Installation and Release Notes describe how you can reinstall your original LTDRIVER, that reinstallation procedure does not return your system exactly to its prior LTDRIVER setup. If you have a backup copy of the system disk, you can restore the system disk to its prior state. 2 Log in to the SYSTEM account. 3 Enter the following command: $ @SYS$UPDATE:VMSINSTAL LATU2054 ddcu: where ddcu is the device name of the source drive that holds the update distribution media. If you are updating from a CD drive connected to an InfoServer, the device name is DADn. The n part 20 of the device name was displayed when you bound to the distribution CD as described in Section 1.2. 4 As the update procedure begins, VMSINSTAL displays the following messages: Note: If you are updating using the InfoServer, ignore any error messages about the BYTLM quota being set too low. VAX/VMS Software Product Installation Procedure V5.4-2 It is 5-MAR-1991 at 15:30. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? If you backed up the system disk, press Return and continue. If you have not yet backed up your system disk, do the following: a. Type NO and press Return. VMSINSTAL returns to DCL level to permit you to perform the backup. b. Back up and restore your system disk (see step 2 in Section 1.1). c. When the backup is complete, restart the LAT update procedure at step 1. 5 The procedure displays the following message: Please mount the first volume of the set on ddcu: * Are you ready? Make sure the distribution media is in the correct drive, and enter YES. 21 6 VMSINSTAL continues with the following display: %MOUNT-MOUNTED, VMSU2 mounted on ddcu: The following products will be processed: LATU2 V5.4 Beginning installation of LATU2 V5.4 at 15:31. %VMSINSTAL-I-RESTORE, Restoring product save set A... 7 VMSINSTAL copies the LAT Version 5.4-2 Installation and Release Notes and the VMS LAT Control Program (LATCP) Manual to the SYS$HELP directory. The LAT Version 5.4-2 Installation and Release Notes provide a detailed description of the installation procedure and the functionality of the LAT software. You should read this document before installing the LAT software. 8 The procedure displays the following message: * Do you want to proceed with this installation [N]? If you want to read the LAT Version 5.4-2 Installation and Release Notes, enter NO to exit the procedure. If you enter YES, the procedure continues and displays the following messages: %LATU2-I-NOINQUIRE, No more questions will be asked Installation will take approximately 5 minutes %LATU2-I-BEGIN, Begin installation of LAT V5.4-2 . . . 9 The installation of LAT V5.4-2 software is complete when the procedure displays the following message: Installation of LATU2 V5.4 completed at 15:40 VMSINSTAL procedure done at 15:40 22 10 To restart LAT, you must reboot your system. ___________________________ 1.10 Printing Patches Applied by the Update Kit If you want a listing of the patches produced by the update, you can print the journal files by logging in to any account that has the SYSPRV privilege and entering the following command: $ PRINT SYS$SYSTEM:*.JNL,SYS$LIBRARY:*.JNL,SYS$LOADABLE_IMAGES:*.JNL ___________________________ 1.11 Release Notes The VMSINSTAL procedure copies the VMS Version 5.4-2 release notes to the file SYS$HELP:VMSU2054.RELEASE_NOTES. You can print this file on a line printer or display it at a terminal. 23