You can use the MP to establish remote console access, such as through the TELNET utility provided with TCP/IP Services for OpenVMS. Alternatively, you can access the MP console interface through the Internet using a browser.

If you intend to set up LAN or remote access for the MP console, you must initially use the serial port for console operations when you set up the machine for the first time. (See your hardware documentation for instructions on setting LAN or remote access for the MP console interface.)

On systems which support iLO-MP, OpenVMS enables the Integrated Console which provides a virtual keyboard, video and mouse (vKVM) to operate from a remote iLO browser window. The Integrated Console functionality allows both pre-boot (UEFI), OpenVMS boot, and runtime (both text console and DECwindows) display and interaction from the iLO browser window.

Most HPE Integrity servers support multiple VGA graphics options. A graphics option consists of a graphics card and a graphics display interface (monitor). When multiple graphics devices are present, you can select only one device for use as a console device. The other graphics devices must be set to Not Configured (NC).

When DECwindows is used on a system booted using the VGA as the OpenVMS console, DECwindows selects the VGA console as the default screen. When enabling multihead DECwindows graphics operation, the VGA console defaults to screen 0. If no VGA device is configured as a console, DECwindows selects a default screen based on the HPE Integrity server model and device bus ordering.

By default, the maximum resolution of the graphics display in DECwindows is 1024x768. This is a restriction of the iLO-MP firmware. To use the Integrated Console, the system must be set up with VGA as the primary console. Both the local keyboard, video and mouse can be used in addition to (or at the same time) with the remote iLO Integrated Console. Performance of DECwindows graphics using the iLO Integrated Console will vary depending on the speed of the LAN, and in general is only recommended for doing occasional system management functions that do not require performance sensitive graphics.

This section describes how to select a console on rx2600 HPE Integrity servers or other servers with outdated firmware. On such servers, you must configure a Console Input, Console Output, and Console Error Device for your OpenVMS console. There is no concept of the Primary console that automatically configures these devices. In addition, on such servers OpenVMS does not support graphics consoles.

Once your console has been configured, return to Section 2.1.

You can upgrade directly to VSI OpenVMS Version 8.4-2 from the following versions of OpenVMS:

If you are running versions prior to these, you must incrementally upgrade to one of these versions before upgrading to VSI OpenVMS 8.4-2, or you can choose to perform a complete installation rather than an upgrade.

If you need an Update License, please contact your VSI Sales representative <info@vmssoftware.com>.

The upgrade procedure is designed so that you do not need to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures.

The upgrade procedure leaves your OpenVMS license and layered product licenses intact. You do not need to reinstall these licenses after you upgrade.

If you changed the directory structure on your system disk, the upgrade procedure does not work correctly. Restore your system disk to a standard directory structure before you attempt an upgrade.

The OpenVMS upgrade procedure provides new files and directories in the directory [VMS$COMMON...]. If you have any special protections and access control lists (ACLs), you need to reapply them to reestablish the security environment you currently have. For more information about creating and maintaining a secure environment, see the VSI OpenVMS Guide to System Security manual.

For the upgrade to be successful, the SYSCOMMON directories in all system roots must be aliases (or hard links) for the VMS$COMMON directory. To check whether this is the case, enter the following commands if you are booted from the system disk that you are upgrading, and compare the displayed file identifiers to ensure that they are all the same:

$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[SYS*]SYSCOMMON.DIR

If you did not boot from the system disk that you are upgrading, mount the disk to be upgraded and specify the actual device name in the command. For example, if the system disk to be upgraded is mounted on DKA100, you would use commands similar to the following:

$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[SYS*]SYSCOMMON.DIR

Output from the first command should list a single file. Output from the second command should list one file for each system root on the disk. Check whether the file ID is the same for all of the listed files and take action as follows:

To free up disk space and file headers, purge the system disk of certain large files. VSI recommends that you enter the following commands, as shown:

$ PURGE/LOG/BEFORE=TODAY SYS$SYSDEVICE:[000000...]*.LOG
$ PURGE/LOG SYS$SYSTEM:PAGEFILE*.SYS
$ PURGE/LOG SYS$SYSTEM:SWAPFILE*.SYS
$ PURGE/LOG SYS$SYSTEM:SYSDUMP.DMP

Check the system disk for application and system dump files by entering the following command:

$DIRECTORY/SIZE/DATE SYS$SYSDEVICE:[000000...]*.DMP

If any .DMP files are found, use your discretion and delete them. Unless these files are important for a current problem investigation, they are unlikely to be applicable after the new version upgrade and they may consume a significant amount of disk space.

Examine and repair if necessary, the system disk using the ANALYZE/DISK_STRUCTURE command. (See the VSI OpenVMS System Management Utilities Reference Manual: A-L for more information about this command.) Use the following procedure:

It is difficult to determine in advance how many blocks of disk space you need for the upgrade. It depends on how many files you have on the target disk already and on how many components you select during the upgrade procedure. However, the following information will help:

To see how much space you have on the system disk, enter the following command:

$ SHOW DEVICE SYS$SYSDEVICE

If you place authorization and AGEN$INCLUDE files on disks other than the system disk, the upgrade procedure will not find these files. This is because the other disks are not mounted during the upgrade. In addition, the logical names you set up to point to these files are not defined during the upgrade. The following sections explain how to make these files available to the upgrade procedure.

Verify (and modify if necessary) system parameters. (For information about verifying and modifying system parameters, see the VSI OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.)

During an upgrade, AUTOGEN initially generates parameter values based on parameter defaults. However, during the GETDATA phase, AUTOGEN modifies parameter values based on entries stored in SYS$SYSTEM:MODPARAMS.DAT. In addition, AUTOGEN analyzes feedback information stored in the AGEN$FEEDBACK.DAT file and, if the data is valid, adjusts any related parameter values accordingly. (AUTOGEN considers data as valid if the system has been up at least for 24 hours and the feedback is no more than 30 days old.)

MIN_GBLPAGES=30128  !Increased by 128 by PLM for product z 12/12/04

If your system was upgraded previously, a new SYS$SYSTEM:MODPARAMS.DAT file was created then. This file has comments and possibly duplicated entries that were created during that upgrade. If you upgrade again, SYS$SYSTEM:MODPARAMS.DAT can become unnecessarily large and potentially confusing. VSI recommends that you edit and reorganize SYS$SYSTEM:MODPARAMS.DAT before you upgrade again.

Be sure your system is set to boot by default from the disk you intend to upgrade.

VSI recommends using the OpenVMS Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM) to add shadowed system disks in a multiple-member shadow set to the UEFI boot device list and dump device list. Be sure to add all members to both lists. For more information about setting boot options and using this utility, see Section 9.4.1.

Perform the steps described in this section to change one of your existing shadowed system disks to a nonshadowed disk.

You now have a nonshadowed system disk that you can use for the upgrade.

During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade each system disk and reboot each computer. When the cluster reboots, each computer will run the upgraded version of the OpenVMS operating system.

If all systems in the OpenVMS Cluster environment are booted from one system disk, you must perform a concurrent upgrade.

To prepare for a concurrent upgrade, follow these steps:

A rolling upgrade allows you to have a mixed-version cluster. During a rolling upgrade, you keep some of the computers in the cluster running and available while you upgrade others. You must have more than one system disk. You upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster.

For additional compatibility issues and restrictions information, see the VSI OpenVMS Version 8.4-2 Release Notes.

The following restrictions apply to rolling upgrades:

To prepare for a rolling upgrade, follow these steps:

If a proper quorum is not maintained at any time during the upgrade procedure, the shutdown procedure hangs the cluster. If the cluster hangs during a shutdown, you can use the Interrupt Priority C (IPC) facility to adjust quorum from the system console of a system that is still a cluster member.

From an HPE Alpha cluster member, press Ctrl/P. The IPC facility displays help information about IPC commands. Enter the commands at the console:

$ Ctrl/P
>>> D SIRR C
>>> C
Interrupt Priority C

Commands:

  C device    Cancel Mount Verification
  Q           Adjust Quorum
  CTRL-Z      Exit IPC
  CTRL-P      Prompt for Crash
IPC> Q
IPC> Ctrl/Z

$ Ctrl/P
Interrupt Priority C

Commands:

  C device    Cancel Mount Verification
  Q           Adjust Quorum
  CTRL-Z      Exit IPC
  CTRL-P      Prompt for Crash
IPC> Q
IPC> Ctrl/Z

You can also adjust quorum using Availability Manager. The method is equivalent to that used by IPC except you do not have to use the console (this assumes the Data Analyzer is running on a system outside the OpenVMS Cluster, which is recommended). For more information, see the “Adjust Quorum” section in the VSI Availability Manager User's Guide.

After the shutdown procedure is finished on all nodes, go to Part II to begin the upgrade procedure.

Boot the VSI OpenVMS OE DVD from a local DVD drive by performing the steps included in this section. To boot the DVD on a cell-based server, a DVD device must be accessible by the nPartition on which OpenVMS is being installed and console commands must be issued from the console of that nPartition.

To use the InfoServer utility to boot over a network, certain configuration steps are required initially (one time only); see Section 9.17. The instructions on booting over the network from a virtual DVD are also included in that section.

At different points during the installation, you must respond to prompts that ask for specific information. This manual and the help text available during the installation procedure tell you how to obtain most of this information and how to make decisions when responding to specific prompts.

To repeat an explanation provided by the installation procedure, type a question mark (? ) at the prompt. To change or correct a response made to an earlier question, enter the caret (^) character as many times as needed. Entering this character might take you back more than one question. To return to the main menu, press Ctrl/Y, which aborts the installation.

VSI recommends that you review the following summary before you begin the installation so that you understand beforehand the types of information you need to provide.

During the installation, you will be prompted to supply the following information:

Select Option 1 on the main Installation Menu to upgrade, install or reconfigure your OpenVMS software. Selecting Option 1 implements a PCSI utility concept called a platform.

The VSI OpenVMS platform contains System Integrated Products (SIP's) that may be automatically installed and optional products for which you will be prompted whether to install. Refer to the Software Product Description for details regarding product versions.

The current platform includes the following products:

If you are installing the VSI OpenVMS High Availability Operating Environment (HAOE) you will receive the contents of the base environment listed above, as well as the following products:

Including the optional products in the OpenVMS platform allows you to install or upgrade these products along with the operating system.

When you choose to upgrade the system disk, and the software on the disk is the same version, you are given options to reinstall or to reconfigure the system or reconfigure the OpenVMS platform.

When you select Option 1 on the Installation Menu, the system asks whether you want to preserve or initialize the system disk. The display is similar to the following:

    There are two choices for Installation/Upgrade:

    INITIALIZE - Removes all software and data files that were
      previously on the target disk and installs VSI OpenVMS.

    PRESERVE -- Installs or upgrades VSI OpenVMS on the target disk
      and retains all other contents of the target disk.

    * Note: You cannot use PRESERVE to install VSI OpenVMS 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]

Use Option 2 to display the layered products and patch kits that can be installed. Generally speaking, products that can be installed or upgraded along with the operating system, should be.

In the following example, WBEMCIM is the file name used in the PCSI kit for the WBEM Services for OpenVMS product. CIM stands for the Common Information Model, which differentiates the current OpenVMS WBEM product from the original one that is based on the Simple Network Management Protocol (SNMP). The version numbers in this example do not necessarily reflect the version numbers of the products actually shipped with VSI OpenVMS Version 8.4-2.

     The following versions of the OpenVMS operating system,
     required components and other optional products
     are available on the VSI OpenVMS distribution media DVD.
     They can be installed by selecting Option 1:

   VSI I64VMS OpenVMS Version 8.4-2
   VSI I64VMS AVAIL_MAN_BASE V8.4-2
   VSI I64VMS CDSA version V2.4
   VSI I64VMS KERBEROS version V3.2
   VSI I64VMS SSL V1.4-284
   VSI I64VMS TDC_RT version V2.3-20
   VSI I64VMS BINARYCHECKER version V1.0
   VSI I64VMS WBEMCIM version V2.9-9
   VSI I64VMS WBEMPROVIDERS version  V2.2-3
   VSI I64VMS DWMOTIF version V1.7
   VSI I64VMS DECNET_PLUS version V8.4-2
   VSI I64VMS DECNET_PHASE_IV version V8.4-2
   VSI I64VMS TCPIP version V5.7

     The following Layered Product kits are available on the VSI OpenVMS
     Distribution media (DVD).They can be installed by selecting
     Option 3.If they are already installed, they can be reconfigured
     by selecting Option 5, or removed by selecting Option 6.

   ----------------------------------- ----------- ----------
   PRODUCT                              KIT TYPE   KIT FORMAT
   ----------------------------------- ----------- ----------
   VSI I64VMS AVAIL_MAN_BASE V8.4-2      Full LP    Compressed
   VSI I64VMS CDSA V2.3-306              Full LP    Compressed
   VSI I64VMS DECNET_PHASE_IV V8.4-2     Full LP    Compressed
   VSI I64VMS DECNET_PLUS V8.4-2         Full LP    Compressed
   VSI I64VMS DWMOTIF V1.7               Full LP    Compressed
   VSI I64VMS HPBINARYCHECKER V1.0       Full LP    Compressed
   VSI I64VMS DWMOTIF_SUPPORT V8.4-2     Full LP    Compressed
   VSI I64VMS KERBEROS V3.1-152          Full LP    Compressed
   VSI I64VMS SSL V1.4-284               Full LP    Compressed
   VSI I64VMS TCPIP V5.7                 Full LP    Compressed
   VSI I64VMS TDC_RT V2.3-1              Full LP    Compressed
   VSI I64VMS WBEMCIM V2.91-A070728      Full LP    Compressed
   VSI I64VMS WBEMPROVIDERS V2.0-31      Full LP    Compressed
   ----------------------------------- ----------- ----------

   13 items found

   Press Return to continue...

Use Option 3 on the Installation Menu for normal installations or upgrades of layered products.

When you select Option 3, the PCSI utility allows you to choose whether to install layered products or to register layered products that are on the target disk but are not in the Product Database. If you attempt to reinstall the same version of a product that is already installed, the product is reinstalled. Any patches that were applied to the product are removed. If you want to reconfigure, select the RECONFIGURE (Option 5) on the Installation Menu.

Most of the software kits included on the VSI OpenVMS distribution media are signed using Secure Delivery. When you use Option 3 of the Installation Menu, these kits are validated by the PCSI utility. You can install kits created before the secure delivery process was enabled in HPE OpenVMS Version 8.3. However, after you install or upgrade to OpenVMS Version 8.3 or later, signed kits that you install subsequently are validated, including any signed kits included on the distribution media.

The DCL command PRODUCT SHOW HISTORY displays the validation status of these kits as unsigned rather than as a validated kit.

As shown in the following example, you are also prompted for a target disk and asked whether you want brief or detailed descriptions. The procedure presents a list of products and allows you to select any or all of these products. Alternatively, you can exit without installing or upgrading any products.

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

   The 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

Do you want to INSTALL or REGISTER? (INSTALL/REGISTER/? ) [INSTALL] INSTALL
   ***********************************************************

   If you choose to install or upgrade DECwindows Motif,
   please note the following:

   o If you did not select the DECwindows server support
     and workstation files options, DECwindows Motif will not run.
     You must add these options to use DECwindows Motif.

   If you choose to install or upgrade DECnet-Plus or DECnet Phase IV,
   please note the following:

   o If you did not select the DECnet option, neither version
     of DECnet will run.You must add this option to use DECnet.

   If you want to install a patch kit, please use main menu option 7.

Press Return to continue...

   You must enter the device name for the target disk on which
   the layered product(s) installation will be performed.

Enter device name for target disk: [DKB300] (? for choices) DKB300

   DKB300: is labeled V84SYS.


   The install 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] NO

 1 - VSI I64VMS AVAIL_MAN_BASE V8.4-2      Layered Product
 2 - VSI I64VMS CDSA V2.4                    Layered Product
 3 - VSI I64VMS DECNET_PHASE_IV V8.4-2     Layered Product
 4 - VSI I64VMS DECNET_PLUS V8.4-2         Layered Product
 5 - VSI I64VMS DWMOTIF V1.7                 Layered Product
 6 - VSI I64VMS DWMOTIF_SUPPORT V8.4-2     Layered Product
 7 - VSI I64VMS BINARYCHECKER V1.0           Layered Product
 8 - VSI I64VMS KERBEROS V3.2                Layered Product
 9 - VSI I64VMS SSL V1.4-284                 Layered Product
10 - VSI I64VMS TCPIP V5.7                   Layered Product
11 - VSI I64VMS TDC_RT V2.3-20               Layered Product
12 - VSI I64VMS WBEMCIM V2.99                Layered Product
13 - VSI I64VMS WBEMPROVIDERS V2.2-3         Layered Product
14 - All products listed above
 ? - Help
 E - Exit

Choose one or more items from the menu separated by commas: 9

Use Option 4 on the Installation Menu to display a list of products that have been installed on a selected target disk by the PCSI utility. Products that were installed by VMSINSTAL or other installation methods do not appear in this display unless they have been registered in the PCSI utilitys product database.

The following is a sample display of the prompts and information that appear when you select Option 4 and WBEM Services for OpenVMS and WBEM Providers for OpenVMS. The version numbers in this example do not necessarily reflect the version numbers of the products actually shipped with VSI OpenVMS Version 8.4-2.

   You must enter the device name for the system disk for which
   you want to display installed products.

   If you enter an invalid device or one which is not a system disk
   an error will occur.

   (Enter "^" and press Return to return to main menu.)

Enter device name for system disk:[DKB300] (? for choices) DKB300
%MOUNT-I-MOUNTED, V84SYS mounted on _DKB300:

   The default is an 80-column display that does not include
   Maintenance (patches) or Referenced by information.

Do you want the full, 132-column display? (Yes/No) [No] NO

------------------------------------- ------------ ------------
PRODUCT                               KIT TYPE     STATE
------------------------------------- ------------ ------------
VSI I64VMS AVAIL_MAN_BASE V8.4-2     Full LP      Installed
VSI I64VMS CDSA V2.3-306               Full LP      Installed
VSI I64VMS DECNET_PLUS V8.4-2        Full LP      Installed
VSI I64VMS DWMOTIF V1.7                Full LP      Installed
VSI I64VMS DWMOTIF_SUPPORT V8.4-2    Full LP      Installed
VSI I64VMS HPBINARYCHECKER V1.0        Full LP      Installed
VSI I64VMS KERBEROS V3.1-152           Full LP      Installed
VSI I64VMS OpenVMS V8.4-2            Platform     Installed
VSI I64VMS TCPIP V5.7                  Full LP      Installed
VSI I64VMS VMS V8.4-2                Oper System  Installed
VSI I64VMS SSL V1.4-284                Full LP      Installed
VSI I64VMS TDC_RT V2.3-1               Full LP      Installed
VSI I64VMS WBEMCIM V2.91-A070728       Full LP      Installed
VSI I64VMS WBEMPROVIDERS V2.0-31       Full LP      Installed
------------------------------------- ------------ ------------

12 items found
Do you wish to display product history? (Yes/No) [No] YES

----------------------------------- ----------- ----------- --------------------
PRODUCT                             KIT TYPE    OPERATION   DATE AND TIME
----------------------------------- ----------- ----------- --------------------
VSI I64VMS AVAIL_MAN_BASE V8.4-2   Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS CDSA V2.3-306             Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS DECNET_PLUS V8.4-2      Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS DWMOTIF V1.7              Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS KERBEROS V3.1-152         Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS OpenVMS V8.4-2          Platform    Install     25-JAN-2015 18:04:23
VSI I64VMS TCPIP V5.7                Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS VMS V8.4-2              Oper System Install     25-JAN-2015 18:04:23
VSI I64VMS SSL V1.4-284              Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS WBEMCIM V2.91-A070728     Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS WBEMPROVIDERS V2.0-31     Full LP     Install     25-JAN-2015 18:04:23
VSI I64VMS TDC_RT V2.3-1             Full LP     Install     25-JAN-2015 18:04:23
HP I64VMS AVAIL_MAN_BASE V8.3        Full LP     Remove      25-SEP-2009 18:04:23
HP I64VMS CDSA V2.2                  Full LP     Remove      25-SEP-2009 18:04:23
HP I64VMS DECNET_PHASE_IV V8.3       Full LP     Remove      25-SEP-2009 18:04:23
HP I64VMS DWMOTIF V1.6               Full LP     Remove      25-SEP-2009 18:04:23
HP I64VMS OpenVMS V8.3               Platform    Remove      25-SEP-2009 18:04:23
HP I64VMS VMS V8.3                   Oper System Remove      25-SEP-2009 18:04:23
HP I64VMS KERBEROS V3                Transition  Remove      25-SEP-2009 18:04:23
HP I64VMS KERBEROS V3                Transition  Reg Product 25-SEP-2008 17:20:44
HP I64VMS CDSA V2.1                  Full LP     Install     27-AUG-2004 21:07:15
HP I64VMS DECNET_PHASE_IV V8.2       Full LP     Install     27-AUG-2004 21:07:15
HP I64VMS DWMOTIF V1.5               Full LP     Install     27-AUG-2004 21:07:15
HP I64VMS OpenVMS V8.3               Platform    Install     27-AUG-2004 21:07:15
HP I64VMS TCPIP V5.4-18              Full LP     Install     27-AUG-2004 21:07:15
HP I64VMS VMS V8.3                   Oper System Install     27-AUG-2004 21:07:15
----------------------------------- ----------- ----------- --------------------

26 items found

Press Return to continue...

Use Option 5 of the Installation Menu to reconfigure layered products, including the DECwindows graphical user interface and networking products. This allows you to change the product choices you made during a previous installation or upgrade.

You can reconfigure a product only if all of the following conditions are true:

When you select Option 5 on the Installation Menu, the procedure prompts you for a target disk name and asks whether you want brief or detailed descriptions about the reconfiguration options. The procedure then lists the products you can configure. You can select any or all of these products, or you can exit without reconfiguring products.

The following is a sample display of the prompts and information that might appear when you select Option 5. The version numbers in this example do not necessarily reflect the version numbers of the products actually shipped with VSI OpenVMS Version 8.4-2.

   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


   You must enter the device name for the target disk on which
   the layered product(s) reconfiguration will be performed.

Enter device name for target disk: [DKB300] (? for choices) DKB300

   DKB300: is labeled V84SYS.


   The reconfigure 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] NO

 1 - VSI I64VMS AVAIL_MAN_BASE V8.4-2    Layered Product
 2 - VSI I64VMS CDSA V2.3-306              Layered Product
 3 - VSI I64VMS DECNET_PHASE_IV V8.4-2   Layered Product
 4 - VSI I64VMS DECNET_PLUS V8.4-2       Layered Product
 5 - VSI I64VMS DWMOTIF V1.7               Layered Product
 6 - VSI I64VMS DWMOTIF_SUPPORT V8.4-2   Layered Product
 7 - VSI I64VMS HPBINARYCHECKER V1.0       Layered Product
 8 - VSI I64VMS KERBEROS V3.1-152          Layered Product
 9 - VSI I64VMS SSL V1.4-284               Layered Product
10 - VSI I64VMS TCPIP V5.7                 Layered Product
11 - VSI I64VMS TDC_RT V2.3-1              Layered Product
12 - VSI I64VMS WBEMCIM V2.91-A070728      Layered Product
13 - VSI I64VMS WBEMPROVIDERS V2.0-31      Layered Product
14 - All products listed above
 ? - Help
 E - Exit

Choose one or more items from the menu separated by commas:

When you select Option 6, you are prompted for a target disk name and whether you want brief or detailed descriptions about the remove options. The procedure then lists the products you can remove. You can select any or all of these products, or you can exit without removing any products.

The following is a sample display of the prompts and information that appear when you select Option 6. The version numbers in this example do not necessarily reflect the version numbers of the products actually shipped with VSI OpenVMS Version 8.4-2.

   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


   You must enter the device name for the target disk on which
   the layered product(s) removal will be performed.

Enter device name for target disk: [DKB300:] (? for choices) DKB300

   DKB300: is labeled V84SYS.


   The remove 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] NO

 1 - HP I64VMS AVAIL_MAN_BASE V8.3       Layered Product
 2 - HP I64VMS CDSA V2.3-306             Layered Product
 3 - HP I64VMS DECNET_PHASE_IV V8.3      Layered Product
 4 - HP I64VMS DECNET_PLUS V8.3          Layered Product
 5 - HP I64VMS DWMOTIF V1.6              Layered Product
 6 - HP I64VMS DWMOTIF_SUPPORT V8.3      Layered Product
 7 - HP I64VMS HPBINARYCHECKER V1.0      Layered Product
 8 - HP I64VMS KERBEROS V3.1-152         Layered Product
 9 - HP I64VMS SSL V1.4-284              Layered Product
10 - HP I64VMS TCPIP V5.7                Layered Product
11 - HP I64VMS TDC_RT V2.3-1             Layered Product
12 - HP I64VMS WBEMCIM V2.91-A070728     Layered Product
13 - HP I64VMS WBEMPROVIDERS V2.0-31     Layered Product
13 - All products listed above
 ? - Help
 E - Exit

Choose one or more items from the menu separated by commas:

  This procedure can perform one of the following operations:

    1)Install one or more patches
    2)Undo recent patches for which there is recovery data
    3)Show recovery data
    4)Delete recovery data
    5)Find patch kits

Enter CHOICE or X to return to main menu: (1/2/3/4/5/X)

Note the following about these options:

After you provide the necessary information, a PCSI/PRODUCT command automatically performs the operation you requested. If you chose options 1, 2, or 4 from the submenu, the PCSI utility prompts you for additional input and displays additional information.

$$$ SHOW DEVICE

   Shutting down the system

     SYSTEM SHUTDOWN COMPLETE

**** Primary HALTED with code HWRPB_HALT$K_REMAIN_HALTED

****   Hit any key to cold reboot   ****
P00>>>

A few seconds after you boot the distribution media DVD, several informational messages will appear, followed by the OpenVMS banner and eventually by the Installation Menu, as shown in the following example:

       .
       .
       .
  ****************************************************************
  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.4-2
  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/? )

To install OpenVMS, follow these steps:

After the system is rebooted with the new parameters, you can log into your SYSTEM account, as explained in Section 8.3. If you did not allow the installation procedure to create a boot option for your system disk, you can set up such an option now, as explained in Section 9.4. Chapter 9 includes additional information regarding setting up and booting your system.

This completes the basic installation. Next, we recommend that you review the information in the AFTER INSTALLATION part of this manual: Part III.

A few seconds after you boot the VSI OpenVMS OE DVD, several informational messages followed by the OpenVMS banner and eventually the Installation and Upgrade Menu appears.

To upgrade the OpenVMS operating system, choose Option (1) on the menu:

       .
       .
       .
  ****************************************************************
  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.4-2
  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

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, enter PRESERVE or press Enter (or Return) to accept the default (PRESERVE).

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 being upgraded and respond to the prompt:

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.

If you are using the VSI OpenVMS Version 8.4-2 operating system media and you selected a target disk that already has Version 8.4-2 installed, you are presented with several configuration options. A sample display follows.

Version 8.4-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 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 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" (Option 3) from the Installation 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 Installation 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/? )

When you specify the /SAVE_RECOVERY_DATA qualifier with the PRODUCT INSTALL command, the PCSI utility saves information that can be used for removing patches and mandatory update kits at a later time. The PRODUCT UNDO PATCH command removes the patches and kits.

The upgrade procedure, after entering the PRODUCT INSTALL command, checks the target disk for recovery data that was saved by the PCSI utility during patch installations. 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 data is deleted because it becomes invalid after the upgrade and the disk space freed up might be needed during the upgrade. (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 25-JUL-2014 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.

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 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]  I640842

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).

$ SET VOLUME/VOLUME_CHARACTERISTICS=HARDLINKS SYS$SYSDEVICE
$ ANALYZE DISK_STRUCTURE/REPAIR SYS$SYSDEVICE

   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).

   OpenVMS I64 systems include WBEM Services for OpenVMS; the WBEM data
   repository requires an ODS-5 disk.  If you choose to convert the
   target system disk to ODS-5, the repository can be on the system
   disk; otherwise you will need to provide an additional ODS-5 disk.
   (? 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 VSI OpenVMS System Management Utilities Reference Manual: A-L.

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

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

...OpenVMS I64 will be upgraded on DKB400:.

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 VSI 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. WBEM Services for OpenVMS
  does not require hard links. (? 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 (link) counts. ANALYZE/DISK/REPAIR counts the number of directory entries that reference each file, and sets the link count if it is incorrect. 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:

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

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

Boot options in the UEFI 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 this is your normal system disk and you want the upgrade procedure to assist you in setting up or validating boot options in the UEFI Boot Manager menu, answer YES.

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

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

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)

If you answer YES to this question, the procedure will ask whether your system will use IP for Cluster Communications.

Will this system use IP for Cluster Communications ?  (Yes/No)

If the system being upgraded is member of an existing cluster, answering YES to this question causes the SYS$MANAGER:CLUSTER_CONFIG.COM procedure to run automatically when your upgraded system is first booted. However, correct cluster membership information is required by the upgrade procedure. Note that you can run this procedure 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 the Guidelines for OpenVMS Cluster Configurations manual.

At this point, if you are upgrading from an HPE OpenVMS release to a VSI OpenVMS release, you will see information pertaining to the re-branding of installed product licenses. This process is required to maintain consistency in the installed product license database. Refer to Section 5 if you would like more 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 Section 6.3.8.

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

The following products are part of the OpenVMS installation;
    if necessary they will be installed or upgraded along with the OpenVMS operating system:

      o Availability Manager (base) for OpenVMS I64
      o CDSA for OpenVMS I64
      o KERBEROS for OpenVMS I64
      o SSL for OpenVMS I64
      o Performance Data Collector (base) for OpenVMS I64
      o HP Binary Checker for OpenVMS I64
      o WBEM Services for OpenVMS (WBEMCIM)
      o WBEM Providers for OpenVMS (WBEMPROVIDERS)

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

      o DECwindows Motif for OpenVMS I64
      o DECnet-Plus for OpenVMS I64
      o DECnet Phase IV for OpenVMS I64
      o TCP/IP Services for OpenVMS

    If you want to add or delete optional 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
    is already installed on your system. An upgrade is not required.

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

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

    SSL for OpenVMS I64...
    is installed on your system. An upgrade is not required.

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

    HP Binary Checker for OpenVMS I64

    DECwindows Motif for OpenVMS I64 V1.7
    is installed on your system. An upgrade is not required.

    The DECnet-Plus kit is provided with
    the OpenVMS operating system kit.  VSI 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.4-2? (Yes/No) [Yes]

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

    WBEM Services for OpenVMS (WBEMCIM)
    is installed on your system. It will be upgraded.

    WBEM Providers for OpenVMS (WBEMPROVIDERS)
    is installed on your system. It will be upgraded.

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.4-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 keep the currently installed version or upgrade to the newer version supplied with OpenVMS Version 8.4-2. If you choose to keep the currently installed version, you should verify what level of support for this version is available from HPE or VSI.

Some windowing and networking products might have versions installed that do not work with VSI OpenVMS Version 8.4-2. In this case, you are not given a choice to upgrade; the software is upgraded automatically.

The procedure 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]  

If you answer YES, the procedure displays additional explanatory text with each prompt.

PCSI kits included on the OpenVMS distribution media are signed using Secure Delivery. Each target file includes an associated digital signature file (also referred to as a manifest) that is used for Secure Delivery validation. This validation involves authenticating the originator and verifying the contents of the target file. The digital signature file has the same file name as the target file plus _ESW appended to the file extension, as in filename.PCSI$COMPRESSED_ESW.

When you upgrade from the distribution media (and if the re-branding procedure has not already done this), the upgrade procedure validates any PCSI kits that are being installed. For each kit successfully validated, you may see a message similar to the following:

Performing product kit validation of signed kits...
%PCSI-I-HPCVALPASSED, validation of
DKB400:[KITS.CDSA]HP-I64VMS-CDSA-Vnnnn-nnn-n.PCSI$COMPRESSED;1 succeeded
    .
    .
    .

Performing product kit validation ...
%PCSI-I-VSICVALPASSED, validation of
DKB400:[KITS.BINARYCHECKER]VSI-I64VMS-BINARYCHECKER-Vnnnn-nnn-n.PCSI$COMPRESSED;1 succeeded
   .
   .
   .

Signed PCSI kits that are installed subsequent to the initial boot of the OpenVMS DVD (including signed kits on the distribution media) are validated. In addition, the DCL command PRODUCT SHOW HISTORY displays the validation status of installed products.

As you begin the upgrade procedure, the procedure 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:
    VSI I64VMS OpenVMS V8.4-2 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.

VSI I64VMS OpenVMS V8.4-2: OpenVMS and related products Platform

   COPYRIGHT 1976, 2015 ...

   VMS Software, Inc.

Do you want the defaults for all options? [YES]

During an upgrade, the PCSI utility defines default values as the values that you selected when you last installed or upgraded the OpenVMS operating system on your system. Therefore, before you respond to the prompt, note the following:

When you select component options, also note the following:

If you answer YES to accept the defaults for all options, the procedure displays a message similar to the following, the contents of which depend on the products you chose to install. If you answer NO, the procedure prompts you for each option and suboption.

Availability Manager (base) for OpenVMS I64

CDSA for OpenVMS I64
KERBEROS for OpenVMS I64
SSL for OpenVMS I64
Performance Data Collector (base) for OpenVMS I64
HP Binary Checker for OpenVMS I64
WBEM Services for OpenVMS (WBEMCIM)
WBEM Providers for OpenVMS (WBEMPROVIDERS)

For a list of component options included with VSI OpenVMS Version 8.4-2 operating system, see Example 6.1.

When you have answered all the prompts and selected the components you want installed, the procedure 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 ...

The following products will be installed to destinations:
    VSI I64VMS CDSA V2.4-322A              DISK$I640842:[VMS$COMMON.]
    VSI I64VMS DECNET_PLUS V8.4-2          DISK$I640842:[VMS$COMMON.]
    VSI I64VMS HPBINARYCHECKER V1.1-A      DISK$I640842:[VMS$COMMON.]
    VSI I64VMS KERBEROS V3.2-256           DISK$I640842:[VMS$COMMON.]
    VSI I64VMS OpenVMS V8.4-2              DISK$I640842:[VMS$COMMON.]
    VSI I64VMS VMS V8.4-2                  DISK$I640842:[VMS$COMMON.]
    VSI I64VMS WBEMCIM V2.99-B100614       DISK$I640842:[VMS$COMMON.]
    VSI I64VMS WBEMPROVIDERS V2.2-3A       DISK$I640842:[VMS$COMMON.]

The following products will be removed from destinations:
    HP I64VMS CDSA V2.2                    DISK$I640842:[VMS$COMMON.]
    HP I64VMS DECNET_PLUS V8.3             DISK$I640842:[VMS$COMMON.]
    HP I64VMS KERBEROS V3.0                DISK$I640842:[VMS$COMMON.]
    HP I64VMS OpenVMS V8.3                 DISK$I640842:[VMS$COMMON.]
    HP I64VMS VMS V8.3                     DISK$I640842:[VMS$COMMON.]

Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%

The following products have been installed:
    VSI I64VMS CDSA V2.4-322A               Layered Product
    VSI I64VMS DECNET_PLUS V8.4-2           Layered Product
    VSI I64VMS HPBINARYCHECKER V1.1-A       Layered Product
    VSI I64VMS KERBEROS V3.2-256            Layered Product
    VSI I64VMS OpenVMS V8.4-2               Platform (product suite)
    VSI I64VMS VMS V8.4-2                   Operating System
    VSI I64VMS WBEMCIM V2.99-B100614........Layered Product
    VSI I64VMS WBEMPROVIDERS V2.2-3A........Layered Product

The following products have been removed:
    HP I64VMS CDSA V2.2                    Layered Product
    HP I64VMS DECNET_PLUS V8.2             Layered Product
    HP I64VMS KERBEROS V3.0                Layered Product
    HP I64VMS OpenVMS V8.3                 Platform (product suite)
    HP I64VMS VMS V8.3                     Operating System

VSI I64VMS OpenVMS 8.4-2: OpenVMS and related products Platform

   VSI I64VMS KERBEROS V3.1-152

      Configure and set up Kerberos

      If Kerberos will be run on this system, but has not been
      used previously, you need to perform the following steps.

      o Run the Kerberos configuration procedure:

        @SYS$STARTUP:KRB$CONFIGURE.COM

      o Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:

        $ @SYS$STARTUP:KRB$STARTUP

      o Add the following line to SYS$MANAGER:SYLOGIN.COM:

        $ @SYS$MANAGER:KRB$SYMBOLS

 ...similar messages will appear for other installed products...

Press RETURN to continue:

At this point in an upgrade, the procedure creates and validates boot options if you chose to have the procedure do so (see Section 7.1.8).

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

After the system shuts down, you can boot the newly upgraded system disk. AUTOGEN will run automatically, after which the system shuts down again and automatically reboots. If you are doing a concurrent or rolling upgrade in an OpenVMS Cluster environment, do not boot any other cluster members now.

Now go to Chapter 8 and check for any postupgrade tasks that need to be performed before the system and cluster can be used. Once you have completed all required postupgrade tasks, you can reboot and then use other cluster members.

Log in from a character-cell terminal by entering the user name SYSTEM followed by the password. The display is similar to the following:

        OpenVMS I64 Operating System, Version 8.4-2

Username: SYSTEM
Password:
  .
  .
  .
   OpenVMS I64 Operating System, Version 8.4-2 

If you forget your password for the SYSTEM account, follow the instructions in Section 9.14 to perform an emergency startup.

If you installed the DECwindows Motif for OpenVMS software on your workstation, do the following after the login window is displayed on your screen:

Message from user SYSTEM on HOMER
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found

The NET$PROXY.DAT file is the primary network proxy authorization file. The other network authorization file to be created is NETPROXY.DAT. To create the network proxy authorization files, enter the following commands:

$ SET DEFAULT SYS$COMMON:[SYSEXE]
$ MC AUTHORIZE CREATE/PROXY
$ SET DEFAULT SYS$LOGIN

%UAF-W-NETCHANERR, error assigning a channel to NET:
-SYSTEM-W-NOSUCHDEV, no such device available

For more information about network proxy accounts and files, see the VSI OpenVMS System Manager's Manual, Volume 1: Essentials. For more information about the Authorize utility, see the VSI OpenVMS System Management Utilities Reference Manual: A-L.

The initial installation of OpenVMS does not create the queue manager or any queues. VSI recommends that you create the queue manager and your default batch and print queues now. When you install layered products (as described in Section 8.26), some of these products expect such queues to be present or try to create queues themselves.

To set up the queue manager and a batch queue for new installations, enter the following commands at the DCL prompt.

$ START QUEUE /MANAGER /NEW_VERSION
$ INITIALIZE /QUEUE /START /BATCH SYS$BATCH

For more information about starting and creating queues, see the VSI OpenVMS System Manager's Manual, Volume 1: Essentials.

If you installed DECnet, or if you added DECnet during an upgrade, you must now configure DECnet. Follow the instructions provided for the version of DECnet you installed. The DECnet End System License is included with the Base Operating Environment (BOE). If you want your system to take advantage of the advanced features of DECnet (such as routing, DTSS server, DNS server), you must register and install the DECnet-Plus Extended Function License.

To load and register licenses, perform the steps described in Section 8.9.

If you installed DECnet-Plus for OpenVMS software, see the DECnet-Plus for OpenVMS Release Notes and the DECnet-Plus for OpenVMS Installation and Configuration manual for information about how to configure this software using the NET$CONFIGURE procedure.

If you installed DECnet Phase IV, see the DECnet for OpenVMS Guide to Networking manual for information about configuring this software using the NETCONFIG command procedure.

Once you have configured DECnet Phase IV, edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM so that the software starts when the system reboots. (This step is not required if you are running DECnet-Plus.) You can have the software start interactively or in batch mode by making one of the following changes:

Locate and uncomment the line:

$!$ START/NETWORK DECNET

So it now appears as:

$ START/NETWORK DECNET

To start the network in a batch job (speeds up startup) locate and uncomment the line:

$!$ SUBMIT SYS$MANAGER:STARTNET.COM

So it now appears as:

$ SUBMIT SYS$MANAGER:STARTNET.COM

For information about editing STARTUP-VMS.COM, see Section 8.28.

If you plan to run TCP/IP Services for OpenVMS software, note the following:

You need networking software to download patches and as a requirement for certain layered products. If you are using neither DECnet nor TCP/IP Services for OpenVMS, you should install and configure third-party networking software now. See the appropriate vendors product documentation.

To configure WBEM Services for OpenVMS on a system for the first time, follow these steps:

To configure WBEM Services for OpenVMS on a system where it has been configured previously, follow these steps:

Users of TDC_RT require various privileges, depending on the types of data to be collected. Online help is available when running the collector application and specifies the privileges required to collect each type of data. Enabling the following set of privileges enables collection of all data items: CMKRNL, LOG_IO, NETMBX, PHY_IO, SYSLCK, SYSPRV, WORLD.

Users of the product also require working set quotas (WSQUO) greater than 7000 pagelets.

TDC_RT provides a startup file that should be launched during system startup. The startup file defines several logical names required for use of the product, but the startup file does not actually start the data collector.

$ @SYS$STARTUP:TDC$STARTUP

To directly run TDC$STARTUP.COM, SYSNAM privilege is required.

As of OpenVMS Version 8.2, TDC and TDC_RT use the same naming scheme for image files. A build number is tagged to the image file names. For example, if the version of TDC_RT that ships with your operating system is Version 2.2-60 (where 60 is the build number), then the files that are installed will have names such as TDC$APISHR$I_V842-0060.EXE, where $I denotes HPE Integrity servers), V842 denotes the version of OpenVMS (8.4-2), and 0060 is the build number. The SYS$STARTUP:TDC$STARTUP.COM startup file, which is also identical for both TDC and TDC_RT, uses this build number to determine which image files to use. When a subsequent installation is performed with software that has higher build numbers, the TDC$STARTUP.COM startup file uses the image files with the highest build number appropriate for the current platform.

$ SET COMMAND SYS$COMMON:[TDC]TDC$DCL

Each user can add this SET command to their LOGIN.COM file. However, because elevated privileges are required for most data collection operations, it might not be appropriate to add this command to SYS$MANAGER:SYLOGIN.COM.

$ TDC

For more information about running the application, see the file SYS$COMMON:[TDC]TDC_README.TXT. Release notes are located in the file SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT. See both of these files before running the collector application.

TDC_RT is installed in SYS$COMMON:[TDC] by default. Included are only those files required to run the data collector with the particular operating system version it was distributed with. Once TDC_RT is installed and SYS$STARTUP:TDC$STARTUP.COM has been run on each cluster member, then all cluster members in a single-version, single-architecture OpenVMS Cluster should be able to run the software.

For mixed-version and mixed-architecture clusters, you should obtain and install a complete Performance Data Collector kit (TDC Version 2.2).

The complete kit provides an SDK and run-time environments for all supported OpenVMS configurations. It supports installation on a cluster-wide basis in mixed-version and mixed-architecture OpenVMS Clusters.

For a list of layered products you can install, see the Software Product Descriptions included with your operating system kit. Note that some products require a license key (PAK) from VSI.

Follow these steps:

When modifying system parameters, note the following:

For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the VSI OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.

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 earlier 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 might eventually contain many levels of duplicated parameters. For this reason, you should review MODPARAMS.DAT after each upgrade. This enables you to eliminate any duplication. You can also take this opportunity to modify any parameters, if necessary.

Based on your examination of AUTOGEN's AGEN$PARAMS.REPORT, you might need to modify parameter values in MODPARAMS.DAT.

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

UEFI is the main boot and preboot interface; it is the core interface to the system firmware and console commands on all models. BMC is provided on entry-class HPE Integrity servers (although on a few systems the interface itself is hidden). BMC provides basic management capabilities and access to UEFI. MP (or iLO) is available on most systems. In addition to providing access to UEFI, MP provides advanced management functionality, including remote management, network console with Web-based access, and enhanced diagnostic capabilities. Both BMC and MP (iLO) can operate on standby powereven when the main power switch is turned off.

You can use MP (iLO) or BMC to interact with the capabilities of the UEFI console interface.

The following list briefly describes some of the main features of UEFI, MP, and BMC.

For the complex environments of cell-based servers, a wider variety of tools are provided. Systems with multiple nPartitions provide a separate UEFI interface for each nPartition. MP provides access to, and allows management across, the complex and each nPartition UEFI interface.

In addition to MP and UEFI (cell-based servers do not provide BMC), these systems offer Partition Manager and other tools that vary from system to system and operating system to operating system. The Partition Manager (parmgr) utility provides a graphical interface for managing nPartitions and complex hardware. It centralizes all nPartition management functions in one place, providing the system manager with the tools to dynamically reconfigure, power on, power off, create, delete, and modify nPartitions.

Partition Manager is a free product that can be run on HP-UX or Microsoft Windows™ systems. You can use either of these to manage nPartitions for OpenVMS. Partition

Some versions of the UEFI, MP and BMC console interfaces still interpret the Delete (or Backspace) key as do UNIX systems, which is different from the way OpenVMS or Microsoft Windows™ systems interpret it. Whereas the OpenVMS operating system uses the ASCII DEL/RUBOUT character (7F hexadecimal) to delete the last character typed in a command line, these facilities use Ctrl/H.

When you enter commands for these servers, if you press Delete at a VTxxx terminal (or the key you have mapped to send the DEL/RUBOUT character code in your terminal emulator), the last character typed is not deleted.

You can remap a terminal so that the Delete key removes the last character typed by adding the following DCL command to your login command procedure (generally, LOGIN.COM):

$ SET TERMINAL/BACKSPACE=DELETE