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
$ @SYS$UPDATE:VMSKITBLDVMSKITBLD prompts you to choose one of the following options:
Operation [BUILD,ADD,COPY]?
* Enter mounted SOURCE disk name (ddcu:):
* Enter SOURCE disk top level system directory [default = SYS0]:
* Enter TARGET disk name (ddcu:):
* Enter TARGET disk top level system directory [default = SYS0]:
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.
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
$ @SYS$UPDATE:VMSKITBLDVMSKITBLD prompts you to choose one of the following options:
Operation [BUILD,ADD,COPY]?
* Enter mounted SOURCE disk name (ddcu:):
* Enter SOURCE disk top level system directory [default = SYS0]:
* Enter TARGET disk name (ddcu:):
* Enter TARGET disk top level system directory [default = SYS0]:
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:
SYSBOOT> USE DEFAULT SYSBOOT> CONTINUE
Example
SYSBOOT> USE DEFAULT 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 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 |
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. |
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:
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:
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.
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.
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.
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 |
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 |
When you install the OpenVMS VAX operating system, the installation procedure does the following:
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:
To install the OpenVMS VAX operating system, follow the installation procedures in the current OpenVMS VAX Upgrade and Installation Manual.
When you upgrade the operating system, the upgrade procedure does the following:
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.
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:
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.
If you want to remove the operating system from your disk, you can do so in one of two ways:
How to Perform This Task
Follow these steps to remove OpenVMS Alpha operating system files:
$ 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
$ PRODUCT REMOVE * /REMOTE
$ PRODUCT SHOW PRODUCT/REMOTE $ PRODUCT REMOVE product-name /REMOTE
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:
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 |
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 |
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.
Before you use VMSINSTAL.COM, perform the following operations (not necessarily in the order listed):
$ 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.
$ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE
UAF> SHOW SYSTEM
UAF> MODIFY SYSTEM/DIOLM=100
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.
6017P003.HTM OSSG Documentation 22-NOV-1996 14:21:20.34
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.