The following sections describe the remaining
steps that you need to perform to complete the upgrade.
6.4.1 Selecting 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 or HP AXPVMS
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$I64084:[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 Integrity servers
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:
Prior to Version 8.4:
Performing product kit validation of signed kits...%PCSI-I-HPCVALPASSED, validation of
DKB400:[KITS.CDSA]HP-I64VMS-CDSA-Vnnnn-nnn-n.PCSI$COMPRESSED;1 succeeded
.
.
.
Note that because of
limitations in the OpenVMS Alpha CD boot environment, OpenVMS Alpha
kits are not validated when booted from it. On both OpenVMS Alpha
and Integrity server systems, signedPCSI kits that are installed subsequent to
the initial boot of the OpenVMS CD/DVD (including signed kits on the
distribution media) are validated. In addition, on both OpenVMS Alpha and OpenVMS Integrity server
systems, the DCL command PRODUCT SHOW HISTORY displays the
validation status of installed products.
6.4.4 Saving Archived Files
By default, the OpenVMS upgrade deletes files
that were archived as filename.type_OLD by OpenVMS
remedial kits. If you do not want to delete these files, you can
save them by performing one of the following actions:
When the script asks whether
you want the defaults for all options, answer NO. (This script is
shown in the example in Section 6.4.5.) Step through the options and answer
NO to the option for deleting files archived by remedial kits. This
action saves all such files.
Before beginning the upgrade,
rename any _OLD files that you want to save. Files that you do not
rename are deleted.
Note that the upgrade does not delete all files
with a file extension ending in _OLD. Rather, it deletes only those
_OLD files that were archived by OpenVMS remedial kits.
NOTE: OpenVMS patches save these _OLD files in VMS$REMEDIAL_OLD_FILES.TXT
in the SYS$UPDATE directory. All files listed in this file are supposed
to have _OLD appended to their names; however, some patch kits add
the files without this extension. If the upgrade procedure detects
files without _OLD appended, it displays a message similar to the
following:
%UPGRADE-I-FIXUP, appending _OLD to file names in
PCSI$DESTINATION:[SYSUPD] VMS$REMEDIAL_OLD_FILES.TXT
[SYSUPD]VMSKITBLD.DAT
[SYSHLP]XFC$SDA.HLP
[SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE-OLD
[SYS$LDR]SYS$XFCACHE.DSF
[SYS$LDR]SHELL9K.EXE_STB
[000000]HP-I64VMS-VMS-V0820-1-2.PCSI$DESCRIPTION
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.4 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.4: OPENVMS and related products Platform
COPYRIGHT 1976 ...
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 H.
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.12.
After you boot the upgraded
system disk and log in, you can obtain information about individual
system files by entering HELP SYS_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
HP Binary Checker 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.4 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.
NOTE: If you perform two installations at the same time to OpenVMS
Alpha systems connected via MEMORY CHANNEL, you might see a message
similar to the following every 5 seconds:
%PMA0 CPU00: 30-AUG-2004 14:58:40 Remote System Conflicts with
Known System - REMOTE NODE
%PMA0 CPU00: 30-AUG-2004 14:58:45 Remote System Conflicts with
Known System - REMOTE NODE
Disregard the message. The installation or upgrade will proceed
normally and the messages will not be present when the system reboots
with its real node name. The version numbers in this example do not
necessarily reflect the version numbers of the products actually shipped
with OpenVMS Version 8.4.
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$I64084:[VMS$COMMON.]
HP I64VMS DECNET_PLUS V8.4 DISK$I64084:[VMS$COMMON.]
HP I64VMS HPBINARYCHECKER V1.0 DISK$I64084:[VMS$COMMON.]
HP I64VMS KERBEROS V3.1-152 DISK$I64084:[VMS$COMMON.]
HP I64VMS OPENVMS V8.4 DISK$I64084:[VMS$COMMON.]
HP I64VMS VMS V8.4 DISK$I64084:[VMS$COMMON.]
HP I64VMS WBEMCIM V2.91-A070728 DISK$I64084:[VMS$COMMON.]
HP I64VMS WBEMPROVIDERS V2.0-31 DISK$I64084:[VMS$COMMON.]
The following products will be removed from destinations:
HP I64VMS CDSA V2.2 DISK$I64084:[VMS$COMMON.]
HP I64VMS DECNET_PLUS V8.3 DISK$I64084:[VMS$COMMON.]
HP I64VMS KERBEROS V3.0 DISK$I64084:[VMS$COMMON.]
HP I64VMS OPENVMS V8.3 DISK$I64084:[VMS$COMMON.]
HP I64VMS VMS V8.3 DISK$I64084:[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.4 Layered Product
HP I64VMS HPBINARYCHECKER V1.0 Layered Product
HP I64VMS KERBEROS V3.1-152 Layered Product
HP I64VMS OPENVMS V8.4 Platform (product suite)
HP I64VMS VMS V8.4 Operating System
HP I64VMS WBEMCIM V2.91-A070728........Layered Product
HP I64VMS WBEMPROVIDERS V2.0-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.4: 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 configuration procedure:
@SYS$STARTUP:KRB$CONFIGURE.COM
o Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:
$ @SYS$STARTUP:KRB$STARTUP
o Add the following line to SYS$MANAGER:SYLOGIN.COM:
$ @SYS$MANAGER:KRB$SYMBOLS
Press RETURN to continue:
6.4.7 Upgrade Creates and Validates Boot Options (Integrity servers only)
At this point in an OpenVMS Integrity servers
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 Integrity servers 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:
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-2009 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.4
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
