Installation and Upgrade Guide

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.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 (page 107).) 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.3-1H1 Platform (product suite)
6.4 Completing the Upgrade 107