HP OpenVMS Systems Documentation

Content starts here
HP OpenVMS Version 8.3 Upgrade and Installation Manual > Chapter 6 Upgrading the OpenVMS Operating System

Performing the Upgrade

  Table of Contents

  Glossary

  !Index

The following sections describe how to upgrade from the operating system media.

Upgrading the System Using Option 1 of the Operating System Menu

f

After you boot the operating system CD (OpenVMS Alpha) or DVD (OpenVMS I64 OE DVD), the HP copyright banner and several messages appear, followed eventually by the operating system main menu. Choose the upgrade option (1) on the menu, as in the following example:

       Installing required known files...

Configuring devices...
.
.
.
****************************************************************

You can install or upgrade the OpenVMS I64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS I64 distribution media (CD/DVD).

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 I64 Version 8.3
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install, or Undo patches; Show or Delete recovery data
     8)  Execute DCL commands and procedures
     9)  Shut down this system      
    
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?)
1

Choosing INITIALIZE or PRESERVE



The procedure displays the following information and prompts:

       ***********************************************************

This 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 I64.

Preserve -- installs or upgrades OpenVMS I64 on the target disk
and retains all other contents of the target disk.

* NOTE: You cannot use preserve to install OpenVMS I64 on a disk on
which any other operating system is installed. This includes
implementations of OpenVMS for other architectures.

Do you want to INITIALIZE or to PRESERVE? [PRESERVE])

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

Specifying the Target Disk

Next the procedure asks 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 I64 will be installed.

Enter device name for target disk: [DKB300] (? 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

Selecting Reinstallation and Reconfiguration Options

If you are using the .OpenVMS Version 8.3 operating system media and you selected a target disk that already has Version 8.3 installed, you are presented with several configuration options. A sample display follows. See also the example in “Adding and Removing Operating System Files (Optional)”.

   Version 8.3 of the OpenVMS operating system is already installed 
on DKB400:.

Please choose one of the following:

1) Reconfigure the OpenVMS platform.
2) Reconfigure the OpenVMS operating system.
3) Reinstall the OpenVMS operating system.
4) Return to the Main Menu (abort the upgrade/installation).

Enter a "?" for more information.

If you enter a question mark (?), the following information is displayed:


o Reconfigure the OpenVMS platform.

This action will allow you to change your selections of which
products you installed along with the OpenVMS operating system
installation.

This will NOT change any options in the OpenVMS operating system,
nor will it reinstall any operating system files.

o Reconfigure the OpenVMS operating system.

This action will allow you to change your choices about which
options you included for the OpenVMS operating system.

This will NOT change any options for the products you installed
along with the OpenVMS operating system installation, nor will
it reinstall or upgrade Yany of them.

o Reinstall the OpenVMS operating system.

This action will cause ALL operating system files to be replaced.
You can also change your choices about which options you included
for the OpenVMS operating system.

This will NOT change any options for the products you installed
along with the OpenVMS operating system installation, nor will
it reinstall or upgrade any of them.

Reinstall will take longer than Reconfigure. Reinstall may be
appropriate if you suspect that files in the operating system,
or in the windowing and network products have become corrupted.


If you want to reinstall or upgrade any of the products you installed
along with the OpenVMS operating system installation, choose "Install
or upgrade layered products" (option 3) from the main menu.

If you want to change your choices about which options you included
for any of the products you installed along with the OpenVMS operating
system installation, choose "Reconfigure installed products" (option 5)
from the main menu.

Next the menu is redisplayed:

   Please choose one of the following:

1) Reconfigure the OpenVMS platform.
2) Reconfigure the OpenVMS operating system.
3) Reinstall the OpenVMS operating system.
4) Return to the Main Menu (abort the upgrade/installation).


Enter choice or ? for help: (1/2/3/4/?)
M

For additional configuration information, see “Adding and Removing Operating System Files (Optional)”.

Checking for Recovery Data

If you specify the /SAVE_RECOVERY_DATA qualifier with the PRODUCT INSTALL command, the PCSI utility saves information that can be used to remove patches and mandatory update kits at a later time. Use the PRODUCT UNDO PATCH command to remove the patches and kits. The /SAVE_RECOVERY_DATA qualifier and PRODUCT UNDO PATCH command were first added to OpenVMS Alpha in Version 7.3-2; they were backported to OpenVMS Alpha Version 7.2-2, 7.3, and 7.3-1.

The upgrade procedure now checks the disk for recovery data saved by the PCSI utility. Any recovery data must be removed before the upgrade can continue because this data becomes invalid after the upgrade. If no recovery data is present, the upgrade continues. If recovery data is present and all the data found applies only to the OpenVMS operating system, the upgrade procedure deletes the data and continues. (The procedure does not display the deletion of the files because earlier patches to OpenVMS are always removed as part of the upgrade.) If any of the recovery data applies to products other than the OpenVMS operating system, then the upgrade procedure displays a message similar to the following:

        The target system has recovery data from PRODUCT operations which
used the /SAVE_RECOVERY_DATA qualifier. This data must be deleted
to continue the OpenVMS upgrade.

Please examine the following display.

If you wish to delete this data and continue the OpenVMS upgrade,
answer YES to the question "Do you want to continue?"

If you do not wish to delete this data, answer NO. A NO answer
will preserve the recovery data and abort the OpenVMS upgrade.

The following patch recovery data has been selected:

RECOVERY DATA SET 001 ]created 8-JUL-2006 15:23:39.69
-------------------------------------- ------------------------------------
PATCH APPLIED TO
-------------------------------------- ------------------------------------

JAK VMS RM1 V1.0 JAK VMS RMTEST V1.0
-------------------------------------- ------------------------------------

* If you continue, recovery data for the patches listed above will be deleted.
* The deletion of recovery data does not affect the installation status of
* patches applied to products that are not participating in this operation.
* However, continuing with this operation prevents you from uninstalling
* these patches at a future time by use of the PRODUCT UNDO PATCH command.

Do you want to continue? [YES]

If you answer YES (the default), the recovery data sets are deleted and the OpenVMS upgrade continues.

    
Deleting RECOVERY DATA SET 001 ...

If you answer NO, the recovery data sets are not deleted and the OpenVMS upgrade aborts.

    Do you want to continue? [YES] NO
%PCSIUI-I-USERABORT, operation terminated by user request

You chose to retain recovery data on the target system disk.
The OpenVMS upgrade cannot continue.

Please correct the situation that prevents you from deleting the
recovery data and then retry the upgrade.


Specifying the Volume Label

After you specify the target disk and, if applicable, check for recovery data, the procedure informs you of the volume label currently assigned to the target disk (if one was previously defined) you specified and asks whether you want to keep that label. As shown in the following example, if you choose not to keep the label, you are prompted for a new label. The OpenVMS operating system uses the volume label to identify and reference the disk. Make sure the label you use is unique; problems occur if the same label is used by different disk volumes.

      DKB400: is now labeled I64SYS.
    Do you want to keep this label? (Yes/No) [Yes] NO

Enter volume label for target system disk: [I64SYS] I64083
;

You can accept the default label assigned by the system or specify a different volume label. (The label name has a limit of 12 characters that can include A to Z, 0 to 9, the dollar sign ($), hyphen (-), and underscore(_) characters).

NOTE: OpenVMS requires that the volume labels for all disks on your system or OpenVMS Cluster have unique labels. If a disk that has the same label as the system disk is mounted, various OpenVMS components will not function as intended or a node might crash during boot.

If you change the volume label for a disk in an OpenVMS Cluster, be sure to change the command that mounts the disk on other nodes in the cluster; otherwise, the disk will not mount on those nodes once they are rebooted.

Specifying the On-Disk Structure Level

If the target disk is currently initialized with On-Disk Structure Level 2 (ODS-2), the procedure informs you and gives you the option to convert the disk to On-Disk Structure Level 5 (ODS-5), as in the following example. If the target disk is currently initialized with ODS-5, the upgrade continues without displaying information about the disk structure.

     The  target  system disk is currently at On-Disk Structure Level 2
(ODS-2). It can be converted to On-Disk Structure Level 5 (ODS-5).
(? for more information)


Do you want to convert the target system disk to ODS-5? (Yes/No/?)

If you answer YES, the disk will be converted to ODS-5. The procedure informs you that you can use the BACKUP/CONVERT command to convert ODS-5 disks back to ODS-2 format; for more information, see the HP OpenVMS System Management Utilities Reference Manual: A--L.

NOTE: HP recommends that your system disk be structured in ODS-5 format unless you use software that requires ODS-2. Hard links are supporetd on ODS-5 disks only. A brief comparison of ODS-2 and ODS-5, including advantages and disadvantages, follows this note.

If you are installing WBEM Services for OpenVMS, which is supported on OpenVMS I64 systems only, note that although this product can be installed on an ODS-2 disk, the WBEM Services for OpenVMS data repository requires an ODS-5 disk. In addition, the WBEM Services for OpenVMS SDK kit requires an ODS-5 disk. If you install WBEM Services for OpenVMS onto an ODS-5 disk, you can have everything on the same disk.



A brief summary of ODS-2 and ODS-5 file systems follows; for more information, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials:

  • ODS-2

    ODS-2 allows for full compatibility with all OpenVMS VAX systems and with OpenVMS Alpha systems prior to Version 7.2.

  • ODS-5

    • ODS-5 supports file names that are longer and have a wider range of legal characters. This feature permits use of file names similar to those in a Windows or UNIX environment.

    • ODS-5 supports hard links to files, access dates, and files whose names differ only by case.

    • ODS-5 volumes cannot be mounted on any version of OpenVMS prior to Version 7.2.

    • Systems running OpenVMS VAX Version 7.2 and higher can mount ODS-5 volumes but cannot create or access files that have extended names. (On OpenVMS VAX systems, lowercase file name characters are seen in uppercase.)

If you choose not to change to ODS-5, the upgrade continues and the target disk is mounted. For example:

  Do you want to convert the target system disk to ODS-5? (Yes/No/?) NO    

OpenVMS I64 will be upgraded on DKB400:.
C

If you choose to change to ODS-5, you are given the option to enable hard links. (For more information about hard links, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials.) The upgrade then continues.

  Do you want to convert the target system disk to ODS-5? (Yes/No/?) YES

DKB400: has been converted to ODS-5.

You can use the BACKUP/CONVERT command to convert ODS-5 disks back
to ODS-2 format. For more information, refer to the OpenVMS System
Management Utilities Reference Manual.

Hard links can be enabled on ODS-5 disks. (? for more information)
(***Enabling hard links can take from 5-10 minutes to an hour or more.***)

Do you want to enable hard links? (Yes/No/?)
YES

If you choose to enable hard links, the procedure automatically executes an ANALYZE/DISK_STRUCTURE/REPAIR operation to correctly set the reference counts. This operation can take from 5 to 10 minutes to an hour or more, depending on the complexity of the system disk configuration, the number of layered products installed, and the number of user files. During the process, messages similar to the following are displayed:

     w	Hard links have been enabled on DKB400:.

The newly enabled hard links are not correct and need to be updated.
The Analyze/Disk_Structure utility will now be run to do this.

This can take from 5 - 10 minutes to an hour or more. It is a normal
requirement when hard links are enabled on an existing disk.

%ANALDISK-I-COUNT, 1000 hard link updates completed
%ANALDISK-I-COUNT, 2000 hard link updates completed
%ANALDISK-I-COUNT, 3000 hard link updates completed
%ANALDISK-I-COUNT, 4000 hard link updates completed
%ANALDISK-I-COUNT, 5000 hard link updates completed
%ANALDISK-I-COUNT, 6000 hard link updates completed

OpenVMS I64 will be upgraded on DKB400:.

Choosing Whether to Allow the Procedure to Create and Validate Boot Options (I64 only)

On OpenVMS I64 upgrades, the procedure next asks whether you want to create or validate boot options.

      Boot options in the EFI Boot Manager boot option menu can provide a
convenient way to boot your system. The installation procedure can
automatically create a new boot option (if none exists) or validate
existing boot options.

Do you want to create or validate boot options? (Yes/No) [Yes]
YES

If your system disk will normally be booted on this system and this device, and if you want the upgrade procedure to assist you in setting up or validating boot options on the EFI console in the EFI Boot Manager menu, answer YES. The procedure creates and validates a new boot option if one does not exist, or it validates existing boot options, just before the upgrade completes. (See “Upgrade Creates and Validates Boot Options (I64 Only)”.)

If you answer YES and no boot option exists, the procedure allows you to set OpenVMS boot flags (VMS_FLAGS), as shown in the following example. Enter the OpenVMS flags (for example, 0,1), or press Enter to set no flags (the default). If a boot option exists, you can change boot flags after the upgrade completes (for information about changing boot flags, see “Setting Boot Options for Your System Disk”).

      You can set VMS_FLAGS or accept the default, 0,0.

Enter the value for VMS_FLAGS: (n.n) [0,0]

If you do not want the procedure to assist you in setting up or validating boot options on the EFI console, answer NO.

HP recommends that you allow the procedure to assist you in setting up and validating boot options.

NOTE: If your newly upgraded system disk is a Fibre Channel device, HP recommends that you add it as a boot option in the EFI boot menu. If you do not allow the upgrade procedure to add the device to the boot menu, you can add it by using the OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM) after the upgrade completes. (To add Fibre Channel devices to the EFI boot menu, you must use this utility instead of EFI.)

HP recommends using the OpenVMS I64 Boot Manager utility to add shadowed system disks in a multiple-member shadow set to the EFI boot device list and dump device list. Be sure to add all members to both lists.

For information about the OpenVMS I64 Boot Manager utility, see “Setting Boot Options for Your System Disk”. For more information about configuring and booting Fibre Channel devices, see Appendix D “Setting Up and Booting Fibre Channel Storage Devices”.

Warning About Removal of the DECRAM Command

When upgrading from versions of OpenVMS prior to 8.3, the procedure displays a message similar to the following that warns you that the DCL command DECRAM is being removed to prevent conflict with the DECRYPT command:

h    Beginning with OpenVMS V8.3, the DCL commands ENCRYPT and DECRYPT
are provided as part of OpenVMS.

Because "DECRYPT" conflicts with the existing command "DECRAM",
this upgrade will remove the DECRAM command.

If you use the command DECRAM interactively or in command
procedures, please see the release notes for more information.

The DECRYPT command (introduced with OpenVMS Version 8.3) overwrites the default definition of DECR, which you might have been using to run DECram. You should update any command procedures that use the DECRAM command so that they use the foreign command style of DCL to run DECram:

$ DECRAM == "$MDMANAGER"

This change affects only the use of the DCL command; all other aspects of the DECram product remain the same.

Setting OpenVMS Cluster Membership Information



The procedure now asks whether your system will be part of an OpenVMS Cluster. For example:

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

Unlike an installation, answering YES to this question does not cause the SYS$MANAGER:CLUSTER_CONFIG.COM procedure to be run. However, correct cluster membership information is required by the upgrade procedure. Note that you can run SYS$MANAGER:CLUSTER_CONFIG.COM manually to configure or reconfigure your system as a member of an OpenVMS Cluster. For more information about configuring a member of an OpenVMS Cluster, see Guidelines for OpenVMS Cluster Configurations.

Setting OpenVMS Galaxy Information (Alpha Only)

The procedure next asks whether your system is an instance in an OpenVMS Galaxy. The display is similar to the following:

   Will this system be an instance in an OpenVMS Galaxy? (Yes/No) 

If you answer YES to this question, and you also answered YES to the OpenVMS Cluster question, then information about required remedial kits is displayed. Your answer to this question determines how the system parameter GALAXY is set.



Updating Time Zone Information

For local time zone support to work correctly, the time zone that accurately describes the location you want to be considered as your default time zone must be set. In addition, your system must be configured correctly to use a valid OpenVMS time differential factor (TDF).

If the installation procedure determines that time zone information is incomplete, it prompts you to set the correct default time zone and TDF for your system. For information about setting the time zone information, see “Installing OpenVMS Using Option 1 of the Operating System Menu”.

For more information about TDF and local time zone support, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials.



Upgrading Windowing, Networking, and Related Products

The procedure now presents information about the optional DECwindows GUI (DECwindows Motif for OpenVMS) and networking (DECnet and TCP/IP) products that will be upgraded along with the OpenVMS operating system. As noted by the procedure, you can change the default values for these products later in the installation procedure.

NOTE: The following display is what might be seen during an OpenVMS I64 installation. Some of the products listed are supported on OpenVMS I64 systems only.
<

If necessary, the following products will be upgraded along with
the OpenVMS operating system:

o Availability Manager (base) for OpenVMS I64 (required part of OpenVMS)
o CDSA for OpenVMS I64 (required part of OpenVMS)
o KERBEROS for OpenVMS I64 (required part of OpenVMS)
o SSL for OpenVMS I64 (required part of OpenVMS)
o Performance Data Collector (base) for OpenVMS I64 (required part of OpenVMS)
o DECwindows Motif for OpenVMS I64
o DECnet-Plus for OpenVMS I64
o DECnet Phase IV for OpenVMS I64
o HP TCP/IP Services for OpenVMS
o WBEM Services for OpenVMS

If you want to add or delete these products, you can do so later in
the upgrade by answering NO to the following question:

"Do you want the defaults for all product options?"

Availability Manager (base) for OpenVMS I64 (required part of OpenVMS)
is installed on your system. It will be upgraded.

CDSA for OpenVMS I64 (required part of OpenVMS)
is installed on your system. It will be upgraded.


KERBEROS for OpenVMS I64 (required part of OpenVMS)
is installed on your system. It will be upgraded.

SSL for OpenVMS I64 (required part of OpenVMS)
is installed on your system. It will be upgraded.

Performance Data Collector (base) for OpenVMS I64 (required part of OpenVMS)
is installed on your system. It will be upgraded.

DECwindows Motif for OpenVMS I64
is installed on your system. It will be upgraded.

Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. HP strongly recommends that
DECnet users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.

DECnet Phase IV is also provided as an option.

If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please see OpenVMS
Management Guide for information on running DECnet over TCP/IP.

Do you want to install DECnet-Plus for OpenVMS I64 V8.3? (Yes/No) [Yes]

HP TCP/IP Services for OpenVMS
is alredy installed on your system. An upgrade is not required.


WBEM Services for OpenVMS is not installed on your system.
It will not be installed.

NOTE: Beginning with OpenVMS Version 8.3, DECwindows client files are made available through the DWMOTIF_SUPPORT kit. (Prior to Version 8.3, the client files were included directly with the OpenVMS operating system kit.) The OpenVMS installation procedure installs this kit automatically. The DWMOTIF_SUPPORT kit name is listed during the installation.

Required versions of some of the windowing and networking products might already be installed on the system. If so, you will see a message to this effect, as seen for most of the products in the previous example. For some of the windowing and networking products, earlier versions might be installed that still work on OpenVMS Version 8.3. In this case, you will see a message indicating the software is already installed and asking whether you want to install the newer version. You can keep the currently installed version or upgrade to the newer version supplied with OpenVMS Version 8.3. If you choose to keep the currently installed version, you should verify what level of support for this version is available from HP.

Some windowing and networking products might have versions installed that do not work on OpenVMS Version 8.3. In this case, you are not given a choice to upgrade—the software is upgraded automatically. (On OpenVMS Alpha upgrades, if older versions of SSL for OpenVMS are found, the procedure removes them.)


NOTE: For support of Instant Capacity (iCAP) and Pay per use (PPU) functionality (supported on cell-based Integrity servers), you must install TCP/IP Services for OpenVMS and WBEM Services for OpenVMS. SSL for OpenVMS is required and installed automatically.