Filter
Top Products
1. Check for a POLYCENTER software installation (PCSI) utility TDC V2.0 installation by
logging on to a privileged account and entering the following command:
$ PRODUCT SHOW PRODUCT TDC
If the resulting display shows that TDC is not found on the system, no action is required; if
TDC is found, proceed to step 2.
2. If the SHOW PRODUCT display shows that TDC V2.0 is installed, enter the following
command to remove the product:
$ PRODUCT REMOVE TDC
4.5 Software That Must be Deconfigured (Integrity servers Only)
Before upgrading, if you are using or have configured WBEM Providers for OpenVMS, you must
manually deconfigure WBEM Providers by entering the following command:
$ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$DECONFIGURE.COM
4.6 Saving Archived Files from Being Deleted by the Upgrade
By default, the upgrade procedure deletes files that were archived as filename.type_OLD by
OpenVMS remedial kits. If you do not want these files deleted, you can rename them before you
perform the upgrade. Alternatively, you can have the upgrade procedure save them by responding
to the prompts, as described in Section 6.4.4 (page 118).
4.7 Preparing the System Disk
The following sections describe how to prepare the system disk for the upgrade. Operations
include the following:
• Checking for appropriate directory structure and preserving your security protections
• Checking the SYSCOMMON directories
• Purging duplicate files from the system disk
• Examining the system disk
• Checking the size of the system disk
• Returning authorization and AGEN$INCLUDE files to the system disk
• Verifying system parameters
4.7.1 Checking the Directory Structure and Preserving Your Security Protections
If you changed the directory structure on your system disk, the upgrade procedure does not
work correctly. Restore your system disk to a standard directory structure before you attempt
an upgrade.
The OpenVMS upgrade procedure provides new files and directories in the directory
[VMS$COMMON...]. If you have any special protections and access control lists (ACLs), you
need to reapply them to reestablish the security environment you currently have. For more
information about creating and maintaining a secure environment, see the HP OpenVMS Guide
to System Security manual.
4.7.2 Checking the SYSCOMMON Directories
For the upgrade to be successful, the SYSCOMMON directories in all system roots must be aliases
(or hard links) for the VMS$COMMON directory. To check whether this is the case, enter the
following commands if you are booted from the system disk that you are upgrading, and compare
the displayed file identifiers to ensure that they are all the same:
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[000000]VMS$COMMON.DIR
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[SYS*]SYSCOMMON.DIR
4.5 Software That Must be Deconfigured (Integrity servers Only) 87