A Product Authorization Key (PAK) contains information that is provided for many Digital products. The data provided in the PAK allows you to register a software license in the license database on a system.
If you did not register and load your operating system license during the installation of the OpenVMS operating system, you must perform that task (and register other licenses, if necessary) before you install other software products, as explained in the following steps:
For more information about loading licenses, see the OpenVMS License Management Utility Manual.
The /NO_SHARE qualifier for the LICENSE MODIFY command lets you add the NO_SHARE option to a PAK registered in a license database (LDB). NO_SHARE PAKs are assigned to a single node in an OpenVMS Cluster system. A NO_SHARE PAK cannot be shared with other OpenVMS Cluster nodes.
This qualifier remedies problems that occasionally occur when you attempt to use the PAK of a software product for which you already have other PAKs in your LDB. The PAK does not combine with the other PAKs for the same software product, resulting in LICENSE-W-NOCOMB warnings. Often, the license is not loaded on the nodes on which you want it loaded.
To remedy this problem, do the following:
Before you run VMSINSTAL.COM, note the following:
Caution
If you continue the procedure without making the required corrections, Digital cannot guarantee that the installation will be supported.
To run VMSINSTAL.COM, enter a command in the following format:
@SYS$UPDATE:VMSINSTAL product-list source: [OPTIONS option-list] [destination] [qualifiers]
Example
$ @SYS$UPDATE:VMSINSTAL CALENDAR020 MUA0:
The command in this example installs the product CALENDAR, from save sets named CALENDAR020, on a magnetic tape on the MUA0: drive. (This command shows the simplest case, in which you use no options or qualifiers.)
The following sections explain required and optional parameters in the VMSINSTAL.COM command line:
Parameter | Section |
---|---|
Product list | Section 3.5.1 |
Source | Section 3.5.2 |
Options | Section 3.5.3 |
Destination | Section 3.5.4 |
Backup qualifiers | Section 3.5.5 and Section 3.7.3.3 |
Section 3.5.6 explains how to complete an installation.
Products are stored in a save set, which is a specially formatted file that contains a group of files. Installation and upgrade procedures move the files from the save set to your system disk.
The product-list parameter lists the products that you want to install. You can use this parameter when you install layered products or update the operating system. (When you perform an upgrade procedure, you can list only one product, VMSvvu.)
Note
Do not use the wildcard character (*) if you are installing layered products and updating the operating system at the same time. In this case, update the system first. If you use the wildcard character, VMSINSTAL sorts the product list in alphabetical order; the operating system would probably not be installed first.
If you want to specify more than one item in the product-list parameter, separate the items using commas and no intervening spaces. Use the following format to specify the product list:
facvvu
Table 3-3 explains the format of facvvu. Using this format, you can install a specific version and update of a product from distribution media containing several versions and updates. If you do not include a version and update number, all versions and updates to the specified product from the source are installed in alphabetical order.
fac | The product name code (1 to 36 alphanumeric characters) |
vv | The major version number (2 digits) |
u | The minor version number (1 digit), also known as update number |
If you are installing from a distribution kit, the list of products on your distribution media is included with the bill of materials for the distribution kit. If the list is not available, you can obtain one by using the DIRECTORY command; the distribution media then finds and displays the products that are included.
To obtain the product list, enter commands in the following format:
MOUNT/OVERRIDE=ID device:
DIRECTORY device:[0,0]
where device is the drive that holds the distribution media.
If you are installing from a disk directory, obtain the product list by entering DIRECTORY and specifying the disk directory in the following format:
DIRECTORY node::device:[directory]
Examples
$ MOUNT/OVERRIDE=ID MUA0: %MOUNT-I-MOUNTED, VMS071 mounted on _MUA0: $ DIRECTORY MUA0:[0,0]
Directory MUA0:[000,000] 000000.DIR;1 BACKUP.SYS;1 BADBLK.SYS;1 BADLOG.SYS;1 BITMAP.SYS;1 CONTIN.SYS;1 CORIMG.SYS;1 DECW071.C;1 DECW071.D;1 DECW071.E;1 DECW071.F;1 INDEXF.SYS;1 ISL_SCRIPT.ESS;1 SECURITY.SYS;1 SYS0.DIR;1 VMS071.A;1 VMS071.B;1 VMS071.C;1 VMS071.D;1 VMS071.E;1 VMS071.F;1 VOLSET.SYS;1 Total of 22 files.
$ DIRECTORY BRAVO::DUA1:[0,0]
Note
To access a remote node, you must have read and execute access (R,E) to the directory.
The source parameter identifies the source of the optional software product as one of the following:
You can also use a logical name to specify the source. If you do not specify the source, VMSINSTAL.COM asks you for it, as follows:
* Where will the distribution volumes be mounted:
The VMSINSTAL.COM command procedure permits the use of six options. Table 3-4 briefly describes each option. Section 3.7 contains a detailed description of each option.
Letter Choice | Option | Description |
---|---|---|
A | Autoanswer | Makes it easier to reinstall a product after an upgrade by providing responses to the questions and prompts during the reinstallation. (Specify this option only when installing layered products.) |
AWD= | Alternate Working Device | Lets you specify an alternate working device for the temporary working directory. (You can specify this option when installing layered products or applying updates.) |
G | Get Save Set | Saves you time by allowing you to store product save sets temporarily on a magnetic tape or in a disk directory. (Specify this option only when installing layered products.) |
L | File Log | Logs all file activity to the terminal during installation. |
N | Release Notes | Displays or prints the online release notes file supplied by the layered product. |
R | Alternate Root | Lets you install the product on a system disk other than that of the running system. |
You specify each option by entering the appropriate option letter after the keyword OPTIONS in the command that starts VMSINSTAL.COM. The OPTIONS keyword is optional. However, if you have an option list, you must enter OPTIONS before it. If you enter an option list without the OPTIONS keyword, VMSINSTAL.COM displays an informational error message and the installation ends. (The option-list parameter lists the options requested.)
How to Perform This Task
If you specify more than one option, separate the options with commas. Do not separate the options with spaces.
Example
$ @VMSINSTAL.COM NEWAID021 MTA0: OPTIONS A,N
The destination parameter is optional. By default, VMSINSTAL.COM assumes that the product is to be installed in the system common directory SYS$COMMON on the system disk. However, you must use this parameter in the following two instances:
device:[SYSn.]
device | The device on which the alternate root resides |
SYSn. | The top-level directory of the alternate system root |
device:[directory]
device | The destination disk device |
directory | Usually a directory dedicated to product save sets on the specified disk |
The VMSINSTAL.COM command procedure includes a BACKUP command that copies the save sets to the destination directory. You can verify, log, and confirm the copy operation by specifying BACKUP qualifiers with the VMSINSTAL.COM Get Save Set option. See Section 3.7.3 for more information.
When the installation is complete, VMSINSTAL.COM does one of the following, depending on the requirements of the product you have installed:
When the product is installed, back up the updated system disk. For instructions, see Section 10.17.
If the system fails during installation of an update or optional software product, VMSINSTAL.COM attempts to continue the installation upon rebooting. Depending on when the system failed, one of three conditions exists:
When you use VMSINSTAL.COM, the command procedure allows you to select up to six options (summarized previously in Table 3-4.) The following sections describe those VMSINSTAL.COM options in detail.
The Autoanswer option makes it easier to reinstall a product by providing responses to VMSINSTAL.COM questions and prompts during the reinstallation. You use the Autoanswer option most often to reinstall products after an upgrade.
If you specify the Autoanswer option when you install a product initially, an answer file is created in the form product.ANS in the SYS$UPDATE directory, where product is the product name parameter that you provide when you start VMSINSTAL.COM.
The answer file contains a record of your responses to questions and prompts from VMSINSTAL.COM. For example, if you install the product NEWAID010 with the Autoanswer option, VMSINSTAL.COM creates an answer file called NEWAID010.ANS.
When you reinstall the product and specify the Autoanswer option (typically after upgrading your operating system), VMSINSTAL.COM reads the answer file instead of asking you questions.
If you want to create a new answer file when you reinstall a product, you must first delete the existing answer file.
Example
To use the Autoanswer option, specify the following command:
$ SYS$UPDATE:VMSINSTAL.COM NEW$PRODUCT010 CSA1: OPTIONS AYou can then examine the file:
$ TYPE SYS$COMMON:[SYSUPD]NEW$PRODUCT010.ANS;1 * Do you want to install the entire kit [Y]? \ * Are these selections correct [Y]? \ * Does this product have an authorization key registered and loaded? \Y * Will you allow a system shutdown after this product is installed [YES]? \ * How many minutes for system shutdown [0]: \ * Do you want to do an automatic system reboot [YES]? \ $
Restriction
Before using this option, check with the product's installation guide to be sure this option is supported by that product.
You can use the Alternate Working Device option to specify an alternate working device for the temporary working directory (defined as the logical name VMI$KWD). This option allows you to perform an installation with fewer free blocks on the system disk than are otherwise required.
If you do not specify this option, VMSINSTAL.COM creates the temporary working directory in the following location:
SYS$SPECIFIC:[SYSUPD.facvvu]
Table 3-3 explains the format of facvvu.
How to Perform This Task
Use the following format to specify this option:
AWD=dev:[dir]
where:
dev | Specifies the alternate working device |
dir | Specifies the directory under which the facvvu subdirectory will be created |
Specifying a directory is optional. If you do not specify a directory, VMSINSTAL.COM creates the working directory on the specified device with the following directory specification: [000000.facvvu]. If you specify a directory, VMSINSTAL.COM creates the working directory as a subdirectory within the directory that you specify (for example, [WORK.facvvu]). If the directory that you specify does not exist, VMSINSTAL.COM does not create it.
Example
To use the working directory [INSTALL] on the alternate device DUA2:, specify the following:
$ @SYS$UPDATE:VMSINSTAL.COM NEWAID010 CSA1: OPTIONS AWD=DUA2:[INSTALL]
Note
You cannot use this option to copy operating system kits.
Installing products either from a distribution tape or from console media directly onto your system disk is time-consuming. The Get Save Set option saves you time by allowing you to copy product save sets and store them temporarily while you do other work; you can then perform an update more quickly at a time that is convenient for you.
You might consider dedicating a user disk on a node that other licensed system users can access. You can store product save sets on this dedicated user disk to give other licensed system users fast access to the product save-set directory.
To store a product save set on a disk directory using the Get Save Set option, enter a command using the following syntax:
@SYS$UPDATE:VMSINSTAL.COM product-list source OPTIONS G device:[directory]
The directory you specify must exist, and the device must be mounted.
Examples
If you specify just one option, enter the disk directory name immediately after the OPTIONS G parameter, leaving a space between G and the disk directory. For example, if you are storing save sets for a product named NEWAID010 from the console drive into disk directory USER1:[PRODUCTS], enter the following command:
$ @SYS$UPDATE:VMSINSTAL.COM NEWAID010 CSA1: OPTIONS G USER1:[PRODUCTS]
If you specify more than one option, place the disk directory name after the last option, leaving a space between the last option and the disk directory name. For example:
$ @SYS$UPDATE:VMSINSTAL.COM NEWAID010 CSA1: OPTIONS G,N USER1:[PRODUCTS]
VMSINSTAL.COM creates one or more files to store the product save set in the disk directory. The save-set file name has the following format:
facvvu.x
Table 3-3 explains the format of facvvu. The format of the file type (x) is:
x | A literal file type that identifies save-set files, where A is the first save set, B the second, and so forth |
To install the product on your system, enter a command in the following format:
@SYS$UPDATE:VMSINSTAL product-list device:[directory]
Example
For the product NEWAID010, enter this command:
$ @SYS$UPDATE:VMSINSTAL NEWAID010 USER1:[PRODUCTS]
VMSINSTAL.COM installs the NEWAID product on your system disk.
When you use the Get Save Set option, you can specify three BACKUP command qualifiers: /VERIFY, /LOG, and /CONFIRM. The qualifiers must be enclosed in quotation marks because they are passed as a parameter of the Get Save Set option (G). VMSINSTAL passes the parameter to the BACKUP command within VMSINSTAL. The following example includes the Get Save Set option and BACKUP qualifiers:
$ @SYS$UPDATE:VMSINSTAL TEST042 DUA0:[KITS] OPTIONS G DUB0:[KITS] - _$ "VERIFY/LOG/CONFIRM"
Following are explanations of the qualifiers shown in the example:
Qualifier | Explanation |
---|---|
/VERIFY | Compares the contents of the output specifier with the contents of the input specifier after a save, restore, or copy operation completes. If a file does not compare successfully, an error message reporting this fact is displayed. |
/LOG | Causes the file specification of each file processed to be displayed at the terminal during the operation. The default is /NOLOG. |
/CONFIRM | Displays a prompt on your terminal before each file is processed. To process the file, enter Y or YES and press the Return key. The system interprets any other response, including simply pressing the Return key, as NO. |
See the OpenVMS System Management Utilities Reference Manual for more information about the BACKUP command and its qualifiers.
The File Log option logs all file activity to the terminal during installation. File activity as any action that alters the disposition of a file, such as creating a new file, updating a library, or deleting a file.
Use the Release Notes option to display or print the online release notes file supplied by a layered product and by the update procedure.
Note
Not all layered products provide online release notes.
The release notes file receives the file name facvvu.release_notes, where facvvu represents the product name code, version, and update numbers (see Table 3-3); for example, NEWAID010.RELEASE_NOTES.
How to Perform This Task
If release notes are available and you specify option N, VMSINSTAL.COM asks you the following questions. (The default answers are indicated in brackets.)
Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above. (1) *Select option [2]: (2) *Queue name [SYS$PRINT]: (3) *Do you want to continue the installation [N]:
Following are explanations that correspond to the numbered entries in the example:
%VMSINSTAL.COM-W-NOFILE, New File facvvu.RELEASE_NOTES does not exist. %VMSINSTAL.COM-W-NORELNOTE, unable to locate release notes. *Do you want to continue the installation [N]:
You can use the Alternate Root option to install the product on a system disk other than that of the running system. You might use this option to test a layered product without disturbing the running system.
The operating system in the alternate root must be complete and have the same version or update level as the running system. All files and software products that the product installation refers to must be present in the alternate root.
Notes
Not all optional software products allow you to install a product on an alternate root. Consult the documentation of the specific product to determine whether you can install the product on an alternate root.
Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]
![]()
6017P004.HTM OSSG Documentation 22-NOV-1996 14:21:21.84Copyright © Digital Equipment Corporation 1996. All Rights Reserved.