[Digital logo]
[HR]

OpenVMS System Manager's Manual


Previous | Contents

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.
$

2.5.3 Using VMSKITBLD.COM to Add an Alternate System Root Directory

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.


Note

Do not use the ADD option to create a system root to add a new system to an OpenVMS Cluster environment. Instead, use the SYS$MANAGER:CLUSTER_CONFIG.COM procedure.

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 on calculating size for page, swap, and dump files, see Section 15.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 Digital 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.
    5. 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.
      $ 
      

      2.5.3.1 Configuring a System Root Added with VMSKITBLD

      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> 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 14.5 and the OpenVMS System Management Utilities Reference Manual (AUTOGEN) for detailed information on AUTOGEN.

      Example

      SYSBOOT> USE DEFAULT
      SYSBOOT> CONTINUE
         .
         .
         .
      $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT CHECK_FEEDBACK
         .
         .
         .
       
       
      


      Chapter 3
      Installing, Upgrading, and Updating Software

      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 Alpha operating system, use the POLYCENTER Software Installation utility. To install or upgrade the OpenVMS VAX operating system, use the VMSINSTAL.COM command procedure.

      Layered Product Software

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

      Information Provided in This Chapter

      This chapter describes the following tasks:
      Task Section
      Installing the OpenVMS operating system Section 3.1
      Installing layered product software Section 3.3
      Using VMSINSTAL.COM to install layered software Section 3.4 through Section 3.7
      Using the POLYCENTER Software Installation utility Section 3.8 through Section 3.11

      This chapter explains the following concepts:
      Concept Section
      VMSINSTAL.COM Section 3.4
      POLYCENTER Software Installation utility Section 3.8

      3.1 Installing, Upgrading, and Updating the Operating System

      The following sections explain how to install, upgrade, and update the OpenVMS operating system. For additional information, refer also to the following:
      • On VAX systems, see 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, see the most recent version of the OpenVMS Alpha Upgrade and Installation Manual.

      Understanding Installation, Upgrade, and Update Procedures

      The installation of software can mean a complete installation, an upgrade, or an update. The terms have the following meanings:
      Installation Used to install a completely new version of the operating system.
      Upgrade Used to make major changes to an existing version of the operating system.
      Update Used to make minor changes to an existing version of the operating system.

      3.1.1 Installing or Upgrading the OpenVMS Alpha Operating System

      To install or upgrade the OpenVMS Alpha operating system, boot the OpenVMS Alpha operating system CD--ROM from the local drive or from a drive connected to an InfoServer system. After you enter the appropriate boot command, a command procedure displays a menu that lists the following options:

      • Install or upgrade OpenVMS Alpha, using the POLYCENTER Software Installation utility
      • List layered product kits that the procedure can install
      • Install or upgrade layered products, using the POLYCENTER Software Installation utility
      • Show installed products
      • Reconfigure installed products
      • Remove installed products
      • Execute DCL commands and procedures, from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk
      • Shut down the system

      When you choose the install or upgrade OpenVMS Alpha option, the system asks whether you want to initialize or preserve the system disk. Depending on the option you choose, the POLYCENTER Software Installation utility installs or upgrades the OpenVMS Alpha operating system. For example:

      • If you choose to initialize the system disk (INITIALIZE), the utility performs these operations:
        • Removes all software and data files that were previously on the target disk
        • Installs the OpenVMS Alpha operating system

        Caution

        Initializing the target disk erases its contents. For this reason, use the installation procedure only on new computers or if you are sure you want to replace the entire contents of the target disk with new system files.

      • If you choose to preserve the system disk (PRESERVE) and the OpenVMS Alpha operating system is not already installed on the target disk, the utility performs these operations:
        • Installs the OpenVMS Alpha operating system
        • Retains, or preserves, all other contents of the target disk
      • If you choose PRESERVE and the OpenVMS Alpha operating system is installed on the target disk, the utility upgrades your system, as follows:
        • Merges and replaces old operating system files and new files
        • Retains, or preserves, all other contents of the target disk

        Caution

        The upgrade procedure does not work correctly if you have changed the names of system directories on your system disk. Restore the names of the original system directories on the system disk before attempting an upgrade. (Check the DEC-AXPVMS-VMS-*-2.PCSI$DESCRIPTION file in SYS$SYSDEVICE:[VMS$COMMON] for original system directory names.)

      For information about booting the OpenVMS Alpha operating system CD--ROM and choosing the INITIALIZE or PRESERVE options, see the current OpenVMS Alpha Upgrade and Installation Manual.

      3.1.2 Installing or Upgrading from a Running Alpha System

      You can install or upgrade an OpenVMS Alpha system to a target system disk using the OpenVMS Alpha system disk from which you are booted as the source disk for the product. To install or upgrade in this manner, execute AXPVMS$PCSI_INSTALL.COM in SYS$SYSTEM. This procedure is the same installation procedure that installs or upgrades OpenVMS Alpha from the OpenVMS Alpha operating system CD--ROM. (The procedure is similar to using VMSKITBLD.COM, which is no longer supported on Alpha systems.) Privileges required by the procedure are:
      BYPASS OPER
      CMKRNL SYSPRV
      LOG_IO VOLPRO

      The procedure attempts to turn on these privileges but if it cannot, it reports an error and exits. Your original privilege settings are restored.

      Execute the following command to run the installation or upgrade procedure:

      $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL.COM 
      

      The operation of AXPVMS$PCSI_INSTALL.COM is documented in the current OpenVMS Alpha Upgrade and Installation Manual. Before you execute this command procedure, read the appropriate chapters in that manual. Refer to Table 3-1 and Table 3-2.

      Table 3-1 If You Are Installing
      Read chapter... To find information about...
      Preparing to Install What to do before running AXPVMS$PCSI_INSTALL.COM
      Installing How to use AXPVMS$PCSI_INSTALL.COM
      After Installing What to do after an installation

      Table 3-2 If You Are Upgrading
      Read chapter... To find information about...
      Preparing to Upgrade and
      Before Upgrading
      What to do before running AXPVMS$PCSI_INSTALL.COM
      Upgrading How to use AXPVMS$PCSI_INSTALL.COM
      After Upgrading What to do after an upgrade

      3.1.3 Installing the OpenVMS VAX Operating System

      When you install the OpenVMS VAX operating system, the installation procedure does the following:

      • Initializes the system disk, erasing its contents
      • Creates a system directory structure on the new system disk
      • Transfers system files from the distribution media to the new system disk

      Caution

      The installation procedure initializes the target disk, erasing its contents. For this reason, use the installation procedure only on new computers or if you are sure you want to replace the entire contents of the target disk with new system files.

      You use the installation procedure under the following conditions:

      • If your VAX computer is new; that is, if it has never had any version of the operating system running on it.
      • If your computer is running a version of the OpenVMS VAX operating system and you are sure you are willing to destroy the entire contents of the system disk, including both system and user files.
      • If you are running the OpenVMS VAX operating system, but are not able to perform an upgrade. For example, if you do not have a standard version of the OpenVMS VAX operating system on your system disk, the upgrade procedure might not work correctly.
      • If you want to run the OpenVMS VAX operating system in a C2 security environment.

      To install the OpenVMS VAX operating system, follow the installation procedures in the current OpenVMS VAX Upgrade and Installation Manual.

      3.1.4 Upgrading the OpenVMS VAX Operating System

      When you upgrade the operating system, the upgrade procedure does the following:

      • Makes room for the upgrade by purging and deleting most system files but leaves some system files and all user files intact. The upgrade also leaves most layered products intact. In some cases, reinstalling layered products after you upgrade may be necessary.
      • Transfers the system files from the distribution media to the system disk.
      • Merges old system libraries with new libraries.
      • Cleans up files and directories used only during the upgrade.

      In most cases, if you are already running a standard version of the operating system, you can use the upgrade procedure to obtain the next highest version. The upgrade procedure does not initialize the system disk.


      Caution

      The upgrade procedure does not work correctly if you have changed the names of system directories on your system disk. Restore the names of the original system directories on the system disk before attempting an upgrade. (Check the VMSKITBLD.DAT file in SYS$UPDATE for original system directory names.)

      To perform an upgrade of the OpenVMS VAX operating system, follow the upgrade procedures in the current OpenVMS VAX Upgrade and Installation Manual.

      3.1.5 Updating the OpenVMS Alpha or OpenVMS VAX Operating System

      An update procedure makes minor changes to the operating system. When you update the operating system, the update procedure replaces some system files and applies patches to others (if necessary).

      The two types of updates are:

      • A required update you perform after installing or upgrading the operating system is referred to as a mandatory update. The directions for an installation or an upgrade indicate when to perform a mandatory update.
      • Another type of update allows you to apply a special release of the operating system, which might include new features, support for new hardware, or refinements to specific software components. Instructions for applying such an update are included with the specific release.

      Caution

      The update procedure does not work correctly if you have changed the names of system directories on your system disk. Restore the names of system directories before attempting an update. (On VAX systems, check the VMSKITBLD.DAT file in SYS$UPDATE for original system directory names. On Alpha systems, check the DEC-AXPVMS-VMS-*-2.PCSI$DESCRIPTION file in SYS$SYSDEVICE:[VMS$COMMON] for original system directory names.)

      Follow the instructions provided with the update kit. The instructions will indicate whether to use VMSINSTAL.COM or the POLYCENTER Software Installation utility.

      3.2 Removing the OpenVMS Alpha Operating System (Alpha Only)

      If you want to remove the operating system from your disk, you can do so in one of two ways:

      • If the disk contains a small number of user files, copy those user files elsewhere and then reinitialize the disk.
      • If the disk contains many user files, use the PRODUCT REMOVE command to remove an obsolete or extra copy of the OpenVMS Alpha operating system without removing any of the user files. Note that you must also delete or archive certain operating system files that the PRODUCT REMOVE command cannot delete. The following procedure describes this method of removing the operating system.

      How to Perform This Task

      Follow these steps to remove OpenVMS Alpha operating system files:

      1. If your system disk has multiple system-specific roots, boot the system and execute SYS$MANAGER:CLUSTER_CONFIG.COM to remove all roots except the one from which you are booted.
      2. Shut down and boot from the distribution CD--ROM or from a system disk other than the one from which OpenVMS Alpha is being removed. Then do one of the following:
        • If OpenVMS Alpha is not running from the distribution CD--ROM, log in to a privileged account.
        • If OpenVMS Alpha is running from the distribution CD--ROM, choose the option to execute DCL commands.
      3. Enter the following DCL commands:
        $ DEFINE/NOLOG PCSI$SYSDEVICE target-disk 
        $ DEFINE/NOLOG PCSI$SPECIFIC target-disk:[SYSx.] 
        $ DEFINE/NOLOG PCSI$DESTINATION target-disk:[VMS$COMMON] 
        $ PRODUCT REMOVE VMS /REMOTE 
        

        where:
        • target-disk is the device name of the disk from which OpenVMS Alpha is being removed.
        • SYSx is the root number that you did not remove in step 1.
      4. If the disk also contains layered products that were installed using the POLYCENTER Software Installation utility, Digital recommends that you remove them as well. Use the following command to remove all the products at once:
        $ PRODUCT REMOVE * /REMOTE
        

        Use the following commands to remove individual products:
        $ PRODUCT SHOW PRODUCT/REMOTE
        $ PRODUCT REMOVE product-name /REMOTE
        
      5. Because the PRODUCT REMOVE command does not delete certain files, review the target disk to determine if you want to delete, move, or archive the operating system files that still remain on the disk.
        Following are lists of the files that the PRODUCT REMOVE command does not delete:
        • In target-disk:[SYS*.SYSEXE], where * is 0 or the hexadecimal number of any additional OpenVMS Cluster roots on the target disk:
          • ALPHAVMSSYS.PAR
          • MODPARAMS.DAT
          • PAGEFILE.SYS
          • SWAPFILE.SYS
        • In target-disk:[VMS$COMMON.SYSEXE]:
          • LMF$LICENSE.LDB
          • PCSI$FILE_SYSTEM.PCSI$DATABASE
          • PCSI$PROCESSOR.PCSI$DATABASE
          • PCSI$ROOT.PCSI$DATABASE
          • RIGHTSLIST.DAT
          • SYSUAF.DAT

        As you examine the preceding lists of files, you might want to archive, rather than delete, the following files:
        • ALPHAVMSSYS.PAR
        • MODPARAMS.DAT
        • LMF$LICENSE.LDB
        • RIGHTSLIST.DAT
        • SYSUAF.DAT
      6. Review the target disk for the directory structures [VMS$COMMON...] and [SYSx...], which will remain after you remove OpenVMS Alpha. You might want to delete these directories.

        3.3 Installing or Upgrading Layered Products

        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.4
          Running VMSINSTAL.COM Section 3.5
          Recovering from a system failure Section 3.6
          Selecting VMSINSTAL.COM options Section 3.7

          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.8 and to the layered product installation documentation.
          Task Section
          Using the POLYCENTER Software Installation utility Section 3.8
          Installing software Section 3.9
          Performing operations on installed software Section 3.10
          Removing installed software Section 3.11

        3.4 Preparing Your System to Run VMSINSTAL.COM

        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.4.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 10.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 DECnet for OpenVMS.
        • 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 14.5.1.1.)
          Use AUTOGEN with feedback to size the system resources properly. (See Section 14.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 6.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 6.1.2 for details.
        • Physically mount the first distribution media that contains the software product. See Section 8.5 for details.
        • Register and load licenses, as explained in the next section.

        3.4.2 Registering and Loading Licenses

        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.


        Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]

        [HR]

          6017P003.HTM
          OSSG Documentation
          22-NOV-1996 14:21:20.34
        

        Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

        Legal