Digital PDFs

AA-LB34A-TE

April 2000

162 pages

Original

6.0MB

Document:	VMS Installation and Operations: VAXstation 2000, MicroVAX 2000
Order Number:	AA-LB34A-TE
Revision:	0
Pages:	162
Original Filename:

OCR Text

VMS Installation and Operations:
VAXstation 2000, MicroVAX 2000
Order Number: AA-LB34A-TE

April 1988
This guide describes the VMS installation procedure for the V AXstation
2000 and the MicroVAX 2000. 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 Cl 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
DECUS
DECwriter

DIBOL
EduSystem
IAS
MASSBUS
PDP
PDT
RSTS
RSX

UNIBUS
VAX
VAXcluster
VMS
VT

~urnuo~u TM
ZK4452

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 l..td.
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 (SDC), Digital Equipment
Corporation, Westminster, Massachusetts 01473.

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-quality
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

CHAPTER 2 VAXSTATION 2000/MICROVAX 2000 HARDWARE

2-1

2.1

THE ON/OFF SWITCH

2-1

2.2

THE HALT BUTTON

2-2

2.3
2.3.1
2.3.2
2.3.3
2.3.4

THE CONSOLE TERMINAL AND SERIAL LINES
Turning On the Console Terminal
Diagnostic Console Terminal
The VAXstation 2000 Serial Lines
The MicroVAX 2000 Serial Lines

2-3
2-4
2-5
2-7
2-7

2.4

THE OPTIONAL EXPANSION BOX

2-8

Contents

2.5
2.5.1
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6

THE TK50 TAPE CARTRIDGE DRIVE
Tape Cartridges
Inserting a Tape Cartridge in a TK50 Drive
Initializing a Tape Cartridge
Mounting a Tape Cartridge
Dismounting a Tape Cartridge
Removing a Tape Cartridge from a TK50 Drive

2-9
2-11
2-13
2-15
2-15
2-16
2-16

2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.6.6

THE DISKETTE DRIVE
RX33 Diskettes
Inserting an RX33 Diskette
Initializing and Formatting an RX33 Diskette
Mounting an RX33 Diskette
Dismounting an RX33 Diskette
Removing an RX33 Diskette

2-16
2-17
2-18
2-22
2-22
2-23
2-23

2.7

THE FIXED DISK DRIVE

2-23

CHAPTER 3 BEFORE INSTALLING VMS

3-1

3.1

THE DISTRIBUTION MEDIA AND SYSTEM DISK

3-1

3.2

DEVICE NAMES

3-1

3.3

INFORMATION ON VAXCLUSTER ENVIRONMENTS

3-2

CHAPTER 4 INSTALLING VMS FROM A TAPE CARTRIDGE

4-1

4.1

BEFORE YOU START

4-1

4.2

TURNING ON THE SYSTEM

4-2

4.3

PREPARING THE SYSTEM DISK

4-3

Contents

4.4

BOOTING STANDALONE BACKUP

4-3

4.5

CREATING A SYSTEM DISK

4-4

4.6

INSTALLING THE MANDATORY UPDATE AND RUNNING
AUTOGEN

4-9

CHAPTER 5 INSTALLING THE VMS OPERATING SYSTEM FROM
DISKETTES

5-1

5.1

BEFORE YOU START

5-1

5.2

TURNING ON THE SYSTEM

5-2

5.3

PREPARING THE SYSTEM DISK

5-3

5.4

BOOTING STANDALONE BACKUP

5-3

5.5

CREATING A SYSTEM DISK

5-4

5.6

INSTALLING THE MANDATORY UPDATE AND RUNNING
AUTOGEN

5-10

CHAPTER 6 AFTER INSTALLING VMS

6-1

6.1

REGISTERING YOUR LICENSES

6-1

6.2

REMOVING UNWANTED FILES WITH VMSTAILOR

6-2

6.3

CUSTOMIZING THE SYST~M

6-2

6.4

TESTING THE SYSTEM

6-3

vii

Contents

6.5

DECOMPRESSING THE SYSTEM LIBRARIES

6-3

6.6

BACKING UP THE SYSTEM DISK

6-3

CHAPTER 7 RUNNING UETP
7.1

SUMMARY OF UETP OPERATING INSTRUCTIONS

7-1

7.2
7.2.1

LOGGING IN
SYSTEST Directories

7-3
7-3

7.3
7.3.1
7.3.2
7.3.3
7.3.4
7.3.5
7.3.6
7.3.7
7.3.8

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 Ether11et 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
Preparing a Second LPA 11-K for UETP Testing
Devices Not Tested
Preparing for VA~cluster Testing
Preparing a Small-Disk System
Preparing DECnet

7-3
7-4
7-4
7-5
7-5
7-6
7-6
7-6
7-7
7-7
7-7
7-8
7-8
7-8
7-9
7-10

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 • 7-13
Using CTRL/C • 7-14

7-10
7-11
7-11
7-12
7-12
7-13

7.3.~

7.3.10
7.3.11
7.;3.12
7.3.13
7.3.14
7.3.15
7.4
7.4.1
7.4.2
7.4.3
7.4.4
7.4.5

7.4.5.1
7.4.5.2

viii

7-1

Contents

7.5
7.5.1
7.5.2
7.5.2.1

7.5.3
7.5.4
7 .5.4.1
7.5.4.2
7.5.4.3
7 .5.4.4
7.5.4.5
7.5.4.6
7.5.4.7
7.5.4.8
7.5.4.9
7.5.4.10

7.6
7.6.1
7.6.2
7.6.2.1
7.6.2.2

7.6.3
7.6.4
7.6.4.1
7.6.4.2

7.6.5

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

7-14
7-14
7-15

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

7-27
7-28
7-28

7-17
7-18

7-31
7-32
7-35

PART II
CHAPTER 8 STARTUP AND SHUTDOWN PROCEDURES

8-1

8.1

OVERVIEW OF BOOTING

8-1

8.2

SNIFFER BOOT

8-2

8.3
8.3.1

AUTOMATIC BOOT
Changing the Default Boot Device

8-2
8-3

Contents

8.4

MANUAL BOOT

8-4

8.5

CONVERSATIONAL BOOT

8-5

8.6

BOOTING WITH XDELTA

8-7

8.7

IF THE SYSTEM DOES NOT BOOT

8-7

8.8
8.8.1
8.8.2

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

8-7
8-8
8-8

8.9

IF THE SYSTEM FAILS

8-9

CHAPTER 9 BACKUP PROCEDURES
9.1
9.1.1
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6

OVERVIEW OF STANDALONE BACKUP
Installing Standalone BACKUP on the System Disk
Booting Standalone BACKUP from the System Disk
Installing Standalone BACKUP on a Diskette
Booting Standalone BACKUP from a Diskette
Installing Standalone BACKUP on a Tape Cartridge
Booting Standalone BACKUP from a Tape Cartridge

9-1
9-1
9-2
9-3
9-4
9-5
9-6

9.2
9.2.1
9.2.2
9.2.3
9.2.4

BACKING UP THE SYSTEM DISK
Backing Up the System Disk to Diskettes
Restoring the System Disk from Diskettes
Backing Up the System Disk to Tape Cartridges
Restoring the System Disk from Tape Cartridges

9-7
9-7
9-9
9-10
9-12

APPENDIX A CONFIGURING DEVICES
A. 1

9-1

PREVENTING AUTOCONFIGURATION

A-1
A-1

Contents

A.2

USING THE CONNECT COMMAND

A-2

APPENDIX B VAXSTATION 2000/MICROVAX 2000 1/0 SPACE

B-1

APPENDIX C VAXSTATION 2000/MICROVAX 2000 DISK DRIVER

C-1

GLOSSARY

Glossary-1

INDEX

FIGURES
2-1

VAXstation 2000 ON/OFF Switch

2-2

VAXstation 2000 HALT Button

2-3

VAXstation 2000 Expansion Box and System Box

2-8

2-4

VAXstation 2000 Tape Cartridge Drive

2-9

2-5

Inserting a Label on a Tape Cartridge

2-12

2-6

Positioning the Write-Protect Switch

2-13

2-7

How to Insert a Tape Cartridge

2-14

2-8

V AXstation 2000 Diskette Drive

2-17

2-9

RX33 Diskette

2-19

2-10

The Diskette Write-Protected Tab

2-20

2-11

Diskette Being Inserted into Drive

2-21

2-1

Turning On the Console Terminal

2-4

2-2

TK50 Tape Cartridge Drive Controls

2-10

2-3

Tape Cartridge Drive Indicator Lights

2-11

2-4

Differences Between RX33 and RX50 Diskettes

2-17

2-5

Fixed Disk Drives

2-24

4-1

Installation Questions for Local Area and
Mixed-Interconnect Configurations

4-7

Installation Questions for Local Area and
Mixed-Interconnect Configurations

5-8

The Device Tests

7-31

TABLES

5-1
7-1

Contents

8-1

Default Boot Device Names

8-2

SYSGEN Commands Used in SYSBOOT

8-4
8-6

A-1

VAXstation 2000/MicroVAX 2000 Autoconfiguration
Table

A-2

VAXstation 2000/MicroVAX 2000 Address Map

B-1

xii

Preface
The VAXstation 2000 and MicroVAX 2000 computers both use the MicroVAX
II processor chip. The VAXstation 2000 computer is a single-user workstation,
and the MicroVAX 2000 computer is a multi-user system.
This guide refers to the following products by their abbreviated names:
•

The VAXstation 2000 computer is referred to as the VAXstation 2000.

•

The MicroVAX 2000 computer is referred to as the MicroVAX 2000.

•

The VAXstation 2000 and Micro VAX 2000 computers are referred to
collectively as the VAXstation 2000/MicroVAX 2000.

VMS Installation and Operations: VAXstation 2000, MicroVAX 2000 contains
specific installation and operations information for the VAXstation 2000 and
MicroVAX 2000 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 the VAXstation
2000/MicroVAX 2000.

Document Structure
VMS Installation and Operations: VAXstation 2000, MicroVAX 2000 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 system hardware you use during the installation.

•

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 from a tape
cartridge.

•

Chapter 5 describes how to install the VMS operating system from
diskettes.

•

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

•

Chapter 7 describes the User Environment Test Package (UETP) and how
you can use it to test the system.

xiii

Preface

Part II
•

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

•

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

•

Appendix A describes how to configure manually the devices attached to
the system.

•

Appendix B contains information about the physical addresses in the
VAXstation 2000/MicroVAX 2000 1/0 space.

•

Appendix C contains information about the VAXstation 2000/MicroVAX
2000 disk driver.

•

The Glossary lists and defines terms.

Associated Documents
The followi11:g documents may be useful:

xiv

•

VMS Release Notes-provides notes on 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 VMS 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 hardware information on system hardware.

Preface

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
05-JUN-1988 11 :55:22

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

$TYPE MYFILE.DAT

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.

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 ( · ) 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 Chapters 1 through
3 of this guide and follow the appropriate installation procedure.

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 initialize 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 an 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

VAXstation 2000/MicroVAX 2000 Hardware

Before you install the VMS operating system, you need to be familiar with
the following VAXstation 2000 /Micro VAX 2000 hardware components:
•

ON/OFF switch

•

HALT button

•

Console terminal

•

Optional expansion boxes

•

Diskette drive

•

Tape cartridge drive

•

Fixed disk

This chapter does not provide a detailed description of VAXstation 2000/
MicroVAX 2000 hardware; it describes the hardware you need to be familiar
with to perform system management operations. For a detailed description
of hardware for your configuration, see the hardware manuals supplied with
your VAX computer.

2.1

The ON/OFF Switch
The ON/OFF switch, shown in Figure 2-1, is located on the front panel of
the system box and any expansion boxes your system might have. Setting the
switch to 1 turns the power on. Setting the switch to 0 turns the power off.

2-1

VAXstation 2000/MicroVAX 2000 Hardware
2.1 The ON/OFF Switch

Figure 2-1

VAXstation 2000 ON/OFF Switch

ZK-7482-HC

2.2

The HALT Button
The HALT button is located on the panel at the back of the system box,
next to the line printer port. The button is indicated by the halt icon, which
consists of an inverted triangle within a circle. Figure 2-2 shows the HALT
button on the VAXstation 2000. To put the system in console mode, press
the HALT button. When the.system is in console mode, the console terminal
displays the console-mode prompt(> > > ).
Note: Although the back of the MicroVAX 2000 is slightly different from the
V AXstation 2000, the HALT button is in the same location..

2-2

VAXstation 2000/MicroVAX 2000 Hardware
2.2 The HALT Button

Figure 2-2

VAXstation 2000 HALT Button

UNDERNEATH VIEW
HALT
BUTION
ETHERNET
SWITCH

ZK-7483-HC

2.3

The Console Terminal and Serial Lines
In general, use the console terminal to boot the operating system or to shut
it down. During installation use the console terminal to boot the system and

monitor the installation process.
•

On the VAXstation 2000, the workstation display monitor and keyboard
act as the console terminal.

•

On the MicroVAX 2000, the terminal that is attached to connector 1 on
the DEC423 converter acts as the console terminal. You can use any
supported terminal (a VT220 or VT240, for example) as the console
terminal on a MicroVAX 2000.

The console terminal runs in two different modes: program mode and console
mode.
•

Program mode - When the console terminal is in program mode, the
VMS operating system is running. In program mode you can enter DCL
commands, run programs, and receive system messages.

2-3

VAXstation 2000/MicroVAX 2000 Hardware
2.3 The Console Terminal and Serial Lines

•

2.3.1

Console mode - When the console terminal is in console mode, the
VMS operating system is not running. The console terminal displays the
console-mode prompt(> > > ). In console mode, you can control and
monitor system operations by entering console-mode commands.

Turning On the Console Terminal
Turn on the power to the console terminal before turning on the power to the
system. To turn on the console terminal, use the following procedure:
1

Make sure that the cable between the console terminal and the system is
connected properly.

Make sure that the power cable is connected to the terminal and plugged
in to a wall outlet.

If you have a VAXstation 2000, press the power switch on the back of the
workstation monitor.
If you have a MicroVAX 2000, turn the terminal power switch to the ON
position.

The terminal power switch is located in different positions on different types
of console terminals. Table 2-1 describes the location of the power switch
on some supported terminals and how each terminal should respond. If your
terminal is not listed, see the owner's manual for your terminal.
Table 2-1

2-4

Turning On the Console Terminal

Terminal Type

Power Switch Location

Terminal Response

VT 100-series terminal

Power switch is on the
back left.

The terminal beeps
and a blinking cursor
(either a rectangle
or an underscore) is
visible on the screen.

VT220 terminal

Power switch is on the
back left.

The terminal beeps
and displays VT220
OK in the middle of the
screen.

VT240 terminal

Power switch is on the left
corner at the front of the
accompanying terminal box.
(On VT200-series graphics
terminals, there also is a
power switch on the back
right of the terminal screen.)

The terminal beeps
and displays VT240
OK in the middle of the
screen.

VT330 terminal

Power switch is on the left
side of the terminal screen.

The terminal beeps
and displays VT330
OK in the middle of the
screen.

VT340 terminal

Power switch is on the left
side of the terminal screen.

The terminal beeps
and displays VT340
OK in the middle of the
screen.

VAXstation 2000/MicroVAX 2000 Hardware
2.3 The Console Terminal and Serial Lines

Table 2-1 (Cont.)

2.3.2

Turning On the Console Terminal

Terminal Type

Power Switch Location

Terminal Response

LA34 hardcopy terminal

Power switch is on the
back left.

The type head moves
to the first position on
a line.

LA 120 hardcopy terminal

Power switch is on the
front left, halfway down the
stand.

The type head moves
to the first position on
a line.

Diagnostic Console Terminal
Because the console terminal is an important tool in diagnosing system
hardware failures, the VAXstation 2000 /MicroVAX 2000 provides for a
diagnostic console terminal in case the primary console terminal is not
working. You can use any supported terminal as the diagnostic console
terminal. You can also use a hardcopy terminal (for example, an LAlOO)
as a diagnostic console terminal if you want a hardcopy of the installation
procedure.
Note: You cannot use a VR260 or VR290 monitor as a diagnostic console
terminal.
To attach a diagnostic console terminal to a VAXstation 2000 or Micro VAX
2000, you need a BCC08 cable. To attach a diagnostic console terminal, 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

Answer the questions. When the procedure asks if an automatic 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

Turn the ON/OFF switch on the system box and any expansion boxes to
the 0 (off) position. Also turn off the power to the console terminal.

If you have a MicroVAX 2000, remove the DEC423 converter.

Attach the end of the BCC08 cable marked CONSOLE to the serial port
of the diagnostic console terminal. Attach the other end to the printer
port on the system box. Turn on the diagnostic console terminal.

Check the baud rate on the diagnostic console terminal (see the
documentation that came with your terminal). The baud rate should
be set to 9600.

Turn on the system.

2-5

VAXstation 2000/MicroVAX 2000 Hardware
2.3 The Console Terminal and Serial Lines

The primary console terminal is disabled. You can use the diagnostic console
terminal in its place.

CAUTION: Do not turn off the diagnostic console terminal while the VMS operating
system is running, because you might halt the system. If you accidentally
turn off the diagnostic console terminal and halt the system, you can
resume your process by turning on the terminal, pressing RETURN to
get the console-mode prompt(> > > ), and entering the CONTINUE
command.
If you do not have a hardcopy terminal, you can still get a hardcopy of

the installation procedure by connecting a printer to the diagnostic console
terminal. For example, if you use a VT220 terminal as the diagnostic console
terminal, you could attach an LASO printer to the diagnostic console terminal.
You can set up the terminal so that whatever is displayed on the screen
is printed. To attach a printer to the diagnostic console terminal, use the
following procedure:
1

Make sure the power to the system box, diagnostic console terminal,
expansion boxes (if present), and printer is off.

Attach one end of a BCCOS printer cable to the printer port of the
diagnostic console terminal. Attach the other end of the cable to the
connector on the printer.

Turn on the printer.

Check the baud rate on the printer (see the documentation that came
with your printer). The baud rate should match what the terminal you
are using requires (see the documentation that came with your terminal).

Turn on the diagnostic console terminal.

Check the set-up on the diagnostic console terminal to make sure
characters displayed on the terminal are printed (for example, on the
VT220 this set-up characteristic is called AUTOPRINT MODE).

Turn on the expansion boxes (if present), and the system box.

To disconnect the diagnostic console terminal, 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

2-6

Turn the ON/OFF switch on the system box and any expansion boxes to
the 0 (off) position.

Turn off and disconnect the diagnostic console terminal.

If you have a MicroVAX 2000, reconnect the DEC423 converter.

Turn on the system.

VAXstation 2000/MicroVAX 2000 Hardware
2.3 The Console Terminal and Serial Lines

2.3.3

The VAXstation 2000 Serial Lines
The VAXstation 2000 has four serial lines, each with a specific purpose. Serial
line 0 is for the LK201 keyboard, and serial line 1 is for a mouse or tablet
pointing device. The DCL command SHOW DEVICE displays these serial
lines along with the graphics video monitor as VCAO.
Serial line 2 is for a modem or other serial communication device that allows
you to dial into your system. The DCL command SHOW DEVICE displays
this serial line as TTA2. Serial line 3 is for a printer. The DCL command
SHOW DEVICE displays this serial line as TTA3.
The VAXstation 2000 console terminal is called OPAO. The console terminal
normally takes input from the LK201 keyboard and displays output on
the workstation display monitor. However, you can connect a diagnostic
console terminal to the printer port, as described in Section 2.3.2. The BCC08
terminal cable tells the system that a diagnostic console terminal, not a
printer, is attached to the printer port. To connect a printer or terminal for
use other than a diagnostic console, you would use a BCCOS terminal cable.
The DCL command SHOW DEVICE displays OP AO in place of TTA3 if you
boot the system using the diagnostic console terminal.
By default, the SYSGEN command AUTOCONFIGURE automatically
configures the serial lines when you boot the system. Because of the
complexity of this process, DIGITAL recommends that you let SYSGEN
configure the serial lines automatically. If you need to connect the serial lines
manually using the SYSGEN command CONNECT, see Appendix A.

2.3.4

The MicroVAX 2000 Serial Lines
The MicroVAX 2000 has four serial lines to which user terminals can connect.
Three of the serial lines have a device name of the form TTAn, where n is a
number between 0 and 3 corresponding to the unit number of the line.
The MicroVAX 2000 console terminal is nbrmally attached to serial line 0 and
called OP AO. However, you can connect a diagnostic console terminal to the
printer port, as described in Section 2.3.2. The BCC08 terminal cable tells
the system that a diagnostic console terminal, not a printer, is attached to the
printer port. To connect a printer or terminal for use other than a diagnostic
console, you would use a BCCOS terminal cable. The DCL command SHOW
DEVICE displays OP AO in place of TTA3 if you boot the system using the
diagnostic console terminal.
By default, the SYSGEN command AUTOCONFIGURE automatically
configures the serial lines when you boot the system. Because of the
complexity of this process, DIGITAL recommends that you let SYSGEN
configure the serial lines automatically. If you need to connect the serial lines
manually using the SYSGEN command CONNECT, see Appendix A.

2-7

VAXstation 2000/MicroVAX 2000 Hardware
2.4 The Optional Expansion Box

2.4

The Optional Expansion Box
Your VAXstation 2000 /MicroVAX 2000 may be equipped with optional
expansion boxes. These expansion boxes provide additional storage for the
system. There are two different expansion box configurations:
•

The tape cartridge expansion box, which contains a TK50 tape cartridge
drive

•

The fixed disk drive expansion box, which contains an RD53 or RD54
fixed disk

Your system configuration can contain one or both of these expansion boxes
in addition to the system box. Each expansion box has an ON/OFF switch
identical to the one on the system box. Figure 2-3 shows a VAXstation 2000
expansion box resting on top of the system unit.
Figure 2-3

2-8

VAXstation 2000 Expansion Box and System Box

VAXstation 2000/MicroVAX 2000 Hardware
2.5 The TK50 Tape Cartridge Drive

2.5

The TK50 Tape Cartridge Drive
If you are installing the VMS operating system from tape cartridges, you
should be familiar with the tape cartridge drive in the expansion box. If you

are installing the VMS operating system from diskettes, go to Section 2.6.
The device name of the tape cartridge drive is MUAO. Figure 2-4 shows the
VAXstation 2000 tape cartridge expansion box resting on top of the system
unit.
Figure 2-4 VAXstation 2000 Tape Cartridge Drive

ZK-7489-HC

When using the TKSO tape cartridge drive shown in Figure 2-4, you should
be aware of the following:
•

The green light blinks when the tape in the drive is 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.

2-9

VAXstation 2000/MicroVAX 2000 Hardware
2.5 The TKSO Tape Cartridge 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 rapidly 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.

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 glo~s 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.
Table 2-2 summarizes the tape cartridge drive controls. Table 2-3 describes
the tape cartridge drive lights.
Table 2-2

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

Cartridge release handle

Open

Lets you insert or remove a
tap~ after rewind and unload

operations are complete.
Closed

2-10

Locks tape in operating position.

VAXstation 2000/MicroVAX 2000 Hardware
2.5 The TK50 Tape Cartridge Drive

Table 2-3

2.5.1

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 rapid
blinking means tape cal'ibration
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.

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-5 shows how to insert the label on a
tape cartridge.

2-11

VAXstation 2000/MicroVAX 2000 Hardware
2.5 The TK50 Tape Cartridge Drive

Figure 2-5

Inserting a Label on a Tape Cartridge

95MB
296MB

D
D

LABEL

ZK-6520-HC

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-6 shows how to write-protect a tape cartridge.

2-12

VAXstation 2000/MicroVAX 2000 Hardware
2.5 The TK50 Tape Cartridge Drive

Figure 2-6

Positioning the Write-Protect Switch

NOT WRITEPROTECTED

WRITEPROTECTED

ZK-6521-HC

2.5.2

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

Make sure the tape 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 MUAO

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.5.5 to dismount the tape cartridge.
Then follow the directions for removing a tape cartridge in Section 2.5.6.

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.

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.

2-13

VAXstation 2000/MicroVAX 2000 Hardware
2.5 The TK50 Tape Cartridge Drive

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

Figure 2- 7

GREEN INDICATOR
LIGHT IS LIT

How to Insert a Tape Cartridge

CARTRIDGE
RELEASE HANDLE

LOAD/UNLOAD
BUTTON
RED INDICATOR
LIGHT IS LIT

2-14

ZK-7490-HC

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 pla(:e. 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 15 seconds and 3 1/2 minutes. During this time, the green
light blinks. When the tape is ready, the green light glows.

VAXstation 2000/MicroVAX 2000 Hardware
2.5 The TK50 Tape Cartridge Drive

2.5.3

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

You should initialize a new tape cartridge before you use it the first time.
Initialize an old tape cartridge to erase its contents.
Before you initialize a tape cartridge, 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 MUAO volume-label

where volume-label is a one to six 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 and gives it the label TEST:
$ INITIALIZE MUAO TEST

2.5.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 MUAO volume-label

where volume-label is the one to six character alphanumeric identification you
assigned to the tape cartridge with the INITIALIZE command.
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 MUAO

2-15

VAXstation 2000/MicroVAX 2000 Hardware
2.5 The TK50 Tape Cartridge Drive

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

The system displays the volume label.

2.5.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 finish 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 MUAO

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

2.5.6

Removing a Tape Cartridge from a TK50 Drive
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.6

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

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

Push the cartridge-release handle closed until it locks firmly into place.

The Diskette Drive
CAUTION: Use an RX33 diskette only in an RX33 diskette drive. Because RX33 and
RX50 diskettes have incompatible formats, using an RX33 diskette in an
RXSO drive might destroy the data on the diskette and might damage the
drive. You can use an RXSO diskette in an RX33 diskette drive.
If you are installing the VMS operating system from diskettes, you should
be familiar with the diskette drive on the front of your system. If you are

installing the VMS operating system from a tape cartridge, make sure you
read Section 2.5.
The RX33 diskette drive is located behind the drive door on the front of the
system box. Figure 2-8 shows a VAXstation 2000 diskette drive with the door
open. The diskette drive has an access slot with a drive lever that lets you
insert and remove diskettes. The device name of the RX33 diskette drive is
DUA2.

2-16

VAXstation 2000/MicroVAX 2000 Hardware
2. 6 The Diskette Drive

Figure 2-8

VAXstation 2000 Diskette Drive

ZK-7485-HC

When using the diskette drive shown in Figure 2-8, you should be aware of
the following:
•

The diskette drive activity light glows red when the diskette in the drive
is moving (being read from or written to).

CAUTION: Never attempt to remove a diskette from the drive when the activity
light glows; this damages the diskette and might damage the drive.
•

2.6.1

The diskette drive lever holds the diskette in the drive. After you insert
a diskette in the drive, turn the lever perpendicular to the access slot.
When you turn the lever parallel to the access slot, the diskette pops out
of the drive. Never turn the lever parallel to the access slot when the
drive activity light is on.

RX33 Diskettes
You can use either RX33 or RXSO diskettes in the RX33 diskette drive.
Table 2-4 shows the differences between these two types of diskettes.
Table 2-4

Differences Between RX33 and RX50 Diskettes

Diskette

Description

Storage
Capacity

Preformatted?

RX33

Grey or black plastic jacket; no arrow

2400 blocks

RX50

Black plastic jacket; red arrow

800 blocks

Yes

CAUTION: Use an RX33 diskette only in an RX33 diskette drive. Because RX33 and
RXSO diskettes have incompatible formats, using an RX33 diskette in an
RXSO diskette drive might might destroy the data on the diskette and

2-17

VAXstation 2000/MicroVAX 2000 Hardware
2. 6 The Diskette Drive

might damage the diskette. You can use an RX50 diskette in an RX33
diskette drive.
Also, format an RX50 diskette using only Field Service diagnostic tools.
Consider discarding an RX50 diskette rather than formatting it. For more
information, contact DIGIT AL Field Service.
Figure 2-9 shows an RX33 diskette.
When using the diskette shown in Figure 2-9, you should be aware of the
following:
•

Each diskette comes in a protective paper envelope. You should keep
diskettes in their paper envelopes when you are not using them.

•

The diskette label provides information about the contents of the diskette.
Label a diskette if you will copy files to it (distribution diskettes are
labeled already). You should write on the diskette label before you affix
it to the diskette. To write on a diskette label after you affix it to the
diskette, use a felt-tipped pen. If you use a pencil or pen to write on the
label, you might damage the diskette.

•

The plastic diskette jacket is the protective cover for the diskette surface.
There are slots in the cover through which the drive head accesses
the diskette. You should avoid touching the diskette surface at these
openings.

•

The write-protect notch is a square-shaped cut in the side of the diskette
that controls whether you can write to the diskette.
To write-protect a diskette, place one of the adhesive foil tabs supplied
with your diskettes over the write-protect notch on the side of the plastic
cover (see Figure 2-10). Write-protecting diskettes guards against loss of
data or accidental overwriting. Always write protect distribution diskettes
before an installation.
To write-enable a diskette, make sure that no adhesive foil tab covers the
diskette write-protect notch. When the write-protect notch is uncovered,
you can add, change, or delete information on the diskette. You should
write-enable a diskette if you will copy or back up files to it.

2.6.2

Inserting an RX33 Diskette
To insert a diskette into the diskette drive, use the following procedure:
1

Open the drive door on the front panel of the VAXstation 2000 /
MicroVAX 2000.

Make sure the drive is empty. If the VMS operating system is not
running, go to step 3.
If the VMS operating system is running and there is a diskette in the
drive, enter the following command and press RETURN:
$ SHOW DEVICE DUA2

2-18

VAXstation 2000/MicroVAX 2000 Hardware
2. 6 The Diskette Drive

Figure 2-9

RX33 Diskette

WRITE PROTECT
NOTCH

DISKETTE
SURFACE
DO NOT
TOUCH

ZK-7486-HC

2-19

VAXstation 2000/MicroVAX 2000 Hardware
2.6 The Diskette Drive

Figu~e 2-10

The Diskett~ Write-Protected Tab

WRITEPROTECT

TAB

ZK-7487-HC

If the display indicates that the status of the diskette is MOUNTED, you
must dismount the diskette and remove it from the drive. Follow the
directions in Section 2.6.5 to dismount the diskette. Turn the diskette
drive lever until it is parallel to the access slot. Remove the diskette from
the drive and place the diskette in its paper envelope.

CAUTION: Never attempt to remove a diskette from the drive when the red
activity ligpt glows or blinks; you might damage the diskette drive.
3

Remove the diskette you want to insert from its paper envelope. When
you remove the diskette, make sure you handle only the edges. Do not
touch exposed surfaces of the diskette.

Write-protect a diskette that contains software that you will install on
your system. Write-enable a diskette if you will copy or back up files to
it.

Hold the di*ette so that the write-protect notch is to your left and
the diskette label faces up. Slide the diskette in the drive until it clicks
into place. If the diskette is aligned incorrectly, the system displays the
following message when you try to access the diskette:
%INIT-F-MEDOFL, medium is offline

If the system displays this error message, remove the diskette from the
drive and reinsert it.

Turn the diskette drive lever until it is perpendicular to the access slot.

Figure 2-11 illustrates this procedure.

2-20

VAXstation 2000/MicroVAX 2000 Hardware
2. 6 The Diskette Drive

Figure 2-11

Diskette Being Inserted into Drive

ZK-7488-HC

2-21

VAXstation 2000/MicroVAX 2000 Hardware
2. 6 The Diskette Drive

2.6.3

Initializing and Formatting an RX33 Diskette
Note: You do not need to initialize and format any diskettes when you install
the VMS operating system.
The INITIALIZE command does the following:
•

Erases any data stored on the diskette

•

Assigns a volume label to the diskette

•

Prepares the diskette to store VMS files

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

CAUTION: Do not initialize and format diskettes that contain operating system
software or files that you want to save. The INITIALIZE command erases
the contents of the diskette.
To initialize and format an RX33 diskette, enter the following command and
press RETURN:
$ INITIALIZE/DENSITY=DOUBLE DUA2 volume-label

where volume-label is a one to six character alphanumeric identification. Write
the volume label of the diskette on the paper label. You will need to know
the volume label when you use the diskette.
For example, the following command initializes and formats the diskette in
the system box and labels it TEST:
$ INITIALIZE/DENSITY=DOUBLE DUA2 TEST

2.6.4

Mounting an RX33 Diskette
Note: You do not need to mount any tape diskettes when you install the
VMS operating system. The VMS installation procedure does this
automatically.
After you insert a diskette (and initialize it, if it is new), you must mount it,
to make it available to the system. To mount a diskette, use the MOUNT
command in the following format:
$ MOUNT DUA2 volume-label

where volume-label is the label you assigned to the diskette with the
INITIALIZE command.
If you do not specify the correct volume label when you mount the diskette,
the system displays the following messages:
%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 DUA2

2-22

VAXstation 2000/MicroVAX 2000 Hardware
2. 6 The Diskette Drive

Then enter the following command to determine the volume-label of the
diskette:
$ SHOW DEVICE DUA2

The system displays the volume label.

2.6.5

Dismounting an RX33 Diskette
Note: You do not need to dismount any diskettes when you install the
VMS operating system. The VMS installation procedure does this
automatically.
When you finish using a diskette, you should dismount it. To dismount a
diskette, enter the DISMOUNT command in the following format and press
RETURN:
$ DISMOUNT DUA2

After you have dismounted the diskette, you can remove it from the diskette
drive.

2.6.6

Removing an RX33 Diskette
To remove a diskette from the drive, use the following procedure:
1

Open the door on the front panel of the VAXstation 2000 /Micro VAX
2000 system unit.

Make sure that the red activity light on the drive is off.

CAUTION: Never turn the diskette-drive lever if the activity light glows or
blinks; you might damage the diskette drive.

2. 7

Turn the diskette drive lever until it is parallel to the access slot.

Gently remove the diskette from the drive. Make sure you handle only
the edges of the diskette.

Put the diskette in its paper envelope.

The Fixed Disk Drive
Your VAXstation 2000 /Micro VAX 2000 contains a fixed disk drive
permanently sealed within the system box. The system box contains either an
RD32 or RD53 fixed disk drive. If your configuration includes an expansion
box, the expansion box contains an RD53 or RD54 fixed disk drive. Table 2-5
lists the capacity of these fixed disk drives.

2-23

VAXstation 2000/MicroVAX 2000 Hardware
2. 7 The Fixed Disk Drive

Table 2-5

2-24

Fixed Disk Drives

Drive

Height

Storage Capacity

RD32

Half

83,204 blocks

RD53

Full

138,672 blocks

RD54

Full

311,200 blocks

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
diskettes or 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 system 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

Device Names
At different times during the installation you need to tell the system which
drive contains the distribution media and which drive contains the system
disk. You do this by referring to the diskette or tape cartridge drive that
holds the distribution media and to the fixed disk that you want to be your
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.

•

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

For example, DUA2 is the device name for the diskette drive (if your system
has one). DU is the device code for the diskette drive, A names the controller
(the controller provides the interface between the processor and the drive),
and 2 is the unit number.

3-1

Before Installing VMS
3.2 Device Names

The device names for the VAXstation 2000 /Micro VAX 2000 are as follows:

Note: Your configuration might not include all of these devices
•

DUAO-fixed disk in the system box

•

DUAl-fixed disk in an expansion box

•

DUA2-RX33 diskette drive

•

MUAO-TKSO tape cartridge drive

•

ESAO-network

If your system has more than one fixed disk, you can use either as the system
disk. When choosing a system disk, you need to 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 fixed
disk that will be the system disk.

3.3

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 (Cl, Ethernet, or both).

Note: The VAXstation 2000/MicroVAX 2000 cannot be part of a CI-only
VAXcluster environment.
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 you are installing VMS on. For example:
Enter a value for ALICE'S ALLOCLASS parameter:

Enter the appropriate allocation class value for the VAX computer that you
are installing the VMS operating system on. 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

3-2

Before Installing VMS
3.3 Information on VAXcluster Environments

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 to 4095 or 61440
to 65535.

•

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

3-3

Installing VMS from a Tape Cartridge

This chapter describes installing the VMS operating system on a VAXstation
2000 or MicroVAX 2000 from a tape cartridge. To install the VMS operating
system from diskettes, see Chapter 5.
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 manual
for the VAXstation 2000/MicroVAX 2000.

•

Make sure you have all the items listed on the bill of materials in the
VMS distribution kit. The tape cartridge 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 items.
•

If you are installing the VMS operating system on a VAX computer in

a VAXcluster environment, determine whether you want a local area,
or a mixed-interconnect configuration. For a complete description of
configurations, see the VMS VAXcluster Manual. If you are installing the
VMS operating system in a local area or mixed-interconnect configuration,
you need to obtain the following information from either the network or
VAXcluster manager:
DECnet node name and node address
Cluster group number and password
Allocation class value
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 system disk

Booting standalone BACKUP

4-1

lhstalling VMS from a Tape Cartridge
4.1 Before You Start

Creating the system disk

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 on the system for the
installation:
1

Turn on the console terminal.
•

If you have a VAXstation 2000, press the power switch on the back of

the workstation monitor.
•

If you have a MicroVAX 2000, your console terminal must be set to
8 bits, no parity transmit, and no parity receive. This is the default
for most terminals, except the LA120. The baud rate of the console
terminal should be set to 9600 baud. For instructions on checking
these settings, see the owner's manual provided with your terminal.

Push the power switch on the front of the system box and any expansion
boxes to the 1 (On) position.

The VAXstation 2000 /Micro VAX 2000 should display self-test messages
similar to the following:
KA410-A V1.2
F ... E ... D ... C ... B ... A ... 9 ... 8 ... 7 ... 6 ... 5 ... 4 ... 3 ... 2 ... 1. ..

bK
>>>

If the console-mode prompt(> > > ) does not appear on the screen,

press the HALT button.
If the system does not power up properly (for example, if you receive the

message ?84 FAIL), refer to the troubleshooting section of the hardware
manual supplied with your system.

4-2

To prepare the system disk, go to Section 4.3.

Installing VMS from a Tape Cartridge
4.3 Preparing the System Disk

4.3

Preparing the System Disk
To set up the fixed disk you use during the installation, do the following:
1

If your system consists of more than one fixed disk, decide which one you

want to be the system disk.

If your VAXstation 2000 or MicroVAX 2000 has not run operating system

software previously, the fixed disk(s) might not be formatted. You must
format the fixed disk(s) before you begin the installation. For instructions
on formatting fixed disks, refer to the hardware manual for your system.

CAUTION: Do not format a disk after the installation, or you will erase the
contents of the disk.

4.4

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

2 A 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.
1

Insert the tape cartridge labeled VAX/VMS VS.O BIN TKSO into the tape
cartridge drive.

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

Ignore any error messages about missing drivers that resemble the
following:
%SYSGEN-I-OPENIN, error opening SYS$SYSROOT: [SYSEXE]VEDRIVER.EXE; as input
%SYSGEN-E-FNF, file not found

These messages might be displayed during the installation.

Standalone BACKUP displays the following message:
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

4-3

Installing VMS from a Tape Cartridge
4.4 Booting Standalone BACKUP

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 DUAO:
Available device MUAO:

device type Generic_DU
device type TK50

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

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 31-DEC-1988 15:00
$

4.5

To create a system disk, go to Section 4.5.

Creating a System Disk
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
these save sets from the distribution tape cartridge to your system disk.
The instructions refer to the target-drive. The target-drive is the drive that
holds the system disk.
1

Determine the device name of the system disk. If your VAXstation 2000 /
MicroVAX 2000 system has more than one fixed disk, either of the
following disks can be the system disk:
•

DUAO-disk drive in the system box

•

DUAl-disk drive in the expansion box

Write the device name of the system disk 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 MUAO:VMS050.B/SAVE_SET target-drive:

Substitute the device name of your system disk for target-drive. Your
system disk is either DUAO· or DUAL Make sure you put a colon (:)
after each device name and that you use zeros in the device name and
VMS050.
The required save set is transferred from the distribution tape cartridge to
the system disk. 1 After approximately 25 minutes, the procedure displays
the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

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 9.2

4-4

Installing VMS from a Tape Cartridge
4.5 Creating a System Disk

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:30
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 the HALT button located on the back of the system box.

To boot the system disk, enter the BOOT command in the following
format:
>» B ddcu

Substitute the device name of the system disk for ddcu. The device name
of the system disk is either DUAO or DUAl, the disk you chose to be the
system disk.

When the boot is complete, the procedure displays some messages and
asks 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.
VAX/VMS Version BI50 Major version id = 01 Minor version id = 00
VAX/VMS V5.0 Installation Procedure
%%%%%%%%%%% OPCOM 31-DEC-1988 15:35:12.02 %%%%%%%%%%%
Logfile has been initialized by operator _$0PAO:
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:00

4-5

Installing VMS from a Tape Cartridge
4.5 Creating a System Disk

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.
Type MUAO and press RETURN:
Enter the name of the drive holding the distribution media (DDCU): MUAO

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

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 12.
If you are installing the VMS operating system in a cluster, type Y (for
YES), press RETURN, and go to step 10.

Note: If you answer YES to the V AXcluster question, you must have a
VAXcluster license.
1 0 The procedure displays the following message:
Now configuring system to be a cluster member.

11 Table 4-1 lists the questions you are asked if you want either a local area
or mixed-interconnect configuration. Typical responses are explained in
the tables.

4-6

Installing VMS from a Tape Cartridge
4.5 Creating a System Disk

Table 4-1

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 3 1 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 VAXcluster Manual for
information on served cluster disks.

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.

12 The procedure displays the following message:
You may now remove the distribution tape from _MUAO:

Remove the distribution tape cartridge from the tape cartridge drive.

13 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:

4-7

Installing VMS from a Tape Cartridge
4.5 Creating a System Disk

Now we will ask you for new 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 passwords for the
following accounts:
SYSTEM, SYSTEST, FIELD
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 SYSTEST verified
%VMS-I-PWD_OKAY, account password for FIELD 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.

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

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

%UAF-I-RDBDONEMSG, rights database modified

4-8

Installing VMS from a Tape Cartridge
4.5 Creating a System Disk

15 After the procedure creates your RIGHTS database, go to Section 4.6 to
install the mandatory update.

4.6

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 the RIGHTS database, it displays the
following messages:
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.
-BUILP 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 m11st now install the MANDATORY UPDATE, which can be found
on a separate distribution volume.
VAX/VMS Software Product Installation Procedure VS 0
It is 31-DEC-1988 at 15:17
Enter a (?) at any time for help.

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:

MUAO:

The procedure displays the following message:
Please mount the first volume of the set on MUAO:
*Are you ready?

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

mounted on _MUAO:

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

4-9

Installing VMS from a Tape Cartridge
4.6 Installing the Mandatory Update and Running AUTOGEN

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

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 like this:
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 Shutdown

The system tries to reboot automatically.
If the system does not reboot automatically, press the HALT button, and
enter the BOOT command in the following format:
>» B ddcu

Substitute the device name of the system disk for ddcu.
8

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
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 15:00: %%%%%%%%%%%
Logfile has been initialized by operator _OPAO:
Logfile is SYS$SYSROOT: [SYSMGR]OPERATOR.LOG;l

4-10

Installing VMS from a Tape Cartridge
4.6 Installing the Mandatory Update and Running AUTOGEN

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 16:40:02.30
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.
9

Press RETURN. The system asks you for a user name and password. Log
into the SYSTEM account so that you can perform certain post installation
tasks. For example:
Welcome to VAX/VMS V5.0
USERNAME: SYSTEM
PASSWORD: PANCAKES

Welcome to VAX/VMS V5.0

If you forget the password, follow the instructions for breaking into the
system in the Guide to Setting Up a VMS System.

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

4-11

Installing the VMS Operating System from
Diskettes
This chapter describes installing the VMS operating system on a VAXstation
2000 or MicroVAX 2000 from diskettes. To install the VMS operating system
from tape cartridges, see Chapter 4.

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.

5.1

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

Make sure the hardware has been installed and checked for proper
operation. For detailed hardware information see the hardware manual
for the VAXstation 2000/MicroVAX 2000.

•

Make sure you have all the items listed on the bill of materials in the
VMS distribution kit. The diskette distribution kit should contain the
following:
25 RX33 diskettes that contain the VMS required (10 diskettes), library
(11 diskettes), and optional (4 diskettes) save sets
One RX33 diskette that contains standalone BACKUP
One RX33 diskette that contains the mandatory update
If your kit is incomplete, notify the DIGITAL Software Distribution
Center. Request priority shipment of any missing items.

•

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

DECnet node name and node address
Cluster group number and password
Allocation class value
The installation procedure transfers the VMS files from the distribution RX33
diskettes to the system disk. The proce9ure consists of the following stages:
1

Turning on the system

Preparing the system disk

5-1

Installing the VMS Operating System from Diskettes
5.1 Before You Start

Booting standalone BACKUP

Creating the system disk

Installing the mandatory update and running AUTOGEN

The entire procedure takes approximately two 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.

5.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 on the system for the
installation:
1

Turn on the console terminal.

•

If you have a VAXstation 2000, press the power switch on the back of
the workstation monitor.

•

If you have a MicroVAX 2000, your console terminal should be set to
8 bits, no parity transmit, and no parity receive. This is the default
for most terminals, except the LA120. The baud rate of the console
terminal should be set to 9600 baud. For instructions on checking
these settings, see the owner's manual provided with your terminal.

Push the ON/OFF switch on the front of the system box and any
expansion boxes to the 1 (On) position.

The VAXstation 2000 /Micro VAX 2000 should display a verification
message similar to the following:
KA410-A V1.2
F ... E ... D ... C ... B ... A ... 9 ... 8 ... 7 ... 6 ... 5 ... 4 ... 3 ... 2 ... 1 ...

OK
>>>

If the console-mode prompt(> > > ) does not appear on the screen,
press the HALT button.
If the system does not power up properly (for example, if you receive the
message ?84 FAIL), refer to the troubleshooting section of the hardware
manual for your system.
4

5-2

To prepare the system disk, go to Section 5.3.

Installing the VMS Operating System from Diskettes
5.3 Preparing the System Disk

5.3

Preparing the System Disk
This section describes the steps for setting up the system disk you use during
the installation.
1

If your system consists of more than one fixed disk, decide which one you
want to be the system disk.

If your VAXstation 20QP or MicroVAX 2000 has not run operating system
software previously, the fixed disk(s) might not be formatted. You must
format the fixed disk(s) before you begin the installation. For instructions
on formatting fixed disks, refer to the hardware manual for your system.

CAUTION: Do not format a disk after the installation, or you will erase the
contents of the disk.
3

5.4

To boot standalone BACKUP, go to Section 5.4.

Bootin~ Standalone BACKUP

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

Volume Label 2

VAX/VMS V5 .0 RX33 S/A BKUP

STANDBACKUP

paper label is the label affixed to a diskette.

2 A volume label is the name the VMS operating system uses to refer to a diskette.

During
the installation the procedure displays the volume label, not the paper label, in messages.

Booting standalone BACKUP takes approximately three minutes.
1

Insert the diskette labeled VAX/VMS VS.O RX33 S/A BKUP in the
diskette drive.

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

Ignore any error messages about missing drivers that resemble the
following:
%SYSGEN-I-OPENIN, error opening SYS$SYSROOT:[SYSEXE]VEDRIVER.EXE; as input
file not found

%SYSG~N-E-FNF,

These messages might be displayed during the installation.

A few minutes later, standalone BACKUP displays the following message:
VAX/VMS Version V5.0 Major version id = 01 Minor version id = 00

5-3

Installing the VMS Operating System from Diskettes
5.4 Booting Standalone BACKUP

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 DUAO:
Available device DUA2:

device type Generic_DU
device type RX33

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, Stand-alone BACKUP V5.0; the date is 31-DEC-1988 15:00
$

5.5

Remove the diskette labeled VAX/VMS V5.0 RX33 S/ A BKUP from the
diskette drive.

To create a system disk, go to Section 5.5.

Creating a System Disk
The VMS files are stored on the distribution diskettes as three save sets:
required, library, and optional. This section describes the steps for transferring
these save sets from the distribution diskettes to your system disk.
The instructions refer to the target-drive. The target-drive is the drive that
holds the system disk.
1

Determine the device name of the system disk for your configuration. If
your VAXstation 2000/MicroVAX 2000 configuration has more than one
fixed disk, you can choose which disk you want to be the system disk:
•

DUAO-disk drive in the system box

•

DUAl-disk drive in the optional expansion box

Write the device name of the system disk on a piece of paper. You will
need this information throughout the installation.

Insert the diskette labeled VAX/VMS V5.0 RX33 REQ 1/10 into the
diskette drive.

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

Substitute the device name of your system disk for target-drive. Your
system disk is either DUAO or DUAL Make sure you put a colon (:)
after each device name and that you use zeros in the device name and
VMS050.
The procedure begins to transfer the required save set from the
distribution diskettes to the system disk. 1 The entire process takes
approximately 30 minutes. During the process the procedure displays the
following message:
1

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

5-4

Installing the VMS Operating System from Diskettes
5.5 Creating a System Disk

%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYREAD, Mount volume 2 on _SABKUP$DUA2: for reading
Enter "YES" when ready:

Note: Disregard any error messages similar to the following:
%BACKUP-W-INCFILATR, incomplete file attribute data for

These messages are normal when installing the VMS operating system
from diskettes.
4

Remove the diskette labeled VAX/VMS VS.O RX33 REQ 1/10 diskette
and insert the diskette labeled VAX/VMS V5;0 RX33 REQ 2/10 diskette
in the drive. When you are ready to continue, type Y (for YES) and press
RETURN.
The procedure repeats another verification and mount message for each
diskette in the required save set. Each time the procedure displays a
mount message, remove the diskette in the drive and insert the next
diskette in the save set. Each diskette takes approximately three minutes
to process.

After the last diskette is processed, standalone BACKUP displays the
following message:
%BACKUP-I-PROCDONE, Operation completed. Processing finished at 31-DEC-1988 15:30
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 the HALT button located on the back of the system box.

Note: Do not remove the VAX/VMS V5.0 RX33 REQ 10/10 diskette from the
diskette drive until you are directed to do so.

To boot the system disk, use the boot command in the following format:
»> B ddcu

Substitute the device name of the system disk for ddcu. The device name
of the system disk is either DUAO or DUAl, the disk you chose to be the
system disk.
8

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

5-5

Installing the VMS Operating System from Diskettes
5.5 Creating a System Disk

%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:00

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 name of VMSRL5 just press RETURN in response to
the next question.
Enter the volume label for this system disk (no spaces) [VMSRL5] : SYSDSK

10 The procedure asks which drive holds the distribution diskette. Type
DUA2 and press RETURN:
Enter the name of the drive holding the distribution media (DDCU): DUA2

11 Several minutes later the system displays the following messages:
%MOUNT-I-MOUNTED, VMS050 mounted on _DUA2:
Please replace the last floppy from the REQUIRED saveset with
the first floppy from the LLBRARY saveset.
Is the first floppy labeled LIBRARY ready to be mounted [N]?

12 Remove the diskette labeled VAX/VMS VS.O RX33 REQ 10/10. Insert the
diskette labeled VAX/VMS VS.O RX33 LIB 1/11. When you are ready,
type Y (for YES) and press RETURN.
1 3 The installation procedure now transfers the library and optional save sets
to the system disk. This takes approximately 30 minutes.
The procedure displays the following messages:
%MOUNT-I-MOUNTED, VMS050C mounted on _DUA2:
Restoring LIBRARY saveset.
-- please insert the next floppy(s) from the LIBRARY saveset
in DUA2:, when requested to do so.
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-I-RESUME, resuming operations on volume 2
%BACKUP-I-READYREAD, mount volume 2 on _DUA2: for reading
Enter "YES: when ready:

5-6

Installing the VMS Operating System from Diskettes
5.5 Creating a System Disk

14 Remove the diskette labeled VAX/VMS VS.O RX33 LIB 1/11 and insert
the diskette labeled VAX/VMS VS.O RX33 LIB 2/11. Type Y (for YES)
and press RETURN to continue.
The procedure repeats. another mount message for each diskette in the
library save set. Each time the procedure displays a mount message,
remove the diskette in the drive and insert the next diskette of the save
set. Each diskette takes approximately three minutes to process.

1 5 The procedure displays the following message:
Please replace the last floppy from the LIBRARY saveset with
the first floppy from the OPTIONAL saveset.
Is the first floppy labeled OPTIONAL ready to be mounted [NJ?

16 Remove the diskette labeled VAX/VMS VS.O RX33 LIB 11/11 from
the diskette drive and insert the diskette labeled VAX/VMS VS.O RX33
OPT 1/4. When you are ready to continue, type Y (for YES) and press
RETURN.
The procedure displays the following message:
%MOUNT-I-MOUNTED, VMS050D mounted on _DUA2:
Restoring OPTIONAL saveset.
-- please insert the next floppy(s) from the OPTIONAL saveset
in DUA2:, when requested to do so.
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-I-RESUME, resuming operations on volume 2
%BACKUP-I-READYREAD, mount volume 2 on _DUA2: for reading
Enter "YES: when ready:

17 Remove the diskette labeled VAX/VMS VS.O RX33 OPT 1/4 and insert
the diskette labeled VAX/VMS VS.O RX33 OPT 2/4. Type Y (for YES)
and press RETURN.
The procedure repeats another verification and mount message for each
diskette in the optional save set. Each time the procedure displays a
mount message, remove the diskette in the drive and insert the next
diskette of the save set. Each diskette takes approximately three minutes
to process.

1 8 After the optional save set has been transferred, the procedure displays
the following messages:
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, press RETURN, and go to step 21.
If you are installing the VMS operating system in a cluster, type Y, press
RETURN, and go to step 19.

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

5-7

Installing the VMS Operating System from Diskettes
5.5 Creating a System Disk

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

20 Table 5-1 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 5-1

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 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 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 to 4095 or 61440 to 65535.

Enter this cluster's password:

Enter the cluster password. The password
must be from 1 to 3 1 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 .

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

21 The procedure displays the following message:
You may now remove the distribution diskette from _DUA2:

Remove the last diskette of the optional save set from the drive.

5-8

Installing the VMS Operating System from Diskettes
5.5 Creating a System Disk

22 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 new 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 passwords for the
following accounts:
SYSTEM, SYSTEST, FIELD
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 SYSTEST verified
%VMS-I-PWD_OKAY, account password for FIELD 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.

5-9

Installing the VMS Operating System from Diskettes
5.5 Creating a System Disk

23 After you have entered the passwords, the procedure creates your
RIGHTS database. The procedure 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

24 After the procedure creates your RIGHTS database, go to Section 5.6 to
install the mandatory update.

5.6

After the procedure creates the RIGHTS database, it displays the
following messages:
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 15:17
Enter a (?) at any time for help.

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: DUA2:

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

5-10

Insert the diskette labeled VAX/VMS VS.O RX33 MANDATORY UPDATE
in the diskette drive. When you are ready to continue, type Y (for YES)
and press RETURN. The procedure displays the following messages:

Installing the VMS Operating System from Diskettes
5.6 Installing the Mandatory Update and Running AUTOGEN

%MOUNT-I-MOUNTED, VMSMUP

mounted on _DUA2:

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

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 shutdown messages
that begin like this:
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 Shutdown

The system tries to reboot automatically.
If the system does not reboot automatically, press the HALT button and

enter the boot command in the following format:
>» B ddcu

Substitute the device name of the system disk for ddcu.

After the system reboots, it displays the following message:

Note: The procedure might display warning messages that the VMS and
V AXcluster licenses must be registered. Be sure to register these
licenses when the installation procedure finishes.

5-11

Installing the VMS Operating System from Diskettes
5.6 Installing the Mandatory Update and Running AUTOGEN

VAX/VMS Version V5.0 Major version id = 01 Minor version id = 00
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 syst~m (approximately three minutes).

%%%%%%%%%%% OPCOM 31-DEC-1988 15:00: %%%%%%%%%%%
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
SYSTEM
job terminated at 31-DEC-1988 15:00:00.00
Accounting information:
Buffered I/O count:
133
Direct I/O 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.
10 Press RETURN. The system asks you for a user name and password. Log
into the SYSTEM account so that you can perform certain post installation
tasks. For example:
Welcome to VAX/VMS V5.0
USERNAME: SYSTEM
PASSWORD: PANCAKES

Welcome to VAX/VMS V5.0

If you forget the password, follow the instructions for breaking into the
system in the Guide to Setting Up a VMS System.

11 There are several things you must do before you can use the system. For
complete information, see Chapter 6.

5-12

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:

6.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 cart free 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 these licenses, see the current
version of the VMS Release Notes.

6-1

After Installing VMS
6.2 Removing Unwanted Files with VMSTAILOR

6.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. 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 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 VMSTAILOR 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 Version 5.0 that affected the MAIL utility.

6.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 8 in this book. This chapter explains the different ways to
boot the system. It also tells you how to shut down the system.

If your processor 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
VAXcluster 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. Follow the directions in Chapter 3 to build the cluster.

6-2

After Installing VMS
6.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

6.4

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

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

6.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 9. 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.

6-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:

7 .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 7.2.
1

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

Note: Because the SYSTEST and SYSTEST_CLIG 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_UJC=[l,7].
(You can create this directory with the DCL command CREATE
/DIRECTORY.)

7-1

Running UETP
7 .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 7.3).
If you encounter any problems in preparing to run UETP, read Section 7.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 7.5.

If you want to run UETP without using the default responses, refer to
Sections 7.4 through 7.4.4, which explain the options.

7-2

Running UETP
7 .2 Logging In

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

7.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
"SYS$TEST" = 11 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 7.3.2 discusses setting up scratch disks for testing.

7. 3

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

Note: Your system may hot 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.

7-3

Running UETP
7.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.

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

7.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: TEST1

7-4

Running UETP
7 .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: TEST!

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 (VIC) of [1,7]. The directory must have a VIC 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.

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

7.3.4

Setting Up Tape Cartridge Drives
To set up tape cartridge drives that you want to 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.

7-5

Running UETP
7.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.

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

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

7.3.7

Preparing the DR11-W for UETP Testing
Note: Only DIGITAL Field Service personnel should set up the DRll-W for
UETP testing.
The DRl 1-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 DRll-W properly, the ElOS switchpack must be set as follows:
Switch 1

Switch 2

Switch 3

Switch 4

Switch 5

Off

Wheh UETP testing is completed, restore the DRl 1-W to the proper operating
configuration.

7-6

Running UETP
7.3 Setting Up for UETP

7.3.8

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

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

•

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

•

The DRV-11WA 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.

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

•

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.

7.3.10 Preparing the MA780 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.

7-7

Running UETP
7 .3 Setting Up for UETP

7 .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
LPAll-K should be LPA11$1.

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

7 .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 ~he 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.

7-8

Running UETP
7 .3 Setting Up for UETP

To set the password of the SYSTEST_CLIG account to the null password,
enter the following commands and press RETURN after each one:
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> MODIFY /NOPASSWORD SYSTEST_CLIG
UAF> EXIT
$

Note: DIGITAL 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.

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

7-9

Running UETP
7 .3 Setting Up for UETP

7 .3.15 Preparing DECnet
The DECnet phase of UETP uses more system resources than most. 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

7 .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 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 7.4.2 through 7.4.4. If you
want to run all the test phases, skip the next section.

7-10

Running UETP
7 .4 Starting UETP

7.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 7.4.2 and 7.4.4 discuss these questions. After you answer both
questions, the phase you have selected runs to completion.

7.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 l, 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 7.4.4). Make certain that all line printers and
hardcopy terminals have enough paper; each run requires two pages.

7-11

Running UETP
7.4 Starting UETP

7.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 specifyirtg 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 7.5.2.

7.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 7.5 for troubleshooting information.

7-12

Running UETP
7.4 Starting UETP

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

7-13

Running UETP
7.4 Starting UETP

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

7. 5

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

7.5.1

Relationship of U ETP 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:

7-14

•

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 I/ 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.

Running UETP
7 .5 Troubleshooting

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

7-15

Running UETP
7. 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 * CC
8704 +
323) I C
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 t]le
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.

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

7-16

Running UETP
7.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 SYS TEST 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

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

7-17

Running UETP
7. 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.

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

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

7-18

Running UETP
7~5

7.5.4.1

Troubleshooting

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
TMPMl3X
NETMBX
VOLPRO
PHLIO
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/0
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/0
may access objects via system protection

$ SHOW PROCESS/QUOTAS

31-DEC-1988 18:06:03.36

OPAO:

User: SYSTEST

7-19

Running UETP
7. 5 Troubleshooting

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

Direct I/O limit:
Buffereq 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

TQELM: 20

CPU: no limit

ENOLM: 300

PGFLQUOT A: 20480

WSDEFAULT: 256

WSQUOTA: 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.

7-20

98
0
0

Running UETP
7. 5 Troubleshooting

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

7-21

Running UETP
7. 5 Troubleshooting

Solution

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

7.5.4.3

•

Run the device test individually (see Section 7.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 npt 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 -c

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

* 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:

7-22

•

Delete unnecessary files to create more space.

•

Purge files, if multiple versions exist.

•

Mount a volume with sufficient space.

Running UETP
7.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 Chapter 6 for
more information.

See Sections 7.2.1 and 7.3.2 for a further discussion of disk space.
7.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:

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

* UETCLIGOOmaster *
* 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.

7-23

Running UETP
7 .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 7.3.13 and Section 7.5.2.1 for information on preparing
for VAXcluster testing.

7.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
se~up for the cluster test; refer to Section 7.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 7.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 UETLO*.LOG;*

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

7-24

Running UETP
7.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.

7.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 7.4.1) to determine whether
the error can be re-created.
Refer to the VMS System Messages and Recovery Procedures Reference

Volume.

7-25

Running UETP
7 .5 Troubleshooting

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

7.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, UETLOADOO 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, UETLOAD03_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, UETLOAD05_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, UETLOADOO 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:

7-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
7.5 Troubleshooting

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

•
7.5.4.10

I/O device failure causing driver-permanent loop-Call DIGITAL Field
Service.
·

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.

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

7-27

Running UETP
7.6 UETP Tests and Phases

7.6.1

Initialization Phase
The following occurs during the initialization phase:
•

The image UETINITOO.EXE prompts you for information (see Section 7.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.

7.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 phq.se and presents instructions for testing a single device. If you
want to run the entire device test phase individually, refer to Section 7.4.1.

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

7-28

Running UETP
7.6 UETP Tests and Phases

7.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 7-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 U ETI NI DEV. 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

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

7-29

Running UETP
7.6 UETP Tests and Phases

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

Ac
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 (LP A 11-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 LPAll-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 is correct, an AST routine
is associated with a $QIO read to compare the received message against the
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.

7-30

Running UETP
7.6 UETP Tests and Phases

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 7-1 lists the device test images and the devices to be tested.
Table 7-1

7.6.3

The Device Tests

Test Image Name

Devices Tested

UETDISKOO.EXE

Disks

UETT APEOO.EXE

Magnetic tape drives and tape cartridge drives

UETTTYSOO.EXE

Terminals and line printers

UETLPAKOO.EXE

LPA 11-K

UETCOMSOO. EXE

DMC 11 , DMR 11

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

7-31

Running UETP
7.6 UETP Tests and Phases

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 7.4.1).

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

7.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 minJ.Ites at
normal communications transfer rates.

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

7-32

Running UETP
7.6 UETP Tests and Phases

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

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:

7-33

Running UETP
7 .6 UETP Tests and Phases

For Circuits

•

Arriving congestion loss

•
•
•

Corruption loss

•
•
•
•
•
•
•

Initialization failure

•
•

Selection timeouts

•
•
•

Transit congestion loss
Line down

Data errors inbound
Data errors outbound
Remote reply timeouts
Local reply timeouts
Remote buffer errors
Local buffer errors

Remote process errors
Local process errors
Locally initiated resets
Network initiated resets

For Nodes

•
•
•
•
•
•
•

•
•

7-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
7.6 UETP Tests and Phases

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

7-35

Running UETP
7.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.

7-36

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

Startup and Shutdown Procedures

This chapter contains information on the following:

8.1

•

Overview of booting the system

•

Ways to boof the system

•

Shutting down the system

Overview of Booting
Booting is the process of loading system software into the processor's main
memory. The VAXstation 2000/MicroVAX 2000 uses an internal memory
device to boot the VMS operating system from the system disk into memory.
The boot process consists of the following steps:
1

You enter the BOOT command. The boot procedure deposits information
in the general purpose registers.

VMB, the primary boot program, is loaded from random access memory
(RAM) into main memory. VMB is a program that allows access to the
system disk. VMB 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.PAR 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, SYSBOOT 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.

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 you can log into the VMS operating
system.

8-1

Startup and Shutdown Procedures
8.2 Sniffer Boot

8.2

Sniffer Boot
A sniffer boot lets you to boot the system without specifying a device name.
To cause a sniffer boot, do the following:
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.

Press the HALT button.

Enter the following command and press RETURN:
>» B

The system successively tries boot devices until it finds one it can boot
from. The system searches in the following order for a device from which
it can boot:
•

Floppy diskette drives

•

Fixed disks

•

Tape cartridge drives

•

The network

If the system does not find any device from which to boot, it continues to try

to boot from the network indefinitely.
When the system boots automatically, it does a sniffer boot if you have not
specified a default boot device, or if you cleared the default boot device.

8.3

Automatic Boot
The VMS operating system can boot automatically from the disk designated
in non-volatile RAM. When you installed the system hardware, you
designated the default boot device. If you want to boot automatically from a
different device, you must change the designation in non-volatile RAM (see
Section 8.3.1).
You can set the system so it boots automatically from the default boot device
under the following conditions:

8-2

•

When you first turn on system power

•

When system power comes on after a power failure

•

After you shut down the system (if you entered Y at the auto reboot
prompt)

•

After a bugcheck

•

If the system halts under program control

Startup and Shutdown Procedures
8.3 Automatic Boot

To control whether the system boots automatically in these situations, do the
following:
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 the HALT button.

Type the following and press RETURN:
»> TEST 53

The system displays a prompt that indicates whether the system can
reboot automatically. For example:
2 ?

»>

In this case, the value has been set to 2. You can enter either of the
following values at this prompt or press RETURN to accept the current
value:
2-If the power comes on or the system halts under program control,
the system attempts to reboot from the default boot device designated
in RAM.
3-When power comes on to the system or the system halts under
program control, it displays the console-mode prompt(> > > ), and
does not attempt to reboot.

8.3.1

Changing the Default Boot Device
To change the default boot device, do the following:
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 the HALT button.

Type the following and press RETURN:
»> TEST 51

8-3

Startup and Shutdown Procedures
8.3 Automatic Boot

The system displays a prompt that indicates the current default boot
device. For example:
DUAO? >»

To change the default boot device, enter a new device name from those
listed in Table 8-1 and press RETURN. To clear the default boot device,
enter a period ( . ) and press RETURN.

Table 8-1

Default Boot Device Names

Device

Name

Fixed disk in system box

DUAO
DUA1
DUA2
MUAO
ESAO

Fixed disk in expansion box
Diskette drive
Tape cartridge drive
Network

8.4

Manual Boot
To boot the system manually, 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 the HALT button.

Enter the BOOT command in the following format and press RETURN:
I

»> B ddcu

Substitute the name of the system disk for ddcu. For an explanation of
device names, see Chapter 3.
For example, to boot from the fixed disk in the system box, enter the
following command and press RETURN:
>» B DUAO

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

The final message should look like the following:
SYSTEM

8-4

job terminated at 31-DEC-1988 15:14:32.13

Startup and Shutdown Procedures
8.5 Conversational Boot

8.5

Conversational Boot
A conversational boot is most commonly used in research and development
environments and during software upgrades. Perform a conversational boot
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:
•

Look at system parameter values

•

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

•

Specify a minimum startup

There are several ways to perform a conversational boot. The following
procedure is the most direct:
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 the HALT button.

To begin the conversational boot, enter the following command and press
RETURN:
»> B/1 [ddcu]

Substitute the device name of the system disk for ddcu. If you do not
specify a system disk, the system does a sniffer boot.
4

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

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

8-5

Startup and Shutdown Procedures
8.5 Conversational Boot

Table 8-2

SYSGEN Commands Used in SYSBOOT

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.

HELP

Displays a summary of the SYSBOOT
commands on the terminal screen.

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. The CONTINUE command completes the boot
process:
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 system
parameter values:
SYSBOOT> USE DEFAULT
SYSBOOT> CONTINUE

You can also use the conversational boot operation 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
and press RETURN:
SYSBOOT> SET STARTUP _Pl "MIN"

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

8-6

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

Installs known images

Startup and Shutdown Procedures
8.5 Conversational Boot

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.
The value of STARTUP_Pl is saved and affects future boot operations. After
the operating system boots, you can log into the SYSTEM account and 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 ""
SYSGEN> WRITE CURRENT
SYSGEN> EXIT

8.6

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

8. 7

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. An example of a hardware problem is a read error on a disk or
tape cartridge drive. If you suspect a hardware problem, do the following:
1

Consult the hardware manual for your VAX processor

Contact the appropriate DIGITAL Field Service representative

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:05:03.17

If the system does not display this message, a software problem has probably

occurred. Do the following:

8.8

Turn off the system box. Turn it back on and try to reboot.

Do a conversational boot using default SYSGEN parameters as described
in Section 8.5. If the system boots, run AUTOGEN. For more information
on AUTOGEN, see the Guide to Setting Up a VMS System.

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, see

Section 8.3.

8-7

Startup and Shutdown Procedures
8.8 Shutting Down the System

8.8.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 the HALT button
on the back of the system box.
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. To run the OPCCRASH program, log
into the SYSTEM account, enter the following command and press
RETURN:
$ RUN SYS$SYSTEM:OPCCRASH

To halt the system after the procedure completes, press the HALT button
on the back of the system box.
For more information about the OPCCRASH program, see the Guide to
Setting Up a VMS System.
•

8.8.2

An Emergency Shutdown with CRASH Commands Use this emergency
shutdown procedure if OPCCRASH fails. Section 8.8.2 describes using
CRASH commands.

Emergency Shutdown with CRASH Commands
Note: Use CRASH commands only if 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

Press the HALT button.

To examine processor registers, enter the following command and press
RETURN:
»> E/G/N:F 0

The system displays the contents of the registers. Write these values
down if you want to save information about the state of the system.
3

Enter the following commands and press RETURN:
>>>
>>>

D PC FFFFFFFF
D PSL 041FOOOO

By depositing these values, you cause the system to write a memory
dump to the system dump file on disk.

8-8

Startup and Shutdown Procedures
8.8 Shutting Down the System

Enter the following command and press RETURN:
>» CONTINUE

This causes the system to perform a bugcheck.
5

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.

8.9

If the System Fails
Your system can fail in the following ways:
•

Bugcheck-The system displays a bugcheck message on the console
terminal and shuts itself down. This happens because the system
encountered a problem that made further operation impossible. Reboot
the system.

•

Hang-The system stops responding to your commands. The problem
could be a failure in system software or a hardware component or a
power failure.

•

Erratic behavior-The system does not respond according to
specifications. The problem could be a failure in system software or a
hardware component.

To see if the failure is a system problem and not something you have done,
try the following:
•

Make sure that you did not press the Fl key (the NO SCROLL key on a
VTlOO series terminal) accidentally.

•

Press CTRL/T to check the status of your process. A status line should
appear, indicating the name of the program that is executing and other
information. If the status line does not appear, the program you are
executing might be hung. (If you have disabled CTRL/T by entering the
command SET NOCONTROL=T or have set the terminal to nobroadcast
mode by entering the command SET TERMINAL/NOBROADCAST, this
procedure does not work.)

•

Make sure the cable connecting the terminal or monitor to the system box
is secure.

Usually you can force an exit from a hung program by pressing CTRL/Y.
When you press CTRL/Y, any work performed by the program and not saved
on disk is lost.
If the system is hung, press the HALT button and reboot without a normal
shutdown.
If you have a problem with the system that DIGITAL has not warned you
about, note in detail the sequence of events that caused the problem and
notify your DIGITAL Field Service representative.

8-9

Backup Procedures

This chapter describes the following procedures:

9.1

•

Installing and booting standalone BACKUP on the system disk

•

Installing and booting standalone BACKUP on a diskette

•

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, a
diskette, or any other media that the system supports. DIGITAL recommends
that you keep standalone BACKUP on your system disk and on a tape
cartridge or diskette. Usually you boot standalone BACKUP from the system
disk because it saves time. However, you need to keep a copy of standalone
BACKUP on tape cartridge or diskette in case the system disk becomes
damaged. As part of your distribution kit, you received standalone BACKUP
on either a tape cartridge or a diskette.

9.1.1

Installing Standalone BACKUP on the System Disk
You can install standalone BACKUP in any available root directory on the
system disk from [SYSl] 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.

9-1

Backup Procedures
9.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.

9.1.2

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

Booting Standalone BACKUP from the System Disk
To boot standalone BACKUP from the system disk, 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

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 the HALT button.

Enter the BOOT command in the following format:
>>> B/EOOOOOOO ddcu

Substitute the device name of the system disk for ddcu. The device name
of the system disk is either DUAO or DUAl, depending on whether your
system disk is in the system box, or an expansion box. If you do not
specify the device name of the system disk, the system does a sniffer
boot.

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 DUAO:
Available device MUAO:

device type Generic_DU
device type TK50

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, Standalone BACKUP V5.0; the date is 31-DEC-1988 15:00
$

9-2

Backup Procedures
9.1 Overview of Standalone BACKUP

To make a backup copy of the system disk, go to Section 9.2. To restore the
system disk go to either Section 9.2.4 or Section 9.2.2.

9.1.3

Installing Standalone BACKUP on a Diskette
If your configuration includes a diskette drive, DIGITAL recommends that

you keep standalone BACKUP on a diskette in case the system disk becomes
damaged. To install standalone BACKUP on an RX33 diskette, use the
following procedure:

Note: If you have a diskette distribution kit, you should already have
standalone BACKUP on a diskette. If the original diskette becomes
damaged or if you need to make extra f:Opies, use the procedure in this
section.
1

Obtain one blank RX33 diskette. Write the name S/A BKUP VS.O on the
paper label. Affix the paper label to the diskette.

Log into the SYSTEM account.

Insert the diskette labeled S/A BKUP VS.O in the diskette drive.

Note: If you inserted the diskette into the drive upside down, or if it is
improperly aligned, you may receive the following error message:
%MOUNT-F-MEDOFL, medium is offline

. If you receive this error message, remove the dis.l<ette from the drive and

reinsert it.
5

Tl~e procedure asks for the name of the target device.

Type DUA2 and

press RETURN. For example:
%STABACKIT-I-SYMDEL, all global symbols deleted
Enter the name of the device on which to build the Kit: DUA2

The procedure displays the following message. Type Y (for YES) to
initialize the diskette. For example:
Do you want to initialize _DUA2:?
Note that this will erase all files currently on the volume.
It is not necessary to initialize the disk, and you would not want to
initialize if you want to aqd a kit to an existing Files-11 disk. The
disk must be a valid Files-11 disk if you wish to skip initializing, however.
[Do you want to initialize [Yes/No, default No]:

The procedure displays verification messages informing you that files are
being copied. When the procedure finishes, it displays Cl message similar
to the following:
Ending time
31-DEC-19~8 13:4q:29.90
Starting time 31~DEC-1988 13:22:39.05
The Kit is complete.
$

Remove the diskette labeled S/A BKUP VS.O from the diskette drive.

Write-protect the diskette and store it in a safe place.

9-3

Backup Procedures
9.1 Overview of Standalone BACKUP

9.1.4

Booting Standalone BACKUP from a Diskette
If the system disk containing standalone BACKUP should become unusable,
you can boot standalone BACKUP from an RX33 diskette. You need an RX33
disket~e that contains standalone BACKUP (either the distribution diskette or
one that you created). To boot standalone BACKUP from diskettes, 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.

Press the HALT button.

Insert the standalone BACKUP diskette into the diskette drive (DUA2).

Enter the following command and press RETURN:
»> B DUA2

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 DUAO:
Available device DUA2:

device type Generic_DU
device type RX33

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 15:00
$

Remove the standalone BACKUP diskette from the diskette drive.

To make a backup copy of the system disk, go to Section 9.2.
To restore the system disk go to either Section 9.2.4 or Section 9.2.2.

9-4

Backup Procedures
9.1 Overview of Standalone BACKUP

9.1.5

Installing Standalone BACKUP on a Tape Cartridge
If your system has a tape cartridge drive, 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.

Write-enable the tape cartridge.

Insert the tape cartridge labeled S/A BKUP VS.O into the drive.

Log into the SYSTEM account.

The procedure asks you for the name of the target device. Type MUAO
and press RETURN. For example:
Enter the name of the device on which to build the kit: MUAO

The procedure displays the following message:

Please place the scratch tape cartridge in drive _MUAO:
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.

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

11 Remove the tape cartridge labeled S/A BKUP VS.O from the tape cartridge
drive.

12 Write-protect the tape cartridge and store it in a safe place.

9-5

Backup Procedures
9.1 Overview of Standalone BACKUP

9.1.6

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

Press the HALT button.

Insert the tape cartridge that contains standalone BACKUP into the tape
cartridge drive.

To boot standalone BACKUP, enter the following command at the
console-mode prompt(> > > ) and press RETURN:
>» B MUAO

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
yot1 have them, HSC and MSCP-served devices. For example:
Available device DUAO:
Available device MUAO:

device type Generic_DU
device type TK50

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 15:50
$

Remove the tape cartridge containing standalone BACKUP from the tape
cartridge drive.
To make a backup copy of the system disk, go to Section 9.2.
To restore the system disk go to either Section 9.2.4 or Section 9.2.2.

9-6

Backup Procedures
9.2 Backing Up the System Disk

9.2

Backing Up the System Disk
There are several reasons to back up a system disk:
•

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 does occur,
you can restore the backup copy to 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 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. Back up the system disk to a tape
cartridge, diskettes, or another disk. Then restore the files to the original
system disk.The BACKUP command creates a copy on which files are
stored contiguously.

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.

9.2.1

Backing Up the System Disk to Diskettes
To back up the system disk to diskettes, use the following procedure:
1

Boot standalone BACKUP as described in Sections 9.1.2~ 9.1.4, or 9.1.6.

Determine the device name of the system disk you are backing up.
•

DUAO-disk in the system box

•

DUAl-disk in the expansion box

Note: You use at least 25 diskettes to back up the system disk. Label the
diskettes in sequence. The procedure asks you for each diskette until
the operation is complete.
3

Write-enable a scratch diskette. To write-enable a diskette, remove the
foil adhesive tab covering the write-protect notch.

9-7

Backup Procedures
9.2 Backing Up the System Disk

Insert the diskette in the diskette drive.

Enter the BACKUP command in the following format and press RETURN:
$ BACKUP/IMAGE/VERIFY source-drive: DUA2:saveset.BCK/SAVE_SET

where:

•

source-drive: is the location of the files you want to back up. Use the
device name of the system disk, either DUAO (the disk in the system
box) or DUAl (the disk in the expansion box).

•

saveset.BCK is the name of the save set (the name should reflect the
contents of the backup diskette and cannot exceed 17 characters.)

For example:
$ BACKUP/IMAGE/VERIFY DUAO: DUA2:DEC_31_BACKUP.BCK/SAVE_SET

The procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

The procedure displays the following messages:
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYREAD, Mount volume 2 on DUA2: for writing
Enter "YES" when ready.

a. Remove the backup diskette from the drive.
b. Label the diskette COMPLETE SYSTEM BACKUP, number it, and
include the date.

c. Write-protect the backup diskette.
d. Write-enable another scratch diskette, and insert it in the drive.

e. When you are ready to continue, Type Y (for YES) and press
RETURN.
f.

The procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

Each time the procedure displays a mount request, follow steps a
through e.
8

When the procedure is finished, it displays the following message:
%BACKUP-I-PROCDONE, Operation completed. Processing finished at 31-DEC-1988 15:30
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 last backup diskette from the drive. Label the diskette
COMPLETE SYSTEM BACKUP, number it, and include the date.

10 Write-protect the diskette.
11 Press the HALT button.

1 2 Reboot the system disk.

9-8

Backup Procedures
9.2 Backing Up the System Disk

Store the backup diskettes in a safe place.
Note: The BACKUP command creates a system disk that includes a DIGITALprovided 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.

9.2.2

Restoring the System Disk from Diskettes
To restore the system disk from diskettes, use the following procedure:
1

Boot standalone BACKUP as described in Sections 9.1.2, 9.1.4, or 9.1.6.

Determine the device name of the system disk which you are restoring.
•

DUAO-disk in the system box

•

DUAl-disk in the expansion box

Insert the first backup diskette in the diskette drive.

Enter the BACKUP command in the following format and press RETURN:
$ BACKUP/IMAGE/VERIFY DUA2:save set.BCK/SAVE_SET target-drive:

where:

•

saveset.BCK is the name of the save set.

•

target-drive: is the device name of the system disk which you are
restoring, either DUAO (the disk in the system box) or DUAl (the
disk in the expansion box).

For example:
$ BACKUP/IMAGE/VERIFY DUA2:DEC_31_BACKUP.BCK/SAVE_SET DUAO:

The procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

The procedure displays the following messages:
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYREAD, Mount volume 2 on DUA2: for reading
Enter "YES" when ready.

a. Remove the backup diskette from the drive.
b. Make sure the next backup diskette is write-protected and insert it in
the drive.

c. When you are ready to continue, type Y (for YES) and press
RETURN.

9-9

Backup Procedures
9.2 Backing Up the System Disk

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

When the procedure is finished, it displays the following message:
%BACKUP-I-PRDCDONE, 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 last backup diskette from the diskette drive.

Press the HALT button.

10 Reboot the system.
Store the backup diskettes in a safe place.

9.2.3

Backing Up the System Disk to Tape Cartridges
To back up the system disk to tape cartridges, use the following procedure:
1

Obtain a scratch tape cartridge that you can use for the backup copy.

Write-enable the tape cartridge. To write-enable a tape cartridge, slide the
write-protect switch away from the tape cartridge label.

Insert the tape cartridge in the tape cartridge drive.

Boot standalone BACKUP as described in either Section 9.1.2,
Section 9.1.4, or Section 9.1.6.

Determine the device name of the system disk you are backing up.

•

DUAO-disk in the system box

•

DUAl-disk in the expansion box

Enter the BACKUP command in the following format:

$ BACKUP/IMAGE/VERIFY/BUFFER=5 source-drive: MUAO:saveset.BCK/REWIND/LABEL=volume-label

where:

9-10

•

source-drive: is the location of the files you want to back up. Use the
device name of the system disk, either DUAO (the disk in the system
box) or DUAl (the disk in the expansion box).

•

saveset.BCK is the name of the save set (the name should reflect
the contents of the backup tape and cannot exceed 17 characters in
length).

•

volume-label is the volume label of the tape cartridge in the drive. If
the tape has been initialized already, 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.

Backup Procedures
9.2 Backing Up the System Disk

For example:
$

BACKUP/IMAGE/VERIFY/BUFFER=5 DUA1: MUAO:DEC_31_BACKUP.BCK/REWIND/LABEL=BACKUP

The procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

If your system disk contains more data than the tape cartridge can store,
the procedure displays the following messages and prompt:
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYWRITE, Mount volume 2 on _MUAO: for writing
Enter "YES" when ready.

If you do not receive these messages, go to step 9.

a. Remove the backup tape cartridge from the drive.
b. Label it COMPLETE SYSTEM BACKUP, number it, and include the

date.

c. Write-protect the tape cartridge.
d. Write-enable another scratch tape cartridge and insert it in the drive.
e. When you are ready to continue, type Y (for YES) and press

RETURN.
f.

The procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

Each time the procedure displays a mount request, follow steps a
through e.

ensure the standalone application volume is online and ready.
Enter "YES" to continue:

10 Remove the backup tape cartridge from the drive. Label the tape cartridge
COMPLETE SYSTEM BACKUP, number it (if you used more than one
tape), and include the date.
11 Write-protect the tape cartridge.

1 2 Press the HALT button.
1 3 Reboot the system.
Store the backup tape cartridge in a safe place.

Note: The BACKUP command creates a system disk that includes a DIGITALprovided 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 V AXclusters.) 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,
9-11

Backup Procedures
9.2 Backing Up the System Disk

see the Guide to Maintaining a VMS System. For more information on the
BACKUP command, see the VMS Backup Utility Manual.

9.2.4

Restoring the System Disk from Tape Cartridges
To restore the system disk from tape cartridges, use the following procedure:
1

Boot standalone BACKUP as described in Sections 9.1.2, 9.1.4, or 9.1.6.

Determine the device name of the system disk you want to restore.
•

DUAO-disk in the system box

•

DUAl-disk in the expansion box

Insert the first tape cartridge containing the backup of the complete
system disk in the tape drive. Make sure the tape cartridge is writeprotected.

Enter the BACKUP command in the following format and press RETURN:
$ BACKUP/IMAGE/VERIFY/BUFFER=5 MUAO:saveset.BCK/REWIND target-drive:

where:

•

saveset.BCK is the name of the save set.

•

target-drive: is the device name of the system disk which you are
restoring, either DUAO (the disk in the system box) or DUAl (the
disk in the expansion box).

For example:
$ BACKUP/IMAGE/VERIFY/BUFFER=5 MUAO:DEC_31_BACKUP.BCK/REWIND DUAO:

The procedure displays the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

6 If your system disk contained more data than one tape cartridge could
store, you receive the following messages and prompt:
%BACKUP-I-RESUME, Resuming operation on volume 2
%BACKUP-I-READYREAD, Mount volume 2 on MUAO: for reading
Enter "YES" when ready.

If you do not receive these messages, go to step 7.

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.

9-12

Backup Procedures
9.2 Backing Up the System Disk

Remove the last backup tape cartridge from the drive.

Press the HALT button.

10 Reboot the system.
Store the backup tape cartridge(s) in a safe place.

9-13

Configuring Devices

This appendix describes how to prevent the VAXstation 2000 /Micro VAX 2000
from automatically configuring the devices in your system. It also describes
how to use the CONNECT command to configure the devices in your system
manually.

Note: DIGIT AL recommends that you let SYSGEN automatically configure the
devices in your system.
The MicroVAX 2000 /VAXstation 2000 automatically configures the devices
attached to the system when you boot the system. This configuration is a
static determination that can only be performed when the system boots. For
example, if you leave an expansion box unplugged when the system boots,
you cannot use the SYSGEN AUTOCONFIGURE command to configure the
expansion box once the system has booted.
To configure devices that were turned off or unplugged when the system
booted, reboot the system or manually configure the devices. Before you
can configure the devices in your system manually, you must prevent
autoconfiguration using the instructions in Section A.1.

A.1

Preventing Autoconfiguration
Although DIGITAL recommends that you let the command procedure
SYS$SYSTEM:STARTUP.COM start SYSGEN and configure the devices
in your system, you can prevent a device from being configured.
The command procedure STARTUP.COM contains the SYSGEN command
AUTOCONFIGURE ALL. This command uses the information in Table A-1
to configure the devices in your system. To prevent a device from being
configured, you must set the SYSGEN parameter NOAUTOCONFIG to 1 as
follows:
1

Log in to the system manager's account (SYSTEM). If the system manager
menu is available, select option 1 to exit to DCL.

Enter the following command at the DCL prompt and press RETURN:
$ RUN SYS$SYSTEM:SYSGEN

Enter the following commands at the SYSGEN> prompt. Press RETURN
after each one:
SYSGEN> USE CURRENT
SYSGEN> SHOW NOAUTOCONFIG

SYSGEN displays the following information:
Parameter Name
NOAUTOCDNFIG

Current

Default

Minimum

Maximum

Unit

Dynamic

Boolean

A-1

Configuring Devices
A.1 Preventing Autoconfiguration

Enter the following commands at the SYSGEN> prompt. Press return
after each one:
SYSGEN> SET NOAUTOCONFIG 1
SYSGEN> SHOW NOAUTOCONFIG

SYSGEN displays the following information:
Parameter Name

Current

Default

Minimum

Maximum

NOAUTOCONFIG

Unit

Dynamic

Boolean

Enter the following command at the SYSGEN> prompt and press
RETURN:
SYSGEN> WRITE CURRENT

Reboot the system.

If you choose to prevent autoconfiguration, you should make sure that the
base asynchronous serial ports are always autoconfigured. Enter the following
command at the SYSGEN> prompt and press RETURN:
SYSGEN> AUTOCONFIGURE ALL/SELECT=TT:

Or you may enter the following command, making sure that you do not
include "TT" in the list of device names:
SYSGEN> AUTOCONFIGURE ALL/EXCLUDE=(device-name[, ... ])

To configure the devices in your system manually, proceed to Section A.2.

A.2

Using the CONNECT Command
CAUTION: Use the CONNECT command with extreme caution. An incorrect
command can cause the system to fail. Note that the "0" following
the percent sign ( %) in the /VECT argument is a capital letter 0
(abbreviation for octal), rather than a zero.
You can use the CONNECT command to configure devices manually after
your system boots. Table A-1 shows the appropriate csr_addr values for
the command's /CSR qualifier. These csr_addr values are offsets from the
beginning of VAXstation 2000/MicroVAX 2000 1/0 space, rather than the bus
address value that you would specify for a UNIBUS device.
Table A-1

VAXstation 2000/MicroVAX 2000 Autoconfiguration Table

Device

Name

Driver

CSR
(Offset)

Standard Serial Lines

YEDRIVER

AX0800

A0774

No. of
Vectors

First
Vector

Vector Offset

A0300

ST506 Disk Controller

DVDRIVER

Axocoo

TK50 Tape Controller

TVDRIVER

AXOC80

Aono

Ethernet Controller

ESDRIVER

AX4EOO

A0120

Black & White Video
Option

VEDRIVER

AX5000

A0104

A-2

Configuring Devices
A.2 Using the CONNECT Command

The following are examples of CONNECT commands for VAXstation
2000 /Micro VAX 2000 devices:
SYSGEN> CONNECT ESAO /ADAP=O /CSR=%X4EOO /VECT=%0120 /NUMV=01 /DRIVER=ESDRIVER
SYSGEN> CONNECT MUAO /ADAP=O /CSR=%XOC80 /VECT=%0770 /NUMV=01 /DRIVER=TVDRIVER
SYSGEN> CONNECT DUAO /ADAP=O /CSR=%XOCOO /VECT=%0774 /NUMV=01 /DRIVER=DVDRIVER
SYSGEN> CONNECT DUA1 /ADAP=O /CSR=%XOCOO /VECT=%0774 /NUMV=01 /DRIVER=DVDRIVER
SYSGEN> CONNECT DUA2 /ADAP=O /CSR=Y.xocoo /VECT=%0774 /NUMV=01 /DRIVER=DVDRIVER
SYSGEN> CONNECT VCAO /ADAP=O /CSR=%X5000 /VECT=%0104 /NUMV=01 /DRIVER=VEDRIVER

To exit from SYSGEN, enter the following command at the SYSGEN>
prompt and pres~ RETURN:
SYSGEN> EXIT

A-3

VAXstation 2000/MicroVAX 2000 1/0 Space

This appendix contains information about the physical addresses in the
VAXstation 2000/MicroVAX 2000 I/O space.
Table B-1 lists the physical addresses in VAXstation 2000 /Micro VAX 2000
I/O space where existing and configured components can be found. The
VAXstation 2000/MicroVAX 2000 initialization procedures map various
regions of this address space. All values in Table B-1 appear in hexadecimal
radix.
VMS defines symbols for VAXstation 2000 /MicroVAX 2000 physical
addresses in the macro $1041 ODEF and for the respective offsets from the
virtual address contained in EXE$GL_CPUNODSP in the macro $KA410DEF.
Both macros reside in SYS$LIBRARY:LIB.MLB.
When using the offsets defined by the $KA41 ODEF macro in system code,
you must first obtain the starting address of nodespace and use the symbolic
offsets as displacements from that address. The following example illustrates
this technique:
MOVL
MOVB

Table B-1

G~EXE$GL_CPUNODSP,RO

KA410$B_INTMSK(RO),R1

;Get starting address of nodespace
;Get interrupt mask register

VAXstation 2000/MicroVAX 2000 Address Map

Physical Reference
Physical Address
Symbol

Contents
Description

Virtual Reference
Symbol

System Board Addresses
00000000~001FFFFF

System board
RAM

00200000~00FFFFFF

Memory option
board RAM

20020000

10410$AB_CFGTST

20040000~2007FFFF

20040004

Configuration and
test register (on
read)
1/0 reset register
(on write)

KA4 10$B_CFGTST

System board
ROM
10410$AL _SIDEX

20040020~2004003F

System ID
extension register

KA410$L_SIDEX

Interrupt vector
numbers

20080000

10410$AL _HL TCOD

Halt code register

KA410$L _HLTCOD

20080004

10410$AL _MSER

Memory system
error register

KA410$L _MSER

B-1

VAXstation 2000/MicroVAX 2000 1/0 Space

Table B-1 (Cont.)

VAXstation 2000/MicroVAX 2000 Address Map

Physical Reference
Physical Address
Symbol

Contents
Description

Virtual Reference
Symbol

System Board Addresses
20080008

10410$AL _MEAR

Memory error
address register

KA410$L _MEAR

2008000C

10410$AB_INTMSK

Interrupt mask
register

KA410$B_INTMSK

20080000

10410$AB_VDCORG

Monochrome
display origin

KA410$B_VDCORG

2008000E

10410$AB_VDCSEL

Video interrupt
select

KA410$8_ VDCSEL

2008000F

10410$AB_INTREQ

Interrupt request
register (on read)
Interrupt request
clear (on read)

KA410$B_INTREQ

10410$AB_INTCLR

KA410$B_INTCLR

20090000~2009007F

10410$AB_NIADRS

Network address
ROM

KA410$B_NIADRS

200A0000~200AOOOF

10410$AW_
SERCSR

Serial line
controller

KA410$W _SERCSR

200B0000~200BOOFF

10410$AL _ TODSEC

Time-of-year
clock and nonvolatile RAM

KA410$L_TQDSEC

2oocoooo~2oocooo1

104 10$AB_DKCREG

Disk controller
ports

KA410$B_DKCREG

200C0080~200C009F

10410$AB_SCTLS

TK50 controller
chip

KA410$B_SCTLS

200COOAO

10410$AB_SCDADR

TK50 OMA
address register

KA410$B_SCDADR

200COOCO

10410$AW_
SCDCNT

TK50 OMA byte
count register

KA410$W_SCDCNT

200COOC4

10410$AB_SCDDIR

TK50 OMA
transfer direction

KA410$B_SCDDIR

200D0000~20003FFF

10410$AB_DKBUFS

Disk/tape data
buffer RAM

KA410$B_DKBUFS

200F0000~200F003F

10410$A W _ VCCMD

Monochrome
video cursor chip

KA410$W _ VCCMD

30000000~3001FFFF

10410$AB_VMEMS

Monochrome
video RAM

B-2

VAXstation 2000/MicroVAX 2000 1/0 Space

Table B-1 (Cont.)

VAXstation 2000/MicroVAX 2000 Address Map

Physical Reference
Physical Address
Symbol

Contents
Description

Virtual Reference
Symbol

Option Board Addresses
200E0000~200EFFFF

10410$AW _NIRDP

Network option,
signal NIENA

KA410$W _NIRDP

22000000~23FFFFFF

10410$AB_PCCSR

Future option
CS Rs

KA410$B_PCCSR

24000000~25FFFFFF

10410$AB_XCSR

Future option
CS Rs

KA410$B_XCSR

20100000~2013FFFF

10410$AB_NIROMS

Network option
ROM

KA410$B_NIROMS

20140000~2017FFFF

10410$AB_
VD ROMS

Video option
ROM

KA410$8_ VDROMS

20180000~201BFFFF

10410$AB_PCROMS

Additional option
1 ROM

KA410$B_PCROMS

201C0000~201FFFFF

10410$AB_XROMS

Additional option
2 ROM

KA4 10$B_XROMS

38000000~3BFFFFFF

10410$AB_VDCSR 1

Video option
(32-bit path)

KA410$B_VDCSR1

3C000000~3COOFFFF

10410$AB_VDCSR2

Video option
( 16-bit path)

KA410$B_VDCSR2

Ethernet Network Option Board Addresses
200E0000~200E0007

10410$AW_NIRDP

DESV A registers

KA410$W_NIRDP

20100000~2011FFFF

10410$AB_NIROMS

Firmware ROM

KA410$B_NIROMS

B-3

VAXstation 2000/MicroVAX 2000 Disk Driver

The VAXstation 2000 /Micro VAX 2000 disk driver provides a certain amount
of DIGITAL Storage Architecture (DSA) disk operation. In particular, the
driver supports block revectoring and bad block replacement. These functions
provide the system with a logically perfect disk medium.
Like other DSA disks, if a serious error occurs during a replacement operation,
the disk becomes write protected to prevent further changes. This is done to
preserve data integrity and minimize damage that could be caused by failing
hardware. Unlike other DSA disks, there is no visible indication on the drive
itself that it is write-protected.
You can tell that the disk is write-protected by the following indications:
•

ERRFMT messages

•

The disk enters mount verification and hangs

•

DCL command SHOW DEVICE output indicates that the disk is writelocked

•

Error messages from programs and utilities attempt to write to the disk

If the disk becomes write protected, use the following procedure:

Shut down the system.

Use standalone BACKUP to create a full backup of the disk.

Format the disk with the disk formatter.

Restore the disk from the backup using standalone BACKUP. Note that
any files with sectors flagged with a forced error may be corrupted and
need to be restored from a previous backup.

If errors ocurring during replacement operations becomes a chronic condition,
call DIGITAL Field Service.

C-1

Glossary

boot or bootstrap: The process of loading system software into a processor's main
memory. This guide uses the term boot to refer to this process.
boot server: A 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. A VAXstation 2000/MicroVAX 2000 cannot be part of a CI-only
VAXcluster.
console mode: In console mode, you control the system by entering console-mode
commands. In console mode, the VMS operating system is not running.
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.
local area VAXcluster: Consists of a VAX computer that acts as a boot server 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 server
and satellite node.
local drive: Any drive that is connected directly to a computer is referred to as a local
drive.
media: A generic term that refers to any packaging agent capable of storing computer
software. Examples of media are magnetic tapes, diskettes, disk packs, compact
disks (CDROM), 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 CPU is running and 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 mode.
satellite node: A computer that is part of a local area VAXcluster. A satellite node is
booted remotely from the system disk of the boot server in the local area VAXcluster.
See also boot server.
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.
standalone BACKUP: A version of the BACKUP utility that is booted into memory. It
runs without the control of the VMS operating system.
Glossary-1

Glossary

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
computers. In addition, each computer has its own directory on the system disk that
contains its page, swap, and dump files.
VAXcluster environment: A computer system consisting of a number of highly
integrated VAX computers. There are three types of VAXcluster environments:
Cl-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.
VMSTAl LOR: A software program that lets you remove files from or add files to your
system disk.

Glossary-2

Index
Console terminal (cont'd.)

A
Access slot
on the diskette drive• 2-1 7
Activity light
on the diskette drive• 2-17
Address space • B-1
ALLOCLASS parameter• 3-3
ANALYZE/CRASH command• 8-9
AUTOGEN
function during installation• 4-9, 5-10

B
BACKUP
See Backup Utility
BACKUP command• 9-7
/IMAGE qualifier• 9-7
/PHYSICAL qualifier• 9-7
Backup Utility (BACKUP)• 9-1
Bugcheck • 8-9
Bugcheck message
during UETP• 7-27

c
Cartridge-release handle
on the tape cartridge drive• 2-10
Cluster group number
rules for creating • 3-3
Cluster password
rules for creating• 3-3
CLUSTER_SIZE attribute• 9-9, 9-11
CONNECT command• A-2
Console mode• 2-4
Console report during UETP • 7-28
choosing format of• 7-12
error messages•7-12, 7-14
Console terminal
See also diagnostic console terminal
console mode• 2-4
default setting• 4-2, 5-2

description• 2-3
program mode• 2-3
CONTINUE command• 8-5
Controller designation
definition• 3-1
CRASH commands• 8-8
CTRL/T•8-9
CTRLNAME•7-7, 7-29

D
DECnet node address• 3-2
DECnet node name• 3-2
DECnet-VAX
error message during UETP • 7-25
preparing for UETP • 7-10
registering the license• 6-1
UETP test of• 7-32
UETP test phase• 7-32
Device code
definition• 3-1
Device name
controller designation• 3-1
device code • 3-1
of the diskette drive• 2-16
of the tape cartridge drive• 2-11
syntax• 3-1
unit number• 3...., 1
Device test
running individually• 7-29
Diagnostic console terminal• 2-5
disconnecting• 2-6
Diagnostics
relationship to UETP • 7-14
Disk
See System disk, User disk
Diskette
description of• 2-17
differences between RX33 and RX50 • 2-17
dismounting• 2-23
initializing• 2-22
inserting into drive• 2-18
label•2-18
mounting• 2-22
removing from drive• 2-23

lndex-1

Index

Diskette (cont'd.)
write protecting• 2-18
write-protect notch• 2-18
write-protect tab• 2-18
Diskette drive
access slot • 2-1 7
activity light• 2-17
description of• 2-16
device name of• 2-16
lever• 2-17
Distribution kit
~pecartridge•4-1,5-1

Distribution media
definition• 3-1
DR11-W
preparing for UETP • 7-6
DR11-WA
preparing for UETP• 7-7
DR750
preparing for UETP•7-7
DR780
preparing for UETP • 7-7

E
Error during UETP
diagnosing• 7-14
sources of• 7-15
Error Log Utility
relationship to UETP•7-2, 7-14, 7-26
Ethernet
defining a remote node for UETP • 7-16
preparing for UETP • 7-6
Expansion box• 2-23

F
Fixed disk
RD32•2-23
RD53•2-23
storage capacity of• 2-23

Hang
See System hang
Hardware problem
diagnosing• 8-7

I
1/0 space• B-1
/IMAGE qualifier• 9-7
Installation procedure
definition • 1-1
preparing a new system • 5-1
stages of•4-1, 5-1

L
Lever
on the diskette drive• 2-17
License registration
for system integrated products• 6-1
for VMS•6-1
Line printer
preparing for UETP • 7-2, 7-4, 7-6
UETP output• 7-30
UETP~~image•7-31

UETP test of• 7-28
LOADS•7-31
Load test
defining user load for UETP • 7-12
description • 7-12, 7-3 1
error during UETP • 7-24
running individually• 7-11
LOAD/UNLOAD button
on the tape cartridge drive• 2-10
Log file generated by UETP
See also UETP.LOG
duringthe~adtest•7-24

NETSERVER.LOG • 7-23
OLDUETP. LOG• 7-17
Logical name used by UETP
CTRLNAME. 7-7 7-29
LOADS• 7-31
MODE•7-15
SYS$1NPUT • 7-28
SYS$0UTPUT • 7-30
SYS$TEST • 7-3, 7-9, 7-17
UETP$NODE_ADDRESS•7-10
I

H
Halt button
location• 2-2

lndex-2

Index

Long report format
See Console report during UETP
LPA 11-K
preparing for UETP • 7-8

M
MA780
preparing for UETP • 7-7
Magnetic tape
preparingforUETP•7-2,7-3,7-5
test of• 7-28, 7-30
UETPte~image•7-31

Mandatory update
definition• 1-2
Master command procedure
See UETP. COM
MicroVAX 2000
serial lines• 2-7
MODE•7-15, 7-36

N
No PCB or swap slots error message• 7-26

0
ON/OFF switch
location• 2-1
OPCCRASH. EXE• 8-8
Output during UETP
See also UETP. LOG
console report•7-12, 7-28
interpreting• 7-15
terminal and line printer• 7-30

p
Phase controller for UETP
See UETPHASOO.EXE
/PHYSICAL qualifier• 9-7
Privilege
required for UETP • 7-20

Program mode• 2-3

a
Quota
required for UETP • 7-20

R
RD32 fixed disk
See fixed disk
RD53 fixed disk
See fixed disk
RMS Journaling
registering the license• 6-1
RX33 diskette
See Diskette
RX33 diskette drive
See Diskette drive

s
Saveset. BCK
definition•9-8, 9-9, 9-10, 9-12
SDA
See System Dump Analyzer
Short report format
See Console report during UETP
SHOW CRASH command• 8-9
SHUTDOWN.COM• 8-8
Source-drive
definition• 9-8, 9-1 O
STABACKIT.COM•9-1, 9-3, 9-5
Standalone BACKUP
definition• 9-1
function during installation• 4-3, 5-3
relation to Backup Utility• 9-1
SYS$1NPUT • 7-28
SYS$0UTPUT•7-30
SYS$TEST•7-3,7-9, 7-17
SYSBOOT .EXE• 8-1, 8-5
commands• 8-5
SYSGEN
See System Generation Utility

lndex-3

Index

System
logging into for UETP • 7-1 , 7-3
resource requirements for UETP • 7-1 , 7-3
System disk
checking amount of free space on• 6-3
definition • 3-1
designating as default boot device• 8-3
guidelines for choosing• 3-2
reasons for backing up• 9-7
space requirements for UETP • 7-4
test error during UETP • 7-21, 7-22
UETP test image• 7-31
UETP test of• 7-30
using VMST AILOR to customize• 6-2
System Dump Analyzer (SDA) • 8-9
System Generation Utility (SYSGEN) • A-1
ALLOCLASS parameter• 3-3
commands for conversational boot• 8-5
System hang•7-18, 7-27, 8-9
SYSTEST account
logging into for UETP • 7-1 , 7-3
privileges required for UETP • 7-20
quotas required for UETP • 7-20
SYSTEST directory
creating for UETP • 7-5
function during UETP • 7-3
SYSTEST_CLIG account
reenabling for UETP • 7-8
requirements for UETP • 7-8, 7-35

T
Tailored system disk
See VMST AILOR
Tape cartridge
description of• 2-11
dismounting• 2-16
initializing• 2-15
inserting• 2-13
label slot• 2-12
mounting • 2-15
removing• 2-16
write-protecting• 2-12
write-protect switch• 2-12
Tape cartridge distribution kit
contents of• 4-1, 5-1
Tape cartridge drive
description of• 2-9
device name of• 2-9

lndex-4

Tape cartridge drive (cont'd.)
indicator light• 2-9
LOAD/UNLOAD button• 2-10
preparing for UETP • 7-5
summary of controls• 2-10
summary of indicator lights• 2-10
Target-drive
definition•4-4, 5-4, 9-9, 9-12
Terminal
preparing for UETP • 7-2, 7-4, 7-6, 7-11
simulating users for UETP • 7-31
test of• 7-28
UETP output• 7-30
UETPteMimage•7-31
UETP test of• 7-30
TK50 tape cartridge
See tape cartridge
TK50 tape cartridge drive
See tape cartridge drive

u
UETCONTOO.DAT • 7-28
UETDISKOO
error message• 7-22
UETDNETOO.DAT• 7-32
UETINIDEV.DAT•7-28, 7-29
format• 7-29
UETININET.DAT•7-32, 7-33
UETINITOO.EXE•7-Hi, 7-28
UETINIT01
error message• 7-21
UETINIT01.EXE•7-18, 7-28
failure• 7-21
UETLOADOO.DAT • 7-31
UETNETSOO.EXE • 7-33
UETP
See User Environment Test Package
UETP$NODE_ADDRESS•7-10
UETP.COM • 7-27
termination of• 7-13
UETP.LOG•7-12, 7-17, 7-26, 7-32
UETPHASOO.EXE • 7-27, 7-28, 7-32
UETUNASOO.EXE • 7-16
UIC
See User Identification Code
Unit number
definition • 3-1

Index

Update procedure
See also Mandatory update
definition• 1-2
restrictions• 1-2
Upgrade procedure
definition• 1-1
restrictions• 1-2
User disk
preparing for UETP • 7-1 , 7-4, 7-5
space requirements for UETP • 7-4
test error during UETP • 7-21
UETP test image• 7-31
UETP test of• 7-30
User Environment Test Package (UETP)
aborting execution of• 7-13
description of• 7-1
displaying tests as they run• 7-15
initialization phase• 7-28
interpreting output of• 7-15
master command procedure• 7-27
normal completion of• 7-12
organization of• 7-27
required privileges• 7-20
required quotas• 7-20
requirements for small disk systems• 7-9
running all phases of• 7-2
running individual phase of• 7-11
running multiple passes of• 7-11 , 7-1 7
starting • 7-10
typical failures reported by• 7-18
when to run • 6-3
User Identification Code (UIC)
for UETP • 7-5
User load
defined for UETP DECnet test• 7-33
defining for the UETP load test• 7-12
equation used to determine for UETP load test•
7-16

v
VAX cluster environment
how to prepare• 6-2
preparing for UETP • 7-9
registering the VMS license• 6-1
test failure during UETP • 7-23
V AXstation 2000
serial lines• 2-7
VAXstation 2000/MicroVAX 2000
configuring devices• A-1
disk driver• C-1
1/0 space•B-1
V AXVMSSYS.PAR • 8-1
VMS.EXE• 8-1
VMS license• 6-1
VMSTAILOR
adding files to a system disk• 6-2
removing files from a system disk• 6-2
Volume-label
definition• 4-3, 5-3, 9-10
used with BACKUP command• 9-10
Volume Shadowing
registering the license• 6-1

w
Winchester fixed disk
See Fixed disk• 2-23
Wrong account error message• 7-20
Wrong privileges error message• 7-19
Wrong quotas error message• 7-19

lndex-5

Reader's Comments

VMS Installation and Operations:
VAXstation 2000, MicroVAX 2000
AA-LB34A-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

D
D
D
D
D
D
D
D

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

·--;;~t;;;:d

Here ~d Ta~ ------------------Tlllr-------;~~;~--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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Reader's Comments

VMS Installation and Operations:
VAXstation 2000, MicroVAX 2000
AA-LB34A-TE

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

D
D
D

D
D
D
D
D
D
D
D

Cl
D
D
D
D

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

- - - Do Not Tear - Fold Here and Tape -------------------~111r--------------
No Postage

mnmnomn™

~;~=~=~y
in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POSTAGE 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ·