HP OpenVMS Systems Documentation

This appendix provides you with a quick method and an easy to follow set of directions to apply multiple OpenVMS VAX version upgrades to your current system.

Your first step is to determine which upgrade path you need to perform. Table A-1 lists the recommended upgrade paths to reach OpenVMS VAX Version 7.3.

This procedure refers to an intermediate upgrade and final upgrade. An intermediate upgrade is defined as a version of the operating system that you need to install to reach your final version.

The final upgrade is the version of the operating system that you want to be running on your system at the end of this process.

Before you begin the multiversion upgrade, you need to perform the following steps:

1. Locate the OpenVMS VAX software kits for the versions that you need.
2. Review the layered products on your system to determine the minimum supported version of each layered product to be installed on your final operating system version.
   • Determine which layered products you want to run on your system. See the web page at the following URL:

     http://www.support.compaq.com/openvms/

   • For information about specific layered products, see Section A.3.

Follow these steps to perform an intermediate upgrade of your OpenVMS VAX operating system.

1. Review your mixed-cluster version environment. Compaq recommends that you upgrade all of your systems to the same version prior to performing a multiversion upgrade.
2. Review the firmware running on your system. For information about specific layered products, see Section A.3.
3. Review the version-specific documentation. Compaq recommends that you read the New Features, Release Notes, Installation Guide, and Software Product Description available in your software kit.
4. Review the preupgrade checklist located in the Installation Guide.
5. Perform the upgrade.

   Important For the intermediate upgrade, install only the base operating system. Do not install any options. By installing only the base operating system, the time that you spend upgrading your VAX computer during this intermediate upgrade can be reduced by 40 percent.

6. Perform the postupgrade checklist located in the Installation Guide.
7. If you are performing multiple intermediate upgrades, repeat steps 3-7 as necessary.
8. You have completed the intermediate phase of the multiversion upgrade procedure. Proceed to Section A.2.3 to apply the final upgrade phase of this procedure.

Follow these steps to perform the final upgrade of your OpenVMS VAX operating system.

1. Review the version-specific documentation. Compaq recommends that you read the New Features, Release Notes, Installation Guide, and Software Product Description available in your software kit.
2. Perform the preupgrade checklist located in the Installation Guide.
3. Perform the complete upgrade and select the optional files that you need for your final version.
4. Perform the postupgrade checklist located in the Installation Guide.
5. Upgrade the layered products on your system based on your review of layered products in Section A.2.1. See the web page at the following URL:

   http://www.support.compaq.com/openvms/

This section provides specific information about the following layered products and firmware:

• BASEstar
• Debugger

This section contains information about layered products.

BASEstar Classic Domain

A BASEstar Classic domain that consists of BASEstar Classic for OpenVMS VAX Versions 3.2 and 3.3 is fully supported on OpenVMS Version 7.3, as long as you obtained the kits through normal support channels.

However, on Alpha systems you need to be running BASEstar Classic Version 3.4. This means that any BASEstar Classic domain consisting of both VAX and Alpha systems can only have the VAX systems upgraded to OpenVMS Version 7.3 at this time.

Debugger Graphical User Interface (GUI)

To run the Debugger Graphical User Interface (GUI) on OpenVMS Version 7.3, you must be running the DECwindows Motif for OpenVMS layered product. See Section 1.1.3 for information about DECwindows Motif.

This appendix contains supplemental information to the license instructions given in the installation and upgrade procedures and in the OpenVMS License Management Utility Manual. Although most of the information in this appendix pertains to managing OpenVMS and System Integrated Product (SIP) licenses, some of the information pertains to managing layered product licenses.

This appendix covers the following information:

• Registering your licenses
• Using the License Unit Requirement Table (LURT)
• License Management Facility (LMF) notes
• Volume Shadowing for OpenVMS license
• Other System Integrated Product (SIP) licenses

This section provides an overview of the license registration procedure.

B.1.1 When to Register

After you install the OpenVMS VAX operating system, you must register an OpenVMS VAX license. An OpenVMS VAX license lets you use the operating system. You must also register the licenses for any of the following SIPs you have purchased:

• OpenVMS Cluster software
• Compaq DECnet-Plus for OpenVMS VAX
• DECnet Phase IV for OpenVMS VAX
• OpenVMS RMS Journaling
• Volume Shadowing for OpenVMS

After you upgrade the OpenVMS VAX operating system, in most cases, there is no need to reregister licenses for the operating system or for SIPs.

In addition to the OpenVMS VAX operating system and the SIPs, many layered products---including DECwindows Motif for OpenVMS VAX---that run on OpenVMS VAX Version 7.3 also require license registration. Refer to the OpenVMS License Management Utility Manual for a full explanation of license registration.

B.1.2 How to Register

To register a license, you need to obtain a Product Authorization Key (PAK). A typical PAK is a piece of paper provided by Compaq Computer Corporation that contains the appropriate information to authorize access to software on a VAX computer or in an OpenVMS Cluster environment. You can obtain a PAK from a Compaq representative the same way that you obtain software.

B.2 Using the License Unit Requirement Table (LURT)

Many PAKs contain an alphabetic letter in the availability or activity fields. This letter refers to a column in the License Unit Requirement Table (LURT). (For more information about using the LURT, refer to the OpenVMS License Management Utility Manual.)

Table B-1 has seven lettered columns (A, B, C, D, E, F, and I; G and H are reserved by Compaq and are not listed here). The numbers listed in these columns indicate the number of license units required for each processor listed in the System Marketing Model column. For example, if your PAK specifies Availability = F, you would look in column F to determine that you need 600 license units to load the license on a VAX 6000-220 computer, or 4800 license units to load the license on a VAX 9000-430 computer.

Note that some PAKs specify MOD_UNITS in the options field. The MOD_UNITS option allows the system manager to use the DCL command LICENSE MODIFY/UNITS to temporarily increase the size of the PAK. This permits a product to be used, in certain emergency situations, on a processor larger than the processor size specified in the license. Check your license terms and conditions before modifying license units. Reset the PAK size to its original size after the emergency situation is resolved.

A---OpenVMS Capacity or OpenVMS Unlimited or Base
B---OpenVMS Server
C---OpenVMS Concurrent User
D---OpenVMS Workstations
E---System Integrated Products (SIPs)
F---Layered Products
G---Compaq Reserved (not shown)
H---OpenVMS Reserved (not shown)
I---Layered Products
NA---Not applicable