____________________________________________________ VMS Version 5.5-2 Update Procedures Order Number: AV-PSY0A-TE August 1992 This document describes how to update the VMS operating system to Version 5.5-2. Revision/Update Information: This is a new manual. Software Version: VMS Version 5.5-2 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ August 1992 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 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. © Digital Equipment Corporation 1992. All Rights Reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DECnet, DEC PHIGS, DECwindows, MSCP, VAX, VAXcluster, VMS, and the DIGITAL logo. ZK5963 This document was prepared using VAX DOCUMENT, Version 2.1. 1 Introduction There are two variations of the VMS Version 5.5 software that you may be running: o V5.5-Runs the single, clusterwide Batch and Print Queuing System introduced in VMS Version 5.5 o A5.5-Runs the batch and print queuing system that was available in the VMS operating system prior to VMS Version 5.5 This update kit contains either a TK50 cartridge, a magnetic tape, or a compact disc to update your VMS software. You can update from the following versions of VMS: o VMS V5.5 or VMS V5.5-1 to VMS V5.5-2 o VMS A5.5 or VMS A5.5-1 to VMS A5.5-2 Note that the VMS Version 5.5-2 software contains all the changes that were available in VMS Version 5.5-1. ________________________ Note ________________________ If your system is running any version of VMS prior to Version 5.5, you need to upgrade to Version 5.5 before you update to Version 5.5-2. To upgrade your system to VMS Version 5.5, obtain the Version 5.5 kit, the VMS Version 5.5 Upgrade and Installation Manual, and the VMS Version 5.5 Release Notes. If, as part of the VMS Version 5.5 upgrade, you chose to convert to the new Batch and Print Queuing System using the command procedure VMS$UPGRADE_A55_V55.COM then you must reboot your system before applying the VMS Version 5.5-2 update. See Section 10 for more details on executing VMS$UPGRADE_A55_V55.COM. ______________________________________________________ 1 2 Necessary Documentation The following sections contain instructions for updating your system to VMS Version 5.5-2. To supplement these instructions, you can reference the following documents: o The VMS upgrade and installation supplement for your VAX computer o VMS Version 5.5 Upgrade and Installation Manual o VMS VAXcluster Manual 3 Preparing to Update Your System Before performing the update, complete the steps in this section: 1. Using standalone BACKUP, make an image backup copy of the system disk. When you update to Version 5.5-2, apply the update to the backup copy. If you cannot apply the update to the backup copy, restore your image backup to the system disk before beginning the update. An image backup stores files contiguously, creating contiguous free space on the system disk. 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 could corrupt the contents of the system disk. Before you perform the update, back up the system disk so that you always have a working copy. ______________________________________________________ 2. If you are not updating a VAX 6000 series computer with an RF-series system disk, go to step 3. If you are updating a VAX 6000 series computer with an RF-series system disk, 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 (refer to Section 3.1 of 2 the VMS Upgrade and Installation Supplement: VAX 6000 Series). The value n.n indicates the version of console microcode installed on your system. Table 1 lists the minimum required versions of console microcode you must have to update to VMS Version 5.5-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.02 Model 500 Series 2.02 2.02 2.02 Model 600 Series 1.01 1.01 [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 Digital Services 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 update to VMS Version 5.5-2. If you do not receive regular console microcode updates, contact your Digital Services representative to obtain the version you need. For more information on upgrading console microcode, refer to your hardware documentation. 3. Caution: If you are a VMS Posix Version 1.0 user, install the VMS Posix Version 1.1 kit prior to or after applying the VMS Version 5.5-2 update. In rare circumstances, the VMS Posix Version 1.0 kit can cause system failure and data corruption. 3 4. The VMS Version 5.5-2 update kit includes DECwindows files that are not compatible with some versions of the layered product DEC PHIGS. If your site currently has Versions 2.3A or 2.3B of DEC PHIGS installed, then you will need to install DEC PHIGS V2.3C after you update your system to VMS Version 5.5-2. DEC PHIGS V2.3C is compatible with the DECwindows files included in this kit. Please note that three-dimensional applications will not work until DEC PHIGS V2.3C has been installed. The VMS Version 5.5-2 update procedure displays a system message describing the DECwindows file options to help you determine your system environment. Refer to the VMS Version 5.5 Release Notes for a more complete description of the options for installing DECwindows files. 5. Log in to the SYSTEM account. 6. Make sure the system disk has enough free blocks. The VMS Version 5.5-2 update requires 67,000 free blocks (for peak disk block utilization). 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 (67,000), go to step 7. 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 c. If there still are not enough free blocks, for example as in a small-disk environment, you have three possible update options: o Use the non-safety-mode option 4 o Use the Alternate Working Device (AWD) option o Use the non-safety-mode with the AWD option Non-Safety Mode-The non-safety-mode option of the update has a peak block usage on the system disk of 30,000 blocks for this update. However, the system disk becomes unusable if the system crashes during the update. (Note that you can recover the contents of your system disk when in non-safety mode with the image backup made in step 1 of this section.) The update procedure automatically detects the small- disk environment and provides prompts through the non-safety-mode option, described in Section 9. Alternate Working Device (AWD)-The AWD option of VMSINSTAL has a peak block usage on the system disk of 15,000 blocks for this update. However, the AWD option requires 67,000 blocks on a designated alternate disk and takes twice as long to perform the update because of the time required to complete the processing to the alternate disk. Note that if you elect not to purge, the AWD option of VMSINSTAL has a peak block usage on the system disk of 67,000 blocks for this update, and additionally requires 67,000 blocks on a designated alternate disk. Section 9 describes how to use the AWD option. Non-Safety Mode with AWD-The non-safety mode with the AWD option of VMSINSTAL has a peak block usage on the system disk of 15,000 blocks and requires 25,000 blocks on a designated alternate disk. However, the system disk becomes unusable if the system crashes during the update. (Note that you can recover the contents of your system disk when in non-safety mode with the image backup made in step 1 of this section.) The update procedure automatically detects the small-disk environment and provides helpful prompts through the non-safety-mode option described in Section 9. 5 7. Make sure the system has enough free global pages. To update to VMS Version 5.5-2, the system requires a minimum of 418 free global pages. If there is an insufficient number of free global pages available, you cannot continue with the update. To determine the number of free global pages, enter the following command at the DCL prompt: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") If the number returned is less than 418, increase the SYSGEN parameter GBLPAGES as necessary: a. For example, if you must increase GBLPAGES by 128 pages, add the following line to the file SYS$SPECIFIC:[SYSEXE]MODPARAMS.DAT: ADD_GBLPAGES=128 b. To change the value of the parameter, run the procedure AUTOGEN.COM using the following command: $ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN c. Reboot your system for the change to take effect. For complete information about how to use AUTOGEN, see the Guide to Setting Up a VMS System. ________________________ Note ________________________ The optimal number of 1605 free global pages is required to install the file DCLTABLES.EXE at the end of the update. If you receive a system message indicating that you have fewer than 1605 free global pages available on your system, you should continue with the update. The update procedure will not fail. At the end of the update, you will receive error messages stating that the global page table is full. You can safely ignore these error messages; this problem is corrected by the automatic reboot that is part of the update procedure. ______________________________________________________ 6 8. To make sure that the SYSTEM account has sufficient quotas and limits, use the VMS Authorize Utility as follows: a. Enter the following commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM b. Compare the SYSTEM account's limits and quotas to the following minimum required values: _____________________________________________________ Quota_Name____________________Minimum_Values_________ Open file quota (FILLM) 100 Buffered I/O limit (BIOLM) 18 Direct I/O limit (DIOLM) 18 AST limit (ASTLM) 24 Enqueue quota (ENQLM) 200 Buffered byte quota count 32768[1] (BYTLM) [1]If_you_are_using_the_InfoServer_to_update_your____ system,_increase_the_value_of_BYTLM_to_33150.________ c. 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 d. Exit the Authorize Utility by entering the following command: UAF> EXIT e. If you adjust any of the SYSTEM account limits or quota values, log out and log in again so the new values take effect. 7 9. Once you are logged in to the SYSTEM account, make sure that you are the only user by completing the following steps: a. Notify current users that they must log out by entering the following command: $ REPLY/ALL/BELL/SHUTDOWN "Log out for VMS V5.5-2 update please..." b. Prevent nonprivileged users from logging in by entering the following command: $ SET LOGINS/INTERACTIVE=0 10.If you are using the InfoServer system to update, proceed to Section 4. 11.If you are not using the InfoServer system, and 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 Proceed to Section 5. 4 Using the InfoServer System to Update Your System If you are using the InfoServer system for your update, start the InfoServer Client software and make the compact disc drive accessible to your system. This section describes these tasks. To start the InfoServer Client software, perform the following steps: 1. If you have a standalone system running A5.5 or A5.5-1, you must define the SYSGEN parameter SCSNODE. To see whether SCSNODE is defined on your system, enter the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SHOW SCSNODE 8 If SYSGEN displays a value for SCSNODE, proceed to the next step. If SYSGEN does not display a value for SCSNODE, enter the following commands, where node is a unique node name up to six characters in length: 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 upgrade and installation supplement for your VAX computer. For more information about SCSNODE as it pertains to VAXcluster batch and print queues, see the VMS DCL Dictionary or the VMS VAXcluster Manual. 2. If you use DECnet software, make sure that it is already started. To check the status of your DECnet software, enter the following command: $ SHOW NETWORK If the system displays the following message, DECnet is not running: %SHOW-I-NONET, network unavailable Start the network by entering the following command: $ @SYS$MANAGER:STARTNET For more information about DECnet network software, see the Guide to DECnet-VAX Networking. 3. Start the InfoServer Client software by entering the following command: $ @SYS$STARTUP:ESS$STARTUP CLIENT The CLIENT parameter loads the client driver, ESS$DADDRIVER.EXE, and the InfoServer transport driver, ESS$LASTDRIVER.EXE. 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 node 9 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 4. After you start the InfoServer Client software, you must make the compact disc drive accessible to your system by completing the following steps: a. Insert the VMS distribution compact disc into the drive connected to the InfoServer system. b. Enter the following commands: $ RUN SYS$SYSTEM:ESS$LADCP LADCP> BIND VMSU2055 %LADCP-I-BIND, service bound to logical unit DAD$VMSU2055 (_DADn:) LADCP> EXIT Make note of the device name _DADn: because you must specify this device name during the update procedure. ________________________ Note ________________________ If you have installed the InfoServer Tape Client for VMS (ESS020 or ESS021) on the system to be upgraded to V5.5-2, you will need to reinstall the tape client at the conclusion of the upgrade to restore the tape client funtionality. ______________________________________________________ 5 Matching Update Procedures to System Configurations Different system configurations require slightly different update procedures. The following list indicates the possible system configurations and the section of this document to which you should refer: o VAXcluster environment (not including mixed-version VAXclusters and Local Area VAXclusters with one boot server and two system disks): Section 6 10 o Mixed-version VAXcluster environment (for example, one that combines systems running VMS Version 5.5 with systems running VMS Version 5.5-2): Section 7 o Local Area VAXcluster environment with one boot server and two system disks: Section 8 o Standalone system: Section 9 6 Updating VAXcluster Environments Use the following procedure to update VAXcluster environments that do not include mixed-version VAXcluster systems and Local Area VAXcluster systems 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 7. ______________________________________________________ 1. Make sure that you have prepared your system for the update, as described in Section 3. 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 according to the instructions in Section 9. 5. If the VAXcluster environment uses several system disks, repeat steps 1 through 4 in this section for each system disk in the VAXcluster environment. 6. After the update is complete, follow the steps in Section 10. 11 7 Performing a Rolling Update for Mixed-Version VAXcluster Environments Perform a rolling update when you want nodes in a VAXcluster environment to run different versions of the VMS operating system. Because 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.5-2 rolling update, systems running VMS Versions 5.4 through 5.5-1 can remain 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 6. ________________________ Note ________________________ If you did not convert to the new Batch and Print Queuing System when you upgraded to VMS Version 5.5, your operating system version is A5.5. With A5.5, the following versions of the VMS operating system are supported in mixed-version VAXcluster environments: V5.4, V5.4-0A, V5.4-1, V5.4-1A, V5.4-2, V5.4-3, A5.5, A5.5-1, and A5.5-2. If you upgraded to the new Batch and Print Queuing System when you installed VMS Version 5.5, your operating system version is V5.5. With V5.5, the following versions of the VMS operating system are supported in mixed-version VAXcluster environments: V5.5, V5.5-1, and V5.5-2. ______________________________________________________ You can perform the VMS Version 5.5-2 update only on systems that are running Version 5.5 or Version 5.5-1. If none of the systems in your cluster are running Version 5.5 or Version 5.5-1, obtain the Version 5.5 kit and upgrade one system disk to Version 5.5. ________________________ Note ________________________ Shadow set members that support the VMS Volume Shadowing assisted merge (minimerge) operation can be VMS MSCP served only by VAXcluster nodes running VMS Version 5.5-2. Shadow sets supporting the minimerge operation cannot be served by multiple VAXcluster 12 nodes that are running a mixture of Version 5.5-2 and previous versions of the VMS operating system. See the VMS Version 5.5-2 Release Notes for more details on the VMS Volume Shadowing assisted merge (minimerge) operation. ______________________________________________________ If the system you are upgrading to VMS Version 5.5 is running Version 5.4-3, and your configuration contains at least two computer systems with CIXCDs that boot from different system disks, you must install a patch to all Version 5.4-3 system disks before you begin the Version 5.5 upgrade. For information about installing the patch, see the VMS Version 5.5 Upgrade and Installation Manual. In order for DECnet-VAX cluster alias logic to operate correctly across a mixed-version cluster, a DECnet-VAX upgrade kit must be applied to all nodes running versions of the VMS operating system that are prior to VMS Version 5.5-2. This DECnet-VAX upgrade kit is included in the VMS Version 5.5-2 update kit for your convenience. After the VMS Version 5.5-2 update is complete, perform the following steps to copy and install the DECnet-VAX upgrade kit: 1. Log in to the SYSTEM account on a node booted from a system disk that is running a version of VMS previous to Version 5.5-2. 2. Copy the saveset to this disk as follows: COPY ddcu:[VMS$COMMON.SYSUPD]DECNETIV_0551A1.A SYS$COMMON:[SYSUPD] where: ddcu is the name of the VMS Version 5.5-2 system disk. 3. Use VMSINSTAL to apply the upgrade kit as follows: $ @SYS$UPDATE:VMSINSTAL DECNETIV_0551A1 SYS$UPDATE 4. Reboot all the nodes running VMS Version 5.4 through Version 5.5-1 that boot from the disk to which the DECnet upgrade kit was applied. 5. Repeat the above steps for each system disk that is running a version of VMS previous to Version 5.5-2. 13 _______________________ Caution _______________________ Failure to do so may result in system failure and data corruption. ______________________________________________________ To perform a rolling update, complete the following steps: 1. Make sure you have prepared your system for the update, as described in Section 3. 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. Review your quorum setup before shutting down any nodes. See the VMS VAXcluster Manual for additional information. 4. Apply the update as described in Section 9. 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. Repeat steps 1 through 4 in this section for each additional system disk that you are updating. 6. After the update is complete, follow the steps in Section 10. 8 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 3 to prepare your system for the update. 4. Apply the update to the first system disk, as described in Section 9. 14 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 9. 6. After the update is complete, follow the steps in Section 10. 9 Applying the Version 5.5-2 Update To update the VMS operating system to Version 5.5-2, complete the following steps: 1. Place the VMS distribution media into the drive. (If you are using the InfoServer system, you should have already inserted the compact disc and completed the steps in Section 4.) 2. Start the update with VMSINSTAL. ________________________ Note ________________________ If the installation is being done in a small-disk environment and you do not have enough free blocks as determined during step 5 of Section 3, you can follow the non-safety-mode prompts within the update procedure or enter the alternate working device (AWD) option, or both. ______________________________________________________ o To start the VMSINSTAL command procedure without the AWD option, enter the following command: @SYS$UPDATE:VMSINSTAL VMSU2055 ddcu: OPTIONS N where: ddcu is the device name of the source drive that holds the VMS distribution media. The OPTIONS N portion of the command indicates that you want to display the release notes option menu, from which you can view or print the release notes. 15 Note that the command procedure can also be run in non-safety mode by responding to the non-safety- mode prompt that occurs if your free disk blocks are limited, as shown in step 8 of this section. The following example shows the command line you would enter if your distribution media (VMSU2055) were loaded on a TK50 tape cartridge drive on controller B, with unit number 3: $ @SYS$UPDATE:VMSINSTAL VMSU2055 MUB3: OPTIONS N If you are updating from a compact disc drive connected to the InfoServer system, the device name is DADn. The n part of the device name was displayed when you bound to the distribution compact disc, as described in Section 4. o To start the VMSINSTAL command procedure with the AWD option, enter the following command: @SYS$UPDATE:VMSINSTAL VMSU2055 ddcu: OPTIONS N,AWD=adcu:[dir] where: ddcu is the device name of the source drive that holds the update distribution media. The OPTIONS N portion of the command indicates that you want to display the release notes option menu. adcu defines the alternate drive. See Section 3 for the required number of free blocks that must be available on the system disk and the alternate work disk. dir in the AWD option entry specifies the directory under which the [.VMSU2055] subdirectory will be created. Specifying a directory is optional. If you do not specify a directory, VMSINSTAL creates the working directory on the specified device with the directory specification [000000.VMSU2055], which is defined as the logical name VMI$KWD. If you specify a directory, VMSINSTAL creates the working directory as a subdirectory to the directory that you specify. 16 The following example shows the command line that you would enter to create the working directory [INSTALL.VMSU2055] on the alternate device DUA2: if your distribution media (VMSU2055) were loaded on a TK50 tape cartridge drive on controller B, with unit number 3: $ @SYS$UPDATE:VMSINSTAL VMSU2055 MUB3: OPTIONS N,AWD=DUA2:[INSTALL] Note that the AWD command option can also be run in the non-safety mode by responding to the non-safety- mode prompt (see step 8 of this section). If the VMSINSTAL command fails, check the error messages to see if any of the following conditions occurred: o You may have entered the letter O rather than the number 0 in the product name. VMSINSTAL displays the following message: %VMSINSTAL-E-NOPRODS, None of the specified products were found o You may have 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. ________________________ Note ________________________ If you are updating using the InfoServer system, the procedure may display error messages stating that the BYTLM quota is too low. If you set the BYTLM quota for the system account to 33150 before the update (as described in Section 3), you can ignore these messages. ______________________________________________________ 3. As the update procedure begins, VMSINSTAL displays messages similar to the following: VAX/VMS Software Product Installation Procedure V5.5 It is 23-AUG-1992 at 13:30. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? 17 If you backed up the system disk, press the Return key and go to step 4. If you have not yet backed up the system disk, do the following: a. Enter NO and press the Return key. VMSINSTAL returns to DCL level to permit you to perform the backup. b. Back up the system disk (as described in step 1 in Section 3). c. When the backup is complete, restart the update procedure at step 1 in this section. 4. 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. 5. VMSINSTAL continues with the following display: %MOUNT-I-MOUNTED, VMSU2 mounted on ddcu: The following products will be processed: VMSU2 V5.5 Beginning installation of VMSU2 V5.5 at 13:31. %VMSINSTAL-I-RESTORE, Restoring product save set A... 6. If you specified OPTIONS N, 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]: 18 Enter the number of the option you want. Note that if you select option 2, printing the release notes for VMS Version 5.5-2 uses approximately 120 pages. Note that a printed copy of the VMS Version 5.5-2 Release Notes is provided in your kit. The system displays the following message: * Do you want to continue the installation? [NO] If you want to continue with the update, enter YES and press the Return key. If you want to stop the update procedure, enter NO and press the Return key. In either case, if you selected option 1, 2, or 3, the release notes will be displayed or printed according to your choice. 7. The procedure displays the following message: %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. *Do you want to purge files replaced by this installation [YES]? Purging files deletes multiple copies of files and frees space on the system disk. If you have a small- disk environment, you should purge files to conserve space. If you want to purge files replaced by the update, press the Return key. If you do not want to purge these files, enter NO and press the Return key. 8. The VMSINSTAL procedure can detect a small-disk system environment and sends a message if there is insufficient disk space to update using safety mode on the system disk or an alternate working device (AWD). If insufficient disk space is detected, you are given the option of continuing the update procedure using non-safety mode described as follows. Note that if you elect to continue in non-safety mode, your files will be automatically purged. If you do not receive a non-safety-mode message, go to the next step. 19 If a non-safety-mode message is displayed as follows, indicate whether you will continue the update procedure by entering YES or NO in response to the system prompt. o Non-Safety Mode-Option: If you receive the following message, you do not have enough free disk blocks to accommodate an update in safety mode: *** Insufficient Disk Space to run in Safety Mode *** Installation of this kit requires 67,000 free blocks on the system disk in safety mode. You have 55980 free blocks on your system disk. **** Non-Safety Mode Check being Made **** There is sufficient disk space to install this kit in non-safety mode. If a crash occurs before this installation is complete, your system may be rendered unusable. *** WARNING *** If you elect to run in Non-safety Mode files replaced by this installation will be PURGED. If you answer NO to the following question, the installation of 5.5-2 will terminate. * Do you want to continue in non-safety mode (Y/N)? o Non-Safety-Mode Option with AWD: If you selected the AWD option, and do not have enough free disk blocks to accommodate an update in the safety mode, you will receive the following message: *** Insufficient Disk Space to run in Safety Mode *** Installation of this kit requires 15,000 free blocks on the system disk, and 67,000 free blocks on the alternate working disk to run in safety mode. You have 12133 free blocks on your system disk and 59685 free blocks on your alternate working disk. **** Non-Safety Mode Check being Made **** There is sufficient disk space to install this kit in non-safety mode. If a crash occurs before this installation is complete, your system may be rendered unusable. If you answer NO to the following question, the installation of 5.5-2 will terminate. 20 * Do you want to continue in non-safety mode (Y/N)? Answer NO to this question to reject the non-safety mode and stop the procedure. See step 5 of Section 3 to determine block sizes for the various update options. Answer YES to this question to continue the update. (Note that during the procedure, you accept a remote risk of a system crash that might destroy all existing software on the system disk. You could recover the contents of your disk from the image backup made in step 1 of Section 3.) 9. As you continue with the update, the system goes on to display 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, enter NO to this question and the update procedure stops. 10.If you can boot the system, enter YES and the procedure continues and displays the following questions about the shutdown that will occur after the update: *How many minutes for system shutdown [0]? *Do you want to do an automatic system reboot [YES]? 11.The procedure then 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. 21 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.) A list of these updates will be placed in file SYS$UPDATE:VMSU2055.TXT at installation completion. %VMSINSTAL-I-RESTORE, Restoring product save set B... %VMSINSTAL-I-RESTORE, Restoring product save set C... %VMSINSTAL-I-RESTORE, Restoring product save set D... %VMSINSTAL-I-RESTORE, Restoring product save set E... The preceding four restore messages are followed by a series of installation messages identifying the files being modified during a safety-mode update. In a non- safety-mode update, you will see the restore message for each of the save sets B, C, D, and E interspersed among the installation messages. ________________________ Note ________________________ If you are updating a tailored system, some files might not be present. Because the update might attempt to modify these missing files, you should do the following: o Ignore any "file not found" error messages that appear during the application of a VMS update. o If you use VMSTAILOR or DECW$TAILOR to restore 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 VMSTAILOR and DECW$TAILOR, see the VMS Version 5.5 Upgrade and Installation Manual. ______________________________________________________ 22 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: where: n is the version number. nnn is the total number of patches. mm is the number of patches that may have failed. If these errors are related to tailoring your system or reapplying the update; they can be ignored. 12.Once the update has been applied, the procedure displays the following message: After rebooting, you may wish to run @SYS$UPDATE:VMSU2055-PURGE.COM, which purges old copies of files generated by this installation. The following message is displayed only during a safety- mode update: %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... You may receive either of the following network (NCP) messages, which can be ignored: %NCP-W-UNRCMP, Unrecognized component, Object Or: %NCP-I-SUCCESS, Success Object = X$X0 %NML-I-RECDELET, Database entry deleted The procedure then writes the new VMB boot block: Writing boot block for new VMB... If DECwindows layered products that have special fonts are installed on your system, the screen displays a series of messages listing the associated font files. The listing of files indicates they are available in the directory DECW$MKFONTDIR. 13.When VMSINSTAL completes the update, it displays a message similar to the following: 23 Installation of VMSU2 V5.5 completed at 14:59 %VMSINSTAL-I-SHUTDOWN, This product requires that the system be rebooted. SHUTDOWN -- Perform an Orderly System Shutdown on node 14.If you are installing the update from a console drive, the procedure displays the following question: * 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 distribution media from the drive, and insert the console volume. Enter YES and press the Return key. 15.The procedure now shuts down the system. 16.Reboot the system with 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.5-2 of the VMS operating system. ________________________ Note ________________________ VMSINSTAL creates a journal file (with the file type .JNL) for each image that is patched during the update process. (See Section 10 for additional information about the .JNL files produced by the update.) ______________________________________________________ 10 Tasks to Perform After the Update After you apply an update to your system, Digital recommends that you perform the following tasks: o 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 24 o Display the free block count on the system disk by entering the following command: $ SHOW DEVICE SYS$SYSDEVICE: ________________________ Note ________________________ Do not perform the following procedure until you have rebooted the updated system disk and any nodes that use the updated system disk to complete the update (as in Section 9). ______________________________________________________ o To purge files that the update procedure could not purge, use the VMSU2055-PURGE.COM command procedure. For example: $ @SYS$UPDATE:VMSU2055-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. o The VMSINSTAL procedure copies the VMS Version 5.5-2 Release Notes to the file SYS$HELP:VMSU2055.RELEASE_ NOTES. You can print this file on a line printer or display it at a terminal. (Note that printing the release notes uses approximately 120 pages.) You are not required to print the VMS release notes, a printed copy of the VMS Version 5.5-2 Release Notes is provided in your kit. o If you are currently running Version A5.5 or A5.5-1, Digital strongly recommends that you update to the new job controller and queue manager immediately after you complete the VMS Version 5.5-2 update. ________________________ Note ________________________ For clustered systems, the minimum version of all nodes must be A5.5-1 before you update to the new job controller and queue manager. ______________________________________________________ 25 If you are running A5.5 or A5.5-1, you should complete the Version 5.5-2 update procedure before updating to the new job controller and queue manager. After you complete the VMS Version 5.5-2 update, perform the following tasks to update to the new job controller and queue manager: 1. Reboot the system. 2. Log in to the SYSTEM account. 3. Enter the following command to invoke the command procedure VMS$UPGRADE_A55_V55.COM: $ @SYS$UPDATE:VMS$UPGRADE_A55_V55.COM The command procedure displays the following question: "Do you wish to convert queues now ? (YES,NO,ABORT)" 4. Enter YES. The procedure updates to VMS Version 5.5- 2, with the new job controller and queue manager. Upon completion of the upgrade, the new queue manager is left in a stopped state. When you enter the START/QUEUE/MANAGER command to start the queue manager, the queue manager database will contain information transferred from the old queue database file JBCSYSQUE.DAT. ________________________ Note ________________________ After you enter YES in response to the queue conversion question, do not include the /NEW qualifier with the START/QUEUE/MANAGER command. This qualifier overwrites the queue database. ______________________________________________________ If you enter NO, the procedure updates your system to VMS Version V5.5-2, with the new job controller and queue manager. However, the information in the A5.5 queue database file JBCSYSQUE.DAT is not transferred to the new queue database. When you start the queue manager, the database will be empty. 26 If you enter ABORT to this question, you do not update to VMS Version V5.5-2. The original job controller and queue manager still manage queue activity by manipulating data in the original queue database file JBCSYSQUE.DAT. Digital recommends you update to A5.5-1 or A5.5-2 before converting to the new job controller and queue manager. Do not update A5.5 systems to the new job controller and queue manager. 27