Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home
HP OpenVMS Version 8.3-1H1 for Integrity Servers Upgrade and Installation Manual

Chapter 1 Getting Started

» 

Content starts here

This chapter defines key terms and describes preliminary procedures you must perform before installing or upgrading your OpenVMS system.

NOTE: Throughout this book, examples are taken from OpenVMS I64 installations or upgrades except where stated otherwise. OpenVMS DCL commands are in uppercase, while HP Integrity servers console commands are in lowercase.

1.1 Key Terms

Table 1-1 lists a few key terms you need to know before you install or upgrade the system.

Table 1-1 Definitions of Terms

TermDefinition

HSx device

A self-contained, intelligent, mass storage subsystem that lets computers in an OpenVMS Cluster system environment share disks. The disk on which you install or upgrade the operating system can be connected to one of these systems (for example, an HSV or HSG).

InfoServer

A general-purpose disk storage server. For OpenVMS Alpha systems, the InfoServer may be an independent hardware device or, beginning with OpenVMS Version 8.3, it may be a utility (software application) on an OpenVMS system. On OpenVMS I64 systems, the InfoServer is only available as a software application on an OpenVMS system.

The InfoServer hardware can serve CDs only (it does not support DVDs); thus, this hardware device cannot serve the OpenVMS I64 operating environment (OE) DVD. The InfoServer utility can serve both DVDs and CDs (for OpenVMS I64 and OpenVMS Alpha systems, respectively). The systems connected to the same LAN can use the InfoServer utility to boot the OpenVMS operating system from a virtual drive (instead of the local drive). For more information about the InfoServer utility, see the HP OpenVMS Version 8.3 New Features and Documentation Overview.

local drive

A drive on your computer system, such as a CD, DVD, or disk drive (hard drive), that is connected directly to the computer. If you have a standalone computer, it is likely that all drives connected to the computer system are local drives.

operating system media

The OpenVMS Alpha operating system CD or the OpenVMS for Integrity servers Operating Environment DVD (OE DVD) included with an OpenVMS distribution kit, which contains the OpenVMS operating system and the installation and other procedures described in this manual.

provisioning

Using HP Systems Insight Manager (HP SIM), the process of installing or upgrading OpenVMS on one or more Integrity servers automatically. HP SIM initiates the process and the installation or upgrade automatically continues in the background.

source drive

The drive that holds the operating system media during an upgrade or installation. This can be a local drive or an InfoServer virtual drive. The drive contains the OpenVMS Alpha operating system CD or the OpenVMS for Integrity servers Operating Environment DVD, or a copy of it.

system disk

The disk from which OpenVMS is typically booted. During an installation or upgrade, this is the target disk because it receives files from the source drive. After installation or upgrade, the target drive is booted and becomes the system disk.

target drive

The drive that holds the target system disk during the upgrade or installation. Note: the target drive must be a hard drive, not a CD or DVD.

virtual media (vMedia)

A virtual-disk capability included with Integrated Lights Out (iLO) 2 Management Processor (MP) on Integrity servers. vMedia provides virtual devices that mimic physical hardware devices. For example, it can provide a virtual CD/DVD drive that emulates the DVD drive on a PC and connects over the network to your Integrity server as if it were physically connected. You can use vMedia to install OpenVMS on Integrity servers that do not include a built-in DVD drive or that are physically located elsewhere. vMedia can provide the network service for HP SIM provisioning, or it can be used independently of HP SIM.

 

1.2 Getting to Know Your Integrity Server

The OpenVMS operating system is now supported on a wide variety of HP Integrity servers, including the following:

  • Entry-class servers, which include members of the rx16nn, rx26nn, rx36nn, rx46nn, and rx66nn series and the BladeSystems Integrity BL860c Server Blade

  • Midrange servers, which include members of the rx76nn and rx86nn series

  • High-end servers (Superdome)

For an up-to-date list of servers supported by the current release of OpenVMS, see the HP OpenVMS Alpha Version 8.3 and HP OpenVMS I64 Version 8.3-1H1 Software Product Description (SPD 82.35.xx).

The hardware, firmware, and software supported might vary significantly from system to system. Integrity servers are available in many different configurations. The hardware, utilities, and hardware configuration procedures might differ significantly across models, and even across versions of the same model. This manual provides basic information about the firmware, hardware, and utilities offered on Integrity servers. This information is not meant to replace the hardware documentation. For the most up-to-date and relevant information for your particular model, see the hardware documentation for your Integrity server. The hardware documentation includes model-specific illustrations to guide you. The latest version of documentation for your server can be found online at:

http://docs.hp.com/en/hw.html

http://www.hp.com/support/itaniumservers

For the latest information about firmware, software requirements, and special considerations for your Integrity server, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes.

1.2.1 Entering Commands at Integrity Server Console Interfaces

When entering commands for the Integrity server, if you press Delete on a VTxxx terminal (or press the key you have mapped to send the DEL/RUBOUT character code in your terminal emulator), the last character typed might not be deleted. The firmware on Integrity servers where that unexpected behavior occurs uses Ctrl/H to delete the last character typed. On such Integrity servers, you can remap your terminal to use Ctrl/H instead of DEL/RUBOUT, as described in Section A.1.3.

1.2.2 Integrity Server Tools

Integrity servers include multiple interfaces for working with various aspects of the server or server complex. The Management Processor (MP) is available on most Integrity servers. Many entry-class Integrity servers now come with the Integrated Lights Out (iLO) MP (Integrity iLO 2 MP), which provides a complete remote console experience, including a web-based graphical user interface and the functionality provided by vMedia. MP and Integrity iLO provide a service interface that allows access to all hardware and, in a complex, all nPartitions. The MP is always available, even when the main power source is turned off (MP can operate on standby power). On cell-based servers (such as rx7620, rx8620, and Superdome), MP is available whether or not nPartitions are configured or booted in the server complex. You can navigate from MP to and from the operating system (if it is booted).

The Extensible Firmware Interface (EFI) provides support for operating system loaders and allows you to configure the firmware and control the booting environment. EFI is accessible only when the operating system is not booted. On cell-based servers, each nPartition has a separate EFI console interface. EFI provides support for managing nPartitions. The EFI interface is available from an nPartition console only when the nPartition is in an active state but has not booted an operating system.

You can move from the EFI interface to MP and back again. Similarly, you can move from MP to the operating system and back.

1.2.3 Virtual Connect (VC) on HP BladeSystem c-Class Enclosures

HP Virtual Connect (VC) is a set of interconnect modules and embedded software available for HP BladeSystem c-Class enclosures. VC simplifies the setup and administration of server connections. Where most server interconnect choices come with compromises such as too many cables or too much to manage, VC reduces the number of network cables and simplifies management while adding the unique ability to wire everything once, then add, replace or recover servers in minutes instead of hours or days.

VC is enabled with a choice of Ethernet and Fibre Channel modules designed for the HP BladeSystem. The built-in HP Virtual Connect manager defines a server connection profile for each server bay—even before a server is installed. This profile establishes the Media Access Control (MAC) addresses for all Network Interface Controllers (NICs), the World Wide Names (WWNs) for all Host Bus Adapters (HBAs), and the SAN boot parameters. The profile then holds them constant so that even if the server is changed, the configuration and connection profile stay constant. When a new server takes its place, the same profile is assigned.

For more information about VC, select the Virtual Connect networking link at the following website:

http://www.hp.com/go/bladesystem/virtualconnect

In addition, see the HP Virtual Connect for c-Class BladeSystem User's Guide, available at the following location:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00865618/c00865618.pdf

1.2.4 Cell-Based Server Terminology

A cell-based server—such as the HP rx7620, rx8720, or Superdome server—is a hardware complex that can run one or more operating systems and that supports dividing hardware resources into nPartitions. Thus, it enables you to configure a complex into one large system or into several smaller systems.

All processors and memory are contained in cells, each of which can be assigned for exclusive use by an nPartition. An nPartition defines a subset of the server hardware resources that is used as an independent system environment. An nPartition has its own EFI system boot interface and each nPartition boots and reboots independently. Each nPartition provides both hardware and software isolation so that hardware or software faults in one nPartition do not affect other nPartitions within the same server complex.

By using HP software-based nPartition management tools, you can configure nPartition definitions for a server without physically modifying the server hardware configuration. The main administration tools for nPartitions are the Partition Manager, which provides a graphical interface, and the nPartition Commands, which provides a command-line interface. Versions of these interfaces are provided on HP-UX, Linux®, and Microsoft® Windows® systems. The nPartition Commands tool is also available on Linux systems. MP and EFI can also perform nPartition administrative tasks. Slightly different tool sets and capabilities are available on different server models. For more information, see your hardware documentation. In addition, see the nPartition Administrator's Guide (previously titled HP System Partitions Guide: Administration for nPartitions).

1.2.5 Getting Started: Main Steps After You Unpack Your Integrity Server

When you unpack your Integrity server, the main steps for getting OpenVMS up and running are those listed in Table 1-2. As indicated in the third column, some of the instructions are provided in this manual. However, for the most up-to-date information specific to your Integrity server model and version, always refer to the hardware documentation provided for your Integrity server.

Table 1-2 Getting OpenVMS Started on Integrity Servers

Step

ActionDocumentation

1

Connect your console cable to the serial port; if MP is present on your server, connect to the MP serial port.Section A.2

2

Optionally, configure MP to accept connections over TCP/IP Services for OpenVMS.Hardware manual

3

From the EFI Shell interface or EFI Boot Manager menu, select the device for the OpenVMS console.Section A.2; if you ordered your server preinstalled, console selections are already made but you might need to change them

4

Power on your Integrity server, insert the OpenVMS I64 distribution media (DVD) into the drive, cycle power, and then use the EFI boot menu to boot from the DVD.For how to power on and recycle power, see the hardware documentation; for instructions on booting the DVD, see Section 3.2.1

 

After the initial boot, you need not use EFI to configure boot options. You can configure EFI boot options while OpenVMS is running by using the OpenVMS I64 Boot Manager (SYS$MANAGER:BOOT_OPTIONS.COM), as explained in Section A.5.2. This utility is easier to use than EFI and allows you to configure the most pertinent options for your system. In addition, the OpenVMS installation (and upgrade) procedure can assist you in establishing and validating boot options for your system disk.

1.3 Examining Software and Hardware Components

Before you begin an installation or upgrade, be sure you have all the required hardware and software components, as described in the following sections.

1.3.1 Hardware Components

For hardware components, verify the following::

  • Be sure the hardware is installed and verified for proper operation. For detailed information, see the hardware manuals you received with your computer.

    For initial installations on Integrity servers, your console terminal requires a standard PC-to-PC file transfer cable (also known as a null modem cable; 9-pin female connectors at each end) to connect a PC, laptop, or similar device that includes terminal emulation software; alternatively, you can use a VGA monitor and USB keyboard (and USB mouse). For information about setting up your system console, see Section A.2.

  • Be sure you know how to turn on and operate the components of your system, including the system unit, console, monitor, drives, terminals, and printers. If necessary, read the hardware manuals that came with these components.

  • Make sure you record the installation procedure. You need a transcript if a problem occurs during installation. If you are using terminal emulation software, set the software to log the session. Otherwise, set up your system to record the installation procedure on either a hardcopy terminal or a printer attached to the console terminal. (See your hardware manuals for more details about connecting those components to your system.)

1.3.2 Software Components

For software components, verify the following:

  • Be sure you have all the items listed on the bill of materials contained in the distribution kit. If your distribution kit is incomplete, notify HP Customer Support and request priority shipment of any missing items.

  • Before installing the OpenVMS operating system software, review all cover letters and release notes.

1.3.3 OpenVMS for Integrity Servers Operating Environment DVD

Included in your OpenVMS I64 kit is the OpenVMS for Integrity Servers OE DVD, which you use to install the operating system or to perform operations such as backing up the system disk. The DVD is labeled similar to the following:

DVD label

HP OpenVMS Version 8.3-1H1 for Integrity Servers Operating Environment

Volume label

I640831H1

The DVD label is the printed label on the OE DVD. The volume label is the machine-readable name that the OpenVMS I64 operating system uses to access and identify the DVD.

1.3.4 Firmware on Integrity Server Systems

HP Integrity servers include several firmware components (varying with system type), any of which might need updating. For the minimum versions recommended, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes. HP recommends that you sign up for Subscriber's Choice so that you can automatically receive email notices regarding the latest firmware updates. Make sure you register all your products to receive the appropriate firmware update notices. You can sign up for Subscriber's Choice at the following website:

http://itrc.hp.com

To update entry-class Integrity server firmware, follow the instructions provided in this section; for cell-based servers (midrange and high-end), contact HP Customer Support.

To update your firmware, perform the following steps:

  1. Determine the current firmware versions on your Integrity server (see Section 1.3.4.1).

    NOTE: To receive notification of new firmware releases for the Integrity server you own, you can subscribe (free of charge) for drivers and software alerts, as instructed in Section 1.3.4.1.
  2. Create a firmware update CD on any system equipped with a CD or CD/DVD-recordable drive (see Section 1.3.4.2).

  3. Update the firmware on your Integrity server (see Section 1.3.4.3).

1.3.4.1 Checking Firmware Version

To determine the firmware version in place on your Integrity server, you can use the Extensible Firmware Interface (EFI) info fw command at the EFI Shell prompt, as in the following example. (For cell-based servers, check the firmware at the nPartition console.)

Shell> info fw

You can also use the EFI Boot Manager to obtain firmware information. With MP, you can use the MP sysrev command.

NOTE: The info fw command at the EFI> Shell prompt cannot be used while OpenVMS is running. You can use the MP interface to check firmware on your system while OpenVMS is running.EFI Shell commands are not case sensitive. However, in this manual, EFI and other Integrity server interface commands are displayed in lowercase to help distinguish them from OpenVMS DCL commands.

For more information about the latest firmware for your Integrity server, check the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes. In addition, see the information and resources provided on the HP Support website by following these steps:

  1. Go to the following website:

    http://www.hp.com/support/itaniumservers

  2. Select the appropriate server in the provided list.

    The HP Support page that appears provides a list of tasks and services to choose. To automatically receive drivers and support alerts from HP (free of charge), select “Signup: drivers and support alerts” from the list of services (you might need to select “See more...” to access the signup link), and fill out the forms as instructed.

    For more information about firmware for your Integrity server, select “Download drivers and software” from the list of tasks, and continue with the next step.

  3. On the “Download drivers and software” page, select “Cross operating system (BIOS, Firmware, Diagnostics, etc.)”.

  4. On the resulting page, locate the appropriate firmware (look for the latest update; previous versions might also be listed), and select the link for the firmware in the “Description” column.

  5. Select the “Release Notes” tab and read the information about the latest version of firmware available and the instructions on determining the version of firmware in place on your Integrity server. Compare your installed version with firmware versions listed in the release notes.

1.3.4.2 Creating a Firmware Update CD

To create a firmware update CD for your entry-class Integrity server, you need a CD-recordable drive and software, plus a blank CD-R or CD-RW disk. (For updating firmware on a cell-based server, you must contact HP Customer Support.)

NOTE: The following instructions are for recording a DVD on an OpenVMS system. You can record the DVD on any system or PC, such as a Microsoft Windows computer, a Linux system, or an HP-UX system.
  1. Follow steps 1 through 3 from the preceding section.

  2. Locate the appropriate ISO-image firmware file. (Look for the latest update; previous versions might also be listed along with the latest.) Select the link for that file and read the instructions for the file included in the release notes, and then download the ISO-image firmware (zip-compressed) file to your system. (To access the release notes, see step 5 in the preceding section.)

  3. Unzip the firmware file into the corresponding .ISO file. The .ISO file is a block copy of the firmware disk for the Integrity server system. On OpenVMS systems, you can obtain the INFO-ZIP utility from an OpenVMS Freeware CD and use the UnZip utility provided with INFO-ZIP. OpenVMS Freeware CDs are packaged with the OpenVMS for Integrity Servers OE DVD, and the files on the Freeware CDs are available online at the following website:

    http://www.hp.com/go/openvms/freeware

    The following example shows the command for unzipping an .ISO image of the latest firmware for an rx2600 system (the file name changes with each update of the firmware available on the website):

    $ UNZIP PF_CPEAKSYS0nnn.ZIP
    Archive: SYS$SYSROOT:[SYSMGR]PF_CPEAKSYS0nnn.ZIP
     inflating: PF_CPEAKSYS0nnn.ISO
  4. Record the data on the CD, specifying the .ISO file as the source for the CD. For instructions on doing this, enter the following command:

    $ @SYS$MANAGER:CDRECORD HELP
    NOTE: OpenVMS software includes the CD recording tool CDRECORD. For online help, enter the @SYS$MANAGER:CDRECORD HELP command at the OpenVMS DCL prompt as shown previously. For CDRECORD source files, check the OpenVMS Open Source Tools CD supplied with your OpenVMS I64 OE DVD. For more information about the software, visit the following website:

    http://h71000.www7.hp.com/opensource/opensource.html

1.3.4.3 Updating Your Firmware from the Firmware Update CD

You update the firmware of an entry-class Integrity server from the firmware update CD created in the preceding section. For instructions, see the release notes provided for the firmware you downloaded.

IMPORTANT: To update Integrity server firmware on cell-based servers, contact HP Customer Support.

1.3.5 Device-Naming Conventions

When you perform specific operations, you are asked to specify a device name for the source drive and one for the target drive. When specifying those device names, note the following naming conventions:

  • When the source drive is a local CD or DVD drive, the device name is similar to the following:

    DQA0 (IDE drive) or DNA0 (USB drive)

    For a device name, such as DQA0:, note the following conventions:

    • DQ is the device code.

    • A is the device controller designation.

    • 0 is the unit number of the device.

  • When the target drive is a local disk, the device name is similar to the following:

    DKA0:

  • When the source drive is a virtual DVD drive served by the InfoServer, the device name is typically the following:

    DAD1:

  • On OpenVMS systems configured in certain OpenVMS Cluster or HSx environments, the device naming convention is similar to the following:

    DUA20.14.0.2.0

    The values you specify identify components such as the boot device, controller, unit number of the boot device, HSx controller node number, and channel numbers. Because these values vary depending on your specific hardware configuration, see the owner, operator, and technical service manuals that came with your computer for detailed information.

1.4 Using the Operating System Menu

The following sections describe how to use the operating system menu to install, upgrade, and modify your system disk, and perform other related tasks.

The OpenVMS operating system main menu displays automatically when you boot the OpenVMS operating system from the operating system media (for instructions on how to boot from the operating system media, see Section 3.2). From the menu, you can choose options to perform any of the following tasks:

  • Install or upgrade the operating system from the operating system media.

  • Display a list of products that can be installed from the operating system media.

  • Install or upgrade layered products from the operating system media.

  • Show which products are installed on your system.

  • Reconfigure layered products installed on your system.

  • Remove products.

  • Find, install, and remove patches, and display and remove recovery data.

  • Enter the DCL environment from which you can perform preinstallation or maintenance tasks, such as mounting or showing devices and backing up or restoring files on the system disk.

  • Shut down the system.

The following is a sample display of the OpenVMS main menu:

  OpenVMS I64 Operating System, Version 8.3-1H1

  (c) Copyright 1976-2007 Hewlett-Packard Development Company, L.P.

  Installing required known files...

  Configuring devices... 

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

  You can also execute DCL commands and procedures to perform
  "standalone" tasks, such as backing up the system disk. 
  
  Please choose one of the following:

    1) Upgrade, install or reconfigure OpenVMS I64 Version 8.3-1H1
    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/?)

Review the following sections to understand how the menu works. Then you can choose appropriate menu options when you are asked to do so before, during, and after an installation or upgrade.

1.4.1 Using the Install, Upgrade, or Reconfigure OpenVMS Option (1)

Select option 1 on the operating system main menu to install, upgrade, or reconfigure your OpenVMS software. Selecting option 1 implements a PCSI utility concept called a platform. The OpenVMS platform contains:

NOTE: For use of Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP), and Pay per use (PPU) (supported on cell-based Integrity servers), and for support of such products as gWLM and HP Systems Insight Manager (HP SIM), you must install TCP/IP Services for OpenVMS. SSL for OpenVMS is required and is installed automatically.

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

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

Before installing or upgrading OpenVMS, see the information in the following chapters, as appropriate:

NOTE: Before installing or upgrading OpenVMS on a target drive in an OpenVMS Cluster, make sure the target system disk is not mounted elsewhere in the cluster. The target system disk must be dismounted clusterwide (except on the system from which the installation or upgrade is being performed) and must remain so during the installation or upgrade.

When you select option 1 on the operating system main 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 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] 

1.4.1.1 INITIALIZE Option

When you specify the INITIALIZE option, the following operations take place:

  • All software and data files that already exist on the target disk are removed. The software can only be recovered from a backup of the disk, so make sure that you either have a backup or will not need the data again.

  • The operating system is installed.

Specify the INITIALIZE option and perform a full installation under any of the following conditions:

  • If your computer is new (it has never had any version of any operating system running on it, including factory-installed software).

  • If your computer is already running a version of the OpenVMS operating system and you want to overwrite the entire contents of the system disk (the operating system, application software, and user files).

  • If you want to keep an existing system disk and install OpenVMS on a different disk.

  • If you are running the OpenVMS operating system but cannot upgrade. For example, if you changed the names of system directories on the system disk, the upgrade procedure will not work correctly. Therefore, unless you restore the system disk to its original directory structure, you must reinstall the operating system using the INITIALIZE option.

NOTE: During initialization of an OpenVMS I64 target system disk, the installation process creates a diagnostic partition, visible only at the console prompt. For more information about this partition and options you can take, see Appendix I.

For systems that support the Instant Capacity (iCAP) feature, CPU status (how many cores are available and how much time they have remaining) is not affected by initialization of the system disk. Such information is stored in NVRAM on the Integrity server.

1.4.1.2 PRESERVE Option

When you specify the PRESERVE option, the following operations take place:

IF ...THEN ...

The OpenVMS operating system is not already installed on the target disk

  • The operating system is installed.

  • All other contents of the target disk are retained.

The OpenVMS operating system is installed on the target disk

The operating system is upgraded, as follows:

  • Old operating system files and new files are merged or replaced.

  • All other contents of the target disk are retained.

NOTE: If you intend to choose the PRESERVE option (because there are certain files on the disk that you want to retain), HP recommends that you first make a backup copy of your system disk. If there is any problem during the installation or upgrade that might affect the integrity of the disk, you will have the backup copy as a safeguard.

If you choose the PRESERVE option and choose a target disk that already contains the OpenVMS Version 8.3-1H1 software, you are provided with the option to either reconfigure or reinstall the OpenVMS operating system:

  • Reconfigure the operating system if you want to change the options you chose to include when the operating system was installed.

  • Reinstall the operating system if you think that your system files might have become corrupted.

For additional configuration information, see Section 7.11.

1.4.2 Using the Display Layered Products Option (2)

Use option 2 to display layered products that can be installed.

NOTE: Although option 2 displays any patch kits available from the OpenVMS distribution media, HP recommends using option 7 to display patch kits; option 7 enables you to specify locations to search in addition to the standard location.

When you select option 2 on the operating system main menu, the following information is displayed:

  • The version of OpenVMS and versions of the required components and optional products that can be installed or upgraded when you select option 1 on the main menu.

  • The layered product kits that are available for installation when you select option 3 on the operating system main menu. The DECwindows graphical user interface and HP networking products are shown again, along with other layered products.

NOTE: The two lists of products (the products that can be installed or upgraded and the layered product kits available for installation) might be the same or very similar. Generally, products that can be installed or upgraded along with the OpenVMS operating system should be installed or upgraded with the OpenVMS operating system.

The following is an example of a display. WBEMCIM is the file name used in the PCSI kit for the WBEM Services for OpenVMS product, which is available on OpenVMS I64 systems only. 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 Maintenance Protocol (SNMP). The version numbers in this example do not necessarily reflect the version numbers of the products actually shipped with OpenVMS Version 8.3-1H1.

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

   HP I64VMS VMS version V8.3-1H1
   HP I64VMS AVAIL_MAN_BASE V8.3-1H1
   HP I64VMS CDSA version V2.3-306
   HP I64VMS KERBEROS version V3.1-152
   HP I64VMS SSL V1.3-284
   HP I64VMS TDC_RT version V2.3-1
   HP I64VMS WBEMCIM version V2.61-A070728
   HP I64VMS WBEMPROVIDERS version  V1.5-31   
   HP I64VMS DWMOTIF version V1.6
   HP I64VMS DECNET_PLUS version V8.3-1H1
   HP I64VMS DECNET_PHASE_IV version V8.3-1H1
   HP I64VMS TCPIP version V5.6



     The following Layered Product kits are available on the OpenVMS
     Distribution media (CD/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
   ----------------------------------- ----------- ----------
   HP I64VMS AVAIL_MAN_BASE V8.3-1H1    Full LP    Compressed
   HP I64VMS CDSA V2.3-306              Full LP    Compressed  
   HP I64VMS DECNET_PHASE_IV V8.3-1H1   Full LP    Compressed
   HP I64VMS DECNET_PLUS V8.3-1H1       Full LP    Compressed
   HP I64VMS DWMOTIF V1.6               Full LP    Compressed
   HP I64VMS DWMOTIF_SUPPORT V8.3-1H1   Full LP    Compressed
   HP I64VMS KERBEROS V3.1-152          Full LP    Compressed
   HP I64VMS SSL V1.3-284               Full LP    Compressed
   HP I64VMS TCPIP V5.6                 Full LP    Compressed
   HP I64VMS TDC_RT V2.3-1              Full LP    Compressed
   HP I64VMS WBEMCIM V2.61-A070728      Full LP    Compressed
   HP I64VMS WBEMPROVIDERS V1.5-31      Full LP    Compressed
   ----------------------------------- ----------- ----------

   12 items found

   Press Return to continue...

1.4.3 Using the Install or Upgrade Layered Products Option (3)

Use option 3 on the operating system main menu for normal installations or upgrades of the layered products.

NOTE: Although option 3 installs any patch kits available from the OpenVMS distribution media, HP recommends using option 7 to install patch kits; option 7 enables you to install patch kits that are not located in the standard location. In addition, option 7 saves recovery data; when you use option 7 to remove patch kits, only kits with recovery data are removed.

You can use option 1 to install or upgrade the DECwindows graphical user interface and HP networking products along with the OpenVMS operating system. 

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. Note that any patches that were applied to the product are removed. If you want to reconfigure, select the reconfigure option (5) on the main menu.

As of Version 8.3, most of the software kits included on the OpenVMS distribution media are signed using Secure Delivery. When you use option 3 of the OpenVMS I64 operating system menu, these kits are validated by the PCSI utility. You can install kits created before the secure delivery process was enabled in 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.

NOTE: The layered products listed include the required CDSA, Kerberos, SSL, TDC, Availability Manager, WBEM Services for OpenVMS, and WBEM Providers for OpenVMS. Also included are the optional DECwindows, DECnet Phase IV, DECnet-Plus, and TCP/IP Services for OpenVMS products. Support of such features as Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP), and Pay per use (PPU), and for products such as gWLM and HP SIM, requires TCP/IP Services for OpenVMS. When you use HP SIM to provision OpenVMS on an Integrity server, TCP/IP Services for OpenVMS is installed automatically.

You can install (or upgrade to) the new implementation of TCP/IP Services for OpenVMS (Version 5.6) as part of the OpenVMS upgrade. If you want to install Version 5.6 separately, choose the following product, selecting the appropriate option as in the example that follows.

    HP I64VMS TCPIP V5.6
   ***********************************************************

   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 OpenVMS 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 OpenVMS 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 V82SYS.


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

Choose one or more items from the menu separated by commas: 9
NOTE: When you boot the OpenVMS operating system media and select the option to install layered products, the installation procedure for the selected layered product(s) does not run the Installation Verification Procedure (IVP) for layered products. Because the operating system is booted from the media and the layered products are installed on a different device (the target drive), the IVPs cannot execute correctly. However, you can run the IVP for each layered product after you boot the target system (see the layered product installation documents for information about running the IVP).

1.4.4 Using the Show Installed Products Option (4)

Use option 4 on the operating system main 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 utility’s product database.

The following is a sample display of the prompts and information that appear when you select option 4. WBEM Services for OpenVMS and WBEM Providers for OpenVMS are available on OpenVMS I64 systems only. The version numbers in this example do not necessarily reflect the version numbers of the products actually shipped with OpenVMS Version 8.3-1H1.

   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, V82SYS 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
------------------------------------- ------------ ------------
HP I64VMS AVAIL_MAN_BASE V8.3-1H1     Full LP      Installed
HP I64VMS CDSA V2.3-306               Full LP      Installed
HP I64VMS DECNET_PLUS V8.3-1H1        Full LP      Installed
HP I64VMS DWMOTIF V1.6                Full LP      Installed
HP I64VMS DWMOTIF_SUPPORT V8.3-1H1    Full LP      Installed
HP I64VMS KERBEROS V3.1-152           Full LP      Installed
HP I64VMS OPENVMS V8.3-1H1            Platform     Installed
HP I64VMS TCPIP V5.6                  Full LP      Installed
HP I64VMS VMS V8.3-1H1                Oper System  Installed
HP I64VMS SSL V1.3-284                Full LP      Installed
HP I64VMS TDC_RT V2.3-1               Full LP      Installed
HP I64VMS WBEMCIM V2.61-A070728       Full LP      Installed
HP I64VMS WBEMPROVIDERS V1.5-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
----------------------------------- ----------- ----------- --------------------
HP I64VMS AVAIL_MAN_BASE V8.3-1H1   Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS CDSA V2.3-306             Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS DECNET_PLUS V8.3-1H1      Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS DWMOTIF V1.6              Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS KERBEROS V3.1-152         Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS OPENVMS V8.3-1H1          Platform    Install     25-SEP-2007 18:04:23
HP I64VMS TCPIP V5.6                Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS VMS V8.3-1H1              Oper System Install     25-SEP-2007 18:04:23
HP I64VMS SSL V1.3-284              Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS WBEMCIM V2.61-A070728     Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS WBEMPROVIDERS V1.5-31     Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS TDC_RT V2.3-1             Full LP     Install     25-SEP-2007 18:04:23
HP I64VMS AVAIL_MAN_BASE V8.3       Full LP     Remove      25-SEP-2007 18:04:23
HP I64VMS CDSA V2.2                 Full LP     Remove      25-SEP-2007 18:04:23
HP I64VMS DECNET_PHASE_IV V8.3      Full LP     Remove      25-SEP-2007 18:04:23
HP I64VMS DWMOTIF V1.6              Full LP     Remove      25-SEP-2007 18:04:23
HP I64VMS OPENVMS V8.3              Platform    Remove      25-SEP-2007 18:04:23
HP I64VMS VMS V8.3                  Oper System Remove      25-SEP-2007 18:04:23
HP I64VMS KERBEROS V3               Transition  Remove      25-SEP-2007 18:04:23
HP I64VMS KERBEROS V3               Transition  Reg Product 25-SEP-2007 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...
NOTE: The products listed in the product history vary from system to system, depending on the actual history of the system. For definitions of the kit types, see the HP POLYCENTER Software Installation Utility Developer’s Guide.

1.4.5 Using the Reconfigure Installed Products Option (5)

Use option 5 to reconfigure layered products, including the DECwindows graphical user interface and HP 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:

  • The product is available for installation while your system is booted from the operating system media. For information about displaying products that are available for installation, see Section 1.4.2 (option 2 on the main menu).

  • The product is installed. For information about displaying installed products, see Section 1.4.4 (option 4 on the main menu).

  • The version of the product that is available for installation is the same as the version of the product that is installed.

When you select option 5 on the operating system main 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 OpenVMS Version 8.3-1H1.

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


   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 - HP I64VMS AVAIL_MAN_BASE V8.3-1H1   Layered Product
 2 - HP I64VMS CDSA V2.3-306             Layered Product
 3 - HP I64VMS DECNET_PHASE_IV V8.3-1H1  Layered Product
 4 - HP I64VMS DECNET_PLUS V8.3-1H1      Layered Product
 5 - HP I64VMS DWMOTIF V1.6              Layered Product
 6 - HP I64VMS DWMOTIF_SUPPORT V8.3-1H1  Layered Product
 7 - HP I64VMS KERBEROS V3.1-152         Layered Product
 8 - HP I64VMS SSL V1.3-284              Layered Product
 9 - HP I64VMS TCPIP V5.6                Layered Product  
10 - HP I64VMS TDC_RT V2.3-1             Layered Product
11 - HP I64VMS WBEMCIM V2.61-A070728     Layered Product
12 - HP I64VMS WBEMPROVIDERS V1.5-31     Layered Product
13 - All products listed above
 ? - Help
 E - Exit
 
Choose one or more items from the menu separated by commas:

1.4.6 Using the Remove Installed Products Option (6)

Option 6 allows you to remove products that were installed or registered with the PCSI utility. (This option removes complete products. To remove patches, use option 7, as described in Section 1.4.7.)

IMPORTANT: Do not remove the following system-integrated products (SIPs): Availability Manager, CDSA, Kerberos, SSL, TDC_RT, WBEM Services for OpenVMS (WBEMCIM), and WBEM Providers for OpenVMS. These products are tightly bound with the operating system. Attempts to remove any of these products might not work as expected and can create undesirable side effects.

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 OpenVMS Version 8.3-1H1.

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


   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 KERBEROS V3.1-152         Layered Product
 8 - HP I64VMS SSL V1.3-284              Layered Product
 9 - HP I64VMS TCPIP V5.6                Layered Product  
10 - HP I64VMS TDC_RT V2.3-1             Layered Product
11 - HP I64VMS WBEMCIM V2.61-A070728     Layered Product
12 - HP I64VMS WBEMPROVIDERS V1.5-31     Layered Product
13 - All products listed above 
 ? - Help
 E - Exit
 
Choose one or more items from the menu separated by commas:

1.4.7 Using the Patches and Recovery Data Option (7)

Select option 7 to install or undo patches and to perform related operations. When you select option 7, the following options submenu appears:

  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:

  • When you choose submenu option 1, the following information is displayed:

       NOTE: Some patch kits cannot be correctly installed by this         
             procedure; this includes patch kits for versions of
             OpenVMS prior to V8.3.  Patches for OpenVMS V8.3 and
             later install correctly.  For patches to other products,
             check with the patch kit provider, or install the patch
             from the running system.
    
             Options 2 through 5 (undo, show, delete, and find) will work
             correctly for all patch kits.
  • When you choose submenu option 1, 2, 3, or 4, you are prompted for the target device on which to perform the operation:

       You must enter the device name for the target disk on which
       the operation will be performed.
      
    Enter device name for target disk: (? for choices) [DKB300]

  • When you choose submenu option 1, you are prompted to choose detailed or brief descriptions, as follows:

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

  • For each of the submenu options (1 through 5), you are prompted for the patch kit source. You can specify alternate locations. You can use wildcards when you specify the location. The prompt and introductory information are displayed as follows:

       This procedure will look for patch kits in
       
              SYS$SYSDEVICE:[KITS.*]
    
       If you want to add an additional location, enter the
       device and directory specification and press return.
       Wildcards are allowed. For example:
    
              dka100:[dir1]
              dkb0:[dir1,dir2]
              dka200:[dir1,*]
              dkb300:[dir1...]
    
       Enter the single letter "D" to reset the default location.
    
       If you do not want to add an additional location, just press return
       without entering anything. 
    
    Enter additional location, D, or just press Return:

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.

1.4.8 Using the Execute DCL Option (8)

When you select option 8, you get access to a subset of DCL commands (such as SHOW DEVICE, MOUNT, and BACKUP) to perform specific preinstallation and maintenance operations. Note, however, that this is a restricted DCL environment in that certain DCL commands (such as PRODUCT) and certain utilities (such as VMSINSTAL) do not function as expected because you are booting from read-only or write-locked media, and because a full system startup has not been performed.

A triple dollar sign prompt ($$$) indicates that you are in this restricted DCL environment, as in the following example:

$$$ SHOW DEVICE

To exit the DCL environment and return to the main menu, enter the LOGOUT command.

1.4.9 Using the Shutdown Option (9)

When you select option 9 on the operating system main menu, your system shuts down and you are returned to the console prompt (P00>>> on Integrity servers). The system displays a message similar to the following (this example shows the message from an OpenVMS I64 system):

   Shutting down the system

     SYSTEM SHUTDOWN COMPLETE

**** Primary HALTED with code HWRPB_HALT$K_REMAIN_HALTED

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

1.5 Making the Install/Upgrade/Backup Selection

Now that you have reviewed key terms, examined hardware and software requirements, and learned how to use the menu system included on the OpenVMS operating system media, you can do the following:

IF ...THEN GO TO...

You want to install the operating system in an OpenVMS Cluster environment

Chapter 2, and then Chapter 3. Perform postinstallation tasks described in Chapter 7.

You want to install the operating system in a nonclustered environment

Chapter 3. Perform postinstallation tasks described in Chapter 7.

You want to upgrade the operating system in an OpenVMS Cluster environment

Chapter 4, Chapter 5, and then Chapter 6. Perform postupgrade tasks described in Chapter 7.

You want to upgrade the operating system in a standalone environment

Chapter 4, and then Chapter 6. Perform postupgrade tasks described in Chapter 7.

You want only to back up or restore your system disk

Appendix E.

Printable version
Privacy statement Using this site means you accept its terms
© 2007 Hewlett-Packard Development Company, L.P.