Document revision date: 19 July 1999 | |
Previous | Contents | Index |
To remove DECwindows files from the system disk, do the following:
$ RUN SYS$UPDATE:DECW$TAILOR |
Do you want to tailor files "ON" or "OFF"? |
CLASS - DECwindows workstation support files Size of entire class (with subclasses): 14301 Size of common files required for any subclass: 8937 Do you wish to select the entire class (default = NO)? . . . |
To cancel DECW$TAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling DECW$TAILOR during the third phase can cause a partially tailored disk. For a description of each phase, see Section 10.2.1. |
To install DECwindows device support and font files after the OpenVMS VAX installation or to add optional DECwindows files that you previously chose not to install or that you removed, do the following:
$ RUN SYS$UPDATE:DECW$TAILOR |
Do you want to tailor files "ON" or "OFF"? |
CLASS - DECwindows workstation support files Size of entire class (with subclasses): 14301 Size of common files required for any subclasses: 8937 Do you wish to select the entire class (default = NO)? . . . |
To cancel DECW$TAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling DECW$TAILOR during the third phase can cause a partially tailored disk. For a description of each phase, see Section 10.2.1. |
After adding files to the system disk, apply any updates that affect
them. For example, suppose you delete the Version 7.2 DECwindows 100
dots/inch video font files. Later on, you are able to use the 100
dots/inch fonts, so you run DECW$TAILOR to return the files to the
system disk. You must then apply any OpenVMS VAX update that has
occurred since Version 7.2 that affected the 100 dots/inch video font
files. OpenVMS VAX update procedures create a .TXT file that contains a
description of modified files. This file is usually named with the
following format: SYS$UPDATE:VMSUn05n.TXT1.
10.2.5 Sample Session
Example 10-2 illustrates how to add the files for DECwindows 100 dots/inch font files.
Example 10-2 Sample DECW$TAILOR Session |
---|
$ RUN SYS$UPDATE:DECW$TAILOR . . . Do you want to tailor files "ON" or "OFF"? ON TAILOR-ON --------- You will now be prompted with a list of the classes and subclasses of DECwindows files that are optional. The size of each class and subclass is included in the list. This will help you decide whether or not you want to add a class or subclass to your system. Under some classes, there is a set of common files that is required in order for any subclasses to work. These files are added when you ask for either the entire class or any of its subclasses. Total size of the system disk is 2376153 blocks. Total space used on the system disk is 1728072 blocks. Total space left on the system disk is 648081 blocks. CLASS - DECwindows base support files Size of entire class (with subclasses): 3363 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? CLASS - DECwindows workstation support files Size of entire class (with subclasses): 12376 Size of common files required for any subclass: 8916 Do you wish to select the entire class (default = NO)? NO Do you wish to select any of its subclasses (default = NO)? CLASS - 75 dots per inch video font files Size of entire class (with subclasses): 4537 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? CLASS - 100 dots per inch video font files Size of entire class (with subclasses): 3693 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? YES Files have been selected Do you wish to add all of the options selected? YES Creating temporary command file, please wait... * Enter device containing DECwindows distribution media: MUA0: . . . |
1 Examine this file to determine if the update patched the 100 dots/inch font files. |
This appendix provides you with an 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.2 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.2.
Current Version | Intermediate Version(s) | Final Version |
---|---|---|
5.5-2 | 6.1, followed by 6.2, 7.0, or 7.1 1 | 7.2 |
6.0 | 6.2 | 7.2 |
6.1 | 6.2 | 7.2 |
6.2 | 2 | 7.2 |
7.0 | 2 | 7.2 |
7.1 | 2 | 7.2 |
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.
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:
http://www.service.digital.com/openvms |
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.
http://www.service.digital.com/openvms |
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.2, 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.2 at this time.
Debugger Graphical User Interface (GUI)
To run the Debugger Graphical User Interface (GUI) on OpenVMS Version 7.2, 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.2 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 a VAXcluster environment. You can obtain a PAK from a Compaq representative the same way as you obtain software.
See Table B-1 for a complete list of the versions of the OpenVMS VAX operating system and the VAX computers that were first supported by these versions.
VMS Version | First Computer Support |
---|---|
Version 5.0 | VAX 6000 Model 2 xx, VAX 8820--8840 |
Version 5.0--2A | MicroVAX 3300/3400 |
Version 5.1 | VAX 6000 Model 3 xx, MicroVAX 3800/3900 |
Version 5.1--B | VAXstation 3100, Model 30/40 |
Version 5.1--1 | VAXstation 3520/3540 |
Version 5.2 | VAX 6000 Model 4 xx, MicroVAX 3100 |
Version 5.2--1 | VAXstation 3100, Model 38/48 |
Version 5.3 | No CPUs introduced |
Version 5.3--1 | No CPUs introduced |
Version 5.3--2 | VAX 4000 Model 300 |
Version 5.4 | VAXstation 3100 Model 76, VAX 9000, VAX 6000 Model 5 xx, VAXft 310 |
Version 5.4--1 | No CPUs introduced |
Version 5.4--2 | VAX 4000 Model 200 |
Version 5.4--3 | VAXft Models 410, 610, 612 |
Version 5.5 | VAXstation 4000 VLC, MicroVAX 3100 Models 30, 40, and 80, VAX 6000 Model 600, VAX 4000 Model 500, VAXstation 4000 Model 60, and VAXft Model 110 |
Version 5.5--2 | VAX 4000 Model 100, VAXstation 4000 Models 90 and 100, MicroVAX 3100 Model 90, VAX 4000 Model 400, VAX 4000 Model 600, VAX 7000 Model 600, and VAX 10000 Model 600 |
Version 5.5--2H4 | VAX 4000 Models 100A, 500A, 600A, and 700A |
Version 5.5--2HF | VAXft Model 810 |
OpenVMS Version | First Computer Support |
Version 6.0 |
VAX 7000 Models 650 and 660,
VAX 10000 Models 600 and 650 |
Version 6.1 | VAX 7000 Model 7 xx |
Version 6.2 | VAX 4000 Model 106A, MicroVAX 3500 Model 95A, MicroVAX 3100 Model 96, VAXstation 4000 Model 96 |
Many PAKs contain a table name in the availability or activity fields. This name 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-2 has seven lettered columns (A, B, C, D, E, F, and I; G and H are reserved by Compaq and therefore are not listed). 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 require 100 license units to load the license on a VAX--11/780 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 | |||||||
---|---|---|---|---|---|---|---|
OpenVMS | SIP | LP | |||||
System Marketing Model | A | B | C | D | E | F | I |
VAX--11/730 | 10 | NA | NA | NA | 230 | 50 | 50 |
VAX 11/750 | 12 | NA | NA | NA | 230 | 100 | 100 |
VAX 11/780, 785 | 13 | NA | NA | NA | 230 | 100 | 100 |
VAX 6000-210, 6000-310 | 58 | NA | NA | NA | 230 | 300 | 300 |
VAXft 110 | 60 | NA | NA | NA | 230 | 100 | 100 |
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 6000-610 | 81 | NA | NA | NA | 400 | 1200 | 1200 |
VAX 8200, 8250 | 20 | NA | NA | NA | 230 | 100 | 100 |
VAX 8300, 8350 | 25 | NA | NA | NA | 230 | 200 | 200 |
VAX 8500 | 63 | NA | NA | NA | 230 | 400 | 400 |
VAX 8530 | 65 | NA | NA | NA | 230 | 400 | 400 |
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 9000-420 | 241 | NA | NA | NA | 800 | 4800 | 4800 |
VAX 9000-430 | 330 | NA | NA | NA | 800 | 4800 | 4800 |
VAX 9000-440 | 386 | NA | NA | NA | 800 | 4800 | 4800 |
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 II | 18 | NA | 100 | NA | 230 | 50 | 50 |
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 2000 | NA | 52 | NA | NA | 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 6000-510 | NA | 600 | NA | NA | 230 | 400 | 400 |
VAXserver 6000-520 | NA | 890 | NA | NA | 230 | 400 | 400 |
VAXserver 9000-110, 9000-310 | 143 | 143 | NA | NA | 600 | 900 | 900 |
VAXserver 9000-320 | 241 | 241 | NA | NA | 800 | 1200 | 1200 |
VAXserver 9000-330 | 330 | 330 | NA | NA | 800 | 1200 | 1200 |
VAXserver 9000-340 | 386 | 386 | NA | NA | 800 | 1200 | 1200 |
Previous | Next | Contents | Index |
privacy and legal statement | ||
6521PRO_014.HTML |