Document revision date: 19 July 1999

If you want to install layered products, go to the next section.

If you do not want to install layered products or perform any other operations prior to booting the upgraded disk, do the following:

1. Shut down the system by choosing the shutdown option (8) from the menu.
2. Go to Section 7.4.

You can use the menu system included on the operating system CD-ROM to install certain layered products with the POLYCENTER Software Installation utility. You can view a list of the layered products that can be installed in this way by choosing option 2 from the menu. (To install layered products that are not listed, see Chapter 4 and the installation documentation for each layered product.)

You may see the following product name while installing layered products:

DEC AXPVMS UCX V4.2-PLACEHOLDER

Do not attempt to install this kit. This is a "dummy" that is needed for technical reasons to facilitate upgrading from the prior UCX implementation of DIGITAL TCP/IP Services to the new implementation.

If you do attempt to install this kit, the following message will be displayed:

The UCX implementation of TCP/IP Services is obsolete and is not supported on OpenVMS V7.2 and higher versions. Starting with OpenVMS V7.2, the UCX implementation of TCP/IP services is replaced by the new TCPIP product. This is a placeholder kit to satisfy OpenVMS upgrade requirements so that UCX can be automatically upgraded to TCPIP. You cannot use this kit to install UCX.

The installation will then terminate.

You can install (or upgrade to) the new implementation of DIGITAL TCP/IP services, version 5.0, as part of the OpenVMS upgrade. If you wish to install version 5.0 separately, choose the product:

DEC AXPVMS TCPIP V5.0-9

To install layered products using the POLYCENTER Software Installation utility, choose option 2 to view the list and then option 3 to perform the installation. For example:

Please choose one of the following: 1) Upgrade, install or reconfigure OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 2 The following versions of the OpenVMS operating system, the DECwindows graphical user interface and network products. are available on the OpenVMS Distribution compact disk. They can be installed by selecting choice 1: DEC AXPVMS VMS version V7.2 DEC AXPVMS DWMOTIF version V1.2-5 DEC AXPVMS DECNET_OSI version V7.2 DEC AXPVMS DECNET_PHASE_IV version V7.2 DEC AXPVMS TCPIP version V5.0-9 The following Layered Product kits are available on the OpenVMS Distribution Compact Disk. They can be installed by selecting choice 3. If already installed, they can be reconfigured by selecting choice 5, or removed by selecting choice 6. ----------------------------------- ----------- ---------- PRODUCT KIT TYPE KIT FORMAT ----------------------------------- ----------- ---------- DEC AXPVMS DECNET_OSI V7.2 Full LP Sequential DEC AXPVMS DECNET_PHASE_IV V7.2 Full LP Sequential DEC AXPVMS DWMOTIF V1.2-5 Full LP Sequential DEC AXPVMS TCPIP V5.0-9 Full LP Sequential DEC AXPVMS UCX V4.2-99PLACEHOLDER Full LP Sequential ----------------------------------- ----------- ---------- 5 items found Press Return to continue... **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 3 *********************************************************** If you choose to install or upgrade to DECwindows Motif, please note the following: o If you did not select the OpenVMS DECwindows base support and workstation files options, DECwindows Motif will not run. You must add these options to use DECwindows Motif. o If you are upgrading DECwindows Motif from Version 1.1 and want to save the OSF/Motif Release 1.1.3 programming files, DO NOT upgrade now. Instead, see the DECwindows Motif Installation Manual and follow the instructions for running PCSI_INSTALLATION.COM. If you choose to install or upgrade DECnet-Plus or DECnet Phase IV, please note the following: o If you did not select the OpenVMS DECNET option, neither version of DECnet will run. You must add this option to use DECnet. You must enter the device name for the target disk on which the layered product(s) install will be performed. Enter device name for target disk: (? for choices) DKB400 DKB400: is labeled ALPHAUPGIV. The installation can provide brief or detailed descriptions. In either case, you can request the detailed descriptions by typing "?". Do you always want detailed descriptions? (Yes/No) [No] 1 - DEC AXPVMS DECNET_OSI V7.2 Layered Product 2 - DEC AXPVMS DECNET_PHASE_IV V7.2 Layered Product 3 - DEC AXPVMS DWMOTIF V1.2-5 Layered Product 4 - DEC AXPVMS TCPIP V5.0-9 Layered Product 5 - DEC AXPVMS UCX V4.2-99PLACEHOLDER Layered Product 6 - All products listed above 7 - Exit Choose one or more items from the menu separated by commas:

If you do not want to perform any other operations after you install the layered products, do the following:

1. Shut down the system by choosing the shutdown option (8) from the menu.
2. Go to the next section to perform specific tasks after the system shuts down.

After the system shuts down, you need to perform certain tasks, depending on the configuration of your system and the type of upgrade you are performing. Refer to the appropriate section.

If you are upgrading a standalone system:

1. Reboot the system.
2. Log in to the system.
3. Go to Chapter 8 to perform additional postupgrade procedures.

If you are performing a concurrent upgrade in an OpenVMS Cluster environment:

IF ...	THEN ...
you have one system disk,	do the following: Reboot each system that uses the upgraded disk. Go to Chapter 8.
you have multiple system disks,	do the following: Repeat the upgrade process for each system disk in the cluster, beginning with the preupgrade tasks described in Chapter 5. Reboot each system in the cluster. Log in to an upgraded system. Go to Chapter 8 to perform additional postupgrade procedures.

7.4.3 Rolling OpenVMS Cluster Upgrade

If you are performing a rolling upgrade in an OpenVMS Cluster environment:

1. Log in to the upgraded system.
2. Go to Chapter 8 to perform additional postupgrade procedures. (You will reboot the other systems that boot from the upgraded disk after you complete those tasks.)

After you upgrade the OpenVMS Alpha operating system, you need to perform several important tasks before you can use the system. These tasks, described in the order in which you perform them, are as follows:

• Reforming the shadow set (if applicable)
• Registering new licenses
• Examining the AUTOGEN report file
• Modifying the system parameters file (MODPARAMS.DAT)
• Examining your command procedures
• Decompressing system libraries
• Testing the system with UETP, the user environment test package
• Adding and removing operating system files
• Preparing your OpenVMS Alpha system and your PC to run OpenVMS Management Station
• Installing layered products
• Backing up the customized system disk
• Rebooting cluster members (if applicable)
• Running AUTOGEN
• Completing the postupgrade checklist

If you have upgraded a disk in a volume shadowing environment, you must now reform the shadow set as follows:

1. Enter the SHOW DEVICE D command to display a list of disks available on your system. For example:

   $ SHOW DEVICE D Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt $11$DKB100: (NODE1) Online 0 $11$DKB200: (NODE1) Mounted 0 ALPHA070 918150 1 31

2. Enter a command in the following format:

   $ MOUNT/CONFIRM/SYSTEM DSAn: /SHADOW=(upgraded-disk:,new-member:) volume-label

   
   Note the following conventions:

   • DSAn: is the virtual unit name of the shadow set.
   • upgraded-disk: is the name of the shadowed system disk you just upgraded.
   • new-member: is the name of the disk you want to add as a member of the shadow set.
   • volume-label is the volume label of the shadowed system disk you just upgraded.

   Note When you reform the shadow set, the contents of the new member are replaced by the contents of the disk you upgraded. Specifying the /CONFIRM qualifier reminds you of this fact, confirming that you are specifying the correct name of a disk that either is blank or contains files you no longer need.

Example

$ MOUNT/CONFIRM/SYSTEM DSA54: /SHADOW=($11$DKB200:,$11$DKB100:) ALPHA072 %MOUNT-F-SHDWCOPYREQ, shadow copy required Virtual Unit - DSA54 Volume label ALPHA072 Member Volume label Owner UIC $11$DKB100: (NODE1) SCRATCH [100,100] Allow FULL shadow copy on the above member(s)? [N]: YES

8.2 Registering New Licenses

If you need to register new OpenVMS Alpha or layered product licenses, you can do so by entering the following command:

$ @SYS$UPDATE:VMSLICENSE

You can also use the LICENSE REGISTER command.

For information about registering licenses, see the following:

• Section 3.4 in Chapter 3
• Appendix C
• The OpenVMS License Management Utility Manual

When AUTOGEN runs, it writes informational and, if necessary, warning messages to the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You should examine the contents of this report file.

To view AGEN$PARAMS.REPORT on your screen, enter the following command and press the Return key:

$ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT

(You can also print this file or examine it using the EDIT/READ_ONLY command.)

For more information on AGEN$PARAMS.REPORT, see the OpenVMS System Manager's Manual.

If the report includes a message similar to the following, you might need to modify the size of the page, swap, or dump file:

%AUTOGEN-W-DSKSPC, The disk on which DKA0:[SYS0.SYSEXE]PAGEFILE.SYS resides would be over 95% full if it were modified to hold 20000 blocks.

For more information about modifying the sizes of the page, swap, and dump files, see the next section.

8.4 Modifying the System Parameters File

Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade procedure created a new version of this file. The old version is named SYS$SYSTEM:MODPARAMS.DAT_OLD. The new MODPARAMS.DAT file contains all the parameters in the old file, plus various parameters that the upgrade procedure added to ensure that all necessary system parameters are properly propagated from the prior version of OpenVMS. The upgrade procedure also adds comment lines to explain the source of the parameters in each section of the new MODPARAMS.DAT file.

Note that the old MODPARAMS.DAT is included in the new MODPARAMS.DAT each time an upgrade is performed. Because of this, if MODPARAMS.DAT is not reviewed and "cleaned up" after each upgrade, it will eventually contain many levels of duplicated parameters. For this reason, you should review MODPARAMS.DAT after each upgrade. This allows you to eliminate the duplication. You can also take this opportunity to modify any parameters, if necessary.

The following two sections are examples of instances where you need to modify parameters in MODPARAMS.DAT.

8.4.1 System File Sizes

AUTOGEN sets the following files at sizes appropriate for your system:

• [SYSEXE]SYSDUMP.DMP
• [SYSEXE]PAGEFILE.SYS
• [SYSEXE]SWAPFILE.SYS

If you have special workloads or configurations, you can specify different sizes for these files by performing the following steps:

1. Log in to the SYSTEM account.
2. Enter the following command:

   $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES

3. If the file sizes displayed need to be adjusted, add symbols to the MODPARAMS.DAT file (described in detail in the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems) and repeat step 2 until you are satisfied with the file sizes.
4. When you are satisfied with the file sizes, enter the following command to ensure that the modified system files are installed when the system is rebooted:

   $ @SYS$UPDATE:AUTOGEN GENPARAMS REBOOT

If you are upgrading an OpenVMS Cluster system, note the following:

• The upgrade procedure creates a new MODPARAMS.DAT for system root on your system disk. Normally, there is one root for each Alpha computer that boots from the system disk. You must review each of these MODPARAMS.DAT files.
  The MODPARAMS.DAT file for the system on which you are running is located in SYS$SYSTEM:MODPARAMS.DAT. The MODPARAMS.DAT files for other roots on the same system disk can be found in SYS$SYSDEVICE:[SYSx.SYSEXE]MODPARAMS.DAT, where x represents the root number; for example, SYS0, SYS1, SYS2, and so forth. (Valid root numbers may include hexadecimal digits---SYSA, SYSB, and so forth.)
• Be sure the EXPECTED_VOTES value is correct. That value is the sum of all VOTES in the cluster. For example, if there are five Alpha computers in the cluster and each has one VOTE, the value is 5.
• As you reboot each Alpha computer, AUTOGEN runs automatically. The cluster forms when you have booted enough computers to attain cluster quorum.

The upgrade procedure retains the site-specific versions of the following files located in the [VMS$COMMON] directory:

[SYSMGR]LAT$SYSTARTUP.COM [SYSMGR]LOGIN.COM [SYSMGR]SYCONFIG.COM [SYSMGR]SYLOGICALS.COM [SYSMGR]SYLOGIN.COM [SYSMGR]SYPAGSWPFILES.COM [SYSMGR]SYSECURITY.COM [SYSMGR]SYSHUTDWN.COM [SYSMGR]SYSTARTUP_VMS.COM [SYSMGR]TFF$SYSTARTUP.COM [SYSMGR]WELCOME.TXT [SYS$STARTUP]ESS$LAST_STARTUP.DAT

The upgrade procedure may provide new templates for some of these files with the .TEMPLATE extension. The new templates might include features that are not in your site-specific files. Check the templates against your site-specific files and edit your files as necessary.

8.6 Testing the System with UETP

The User Environment Test Package (UETP) is a software package designed to test whether the OpenVMS Alpha operating sytem is installed correctly. As part of the postupgrade procedure, Compaq recommends that you run UETP to verify the upgrade.

For complete information about using UETP, see the OpenVMS System Manager's Manual.

8.7 Decompressing System Libraries

Decompressing the system libraries gives the system faster access to them. The decompressed libraries require several thousand additional blocks of disk space for all libraries to be decompressed. You use the LIBDECOMP.COM procedure to decompress the libraries.

8.7.1 Determining Disk Space

To find out how much disk space you have, enter the following command and press the Return key:

$ SHOW DEVICE SYS$SYSDEVICE

If you have approximately 30,000 free blocks on the disk, you can decompress the libraries. Note that you can choose to decompress only the libraries that are used frequently.

8.7.2 Methods of Using LIBDECOMP.COM

You can use the LIBDECOMP.COM procedure to decompress libraries in three ways:

• Entering a command and responding to prompts from the procedure
• Entering an interactive command
• Entering a batch command

The following three sections describe each method.

If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure, do the following:

1. Enter the following command and then press the Return key:

   $ @SYS$UPDATE:LIBDECOMP.COM

   
   The following information is displayed:

   OpenVMS Library Decompression Utility 1 HELPLIB.HLB 14 NCPHELP.HLB 27 PHONEHELP.HLB 2 STARLET.OLB 15 SDA.HLB 28 LIB.MLB 3 ACLEDT.HLB 16 SHWCLHELP.HLB 29 STARLET.MLB 4 ANLRMSHLP.HLB 17 SYSGEN.HLB 30 STARLETSD.TLB 5 DBG$HELP.HLB 18 ANALAUDIT$HELP.HLB 31 SYS$STARLET_C.TLB 6 DBG$UIHELP.HLB 19 SYSMANHELP.HLB 32 ERFLIB.TLB 7 DISKQUOTA.HLB 20 TFF$TFUHELP.HLB 33 SYS$LIB_C.TLB 8 EDFHLP.HLB 21 EXCHNGHLP.HLB 34 VAXCCURSE.OLB 9 INSTALHLP.HLB 22 TPUHELP.HLB 35 VAXCRTL.OLB 10 LATCP$HELP.HLB 23 EVE$HELP.HLB 36 VAXCRTLD.OLB 11 MAILHELP.HLB 24 EVE$KEYHELP.HLB 37 VAXCRTLT.OLB 12 MNRHELP.HLB 25 UAFHELP.HLB 38 IMAGELIB.OLB 13 EDTHELP.HLB 26 TECO.HLB 39 VMS$VOLATILE_PRIVATE_INTERFACES.OLB A ALL libraries to be decompressed E EXIT this procedure * Enter letter or number(s) of libraries to be decompressed (Separate multiple entries with a comma):

2. Enter the appropriate letter or the numbers of the libraries you want to decompress. To decompress all libraries, the process takes approximately one-half hour.

You can execute LIBDECOMP.COM interactively to decompress up to eight libraries at a time by listing the names of the libraries you want to decompress as parameters on the command line.

Be sure to separate the library names with commas and do not include the file extensions. For example, to decompress VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB interactively, enter the following command:

$ @SYS$UPDATE:LIBDECOMP VAXCRTL, DISKQUOTA, LIB

	privacy and legal statement
6522PRO_009.HTML