Digital PDFs

AA-LB36A-TE

December 1988

137 pages

Original

5.4MB

Document:	VMS 5.0 Installation 62xx 198804
Order Number:	AA-LB36A-TE
Revision:
Pages:	137
Original Filename:	http://bitsavers.org/pdf/dec/vax/vms/5.0/AA-LB36A-TE_VMS_5.0_Installation_62xx_198804.pdf

OCR Text

VMS

VMS Installation and Operations:
VAX 6200 Series

Order Number AA-LB36A-TE

VMS Installation and Operations:
VAX 6200 Series
Order Number: AA-LB36A-TE

·April 1988
This guide describe$ the VMS installation procedure for the VAX 6200
series computers. It also explains the startup, shutdown, and backup
operations for these VAX computers.

Revision/Update Information:

This is a new guide.

Software Version:

VMS Version 5.0

digital equipment corporation
maynard, massachusetts

April 1988
The information in this document is subject to change without notice and should
not be construed as a commitment by Digital Equipment Corporation. Digital
Equipment Corporation assumes no responsibility for any errors that may appear
in this document.
The software described in this document is furnished under a license and may be
used or copied only in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment
that is not supplied by Digital Equipment Corporation or its affiliated companies.
Copyright © 1988 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-10
DECSYSTEM-20
DEC US
DECwriter

DIBOL
EduSystem
IAS
MASS BUS
PDP
PDT
RSTS
RSX

UNIBUS
VAX
VAXcluster
VMS
VT

~urnua~uTM
ZK4662

HOW TO ORDER ADDITIONAL DOCUMENTATION
DIRECT MAIL ORDERS
USA*

CANADA

INTERNATIONAL

Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire
03061

Digital Equipment
of Canada Ltd.
100 Herzberg Road
Kanata, Ontario K2K 2A6
Attn: Direct Order Desk

Digital Equipment Corporation
PSG Business Manager
c/o Digital's local subsidiary
or approved distributor

In Continental USA, Alaska, and Hawaii call 800-DIGIT AL.
In Canada call 800-267-6215.
*Any order from Puerto Rico must be placed with the local Digital subsidiary (809-754-7575).
Internal orders should be placed through the Software Distribution Center (SOC), Digital Equipment
Corporation, Westminster, Massachusetts 014 73.

Production Note
This book was produced with the VAX DOCUMENT electronic publishing
system, a software tool developed and sold by DIGITAL. In this system,
writers use an ASCII text editor to create source files containing text and
English-like code; this code labels the structural elements of the document,
such as chapters, paragraphs, and tables. The VAX DOCUMENT software,
which runs on the VMS operating system, interprets the code to format the
text, generate a table of contents and index, and paginate the entire document.
Writers can print the document on the terminal or line printer, or they can use
DIGITAL-supported devices, such as the LN03 laser printer and PostScript®
printers (PrintServer 40 or LN03R ScriptPrinter), to produce a typeset-qualitv
copy containing integrated graphics.

® PostScript is a registered trademark of Adobe Systems, Inc.

Contents
PREFACE

xiii

NEW AND CHANGED FEATURES

xvii

PART I
CHAPTER 1 THE INSTALLATION, UPGRADE, AND UPDATE
PROCEDURES

1-1

1.1

WHAT HAPPENS DURING AN INSTALLATION

1-1

1.2

WHAT HAPPENS DURING AN UPGRADE

1-1

1.3

WHAT HAPPENS DURING AN UPDATE

1-2

CHAPTER2 THE CONSOLE SUBSYSTEM

2-1

2.1

THE CONSOLE TERMINAL

2-1

2.2
2.2.1
2.2.2
2.2.3
2.2.4

THE PROCESSOR CONTROL PANEL
Upper Keylock Switch
Lower Keylock Switch
RESTART button
Status Indicator Lights

2-1
2-2
2-3
2-3
2-3

2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6

THE TAPE CARTRIDGE DRIVE
Tape Cartridges
Inserting a Tape Cartridge
Initializing a Tape Cartridge
Mounting a Tape Cartridge
Dismounting a Tape Cartridge
Removing a Tape Cartridge

2-4
2-7
2-8
2-9
2-10
2-11
2-11

Contents

2.4
2.4.1

THE CONSOLE COMMAND LANGUAGE
The SHOW CONFIGURATION COMMAND

2-12
2-12

2.5

THE SELF-TEST DISPLAY

2-14

CHAPTER 3 BEFORE INSTALLING VMS
3.1

THE DISTRIBUTION MEDIA AND SYSTEM DISK

3-1

3.2

LOCAL DRIVES

3-1

3.3

HSC DRIVES

3-1

3.4

DEVICE NAMES

3-2

3.5

BOOTING DURING THE INSTALLATION

3-3

3.6

INFORMATION ON VAXCLUSTER ENVIRONMENTS

3-5

CHAPTER4 INSTALLING THE VMS OPERATING SYSTEM

3-1

4-1

4.1

BEFORE YOU START

4-1

4.2

TURNING ON THE SYSTEM

4-2

4.3

PREPARING THE DISK AND TAPE DRIVES

4-3

4.4

BOOTING STANDALONE BACKUP

4-3

4.5

CREATING A SYSTEM DISK ON A LOCAL DRIVE

4-5

4.6

CREATING A SYSTEM DISK ON AN HSC DRIVE

4-7

Contents

4.7

TRANSFERRING THE LIBRARY AND OPTIONAL SAVE SETS

4-10

4.8

INSTALLING THE MANDATORY UPDATE AND RUNNING
AUTOGEN

4-13

CHAPTER 5 AFTER INSTALLING VMS

5-1

5.1

REGISTERING YOUR LICENSES

5-1

5.2

REMOVING UNWANTED FILES WITH VMSTAILOR

5-2

5.3

CUSTOMIZING THE SYSTEM

5-2

5.4

TESTING THE SYSTEM

5-3

5.5

DECOMPRESSING THE SYSTEM LIBRARIES

5-3

5.6

BACKING UP THE SYSTEM DISK

5-3

CHAPTER 6 RUNNING UETP

6-1

6.1

SUMMARY OF UETP OPERATING INSTRUCTIONS

6-1

6.2
6.2.1

LOGGING IN
SYSTEST Directories

6-3
6-3

6.3
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.3.6
6.3.7
6.3.8
6.3.9
6.3.10

SETTING UP FOR UETP
Setting Up the System Disk
Setting Up Additional Disks
Setting Up Magnetic Tape Drives
Setting Up Tape Cartridge Drives
Setting Up Terminals and Line Printers
Preparing Ethernet Adapters for UETP Testing
Preparing the DR11-W for UETP Testing
Preparing the DRV11-WA for UETP Testing
Preparing the DR750 or the DR780 for UETP Testing
Preparing the MA780 for UETP Testing

6-3
6-4
6-4
6-5
6-5
6-6
6-6
6-6
6-7
6-7
6-7
vii

Contents

6.3.11
6.3.12
6.3.13
6.3.14
6.3.15

Preparing a Second LPA 11-K for UETP Testing
Devices Not Tested
Preparing for VAXcluster Testing
Preparing a Small-Disk System
Preparing DECnet

6-8
6-8
6-8
6-9
6-10

6.4
6.4.1
6.4.2
6.4.3
6.4.4
6.4.5

STARTING UETP
Running a Subset of Phases
Single Run Versus Multiple Passes
Defining User Load for Load Test
Long and Short Report Format
'Termination of UETP
Using CTRL/Y • 6-13
Using CTRL/C • 6-14

6-10
6-11
6-11
6-12
6-12
6-13

TROUBLESHOOTING
Relationship of UETP to Error Logging and Diagnostics
Interpreting UETP Output
Defining a Remote Node for UETP Ethernet Testing • 6-1 6
The Log Files
Possible U ETP Errors
Wrong Quotas, Privileges, or Account• 6-19
UETINITO 1 Failure • 6-21
Insufficient Disk Space • 6-22
Incorrect Setup of a V AXcluster • 6-23
Problems During the Load Test • 6-24
DECnet Error • 6-25
Errors Logged but Not Displayed • 6-26
No PCB or Swap Slots • 6-26
Hangs• 6-27
Bugchecks and Machine Checks• 6-27

6-14
6-14
6-15

UETP TESTS AND PHASES
Initialization Phase
Device Test Phase
How the Device Phase Works • 6-28
Running a Single Device Test • 6-29
System Load Test Phase
DECnet Test Phase
Environment • 6-32
How the DECnet Phase Works• 6-33
Cluster-Integration Test Phase

6-27
6-28
6-28

6.4.5.1
6.4.5.2
6.5
6.5.1
6.5.2

6.5.2.1
6.5.3
6.5.4

6.5.4.1
6.5.4.2
6.5.4.3
6.5.4.4
6.5.4.5
6.5.4.6
6.5.4.7
6.5.4.8
6.5.4.9
6.5.4.10
6.6
6.6.1
6.6.2

6.6.2.1
6.6.2.2
6.6.3
6.6.4

6.6.4.1
6.6.4.2
6.6.5

viii

6-17
6-18

6-31
6-32

6-35

Contents

PART II
CHAPTER 7 SYSTEM STARTUP AND SHUTDOWN

7-1

7.1

OVERVIEW OF BOOTING

7-1

7.2

BOOTING FROM A LOCAL DISK DRIVE

7-2

7.3

BOOTING FROM AN HSC DISK DRIVE

7-3

7.4

PERFORMING A CONVERSATIONAL BOOT

7-4

7.5
7.5.1

AUTOMATIC RESTART
Setting a Default Disk

7-7
7-7

7.6

BOOTING WITH XDELTA

7-:-8

7.7

BOOTING FROM A DIFFERENT DIRECTORY ON THE SYSTEM
DISK

7-8

7.8

USING SET BOOT

7-9

7.9

IF THE SYSTEM DOES NOT BOOT

7-9

7.10
7.10.1
7.10.2

SHUTTING DOWN THE SYSTEM
Types of Shutdowns
Emergency Shutdown with CRASH Commands

7-10
7-10
7-11

CHAPTERS BACKUPPROCEDURES
8.1
8.1.1
8.1.2

OVERVIEW OF STANDALONE BACKUP
Installing Standalone BACKUP on the System Disk
Booting Standalone BACKUP from the System Disk

8-1
8-1
8-1
8-2

Contents

8.2
8.2.1

INSTALLING STANDALONE BACKUP ON A TAPE
CARTRIDGE
Booting Standalone BACKUP from a Tape Cartridge

8-3
8-4

8.3

BACKING UP THE SYSTEM DISK

8-5

8.4

RESTORING THE SYSTEM DISK

8-8

APPENDIX A HOW THE SYSTEM ASSIGNS CONTROLLER
LETTERS

A-1

GLOSSARY

Glossary-1

INDEX

FIGURES
2-1

Processor Control Panel

2-2

VAX 6200 Series Tape Cartridge Drive

2-5

2-3

The Tape Cartridge

2-7

2-4

Positioning the Write-Protect Switch

2-8

2-5

How to Insert a Tape Cartridge

2-9

2-1

Upper Keylock Switch Settings

2-2

Lower Keylock Switch Settings

2-3

Restart Button Functions

2-3

2-4

Status Indicator Lights

2-4

2-5

Tape Cartridge Drive Controls

2-6

Tape Cartridge Drive Indicator Lights

2-6

2-7

Commonly Used Console Mode Commands

2-12

2-8

Devices on the VAXBI and the XMI

2-14

3-1

Device Codes for the VAX 6200 Series

3-3

4-1

Installation Questions for Cl-Only Configurations

4-10

4-2

Installation Questions for Local Area and
Mixed-Interconnect Configurations

4-11

TABLES

Contents

6-1
7-1
7-2
7-3
A-1

The Device Tests
Boot Command Qualifiers (Local Disks)
Boot Command Qualifiers (HSC Disks)
SYSGEN Commands Used in SYSBOOT
Controller Naming Example

6-31
7-3
7-4
7-5
A-2

Preface
The VAX 6200 series computers are multi-user systems that are fully
compatible with other VAX processor software, including VMS software,
optional software, and applications software. The VAX 6200 series can be
used as multiprocessors that interconnect several KA62A processors. The
VAX 6210 contains one KA62A processor, the VAX 6220 contains two, the
VAX 6230 contains three, and the VAX 6240 contains four.
This guide refers to the VAX 6210, VAX 6220, VAX 6230, and VAX 6240
computers as the VAX 6200 series.

VMS Installation and Operations: VAX 6200 Series contains specific installation
and operations information for the VAX 6200 series computers. Store this
installation and operations guide in the binder that contains the current
version of the VMS Release Notes. Place it in the section after the VMS Release

Notes.

Intended Audience
This guide is for system managers, operators, and users of VAX 6200 series
systems.

Document Structure
VMS Installations and Operations: VAX 6200 Series is organized into two
parts. Part I provides an overview of the system and covers installation and
post-installation procedures. Part II describes operations that you perform
frequently on the system, such as system startup, shutdown, and backup.
Part I

•

Chapter 1 describes the VMS operating system installation, upgrade, and
update procedures.

•

Chapter 2 describes the console subsystem.

•

Chapter 3 summarizes the basic information you need to know before
installing the VMS operating system.

•

Chapter 4 describes how to install the VMS operating system.

•

Chapter 5 lists the tasks you should perform after you install the VMS
operating system.

•

Chapter 6 describes the VMS User Environment Test Package (UETP) and
how to use it to test the system.

Part II

•

Chapter 7 contains instructions for starting up the system. It also
describes system shutdown procedures.

•

Chapter 8 describes backup procedures that you should perform on a
regular basis.

xiii

Preface

•

Appendix A explains how the system assigns controller letters to devices
on the system.

•

The Glossary lists and defines terms.

Associated Documents
The following documents may be useful:

•

VMS Release Notes-provide notes on the various aspects of the VMS
operating system. More importantly, the release notes contain a
description of the upgrade and update procedures. The release notes
also contain the latest information regarding your VAX computer. You
should read the current version of the release notes before installing,
updating, or upgrading the VMS operating system or using your VAX
computer.

•

The hardware manuals supplied with your VAX computer provide
detailed information on system hardware.

Conventions
Convention

Meaning
In examples, a key name (usually abbreviated)
shown within a box indicates that you press
a key on the keyboard; in text, a key name is
not enclosed in a box. In this example, the key
is the RETURN key. (Note that the RETURN
key is not usually shown in syntax statements
or in all examples; however, assume that you
must press the RETURN key after entering a
command or responding to a prompt.)

CTRL/C

A key combination, shown in uppercase with a
slash separating two key names, indicates that
you hold down the first key while you press the
second key. For example, the key combination
CTRL/C indicates that you hold down the key
labeled CTRL while you press the key labeled C.
In examples, a key combination is enclosed in a
box.

$SHOW TIME

In examples, system output (what the system
displays) is shown in black. User input (what
you enter) is shown in red.

05-JUN-1988 11 :55:22

$ TYPE MYFILE.DAT

xiv

In examples, a vertical series of periods, or
ellipsis, means either that not all the data that
the system would display in response to a
command is shown or that not all the data a
user would enter is shown.

Preface

Convention

Meaning

input-file, ...

In examples, a horizontal ellipsis indicates
that additional parameters, values, or other
information can be entered, that preceding
items can be repeated one or more times, or
that optional arguments in a statement have
been omitted.

[logical-name]

Brackets indicate that the enclosed item is
optional. (Brackets are not, however, optional
in the syntax of a directory name in a file
specification or in the syntax of a substring
specification in an assignment statement.)

quotation marks
apostrophes

The term quotation marks is used to refer
to double quotation marks (" ) . The term
apostrophe ( 1 ) is used to refer to a single
quotation mark.

New and Changed Features
Before VMS Version 5.0 the VAX/VMS System Manager's Reference Manual
included specific information on booting and installing standalone BACKUP
on the different VAX computers. The Guide to VAX/VMS Software Installation
provided information on console subsystems, disk and tape drives, and
booting during installation. There were also 19 separate booklets with
step-by-step instructions for installing the VMS operating system.
With VMS Version 5.0 DIGITAL is providing one guide for each family of
VAX computers. Each guide provides a single source of information on the
following:
•

Disk and tape drives and the console subsystem

•

Installing the VMS operating system on your particular VAX computer

•

Testing the system with UETP

•

Startup and shutdown operations

•

Installing and booting standalone BACKUP

•

Backing up and restoring the system disk

•

Backing up the console media (if applicable)

The guide for your VAX computer provides all the specific information
you need to install the VMS operating system and perform daily startup,
shutdown, and backup operations.
Note the following Version 5.0 restrictions for installing the VMS operating
system:
•

Dual system disks are no longer supported.

•

The entire VMS operating system will not fit on an RC25, RD52, or RK07
system disk. DIGITAL suggests that you add more disk storage to your
system.

•

The VAX-11/782 is no longer supported.

xvii

Part I
Part I describes installation and post-installation procedures.

The Installation, Upgrade, and Update Procedures

This chapter describes what happens during the installation, upgrade, and
update procedures. It also tells when you should do an installation, upgrade,
or an update and refers you to the appropriate documentation.
Before you install, upgrade, or update the VMS operating system, read this
chapter.

1.1

What Happens During an Installation
When you install the VMS operating system, the installation procedure does
the following:
•

Initializes the system disk, erasing its contents

•

Creates a system directory structure

•

Transfers the VMS 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).

•

If your VAX computer is running a version of the VMS operating system
and you want to destroy the entire contents of the system disk (both VMS
and user files).

•

If you are running the VMS operating system, but are not able to perform
an upgrade. For example, if you do not have a standard version of the
VMS operating system on your system disk, the upgrade procedure does
not work correctly.

If you are going to install the VMS operating system, read Part I of this guide.

CAUTION: The installation procedure initializes the system disk, erasing its
contents. For this reason, use the installation procedure only on new
VAX computers or if you want to destroy the contents of the system disk.

1 .2

What Happens During an Upgrade
When you upgrade the VMS operating system, the upgrade procedure does
the following:
•

Makes room for the upgrade by purging and deleting some VMS files but
leaves some of the VMS files and all the user files intact

•

Transfers the VMS files from the distribution media to the system disk

•

Merges the old VMS files and the new VMS files

•

Cleans up files and structures used only during the upgrade

1-1

The Installation, Upgrade, and Update Procedures
1 .2 What Happens During an Upgrade

In most cases, if you are already running a standard version of the VMS
operating system, you can use the upgrade procedure to obtain a higher
version. The upgrade procedure does not intitialize the system disk.
CAUTION: The upgrade procedure will not work correctly if you have changed the
names of system directories on your system disk or if you have deleted
VMS files from them. Restore your VMS system disk to a standard system
before attempting an upgrade.
If you are going to perform an upgrade, see the current version of the VMS

Release Notes for a step-by-step description of the upgrade procedure.

1 .3

What Happens During an Update
The update procedure is used to make minor fixes to the operating system.
When you update the VMS operating system, the update procedure does the
following:
•

Applies patches to some VMS files

•

Replaces some VMS files

After performing an installation or upgrade, you perform an update.
This update is referred to as the mandatory update. The directions for an
installation or an upgrade indicate when to perform the mandatory update.
Some maintenance releases of the VMS operating system are also applied
with the update procedure. The directions for a maintenance update are in
the VMS Release Notes.
CAUTION: The update procedure will not work correctly if you have changed the
names of system directories on your system disk or if you have deleted
VMS files from them. Restore your VMS system disk to a standard system
before attempting an update.

1-2

The Console Subsystem

Before you install the VMS operating system, you need to be familiar with the
VAX 6200 series console subsystem. In general, use the console subsystem
to examine and deposit data in memory or processor registers, stop the
system, and boot the operating system. During installation use the console
subsystem to boot the system and monitor the installation process. The
console subsystem consists of the following:
•

Console terminal

•

Processor control panel

•

Tape cartridge drive

•

Console command language

This chapter describes the parts of the console subsystem that you use to
install the VMS operating system. For a detailed description of the console
subsystem, see the hardware manuals supplied with your system.

2.1

The Console Terminal
The console terminal is a terminal (usually hardcopy) attached to the system.
It prints a log of processor activities. Use the console terminal to control and

monitor system operations.

2.2

The Processor Control Panel
The processor control panel is located on the front of the cabinet, in the upper
left corner. It consists of the following:
•

Two keylock switches

•

Six lights that correspond to the settings of the keylock switches

•

Three status indicator lights

•

One RESTART button

Figure 2-1 shows the processor control panel.

2-1

The Console Subsystem
2.2 The Processor Control Panel

Figure 2-1

Processor Control Panel

ii Standby

QC[Q]
I

'-It

Enable

c:J Battery

ii Secure
ti Update

c:J Fault

a=LQJ
Ii

"-Ii

c:J Run

Halt

ii Auto Start It

URestart
ZK-7445-HC

2.2.1

Upper Keylock Switch
The upper keylock switch regulates system power. It has four settings: OFF,
STANDBY, ENABLE, and SECURE. To change the setting of a keylock
switch, insert the key and turn it. When you select a switch setting, the
corresponding light to the right of the switch glows. There is no light for the
OFF position.
Table 2-1 describes the settings of the upper keylock switch.

2-2

Table 2-1

Upper Keylock Switch Settings

Position

Effect

Light Color

OFF

Shuts off all power except to the
battery backup.

No light

STANDBY

Supplies power only to the power
supply, blower, and memory. Used
for system maintenance.

Red

ENABLE

Supplies power to the whole
system. You can use the console
terminal in console-mode, or use the
RESTART button.

Yellow

SECURE

Supplies power to the whole
system. Used for normal system
operation. You cannot use the
REST ART button or the console
terminal in console-mode.

Green

The Console Subsystem
2.2 The Processor Control Panel

2.2.2

Lower Keylock Switch
The lower keylock switch has three settings: UPDATE, HALT, and AUTO
START. When you select a switch setting, the corresponding light to the right
of the switch glows.
Table 2-2 describes the settings of the lower keylock switch.

2.2.3

Table 2-2

Lower Keylock Switch Settings

Position

Effect

Light Color

UPDATE

Displays the console-mode prompt
at the console terminal. Used to
modify the Electrically Erasable Read
Only Memory (EE ROM).

Red

HALT

Causes the system to halt rather
than restart following a power
failure or error halt.

Yellow

AUTO
START

Allows the system to reboot
automatically after a power failure
or error halt.

Green

RESTART button
Depending on the position of the keylock switches, pressing the RESTART
button boots the system, runs self-tests, or both. Table 2-3 describes various
keylock switches settings and the corresponding function of the RESTART
button.

Note: The upper keylock switch must be in the ENABLE position for the
RESTART button to function.
Table 2-3

2.2.4

Restart Button Functions

Upper Keylock Switch

Lower Keylock Switch

Function

ENABLE

AUTOSTART

Runs self-tests. If the
system passes the
self-test, it reboots.

ENABLE

UPDATE or HALT

Runs self-tests, halts,
and displays the consolemode prompt (> > > ).

STANDBY or SECURE

Any Position

·None.

Status Indicator Lights
There are three status indicator lights on the processor control panel: Run,
Battery, and Fault. Table 2-4 describes the meaning of these lights.

2-3

The Console Subsystem
2.2 The Processor Control Panel

Table 2-4
Light

Color

State

Meaning

Run

Green

System is executing operating system
instructions.

Off

System is in console-mode or turned off.

Battery backup unit is fully charged.

Blinking
1/x
second

Battery backup unit is charging.

Blinking
10/x
second

Battery backup unit is supplying power to the
system.

Off

System either does not have a battery backup
unit, or is turned off.

Self-test in progress. If this light remains
on, there is a hardware fault (see the
troubleshooting chapter of the owner's manual).

Off

Self-test is finished or the system is turned off.

Battery

Fault

2.3

Status Indicator Lights

Green

Red

The Tape Cartridge Drive
The tape cartridge drive is located on the front of the cabinet, in the upper
left corner. Figure 2-2 shows the tape cartridge drive.
When using the tape cartridge drive shown in Figure 2-2, you should be
aware of the following:
•

The green light blinks when the tape in the drive is actually moving
(being read from or written to). If a tape cartridge is in the drive and
this light is off, the drive is inactive and the tape is not positioned at its
beginning.

Note: Never attempt to remove a tape when the green light is blinking or
when it is off; this damages the tape and might damage the drive.
The green light glows when the drive is empty. It also glows when the
drive is inactive and positioned at the beginning of a tape. The only
time you can remove a tape cartridge is when the green light is glowing
steadily.
•

The red LOAD/UNLOAD button controls the loading of the tape.
When the button is pressed in, it is in the LOAD position. The red light
on the button glows when the tape is loaded. It blinks slowly when the
tape is rewinding. It blinks quickly when there is a tape error (for some
reason the tape could not be read). To clear a tape error, press the button
four times.

2-4

The Console Subsystem
2. 3 The Tape Cartridge Drive

Figure 2-2

VAX 6200 Series Tape Cartridge Drive

[[!]
,--,

rl
~'

...,,!,,,

1--=

... ==-

1111[

Ill[
II[
I[
..
.
.

.
.
.

HANDLE
ZK-7443-HC

Note: Never attempt to remove a tape cartridge when the LOAD/UNLOAD
button is in the LOAD (in) position (the red light is on); you might
damage both the tape and the drive.
When the LOAD/UNLOAD button is released, it is in the UNLOAD (out)
position. The only time you can remove a tape is when this button is in
the UNLOAD (out) position (the red light is off).
•

The cartridge-release handle is located next to the tape access slot. This
handle controls the position of the tape drive spindle. Pull the handle
open to insert or remove a tape cartridge.

CAUTION: Pull the cartridge-release handle open only when all three of the
following are true:
•

The green light glows steadily

•

The LOAD /UNLOAD button is in the UNLOAD (out) position

•

The red light on the LOAD /UNLOAD button is off

Otherwise, you might damage both the tape and the drive.

2-5

The Console Subsystem
2.3 The Tape Cartridge Drive

Table 2-5 summarizes the tape cartridge drive controls. Table 2-6 describes
the tape cartridge drive lights.
Table 2-5

Tape Cartridge Drive Controls

Control

Position

Function

LOAD/UNLOAD button

Loads the tape ( 15 seconds to 3
1 /2 minutes).

Out

Rewinds and unloads the tape.

Open

Lets you insert or remove a
tape after rewind and unload
operations are complete.

Closed

Locks tape in operating position.

Cartridge release handle

Table 2-6

2-6

Tape Cartridge Drive Indicator Lights

Red Light

Green Light

Condition

Off

No power to the tape drive.

Off

Safe to move cartridge release
handle: Power is turned on.

Off

Do not move the cartridge release
handle. One of the following
conditions exists:
•

Power-on self test is
occurring.

•

Cartridge is inserted but
handle is still in the up
position.

•

Tape is loading or unloading.

•

Tape is stopped.

Tape loaded successfully.

Blinking

Tape is moving (except rewind).
Read/write commands are
being processed. Irregular fast
blinking means tape calibration is
occurring.

Blinking

Tape is rewinding.

Rapid Blinking

Off

A fault is occurring. Press and
release the LOAD/UNLOAD
button four times. If the problem
persists, do not attempt to
remove the tape cartridge. Call
DIGIT AL Field Service.

The Console Subsystem
2.3 The Tape Cartridge Drive

2.3.1

Tape Cartridges
Follow these guidelines when using tape cartridges:
•

Tape cartridges come in clear plastic protective cases. You should keep
tape cartridges in these cases when you are not using them.

•

The label slot holds the label that provides information about the contents
of the tape cartridge. Label a tape cartridge if you are going to copy files
to it (distribution tape cartridges are already labeled).
To label a tape cartridge, insert a slide-in label into the slot located on the
front of the tape cartridge. Figure 2-3 shows how to insert the label on a
tape cartridge.

CAUTION: Use only the label slot to label a tape cartridge. Applying adhesive
labels or writing on the tape cartridge can damage it.
•

The write-protect switch is a movable switch on the tape cartridge that
controls whether you can write to the tape. To write-protect a tape
cartridge, slide the write-protect switch toward the label slot. An orange
rectangle is visible when the tape cartridge is write-protected.

Always write-protect the distribution tape cartridge before an installation.
Figure 2-4 shows how to write-protect a tape cartridge.
Figure 2-3

The Tape Cartridge

LABEL
SLOT

~o~oomoTM

95MB
296MB

D
D

LABEL

ZK-6520-HC

2-7

The Console Subsystem
2.3 The Tape Cartridge Drive

Figure 2-4

Positioning the Write-Protect Switch

NOT WRITEPROTECTED

WRITEPROTECTED

ZK-6521-HC

2.3.2

Inserting a Tape Cartridge
To insert a tape cartridge in the drive, do the following:
1

Make sure the tape cartridge drive is empty. If the VMS operating system
is not running, go to step 2.
If the VMS operating system is running and a tape cartridge is already in

the drive, enter the following command and press RETURN:
$ SHOW DEVICE MUcu

where:

•

c is the controller designation of the drive. A controller designation
can be one of the alphabetic letters A through Z. The controller
designation, along with the unit number, identifies the loca~ion of the
tape cartridge drive.

•

u is the unit number. The unit number is a decimal number that,
along with the controller designation, identifies the location of the
tape cartridge drive. For more information, see Chapter 3.

If the display indicates that the status of the tape cartridge is MOUNTED,

you must first dismount the tape before removing it from the drive.
Follow the instructions in Section 2.3.S to dismount the tape cartridge.
Then follow the directions for removing a tape cartridge in Section 2.3.6.

2-8

Press the LOAD /UNLOAD button so that it is in the UNLOAD (out)
position. The green light glows steadily and the red light is off.

The Console Subsystem
2.3 The Tape Cartridge Drive

Remove the tape cartridge from its plastic case. You should write-protect
a tape cartridge containing software that you will install on your system.
You should write-enable a tape cartridge if you are going to either copy
or back up files to it.

CAUTION: Never pull open the cartridge-release handle unless the green light
glows, the red light is off, and the LOAD /UNLOAD button is in the
UNLOAD (out) position; you might damage the drive.
4

Pull open the cartridge-release handle.
Figure 2-5 illustrates steps 4 through 7 in the insertion procedure.

Figure 2-5

2.3.3

How to Insert a Tape Cartridge

Hold the tape cartridge with the label facing you and the large arrow
on the top of the tape cartridge pointing into the drive. Insert the tape
cartridge in the drive. Push the tape cartridge into the drive until it locks
into place. The green light turns off, and the red light glows.

Push the cartridge-release handle closed until it locks into place. The red
light turns off and the green light glows.

Press the LOAD /UNLOAD button so that it is in the LOAD (in) position.
The red light glows. The tape cartridge goes through a load process
that takes between 10 and 15 seconds. During this time, the green light
blinks. When the tape is ready, the green light glows.

Initializing a Tape Cartridge
Note: You do not need to initialize any tape cartridges when you install the
VMS operating system.
Initializing a tape cartridge does the following:
•

Erases any data stored on the tape cartridge

•

Assigns a volume label to the tape cartridge

•

Prepares the tape cartridge to store VMS files

2-9

The Console Subsystem
2.3 The Tape Cartridge Drive

You should initialize a new tape cartridge before using it the first time.
Initialize an old tape cartridge to erase its contents.
To initialize a tape cartridge, first make sure that the account you are logged
into has the volume protection (VOLPRO) privilege. Make sure the tape
cartridge is write-enabled.

CAUTION: Do not initialize a tape cartridge that contains operating system software
or files that you want to save. The INITIALIZE command erases the
contents of the tape cartridge.
To initialize a tape cartridge, enter the INITIALIZE command in the following
format and press RETURN:
$ INITIALIZE MUcu volume-label

where:
•

c is the controller designation of the drive. A controller designation can
be one of the alphabetic letters A through Z. The controller designation,
along with the unit number, identifies the location of the tape cartridge
drive.

•

u is the unit number. The unit number is a decimal number that, along
with the controller designation, identifies the location of the tape cartridge
drive. For more information, see Chapter 3.

•

volume-label is a 1- to 6-character alphanumeric identification. Write the
volume label of the tape cartridge on the tape cartridge label. You will
need to know the volume label when you use the tape cartridge.

For example, the following command initializes the tape cartridge in the tape
cartridge drive (MUL6), and gives it the label WORK:
$ INITIALIZE MUL6 WORK

2.3.4

Mounting a Tape Cartridge
Note: You do not need to mount any tape cartridges when you install the
VMS operating system. The VMS installation procedure does this
automatically.
After you insert a tape cartridge (and initialize it, if it is new), you must
mount it to make it available to the system. To mount a tape cartridge, enter
the MOUNT command in the following format and press RETURN:
$ MOUNT MUcu volume-label

where:
•

c is the controller designation of the drive. A controller designation can
be one of the alphabetic letters A through Z. The controller designation,
along with the unit number, identifies the location of the tape cartridge
drive.

•

u is the unit number. The unit number is a decimal number that, along
with the controller designation, identifies the location of the tape cartridge
drive. For more information, see Chapter 3.

•

volume-label is a 1- to 6-character alphanumeric identification that you
assigned to the tape cartridge with the INITIALIZE command.

2-10

The Console Subsystem
2.3 The Tape Cartridge Drive

For example, to mount a tape cartridge named MUC6, enter the following
command and press RETURN:
$ MOUNT MUC6 TEST

If you do not specify the correct volume-label when you mount the tape

cartridge, the system displays the following message:
%MOUNT-F-INCVOLLABEL, incorrect volume label

If you do not remember the volume label, enter the MOUNT command in the

following format and press RETURN:
$ MOUNT/OVERRIDE=IDENTIFICATION MUcu

Then enter the following command to determine the volume label of the tape
cartridge:
$ SHOW DEVICE MUcu

The system displays the volume label.

2.3.5

Dismounting a Tape Cartridge
Note: You do not need to dismount any tape cartridges when you install
the VMS operating system. The VMS installation procedure does this
automatically.
When you are finished using a tape cartridge, you should dismount it. To
dismount a tape cartridge, enter the DISMOUNT command in the following
format and press RETURN:
$ DISMOUNT MUcu

where:

•

c is the controller designation of the drive. A controller designation can
be one of the alphabetic letters A through Z. The controller designation,
along with the unit number, identifies the location of the device.

•

u is the unit number. A unit number can be a decimal number that, along
with the controller designation, identifies the location of the device.

When you dismount a tape cartridge, you can remove it from the drive.

2.3.6

Removing a Tape Cartridge
To remove a tape cartridge from the drive, do the following:
1

Press the LOAD /UNLOAD button so that it is in the UNLOAD (out)
position. If the tape is not rewound, the red and green lights blink slowly
as the tape rewinds. When the tape is completely unloaded, the red light
turns off and the green light glows.

CAUTION: Never pull open the cartridge-release handle unless the green light
glows, the red light is off, and the LOAD/UNLOAD button is in the
UNLOAD (out) position; you might damage the tape drive.

2-11

The c·onsole Subsystem
2.3 The Tape Cartridge Drive

2.4

Pull open the cartridge-release handle. The tape cartridge partially ejects.

Remove the tape cartridge and put it in its plastic case.

Push the handle closed until it locks firmly into place.

The Console Command Language
The console subsystem runs in two modes, program mode and console mode.
•

Program mode - In program mode, the VMS operating system controls
the console subsystem. The RUN light on the processor control panel
glows. In program mode, you can enter DCL commands, run programs,
and receive system messages.

•

Console mode - In console mode, the VMS operating system is not
running and the system is halted. The console terminal displays the
console-mode prompt ( > > > ) and the RUN light on the processor
control panel is off. If the upper keylock switch is not set to SECURE,
you can control and monitor system operations by entering console mode
commands.

Table 2-7 describes the console mode commands used in this guide.
Table 2-7

Commonly Used Console Mode Commands

Command

Definition

BOOT

Starts the process that loads system software into
memory. During the installation procedure, use the
abbreviation, B, for the BOOT command.

DEPOSIT

Puts a value in the specified register or memory
location.

EXAMINE

Displays the contents of the specified register or
memory location.

SET BOOT

Equates a boot command to a nickname.

SHOW CONFIGURATION

Displays hardware and self-test information about
the system.

For more information on the console subsystem and command language, see
the hardware manuals supplied with your VAX computer.

2.4.1

The SHOW CONFIGURATION COMMAND
You can obtain additional information about the the system hardware using
the SHOW CONFIGURATION command. Enter the following command and
press RETURN:
>>> SHOW CONFIGURATION

2-12

The Console Subsystem
2.4 The Console Command Language

The system displays a list of hardware information similar to the following:
Type
1+0 MS62A@
2MS62A
3+
KA62A
4+
KA62A
D+
DWMBA/A
E+
DWMBA/A

Code
Rev
(4001)8 ooooe
(4001)
0001
(8001)
0001
(8001)
0001
(2001)
0001
(2001)
0001

XBI D
1+0 DWMBA/BC) (0107)0 FFF00
5+
KLESI-B (0103)
0006
6+
KDB50
(010E)
OF1C
A+
DEBNA
(410F)
023B
XBI E
1+
DWMBA/B
4+
KDB50
6+
TBK50

(0107)
(010E)
(410E)

FFFO
OF1C
0246

This column lists the XMI node number of each device on the XMI bus.
The plus ( +) or minus ( - ) indicates whether the device passed self-test.

This column lists the name of each device on the XMI bus. For a complete
list of names, see Table 2-8.

This column lists the code for each device on the XMI bus. For a complete
list of codes, see Table 2-8.

The last column lists the revision level of each XMI node.

This column lists the VAXBI node number of each device on the VAXBI.
In this example, the VAXBI is connected to the XMI through a DWMBA
on nodes D and E. The plus ( +) or minus ( - ) indicates whether the
device passed self-test.

This column lists the name of each device on the VAXBI. For a complete
list of names, see Table 2-8.

This column lists the codes for the devices on the VAXBI. For a complete
list of codes, see Table 2-8.

The last column lists the revision level of each VAXBI node.

2-13

The Console Subsystem
2.4 The Console Command Language

Table 2-8

Devices on the VAXBI and the XMI

Device

Code

Function

Cl8CA

0108

Cluster port interface (VAX81 to Cl adapter); connects
a system to a V AXcluster.

DE8NA

410F

Ethernet port interface; connects the system to the
Ethernet

T8K50

410E

TK50 tape cartridge drive controller; connects the
tape cartridge drive to the system.
Communications device; supports up to 16 terminals

DH832
DM832

0109

Communications device

DR832

0101

Parallel port.

DS832

010A

DECnet interface.

DWBUA

0102

V AXBI to UNIBUS adapter.

DWM8A
/A

2001

One of two boards that make up the DWM8A. 1

DWM8A
/8

0107

One of two boards that make up the DWM8A.

KA62A

8001

Processor. 1

MS62A

4001

Memory module. 1

KD850

010E

Disk controller; connects DSA disks to the system.

KLESl-8

0103

TU81 /TU81-Plus local tape controller.

1 Found on the XMI

2.5

bus.

The Self-Test Display
When you turn on, reset, or boot the system, it self-tests and displays the
results of the self-test at the console terminal. The self-test display provides
useful information about your hardware configuration.
The self test display on your system should be similar to the following:

Note: The portion of the display under nodes 0 and Fis blank. This is because
VAX 6200 series does not have a node 0 or F on the XMI bus.
F

M
+

>>>

2-14

NODE # ~

TYP

STF

BPD

ETF

BPD

Ct
0
0

P
+

XBI D +f)

ILV

64 Mb

The Console Subsystem
2.5 The Self-Test Display

This line names the nodes on the XMI bus.

This line indicates the type of device that is on XMI bus. The letter A
indicates an I/O adapter, Pa processor, and Ma memory module. From
the previous display, you can see that there is a memory module on node
E, an I/O adapter on node D, and nothing on node C.

This line indicates the results of the self-test: pass ( + ), fail ( - ), or does
not apply (o).

This line shows which processor acts as the boot processor. The letter
B indicates the boot processor (in this case, on node 2). The letter E
indicates the secondary processors.

This line shows the results of the extended self-test. The extended selftest only tests the processors. If the boot processor fails the extended
self-test, a different boot processor is designated.

This line again shows which processor acts as the boot processor. If all
the processors pass the extended self-test, this line should be the same as
the fourth line.

This line indicates the results of the VAXBI self-test. In this example, the
VAXBI is on XMI node number D. The+ means that it passed self-test.

G This line contains an interleave value for each memory module.
0

This line indicates the size of each memory module and the total amount
of memory. In this case there are two 32Mb modules for a total of
64Mb.

2-15

Before Installing VMS

This chapter describes the following:

3.1

•

Terms and procedures you need to know before you do an installation

•

Information you need to install the VMS operating system in a VAXcluster
environment

The Distribution Media and System Disk
When you install the VMS operating system, you work primarily with the
distribution media and the system disk. The distribution media are the tape
cartridges that the VMS operating system is supplied on. The VMS operating
system is supplied on the distribution media in a format that the computer
cannot readily use.
The installation procedure transfers the VMS files from the distribution media
to your system disk and puts them in a format that the system can use. A
system disk is the disk that contains (or will contain) the VMS operating
system in a usable format.

3.2

Local Drives
A drive that is connected directly to a VAX computer is referred to as a
local drive. For example, a magnetic tape drive connected directly to a VAX
computer is referred to as a local tape drive.
If you have a single VAX computer, it is likely that all the drives connected
to the system are local drives. If you have a VAXcluster environment, you
can have local drives or HSC drives, depending on the type of VAXcluster
configuration.
Check with the system manager if you are not sure what types of drives you
are using for the installation.

3.3

HSC Drives
A drive that is connected to an HSC device is referred to as an HSC drive. For
example, a magnetic tape drive connected to an HSC device is referred to as
an HSC tape drive.
If you have a VAXcluster environment, you can have local drives or HSC
drives depending on the type of VAXcluster configuration. Check with the
system manager if you are not sure what types of drives you are using for the
installation.

3-1

Before Installing VMS
3.4 Device Names

3.4

Device Names
At different times during the installation you need to tell the system which
drive holds the distribution media and which drive holds the system disk.
You refer to a drive with its device name. A device name has the following
format:

ddcu
where:

•

dd is the device code. The device code tells what type of device you are
using.

•

c is the controller designation. A controller designation can be one of the
alphabetic letters A through Z. The controller designation, along with the
unit number, identifies the location of the device. For information about
how the system assigns controller letters, see Appendix A.

•

u is the unit number. A unit number can be a decimal number in the
range of 0 to n. 1 The unit number, along with the controller designation,
identifies the location of the device.

Note: The only part of the name you can readily modify is the unit number.
The device code is fixed and the controller designation is made when the
hardware is installed.
For example, MUC6 might be the device name for the tape cartridge drive on
your system. MU is the device code for the tape cartridge drive. C names the
controller (the controller provides the interface between the processor and the
drive) and 6 is the unit number.
If a drive is connected to an HSC device, precede the device name with the

name of the HSC and a dollar sign ( $ ). For example:
TROUT$DUAO

TROUT is the name of the HSC device, and DUAO is the name of an RA82
drive that is connected to it.
Table 3-1 lists device codes for the different drives that can be part of a VAX
6200 series system.

The first drive on a controller is usually assigned a unit number of zero, the next drive is assigned a unit
number of one, and so on. The range is determined by the bus that supports the device. For example, KDBSO
disks can have unit numbers in the range of 0 to 254.

3-2

Before Installing VMS
3.4 Device Names

Table 3-1

Device Codes for the VAX 6200 Series
Used in
a Device
Name

Used in a Boot Name

Console tape cartridge
drive

CSA1

RA60 disk drive

RA70, RASO, RA81,and
RA82 disk drives

TA78, TA79, TA81
/T A81-PLUS and TU81
/TU81-PLUS magnetic
tape drives

Device

You can use any of the disk drives to hold the system disk. When choosing
a system disk, you must be aware of the capacity of the disk as well as the
size of the VMS operating system. Keep in mind that a system disk in a
VAXcluster environment needs more space for the operating system than a
system disk for a standalone system.
Before you begin the installation procedure, make sure you know the device
names for both the drive that will hold the distribution media and the drive
that will hold the system disk.

3.5

Booting During the Installation
During the installation, you need to boot the system disk several times. This
section explains how to determine boot names for devices connected to a VAX
6200 series computer.
The VAX 6200 series boots using small programs stored in read-only memory
(ROM) called boot primitives. Because the boot process is slightly different for
each type of drive, a boot primitive exists for each drive the system supports.
To boot the system using a boot primitive, you must specify the boot name
of the device from which you want to boot. Boot names have the following
format:
ddu

where:
•

dd is the device code

•

u is the unit number

Table 3-1 lists the device codes for the different devices that can be part of a
VAX 6200 series system.
Note that CSAl is an exception to the standard device name format. The
location of the tape cartridge drive is programmed into ROM and given the
name CSAl. You can always use this name to boot the tape cartridge drive
unless you change its location on the system.

3-3

Before Installing VMS
3.5 Booting During the Installation

Suppose you are planning to boot a local disk that has the boot name DU3.
You would use the following procedure:
1

To see how your system is configured, enter the following command and
press RETURN:
>>> SHOW CONFIGURATION

The system displays information about the XMI and VAXBI nodes similar
to the following:
Type
DWMBA/A
KA62A
MS62A

Code
(2001)
(8001)
(4001)

Rev
0001
0001
0001

XBI 2
1- DWMBA/B
5+ TBK50
6+ DRB32
8+ KDB50

(0107)
(410E)
(0101)
(010E)

FFFO
0001
0001
OF1C

2+
3E+

Find the disk controller (KDBSO) in the second part of the display. Then
look in the first column of that line for the VAXBI node number. Write
this number down. In this example, the VAXBI node number is 8.

Write down the XMI node number of the DWMBA/ A. This appears in
the first line of the second part of the display and also in the first part of
the display. In this example, it is 2.

Make sure the console tape cartridge is in the console drive.

Enter the following command and press RETURN:
>>> BOOT/XMI:2/BI:8 DU3

If you want to boot from an HSC disk, you need to add the /NODE qualifier

to the BOOT command line. Use the /NODE qualifier to specify the HSC
node number (in hexadecimal) of the HSC device you want to use when you
boot the system. For example, suppose you want to boot an HSC system disk
that has the following configuration:
•

A unit number of one.

•

A VAXBI node number of 2 (the disk is connected to the VAXBI at
node 2).

•

An XMI node number of 3 (the VAXBI that the disk is on is connected to
the XMI at node 3).

•

An HSC node number 02.

You would enter the following command and press RETURN:
>>> BOOT/XMI:3/BI:2/NODE:02 DU1

For more information about the BOOT command and its qualifiers, see
Chapter 7. For more information about the hardware configuration of your
system, see the hardware manuals provided with your system.

3-4

Before Installing VMS
3.6 Information on VAXcluster Environments

3.6

Information on VAXcluster Environments
If you are installing the VMS operating system in a VAXcluster environment,
the installation procedure will ask you for information about your VAXcluster
environment. Before proceeding, you must read the VMS VAXcluster
Manual. If you have a clear understanding of VAXclusters before you do
an installation, you are less likely to enter incorrect information during the
installation. Entering incorrect information during the installation might force
you to repeat the entire procedure.

Following is a list of the VAXcluster information you need to obtain. For a
complete explanation of each item, see the VMS VAXcluster Manual.
Determine what type of configuration you want: CI-only, local area, or
mixed-interconnect. These configuration types are distinguished by the
interconnect device that the VAX computers in the cluster use to communicate
with one another (CI, Ethernet, or both).
You need to know the DECnet node name and node address for the VAX
computer on which you are installing the VMS operating system. The
network or system manager determines the DECnet node name and node
address for each VAX computer on the network. See your system or network
manager for this information.
During the installation procedure you will be asked for the ALLOCLASS
value of the VAX computer on which you are installing VMS. For example:
Enter a value for ALICE'S ALLOCLASS parameter:

Enter the appropriate allocation class value for the VAX computer on which
you are installing the VMS operating system. Refer to the VMS VAXcluster
Manual 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 that is connected to a dual-pathed disk.
When you enter the allocation class value, the installation procedure uses it
to automatically set the value of ALLOCLASS, a SYSGEN parameter.
If you are going to set up either a local area or a mixed-interconnect
cluster, determine the cluster group number and the cluster password. Use
the following rules to determine the cluster group number and password:

•

Cluster group number-A number in the range from 1-4095 or 6144065535.

•

Cluster password-Must be from 1 to 31 alphanumeric characters in
length and may include dollar signs ( $) and underscores (-).

3-5

Installing the VMS Operating System

This chapter describes how to install the VMS operating system on a VAX
6200 series system from a tape cartridge.

CAUTION: The software installation procedure overwrites the contents of the system
disk. Use the VMS 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, upgrade to the new version
of the VMS operating system. For a complete description of the upgrade
procedure, see the current version of the VMS Release Notes.

4.1

Before You Start
Before you install the VMS operating system, do the following:
•

Make sure your hardware has been installed and checked for proper
operation. For detailed hardware information, see the hardware
documentation for the VAX 6200 series.

•

Make sure you have all the items listed on the bill of materials in the
VMS distribution kit. The distribution kit should contain the following:
A tape cartridge that contains standalone BACKUP and the VMS
required, library, and optional save sets.
A tape cartridge that contains the mandatory update.
If your kit is incomplete, notify the DIGITAL Software Distribution
Center. Request priority shipment of any missing item.

•

If you are installing the VMS operating system on a VAX computer in a
VAXcluster environment, determine whether you want a CI-only, local
area, or mixed-interconnect configuration. For a complete description of
configurations, see the VMS VAXcluster Manual. Depending on the type
of configuration, you need to obtain the following information from either
the network or VAXcluster manager:

CI-Only Configuration: Obtain the allocation class value, the DECnet
node name, and node address for the computer.
Local Area and Mixed-Interconnect Configurations: You need the
allocation class value, the DECnet node name, and node address
for the computer. You also need the cluster group number and
password.
In addition, you need the console tape cartridge.
The installation procedure transfers the VMS files from the distribution tape
cartridge to the system disk. The procedure consists of the following stages:
1

Turning on the system

Preparing the disk and tape drives

Booting standalone BACKUP

4-1

Installing the VMS Operating System
4.1 Before You Start

Creating the system disk

Transferring the library and optional save sets

Installing the mandatory update and running AUTOGEN

The entire procedure takes approximately two to three hours.
Note: The screen displays and examples in this manual depict the installation
of VMS Version 5.0. Your screen displays reflect the version that you are
installing.

4.2

Turning On the System
This procedure assumes that the system is not turned on when you start the
installation. The following steps describe turning the system on and setting
the switches on the processor control panel:
1

Turn on the console terminal.

Make sure the console tape cartridge is in the console drive.

At the control panel, set the lower keylock switch to HALT.

Set the upper keylock switch to ENABLE.
The system initializes and self-tests. During the test, the red FAULT light
glows.
The system displays a self-test message similar to the following:
F

E
M

D
A

2
p

A2
32
ROM = 1.0

A1
32
EEPROM = 1.0/1.0

NODE #
TYP
STF
BPD
ETF
BPD
XBI D +
ILV
64 Mb

SN = NI0128

>>>

Note: If your console displays garbled characters and does not display the
self-test console display, the baud rates of the console terminal and
the processor do not match. The console terminal has a default setting
of 1200 baud. To continue with the installation, press the BREAK key
on the console terminal, pause, and press the break key again until
the console-mode prompt(> > >)appears. Each time you press the
BREAK key, the baud rate of the console terminal changes.
5

4-2

Go to Section 4.3 and prepare the disk and tape drives.

Installing the VMS Operating System
4.3 Preparing the Disk and Tape Drives

4.3

Preparing the Disk and Tape Drives
To set up the disk and tape drives you use during the installation, use the
following procedure:
1

Decide which drive you want to hold the system disk.

Follow this step only if the system disk is on an HSC drive in a
VAXcluster environment. Otherwise go to step 3.
Make sure that both the CIBCI and the HSCSO or HSC70 are turned on
and on line. Obtain the HSC name from the system manager or use the
following procedure:
a. Press CTRL/C at the HSC console terminal.

b. Enter the following command at the HSC> prompt and press
RETURN:
HSC> SHOW SYSTEM

The information displayed includes the name of the HSC. For
example:
31-Dec-1988 15:00:00.00 Boot:30-Dec-1988 11:31:11.41
Version V350
System ID: %X000000011

Up: 51:00
Name: TROUT

DISK allocation class = 1 TAPE allocation class = 0
Start command file m Disabled
SETSHO - Program Exit

For more information, see the HSC User Guide.

4.4

Place a scratch disk in the drive for the system disk (unless your system
disk is fixed).

Spin up the system disk but do not write-protect it.

To boot standalone BACKUP, go to Section 4.4.

Booting Standalone BACKUP
This section describes the steps for booting standalone BACKUP. Standalone
BACKUP lets you transfer the VMS required save set from the distribution
tape cartridge to your system disk. You need the tape cartridge from the
distribution kit that is labeled as follows:
Paper Label 1

Volume Label 2

VAX/VMS V5.0 BIN TK50

SYSTEM

paper label is the label affixed to a tape cartridge.

volume label is the name the VMS operating system uses to refer to a tape cartridge.
During the installation, the procedure displays the volume label, not the paper label, in
messages.

Booting standalone BACKUP takes approximately 20 minutes.

4-3

Installing the VMS Operating System
4.4 Booting Standalone BACKUP

Make sure the console tape cartridge is still in the console tape cartridge
drive.

To boot standalone BACKUP, enter the following command and press
RETURN:
»> B CSA1

The procedure displays a self-test message similar to the following:
F

E
M

D
A
0

B
A

9
M

A2
32

0
+

ROM= 1.0

Ai
32
EEPROM = 1.0/1.0

NODE #
TYP
STF
BPD
ETF
BPD
XBI D +
ILV
64 Mb

SN = NI0128

Loading system software.
Please remove the volume "CONSOL" from the console device.
Insert the first standalone system volume and enter "YES" when ready:

Remove the console tape cartridge. Insert the tape cartridge labeled
VAX/VMS VS.O BIN TKSO. When the distribution tape cartridge is
loaded, type Y and press RETURN.
Standalone BACKUP displays a message similar to the following:
Resuming load operation on volume 'SYSTEM', please stand by ...
VAX/VMS Version V5.0 Major version id = 01 Minor version id = 00

The procedure might ask you for the date and time. Enter the date and
time using the 24-hour clock format and press RETURN. For example:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 31-DEC-1988 15:00

The procedure displays a list of the local devices on your system and, if
you have them, HSC- and MSCP-served devices. For example:
Available device
Available device

MINE$DUAO:
MINE$DJA3:

device type RA81
device type RA60

Check the list of devices. If the list is incomplete, make sure that all the
drives are properly connected to the system. See your hardware manuals
for details.
7

When standalone BACKUP finishes booting, it displays an identification
message followed by the dollar-sign prompt ( $ ):
%BACKUP-I-IDENT, Stand-alone BACKUP V5.0; the date is 15-DEC-1988 15:00
$

To create a system disk on a local drive, go to Section 4.5.
To create a system disk on an HSC drive, go to Section 4.6.

4-4

Installing the VMS Operating System
4.5 Creating a System Disk on a Local Drive

4.5

Creating a System Disk on a Local Drive
This section provides instructions for installing the VMS operating system on
a system disk that is on a local drive. To create a system disk on an HSC
drive, see Section 4.6.
The VMS files are stored on the distribution tape cartridge as three save sets:
required, library, and optional. This section describes the steps for transferring
the required save set from the distribution tape cartridge to your system disk.
The instructions refer to the source-drive and the target-drive where:
•

The source-drive is the drive that holds the distribution tape cartridge

•

The target-drive is the drive that holds the system disk

Determine the device names for the source-drive and the target-drive,
using Table 3-1. Write these names on a piece of paper. You will need
this information throughout the installation.

To transfer the required save set to your system disk, enter the BACKUP
command in the following format:
$ BACKUP/VERIFY source-drive:VMS050.B/SAVE_SET target-drive:

Substitute the appropriate device names for source-drive and target-drive.
Make sure you put a colon (:) after each device name and that you use
zeros in the device names and VMS050.
For example, if your system has the following configuration:
•

A TK50 source-drive with a controller designation of C and a unit
number of six

•

An RA60 target-drive with a controller designation of A and a unit
number of one

Enter the following command and press RETURN:
$ BACKUP/VERIFY MUC6:VMS050.B/SAVE_SET DJA1:

The required save set is transferred from the distribution tape cartridge
to the system disk. 1 This takes approximately 25 minutes. During this
process, the procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

This message indicates that the required save set has been transferred to
the system disk and the files are being checked for errors. Approximately
25 minutes later the procedure displays the following message:
%BACKUP-I-PROCDONE, Operation completed. Processing finished at 31-DEC-1988 15:45
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 online and ready.
Enter "YES" to continue:

Press CTRL/P to put the system in console mode.

The BACKUP command creates a system disk that includes a DIGITAL-provided set of volume parameters,
including a CLUSTER_SIZE (disk access scheme) of 1. For more information, see the note at the end of
Section 8.3.

4-5

Installing the VMS Operating System
4.5 Creating a System Disk on a Local Drive

Remove the tape cartridge labeled VAX/VMS VS.OBIN TKSO. Insert the
console tape cartridge.

To boot the system disk, enter the BOOT command in the following
format:
>>> B /XMI:a /BI:b DUu

where:

•

a is the XMI node number of the node being accessed

•

b is the VAXBI node number of the node being accessed

•

u is the unit number of the system disk

For example, if your system disk has a unit number of 1, on VAXBI node
number 4, and XMI node number D, enter the following command and
press RETURN:
>>> B /XMI:D /BI:4 DU1

Booting the system takes several minutes.

When the boot is complete, the procedure displays some messages and
asks you for the date and time. Enter the date and time using the 24-hour
clock format and press RETURN. For example:

Note: The procedure displays warning messages, similar to the following,
that the VMS license is not registered. Continue with the installation
procedure. Follow the instructions for registering the VMS license
after you finish the installation.
F

E
M

D
A
0

B
A

9
M

2
p

p
+

NODE #
TYP
STF
BPD
ETF
BPD
XBI D +

A2
32
ROM= 1.0

ILV
64 Mb

Ai
32
EEPROM = 1.0/1.0

SN= NI0128

Loading system software.
VAX/VMS Version BI50 Major version id = 01 Minor version id = 00
VAX/VMS V5.0 Installation Procedure
%SMP-I-CPUBOOTED, CPU #4 has joined the PRIMARY CPU in multiprocessor operation
%%%%%%%%%%% OPCOM 31-DEC-1988 15:48:12.72 %%%%%%%%%%%
Logfile has been initialized by operator _OPAO:
Logfile is SYS$SYSROOT: [SYSMGR]OPERATOR.LOG;1
%LICENSE-F-EMTLDB, License database contains no license records
%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
%%%%%%%%%%% OPCOM 31-DEC-1988 15:35:12.02 %%%%%%%%%%%
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
Startup processing continuing ...
Please enter the date and time (DD-MMM-YYYY HH:MM):31-DEC-1988 15:50

4-6

Installing the VMS Operating System
4.5 Creating a System Disk on a Local Drive

The procedure asks for the volume label of the system disk. A volume
label is the name the VMS operating system uses to refer to the system
disk. If you have a VAXcluster environment, each system disk must have
a unique volume label.
You can press RETURN to accept the default volume label, VMSRLS, or
you can enter a volume label of your choice. The volume label can be 1
to 12 characters long; spaces are not allowed. For example:
If this system disk is to be used in a cluster with multiple
system disks, then each system disk must have a unique volume label.
Any nodes having system disks with duplicate volume labels will fail
to boot into the cluster.
You may indicate a volume label of 1 to 12 characters in length. If you
wish to use the default label of VMSRL5 just press RETURN in response to
the next question.
Enter the volume label for this system disk (no spaces) [VMSRL5] : SYSDSK

The procedure asks which drive holds the distribution tape cartridge.
Remove the console tape cartridge and insert the tape cartridge labeled
VAX/VMS VS.OBIN TKSO. Enter the device name of the source-drive. For
example, suppose the source-drive is a TKSO tape drive with a controller
designation of C and a unit number of six. Enter the following and press
RETURN:
Enter the name of the drive holding the distribution media (DDCU): MUC6:

Several minutes later the system displays the following messages:
%MOUNT-I-MOUNTED,. SYSTEM mounted on _MUC6:
Restoring LIBRARY saveset.

To continue the installation procedure, go to Section 4.7.

4.6

Creating a System Disk on an HSC Drive
This section provides instructions for installing the VMS operating system on
a system disk that is on an HSC drive in a VAXcluster environment.
The VMS files are stored on the distribution tape cartridge as three save sets:
required, library, and optional. This section describes the steps for transferring
the required save set from the distribution tape cartridge to your system disk.
The instructions refer to the source-drive and the target-drive where:
•

The source-drive is the drive that holds the distribution tape cartridge

•

The target-drive is the drive that holds the system disk

Determine the device name for the source-drive and the target-drive, using
Table 3-1. Write these names on a piece of paper. You will need this
information throughout the installation.

To transfer the required save set to your system disk, enter the BACKUP
command in the following format:
$ BACKUP/VERIFY source-drive:VMS050.B/SAVE_SET hsc-name$target-drive:

4-7

Installing the VMS Operating System
4.6 Creating a System Disk on an HSC Drive

Substitute the appropriate device names for source-drive and target-drive.
Make sure you put a colon (:)after each device name and that you use
zeros in the device names and VMS050. Precede target-drive with the
HSC name and a dollar sign ( $ ) and press RETURN.
For example, if your system has the following configuration:
•

A TK50 source-drive with a controller designation of C and a unit
number of six

•

An HSC-based RA81 target-drive with an HSC name of YOURS, a
controller designation of A, and a unit number of one

Enter the following command and press RETURN:
$BACKUP/VERIFY MUC6:VMS050.B/SAVE_SET YOURS$DUA1:

The required save set is transferred from the distribution tape cartridge
to the system disk. 1 This takes approximately 25 minutes. During the
process, you see the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

Press CTRL/P to put the system in console mode.

Remove the tape cartridge labeled VAX/VMS V5.0 BIN TK50. Insert the
console tape cartridge.

To boot the system disk, use the BOOT command in the following format:
>>>BOOT /XMI:a /BI:b /NODE:c DUu

where:

•

a is the XMI node number of the CI

•

b is the VAXBI node number of the CI

•

c is the HSC node number (in hexadecimal) of the node being

accessed
•

u is the unit number of the system disk

Booting the system takes several minutes.

When the boot is complete, the procedure displays some messages and
asks you for the date and time. Enter the date and time using the 24-hour
clock format and press RETURN. For example:

Note: The procedure displays warning messages, similar to the following,
that the VMS license is not registered. Continue with the installation
1

4-8

Installing the VMS Operating System
4.6 Creating a System Disk on an HSC Drive

procedure. Follow the instructions for registering the VMS license
after you finish the installation.
F

E
M

D
A
0

B
A

9
M

4
p

2
p

NODE #
TYP
STF
BPD
ETF
BPD
XBI D +

A2
32
ROM= 1.0

A1
32

ILV
64 Mb

EEPROM = 1.0/1.0 SN= NI0128

Loading system software.
VAX/VMS Version BI50 Major version id = 01 Minor version id = 00

VAX/VMS V5.0 Installation Procedure
%SMP-I-CPUBOOTED, CPU #4 has joined the PRIMARY CPU in multiprocessor operation
%%%%%%%%%%% OPCOM 31-0CT-1988 15:48:12.72 %%%%%%%%%%%
Logfile has been initialized by operator _OPAO:
Logfile is SYS$SYSROOT: [SYSMGR]OPERATOR.LOG;1
%LICENSE-F-EMTLDB, License database contains no license records
%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
%%%%%%%%%%% OPCOM 31-DEC-1988 15:35:12.02 %%%%%%%%%%%
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
Startup processing continuing ..
Please enter the date and time (DD-MMM-YYYY HH:MM):31-DEC-1988 15:50

4-9

Installing the VMS Operating System
4.6 Creating a System Disk on an HSC Drive

Several minutes later, the system displays the following messages:
%MOUNT-I-MOUNTED, SYSTEM

mounted on _MUC6:

Restoring LIBRARY saveset.

To continue the installation, go to Section 4.7.

4. 7

Transferring the Library and Optional Save Sets
This section describes the steps for transferring the library and optional save
sets from the distribution tape cartridge to the system disk.
1

The installation procedure now transfers the library and optional save sets
to your system disk. This takes approximately 60 minutes. During this
time the procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OPTIONAL saveset.
%BACKUP-I-STARTVERIFY, starting verification pass
Creating [VMS$COMMON] directory tree.
In a cluster, you can run multiple systems sharing all files except
PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP AND VAXVMSSYS.PAR.
Will this node be a cluster member? (Y/N)

If you are installing the VMS operating system on a standalone system,
type N (for NO), press RETURN, and go to step 3.
If you are installing the VMS operating system in a cluster, type Y (for
YES), press RETURN, and go to step 2.

Note: If you answer YES to the VAXcluster question, you must have a
V AXcluster license.
2

The procedure displays the following message:
Now configuring system to be a cluster member.

Determine the type of cluster configuration you want to create
(configuration types are described in the VMS VAXcluster Manual.)
Table 4-1 lists the questions you are asked if you want a CI-only
configuration. Table 4-2 lists the questions you are asked if you want
either a local area or mixed-interconnect configuration. Typical responses
are explained in the tables.
Table 4-1

Installation Questions for Cl-Only Configurations

Question

How to Respond

Will this node be a cluster member (Y /N)?

Enter Y.

What is the node's DECnet node name?

Enter the DECnet node name-for
example, JUPITR. The DECnet node
name may be from 1 to 6 alphanumeric
characters in length and may not include
dollar signs or underscores.

4-10

Installing the VMS Operating System
4. 7 Transferring the Library and Optional Save Sets

Table 4-1 (Cont.)

Installation Questions for Cl-Only Configurations

Question

How to Respond

What is the node's DECnet node address?

Enter the DECnet node address-for
example, 2.2

Will the Ethernet be used for cluster communications (Y /N)?

Enter N. The Ethernet is not used for
cluster (SCS internode) communications in
Cl-only configurations.

Will JUPITR be a disk server (Y /N)?

Enter Y or N, depending on your
configuration requirements. Refer to the
VMS VAXcluster Manual for information
on served cluster disks.

Enter a value for JUPITR' s ALLOCLASS parameter:

If the system is connected to a dual-ported
disk, enter the appropriate allocation class
value (it must be a value between 1 and
255). Otherwise, enter 0.

Does this cluster contain a quorum disk (Y /N)?

Enter Y or N, depending on your
configuration. If you enter Y, the
procedure asks for the name of the
quorum disk. Enter the device name of the
quorum disk.

Table 4-2

Installation Questions for Local Area and Mixed-Interconnect Configurations

Question

How to Respond

Will this node be a cluster member (Y /N)?

Enter Y.

What is the node's DECnet node name?

Enter the DECnet node name-for
example, JUPITR. The DECnet node
name may be from 1 to 6 alphanumeric
characters in length and may not include
dollar signs or underscores.

What is the node's DECnet node address?

Enter the DECnet node address-for
example, 2.2

Will the Ethernet be used for cluster communications (Y /N)?

Enter Y. The Ethernet is required for
cluster (SCS internode) communications
in local area and mixed-interconnect
configurations.

Enter this cluster's group number:

Enter a number in the range from 1-4095
or 61440-65535.

Enter this cluster's password:

Enter the cluster password. The password
must be from 1 to 31 alphanumeric
characters in length and may include dollar
signs and underscores.

Re-enter this cluster's password for verification:

Re-enter the password.

Will JUPITR be a disk server (Y /N)?

Enter Y. In local area and mixedinterconnect configurations, the system
disk is always served to the cluster.
Refer to the VMS VAXc/uster Manual for
information on served cluster disks.

4-11

Installing the VMS Operating System
4. 7 Transferring the Library and Optional Save Sets

Table 4-2 (Cont.)

Installation Questions for Local Area and Mixed-Interconnect
Configurations

Question

How to Respond

Will JUPITR serve HSC disks (Y)?

Enter a response appropriate for your
configuration.

Enter a value for JUPITR's ALLOCLASS parameter:

Enter the appropriate allocation class
value. If you have a mixed-interconnect
configuration, the value must be between
1 and 255; you cannot enter 0.

Does this cluster contain a quorum disk (Y /N)?

Enter Y or N, depending on your
configuration. If you enter Y, the
procedure asks for the name of the
quorum disk. Enter the device name of the
quorum disk.

The procedure displays the following message:
You may now remove the distribution tape from MUC6:.

Remove the distribution tape cartridge from the tape cartridge drive.

The procedure asks you for new passwords for the SYSTEM, SYSTEST,
and FIELD accounts. Passwords must be at least eight characters in
length; they do not appear on the display. Press RETURN after you enter
each one. After you enter the passwords, the procedure checks each one
to make sure it meets the requirements for a good password.For example:
Now we will ask you for passwords for the following accounts:
SYSTEM, SYSTEST, FIELD
Enter new password for account SYSTEM: PANCAKES
Re-enter the password for account SYSTEM for verification: PANCAKES
%UAF-I-MDFYMSG, user record(s) updated
Enter new password for account SYSTEST: BRATWURST
Re-enter the password for account SYSTEST for verification: BRATWURST
%UAF-I-MDFYMSG, user record(s) updated
Enter new password for account FIELD: ZIRHUMBA
Re-enter new password for account FIELD for verification: ZIRHUMBA
%UAF-I-MDFYMSG, user record(s) updated
The procedure will now check and verify the passwords for the
following accounts:
SYSTEM, FIELD, SYSTEST,.SYSTEST_CLIG
Passwords that can be guessed easily will not be accepted.

If the procedure verifies the passwords, it displays the following
messages:
%VMS-I-PWD_OKAY, account password for SYSTEM verified
%VMS-I-PWD_OKAY, account password for FIELD verified
%VMS-I-PWD_OKAY, account password for SYSTEST verified

If you enter a password incorrectly or if the password is too easy to guess,
the procedure displays error messages similar to the following:
%VMS-I-PWD_INVALID, account password for SYSTEM is invalid
%VMS-I-PWD_WEAK, password is too easy to guess
Because of the preceding error, you must take action to secure this account.
You must either disable this account, change its password, or do both.

4-12

Installing the VMS Operating System
4. 7 Transferring the Library and Optional Save Sets

When the procedure asks if you want to disable the account, type N (for
NO) and press RETURN. When the procedure asks if you want to enter
a new password, type Y (for YES) and press RETURN. Then enter a new
password. For example:
Do you want to disable this account (Y/N)? N
Do you want to change the account password (Y/N)? Y
You must now select a new primary password for the SYSTEM account. The
password you select must be at least 8 characters in length an may not
be the same as the name of the account:
New password: WILLIWAW
Verification:WILLIWAW
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_SET, primary password for account SYSTEM set

After you have entered the passwords, the procedure creates your
RIGHTS database and displays the following message:
Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT
Ignore any "%SYSTEM-F-DUPIDENT, duplicate identifier" errors

%UAF-I-RDBDONEMSG, rights database modified

4.8

After your RIGHTS database is created, go to Section 4.8 to install the
mandatory update and run AUTOGEN.

Installing the Mandatory Update and Running AUTOGEN
Follow the directions in this section to install the mandatory update and run
AUTOGEN. AUTOGEN evaluates your hardware configuration and estimates
typical workloads. It then sets system parameters, the sizes of the page, swap,
and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN
finishes, the installation procedure is complete.
1

After the procedure creates your RIGHTS database, it displays the
following message:
After the installation finishes, you may want to do one or more of the
following tasks:
- DECOMPRESS THE SYSTEM LIBRARIES - For space considerations, many of the system
libraries are shipped in a data compressed format. If you have enough disk
space, you may decompress them for faster access. Use SYS$UPDATE:LIBDECOMP.COM
to data expand the libraries. If you choose not to decompress these libraries
there will be a negative impact on the performance of the HELP and LINK
commands.
-BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit
using the procedure described in you VMS installation and operations
guide which is supplied with your VAX processor.
Continuing the VAX/VMS 5.0 installation procedure.
Configuring all devices on the system.
You must now install the MANDATORY UPDATE, which can be found
on a separate distribution volume.
VAX/VMS Software Product Installation Procedure V5.0
It is 31-DEC-1988 at 16:35
Enter a (?) at any time for help.

4-13

Installing the VMS Operating System
4.8 Installing the Mandatory Update and Running AUTOGEN

The procedure asks you for the device name of the drive that contains the
mandatory update. Enter the following and press RETURN:
*Where will the distribution volumes be mounted: CSA1:

The procedure displays the following series of messages:
Please mount the first volume of the set on CSA1:
*Are you ready?

Insert the tape cartridge labeled VAX/VMS VS.O BIN TKSO
MANDATORY UPDATE in the console drive. When you are ready
to continue, type Y and press RETURN. The procedure displays the
following series of messages:
%MOUNT-I-MOUNTED, VMSMUP

mounted on _CSA1:

The following products will be processed:
VMSMUP V5.0
Beginning installation of VMSMUP V5.0 at 16:45
%VMSINSTAL-I-RESTORE, Restoring product saveset A...
Installing VMS V5.0 mandatory update
Do you want to purge files replaced by this installation [YES]?

Press RETURN (for YES) and go to the next step.

Depending on the version of VMS you are installing, the mandatory
update procedure might ask for certain information. Read the screen
displays for instructions. When the procedure is finished, it displays the
following message:
VMSINSTAL procedure done at 15:30

AUTOGEN runs and displays the following series of messages:
Running AUTOGEN to compute new SYSGEN parameters.
An attempt may be made to re-size the pagefile or swapfile. If
there is insufficient room on the disk, the recommended size is
displayed with a message that the file should be created or
extended manually by the system manager later on.
Running AUTOGEN - Please wait

After AUTOGEN finishes, the procedure displays a series of shutdown
messages that begin as follows:
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
upgrade will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown

4-14

After the system shuts down, press CTRL/P to put the system in console
mode.

Installing the VMS Operating System
4.8 Installing the Mandatory Update and Running AUTOGEN

Remove the tape cartridge labeled TKSO MANDATORY UPDATE and
insert the console tape cartridge.

Boot the system using the boot command in the following format:
>>> B /XMI:a /BI:b [/NODE:c] DUu

where:

•

a is the XMI node number of the node being accessed

•

b is the VAXBI node number of the node being accessed

•

c is the HSC node number (in hexadecimal) of the node being
accessed. The /NODE qualifier is not necessary if you are booting
from a local disk

•

u is the unit number of the system disk

10 After the system reboots the procedure displays the following message:

Note: The procedure might display warning messages that the VMS and
VAXcluster licenses must be registered. Be sure to register these
licenses when the installation procedure finishes.
VAX/VMS Version V5.0 Major version id = 01 Minor version id = 00
%SMP-I-CPUBOOTED, CPU #4 has joined the PRIMARY CPU in multiprocessor operation
You have successfully installed the VMS operating system.
The system is now executing the STARTUP procedure.
Please await the completion of STARTUP before logging
into the system (approximately three minutes).
%%%%%%%%%%% OPCOM 31-DEC-1988 16:50 %%%%%%%%%%%
Logfile has been initialized by operator _$0PAO:
Logfile is SYS$SYSROOT: [SYSMGR]OPERATOR.LOG;1

Finally, the procedure displays informational messages as well as
accounting information. For example:
Startup processing continuing.
%SET-I-INTSET, login interactive limit=64, current interactive value = 0
31-DEC-1988 15:00:00.00
SYSTEM
job terminated at 31-DEC-1988 15:00:00.00
Accounting information:
Buffered I/O count:
133
Direct I/0 count:
12
Page faults:
325
Charged CPU time: 0 00:00:55.23

Peak working set size:
401
Peak virtual size:
2379
Mounted volumes:
0
Elapsed time:
0 00:01:31.24

At this point the VMS operating system is running.
11 Press RETURN. The system asks you for a user name and password.
Log in to the SYSTEM account so that you can perform certain postinstallation tasks. For example:
Welcome to VAX/VMS V5.0
USERNAME: SYSTEM
PASSWORD: PANCAKES

Welcome to VAX/VMS V5.0

4-15

Installing the VMS Operating System
4.8 Installing the Mandatory Update and Running AUTOGEN

If you forget the password, follow the instructions for breaking into the

system in the Guide to Setting Up a VMS System.

1 2 There are several things you must do before you can use the system. For
complete information, see Chapter 5.

4-16

After Installing VMS

After you have installed the VMS operating system, you need to perform
several important tasks to prepare the system for operation. This chapter tells
you what the tasks are, whether they are optional or required, and the order
in which you perform them. The following list summarizes the tasks that are
described in this chapter:

5.1

•

Registering your licenses-You must register the VMS license that came
with the software. You must also register the licenses you have for any
system integrated products that you purchased.

•

Removing unwanted files from the system disk -You can free up space
on the system disk by removing the VMS files that you do not need.

•

Customizing the system-Depending on whether you have a standalone
system or a system that is part of a VAXcluster environment, there are
several things you must do.

•

Testing the system-Once you have customized the system, run the VMS
User Environment Test Program (UETP) to test the system.

•

Decompressing the system libraries-After you test the system, you can
decompress the system libraries.

•

Backing up the system disk-To protect all the work you have just done,
make a backup copy of the system disk.

Registering Your Licenses
The VMS license lets you use the VMS operating system. You must register
this license.
After you register the VMS license, you must register the licenses for any of
the following system integrated products you have purchased:
•

VAXclusters

•

DECnet-VAX

•

RMS Journaling

•

Volume Shadowing

For step-by-step instructions on registering licenses, see the current version of
the VMS Release Notes.

5-1

After Installing VMS
5.2 Removing Unwanted Files with VMSTAILOR

5.2

Removing Unwanted Files with VMSTAILOR
Read this section if you want to remove some of the VMS operating system
files that you do not need from the system disk. For example, if you are not
running DECnet-VAX, you do not need the network support files. You can
remove unwanted files with the VMSTAILOR program. Log into the SYSTEM
account, enter the following command, and press RETURN:
$ RUN SYS$UPDATE:VMSTAILOR

The VMSTAILOR program asks you if you want to tailor files ON or OFF.
Type OFF to remove unwanted files.
The VMSTAILOR program lists each group of files and its size in blocks. Files
are grouped according to their function. For example, all the files required
for cluster support are in one group. A file group is made up of many small
subgroups. You can eliminate an entire group of files, or you can eliminate
one or more of its subgroups.
Decide which file groups or subgroups you do not need to support your
system. The VMSTAILOR program displays step-by-step instructions that are
easy to follow.
VMSTAILOR displays the names of the files it deletes. After it finishes,
AUTOGEN runs automatically to make the adjustments that are necessary
after system files are deleted.

Note: You can use VMSTAILOR at any time to delete or add groups of VMS
files to the system disk. After adding files to the system disk, you should
apply any updates that affect them.
For example, suppose you do not need the VMS Version 5.0 MAIL utility
and you run VMST AILOR to remove those files. Later on, if you decide
you want to use MAIL, you can run VMST AILOR to return the MAIL
files to the system disk. You then apply any VMS upgrade or update that
has occurred since 5.0 that affected the MAIL utility.

5.3

Customizing the System
You must customize the system disk so that it automatically performs certain
tasks when you boot. In addition, if your computer is part of a VAXcluster
environment, you must prepare the cluster operating environment and build
the cluster.
For instructions on customizing the system, read the following documentation
(in the order given):
1

Read Chapter 7 in this book. This chapter explains the different ways to
boot the system. It also tells you how to shut down the system.

If the computer is part of a VAXcluster environment, read the VMS
VAXcluster Manual for further information on setting up a cluster.
a.

Start by reading Chapter 1, which contains general information on
VAXclusters environments.

b. Then follow the directions in Chapter 2 to configure the DECnet-VAX

network. In addition, Chapter 2 tells you how to coordinate the
cluster command procedures and system files.
c.

5-2

Follow the directions in Chapter 3 to build the cluster.

After Installing VMS
5.3 Customizing the System

If you have a standalone system, read the Guide to Setting Up a VMS
System for instructions on customizing and using your system. You will
find information on the following tasks:

a. Editing the template files SYCONFIG.COM, SYLOGICALS.COM,
SYLOGIN.COM, and SYSTARTUP_VS.COM
b. Setting up user accounts

c. Adjusting system parameters

5.4

Testing the System
You must run the User Environment Test Package (UETP) to verify the
installation. For complete information, see Chapter 6. Note that UETP needs
at least 1200 free blocks on the system disk.

5.5

Decompressing the System Libraries
Decompressing the system libraries gives the system faster access to the
libraries. The decompressed libraries require approximately 5000 additional
blocks of disk space. To find out how much disk space you have, enter the
following command and press RETURN:
$ SHOW DEVICE SYS$SYSDEVICE

If you have enough room on the disk, you can decompress the libraries.
The decompression process takes approximately a half hour. Log into the
SYSTEM account, enter the following command, and press RETURN:
$ ©SYS$UPDATE:LIBDECOMP.COM

5.6

Backing Up the System Disk
Now that you have spent a lot of time and effort customizing and testing
the system, protect your work by making a backup copy of the system disk.
DIGITAL recommends that you perform the following operations:
•

Make a standalone backup kit

•

Back up the system disk

For complete information on these operations, see Chapter 8. Once you
have backed up the system disk, install any software products that you have
purchased. Follow the directions given in the software product manuals.

5-3

Running UETP

The User Environment Test Package (UETP) is a VMS software package
designed to test whether the VMS operating system is installed correctly.
UETP puts the system through a series of tests that simulate a typical user
environment, making demands on the system that are similar to demands
that might occur in everyday use.
UETP is not a diagnostic program; it does not attempt to test every feature
exhaustively. When UETP runs to completion without encountering
nonrecoverable errors, the system being tested is ready for use.
UETP exercises devices and functions that are common to all VMS systems,
with the exception of optional features such as high-level language compilers.
The system components tested include the following:

6.1

•

Most standard peripheral devices

•

The system's multiuser capability

•

DECnet-VAX

•

Clusterwide file access and locks

Summary of UETP Operating Instructions
This section summarizes the procedure for running all phases of UETP with
default values. If you are familiar with the test package, refer to this section.
If you need further information, refer to Section 6.2.
1

Log into the SYSTEST account as follows:
Username: SYSTEST
Password:

Note: Because the SYSTEST and SYSTEST_CLJG accounts have privileges,
unauthorized use of these accounts might compromise the security of
your system.

Make sure no user programs are running or user volumes are mounted.
By design, UETP assumes and requests the exclusive use of system
resources. Unpredictable results could occur if you ignore this restriction.

After you log in, check all devices to be sure that the following conditions
exist:
•

All devices you want to test are powered up and are on line to the
system.

•

Scratch disks are mounted and initialized.

•

Disks contain a directory named [SYSTEST] with OWNER_UIC=[l,7].
(You can create this directory with the DCL command CREATE
/DIRECTORY.)

6-1

Running UETP
6.1 Summary of UETP Operating Instructions

•

Magnetic tape drives that you want to test contain a magnetic tape
reel with at least 600 feet of tape. The magnetic tape is initialized
with the label UETP (using the DCL command INITIALIZE). You
should also mount the magnetic tape to make it available to the
system.

•

Scratch tape cartridges have been inserted in each drive you want to
test and are mounted and initialized with the label UETP.

•

Line printers and hardcopy terminals have plenty of paper.

•

Terminal characteristics and baud rate are set correctly (see the user's
guide for your terminal).

Note that some communications devices need to be set up by DIGITAL
Field Service (see Section 6.3.)
If you encounter any problems in preparing to run UETP, read Section 6.3
before proceeding.

To start UETP, enter the following command and press RETURN:
$ ©UETP

UETP responds with the following question:
Run "ALL" UETP phases or a "SUBSET" [ALL]?

Press RETURN to choose the default response enclosed in brackets.
UETP responds with three more questions in the following sequence:
How many passes of UETP do you wish to run [1]?
How many simulated user loads do you want [n]?
Do you want Long or Short report format [Long]?

Press RETURN after each prompt. After you answer the last question,
UETP initiates its entire sequence of tests, which run to completion
without further input. The final message should look like the following:

*****************************************************

*
*

END OF UETP PASS 1 AT 31-DEC-1988 16:30:09.38

*
*

*****************************************************
5

After UETP runs, check the log files for errors. If testing completes
successfully, the VMS operating system is in proper working order.

Note: After a run of UETP, you should always run the Error Log Utility to
check for hardware problems that can occur during a run of UETP. For
information on running the Error Log Utility, refer to the VMS Error
Log Utility Manual.
If UETP does not complete successfully, refer to Section 6.5.
If you want to run UETP without using the default responses, refer to
Sections 6.4 through 6.4.4, which explain the options.

6-2

Running UETP
6.2 Logging In

6.2

Logging In
Obtain the SYSTEST password from your system manager. Log into the
SYSTEST account from the console terminal as follows:
Username: SYSTEST
Password:

Note: Because SYSTEST has privileges, unauthorized use of this account might
compromise the security of your system.
UETP will fail if you do not run the test from the SYSTEST account. Also,
if you try to run UETP from a terminal other than the console terminal, the
device test phase displays an error message stating that the terminal you are
using is unavailable for testing. You can ignore this message.
After you log into the SYSTEST account, enter the command SHOW USERS
to make sure no user programs are running and no user volumes are
mounted. UETP requires exclusive use of system resources. If you ignore
this restriction, UETP may interfere with applications that depend on these
resources.

6.2.1

SYSTEST Directories
If you logged in successfully, you should be in the root directory [SYSTEST]
on the system disk. UETP uses directories named [SYSTEST] to hold all the
files used by UETP command procedure (UETP .COM) and temporary files
used by UETP during testing.

The DCL command SHOW LOGICAL displays the translation of the logical
name SYS$TEST on a typical system:
$ SHOW LOGICAL SYS$TEST
11
SYS$TEST" = "SYS$SYSROOT: [SYSTEST]"

(LNM$SYSTEM_TABLE)

If you want UETP to test a particular disk, such as a scratch disk, create
either a [SYSTEST] directory or a [SYSO.SYSTEST] directory on that disk.
Section 6.3.2 discusses setting up scratch disks for testing.

6.3

Setting Up for UETP
After you log in, you need to set up the devices on the system for UETP
testing.

Note: Your system may not have all the devices described in this section.
You should check all devices to be sure that the following conditions exist:
•

All devices you want to test are turned on and are on line.

•

Scratch disks are mounted and initialized.

•

Disks contain a directory named [SYSTEST] with OWNER_UIC=[l,7].
Use the CREATE/DIRECTORY command if the [SYSTEST] directory does
not exist on the disk.

•

Scratch magnetic tape reels are physically mounted on each drive you
want tested and are initialized with the label UETP (using the DCL
command INITIALIZE). Make sure magnetic tape reels contain at least
600 feet of tape.

6-3

Running UETP
6.3 Setting Up for UETP

•

Scratch tape cartridges have been inserted in each drive you want to test
and are mounted and initialized with the label UETP.

•

Line printers and hardcopy terminals have plenty of paper.

•

Terminal characteristics and baud rate are set correctly (see the user's
guide for your terminal).

Note that some communications devices discussed in this section need to be
set up by DIGITAL Field Service.

6.3.1

Setting Up the System Disk
Before running UETP, make sure that the system disk has at least 1200
blocks available. Note that large systems, such as systems that run more than
20 load test processes, might require a minimum of 2000 available blocks.
Running multiple passes of UETP causes log files to accumulate in the default
directory, further reducing the amount of disk space available for subsequent
passes.
If disk quotas are enabled on the system disk, you should disable them before

you run UETP.

6.3.2

Setting Up Additional Disks
The disk test uses most of the available free space on each testable disk.
UETP estimates the space that the disk test uses for normal testing as follows:
•

On each testable disk, the device test phase tries to create two files. The
size of these files depends on how much free space is available on the
disk. Usually the test creates each file with 5% of the free space on the
disk. However, if the disk is nearly full, the test creates files that are 5
blocks. If the test cannot create 5 block files, it fails. Only the initial file
creation can cause the device test to fail because of lack of disk space.

•

The test randomly reads and writes blocks of data to the files. After every
multiple of 20 writes for each file, the test tries to extend the file. The
size of this extension is either 5 % of the free disk space, or 5 blocks if the
file was created with 5 blocks. This process of extension continues until
the combined space of the files reaches 75% of the free disk space.

By creating and extending fragmented files in this way, UETP exercises the
disk. This allows the test to check for exceeded quotas or a full disk, and to
adjust for the amount of available disk space.
To prepare each disk drive in the system for UETP testing, use the following
procedure:
1

Place a scratch disk in the drive and spin up the drive. If a scratch disk
is not available, use any disk with a substantial amount of free space;
UETP does not overwrite existing files on any volume. If your scratch
disk contains files that you want to keep, do not initialize the disk; go to
step 3.

If the disk does not contain files you want to save, initialize it. For

example:
$ INITIALIZE DUA1: TEST!

6-4

Running UETP
6.3 Setting Up for UETP

This command initializes DUAl, and assigns the volume label TESTl to
the disk. All volumes must have unique labels.
3

Mount the disk. For example:
$MOUNT/SYSTEM DUA1: TEST1

This command mounts the volume labeled TESTl on DUAL The
/SYSTEM qualifier indicates that you are making the volume available to
all users on the system.
4

UETP uses the [SYSTEST] directory when testing the disk. If the volume
does not contain the directory [SYSTEST], you must create it. For
example:
$ CREATE/DIRECTORY/OWNER_UIC=[1,7] DUA1: [SYSTEST]

This command creates a [SYSTEST] directory on DUAl and assigns a user
identification code (UIC) of [1,7]. The directory must have a UIC of [1,7]
to run UETP.
If the disk you have mounted contains a root directory structure, you can
create the [SYSTEST] directory in the [SYSO.] tree.

6.3.3

Setting Up Magnetic Tape Drives
To set up each magnetic tape drive in the system, use the following
procedure:
1

Place a scratch volume with at least 600 feet of magnetic tape in the tape
drive. Make sure that the write-enable ring is in place.

Position the magnetic tape at the beginning-of-tape (BOT) and put the
drive on line.

Initialize each scratch magnetic tape with the label UETP. For example, if
you have mounted a scratch magnetic tape on MTAl, enter the following
command and press RETURN:
$ INITIALIZE MTA1: UETP

Magnetic tapes must be labeled UETP to be tested.
If you encounter a problem initializing the magnetic tape, or if the test
has a problem accessing the magnetic tape, refer to the description of the
INITIALIZE command in the VMS DCL Dictionary.

6.3.4

Setting Up Tape Cartridge Drives
To set up tape cartridge drives that you wantto test, use the following
procedure:
1

Insert a scratch tape cartridge in the tape cartridge drive.

Initialize the tape cartridge. For example:
$ INITIALIZE MUAO: UETP

Tape cartridges must be labeled UETP to be tested.

6-5

Running UETP
6.3 Setting Up for UETP

If you encounter a problem initializing the tape cartridge, or if the test has
a problem accessing the tape cartridge, refer to the description of the DCL
INITIALIZE command in the VMS DCL Dictionary.

6.3.5

Setting Up Terminals and Line Printers
Terminals and line printers must be turned on to be tested by UETP. They
must also be on line. Check that line printers and hardcopy terminals have
enough paper. The amount of paper required depends on the number of
UETP passes that you plan to execute. Each pass requires two pages for each
line printer and hardcopy terminal.
Check that all terminals are set to the correct baud rate and are assigned
appropriate characteristics (see the user's guide for your terminal).
Spooled devices and devices allocated to queues fail the initialization phase
of UETP and are not tested.

6.3.6

Preparing Ethernet Adapters for UETP Testing
Make sure that no other processes are sharing the device when you run
UETP.

Note: If your system is part of a local area VAXcluster, you will not be able
to test your Ethernet adapter because you need the Ethernet adapter to
maintain your cluster connection.
UETP automatically shuts down DECnet and the LAT-11 server for the
duration of the device tests and restarts them when the device tests are
completed. You must shut down any local applications.

6.3.7

Preparing the DR 11-W for UETP Testing
Note: Only DIGITAL Field Service personnel should set up the DRll-W for
UETP testing.
The DRll-W uses an internal logical loopback mode that tests all
functionality except that of module connectors, cables, and transceivers.
Because random external patterns are generated during this operation, the
user device or other processor might need to be isolated from the DRll-W
being tested until the testing is complete.
To test the DR11-W properly, the ElOS switchpack must be set as follows:
Switch 1

Switch 2

Switch 3

Switch 4

Switch 5

Off

When UETP testing is completed, restore the DRll-W to the proper operating
configuration.

6-6

Running UETP
6.3 Setting Up for UETP

6.3.8

Preparing the DRV11-WA for UETP Testing
Note: Only DIGITAL Field Service personnel should set up the DRVll-WA for
UETP testing.
To prepare the DRVl 1-WA on a MicroVAX for UETP testing, make sure the
following conditions exist:
•

The jumpers on the DRV-llWA board are set to W2, W3, and W6.

•

A loop-back cable is connected to the DRVll-WA board.

•

The DRV-llWA board is in a slot from 8 to 12. If the DRVll-WA is in a
slot other than 8 to 12, you might get timeout errors.

When UETP testing is completed, restore the DRVll-WA to the proper
operating configuration.

6.3.9

Preparing the DR750 or the DR780 for UETP Testing
Note: Only DIGIT AL Field Service personnel should set up the DR750 or DR780
for UETP testing.
To prepare the DR750 or the DR780 for UETP testing, use the following
procedure:
1

Copy the DR780 microcode file, XF780.ULD, from the diagnostic medium
to SYS$SYSTEM. Use the procedure described in the documentation
provided with the DR780 Microcode Kit.

Turn off the power to the DR780.

Make the following DR780 backplane jumper changes:
•

Remove the jumper from W7 and WS.

•

Add a jumper from E04Ml to E04Rl.

•

Add a jumper from E04M2 to E04R2.

Disconnect the DDI cable from the DR780. This cable is either a
BC06V-nn cable, which can be disconnected, or a BC06R-nn cable,
which requires that you remove its paddle card from the backplane of the
DR780.

Restore power to the DR780.

When UETP testing is completed, restore the DR750 or the DR780 to the
proper operating configuration.

6.3.10 Preparing the MA 780 for UETP Testing
Make sure that the MA780 is set up according to the guidelines for shared
memory in the Guide to Maintaining a VMS System.
If you run the MA780 device test individually, the logical name CTRLNAME
must be defined as MPM, regardless of the memory name. As an alternative,
you can enter "MPM" in response to the controller designation prompt.

6-7

Running UETP
6.3 Setting Up for UETP

6.3.11 Preparing a Second LPA 11-K for UETP Testing
If you have two LPAll-Ks, be sure that each is given a systemwide logical
name in the SYS$MANAGER:LPA11STRT.COM file. The logical name for
the first LPAll-K should be LPA11$0, and the logical name for the second
LPAl 1-K should be LPAl 1$1.

6.3.12 Devices Not Tested
UETP does not test the following devices; their status has no effect on UETP
execution:
•

Devices that require operator interaction (such as card readers)

•

Software devices (such as the null device and local memory mailboxes)

UETP does not have specific tests for UDA, HSC, or CI devices; they are
tested implicitly by the disk, magnetic tape, and DECnet tests.
UETP also does not test the console terminal or console drives. If you boot
the system, log in, and start UETP, you have shown that these devices can be
used.

6.3.13 Preparing for VAXcluster Testing
Before you run UETP in a VAXcluster environment, you should check the
SYSTEST_CLIG account. The SYSTEST_CLIG account parallels SYSTEST
except that it is dedicated to running the cluster-integration test. The
requirements for the SYSTEST_CLIG account are as follows:
1

The account should be present in the user authorization file, exactly as
distributed by DIGITAL on each system in your VAXcluster.

Note: You may have disabled the SYSTEST_CLIG account as, part of the
VMS Version 5.0 upgrade procedure. If you did, you should reenable
the SYSTEST_CLIG account before you run UETP.
To reenable the SYSTEST_CLIG account, enter the following commands
and press RETURN after each one:
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> MODIFY /FLAGS=NODISUSER SYSTEST_CLIG
UAF> EXIT

The account should have a null password.

Note: You may have supplied a password for the SYSTEST_CLIG account
as part of the VMS Version 5.0 upgrade procedure. If you did, you
should set the password to the null password before you run UETP.
To set the password of the SYSTEST_CLIG account to the null password,
enter the following commands and press RETURN after each one:

6-8

Running UETP
6.3 Setting Up for UETP

$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> MODIFY /NOPASSWORD SYSTEST_CLIG
UAF> EXIT
$

Note: DIGIT AL recommends that you disable the SYSTEST_CLIG account
after testing has completed.
To disable the SYSTEST_CLIG account, enter the following commands
and press RETURN after each one:
$

SET DEFAULT SYS$SYSTEM

$ RUN AUTHORIZE

UAF> MODIFY /FLAGS=DISUSER SYSTEST_CLIG
UAF> EXIT

The privileges and quotas of the SYSTEST_CLIG account should match
those of the SYSTEST account.

UETP requires little additional preparation for the cluster-integration test
phase beyond the requirements for other UETP test phases. The additional
requirements for cluster integration testing are as follows:
1

Your system must be a member of a VAXcluster. If it is not, UETP
displays a message and does not attempt to run the test.

Your system must use the same deadlock detection interval as the other
systems in the VAXcluster.

The files UETCLIGOO.COM and UETCLIGOO.EXE, located in SYS$TEST,
are necessary for each system included in the test.

DECnet must be set up between the VAXcluster nodes; UETP uses
DECnet to create a process on those nodes. All checks that the test makes
depend on its ability to create the SYSTEST_CLIG processes and to
communicate with them using DECnet.

There must be a [SYSTEST] or [SYSO.SYSTEST] directory on some disk
available to the VAXcluster for each node (both VMS and HSC) in the
cluster. The test uses the same directory as the UETP disk test to create a
file on each cluster node and to see if some other VMS node in the cluster
can share access to that file. There must be one such directory per node;
the test continues with the next cluster node once it has finished with a
file.

6.3.14 Preparing a Small-Disk System
You have a small-disk system if your system disk is an RK07, RD52, or RC25.
After you install the VMS operating system on a small-disk system, you may
not have the 1200 blocks of free disk space required to run UETP successfully.
If you do not have 1200 free blocks on your system disk, use VMSTAILOR
before you run UETP. For instructions on using VMSTAILOR, see Chapter 5.

6-9

Running UETP
6.3 Setting Up for UETP

6.3.15 Preparing DECnet
The DECnet phase of UETP uses more system resources than most other
phases. Before you start UETP, you can choose which remote node you want
the DECnet phase of the test to run from. By specifying the least busy node
to run the DECnet test from, you can minimize disruption to remote system
users.
By default, the file UETDNETOO.COM chooses the node to run the DECnet
test from. If you want to choose the node to run the DECnet test on, enter
the following command before you invoke UETP:
$ DEFINE/GROUP UETP$NODE_ADDRESS node_address

This command equates the group logical name UETP$NODE_ADDRESS to
the node address of the node in your area on which you want to run the
DECnet phase of UETP.
For example:
$DEFINE/GROUP UETP$NODE_ADDRESS 2.121

When you run UETP, a router node attempts to establish a connection
between your node and the node defined by UETP$NODE_ADDRESS.
Occasionally the connection between your node and the router node might be
busy or non-existent. When this happens, the system displays the following
error messages:
%NCP-F-CONNEC, Unable to connect to listener
-SYSTEM-F-REMRSRC, resources at the remote node were insufficient
%NCP-F-CONNEC, Unable to connect to listener
-SYSTEM-F-NOSUCHNODE, remote node is unknown

6.4

Starting UETP
When you have logged in and prepared the system and devices, you are
ready to begin the test.
To start UETP, enter the following command and press RETURN:
$ ©UETP

UETP displays the following prompt:
Run "ALL" UETP phases or a "SUBSET" [ALL]?

Throughout the startup dialog, brackets indicate the default value, which you
can choose by pressing RETURN.
When you are running UETP for the first time, it is a good idea to choose
the default value (ALL) and run all the phases. If you choose ALL, UETP
displays three more questions, which are described in Sections 6.4.2 through
6.4.4. If you want to run all of the test phases, skip the next section.

6-10

Running UETP
6.4 Starting UETP

6.4.1

Running a Subset of Phases
You can run a single phase by entering SUBSET or S in response to the
following prompt:
Run "ALL" UETP phases or a "SUBSET" [ALL]?

UETP prompts you for the phase you want to run as follows:
You can choose one or more of the following phases:
DEVICE, LOAD, DECNET, CLUSTER
Phase(s):

There is no default; enter one or more phase names from the list. Separate
two or more phases with spaces or commas.
If your choice includes the LOAD phase, UETP displays the three prompts

described in the next sections. To run the LOAD phase, refer to the next
section.
If you exclude the LOAD phase, UETP responds with only two prompts:
How many passes of UETP do you wish to run [1]?
Do you want Long or Short report format [Long]?

Sections 6.4.2 and 6.4.4 discuss these questions. After you answer both
questions, the phase you have selected runs to completion.

6.4.2

Single Run Versus Multiple Passes
If you specified the default ALL or a subset of phases at the last prompt,

UETP displays the following message:
How many passes of UETP do you wish to run [1]?

You can repeat the test run as many times as you want. If you enter 1 in
response to the prompt (or press RETURN for the default), UETP stops
after completing a single run. If you specify a number greater than 1, UETP
restarts itself continuously until it completes the number of passes (runs)
specified.
You can run UETP once to check that the system is working, or many times
to evaluate the system's response to continuous use. For example, a field
service technician who is interested only in verifying that a newly installed
system works might run UETP once or twice. A manufacturing technician
might let the system run for several hours as part of the system integration
and test.
When you specify multiple UETP runs, you might want to request a short
console log (see Section 6.4.4). Make certain that all line printers and
hardcopy terminals have enough paper; each run requires two pages.

6-11

Running UETP
6.4 Starting UETP

6.4.3

Defining User Load for Load Test
After you specify the number of passes, UETP prompts you as follows:
How many simulated user loads do you want [n]?

Note: UETP displays this prompt only if you choose to run the LOAD phase,
either implicitly (by running all phases), or explicitly (by running a subset
and specifying the LOAD phase).
The purpose of the load test is to simulate a situation in which a number of
users (detached processes) are competing for system resources. In response
to this prompt, enter the number of users you want to simulate for this test.
The number in brackets is the default value that UETP computed for your
system. The default value depends on the amount of memory and the paging
and swapping space that your system has.
Although the given default value is the best choice, you can increase or
decrease the user load by entering your own response to the prompt.
However, be aware that an increase might cause the test to fail because
of insufficient resources.
If you want to see UETP display the user load equation as it runs, see

Section 6.5.2.

6.4.4

Long and Short Report Format
The following prompt allows you to choose one of two console report
formats:
Do you want Long or Short report format [Long]?

If you choose the long report format (the default), UETP sends all error

messages as well as information on the beginning and end of all phases and
tests to the console terminal. UETP records all its output in the UETP.LOG
file, regardless of your response to this question.
In many cases, it may not be convenient to have UETP write the bulk of
its output to the terminal. For example, if you run UETP from a hardcopy
terminal, the printing of all the output can slow the progress of the tests. This
delay may not be a problem if you have requested only one run; however,
you may prefer to use the short format if you intend to run multiple passes of
UETP from a hardcopy terminal.
If you request the short format, UETP displays status information at the

console, such as error messages and notifications of the beginning and end
of each phase. This information enables you to determine whether UETP
is proceeding normally. If the short console log indicates a problem, you
can look at UETP.LOG for further information. UETP.LOG contains all the
output generated by the various phases, as well as the status information
displayed at the console.
After you choose the report format, UETP initiates its sequence of tests
and runs to completion. If UETP does not complete successfully, refer to
Section 6.5 for troubleshooting information.

6-12

Running UETP
6.4 Starting UETP

6.4.5

Termination of UETP
At the end of a UETP pass, the master command procedure UETP .COM
displays the time at which the pass ended. In addition, UETP.COM
determines whether UETP needs to be restarted. (You can request multiple
passes when you start up the test package; see Section 6.4.2).
At the end of an entire UETP run, UETP.COM deletes temporary files and
does other cleanup activities.
Pressing CTRL/Y or CTRL/C lets you terminate a UETP run before it
completes normally. Normal completion of a UETP run, however, includes
the deletion of miscellaneous files that have been created by UETP for the
purpose of testing. The use of CTRL/Y or CTRL/C might interrupt or prevent
these cleanup procedures.
The effect of these control characters depends on what part of UETP you
are executing. For an explanation of the organization of UETP and its
components, refer to Section 6.6.

6.4.5.1

Using CTRL/Y
Press CTRL/Y to abort a UETP run. Note, however, that cleanup of files and
network processes in the [SYSTEST] directory may not be complete.
If you are running an individual test image, pressing CTRL/Y interrupts the
current UETP test and temporarily returns control to the command interpreter.
While the test is interrupted, you can enter a subset of DCL commands that
are executed within the command interpreter and do not cause the current
image to exit. The VMS DCL Concepts Manual contains a table of commands
that you can use within the command interpreter. In addition, you can enter
any of the following commands:

•

The CONTINUE command continues the test from the point of
interruption (except during execution of the cluster test).

•

The STOP command terminates the test; the test aborts and control
returns to the command interpreter.

Note: Using the STOP command may prevent cleanup procedures from
executing normally. You should use the EXIT command if you want
the image to do cleanup procedures before terminating.
•

The EXIT command does cleanup procedures and terminates the test
(except during execution of the cluster test); control returns to the
command interpreter.

If you enter any DCL command other than CONTINUE, STOP, and EXIT,
the test does cleanup procedures and terminates, and the DCL command
executes.

6-13

Running UETP
6.4 Starting UETP

6.4.5.2

Using CTRL/C
Press CTRL/C to interrupt a UETP run. You cannot continue the same test
phase after you press CTRL/C. UETP automatically goes to the next phase in
the master command procedure.

Some UETP phases react to CTRL/C by cleaning up all activity and
terminating immediately. Such tests display the following message:
%UETP-I-ABORTC, 'testname' to abort this test, type -c

The phases that do not display the previous message terminate all processes
they have started. These processes might not have a chance to complete
normal cleanup procedures.
If you are running an individual test image, however, you can use CTRL/C

to terminate the execution of the image and complete cleanup procedures.
Note that CTRL/C does not complete cleanup procedures for the cluster test.

6.5

Troubleshooting
This section explains the role of UETP in interpreting operational errors in
a VMS operating system. Section 6.5.4 discusses common errors that can
appear in a UETP run and describes how to correct them.

6.5.1

Relationship of UETP to Error Logging and Diagnostics
When UETP encounters an error, it reacts like a user program. Either it
returns an error message and continues, or it reports a fatal error and
terminates the image or phase. In either case, UETP assumes that the
VMS hardware is correctly installed and operating and does not attempt
to diagnose the error.
If the cause of an error is not readily apparent, use the following methods to

diagnose the error:

•

VMS Error Log Utility-Run the Error Log Utility to obtain a detailed
report of hardware and system errors. Error log reports provide
information about the state of the hardware device and 1/0 request
at the time of each error. For information about running the Error Log
Utility, refer to the VMS Error Log Utility Manual.

•

Diagnostic facilities-Use the diagnostic facilities to test exhaustively a
device or medium to isolate the source of the error.

6-14

Running UETP
6. 5 Troubleshooting

6.5.2

Interpreting UETP Output
You can monitor the progress of UETP tests at the terminal from which
they were started. This terminal always displays status information, such as
messages that announce the beginning and end of each phase and messages
that signal an error.
The tests send other types of output to various log files depending on
how you started the tests. The log files contain output generated by the
actual test procedures. Even if UETP completes successfully, with no errors
displayed at the terminal, it is good practice to check these log files for errors.
Furthermore, when errors are displayed at the terminal, check the log files for
more information about their origin and nature.
Each test returns a final completion status to the test controller image,
UETPHASOO, using a termination mailbox. This completion status is an
unsigned longword integer denoting a condition value. As a troubleshooting
aid, UETPHASOO displays the test's final completion status using the $FAO
and $GETMSG system services. Sometimes, however, the $FAO service
needs additional information which cannot be provided using the termination
mailbox. When this happens, UETP displays an error message similar to the
following:
UETP-E-ABORT, !AS aborted at !%D

· When UETP displays these types of error messages, check the log files for
more information. You can also run the individual test to attempt to diagnose
the problem.
The error messages that appear at the terminal and within the log files have
two basic sources:
•

UETP tests

•

System components that are tested

To interpret the messages, you might need to refer either to the VMS System
Messages and Recovery Procedures Reference Volume or to the manual that
describes the individual system component.
Several parts of UETP, such as some device tests, UETINITOO.EXE,
UETCLIGOO.EXE, and UETDNETOO.COM, let you obtain additional
information concerning the progress of the test run or the problems it
encounters. Because this information is usually insignificant, it is not
displayed on the screen. To view the information, enter the following
command and run the program:
$ DEFINE MODE DUMP

The following example shows the output for UETINITOO.EXE on a
VAX 11/750:
$ RUN UETINITOO

Welcome to VAX/VMS UETP Version V5.0
%UETP-I-ABORTC, UETINITOO to abort this test, type -c
You are running on an 11/750 CPU with 8704 pages of memory.
The system was booted from _DRAO: [SYSO.].

6-15

Running UETP
6.5 Troubleshooting

Run "ALL" UETP phases or a "SUBSET" [ALL]?
How many passes of UETP do you wish to run [1]?
The default number of loads is the minimum result of
1) CPU_SCALE * ( (MEM_FREE + MEM_MODIFY) / (WS_SIZE * PER_WS_INUSE))
o.80 * <<
8704 +
323) I <
350 *
0.20))

= 103

2) Free process slots

= 56

3) Free page file pages I Typical use of page file pages per process
18040 I
1000 = 18
How many simulated user loads do you want [18)?
Do you want Long or Short report format [Long]?
UETP starting at 31-DEC-1988 09:08:26.71 with parameters:
DEVICE LOAD DECNET CLUSTER phases, 1 pass, 18 loads, long report.
$

This program does not initiate any phase; it displays the equation used by
UETP to determine user load and the specific factors that are employed in the
current run.
You should respond to the questions by pressing RETURN. After you respond
to the first prompt, the program displays the expressions that determine the
default number of simultaneous processes. The following definitions apply:
•

CPU_SCALE refers to the relative processing power of the CPU in
relation to a VAX-11/780. For example, a VAX-11/785 has a
CPU-SCALE of 1.5 because it has 1.5 times the processing power of a
VAX-11/780 (1.0).

•

MEM_FREE represents memory in pages available to users.

•

MEM_MODIFY represents memory pages on the modified page list.

•

WS_SIZE represents working set size.

•

PER_WS_INUSE represents typical percentage of the working set in
active use for each process.

UETINITOO also displays the specific values represented by the expressions.
In this example, UETP selects 18 as the default for simulated user loads,
because 18 is the minimum result of the three expressions.
You should deassign the logical name MODE before running UETP, unless
you prefer to see the previous breakdown every time you run UETP.

6.5.2.1

Defining a Remote Node for UETP Ethernet Testing
When the UETUNASOO test of the UETP executes, it is sometimes difficult to
determine whether the problems it reports concern the device under test or
the remote device. The easiest way to ensure that the test properly reports
errors on the device under test is to define a "good turnaround." A "good
turnaround" is a remote node that you know turns around Ethernet packets
correctly and is up and waiting in the ready state.

You can make the UETUNASOO test use a known "good turnaround" by
performing the following actions. In the commands that follow, assume that
the "good" device is on node BETA, and that node BETA is already defined in
the network database.

6-16

Running UETP
6.5 Troubleshooting

Find the address of the "good" Ethernet node by using the Network
Control Program (NCP). In order to use NCP, the following conditions
must apply:
•

DECnet must be up and running on the system.

•

The account you are using must have TMPMBX and NETMBX
privileges.

Enter the following commands and press RETURN:
$ RUN SYS$SYSTEM:NCP
NCP> TELL BETA SHOW CHARACTERISTICS ACTIVE LINES

If node BETA has not been defined in your network database, NCP

displays an error message. In this event, specify another "good" node and
retry the command. Otherwise, see your system or network manager.
NCP displays information similar to the following:
Active Line Volatile Characteristics as of 15-0CT-1986 16:13:02
Line = UNA-0
Counter timer
= 28800
Receive buffers
=6
Controller
= normal
Protocol
= Ethernet
Service timer
= 4000
Hardware address
= AA-00-04-00-46-D3
UNA device buff er size
= 1498

Use the displayed hardware address (in this case, AA00040046D3) to
define the logical name TESTNIADR to point to the "good turnaround."
Note that you do not specify the hyphens ( - ).
First, log in to the SYSTEST account. Then enter the following command:
$ DEFINE/SYSTEM TESTNIADR AA00040046D3

Run UETP.

When UETP has completed, deassign the logical name TESTNIADR by
entering the following command:
$ DEASSIGN/SYSTEM TESTNIADR

6.5.3

The Log Files
At the end of a UETP run, the directory SYS$TEST contains a log file named
UETP.LOG. This file contains all information generated by all UETP tests
and phases. If the run involves multiple passes, you will find a version of
UETP.LOG for each pass.
Although UETP .LOG contains information from all the passes, only
information from the latest run is stored in this file. Information from the
previous run is stored in a file named OLDUETP.LOG, which also has a
version for each pass. Using these two files, UETP provides the output from
its tests and phases from the two most recent runs.
The cluster test creates a NETSERVER.LOG file in SYS$TEST for each pass
on each system included in the run. If the test is unable to report errors (for
example, if the connection to another node is lost), the NETSERVER.LOG
file on that node contains the result of the test run on that node. UETP does

6-17

Running UETP
6.5 Troubleshooting

not purge or delete NETSERVER.LOG files; therefore, you must delete them
occasionally to recover disk space.
If a UETP run does not complete normally, SYS$TEST might contain other
log files. Ordinarily these log files are concatenated and placed within
UETP.LOG. You can use any log files that appear on the system disk for
error checking, but you must delete these log files before you run any new
tests. You may delete these log files yourself or rerun the entire UETP, which
checks for old UETP.LOG files and deletes them.

6.5.4

Possible UETP Errors
This section is intended to help you identify and solve problems you might
encounter running UETP. You should refer to this section if you need help
understanding a system failure and isolating its cause. This section is not
intended as a repair manual and is not expected to diagnose any flaws in
your system. It should, however, help you to interpret and act upon the
information in the error messages.
If you are unable to correct an error after following the steps in this section,
you should contact your DIGITAL Field Service representative. Any
information you can supply about the measures you have taken to isolate
the problem will help your DIGITAL Field Service representative diagnose the
problem.

The following are the most common failures encountered while running
UETP:
1

Wrong quotas, privileges, or account

UETINITOl failure

Insufficient disk space

Incorrect VAXcluster setup

Problems during the load test

DECnet error

Errors logged but not displayed

No PCB or swap slots

Hangs

10 Bugchecks and machine checks
The following sections describe these errors and offer the best course of action
for dealing with each one.

6-18

Running UETP
6.5 Troubleshooting

6.5.4.1

Wrong Quotas, Privileges, or Account
If your assigned quotas or privileges do not match standard quotas and
privileges for the SYSTEST account, UETP displays the following error
message:

**********************

*
*

UETINITOO
Error count = 1

*
*

**********************
-UETP-W-TEXT,

The following:

OPER privilege,
BIOLM quota,
ENQLM quota,
FILLM quota,
are nonstandard for the SYSTEST account and may result in UETP errors.

This message informs you that the OPER privilege and the BIOLM, ENQLM,
and FILLM quotas either are not assigned correctly or are not assigned at all.

Note: UETP displays a similar message if you run the cluster integration test
phase, and the privileges and quotas for the SYSTEST_CLIG account are
incorrect. The SYSTEST and SYSTEST_CLIG accounts require the same
privileges and quotas. Take the same action described in this section.
Solution

To correct the problem, use the following procedure:
1

Display all privileges and quotas in effect for the current account using the
DCL commands SHOW PROCESS /PRIVILEGE and SHOW PROCESS
/QUOTA as follows:
$ SHOW PROCESS/PRIVILEGES

31-DEC-1988 18:06:02.89

OPAO:

User

SYSTEST

Process privileges :
CMKRNL
CMEXEC
SYS NAM
GRPNAM
DETACH
DIAGNOSE
LOG_IO
GROUP
PRMCEB
PRMMBX
SETPRV
TMPMBX
NETMBX
VOLPRO
PHY~IO

SYSPRV

may change mode to kernel
may change mode to exec
may insert in system logical name table
may insert in group logical name table
may create detached processes
may diagnose devices
may do logical I/O
may affect other processes in same group
may create permanent common event clusters
may create permanent mailbox
may set any privilege bit
may create temporary mailbox
may create network device
may override volume protection
may do physical I/O
may access objects via system protection

$ SHOW PROCESS/QUOTAS

31-DEC-1988 18:06:03.36

OPAO:

User: SYSTEST

Process Quotas:

. 6-19

Running UETP
6.5 Troubleshooting

Account name: SYSTEST
CPU limit:
Infinite
Buffered I/0 byte count quota:
32768
20
Timer queue entry quota:
19543
Paging file quota:
64
Default page fault cluster:
300
Enqueue quota:
Max detached processes:
0

Direct I/O limit:
Buffered I/O limit:
Open file quota:
Subprocess quota:
AST limit:
Shared file limit:
Max active jobs:

55
18
100

Check that the privileges and quotas assigned to the account match the
following:
Privileges
CMKRNL

CM EXEC

NETMBX

DETACH

PRMCEB

PRMMBX PHY_IO

GRPNAM

TM PM BX VOLPRO

SYSNAM SYSPRV

SETPRV

DIAGNOSE
LOG_IO
GROUP

Quotas
BIOLM: 18

PRCLM: 8

DIOLM: 55

ASTLM: 100

FILLM: 100

BYTLM: 32768

TOELM: 20

CPU: no limit

ENOLM: 300

PGFLOUOT A: 20480

WSDEFAULT: 256

WSOUOTA: 512

WSEXTENT: 2048

If any privileges or quotas are incorrect, run_ the Authorize Utility
(AUTHORIZE) to add them (AUTHORIZE is explained in the VMS
Authorize Utility Manual). As an alternative, you can temporarily
assign the correct privileges with the DCL command SET PROCESS
/PRIVILEGES.

If you are logged in to the wrong account, the following error message asks
you to log in to the SYSTEST account:
$ ©UETP

**********************

* UETINITOO
*
* Error count = 1 *

**********************

-UETP-E-ABORT, UETINITOO aborted at 31-DEC-1988 14:24:10.13
-UETP-E-TEXT, You are logged in to the wrong account.
Please log in to the SYSTEST account.

You must run UETP from the SYSTEST account.

6-20

98
0
0

Running UETP
6. 5 Troubleshooting

6.5.4.2

UETINIT01 Failure
UETINITOl failures are related to peripheral devices; this type of error
message might indicate any of the following:

•

Device failure

•

Device not supported or not mounted

•

Device allocated to another user

•

Device write-locked

•

Lost vacuum on a magnetic tape drive

•

Drive off line

In some cases, the course of action you should take is explicit in the error
message. For example, you might receive a message from the Operator
Communication Facility (OPCOM) process informing you of a problem and
recommending a corrective measure:
%DPCOM, 31-DEC-1988 14:10:52.96, request 1, from user SYSTEST
Please mount volume UETP in device _MTAO:
%MOUNT-I-OPRQST. Please mount volume UETP in device _MTAO:

Other error messages might relate information in which the solution is
implicit:
%UETP-S-BEGIN, UETDISKOO beginning at 31-DEC-1988 13:34:46.03

**********************

*
*

DISK_DRA
Error count = 1

*
*

**********************

-UETP-E-TEXT, RMS file error in file DRAO:DRAOO.TST
-RMS-E-DNR, device not ready or not mounted
%UETP-S-ENDED, UETDISKOO ended at 31-DEC-1988 13:34:46.80

This message tells you that a disk drive is either not ready or not mounted.
From this information, you know where to look for the cause of the failureat the disk drive. If you cannot see the cause of the problem immediately,
check the setup instructions in Section 6.3.
In other cases, the cause of a failure might not be obvious from the
information in the message. The problem might be related to hardware
rather than software. For example, the Ethernet adapter test may produce
one of the following messages if UETP does not have exclusive access to the
Ethernet adapter:
•

Inter-module cable unplugged

•

Self-test failure code 0000000

To run the self-test diagnostic on the Ethernet adapter successfully, UETP
needs exclusive access to the adapter. Either DECnet or the LAT terminal
server also might also want to use the Ethernet adapter, which is a shareable
device. UETP shuts down DECnet and the LAT terminal server for the
duration of the device tests and restarts them when the tests are completed.

6-21

Running UETP
6.5 Troubleshooting

Solution

To determine where or when the failure occurs in the execution of UETP, use
the following procedure:

6.5.4.3

•

Run the device test individually (see Section 6.4.1). By doing this, you
can determine if the failure can be re-created. Also, you are isolating
the cause of the problem by reproducing it using the least amount of
software possible. For example, if the failure occurs only when you
run the entire device phase, and not when you run the affected device
test individually, you can conclude the problem is related to deviceinteraction. Conversely, if you can re-create the error by running the
single device test, then you have proved that the error is not related to
device interaction.

•

Run the device test with different media. If your run of the single device
test succeeded in reproducing the error, the magnetic tape or disk media
could be defective. Running the same test with new media determines
whether this is the problem.

•

Call DIGITAL Field Service. If you have tried all the previous steps
without solving the problem, you should contact your DIGITAL Field
Service representative.

Insufficient Disk Space
When you run continuous passes of UETP, log files accumulate on the disk
from which UETP was run. These files reduce the amount of free disk space
available for each successive pass. If the amount of disk space available
becomes too small for the current load, the following error message appears:
%UETP-S-BEGIN, UETDISKOO beginning at 31-DEC-1988 08:12:24.34
%UETP-I-ABORTC, DISK_DJA to abort this test, type AC

**********************

*
*

DISK_DJA
Error count = 1

*
*

**********************

-UETP-F-TEXT, RMS file error in file DJAO:DJAOO.TST
-RMS-F-FUL, device full (insufficient space for allocation)

**********************

*
*

DISK_DJA
Error count = 2

*
*

**********************

-UETP-F-TEXT, RMS file error in file DJAO:DJA01.TST
-RMS-F-FUL, device full (insufficient space for allocation)
%UETP-E-DESTP, DISK_DJA stopped testing DJA unit 0 at 08:12:36.91
%UETP-S-ENDED, UETDISKOO ended at 31-DEC-1988 08:12:37.98

Solution

Make more space available on the disk. You can do this by using one or
more of the following techniques:

6-22

•

Delete unnecessary files to create more space.

•

Purge files, if multiple versions exist.

•

Mount a volume with sufficient space.

Running UETP
6.5 Troubleshooting

•

Check for disk quotas that may be enabled on the disk. If disk quotas
are enabled, either disable or increase them (see the VMS SYSMAN Utility
Manual for a description of the Disk Quota Utility).

•

Run VMSTAILOR if you have a small-disk system. See your Chapter 5
for more information.

See Sections 6.2.1 and 6.3.2 for a further discussion of disk space.

6.5.4.4

Incorrect Setup of a VAXcluster
Most problems that can occur during the cluster-integration test are related
to improper setup of the VAXcluster or of UETP on the VAXcluster. These
problems are most likely to occur at the following stages of the VAXcluster
test:

•

Near the beginning, when processes on VMS nodes are started

•

Toward the end, when cluster file access is checked

The cluster test phase shows that various VMS nodes in your cluster can
simultaneously access files on selected nodes in the cluster. First, UETP tries
to create a file on a disk drive that is accessible to the other selected nodes
in the cluster. The following are the requirements for creating a file in the
cluster test phase:
•

There must be a [SYSTEST] directory on the disk in either the master file
directory (MFD) or in the root directory [SYSO.].

•

The [SYSTEST] directory must be protected so that the SYSTEST account
can create a file in it.

If UETP is unable to find a suitable device on a certain node, the test displays

a warning message and proceeds to the next cluster node.
Nodes on which the operator's terminal (OPAO) is set to the "No Broadcast"
terminal characteristic will generate the following error message during the
cluster test:

**********************

* UETCLIGOOrnaster *
* Error count = 1 *

**********************

-UETP-E-TEXT, 0 operator consoles timed out on the cluster test warning
and 1 operator console rejected it.
-UETP-E-TEXT, Status returned was,
"%SYSTEM-F-DEVOFFLINE, device is not in configuration or not
available"

Disregard this message if OPAO is set to "No- broadcast".
Solution

Whenever you suspect a problem, you should try to recover the
SYS$TEST:NETSERVER.LOG file that was created when the SYSTEST_
CLIG process was created. This file may contain additional error information
that could not be transmitted to the node running the test. If it was not
possible to create the SYSTEST_CLIG process on some node, the system
accounting file for that node may contain a final process status in a process
termination record.

6-23

Running UETP
6.5 Troubleshooting

The following problems can occur during a cluster test:
•

Logging in at other nodes-This problem is due to incorrect setup for the
cluster test at the remote VMS node. For example, if you specified
a password for the SYSTEST_CLIG account or if you disabled the
SYSTEST_CLIG account, the test displays the following message:
%SYSTEM-F-INVLOGIN, login information invalid at remote node

Refer to Section 6.3.13 and Section 6.5.2.1 for information on preparing
for VAXcluster testing.

6.5.4.5

•

Communicating with other nodes-A message indicates a DECnet
problem. Check the NETSERVER.LOG file on the affected node to
determine the cause.

•

Taking out locks or detecting deadlocks-The most likely cause of this
problem is that you are not logged in to the SYSTEST account. Another
possibility is that your cluster is not configured properly.

•

Creating files on VAXcluster nodes-This problem is due to incorrect
setup for the cluster test; refer to Section 6.3.13 for information on
preparing for VAXcluster testing.

Problems During the Load Test
A variety of errors can occur during the load test, because the command
procedures that are started during the tests run several utilities and do many
functions. Tracking a problem can be difficult because UETP deletes the log
files that are generated during the load test (see Section 6.6.3).
Solution
If a problem occurs during the load test and the cause is not obvious, you can

modify UETP.COM to preserve the log files as follows:
1

Add the /NODELETE qualifier to the following line:
$ TCNTRL UETLOADOO.DAT/PARALLEL_COUNT='LOADS/REPORT_TYPE='REPORT

Delete the following line:
$ DELETE UETLD*.LDG;*

Rerun the load test with these changes to try to re-create the problem.
If you re-create the problem, look at the contents of the appropriate log file.

To determine which log file to read, you need to understand the scheme by
which the load test names its processes and log files. (The log file names are
derived from the process names.)
The load test creates processes that are named in the following format:
UETLOADnn_nnnn

6-24

Running UETP
6.5 Troubleshooting

For example:
%UETP-I-BEGIN, UETLOADOO beginning at 31-DEC-1988 15:45:08.97
%UETP-I-BEGIN, UETLOAD02_0000 beginning at 31-DEC-1988 15:45:09.42
%UETP-I-BEGIN, UETLOAD03_0001 beginning at 31-DEC-1988 15:45:09.63
%UETP-I-BEGIN, UETLOAD04_0002 beginning at 31-DEC-1988 15:45:10.76
%UETP-I-BEGIN, UETLOAD05_0003 beginning at 31-DEC-1988 15:45:11.28
%UETP-I-BEGIN, UETLOAD06_0004 beginning at 31-DEC-1988 15:45:12.56
%UETP-I-BEGIN, UETLOAD07_0005 beginning at 31-DEC-1988 15:45:13.81
%UETP-I-BEGIN, UETLOAD08_0006 beginning at 31-DEC-1988 15:45:14.94
%UETP-I-BEGIN, UETLOAD09_0007 beginning at 31-DEC-1988 15:45:16.99
%UETP-I-BEGIN, UETLOAD10_0008 beginning at 31-DEC-1988 15:45:19.32
%UETP-I-BEGIN, UETLOAD11_0009 beginning at 31-DEC-1988 15:45:19.94
%UETP-I-BEGIN, UETLOAD02_0010 beginning at 31-DEC-1988 15:45:20.20
%UETP-I-BEGIN, UETLOAD03_0011 beginning at 31-DEC-1988 15:45:21.94
%UETP-I-BEGIN, UETLOAD04_0012 beginning at 31-DEC-1988 15:45:22.99

Note that if more than ten processes are created, the numbering sequence for
the UETLOADnn portion of the process name starts over at UETLOAD02;
however, the four digits of the _nnnn portion continue to increase.
Each load test process creates two log files. The first log file is created by the
test controller; the second log file is created by the process itself. The log file
that you need to look at for error information on any given load test process
is the one that was created by the test controller (the first log file).
The load test log file derives its file name from the process name, appending
the last four digits of the process name (from the _nnnn portion) to UETLO.
The test-controller log file and the process log file for each process use the
same file name; however, the process log file has the higher version number
of the two. For example, the log files created by the process UETLOADOS_
0003 would be named as follows:
UETL00003.LOG;l (test-controller log file)
UETL00003.LOG;2 (process log file)
Make sure that you look at the log file with the lower version number; that
file contains the load test commands and error information.
After you have isolated the problem, restore UETP.COM to its original state
and delete the log files from the load test (UETLO*.LOG;*); failure to delete
these files might result in disk space problems.

6.5.4.6

DECnet Error
A DECnet error message might indicate that the network is unavailable.
Solution
•

If DECnet is included in your system, register the authorization key (see
the VMS Release Notes).

•

If DECnet is not included in your system, ignore the message; it is normal
and does not affect the UETP run.

If you encounter other DECnet-related errors, you should do the following:

•

Run DECnet as a single phase (see Section 6.4.1) to determine whether
the error can be re-created.

•

Refer to the VMS System Messages and Recovery Procedures Reference

Volume.

6-25

Running UETP
6.5 Troubleshooting

6.5.4.7

Errors Logged but Not Displayed
If no errors are displayed at the console terminal or reported in the
UETP.LOG file, you should run the Error Log Utility to see if any errors

were logged in the ERRLOG.SYS file. See the VMS Error Log Utility Manual
for information about running the Error Log Utility.

6.5.4.8

No PCB or Swap Slots
The following error message indicates that no process control block (PCB) or
swap slots are available:
%UETP-I-BEGIN, UETLDADOO beginning at 31-DEC-1988 07:47:16.50
%UETP-I-BEGIN, UETLOAD02_0000 beginning at 31-DEC-1988 07:47:16.76
%UETP-I-BEGIN, UETLDAD03_0001 beginning at 31-DEC-1988 07:47:16.92
%UETP-I-BEGIN, UETLOAD04_0002 beginning at 31-DEC-1988 07:47:17.13
%UETP-I-BEGIN, UETLDAD05_0003 beginning at 31-DEC-1988 07:47:17.35
%UETP-I-BEGIN, UETLOAD06_0004 beginning at 31-DEC-1988 07:47:17.61
%UETP-W-TEXT, The process -UETLOAD07_0005- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-TEXT, The process -UETLOAD08_0006- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-TEXT, The process -UETLOAD09_0007- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-TEXT, The process -UETLOAD10_0008- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-TEXT, The process -UETLOAD11_0009- was unable to be created,
the error message is
-SYSTEM-F-NOSLOT, no pcb or swap slot available
%UETP-W-ABORT, UETLDADOO aborted at 31-DEC-1988 07:47:54.10
-UETP-W-TEXT, Aborted via a user CTRL/C.

***************************************************

END OF UETP PASS 1 AT

31-DEC-1988 07:48:03.17

***************************************************
Solution

To solve this problem, use the following procedure:

6-26

Rerun individually the phase that caused the error message (the LOAD
phase in the previous example) to see if the error can be reproduced.

Increase the size of the page file, using either the command procedure
SYS$UPDATE:SWAPFILES.COM or the System Generation Utility (see
the VMS System Generation Utility Manual).

Increase the SYSGEN parameter MAXPROCESSCNT, if necessary, and
reboot the system.

Increase both the page file size and the MAXPROCESSCNT, if necessary.

Running UETP
6.5 Troubleshooting

6.5.4.9

Hangs
If there is no keyboard response or system disk activity, the system may be
hung.
Solution

A system hang can be difficult to trace; you should always save the dump file
for reference. To learn why the system hung, run the System Dump Analyzer
as described in the VMS System Dump Analyzer Utility Manual. Reasons for a
system hang include the following:
•

Insufficient pool space-Reboot the system with a larger value for
NPAGEVIR.

•

Insufficient page file space-Increase the page file space using the System
Generation Utility as described in the VMS System Generation Utility

Manual.

•

IfO device failure causing driver-permanent loop-Call DIGITAL Field
Service.

6.5.4.10

Bugchecks and Machine Checks
When the system aborts its run, a bugcheck message appears at the console.
Solution

Call DIGITAL Field Service. Often a hardware problem causes bugchecks and
machine checks; there is no easy way to solve bugchecks or machine checks.
It is important, however, that you save the SYS$SYSTEM:SYSDUMP.DMP
and ERRLOG.SYS files so that they are available for examination. It is also
important to know whether the failure can be re-created; you can verify this
by running UETP again.

6.6

UETP Tests and Phases
This section explains in detail the organization of UETP and the individual
components within the test package.
You run UETP by starting a master command procedure, which contains
commands that start each test phase. The procedure begins by prompting
you for information needed by the various test phases. (See Section 6.4 for a
detailed description of starting UETP.)
The master command procedure, UETP.COM, contains commands that
initiate each test phase. UETP.COM also contains commands that do such
tasks as defining logical names and manipulating files generated by the tests.
The UETP.COM procedure also issues commands to start the test controlling
program, UETPHASOO.EXE, which in turn controls each test phase. The
test controller starts up multiple detached processes. It also reports their
completion status and other information the processes report to it.
The following sections describe the various UETP test phases.

6-27

Running UETP
6.6 UETP Tests and Phases

6.6.1

Initialization Phase
The following occurs during the initialization phase:
•

The image UETINITOO.EXE prompts you for information (see Section 6.4).
Your information defines variables that affect the execution of UETP tests.

•

The image UETINITOl.EXE gathers information on all the controllers
in the system and on their associated devices. This image writes the
information into a file called UETINIDEV.DAT.

•

Using the information in UETSUPDEV.DAT, UETINITOl.EXE verifies
which devices in the system are operable by running the appropriate
device test. Each device test completes a simple read/write operation
to each device. If a device fails this test, the device's entry in
UETINIDEV.DAT specifies that the device cannot be tested. As a result,
subsequent UETP tests ignore that device.

•

For each testable controller, UETINITOl.EXE writes a line into a file called
UETCONTOO.DAT. The line associates a test file with the controller it
tests.

A summary of UETINIDEV.DAT always exists in UETP.LOG, and
UETINITOl.EXE sends that summary to the console if you have requested
the long report format.

6.6.2

Device Test Phase
The device test phase includes separate tests for each type of device, such
as disk, magnetic tape, line printer, and terminal. This section explains the
device test phase and presents instructions for testing a single device. If you
want to run the entire device test phase individually, refer to Section 6.4.1.

6.6.2.1

How the Device Phase Works
The UETP device test phase starts an executable image, the phase controller
UETPHASOO, which creates a detached process for every device controller
to be tested. For example, if a system includes three terminal controllers,
one line printer controller, and two disk controllers, the image creates six
detached processes. In parallel, the detached processes execute images that
test the various types of devices.

The initialization phase of UETP creates a file called UETINIDEV.DAT
and a file called UETCONTOO.DAT. UETINIDEV.DAT contains data on
the VMS-supported controllers in the system and their associated devices;
UETCONTOO.DAT associates a device test image with each testable controller.
UETPHASOO uses the information in UETCONTOO.DAT to find a device
controller name to pass to each detached process that it creates. UETPHASOO
passes the controller name by writing it to a mailbox that is SYS$INPUT to
individual tests. Each detached process uses that data to determine which
controller to test. The test image then searches UETINIDEV.DAT for the
device controller and for all testable units on that controller. The phase
controller terminates when all devices on all controllers have completed
testing.

6-28

Running UETP
6.6 UETP Tests and Phases

Because UETCONTOO.DAT is deleted automatically at the end of a UETP run,
you cannot run the device phase unless you start UETP.COM; you can run
only individual test images. UETINIDEV.DAT exists in SYS$TEST unless you
explicitly delete it.

6.6.2.2

Running a Single Device Test
You must be logged in to the SYSTEST account to run the individual tests as
described in this section. Also, a copy of UETINIDEV.DAT must exist. If a
copy of the file is not present from a previous run (a run of the entire UETP
or a run of the device test phase creates UETINIDEV.DAT), you can create it.
Note that when you run a single test, no log file is created; the test sends all
its output to your terminal.
If you do not want to test all the device types, you can test a specific
controller by choosing a test image name from Table 6-1 and executing it
as in the following example:
$ RUN UETTTYSOO

Controller designation?: TTB

UETP prompts you for the controller designation and the device code. Unless
you are testing your own terminal, you must explicitly designate a controller
name. If you are running the terminal test, you can press RETURN to test
your terminal only.
If you plan to repeat the run several times, you might find it more convenient
to define the logical name CTRLNAME as follows:
$ DEFINE CTRLNAME TTB
$ RUN UETTTYSOO

When you define the controller name in this way, the logical name
CTRLNAME remains assigned after the test completes. To deassign this
logical name, use the DCL command DEASSIGN as follows:
$ DEASSIGN CTRLNAME

Format of UETINIDEV.DAT

The UETINIDEV.DAT file is an ASCII sequential file that you can type or edit
if necessary. The contents of this file are shown in the following command
sequence:
$ TYPE UETINIDEV.DAT

DDB x ddd
UCB y uuuuu
END OF UETINIDEV.DAT

The symbols in this example are defined as follows:
Symbol

Value

T, if there are any testable units for this controller; N, if this controller
is not to be tested

T, if this unit is testable; N, if this unit is not testable

6-29

Running UETP
6.6 UETP Tests and Phases

Symbol

Value

ddd

device controller name, for example, DUA

uuuuu

device unit number, for example, 25

UETINIDEV.DAT contains a DDB (device data block) line for each controller
connected or visible to your system. After the DDB line there is a UCB (unit
control block) line for each unit connected to that controller. In addition, if
your system uses MA780 memory in a loosely coupled CPU configuration,
UETINIDEV.DAT includes one UCB line for each MA780 memory. A device
test can test a particular device only if both the DDB line and the UCB line
indicate that the device is testable.
Running a Test in Loop Mode
If you want to put extra stress on a device, you can run the device test in loop
mode, which causes the test to run indefinitely. For example:
$ DEFINE MODE LOOP
$ RUN UETDISKOO

Controller designation?: DRA
%UETP-I-TEXT, End of pass 1 with 980 iterations at 31-DEC-1988 16:18:51:03
~c

You must use CTRL/C to terminate the test run. If you use CTRL/Y, UETP
does not complete cleanup procedures.
Functions of Individual Device Tests

For each disk in the system, the disk test allocates two files into which it
randomly writes blocks of data. The test then checks the data, reports any
errors to SYS$0UTPUT, and deletes the disk files.
When you run the disk test phase in a cluster environment, the test accesses
all disks that are mounted by the system being tested, and users of the disk
being tested might encounter an insufficient disk space problem. You should
warn users on remote nodes (who share disks with users on the local system)
that UETP may be testing a disk they are using.
The magnetic tape test exercises all the magnetic tape drives in the system.
The test creates a large file on each mounted magnetic tape, into which
it writes multiple sequential records of varying sizes. After writing the
records, the test rewinds the magnetic tape, validates the written records, and
reinitializes the magnetic tape.
The terminal and line printer test generates several pages or screens of
output, in which each page or screen contains a header line and a test pattern
of ASCII characters. A header line contains the test name, the device name,
the date, and the time.
For the laboratory peripheral accelerator (LPAll-K), the test image
determines the configuration on the LPAll-K's 1/0 bus. The image loads all
types of microcode to the LPAll-K and reads or writes data for each device
on the LPAl 1-K 1/0 bus.
The communications device tests fill the transmit message buffer with random
data; then, using loopback mode, they transmit and receive the message
several times. To check that the looped-back data are correct, an AST routine
is associated with a $QIO read to compare the received message against the

6-30

Running UETP
6.6 UETP Tests and Phases

transmitted message. The procedure is repeated using messages of different
lengths.
The interface device tests put their respective devices in maintenance mode,
write random data, and then verify the data.
The MA780 device test creates and modifies mailboxes, common event flags,
and global sections in shared memory; then it verifies that modifications can
be made. You can run MA780 tests in parallel from separate systems so that
the tests interact with each other through common MA780 memories.
The Ethernet adapter test does self-test diagnostics on the device. It also does
read and write tasks with test data that uses various adapter modes (such as
internal loopback and external loopback).
Table 6-1 lists the device test images and the devices to be tested.
Table 6-1

6.6.3

The Device Tests

Test Image Name

Devices Tested

UETDISKOO.EXE

Disks

UETTAPEOO.EXE

Magnetic tape drives and tape cartridge drives

UETTTYSOO.EXE

Terminals and line printers

UETLP AKOO. EXE

LPA 11-K

UETCOMSOO.EXE

DMC11, DMR11

UETDMPFOO. EXE

DMF32, DMP 11

UETDR 1WOO.EXE

DR11-W

UETDR7800. EXE

DR780, DR750

UETMA 7800.EXE

MA780

UETUNASOO. EXE

Ethernet adapters

System Load Test Phase
The purpose of the system load test is to simulate a number of terminal
users who are demanding system resources simultaneously. The system load
tests, directed by the file UETLOADOO.DAT, create a number of detached
processes that execute various command procedures. Each process simulates
a user logged in at a terminal; the commands within each procedure are
the same types of commands that a user enters from a terminal. The load
test creates the detached processes in quick succession, and generally the
processes execute their command procedures simultaneously. The effect on
the system is analogous to an equal number of users concurrently issuing
commands from terminals. In this way, the load test creates an environment
that is similar to normal system use.
The load test uses the logical name LOADS to determine the number
of detached processes to create. When you initiate the UETP command
procedure, it prompts for the number of users to be simulated (see
Section 6.4.3) and consequently the number of detached processes to be
created. Your response, which depends on the amount of memory and the
swapping and paging space in your system, defines the group logical name
LOADS.

6-31

Running UETP.
6.6 UETP Tests and Phases

The UETP master command procedure deassigns all group logical names
assigned by its tests as part of the termination phase. The group logical
name LOADS remains assigned only if the UETP package does not complete
normally.
The command procedures executed by the load test can generate a large
amount of output, depending on the number of detached processes created.
For each detached process (or user), the test creates a version of an output file
called UETLOnnnn.LOG ("nnnn" represents a string of numeric characters).
The console displays only status information as the load test progresses.
Whether the load test runs as part of the entire UETP or as an individual
phase, UETP combines the UETLOnnnn.LOG files, writes the output to the
file UETP.LOG, and deletes the individual output files.
You can run the system load test as a single phase by selecting LOAD from
the choices offered in the startup dialog (see Section 6.4.1).

6.6.4

DECnet Test Phase
If DECnet is included in your VMS system, a run of the entire UETP

automatically tests DECnet hardware and software. Because communications
devices are allocated to DECnet and the DECnet devices cannot be tested
by the UETP device test, UETP shuts down DECnet for the duration of the
initialization and device test phases. It turns DECnet on again after those
phases are completed. The DECnet node and circuit counters are zeroed at
the beginning of the DECnet test to allow for failure monitoring during the
run.
As with other UETP phases, you can run the DECnet phase individually by
following the procedure described in Section 6.4.1.

6.6.4.1

Environment

The DECnet test will work successfully on VMS systems connected to all
DECnet-supported node types, including routing and nonrouting nodes and
several different types of operating systems (such as RSTS, RSX, TOPS, and
RT). There must be some sort of default access on remote systems to copy
files between systems. The DECnet phase tests the following:
•

The node UETP is running on

•

All circuits in sequence

•

All adjacent or first-hop nodes and all circuits in parallel

There is no limit on the number of communication lines supported by the·
tests. A test on one adjacent node should last no more than two minutes at
normal communications transfer rates.

6-32

Running UETP
6.6 UETP Tests and Phases

6.6.4.2

How the DECnet Phase Works
UETP (under the control of UETPHASOO.EXE) reads the file
UETDNETOO.DAT and completes the following steps during the DECnet
phase:
1

Executes a set of Network Control Program (NCP) LOOP EXECUTOR
commands to test the node on which UETP is running.

Uses NCP to execute the command SHOW ACTIVE CIRCUITS. The
results are placed in UETININET.TMP, from which UETP creates the data
file UETININET.DAT. The UETININET.TMP file contains the following
information for any circuit in the ON state but not in transition:
•

Circuit name

•

Node address

•

Node name (if one exists)

The UETININET.TMP file is used throughout the DECnet phase to
determine which devices to test.

Uses the UETININET.TMP file to create an NCP command procedure
for each testable circuit. Each command procedure contains a set of NCP
commands to zero the circuit and node counters and to test the circuit
and adjacent node by copying files back and forth.

Note: If you do not want the counters zeroed, do not test DECnet.

Executes the command procedures from step 3 in parallel to simulate a
heavy user load. The simulated user load is the lesser of the following
values:
•

The number of testable circuits, multiplied by two

•

The maximum number of user-detached processes that can be
created on the system before it runs out of resources (determined
by UETINITOO)

Executes a program, UETNETSOO.EXE, that uses the UETININET.DAT
file to check the circuit and node counters for each testable circuit. If a
counter indicates possible degradation (by being nonzero), its name and
value are reported to the console. All counters are reported in the log
file, but only the counters that indicate degradation are reported to the
console. Following is an example of UETNETSOO output:
%UETP-S-BEGIN, UETNETSOO beginning at 31-DEC-1988 13:45:33.18
%UETP-W-TEXT, Circuit DMC-0 to (NODENAME1) OK.
%UETP-I-TEXT, Node (NODENAME2) over DMC-1 response timeouts= 1.
%UETP-I-TEXT, Circuit DMC-1 to (NODENAME2) local buffer errors = 34.
%UETP-I-TEXT, Node (NODENAME3) over DMP-0 response timeouts= 3.
%UETP-S-ENDED, UETNETSOO ended at 31-DEC-1988 13:45:36.34

Because degradation is not necessarily an error, the test's success is
determined by you, not the system. The following counters indicate
possible degradation:

6-33

Running UETP
6.6 UETP Tests and Phases

For Circuits

•
•

Arriving congestion loss

•

Transit congestion loss

•
•
•
•

Line down

Corruption loss

Initialization failure
Data errors inbound
Data errors outbound

•

Remote reply timeouts

•
•
•
•

Local reply timeouts

•

Remote process errors

•
•
•

Local process errors

Remote buffer errors
Local buffer errors
Selection timeouts

Locally initiated resets
Network initiated resets

For Nodes

•
•

•
•
•
•
•
•
•

6-34

Response timeouts
Received connect resource errors
Aged packet loss
Node unreachable packet loss
Node out of range packet loss
Oversized packet loss
Packet format error
Partial routing update loss
Verification reject

Running UETP
6.6 UETP Tests and Phases

6.6.5

Cluster-Integration Test Phase
The cluster-integration test phase, which consists of a single program and
a command file, depends heavily on DECnet. This phase uses DECnet to
create SYSTEST_CLIG processes on each VMS node in the cluster and to
communicate with each node. SYSTEST_CLIG is an account that is parallel
to SYSTEST, but limited so that it can only be used as part of the clusterintegration test. The following restrictions on the SYSTEST_CLJG account are
necessary for a correct run of the cluster test phase:
•

The account must be enabled and the password must be null. For more
information, see Section 6.3.13.

•

The UIC must be the same as that of the SYSTEST account.

•

The account must have the same privileges and quotas as the SYSTEST
account. For more information, see Section 6.5.4.1.

•

The account can allow login only through DECnet.

•

The account must be locked into running UETCLIGOO.COM when it logs
in.

These items are necessary to ensure the security and privacy of your system.
If the test cannot create a SYSTEST_CLIG process on some VMS node, it
gives the reason for the failure and ignores that node for the lock tests and
for sharing access during the file test. The test makes no attempt to report
information relating to a failure at the node where creation was attempted;
that is, any possible log file is not copied to the node running the test. If
there is a problem communicating with a SYSTEST_CLIG process after it has
been created, the test excludes it from further lock and file sharing tests. At
the end of the cluster-integration test, an attempt is made to report any errors
seen by that node.
UETCLIGOO.EXE has two threads of execution: the primary and the
secondary. The first, or primary thread, checks the cluster configuration;
that is, it checks the VMS and HSC nodes and the disks attached to each
of them that can be seen from the node running the test. For selected VMS
nodes, the primary thread attempts to start up a SYSTEST_CLIG process
through DECnet. Those nodes on which the primary thread was able to start
a SYSTEST_CLIG process run the command file UETCLIGOO.COM, which
starts up UETCLIGOO.EXE and runs the secondary execution thread.
The process running the primary thread checks to see that it can communicate
with the processes running the secondary threads. It then instructs them to
take out locks so that a deadlock situation is created.
The primary thread tries to create a file on some disk on selected VMS and
HSC nodes in the cluster. The primary thread writes a block, reads it back,
and verifies it. The primary thread selects one VMS node at random and
asks that node to read the block and verify it. The primary extends the file
by writing another block and has the secondary read and verify the second
block. The file is deleted.
The secondary processes exit. They copy to the primary process the contents
of their SYS$ERROR files, so that the UETP log file and console report
show all problems in a central place. DECnet automatically creates a
NETSERVER.LOG in SYS$TEST as the test is run, so that if necessary,
you can read that file later from the node in question.

6-35

Running UETP
6.6 UETP Tests and Phases

During the test run, the primary process uses cluster $BRKTHRU to announce
the beginning and ending of the test to each VMS node's console terminal.
You can define the group logical name MODE to the equivalence string
DUMP to trace most events as they occur. Note that the logical name
definitions apply only to the node on which they were defined. You must
define MODE on each system in the VAXcluster on which you want to trace
events.

6-36

Part II
Part II describes frequently performed system operations such as system
startup, shutdown, and backup.

System Startup and Shutdown

This chapter contains information on the following:

7. 1

•

Overview of booting the system

•

Ways to boot the system

•

Shutting down the system

Overview of Booting
Booting is the process of loading system software into memory. The VAX
6200 series boots using small programs stored in ROM (read-only memory)
called boot primitives. Because the boot process is slightly different for each
type of device, a boot primitive exists in ROM for each device the system
supports. A boot primitive does the following:
•

Sets up the system environment.

•

Deposits values in registers

•

Tells the system what type of drive the system disk is on as well as the
controller designation and unit number of the drive. The /XMI, /Bl, and
/NODE qualifiers to the BOOT command give the system additional
information about where the system disk is located.

•

Loads the VMS operating system.

The boot process consists of the following steps:
1

You enter the BOOT command and any applicable qualifiers. The
specified boot primitive deposits information in the general purpose
registers.

VMS.EXE, the primary boot program, is loaded from the boot
block on the system disk (block zero) into memory. VMS.EXE is
a program that allows access to the system disk. VMS.EXE locates
SYS$SYSTEM:SYSBOOT.EXE on the system disk and loads it into
memory.

SYSBOOT.EXE loads the SYSGEN parameters stored in
SYS$SYSTEM: VAXVMSSYS.P AR and checks the conversational boot
flag. If the flag is set, the procedure stops and displays the SYSBOOT>
prompt. If the flag is not set, SYS BOOT .EXE loads the VMS executive
into memory and transfers control to the VMS executive.

When the VMS executive finishes, it executes the SWAPPER process.

The SWAPPER creates the SYSINIT process.

SYSINIT creates the STARTUP process.

7-1

System Startup and Shutdown
7 .1 Overview of Booting

STARTUP executes SYS$SYSTEM:STARTUP.COM (unless you indicated
another file at the SYSBOOT> prompt) and SYSTARTUP_VS.COM.
The current values of SYSGEN parameters are written back to
VAXVMSSYS.P AR.

The boot process finishes and can log into the VMS operating system.

By setting certain System Generation Utility (SYSGEN) parameters, you can
control how many CPUs are activated at boot time and the character of the
multiprocessing system. In a multiprocessing system, the primary CPU is
always booted. By default, all available CPUs are also booted. If you want
to change the default, you can set the SYSGEN parameter SMP_CPUS to
tell the system which secondary CPUs to boot. For information on SYSGEN
parameters that affect multiprocessing, see the VMS System Generation Utility

Manual.

7 .2

Booting from a Local Disk Drive
To boot the system from a local disk drive, use the following procedure:
1

Make sure the console tape cartridge is in the console drive.

If the VMS operating system is not running, go to step 3.
If the VMS operating system is running, log into the SYSTEM account.
Enter the following command and press RETURN:
$ ©SYS$SYSTEM:SHUTDOWN

Answer the questions. When the procedure asks if an automatic system
reboot should be performed, press RETURN for NO. When the system
shuts down, the procedure displays the following message:
SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM

Press CTRL/P to put the system in console mode.

Enter the BOOT command in the following format:
>>> BOOT [/R5:a]

/XMI:b

/BI:c

[/R3:d]

DUu

The following table lists the qualifiers to the BOOT command:

7-2

System Startup and Shutdown
7 .2 Booting from a Local Disk Drive

Table 7-1

Boot Command Qualifiers (Local Disks)

Qualifiers

Function

/R5:a

Deposits a value (a) into R5. This value affects the
execution of VMS.EXE. The /R5 qualifier is optional.

/XMl:b

Specifies the XMI node number (b) of the node being
accessed. Defaults to the lowest numbered 1/0 device.

/Bl:c

Specifies the Bl node number (c) of the node being
accessed. Defaults to zero.

/R3:d

This qualifier is not required unless you are using
Volume Shadowing. For more information, see the
VAX Volume Shadowing Manual.

Specifies the unit number of the drive holding the
system disk.

For example, suppose you want to boot a local disk that has a unit
number of one and your system has the following configuration:
•

The disk is connected to the VAXBI at node 2.

•

The VAXBI you are using is connected to the XMI at node 3.

Enter the following command and press RETURN:
>>> BOOT/XMI:3/BI:2 DU1

7 .3

Booting from an HSC Disk Drive
To boot the system from an HSC disk drive, use the following procedure.
1

Make sure the console tape cartridge is in the console drive.

If the VMS operating system is not running, go to step 3.
If the VMS operating system is running, log into the SYSTEM account.
Enter the following command and press RETURN:
$ ©SYS$SYSTEM:SHUTDOWN

Press CTRL/P to put the system in console mode.

Enter the BOOT command in the following format:
>>>BOOT [/R5:a]

/XMI:b

/BI:c

[/R3:d]

/NODE:e

DUu

The following table lists the qualifiers to the BOOT command:

7-3

System Startup and Shutdown
7 .3 Booting from an HSC Disk Drive

Table 7-2

Boot Command Qualifiers (HSC Disks)

Qualifiers

Function

/R5:a

Deposits a value (a) into R5. This value affects the
execution of VMS.EXE. The /R5 qualifier is optional.

/XMl:b

Specifies the XMI node number (b) of the node being
accessed. Defaults to the lowest numbered 1/0 device.

/Bl:c

Specifies the Bl node number (c) of the node being
accessed and must be used with the /XMI qualifier.
Defaults to zero.

/R3:d

This qualifier is not required unless you are using
Volume Shadowing. For more information, see the
VAX Volume Shadowing Manual.

/NODE:e

Specifies the HSC node number of the node being
accessed. The HSC node number is hexadecimal. You
can specify a maximum of two HSC node numbers (if
two HSCs are available).

Specifies the unit number of the drive holding the
system disk.

For example, suppose you want to boot an HSC disk that has a unit
number of one and your system has the following configuration:
•

The disk is connected to the VAXBI at node 2.

•

The VAXBI you are using is connected to the XMI at node 3.

•

The disk is available to two HSCs, node numbers OE and 02.

Enter the following command and press RETURN:
>>> BOOT/XMI:3/BI:2/NODE:OE02 DU1

Specifying two HSCs gives the system an alternate route in case one is
disabled.

7 .4

Performing a Conversational Boot
A conversational boot is most commonly used in research and development
environments and during software upgrades. Perform a conversational boot
when you want to stop the boot process before it completes. The boot
process stops after it loads SYS$SYSTEM:SYSBOOT.EXE and displays the
SYSBOOT> prompt. At the SYSBOOT> prompt you can enter certain
SYSGEN commands to do the following:

7-4

•
•
•
•
•

Look at system parameter values

•

Specify a minimum startup

Change system parameter values
Specify another parameter file
Specify another system startup command procedure
Select the default system parameter file if you modified system parameters
to values that render the system unbootable

System Startup and Shutdown
7 .4 Performing a Conversational Boot

There are several ways to perform a conversational boot. The following
procedure is the most direct:

Make sure the console tape cartridge is in the tape cartridge drive.

If the VMS operating system is not running, go to step 3.
If the VMS operating system is running, log into the SYSTEM account.

Answer the questions. When the procedure asks if an automatic system
reboot should be performed, press RETURN for NO. When the procedure
is finished, it displays the following message:
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

3 , Press CTRL/P to put the system in console mode.
4

To begin the conversational boot, enter the following command at the
console-mode prompt(> > > ):
>>> B /R5:1 /XMI:a /BI:b [/R3:c] [/NODE:d] DUu

where:

•

a is the XMI node number of the system disk

•

b is the VAXBI node number of the system disk

•

c pertains to Volume Shadowing. This qualifier is not required unless
you are using Volume Shadowing. For more information, see the

VAX Volume Shadowing Manual.
•

d is the HSC node number of the node being accessed. The /NODE
qualifier is not necessary if you are booting from a local disk. The
HSC node number is in hexadecimal. You can deposit a maximum of
two HSC node numbers (if two HSCs are available).

•

u is the unit number of the drive holding the system disk.

At the SYSBOOT> prompt, you can enter any of the SYSGEN
commands listed in Table 7-3. For more information about these
SYSGEN commands, see VMS System Generation Utility Manual.

When you finish using SYSGEN commands, enter the CONTINUE
command to complete the BOOT process.

Table 7-3

SVSGEN Commands Used in SVSBOOT

Command

Description

CONTINUE

Resumes the boot procedure

DISABLE CHECKS

Inhibits checking of parameter values
specified with the SET command

ENABLE CHECKS

Permits checking of parameter values
specified with the SET command

7-5

System Startup and Shutdown
7 .4 Performing a Conversational Boot

Table 7-3 (Cont.)

SYSGEN Commands Used in SYSBOOT

Command

Description

HELP

Displays a summary of the SYSBOOT
commands on the terminal

SET parameter-name

Establishes the value of a system parameter

SET /STARTUP

Sets the name of the system startup
command procedure

SHOW [parameter]

Displays active, current, default, maximum,
and minimum values for specific parameters;
use qualifiers to display characteristics of
parameters grouped by categories

USE [file-spec]

Specifies a parameter file to be used as
a source of values (you must enter the
entire file specification, including device and
directory; you cannot specify a logical name)

The following examples illustrate some operations you can perform during a
conversational boot.
You can enter the following commands to set a new value for the SYSGEN
parameter WSMAX to 512 and to complete the boot procedure:
SYSBOOT> SET WSMAX 512
SYSBOOT> CONTINUE

When the VMS operating system displays the following message, the new
SYSGEN parameter value becomes active.
SYSTEM

job terminated at 31-DEC-1988 15:05:11.01

If you modified the system parameters to values that render the system

unbootable, enter the following commands to boot using default values:
SYSBOOT> USE DEFAULT
SYSBOOT> CONTINUE

You can also use the conversational boot to specify a minimum startup. For
example, if you want to boot the system and avoid autoconfiguring all the
peripheral devices, enter the following command:
SYSBOOT> SET STARTUP_P1 "MIN"

This command initiates a minimum startup that performs the following
sequence of operations:
1

Starts the processes that control error logging, the job controller, and the
operator's log

Installs known images

Defines the number of interactive users as eight

Logs off

Because this procedure does not invoke SYSTARTUP_VS.COM, it does not
autoconfigure the system's peripheral devices.

7-6

System Startup and Shutdown
7 .4 Performing a Conversational Boot

The value of STARTUP_Pl is saved and affects future boot operations. After
the operating system boots, you can run SYSGEN to reset STARTUP_Pl. For
example, enter the following commands to reset STARTUP_Pl to its default
value (null):
$RUN SYS$SYSTEM:SYSGEN
SYSGEN> USE CURRENT
SYSGEN> SET STARTUP_P1 1111
SYSGEN> WRITE CURRENT
SYSGEN> EXIT

7. 5

Automatic Restart
The VMS operating system can restart automatically from the default boot
device designated in EEROM. To restart the system using the RESTART
button, see Section 2.2.3.
If you set the lower keylock switch to AUTO START, the system will restart
automatically under the following conditions:

•

When the system power comes on after a power failure

•

After an error halt

This type of automatic restart is known as a warm start because if the battery
backup unit was able to supply power to memory, the contents of memory
were preserved.
The system also performs an automatic restart if you shut it down and specify
Y at the auto reboot prompt. This type of automatic restart is known as a
cold start because the memory was reinitialized before the system rebooted.
Before the system can perform a cold start, you must designate the default
boot device using the SET BOOT DEFAULT command (see Section 7.5.1).

7.5.1

Setting a Default Disk
If you want the system to reboot automatically after you shut it down, you
must designate the default boot device. To specify a default boot device, use
the SET BOOT command in the following format:

Note: To use any SET command, the lower keylock switch must be in the
UPDATE position.
>>> SET BOOT DEFAULT ddu

For example, if you want the default boot device to be DUO, enter the
following and press RETURN:
>>> SET BOOT DEFAULT DUO

Because the /XMI and /BI qualifiers were not specified, the system uses their
default values.
The next time you boot the system, enter the BOOT command and press
RETURN:
>>> B

The system boots from the device you have designated as the default boot
device.

7-7

System Startup and Shutdown
7. 5 Automatic Restart

To clear the default designation, enter the following and press RETURN:
>>> SET BOOT DEFAULT

For more information on the SET command, see the owner's manual.

7 .6

Booting With XDELTA
XDELTA is a debugging tool that system programmers use. To use XDELTA,
you must boot the system in a special way. For more information on booting
with XDELTA, see the VMS Delta/XDelta Utility Manual.

7. 7

Booting from a Different Directory on the System Disk
The VMS operating system is installed in the system root directory named
[SYSO]. You can use VMSKITBLD, as described in the Guide to Setting Up a
VMS System, to add a copy of the VMS operating system to another system
root directory on the system disk.
To boot from an different directory on the system disk, use the following
procedure:
1

Make sure the console tape cartridge is in the console drive.

If the VMS operating system is not running, go to step 3.
If the VMS operating system is running, log into the SYSTEM account.

Press CTRL/P to put the system in console mode.

Enter the BOOT command in the following format:
>>>BOOT /R5:a0000000

/XMI:b

/BI:c

[/R3:d]

[/NODE:e]

DUu

where:

7-8

•

a is the name of the root directory from which you want to boot.

•

b is the XMI node number of the system disk.

•

c is the VAXBI node number of the system disk.

•

d pertains to Volume Shadowing. This qualifier is not required unless
you are using Volume Shadowing. For more information, see the
VAX Volume Shadowing Manual.

•

e is the HSC node number of the node being accessed. The /NODE
qualifier is not necessary if you are booting from a local disk. The
HSC node number is in hexadecimal. You can deposit a maximum of
two HSC node numbers (if two HSCs are available).

•

u is the unit number bf the drive holding the system disk.

System Startup and Shutdown
7. 7 Booting from a Different Directory on the System Disk

For example, suppose you want to boot from SYSC on an HSC disk
that has a unit number of one and your system has the following
configuration:
•

The disk is connected to the VAXBI at node 2.

•

The VAXBI you are using is connected to the XMI at node 3.

•

The disk is available to two HSCs, node numbers OE and 02.

Enter the following command and press RETURN:
>>> BOOT/R5:COOOOOOO/XMI:3/BI:2/NODE:OE02 DU1

7 .8

Using SET BOOT
Instead of typing the whole BOOT command every time you boot the system,
you can equate the command to a "nickname." Nicknames can be up to four
characters long. To give a BOOT command a nickname, use the SET BOOT
command in the following format:
>>> SET BOOT nickname [boot-parameters]

Note: To use any SET command, the lower keylock switch must be in the
UPDATE position.
For example, suppose you want to assign a nickname to the following BOOT
command:
BOOT/XMI:2/BI:2 DUO

Enter the following command and press RETURN:
>>>SET BOOT WORK /XMI:2/BI:2 DUO

The next time you need to boot from DUO, enter the following and press
RETURN:
>» BOOT WORK

To clear the value of the nickname, enter the following and press RETURN:
>>> SET BOOT nickname

For more information on the SET command, see the owner's manual for the
VAX 6200 series.

7 .9

If the System Does Not Boot
If the system does not boot because a hardware problem occurs, a question
mark (?) usually precedes the error message displayed on the console
terminal. Examples of hardware problems are a read error on a disk drive or
a console tape cartridge, or a machine check error. If you suspect a hardware
problem, do the following:

•

Consult the hardware manual for your VAX processor.

•

Contact the appropriate DIGITAL Field Service representative.

7~9

System Startup and Shutdown
7 .9 If the System Does Not Boot

When the operating system is loaded into memory, a message similar to the
following appears on the terminal screen:
SYSTEM

job terminated at 31-DEC-1988 15:00:00.00

If the system does not display this message, a software problem might have
occurred. If you suspect a software problem, do the following:

7.10

•

Try to boot the system again.

•

Place a backup copy of the system disk in another drive and try to boot
from it.

Shutting Down the System
Before you shut down the operating system, decide if you want it to reboot
automatically or if you want to enter console-mode commands after the
shutdown completes.
If you want the system to reboot automatically after the shutdown, you must

first designate a default boot device in EEROM as described in Section 7.5.1.

7 .10.1 Types of Shutdowns
You can perform the following three types of shutdown operations:

An orderly shutdown with SYS$SYSTEM:SHUTDOWN.COM. This
procedure shuts down the system while performing maintenance
functions such as disabling future logins, stopping the batch and printer
queues, dismounting volumes, and stopping user processes. To use the
SHUTDOWN command procedure, log into the SYSTEM account, enter
the following command and press RETURN:
$ ©SYS$SYSTEM:SHUTDOWN

To halt the system after the procedure completes, press CTRL/P.
For more information about the SHUTDOWN command procedure, see
the Guide to Setting Up a VMS System.

An emergency shutdown with OPCCRASH.EXE. If you cannot perform
an orderly shutdown with SHUTDOWN.COM, run the OPCCRASH
emergency shutdown program. Enter the following command and press
RETURN:
$ RUN SYS$SYSTEM:OPCCRASH

To halt the system after the procedure completes, press CTRL/P.
For more information about the OPCCRASH program, see the Guide to

Setting Up a VMS System.
3

7-10

An emergency shutdown with CRASH commands. Use the emergency
shutdown procedure described in Section 7.10.2 if OPCCRASH fails.

System Startup and Shutdown
7. 1 0 Shutting Down the System

7. 10. 2 Emergency Shutdown with CRASH Commands
Note: Use this emergency shutdown procedure when the system is hung and
you cannot log into SYSTEM to use SHUTDOWN or OPCCRASH.
To force your processor to fail, do the following:
1

Set the upper keylock switch to ENABLE.

Press CTRL/P to put the system in console mode.

Enter the following commands. The system displays a value in response
to each of the EXAMINE commands. For example:
»> E/I 0
I

00000000

7FFE7CEO

00000001

7FFE9D88

00000002

7FFED04E

00000003

0001FACB

00000004

80631200

»> E/I 1
>» E/I 2
»> E/I 3
»> E/I 4
I
»> E PSL
04030004
>>> D PSL 041FOOOO
>» D PC FFFFFFFF

Depositing these values in the program counter (PC) and the processor
status longword (PSL) causes an exception condition that sends the
contents of memory to a dump file on the system disk.
4

Enter the following command and press RETURN:
>>> c

The system displays a fatal bugcheck message and other messages similar
to the following:

****FATAL BUG CHECK, VERSION= 5.0 INVEXCEPTN, Exception while above ASTDEL or on interrupt stack
CRASH CPU: 02

PRIMARY CPU: 02

ACTIVE/AVAILABLE CUP MASKS: 00000016/00000016
CURRENT PROCESS = NULL
REGISTER DUMP
RO = 0000001F

**** MEMORY DUMP COMPLETE ....
>>>

If the system does not reboot automatically, reboot it.

After the system reboots, you can examine the dump file. Log into the
SYSTEM account.

Enter the following commands. Press RETURN after each one:
$ANALYZE/CRASH SYS$SYSTEM:SYSDUMP.DMP
SDA> SHOW CRASH

For more information about the System Dump Analyzer (SDA), see the

VMS System Dump Analyzer Utility Manual.
7-11

Backup Procedures

This chapter describes the following procedures:

8.1

•

Installing and booting standalone BACKUP on the system disk

•

Installing and booting standalone BACKUP on a tape cartridge

•

Backing up and restoring the system disk

Overview of Standalone BACKUP
The Backup Utility lets you create and restore backup copies of files,
directories, and user disks. Because the Backup Utility copies only what
is on the disk and ignores sections of any open files contained in memory,
you should use it to back up user disks, not the system disk. If you use the
Backup Utility to back up the system disk, the portions of the files that were
in memory and data about files not yet written back to the disk (cache) will
not be recorded on the resulting backup copy.
Use standalone BACKUP to make a complete backup of the system disk.
Standalone BACKUP is a version of the Backup Utility that runs without
the support of the entire VMS operating system. Before you use standalone
BACKUP, you must shut down the VMS operating system. The shutdown
procedure sends the contents of the caches back to the disk and closes any
open files. By shutting the system down and using standalone BACKUP, you
can make an exact copy of the system disk.
You can keep standalone BACKUP on the system disk, a tape cartridge,
or any other media that the system supports. DIGITAL recommends that
you keep standalone BACKUP on your system disk and on a tape cartridge.
Usually you boot standalone BACKUP from the system disk because it
saves time. However, you need to keep a copy of standalone BACKUP on
a tape cartridge in case the system disk becomes damaged. As part of your
distribution kit, you received standalone BACKUP on tape cartridge.

8.1.1

Installing Standalone BACKUP on the System Disk
You can install standalone BACKUP in any available root directory on the
system disk from [SYS 1] to [SYSE]. However, DIGITAL has established [SYSE]
as the standard directory for standalone BACKUP.
To install standalone BACKUP in [SYSE] on the system disk, use the following
procedure:
1

Log into the SYSTEM account.

8-1

Backup Procedures
8.1 Overview of Standalone BACKUP

The procedure places the files in the directories [SYSE.SYSEXE] and
[SYSE.SYS$LDR] on the system disk. It lists the files as they are copied.
When the procedure finishes, it displays the following message:
The kit is complete.

8.1.2

To boot standalone BACKUP from the system disk, go to Section 8.1.2.

Booting Standalone BACKUP from the System Disk
To boot standalone BACKUP from the system disk, use the following
procedure:
1

Make sure the console tape cartridge is in the console drive.

If the VMS operating system is not running, go to step 3.
If the VMS operating system is running, log into the SYSTEM account.

Answer the questions. When the procedure asks if an automatic system
boot should be performed, press RETURN for NO. When the procedure
is finished, it displays the following message:
SYSTEM SHUTDOWN COMPLETE -- USE CONSOLE TO HALT SYSTEM

Press CTRL/P to halt the system.

Enter the BOOT command in the following format:
>>> B /R5:EOOOOOOO /XMI:a /BI:b [/NODE=c] DUu

where:

•

a is the XMI node number of the system disk

•

b is the VAXBI node number of the system disk

•

c is the HSC node number of the node being accessed. You do not
need to specify the /NODE qualifier if you are booting from a local
disk.

•

u is the unit number

Standalone BACKUP displays the following message:
VAX/VMS Version V5.0 Major version id = 01 Minor version id = 00

The procedure displays a list of the local devices on your system and, if
you have them, HSC- and MSCP-served devices. For example:
Available device
Available device

8-2

MINE$DUAO:
MINE$DJA3:

device type RA81
device type RA60

Backup Procedures
8.1 Overview of Standalone BACKUP

Check the list of devices. If the list is incomplete, make sure that all the
drives are properly connected to the system. See your hardware manuals
for details.

When standalone BACKUP finishes booting, it displays an identification
message followed by the dollar-sign ( $ ) prompt:

%BACKUP-I-IDENT, Standalone BACKUP V5.0; the date is 31-DEC-1988 12:04:43.11
$

To make a backup copy of the system disk, go to Section 8.3.
To restore the system disk, go to Section 8.4.

8.2

Installing Standalone BACKUP on a Tape Cartridge
DIGITAL recommends that you keep standalone BACKUP on a tape cartridge
in case the system disk becomes damaged. To install standalone BACKUP on
a tape cartridge, use the following procedure:

Note: You should have standalone BACKUP on the tape cartridge that came
with your distribution kit. Use the procedure in this section if your copy
of standalone BACKUP becomes damaged, or if you need to make extra
copies.
1

Obtain one blank tape cartridge. Write the name S/ A BKUP VS.O on the
paper label. Insert the label in the label slot.

Make sure the tape cartridge is write-enabled.

Insert the tape cartridge drive in the drive.

Log into the SYSTEM account.

The procedure asks you for the name of the target device. Type the
device name of the tape cartridge drive and press RETURN. For example:
Enter the name of the device on which to build the kit: MUC6

After you enter the name of the target device, the procedure displays
several informational messages and the following message:
Please place the scratch tape cartridge in drive _MUC6:
This volume will receive the volume label SYSTEM.
Enter "YES" when ready:

When you are ready to continue, type Y (for YES) and press RETURN.

The system displays verification messages informing you that files are
being copied. When standalone BACKUP is installed, the procedure
displays a message similar to the following:
Ending time
31-DEC-1988 16:44:29.90
Starting time 31-DEC-1988 16:30:39.05
The Kit is complete.
$

8-3

Backup Procedures
8.2 Installing Standalone BACKUP on a Tape Cartridge

Remove the tape cartridge labeled S/ A BKUP VS.O from the tape cartridge
drive.

10 Write-protect the tape cartridge and store it in a safe place.

8.2.1

Booting Standalone BACKUP from a Tape Cartridge
If the system disk containing standalone BACKUP should become unusable,
you can boot standalone BACKUP from a tape cartridge. Booting standalone
BACKUP from a tape cartridge takes approximately 15 minutes. You need a
tape cartridge that contains standalone BACKUP (either the distribution tape
cartridge or one that you created). To boot standalone BACKUP from a tape
cartridge, use the following procedure:
1

If the VMS operating system is not running, go to step 2.
If the VMS operating system is running, log into the SYSTEM account.
Enter the following command and press RETURN:
$ ©SYS$SYSTEM:SHUTDOWN

Press CTRL/P to halt the system.

Make sure the console tape cartridge is in the console drive.

Enter the following command and press RETURN:
>» B CSA1

The procedure displays a self-test message similar to the following:
F

E
M

D
A
0

B
A

9
M

p
+

A2
32
ROM = 1.0

NODE #
TYP
STF
BPD
ETF
BPD
XBI D +

A1
32

ILV
64 Mb

EEPROM = 1.0/1.0 SN = NI0128

Loading system software.
Please remove the volume "CONSOL" from the console device.
Insert the first standalone system volume and enter "YES" when ready:

Remove the console tape cartridge. Insert the tape cartridge that contains
standalone BACKUP. When you are ready to continue, type Y and press
RETURN.
Standalone BACKUP displays a message similar to the following:
Resuming load operation on volume 'SYSTEM'. please stand by ...
VAX/VMS Version V5.0 Major version id = 01 Minor version id = 00
%SMP-I-CPUBOOTED, CPU #4 has joined the PRIMARY CPU in multiprocessor operation

8-4

Backup Procedures
8.2 Installing Standalone BACKUP on a Tape Cartridge

The procedure displays a list of the local devices on your system and, if
you have them, HSC- and MSCP-served devices. For example:
Available device
Available device

MINE$DUAO:
MINE$DJA3:

device type RA81
device type RA60

Check the list of devices. If the list is incomplete, make sure that all the
drives are properly connected to the system. See your hardware manuals
for details.

When standalone BACKUP finishes booting, it displays an identification
message followed by the dollar sign ( $ ):
%BACKUP-I-IDENT, standalone BACKUP V5.0; the date is 31-DEC-1988 15:00
$

10 Remove the tape cartridge containing standalone BACKUP from the tape
cartridge drive.
To back up the system disk, go to Section 8.3.
To restore the system disk, go to Section 8.4.

8.3

Backing Up the System Disk
You should back up the system disk for the following reasons:
•

In case a problem occurs during a VMS upgrade or update, or during the
installation of other software products. Before you attempt any of these
procedures, you should back up the system disk. If a problem occurs, you
can restore the backup copy of the system disk.

•

To prevent loss of system files if they are accidentally deleted. After
you install or upgrade the VMS operating system, or any other software
products, you should back up the system disk. If a system file is deleted
and renders the system disk inoperable, you can restore the backup copy
and continue to use the system.

•

In case the drive that holds the system disk malfunctions. If you have
a backup copy of the VMS operating system, you can restore it to a
functioning disk and continue to use the system.

•

To eliminate disk fragmentation. Fragmentation happens when files are
stored noncontiguously on the disk. The BACKUP command creates a
copy on which files are stored contiguously.
If the system disk is removable, eliminating disk fragmentation is a

one-step process. Use the backup copy as the new system disk. Store
the old system disk in a safe place.
If your system disk is fixed, back it up to a disk or magnetic tape.

Then restore the files to the original system disk.

8-5

Backup Procedures
8.3 Backing Up the System Disk

DIGITAL recommends that you use standalone BACKUP, which uses a subset
of Backup Utility qualifiers, to back up and restore your system disk. It is
especially important that you understand the functions of the /IMAGE and
/PHYSICAL qualifiers to the BACKUP command before using standalone
BACKUP.
Qualifier

Function

/IMAGE

Lets you create a functionally equivalent copy of the entire
system disk.

/PHYSICAL

Copies, saves, restores, or compares the entire system disk
in terms of logical blocks, ignoring any file structure.

For a complete description of the Backup Utility and its qualifiers, see the

VMS Backup Utility Manual.
To back up the system disk, use the following procedure:
1

Obtain a scratch disk or tape cartridge that you can use for the backup
copy. Place it in the appropriate drive. If you are using a tape cartridge,
write-enable it (to write-enable a tape cartridge, slide the write-protect
switch away from the tape cartridge label). If you are using a disk, .spin
up the drive.

Write-protect the system disk by pressing the WRITE PROTECT button
on the disk drive.

Boot standalone BACKUP as described in Section 8.1.2 or Section 8.2.1.

Determine the device names of the drive holding the system disk and the
drive holding the backup disk or tape cartridge. For a list of device codes,
see Table 3-1.

Enter the BACKUP command in one of the following formats. If you are
backing up the system disk to another disk, use the first command. If
you are backing up the system disk to a tape cartridge, use the second
command.

$BACKUP/IMAGE/VERIFY source-drive: target-drive:
$ BACKUP/IMAGE/VERIFY/BUFFER=5 source-drive: target-drive:saveset.BCK/REWIND/LABEL=volume-label

where:

•

source-drive is the location of the files you want to back up. Use the
device name of the drive holding the system disk.

•

target-drive is the destination. Use the device name of the drive
holding the backup disk or tape cartridge.

•

saveset.BCK is the name of the saveset (the name should reflect the
contents of the tape and cannot exceed 17 characters in length).

•

volume-label is the volume label of the tape cartridge in the targetdrive. If the tape cartridge has already been initialized, use the same
volume label that was assigned by the INITIALIZE command. If the
tape cartridge has not been initialized, you can assign a volume label
at this time. The volume label can have up to six characters.

8-6

Backup Procedures
8.3 Backing Up the System Disk

The following example uses the BACKUP command to make a backup
disk. You can use a backup disk as the system disk.
$ BACKUP/IMAGE/VERIFY DUAO: DUA1:

The following example uses the BACKUP command to make a backup
tape cartridge. The contents of a backup tape cartridge have to be
restored to a disk before you can use them.
$ BACKUP/IMAGE/VERIFY/BUFFER=5 DUB3: MUC6:DEC_31_BACK.BCK/REWIND/LABEL=SYSDSK

Standalone BACKUP displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

If you are backing up the system disk to another disk, go to step 8.
If you are backing up the system disk to tape cartridges and the system
disk contains more data than one tape cartridge can store, the procedure
displays the following messages:
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYWRITE, Mount volume 2 on MUC6: for writing
Enter "YES" when ready.

If the system does not display these messages, go to step 8.
If the system displays these messages, follow steps a through e.

a. Remove the backup tape cartridge from the drive.
b. Label it COMPLETE SYSTEM BACKUP, number it, at;ld include the
date.

c. Write-protect the tape cartridge.
d. Write-enable another scratch tape cartridge and insert it into the
drive.

e. Type Y and press RETURN.
f.

Standalone BACKUP displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

Each time the procedure displays a mount request, follow steps a through
e.

When the procedure is finished, it displays the following message:
%BACKUP-I-PROCDONE, Operation completed.

Processing finished at 31-DEC-1988 15:45.

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 online and ready.
Enter "YES" to continue:

Remove the backup tape cartridge from the drive. Label it COMPLETE
SYSTEM BACKUP, and include the number of the tape cartridge in the
backup sequence (if you used more than one tape). Also include the date
on the label of the tape cartridge.

1 0 Press CTRL/P to halt the system.
11 Reboot the system.
Store the backup copy of the system disk in a safe place.

8-7

Backup Procedures
8.3 Backing Up the System Disk

Note: The BACKUP command creates a system disk that includes a
DIGIT AL-provided set of volume parameters, including a CLUSTER_
SIZE (disk access scheme) of one. (The CLUSTER_SIZE refers to
the way files are stored on the disk, NOT to VAXclusters.) You
can change most volume parameters later with the SET VOLUME
command. However, to change the CLUSTER_SIZE you must back up
the system disk to a disk that has been previously initialized with the
CLUSTER_SIZE that you want. To prevent the BACKUP command
from reinitializing the target disk, use the /NOINITIALIZE qualifier.
For more information about initializing a disk, see the Guide to
Maintaining a VMS System. For more information on the BACKUP
command, see the VMS Backup Utility Manual.

8.4

Restoring the System Disk
To restore the system disk, use the following procedure:
1

Write-protect the backup disk or tape cartridge

Insert the backup disk or tape cartridge in the appropriate drive. If you
are using a tape cartridge drive, put it on line. If you are using a disk
drive, spin it up.

Boot standalone BACKUP as described in Section 8.1.2 or Section 8.2.1.

Place a scratch disk in the drive you intend to use for the new system
disk. Spin it up but do not write-protect it.

Determine the device names of the drive holding the system disk and the
drive holding the backup disk or tape cartridge. For a list of device codes,
see Table 3-1.

Enter the BACKUP command in one of the following formats. Use the
first command if you have a backup disk. Use the second command if
you have a backup tape cartridge.
$BACKUP/IMAGE/VERIFY source-drive: target-drive:
$ BACKUP/IMAGE/VERIFY/BUFFER=5 source-drive:saveset.BCK/REWIND target-drive:

where:

•

source-drive is the location of the files you want to restore. Use the
device name of the drive holding the backup disk or tape cartridge.

•

saveset is the name of the saveset (if you have a backup tape
cartridge).

•

target-drive is the destination. Use the device name of the drive
holding the system disk.

The following example uses the BACKUP command to restore the system
disk from a backup tape cartridge:
$ BACKUP/IMAGE/VERIFY/BUFFER=5 MUC6:DEC_31_BACK.BCK/REWIND DUB3:

Standalone BACKUP displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

8-8

Backup Procedures
8.4 Restoring the System Disk

If the backup copy of the system disk is another disk or one tape cartridge,

go to step 9.

If the backup copy of the system disk consists of several tape cartridges,

the procedure displays the following message:
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYREAD, Mount volume 2 on MUA1: for reading
Enter "YES" when ready.

a. Remove the backup tape cartridge from the drive.

b. Insert the next backup tape cartridge in the drive.

c. When you are ready to continue, type Y (for YES) and press
RETURN.
d. The procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

Each time the procedure displays a mount request, follow steps a through
c.

When the procedure finishes, it displays the following message:
%BACKUP-I-PRDCDONE, Operation completed.

Processing finished at 31-DEC-1988 15:50.

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 online and ready.
Enter "YES" to continue:

10 Press CTRL/P to halt the system.
11 Reboot the system.
Store the backup copy in a safe place.

8-9

How the System Assigns Controller Letters

The system assigns a letter to each controller on the VAXBI in order, starting
with the controller that has the lowest VAXBI node number. If the system
has more than one VAXBI, the system begins assigning controller letters on
the VAXBI with the lowest XMI node number.
The system assigns a unique controller letter to each controller type starting
with the letter A. For example, if a system has three KDB50s (controller type
DU), then the first KDB50 disk controller would be assigned the letter A,
the second B, and the third C. If the same system has three KLESI-Bs, then
because the KLESI-B is a different controller type (MU), the first KLESI-B tape
controller would be assigned the letter A, the second B, and so forth.
An exception to this rule occurs with the TBK50 controller. The TBK50 is a BI
VAXport which architecturally can be both a disk and tape controller. When
the system finds a TBK50, it must assign the same disk and tape controller
letter to this device. If necessary, the system skips unassigned disk or tape
controller letters to make sure that the TBK50 uses the same letter for the disk
and tape designation.
This exception applies only to controller letter assignment for disk (DU) and
tape (MU) devices. Devices such as the DEBNA (ET) are neither disk nor tape
controllers and are unaffected by the presence of a TBK50.
Also, HSC disk or tape drives that are attached to the CI always have the
controller letter A. These devices are already uniquely identified by the HSC's
allocation class and do not require unique controller letters.
The following example shows how the system assigns controller letters:
>>> SHOW CONFIGURATION

Code
(2001)

Rev
0001

(8001)
(4001)

0001
0001

XBI 2
1- DWMBA/B
(0107)
5+ KDB500
(010E)
6+ KLESI-B@ (0103)
7+ DEBNA9
(410F)
8+ CIBCA0
(0108)
9+ TBK500
(410E)

FFFO
OF!C
0006
023B
0002
0001

XBI 3
1- DWMBA/B
(0107)
3+ KLESI-B0 (010E)
4+ TBK500
(410E)
8+ KDB500
(010E)

FFFO
OF!C
0001
OF!C

2+
3+
4E+

Type
DWMBA/A
DWMBA/A
KA62A
MS62A

A-1

How the System Assigns Controller Letters

Since there are two VAXBis (XMI nodes 2 and 3), the system begins
assigning controller letters on the VAXBI that has the lowest XMI node
number (in this case, XMI node 2). The system starts assigning controller
letters with the device that has the lowest VAXBI node number (excluding
the DWMBA). In this case, the device with the lowest XMI node number
is the KDBSO. The KDBSO is designated DUA.

The next device, the KLESI-B, is designated MUA.

The DEBNA is designated ETA.

G The CIBCA is designated PAA. HSC disk or tape drives that are attached
to this controller have the controller letter A.

The next device is a TBKSO, which can be a disk and tape controller.
Because the controller letter A has been used, the next available controller
letter is B. The TBKSO is designated MUB. The system also reserves DUB
for the TBKSO.

The next device (KLESI-B) is designated MUC. The KLESI-B cannot use
the letter B, because there is already a controller named MUB.

The next device is a TBKSO, which can be a disk and tape controller.
Because the controller letter C has been used, the next available controller
letter is D. The TBKSO is designated MUD. The system also reserves DUD
for the TBKSO. DUC was skipped so the TBKSO could use the letter D for
both the DU and MU devices.

G The last device (KDBSO) is designated DUE. The KDBSO cannot use the
letter D, because the TBKSO reserved it.
Table A-1 summarizes how the system assigned the controller letters in this
example.
Table A-1

Controller Naming Example

Device

KDB50

KLESl-B

CIBCA
TBK50

KLESl-B

TBK50

1 DUB is reserved.
2DUD is reserved; DUC skipped.

A-2

DEBNA

KDB50

Glossary

boot or bootstrap: The process of loading system software into a VAX computer's
main memory. This guide uses the term boot to refer to this process.
boot name: A name that helps identify the location of the system disk and the
instructions used to boot the system.
boot server: AVAX computer that is part of a local area VAXcluster. The boot server
in a local area VAXcluster has a system disk that contains cluster common files;
other nodes in the cluster (satellite nodes) can access these files. See also satellite

node.
Cl-only VAXcluster: A computer system consisting of a number of VAX computers. It
uses only the computer interconnect (CI) to communicate with other VAX computers
in the cluster.
Cl BCA: An interface between the VAXBI of the VAX 6200 series and the computer
interconnect (Cl).
computer interconnect: A type of 1/0 subsystem that links VAX processors to each
other and to HSC devices.
console mode: In console mode, the system is halted and the VMS operating system
is not running. You control the system using the console subsystem. Console mode
is indicated by the console-mode prompt(> > > ) on the console terminal. See
also program mode.
console tape cartridge: The tape cartridge that contains the console program. It is
not shipped as part of the VMS distribution kit. The console tape cartridge is used
in the console tape cartridge drive.
device name:. The name you use to identify a device on the system. A device name
indicates the device code, controller designation, and unit number.
Hierarchical Storage Controller (HSC) device: A self-contained, intelligent, mass
storage subsystem that lets processors in a VAXcluster environment share disks.
Examples of HSC devices are the HSCSO and the HSC70.
HSC drive: Any drive that is connected to an HSC device is referred to as an HSC
drive. A system disk on an HSC drive can be shared by several computers in a
VAXcluster environment.
local area VAXcluster: Consists of a VAX computer that acts as a boot node and a
number of low-end VAX computers that act as satellite nodes. Ethernet connects all
of the computers. These computers share a single file system. See also boot node
and satellite node.
local drive: Any drive that is connected directly to a computer is referred to as a local
drive.

Glossary-1

Glossary

Mass Storage Control Protocol (MSCP): The protocol used to communicate
between a VAX processor and a controller. An MSCP server makes local KDBSO
disks accessible to all the nodes in a VAXcluster environment.
media: A generic term that refers to any packaging agent capable of storing computer
software. Examples of media are magnetic tapes, compact disks, floppy diskettes,
disk packs, tape cartridges, etc.
mixed-interconnect VAXcluster: A computer system consisting of a number of
VAX computers. It uses both the computer interconnect (CI) and the Ethernet to
communicate with other VAX computers in the cluster.
program mode: In program mode, the system is controlled by the VMS operating
system. In program mode, you can enter DCL commands, run programs, and
receive system messages. See also console 11!-ode.
save set: The format that the Backup Utility stores files in. The VMS operating system
is shipped in this format.
scratch media: Media that are blank or have files that you no longer need. For
example, a scratch tape cartridge.
spin up/spin down: To spin up means to bring a disk drive up to operating speed. To
spin down means to bring it to a gradual stop.
standalone BACKUP: A version of the BACKUP utility that runs from memory
without the control of the VMS operating system.
standalone system: A computer system with only one VAX computer.
system disk: The disk that contains (or will contain) the VMS operating system. A
VMS system disk is set up so that most of the VMS files can be shared by several
processors. In addition, each processor has its own directory on the system disk that
contains its page, swap, and dump files.
KDB50: An intelligent disk drive controller that supports up to four disk drives on the
VAXBI.
UNIBUS: A medium-speed IJO subsystem. Some of the devices that can be connected
to the UNIBUS are UDASO's, RL02 disk drives, and TU81 magnetic tape drives.
VAXcluster environment: A computer system consisting of a number of highly
integrated VAX computers. There are three types of VAXcluster environments:
CI-only, local area, and mixed interconnect.
VMS User Environment Test Package (UETP): A software package that tests
all the standard peripheral devices on your system, various commands and
operating system functions, the system's multi-user capability, DECnet-VAX, and
the VAXcluster environment.
VMSTAILOR: A software program that lets you customize your system disk.

Glossary-2

Index

A
ALLOCLASS parameter• 3-5
ANALYZE/CRASH command• 7-11
A UT OGEN
function during installation • 4-13
Automatic restart
types of• 7-7

B
BACKUP
See Backup Utility
BACKUP command• 8-5
/IMAGE qualifier• 8-6
/PHYSICAL qualifier• 8-6
Backup Utility (BACKUP)• 8-1
/Bl qualifier• 7-2, 7-3
BOOT command
qualifiers for HSC disks• 7-3
qualifiers for local disks• 7-2
Boot name
definition • 3-3
device code • 3-3
syntax• 3-3
unit number• 3-3
Boot primitive
definition•3-3, 7-1
function • 7-1
Bugcheck message
during UETP • 6-27

c
Cartridge-release handle
on the tape cartridge drive• 2-5
Cluster group number
rules for creating• 3-5
Cluster password
rules for creating • 3-5
CLUSTER_SIZE attribute• 8-8

Cold start
definition• 7-7
Console mode• 2-12
Console report during UETP • 6-28
choosing format of• 6-12
error messages• 6-12, 6-14
Console subsystem
components• 2-1
console mode• 2-12
processor control panel• 2-1
program mode• 2-12
Console terminal
description• 2-1
CONTINUE command• 7-5
Controller designation
definition• 3-2
Conversational boot
from a local system disk• 7-5
from an HSC system disk• 7-5
CRASH commands• 7-11
CTRLNAME. 6-7 6-29
I

D
DECnet node address• 3-5
DECnet node name• 3-5
DECnet-VAX
registering the license• 5-1
DECnet-VAX
error message during UETP • 6-25
preparing for UETP • 6-10
UETP test of• 6-33
UETP test phase• 6-32
Device code
definition• 3-2
Device name
controller designation• 3-2
device code• 3-2
syntax• 3-2
unit number• 3-2
Device test
running individually• 6-29
Diagnostics
relationship to UETP • 6-14

lndex-1

Index

Disk
See System disk, User disk
Distribution kit
tape cartridge• 4-1
Distribution media
definition• 3-1
DR11-W
preparing for UETP • 6-6
DR11-WA
preparing for UETP • 6-7
DR750
preparing for UETP • 6-7
DR780
preparingforUETP•6-7

E
Error during UETP
diagnosing• 6-14
sources of• 6-15
Error Log Utility
relationship to UETP • 6-2, 6-14, 6-26
Ethernet
defining a remote node for UETP • 6-16
preparing for UETP • 6-6

H
Hang
See System hang
Hardware problem
diagnosing• 7-9
HSC drive
booting from • 3-4
definition • 3-1

K
Keylock switch• 2-2, 2-3

L
License registration
for system integrated products• 5-1
for VMS•5-1
Line printer
preparingforUETP•6-2,6-4,6-6
UETP output• 6-30
UETP test image• 6-31
UETP test of• 6-28
LOADS•6-31
Load test
defining user load for UETP • 6-12
description • 6-1 2, 6-3 1
error during UETP • 6-24
running individually• 6-11
LOAD /UNLOAD button
on the tape cartridge drive• 2-5
Local drive
booting from• 3-3
definition• 3-1
Log file generated by UETP
See also UETP.LOG
during the load test• 6-24
NETSERVER.LOG • 6-23
OLDUETP.LOG • 6-17
Logical name used by UETP
CTRLNAME. 6-7 6-29
LOADS•6-31
MODE•6-15
SYS$1NPUT • 6-28
SYS$0UTPUT•6-30
SYS$TEST. 6-3, 6-9 6-1 7
UETP$NODE_ADDRESS•6-10
Long report format
See Console report during UETP
LPA 11-K
preparingforUETP•6-8
I

I
/IMAGE qualifier• 8-6
Indicator lights
on processor control panel• 2-3
Installation procedure
stages of• 4-1
Installation procedure
definition• 1-1

lndex-2

Index

M
MA780
preparing for UETP • 6-7
Magnetic tape
preparing for UETP • 6-2, 6-3, 6-5
test of• 6-28, 6-30
UETPte~image•6-31

Mandatory update
definition• 1-2
Master command procedure
See UETP.COM
MODE•6-15, 6-36
Multiprocessing system
setting SYSGEN parameters• 7-2

N
Nickname
for BOOT command• 7-9
/NODE qualifier• 7-3
No PCB or swap slots error message• 6-26

0
OPCCRASH.EXE • 7-10
Output during UETP
See also UETP.LOG
console report• 6-12, 6-28
interpreting• 6-15
terminal and line printer• 6-30

p
Phase controller for UETP
See UETPHASOO.EXE
/PHYSICAL qualifier• 8-6
Privilege
required for UETP • 6-20
Processor control panel
components• 2-1
indicator lights• 2-3
keylock switches• 2-2, 2-3
Program mode• 2-12

a
Quota
required for UETP • 6-20

R
/R3 qualifier• 7-2, 7-3
/R5 qualifier• 7-2, 7-3
RMS Journaling
registering the license• 5-1

s
Saveset.BCK
definition• 8-6
SDA
See System Dump Analyzer
Self-test display
description• 2-14
SET BOOT command
using to designate default disk• 7-7
using to specify a nickname• 7-9
Short report format
See Console report during UETP
SHOW CONFIGURATION command• 2-12
SHOW CRASH command• 7-11
SHUTDOWN.COM•7-10
Source-drive
definition• 4-5, 4-7, 8-6
STABACKIT.COM•8-1, 8-3
Standalone BACKUP
definition• 8-1
function during installation• 4-3
relation to Backup Utility• 8-1
SYS$1NPUT • 6-28
SYS$0UTPUT•6-30
SYS$TEST•6-3,6-9, 6-17
SYSBOOT.EXE•7-1, 7-4
commands• 7-5
SYSGEN
See System Generation Utility
System
logging into for UETP • 6-1, 6-3
resource requirements for UETP • 6-1 , 6-3

lndex-3

Index

System disk
booting from a local drive• 3-3
booting from an HSC drive• 3-4
checking amount .of free space on• 5-3
definition• 3-1
designating as default boot device• 7-7
reasons for backing up• 8-5
space requirements for UETP • 6-4
test error during UETP • 6-21, 6-22
UETP test image• 6-31
UETP test of• 6-30
using VMST AILOR to customize• 5-2
System Dump Analyzer (SDA) • 7-11
System Generation Utility (SYSGEN)
ALLOCLASS parameter• 3-5
commands for conversational boot• 7-5
setting multiprocessing parameters• 7-2
System hang• 6-18, 6-27
SYSTEST account
logging into for UETP • 6-1 , 6-3
privileges required for UETP • 6-20
quotas required for UETP • 6-20
SYSTEST directory
creating for UETP • 6-5
function during UETP • 6-3
SYSTEST_CLIG account
reenabling for UETP • 6-8
requirements for UETP • 6-8, 6-35

T
Tailored system disk
See VMST AILOR
Tape cartridge
description• 2-7
dismounting• 2-11
initializing• 2-9
inserting• 2-8
label slot• 2-7
mounting• 2-10
removing• 2-11
write-protecting• 2-7
write-protect switch• 2-7
Tape cartridge distribution kit
contents of• 4-1
Tape cartridge drive• 2-4
indicator light• 2-4
LOAD/UNLOAD button• 2-5
preparingforUETP•6-5

lndex-4

Tape cartridge drive (cont'd.)
summary of controls• 2-6
summary of indicator lights• 2-6
Target-drive
definition• 4-5, 4-7, 8-6
Terminal
preparing for UETP•6-2, 6-4, 6-6, 6-11
simulating users for UETP • 6-31
test· of• 6-28
UETP output• 6-30
UETPte~image•6-31

UETP test of• 6-30
TK50 drive
See tape cartridge drive
TK50tape
See tape cartridge
TK50 tape cartridge
See tape cartridge

u
UETCONTOO.DAT • 6-28
UETDISKOO
error message• 6-22
UETDNETOO.DAT • 6-33
UETINIDEV.DAT• 6-28, 6-29
format•6-29, 6-30
UETININET.DAT • 6-33
UETINITOO.EXE • 6-16, 6-28
UETINIT01
error message• 6-2 1
UETINIT01.EXE•6-18, 6-28
failure• 6-2 1
UETLOADOO.DAT • 6-31
UETNETSOO.EXE • 6-33
UETP
See User Environment Test Package
UETP$NODE_ADDRESS•6-10
UETP.COM • 6-27
termination of• 6-13
UETP.LOG•6-12, 6-17, 6-26, 6-32
UETPHASOO.EXE. 6-27 6-28, 6-33
UETUNASOO.EXE • 6-16
UIC
See User Identification Code
Unit number
definition• 3-2
Update procedure
See also Mandatory update
I

Index

Update procedure (cont'd.)
definition• 1-2
restrictions• 1-2
Upgrade procedure
definition• 1-1
restrictions• 1-2
User disk
preparingforUETP•6-1, 6-4, 6-5
space requirements for UETP • 6-4
test error during UETP • 6-21

VMSTAILOR
adding files to a system disk• 5-2
removing files from a system disk• 5-2
Volume-label
definition• 4-3, 8-6
used with BACKUP command• 8-6
Volume Shadowing
BOOT command qualifier used.for• 7-3
qualifier used for• 7-2
registering the license• 5-1

UETPte~image•6-31

UETP test of• 6-30
User Environment Test Package (UETP)
aborting execution of• 6-13
description of• 6-1
displaying tests as they run• 6-15
initialization phase• 6-28
interpreting output of• 6-15
master command procedure• 6-27
normal completion of• 6-12
organization of• 6-27
required privileges• 6-20
required quotas• 6-:-20
requirements for small disk systems• 6-9
running all phases of• 6-2
running individual phase of• 6-11
running multiple passes of• 6-11, 6-1 7
starting• 6-10
typical failures reported by• 6-18
when to run • 5-3
User Identification Code (UIC)
for UETP • 6-5
User load
defined for UETP DECnet test• 6-33
defining for the UETP load test• 6-12
equation used to determine for UETP load test•
6-16

w
Warm start
definition• 7-7
Wrong account error message• 6-20
Wrong privileges error message• 6-19
Wrong quotas error message• 6-19

x
/XMI qualifier• 7-2, 7-3

v
V AXcluster environment
how to prepare• 5-2
preparing for UETP • 6-9
registering the VMS license• 5-1
test failure during UETP • 6-23
VAXVMSSYS.PAR • 7-1
VMB.EXE•7-1
VMSKITBLD • 7-8
VMS license• 5-1

lndex-5

Reader's Comments

VMS Installation and Operations:
VAX 6200 Series
AA-LB36A-TE

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

I rate this manual's:
Accuracy (software works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

I would like to see more /less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

Name/Title

Dept.
Date

Company
Mailing Address
Phone

I
I
I
I
I

Do Not Tear - Fold Here and Tape

-------------------"lllr-------;~;;~---'
11

tf Mailed
in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POST AGE WILL BE PAID BY ADDRESSEE

DIGIT AL EQUIPMENT CORPORATION
Corporate User Publications-Spit Brook
ZK01-3/J35
110 SPIT BROOK ROAD
NASHUA, NH 03062-9987

111 ..... 11.11 .... 11 .... 1.11.1 .. 1.1 .. 1.. 1.1 ... 1.11 .. 1
-

Do Not Tear - Fold Here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -