HP OpenVMS Version 8.3 Upgrade and Installation Manual > Chapter 7 After Installing or Upgrading the OpenVMS Operating System

Postinstallation and Postupgrade Tasks

  Table of Contents



Use the checklist in Table 7-1 “Postinstallation and Postupgrade Checklist” to ensure that you perform all necessary postinstallation or postupgrade tasks. Unless indicated otherwise, these tasks are applicable as both postinstallation and postupgrade tasks.

Table 7-1 Postinstallation and Postupgrade Checklist

For a newly installed system disk, you can back up the disk. (At this point, you could reinstall OpenVMS onto the disk instead.)

For a newly upgraded system disk, if it is not going to be a shadow set member, back up the system disk as a safeguard before proceeding with the next steps. If your newly upgraded system disk is going to be a shadow set member, re-form the shadow set. As an optional precaution, you can back up the system disk as well.
“Backing Up Your System Disk”
Register any licenses that were not registered during the installation; for an upgrade, register any new licenses.“Registering Your Licenses”
New installations only (optional): Set system parameters to enable volume shadowing.“Set System Parameters for Volume Shadowing (New Installations Only; Optional)”
Tune BAP system parameters (Alpha upgrades only).“Tuning BAP System Parameters (Alpha Upgrade Only)”
If you set system parameters to enable volume shadowing or removed hardcoded BAP system parameters, run AUTOGEN and reboot. “Running AUTOGEN to Set System Parameter Changes”
If you want to form a shadow set for a newly installed system disk, you can do this now or later. If you upgraded a disk in a volume shadowing environment, re-form the shadow set. “Forming the Shadow Set”
New installations, some upgrades: Perform the following tasks that generally apply to new installations only but could also apply after an upgrade: 

Create proxy files, if required.

“Creating Network Proxy Authorization Files”


Set up the queue manager and start the default batch and print queues.

“Setting Up the Queue Manager and Default Queues ”

Configure a multihead system, if applicable.“Configuring a Multihead System (Optional)”

Configure DECnet if it was installed. After an upgrade, perform only if DECnet was added during the upgrade.

“Configuring DECnet ”

Configure TCP/IP Services for OpenVMS if it was installed. After an upgrade, configure TCP/IP Services only if it was added during the upgrade.“Configuring HP TCP/IP Services for OpenVMS”

If you are using neither DECnet nor TCP/IP Services, install and configure third-party networking software, if necessary. Networking software is required to download patches and for certain layered products.

“Installing and Configuring Third-Party Networking Software”

Initialize or configure the following optional products, as needed: 
Initialize CDSA if you have installed a new version of CDSA without upgrading the base operating system.“Initializing CDSA (Optional)”
Configure Availability Manager.“Configuring the Availability Manager Base Software (Optional)”
Configure Kerberos.“Configuring Kerberos (Optional)”
Configure SSL for OpenVMS.“Configuring SSL for OpenVMS”
Configure WBEM Services for OpenVMS“Configure WBEM Services for OpenVMS (Optional; I64 only)”
On Integrity servers that include Instant Capacity (iCAP), configure the iCAP software.“Configure the Instant Capacity Software (Optional; I64 only)”
On Integrity servers that include Pay per use (PPU), configure the PPU software.“Configure the Pay per use Software (Optional; I64 only)”
Initialize and run the Performance Data Collector base software (TDC_RT).“Initializing and Running the Performance Data Collector Base Software (Optional)”
Prepare your OpenVMS system and your PC to run OpenVMS Management Station, and follow procedures in Appendix G “Preparing to Use OpenVMS Management Station”.“Preparing to Use OpenVMS Management Station (Optional)”
Install OpenVMS Debugger clients on a PC.“Installing OpenVMS Debugger Clients on a PC (Optional) ”
Create or edit a system-specific or clusterwide login welcome message SYS$MANAGER:WELCOME.TXT (optional).“Creating a System-Specific Login Welcome Message (Optional)”
Upgrades only: Examine command procedures for which the upgrade may have provided new template files.“Examining Your Command Procedures (Upgrades Only)”
Add and remove operating system files (optional).“Adding and Removing Operating System Files (Optional)”
Expand the system libraries using LIBDECOMP.COM (optional; Alpha only).“Expanding the System Libraries (Optional; OpenVMS Alpha Only)”
Download and apply any relevant OpenVMS or networking patches that are available (optional but recommended).“Installing Patches (Optional but Recommended)”
New installations, some upgrades: Install and configure layered products.“Installing and Configuring Layered Products (New Installations, Some Upgrades)”

Upgrades only (optional): Reinstall optional DECevent software (which is automatically removed during an upgrade)

“Reinstall DECevent Software (Upgrades only; optional)”

New installations, some upgrades: Create print queues.“Creating Print Queues (New Installations, Some Upgrades)”
Update SYSTARTUP_VMS.COM to have layered products, print queues, and other products or devices start at boot.“Updating SYSTARTUP_VMS.COM to Start Layered Products and Print Queues”
Create user accounts.“Creating Accounts (New Installations, Some Upgrades)”
Run the User Environment Test Package (UETP) to test the system (optional).“Testing the System with UETP (Optional)”
Back up the system disk and start a systematic routine for backing up the application, data, and user disks.“Backing Up the Customized System Disk and Initiating Systematic Backups”
If the system disk was pulled out of the shadow set and all the appropriate postupgrade steps recommended in this chapter thus far were performed on that disk, then re-form the shadow set once again.“Reforming the Shadow Set as Final Postupgrade Backup”
Upgrades only: Reboot cluster members, if applicable.“Rebooting Cluster Members (Upgrades Only)”
Tune your operating system: After the system has run for at least 24 hours with users or a typical application workload on the system, run AUTOGEN to collect feedback and, if necessary, modify the MODPARAMS.DAT file.

“Running AUTOGEN to Tune the System”

“Modifying System Parameters”