Using the Operating System Menu
» Table of Contents |  | | » Glossary | | | » Index | | |
| | |
| ||
| ||
The following sections describe how to use the operating system menu to install, upgrade, and modify your system disk, and perform other related tasks.
| |
| |
| |
 | NOTE: The OpenVMS Alpha CD and OpenVMS I64 DVD menu options are very similar. This section provides examples from the OpenVMS I64 menu system. |
| |
| |
| |
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 “Booting the OpenVMS Operating System Media”). 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.
Shut down the system.
The following is a sample display of the OpenVMS main menu:
|
|
|
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.
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:
The OpenVMS operating system
The required Kerberos, CDSA, SSL, Performance Data Collector (TDC) (base), and Availability Manager (base) products
The optional DECwindows Motif for OpenVMS, DECnet-Plus, DECnet Phase IV, TCP/IP Services for OpenVMS products and, for OpenVMS I64 only, the WBEM Services for OpenVMS product
| |
| |
| |
| NOTE: For use of Instant Capacity (iCAP) and Pay per use (PPU) features (supported on cell-based Integrity servers), you must install TCP/IP Services for OpenVMS and WBEM Services for OpenVMS on Integrity servers (SSL for OpenVMS is required and installed automatically). In addition, you can use the OpenVMS nPartition Provider to support Instant Capacity (iCAP). |
| |
| |
| |
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:
|
|
|
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 “Alternative Ways to Initialize the System Disk”. 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. With both OpenVMS Alpha and I64 systems, the installation procedure initializes the target disk with volume expansion (INITIALIZE/LIMIT). This renders the disk incompatible with versions of OpenVMS prior to Version 7.2. In most cases, this does not present a problem. However, if you intend to mount the new disk on a version of OpenVMS prior to Version 7.2, you must perform the alternate method of initialization described in Appendix I “Alternative Ways to Initialize the System Disk”. Note that as a result of this alternate method, your new system disk might include a relatively large minimum allocation size (as defined by /CLUSTER_SIZE). Small files will use more space than would be used otherwise. Therefore, perform these steps only for system disks that must be mounted on versions of OpenVMS prior to Version 7.2. |
| |
| |
| |
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 OpenVMS operating system is installed on the target disk | The operating system is upgraded, as follows:
|
| |
| |
| |
| 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 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 “Adding and Removing Operating System Files (Optional)”.
Use option 2 to display layered products that can be installed. Although this option 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.
The following is an example of a display. In this 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).
|
|
|
Use option 3 on the operating system main menu for normal installations or upgrades of the layered products.
Although this option 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 located elsewhere than 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.
Note that you can install or upgrade the DECwindows graphical user interface and HP networking products along with the OpenVMS operating system by selecting option 1 on the main menu.
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. When you use option 3 from the OpenVMS Alpha operating system menu, these kits are not validated; this restriction is due to the CD’s space limitations. 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, 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. (This particular example includes notes about installing DECwindows Motif and DECnet.)
| ||||
| | |||
| ||||
| NOTE: The layered products listed include CDSA, Kerberos,
SSL, TDC, and Availability Manager, which are required, and DECwindows,
DECnet Phase IV, DECnet-Plus, TCP/IP Services for OpenVMS, and WBEM
Services for OpenVMS, which are optional. WBEM Services for OpenVMS
is available on OpenVMS I64 systems only. Support of Instant Capacity
(iCAP), Temporary Instant Capacity (TiCAP), and Pay per use (PPU)
requires that WBEM Services for OpenVMS be installed as well as
TCP/IP Services for OpenVMS. (SSL for OpenVMS is required and 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 (option 5 in the example that follows):
| |||
| ||||
| | |||
| ||||
|
|
|
| |
| |
| |
| NOTE: When you boot the OpenVMS operating system media and select the option to install layered products, that installation procedure 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). |
| |
| |
| |
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 is available on OpenVMS I64 systems only.
|
|
|
| |
| |
| |
| 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. |
| |
| |
| |
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 “Using the Display Layered Products Option (2)” (option 2 on the main menu).
The product is installed. For information about displaying installed products, see “Using the Show Installed Products Option (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:
|
|
|
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 “Using the Patches and Recovery Data Option (7)”.)
| |
| |
| |
 | IMPORTANT: Do not remove the SIPs: Availability Manager, CDSA, Kerberos, SSL, and TDC_RT. These products are tightly bound with the operating system. Attempts to remove any of these products do not work cleanly and can create undesirable side effects. |
| |
| |
| |
| |
| |
| |
| NOTE: When you remove a product that was registered using a transition kit (in other words, a product that has been installed using VMSINSTAL or some method other than PCSI), some of the product’s directories, files, or other objects are not removed. Transition kits typically do not contain all the directories, files, and other objects that make up the product. |
| |
| |
| |
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:
|
|
|
Select option 7 to install or undo patches and to perform related operations. When you select option 7, the following options submenu appears:
|
|
|
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 the operation will be performed:
You must enter the device name for the target disk on which
the operation will be performed.
Enter device name for target disk: [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 additional patch kit location (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.
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:
|
|
|
To exit the DCL environment and return to the main menu, enter the LOGOUT command.
When you select option 9 on the operating system main menu, your system shuts down and you are returned to the console prompt (>>> on Alpha systems; P00>>> on Integrity servers). The system displays a message similar to the following (this examples shows the message from an OpenVMS I64 system):
|
|
|