Performing the Upgrade

If both a Table of Contents and Search form are not displayed in separate frames along with this one, you may wish to redisplay this book in a frameset, beginning with the first page.

HP OpenVMS Version 8.2 Upgrade and Installation...

Upgrading the OpenVMS Alpha Operating System

Booting the Operating System Kit

Completing the Upgrade

Performing the Upgrade

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

Upgrading the System Using Option 1 of the Operating System CD Menu

After you boot the operating system CD, 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 8.2
 
    Installing required known files...
 
    Configuring devices...
    (c) Copyright 1976-2004 Hewlett-Packard Development Company, L.P.
 
 
    ****************************************************************
 
    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/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 Alpha Version 8.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 might contain patch kits. If it does, information similar to the following is displayed:

    The following PATCH kits are present on the OpenVMS Alpha
    distribution media.
 
    ----------------------------------- ----------- ----------
    PRODUCT                             KIT TYPE    KIT FORMAT
    ----------------------------------- ----------- ----------
    DEC VAXVMS TCPIP_ECO V5.3-182       Patch       Sequential
    ----------------------------------- ----------- ----------
 
    1 item found
 
    Please consult the OpenVMS 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.

Choosing INITIALIZE or PRESERVE

The procedure 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 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 Return to accept the default (PRESERVE).

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: [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

Checking for Recovery Data

If you specify the /SAVE_RECOVERY_DATA qualifier with the PRODUCT INSTALL command, the POLYCENTER Software Installation (PCSI) utility will save 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 added in OpenVMS Alpha Version 7.3-2 and backported to OpenVMS for 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 has to be removed before the upgrade can continue, because this data would become 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 prior 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-NOV-2004 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.

Do you want to continue? [YES]
 
Deleting RECOVERY DATA SET 002 ...
 
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 specifying the target disk, and if applicable, checking for recovery data, the system then informs you of the volume label currently assigned to the target disk 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 ASPVMS732.

Do you want to keep this label? (Yes/No) [Yes] NO
 
Enter volume label for target system disk: [ALPHASYS]

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

HP strongly recommends 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.

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 system 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/?)

For details about ODS-2 and ODS-5 file systems, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials. A brief summary follows:

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 later can mount ODS-5 volumes, but cannot create or access files having extended names. (Lowercase file name characters are seen in uppercase on OpenVMS VAX systems.)

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 Alpha will be upgraded on DKB400:.

If you choose to change to ODS-5, you will be given the option to enable hard links. For more information about hard links, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials. The upgrade will then continue.

  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 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:

    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 Alpha will be upgraded on DKB400:.

Setting OpenVMS Cluster Membership Information

The procedure now asks whether your system will be part of an OpenVMS Cluster. The display is similar to the following:

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

You should answer YES if the system will be an OpenVMS Galaxy instance or a member of an OpenVMS cluster. Unlike an installation, answering YES to this question will not cause SYS$MANAGER:CLUSTER_CONFIG.COM to be run. However, correct cluster membership information is required by the upgrade procedure. Your response to this question determines how the VAXCLUSTER system parameter will be set. (The parameter name "VAXCLUSTER" has been retained on OpenVMS Alpha systems.) 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, refer to the Guidelines for OpenVMS Cluster Configurations.

Setting OpenVMS Galaxy Information

The procedure next asks whether your system will be 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) 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 will be 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 correctly configured to use a valid OpenVMS time differential factor (TDF).

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

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

Selecting Reinstallation and Reconfiguration Options

If you are using the OpenVMS Alpha Version 8.2 CD and have selected a target disk that already has Version 8.2 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.2 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 displays:

  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 any 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 and patches" (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 then 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/?)

For additional configuration information, see After Installing or Upgrading the OpenVMS Operating System.

Upgrading Windowing and Networking Products

The procedure now presents information about software that you can install along with the OpenVMS operating system. Some of this software is required, as noted; some is optional. The procedure asks whether you want to install the following HP windowing and networking software products:

Availability Manager (base) for OpenVMS (required)

CDSA (required)

Kerberos (required)

Performance Data Collector (base) for OpenVMS (required)

DECwindows Motif for OpenVMS

DECnet-Plus for OpenVMS or DECnet Phase IV for OpenVMS (but not both)

TCP/IP Services for OpenVMS

The software that you choose to install (including the required software) is included with the OpenVMS Alpha operating system. You can change the default values for these products later in the installation/upgrade procedure.

If you are upgrading DECnet, the procedure removes the existing version of DECnet during the upgrade.

The display is similar to the following:

    If necessary, the following products will be upgraded along with 
    the OpenVMS operating system:
 
        o Availability Manager (base) for OpenVMS Alpha (required part of OpenVMS)
        o CDSA for OpenVMS Alpha (required part of OpenVMS)
        o KERBEROS for OpenVMS Alpha (required part of OpenVMS)
        o Performance Data Collector (base) for OpenVMS Alpha (required part of 
          OpenVMS)
        o DECwindows Motif for OpenVMS Alpha
        o DECnet-Plus for OpenVMS Alpha
        o DECnet Phase IV for OpenVMS Alpha
        o HP TCP/IP 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 Alpha (required part of OpenVMS) is
    required.
    It will be installed.
 
    CDSA for OpenVMS Alpha (required part of OpenVMS)
    is already installed on your system. An upgrade is not required.
 
    
    KERBEROS for OpenVMS Alpha (required part of OpenVMS)
    is already installed on your system. An upgrade is not required.
 
    Performance Data Collector (base) for OpenVMS Alpha (required part of OpenVMS) is 
    required. 
    It will be installed.    
 
    DECwindows Motif for OpenVMS Alpha 
    is installed on your system. It will be upgraded.

    DECnet-Plus for OpenVMS Alpha
    is installed on your system. It will be upgraded.
 
    DECnet Phase IV for OpenVMS Alpha is not installed on your system.
     It will not be installed.
 
    HP TCP/IP Services for OpenVMS
    is installed on your system. It will be upgraded.

Some of the windowing and networking products might have the required versions already installed on the system. You will see a message indicating that the software is already installed and that an upgrade is not required, as for CDSA and Kerberos in the previous example. Some of the windowing and networking products might have versions installed that are earlier than the current versions, but which still work on OpenVMS Version 8.2. 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 choose to keep the currently installed version, or to upgrade to the newer version supplied with OpenVMS Version 8.2. If you choose to keep the currently installed version, you should verify what level of support is available from HP for this version.

Some windowing and networking products might have versions installed that do not work on OpenVMS Version 8.2. In this case, you are not given a choice to upgrade. The software will be upgraded automatically. In the preceding example, an earlier version of TCP/IP Services for OpenVMS is currently installed on the system. The message indicates it will be upgraded.

Booting the Operating System Kit

Completing the Upgrade