HP OpenVMS Version 8.2-1 for Integrity Servers...

Upgrading the OpenVMS Operating System

Performing the Upgrade

What to Do After the Shutdown

Completing the Upgrade  

Choosing Descriptive Help Text  

The system next prompts you as follows:

       The installation operation 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]  

Saving Archived Files  

By default, the OpenVMS upgrade deletes files that were archived as filename.extension_OLD by OpenVMS remedial kits. If you do not want to delete these files, you can save them by taking one of the following steps:

1. When the script asks whether you want the defaults for all options, answer NO. (This script is shown in the example in Selecting Product Component Options.) Step through the options and answer NO to the option for deleting files archived by remedial kits. This action saves all such files.
2. Before beginning the upgrade, rename any _OLD files that you want to save. Files that you do not rename are deleted.

Note that the upgrade does not delete all files with an extension ending in _OLD. Rather, it deletes only those _OLD files that were archived by OpenVMS remedial kits.

OpenVMS patches save these _OLD files in VMS$REMEDIAL_OLD_FILES.TXT in the SYS$UPDATE directory. All files listed in this file are supposed to have _OLD appended to their names; however, some patch kits add the files without this extension. If the upgrade procedure detects files without _OLD appended, it displays a message similar to the following: %UPGRADE-I-FIXUP, appending _OLD to file names in PCSI$DESTINATION:[SYSUPD] VMS$REMEDIAL_OLD_FILES.TXT [SYSUPD]VMSKITBLD.DAT [SYSHLP]XFC$SDA.HLP [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE-OLD [SYS$LDR]SYS$XFCACHE.DSF [SYS$LDR]SHELL9K.EXE_STB [000000]HP-I64VMS-VMS-V0820-1-2.PCSI$DESCRIPTION

Selecting Product Component Options  

As you begin the upgrade procedure, the system asks whether you want all the default values (meaning all the files and subgroups of files for each component included in the operating system). The display is similar to the following:

   The following product has been selected:
       HP I64VMS OPENVMS V8.2-1        Platform (product suite) 
 
 
   Configuration phase starting ...
 
   You will be asked to choose options, if any, for each selected product and for
   any products that may be installed to satisfy software dependency requirements.
 
   HP I64VMS OPENVMS V8.2-1: OPENVMS and related products Platform
 
      COPYRIGHT 1976, 20-JUN-2005
 
      Hewlett-Packard Development Company, L.P.
 
   Do you want the defaults for all options? [YES] 

• If you accept the default values, you receive the same components that you selected when you last installed or upgraded the system (instead of all the components currently available) plus any new components that were not in the previous version of the OpenVMS operating system.



• If you want to include or exclude any components differently than you did in the last installation or upgrade, you must answer NO and then respond to the prompts for each option, even those that you are not changing.



• If you want to review the current defaults first, answer NO. Then answer YES when the system asks whether you want to view the values.
  
  If you review the defaults and are satisfied, answer YES to the prompt asking whether you are satisfied with the values. If you want to make changes, answer NO to that question and then answer YES when the system asks whether you want to reenter the values.

When you select component options, also note the following:

• Whether you choose all the default values or select individual files, the system allows you to view your selections and make changes.



• If you are not sure whether you want certain component options, you can request help by entering a question mark (?) at the prompt for that component (or group of components).



• You should review the list of options and compare them with the requirements for your procedure. If you are selecting components individually, be sure that you include all components necessary to support the needs of your users. Note also that certain components depend upon the installation of other components.



• OpenVMS Management Station software is installed automatically on your OpenVMS system disk when you accept all the default values. If you do not accept the default values, you must select the OpenVMS Management Station component (server and client files) if you plan to use that product. After the upgrade is complete, you can then prepare your OpenVMS system and your PC to run OpenVMS Management Station by following the procedures described in Preparing to Use OpenVMS Management Station.



• If you decide after the upgrade to change which OpenVMS operating system components you want installed on your system, you must reconfigure the installation as described in Adding and Removing Operating System Files (Optional).



• After you boot the upgraded system disk and log in, you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($).

Unless you have specific reasons to do otherwise, HP recommends that you accept the defaults and install all OpenVMS options. OpenVMS and layered products have various dependencies on many of these options. Even if you think you do not need certain options, some OpenVMS or layered product operations might not work correctly if other OpenVMS options are not installed.

    
    You are installing the Performance Data Collector runtime 
    environment for use ONLY with Version 8.2-1 of OpenVMS 
    on Integrity server platforms.
 
    Note that a full kit that provides runtime environments for all 
    OpenVMS configurations supported by the Performance Data Collector, 
    and that includes a Software Developers Kit, can be downloaded from 
    URL:
 
            http://www.hp.com/products/openvms/tdc/
 
    %TDC-I-NOSTRT, The TDC startup and IVP procedures will not be run
 
    Insert the following line in SYS$MANAGER:SYSTARTUP_VMS.COM: 
 
    
            @sys$startup:tdc$startup.com
 
    Availability Manager (base) for OpenVMS I64 (required part of OpenVMS)
 
    CDSA for OpenVMS I64 (required part of OpenVMS)
 
    KERBEROS for OpenVMS I64 (required part of OpenVMS)
 
    Performance Data Collector (base) for OpenVMS I64 (required part of OpenVMS)
 
      Do you want to continue? [YES] 

Component and Product Installation Confirmation Messages  

When you have answered all the prompts and selected the components you want installed, the system allows you to review your selections and make changes, and then displays information about the various components and products that were installed, as shown in the following sample display in which the review is not chosen. You might see an %UPGRADE-I-FIXUP message, which indicates that obsolete files on the system were incorrectly saved by remedial kits. The "fixup" allows them to be correctly removed.

   Do you want to review the options? [NO] NO
 
   Execution phase starting ...
 
   %PCSI-W-VERRES, version types W through Z are reserved for HP internal use
   -PCSI-W-VERINS, the installation of product HP I64VMS AVAIL_MAN_BASE V8.2-1
   -PCSI-W-VERREM, will remove current product HP I64VMS AVAIL_MAN-BASE V8.2
 
   %PCSI-W-VERRES, version types W through Z are reserved for HP internal use
   -PCSI-W-VERINS, the installation of product HP I64VMS OPENVMS V8.2-1
   -PCSI-W-VERREM, will remove current product HP I64VMS OPENVMS V8.2
 
   The following products will be installed to destinations:
       HP I64VMS AVAIL_MAN_BASE V8.2-1        DISK$I64821:[VMS$COMMON.]
       HP I64VMS DECNET_PLUS V8.2-1           DISK$I64821:[VMS$COMMON.]
       HP I64VMS OPENVMS V8.2-1               DISK$I64821:[VMS$COMMON.]
       HP I64VMS TDC_RT V2.1-nn               DISK$I64821:[VMS$COMMON.]
       HP I64VMS VMS V8.2-1                   DISK$I64821:[VMS$COMMON.]
    
   The following products will be removed from destinations:
       HP I64VMS AVAIL_MAN_BASE V8.2          DISK$I64821:[VMS$COMMON.]
       HP I64VMS DECNET_PLUS V8.2             DISK$I64821:[VMS$COMMON.]
       HP I64VMS OPENVMS V8.2                 DISK$I64821:[VMS$COMMON.]
       HP I64VMS TDC_RT V2.1-69               DISK$I64821:[VMS$COMMON.]
       HP I64VMS VMS V8.2                     DISK$I64821:[VMS$COMMON.]
 
   Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%  
 
   The following products have been installed:
       HP I64VMS AVAIL_MAN_BASE V8.2-1        Layered Product
       HP I64VMS DECNET_PLUS V8.2-1           Layered Product
       HP I64VMS OPENVMS V8.2-1               Platform (product suite)
       HP I64VMS TDC_RT V2.1-nn               Layered Product
       HP I64VMS VMS V8.2-1                   Operating System
 
   The following products have been removed:
       HP I64VMS AVAIL_MAN_BASE V8.2          Layered Product
       HP I64VMS DECNET_PLUS V8.2             Layered Product
       HP I64VMS OPENVMS V8.2                 Platform (product suite)
       HP I64VMS TDC_RT V2.1-69               Layered Product
       HP I64VMS VMS V8.2                     Operating System
                  
   HP I64VMS OPENVMS V8.2-1: OPENVMS and related products Platform
  
       HP I64VMS TDC_RT V2.1: The Performance Data Collector (base) for OpenVMS
 
         Users of this product require the following privileges:
             (CMKRNL,LOG_IO,WORLD,PHY_IO,SYSPRV,SYSLCK)
 
         Users of this product require the following process resource limits:
             WSQUO minimum 4000
 
         A read-me file is available in SYS$COMMON:[TDC]TDC_README.TXT
     
         Release notes are available in SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT

Configuring and Validating Boot Options 

At this point during an OpenVMS I64 upgrade, you are asked whether you plan to use the system disk you just upgraded (in this case, DKB400:) to boot this system:

   Will DKB400 normally be used when you boot this system
   from the system disk you have just intalled? (Yes/No)

If your newly upgraded 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.

If you do not want the upgrade procedure to assist you in setting up or validating boot options on the EFI console, answer NO. If you answer NO, you can set up and validate boot options later (refer to Setting Boot Options for Your System Disk). You can boot the system disk manually now (refer to Booting Manually from the Local System Disk).

To configure booting on Fibre Channel devices, you must use the OpenVMS I64 Boot Manager utility (BOOT_OPTIONS.COM). (Use of the utility is optional for other devices but mandatory for Fibre Channel devices.) HP recommends using this utility to add members of a multiple-member shadow set to the boot device list and the dump device list. Be sure to add all members to both device lists. For information about the OpenVMS I64 Boot Manager utility, refer to Setting Boot Options for Your System Disk. For information about configuring and booting Fibre Channel devices, refer to Setting Up and Booting Fibre Channel Storage Devices.

• If you answer NO, the following message is displayed:

     If there is an existing boot option that was used to boot this
     system disk, you may be able to use it. Otherwise, you will have
     to use the EFI Shell the first time that you boot the newly
     installed system. After booting, use the OpenVMS I64 Boot Manager
     to create a Boot Option. To do this log in to a privileged
     account and execute this command:
   
         $ @SYS$MANAGER:BOOT_OPTIONS 

  
  
  The system then informs you that the upgrade is complete and prompts you to press Return to continue, at which point it returns you to the OpenVMS main menu. You could select option 7 ("Execute DCL commands and procedures") from the OpenVMS main menu and enter the command at the DCL prompt ($$$) to invoke the OpenVMS I64 Boot Manager utility.



• If you answer YES, the installation procedure determines whether a boot entry already exists for the system disk (DKB400:):

  If an entry is found, a message similar to the following is displayed: The EFI Boot Manager menu includes the following boot option(s) for DKB400: EFI Boot Options list: Timeout = 0 secs. ---------------------------------------------------------------------- 01. DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) "OpenVMS on DKB400: PKA0.1" ---------------------------------------------------------------------- 1 entries found. In this example, one boot option is found. If multiple entries are found and if they are all SCSI devices, the procedure displays the following message and then notifies you that the upgrade is complete. Noted that you are given the opportunity to invoke the OpenVMS I64 Boot Manager to validate the boot option for your system. Please use the OpenVMS I64 Boot Manager to ensure that you have a valid boot option for the system you have just installed. When one entry is found, as in the example given, or if multiple Fibre Channel entries are found, the procedure displays the following information and prompt: Validating will ensure that the system you have just installed will boot correctly. Do you want to validate the boot option(s)? (Yes/No) [Yes] Validate the boot option by entering YES or by pressing Enter (or Return) at the prompt. The validation process is displayed, as in the following example, in which the found entry fails to boot and is then fixed and validated: Validate EFI Boot Options list: Timeout = 0 secs. ----------------------------------------------------------------------- 01. DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) OpenVMS on DKB400: PKA0.1 efi$bcfg: Option Failed. Fixing Boot Entry automatically. efi$bcfg: Entry 1 Boot0001 removed. efi$bcfg: DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) (Boot0001) Option successfully added ----------------------------------------------------------------------- 1 entries validated.

  If no existing entry is found, you are asked whether you want to add a boot option: Do you want to add a boot option? (Yes/No) [Yes] Answer YES or press Enter (or Return) to have the procedure add a boot option for you. You then see a message confirming that the boot option was added successfully: efi$bcfg: dkb400: (Boot0001) Option successfully added. The boot option is called "OpenVMS on DKB400:"; it is the first entry in the Boot Options menu, and is configured (by default) to boot from SYS0. If you answer NO, you are given the opportunity to run the OpenVMS I64 Boot Manager, as described next.

At this point, whether you answered NO or YES to the initial prompt ("Will DKB400: normally be used when you boot this system from the system disk you have just installed?"), the following message and prompt are displayed:

     If you want to run the OpenVMS I64 Boot Manager to examine,
     change or validate entries in the EFI Boot Manager menu, you
     can do so at this time.
 
     Alternatively you can run the OpenVMS I64 Boot Manager
     after the installation or upgrade completes. To do this choose 
     the DCL option from the main menu and then execute this command:
 
        $$$ @SYS$MANAGER:BOOT_OPTIONS
 
     You can also execute this command from a properly privileged
     account after booting your OpenVMS I64 system.
 
   Do you want to run the OpenVMS I64 Boot Manager now? (Yes/No) [No]

If you answer YES to this prompt, the procedure invokes the OpenVMS I64 Boot Manager. (For more information about using this utility, refer to Setting Boot Options for Your System Disk and the HP OpenVMS System Manager's Manual, Volume 1: Essentials ). When you finish and exit the utility, a message is displayed indicating the installation is complete, followed by other information and then the operating system menu (refer to Upgrade Completes and Returns to OpenVMS Operating System Menu).

If you answer NO, a message is displayed indicating the installation is complete, followed by other information and the operating system menu (refer to Upgrade Completes and Returns to OpenVMS Operating System Menu).

Upgrade Completes and Returns to OpenVMS Operating System Menu  

The upgrade procedure is now complete. The procedure displays information about the special startup procedure that runs when the newly installed system is first booted. It then prompts you to press Return to continue. After you do so, you are returned to the OpenVMS operating system menu. The following is a sample display:

   The upgrade is now complete.
 
    When the newly upgraded system is first booted, a special
    startup procedure will be run.  This procedure will:
 
      o  Run AUTOGEN to set system parameters.
      o  Reboot the system with the newly set parameters.
 
 
    You may shut down now or continue with other operations.
 
     Process I64VMS_INSTALL logged out at 15-JUN-2005 14:45:49.54
 
    Press Return to continue...
 
    ****************************************************************
 
    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 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 I64 Version 8.2-1
        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/?)

Shutting Down the System  

Unless you want to perform any other operations prior to booting the upgraded disk, shut the system down by choosing the shutdown option (8) from the menu:

    Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?)  8
      Shutting down the system
       .
       .
       .
 
	    SYSTEM SHUTDOWN COMPLETE

Performing the Upgrade

What to Do After the Shutdown