Document revision date: 19 July 1999

The OpenVMS VAX Version 7.2 kit is available on two, 6250 BPI, open reel magnetic tapes or on two TK50 CompacTape cartridges. (Earlier versions of OpenVMS VAX shipped on four magnetic tapes.)

The first tape or cartridge contains the VMS072.A, VMS072.B, and VMS072.C save sets. The second tape or cartridge contains standalone BACKUP (TK50 tape cartridge only), the VMS072.D, VMS072.E, and VMS072.F save sets, and the DECW072.C, DECV072.D, DECW072.E, and DECW072.F save sets.

The DECamds software (AMDS) is included on the OpenVMS VAX distribution media. The AMDS kit is located on the second magnetic tape or TK50 CompacTape cartridge, and on the compact disc in the [AMDS072] directory.

The Monitoring Performance History (MPH) kit is also included on the OpenVMS VAX distribution media. The MPH kit is located on the second magnetic tape or TK50 CompacTape cartridge and on the compact disc in the [MPH] directory.

1.3.4 Software Product Descriptions (SPDs)

If your distribution kit is on compact disc, the SPD files are located in the [DOCUMENTATION.V072] directory. For information about locating and printing these SPD files, refer to the Guide to OpenVMS Version 7.2 CD--ROMs.

The following SPD files are located on the second TK50 CompacTape cartridge and the second magnetic tape. These SPD files have been grouped into an OpenVMS BACKUP save set named VMS072_SPD.BCK. File names with the .PS extension are in PostScript format. File names with the .TXT extension are in ASCII (plain text) format.

DECNET_SPD.PS DECNET_SPD.TXT	DECnet-Plus for OpenVMS VAX and Alpha, Version 7.2
RMS_SPD.PS RMS_SPD.TXT	RMS Journaling for OpenVMS
CLUSTER_SPD.PS CLUSTER_SPD.TXT	OpenVMS Cluster Software
VOL_SHAD_SPD.PS VOL_SHAD_SPD.TXT	Volume Shadowing for OpenVMS

To obtain all the SPD files and restore them to your current default directory, enter a BACKUP command using the following format:

BACKUP source-drive:VMS072_SPD.BCK /SAVE_SET *.*;*

For source-drive, substitute the name of the device that holds your distribution kit. For example, if your source-drive is a local magnetic tape drive with the device name MUAO, you would enter the following command:

$ BACKUP MUAO:VMS072_SPD.BCK/SAVE_SET *.*;*

To restore all the SPD files in PostScript format to your default directory, enter the following:

$ BACKUP MUAO:VMS072_SPD.BCK/SAVE_SET/SELECT=*.PS *.*;*

The following command restores the PostScript SPD file for the OpenVMS VAX and OpenVMS Alpha operating systems to your current default directory:

$ BACKUP MUAO:VMS072_SPD.BCK/SAVE_SET/SELECT=OVMS_72_SPD.PS *.*;*

1.4 What Happens During an Installation

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

• Initializes the system disk, overwriting its contents.
• Creates a system directory structure.
• Transfers the OpenVMS VAX files from the distribution media to the system disk.

Use the installation procedure under the following conditions:

• If your VAX computer is new (it has never had any version of the operating system running on it, including factory-installed software).
• If your VAX computer is running a previous version of the operating system and you want to overwrite the entire contents of the system disk (the OpenVMS VAX operating system, application software, and user files).
• If you are running a previous version of the operating system, but you cannot upgrade. For example, if you changed the names of system directories on the system disk, the upgrade procedure will not work correctly. You can either restore the system disk to its original directory structure, or you can reinstall the OpenVMS VAX operating system.

This manual contains step-by-step instructions for performing an OpenVMS VAX installation. However, you will need to refer to several different documents before and during the installation. Figure 1-1 illustrates the major steps in an installation and the documents you will use to perform each step.

Figure 1-1 Documentation Used to Perform an Installation

1.5 What Happens During an Upgrade

• Deletes and purges some OpenVMS VAX files on the system disk but leaves all the user files intact.
• Transfers the new OpenVMS VAX files from the distribution media to the system disk.

  Note The upgrade procedure puts the most recent versions of the OpenVMS VAX files in the system common directories (SYS$COMMON). The upgrade procedure does not replace or delete any versions of these files in the system-specific directories (SYS$SPECIFIC). If there are previous versions of OpenVMS VAX files in the system-specific directories, the upgrade procedure or the upgraded system may not work correctly.

• Merges some of the old OpenVMS files and the new OpenVMS VAX files and replaces others.
  Certain OpenVMS VAX files are placed either over or under existing files (that is, they are given a version number above or below the version number of the existing file). This protects any customizations to the files and results in having two versions of the file when the upgrade is completed. For more information, see Appendix F.
• Cleans up files and structures used only during the upgrade.
• Leaves your OpenVMS license and System Integrated Product (SIP) licenses intact.
  You do not need to reinstall these licenses after you upgrade. (Refer to Appendix B for detailed information about license management for OpenVMS VAX Version 7.2.)

In most cases, you can use the upgrade procedure to obtain a higher version of the OpenVMS VAX operating system. Unlike the installation procedure, the upgrade procedure does not initialize your system disk. This means you can get the latest version of the operating system and keep your user files and optional software files intact.

1.5.2 How to Use the Upgrade Documentation

This manual contains step-by-step instructions for performing an OpenVMS VAX upgrade. However, you will need to refer to several different documents before and during an upgrade. Figure 1-2 illustrates the major steps in an upgrade and the documents you will use to perform each step.

Figure 1-2 Documentation Used to Perform an Upgrade

If you want to install the OpenVMS VAX operating system, go to Chapter 2.

If you are upgrading the OpenVMS VAX operating system, go to Chapter 5.

This chapter describes how to prepare for installing the OpenVMS VAX operating system, including:

• Being aware of the cautions and restrictions
• Ensuring your hardware is ready
• Ensuring your software distribution kit is complete
• Preparing for a VAXcluster environment
• Preparing your tape and disk drives
• Gathering the information you need to supply during the installation procedure
• Completing the preinstallation checklist

If you are an experienced system manager, you can use the checklist at the end of the chapter to complete all the necessary preinstallation tasks.

If you are a less-experienced system manager, you should read the entire chapter and then use the checklist to make sure you completed all the preinstallation tasks.

2.1 Cautions and Restrictions

Before you begin the installation procedure, note the following cautions and restrictions.

2.1.1 Cautions

The following cautions apply for Version 7.2 of the OpenVMS VAX operating system:

• The software installation procedure overwrites the contents of the system disk. Use the installation procedure only if your VAX computer is new or if you want to destroy the contents of the system disk. If your system disk contains files you want to save, you should upgrade to the new version of OpenVMS VAX. For an overview of the upgrade procedure, see Chapter 5.
• Do not attempt to use VMSINSTAL with OPTION G to transfer OpenVMS VAX save sets to another media type; doing so produces an unusable system. Instead, you can use the DCL command COPY to transfer save sets to another media type.
  If you move the save sets from the distribution media before beginning the installation, you must move them to the [000000] directory on a disk that is not the system disk; otherwise, the installation will fail.

The following restrictions apply for Version 7.2 of the OpenVMS VAX operating system:

• If your system contains DIGITAL Storage Systems Interconnect (DSSI) disks attached to a KFQSA controller, you will notice a change in the device names for DSSI disks attached to KFQSA controllers.
  When you boot standalone BACKUP, it displays the devices on your system using the new device naming scheme. Use the new device names throughout the installation and after you complete the installation.
• If you want to use DECwindows software with OpenVMS VAX Version 7.2, you must purchase and install the DECwindows Motif for OpenVMS Version 1.2--3, or higher, layered product. For more information, see Section 1.1.2.

Before beginning an installation or upgrade, be sure you have all the required hardware and software components, as described in the following sections.

2.2.1 Hardware Components

Before you begin an installation or upgrade, do the following:

• Be sure the hardware has been installed and checked for proper operation. For detailed information, refer to the hardware manuals you received with your VAX computer.
• Be sure you know how to turn on and operate the components of your system, including the system unit, console, monitor, drives, terminals, and printers. If necessary, read the hardware manuals that came with these components.
• Set up your system to record the installation procedure on either a hardcopy terminal or a printer attached to the console terminal. (Refer to your hardware manuals for more details about connecting those components to your system.) If you do not do this, the screen messages will be lost. You need a transcript in case there is a problem during the installation.

Before you begin an installation or upgrade, do the following:

• Be sure you have all the items listed on the bill of materials in the distribution kit. If your distribution kit is incomplete, notify your Compaq support representative and request priority shipment of any missing items.
• Before installing the OpenVMS VAX operating system software, review all cover letters and release notes.
• Read the Before Installing OpenVMS section in the installation and upgrade supplement for your VAX computer, which describes tasks specific to your VAX computer that you must complete before beginning the installation.

Now that you have determined that your hardware and software components are ready, you can make the necessary preparations for installing the OpenVMS VAX operating system.

2.3.1 Preparing for a VAXcluster Environment

If you are installing the OpenVMS VAX operating system in a VAXcluster environment, the installation procedure displays information about cluster configuration. But, because there is no network present on the system at this point in the procedure, no cluster configuration work can actually be performed at this time. Before proceeding, review OpenVMS Cluster Systems, which provides the information you need to answer questions during the installation.

Table 2-1 lists the VAXcluster information you need and explains how to obtain that information. For a complete explanation, refer to OpenVMS Cluster Systems.

Table 2-1 VAXcluster Information for Installations

Information You Need	How to Get It
Type of configuration	Configuration types are distinguished by the interconnect device that the VAX computers in the cluster use to communicate with one another: Computer Interconnect (CI), Ethernet, DIGITAL Storage Systems Interconnect (DSSI), or FDDI (Fiber Distributed Data Interface).
DECnet node name and node address	Determined by the network or system manager for each VAX computer on the network. See your system or network manager for the DECnet node name and node address for the VAX computer on which you are installing the OpenVMS VAX operating system. Refer to the DECnet-Plus for OpenVMS Installation and Configuration manual for more information.
Allocation class value	During the installation procedure you are asked for the ALLOCLASS value of the VAX computer on which you are installing the OpenVMS VAX operating system. For example: Enter a value for MYNODE's ALLOCLASS parameter: Refer to OpenVMS Cluster Systems for the rules on specifying allocation class values. Note that, in a mixed-interconnect VAXcluster environment, the allocation class value cannot be zero. It has to be a value between 1 and 255. This is also true for any VAX computer connected to a dual-pathed disk. When you enter the allocation class value, the installation procedure uses it to set the value of the ALLOCLASS system parameter automatically.
Quorum disk	Refer to OpenVMS Cluster Systems to determine whether you want a quorum disk in the cluster.
Location for page and swap files	Refer to OpenVMS Cluster Systems to determine where the page and swap files will be located for the system from which you are installing the OpenVMS VAX operating system software.
MOP servers, disk servers, tape servers	To establish either a local area or a mixed-interconnect cluster, determine which systems will be Maintenance Operations Protocol (MOP) servers, disk servers, and tape servers. Refer to OpenVMS Cluster Systems.
Cluster group number and cluster password	To establish either a local area or a mixed-interconnect cluster: Cluster group number - A number in the range from 1 to 4095 or from 61440 to 65535 Cluster password - Can range from 1 to 31 alphanumeric characters, including dollar signs ($) and underscores (_)

2.3.2 Preparing Tape and Disk Drives

Prepare your tape and disk drives using the following steps:

1. Decide which drive will hold the distribution media and which drive will hold the system disk. Determine the device names for each drive. You will need this information throughout the installation. If you need information about devices and device names, refer to the Before Installing the OpenVMS Operating System section in the upgrade and installation supplement for your VAX computer.

   Note Do not place the distribution media in the drive at this point.

2. Follow this step only if the source drive or target drive is attached to an HSx device. Otherwise, go to step 3.
   Make sure that both the CI and HSx devices are turned on and are on line. Obtain the HSx name from the system manager, or use the following procedure:
   1. Press Ctrl/C at the HSx console terminal.
   2. Enter the following command at the HSx> prompt and press Return:

      HSx> SHOW SYSTEM

      
      The information displayed includes the name of the HSx. For example:

      11-SEP-1998 15:00:00.00 Boot:11-SEP-1998 11:31:11.41 Up: 51:00 Version V350 System ID: %X000000011 Name: MUTT . . . DISK allocation class = 1 TAPE allocation class = 0 Start command file Disabled SETSHO - Program Exit

      
      For more information, refer to the x User's Guide.

3. Place a scratch disk in the drive for the system disk (unless the system disk is fixed).
4. Spin up the disk that will be the system disk but do not write protect it.

During the installation, the procedure prompts you to supply certain information. To save time once the procedure begins, be sure you have the following information available. Remember, entering incorrect information during the installation could force you to repeat the entire installation procedure.

Required Information	Explanation
Passwords	You will be prompted to type passwords of at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts.
SCSNODE and SCSSYSTEMID parameters	You will be prompted to supply an SCSNODE name and an SCSSYSTEMID system parameter. The SCSNODE name must be a 1- to 6-character name; the SCSSYSTEMID system parameter is a number in the range of 1025 to 65535. If you will be using DECnet Phase IV or DECnet-Plus with Phase IV compatible addresses, then SCSNODE must be the DECnet node name, and SCSSYSTEMID must be calculated from the DECnet address as follows: (DECnet-area * 1024) + DECnet-node-number
Optional components and OpenVMS Management Station files	The installation procedure prompts you to specify whether you want to install the library (VMS072.C), optional (VMS072.D) OpenVMS components, and OpenVMS Management Station software PC files (VMS072.F). Appendix D lists the files included in these save sets. You can save some space on your system disk if you choose not to install these components, but be sure to review Appendix D before deciding.
Location for Help Message utility	Save set VMS072.E contains the online Help Message utility, which you can install on your system disk or on an alternate disk. (However, if you copied the distribution kit to some other media from which you will be performing the installation, you cannot install this save set on that media.)
DECwindows components	The installation procedure prompts you to specify which of the following DECwindows components you want to install: DECwindows base support (required for running DECwindows software), which includes: DECwindows transport DECwindows keymaps DECwindows workstation support (required for VAX workstations), which includes: DECwindows X11 display server Graphics drivers 75 dots/inch video fonts 100 dots/inch video fonts (option available only if you select DECwindows workstation support) You must install the DECwindows Motif for OpenVMS (previously called VMS DECwindows Motif) layered product if you want to run the DECwindows software. DECwindows Motif for OpenVMS Version 1.2--3 (or 1.2 if the VAXMOTF05_012 remedial kit is installed) is the minimum supported version for systems running OpenVMS VAX Version 7.2. If you do not know which version of DECwindows Motif you are currently running on your system, you can check by entering the following command: $ ANALYZE/IMAGE SYS$LIBRARY:DECW$XLIBSHR.EXE Note that the DECwindows Motif for OpenVMS layered product does not have the DECwindows base and workstation support components. To get full DECwindows support, you must select the DECwindows components provided with the OpenVMS VAX kit and install the separate DECwindows Motif for OpenVMS layered product, which supports both Motif and XUI environments.
PAK information	The information listed on Product Authorization Keys (PAKs) for your OpenVMS VAX license and any system integrated products you will run. The installation procedure gives you the opportunity to register any licenses you have. To register your licenses, you will need to enter the information listed on the PAK for each license.

	privacy and legal statement
6521PRO_001.HTML