Document revision date: 19 July 1999

The following restrictions apply to rolling upgrades. See the OpenVMS Version 7.2 Release Notes for additional compatibility issues and restrictions.

• Rolling upgrades are supported from Version 6.2-xxx and 7.1-xxx of the OpenVMS Alpha operating system. Rolling upgrades in mixed-architecture OpenVMS Cluster environments are supported with VAX computers running Versions 7.1 or 6.2 of the OpenVMS VAX operating system (see Table 6-1).
• The upgraded system does not attempt to access any disk that is being accessed by one or more of the remaining OpenVMS Cluster systems.
• The remaining OpenVMS Cluster systems do not attempt to access the target disk of the system being upgraded.
  If the target disk being upgraded is locally attached to the system performing the upgrade, then it is not accessible to the remaining OpenVMS Cluster systems. (The OpenVMS system booted from the operating system CD-ROM does not MSCP serve local disks.) Whenever possible, Compaq recommends that you perform the upgrade on a local disk or that you perform a concurrent upgrade.
  During the upgrade, be sure that the target disk you select, as well as any disk you access from the DCL menu option, is either a local disk or one that is not being accessed by any of the remaining OpenVMS Cluster members.

  Note Any attempt to access the target disk from the remaining OpenVMS Cluster members will corrupt the target disk in most cases. Even if the target disk is mounted only by a remaining cluster member, and no file access is done, the target disk will probably be corrupted. If a disk is corrupted in this way, the only supported recovery is to restore the backup copy of the corrupted disk.

• Compaq recommends that all Alpha computers in a cluster run the same (and preferably the latest) version of the OpenVMS Alpha operating system.
• You cannot perform a rolling upgrade if all systems boot from a single system disk. Perform a concurrent upgrade instead.
• The upgrade procedure affects the queuing system as follows:
  • The queuing system is not active on the system you are upgrading; do not attempt to execute a START/QUEUE/ MANAGER command.
  • You cannot create a queue database on the operating system CD-ROM (because it is not writable).
  • The queue manager process on other nodes in the cluster can continue to run during the upgrade if the queue database is not on the disk being upgraded.

To prepare for a rolling upgrade:

1. Log in to any node where the target disk is mounted as a data disk, rather than as the system disk. (That disk must be the one on which you already performed the preupgrade tasks described in Chapter 5.)
2. Check the votes and make adjustments to maintain the proper quorum so the cluster can continue to operate throughout the upgrade. (OpenVMS Cluster Systems describes this procedure in detail.)
3. Use the DCL command DISMOUNT/CLUSTER to dismount the data disk. (You can also perform this operation using the SYSMAN utility.)
   Note that you can ignore messages from nodes where the specified data disk is being used as the system disk.
4. Verify that the data disk has been dismounted successfully by entering the following commands:

   $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO SHOW DEVICE disk-name

   
   Examine the display to be sure the disk is not mounted on any nodes as a data disk. Noting the value listed in the Trans Count field can help you make that determination: A value of less than 50 indicates that the disk is mounted as a data disk rather than as the system disk; a much larger value (for example, 300) indicates that the disk most likely is the system disk.

5. If the disk is still mounted on any nodes as a data disk, use the SYSMAN utility to dismount the disk; otherwise, exit from the SYSMAN utility.
6. Shut down all nodes that boot from the system disk you are upgrading, including the node from which you will perform the upgrade. Enter the following command on each node:

   $ @SYS$SYSTEM:SHUTDOWN

7. When the procedure asks if an automatic system reboot should be performed, enter N (No) and press the Return key.
8. Choose the REMOVE_NODE option.
9. If proper quorum is not maintained at any time during the upgrade procedure, the shutdown procedure will hang the cluster. If the cluster hangs during a shutdown, enter the following commands on the system console of a system that is still a cluster member:

   $ [Ctrl/P] >>> D SIRR C >>> C IPC> Q IPC> [Ctrl/Z]

10. After the shutdown procedure is finished on all nodes, go to Chapter 7 to begin the upgrade procedure.

This chapter describes the following tasks:

• Beginning the upgrade from the operating system CD-ROM
• Specifying the target disk
• Specifying the volume label
• Updating time zone information
• Choosing descriptive help text
• Completing the upgrade
• Performing postupgrade tasks (including booting the upgraded system)
• Installing layered products

The OpenVMS Alpha Version 7.2 operating system includes procedures that allow you to easily upgrade the operating system using the POLYCENTER Software Installation utility. To get started, boot the OpenVMS Alpha operating system CD-ROM either from your local CD-ROM drive or from a CD-ROM drive connected to the InfoServer, as described in the following sections.

7.1.1 Booting from the Local Drive

To boot the operating system CD-ROM from the local drive, follow these steps:

1. Insert the operating system CD-ROM into the local CD-ROM drive.
2. At the console prompt (>>>), enter the SHOW DEVICE command so you can identify the name of the CD-ROM drive (for example, DKA400:)
3. Enter the boot command in the following format:

   BOOT -FLAGS 0,0 source-drive

   
   Substitute the device name of the CD-ROM drive (as listed in the SHOW DEVICE display) for source-drive.
   For example, if the SHOW DEVICE display lists the device name of your CD-ROM drive as DKA400, enter the following command and press the Return key:

   >>> BOOT -FLAGS 0,0 DKA400

To boot the operating system CD-ROM using the InfoServer, follow these steps:

1. At the console prompt, enter the following command:

   >>> BOOT -FLAGS 0,0 -FILE APB_072 lan-device-name

   
   Note the following conventions:

   • APB_072 is the file name of the APB program used for the initial system load (ISL) boot program.
   • lan-device-name is the name of the local area network (LAN) device Ethernet identified with your computer. For information about the LAN devices your system supports, refer to the following table. For additional information, see the hardware manuals that you received with your Alpha computer and the OpenVMS Software Product Description.

   Alpha Computer	Ethernet Device	FDDI Device
   ALPHAbook 1	EOA0	--
   AlphaServer 400 series	EWA0	FWA0
   AlphaServer 1000 series	ERA0, EWA0	FRA0
   AlphaServer 1000A series	EWA0	FWA0
   AlphaServer 1200 series	EWA0	FWA0
   AlphaServer 2000 series	ERA0, EWA0	FRA0
   AlphaServer 2100, 2100A series	ERA0, EWA0	FRA0
   AlphaServer 4100 series	EWA0	FWA0
   AlphaServer 8200 series	EXA0, EWA0	FXA0
   AlphaServer 8400 series	EXA0, EWA0	FXA0
   AlphaStation 200 series	EWA0	FWA0
   AlphaStation 400 series	EWA0	FWA0
   AlphaStation 500 series	EWA0	FWA0
   AlphaStation 600 series	ERA0, EWA0	FWA0
   DEC 2000 series	ERA0	--
   DEC 3000 series	ESA0	"n/ESA0"
   DEC 4000 series	EZA0	--
   DEC 7000 series	EXA0	FXA0
   DEC 10000 series	EXA0	FXA0
   DIGITAL Personal Workstation (DPWS) series	EWA0	FWA0

   Note If you are using a DEC 3000 or 4000 series system, note the following: On DEC 3000 series systems, you can boot through the InfoServer with an Ethernet PMAD device or FDDI DEFTA device by specifying the device name as "n/ESA0". The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8. On DEC 4000 series, you must specify the ISL file name in uppercase (APB_072).

2. The InfoServer ISL program then displays the following menu:

   Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value:

3. Respond to the prompts as follows, pressing the Return key after each entry:
   1. Enter 3 for the function ID.
   2. Enter 2 for the option ID.
   3. Enter the service name (ALPHA072).
   
   A sample display follows:

   Enter a function ID value: 3[Return] OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2[Return] Enter a Known Service Name: ALPHA072[Return]

The following sections describe how to upgrade from the operating system CD-ROM.

7.2.1 Upgrading from the CD-ROM

After you boot the operating system CD-ROM, choose the upgrade option (1) from the menu displayed on the screen. The display is similar to the following:

OpenVMS (TM) Alpha Operating System, Version V7.2 Copyright (c) 1998 Compaq Computer Corporation. All rights reserved. Installing required known files... Configuring devices... **************************************************************** 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) 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/?) 1

The OpenVMS Alpha operating system CD-ROM may contain patch kits. If it does, information similar to the following will be displayed:

The following PATCH kits are present on the OpenVMS Alpha distribution media. ----------------------------------- ----------- ---------- PRODUCT KIT TYPE KIT FORMAT ----------------------------------- ----------- ---------- DEC AXPVMS UCXECO_42_1 V1.0 Patch Sequential ----------------------------------- ----------- ---------- 1 item found Please consult the OpenVMS Alpha Upgrade and Installation Manual, the Release Notes, and the Cover Letter to determine if any or all of these patches may be required for your system.

7.2.2 Choosing INITIALIZE or PRESERVE

After you choose the upgrade option (if you are upgrading from the operating system CD-ROM) or start the AXPVMS$PCSI_INSTALL command procedure (if you are upgrading from a running OpenVMS Alpha Version 7.2 system), the system displays the following information and prompts:

*********************************************************** The installation procedure will ask a series of questions. () - encloses acceptable answers [] - encloses default answers Type your response and press the <Return> key. Type: ? - to repeat an explanation ^ - to change prior input (not always possible) Ctrl/Y - to exit the installation procedure There are two choices for Installation/Upgrade: INITIALIZE - removes all software and data files that were previously on the target disk and installs OpenVMS Alpha. PRESERVE -- installs or upgrades OpenVMS Alpha on the target disk and retains all other contents of the target disk. * NOTE: You cannot use PRESERVE to install OpenVMS Alpha on a disk on which OpenVMS VAX or any other operating system is installed. Do you want to INITIALIZE or to PRESERVE? [PRESERVE])

For an upgrade, press the Return key to accept the default (PRESERVE).

7.2.3 Specifying the Target Disk

Next, the procedure asks you for the name of the target disk. If you enter a question mark (?), the system displays a list of devices on your system. Select the appropriate disk and respond to the prompt. For example:

You must enter the device name for the target disk on which OpenVMS Alpha will be installed. Enter device name for target disk: (? for choices) dkb400

If you select a device that is not available or that cannot be used for some other reason, the system displays information indicating why the device cannot be used. For example, if you enter MKA500, a tape device, a message similar to the following is displayed:

MKA500 is not a disk device

7.2.4 Specifying the Volume Label

The system then prompts you for the volume label and asks if the information is correct. You can accept the default label assigned by the system (AXPVMSSYS) or specify a different volume label (with a limit of 12 characters that can be letters A-Z, numbers 0-9, dollar signs ($), hyphens (-), or underscores (_)).

After you select the volume label, the target disk is mounted and page and swap files are created. For example:

DKB400: is now labeled ALPHAUPGIV. Do you want to keep this label? (Yes/No) [Yes] OpenVMS Alpha will be upgraded on DKB400:.

7.2.5 Checking Related Software

At this point the upgrade performs checks of some related software products.

7.2.5.1 Spiralog

The target system contains a version of SPIRALOG that is not compatible with this version of the operating system. SPIRALOG must be removed before upgrading OpenVMS Alpha. Termination is strongly recommended. Do you want to terminate? (Yes/No) [YES]

Note that Spiralog will not work with OpenVMS Alpha Version 7.2. If you have any version of Spiralog installed on your system, uninstall it before upgrading to OpenVMS Alpha Version 7.2.

7.2.5.2 AMDS

Beginning with OpenVMS version 7.2 and AMDS version 7.2, certain parts of AMDS that were previously supplied with the layered product kit are now incorporated into OpenVMS. Because of this, prior versions of AMDS must be removed.

If the upgrade procedure detects a prior version of AMDS, it will display the following message and automatically remove the prior version of AMDS. Note that you must reinstall AMDS if you wish to continue using it.

The target system contains a version of DEC AMDS that is not compatible with this version of the operating system. If you continue AMDS will be removed. A current version of AMDS can be installed after the upgrade completes.

7.2.5.3 PATHWORKS

If PATHWORKS is installed on the system, OpenVMS Version 7.2 requires PATHWORKS Version V6.0B or later. The installation determines the PATHWORKS version and displays one of the following messages if an earlier version of PATHWORKS is present.

If PATHWORKS Version 5 or earlier is present:

PATHWORKS V5 is installed on the target system. This version of PATHWORKS will not work on OpenVMS V7.2. You must upgrade to PATHWORKS V6.0B or later, or disable PATHWORKS on the target system, before upgrading OpenVMS. Please refer to the release notes for additional information. Do you want to continue? (Yes/No) [NO]

If PATHWORKS Version 6.0 or 6.0A is present:

PATHWORKS V6.0-000 is installed on the target system. This version of PATHWORKS is not supported on OpenVMS V7.2. PATHWORKS V6.0B and later are supported on OpenVMS V7.2. You may wish to upgrade to PATHWORKS V6.0B or later before upgrading OpenVMS. Please refer to the release notes for additional information. Do you want to continue? (Yes/No) [NO]

In both cases the default is to terminate the upgrade. You must explicitly enter Yes and press the Return key to continue.

7.2.6 Checking OpenVMS Cluster Membership

The procedure now asks if your system will be part of a cluster. The display is similar to the following:

Will this system be a member of an OpenVMS Cluster? (Yes/No) Yes

Unlike an installation, answering Yes to this question will not cause SYS$MANGER:CLUSTER_CONFIG.COM to be run. However, correct cluster membership information is required by the upgrade procedure.

	privacy and legal statement
6522PRO_007.HTML