HP OpenVMS Systems Documentation
OpenVMS VAX Version 7.3
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.
By following these directions, the time that you spend upgrading your VAX computer from Version 5.5-2 to Version 7.3 can be significantly reduced.
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.
|Current Version||Intermediate Version||Final Version|
|6.1||No intermediate version needed.||7.3|
|6.2||No intermediate version needed.||7.3|
|7.0||No intermediate version needed.||7.3|
|7.1||No intermediate version needed.||7.3|
|7.2||No intermediate version needed.||7.3|
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.
You should not plan to stay at the intermediate version. If you need to upgrade to and run the intermediate version, use the normal upgrade procedure located in the installation manual for that specific version.
Before you begin the multiversion upgrade, you need to perform the following steps:
Follow these steps to perform an intermediate upgrade of your OpenVMS VAX operating system.
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.
Follow these steps to perform the final upgrade of your OpenVMS VAX operating system.
This section provides specific information about the following layered products and firmware:
This section contains information about layered products.
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.
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:
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:
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.
|License Types by Code|
|System Marketing Model||A||B||C||D||E||F||I|
|VAX 6000-210, 6000-310||58||NA||NA||NA||230||300||300|
|VAXft 310, 410, 610, 810||58||NA||NA||NA||230||300||300|
|VAX 6000-220, 6000-320, 6000-410||69||NA||NA||NA||230||600||600|
|VAX 6000-230, 6000-330, 6000-510||81||NA||NA||NA||400||900||900|
|VAX 6000-240, 6000-340, 6000-350, 6000-420, 7000-610, 10000-610||93||NA||NA||NA||400||1200||1200|
|VAX 6000-540, 6000-640||170||NA||NA||NA||600||2400||2400|
|VAX 6000-550, 6000-650||195||NA||NA||NA||600||2400||2400|
|VAX 6000-560, 6000-660||220||NA||NA||NA||600||2400||2400|
|VAX 8200, 8250||20||NA||NA||NA||230||100||100|
|VAX 8300, 8350||25||NA||NA||NA||230||200||200|
|VAX 8550, 8700, 8810||72||NA||NA||NA||400||600||600|
|VAX 8600, 8650||28||NA||NA||NA||230||400||400|
|VAX 8800, 8820||93||NA||NA||NA||400||1200||1200|
|VAX 8830, 6000-360, 6000-430, 6000-520, 6000-620||119||NA||NA||NA||600||1800||1800|
|VAX 7000-620, 10000-620||145||NA||NA||NA||600||1800||1800|
|VAX 6000-440, 6000-450, 6000-460, 6000-530||143||NA||NA||NA||600||2400||2400|
|VAX 7000-630, 10000-630||167||NA||NA||NA||600||2400||2400|
|VAX 7000-640, 10000-640||197||NA||NA||NA||600||2400||2400|
|VAX 6000-630, 9000-210, 9000-410||143||NA||NA||NA||600||2400||2400|
|VAX 7000-710, 810||93||NA||NA||NA||230||600||600|
|VAX 7000-720, 820||193||NA||NA||NA||230||600||600|
|VAX 7000-730, 830||293||NA||NA||NA||230||600||600|
|VAX 7000-740, 840||393||NA||NA||NA||230||600||600|
|VAX 7000-750, 850||493||NA||NA||NA||230||600||600|
|VAX 7000-760, 860||593||NA||NA||NA||230||600||600|
|MicroVAX 2000, 3100-10e, 3100-20e, 3100-30, 3100-40, 3100-80||18||NA||100||NA||230||20||20|
|MicroVAX 3100-90, 3100-96, 3100-96A||60||NA||100||NA||230||20||20|
|MicroVAX 3500, 3600, 3800, 3900, 4000-200||60||NA||100||NA||230||200||200|
|MicroVAX 3300, 3400, 4000-100, 4000-106A||60||NA||100||NA||230||100||100|
|VAX 4000-100, 4000-106||60||NA||100||NA||230||100||100|
|VAX 4000-300, 4000-400, 4000-500A, 4000-600A, 4000-700A, 4000-706A||60||NA||100||NA||230||300||300|
|VAX 4000-500, 4000-600||60||NA||100||NA||400||900||900|
|VAXstation II, II/GPX||NA||NA||NA||100||50||10||10|
|VAXstation 2000, 2000/GPX||NA||NA||NA||100||50||10||10|
|VAXstation 3100, 3200, 3500, 3520, 3540, 4000-60, 4000 VLC, 4000-90, 4000-96||NA||NA||NA||100||50||10||10|
|VAXserver 3300, 3400, 3500, 3600, 3900, 4000-200, 4000-300||NA||100||NA||NA||50||10||10|
|VAXserver 6000-210, 6000-310||NA||1443||NA||NA||230||200||200|
|VAXserver 6000-220, 6000-320, 6000-410, 6000-420||NA||1737||NA||NA||230||400||400|
|VAXserver 9000-110, 9000-310||143||143||NA||NA||600||900||900|
A---OpenVMS Capacity or OpenVMS Unlimited or Base
C---OpenVMS Concurrent User
E---System Integrated Products (SIPs)
G---Compaq Reserved (not shown)
H---OpenVMS Reserved (not shown)