HP OpenVMS Systems Documentation

You can use VMSKITBLD to copy the operating system files to a target disk without deleting the files already existing on the target disk. For example, if you accidentally delete a large number of system files from a system disk, you can use VMSKITBLD to copy the system files from another system disk.

To do this, the operating system must be running and the source disk that you intend to copy from must be mounted.

When you use the COPY option of VMSKITBLD.COM, the user-modified files (including SYSUAF.DAT and site-specific command files) are not copied from the source disk; VMSKITBLD uses the unaltered TEMPLATE versions of these files. In addition, the procedure does not create the system-specific files SWAPFILE.SYS, PAGEFILE.SYS, or SYSDUMP.DMP.

Before VMSKITBLD copies each new system file, it deletes the older version of the file from the target disk.

How to Perform This Task

1. Log in to the SYSTEM account.
2. Place the target disk into the appropriate drive.
3. Note the device name of the target disk.
4. Enter the following command to invoke VMSKITBLD:

   $ @SYS$UPDATE:VMSKITBLD

   VMSKITBLD prompts you to choose one of the following options:

   Operation [BUILD,ADD,COPY]?

5. Enter COPY and press Return. VMSKITBLD displays messages that either prompt you for information needed to complete the copy operation or inform you of the procedure's status.
   1. In response to the following prompt, enter the name of the source disk.

      * Enter mounted SOURCE disk name (ddcu:):

   2. In response to the following prompt, enter the top-level system directory for the source disk:

      * Enter SOURCE disk top level system directory [default = SYS0]:

      
      In most cases, you can choose the default value [SYS0].
   3. In response to the following prompt, enter the name of the target disk:

      * Enter TARGET disk name (ddcu:):

   4. In response to the following prompt, enter the top-level system directory:

      * Enter TARGET disk top level system directory [default = SYS0]:

      
      In most cases, you can choose the default value [SYS0].
   
   When the system displays the dollar sign ($) prompt, the files have been copied and the system disk is complete. VMSKITBLD automatically dismounts the target disk.

Example

* Enter mounted SOURCE disk name (ddcu:): SYS$SYSDEVICE:
* Enter SOURCE top level system directory [default = SYS0]: [Return]
* Enter TARGET disk name (ddcu:): DUA0: [Return]
* Enter TARGET disk top level system directory [default = SYS0]: [Return]
%DCL-I-ALLOC, _DUA0: allocated
%MOUNT-I-MOUNTED, VAXVMSRL5 mounted on _DUA0:
    Copying files from source disk ...
    Copying DECwindows files from source disk ...
    Writing a boot block ...
    System disk complete.
$

Use the ADD option to create an alternate system root directory on a target system disk. You might use this option to create a test environment where you can test software without interfering with the current version of the system.

The system disk that you are adding to cannot be in use.

The ADD option creates only new specific root directories. The current common directory is linked to the new root.

How to Perform This Task

1. Log in to the SYSTEM account.
2. Check the number of free blocks on the system disk to make sure you have adequate space for the new files, including SWAPFILE.SYS, PAGEFILE.SYS, and SYSDUMP.DMP. The sizes of these files are determined by the type of computer you use. For information about calculating size for page, swap, and dump files, see Section 16.4.
3. Make sure the target system disk is dismounted and on line.
4. Enter the following command to invoke VMSKITBLD:

   $ @SYS$UPDATE:VMSKITBLD

   VMSKITBLD prompts you to choose one of the following options:

   Operation [BUILD,ADD,COPY]?

5. Enter ADD and press Return. VMSKITBLD displays messages that either prompt you for information needed to complete the operation or inform you of the procedure's status.
   1. In response to the following prompt, enter SYS$SYSDEVICE and press Return:

      * Enter mounted SOURCE disk name (ddcu:):

   2. In response to the following prompt, press Return to choose the default:

      * Enter SOURCE disk top level system directory [default = SYS0]:

   3. In response to the following prompt, enter the name of the target disk:

      * Enter TARGET disk name (ddcu:):

   4. In response to the following prompt, enter the new root directory specification:

      * Enter TARGET disk top level system directory [default = SYS0]:

      
      Do not specify directories SYSE or SYSF:
      • SYSE is reserved for storing standalone BACKUP.
      • SYSF is reserved for Compaq use.
   
   When the system displays the dollar sign ($) prompt, the target system directory contains the new system root directory. VMSKITBLD automatically dismounts the target disk.
6. Configure the new system root by booting the target disk and running AUTOGEN. For instructions, see Section 2.5.3.1.

Example

The following example adds an alternate system root directory named SYSA on the target disk SHEMP$DUA5:

* Enter mounted SOURCE disk name (ddcu:): SYS$SYSDEVICE:
* Enter SOURCE top level system directory [default = SYS0]:[RETURN]
* Enter TARGET disk name (ddcu:): SHEMP$DUA5: [RETURN]
* Enter TARGET disk top level system directory [default = SYS0]: SYSA [RETURN]
%DCL-I-ALLOC, _SHEMP$DUA5: allocated
%MOUNT-I-MOUNTED, VAXVMSRL5   mounted on _SHEMP$DUA5:
    Creating system specific directories ...
    Creating SYSGEN files ...
%SYSGEN-I-CREATED, _SHEMP$DUA5:<SYSA.SYSEXE>SWAPFILE.SYS;1 created
%SYSGEN-I-CREATED, _SHEMP$DUA5:<SYSA.SYSEXE>PAGEFILE.SYS;1 created
%SYSGEN-I-CREATED, _SHEMP$DUA5:<SYSA.SYSEXE>SYSDUMP.DMP;1 created
    System disk complete.
$

After you use VMSKITBLD to add an alternate system root directory to a system disk, you must configure system parameters for the new root. Perform the following steps:

1. Shut down the system and halt your computer. For instructions on shutting down your system, see Section 4.8.1.
2. Perform a conversational boot, as described in the upgrade and installation supplement for your computer.
3. When the conversational boot prompt (SYSBOOT>) appears, enter the following commands:

   SYSBOOT> USE DEFAULT SYSBOOT> SET STARTUP_P1 "MIN" SYSBOOT> CONTINUE

4. After the system boots, log in to the SYSTEM account and execute AUTOGEN from the SAVPARAMS phase to set appropriate values for system parameters.
   To reboot from the former root, specify REBOOT as the end phase when invoking AUTOGEN.
   To reboot from the new root directory, specify SHUTDOWN as the AUTOGEN end phase, and reboot manually. See Section 15.5 and the OpenVMS System Management Utilities Reference Manual (AUTOGEN) for detailed information about AUTOGEN.

Example

SYSBOOT> USE DEFAULT

SYSBOOT> SET STARTUP_P1 "MIN"
SYSBOOT> CONTINUE
   .
   .
   .
$ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT CHECK_FEEDBACK
   .
   .
   .

This chapter describes the concepts related to installing, upgrading, and updating OpenVMS operating system software and layered products. Two methods are available for installing or upgrading software: the POLYCENTER Software Installation utility and the VMSINSTAL.COM command procedure.

Operating System Software

To install or upgrade the OpenVMS VAX or Alpha operating system, refer to the current OpenVMS VAX or Alpha Upgrade and Installation Manual.

Layered Product Software

To install or upgrade layered products, use either the POLYCENTER Software Installation utility or the VMSINSTAL.COM command procedure. Each layered product is packaged to use one of these. Refer to the layered product's documentation for information about which to use.

Information Provided in This Chapter

This chapter describes the following tasks:

This chapter explains the following concepts:

3.1 Installing, Upgrading, and Updating the Operating System

Refer to the following documentation for detailed instructions on how to install and upgrade the OpenVMS operating system:

• On VAX systems, refer to the most recent versions of the OpenVMS VAX Upgrade and Installation Manual and the upgrade and installation supplement for your VAX computer.
• On Alpha systems, refer to the most recent version of the OpenVMS Alpha Upgrade and Installation Manual.

To install and upgrade layered products, use either the software installation command procedure, SYS$UPDATE:VMSINSTAL.COM, or the POLYCENTER Software Installation utility. The installation documentation for each layered product states which procedure you should use.

Install or upgrade a layered product on your Alpha or VAX system as follows:

• If you are installing or upgrading a layered product using VMSINSTAL.COM, review the information in the following sections:

  Task	Section
  Preparing your system to run VMSINSTAL.COM	Section 3.3
  Running VMSINSTAL.COM	Section 3.4
  Recovering from a system failure	Section 3.5
  Selecting VMSINSTAL.COM options	Section 3.6

  
  Note that these sections do not describe specific VMSINSTAL.COM procedures. The examples used are for illustration only. For details of a particular product, refer to the installation documentation for the specific product.
• If you are installing or upgrading a layered product using the POLYCENTER Software Installation utility, refer to Section 3.7 and to the layered product installation documentation.

  Task	Section
  Using the POLYCENTER Software Installation utility	Section 3.7
  Installing software	Section 3.8
  Performing operations on installed software	Section 3.9
  Removing installed software	Section 3.10

This section provides guidelines for preparing your system for using VMSINSTAL.COM. Note that each software product that you install might not require you to follow all of the guidelines listed in this section.

3.3.1 Performing Preliminary Operations

Before you use VMSINSTAL.COM, perform the following operations (not necessarily in the order listed):

• Back up your system disk, as described in Section 11.17. Use the backup copy as a working copy for the installation.
  VMSINSTAL.COM might delete the older version of the product before it installs the newer version. If the system fails during installation, you might have to make a new working copy of the system disk and restart the installation.
• Log in to the SYSTEM account at the console terminal.
• Be sure all users have logged out and all batch jobs have completed by using, respectively, the SHOW USERS and SHOW SYSTEM/BATCH commands. Keep users off the system until VMSINSTAL.COM completes by using the following command:

  $ SET LOGINS/INTERACTIVE=0

  Note If you cannot log off all users during the installation of a layered product that updates the DCL help library, note that the help files for that layered product will not be installed if a user on the system is accessing DCL help. The installation procedure generates warning messages and stores the help files in a working directory.

• Shut down network software.
• Check system parameters. (GBLPAGES, GBLSECTIONS and NPAGEDYN often need to be adjusted.) Read the documentation supplied with each layered product to be installed, and find out if the product has any specific resource requirements.
  If you must change parameter values, increase the values by adding ADD_ parameter-name symbols to MODPARAMS.DAT. (See Section 15.5.1.1.)
  Use AUTOGEN with feedback to size the system resources properly. (See Section 15.4.1.)
• Make sure the limits in the SYSTEM account authorization record are equal to or greater than the recommended limits.
  To check these limits, run the Authorize utility (AUTHORIZE) to display the current limits of the SYSTEM account's user authorization file.
  To run AUTHORIZE, enter the following commands:

  $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE

  
  At the UAF prompt (UAF>), enter the following command:

  UAF> SHOW SYSTEM

  
  See Section 7.1.2 for details.
• If necessary, use the Authorize utility to modify the SYSTEM account limits. Changes you make do not take effect until you log out and log in again.
  For example, to increase the DIOLM limit to 100, enter the following command:

  UAF> MODIFY SYSTEM/DIOLM=100

  
  See Section 7.1.2 for details.
• Physically mount the first distribution media that contains the software product. See Section 9.5 for details.
• Register and load licenses, as explained in the next section.

A license refers to the authorization you have to use a product. The License Management Facility (LMF) enables you to register, manage, and track software licenses on line.

A Product Authorization Key (PAK) contains information that is provided for many Compaq 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:

1. Log in to the system manager's account, SYSTEM.
2. Register the license in one of two ways:
   • Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data listed on your operating system PAK. (You can register other software product licenses at this time as well.)
   • At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information.
3. Use either of the following utilities to load a license:
   • License Management Facility (LMF), which loads the PAK only on the local node.
   • System Management utility (SYSMAN), which allows you to load the PAK throughout an entire cluster. (SYSMAN LICENSE commands are a subset of LMF commands.)
   
   Only the local node requires the installation of a license before you use VMSINSTAL.COM.

For more information about loading licenses, refer to the OpenVMS License Management Utility Manual.

3.3.3 Preventing Nodes from Sharing PAKs

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, perform the following actions:

1. Add the NO_SHARE option to the PAK or PAKs causing the NOCOMB warnings.
2. Assign each PAK to a specific OpenVMS Cluster node.

Before you run VMSINSTAL.COM, note the following points:

• Read the installation instructions for the specific product or update. If you need assistance during an installation, enter a question mark (?) for an explanation of possible responses.
• When you first start VMSINSTAL.COM, the procedure displays several prompts and messages that direct and explain the installation. These prompts and messages differ, depending on the software product that you are installing.
• When the procedure asks if you are satisfied with the backup of your system disk, back up your system disk before continuing with the installation if you do not have a recent backup of your system disk.
• If you do not satisfy all conditions required to start VMSINSTAL.COM, the procedure displays a warning message explaining the problem and asks you if you want to continue. Compaq strongly recommends that you satisfy these conditions before you try to start VMSINSTAL.COM again.

  Caution If you continue the procedure without making the required corrections, Compaq cannot guarantee that the installation will be supported.

How to Perform This Task

To run VMSINSTAL.COM, enter a command in the following format:

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:

Section 3.4.6 explains how to complete an installation.