 |
» |
|
|
|
This chapter explains how to upgrade the OpenVMS
operating system from a local CD or DVD drive and includes information
about reinstalling or reconfiguring your system. This chapter is organized into sections that describe
the major tasks for upgrading OpenVMS, in the order in which these
tasks must be performed. Section 6.1 includes a checklist that you can use to
make sure you perform all the upgrade tasks described in this chapter. Use the checklist in Table 6-1 to ensure that you perform all necessary upgrade
tasks. Table 6-1 Upgrade Checklist | | Task | Section |
|---|
| Boot the OpenVMS operating
system media. | Section 6.2.1 | | Use option 1 of the operating
system menu to upgrade your OpenVMS operating system, respond to the
prompts, and shut down the system when the upgrade completes. | Section 6.3, Section 6.4 | | If you did not allow the
upgrade procedure to create a boot option for your upgraded system
disk, add a boot option now, if desired. | Section A.5.2 | | Reboot your system. (The
steps vary according to the type of upgrade you are performing.) | Section 6.5 | | Perform postupgrade tasks,
as necessary. | Chapter 7 |
The OpenVMS operating system includes procedures that
allow you to easily upgrade the operating system using the PCSI utility. These tools are available once you boot the system properly. You can use a VGA graphics device, serial device, or
network interface for the console. For information about
configuring your system console, see Section A.2. | | | |  | NOTE: When
using a VGA console and upgrading from vMedia or a USB DVD drive with
the keyboard plugged into a USB hub, if the keyboard is not responding,
simply unplug the hub and plug it back in. | | | | |
6.2.1 Booting the OpenVMS I64 OE DVD | |
You can boot the OpenVMS
I64 OE DVD in any of the following ways. This section gives detailed
instructions on booting from the local DVD drive. Detailed instructions
on the other methods are available in the appendixes, as noted in
the corresponding sections that follow. From your local DVD drive
(Section 6.2.1.1) From a virtual DVD drive
served over the network by the InfoServer utility (Section 6.2.1.2) From an image on a PC
or Windows server in the network accessed through the HP SIM interface
(Section 6.2.1.3) From an image on a PC
or Windows server in the network using vMedia through a browser connected
to your Integrity server iLO 2 MP port (Section 6.2.1.4)
The latter two options can be used for entry-class
Integrity servers that support such means; they can be used when a
local DVD drive is not available. For more information about booting
operations, see Section A.6. 6.2.1.1 Booting from the Local DriveTo boot a local OpenVMS I64 OE DVD, follow these
steps. To boot the DVD on a cell-based server, a DVD device must
be accessible by the nPartition that OpenVMS is being installed on. Make
sure your Integrity server is powered on. If your system has an attached
external device, make sure it is turned on and operational. Insert
the DVD into the drive you want to use. Cycle
power. From
the main EFI boot menu (for cell-based servers, this must be the EFI
boot menu for the nPartition on which OpenVMS is to be booted), select
the appropriate item from the boot options list. Note that the EFI
boot menu is timed; press any key to stop the countdown timer. For some systems, the boot option to select is
the Internal Bootable DVD option. If that option is not listed in
your EFI boot menu, move to the Boot From a File menu and select the
Removable Media Boot option, if present. Alternatively (and this method is recommended
for cell-based servers), boot the DVD drive from the EFI Shell prompt
by entering the command shown in the following example, where fsn: corresponds to the Integrity server DVD drive (such
as fs0:). Note that if you have navigated to a particular file system,
the EFI Shell prompt would reflect that file system; for example,
if the current file system is fs0:, the EFI Shell prompt would be
fs0:>. Shell> fsn:\efi\boot\bootia64.efi |
To determine which device is the bootable DVD
drive, examine the list of mapped devices and look for an fs device
listing that includes the letters “CDROM”, as in the
following line, where fsn is the file system
associated with the drive, which is usually fs0: (instead of "fsn", you might see something similar to "V8.3-1H1"; instead
of Ata, you might see Scsi, depending on the server model): fsn : Acpi(HWP0002,400)/Pci(4|1)/Ata(Primary,Master)/CDROM(Entry0) You can use the following command to display the
mapping of various EFI device names to OpenVMS device names, where
fsn is the device you want to check (such as
fs0:): Shell> fsn:\efi\vms\ms_show dev -fs |
On most Integrity servers, the DVD drive is DQA0: (IDE) or DNA0: (USB). On systems that include a SCSI
bus, such as the Superdome server, the DVD drive is DKA0:. For more
information about the vms_show command, see the HP OpenVMS System Management Utilities Reference Manual.
| | | | | NOTE: By default, certain versions of EFI might interpret the Delete (or Backspace) key differently than
do OpenVMS Alpha systems or Microsoft Windows computers. In such cases,
press Ctrl/H to delete the last
character entered. For more information, see Section A.1.3. | | | | |
When the DVD boots properly, the OpenVMS operating
system banner appears, followed by the operating system menu. You
can now upgrade your OpenVMS I64 operating system on the target disk
(see Section 6.3).
If the methods documented in this section do not succeed in booting
the DVD, see Section A.6.2.1. | | | | | NOTE: When booting OpenVMS from the installation DVD for the first
time on any OpenVMS I64 system with a SAN storage device, you might
experience a delay in EFI initialization because the entire SAN is
scanned. Depending on the size of the SAN, this delay might range
from several seconds to several minutes. | | | | |
6.2.1.2 Booting Over the Network Using the InfoServer UtilityTo use the InfoServer utility to boot from the network,
certain configuration steps are required initially (one time only);
see Appendix B. The instructions
on booting over the network from a virtual DVD drive are also included
in Appendix B. 6.2.1.3 Booting Using HP SIM ProvisioningTo use HP SIM provisioning to boot an image
of the OpenVMS OE DVD, certain configuration steps are required initially
(one time only). For these steps and the booting instructions, see Appendix C. For upgrades, your
OpenVMS boot flags must be set to (0,0). 6.2.1.4 Booting Using vMediaTo use vMedia to boot an image of the OpenVMS OE DVD, certain configuration
steps are required initially (one time only); see Section C.1.4. For instructions
on booting with vMedia, see Section C.2. The following sections describe how to upgrade
from the operating system media. 6.3.1 Upgrading the System Using Option 1 of the Operating System
Menu | |
After
you boot the operating system DVD (OpenVMS I64 OE DVD), the HP copyright banner
and several messages appear, followed eventually by the operating
system main menu. Choose the upgrade option (1) on the menu, as in
the following example: |
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/?) 1
|
6.3.2 Choosing INITIALIZE or PRESERVE | |
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, press Enter (or Return) to accept the default (PRESERVE). 6.3.3 Specifying the Target Disk | |
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 and respond
to the prompt. For example: 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. For example, if you enter
MKA500, a tape device, a message similar to the following is displayed: MKA500 is not a disk device |
| | | |  | CAUTION: If the selected target disk includes .EXE or .COM
files installed by a previous upgrade or installation in one or more
system-specific root directories in SYS$COMMON, the upgrade procedure
tells you that when you boot from a root that contains any of these
files, they are used instead of the files provided by the newer version
of OpenVMS. This can make the upgraded system unbootable or cause
errors after booting. Unless an HP representative has advised you
to keep one or more of these files where they are, you must delete,
rename, or move these files from the system-specific root directory.
The procedure lists the names and locations of these files. Record
these if you are not using a hardcopy terminal. The procedure gives
you the option of terminating the upgrade so that you can do what
is necessary for these files: select option 8 (“Execute DCL
commands and procedures”) on the OpenVMS main menu and enter
the appropriate DCL commands. | | | | |
6.3.4 Selecting Reinstallation and Reconfiguration Options | |
If you are using the OpenVMS Version 8.3-1H1 operating
system media and you selected a target disk that already has Version
8.3-1H1 installed, you are presented with several configuration options.
A sample display follows. See also the example in Section 7.11. Version 8.3-1H1 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 main menu.
If you want to change your choices about which options you included
for any of the products you installed along with the OpenVMS operating
system installation, choose "Reconfigure installed products" (option 5)
from the main menu. |
|
Next the menu is redisplayed: Please choose one of the following:
1) Reconfigure the OpenVMS platform.
2) Reconfigure the OpenVMS operating system.
3) Reinstall the OpenVMS operating system.
4) Return to the Main Menu (abort the upgrade/installation).
Enter choice or ? for help: (1/2/3/4/?) |
For additional configuration information, see Section 7.11. 6.3.5 Checking for Recovery Data | |
If 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. Use the PRODUCT UNDO PATCH command to remove the patches
and kits. The upgrade procedure now checks the disk for
recovery data saved by the PCSI utility. Any recovery data must be
removed before the upgrade can continue because this data becomes
invalid after the upgrade. If no recovery data is present, the upgrade
continues. If recovery data is present and all the data found applies
only to the OpenVMS operating system, the upgrade procedure deletes
the data and continues. (The procedure does not display the deletion
of the files because 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-2007 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. |
6.3.6 Specifying the Volume Label | |
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 you specified and asks whether
you want to keep that label. As shown in the following example, if
you choose not to keep the label, you are prompted for a new label.
The OpenVMS operating system uses the volume label to identify and
reference the disk. Make sure the label you use is unique; problems
occur if the same label is used by different disk volumes. DKB400: is now labeled I64SYS. |
Do you want to keep this label? (Yes/No) [Yes] NO
Enter volume label for target system disk: [I64SYS] I640831H1 |
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). 6.3.7 Specifying the On-Disk Structure Level | |
If the target disk is currently initialized with
On-Disk Structure Level 2 (ODS-2), the procedure informs you and gives
you the option to convert the disk to On-Disk Structure Level 5 (ODS-5),
as in the following example. If the target disk is currently initialized
with ODS-5, the upgrade continues without displaying information about
the disk structure. You are not asked whether to convert the
system disk's structure or whether to enable hard links. | | | | | NOTE: If your disk was initialized with ODS-5, and hard links was
not enabled but now you want to enable hard links, you can enable
them prior to the upgrade by using the following commands as shown:$ SET VOLUME/VOLUME_CHARACTERISTICS=HARD_LINKS 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 HP OpenVMS System Management Utilities Reference Manual: A-L. A brief summary of ODS-2 and ODS-5 file systems
follows; for more information, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. ODS-2 ODS-2 allows for compatibility with
OpenVMS VAX and Alpha systems that use ODS-2 disks (as well as OpenVMS
I64 systems using ODS-2 disks). Choose ODS-2 if you do not need the
new features of ODS-5 disks, including the support of applications
ported from other operating systems (such as UNIX, Linux, and MS Windows)
available with ODS-5 disks. ODS-5 ODS-5 supports file names that are longer and have
a wider range of legal characters. This feature permits use of file
names similar to those in a Windows or UNIX environment. ODS-5 supports hard links to files, access dates,
and files whose names differ only by case. ODS-5 volumes cannot be mounted on any version of
OpenVMS prior to Version 7.2. Systems running OpenVMS VAX Version 7.2 and higher
can mount ODS-5 volumes but cannot create or access files that have
extended names. (On OpenVMS VAX systems, lowercase file name characters
are seen in uppercase.)
If you choose not to change to ODS-5, the upgrade
continues and the target disk is mounted. For example: Do you want to convert the target system disk to ODS-5? (Yes/No/?) NO
...OpenVMS 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 HP 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:. |
6.3.8 Choosing Whether to Allow the Procedure to Create and Validate
Boot Options | |
On OpenVMS I64 upgrades, the procedure next asks
whether you want to create or validate boot options. Boot options in the EFI 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 your system disk will normally be booted on
this system and this device, and if you want the upgrade procedure
to assist you in setting up or validating boot options on the EFI
console in the EFI Boot Manager menu, answer YES. The procedure creates
and validates a new boot option if one does not exist, or it validates
existing boot options, just before the upgrade completes. (See Section 6.4.7.) If you answer YES and no boot option exists, the
procedure allows you to set OpenVMS boot flags (VMS_FLAGS), as shown
in the following example. Enter the OpenVMS flags (for example, 0,1),
or press Enter to set no flags (the default). If
a boot option exists, you can change boot flags after the upgrade
completes (for information about changing boot flags, see Section A.5.2). You can set VMS_FLAGS or accept the default, 0,0.
Enter the value for VMS_FLAGS: (n.n) [0,0] |
If you do not want the procedure to assist you
in setting up or validating boot options on the EFI console, answer
NO. HP recommends that you allow the procedure to
assist you in setting up and validating boot options. 6.3.9 Warning About Removal of the DECRAM Command | |
When upgrading from versions of OpenVMS prior
to 8.3, the procedure displays a message similar to the following
that warns you that the DCL command DECRAM is being removed to prevent
conflict with the DECRYPT command: Beginning with OpenVMS V8.3, the DCL commands ENCRYPT and DECRYPT
are provided as part of OpenVMS.
Because "DECRYPT" conflicts with the existing command "DECRAM",
this upgrade will remove the DECRAM command.
If you use the command DECRAM interactively or in command
procedures, please see the release notes for more information. |
The DECRYPT command
(introduced with OpenVMS Version 8.3) overwrites the default definition
of DECR, which you might have been using to run DECram. You should
update any command procedures that use the DECRAM command so that
they use the foreign command style of DCL to run DECram: This change affects only the use of the DCL command;
all other aspects of the DECram product remain the same. 6.3.10 Setting OpenVMS Cluster Membership Information | |
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) |
Unlike an installation, answering YES to this
question does not cause 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 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 Guidelines for OpenVMS Cluster Configurations. 6.3.11 Updating Time Zone Information | |
For local time zone support to work correctly,
the time zone that accurately describes the location you want to be
considered as your default time zone must be set. In addition, your
system must be 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 3.3.3. For more information about TDF and local time
zone support, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. 6.3.12 Upgrading Windowing, Networking, and Related Products | |
The procedure now presents information about the
optional DECwindows GUI (DECwindows Motif for OpenVMS) and networking
(DECnet and TCP/IP) products that will be upgraded along with the
OpenVMS operating system. As noted by the procedure, you can change
the default values for these products later in the installation procedure. | | | | | NOTE: The following display shows what you might see during an OpenVMS
I64 installation. Some of the products listed are supported on OpenVMS
I64 systems only. | | | | |
|
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 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 HP 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.
DECwindows Motif for OpenVMS I64 V1.6
is installed on your system. An upgrade is not required.
Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. HP 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.3-1H1? (Yes/No) [Yes]
HP 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. |
|
| | | | | NOTE: Beginning with OpenVMS Version 8.3, DECwindows
client files are made available through the DWMOTIF_SUPPORT kit.
(Prior to Version 8.3, the client files were included directly with
the OpenVMS operating system kit.) The OpenVMS installation procedure
installs this kit automatically. The DWMOTIF_SUPPORT kit name is
listed during the installation. | | | | |
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.3-1H1. 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.3-1H1.
If you choose to keep the currently installed version, you should
verify what level of support for this version is available from HP. Some windowing and networking products might have
versions installed that do not work on OpenVMS Version 8.3-1H1.
In this case, you are not given a choice to upgrade—the software
is upgraded automatically. | | | | | NOTE: For support of Instant Capacity (iCAP) and Pay
per use (PPU) functionality (supported on cell-based Integrity servers), and for support of such products as gWLM and HP SIM, install
TCP/IP Services for OpenVMS. When you provision OpenVMS on Integrity
servers, TCP/IP Services for OpenVMS is installed automatically. | | | | |
The following sections describe the remaining
steps that you need to perform to complete the upgrade. 6.4.1 Choosing Descriptive Help Text | |
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. 6.4.2 Removing Older Versions of ENCRYPT | |
Beginning with OpenVMS Version 8.3, Encryption
for OpenVMS is included with the operating system. If an older version
of ENCRYPT (HP I64VMS ENCRYPT) is found on your system, the upgrade procedure removes
the product. Confirmation of the removal of the ENCRYPT product is
displayed, as in the following example: HP I64VMS ENCRYPT will now be removed.
This is required because OpenVMS now includes ENCRYPT.
The following product has been selected:
HP I64VMS ENCRYPT V1.6 Layered Product
The following product will be removed from destination:
HP I64VMS ENCRYPT V1.6 DISK$I640831H1:[VMS$COMMON.]
Portion done: 0%...20%...30%...40%...50%...60%...70%...80%...90%...100%
The following product has been removed:
HP I64VMS ENCRYPT V1.6 Layered Product |
6.4.3 Secure Delivery Validation | |
As of Version 8.3, most 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 (HP, in this
case) 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 OpenVMS I64 from the distribution
media, the procedure validates any PCSI kits that are being installed.
For each kit successfully validated, you see a message similar to
the following: Performing product kit validation of signed kits...
%PCSI-I-VALPASSED, validation of
DKB400:[KITS.CDSA]HP-I64VMS-CDSA-Vnnnn-nnn-n.PCSI$COMPRESSED;1 succeeded
.
.
. |
Signed PCSI kits that are installed subsequent to the initial boot
of the OpenVMS kit (including signed kits on the distribution media)
are validated. In addition, the DCL command
PRODUCT SHOW HISTORY displays the validation status of installed products. 6.4.5 Selecting Product Component Options | |
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:
HP I64VMS OPENVMS V8.3-1H1 Platform (product suite)
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
HP I64VMS OPENVMS V8.3-1H1: OPENVMS and related products Platform
COPYRIGHT 1976, 30-Aug-2007
Hewlett-Packard Development Company, L.P.
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: If you accept the default
values, you receive the same components that you selected when you
last installed or upgraded the system (instead of all the components currently available) plus any new components that
were not in the previous version of the OpenVMS operating system. If you want to include
or exclude any components differently than you did in the last installation
or upgrade, you must answer NO and then respond to the prompts for each option, even those that you are not changing. If you want to review
the current defaults first, answer NO. Then answer YES when the procedure
asks whether you want to view the values. If you review the defaults and are satisfied, answer YES to the prompt
asking whether you are satisfied with the values. If you want to
make changes, answer NO to that question and then answer YES when
the procedure asks whether you want to reenter the values.
When you select component options, also note the
following: Whether you choose all
the default values or select individual files, the procedure allows
you to view your selections and make changes. If you are not sure whether
you want certain component options, you can request help by entering
a question mark (?) at the prompt for that component (or group of
components). You should review the
list of options and compare them with the requirements for your procedure.
If you are selecting components individually, be sure that you include
all components necessary to support the needs of your users. Note
also that certain components depend upon the installation of other
components. OpenVMS Management Station
software is installed automatically on your OpenVMS system disk when
you accept all the default values. If you do not accept the default
values, you must select the OpenVMS Management Station component (server
and client files) if you plan to use that product. After the upgrade
is complete, you can then prepare your OpenVMS system and your PC
to run OpenVMS Management Station by following the procedures described
in Appendix G. If you decide after the
upgrade to change which OpenVMS operating system components you want
installed on your system, you must reconfigure the installation as
described in Section 7.11. After you boot the upgraded
system disk and log in, you can obtain information about individual
system files by entering HELP SYSTEM_FILES at the dollar sign prompt
($).
| | | | | NOTE: Unless you have specific reasons to do otherwise,
HP recommends that you accept the defaults and install all OpenVMS
options. OpenVMS and layered products have various dependencies on
many of these options. Even if you think you do not need certain
options, some OpenVMS or layered product operations might not work
correctly if other OpenVMS options are not installed. | | | | |
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
WBEM Services for OpenVMS (WBEMCIM)
WBEM Providers for OpenVMS (WBEMPROVIDERS) |
For a list of component options included with
the OpenVMS Version 8.3-1H1 operating system, see Example 3-1. 6.4.6 Component and Product Installation Confirmation Messages | |
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:
HP I64VMS CDSA V2.3-306 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS DECNET_PLUS V8.3-1H1 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS KERBEROS V3.1-152 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS OPENVMS V8.3-1H1 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS VMS V8.3-1H1 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS WBEMCIM V2.61-A070728 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS WBEMPROVIDERS V1.5-31 DISK$I640831H1:[VMS$COMMON.]
The following products will be removed from destinations:
HP I64VMS CDSA V2.2 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS DECNET_PLUS V8.3 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS KERBEROS V3.0 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS OPENVMS V8.3 DISK$I640831H1:[VMS$COMMON.]
HP I64VMS VMS V8.3 DISK$I640831H1:[VMS$COMMON.]
Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%
The following products have been installed:
HP I64VMS CDSA V2.3-306 Layered Product
HP I64VMS DECNET_PLUS V8.3-1H1 Layered Product
HP I64VMS KERBEROS V3.1-152 Layered Product
HP I64VMS OPENVMS V8.3-1H1 Platform (product suite)
HP I64VMS VMS V8.3-1H1 Operating System
HP I64VMS WBEMCIM V2.61-A070728........Layered Product
HP I64VMS WBEMPROVIDERS V1.5-31........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
HP I64VMS OPENVMS V8.3-1H1: OPENVMS and related products Platform
HP 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 cofniguration 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
Press RETURN to continue:
|
|
6.4.7 Upgrade Creates and Validates Boot Options | |
At this point in an OpenVMS I64 upgrade, the procedure
creates and validates boot options if you chose to have the procedure
do so (see Section 6.3.8). If you answered NO , the following message is displayed If there is an existing boot option that was used to boot this
system disk, you may be able to use it. Otherwise, you will have
to use the EFI Shell the first time that you boot the newly
installed system. After booting, use the OpenVMS I64 Boot Manager
to create a Boot Option. To do this log in to a privileged
account and execute this command:
$ @SYS$MANAGER:BOOT_OPTIONS |
The procedure then informs you that the upgrade is complete
and prompts you to press Return (Enter) to continue, at which point it returns you to the OpenVMS main
menu. You can select option 8 (“Execute DCL commands and procedures”) on the OpenVMS main menu and enter the command at the DCL triple
dollar sign prompt ($$$) to start the OpenVMS I64 Boot Manager utility. If you answered YES, the procedure determines whether
a boot entry already exists for the system disk (in this example,
DKB400:): If an entry is found, a message similar to the following is displayed: The EFI Boot Manager menu includes the following boot option(s)
for DKB400:
Validate EFI Boot Options list: Timeout = 0 secs.
----------------------------------------------------------------------
1 DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) "OpenVMS on DKB400: PKA0.1"
----------------------------------------------------------------------
1 entries found. |
In this example,
one boot option is found. If multiple entries are found and if they
are all SCSI devices, the procedure displays the following message
and then notifies you that the upgrade is complete:
The EFI Boot Manager menu includes multiple Boot Options for $1$DGA1200:
Boot Options cannot be created or validated automatically.
Please use the OpenVMS I64 Boot Manager to ensure that you
have a valid boot option for the system you have just installed. |
When one entry is found, or when multiple Fibre Channel entries
are found, the procedure validates the boot options, as in the following
example, in which the found entry fails to boot and is then fixed
and validated: Validate EFI Boot Options list: Timeout = 0 secs.
-------------------------------------------------------------------
1 DKB400: PKA0.1
DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0)
efi$bcfg: Option Failed. Fixing Boot Entry automatically.
efi$bcfg: Entry 1 Boot0001 removed.
efi$bcfg: DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) (Boot0001) Option
successfully added
-----------------------------------------------------------------------
1 entries validated. |
If no existing entry is found, a boot option is created and the procedure displays validation
text as in the following example: efi$bcfg: DKB400: (Boot0003) Option successfully added
The Boot Option is called OpenVMS on DKB400:;
it is the first entry in the Boot Options menu, and is
configured (by default) to boot from SYS0.
VMS_FLAGS are set to -fl 0,0 |
6.4.8 Upgrade Completes and Returns to OpenVMS Operating System Menu | |
The upgrade procedure is now complete. The procedure
displays information about the special startup procedure that runs
when the newly installed system is first booted. It then prompts
you to press Return (Enter) to continue.
After you do so, you are returned to the OpenVMS operating system
menu. The following is a sample display: |
The upgrade is now complete.
When the newly upgraded system is first booted, a special
startup procedure will be run. This procedure will:
o Run AUTOGEN to set system parameters.
o Reboot the system with the newly set parameters.
You may shut down now or continue with other operations.
Process I64VMS_INSTALL logged out at 25-JUL-2007 14:45:49.54
Press Return to continue...
****************************************************************
You can install or upgrade the OpenVMS I64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS I64 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/?) |
|
6.4.9 Shutting Down the System | |
Unless you want to perform any other operations
prior to booting the upgraded disk, shut the system down by choosing
the shutdown option (9) on the menu: Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 9
Shutting down the system
.
.
.
SYSTEM SHUTDOWN COMPLETE |
After an OpenVMS I64 system shuts down, you can use the
OpenVMS I64 Boot Manager utility to add and validate a boot option
for the newly upgraded system disk, and then boot the newly upgraded
system disk. AUTOGEN runs 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 7 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. |
Printable version
