Document revision date: 19 July 1999

Before you begin the installation, use the following checklist to make sure you have completed all of the tasks described in this chapter:

• Read the cautions and restrictions described at the beginning of this chapter.
• Make sure the hardware is installed and tested. (Described in the hardware manuals for your VAX computer)
• Check the contents of your kit against the bill of materials (BOM).
• Read Appendix B of this manual, the OpenVMS Version 7.2 New Features Manual, the OpenVMS Version 7.2 Release Notes, and any cover letters included with your kit.
• Turn on the system. (Described in the upgrade and installation supplement for your VAX computer)
• Set up your system to record the installation procedure. (Described in the upgrade and installation supplement for your VAX computer)
• Read the Before Installing OpenVMS section in the upgrade and installation supplement for your VAX computer and perform the tasks described there.
• Make sure you have the most recent version of the console media if you have a VAX computer that uses console media. (Described in the upgrade and installation supplement for your VAX computer)
• Determine whether you want a CI only, local area, or mixed-interconnect cluster if you are installing the OpenVMS VAX operating system on a VAX computer in a VAXcluster environment. (Described in OpenVMS Cluster Systems)
  You should have the following information, depending on the type of VAXcluster:
  • CI Only VAXcluster: Get the allocation class value, DECnet node name, and DECnet node address for the computer. You also need to decide if you want a quorum disk and where the page and swap files for the system from which you are installing will be located.
  • Local Area and Mixed-Interconnect VAXclusters: Get the allocation class value, the DECnet node name, the DECnet node address, the cluster group number, and the cluster password. You also need to decide if you want a quorum disk and where the page and swap files for the system from which you are installing will be located.
• Prepare the disk and tape drives. (Described in Section 2.3.2)
• Make sure you have the following information (described in Section 2.3.3) available:
  • Passwords containing at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts.
  • SCSNODE and SCSSYSTEMID if you are installing a standalone system.

  • A list of optional OpenVMS VAX components you want to install.
  • A list of optional DECwindows support components you want to install.
  • Information listed on Product Authorization Keys (PAKs) for your OpenVMS VAX license and any system integrated products you will run.

After you have performed all the tasks in the checklist, go to Chapter 3 to begin the installation.

During the installation procedure, OpenVMS VAX files are transferred from the distribution media to the system disk or, for certain files, to an alternate disk. The time required to complete an installation varies depending on your hardware configuration and on the distribution media you are using. In most cases, magnetic tapes and tape cartridges require more time than compact discs.

This chapter describes the following installation tasks:

• Booting standalone BACKUP
• Creating the system disk
• Configuring a cluster
• Setting passwords
• Creating the rights database
• Registering licenses
• Running AUTOGEN

At certain points in the procedure you will need to refer to the upgrade and installation supplement for installation instructions that are specific to your VAX computer.

3.1 Booting Standalone BACKUP

Standalone BACKUP is a subset of the OpenVMS Backup utility (BACKUP). Because you boot it into main memory, standalone BACKUP executes outside the control of the operating system. You use standalone BACKUP to restore the required save sets from the distribution media to your system disk.

To boot a standalone BACKUP environment, enter the following:

>>> B DKA400

Standalone BACKUP is included in the OpenVMS VAX distribution kit. Each piece of media in the distribution kit has a label that indicates its contents. For example, there are two CompacTape cartridges in a TK50 kit. Standalone BACKUP is on the second tape cartridge.

3.1.1 Booting from Tape Cartridge

If your distribution media is contained on TK50 CompacTape cartridges, complete the following steps to boot standalone BACKUP. (If you are using an InfoServer device, go to Section 3.1.2.)

1. Place the media that contains standalone BACKUP in the source drive or in the console drive.
2. Follow the instructions in the Booting Standalone BACKUP section of the upgrade and installation supplement for your VAX computer.
3. After you boot standalone BACKUP, the system displays the following message:

   %BACKUP-I-IDENT, standalone BACKUP V7.2; the date is 13-NOV-1998 10:00 $

After you have booted standalone BACKUP, go to Section 3.2.

3.1.2 Booting from the InfoServer

If you are using the InfoServer to boot standalone BACKUP from a compact disc, complete the following steps:

1. Insert the distribution compact disc into the drive.
2. Follow the instructions in the Booting Standalone BACKUP section of the upgrade and installation supplement for your VAX computer.
3. Enter your VAX processor boot command by using the designator for the Ethernet adapter in the boot path and, except for the VAX 9000 computer, add the /R5:100 qualifier to the boot command.
   For example, on a VAX 6000 computer, enter:

   >>> B/R5:100/X:D/B:6 ET0

   
   On VAX 9000 computers, standalone BACKUP resides on the console hard disk. Because the boot process is slightly different for each type of controller, each supported controller has a unique boot command procedure. Refer to the upgrade and installation supplement for your VAX 9000 computer for instructions for booting standalone BACKUP on your system.

4. During an InfoServer boot, the procedure prompts you for a file name that contains an initial system load (ISL) boot program instead of a virtual memory boot (VMB) program. Select one of the two files as follows:
   • ISL_SVAX_072
   • ISL_LVAX_072
   
   Use the following table to determine which file name and boot path designator to use for your processor. Note that the VAX 9000 computer has the ISL file data built in its VMB image that runs from the console.

   Processor Series	ISL File	Boot Path Designator
   VAX 3000	ISL_SVAX_072	ESA0 (LANCE), XQA0 (DELQA)
   VAX 4000	ISL_SVAX_072	EZA0 (SGEC), XQA0 (DELQA)
   VAX 6000	ISL_LVAX_072	EXA0 (DEMNA), FXA0 (DEMFA), ETA0 (DEBNI) (DEBNA)
   VAX 7000	ISL_LVAX_072	EXA0 (DEMNA), FXA0 (DEMFA)
   VAX 10000	ISL_LVAX_072	EXA0 (DEMNA), FXA0 (DEMFA)
   MicroVAX	ISL_SVAX_072	ESA0 (LANCE), XQA0 (DELQA)
   VAXstation	ISL_SVAX_072	ESA0 (LANCE)
   VAXft 110, 310, 410, 610, and 612	ISL_SVAX_072	EPA0 (LANCE)

   
   On a VAX 6000 computer, respond to the prompt as shown in the following example:

   Loading system software. Filename: ISL_LVAX_072

5. The InfoServer ISL program then displays the following menu:

   Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value: 3

   
   Enter 3, as shown in the previous display, for the function ID value. The following menu is displayed:

   OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2

   
   Enter 2 for the Option ID value. The following is displayed:

   Enter a Known Service Name:

   
   Enter the ISL file name for your processor series from the previous table.
   If you need more information, select function ID 2 for help.

6. After you boot standalone BACKUP, the system displays the following:

   %BACKUP-I-IDENT, standalone BACKUP V7.2; the date is 11-NOV-1998 10:00 $

After you have booted standalone BACKUP, go to Section 3.2.

3.1.3 Booting from the CD-ROM

If you are installing from the OpenVMS VAX operating system CD-ROM (your VAX computer supports booting from a local CD-ROM or from an InfoServer), you can use the full OpenVMS environment instead of the standalone BACKUP environment to transfer the VMS072.B save set to your target system disk.

Although it may take slightly longer to boot OpenVMS than to boot standalone backup, you might prefer the more robust OpenVMS environment. It provides a greater range of commands and utilities than the standalone BACKUP environment.

If you want to use the full OpenVMS environment, follow these steps:

1. Boot the CD-ROM and specify root 1. For example, from a local drive on a VAXstation 4000 computer, enter:

   >>> B/R5:10000000 DKA400:

   
   If you are booting from an InfoServer device, enter a command that specifies root 1. For example, on a VAX 6000 compute, enter:

   >>> B/R5:10000100/X:D/B:6 ET0

2. After you boot the OpenVMS CD-ROM, the system displays the following menu:

   1) Execute DCL commands and procedures 2) Shut down this system

   
   Choose option 1 to execute DCL commands and procedures.
   The system displays a triple dollar sign ($$$) DCL prompt to indicate that you are in this specialized DCL environment.
   You can ignore the following SYSINIT errors if they appear:

   %SYSINIT-E, %SYSINIT, error opening system dump file, status = 00000910 %SYSINIT, primary PAGEFILE.SYS not found; system initialization continuing %SYSINIT, no dump file - error log buffers not saved %SYSINIT-E, error mounting system device, status = 007282EC

   Important Note During the installation, do not change the displayed system time, even if it is incorrect. Attempting to change this value results in a write lock error that requires a CD reboot.

3. Go to Section 3.2.3 to transfer the VMS072.B save set to your system disk.

You create an OpenVMS VAX Version 7.2 system disk by transferring OpenVMS VAX files from the distribution media to your system disk. (For certain files, you have the option to transfer the files to your system disk or to an alternate disk.)

To transfer the OpenVMS VAX files from the distribution kit to your system disk, perform the steps described in the sections that follow.

3.2.1 Determining Device Names

If you have not already done so, determine the device names for the source drive, the target drive, and an alternate device if you will be using one. Write these names on a piece of paper. You will need this information throughout the installation. If either the source drive or the target drive is connected to an HSC, you also need the name of the HSC. (To determine the value for hsc-name, see Section 2.3.2 in Chapter 2.)

If you need more information about determining the device names for your system, refer to the upgrade and installation supplement for your VAX computer.

3.2.2 Loading Distribution Media

Each piece of media in the distribution kit has a label that indicates its contents. Place the media that contains the OpenVMS VAX operating system in the source-drive.

If your OpenVMS VAX distribution kit consists of more than one piece of media, place the first piece of media in the source-drive. For example, if you have a TK50 CompacTape cartridge kit, make sure the first tape is in the source-drive.

If you are installing from a compact disc, disc one of two is already in the drive.

3.2.3 Transferring VMS072.B to Your System Disk

Enter a BACKUP command in the following format to transfer the VMS072.B save set to your system disk:

$ BACKUP/IMAGE/VERIFY [hsc-name]source-drive:VMS072.B/SAVE_SET- _$ [hsc-name]target-drive:

Substitute the appropriate device names for hsc-name (if appropriate), source-drive, and target-drive. Make sure you put a colon (:) after each device name and that you use zeros rather than the letter "O" in the device names and in VMS072.

The square brackets ([]) indicate that you need the hsc-name only if the device is connected to an HSC.

For example, if your system has a source-drive that is a local TU80 magnetic tape drive with a device name of MUA0 and a target-drive that is an RA82 disk drive with a device name of DUA1, enter the following command and press Return:

$ BACKUP/IMAGE/VERIFY MUA0:VMS072.B/SAVE_SET DUA1:

If your system has a source-drive that is a local tape cartridge drive with a device name of MUC6 or a target-drive that is an RA81 disk drive with a device name of DUA1 and an HSC name of YOURS, enter the following command and press Return:

$ BACKUP/IMAGE/VERIFY MUC6:VMS072.B/SAVE_SET YOURS$DUA1:

The procedure transfers the VMS072.B save set from the distribution kit to the system disk. ¹ The amount of time this takes varies depending on the type of VAX computer and distribution media you have. During the process, the command displays the following message:

%BACKUP-I-STARTVERIFY, starting verification pass

This message indicates that the VMS072.B save set has been transferred to the system disk and the files are being checked for errors. If, instead, you see a message similar to the following, you might have the wrong volume of the distribution kit in the source drive:

% BACKUP-F-OPENIN, error opening MUA0:[000000]VMS072.B; as input - SYSTEM-W-NOSUCHFILE, no such file . . . If you do want to perform another standalone BACKUP operation, ensure the standalone BACKUP volume is on line and ready. Enter "YES" to continue:

If the procedure displays the previous messages, remove the distribution volume from the drive and replace it with the correct volume as described in Section 3.2.2. Then type Yes, press Return, and repeat this step.

Completing the Transfer Operation

Complete the transfer of the VMS072.B save set to your system disk by performing one of the following operations:

• If you are using standalone BACKUP to transfer the VMS072.B save set, the procedure displays the following message when it has completed checking files:

  %BACKUP-I-PROCDONE, Operation completed. Processing finished at 13-NOV-1998 10:00. If you do not want to perform another standalone BACKUP operation, use the console to halt the system. If you do want to perform another standalone BACKUP operation, ensure the standalone application volume is on line and ready. Enter "YES" to continue:

  
  Go to Section 3.2.4 to boot the new system disk.

• If you are using the specialized OpenVMS environment to transfer the VMS072.B save set, the system displays the triple dollar sign ($$$) DCL prompt after the BACKUP operation completes. Enter the command LOGOUT to return to the menu. For example:

  $$$ LOGOUT 1) Execute DCL commands and procedures 2) Shut down this system

  
  You can then choose option 2 to shut down the system in preparation for booting the new system disk, as described in Section 3.2.4.

Halt the system and boot the new system disk, as described in the upgrade and installation supplement for your VAX computer.

When the boot is completed, the procedure displays a message and prompts you to enter the date and time. Enter the date and time using the 24-hour clock format and press Return.

For example:

OpenVMS (TM) VAX Version V7.2 Major version id = 1 Minor version id = 0 OpenVMS VAX V7.2 Installation Procedure Model: VAXstation 3100-M76/SPX System device: RZ26 - _DKB100: Free blocks: 1984383 CPU type: 11-04 * Please enter the date and time (DD-MMM-YYYY HH:MM) 13-NOV-1998 10:35 ********************************************************* %SYSTEM-W-TZGMT, your local timezone has defaulted to GMT %SYSTEM-I-SETTZ, to set your local timezone use: $ @SYSMANAGER:UCT$TIME_SETUP.COM ********************************************************* On MIN or UPGRADE system startup - CLUE is not run. %%%%%%%%%%% OPCOM 13-NOV-1998 10:35:08.98 %%%%%%%%%%% Operator _OPA0: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 13-NOV-1998 10:35:09.00 %%%%%%%%%%% Operator status for operator _OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %%%%%%%%%%% OPCOM 13-NOV-1998 10:35:09.62 %%%%%%%%%%% Logfile has been initialized by operator _OPA0: Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 %%%%%%%%%%% OPCOM 13-NOV-1998 10:35:09.64 %%%%%%%%%%% Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SYSTEM-I-BOOTUPGRADE, security auditing disabled %%%%%%%%%%% OPCOM 13-NOV-1998 10:35:11.60 %%%%%%%%%%% Message from user JOB_CONTROL %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT %%%%%%%%%%% OPCOM 13-NOV-1998 10:35:11.60 %%%%%%%%%%% Message from user JOB_CONTROL -RMS-E-FNF, file not found %LICENSE-F-EMTLDB, license database contains no license records %SYSTEM-I-BOOTUPGRADE, security server not started %%%%%%%%%%% OPCOM 13-NOV-1998 10:35:16:75 %%%%%%%%%%% Message from user SYSTEM %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node -LICENSE-F-NOLICENSE, no license is active for this software product -LICENSE-I=SYSMGR, please see your system manager %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node -%LICENSE-F-NOLICENSE, no license is active for this software product -%LICENSE-I-SYSMGR, please see your system manager Startup processing continuing... %SET-I-INTSET, login interactive limit = 1, current interactive value = 0 %SET-I-INTSET, login interactive limit = 0, current interactive value = 0

	privacy and legal statement
6521PRO_002.HTML