Digital PDFs

AI-Y514B-TE

April 1986

266 pages

Original

23MB

Document:	VMS 4.4 Guide to VAX VMS Software Installation
Order Number:	AI-Y514B-TE
Revision:
Pages:	266
Original Filename:	https://archive.org/download/stx_AI-Y514B-TE_VMS_4.4_Guide_to_VAX_VMS_Software_Installation_Apr86/AI-Y514B-TE_VMS_4.4_Guide_to_VAX_VMS_Software_Installation_Apr86.pdf

OCR Text

Guide to VAX/VMS Software
Installation
Order Number: AI-Y514B-TE

April 1986
This manual provides detailed information to support the software installation
booklets. It also includes information to support the installation of system
upgrades, maintenance updates, and optional software products.

Revision/Update Information:

This revised document supersedes the

Guide to VAX/VMS Software Installation
Version 4.0.
Software Version:

digital equipment corporation
maynard, massachusetts

VAX/VMS Version 4.4

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 ©1986 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

smanm
ZK-2838

HOW TO ORDER ADDITIONAL DOCUMENTATION
DIRECT MAIL ORDERS
USA & PUERTO RICO*

CANADA

INTERNATIONAL

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

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

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

In Continental USA and Puerto Rico call 800-258-1710.
In New Hampshire, Alaska, and Hawaii call 603-884-6660.
In Canada call 800-267-6215.
*

Any prepaid 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.
This document was prepared using an in-house documentation production system. All page
composition and make-up was performed by T^X, the typesetting system developed by
Donald E. Knuth at Stanford University. TgX is a registered trademark of the American Mathematical
Society.

Contents
PREFACE

xiii

NEW AND CHANGED FEATURES

xvii

CHAPTER 1

OVERVIEW OF SOFTWARE INSTALLATION

1-1

1.1

SUMMARY OF A NEW INSTALLATION

1-2

1.2

SUMMARY OF A SYSTEM UPGRADE

1-3

1.3

SUMMARY OF MAINTENANCE UPDATE AND OPTIONAL PRODUCT
INSTALLATIONS
1-3

CHAPTER 2

CONSOLE SUBSYSTEMS

2-1

2.1

THE CONSOLE TERMINAL AND COMMAND LANGUAGE

2-1

2.2

PROCESSOR CONTROL PANELS
2.2.1
VAX 8600/8650 Processor Control Panel
2.2.1.1
Indicator Lights • 2-3
2.2.1.2
Switches • 2-4

2-3
2-3

2.2.2

VAX 8200 Processor Control Panel
2.2.2.1
Keylock Switches • 2-6
2.2.2.2
Status Lights • 2-7
2.2.2.3
Restart Pushbutton • 2-8

2-6

2.2.3

VAX-11/780 Processor Control Panel
2.2.3.1
Indicator Lights • 2-9
2.2.3.2
Switches • 2-9
VAX—11/750 Processor Control Panel
2.2.4.1
Indicator Lights • 2-10
2.2.4 2
Switches • 2-11

2-8

2.2.4

2-10

2.2.5

VAX-11/730 and VAX-11/725 Processor Control
Panels _
2.2.5.1
Indicator Lights • 2-13
2.2.5.2
Switches • 2-14

2-13

BLOCK STORAGE DEVICES

2-15

2 3.1

Block Storaae on the VAX 8600/8650

2-16

2.3.2
2.3.3

Rlnnk Storage on tho VAX 8200

2-16

Block Storage on the VAX-11/780
2.3.3.1
Handling TU58 Cassettes • 2-21
2.3.3.2
Block Storage on the VAX-11/750 • 2-24
2.3.3.3
Block Storage on the VAX-11/730 • 2-24
2.3.3.4
Block Storage on the VAX-11/725 • 2-26

2-18

CONTROLS AND INDICATORS FOR PERIPHERAL DEVICES

3-1

3.1

RL02 DISK DRIVE

3-2

3.2

RK07 DISK DRIVE

3-3

3.3

RP05 AND RP06 DISK DRIVES

3-5

3.4

RP07 DISK DRIVE

3-8

3.5

RM03 AND RM05 DISK DRIVES

3-9

3.6

R80 AND RM80 DISK DRIVES

3-11

3.7

RA60, RA80, AND RA81 DISK DRIVES

3-13

3.8

RC25 DISK DRIVE

3-15

3.9

HANDLING DISK CARTRIDGES AND DISK PACKS
3.9.1
Handling RL02 and RK07 Disk Cartridges

3-16
3-16

CHAPTER 3

Contents

3.9.2

Handling Disk Packs _•
3.9.2.1
Installing the Disk • 3-20
3.9.2.2
Removing the Disk Pack from the Drive • 3-21

3-18

3.10

TS11 TAPE DRIVE

3 22

3.11

TE1 6 TAPE DRIVE

3-23

3.12

TU77 TAPE DRIVE

3-25

3.13

TU78 TAPE DRIVE

3-27

3.14

TU80 AND TU81 TAPE DRIVES

3-29

3.15

HSC50 AND HSC70 CONTROLLERS

3-31

SUPPORT INFORMATION

4-1

4.1

LOGGING IN TO THE SYSTEM

4-1

4.2

BOOTING DURING INSTALLATION
4.2.1
Booting VAX Processors

4-2
4-2

4.3

BOOTING FROM HSC DISKS
4.3.1
Booting a VAX 8600 or a VAX-11/780 During an
Installation
4.3.2
Booting a Running VAX 8600 or a VAX-11/780
4.3.3
Booting a VAX 8200 or a VAX-11/750 During an
Installation
4.3.4
Booting on a Running VAX 8200 or a VAX—11/750

4-4

4-8
4-9

4.4 NAMING DEVICES
4.4.1
Boot Names for the VAX—11/785 _1__
4.4.2
Boot Names for the VAX—11/750 _
4.4.3 VAX 8600 Device Names _
4.4.4 VAX 8200 Device Names _
4.4.5 VAX-11/780 Device Names _

4-11
4-14
4-15
4-15
4-16
4-16

CHAPTER 4

4-5
4-6

Contents

4.4.6
4.4.7
4.4.8

_
_
-

4-17
4-18
4-18

4.5 BACKING UP A SYSTEM DISK
4.5.1
Backing up a VAX 8600 System Disk 4.5.2
Backing Up a VAX 8200 System Disk 4.5.3
Backing Up a VAX—11/780 System Disk 4.5.4
Backing Up a VAX—11/750 System Disk 4.5.5
Backing Up an R80 System Disk on a VAX—11/730 _
4.5.6
Backing Up an RL02 System Disk 4.5.7
Backing Up a Fixed RC25 System Disk 4.5.8
Backing Up a Removable RC25 System Disk _

4-18
4-19
4-20
4-22
4-24
4-26
4-28
4-29
4-31

4.6

VAX—11/750 Device Names
VAX-11/730 Device Names
VAX-11/725 Device Names

BUILDING STANDALONE BACKUP ON CONSOLE MEDIA
4-33
4.6.1
Building Standalone BACKUP on RX01 Diskettes or TU58 Tape
Cassettes _
4-33
4.6.2
Building Standalone BACKUP on RX50 Diskettes _
4-36
4.6.3
Building Standalone BACKUP on an RL02 Disk _
4-38

4.7 USING STANDALONE BACKUP ON DISK
4.7.1
Installing Standalone BACKUP in Alternate System Root
SYSE _
4.7.2 Creating a Command Procedure to Boot Standalone
BACKUP _
4.7.3
Booting Standalone BACKUP from SYSE _

4-39
4-40
4-40
4-42

VMSINSTAL COMMAND PROCEDURE

5-1

5.1

PREPARING TO USE VMSINSTAL

5-1

5.2

INVOKING VMSINSTAL

5-3

5.3

CHOOSING VMSINSTAL OPTIONS

5-6

5.4

RECOVERING FROM A SYSTEM FAILURE

5-10

5.5

SPECIAL CONSIDERATIONS FOR SMALL-DISK SYSTEMS

5-11

CHAPTER 5

5.5.1
5.5.2

5.6

Installing Optional Products on Small-Disk Systems
Handling Revised Files Detected During Installation

5-12
5-13

ERROR MESSAGES

5-13

UPGRADING TO VERSION 4.4

6-1

6.1

PREPARING TO UPGRADE THE SYSTEM

6-3

6.2

PERFORMING THE UPGRADE
6.2.1
Upgrade Phase 1
6.2.1.1
Upgrade Phase 1 for VAX-1 1/725, VAX-11/730,
VAX-11/780, and VAX 8600 Systems • 6-9
6.2.1.2
Upgrade Phase 1 for VAX-1 1/750 and VAX 8200
Systems *6-12
6.2.2
Upgrade Phase 2
6.2.3
Upgrade Phase 3
6.2.4
Upgrade Phase 4
6.2.5
Upgrade Phase 5

6-6
6-8

6-15
6-16
6-16
6-17

6.3

SPECIAL FILE HANDLING DURING UPGRADE

6-19

6.4

INSTALLED IMAGES

6-20

6.5

CREATING ALTERNATE ROOTS ON A COMMON SYSTEM DISK

6-20

RUNNING THE UETP

7-1

7.1

SUMMARY OF OPERATING INSTRUCTIONS

7-2

7.2

SETTING UP THE UETP
7.2.1
Loaaina In
7.2.1.1
[SYSTEST] Directories • 7-4

7-3
7-4

CHAPTER 6

CHAPTER 7

Contents

7.2.2

Preparing Devices
7.2.2.1
7.2.2.2
7.2.2.3
7.2.2.4
7.2.2.5
7.2.2.6
7.2.2.7
7.2.2.8
7.2.2.9
7.2.2.10

7.2.3
7.2.4

Preparing for VAXcluster Testing _
Preparing a Small-Disk System _
7.2.4.1
7.2.4.2

7.4

7.5 TROUBLESHOOTING
7.5.1
Relationship of the UETP to Error Logging and
Diagnostics _
7.5.2
Interpreting UETP Output _
7.5.3 The Log Files _
7.5.4 Possible UETP Errors _

viii

7-12
7-12

Single Run Versus Multiple Passes • 7-13
Defining User Load for Load Test *7-13
Long and Short Report Format • 7-15
Running a Subset or Individual Phase • 7-16

USING CTRL/Y AND CTRL/C
7.4.1
Using CTRL/Y _
7.4.2
Using CTRL/C _

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-9
7-10

Running the UETP from the Library Disk *7-11
Running the UETP from the System Disk • 7-11

7.3 INTERACTING WITH THE UETP
7.3.1 Startup Dialog _
7.3.1.1
7.3.1.2
7.3.1.3
7.3.1.4

7-5

Setting Up the System Disk • 7-5
Setting Up Additional Disk Drives • 7-5
Setting Up Magnetic Tape Drives • 7-6
Setting Up Terminals and Line Printers • 7-7
Preparing the DEUNA for UETP Testing • 7-7
Preparing the DR11-W for UETP Testing • 7-7
Preparing the DR750 or the DR780 for UETP Testing • 7-8
Preparing the MA780 for UETP Testing • 7-9
Preparing a Second LPA11-K for UETP Testing • 7-9
Devices Not Tested • 7-9

Wrong Quotas, Privileges, or Account • 7-21
UETINIT01 Failure • 7-23
Insufficient Disk Space • 7-24
Incorrect Setup of a VAXcluster • 7-25
Problems During the Load Test • 7-27
DECnet Error • 7-28
Errors Logged but not Displayed • 7-28
No PCB or Swap Slots • 7-29
Hangs • 7-30
Bugchecks and Machine Checks • 7-30

7-16
7-17
7-17
7-18
7-18
7-18
7-19
7-20

7.6

UETP TESTS AND PHASES
7.6.1
Initialization Phase
7.6.2
Device Test Phase
7.6.2.1
How the Device Phase Works • 7-32
7.6.2.2
Running a Single Device Test • 7-32
7.6.3 System Load Test Phase
7.6.4
DECnet Test Phase
7.6.4.1
Environment • 7-37
7.6.4.2
How the DECnet Phase Works • 7-37
7.6.5 Cluster-Integration Test Phase
7.6.6 Termination of the UETP

7-30
7-31
7-31

APPENDIX A

FILES OF THE VAX/VMS SYSTEM

A-1

APPENDIX B

RESTORING THE VAX/VMS SOURCE KIT

B-1

APPENDIX C

USING VMSUPDATE

C-1

C.1

PREPARING TO INSTALL OPTIONAL SOFTWARE

C-1

C.2

PERFORMING THE INSTALLATION

C-2

C.3

COMPLETING THE INSTALLATION

C-3

OPERATING SYSTEM DISTRIBUTION KITS

D-1

D.1

VAX 8600 DISTRIBUTION KIT

D-1

D.2

VAX 8200 DISTRIBUTION KIT

D-2

D.3

VAX-11/780 DISTRIBUTION KIT
D.3.1
Magnetic Tape Kit _
D.3.2 RK07 Kit _
D.3.3 RA60 Kit __

D-2
D-3
D-3
D-4

APPENDIX D

7-35
7-36

7-39
7-41

Contents

D.4

VAX-11/750 DISTRIBUTION KIT
D.4.1
Magnetic Tape Kit _
D.4.2 RK07 Kit _
D.4.3 RA60 Kit _
D.4.4 RL02 Kit _

D-4
D-5
D-5
D-6
D-6

D.5

VAX-11/730 DISTRIBUTION KITS
D.5.1
RL02 Distribution Kit _
D.5.2 Magnetic Tape Distribution Kit _
D.5.3 RA60 Kit _

D-7
D-7
D-8
D-8

D.6

VAX-11/725 DISTRIBUTION KIT

D-9

INDEX

FIGURES
2—1

The VAX 8600 Processor Control Panel

2-3

2—2

The VAX 8200 Processor Control Panel

2-6

2-3

The VAX-11/780 Processor Control Panel

2-8

2-4

The VAX-11/750 Processor Control Panel

2-10

2-5

VAX-11/730 and VAX-11/725 Processor Control Panel

2-13

2-17

2—6

Inserting a Diskette into CSA2

2—7

TU58 Locations on IDC-Configured VAX—11/730

2-25

2-8

TU58 Locations on UDA-Configured VAX-11/730

2-25

2- 9

TU58 Locations on VAX-11/725

2-27

3- 1

RL02 Front Panel Controls and Indicators

3—2

RK07 Front Panel Controls and Indicators

3—3

RP05 and RP06 Front Panel Controls and Indicators

3—4

RP07 Front Panel Controls and Indicators

3—5

RM03/RM05 Front Panel Controls and Indicators

3-6

R80 and RM80 Front Panel Controls and Indicators

3-7

RA60, RA80, and RA81 Front Panel Controls and Indicators

3-8

_
_
_

3-2
3-4
3-6
3-8
3-10
3-12

3-14

RC25 Control and Indicators

3-15

3—9

Disk Drive with Lid Released

3-17

3—10

Disk Cartridge

3-17

Contents

3—11

Disk Pack Construction

3—12

Disk Pack Access

3-19

3-20

3-13

TS11 Front Panel Controls and Indicators

3-22

3-14

TE16 Front Panel Controls and Indicators

3-24

3—15

TU77 Front Panel Controls and Indicators

3-26

3-27

3-16

TU78 Front Panel Controls and Indicators

3—17

TU80 and TU81 Front Panel Controls and Indicators

3—18

Operator Control Panel Controls and/indicators

3-29

3-31

TABLES
2-1

Block Storage Devices

2-16

4-1

Dfivicfi Codfis

4-12

4-2

VAX 8600 Device Codes

4-15

VAX 8200 Device Codes

4-16

VAX-11/780 Device Codes

4-16

VAX-11/750 Device Codes

4-17

4-6

VAX-11 /730 Device Codes

4-18

7-1

The Devine Tests;

7-35

A—1

Files Contained in Directory [SYSEXE]

A-2

A—2

Files Contained in Directory [SYSHLP]

A-9

*
1

<ji

4-3
4-4

A—3

Files Contained in Directory [SYSHLP. EXAMPLES]

A-1 0

A—4

Files Contained in Directory [SYSLIB]

A-1 2

A—5

Files Contained in Directory [SYSMGR]

A-1 5

A—6

Files Contained in Directory [SYSMSG]

A-1 6

A—7

Files Contained in Directory [SYSTEST]

A-1 7

A—8

Files Contained in Directory [SYSUPD]

A 18

Preface
This manual contains information that supports the various software
installation booklets used to install VAX/VMS operating systems. It
also includes instructions to support the installation of system upgrades,
maintenance updates, and optional software products.
All references to VAX-11/780 apply to the VAX-11/782 and
VAX-11/785 except as noted. All references to VAX 8600 apply to the VAX
8650 except as noted. For information on installing Micro VAX hardware,
see the hardware manual supplied with your Micro VAX processor. For
information on installing Micro VMS software, see Installing or Upgrading
MicroVMS from Diskettes or Installing or Upgrading MicroVMS from a Tape
Cartridge.

Intended Audience
This manual is intended for all users who are qualified to install software on
VAX processors.

Structure of This Document
This manual includes seven chapters and four appendixes.
•

Chapter 1 introduces software installation on VAX processors and
includes an overview of the installation procedure.

•

Chapter 2 describes the CPU console controls and indicators for the
various VAX processors that relate to software installation.

•

Chapter 3 describes the controls and indicators for the various storage
devices used to install the operating system. These include console
storage devices, disk drives and magnetic tape drives. This chapter
describes how to load media into the various drives.

•

Chapter 4 expands on the installation procedures.

•

Chapter 5 describes the VMSINSTAL command procedure.

•

Chapter 6 explains how to upgrade your operating system.

•

Chapter 7 describes the User Environment Test Package and includes
some instructions on operator-level troubleshooting.

•

Appendix A lists the files that make up a Version 4.4 operating system.

XIII

Preface

•

Appendix B provides source kit licensees with instructions on how to
invoke the source kit command procedure and a pointer to supporting
documentation.

•

Appendix C outlines the VMSUPDATE command procedure that was
previously used to install updates and products onto the operating
system.

•

Appendix D describes the contents of the various software distribution
kits.

Associated Documents
The following documents include material that may be helpful in performing
installations of the operating system on VAX processors.
•

VAX/VMS System Manager's Reference Manual

•

VAX/VMS DCL Dictionary

•

VAX/VMS Authorize Utility Reference Manual

•

VAX/VMS Bad Block Locator Utility Reference Manual

•

VAX/VMS Disk Quota Utility Reference Manual

•

VAX/VMS Error Log Utility Reference Manual

•

VAX/VMS System Dump Analyzer Reference Manual

•

VAX/VMS System Generation Utility Reference Manual

In addition, the VAX/VMS Volume Shadowing Manual describes how to install
software using a system disk shadow set, if you have the volume shadowing
option.

Preface

Conventions Used in This Document
Convention

Meaning

[REU

A symbol with a one- to three-character
abbreviation indicates that you press a key
on the terminal, for example, |ret| .

|CTRL/x|

The phrase CTRL/x indicates that you
must press the key labeled CTRL while
you simultaneously press another key, for
example, CTRL/C, CTRL/Y, CTRL/O.

$ SHOW TIME
05-JUN-1985 1 1:55:22

Command examples show all output lines
or prompting characters that the system
prints or displays in black letters. All
user-entered commands are shown in red
letters.

$ TYPE MYFILE.DAT

Vertical series of periods, or ellipsis, mean
either that not all the data that the system
would display in response to the particular
command is shown or that not all the data
a user would enter is shown.

file-spec, . . .

Horizontal ellipsis indicates that additional
parameters, values, or information can be
entered.

[logical-name]

Square brackets indicate that the enclosed
item is optional. (Square 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
The following new features have been added to the Guide to VAX/VMS
Software Installation for VAX/VMS Version 4.4:
•

Description of console, peripherals, and upgrade procedure for VAX
8600/8650 processors

•

Description of console, peripherals, and upgrade procedure for VAX 8200
processor

•

Description of support for the HSC70 controller

•

Description of new VMSINSTAL option Release notes option (N) and new
VMSINSTAL error messages

Overview of Software Installation

You install software on a VAX processor by restoring (or converting) the
software from a transportable form on magnetic tape or disk to a form that
can be bootstrapped from a disk and run on a processor.
There are three kinds of VAX/VMS software installation:
•

Installation of a newly purchased operating system

•

Upgrade of your system to the most recent major version

•

Installation of maintenance updates and optional software products

If you are installing a new system, follow the instructions in the software
installation booklet appropriate to your configuration. Currently, booklets
are provided for 17 installation scenarios:
•

Installing VAX /VMS on a VAX-11/725

•

Installing VAX/VMS on a VAX-11/730 configured for R80/RL02
operations

•

Installing VAX/VMS on a UDA-based VAX-11/730 from an RA60
distribution disk

•

Installing VAX/VMS on a UDA-based VAX-11/730 from magnetic tape

•

Installing VAX/VMS on a VAX-11/750 from an RL02 distribution kit

•

Installing VAX/VMS on a VAX-11/750 from an RK07 or RA60
distribution disk

•

Installing VAX/VMS on a VAX-11/750 dual-RK07 system

•

Installing VAX/VMS on a VAX-11/750 from magnetic tape

•

Installing VAX/VMS on a VAX-11/750 from an HSC-based disk

•

Installing VAX/VMS on a VAX-11/750 from an HSC-based tape

•

Installing VAX/VMS on a VAX-11/780 from an RK07 or RA60
distribution disk

•

Installing VAX/VMS on a VAX-11/780 dual-RK07 system

•

Installing VAX/VMS on a VAX-11/780 from magnetic tape

1-1

Overview of Software Installation

•

Installing VAX/VMS on a VAX-11/780 from an HSC-based disk

•

Installing VAX/VMS on a VAX-11/780 from an HSC-based tape

•

Installing VAX/VMS on a VAX 8600 from magnetic tape

•

Installing VAX/VMS on a VAX 8600 from an HSC-based tape

The booklets that describe these installation procedures are shipped in
your distribution kit. Each booklet defines the installation environment and
includes key messages generated by the program.
In most cases, variable information (that is, dates and times and so forth)
is included in displays for illustration purposes only. You should substitute
values appropriate to your installation. Note too, that time intervals specified
for various events may vary from installation to installation.
Other variables reflect the many hardware configurations that may be
encountered in an installation. These include device name variables (load
device and system device) and boot name variables. See Chapter 4 for help
with handling these variables.

1.1

Summary of a New Installation
A newly purchased operating system can be installed by anyone authorized
to do it.
The following is a summary of how a newly purchased operating system is
installed:
1

Boot standalone BACKUP from the distribution kit into the processor.

Using standalone BACKUP, restore the required save set to get a partial,
but bootable, system.

Boot the partially restored system.

Restore the rest of the operating system.

Boot the restored system.

Run the User Environment Test Package (UETP).

1-2

Overview of Software Installation

1.2

Summary of a System Upgrade
Upgrades are installed on existing operating systems to bring them up to
the latest major revision from the most recent maintenance version. For
example, if you want to bring a Version 4.3 system up to Version 4.4, you
would install the Version 4.4 upgrade kit. For the upgrade to be successful,
the existing system files must be substantially the same as when the system
was installed.
A system upgrade is performed in nine steps:

1.3

Back up your current system disk to the disk that will be used for the
upgrade.

Boot the new system volume and log in to the system manager's account
(SYSTEM).

If you want to keep any files that may be affected by the upgrade, move
them to a user directory.

Be sure you have enough space on the new system volume to do the
upgrade.

Be sure the CPU is set up for automatic restart.

Prevent users from logging into the system, stop all queues, and, if
applicable, disconnect the system from DECnet.

Invoke the VMSINSTAL command procedure and follow instructions
that are displayed through the five upgrade phases.

If any of the system reboots fails, change system parameters as directed.

When the upgrade is completed, boot the new system and make
any required changes in system procedures before resuming normal
operations.

Summary of Maintenance Update and Optional Product
Installations
When you install a maintenance update, you must refer to the accompanying
release notes for directions. Similarly, when you install an optional software
product you should refer to the installation documentation that is included
with the product.
You use the VMSINSTAL command procedure to install all maintenance
updates and some optional software products. A few of the optional software
products are installed using the VMSUPDATE command procedure.

1-3

Overview of Software Installation

Both procedures require very little interactive input. You need only prepare
the system for the installation, and then physically manipulate the media as
directed by prompting messages during the installation.
Below is a summary of how to install maintenance updates and optional
products:
1

Back up your system disk.

Keep users off the system.

Set your default to point to the disk receiving the software.

Invoke the installation command procedure.

Respond to prompts from the command procedure.

Shut down the system and then reboot with the new products installed.

Console Subsystems

During the installation, you use the console subsystem to communicate with
the central processing unit (CPU). Each VAX console subsystem includes the
following:
•

A console terminal

•

A console command language

•

Indicators and controls on the processor control panel

•

One or two block storage devices (depending on the type of processor
you have)

•

The optional remote diagnostic port (not usually used to install software)

Because the processor control panels vary from processor to processor, this
chapter discusses each VAX system separately.
The console terminal and the console command language are basically the
same for all VAX processors, however, so a common description is given.

2.1

The Console Terminal and Command Language
The console terminal is a hardcopy terminal that you use as a control station
during the installation. You use the console terminal to enter all commands
and to read all output messages and prompts during the installation. Push
the power switch to the ON position to turn on the console terminal, and
ensure that it contains an adequate supply of paper before you begin the
software installation.
VAX console subsystems run in two mutually exclusive modes: program
mode and console mode. When power is applied, the subsystem is in one of
these modes. In general, if the CPU is running, the console subsystem is in
program mode and the console terminal is used like other terminals on the
system. For example, you use program mode during an installation to invoke
the standalone Backup Utility (BACKUP), to enter DCL commands, and to
receive appropriate installation messages and prompts.

2-1

Console Subsystems

If the CPU is halted, the subsystem is in console mode and the console
terminal can accept commands from the operator. In console mode, you use
the console command language. For most installations, the console command
you will use most often is BOOT. In some cases, you may also use the HALT
command and the DEPOSIT command. The following table describes the
most commonly used console commands:

Command

Definition

BOOT

Causes execution of a console command procedure that
loads a VAX software program into memory and transfers
control to this program.

BOOT/NOSTART

Stops after boot command file has been executed so that
you can alter any input registers (using DEPOSIT) before
transferring control to the primary bootstrap program,
VMB. This command is used only with VAX 8600 or
8650 processors.

DEPOSIT

Puts a value in the specified register or memory location.
See Appendix A for a list of the possible VMB boot
register inputs.

START nnnn

Continues execution of the bootstrap program at the
specified address. (Used in conjunction with the BOOT
/NOSTART command.)

For example, you use the BOOT command to load software into the
CPU; the standalone Backup Utility is loaded first, followed by the
restored components of the operating system. When a bootstrap function
is completed, the console program returns the system to program mode
automatically.
If you use HSC disks to install a new system, you use the DEPOSIT
command to prepare the general registers for booting.
For most systems, such as the VAX-11/725, VAX-11/730, VAX-11/750,
VAX 8200 or VAX 8600/8650, you press CTRL/P to change from program
mode to console mode. The system indicates that it is in console mode by
displaying the console program prompt (> > > ) on the console terminal. If
you have a VAX-11/780, however, you must first press CTRL/P and then
enter the HALT console command to change from program mode to console
mode.
The console program automatically returns the system to program mode after
a bootstrap function has completed. Another way to return the system to
program mode is to enter the CONTINUE console command.

2-2

Console Subsystems

2.2

Processor Control Panels
This section describes the processor control panels for the various VAX
processors.

2.2.1

VAX 8600/8650 Processor Control Panel
The control panel on the VAX 8600/8650 contains a row of four indicator
lights and two five-position keylock switches. Figure 2-1 displays the
processor control panel.

Figure 2-1

2.2.1.1

The VAX 8600 Processor Control Panel

Indicator Lights
There are four indicator lights on the processor control panel. Three of these
lights (VAX STATE, REMOTE ENABLE, and REMOTE ACTIVE) are green
and provide information about the state of the VAX 8600/8650 processor.
The fourth light, ALERT, is the only red light on the panel and is used as
a warning indicator to signal an air flow or temperature problem detected
within the processor cabinet.
Following is a description of each indicator light:
VAX STATE

When flashed on and off, indicates that the CPU is running.

REMOTE ENABLE

When lit, indicates that remote port access is enabled.

REMOTE ACTIVE

When lit, indicates that a carrier signal is present on the
remote port dialup line.

2-3

Console Subsystems

ALERT

This light has three states. When the light is off, normal
temperature and air flow conditions exist within the CPU
cabinet. No user action is required.
When the ALERT light is on, one or more of the
temperature sensors in the CPU cabinet have detected
a higher-than-normal temperature condition which you
should correct immediately. A warning message is sent to
the console.
If the ALERT light begins flashing, temperature or air flow
sensors have exceeded their limits and the system will
automatically shut down within one minute unless you
correct the problem immediately.

2.2.1.2

Switches
The two front panel switches located next to the indicator lights are the
terminal control switch and the restart control switch. The position of these
switches determines the reaction of the processor to a variety of external
inputs.
The terminal control switch lets you control system power from the front of
the CPU cabinet, and lets you control local and remote terminal port access
to the console. Power is applied to the system when the terminal control
switch is in any position but OFF. During installation, you set the switch to
LOCAL.
The switch has five positions:
OFF

No power is applied to the system.

LOCAL

Processor responds to local console commands only. The
remote terminal line is inoperable. Set the terminal control
switch to LOCAL before beginning the VAX 8600/8650
software installation.

LOCAL DISABLE

If the console subsystem is in program mode, the LOCAL
DISABLE setting will prevent console mode commands
from being entered at the console terminal. The CTRL/P
break character is ignored, and the setting of the restart
control switch is ignored on power recovery and after
error halts (a RESTART/BOOT is always attempted).
If the console subsystem is in console mode, commands
are accepted from the local console terminal. The remote
console line is disabled.

2-4

Console Subsystems

REMOTE

With the switch in this setting, local and remote terminals
can be used both as ordinary VMS terminals or as
console terminals. The CTRL/P break character and
any subsequent console mode commands are accepted
from either line.
If the console subsystem is in console mode, command
line input from either the local or remote terminal will
be echoed on both. Any output resulting from these
commands will also be echoed on both terminals.
The remote line is forced to disconnect if the switch is
moved to the LOCAL or LOCAL DISABLE position.

REMOTE DISABLE

This setting allows the remote line to be used as an
ordinary VMS terminal, but not as a console terminal. A
CTRL/P entered from the remote terminal will be ignored
by the console subsystem. The remote line is forced to
disconnect if the switch is moved to the LOCAL or LOCAL
DISABLE position, or if the console subsystem enters
console mode.
The local console terminal can be used in either console or
program mode when the switch is in this position.

The setting of the restart control switch determines the procedure used by
the processor when the system powers up or after an error halt. The switch
has four positions:
BOOT

Attempts to bootstrap the system using the default
bootstrap command procedure.

RESTART/BOOT

Attempts a system restart by checking the restart
parameter block for valid data. If the restart parameter
block is invalid, the system will attempt to bootstrap itself
using the default bootstrap command procedure.

HALT

Halts the system and displays the console prompt
(> > > ) at the console terminal on powerup or following
a system crash.

RESTART/HALT

Attempts a system restart by checking the restart
parameter block for valid data. If the restart parameter
block is invalid, the system halts.

If the terminal control switch is in the LOCAL DISABLE position, the setting
of the restart control switch is ignored and assumed to be in the RESTART
/BOOT position.

2-5

Console Subsystems

2.2.2

VAX 8200 Processor Control Panel
The processor control panel on a VAX 8200 processor consists of a fourposition keylock switch with three corresponding indicator lights, a threeposition keylock switch with threee corresponding indicator lights, three
status lights, and a Restart push button. Figure 2-2 shows the VAX 8200
processor control panel.

Figure 2-2

2.2.2.1

The VAX 8200 Processor Control Panel

Keylock Switches
There are two keylock switches on the processor control panel of a VAX
8200 processor. Each keylock switch is associated with three indicator lights,
although the upper keylock switch has four possible settings. To change
a keylock switch setting, insert a key and turn to the desired setting. The
following list describes the possible settings for the keylock switches.

2-6

Console Subsystems

2.2.2.2

Off

The upper keylock switch is set in the vertical position; there
is no corresponding light. Removes power from the entire
system, including the Battery Backup Unit (BBU).

Standby

When the upper keylock switch is set to Standby, the red
indicator light glows. The power supply and blower in the
main unit are turned on.

Enable

When the upper keylock switch is set to Enable, the yellow
indicator light glows. Power is supplied to the entire system
and the system can enter console mode. If the lower keylock
switch is set to Auto Start, pressing the Restart push button
reboots the system. When the switch setting is changed
from Standby to Enable, system self-tests run.

Secure

When the upper keylock switch is set to Secure, the green
indicator light glows. This setting maintains power to the
entire system, and is used for normal operation. The system
cannot enter console mode, and you cannot reboot the
operating system by pressing the Restart push button.

Update

When the lower keylock switch is set to Update, the red
indicator light glows. This setting allows you to change data
in the electrically erasable programmable read only memory
(EEPROM) using the EEPROM Utility.

Halt

When the lower keylock switch is set to Halt, the yellow
indicator light glows, causing the processor to halt in console
mode. This setting prevents booting of the operating system
when power to the the VAX 8200 is turned on.

Auto Start

When the lower keylock switch is set to Auto Start, the
green indicator light glows. Use this position for normal
system operations to let the system automatically reboot
when power is restored following a power failure. If the
upper keylock switch is set to Enable, pressing the Restart
push button reboots the system.

Status Lights
There are three status lights on the processor control panel of a VAX 8200
processor. The following list describes the processor status indicated when
each light is lit.

2-7

Console Subsystems

2.2.2.3

Run

This green light glows when the VAX 8200 processor is running
under an operating system. When the system enters console
mode, the green light goes off.

Battery

This green light glows when the Battery Backup Unit (BBU) is fully
charged. It flashes slowly when the BBU is charging itself, and
flashes quickly when the BBU is supplying power to the system. If
your system has no BBU, this light is always off.

Fault

This red light glows during self-tests and turns off once self-tests
have completed successfully.

Restart Pushbutton
The Restart push button is located on the lower right side of the processor
control panel. Pressing the Restart push button reboots the operating system
when the upper keylock switch is set to Enable and the lower keylock switch
is set to Auto Start. If the lower keylock switch is not set to Auto Start and
the upper keylock switch is set to Enable, pressing the Restart push button
causes the system to run self-tests. If the upper keylock switch is not set to
Enable, pressing the Restart push button has no effect.

2.2.3

VAX—11/780 Processor Control Panel
The VAX-11/780 processor control panel consists of four indicator lights, an
AUTO RESTART switch, a BOOT switch, and a five-position keylock switch.
The indicator lights reflect the current state of the system, and the switches
dictate how the system will react to initial bootstrapping, shutdowns, and
restarts. Figure 2-3 shows the VAX-11/780 processor control panel.

Figure 2-3

The VAX-11/780 Processor Control Panel

ZK-776-82

2-8

Console Subsystems

2.2.3.1

Indicator Lights
There are four indicator lights on the processor control panel. The first three
indicate the operational state of the CPU. The fourth indicates the state of
remote diagnostic procedures (not usually applicable to software installation).

2.2.3.2

ATTN

When lit, indicates that you have the attention of the console
program.

RUN

When lit, indicates that the processor is running.

POWER

When lit, indicates that power is applied to the processor
and that the keylock switch is not in the OFF position.

REMOTE

When lit, indicates that remote diagnostic procedures are
being performed on the system.

Switches
The AUTO RESTART switch controls the processor's powerup sequence.
This switch has two positions:
ON

Restarts the system automatically, even when unattended.

OFF

Halts the system and displays the console prompt (> > > ) at the
console terminal.

The BOOT switch bootstraps the system using the default bootstrap
command
The keylock switch lets you control system power from the front of the
CPU cabinet, and lets you establish the operating mode as described below.
Power is applied to the system when the keylock switch is in any position
but OFF. During installation, you set the switch to LOCAL.
OFF

No power is applied to the CPU (except battery backup to
the time-of-year clock) or to memory.

LOCAL DISABLE

Local console terminal commands are ignored.

LOCAL

Processor responds to local console commands and the
remote line is disabled. This position is used for installing
the operating system software.

REMOTE DISABLE

Processor cannot respond to commands from remote line
terminals.

REMOTE

Processor responds to commands from a remote line
terminal but local console commands are ignored.

2-9

Console Subsystems

2.2.4

VAX-11/750 Processor Control Panel
The VAX-11/750 processor control panel includes seven indicator lights,
four switches, and a TU58 cartridge drive. The indicator lights reflect the
current status of the system, and the switches dictate how the system will
react to initial bootstrapping, shutdowns, and restarts. Figure 2-4 shows the
VAX-11/750 processor control panel.

Figure 2-4

The VAX-11/750 Processor Control Panel

BOOT DEVICE

CPU STATE

POWER ON ACTION

LOCAL
SECURE

REMOTE/
SECURE

OFF -

- REMOTE

ZK-995-82

2.2.4.1

Indicator Lights
There are seven indicator lights on the processor front panel: the first three
indicate the state of the processor, and the remaining four indicate the state
of the remote diagnostic procedures.
The CPU status lights are described in the following list:
POWER

When lit, indicates that power is applied to the processor and that the
keylock switch is not in the OFF position.

RUN

When lit, indicates that the processor is running.

ERROR

When dimly lit, indicates the processor is running normally.
When brightly lit, indicates that the processor has experienced an
unrecoverable error. If this occurs, push the white RESET button to
reset the machine. (The ERROR light will remain dimly lit.) If the light is
not lit during normal operation, the bulb is probably defective.

The remote diagnostic indicator lights appear only on processors that have
installed a remote diagnostic ROM, and are visible only when lit. The remote
diagnostic indicator lights are described in the following list:

2-10

Console Subsystems

2.2.4.2

REMOTE D

When lit, indicates that the keylock switch is in the REMOTE
position.

RD FAULT

When lit for more than 10 seconds, indicates that the remote
diagnostic ROM has detected an error. When a processor
configured with a remote diagnostic ROM is powered up, this
light will come on for about 10 seconds to indicate that a self
test is in progress.

RD TEST

When lit, indicates that the remote host connection has been
made with successful protocol exchange.

RD CARRIER

When lit, indicates that a carrier signal is present on a dialup
line.

Switches
The POWER ON ACTION switch controls the processor's powerup sequence.
The processor interprets and acts on the position of the POWER ON
ACTION switch in the following situations:
•

After an orderly shutdown

•

After a brief power failure

•

After the microcode detects a halt condition (for example, a HALT
instruction executed in kernel mode)

Each position of the switch provides the processor with instructions on how
to power up the system for different situations.
BOOT

Bootstraps the system from the device selected by the BOOT
DEVICE switch.

RESTART
(BOOT)

Restarts the system. A bootstrap is executed from the
device selected by the BOOT DEVICE switch if the restart
fails.

HALT

Halts the system and displays the console prompt (> > > )
at the console terminal.

RESTART
(HALT)

Restarts the system. The system halts if the restart fails.

During normal operations, the POWER ON ACTION switch should be set to
RESTART (BOOT) for the most comprehensive system recovery procedure.
The BOOT DEVICE switch is used to select the system's bootstrap device.
The processor interprets and acts on the position of the BOOT DEVICE
switch in the following situations:

2-11

Console Subsystems

•

When you issue the console BOOT command without specifying a device
name

•

When the system attempts an automatic bootstrap

In either situation, the processor examines the BOOT DEVICE switch and
assumes that the selected bootstrap device is the first unit on the first
controller, that is, unit number 0 on controller A.
The BOOT DEVICE switch has four positions: A, B, C, and D. Position
A always causes the system to bootstrap from the TU58 cartridge drive.
Positions B, C, and D correspond to the remaining disk controllers. Consult
your DIGITAL field service representative to determine how the positions
correspond to the available disk controllers. Typically, you should set the
BOOT DEVICE switch to the position corresponding to your system disk.
The RESET button (in earlier models labeled INITIALIZE) provides for an
automatic system shutdown followed by a power-up sequence without
disturbing the contents of memory. The system determines the power-up
action by examining the position of the POWER ON ACTION switch.
The 5-position keylock switch allows you to control system power, and lets
you establish the various operating modes. During installation, you set the
switch to LOCAL. Power is applied to the system when the keylock switch is
in any position except OFF.
OFF

No power is applied to the CPU (except battery backup to
the time-of-year clock) or to memory.

SECURE

Console commands are ignored, the remote diagnostic line
is disabled, and the RESET switch is disabled.

LOCAL

Processor acts on console commands, but the remote
diagnostic line is disabled.

REMOTE/SECURE

Processor responds to commands from the remote
diagnostic line, but local console terminal commands
are ignored and the RESET switch is disabled. The remote
diagnostic module cannot be used for fault isolation in this
setting.

REMOTE

Processor responds to commands from the remote
diagnostic line but local console terminal commands are
ignored; however, the remote line can be used to restore
control to the local console terminal.

2-12

Console Subsystems

2.2.5

VAX—11/730 and VAX-11/725 Processor Control Panels
The processor control panel is nearly identical on the VAX-11/725 and
the VAX-11/730 processors. The only difference is that there is no BATT
(battery) indicator for the VAX-11/725 because the system does not include
a battery backup feature.
The panel includes several indicator lights, an AUTO RESTART/BOOT
switch, and a 6-position keylock switch. The indicator lights reflect the
current state of the system and the switches dictate how the system will react
to initial bootstrapping, shutdowns, and restarts.
Figure 2-5 shows the VAX-11/730 and VAX-/725 processor control panel.

Figure 2-5

VAX-11/730 and VAX-11/725 Processor Control Panel

Battery Backup Not Included on VAX-11/725
ZK-1002-82

2.2.5.1

Indicator Lights
The four processor control panel indicator lights and their respective
functions are described below.
RUN

When lit, this light indicates that the processor is running in program
mode.

DC ON

When lit, this light indicates that DC power is present in the processor,
and that the keylock switch is not in the OFF position.

2-13

Console Subsystems

BATT

When lit steadily, light indicates that the backup battery is at greater
than 90% of full power. (This indicator is not included on the VAX-11
/725 processor control panel.)
When flashing slowly (less than once every second), this light indicates
that the backup battery is at less than 90% of full power and is
charging.
When flashing quickly, this light indicates that the backup battery is at
less than 90% of full power and is discharging.
When the light is out, the backup battery is dead or not present.

R/D

2.2.5.2

When lit, this light indicates that remote diagnostic procedures are
being performed on the system.

Switches
This section describes the AUTO RESTART/BOOT switch and the keylock
switch.
The AUTO RESTART/BOOT switch has two functions: it instructs the
processor what to do when halt conditions occur, and it bootstraps the
system. The switch has three positions: ON, OFF, and BOOT. The first two
positions, ON and OFF, control the action of the processor in the following
situations:
•

During initial powerup

•

After a momentary power failure

•

When the microprogram detects an error halt condition (for example, a
HALT instruction executed in kernel mode)

If the switch is in the ON position when these conditions occur, the system
restarts automatically. If the switch is in the OFF position, a console prompt
(> > > ) appears at the console terminal and no action is taken by the
processor.
The BOOT position is spring loaded. When the switch is momentarily
pushed to the BOOT position, it bootstraps the system, using the default
bootstrap command procedure.

2-14

Console Subsystems

During installation, the AUTO RESTART switch must be set to the OFF
position. During normal operation, the switch should be left in the ON
position. This position permits the most comprehensive system recovery
procedure.
The keylock switch lets you control system power from the front of the
CPU cabinet and establish various operating modes. Power is applied to
the system when the keylock switch is in any position except OFF. During
installation, you set the keylock switch to LOCAL. Each of the positions is
described below:

2.3

OFF

Power is off.

STD BY

Power is applied only to the WCS module and main memory.

LOCAL

Processor can respond to console commands from the local
console, but the remote diagnostics line is disabled.

LOC DSBL

Processor cannot respond to console commands, but the console
terminal can be used as a standard terminal. The remote line is
disabled. The BOOT position of the AUTO RESTART/BOOT switch
is ignored.

REM DSBL

Processor cannot respond to console commands from remote line
terminals, but the remote terminal is usable as a standard terminal.
The local console is disabled.

REMOTE

Processor responds to console commands from a remote line
terminal, but the local console terminal is disabled.

Block Storage Devices
The block storage device is the console subsystem component that provides
storage for the console program. Block storage devices may also be used to
install updates and optional products on a system. If you install or upgrade
your system using a magnetic tape distribution kit, standalone BACKUP is
distributed on block storage media. When you bootstrap your system, the
block storage device provides a command procedure that bootstraps the
operating system from the system device to the CPU.
Table 2-1 lists the block storage devices for the various VAX processors.

2-15

Console Subsystems

Table 2-1

Block Storage Devices
VAX Processor

Block Storage Device

VAX 8600

RL02

VAX 8650

RL02

VAX 8200

RX50

VAX-1 1/780

RX01

VAX-11/782

RX01

VAX-11/785

RX01

VAX-1 1/750

TU58

VAX-11/730

TU581

VAX-11/725

TU581

1 These systems feature two TU58 drives.

2.3.1

Block Storage on the VAX 8600/8650
The RL02 disk drive on the VAX 8600/8650 is the device that provides
the storage for the console program. During the VAX 8600/8650 software
installation, you will be prompted to replace the console RL02 disk pack with
the RL02 containing standalone BACKUP.

2.3.2

Block Storage on the VAX 8200
The block storage device on a VAX 8200 is a dual RX50 diskette drive that
is located on the front of the processor, immediately above the processor
control panel. The device name of diskette drive 1 (located on the left) is
CSA1; the device name of diskette drive 2 (located on the right) is CSA2.
Figure 2-6 shows how to insert a diskette into CSA2.
Follow these steps to insert a diskette into CSA2:
1

Check the drive to ensure that it is inactive; the activity light below the
drive should be off. Do not open the diskette drive door if the activity
light is glowing or blinking.

Press the outer portion of the right door to open the CSA2 diskette drive.

Check to ensure that the diskette drive is empty. If there is a diskette in
the drive already, remove it gently, taking care not to touch any exposed
platter surfaces. Place the diskette that you have removed into a paper
envelope.

2-16

Console Subsystems

Figure 2-6

Inserting a Diskette into CSA2
WRITE-PROTECT

ZK-1680-84

Remove the diskette from its paper envelope; do not touch any exposed
platter surfaces.

Align the diskette so that the orange arrow is in line with the orange
bar on the drive, and slide the diskette into the compartment. (If the
diskette is improperly aligned, error messages will be generated. If an
error message appears, remove the diskette, realign it, and reinsert it.)

Close the diskette drive door.

To remove a diskette from the drive, follow the first three steps in the
insertion procedure.

2-17

Console Subsystems

2.3.3

Block Storage on the VAX—11 /780
The VAX-11/780 block storage device is an RX01 diskette drive assigned
the logical device name CSA1. To insert a diskette into CSA1, proceed as
follows while referring to the photograph associated with each instruction.

Unlatch and open the cabinet doors of the CPU cabinet.

Swing out the diskette drive assembly until it is at a right angle to the
cabinet.
The drive assembly is a rectangular, unpainted steel box in the lower
right-hand corner of the central processor cabinet. There is a black
handle on the right of the drive assembly. Pull the handle to swing out
the drive assembly until it is perpendicular to the cabinet. If you do not
swing it out far enough, or if you swing it out too far, you will not be
able to insert the diskette.

2-18

Console Subsystems

Press the black push button to unlock the slot cover. The cover will
spring open.

Insert the console floppy diskette in the drive. Its label should be at the
top and should face the right-hand cabinet door. The oval slot on the
diskette should be at the bottom.

2-19

Console Subsystems

2-20

Console Subsystems

Close and latch the door on the cabinet.

To remove a diskette from the drive, follow the same procedure to gain
access to the diskette, then lift it firmly but gently out of the drive, taking
care not to touch any exposed platter surfaces.

2.3.3.1

Handling TU58 Cassettes
VAX-11/750, VAX-11/730 and VAX-11/725 processors use TU58 tape
cassettes as the block storage device. To insert a cassette into a TU58 drive,
proceed as follows while referring to the photograph associated with each
instruction.

2-21

Console Subsystems

If a cassette is already in the drive, remove the cassette by gripping it
firmly with your fingertips and pulling it gently towards you.

2-22

Console Subsystems

Insert a TU58 with the label facing up and the RECORD tab facing
forward.

Gently push the cassette into the slot until it seats. When fully inserted,
the cassette protrudes from the drive about one-half inch.

2—23

Console Subsystems

2.3.3.2

Block Storage on the VAX-11 /750
The VAX-11/750 uses a single TU58 cassette drive as its block storage
device. The primary purpose of the TU58 is to give you the option of using a
special standalone bootstrap facility called BOOT58 if you cannot boot from
the system disk.
The recommended method for daily operations is to boot from the system
disk itself by positioning the BOOT DEVICE switch to the appropriate setting
and then entering the BOOT command without specifying a boot command
procedure. If you are not sure of the correct setting, see your DIGITAL field
service representative.
If you do not have a position on the BOOT DEVICE switch for the system
device, or if you want to boot from a system root other than SYSO, invoke
the BOOT58 program by setting the BOOT DEVICE switch to position
A and then entering the BOOT command. When you enter the BOOT
command, the BOOT58 program boots, and lets you select the appropriate
boot command procedure. (See the VAX/VMS System Manager's Reference
Manual for more information on bootstrapping VAX/VMS on a
VAX-11/750.)
You can also invoke the BOOT58 facility by entering the following console
command:
»>B/800 DDAO

In addition to providing bootstrap functions, the TU58 drive is used for
installing maintenance updates and optional software products, and for
booting standalone BACKUP on magnetic tape system installations.

2.3.3.3

Block Storage on the VAX-11/730
There are currently two VAX-11/730 system controller configurations:
the Integrated Disk Controller (IDC) configuration, and the UNIBUS Disk
Adapter (UDA) configuration. Although both configurations use a dualTU58 block storage subsystem, the physical locations of the TU58 drives are
different.
The two TU58 cartridge drives are assigned the device names CSA1 and
CSA2, respectively.
CSA1 is used to install updates and optional products and to boot standalone
BACKUP from magnetic tape distribution kits. CSA2 is used to boot the
console program from the console TU58.

2-24

Console Subsystems

Figure 2-7 shows the locations of the TU58 drives on an IDC-based
VAX-11/730. CSA1 is located at the front of the CPU cabinet above the
processor control panel. The other TU58 drive, CSA2, is accessible only by
sliding the CPU out from the cabinet, as shown.
Caution
If you have to slide out the CPU, be sure to extend the safety foot
located under the cabinet first.

Figure 2-7

TU58 Locations on IDC-Configured VAX-11/730

Internal Cassette
Drive (CSA2)

Front Cassette
Drive (CSA1)

ZK-1000-82

There is a LED indicator light on either side of the CSA1 drive. When lit,
the left-hand LED indicates that the front drive (CSA1) is active. When the
right-hand LED is lit, the internal drive (CSA2) is active.
On the UDA-configured VAX-11/730 processors, both TU58 drives are
located at the front of the CPU, and both are readily accessible. CSA1 is
located on the left side of the front panel and is labeled 0. CSA2 is located
on the right side of the front panel and is labeled 1. Figure 2-8 shows the
locations of the TU58 drives on UDA-configured VAX-11/730 systems.

Figure 2-8

TU58 Locations on UDA-Configured VAX-11/730

Run

VAX 11/730

9DSD050

DC On

Bait

R/D

O O O O

-V / locdsbl

Auto Restart-

Sid By

II i 1

Off

\ 3—C/fiemDSBl
^7

Y' Remote

ZK-1345-83

2-25

Console Subsystems

2.3.3.4

Block Storage on the VAX—11/725
On the VAX-11/725 system, CSA1 is located at the front of the CPU cabinet,
and CSA2 is located at the right side of the cabinet. The difference between
the VAX-11/725 and the IDC-configured VAX-11/730 is that CSA2 is
readily accessible through an opening in the side of the cabinet.
Activity indicators, labeled 0 for CSA1 and 1 for CSA2, are located at each
side of CSA1. Figure 2-9 shows the location of the TU58 drives on the
VAX-11/725.

2-26

Console Subsystems

Figure 2-9

TU58 Locations on VAX-11/725

2-27

Controls and Indicators for Peripheral
Devices

This chapter covers operating information related to the peripheral devices
you use when installing software on a VAX processor. It describes how to
use the operating controls and indicators for the various drives, and how to
handle the various types of storage media.
The peripheral devices are magnetic tape drives and disk drives that may be
configured in various system hardware configurations.
•

RL02 disk drive

•

RK07 disk drive

•

RP05, RP06 disk drives

•

RP07 disk drive

•

RM03, RM05 disk drives

•

R80, RM80 disk drives

•

RA60, RA80, RA81 disk drives

•

RC25 disk drive

•

TU78 tape drive

•

TE16, TU45, TU77 tape drives

•

TS11 tape drive

Each device is described as either a load (source) device or a system (target)
device. During an installation, the load device is the storage system that
contains the distribution media, and the system device is the storage system
that contains the new system volume.

3-1

Controls and Indicators for Peripheral Devices

3.1

RL02 Disk Drive
The RL02 disk drive is used with VAX-11/730 systems as either a load
device, a system device or, in a dual-RL02 configuration, as both. With
VAX-11/750 systems, the RL02 is used solely as a load device.
In VAX-11/730 system configurations, the RL02 connects to the UNIBUS by
means of an integrated disk controller (IDC). In non-IDC configurations, it
uses the RL211 controller.
The RL02 provides four front panel controls and indicators (see Figure 3-1.)

Figure 3-1

•

LOAD switch and indicator

•

Logical Address Receptacle and READY indicator

•

FAULT indicator

•

WRITE PROT (write protect) switch and indicator

RL02 Front Panel Controls and Indicators

LOAD

1
READY

FAULT

WRITE
PROT

ZK-1950-84

The LOAD switch and indicator combines an alternate-action switch with a
light that indicates when it is safe to load (or unload) the disk from the drive.
When the drive is at rest, the LOAD indicator is lit, and you may either load
or unload the disk as appropriate. When you insert a disk into the drive and
press the LOAD switch, the indicator immediately turns off and the drive
begins to accelerate to operating speed. When the drive reaches operating
speed, the READY indicator turns on.
Before you can remove the disk from the drive, you must bring the drive to
rest. If the LOAD indicator is not lit, the drive is at operating speed, so you
must press the LOAD switch to bring it to rest. When the drive comes to
rest, the LOAD indicator turns on, and you may remove the disk.

3-2

Controls and Indicators for Peripheral Devices

The logical address receptacle lets you select a unit address for each drive
by simply inserting the appropriate logical address plug. With each drive,
you receive four plugs (numbered 0 through 3) from which you may select
the desired unit address.
Each plug is a mechanical device that activates a set of address switches
corresponding to the unit address numeral inscribed on the plug face. For
example, if the plug is inscribed with the numeral 0, it will activate a set of
switches that assign the unit address 0 to the drive.
Each logical address plug incorporates a READY indicator that turns on
when the drive is at operating speed. The indicator remains on until you
press the LOAD switch to begin applying braking action to the drive spindle.
The FAULT indicator turns on when a hardware fault is detected. For
example, if a loss of write current is detected, the FAULT lamp will turn on
and will remain on until the faulty condition is corrected. If a fault condition
persists, notify maintenance personnel.
The WRITE PROT switch (write protect) is an alternate-action switch that
protects you from inadvertently overwriting the distribution disk. When the
switch is activated, the indicator turns on and the disk is write protected.
Conversely, if the switch is deactivated, the indicator turns off and the
processor is allowed to write to the disk.
During installation, you are usually instructed to write protect the distribution
disk.

3.2

RK07 Disk Drive
The RK07 is a medium-capacity disk that is used to distribute software
for VAX-11/750 and VAX-11/780 systems. The RK07 connects to the
UNIBUS by means of the controller, and it provides the controller with
static, dual-port access to the drive.
The following controls and indicators are located on the RK07 front panel:
•

RUN/STOP switch and indicator

•

Logical Address Plug and READY indicator

•

FAULT indicator

•

WRITE PROT (write protect) switch and indicator

•

Port Selection controls (the A selector switch and indicator and the B
selector switch and indicator)

The RK07 front panel is shown in Figure 3-2.

3-3

Controls and Indicators for Peripheral Devices

Figure 3-2

RK07 Front Panel Controls and Indicators

RUN
STOP

1
READY

FAULT

WRITE
PROT

7K 1952-84

The RUN/STOP switch is an alternate-action switch that you use either to
bring the disk drive up to operating speed (RUN active) or bring the drive to
rest (STOP active). When the indicator is off, the drive is at rest. To bring
the drive up to speed, press the switch once. The indicator turns on and
the drive begins to accelerate to operating speed. When operating speed is
reached, the READY indicator lights.
To bring the drive to rest when it is at operating speed, press the switch
once. The READY indicator will turn off immediately and the drive will
begin to decelerate. The RUN/STOP indicator turns off when the drive
stops.
The logical address receptacle lets you select a unit address by simply
inserting the appropriate logical address plug. With each drive, you receive
eight plugs (numbered 0 through 7) from which you may select the desired
unit address.
Each plug is a mechanical device that activates a set of address switches
corresponding to the unit address numeral inscribed on the plug face. For
example, if the plug is inscribed with the numeral 0, it will activate a set of
switches that assign the unit address 0 to the drive.
Each logical address plug incorporates a READY indicator that turns on
when the drive is at operating speed and remains on until you press the
RUN/STOP switch to begin applying braking action to the drive spindle.
The FAULT indicator turns on when a hardware fault is detected. For
example, if a loss of write current is detected, the FAULT indicator turns on
and remains on until the faulty condition is corrected. See your DIGITAL
field service representative for instructions on correcting fault conditions.
The WRITE PROT switch (write protect) is an alternate-action switch that
protects you from inadvertently overwriting the distribution disk. When the
switch is activated, the indicator turns on and the disk is write protected.
Conversely, if the switch is deactivated, the indicator turns off, and the
processor is allowed to write to the disk.

3-4

Controls and Indicators for Peripheral Devices

During installation, you are usually instructed to write protect the distribution
disk.
The controller may access the RK07 disk drive through I/O port A, I/O port
B, or both ports, depending on the setting of the I/O port selector switches
on the drive front panel. You use the A selector switch to enable access
through port A and the B selector switch to enable access through port B.
The A indicator lights when port A is being used, and the B indicator lights
when port B is being used.

3.3

RP05 and RP06 Disk Drives
The RP05 and RP06 are MASSBUS devices that connect to the processor by
means of the MASSBUS controller. They are large-capacity storage systems;
the RP05 has a capacity of 100 megabytes, and the RP06 has a capacity of
200 megabytes. Port selection gives the controller static, dual-port access to
each of these drives.
The front panel controls and indicators for the RP05 and RP06 include the
following:
•

One logical address plug

•

Four switches

•

Seven indicators

Figure 3-3 shows the locations of the controls and indicators.
Three of the switches are rocker switches and the other is a push button
switch. The indicators provide short status messages and are visible only
when active.
The logical address receptacle lets you select a unit address for each drive
by simply inserting the appropriate logical address plug. With each drive,
you receive eight plugs (numbered 0 through 7) from which you may select
the desired unit address, and a service plug with the letter S inscribed on its
face.

3-5

Controls and Indicators for Peripheral Devices

Figure 3-3

RP05 and RP06 Front Panel Controls and Indicators

Each address plug is a mechanical device that activates a set of address
switches corresponding to the unit address numeral inscribed on the plug
face. For example, if the plug is inscribed with the numeral 0, it will activate
a set of switches that assign the unit address 0 to the drive. If you have
multiple drives, be sure that you do not use identically numbered plugs on
drives assigned to the same controller.
The START/STOP switch is a three-position toggle switch: START, STOP,
and an unlabeled center position.
If all interlocks are satisfied and the access door is closed (DOOR LOCKED
indicator lit), you begin a powerup sequence by momentarily pressing
the switch to START. The START indicator turns on and the STANDBY
indicator turns off (assuming it was lit when you pressed the switch). As
soon as you release the switch, it returns to the center position, but the
START indicator remains on until you stop the drive. When the drive
reaches operating speed, the heads extend and read/write operations may
begin.
To stop the drive, press the switch to the STOP setting (it will remain there).
The heads retract and the drive begins to decelerate. When the drive stops,
the DOOR LOCKED indicator turns off and you may safely remove the disk
pack.

3-6

Controls and Indicators for Peripheral Devices

The WRITE PROTECT switch is a two-position rocker switch that protects
you from inadvertently overwriting the data on the disk when performing
read-only operations. When you set the switch to the WRITE PROTECT
position, the disk is protected and the WRITE PROTECT indicator turns on.
When you press it to the unlabeled "off" position, protection is removed and
the WRITE PROTECT indicator turns off.
The CONTROL A/CONTROL B switch is a three-position rocker switch
that determines whether the controller accesses the drive through port A,
port B, or through both ports. When you set the switch to CONTROL A, the
controller accesses the drive through port A, and the CONTROL A indicator
turns on. When you set the switch to CONTROL B, the controller accesses
the drive through port B, and the CONTROL B indicator turns on. If you
position the switch to the unlabeled center position, the controller may access
the drive through either port and both the CONTROL A and CONTROL B
indicators will turn on.
The lamp test switch is an unlabeled pushbutton switch used to verify the
status of the front panel indicators. Replace any indicator that fails to turn
on when you press the switch.
The START indicator turns on when you press the START/STOP switch to
the START position and remains on until you stop the drive.
The CONTROL A/B indicators indicate which ports are being used by the
controller.
The READY indicator indicates the drive is online.
The UNSAFE indicator indicates there is a drive malfunction that requires
attention.
The STANDBY indicator indicates the drive is in STANDBY mode ready
to be powered up. As soon as the drive is powered up, the STANDBY
indicator turns off and the START indicator turns on.
The WRITE PROTECT indicator indicates the disk is write protected.
The DOOR LOCKED indicator indicates the drive access door is locked and
the disk is not accessible.

3-7

Controls and Indicators for Peripheral Devices

3.4

RP07 Disk Drive
The RP07 disk drive implements fixed-head technology incorporating a
sealed-head-disk assembly to provide fast access and 516 megabytes of
storage. It connects to the MASSBUS by means of the MASSBUS controller
and provides the controller with static dual access to the drive.
The front panel controls and indicators for the RP07 include four toggle
switches and six indicators:
•

START/STOP switch

•

ON-LINE switch (not labeled) and labeled indicator

•

WRITE PROTECT switch (not labeled) and labeled indicator

•

ACCESS A, A/B, ACCESS B switch, and associated indicators

•

UNSAFE indicator

Figure 3-4 shows the locations of the controls and indicators.

Figure 3-4

RP07 Front Panel Controls and Indicators

UNSAFE

START

ON
LINE

WRITE
PROTECT

ACCESS A

A/B

STOP

ACCESS B

ZK-1954-84

The START/STOP switch is a two-position toggle switch used to bring the
head-disk assembly up to speed by setting the switch to the START position.

3-8

Controls and Indicators for Peripheral Devices

When you set the switch to the STOP position, a braking action is applied to
the head-disk assembly.
The ON-LINE switch (unlabeled) is a two-position toggle switch used to put
the drive on line, that is, to make the drive available to the processor. In
the up position, the drive is on line, and the ON-LINE indicator turns on.
Conversely, the ON-LINE indicator turns off and the drive goes off line
when the switch is in the down position.
The WRITE PROTECT switch (unlabeled) is a two-position toggle switch
used to prevent inadvertent overwriting of the disk. When the switch is in
the up position, the WRITE PROTECT indicator turns on and the media is
protected. When the switch is set to the down position, the indicator turns
off and the processor may write to the media.
The ACCESS A, A/B, ACCESS B switch is a three-position toggle switch
the controller uses to access the drive. In the ACCESS A position, the A
indicator turns on and the controller accesses the drive through port A. In
the ACCESS B position, the B indicator turns on and the controller accesses
the drive through port B. In the A/B position, both indicators turn on and
the controller can access the drive through both ports.
The UNSAFE indicator flashes when the drive logic senses a potential
problem such as an abnormal rise in temperature or insufficient air flow. If
a problem needs immediate attention, for example if a start-spindle error
occurs, the indicator lights steadily.

3.5

RM03 and RM05 Disk Drives
The RM03 and RM05 disk drives are MASSBUS devices that connect to
the processor by means of the MASSBUS controller. The RM03 has a
67-megabyte storage capacity. The RM05 has a storage capacity of 256
megabytes. Optional port selection gives the controller static, dual-port
access to each of these drives.
The front panel controls and indicators for the RM03 and RM05 include:
•

START switch and associated indicator

•

Unlabeled Drive Number receptacle

•

READY indicator

•

FAULT CLEAR switch and associated indicator

•

WRITE PROTECT switch and associated indicator

You may also choose a pair of port-selection switches that mount on the
drive cabinet door.
3-9

Controls and Indicators for Peripheral Devices

Figure 3-5 shows the locations of the controls and indicators.

Figure 3-5

RM03/RM05 Front Panel Controls and Indicators

FRONT PANEL CONTROLS AND INDICATORS

DRIVE CABINET SWITCHES
ZK-1953-84

The START switch is an alternate-action switch used to power up the
drive when the disk pack is installed, the access door is locked, and the
power supply circuits are on. If these conditions are met when you activate
the switch, the START indicator turns on and the drive spindle begins to
accelerate to operating speed.
When you activate the START switch, the READY switch flashes once a
second until the drive spindle reaches operating speed. When the drive is up
to speed and the heads are loaded, this indicator remains on steadily if no
fault conditions are detected.

3-10

Controls and Indicators for Peripheral Devices

Each drive comes with eight logical address plugs numbered 0 through 7.
You select the drive's unit address by inserting the appropriately numbered
plug into the drive select receptacle. The plugs are mechanical devices that
activate a set of switches to select the unit address that corresponds to the
number inscribed on the plug face.
The FAULT indicator turns on when one or more of the following fault
conditions are detected:
•

Write fault

•

Head select fault

•

Read/write fault

•

Read/write while off cylinder fault

•

Voltage fault

If the fault indicator lights due to a momentary fault, you can turn it off by
pressing the FAULT CLEAR switch on the front panel. If the fault indicator
stays on when you press the FAULT CLEAR switch, notify maintenance
personnel.
The write protect switch is an alternate-action switch used to protect against
unintentional overwriting of the disk pack. When you activate the switch,
the PROTECT indicator turns on and the drive write circuits are disabled.
Conversely, when you deactivate the switch, the PROTECT indicator turns
off and the controller may write to the disk pack.
If you have port selection, you use the A/B switches to manually give the
controller access to the drive through either port A, port B, or both ports.
Each switch has an associated activity indicator located directly above it.

3.6

R80 and RM80 Disk Drives
The R80 and RM80 disk drives are random-access, disk-storage systems that
implement Winchester fixed-media technology.
The RM80 is a MASSBUS device that connects to either a VAX-11/780 or
VAX-11/750 by means of the MASSBUS controller. It has a storage capacity
of 124 megabytes.
The R80 is used with VAX-11/730 systems as a system device and has a
storage capacity of 121 megabytes. The R80 connects to the UNIBUS by
means of an integrated disk controller.

3-11

Controls and Indicators for Peripheral Devices

Both the RM80 and the R80 have identical front panel controls and
indicators:
•

RUN/STOP switch and indicator

•

FAULT switch and indicator

•

Logical address receptacle and READY indicator

•

WRITE PROT switch and indicator

•

STAT 1 and STAT 2 indicators

The RM80 optionally provides two port selection switches.
Figure 3-6 gives the locations of the controls and indicators.

Figure 3-6

R80 and RM80 Front Panel Controls and Indicators

RUN
STOP

FAULT

2
READY

WRITE
PROT

STAT

FRONT PANEL CONTROLS AND INDICATORS

DRIVE CABINET SWITCHES
/K

1 Qri 1 8-1

When the drive is at rest, the RUN/STOP switch is used to start the drive
spindle accelerating to operating speed. The indicator turns on when you
press the switch and remains on until you stop the drive.
When the drive is at operating speed, the RUN/STOP switch is used to
bring the spindle to a gradual stop. When you press the switch, the drive
spindle begins to decelerate, but the RUN/STOP indicator remains on until
the spindle stops.

3-12

Controls and Indicators for Peripheral Devices

The FAULT indicator turns on when a fault is detected. When you press the
lit switch, five front panel indicators flash an error code that identifies the
faulty component.
The logical address receptacle lets you select a unit address for each drive
by simply inserting the appropriate logical address plug into the receptacle.
With each drive, you receive eight plugs (numbered 0 through 7) from which
you may select the desired unit address.
Each plug is a mechanical device that activates a set of address switches
corresponding to the unit address numeral inscribed on the plug face. For
example, if the plug is inscribed with the numeral 0, it will activate a set of
switches that assign the unit address 0 to the drive.
Each logical address plug incorporates a READY indicator that turns on
when the drive is at operating speed and remains on until you press the
RUN/STOP switch to stop the drive.
The ST AT 1 and ST AT 2, indicators together with the FAULT, READY,
and WRITE PROTECT indicators, flash an error code when you press the
FAULT switch.
The WRITE PROT switch (write protect) is an alternate-action switch that
protects you from inadvertently overwriting the disk. When the switch is
activated, the indicator turns on and the disk is write protected. Conversely,
if the switch is deactivated, the indicator turns off and the processor is
allowed to write to the disk.
The RM80 port selection switches allow two processors to share a driver,
or a single processor to access two drivers. At the driver, port access is
determined by the state of the A and B selector switches on the driver
cabinet. You activate the A switch to enable access through port A and the B
switch to enable access through port B. The A indicator turns on when port
A is being used, and the B indicator turns on when port B is being used.

3.7

RA60, RA80, and RA81 Disk Drives
The RA60, RA80, and RA81 disk drives attach to the host either by means
of a UNIBUS disk adapter (UDA) controller, or by means of a hierarchical
storage controller (HSC) and the computer interconnect (Cl). The RA60
provides a removable disk; the RA80 and RA81 implement fixed-head
media. All three drives provide port selection to make them simultaneously
accessible to two controllers.
All three drives include the following front panel controls and indicators:
•

RUN/STOP switch and indicator

•

FAULT switch and indicator
3—13

Controls and Indicators for Peripheral Devices

•

Logical address receptacle and READY indicator

•

WRITE PROT switch and indicator

•

Port selection switches and indicators

Figure 3-7 gives the locations of the controls and indicators.

Figure 3-7

RA60, RA80, and RA81 Front Panel Controls and Indicators

RUN
STOP

FAULT

READY

WRITE
PROT

ZK-2035-84

In addition to the functions described below, the indicators flash an error
code when you press the FAULT switch.
When the drive is at rest, you use the RUN/STOP switch to start the drive
accelerating to operating speed. The indicator turns on when you press the
switch and remains on until you subsequently stop the drive. You can only
gain access to the RA60 drive compartment if the RUN/STOP indicator is
turned off.
When the drive is at operating speed, the RUN/STOP switch is used to
bring the drive to a gradual stop. The drive spindle immediately begins to
decelerate but the RUN/STOP indicator remains on until the spindle stops.
The FAULT indicator turns on when a fault is detected. When you press the
lit switch, the five indicators will flash an error code that identifies the faulty
component.
The logical address receptacle lets you select a unit address for each drive by
inserting the appropriate logical address plug. With each drive, you receive
eight plugs (numbered 0 through 7) from which you may select the desired
unit address.
Each plug is a mechanical device that activates a set of address switches
corresponding to the unit address numeral inscribed on the plug face. For
example, if the plug is inscribed with the numeral 0, it will activate a set of
switches that assign the unit address 0 to the drive.
Each logical address plug incorporates a READY indicator that turns on
when the drive is at operating speed and remains on until you press the
RUN/STOP switch to bring the drive to a gradual stop.

3-14

Controls and Indicators for Peripheral Devices

The WRITE PROT switch (write protect) is an alternate-action switch that
protects you from inadvertently overwriting the disk. When the switch is
activated, the indicator lights and the disk is write protected. Conversely, if
the switch is deactivated, the indicator turns off and the processor is allowed
to write to the disk.
With dual-port capability, the port selection switches allow two processors
to share a drive, or a single processor to access two drives. When you select
a port, the associated indicator turns on.

3.8

RC25 Disk Drive
The control panel for the RC25 disk drive includes five switches with related
indicators:
•

The RUN switch and indicator

•

The WRITE PROTECT REMOVED switch and indicator

•

The WRITE PROTECT FIXED switch and indicator

•

The FAULT switch and indicator

•

The EJECT switch and indicator

Figure 3-8 shows the locations of the controls and indicators.
Figure 3-8

RC25 Control and Indicators

[imm

RC25

Writ© Protect
Run

Removed

Fixed

Fault

r~r~i
Eject

ZK-1001-82

3-15

Controls and Indicators for Peripheral Devices

The RUN switch is used either to bring the drive spindle up to operating
speed or to spin it down. Note that the drive spindle cannot be brought up
to operating speed unless the removable cartridge is in the drive.
When you press the switch to bring the spindle up to speed, the indicator
flashes as the spindle is coming up to speed and remains lit when the spindle
is at operating speed.
When you use the switch to spin down the spindle, the indicator flashes
as the spindle speed diminishes and turns off when the spindle is stopped.
Simultaneously, the EJECT indicator turns on to indicate it is safe to remove
the cartridge.
The WRITE PROTECT switches are used to write protect the appropriate
head, either the FIXED or the REMOVED. When you write protect a head,
the corresponding indicator turns on.
The FAULT indicator turns on when a fault is detected. When you press
the lit FAULT switch, the indicators flash an error code to identify the faulty
component.
The EJECT switch is used to open the cartridge receiver door when you
want to insert or extract the removable cartridge. The EJECT indicator turns
on when it is safe to open the door.

3.9

Handling Disk Cartridges and Disk Packs
This section provides instructions on how to handle disk media, including the
disk cartridges used in the RL02 and RK07 disk drives, and the large-capacity
disks.

3.9.1

Handling RL02 and RK07 Disk Cartridges
This section tells you how to load and unload disk cartridges. Refer to
Figure 3-9 and Figure 3-10 while using this procedure.
To load a cartridge into a drive:
1

Press the drive lid release bar and raise the lid.

Lift the disk cartridge by grasping the top cover handle with one hand.

While supporting the base of the protective cover with your other hand,
lower the top cover handle.

Push the handle slide to the left with your thumb while lifting the
handle. You will feel the release as the cartridge disengages from the
protective cover.

3-16

Controls and Indicators for Peripheral Devices

Figure 3-9

Figure 3-10

Disk Drive with Lid Released

Disk Cartridge

3-17

Controls and Indicators for Peripheral Devices

5 Lift the cartridge away from the protective cover and place it in the drive
shroud with the top cover handle recess facing the rear of the drive.
6 Rotate the top cover handle a few degrees clockwise and
counterclockwise to be sure the shroud locating studs are properly
seated within the cartridge housing.

7 Gently lower the top cover handle to a horizontal position so the
cartridge engages the drive spindle.
8

Place the protective cover on top of the cartridge cover.

Close the lid.

To unload the cartridge:

3.9.2

Bring the drive to rest.

Press the lid release bar and raise the lid.

Remove the protective cover from the disk top cover.

While supporting the base of the protective cover with your palm, use
the thumb of your other hand to push the cartridge handle slide to
the left and raise the handle to disengage the cartridge from the drive
spindle.

Lift the cartridge out of the shroud and place it in the protective cover.

Lower the top cover handle to secure the cartridge to the protective
cover.

Handling Disk Packs
Disk packs include three or more platters and are protected by a plastic
storage canister when you are handling them (see Figure 3-11).
The plastic storage canister includes a pack handle that is also used to
disengage the canister from the disk pack. You disengage the bottom dust
cover from the disk pack by squeezing two latching levers located beneath
the base. When the plastic canister and the dust cover are removed from the
disk pack, they cannot be mechanically coupled.
Before moving the disk pack, be sure it is secured to the plastic canister.

3-18

Figure 3-11

Disk Pack Construction

PACK HANDLE

STORAGE
CANISTER

3-19

Controls and Indicators for Peripheral Devices

3.9.2.1

Installing the Disk
Use this procedure in conjunction with Figure 3-12 to install the disk in the
disk drive.

Figure 3-12

Disk Pack Access

3-20

Controls and Indicators for Peripheral Devices

Be sure the disk drive is at rest and that it is safe to open the pack access
door (or cover) before attempting to load or unload the disk pack. (See
appropriate descriptions on controls and indicators.)
If you have to remove a disk pack before installing a replacement pack,
see the next section for instructions on how to remove a disk pack before
proceeding to install your disk pack.

3.9.2.2

Open the drive access door (or cover).

Hold the plastic canister by the handle in one hand and remove the dust
cover by squeezing the latching levers.

Carefully place the disk pack (still attached to the plastic canister) in the
drive so that it rests on the drive spindle.

Turn the handle on the plastic canister clockwise until it stops turning
easily. Do not force the handle.

Lift the plastic canister straight up from the disk pack, taking care to
avoid damaging the edges of the disks.

Place the plastic canister on the dust cover and store them in a safe place.
Note that the dust cover does not latch to the plastic canister when the
disk pack is removed.

Close the drive access door (or cover).

Removing the Disk Pack from the Drive
Use this procedure to remove the disk pack from the drive. If you need help
with any of the steps, refer to appropriate descriptions on drive controls and
indicators.
1

Stop the drive.

When it is safe to remove the disk pack, open the drive access door (or
cover).

Place the plastic canister over the the disk pack, taking care to avoid
damaging the edges of the disks.

Turn the handle on plastic canister counterclockwise two full turns. An
audible clicking sound indicates the disk is free.

Grasp the handle of the plastic canister and carefully lift the disk pack
(now attached to the plastic canister) out of the drive.

While holding the disk pack in one hand, attach the dust cover to the
pack by squeezing the latching levers on the dust cover, seating the disk
pack into the dust cover, and then releasing the latching levers.
3-21

Controls and Indicators for Peripheral Devices

3.10

Store the disk pack in a safe place, preferably on a flat shelf. Do not
stack disk packs on one another.

TS11 Tape Drive
The TS11 tape drive is used solely as a load device. It is compatible with all
VAX systems but is usually configured with the small- to mid-sized members.
The TS11 connects to the UNIBUS by means of the I/O bus and a controller.
The TS11 front panel provides two switches and six indicators for controlling
and monitoring the drive's status:
•

The LOAD/REW/UNLD (LOD in some versions) switch and indicator

•

The ON-LINE (ONL in some versions) switch and indicator

•

The MICRO OK (UOK in some versions) indicator

•

The VOL VALID (VCK in some versions) indicator

•

The DENS ERROR (DCK in some versions) indicator

•

The WRITE LOCK (WLK in some versions) indicator

•

The BOT (beginning-of-tape) indicator

•

The EOT (end-of-tape) indicator

Figure 3-13 shows the locations of the controls and indicators.

Figure 3-13

TS11 Front Panel Controls and Indicators

LOAD
REW
UNLD

ON¬
LINE

MICRO
OK

VOL
VALID

DENS
ERROR

WRITE
LOCK

BOT

EOT

1955-84

The LOAD/REW/UNLD switch has three functions depending on the
current state of the drive.
•

If you have just threaded the tape, put the switch in LOAD position to
load the tape.

•

If you are not at the beginning of the tape, put the switch in REW
position to rewind the tape.

3-22

•

If you are at the beginning of the tape, put the switch in UNLD position
to unload the tape.

The ON-LINE switch is an alternate-action switch used to bring the tape
transport on line or off line as appropriate. The indicator turns on if the
transport is on line.
The six indicators are listed below:
The MICRO OK indicator turns on only if the microprocessor-controlled
formatter is operating without errors.
The VOL VALID indicator turns on to alert you to a change in the status of
the tape transport; that is, it turns on if the transport has changed from on
line to off line, or vice versa, since the last processor command.
The DENS ERROR indicator turns on if an invalid identification burst is
sensed at BOT (beginning-of-tape). This usually indicates that a phase¬
encoding error has probably occurred and that the tape data is invalid.
The WRITE LOCK indicator turns on if you place a tape reel on the
transport that does not have a write-protect ring on it.
The BOT indicator turns on when the beginning of the tape is sensed.
The EOT indicator turns on when the end of the tape is sensed.

3.11

TE16 Tape Drive
The TE16 tape drive is used solely as a load device. It is configured with
MASSBUS systems only and connects to the processor by means of the
MASSBUS and the MASSBUS adapter.
The TE16 front panel provides four indicators, a transport select receptacle,
and three switches.
•

The PWR (power) indicator

•

The BOT (beginning of tape) indicator

•

The WRL (write lock) indicator

•

The SELECT indicator

•

The TRANSPORT SELECT (unlabeled) receptacle

•

The LOAD switch and indicator

•

The ON LINE switch and indicator

•

The REW/UNLD (rewind/unload) switch

3-23

Controls and Indicators for Peripheral Devices

Figure 3-14 shows the locations of the controls and indicators.

Figure 3-14

TE16 Front Panel Controls and Indicators

PWR
LOAD

BOT

WRL
i=i

ON LINE
n~]

SELECT

REW/UNLD

0
READY

The PWR indicator turns on when power is applied to the transport.
The BOT indicator turns on when the beginning of the tape is sensed.
The WRL indicator turns on if you place a tape reel on the transport that
does not have a write-protect ring on it.
The SELECT indicator indicates which transport the processor has selected.

3-24

Controls and Indicators for Peripheral Devices

The TRANSPORT SELECT receptacle is used to assign a unit number (from
0 through 7) to a transport by receiving the appropriate unit-number plug.
Each TE16 includes eight unit-number plugs, and you may not assign the
same unit number to more than one transport on a formatter.
After you have threaded the tape onto the transport, pressing the LOAD
switch causes the transport to load the tape and turn on the indicator.
The ON LINE switch is an alternate-action switch used either to put the
transport on line or to take it off line. The indicator turns on only when the
transport is on line.
The REW/UNLD switch is used either to rewind (REW position) the tape; or
if the tape is at BOT, to unload (UNLD position) it.

3.12

TU77 Tape Drive
The TU77 tape drive is used solely as a load device. It is configured with
MASSBUS systems only and connects to the processor by means of the
MASSBUS and the MASSBUS adapter.
The TU77 front panel provides a transport select control, four switches, and
seven indicators.
•

TRANSPORT SELECT (unlabeled) thumbwheel control and indicator

•

LOAD/REW (load/rewind) switch

•

ON LINE switch

•

UNLOAD switch

•

RESET switch

•

POWER indicator

•

BOT (beginning of tape) indicator

•

ON LINE indicator

•

FILE PROTECT indicator

•

LOAD FAULT indicator

•

Two tape density indicators (800/1600)

Figure 3-15 shows the locations of the controls and indicators.

3-25

Controls and Indicators for Peripheral Devices

Figure 3-15

TU77 Front Panel Controls and Indicators

bot O
LOAD REW

(^)

□□□
on line O

file protect

load fault Q

800

1600

TU77

ZK-1957-84

The transport select control is a thumbwheel used to assign a unit address
to the tape drive. As you turn the thumbwheel, your selection is visible
through an adjoining window in the front panel.
After you have threaded the tape onto the transport, putting the LOAD
/REW switch in the LOAD position causes the transport to load the tape.
When the tape is loaded, putting the switch in the REW position rewinds the
tape to BOT (beginning of tape).
The ON LINE switch is an alternate-action switch used either to put the
transport on line or take it off line.
The UNLOAD switch is operable only when the tape drive is off line. When
you press the UNLOAD switch, the transport rewinds and then unloads the
tape.
The RESET switch is used to take the tape transport off line and turn off the
LOAD FAULT indicator if it is lit.
The POWER indicator turns on when power is applied to the transport.
The BOT indicator turns on when the beginning of the tape is sensed.
The ON LINE indicator turns on when the transport is on line.
The FILE PROTECT indicator turns on if the tape reel on the transport does
not have a write-protect ring on it.
The SELECT indicator indicates which transport the processor has selected.
The LOAD FAULT indicator indicates the automatic tape loading
mechanism tried to load the tape twice and failed.
The 800 indicator turns on when the transport is set to read or write at 800
bpi.

3-26

Controls and Indicators for Peripheral Devices

The 1600 indicator turns on when the transport is set to read or write at 1600
bpi.

3.13

TU78 Tape Drive
The TU78 tape storage system is used solely as a load device. It is configured
with MASSBUS systems only and connects to the processor by means of the
MASSBUS and the MASSBUS adapter. The TU78 features static dual-port
access that gives two processors access to the TU78 or the TU78 access to a
processor through two ports.
The TU78 front panel provides a transport select control, four switches, and
seven indicators.
•

PORT SELECT thumbwheel control and indicator

•

LOAD/REW (load/rewind) switch

•

ON LINE switch

•

UNLOAD switch

•

RESET switch

•

POWER indicator

•

BOT (beginning of tape) indicator

•

ON LINE indicator

•

FILE PROTECT indicator

•

LOAD FAULT indicator

•

Two tape density indicators (6250/1600)

Figure 3-16 shows the locations of the controls and indicators.
Figure 3-16

TU78 Front Panel Controls and Indicators

3-27

Controls and Indicators for Peripheral Devices

The port selection control is a thumbwheel control used to determine port
selection for the TU78:

MASSBUS port A is selected.

MASSBUS port B is selected.

Both MASSBUS ports are selected.

Neither MASSBUS port is selected.

When the tape is threaded on the transport, pressing the LOAD/REW
switch causes the transport to load and rewind the tape. When the tape has
rewound, the BOT light turns on.
The ON LINE switch is an alternate-action switch used either to put the
transport on line or to take it off line.
The UNLOAD switch is operable only when the tape drive is off line. When
you press the UNLOAD switch, the transport rewinds and unloads the tape.
The RESET switchtakes the tape transport off line and turns off the LOAD
FAULT indicator if it is lit.
The POWER indicator turns on when power is applied to the transport.
The BOT indicator turns on when the beginning of the tape is sensed.
The ON LINE indicator turns on when the transport is on line.
The FILE PROTECT indicator turns on if the tape reel on the transport has
no write-protect ring.
The LOAD FAULT indicator turns on when the automatic tape loading
mechanism fails twice to load the tape.
The 6250 indicator turns on when the transport is set to read or write at 6250
bpi.
The 1600 indicator turns on when the transport is set to read or write at 1600
bpi.

3-28

3.14

TU80 and TU81 Tape Drives
The TU80 and TU81 tape storage systems are used solely as load devices
during an installation. In postinstallation operations, these systems are used
primarily for disk backup.
The TU80 and TU81 tape systems are very similar, as they are both UNIBUS
devices. The primary difference is that the TU81, which is the first tape drive
supported by DSA software protocol, has a higher storage density and higher
data transfer rates than the TU80.
The front panels for both tape drives are virtually the same. Both front
panels are partitioned into three sections:
•

Operator controls and indicators

•

Maintenance controls and indicators

•

Special controls and indicators

Figure 3-17 shows the locations of the front panel controls and indicators.
Figure 3-17

TU80 and TU81 Front Panel Controls and Indicators

MAINTENANCE

INDICATOR
PUSHBUTTON

OPERATOR
ZK-2075-84

This description is limited to indicators and controls used in routinely
operating and monitoring the tape system.
•

FILE PRO (file protect) indicator

•

LOGIC ON switch and indicator

•

LOGIC OFF switch and indicator
3-29

•

BOT (beginning of tape) indicator

•

LOAD/REWIND switch

•

UNLOAD switch

•

SELECT indicator

•

ON LINE switch and indicator

•

RESET switch and indicator

The FILE PRO indicator turns on when the write-protect ring is missing and
writing is not allowed.
The LOGIC OFF switch is used to take power from the system. The
indicator turns on to indicate main power is applied but subassembly power
is removed.
The LOGIC ON switch is used to make the tape system ready for operation.
When the system is operational, the indicator turns on.
The BOT indicator turns on at the beginning of the tape.
The LOAD/REWIND switch is used to load the tape when the transport is
powered on and the tape is threaded. When the tape is loaded, this switch is
used to rewind the tape.
The UNLOAD switch is used to unload the tape onto the supply reel when
tape is at BOT or when it is threaded but not loaded. If the tape is loaded
but is beyond BOT, this switch is used to rewind the tape.
The ON-LINE switch is used to make the tape accessible to the host system
and to turn on the indicator. Press the RESET switch to take the system off
line.
The SELECT indicator turns on when the host system is doing group code
recording (GCR) operations with the tape drive.
The RESET switch is used to take the transport off line, to stop the tape and
clear the error state, to turn off the RESET indicator and clear a diagnostic
test condition and to stop LOAD or REWIND operations. The indicator turns
on if a fault is detected or if the system is in a diagnostic state.

3-30

3.15

HSC50 and HSC70 Controllers
The HSC50 and HSC70 controllers (hierarchical storage controller) provide
one or more host computers with access to a set of mass storage devices by
means of the computer interconnect (Cl) and the star coupler. Each controller
can support a mix of Disk Storage Architecture (DSA) disk devices (RA60,
RA80, and RA81) and the TA78 tape system.
The operator control panel (OCP) of the HSC50 and HSC70 controllers is
illustrated in Figure 3-18.

Figure 3-18

Operator Control Panel Controls and/indicators

MOMENTARY
CONTACT
SWITCH

IN/OUT
SWITCH

ZK-2076-84

•

STATE indicator

•

POWER indicator

•

INIT (initialize) switch and indicator

•

FAULT switch and indicator

•

ONLINE switch and indicator

•

Two blank indicators

An internal SECURE/ENABLE switch provides security against activating the
OCP controls inadvertently. The OCP controls are disabled when the switch
is positioned at SECURE.
3-31

The STATE indicator turns on when the initialization sequence is completed.
It remains lit for several minutes during the early stages of the bootstrap
diagnostic tests and then flashes at half-second intervals for the rest of
the bootstrap process. When the bootstrap process completes, the STATE
indicator flashing rate reduces to one-second intervals and the STATE
indicator continues to flash at this rate during normal operations.
The POWER indicator turns on when power is applied to the HSC. It
remains lit if all DC voltages are at the correct level and AC power is present.
The INIT switch is a momentary-contact switch used to initialize and
boot the HSC. When you press the INIT switch, the indicator turns on
and remains on during the initialization sequence. When the initialization
sequence is completed, the INIT indicator turns off and the STATE indicator
turns on.
The FAULT indicator turns on when a significant problem is detected in the
HSC.
The FAULT switch is used to test the operator control panel (OCP) indicator
lamps and to determine the nature of detected faults.
If the FAULT indicator is not lit (no fault present), the switch may be used to
test the condition of the indicators. If any indicator does not turn on, notify
maintenance personnel.
If the FAULT indicator is lit (fault is present) when you press the switch,
the OCP indicators will flash a five-bit code that identifies the problem. If
more than one fault condition exists, pressing the FAULT switch causes the
appropriate fault codes to flash. See the HSC User Guide for an explanation
of these 5-bit codes.
To determine the effect of a fault on the operational state of the HSC, press
the FAULT switch a second time. If the HSC is not operating, the fault code
continues to flash. If the HSC is operating, the FAULT indicator turns off
and the other indicators return to their normal state.
The ONLINE switch is a two-position switch that enables the HSC to make
connection with other nodes on the Cl. See the HSC User Guide for additional
control settings to put the HSC on line.
When the switch is in the active position (IN), the HSC is able to connect
with host computers on the Cl. The ONLINE indicator turns on when the
first connection is made and remains on until all connections are terminated
even if you deactivate the ONLINE switch.
When you deactivate the switch (OUT position), the HSC is not allowed
to make any further connections with nodes on the Cl; however, existing
connections are maintained and the HSC is still on line.

3-32

If the ONLINE indicator is not lit (indicating no host computer connections)
when the switch is deactivated, the HSC immediately goes off line.
The two blank indicators are used to provide the two least significant bits in
the OCP fault codes.

3-33

Support Information

The software installation booklets provide a step-by-step approach to
installing a new VAX/VMS system under 17 scenarios. This chapter supports
the booklets with additional details.

4.1

Logging In to the System
When you boot the system, it announces itself with a message such as the
following:
VAX/VMS Version 4.4 15-APR-1986 12:00
'/.OPCOM, 16-APR-1986 16:36:29.58, logfile initialized by operator 0PA0
log file is SYS$MANAGER:OPERATOR.LOG
Login quotas - Interactive limit=64. Current Interactive value=0
SYSTEM job terminated at 16-APR-1986 16:36;31.41

Perform the following steps to log in to the system as the system manager.
When you log in, make your entries quickly and accurately. The security
features of the system may disable login if you make too many mistakes or if
you take too much time. If you make a mistake, press the RETURN key to
start the login procedure again.
1

Press the RETURN key on the console terminal.

When the system prompts you for your user name, type SYSTEM and
press RETURN.
USERNAME:

SYSTEM

When the system prompts for your password, type it and press RETURN.
Note that the password will not echo, that is, you will not see the
password displayed on the screen as you enter it.

When you type the proper password, the system prints the following
message on the console terminal:
Welcome to VAX/VMS Version 4.4.

You may start to use the system when the console terminal prints the dollar
sign prompt ($).

4-1

4.2

Booting During Installation
At various points in the installation procedure, you must boot software into
memory from a storage device, either a console storage device (RL02, TU58
or diskette) or a disk. For example, you begin the installation by booting
standalone BACKUP into memory so that you can do a partial restoration of
the operating system. Then you boot the partially restored operating system
into memory so that you can restore the remaining system files. Finally,
when the entire operating system has been restored, you boot it into memory
from the system disk.

4.2.1

Booting VAX Processors
All booting is done in console mode, that is, under the direction of the
console program. On the VAX-11/725, the VAX-11/730 VAX-11/750 and
the VAX 8200, you put the system into console mode and halt the CPU by
pressing CTRL/P on the console terminal keyboard. On the VAX-11/780,
VAX-11/782, VAX-11/785, VAX 8600, and VAX 8650, CTRL/P puts the
system in console mode, but you must use the console command F1ALT to
halt the CPU.
The system indicates it is in console mode by displaying the console prompt
(> > > ) on the console terminal.
With the system in console mode, you boot software from a device by typing
the word BOOT (or simply the letter B) followed by the abbreviated name of
the boot command procedure for the particular device.
Upon completion of the boot, the console program automatically returns the
system to program mode.
If you have a VAX 8200 or a VAX-11/750, you may boot software in one of
two ways:
•

Directly from the system disk

•

Indirectly using the standalone BOOT58 program on the console volume

It is best to boot directly from the system disk; use the BOOT58 program
only if you cannot boot directly from the disk.
If you have a VAX 8200, type the following command to boot directly from
the system disk:
>>> B DUnu

where the variable n refers to the VAXBI node identification number and the
variable u to the device unit number. See Section 4.4 for more information
about device names.
4-2

For all other types of processors, type the following boot command instead:
»> B ddcu

where ddcu is the device name of the system disk. See Section 4.4 for more
information about device names. For example, if the system disk is the first
RK07 on controller A, enter the following boot command:
»> B DMAO

On a VAX-11/750, you may also boot directly from the system disk by
assigning the system disk a position on the BOOT DEVICE switch. When the
BOOT DEVICE switch is set at this position, set the POWER ON ACTION
switch to BOOT to boot your system disk.
You should use BOOT58 only when you cannot boot directly from the disk.
The most common reason for being unable to do so is because the boot block
on the disk has been corrupted.
Use the following procedure to obtain the BOOT58> prompt on a VAX
8200:
1

Insert the console volume diskette into the console drive (CSA1).

Set the upper keylock switch on the processor control panel Enable.

Set the lower keylock switch on the processor control panel Halt.

Press CTRL/P to obtain the console program prompt.

Type the following BOOT command:
»> B/R5 :800 CSA1

Use the following procedure to obtain the BOOT58> prompt on a VAX-11
/750:
1

Insert the console volume tape cartridge into the console drive (CSA1).

Set the keylock switch on the processor control panel to LOCAL.

Set the POWER ON ACTION switch to HALT.

Press CTRL/P to obtain the console program prompt.

Type the following BOOT command:
»> B/800 DDAO

4-3

When you get the BOOT58 prompt, enter the name of the applicable boot
command procedure.
B00T58> (BDxyB00.CMD

Indicates that the rest of the line contains the name of a command
procedure.

A letter that indicates the type of disk drive holding the system disk. For
example, the letter U indicates either an RA80 or RA81 disk drive (see
Table 4-1).

A number that specifies the unit number of the disk drive holding the
system disk.

You may use the following short form of the previously specified command
enter the name of the appropriate desired boot command procedure:
B00T58> BOOT Dxy

Either method of specifying the desired boot command procedure can be
used. For example, to boot from the first RA80 on controller A, use either of
these BOOT58 command forms:
B00T58> ODUOBOO.CMD
B00T58> BOOT DUO

See the VAX/VMS System Manager's Reference Manual for more information
on using the BOOT58 program.

4.3

Booting from HSC Disks
The way in which you boot an HSC disk is in part dependent on the type of
VAX processor you are using. If you have a VAX 8200 or a VAX-11/750, use
the BOOT58 utility; if you have any other VAX/VMS system, use console
mode commands.
If you want to use a nonstop boot or are installing a new system, you use
the CIBOO.CMD command procedure (named CIBOO.COM on a VAX 8600
system); if you want to change system parameters during the boot, you
use the CIGEN command procedure. In either case, you must provide the
selected boot command file with two pieces of information before you use it
to boot the disk: the unit number of the disk drive and the node numbers of
the HSCs controlling it.
Furthermore, if you want to boot from a system root other than SYSO, you
must identify the root. Note however that when installing a system, you
boot from SYSO. See the VAX/VMS System Manager's Reference Manual for
more information on booting from alternate system roots and see Chapter 6
of this manual for details on creating alternate roots.
4—4

The way you provide the information to the Cl boot command procedure
depends on whether you have a running system or are installing a new
system.
If you have a running system, you can copy the Cl boot command file from
the console volume to a disk directory, edit it, and copy the edited version
back to the console volume. If you want to use the Cl boot command
file as your default boot command procedure, copy the edited version to
DEFBOO.CMD (named DEFBOO.COM on the VAX 8600) on the console
volume. See the VAX/VMS System Manager's Reference Manual for details.
If you are installing a new system, you will have to use console commands
(BOOT58 commands if you have a VAX 8200 or a VAX-11/750) to deposit
the information in the appropriate registers. Note that the form of the
DEPOSIT command varies for different VAX processors.
The following sections describe these scenarios for booting HSC disks:

4.3.1

•

booting a VAX 8200 during an installation

•

booting a running VAX 8200

•

booting a VAX 8600 during an installation

•

booting a running VAX 8600

•

booting a VAX-11/780 during an installation

•

booting a running VAX-11/780

•

booting a VAX-11/750 during an installation

•

booting a running VAX-11/750

Booting a VAX 8600 or a VAX—11/780 During an Installation
This section describes the steps for booting an HSC disk on a VAX 8600 or a
VAX-11/780 while installing a new operating system.
1

Determine the unit number of the HSC disk and the node number of the
HSC controlling it.

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

Use the console HALT command to stop the processor.

When you get the console prompt (> > > ), deposit the HSC node
number into R2 using the following command format. Note that all
numeric entries are made using hexadecimal notation.
»> DEPOSIT R2 node_number

4-5

For example, if the HSC is node number 12 (hexadecimal OC) on the
CI780, use this command:
»> DEPOSIT R2 OC

If the disk device is accessible to two HSCs, deposit both node numbers
in hexadecimal values putting the larger number in hex digits 3 and 2,
and the lesser in digits 1 and 0. For example, if one FISC is numbered 15
(hex OF) and the other is numbered 10 (hex 0A), the proper command is
»> DEPOSIT R2 OFOA

Deposit the unit number of the HSC disk into R3 using a command in
the following format:
»> DEPOSIT R3 unit_number

For example, if the HSC disk is unit number 21, deposit a hexadecimal
15 into R3:
»> DEPOSIT R3 15

Boot the HSC disk with this command:
»> (DCIB00.CMD

4.3.2

Booting a Running VAX 8600 or a VAX-11/780
This section describes how to set up DEFBOO.CMD for a nonstop system
boot of an HSC disk on a VAX 8600 or a VAX-11/780 system that is up and
running the VAX/VMS operating system. In this example, the HSC device is
an RA60 disk drive assigned unit number 03 on an HSC controller assigned
node number 12 (hexadecimal OC). The example assumes the user wants to
boot the system from alternate root SYSA.
1

Be sure your console drive is connected. If it is not, invoke the System
Generation Utility (SYSGEN) to connect it, as follows:
$ RUN SYS$SYSTEM:SYSGEN
SYSGEN> CONNECT CONSOLE
SYSGEN> EXIT

Mount the console volume as a foreign volume:
$ MOUNT/FOREIGN CSA1:

Copy CIBOO.CMD (CIBOO.COM on a VAX 8600) to your default disk
directory.
$ EXCHANGE COPY CSA1:CIB00.CMD *.*

4-6

Support Information

4 Edit the disk file in your default directory as shown in the following
example. The first line you add deposits the HSC node number in R2,
and the second line you add deposits the HSC disk's unit number in R3.
To set the system root at SYS A, edit the line commented as software boot
control flags by changing the most significant digit in R5 to the letter
A. This digit determines the system root for system disks with multiple
systems.
Note that all numeric entries are made using hexadecimal notation.

DEPOSIT RO 20

!Cl PORT DEVICE

DEPOSIT R1 E

!Cl TR=E

DEPOSIT R2 OC

!HSC NODE NUMBER

DEPOSIT R3 03

!DEVICE UNIT NUMBER
!BOOT BLOCK LBN

DEPOSIT R4 0
DEPOSIT R5 A0004000

If the disk is dual-ported (accessible to two HSC controllers), you must
specify the node numbers of both controllers in R2. Further, you must
specify the higher-numbered node in bits <15:8> and the lowernumbered node in bits < 7:0> . For example, if the disk is accessible
to the HSC numbered OC and the HSC numbered OA, the line for R2
should appear like this:
DEPOSIT R2 0C0A

(NOT USED)

!DESIGNATED ROOT IS SYSA

!DUAL-PORTED HSC NODE NUMBERS

Copy the edited boot command file to the default boot command
procedure DEFBOO.CMD (DEFBOO.COM on a VAX 8600) on your
console volume.
$ EXCHANGE COPY device:[directory]CIBOO.CMD CSA1:DEFBOO.CMD

You should provide another copy of this file in case DEFBOO.CMD
(DEFBOO.COM on a VAX 8600) is overwritten. Use the same command,
but provide a distinctive file name for the other file.

Shut down the system.
$ <DSYS$SYSTEM: SHUTDOWN

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

Use the HALT command to stop the processor.

1 0 Boot the HSC disk by invoking the default boot command procedure:
»> B

4-7

Support Information

4.3.3

Booting a VAX 8200 or a VAX—11 /750 During an Installation
This section describes how to boot an HSC disk on a VAX 8200 or a VAX-11
/750 while installing a new operating system.

On a VAX 8200, set the upper keylock switch to Enable and the lower
keylock switch to Halt. On a VAX-11/750, set the BOOT SELECT
switch on the processor control panel to position A.

Determine the unit number of the HSC disk and the node number of the
HSC controlling it.

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

On a VAX 8200, type this command to invoke BOOT58:
»> B/R5 :800 CSA1

On a VAX-11/750, type this command to invoke BOOT58:
»> B/800 DDA0

If you fail to add the /800 qualifier, the console program will try to
execute DEFBOO.CMD.
6

On a VAX 8200, type the following command to deposit the VAXBI node
number into register Rl.
B00T58> D/G 1 node-number

For example, if the VAXBI node number is 06, you use this command:
B00T58> D/G 1 06

Type the following command to deposit the HSC node number into
register R2.
B00T58> D/G 2 node_number

Note that all numeric entries are made using hexadecimal notation. For
example, if the HSC is node number 12 (hexadecimal OC) on the CI750,
you use this command:
B00T58> D/G 2 0C

If the load device is accessible to two HSCs, deposit both node numbers
in hexadecimal digits putting the larger number in hexadecimal digits
3 and 2, and the lesser in digits 1 and 0. For example, if one HSC
is numbered 15 (hexadecimal OF) and the other is numbered 10
(hexadecimal 0A), the proper command is this:
B00T58> D/G 2 OFOA

4-8

Deposit the unit number of the load device into R3.
B00T58> D/G 3 unit_number

For example, if the load device is unit number 21, deposit a hexadecimal
15 into R3:
B00T58> D/G 3 15

10 Type the following command to boot the HSC disk.
B00T58> OCIBOO.CMD

4.3.4

Booting on a Running VAX 8200 or a VAX—11/750
This section describes how to set up DEFBOO.CMD to do a nonstop system
boot of an HSC disk on a VAX 8200 or a VAX-11/750 system that is up and
running the VAX/VMS operating system. In this example, the HSC device is
an RA60 disk drive assigned unit number 03 on an HSC controller assigned
node number 12 (hexadecimal 0C). The example assumes the user wants to
boot the system from alternate root SYSA.
1

On a VAX 8200, set the upper keylock switch to Enable and the lower
keylock switch to AUTO START. On a VAX-11/750, set the BOOT
SELECT switch to position A.

Be sure your console drive is connected. If it is not, invoke the System
Generation Utility (SYSGEN) to connect it, as follows:
$ RUN SYS$SYSTEM:SYSGEN
SYSGEN> CONNECT CONSOLE
SYSGEN> EXIT

Mount the console volume as a foreign volume:
$ MOUNT/FOREIGN CSA1:

Copy CIBOO.CMD to your default disk directory.
$ EXCHANGE COPY CSA1:CIB00.CMD *.*

Edit the disk file in your default directory. The first line you add deposits
the HSC node number in register R2, and the second line you add
deposits the HSC disk's unit number in register R3.
To set the system root at SYSA, you edit the line commented as software
boot control flags by changing the most significant digit in register R5 to
the letter A. This digit determines the system root for system disks with
multiple systems.

4-9

Note that all numeric entries are made using hexadecimal notation.

D/G RO 20
D/G R1 E
D/G R2 0C
D/G R3 03
D/G R4 0
D/G R5 A0004000

If the disk is dual ported (accessible to two HSC controllers), you must
specify the node number of both controllers in R2. Further, you must
specify the higher-numbered node in bits < 15:8> and the lowernumbered node in bits < 7:0> . For example, if the disk is accessible
to the HSC numbered 12 (hexadecimal OC) and the HSC numbered 10
(hexadecimal OA), the line for R2 should appear like this:
D/G R2 0C0A

!Cl PORT DEVICE
!Cl TR=E
!HSC NODE NUMBER
!DEVICE UNIT NUMBER
!BOOT BLOCK LBN (NOT USED)
!SOFTWARE BOOT CONTROL FLAGS

!DUAL PORTED HSC NODE NUMBERS

Copy the edited boot command to the default boot command procedure
(DEFBOO.CMD) on your console volume.
$ EXCHANGE COPY device:[directory]CIB00.CMD CSA1:DEFB00.CMD

You should provide another copy of this file in case DEFBOO.CMD is
overwritten. Use the same command, but provide a distinctive file name
for the other file.
8

Write the boot block on the console volume using the WRITEBOOT
Utility.
a

Invoke WRITEBOOT.
$ RUN SYS$SYSTEM:WRITEBOOT

When WRITEBOOT asks for the target device, make the following
entry:
Target system device (and boot file if not VMB.EXE):? CSAliB00T58.EXE

In response to the next question, enter the number 1:
Enter VBN of boot file code (default is one):

When you are asked for the address of the primary bootstrap, enter
Enter load address of primary bootstrap in HEX (default is 200): C000

4-10

Shut down the system.
$ ®SYS$SYSTEM:SHUTDOWN

10 Press CTRL/P to put the system in console mode.
11 The following command boots the HSC disk (using the DEFBOO.CMD
command procedure that you have set up in this section):
»> B

4.4

Naming Devices
When you install software on a VAX processor, you are concerned primarily
with two devices—the load device and the system device. The load device
is the drive that holds the distribution media; it may be either a magnetic
tape drive or a disk drive. The system device is the disk drive that holds the
system disk.
In addition to these devices, you may have to use the block storage device
that is part of your console subsystem. The block storage device is used to
hold standalone BACKUP when you install a system from magnetic tape. It
is also used to hold the distribution media when you install updates or add
optional products to your system. For example, the mandatory update is
installed from the block storage device.
When you install software, you must provide the procedure with device
names. For example, you have to specify the device names of the load
device and the system device when you restore the required save set. The
installation procedure also prompts you for the name of the load device
when it is ready to restore the rest of the operating system. You also use the
device name, or a modified version of it, to bootstrap software from a device
other than the default device.
As you do the installations, references to the device name appear in the
format ddcu. This format is described in the following table:

4-11

A two-letter code that represents the device type. For example, an
RK07 disk drive is device type DM, an RA60 disk drive is device type
DJ, and a TE16 magnetic tape drive is device type MT. Table 4-1 lists
all the device codes.

A one-letter code that represents the hardware controller for the device.
Controllers provide the interface for the various devices that connect to
the processor. Specifically, the first controller on a bus is designated the
A controller, the next is the B controller, and so forth. For example, if
you are installing Version 4.4 on a system configured with dual-RA60
disk drives attached to UDA controller A, the distribution disk might
be mounted on device DJA1, and the new system volume mounted on
DJAO.

A number that represents the unit address of the drive. The first drive
on a controller is usually assigned unit address 0 and each succeeding
drive is assigned the next higher unit address, 1, 2, and so forth.
However, this is not a constraint and you are permitted to assign
unit numbers as needed. You are limited to the range of acceptable
unit numbers for a device. For example, most MASSBUS disks may
be assigned unit numbers in the range 0 to 7, but UDA-supported
disks may have unit numbers in the range 0 through 255. For installation
purposes however, unit numbers are limited by the set of boot command
procedures on your console media.
«

To assign a unit number to a device, simply insert the appropriately inscribed
logical address plug. (See Chapter 3 for details on the use of logical address
plugs.)
Table 4-1 presents the device codes for all the devices you use in doing
installations and upgrades. Note that you must use device code DB when
booting a devices coded as DR.

Table 4-1

Device Codes
Code

Device

Console storage devices (RL02, RX01, RX50 or TU58)

RC25 disk drive

RP05 and RP06 disk drives

Console storage device (TU58 on VAX-11/750 only)

RL02 disk drive on VAX-11/750

RK06 and RK07 disk drives

RL02 and R80 disk drives on VAX-11/730

4-12

Support Information

Table 4-1 (Cont.)

Device Codes

Code

Device

RM03, RM05, RM80, and RP07 disk drives

RA60 disk drive

RA80 and RA81 disk drives

TU78 magnetic tape drive

TS1 1 and TU80 magnetic tape drives

TE16, TU45 and TU77 magnetic tape drives

TA81 and TU81 magnetic tape drives

The only part of the name you can readily modify is the unit number. The
device type is fixed and the controller determination is made when the
hardware is installed.
Some examples of device names are presented below.

Device

Name

Second RK07 disk drive on UNIBUS controller A

DMA1

First TE16 magnetic tape on MASSBUS controller A

MTAO

Eighth RA81 disk on UDA controller A

DUA7

For all VAX systems except the VAX-11/750, omit the controller designation
when you specify the boot command procedure for a particular device. For
example, if you have a VAX-11/780 and you want to boot the operating
system from the first RP06 disk drive MASSBUS controller A, you would use
the format ddu as shown in the following example:
»> B DBO

Here, the device type is specified as DB and the unit address is 0. The
console subsystem program uses this code to invoke the appropriate boot
command procedure. In this example, the primary bootstrap program
converts DBO to DBOBOO.CMD (named DBOBOO.COM on the VAX 8600)
and then calls the command procedure.

4-13

Support Information

4.4.1

Boot Names for the VAX-11 /785
The names used to invoke bootstrap command files on the VAX-11/785 are
somewhat different from other VAX processors. You may use one of three
forms to invoke a boot command file on the VAX-11/785.
The first form specifies the device type and the unit.
»> B ddu

The invoked boot command procedure includes a default controller value of
A (first controller on the bus) and the unit number you specify. For example,
assume you use this command:
»> B DM5

The sixth RK07 on the A controller will be booted.
The second form provides the device type and controller designations, but
omits the device's unit designation:
»> B ddc

Here, the invoked boot command procedure takes the controller literal you
provide, but before you use this form you must deposit the unit number of
the disk in R3. You do this by using a console DEPOSIT command of this
form:
>» DEPOSIT R3 unit.number

For example, if you want to boot from an RP06 on controller C that is
assigned unit number 3, you would use this sequence of commands:
»> DEPOSIT R3 3
»> B DBC

The third form provides neither the controller nor the unit designations:
»> B dd

The invoked boot command procedure includes a default controller value of
A (first controller on the bus) and the a default unit number of 0 (first unit
on the controller). For example, if you want to boot from the first disk drive
on the UDA, you could use this command:
»> B DU

4—14

4.4.2

Boot Names for the VAX—11 /750
Boot names for the VAX-11/750 require both the controller designation and
the unit number.
»> B ddcu

For example, if you want to boot the system from the third drive on the first
UDA, you might use this command:
»> B DUA2

4.4.3

VAX 8600 Device Names
Device codes for VAX 8600 installations (including VAX 8650) are listed in
Table 4-2. Note that you use device code DB when booting a device coded
as DR.

Table 4-2

VAX 8600 Device Codes
Code

Device

Console storage device (RL02)

RP05 and RP06 disk drives

RM03, RM05, RM80, and RP07 disk drives

RK07 disk drive

RA60 disk drive

RA80 and RA81 disk drives

TU78 magnetic tape drive

TS1 1 and TU80 magnetic tape drives

TE16, TU45 and TU77 magnetic tape drives

TA81 and TU81 magnetic tape drive

All the tape drives and the RL02 console disk drive are used solely as load
devices. The RK07 and the RA60 may be used either as load devices or as
system devices depending on system configuration. All of the other disk
drives are used solely as system devices.

4-15

4.4.4

VAX 8200 Device Names
Device codes for VAX 8200 installations are listed in Table 4-3. Note that
you use the device code DU when you boot from an RA60 disk.

Table 4-3

VAX 8200 Device Codes
Code

Device

Console storage device (RX50)

RA60 disk drive

RA80 and RA81 disk drives

TU80 magnetic tape drive

TA81 and TU81 magnetic tape drive

All the tape drives and the RX50 console diskette drives are used solely as
load devices. The RA60 may be used either as a load device or as a system
device depending on system configuration. All of the other disk drives are
used solely as system devices.

4.4.5

VAX-11/780 Device Names
Device codes for VAX-11/780 installations (including VAX-11/785) are
listed in Table 4-4. Note that you use device code DB when booting a device
coded as DR.

Table 4-4

VAX-11 /780 Device Codes
Code

Device

Console storage device (RX01)

RP05 and RP06 disk drives

RM03, RM05, RM80, and RP07 disk drives

RK07 disk drive

RA60 disk drive

RA80 and RA81 disk drives

TU78 magnetic tape drive

4-16

Support Information

Table 4-4 (Cont.)

VAX—11/780 Device Codes

Code

Device

TS11 and TU80 magnetic tape drives

TE16, TU45 and TU77 magnetic tape drives

TA81 and TU81 magnetic tape drive

All the tape drives and the floppy diskette drive are used solely as load
devices. The RK07 and the RA60 may be used either as load devices or as
system devices depending on system configuration. All of the other disk
drives are used solely as system devices.

4.4.6

VAX-11/750 Device Names
Table 4-5 lists the device codes that may be applicable when installing
various VAX-11/750 system configurations. Note that you use device code
DB when booting a device coded as DR.

Table 4-5

VAX- 11/750 Device Codes
Code

Device

RP05 and RP06 disk drives

TU58 cassette drive

RL02 disk drive

RK07 disk drive

RM03, RM05, RM80, and RP07 disk drive

RA60 disk drive

RA80 and RA81 disk drives

TA78 and TU78 magnetic tape drives

TS1 1 and TU80 magnetic tape drives

TE16, TU45, and TU77 magnetic tape drives

TA81 and TU81 magnetic tape drive

All of the tape drives and the RL02 disk drive are used solely as load devices.
The RK07 and the RA60 may be used either as load devices or as system
devices depending on system configuration. All of the other disk drives are
used solely as system devices.

4-17

Support Information

4.4.7

VAX-11/730 Device Names
Table 4-6 lists the device codes that may be applicable to the installation of
various VAX-11/730 system configurations.

Table 4-6

VAX-11/730 Device Codes
Code

Device

Console storage device (TU58)

RL02 and R80 disk drives

RA60 disk drive

RA80 and RA81 disk drives

TS1 1 and TU80 magnetic tape drives

TU81 magnetic tape drive

All of the tape drives are used solely as load devices. In dual-RL02 IDC
configurations, the load device and the system device are RL02 disk drives.
Similarly, the dual-RA60 UDA configuration uses RA60 disk drives as both
the load and system devices. The R80, RA80, and RA81 are fixed-head
devices used solely as system devices.

4.4.8

VAX-11 /725 Device Names
The only two devices in a VAX-11/725 system are the fixed disk and the
removable disk. Configurations of pre-Version 4.0 systems use the device
name DUAO for the removable disk, and DUA1 for the fixed disk. For
Version 4.0 and greater systems, the removable disk is called DAAO and the
fixed disk is DAA1. Note, however, that the boot names are DUO and DU1
for all versions.

4.5

Backing Up a System Disk
Before you upgrade or update your system, or before you install an optional
product, you should back up your current system disk. This provides you
with a backup of your system if a problem occurs during the installation.
The recommended method is to use BACKUP to make a copy of the system
disk, and to then use the copy as the target disk for your installation.

4-18

Support Information

You may use either online BACKUP or standalone BACKUP to make a
copy of your system disk. Usually, standalone BACKUP will take longer
but is safer and less complex than using online BACKUP. If you use online
BACKUP, the system may continue in use while you are making the copy.
With standalone BACKUP, all use of the system disk is discontinued because
only standalone BACKUP runs during the backup procedures.
This section assumes the use of standalone BACKUP. If you received your
operating system on magnetic tape, it was accompanied by standalone
BACKUP on four pieces of console media (TU58 tape cartridges or RX01
floppy diskettes), three pieces of console media (RX50 diskettes) or one
RL02 disk. If you received your system on disk, you must build a bootable
standalone BACKUP kit (see Section 4.6).

4.5.1

Backing up a VAX 8600 System Disk
Use standalone BACKUP to back up your system disk to a scratch disk or
tape. The procedure is as follows:
1

Shut down your system.

Write-protect your system disk by pressing the WRITE PROTECT button.

Boot standalone BACKUP from the RL02 console drive.
a

Enter this command at the console prompt (> > > ) to begin the
standalone BACKUP boot sequence:
»>B CSA1

The procedure prompts you to spin down the console RL02
and replace it with the standalone volume labeled STABACKUP
(VAX/VMS V4.4 S/A BACKUP). The next prompt tells you to enter
YES, or simply Y, when you are ready to continue. Note that you
must wait for the READY light on the console RL02 drive to turn on
before typing YES.
Enter YES, and the procedure displays this message:
Resuming load operation on volume

'STABACKUP',

please stand by...

When the volume is booted, the standalone system announces itself
and may ask for the date and time:
VAX/VMS Version V4.4 15-APR-1986 22:29
PLEASE ENTER DATE AND TIME

(DD-MMM-YYYY

HH:MM)

4-19

Support Information

If you are prompted to do so, enter the date in day-month-year
format, and the time in hours and minutes using the 24-hour clock
format. For example, if the time is 3:58 P.M. and the date is April
15, 1986, type:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

HH:MM) 15-APR-15:58

Standalone BACKUP identifies itself and presents the DCL prompt
($):
‘/.BACKUP-1-IDENT, standalone BACKUP V4.4; the date is <DD-MMM-YYYY HH:MM>
$

Place a scratch volume on the drive to which you will back up your
system disk.

Issue one of the following standalone BACKUP commands. The first
command is for disk devices; the second for tapes.
$ BACKUP/VERIFY/IMAGE system.disk: scratch.disk:
$ BACKUP/VERIFY/IMAGE/REWIND system_disk: tape.device:save_set_name

For example, if the system disk were DMAO and the scratch disk were
DMA1, you would issue this command to back up the system disk.
$

4.5.2

BACKUP/VERIFY/IMAGE DMAO: DMA1:

Backing Up a VAX 8200 System Disk
Use standalone BACKUP to back up your system disk to a scratch disk or
tape. The procedure is as follows:
1

Shut down your system.

Write-protect your system disk by pressing the WRITE PROTECT button.

Boot standalone BACKUP from the RX50 console drive as follows:

Enter this command at the console prompt (> > > ) to invoke the
BOOT58 utility:
»>B/R5:800 CSA1

Enter the following command to begin the standalone BACKUP boot
sequence:
B00T58> (8CSAB00.CMD

4-20

Support Information

The procedure prompts you to replace the console RX50 with with
the first standalone volume labeled SYSTEM__1 (VAX/VMS V4.4
S/A BKUP RX50 1/3) and to enter YES, or simply Y, when you are
ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_1', please stand by...

When the first volume is booted, the procedure prompts you
to replace it with the standalone volume labeled SYSTEM_2
(VAX/VMS V4.4 S/A BKUP RX50 2/3) and to enter YES when
you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_2', please stand by...

When the second volume is booted, the standalone system
announces itself and may ask for the date and time:
VAX/VMS Version V4.4 15-APR-1986 22:29
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

HH:MM)

HH:MM) 15-APR-1986 15:58

Next, the procedure prompts you to replace the second standalone
volume with the volume labeled BACKUP (VAX/VMS V4.4 S/A
BKUP RX50 3/3) and to enter YES when you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'BACKUP', please stand by...

When the application volume is booted, standalone BACKUP
identifies itself and presents the DCL prompt ($):
•/.BACKUP-1-IDENT, standalone BACKUP V4.4; the date is <DD-MMM-YYYY HH:MM>
$

Place a scratch volume on the drive to which you will back up your
system disk.

Issue one of the following standalone BACKUP commands. The first
command is for disk devices; the second for tapes.
$ BACKUP/VERIFY/IMAGE system_disk: scratch.disk:
$ BACKUP/VERIFY/IMAGE/REWIND system_disk: tape_device:save_set_name

4-21

Support Information

For example, if the system disk were DJAO and the scratch disk were
DJA1, you would issue this command to back up the system disk.
$

4.5.3

BACKUP/VERIFY/IMAGE DJAO: DJA1:

Backing Up a VAX—11/780 System Disk
Use standalone backup to back up your system disk to a scratch disk or tape.
The procedure is as follows:
1

Shut down your system.

Write-protect your system disk by pressing the WRITE PROTECT button.

Boot standalone BACKUP from the console diskette drive as follows:

Enter this command at the console prompt (> > > ) to begin the
standalone BACKUP boot sequence:
»>B CSA1

The procedure prompts you to successively place the four volumes
containing the standalone BACKUP kit in the console drive.
The first prompt directs you to replace the console floppy with the
standalone volume labeled SYSTEM_1 (VAX/VMS V4.4 S/A BKUP
RX1 1/4) and to enter YES, or simply Y, when you are ready to
continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM.l', please stand by...

When the first volume is booted, the procedure prompts you
to replace it with the standalone volume labeled SYSTEM_2
(VAX/VMS V4.4 S/A BKUP RX1 2/4) and to enter YES when
you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_2', please stand by...

When the second volume is booted, the procedure prompts you
to replace it with the standalone volume labeled SYSTEM_3
(VAX/VMS V4.4 S/A BKUP RX1 3/4) and to enter YES when
you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_3', please stand by...

4-22

Support Information

When the third volume is booted, the standalone system announces
itself and may ask for the date and time:
VAX/VMS Version V4.4 15-APR-1986 22:29
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

HH:MM)

HH:MM) 15-APR-1986 15:58

Next, the procedure prompts you to replace the third standalone
volume with the volume labeled BACKUP (VAX/VMS V4.4 S/A
BKUP RX1 4/4) and to enter YES when you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'BACKUP', please stand by...

When the application volume is booted, standalone BACKUP
identifies itself and presents the DCL prompt ($):
‘/.BACKUP-1-IDENT, standalone BACKUP V4.4; the date is <DD-MMM-YYYY HH:MM>
$

Place a scratch volume on an appropriate drive.

For example, if the system disk were DMAO and the scratch disk were
DMA1, you would issue this command to back up the system disk:
$

BACKUP/VERIFY/IMAGE DMAO: DMA1:

4-23

Support Information

4.5.4

Backing Up a VAX-11/750 System Disk
Use standalone backup to back up your system disk to a scratch disk or tape.
The procedure is as follows:
1

Shut down your system.

Write-protect your system disk by pressing the WRITE PROTECT button.

Boot standalone BACKUP from the TU58 cassette drive as follows:

Enter this command at the console prompt (> > > ) to invoke the
BOOT58 utility:
»>B/800 DDAO

Enter the following command to begin the standalone BACKUP boot
sequence:
B00T58> OCSABOO.CMD

The procedure prompts you to successively place the four volumes
containing the standalone BACKUP kit in the console drive.
The first prompt directs you to replace the console TU58 with the
standalone volume labeled SYSTEM_1 (VAX/VMS V4.4 S/A BKUP
T58 1/4) and to enter YES, or simply Y, when you are ready to
continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_1‘, please stand by...

When the first volume is booted, the procedure prompts you
to replace it with the standalone volume labeled SYSTEM_2
(VAX/VMS V4.4 S/A BKUP T58 2/4) and to enter YES when
you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_2', please stand by...

When the second volume is booted, the procedure prompts you
to replace it with the standalone volume labeled SYSTEM_3
(VAX/VMS V4.4 S/A BKUP T58 3/4) and to enter YES when
you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_3', please stand by...

4-24

Support Information

When the third volume finishes booting, the standalone system
announces itself and may prompt for the date and time:

n
VAX/VMS Version V4.4 15-APR-1986 22:29
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

If you are prompted to do so, enter the date in day-month-year
format, and the time in hours and minutes using the 24-hour clock
format. For example, if the time is 3:58 P.M. and the date is April
17, 1986, type:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

HH:MM) 17-APR-1986 15:58

Next, the procedure prompts you to replace the third standalone
volume with the application volume labeled BACKUP (VAX/VMS
V4.4 S/A BKUP T58 4/4), and to enter YES when you are ready to
continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'BACKUP' please stand by...

When the application TU58 cassette is booted, standalone BACKUP
identifies itself and presents the DCL prompt ($):
'/.BACKUP -1 -1 DENT, standalone BACKUP V4.4; the date is <DD-MMM-YYYY HH:MM>
$

Place a scratch volume on an appropriate drive.

Issue one of the following BACKUP commands. The first command is for
disk devices; the second for tapes.
$ BACKUP/VERIFY/IMAGE system.disk: scratch.disk:
$ BACKUP/VERIFY/IMAGE/REWIND system_disk: tape.device:save_set_name

For example, if system disk were DMAO and the scratch disk were
DMA1, you would issue this command to back up the system disk.
$ BACKUP/VERIFY/IMAGE DMAO: DMA1:

4-25

Support Information

4.5.5

Backing Up an R80 System Disk on a VAX-11 /730
Because an R80 disk has a much greater storage capacity than an RL02 disk,
it is usually necessary to back up the contents of an R80 disk to a group of
RL02 disks that are referred to as the backup volume set. This procedure is
described in the VAX/VMS System Manager's Reference Manual.
Use this procedure to back up your R80 system disk:
1

Boot standalone BACKUP from the TU58 cassette drive as follows:

Enter this command at the console prompt (> > > ) to invoke the
BOOT58 utility:
>»B/800 DDAO

Enter the following command to begin the standalone BACKUP boot
sequence:
B00T58> OCSABOO.CMD

When the second volume is booted, the procedure prompts you
to replace it with the standalone volume labeled SYSTEM _3
(VAX/VMS V4.4 S/A BKUP T58 3/4) and to enter YES when
you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_3', please stand by...

4-26

Support Information

When the third volume finishes booting, the standalone system
announces itself and may prompt for the date and time:

y.y.
VAX/VMS Version V4.4 15-APR-1986 22:29
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

If you are prompted to do so, enter the date in day-month-year
format, and the time in hours and minutes using the 24-hour clock
format. For example, if the time is 3:58 P.M. and the date is April
17, 1986, type:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

HH:MM)

HH:MM) 17-APR-1986 15:58

i When the application TU58 cassette is booted, standalone BACKUP
identifies itself and presents the DCL prompt ($):
•/.BACKUP-1-IDENT, standalone BACKUP V4.4; the date is <DD-MMM-YYYY HH:MM>
$

Assign device name DQAO to the R80 drive and be sure it is write
protected.

Assign device name DQA1 to the RL02 drive that will hold the scratch
disks, that is, the disks you are using to back up the R80.

Place a scratch RL02 disk in DQA1.

Specify the name and file type of the save set you are creating:
$ BACKUP/VERIFY DQAO: DQA1:filename.type/SAVE_SET

When standalone BACKUP is ready for the next scratch disk, it will
prompt you with the following message:
‘/.BACKUP-1-READYWRITE, Mount Volume 2 on _DQA1: for writing
Press RETURN when ready:

Place the next RL02 scratch disk (volume 2 of the backup volume set) in
the drive and press the RETURN key.
Repeat this step each time you receive the prompt for another volume.
When the volume set is completed, you are returned to the DCL level (as
indicated by the dollar sign prompt ($).

4-27

Support Information

4.5.6

Backing Up an RL02 System Disk
Take the following steps to back up an RL02 system disk.
1

Load the system disk in the RL02 drive designated DQAO.

Write-protect the system disk.

Boot standalone BACKUP from the TU58 cassette drive as follows:
a

Enter this command at the console prompt (> > > ) to invoke the
BOOT58 utility:
»>B/800 DDAO

Enter the following command to begin the standalone BACKUP boot
sequence:
B00T58> ©CSAB00.CMD

4-28

Support Information

When the third volume finishes booting, the standalone system
announces itself and may prompt for the date and time:

n
VAX/VMS Version V4.4 15-APR-1986 22:29
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

If you are prompted to do so, enter the date in day-month-year
format, and the time in hours and minutes using the 24-hour clock
format. For example, if the time is 3:58 P.M. and the date is April
17, 1986, type:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

HH:MM)

HH:MM) 17-APR-1986 15:58

When the application TU58 cassette is booted, standalone BACKUP
identifies itself and presents the DCL prompt ($):
•/.BACKUP-1-IDENT, standalone BACKUP V4.4; the date is <DD-MMM-YYYY HH:MM>
$

4
5

Place a scratch disk in DQA1.
Back up the system disk to the scratch disk with the following command:
$ BACKUP/IMAGE/VERIFY DQAO: DQA1:

4.5.7

Backing Up a Fixed RC25 System Disk
Use the following procedure to back up a fixed RC25 system disk:
1

Replace the removable data disk with a removable scratch disk.

Boot standalone BACKUP from the TU58 cassette drive as follows:

Enter this command at the console prompt (> > > ) to invoke the
BOOT58 utility:
»>B/800 DDAO

Enter the following command to begin the standalone BACKUP boot
sequence:
B00T58> 0CSAB00.CMD

4-29

Support Information

When the first volume is booted, the procedure prompts you
to replace it with the standalone volume labeled SYSTEM _2
(VAX/VMS V4.4 S/A BKUP T58 2/4) and to enter YES when
you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_2', please stand by...

When the second volume is booted, the procedure prompts you
to replace it with the standalone volume labeled SYSTEM _3
(VAX/VMS V4.4 S/A BKUP T58 3/4) and to enter YES when
you are ready to continue.
When you enter YES, the procedure displays this message:
Resuming load operation on volume 'SYSTEM_3', please stand by...

When the third volume finishes booting, the standalone system
announces itself and may prompt for the date and time:
7.7.
VAX/VMS Version V4.4 15-APR-1986 22:29
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

HH:MM)

HH:MM) 15-APR-1986 15:58

4-30

Support Information

When the application TU58 cassette is booted, standalone BACKUP
identifies itself and presents the DCL prompt ($):
•/.BACKUP-1-IDENT, standalone BACKUP V4.4; the date is <DD-MMM-YYYY HH:MM>
$

When you get the DCL prompt ($), back up the fixed system disk to the
removable scratch disk:
$ BACKUP/IMAGE/VERIFY DAA1: DAAO:

The removable disk is now a backup of the fixed system disk.

4.5.8

Backing Up a Removable RC25 System Disk
Use the following procedure to back up a removable system disk:
1

Replace the removable system disk (the disk you want to back up) with
a removable scratch disk.

Boot standalone BACKUP from the TU58 cassette drive as follows:

Enter this command at the console prompt (> > > ) to invoke the
BOOT58 utility:
»>B/800 DDAO

Enter the following command to begin the standalone BACKUP boot
sequence:
B00T58> (SCSABOO.CMD

4-31

Support Information

When the third volume finishes booting, the standalone system
announces itself and may prompt for the date and time:

U
VAX/VMS Version V4.4 15-APR-1986 22:29
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

If you are prompted to do so, enter the date in day-month-year
format, and the time in hours and minutes using the 24-hour clock
format. For example, if the time is 3:58 P.M. and the date is April
17, 1986, type:
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY

HH:MM)

HH:MM) 17-APR-1986 15:58

When the application TU58 cassette is booted, standalone BACKUP
identifies itself and presents the DCL prompt ($):
'/.BACKUP-1-IDENT, standalone BACKUP V4.4; the date is <DD-MMM-YYYY HH:MM>
$

When you get the DCL prompt ($), back up the fixed data disk to the
removable scratch disk by issuing this command:
$ BACKUP/IMAGE/VERIFY DAA1: DAAO:

The removable disk is a backup of the fixed data disk. Put it aside until
you are instructed to use it for restoring the fixed disk.

Mount the original removable system disk.

Back up the removable system disk to the fixed disk.
$ BACKUP/IMAGE/VERIFY DAAO: DAA1:

The fixed disk is a backup of the removable system disk.

4—32

Support Information

Replace the the original removable system disk with another removable
scratch disk.

Back up the fixed disk to the removable disk.
$ BACKUP/IMAGE/VERIFY DAA1: DAAO:

The removable disk is a backup of the original removable system disk.
Put it aside and replace it with the removable disk that was used to back
up the fixed data disk in step 3.
8

Back up the removable disk to the fixed disk.
$ BACKUP/IMAGE/VERIFY DAAO: DAA1:

The fixed disk is restored to its original state as the data disk.

9
4.6

Replace the removable disk with the original removable system disk.

Building Standalone BACKUP on Console Media
To back up your system disk, you may use either online BACKUP or
standalone BACKUP. If you elect to use standalone BACKUP and your
system was not distributed on magnetic tape, you will have to build
standalone BACKUP on either console media or on disk.
If you have a VAX-11/780, the console medium is an RX01 diskette. For all
other VAX-11 systems, the console medium is a TU58 cassette. The console
medium on a VAX 8600 is an RL02 disk, and the console medium on the
VAX 8200 is an RX50 diskette.
The following sections describe how to build standalone BACKUP on console
media.

4.6.1

Building Standalone BACKUP on RX01 Diskettes or TU58 Tape
Cassettes
Invoke the SYS$UPDATE:STABACKIT.COM command procedure to build
a standalone BACKUP kit. The following procedure for building standalone
BACKUP on RX01 diskettes can also be used to build the kit on TU58
cassettes (simply substitute TU58 for RX01 in the following description):
1

Label four blank RX01 floppy diskettes SYSTEM _1, SYSTEM _2,
SYSTEM _3, and BACKUP, respectively.

At the DCL prompt ($), enter the following:
$ ®SYS$UPDATE:STABACKIT

4-33

Support Information

When STABACKIT executes, it prompts you for for the target device.
Respond by entering CSA1: as shown:
Enter the name of the device on which to build the kit: CSA1:

When you identify the target device, STABACKIT tells you that four
blank RX01 diskettes are needed to build the kit, three for the standalone
VAX/VMS files, and the other for the BACKUP application image.
STABACKIT also gives you the option of building the VAX/VMS files as
a system kit without building the application (in this case BACKUP) kit,
or building both the system and application kits at this time.
Do you want to build the system kit? [Yes/No, default Yes]:
Do you want to build the application kit? [Yes/No, default Yes]:

Respond to both questions by pressing the RETURN key. DIGITAL
recommends that you always build both the system and application kits.

Note
If you are building a kit on TU58 cassettes, allow 40 minutes
per cassette to run BAD.
Next, wait for the prompt that asks you to insert the first system diskette
in the console drive:
Please place the first system floppy diskette in drive _CSA1:.
This volume will receive the volume label SYSTEM.l.
Enter "YES" when ready:

Insert the diskette labeled SYSTEM_1 into CSA1; then enter YES. If you
elected to have the bad block test run, you get the following message:
Analyzing floppy diskette for bad blocks .
SYSTEM.1
mounted on _CSA1:

The test takes approximately 15 minutes (40 minutes for TU58s). Upon
completion, you are given the number of blocks on the diskette and the
number that are bad. Then STABACKIT mounts the diskette, creates
[SYSO.SYSEXE], and copies the set of system files to it, accompanied by
appropriate messages. Then, STABACKIT prompts to insert for the next
diskette:
Please place the second system floppy diskette in drive _CSA1:.
This volume will receive the volume label SYSTEM.2.
Enter "YES" when ready:

4-34

Support Information

Replace the diskette labeled SYSTEM _1 with the diskette labeled
SYSTEM—2, then enter YES.

When you press enter YES, STABACKIT runs BAD (assuming you
chose to do so), mounts the diskeette and copies the system files to
[SYSO.SYSEXE]. Then, STABACKIT prompts you to insert the third
diskette:
Please place the third system floppy diskette in drive _CSA1:.
This volume will receive the volume label SYSTEM_3.
Enter "YES" when ready:

10 Replace the diskette labeled SYSTEM_2 with the diskette labeled
SYSTEM_3, then enter YES.
11 When you enter YES, STABACKIT runs BAD (assuming you chose to
do so), mounts the diskette and copies the rest of the system files to
[SYSO.SYSEXE].
When the last file is copied, STABACKIT prompts you to insert the fourth
diskette:
Please place the application floppy diskette in drive _CSA1:.
This volume will receive the volume label BACKUP.
Enter "YES" when ready:

1 2 Replace the diskette labeled SYSTEM _2 with the diskette labeled
BACKUP; then enter YES.

1 3 When you enter YES, STABACKIT runs BAD, mounts the diskette
and copies the executable backup image (STABACKUP.EXE) to
[SYSO.SYSEXE].
14 When you get this message, the kit is built:
The console volume will be mounter /NOWRITE for protection.
Please replace the original console floppy diskette.
Enter "YES" when ready:

1 5 Replace the diskette labeled BACKUP with the console floppy diskette,
then press RETURN.
The procedure responds by mounting the console floppy diskette, giving
the starting and ending times, and then returning the system to DCL
command level.

4-35

Support Information

4.6.2

Building Standalone BACKUP on RX50 Diskettes
Invoke the SYS$UPDATE:STABACKIT.COM command procedure to build a
standalone BACKUP kit on RX50 diskettes:
1

Label three blank RX50 diskettes SYSTEM__1, SYSTEMS, and
BACKUP, respectively.

Type the following command:
$ <DSYS$UPDATE: STABACKIT

The STABACKIT command procedure prompts you for for the target
device. Respond by entering CSA1:
Enter the name of the device on which to build the kit: CSA1:

When you identify the target device, STABACKIT tells you that three
blank RX50 diskettes are needed to build the kit, two for the standalone
VAX/VMS files, and the other for the BACKUP application image.
STABACKIT also gives you the option of building the VAX/VMS files as
a system kit without building the application (in this case BACKUP) kit,
or building both the system and application kits at this time.
Do you want to build the system kit? [Yes/No, default Yes]:
Do you want to build the application kit? [Yes/No, default Yes]:

Respond to both questions by pressing the RETURN key. DIGITAL
recommends that you always build both the system and application kits.

Next, STABACKIT gives you the option of using the Bad Block Locator
Utility (BAD) to check for bad blocks on the target diskette. This
operation requires approximately 15 additional minutes for each diskette
but by finding bad blocks that would otherwise give you a problem
building the kit, you may actually save time.
Next, wait for the prompt that asks you to insert the first system diskette
in the console drive:
Please place the first system floppy diskette in drive _CSA1:.
This volume will receive the volume label SYSTEM.l.
Enter "YES" when ready:

Insert the labeled SYSTEM—l into CSA1; then enter YES. If you elected
to have the bad block test run, you get the following message:
Analyzing floppy diskette for bad blocks .
SYSTEM.l
mounted on _CSA1:

4-36

Support Information

The test takes approximately 15 minutes. Upon completion, you are
given the number of blocks on the diskette and the number that are
bad. Then STABACKIT mounts the diskette, creates [SYSO.SYSEXE], and
copies the set of system files to it, accompanied by appropriate messages.
Then, STABACKIT prompts you for the next diskette:
Please place the second system diskette in drive _CSA1:.
This volume will receive the volume label SYSTEM_2.
Enter "YES" when ready:

Replace the diskette labeled SYSTEM_1 with the diskette labeled
SYSTEM—2, then enter YES.

When you press enter YES, STABACKIT runs BAD (assuming you
chose to do so), mounts the diskette and copies the more system files to
[SYSO.SYSEXE]. Then, STABACKIT prompts you for the third diskette:
Please place the application floppy diskette in drive _CSA1:.
This volume will receive the volume label BACKUP.
Enter "YES" when ready:

10 Replace the diskette labeled SYSTEM_2 with the diskette labeled
BACKUP; then enter YES.
11 When you enter YES, STABACKIT runs BAD, mounts the diskette
and copies the executable backup image (STABACKUP.EXE) to
[SYSO.SYSEXE].

1 2 When you get this message, the kit is built:
The console volume will be mounter /NOWRITE for protection.
Please replace the original console floppy diskette.
Enter "YES" when ready:

13 Replace the diskette BACKUP with the console floppy diskette, then
press RETURN.
The procedure responds by mounting the console diskette, giving
the starting and ending times, and then returning the system to DCL
command level.

4-37

Support Information

4.6.3

Building Standalone BACKUP on an RL02 Disk
Invoke the SYS$UPDATE:STABACKIT.COM command procedure to build a
standalone BACKUP kit on an RL02 disk:
1

Label one blank RL02 disk STABACKUP.

Type the following command:
$ <DSYS$UPDATE: STABACKIT

The STABACKIT command procedure prompts you for for the target
device. Respond by entering CSA1:
Enter the name of the device on which to build the kit: CSA1:

When you identify the target device, STABACKIT tells you that one
blank RL02 disk is needed to build the kit.
STABACKIT also gives you the option of building the VAX/VMS files as
a system kit without building the application (in this case BACKUP) kit,
or building both the system and application kits at this time.
Do you want to build the system kit? [Yes/No, default Yes]:
Do you want to build the application kit? [Yes/No, default Yes]:

Respond to both questions by pressing the RETURN key. DIGITAL
recommends that you always build both the system and application kits.
6

Next, STABACKIT gives you the option of using the Bad Block Locator
Utility (BAD) to check for bad blocks on the target disk.
Next, wait for the prompt that asks you to insert the RL02 in the console
drive:
Please place the system device in drive _CSA1:.
This volume will receive the volume label STABACKUP.
Enter "YES" when ready:

Insert the RL02 disk labeled STABACKUP into CSA1; then enter YES.
If you elected to have the bad block test run, you get the following
message:
Analyzing disk for bad blocks .
STABACKUP
mounted on _CSA1:

Upon completion, you are given the number of blocks on the disk and
the number that are bad. Then STABACKIT mounts the disk, creates
[SYSO.SYSEXE], and copies the set of system files to it, accompanied by
appropriate messages.

4-38

Support Information

When you get this message, the kit is built:
The console volume will be mounter /NOWRITE for protection.
Please replace the original console disk.
Enter "YES" when ready:

Replace the RL02 disk labeled BACKUP with the console RL02, then
press RETURN.
The procedure responds by mounting the console disk, giving the starting
and ending times, and then returning the system to DCL command level.

4.7

Using Standalone Backup on Disk
Installing and using standalone BACKUP in an alternate root on your system
disk saves time when backing up your system disk because you do not have
to boot standalone BACKUP from console media, which is a relatively slow
process.
The procedures described here apply to all VAX processors. However, you
should note the following:
•

You can install standalone BACKUP in any available disk directory root
from SYS1 through SYSE; however, DIGITAL has established SYSE as
the standard alternate system directory root for standalone BACKUP. The
discussion in this section assumes you will install standalone BACKUP in
SYSE.

•

You cannot use these procedures to restore your operating system to the
system disk from which standalone BACKUP is booted.

•

There are some limitations with regard to the VAX-11/750, which are
noted within the procedures.

•

The console device is CSA1 on VAX systems with a single console drive
and CSA2 on systems with two console drives. See Chapter 2 for help
in locating the console drives.

The rest of this section explains the following:
•

How to install standalone BACKUP in alternate system directory root
SYSE

•

How to create a bootstrap command procedure that will let you boot
standalone BACKUP from SYSE

•

How to boot standalone BACKUP from SYSE

4-39

Support Information

4.7.1

Installing Standalone BACKUP in Alternate System Root SYSE
Use the SYS$UPDATE:STABACKIT command procedure to install standalone
BACKUP in the alternate system root SYSE. First, log in to the SYSTEM
account. Then, enter this command:
$ <DSYS$UPDATE:STABACKIT SYS$SYSDEVICE:

[SYSE.SYSEXE]

Be sure to enter the command exactly as shown. You will not be prompted
for the destination if you forget to enter it.
After you install standalone BACKUP in SYSE, the next step is to create a
command procedure to boot it.

4.7.2

Creating a Command Procedure to Boot Standalone BACKUP
The recommended procedure for creating a command procedure to boot
standalone BACKUP from alternate root SYSE is to modify an existing boot
command procedure. Ideally, this should be the default boot command
procedure, DEFBOO.CMD. (DEFBOO.COM for VAX 8600 processors.)
First, make a copy of the boot procedure in your default device directory.
Then, edit the copy as instructed. Finally, give the edited copy an
appropriate file name, and store it on the console volume.
You may choose any unique name in the form xxxBOO.CMD (or
xxxBOO.COM for VAX 8600) for the command procedure you create.
However, DIGITAL suggests you use a file name identical to that of the
copied file, except that the first letter should be an X.
For example, if you use a copy of DEFBOO.CMD, the new file should be
named XEFBOO.CMD. Note that you are limited to six characters when you
specify the boot command procedure file name.
The following procedure assumes you will use a copy of DEFBOO.CMD and
rename it XEFBOO.CMD.
1

If necessary, use the following command sequence to connect the console
device:
$ RUN SYSGEN
SYSGEN> CONNECT CONSOLE
SYSGEN> EXIT

Mount the console device as a foreign device:

Invoke the Exchange Utility to make a copy of DEFBOO.CMD in your
default disk directory:

$ MOUNT/FOREIGN CSA1

4-40

Support Information

For VAX 8600:
$ EXCHANGE COPY CSA1:DEFB00.COM *

For VAX 8200, VAX-11/780, and VAX-11/750:
$ EXCHANGE COPY CSA1:DEFB00.CMD *

For VAX-11/730 and VAX-11/725:
$ EXCHANGE COPY CSA2:DEFB00.CMD *

Rename the copy of DEFBOO.CMD in your default directory.
$ RENAME DEFBOO.CMD XEFB00.CMD

Invoke an editor to modify XEFBOO.CMD. The table below shows how
to determine the line that you must modify for your processor; it shows
the line before and after you change it.
Processor Type

Line to Change

Line After Change

VAX 8600

DEPOSIT R5
XXXXXXXX

DEPOSIT R5 EXXXXXXX

VAX 8200

D/G 5 0

D/G 5 EXXXXXXX

VAX-11/780

DEPOSIT R5 0

DEPOSIT R5 EXXXXXXX

VAX-11/782

DEPOSIT R5 0

DEPOSIT R5 EXXXXXXX

VAX-1 1/750

D/G 5 0

D/G 5 EXXXXXXX

VAX-1 1/730

D/G/L 5 0

D/G/L 5 EXXXXXXX

VAX-11/725

D/G/L 5 0

D/G/L 5 EXXXXXXX

6 When you have edited the file, invoke EXCHANGE to store it on the
console volume:
For VAX 8600:
$ EXCHANGE COPY XEFB00.C0M CSA1:

For VAX 8200, VAX-11/780, and VAX-11/750:
$ EXCHANGE COPY XEFBOO.CMD CSA1:

For VAX-11/730 and VAX-11/725:
$ EXCHANGE COPY XEFBOO.CMD CSA2:

4-41

Support Information

4.7.3

Booting Standalone BACKUP from SYSE
To boot standalone BACKUP from SYSE:
1

Type the following command to shut the system down.
$ <3SYS$SYSTEM :SHUTDOWN.COM

The shutdown procedure asks the following three questions. Respond by
pressing the RETURN key three times.
How many minutes until final shutdown?
Reason for shutdown?

[0]

[Standalone]

Do you want to spin down the disk volumes?

[NO]

As the shutdown continues, the console terminal prints several shutdown
messages. When the console terminal prints the following message,
shutdown is complete:
SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

At this point, press CTRL/P to enter console mode. At the > > >
prompt, type HALT to stop the processor.

When the processor halts, enter the following command to boot
standalone BACKUP from SYSE:

For VAX-11/750:
»> B/Exxxxxxx

For all other processors:
»> B XEF

If you are not using a modified version of the default bootstrap command
procedure to boot standalone BACKUP, use the first three characters in
the name of the bootstrap command procedure you created. For example,
if you are using XUOBOO.CMD, type the following command:
»> b xuo

4—42

VMSINSTAL Command Procedure

You use the VMSINSTAL command procedure (VMSINSTAL.COM) to
upgrade your system to the most recent major version, to install system
maintenance updates, and to install many optional software products.
Some optional software products, however, must be installed using the
VMSUPDATE command procedure until they are adapted for VMSINSTAL.
See Appendix C for information on VMSUPDATE.
This chapter describes the following:
•

How to prepare your system for the installation

•

How to invoke VMSINSTAL

•

How to select the VMSINSTAL options appropriate to your needs

•

What to do if the system fails during installation

•

Special considerations for small-disk systems

•

Error messsages

This chapter does not describe installation procedures specific to any
upgrade, update, or product. The examples used are for illustration only.
For installation details of a particular product, refer to the installation guide
that accompanies it.

5.1

Preparing to Use VMSINSTAL
Before you begin the installation procedure, do the following:
1

Back up your system disk, and use the backup copy as a working
copy for doing the installation. If you back up your system disk to
magnetic tape, you will have to restore the tape to a Files-11 disk to get
a working copy. The working copy has more contiguous space than the
original system disk because of the way BACKUP creates the copy. This
additional contiguous space may be needed during the installation.
If the system fails during installation, your working copy may be left in
an unusable state because VMSINSTAL may delete the older version of
the product before it installs the newer version. You may have to make
a new working copy of the system disk and restart the installation from
the beginning if a failure occurs.

5-1

VMSINSTAL Command Procedure

Note
If SYSGEN parameters MOUNTMSG or DISMOUMSG are
set to 1, you will receive a message from OPCOM each time
a disk or tape is mounted or dismounted. If these messages
are not disabled, and you are installing from an operator's
terminal, they will appear within 30 seconds of each mount
or dismount.

Be sure that all users are logged out and that all batch jobs are
completed.

Keep users off the system with the following command:
$ SET L0GINS/INTERACTIVE=O

Shut down DECnet-VAX (if your system includes it). First invoke the
Network Control Program (NCP):
$

RUN SYS$SYSTEM:NCP

When the console terminal prints the NCP prompt (NCP> ), enter the
following command:
NCP> SET EXECUTOR STATE SHUT

DECnet-VAX will perform an orderly shutdown and the OPCOM facility
will notify you when DECnet-VAX is off. Exit from NCP by typing EXIT
at the prompt.

Be sure the following limits in the SYSTEM account authorization record
are equal to or greater than those specified here:
Buffered byte count quota (BYTLM) = 18000
Enqueue quota (ENQLM) = 30
Direct 1/0 limit (DIOLM) = 18
Buffered I/O limit (BIOLM) = 18
Open file quota (FILLM) = 20
AST limit (ASTLM) = 24

To check these limits, run the Authorize Utility (AUTHORIZE) by
entering the following command:
$ RUN SYS$SYSTEM:AUTHORIZE

When the system responds with the UAF> prompt, enter this command:
UAF> SHOW SYSTEM

AUTHORIZE responds by displaying the current limits of the SYSTEM
account's user authorization file.

5-2

VMSINSTAL Command Procedure

If the current limits need to be modified, use the AUTHORIZE command
MODIFY in the following form to make the change:
UAF> MODIFY SYSTEM/limit=new_value

For example, to increase the DIOLM limit to 18, you use the following
command:
UAF> MODIFY SYSTEM/DI0LM=18

When you have completed the modifications, return to DCL command
level by entering the word EXIT when you get the UAF> prompt.
Note that the modification will not take effect until you log out and log
in again. (See the VAX/VMS Authorize Utility Reference Manual for a
description of the Authorize Utility.)

If your system configuration is tailored, load the library disk onto a
drive before starting. The library disk has files that are needed to run
VMSINSTAL.

10 Physically mount the distribution media containing the software
products.

5.2

Invoking VMSINSTAL
This section tells you how to invoke VMSINSTAL and describes options
that can be used. Before you begin the installation, be sure you read and
understand the installation procedures for the specific product or update.
When you invoke VMSINSTAL, it asks if you are satisfied with the backup
of your system disk. Be certain that the backup copy is satisfactory before
you continue with the installation.
If you have not satisfied all conditions required to begin the installation when
you invoke VMSINSTAL, you will get a warning message explaining the
problem together with a prompt asking if you want to continue. DIGITAL
strongly recommends that you correct these conditions before you try to
invoke VMSINSTAL again.

Note
If you continue without making the required corrections, the
resulting installation may not be supported by DIGITAL.
To invoke VMSINSTAL, type a command with the following syntax:
$ «SYS$UPDATE:VMSINSTAL product-list source: OPTIONS option-list _$ [destination] [qualifiers]

5-3

VMSINSTAL Command Procedure

product-list
The list of the products you want to install. If you use a wildcard character
(*) as the product-list parameter, all versions and updates of all products
from the distribution source will be installed in chronological order.

source
Identifies the source of the optional software product as one of the following:
•

A device drive that holds the distribution medium; for example, the
TU58 drive designated CSA1: on a VAX-11/750

•

A disk directory to which the product save set has been transferred from
the distribution media for later installation (this occurs if option G is
specified)

•

A disk directory on another node

You may also use a logical name to specify the source. If you do not specify
the source, VMSINSTAL will prompt you for it.

OPTIONS
A keyword that precedes the list of options to be installed. If you enter an
option list and the OPTIONS keyword is not included in the command, you
will receive an error message and the installation will terminate.

option-list
A list of the options requested. If more than one option is specified, they
must be physically adjacent with no intervening spaces or commas. See
Section 5.3 for details.

destination
By default, VMSINSTAL assumes that the product is to be installed in the
system-specific directory root on the system disk.

Note
If the system you are installing on uses a common system disk,
the product will be installed in the common area. In this case the
alternate root definition is ignored.
There are two instances in which you must use this optional parameter:
•

You must select this option if you want to install the product in an
alternate root (option R). The product is installed on a system root other
than that on which the target system is running. Specify the alternate
system root using the following format:
ddcu:[SYSn.]

5-4

VMSINSTAL Command Procedure

where
ddcu:

Is the device on which the alternate root resides.

[SYSn.]

Is the top-level directory of the alternate system root.

If you wish, you may specify a previously defined logical name for the
alternate root.
•

You must select this option if you specify the GET save set option
(option G) to copy the product kit save sets into a storage directory
for later installation. Specify the destination directory in the following
format:
[node::]ddcu:[directory]

where
[node::]

A node remote from the target system. (DECnet software
must be installed on your system to use this option.) If no
node is specified, VMSINSTAL assumes that the product
save sets are to be stored on the local node.

ddcu:

The destination disk device.

[directory]

Usually a directory dedicated to product save sets on the
specified disk.

qualifiers
This parameter may be specified in conjunction with the GET save set option
(option G) to further qualify the BACKUP command that copies the save sets
to the destination directory.
The following example of a command line for invoking VMSINSTAL includes
option G and BACKUP qualifiers:
$ ®SYS$UPDATE:VMSINSTAL TEST042 DUAO:[KITS] OPTIONS G DUBO:[KITS]
_$ "/VERIFY/LOG/CONFIRM"

If you want to specify more than one item in the product list parameter,
you must separate the items using commas and no intervening spaces. The
format for the product list is:
facvvu

fac

The product facility code (1 to 36 alphanumeric characters)

The major version number (2 digits)

The update number (1 digit)

For example, if you update your operating system to VAX/VMS Version 4.4,
the product name (fac) is VMS, the major version (vv) is 04, and the update
number (u) is 4. Therefore the product-list parameter is VMS044.

5-5

VMSINSTAL Command Procedure

If you omit the product-list parameter, you will be prompted for it. If you are
installing from a distribution device, the list of products on your distribution
volume is included with the bill of materials for the distribution kit. If the list
is not available, issue a DIRECTORY command for the distribution volume
to find the products that are included.
If you are installing from a disk directory, you can obtain the product list
by entering a DIRECTORY command specifying the disk directory in the
following format. If you are accessing a remote node, you must have READ
and EXECUTE (R,E) access to the directory.
$ DIRECTORY node::disk:[directory]

Using this format, you can install a specific version and update of a product
from a distribution volume containing several versions and updates. If you
do not include a version or update number, then all versions and updates
from the source are installed in chronological order.
When you invoke VMSINSTAL, you receive several prompts and messages
that direct and explain the installation. These prompts and messages differ,
depending on the update or software product you are installing. Consult the
installation documentation that comes with the update or software product
for specific instructions. If you need assistance during an installation, typing
a question mark (?) at a prompt will give you an explanation of acceptable
responses.
When the installation is completed, VMSINSTAL will do one of two things,
depending on the requirements of the product you have installed. It will
either perform an automatic shutdown of the system and instruct you to
manually reboot, or it will simply return you to the DCL command level.
When the product is installed, you should back up the updated system disk.

5.3

Choosing VMSINSTAL Options
The VMSINSTAL command procedure permits the use of five options:
•

Auto-answer option (A)

•

Get save set option (G)

•

File log option (L)

•

Release notes option (N)

•

Alternate root option (R)

5-6

VMSINSTAL Command Procedure

You specify each of these options by entering the appropriate option
letter following the keyword OPTIONS in the command line that invokes
VMSINSTAL. If you specify more than one option, the letters must be
physically adjacent and cannot be separated by spaces or commas.

Auto-answer (A)
The auto-answer option makes it easier to reinstall a product or a system
update by providing responses to VMSINSTAL questions and prompts
during the reinstallation. The auto-answer option is used most often for
reinstalling products when you upgrade the system.
If you specify the auto-answer option when you install a product, an answer
file is created of the form product.ANS in the SYS$UPDATE directory, where
product is a file name that reflects the product-list parameter you provide
when you invoke VMSINSTAL.
The file type of an answer file is ANS. The answer file is used to record
your responses to questions and prompts from VMSINSTAL during the
installation. For example, if you install the product, NEWAID, with
the auto-answer option, VMSINSTAL creates an answer file designated
NEWAID.ANS.
When you subsequently reinstall the product and specify the auto-answer
option (typically after upgrading your operating system), VMSINSTAL reads
the answer file instead of prompting you for responses.
If you want to create a new answer file when you reinstall a product, you
must delete the existing answer file first.

GET save set (G)
Installing products from a distribution tape or from console media directly
onto your system is a time-consuming task. The GET save set option saves
you time by allowing you to temporarily store product save sets in a disk
directory or on a magnetic tape. At your convenience the product save sets
can be restored to your system from disk rather quickly in standalone mode
using VMSINSTAL.
You may want to consider dedicating a user disk on a central node for
storing product save sets to give other licensed system users fast access to the
product save-set directory.
To store a product save set on a disk directory using the GET option, use a
command with the following syntax:
$ ®SYS$UPDATE:VMSINSTAL product-list source:
-OPTIONS G device:[directory]

5—7

VMSINSTAL Command Procedure

You specify the disk directory immediately following the OPTIONS G
parameter. For example, if you are installing a product named NEWAID from
the VAX-11/750 console drive into disk directory USERl:[PRODUCTS], you
would use the following command:
$ ®SYS$UPDATE:VMSINSTAL NEWAID CSA1: OPTIONS G
_USERi:[PRODUCTS]

VMSINSTAL will create one or more files to store the product save set in the
disk directory. The save set file name will have the following format:
facvvu.x

fac

The product facility code (1 to 36 alphanumeric characters)

The major version number (2 digits)

The update number (1 digit)

A literal extension that is used to identify save set files, where A is the
first save set, B the second, and so forth.

Note
Valid extensions for save set files include the literal range A
through Z and the numeric range 27 through 9999.
For example, if you are storing update 1 to Version 2.0 of the example
product, NEWAID, and this requires four save sets, VMSINSTAL would
create the following four files:
NEWAID021.A
NEWAID021.B
NEWAID021.C
NEWAID021.D
When you want to install the product on your system, you use the following
format:
$ ®SYS$UPDATE:VMSINSTAL product-list device: [directory]

For the example product NEWAID, you would use this command:
$ ®SYS$UPDATE:VMSINSTAL NEWAID USER1:[PRODUCTS]

VMSINSTAL responds by installing the NEWAID product on your system
disk.

File Log (L)
The file log option logs all file activity to the terminal during installation.
File activity is defined as any action that alters the disposition of a file, such
as creating a new file, updating a library, or deleting a file.

5-8

VMSINSTAL Command Procedure

Release Notes ( N)
The release notes option is used to display or print the release notes file
supplied by the layered product.

Note
Not all layered products provide online release notes.
The release notes file is named by the person who builds the product kit.
It is given the file name facvvu.release—notes, where facvvu represents the
product facility code, version, and update numbers.
If release notes are available and the N option is specified, VMSINSTAL
prompts the installer with the following questions. (The default answers are
indicated in brackets.)
Release
(1)
(2)
(3)

Notes Options:
Display release notes
Print release notes
Both 1 and 2

♦Select option [3]:
♦Queue name [SYS$PRINT]:
♦Do you want to continue the installation [N]:

The first prompt (*Select option:) allows the installer to choose either option
1, 2, or 3.
The second prompt (*Queue name:) is displayed only if option 2 or 3 is
selected. If the installer enters the name of a print queue, the system returns
a message indicating that the release notes have been successfully queued
to the printer. If a print queue is not specified, the output is directed to
SYS$PRINT by default.
The third prompt (*Do you want to continue the installation:) allows the
installer to either continue or terminate the installation. The default is to
terminate the installation at this point.
If no release notes are supplied with the product, VMSINSTAL returns
two error messages, followed by the prompt to continue or terminate the
installation, as follows:
'/.VMSINSTAL-W-NOFILE, New File FACVVU.RELEASE.NOTES does not exist.
'/.VMSINSTAL-W-NORELNOTE, unable to locate release notes.
♦Do you want to continue the installation [N]:

You can continue the installation by entering Y in response to this prompt,
regardless of whether release notes are available.

5-9

VMSINSTAL Command Procedure

Alternate Root (R)
The alternate root option permits you to install the product to a system
root other than that of the running system. The VAX/VMS system in the
alternate root must be complete and at the same version/update level as the
running system. All files and software products that are referenced by the
product installation must be present in the alternate root. Note that not all
optional software products allow installation to a system root other than that
of the running system. Consult the documentation of the specific product to
determine whether the product can be installed to an alternate system root.
If you specify option R when installing on a system that uses a common
system disk (in a clustered environment), the alternate root is ignored and
the product is installed on the common system disk.

5.4

Recovering From a System Failure
If the system fails during installation of an update or optional software
product, VMSINSTAL will attempt to continue the installation upon
rebooting. Depending on the point in the installation at which the system
failed, one of three conditions will exist:
•

The system disk will not have been altered before the system failure. In
this case, VMSINSTAL will instruct you to restart the installation.

•

The system disk or a library used by the installation will have been
corrupted. In this case, VMSINSTAL instructs you to restore either
the system disk or the corrupted library from the backup copy (see
Section 5.1) and restart the installation.

•

VMSINSTAL will continue the installation. In this case, VMSINSTAL
performs most of the installation and then informs you that there may be
some tasks you must perform manually to complete the installation. If
VMSINSTAL instructs you to do so, reboot the system, log in as system
manager, and perform the following tasks:
—

Purge all system files that have been replaced, even if you requested
an automatic purge.
$ PURGE/LOG SYS$SYSR00T:[*...]*.*

—

If you have a tailored system, restore all library files to the system
disk, because VMSINSTAL removes them during the installation.
To restore your library files, mount the library disk and use the
following command to make a copy request:
$ ®SYS$UPDATE:VMSTAILOR COPY VMIORIG

5-10

VMSINSTAL Command Procedure

After the copy command is executed, use the following command to
delete the tailoring file:
$ DELETE SYS$UPDATE:VMIORIG.TLR;*

Both commands are necessary to return your system disk to its
previous state when a failure occurs during an installation.

5.5

Special Considerations for Small-Disk Systems
A small disk is a disk whose storage capabilities (fewer than 70,000 blocks)
make it impractical to use as a system disk for storing a complete operating
system. Currently, small-disk systems include:
•

Dual-RL02 systems

•

Dual-RK07 systems

•

RC25 systems

DIGITAL recommends that each of these system configurations use a
tailoring environment in which two disks are used to support the operating
system—a system disk and a library disk. The system disk includes all of the
files required for basic operating system functions, and a limited set of library
files that you can select that support additional operating system functions.
The procedure for installing the operating system on a small-disk system has
two parts:
•

Restoring the required save set to the system disk

•

Restoring the library files save set to the library disk

When the restorations are completed, you may tailor your system by copying
selective files from the library disk to the system disk. (See the VAX/VMS
System Manager's Reference Manual for details on how to use the tailoring
facility.)

5-11

5.5.1

Installing Optional Products on Small-Disk Systems
When you install optional products on a small-disk system, the library disk
must be mounted. Before being prompted for the first optional software
volume, you will receive the following message:
'/.VMSINSTAL-1-SMALLDISK, This is a small-disk system.
This is a small-disk system and must be tailored to accommodate your new
software products. The current tailoring environment will be recorded, and
the system files that are not required will be temporarily removed from the
system disk. After installation, the original environment will be restored.
'/.MOUNT-1-MOUNTED, VAXVMSLB4 mounted on _ddcu:
n library files recorded in SYS$SYSROOT:[SYSUPD]VMIORIG.TLR;
m revised library files recorded in SYS$SYSR00T:[SYSUPD]VMIDIFF.TLR;
The current tailoring environment has been recorded in VMIORIG.TLR.
If a
power failure or drastic error occurs during this installation, you can
restore the environment by entering the following commands after mounting
the library disk.
Please see your documentation for more details.
$ ©SYS$UPDATE:VMSTAILOR COPY VMIORIG
$ DELETE SYS$UPDATE:VMIORIG.TLR
(n blocks were made available by tailoring.)
Deleting tailored software configuration.

The tailored software configuration is automatically restored when the
installation is complete. The number of library files recorded depends on the
number of library files on your system disk when the installation begins. If
any revised library files are recorded, refer to Section 5.5.2 for instructions on
how to resolve file conflicts.
When you have completed the installation, you will receive a message that
announces the restoration of the original software configuration.
If you do not have enough space left on the system disk to restore your
original tailored environment, you will receive the following message:
There are not enough free blocks left on the system disk to restore your
original tailoring environment.
The environment has been recorded and
may be restored manually (as described above) after sufficient space has
been obtained by purging and/or deleting files.
Only x blocks of the required y are available!

Variables x and y represent the number of free blocks on the system disk
after the installation and the total number of blocks in the original software
configuration, respectively.
You should free enough space on the system disk to accommodate the
total software configuration, and then restore it with the tailoring command
COPY, as shown below:
Tailor> COPY VMIORIG

5-12

VMSINSTAL Command Procedure

Alternatively, you may choose to reconfigure a new system disk that
is compatible with the available disk space. (See the VAX/VMS System
Manager's Reference Manual for more information about the tailoring facility.)

5.5.2

Handling Revised Files Detected During Installation
Revised files should not be detected during most optional software
installations. However, if revised files are found, you will receive an
appropriate message followed by a listing of the revised files. Here is an
example:
10 revised library files recorded in SYS$SYSR00T:[SYSUPD]VMIDIFF.TLR;.
'/.VMSINSTAL-E-LIBDIFF, The following system and library disk files do not match.
[SYSEXE]ANALIMDMP.EXE
[SYSEXE]ANALYZBAD.EXE
[SYSEXE]AUTHORIZE.EXE
[SYSEXElB00T58.EXE
[SYSEXE]B00TBL0CK.EXE
[SYSEXE]CDU.EXE
[SYSEXE]DISKQUOTA.EXE
[SYSEXE]EDT.EXE
[SYSEXE]EVL.EXE
[SYSEXE]EXCHANGE.EXE
'/.VMSINSTAL-F-LIBDIFF2,
You must resolve these differences before continuing.
*/,VMSINSTAL-F-UNEXPECTED, Installation terminated due to unexpected event.

As the last line of the message states, the installation is terminated and you
will have to determine which of the revised files you want to keep and which
you want to delete before you attempt to do the installation. Then you must
remove all the named files from the system disk so VMSINSTAL can proceed
when reinvoked.

5.6

Error Messages
This section describes the error messages issued by the VMSINSTAL
command procedure. Each message consists of an abbreviation followed
by a text message. The list includes an explanation of each message, and
appropriate user action.
ACCOUNT,

This installation creates an account named name.

Explanation: The product being installed has created (or
updated) an account with the specified name. The user
authorization file (SYSUAF) has been updated accordingly.

User Action:

None.

5-13

VMSINSTAL Command Procedure

ACTIVE,

The following processes are still active:

Explanation: VMSINSTAL checks to ensure that no user
processes are active when an installation is begun. This check
has failed, and VMSINSTAL lists those processes that are still
active.
User Action: You will be asked if you want to continue the
installation. It is recommended that you remedy this situation
before continuing.
AUTOSYNC,

Auto-answer file is not synchronized to the current
question

Explanation: You have specified the auto-answer option, and
VMSINSTAL is using the answers from an existing answer file.
The question being asked by the installation procedure does not
correspond to the next question and answer in the answer file.
User Action:

The installation procedure must have changed.
Delete the existing answer file and begin the installation again.
BACKUPERR,

An error has occurred in recreating the save set

Explanation: A BACKUP error was detected while recreating the
save sets in the processing of the GET option. The operation will
be aborted.

User Action: Be sure the specified output device has media
which can be written.
BAD ACC,

Unable to CREATE/UPDATE account named name.

Explanation: The product being installed has either tried to
create an account that already exists or has tried to modify a
nonexistent account.

User Action:

If you can determine the problem and resolve it,
then simply install the product again. Otherwise, contact your
DIGITAL field service representative.
BADCONDEV,

Please specify an existing console device.

Explanation: You have specified a console device on which the
console volume is to be mounted, but the device specified is not
a console device.

User Action:

5-14

Specify an existing console device.

VMSINSTAL Command Procedure

BADDISDEV,

Please specify a disk or tape device.

Explanation: You have specified a device on which the
distribution volumes are to be mounted, but the device is neither
a disk nor a tape.

User Action:

Specify a disk or tape device.

Directory directory does not exist.

BADDISDIR,

Explanation: You are trying to restore the distribution kit from a
nonexistent directory.

User Action:

Specify the correct directory when you invoke

VMSINSTAL.
BADGETDIR,

Directory directory does not exist.

Explanation: You are trying to copy the specified product save
set to a nonexistent directory.

User Action:

Specify the proper directory when you invoke

VMSINSTAL.
BADLIBDEV,

Please specify an explicit disk drive.

Explanation: For tailored configurations, you have specified a
device on which the library disk is to be mounted, but the device
is not a disk.

User Action:
BADSPEC,

Specify a disk device.

File specification cannot be parsed using default
specification.

Explanation: VMSINSTAL cannot locate the file because of an
invalid file specification.
User Action:

If you can determine the problem and resolve it,
then simply install the product again. Otherwise, contact your
DIGITAL field service representative.

CREATDIR,

Creating temporary directory DIR-NAME.

Explanation: This is an informational message. VMSINSTAL
creates a temporary directory if the G option is specified.

User Action:

None.

5-15

VMSINSTAL Command Procedure

CTRLY,

Installation cancelled via CTRL/Y.

Explanation: This is an informational message that appears
when you cancel the installation by entering a CTRL/Y.

User Action:
DECNET,

None.

Your DECnet network is up and running.

Explanation: VMSINSTAL checks to ensure that your DECnet
network has been shut down when an installation is begun. This
check has failed.
User Action:

You will be asked if you want to continue the
installation. It is recommended that you remedy this situation
before continuing.
DEVALLOC,

Device device-name already allocated to another user.

Explanation: You have specified a device that is allocated
to another user in response to the prompt "Where will the
distribution volumes be mounted?". You will be prompted again
for another device.

User Action:

Provide a device name that is not already
allocated to another user.

DEVMNT,

Device device-name will be mnt-status.

Explanation: This is an informational message telling you the
device specified for the output of the G option will be initialized
(if it is a disk) and mounted. This message is issued only if the
specified output device is not mounted when VMSINSTAL is
invoked.

User Action:
DEVNOTEXIST,

None.
Device device-name does not exist.

Explanation: The device specified for the output of the G option
does not exist.

User Action:

5—1 6

Specify a valid device name.

VMSINSTAL Command Procedure

ILLSAVESET,

Illegal save set name specified to RESTORE—
SAVESET.

Explanation: The product installation procedure contains an
incorrect call to RESTORE—SAVESET.
User Action:

Contact your DIGITAL field service

representative.
INSFAIL,

The installation of product-name has failed.

Explanation: The product installation did not exit with a
successful status.

User Action:

Examine the console output to determine the
cause of the error. If you are unable to resolve the problem,
contact your DIGITAL field service representative.
INSDFAIL,

The installation of a product has failed.

Explanation: An error occurred while attempting to do deferred
callbacks during the installation.

User Action:

Examine the console output to determine the
cause of the error. If you are unable to resolve the problem,
contact your DIGITAL field service representative.
INTEGER,

Please enter an integer value.

Explanation: VMSINSTAL asked a question that must be
answered by specifying an integer.

User Action:
INVOPTIONS,

Answer the question again, specifying an integer.

To specify options, parameter 3 must be the word
OPTIONS.

Explanation: If you are specifying VMSINSTAL options, the
third parameter to VMSINSTAL must be the word OPTIONS.

User Action:

Invoke VMSINSTAL again, specifying the options
in the correct format.

5-17

VMSINSTAL Command Procedure

IVPFAIL,

The IVP for product has failed.

Explanation: VMSINSTAL has invoked the installation
verification procedure (IVP) for the specified product, and the
IVP has failed.
User Action:

If you can determine the problem and resolve it,
then simply install the product again. Otherwise, contact your
DIGITAL field service representative.
LIBDIFF,

The following system and library disk files do not match.

LIBDIFF2,

You must resolve these differences before you continue.

Explanation: The following system and library disk files do not
match. You must resolve these differences before continuing.
For tailored systems, VMSINSTAL temporarily removes all
nonessential system files from the system disk. Before doing
this, however, it checks to ensure that the copies of these files on
the system disk match those on the library disk. This check has
failed, and the offending files are listed.

User Action:

You must resolve the differences before
reinvoking VMSINSTAL.
LOWQUOTA,

One or more account quotas may be too low.

Explanation: VMSINSTAL checks to ensure that your process
quotas are valid when an installation is begun. This check has
failed.

User Action: You will be asked if you want to continue the
installation. It is recommended that you remedy this situation
before continuing. See Section 5.1.
MOVEFILES,

Files will now be moved to their target directories.

Explanation: This is an informational message. If sufficient
disk space is available at the beginning of an installation,
VMSINSTAL builds new files in a working directory for the
optional product or update. After all the files are built, they are
moved to their target directories.

User Action:

5-18

None.

VMSINSTAL Command Procedure

NOACCMAN,

Account manipulation on alternate roots not
supported.

Explanation: The product being installed to an alternate system
root cannot update the user authorization file (SYSUAF).
User Action:

Do not attempt to update the user authorization
file from an alternate system root.

NOCONSOLE,

Unknown CPU type number. Console volume
cannot be remounted.

Explanation: While attempting to remount the console volume,
VMSINSTAL could not determine what type of CPU you have.

User Action:

Contact your DIGITAL field service

representative.
NOFILE,

[new] file file does not exist.

Explanation: VMSINSTAL is attempting to locate an existing (or
perhaps new) file with the given name, but the file cannot be
found.

User Action:

If you can determine the problem and resolve it,
then simply install the product again. Otherwise, contact your
DIGITAL field service representative.
NOLIBDISK,

Library disk could not be mounted.

Explanation: You were asked to mount the library disk so that
an installation could be performed on a tailored system. For
some reason, the library disk could not be mounted.

User Action:

Correct the situation that prevented mounting the
library disk and begin the installation again.
NOPRINT,

File file cannot be printed.

Explanation: The product installation required the printing of
one or more files, but the files could not be queued for printing.

User Action:

This error is most likely caused by an undefined
SYS$PRINT queue at your site. If you do not care that the
files could not be printed, then you can ignore this message.
Otherwise, define a SYS$PRINT queue and perform the
installation again.

5-19

VMSINSTAL Command Procedure

NOPROC,

The kit installation procedure is missing.

Explanation: The main installation procedure for the product
could not be located on the distribution volumes.

User Action:

Contact your DIGITAL field service

representative.
NOPRODS,

None of the specified products were found.

Explanation: You have specified one or more products to be
installed from the distribution volumes, but none of the products
exists on the volumes.
User Action:
NORELNOTE,

Specify products that exist on the volumes.

Unable to locate release notes.

Explanation: You have specified option N during a layered
product installation for a product that does not include online
release notes.
User Action:
NOSAVESET,

None.

Required save set letter does not exist.

Explanation: The product save set with the specified letter,
which is required for the installation, does not exist on the
distribution volumes.

User Action:

Contact your DIGITAL field service

representative.
NOSETPRV,

You are not running on an account with SETPRV
privilege.

Explanation: VMSINSTAL checks to ensure that your account
has SETPRV privilege when an installation is begun. This check
has failed.

User Action:

You will be asked if you want to continue the
installation. It is recommended that you remedy this situation
before continuing.

5-20

VMSINSTAL Command Procedure

NOSPACE,

There are not enough blocks to restore the system disk.

Explanation: After installation on a dual-RL02 system,
VMSINSTAL attempts to restore your system disk to its original
tailoring configuration. However, there are not enough free
blocks left on the system disk.

User Action: VMSINSTAL tells you how many additional free
blocks are required. You must make more space on the system
disk by purging and/or deleting files. Once this is accomplished,
you can restore the original tailoring configuration, as described
in Section 5.4.
Remote node nodename not known or unavailable.

NOSUCHNODE,

Explanation: The product is being installed on a remote node
that is either not known or unavailable.

User Action:
NOTSYSTEM,

Specify an existing node name.

You are not logged in to the SYSTEM account.

Explanation: VMSINSTAL checks to ensure that you are logged
in to the SYSTEM account when an installation is begun. This
check has failed.

User Action:

You will be asked if you want to continue the
installation. It is recommended that you remedy this situation
before continuing.
NULSAVESET,

Null save set name specified to RESTORE—
SAVESET.

Explanation: A product installation procedure contained an
incorrect call to RESTORE—SAVESET.
User Action:

Contact your DIGITAL field service

representative.
PEAKUTIL,

This product requires number blocks during installation.

Explanation: The installation procedure for the product has
determined that there are not enough free blocks on the system
disk to install the product.

User Action:

Make more space on the system disk by purging
and/or deleting files, and then install the product again.

5-21

VMSINSTAL Command Procedure

PRODSKIP,

Products that have not been installed will be skipped.

Explanation: You have requested that multiple products be
installed, but one of these products requires that the system be
rebooted after its installation. To accomplish this, the remaining
uninstalled products must be skipped.

User Action:

Reinstall the remaining products after the system

is rebooted.
REBOOT,

This product requires that the system be rebooted.

Explanation: The product that was just installed requires that
the system be rebooted to complete the installation.

User Action:
RECORDANS,

Reboot the system after shutdown completes.

Auto-answer file will be recorded.

Explanation: The auto-answer option was specified when
VMSINSTAL was invoked. No answer file exists for the product
about to be installed, so one will be recorded.
User Action:

Answer the prompts and questions as usual. Your
answers will be recorded.

RECOVER,

Product was being installed when the system failed.

Explanation: The specified product was being installed when
the system failed because of a power failure or other problem.

User Action:

You will receive additional instructions on how to

proceed.
RESTORE,

Restoring product save set letter . . .

Explanation: The specified product save set is about to be
restored from the distribution volumes by the Backup Utility.
User Action:
RETAILOR,

None.

Your original tailoring environment will now be
restored.

Explanation: The tailoring files that were removed from your
system disk for installation will be copied back to the system
disk.

User Action:

5-22

None.

VMSINSTAL Command Procedure

REWIND,

The tape will be rewound to try again.

Explanation: VMSINSTAL is attempting to restore a product
save set with the Backup Utility. The required save set was
not located on the currently mounted distribution tape, but
VMSINSTAL will rewind the tape in case the save sets were not
recorded in order.

User Action:

This message will be preceded by various serious
BACKUP messages, which can be ignored.

SMALLDISK,

This is a small disk system.

Explanation: VMSINSTAL has determined that you are running
a tailored system. It will temporarily remove all nonessential files
from the system disk in order to make room for the installation.
User Action:

You will receive additional instructions as to how

to proceed.
SYSDIR,

This product creates system directory directory.

Explanation: The product being installed creates the specified
system directory.

User Action:
SYSDISK,

None.

This product creates system disk directory directory.

Explanation: The product being installed creates a directory on
the system disk.

User Action:
TAMPER,

None.

File file has been tampered with.

Explanation: VMSINSTAL is attempting to update a system text
file, but the file has been modified locally. The update cannot be
performed.

User Action:

If you modify system text files, they cannot be
updated by DIGITAL software installations.

5-23

VMSINSTAL Command Procedure

UNEXPECTED,

Installation terminated due to unexpected event.

Explanation: Some unexpected event has caused the immediate
termination of VMSINSTAL. This message should be preceded
by other messages that explain the problem in greater detail.

User Action:

If you can determine the problem and resolve it,
then simply install the product again. Otherwise, contact your
DIGITAL field service representative.

UPDATED,

File file is already updated.

Explanation: VMSINSTAL is attempting to update a system text
file, but the file has already been updated successfully.

User Action:
USEANS,

None.

Auto-answer file will be used.

Explanation: The auto-answer option was specified when
VMSINSTAL was invoked. An answer file exists for the product
about to be installed, so the recorded answers will be used.

User Action:

You will not have to answer prompts and
questions displayed by the product. If you want to record
new answers, then you must delete the answer file and install
the product with the auto-answer option.

VMIORIG,

VMIORIG.TLR still exists; please see your documentation.

Explanation: When performing an installation on a
tailored system, VMSINSTAL records the current tailoring
configuration and then removes it from the system disk
temporarily. The configuration is recorded in the file
SYS$UPDATE:VMIORIG.TLR. After installation, VMSINSTAL
restores the configuration and deletes VMIORIG.TLR. However,
if the system crashes during the installation, then you must
restore the configuration and delete the file manually. See
Section 5.4.

User Action:

Because VMIORIG.TLR still exists, VMSINSTAL
assumes that you have not restored your tailoring configuration.
You must do so, and then delete VMIORIG.TLR.

5-24

VMSINSTAL Command Procedure

YESNO,

Please enter YES or NO.

Explanation: VMSINSTAL asked a question that must be
answered with YES or NO.

User Action:

Answer the question again, specifying YES or
NO. You may abbreviate these as Y or N.

5-25

Upgrading To Version 4.4

This chapter tells you how to upgrade your VAX/VMS operating system
from Version 4.2 or later to Version 4.4. If your operating system is not
currently at 4.2 or 4.3, you will have to update to Version 4.2 before you can
upgrade to Version 4.4.
When you complete the upgrade to Version 4.4, you must perform a
mandatory update using the appropriate mandatory update kit:
•

If you have a VAX 8600, use the kit labeled VAX/VMS V4.4 BIN 16MT9
MANDATORY UPDATE BB-FY83*-BE, where the asterisk represents the
most recent version.

•

If you have a VAX 8200, use the kit labeled VAX/VMS V4.4 BIN RX50
MANDATORY UPDATE BLHC59*-BE, where the asterisk represents the
most recent version.

•

If you have a VAX-11/780, VAX-11/782, or VAX-11/785, use the kit
labeled VAX/VMS V4.4 BIN RX01 MANDATORY UPDATE AS-FY81*-BE,
where the asterisk represents the most recent version.

•

If you have a VAX-11/750, VAX-11/730, or VAX-11/725, use the kit
labeled VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE BE-FY82*-BE,
where the asterisk represents the most recent version.

Note
Follow the instructions provided in the VAX /VMS Release Notes,
Version 4.4, to perform the upgrade and the mandatory update
procedures. This chapter contains a general description of the
upgrade procedure, but does not include information that is
specific to the Version 4.4 upgrade procedure.
A major part of the upgrade is automated and does not require an operator
to be present. For this reason, you should perform the upgrade from a
hardcopy device to preserve a record of the events that occur during the
upgrade.
Section 6.1 lists the steps you should take before you start the upgrade. The
upgrade procedure is described in Section 6.2. Sections 6.3 through 6.5 deal
with postupgrade information.
Here is a list of materials you need to do the upgrade:
•

The Version 4.4 software distribution kit

6-1

Upgrading To Version 4.4

•

A disk on which to build the upgraded system

•

A blank console volume (RL02 if you have a VAX 8600 or 8650, RX50
diskette if you have a VAX 8200, RX01 diskette if you have a VAX-11
/780, VAX-11/782, or VAX-11/785; TU58 if you have any other VAX
processor.)

•

A blank library disk if you are upgrading to a tailored environment

Before beginning the upgrade, read the entire procedure to ensure that you
are aware of all upgrade requirements.

Note
If you have changed the names of system directories in your
current operating system, or deleted VAX/VMS files from them,
the upgrade procedure may not work correctly. Restore your
operating system to a standard system before you begin the
upgrade.
The upgrade procedure was engineered so layered products should not
have to be reinstalled. However, certain layered products may need to be
reinstalled because of product-specific installation procedures. For example,
products that create directories that are synonymous with system directories
must be reinstalled.
Note the following restrictions before beginning the upgrade:
•

As part of the upgrade, the paging, swapping, dump, and authorization
files are purged to one version.

•

Everything in the [SYSERR] directory is deleted.

•

All operator and accounting logs are deleted. If you want to keep any of
the files, move them to a user directory before starting the upgrade.

•

The upgrade cannot be applied to a tailored system. A tailored system
must be installed on a separate, clean disk.

DIGITAL recommends that you back up your system disk and console RL02
(VAX 8600 and 8650 only) before performing the upgrade. Use the command
procedure SYS$UPDATE:CONSCOPY to back up a console RL02.
If the upgrade is interrupted for any reason, it can resume from the point at
which the system was most recently booted. The system reboots three times
during the upgrade.
If you want the upgrade to resume automatically, you must boot the system
exactly as requested by the upgrade procedure after the planned system
shutdown in Phase 1.

6-2

Upgrading To Version 4.4

To allow the upgrade procedure to resume at any point, the procedure copies
the Version 4.4 system files in an alternate disk directory root (SYSF) from
your current system's files, (SYSO through SYSD). This ensures that you have
at least one set of bootable system files at all times.

6.1

Preparing to Upgrade the System
Take the following steps to prepare for the upgrade. Note that the system
disk and the distribution volume cannot be moved from one device to
another during the upgrade.
1

Use standalone BACKUP to back up the system disk to a scratch disk.
(A step-by-step procedure for backing up your system disk is given in
Chapter 4).

If your current system disk can be removed, store it in a safe place so
that it is readily available if needed. Use the backup copy to upgrade
your system.

Note
If you have a VAX 8600/8650, use the command procedure
SYS$UPDATE:CONSCOPY to create an RL02 backup copy of
your console media.
4

Boot the backup copy of your system disk (or your current system disk,
if it cannot be removed).
If you are upgrading a VAX system other than a VAX 8600/8650 or
VAX-11/750, put the system in console mode, halt the processor and
type the following command:
»> B ddu

Proceed to the next step.
If you are upgrading a VAX 8600/8650, use the following method to
boot the backup copy of your system disk:
1

Shut down your system.

Replace the console RL02 disk with the backup RL02.

Set the left keylock switch on the front panel of the processor to
Restart Boot

Type the following at the console terminal:
»> REBOOT

6-3

Upgrading To Version 4.4

Proceed to the next step.
If you are upgrading a VAX-11/750, use one of the following boot
methods:
•

If you have a switch position on the BOOT DEVICE switch allocated
to the system device, set the switch to the appropriate position and
type the letter B at the console terminal. If you are not sure of the
correct setting, contact your DIGITAL field service representative.

•

If you do not have a position on the BOOT DEVICE switch for the
system device and want to boot the disk directly, press CTRL/P to
change to console mode, and type the following command:
»> B ddcu

where ddcu refers to the device name of your system device. See
Chapter 4 for help with device names.
•

If you want to boot using the TU58, insert the console TU58 in the
console drive and set the BOOT DEVICE switch to position A. Then
press CTRL/P to go into console mode and type this command:
»> B/800 DDAO

Then when you get the BOOT58 prompt, type this command:
B00T58> B ddcu

where ddcu is the device name of the system device.
If you decide to boot from the TU58 cartridge, be sure to reply YES when
the upgrade procedure asks if you want to boot from the TU58.
5

When the backup copy of your system disk boots, log in under the
system manager's account, SYSTEM. (You may want to consider having
a second terminal logged in for doing support tasks during the upgrade.)

A minimum of 16,000 free blocks must be available on the system disk
being upgraded. If space is not available, delete as many user files
as necessary to get it. You can confirm the free block count with the
following command:
$ SHOW DEVICES/FULL ddcu:

where ddcu is the device name of the drive that contains the backup
copy of your system disk.
7

Make sure the restart switch on your processor control panel is set
to automatic restart. The upgrade will continue automatically after
shutdowns as long as this switch is positioned as shown in the following
table.

6-4

Upgrading To Version 4.4

VAX System

Restart Switch

Required Setting

VAX-11/725
VAX-1 1/730
VAX-11/750
VAX-1 1/780

AUTO/RESTART BOOT
AUTO/RESTART BOOT
POWER ON ACTION
AUTO/RESTART

ON
ON
(RESTART)
ON

VAX 8200

Top keyswitch
Bottom keyswitch

VAX 8600

Left keyswitch

ENABLE
AUTO START
RESTART/BOOT

Type the following command to prevent users from logging in to the
system:
$ SET L0GINS/INTERACTIVE=0

If the network is running, shut it down. Enter the following commands:
$ RUN SYS$SYSTEM:NCP
NCP>SET EXECUTOR STATE OFF
NCP>EXIT

10 Stop all queues to avoid locked-file errors during the upgrade. Note that
queues are initialized during the upgrade, and any jobs pending will be
lost. Check to see if there are any jobs in the queues with the following
command:
$ SHOW QUEUE/DEVICE/BATCH/FULL/ALL

If no queues are set up, an appropriate message will be displayed and
you may bypass this step.
Use the following DCL command to stop each queue:
$ STOP/QUEUE/NEXT queue-name

where queue-name is the name of a queue.

6-5

Upgrading To Version 4.4

6.2

Performing the Upgrade
At this point, begin the upgrade procedure.
1

Place the VAX/VMS Version 4.4 distribution volume on the appropriate
drive. If you are using a tape drive, put the drive on line; if you are
using a disk drive, spin up the disk.

Invoke the VMSINSTAL command procedure.
$ ®SYS$UPDATE:VMSINSTAL

VMSINSTAL responds by announcing itself and asking if you have a
satisfactory backup copy of your current system:
VMS Software Product Installation Procedure
It is <date> at <time>
Enter a question mark (?) at any time for help.
♦Are you satisfied with the backup of your system disk [YES]?

If you have backed up your system disk, press the RETURN key to
continue with the upgrade.
If you have not backed up your system disk, you may exit from
VMSINSTAL to do so by entering NO. VMSINSTAL will return you
to DCL level so that you can perform the backup. When the backup is
completed, invoke VMSINSTAL to restart the upgrade.

Next, VMSINSTAL requests the name of the drive holding the
distribution volume. Enter the device name in the ddcu: format.
For example, if the distribution volume is a magnetic tape mounted in a
TS11 that is the first device on the UNIBUS, enter MSAO:. See Chapter 4
if you need more ir 'ormation on device names.
The upgrade procedure may abort if you type the device name
incorrectly. If you specify a nonexistent device or a device that is not
connected, an "invalid device" error message will be displayed. If this
happens, use the DCL command SHOW DEVICES to verify the device
status.

When VMSINSTAL prompts you for the name of the product you wish
to install, respond by entering VMS.

When your distribution volume is ready for mounting, enter Y.
VMSINSTAL responds with the following messages:

6-6

Upgrading To Version 4.4

‘/.MOUNT-I-MOUNTED,

VMS044

mounted on _ddcu:

The following products will be installed:
VMS

V4.4
Beginning installation of VMS 4.4 at <dd-mmm-yyyy hh-mm>

'/.VMSINSTAL-I-RESTORE,

Restoring product save set A. . .
VAX/VMS V4.4 Upgrade Procedure

If you are using a tape distribution volume, there will be a pause of
several minutes between the first and second lines.
7

Next, the procedure describes the upgrade and discusses the automatic
restart capability.

This is followed by a set of messages that describe cautions and
requirements related to doing the upgrade:
•

First the procedure states that the kit must be stored in directory
[000000]. The kit is stored in [000000] by default.

•

Then you are cautioned about preserving files that may be deleted
by the upgrade.

•

Next, the procedure notes the importance of RESTAR.CMD matching
your memory interleaving.

•

The procedure describes how AUTOGEN may attempt to change the
size of your paging file and swapping file if you do not manually
override it.

•

If you have DECnet-VAX installed, you must reapply the DECnetVAX license after an upgrade to VMS; the DECnet-VAX license is
packaged in a separate distribution kit.

•

If you are upgrading a VAX-11/785, you are told that the default
bootstrap command procedure must be set to boot the system device
before you start the upgrade.

If you indicate that you want to interrupt the upgrade to comply with
any of these conditions, the procedure returns you to DCL command
level and the upgrade terminates. If you do this, you must reinvoke
VMSINSTAL when you are ready to resume the upgrade. The point at
which the upgrade resumes is determined by your system configuration.
•

If your distribution medium is located on an HSC disk, the procedure
asks for the name of the HSC (for example, HSC001). See the HSC
User Guide for details on HSC names.

6-7

Upgrading To Version 4.4

•

If your system includes either a CI780 or CI750, the upgrade gives
you the option of creating a common disk for a VAXcluster.

•

If your system does not include a CI780 or CI750 and the system
disk has fewer than 70,000 blocks, the upgrade gives you the option
of building a tailored system.

Note
If you intend to tailor a system that includes only two
disk drives,—that is, a dual-RK07 configuration or a
VAX-11/725—you will not be able to install any optional
product distributed on large-disk media. For example, if
your disk storage is limited to just two RK07 disk drives,
you will not be able to install any optional product
distributed on an RK07 distribution kit.
If you decide to tailor your system, the upgrade procedure will
prompt you for the name of the device you will use to build the
LIBRARY disk.
•

If DECnet-VAX is installed on your system (as determined by the
presence of the file SYS$SYSTEM:NETNODE.DAT), the upgrade
procedure lets you select a DECnet-VAX area for your system. For
more information on area routing, see the VAX/VMS Networking

Manual.

6.2.1

Upgrade Phase 1
The upgrade consists of five phases. Two descriptions are provided for Phase
1: one for users upgrading systems other than VAX-11/750 and one for
users upgrading VAX-11/750 systems. The final four phases are common to
all VAX systems.

Note
Throughout this section, all command procedures used for
upgrading a VAX 8600/8650 will use file extension .COM in
place of .CMD.

6-8

Upgrading To Version 4.4

6.2.1.1

Upgrade Phase 1 for VAX—11/725, VAX-11/730, VAX-11/780, and
VAX 8600 Systems
1

To ensure system security, the upgrade procedure requires you to change
the passwords for the SYSTEM, SYSTEST, and FIELD accounts before
continuing. The first time you set these passwords, the system requires a
password of six or more characters.

The upgrade procedure turns off the disk quotas on the system disk
and removes directory entries that point to nonexistent files. If disk
quotas are not running on your system, an appropriate error message is
displayed. You may ignore this message.

Your upgraded system will be built in system root SYSF. At this point
the upgrade procedure will prompt you through the building of a new
console volume that will let you boot the new system from SYSF.
Specifically, the procedure will change the default bootstrap command
procedure DEFBOO.CMD (DEFBOO.COM on VAX 8600 processors) on
the new volume to boot from SYSF.

The procedure prompts you to insert your current console volume in the
console drive. Your current console volume (the procedure calls it your
"old" console volume) is used as a base to build the new console volume
but it is not altered by the procedure.

When you indicate that you are ready to continue, the procedure copies
your old console volume to a disk directory.

The procedure prompts you to set DEFBOO.CMD to boot the backup
copy of your system disk (assuming you have not done so previously).
Using the form dduBOO.CMD, enter the name of the boot file you want
to copy to DEFBOO.CMD. For example, if the system disk is in DBA1,
you enter DBlBOO.CMD. If the system disk is controlled by either an
HSC or a UDA, the revised version of CIBOO.CMD or DUABOO.CMD
that you built when you first installed VAX/VMS on the HSC- or the
UDA-controlled system disk must be used. The selected command
procedure must be able to boot the system disk from the drive where
you have placed it without any operator intervention (for example,
registers RO through R5 must be correctly initialized by the command
procedure).
Do not specify a conversational boot command file. The upgrade kit
parameters will boot any system. The procedure builds a conversational
boot file (UPGGEN.CMD) that boots from SYSF, but you should only
use this file for situations prescribed by the procedure.

6-9

Upgrading To Version 4.4

Next, store the old console volume for safekeeping and insert a blank
volume in the console drive. Do not remove this volume for the rest of
the upgrade.

Note
If you have a VAX 8600/8650, your old console RL02 is used
during this upgrade. A new one is not created, therefore, you
should have a backup copy of your console RL02.
Note
If the new console volume is a TU58, ensure the RECORD
switch is set to permit writing; that is, the switch should
be slid in the direction of the arrow inscribed on it. If the
new console volume is a diskette, ensure that it is NOT
write-protected.

The procedure gives you the opportunity to use the Bad Block Locator
Utility (BAD) to check the new console volume for defective blocks.
DIGITAL recommends that you run BAD on the new console volume. If
you choose to run BAD, allow an additional 30 minutes if you are using
a TU58 volume or an additional 15 minutes if you are using a diskette
volume.

Note
The Bad Block Locator Utility is not used for upgrades on the
VAX 8600/8650.
Details on running BAD can be found under the ANALYZE/MEDIA
command in the VAX/VMS DCL Dictionary or in the VAX/VMS Bad Block

Locator Utility Reference Manual.
9

Finally, the procedure initializes the new console volume. Just before the
first reboot, the procedure will copy the console files from the disk to this
new console volume.

Note
Unless you are upgrading to a tailored system or using RL02
distribution media, you should not have to intervene in the
upgrade from this point on.
10 The upgrade purges directories and removes installed images. If you
are building a tailored system, the procedure tells you that you will be
needed to prepare the LIBRARY disk in Phase 2 of the upgrade.
11 Next, the procedure builds the directory tree in SYSF and deletes all
operating system files not needed to complete the upgrade.

1 2 The upgrade procedure restores the Version 4.4 required save set to the
backup copy of your system disk and verifies that the save set files have
been restored correctly.

6-10

Upgrading To Version 4.4

1 3 When the verification pass is complete, the upgrade procedure purges
the paging, swapping, dump, and authorization files and puts the current
version in the new directory tree.
14 After using AUTOGEN to save your old SYSGEN parameters and
preparing the startup command file for Phase 2, the upgrade procedure
copies the console files to the new volume and builds its boot block in
preparation for the first reboot.
1 5 The procedure tells you it will shut down to reboot the partially
installed Version 4.4 system. It also tells you that the upgrade continues
automatically after the reboot but that if you must restart the upgrade
manually, simply enter the letter B.

1 6 Then the procedure cautions you not to move the distribution volume
nor the system volume and not to change the SYSGEN parameters for
the remainder of the upgrade.
1 7 Next, the procedure tells you how to handle a shutdown failure or a
reboot failure.
•

On a VAX-11/730 system, the microcode may be reloaded. If the
system fails to boot correctly, power the system off and then on
again so that the console will reload the microcode from the newly
created TU58.

•

If the system fails to boot in a CI780 environment because of
insufficient nonpaged dynamic memory, use the conversational boot
command procedure UPGGEN.CMD to increase the NPAGEDYN
system parameter:
»> OUPGGEN.CMD
SYSB00T> SET NPAGEDYN 120000
SYSB00T> CONTINUE

Note
An incorrect NPAGEDYN parameter implies that AUTOGEN did
not function correctly. If you need to increase this parameter,
submit a Software Performance Report that describes your
complete hardware configuration and what you did to get the
system to boot.
When the system reboots, it identifies itself and announces the beginning of
Phase 2.
VAX/VMS Version 4.4 <dd-mm-yyyy hh:mm>

Skip to Section 6.2.2, which describes Phase 2.

6-11

Upgrading To Version 4.4

6.2.1.2

Upgrade Phase 1 for VAX-11/750 and VAX 8200 Systems
This section describes the first phase of the upgrade for users who are
upgrading VAX-11/750 or VAX 8200 systems.
1

To ensure system security, the upgrade procedure requires you to change
the passwords for the SYSTEM, SYSTEST, and FIELD accounts before
continuing. The system requires a password of six or more characters.

The upgrade procedure turns off the disk quotas on the system disk and
removes directory entries that point to nonexistent files. If you are not
running disk quotas, an appropriate error message is displayed. You may
ignore this message.
You are asked if you want to boot using the console volume rather than
directly from the disk. If you have a CI750, you must answer YES to
this question. DIGITAL recommends that you answer YES in any case to
ensure that your console volume contains the latest versions of the VMB
and BOOT58 programs.
If you choose to boot directly from the system disk, skip the next step
and go to step 4.

Your upgraded system will be built in system root SYSF so that your
current system in SYSO is available if needed. At this point, the
procedure will guide you through the building of a new console volume
if you indicated in step 2 that you would be booting from the console
volume. Specifically, the procedure will change the default bootstrap
command procedure (DEFBOO.CMD) on the new volume to boot from
SYSF.

On a VAX-11/750, position the BOOT DEVICE switch on your
processor control panel to position A and leave it in position A for
the rest of the upgrade.

The procedure prompts you to insert your current console volume
in the console drive. Your current console volume (the procedure
calls it your "old" console volume) is used as a base to build the new
console volume but it is not altered by the procedure.

When you indicate you are ready to continue, the procedure copies
your old console volume to a disk directory in Files-11 format.

6-12

Upgrading To Version 4.4

must be used. The selected command procedure must be able to
boot the system disk without any operator intervention (for example,
registers RO through R5 must be correctly initialized by the command
procedure).
Do not specify a conversational boot command file. The upgrade
kit parameters will boot any system. The procedure builds a
conversational boot file (UPGGEN.CMD) that boots from SYSF,
but you should only use this file for situations prescribed by the
procedure.

When this is done, put your old console volume away for
safekeeping and insert a blank volume in the console drive. This
volume must remain in the console drive for the rest of the upgrade.

Note
If your new console volume is a TU58, ensure that the
RECORD switch is set to permit writing, that is, the
switch should be slid in the direction of the arrow
inscribed on it. If your new console volume is a diskette,
ensure that it is NOT write-protected.
f

The procedure gives you the opportunity to use the Bad Block
Locator Utility (BAD) to check the new console volume for defective
blocks. DIGITAL recommends that you run BAD on the new console
volume. If you choose to run BAD, allow an additional 30 minutes if
you are using a TU58 volume or an additional 15 minutes if you are
using a diskette volume.
Details on running BAD can be found under the ANALYZE/MEDIA
command in the VAX/VMS DCL Dictionary or in the VAX/VMS Bad

Block Locator Utility Reference Manual.
Q

Finally, the procedure initializes the new console volume. Just before
the first reboot, the procedure will copy the console files from the
disk to this new console volume.

Note
Unless you are upgrading to a tailored system or using RL02
distribution media, you should not have to intervene in the
upgrade from this point on.
4

The upgrade procedure now cleans up its directories and removes
installed images. If you are building a tailored system, the procedure
tells you that you will be needed to prepare the LIBRARY disk in Phase
2 of the upgrade.

Next, the procedure builds the directory tree in SYSF and and deletes all
operating system files not needed to complete the upgrade.

6-13

Upgrading To Version 4.4

The upgrade procedure restores the Version 4.4 required save set to the
backup copy of your system disk and verifies that the save set files have
been restored correctly.

When the verification pass is complete, the upgrade procedure purges
the paging, swapping, dump, and authorization files and puts the most
current version in the new directory tree.

After using AUTOGEN to save your old SYSGEN parameters and
preparing the startup command file for Phase 2, the upgrade procedure
copies the console files to the new volume and builds a boot block on it
in preparation for the first reboot.

The procedure tells you it will shut down to reboot the partially
installed Version 4.4 system. It also tells you that the upgrade continues
automatically after the reboot and how to boot the new system if you
must restart the upgrade manually:
•

If you are booting from the console volume, you will reboot the
system from the BOOT58 command level. To invoke BOOT58 on a
VAX-750, press CTRL/P to put the system in console mode; then
enter the following command:
»> B/800 DDAO

To invoke BOOT58 on a VAX 8200, press CTRL/P to put the system
in console mode; then enter the following command:
»> B/R5 : 800 CSA1

Type the following command at the BOOT58 prompt:
B00T58> B

•

If you are booting from the disk, press CTRL/P to put the system in
console mode; then enter the following command:
»> B/F0000000 ddcu

where ddcu is the device name of the system disk.
1 0 If the system fails to boot in a CI750 environment because of insufficient
nonpaged dynamic memory, use the conversational boot command
procedure UPGGEN.CMD to increase the NPAGEDYN system
parameter. First, invoke BOOT58 as follows:
•

On a VAX-11/750 type

•

On a VAX 8200 type

»> B/800 DDAO

»> B/R5 : 800 DDAO

6—14

Upgrading To Version 4.4

Type these commands at the BOOT58 prompt:
B00T58> SUPGGEN.CMD
SYSB00T> SET NPAGEDYN 120000
SYSB00T> CONTINUE

Note
An incorrect NPAGEDYN parameter implies that AUTOGEN
did not function correctly. If you need to increase this
parameter, please submit a Software Performance Report
that describes your complete hardware configuration and
what you did to get the system to boot.
When the system reboots, it identifies itself and announces the beginning
of Phase 2.
VAX/VMS Version 4.4 <dd-mm-yyyy hh:mm>

This completes Phase 1 of the upgrade. The rest of the upgrade does not
require that an operator be present; however, if you are booting from
the console volume, you will have to manually reboot each time the
system shuts down (once in Phase 4 and once in Phase 5). If you are
booting from the disk, reboots are automatic and do not require operator
intervention.

6.2.2

Upgrade Phase 2
The rest of the Version 4.4 files in the LIBRARY and OPTIONAL save sets
are restored from the distribution kit. The order in which these components
are restored varies, depending on your configuration.
•

In a standard VAX/VMS configuration with either RK07, RA60, or
magnetic tape distribution media, the LIBRARY save set is restored, and
then the OPTIONAL save set is restored.

•

In a standard VAX/VMS configuration with RL02 distribution media, the
OPTIONAL save set is restored first. Then the procedure prompts you
to remove the first volume of the distribution kit and to insert the second
volume. After you comply, the LIBRARY save set is restored.

•

In a tailored VAX/VMS configuration (other than one using RL02
distribution media), there are two possible scenarios:

•

If you can mount the distribution volume and the scratch library disk
simultaneously, the procedure restores the LIBRARY save set to the
scratch library disk. Then it dismounts the library disk, remounts it as a
FILES-11 disk, and restores the OPTIONAL save set.

6-15

Upgrading To Version 4.4

•

6.2.3

If you cannot mount the distribution volume and the scratch library disk
at the same time, the procedure copies the LIBRARY and OPTIONAL
save sets to the system disk, dismounts the distribution volume, and asks
you to insert a scratch disk in its place. After you comply, the procedure
first restores the LIBRARY save set to the scratch disk, and then the
OPTIONAL save set.

Upgrade Phase 3
Phase 3 of the upgrade merges the VAX/VMS-distributed files that are
commonly edited by system managers with new VAX/VMS files. Ignore any
"file not found" error messages that appear at this time.
Next, the upgrade procedure merges all the miscellaneous user files that exist
in the old system directories into a new set of system directories, temporarily
called [SYSF.SYSEXE], [SYSF.SYSMGR], [SYSF.SYSLIB], and so on. The
amount of time this requires depends on the number of user files.

6.2.4

Upgrade Phase 4
During Phase 4 of the upgrade, the new site-specific console volume is
modified to allow reboot of the complete VAX/VMS Version 4.4 system.
Be sure the new site-specific console volume created in Phase 1 is in the
console drive (CSA1 for VAX 8600, VAX 8650, VAX 8200, VAX-11/780, and
VAX-11/750 systems; CS2 for VAX-11/730 and VAX-11/725 systems).
When the modification is complete, you receive the following message:
System shutting down to boot the complete Version 4.4 system.

Leave the newly created site-specific console volume in the console drive.
The system disk must also remain where it is in order to proceed to the next
phase of the upgrade.
The system will attempt an automatic reboot after the shutdown.

Note
If you are upgrading a VAX-11/750 or a VAX 8200 and are booting
from the console volume, you will have to reboot manually by
entering the letter B when you get the BOOT58> prompt.
If the system fails to boot at this point because of insufficient nonpaged
dynamic memory, you must use a standard conversational bootstrap to
increase the NPAGEDYN (nonpaged dynamic memory) system parameter.

Note
An incorrect NPAGEDYN parameter implies that AUTOGEN did
not function correctly. If you need to increase this parameter.
6-16

please submit a Sofware Performance Report that describe
complete hardware configuration and what you did to get
system to boot.

If needed, invoke the conversational bootstrap procedure for you
disk. For example, if the system disk is on the first MASSBUS de
DBOGEN; if the first UDA device, DUOGEN; and so forth.
When the boot is complete, the following message appears:
VAX/VMS Version 4.4 <date hh:mm>

6.2.5

Upgrade Phase 5

Phase 5 of the upgrade procedure creates a new site-specific SY
parameter file, AUTOGEN.PAR, that combines the default value
4.4 with the site-specific values you were using for the Version
system.

The command procedure cleans up several directories, announce
upgrade to Version 4.4 is complete, and makes several suggestion

After the upgrade finishes, there are several files things that you m
to do:

- DECOMPRESS THE SYSTEM LIBRARIES - For space considerations, many of
libraries are shipped in a data compressed format.
If you have enough
space, you may decompress them for faster access. Use SYS$UPDATE:LIBDE
to data expand the libraries.
If you choose not to decompress these
there will be a negative impact on the performance of the HELP and LIN
commands.

- EDIT SYSTEM SPECIFIC FILES - The system specific files in SYS$MANAG
SYSTARTUP.COM, SYSHUTDOWN.COM, and SYCONFIG.COM have all been
superceded by blank files.
Your copies of these files still exist i
SYS$MANAGER as the next lower version number.

If you chose earlier in the upgrade procedure to create a commo
disk, you will then receive the following message:

- SYSTEM SPECIFIC DIRECTORIES - The upgrade has produced a new common
disk.
If there exist system roots other than the one that has just b
upgraded, it will be necessary to update the information contained in
other system specific roots.
For example, you may want to run AUTOGEN
reconfigure your network database files. If you wish to recreate the
system roots from scratch, use the SYS$MANAGER:MAKER00T.COM procedure
remove and recreate the specified system roots.
Then run AUTOGEN and
reconfigure your network.

The command procedure then continues with the following suggestions:
- Purge unnecessary files - There are a number of files that may be purged
after the upgrade is complete to free up space on your system disk.
First,
you may purge the lower-numbered versions of the following files from the
previous version of the operation system:
[SYSEXE]SHUTDOWN.COM
[SYSEXE]STARTUP.COM
[SYSHLP]HELPLIB.HLB
[SYSLIB]DCLTABLES.EXE
[SYSLIB]ENCRYPSHR.EXE
[SYSLIB]IMAGELIB.OLB
[SYSLIB]LBRSHR.EXE
[SYSLIB]*RTL*.EXE
[SYSLIB]STARLET.OLB
[SYSMGR]RTTLOAD.COM
[SYSMGR]STARTNET.COM
[SYSMGR]EDTINI.EDT
[SYSMGR]WELCOME.TXT
Second, you may purge the lower-numbered versions of the following
files from the new version of the operating system.
These files may be
purged since they are the same as those shipped in the the last version of
the operating system.
[SYSLIB]CDDSHR.EXE
- Delete SYS$SYSTEM:STARTUP.UP5 and UPGRADE.KIT - These files are left
by the upgrade should this phase fail for some reason.
You may delete
them when the upgrade has completed.

Then the system shuts down and automatically reboots.
Note
If you are upgrading a VAX 8200 or a VAX-11/750 and are booting
from the console volume, you will have to reboot manually by
entering the letter B when you get the BOOT58> prompt.
If your system is part of a VAXcluster, you will have to execute AUTOGEN
with this command after the upgrade finishes:
$ <8SYS$UPDATE: AUTOGEN SAVPARAMS REBOOT

Note
If your system includes a CI780 or CI750, VAX/VMS waits
for several minutes to form or join a cluster. If the upgrade
procedure does not continue within 5 minutes, please submit a
Software Performance Report.
If you have upgraded a tailored system and want to decompress the system
libraries, mount the LIBRARY disk and execute this command sequence. In
place of ddcu, enter the name of the drive holding the LIBRARY disk.
$ ®SYS$UPDATE VMSTAILOR MOUNT ddcu:
$ <8SYS$UPDATE: LIBDECOMP

6-18

The decompressed libraries require approximately 5000 additional
of disk space and the decompression process may take up to 2 h
depending on the type of processor you are using. A general gui
for decompressing individual library files is that HELP libraries in
50% and OBJECT libraries by 25% when decompressed.

6.3

Special File Handling During Upgrade

After you have completed the upgrade, you may wish to remove
no longer need. To do so, you need to know that certain files are
specially during the upgrade. These include files that may have b
by users, and shareable images that may have been linked into us

New versions of the following files are copied from the upgrade p
You may wish to reconcile all modifications between the old and
versions.
[SYSLIB]*RLT*.EXE
[SYSLIB]CDDSHR.EXE
[SYSLIB]DCLTABLES.EXE
[SYSLIB]LBRSHR.EXE
[SYSLIB]SCRSHR.EXE
[SYSLIB]SMGSHR.EXE
[SYSLIB]SUMSHR.EXE
[SYSMGR]RTLLOAD.COM
[SYSMGR]SYSTARTUP.COM
[SYSMGR]SYC0NFIG.COM
[SYSMGR]SYSHUTDWN.COM
[SYSMGR]STARTNET.COM
[SYSEXE]STARTUP.COM
[SYSEXE]SHUTDOWN.COM
[SYSHLP]HELPLIB.HLB
[SYSLIB]ENCRYPSHR.EXE
[SYSLIB]IMAGELIB.0LB
[SYSLIB]STARLET.0LB

The upgrade procedure does not copy older versions of the follow
the system disk:
[SYSEXE]N0TICE.TXT
[SYSEXE]RIGHTSLIST.DAT
[SYSEXE]SYSUAF.DAT

The upgrade does not delete the following files, but you should d
after the upgrade has completed:
[SYSEXE]STARTUP.UP5
[SYSEXE]UPGRADE.KIT

Upgrading To Version 4.4

The upgrade procedure may have changed the size of the following files to
better fit the system. You may want to check that the sizes of these files are
appropriate for your application.
[SYSEXE]SYSDUMP.DMP
[SYSEXE]PAGEFILE.SYS
[SYSEXE]SWAPFILE.SYS

6.4

Installed Images
As part of the upgrade, the file SYS$MANAGER:VMSIMAGES.DAT is
created for your site. This is a combined list of files that are installed
for enhanced system performance. Some files in this list may already be
installed by the SYS$MANAGER:SYSTARTUP.COM file and should be
removed.

6.5

Creating Alternate Roots on a Common System Disk
In a VAXcluster that features a common system disk, the MAKEROOT.COM
command procedure is used to create system roots for nodes other than
the first node of the cluster. Type the following command to invoke
MAKEROOT.COM:
$ <DSYS$MANAGER: MAKEROOT

Note that MAKEROOT will abort if your system disk is not a cluster-common
system disk, or if the SYSGEN parameter VAXCLUSTER is 0.
When MAKEROOT executes, it requests the name of the new system root.
Enter the root name using the form SYSx, where x is a hexadecimal digit in
the range 1 through 9 and A through D (for example, SYS1 or SYSA). Note
that system roots SYSE and SYSF are reserved for other system functions.
You may not specify the root of the currently running system (usually SYSO)
and if you specify any other existing system root, you are asked if you wish
to continue, that is, if you want to modify the existing system root. If you
want to modify the existing system root, MAKEROOT deletes the following
files from it:
•

[SYSEXEJMODPARAMS.DAT

•

[SYSEXE]VAXVMSSYS.PAR

•

[SYSMGRJVMSIMAGES.DAT

If a SYSCOMMON directory exists in the directory tree, it will be deleted.

6—20

Note that MAKEROOT does not check the format of the existing
DIGITAL recommends you delete all the files in the directory tre
directory tree itself, or choose a different root.

Next, MAKEROOT asks for the new node name and its SCSSYS
The SYSSYSTEMID is 1024 times the DECnet-VAX area number
system's DECnet-VAX node number in decimal.

For example, if your DECnet-VAX area number is 5, and your DE
node number is 122, the value for SCSSYSTEMID is calculated a
(5 * 1024) + 122

and is equal to 5242.

The node name can be no more than six alphanumeric characters

After you provide the new node name and the node's SCSSYSTE
MAKEROOT prompts for the size of the new root's paging and s
files. The values you provide are subsequently used by AUTOGE

Finally, MAKEROOT creates the new directory tree and the pagi
swapping files. It also generates a VAXVMSSYS.PAR file for the
using the SYSGEN parameters of the currently running node as t
the new node.

When MAKEROOT completes this, it displays the following mess
Now you must build console media for the new system.
can be done in the following manner:

This

Copy all the files from the console to the disk, using
the following commands:
$ <SSYS$UPDATE: C0NSC0PY
$ DISMOUNT CSA1:

SAVE

CSA1:

Next, remove your console media, insert a scratch console media,
and enter the following commands:
$ <BSYS$UPDATE: C0NSC0PY
""
RESTORE
$ EXCHANGE COPY CSA1:DEFB00.CMD *.*

CSA1:

Edit DEFB00.CMD, and adjust the value deposited in R5 to contain
the root name in the high 4 bits.
For example, if you are building
the console for root SYS5, set the value deposited in R5 to 50000000
(50004000 on a VAX-11/782).
After you edit DEFB00.CMD, copy it to smother disk file.GENB00.CMD,
for instance, edit GENB00.CMD to include the low bit set in R5.
For example, if R5 was set to 50000000 in DEFB00.CMD,
set it to 50000001 in GENB00.CMD.
This will boot VAX/VMS
out of root 5, stopping in SYSBOOT.
$ EXCHANGE COPY DEFB00.CMD.GENB00.CMD CSA1:
$ DISMOUNT CSA1:
Remove the new console,
media in the drive.

and replace the original console

Insert the newly-created console media in the console drive
on the new node.
You must now boot the target node into the newly-created root.
Use the conversational bootstrap GENB00.CMD, which you just
created, as you must change the startup command procedure.
»> ©GENB00.CMD
When SYSBOOT prompts,

enter the following commands:

SYSB00T> SET /STARTUP SYS$SYSTEM:STARTUP.COM
SYSB00T> SET STARTUP.Pl "MIN"
SYSB00T> CONTINUE

Following the system boot, log in to the system manager's account SYSTEM
and invoke AUTOGEN with this command:
$ ®SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT

See the VAX/VMS Release Notes, Version 4.4, for instructions on upgrading
the DECnet permanent database.
When the system comes up, be sure to install the mandatory update
described at the start of this chapter.

6-22

Running the UETP

The User Environment Test Package (UETP) is a VAX/VMS software package
designed to test whether the operating system itself is installed correctly. The
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.
The UETP is not a diagnostic program; it does not attempt to test every
feature exhaustively. When the UETP runs to completion without
encountering nonrecoverable errors, the system being tested is ready for
use.
The UETP exercises devices and functions that are common to all VAX/VMS
systems, with the exception of optional features such as high-level language
compilers. The system components tested include the following:
•

Most standard peripheral devices

•

The system's multiuser capability

•

DECnet-VAX

•

Clusterwide file access and locks

The first time you run the UETP, you should run the entire package as
described in Section 7.1, which contains a summary of operating instructions.
If you need more detailed instructions. Section 7.2 of this guide describes
how to prepare the UETP for testing; Section 7.3 gives complete instructions
for running the entire UETP, as well as for running each phase individually.
If your UETP run results in a failure that you are unable to interpret, refer
to Section 7.5 for an explanation of UETP output, error handling, and
troubleshooting.

7-1

Running the UETP

7.1

Summary of Operating Instructions
This section summarizes the procedures for running the entire UETP. You
should follow these instructions when you run the test package for the
first time. If you need further information, refer to Section 7.2 for detailed
instructions on setup, or Section 7.3 for detailed instructions on running the
UETP.
Note that the system must be bootstrapped before you can run the UETP.
Complete bootstrap instructions are included in the VAX/VMS System

Manager's Reference Manual.
Do not run the UETP with other user programs or while user volumes are
mounted. By design, the UETP assumes and requests the exclusive use
of system resources. Unpredictable results could occur if you ignore this
restriction. For example, because the UETP uses large amounts of many
system resources such as memory pool space and disk space, it may interfere
with applications that depend on these resources.

Logging In
Log in under the SYSTEST account as follows:
Username:

SYSTEST

Password:

UETP

Note
The password on your system should have been changed by
your system manager; if it has not, you should change it with
the DCL command SET PASSWORD. Unauthorized use of this
privileged account may compromise the security and privacy of
your installation.
Preparing Devices
After you log in, check all devices to be sure that the following conditions
exist:
•

All devices to be tested are powered up and on line to the system.

•

Scratch disks are mounted and initialized.

•

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

•

Magnetic tape reels are mounted on each drive to be tested and are
initialized with the label UETP.

•

Magnetic tape reels contain at least 600 feet of tape.

7-2

Running the UETP

•

Line printers and hardcopy terminals are well supplied with 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.2.)
If you do not understand the instructions above or if you encounter any
problems in preparing to run the UETP, read Section 7.2 before proceeding.

Invoking the UETP
Enter the following DCL command:
$ ©UETP

The UETP responds with the following prompt:
Run "ALL" UETP phases or a "SUBSET"

[ALL]?

I RET 1

Press RETURN (that is, choose the default response enclosed in brackets).
The UETP will respond with three more questions in the following sequence:
How many passes of UETP do you wish to run
How many simulated user loads do you want
Do you want Long or Short report format

[1] ?
[n]?

[Long]?

[RET~|
|RET|
1 RET|

Press RETURN after each prompt; when you have answered the last
question, the UETP initiates its entire sequence of tests, which run to
completion without further input from you. If the run completes successfully,
your VAX/VMS system is in proper working order.

Note
After a run of the UETP, you should always run the Error Log
Utility to check for hardware problems that occur during a run of
the UETP. For information on running the Error Log Utility, refer
to the VAX/VMS Error Log Utility Reference Manual.
If you want to run the UETP without using the default responses, refer to
Section 7.3, which explains the options.
If the UETP does not complete successfully (that is, without fatal errors),
refer to Section 7.5 for troubleshooting information.

7.2

Setting Up the UETP
This section presents the detailed instructions for setting up the UETP and
includes sections that discuss preparing the system and devices. Although
you should usually run the entire UETP, you can select and run a subset of
the phases by using the instructions described in this section.

7-3

Running the UETP

7.2.1

Logging In
You should log in at the console terminal connected to the system. Running
the UETP from a terminal other than the system console will mark the
terminal available for testing during the initialization phase, although the
device test phase will find the terminal to be unavailable.
All UETP files reside in SYS$TEST on the system disk as described in
Section 7.2.1.1, unless you are running the UETP on a tailored system. The
UETP files on a tailored system reside in LIB$SYSROOT:[SYSTEST] (see
Section 7.2.4).
To access the UETP files, you must log in under the user name SYSTEST; if
you do not, the UETP will fail. The password to this account in the system
as it is distributed is UETP. Because the SYSTEST account has powerful
privileges, you should change the password after the VAX/VMS system
has been installed at your site, using the DCL command SET PASSWORD.
Unauthorized use of this privileged account may compromise the security
and privacy of your installation.

7.2.1.1

[SYSTEST] Directories
The UETP uses directories named [SYSTEST] for two purposes:
•

To hold all the files used by the UETP command procedure (UETP.COM)

•

To hold temporary files used by the UETP during testing

The following explanation is intended to eliminate confusion over references
to directories named [SYSTEST] and to the logical name SYS$TEST.
All the files used by the UETP command procedure reside in a single
directory on the system disk (the disk from which the system was
bootstrapped). This directory is a rooted directory and is assigned the
logical name SYS$TEST. The DCL command SHOW LOGICAL shows the
translation of the logical name SYS$TEST on a typical system:
$ SHOW LOGICAL SYS$TEST
"SYS$TEST" = "SYS$SYSROOT:[SYSTEST]"

(LNM$SYSTEM_TABLE)

If you want the UETP to test a particular disk, such as a scratch disk, you
must create either a [SYSTEST] directory or a [SYSO.SYSTEST] directory on
that disk. See Section 7.2.2.2 for additional information on setting up scratch
disks for testing.

7-4

Running the UETP

7.2.2

Preparing Devices
After logging in, you must set up all the devices to be tested. The following
sections provide detailed instructions for preparing devices.

7.2.2.1

Setting Up the System Disk
Make sure that the system disk has at least 1200 blocks available when the
UETP starts. Note that large systems, such as systems that run more than
20 load test processes, may require a minimum of 2000 available blocks.
Running multiple passes of the UETP will cause log files to accumulate in
the default directory and further reduce the amount of disk space available
for subsequent passes.
If you have disk quotas enabled on the system disk, you should disable them
before you run the UETP.

7.2.2.2

Setting Up Additional Disk Drives
The disk test uses most of the available free space on each testable disk. The
UETP estimates the space to be used by UETDISK00 for normal testing as
follows:
1

For each testable disk, the test tries to create two files. The goal is to
have the combined space of the two files eventually reach 75% of the
total space on the disk. Typically, the files are created with 5% each of
the total space on the disk and are then extended in increments of 5%.
If the disk is nearly full to begin with, the initial allocation and the steps
are reduced to 1% of the total space. If that fails, the test aborts.

The files are written and read asynchronously. After every multiple of 20
writes for each file, the test tries to extend the file by 5% of the total disk
space (or by 1% if the file was created with 1%). If the attempt to extend
the file fails, the test proceeds with the existing allocation. By creating
two files and extending two files, the UETP tends to create fragmented
files and situations that exercise the disk. Extending the files this way
allows the test to check for exceeded quotas or a full disk and to adapt to
the local situation. Only the initial file creation can cause the test to fail
for lack of space.

To prepare each disk drive in the system for UETP testing, perform the
following steps:
1

Physically mount a scratch disk and start up the drive. If a scratch
disk is not available, any disk with a substantial amount of free space
will suffice; the UETP does not overwrite existing files on any volume.

7-5

Running the UETP

If your scratch disk contains files that you want to preserve, do not
initialize the disk; skip to Step 3.

If the disk has not been initialized, use the DCL command INITIALIZE
to do so, as follows:
$ INITIALIZE DMAO: TEST1

This command initializes a disk on an RK06 or RK07 drive (DMAO) and
assigns the volume label TEST1 to the disk. Codes for the various device
types are listed in Chapter 4. All volumes must have unique labels.

Issue the DCL command MOUNT/SYSTEM to connect the disk to the
file system as follows:
$ MOUNT/SYSTEM DMAO: TEST1

This command mounts the volume labeled TEST1 on the drive DMAO.
The /SYSTEM qualifier indicates that you are making the volume
available to all users on the system.

The UETP uses the [SYSTEST] directory when testing the disk. If
the volume does not contain the directory [SYSTEST], issue the DCL
command CREATE/DIRECTORY to create it.
$ CREATE/DIRECTORY/OWNER_UIC=[1,7] DMAO:[SYSTEST]

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

7.2.2.3

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

Mount a scratch volume with at least 600 feet of magnetic tape, making
sure that the write-enable ring is in place; then switch on the device
power.

Position the magnetic tape at the beginning-of-tape mark (BOT) and
make sure the drive is on line.

Once you are logged in to the SYSTEST account, you must initialize
each device on which you have mounted a scratch magnetic tape. For
example, assume you have mounted a scratch magnetic tape on device
MTA1. Initialize the device as follows:
$ INITIALIZE MTA1: UETP

7-6

Running the UETP

Only the magnetic tapes labeled UETP are written during the test run.
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 DCL
command INITIALIZE in the VAX/VMS DCL Dictionary.

7.2.2.4 Setting Up Terminals and Line Printers
To be tested by the UETP, terminals and line printers must be powered up
and on line. If the device is a line printer, press the ONLINE switch. Check
that line printers and hardcopy terminals are properly loaded with paper.
The amount of paper required depends on the number of UETP passes that
you intend 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 will fail the initialization
phase of the UETP and therefore will not be tested.
Note that if you run the UETP from a terminal other than the system console,
the device test phase will display a message that the terminal is unavailable
for testing.

7.2.2.5 Preparing the DEUNA for UETP Testing
Make sure that no other processes are sharing the DEUNA during a run of
the UETP. The UETP procedure automatically shuts down DECnet and the
LAT-11 server for the duration of the device tests, and restarts them when
the device tests are completed. However, you must shut down any local
applications.

7.2.2.6 Preparing the DR11-W for UETP Testing
The DR11-W uses an internal logical loopback mode that tests all
functionality except that of module connectors, cables, and transceivers.
Since random external patterns are generated during this operation, the user
device or other processor may need to be isolated from the DR11-W being
tested until the testing is complete.

Note
Only DIGITAL field service personnel should set up the DR11-W
for UETP testing.

7-7

Running the UETP

To properly test the DR11-W, the E105 switchpack must be set as follows:
Switch 1

Switch 2

Switch 3

Switch 4

Switch 5

Off

When UETP testing is completed, a field service representative will restore
the DR11-W to the proper configuration for operations.

7.2.2.7

Preparing the DR750 or the DR780 for UETP Testing
The following steps are necessary to prepare the DR750 or the DR780 for
UETP testing:

Note
Only DIGITAL Field Service personnel should set up the DR750
or DR780 for UETP testing.
1

Copy the Version 1 DR780 microcode file, XF780.ULD, from the
diagnostic medium (QE005-AY) to SYS$SYSTEM:, using the procedure
described in the Installation Procedures (AA-J949A-TE) provided with
the DR780 Microcode Kit.

Turn off the DR780 power.

Make the following DR780 backplane jumper changes:
•

Remove the jumper from W7 and W8.

•

Add a jumper from E04M1 to E04R1.

•

Add a jumper from E04M2 to E04R2.

Disconnect the DDI cable from the DR780. This cable is either a BC06Vnn 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, a field service representative will restore
the DR750 or the DR780 to the proper configuration for operations.

7-8

Running the UETP

7.2.2.8 Preparing the MA780 for UETP Testing
Make sure that the MA780 is set up according to the guidelines for shared
memory in the VAX/VMS System Manager's Reference Manual.
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.2.2.9 Preparing a Second LPA11-K for UETP Testing
If you have two LPAll-Ks, be sure that each is given the system-wide
logical name in the SYS$MANAGER:LPA11STRT.COM file. The logical
name for the second LPA11 should be LPA11$1.

7.2.2.10 Devices Not Tested
The 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)

The UETP does not explicitly test UDA, HSC, or Cl devices; they are tested
implicitly by the disk, magnetic tape, and DECnet tests.
The UETP does not test the console terminal or the console block storage
device. If you are able to bootstrap the system, log in, and start the UETP,
you have shown that these devices are usable.

7.2.3

Preparing for VAXcluster Testing
The UETP requires little additional preparation for the cluster-integration
test phase, beyond the requirements for other UETP test phases and regular
system management. The requirements for cluster integration testing are as
follows:
1

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

Your system must be consistent with other systems in the VAXcluster.
The cluster-integration test lists each VAX/VMS system to be included
in the lock tests along with the version of VAX/VMS that it is running.
It checks to see that those systems use the same deadlock detection
interval, and it takes advantage of the fact that a VAXcluster is a single
entity for security purposes.

7-9

Running the UETP

7.2.4

The SYSTEST_CLIG account must be present in the user authorization
file, exactly as distributed by DIGITAL on each system in your
VAXcluster. The SYSTEST_CLIG account parallels SYSTEST except
that it is dedicated to the sole purpose of running the cluster-integration
test.

All parts of the cluster-integration phase must reside in SYS$TEST on
each system. The files UETCLIGOO.COM and UETCLIG00.EXE are
necessary for each system to be included in the test.

DECnet must be set up between the VAXcluster nodes; the UETP uses
DECnet to create a process on those nodes. Virtually all checks that the
test makes are dependent on the abilities 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 VAX/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 VAX/VMS node
in the cluster can share access to that file. The requirement is only that
there be one such directory per node; the test continues with the next
cluster node once it has finished with a file.

Preparing a Small-Disk System
If you are running the UETP on a small-disk system, such as a VAX-11/730,
you should be aware of the disk space limitations. Because of the space
limitations, you need to perform special procedures to prepare for a UETP
run. You can run the UETP in either of two ways on a small-disk system:
•

From the library disk (LIB$SYSROOT)

•

From the system disk, after copying the appropriate files

The following two sections describe the methods of preparing a small-disk
system for UETP testing.

7-10

Running the UETP

7.2.4.1

Running the UETP from the Library Disk
Running the UETP from the library disk is the easier of the two methods and
leaves more space on your system disk; however, it allows the UETP to write
to your library disk. If you plan to run the UETP from LIB$SYSROOT, use
the following procedure:
1

Place the library disk in drive DQA1.

Invoke the tailoring procedure and mount the library disk as writeable
with the following command:

Start the UETP with the following command:

$ ®SYS$UPDATE:VMSTAILOR MOUNT/WRITE DQA1:

$ ®LIB$TEST:UETP

7.2.4.2

Running the UETP from the System Disk
As an alternative, you can run the UETP from the system disk. This method
of running the UETP allows you to reserve your library disk as read-only,
but it is more complicated and uses more space on your system disk. (See
Section 7.2.2.1 for a discussion of system disk space.)
If you plan to run the UETP from your system disk, you must first mount
the library disk with the tailoring command MOUNT, then copy the UETP
file group to your system disk. If you want to remove the library disk during
a run of the UETP, you must tailor additional files to the system disk before
you invoke the UETP.
1

Place the library disk in drive DQA1.

Invoke the tailoring procedure with the following command:
$ ®SYS$UPDATE:VMSTAILOR

Enter the following sequence of tailoring commands:
Tailor> MOUNT DQA1:
Tailor> COPY UETP

If you want to remove the library disk during the UETP run, enter the
additional tailoring commands:

7-11

Running the UETP

Tailor>
Tailor>
Tailor>
Tailor>
Tailor>
Tailor>
Tailor>

COPY /FILE CONVERT
COPY /FILE [SYSLIB]CONVSHR
COPY /FILE CDU
COPY /FILE DIFF
COPY /FILE SEARCH
COPY /FILE [SYSHLP]HELPLIB.HLB
EXIT

End tailoring with the EXIT command:
Tailor> EXIT

After you have completed these preparations, run the UETP according to the
instructions in Section 7.3.

7.3

Interacting with the UETP
Each time you invoke the UETP, you specify the following variables, either
explicitly or implicitly:
•

What part of the UETP to run (or whether to run the entire UETP)

•

The number of consecutive passes to be made by the UETP

•

The number of users to be simulated by the UETP in the system load
test

•

The amount of information to be output to the console

These variables are defined by your answers to the questions that the UETP
asks in the startup dialog. The following section describes the startup dialog.

7.3.1

Startup Dialog
When you initiate the UETP, it responds with 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. If you choose ALL, the UETP responds
with three more questions, as described in Sections 7.3.1.1 through 7.3.1.3.
If you want to choose a subset, however, refer to Section 7.3.1.4.

7-12

Running the UETP

7.3.1.1

Single Run Versus Multiple Passes
When you choose the default ALL, the UETP prompts you as follows:
How many passes of UETP do you wish to run [1]?

You can repeat the test run as many times as you wish, without further input.
If you enter 1 in response to the prompt (or press RETURN for the default),
the UETP stops after completing a single run. If you specify a number
greater than 1, the UETP restarts itself continuously until it completes the
number of passes (runs) specified.
The UETP can be run once to check that the system is working, or it can be
repeated 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 the UETP once or twice, whereas
a manufacturing technician might let the system run all night as part of the
system integration and test.
When you specify multiple UETP runs, you may wish to request a short
console log (see Section 7.3.1.3.) Make certain that all line printers and
hardcopy terminals have enough paper; each run requires two pages.

7.3.1.2

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

Your response to this prompt provides information necessary to run the
load test. The maximum number of users that you should enter will
depend upon the amount of memory and the swapping and paging space in
your VAX/VMS system. The UETP takes these factors into account when
computing the default value for the number of users.
If you want to see the equation the UETP uses to compute the default value,
define the logical name MODE and run the UETINITOO program as follows:

7-13

Running the UETP

$ DEFINE MODE DUMP
$ RUN UETINITOO
Welcome to VAX/VMS UETP Version V4.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 _DRA0:[SYSO.].
Run "ALL" UETP phases or a "SUBSET" [ALL]? I RET|
How many passes of UETP do you wish to run [1]? I RET|
The default number of loads is the minimum result of
1) CPU.SCALE * ((MEMJFREE + MEM.MODIFY) / (WS.SIZE * PER.WS.INUSE))
0.80 * ((
8704 +
323) / (
350 *
0.20))

= 8704

2) Free process slots

= 56

3) Free page file pages / Typical use of page file pages per process
18040 /
1000 = 18
How many simulated user loads do you want [18]?
Do you want Long or Short report format [Long]?
UETP starting at 2-0CT-1985 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 serves only to display the
equation used by the UETP to determine user load, and the specific factors
that are employed in the current run.
You should respond to the dialog questions by pressing RETURN. After
you respond to the first prompt, the program displays the expressions that
determine the default number of simultaneous processes. The following
definitions apply:
•

CPU—SCALE refers to the relative processing power of the CPU. CPU_
SCALE is determined as follows:
VAX-11/730 = 0.5
VAX-11/750 = 0.8
VAX-11/780 = 1.0
VAX-11/782 = 1.4
VAX-11/785 = 1.5

•

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, the UETP selects 18 as the default for simulated user loads,
because 18 is the minimum result of the three expressions.

7-14

Running the UETP

You should deassign the logical name MODE before running the UETP,
unless you prefer to see the above breakdown each time you run the UETP.
The purpose of the load test is to simulate a situation in which a number
of detached processes (users) are competing for system resources. Each
detached process executes a command procedure, thereby simulating a user
entering commands from a terminal. When the command procedure is
finished, the detached process logs out. You can monitor the number of
currently active processes at the console, where both the beginning and the
end of each process are displayed.
The load count is also used to limit the number of simultaneous tests during
the device and DECnet test phases. 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. Be aware, however, that an increase might overload
the system and cause failure through insufficient resources.

7.3.1.3

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), the UETP sends to the
console all error messages as well as information on the beginning and end
of all phases and tests. The UETP records all of its output in the UETP.LOG
file, (see Section 7.5.3), regardless of your response to this question.
In many cases, it may not be convenient to have the UETP write the bulk
of its output to the terminal. For example, if you run the 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, but you may prefer to use the short format if you intend to run multiple
passes of the UETP from a hardcopy terminal.
If you request the short format, the 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 the UETP
is proceeding normally. If the short console log indicates a problem, you can
examine UETP.LOG for further information. This disk file contains all of the
output generated by the various phases, as well as the status information
displayed at the console.

7-15

Running the UETP

7.3.1.4

Running a Subset or Individual Phase
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]?

The UETP prompts you for the desired phase as follows:
You can choose one or more of the following phases:
DEVICE, LOAD, DECNET, CLUSTER
Phases(s):

There is no default; enter one or more phase names from the list. If you
choose two or more phases, separate them with spaces or commas.
If your choice is LOAD, the UETP responds with three prompts, as in
running the entire UETP. To run the LOAD phase, refer to Sections 7.3.1.1
through 7.3.1.3 and proceed as if you were running the entire test package.
If you choose a phase other than LOAD, the UETP responds with two
prompts:
How many passes of UETP do you wish to run [1]?
Do you want Long or Short report format [Long]?

These questions are discussed in Sections 7.3.1.1 and 7.3.1.3 respectively.
After you answer both questions, the phase you have selected runs to
completion.

7.4

Using CTRL/Y and CTRL/C
The control characters CTRL/Y and CTRL/C allow you to 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 the UETP for the purpose of testing. These cleanup procedures may be
interrupted or prevented by the use of CTRL/Y or CTRL/C.
The effect of these control characters depends on what part of the UETP you
are executing. For an explanation of the organization of the UETP and its
components, refer to Section 7.6.

7-16

Running the UETP

7.4.1

Using CTRL/Y
You can abort a run of the UETP command procedure by pressing CTRL/Y.
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 (as described in Section 7.6.2.2,
CTRL/Y interrupts the current UETP test and temporarily returns control
to the command interpreter. While the test is interrupted, you can issue
a subset of DCL commands that are performed within the command
interpreter and thus do not cause the current image to exit. The VAX/VMS
DCL Dictionary contains a table of commands that can be used within the
command interpreter. In addition, you can issue any of the following:
•

CONTINUE to continue the test from the point of interruption (except
during execution of the cluster test).

•

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

•

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

•

Any DCL command other than the subset mentioned above; the test
performs cleanup procedures and terminates, and the DCL command
executes.

Note
Use of the STOP command may prevent cleanup procedures that
normally are executed. You should use the EXIT command if
you want the image to perform its cleanup procedures before
terminating.

7.4.2

Using CTRL/C
You can interrupt the command procedure by pressing CTRL/C, but you
cannot continue a phase after you press CTRL/C. The 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. The tests that have enabled CTRL/C in this
way display the following message as they start to run:
V.UETP-I-ABORTC,

'testname' to abort this test, type ~C

The phases that do not display the above message will terminate all
processes they have started, but the processes may not have a chance to
perform normal cleanup procedures.

7-17

Running the UETP

If you are running an individual test image, however, you can use CTRL/C
to terminate the execution of the image and perform cleanup procedures.
Note that CTRL/C does not perform cleanup procedures for the cluster test.

7.5

T roubleshooting
This section explains the role of the UETP in interpreting operational errors
in a VAX/VMS system. Section 7.5.4 discusses the most typical problems
that can appear in a UETP run and describes how to identify them.

7.5.1

Relationship of the UETP to Error Logging and Diagnostics
When the UETP encounters an error, it reacts as a typical user program
would react. It either returns an error message and continues, or it reports a
fatal error and terminates the image or phase. In either case, the UETP does
not attempt to discover the cause of the error.
The UETP assumes that the VAX/VMS hardware is correctly installed and
operating as verified by a previous diagnostic run. If the UETP reports an
error that you cannot diagnose, you can turn to the VAX/VMS error logging
and diagnostic facilities. The system continuously maintains data on various
kinds of errors. By running the Error Log Utility, you can obtain a detailed
report of hardware and system errors that have occurred. Error log reports
provide information about the state of the hardware device and I/O request
at the time each error occurred. The diagnostic facilities can exhaustively
examine a device or medium to isolate the sources of any errors.
For information about running the Error Log Utility, refer to the VAX/VMS

Error Log Utility Reference Manual.

7.5.2

Interpreting UETP Output
You can monitor the progress of the UETP tests at the terminal from which
they were invoked. The 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 (which can include the issuing terminal) depending on how you
invoked the tests. The log files contain output generated by the actual
test procedures. Even if the UETP completes successfully, with no errors
visibly 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.

7-18

Running the UETP

The error messages that appear at the terminal and within the log files have
two basic sources:
•

The UETP tests themselves

•

The system components that are tested

To interpret the messages, you may need to refer either to the VAX/VMS
System Messages and Recovery Procedures Reference Manual or to the manual
that describes the individual system component.
Several parts of the UETP, such as some device tests, UETINIT00.EXE,
UETCLIG00.EXE, and UETDNETOO.COM, allow you to obtain additional
information concerning the progress of the test run or the problems
it encounters. Because this information is usually insignificant, it is
suppressed; however, if the tests can translate the logical name MODE to the
equivalence string DUMP, they issue their messages with this information.
Section 7.3.1.2 gives an example of this output for UETINIT00.EXE.

7.5.3

The Log Files
At the end of a run of the UETP, 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
the UETP.LOG for each pass.
Each time you run the test package, either in its entirety or by individual
phase, in either single or multiple passes, the log file(s) named UETP.LOG
will contain information from the latest run only. Each version of the
UETP.LOG file from the previous run is renamed OLDUETP.LOG; the file(s)
named OLDUETP.LOG will contain information from only one previous run.
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 will contain the result of the test run on that node. The UETP
does 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 may contain other
log files. Ordinarily, These log files are concatenated and placed within
UETP.LOG. If, however, they appear on the system disk, they may be used
for error checking, but they must be deleted before you run any new tests.
You may delete the other log files yourself or rerun the entire UETP, which
checks for old UETP.LOG files and deletes them.

7-19

Running the UETP

7.5.4

Possible UETP Errors
This section is designed to help you identify and solve problems that you
may encounter during a run of the UETP. You should refer to this section
if you need help in understanding a system failure and isolating its cause.
This section is not intended as a repair manual and cannot be expected to
diagnose any flaws in your system. It should, however, help you to interpret
error messages and determine what action to take when you encounter them.
If you are unable to correct an error after following the steps in this
guide, you should contact your DIGITAL Field Service representative. Any
information that you can supply in this event regarding the measures you
have taken to isolate the problem will help to diagnose the failure quickly.
The typical failures listed below appear in an order that roughly reflects the
frequency with which they might occur in running the UETP:
1

Wrong quotas, privileges, or account

UETINIT01 failure

Insufficient disk space

Incorrect VAXcluster setup

Problems during the load test

DECnet error

Errors logged but not displayed

No PCB or swap slots

Hangs

10 Bugchecks and machine checks
The following sections describe how the UETP shows the above errors, and
offer the best course of action for dealing with each problem.

7-20

Running the UETP

7.5.4.1

Wrong Quotas, Privileges, or Account
If your assigned quotas or privileges do not match those that are standard for
the SYSTEST account, UETP issues an error message as follows:

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

UETINITOO
Error count =

*
*

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

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

Solution
In the system distributed by DIGITAL, the SYSTEST account has the
following privileges and quotas assigned to it. If these are altered, the
UETP does not run correctly.

Privileges
CMKRNL

CMEXEC

NETMBX

DETACH

PRMCEB

PRMMBX

DIAGNOSE
PHY_IO

GRPNAM

TMPMBX

VOLPRO

LOG_IO

SYSNAM

SYSPRV

SETPRV

GROUP

Quotas
BIOLM: 18

PRCLM: 8

DIOLM: 55

ASTLM: 55

FILLM: 20

BYTLM: 20480

TQELM: 20

CPU: no limit

ENQLM: 30

PGFLQUOTA: 10000

To check that these privileges and quotas remain assigned, use the DCL
commands SHOW PROCESS/PRIVILEGE and SHOW PROCESS/QUOTA.
The terminal displays all privileges and quotas that are in effect for the
current account:

7-21

$ SHOW PROCESS/PRIVILEGES
2-0CT-1985 18:06:02.89
Process privileges
CMKRNL
CMEXEC
SYSNAM
GRPNAM
DETACH
DIAGNOSE
LOG.IO
GROUP
PRMCEB
PRMMBX
SETPRV
TMPMBX
NETMBX
VOLPRO
PHY.IO
SYSPRV

OPAO:

User :

SYSTEST

may
may
may
may
may
may
may
may
may
may
may
may
may
may
may
may

$ SHOW PROCESS/QUOTAS
2-0CT-1985 18:06:03.36

OPAO:

User :

SYSTEST

Process Quotas:
Account name: SYSTEST
CPU limit :
Buffered I/O byte count quota :
Timer queue entry quota :
Paging file quota :
Default page fault cluster :
Enqueue quota :

Infinite
20480
20
10000
32
20

Direct I/O limit :
Buffered I/O limit:
Open file quota :
Subprocess quota :
AST limit :

55
12
20
8
55

If any privileges or quotas are incorrect, you can run the Authorize Utility
(AUTHORIZE) to add them (AUTHORIZE is explained in the VAX/VMS
Authorize Utility Reference 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, an error message informs you of
the fact and asks you to log in to the SYSTEST account.
$ (DUETP

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

UETINITOO
Error count =

*
*

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

-UETP-E-ABORT, UETINITOO aborted at
2-0CT-1985 14:24:10.13
-UETP-E-TEXT, You are logged in to the wrong account.
Please log in to the SYSTEST account.
$

7-22

Running the UETP

7.5.4.2

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

Device failure

•

Device not supported or not mounted

•

Device allocated to another user

•

Device write-locked

•

Lost vacuum

•

Drive off line

In some cases, the course of action you should take is explicit in the error
message. For example, you may receive a message from the Operator
Communication Facility (OPCOM) process informing you of a problem and
recommending a corrective measure:
'/.OPCOM,
2-0CT-1985 14:10:52.96, request 1, from user SYSTEST
Please mount volume UETP in device _MTA0:
'/.MOUNT -1-OPRQST, Please mount volume UETP in device _MTA0:

Other error messages may relate information in which the solution is implicit:
'/.UETP - S - BEG IN, UETDISK00 beginning at 2-0CT-1985 13:34:46.03

**********************
•
•

DISK.DRA
Error count =

*
*

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

-UETP-E-TEXT, RMS file error in file DRAO:DRA00.TST
-RMS-E-DNR, device not ready or not mounted
'/.UETP - S - ENDED, UETDISK00 ended at 2-0CT-1985 13:34:46.80

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

Inter-module cable unplugged

•

Self-test failure code 0000000

7-23

Running the UETP

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

Solution
To locate the source of the failure, you should try to determine where or
when it occurs in the execution of the software:

7.5.4.3

•

Run the device test individually (see Section 7.6.2.2). One reason for
doing this is to determine whether the failure can be recreated. Also, you
will find it easier to isolate the cause of the problem if you reproduce 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, then you can conclude that a
device-interaction problem is indicated. Conversely, if you can recreate
the error by running the single device test, then you have proven that
the error is not related to device interaction.

•

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

•

Call DIGITAL Field Service. If you have tried all of the above without
solving the problem, you should contact your field service representative.

Insufficient Disk Space
When you run continuous passes of the UETP, log files accumulate on the
disk from which the UETP was run and reduce the amount of free disk
space available for each successive pass. If the available amount of disk
space becomes too small for the current load, an error message indicates
insufficient disk space:

7-24

Running the UETP

•/.UETP-S-BEGIN, UETDISKOO beginning at 2-0CT-1985 08:12:24.34
'/.UETP-I-ABORTC, DISK.DMA to abort this test, type ~C

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

DISK.DMA
Error count =1

**
*

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

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

*
*

DISK.DMA
Error count =2

*
*

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

-UETP-F-TEXT, RMS file error in file DMAO:DMAO1.TST
-RMS-F-FUL, device full (insufficient space for allocation)
7.UETP-E-DESTP, DISK.DMA stopped testing DMA unit 0 at 08:12:36.91
'/.UETP - S - ENDED, UETDISKOO ended at 2-0CT-1985 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:
•

Delete unnecessary files to create more space.

•

Purge files, if multiple versions exist.

•

Mount a volume with sufficient space.

•

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

See Sections 7.2.1.1 and 7.2.2.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 the 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 VAX/VMS nodes are started

•

Toward the end, when cluster file access is checked

The cluster test phase shows that various VAX/VMS nodes in your cluster
can simultaneously access files on each node in the cluster. For each node
in the cluster, the test looks for some disk device that is visible to all nodes
in the cluster and that is set up so that the test can create a file on it. The
requirements for creating a file in the cluster test phase are similar to those of
the UETP disk test (UETDISK00.EXE):

7-25

Running the UETP

•

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.

The cluster test phase need only create a small file. If there is not such a
disk on some cluster node, the test gives a warning and proceeds to the next
cluster node.
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.
An error message may indicate a problem with any of the following during a
run of the cluster test:
•

Logging in at other nodes—This problem is due to incorrect setup for
the cluster test at the remote VAX/VMS node; refer to Section 7.2.3 for
information on preparing for VAXcluster testing.

•

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.
Otherwise, your cluster is not properly configured; you should send an
SPR.

•

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

7-26

7.5.4.5

Problems During the Load Test

A variety of errors can occur during the load test, because the com
procedures that are invoked during the tests run several utilities an
many functions. Tracking a problem can be difficult because the
deletes the log files that are generated during the load test (see Sec

If a problem occurs during the load test and the cause is not obvio
can modify UETP.COM to preserve the log files.
1

Append /NODELETE 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 recreate the proble

If you recreate the problem, examine the contents of the appropria
To determine which log file to read, you need to understand the s
which the load test names its processes and log files. (The log file
derived from the process names.)

The load test creates processes that are named in the following for
UETLO ADnn _nnnn
For example:
'/.UETP - I- BEGIN,
'/.UETP-1-BEGIN,
'/.UETP-1-BEGIN,
'/.UETP -I-BEGIN,
'/.UETP-I-BEGIN,
'/.UETP -I-BEGIN,
'/.UETP-1-BEGIN,
'/.UETP-1-BEGIN,
'/.UETP-1-BEGIN,
'/.UETP-1-BEGIN,
'/.UETP-1-BEGIN,
'/.UETP-1-BEGIN,
'/.UETP -I-BEGIN,
'/.UETP-1-BEGIN,

UETLOADOO beginning at 22 -AUG-1985 15:45:08.97
UETL0ADO2. .0000 beginning at 22-AUG- 1985 15:45:09.42
UETL0ADO3. .0001 beginning
22-AUG- 1985 15:45:09.63
UETLOAD04. .0002 beginning
22-AUG- 1985 15:45:10.76
UETL0ADO5. .0003 beginning
22-AUG- 1985 15:45:11.28
UETLOAD06. .0004 beginning
22-AUG- 1985 15:45:12.56
UETL0AD07. .0005 beginning
22-AUG- 1985 15:45:13.81
UETL0ADO8. .0006 beginning
22-AUG- 1985 15:45:14.94
UETLOAD09. .0007 beginning
22-AUG- 1985 15:45:16.99
UETLOADIO. .0008 beginning
22-AUG- 1985 15:45:19.32
UETL0AD11. .0009 beginning
22-AUG- 1985 15:45:19.94
UETL0AD02. .0010 beginning
22-AUG- 1985 15:45:20.20
UETL0ADO3. .0011 beginning
22-AUG- 1985 15:45:21.94
UETLOAD04. .0012 beginning
22-AUG- 1985 15:45:22.99

Note that if more than ten processes are created, the numbering se
the UETLOADnn portion of the process name starts over at UETL
however, the four digits of the _nnnn portion continue to increase

Each load test process creates two log files. The first log file is cre
the test controller; the second log file is created by the process itse
file that you need to examine for error information on any given l
process is the one that was created by the test controller (the first l

Running the UETP

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 UETLOAD05—
0003 would be named as follows:
UETLO0003.LOG; 1 (test-controller log file)
UETL00003.LOG;2 (process log file)
Make certain that you read the log file with the lower version number, as that
file is the one that 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 that remain from the load test (UETLO*.LOG;*);
failure to delete these files may result in disk space problems.

7.5.4.6

DECnet Error
A DECnet error message may indicate that the network is not available.

Solution
•

If the DECnet license is included in your system, turn it on (see the
installation documentation for DECnet-VAX).

•

If DECnet is not included in your system, ignore the message; this is
normal and the UETP run will not be affected.

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

7.5.4.7

•

Run DECnet as a single phase (see Section 7.3.1.4) to determine whether
the error can be recreated.

•

Refer to the VAX/VMS System Messages and Recovery Procedures Reference
Manual or the installation documentation for DECnet-VAX.

Errors Logged but not Displayed
If no errors are shown 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 VAX/VMS Error Log Utility Reference Manual
for information about running the Error Log Utility.

7—28

7.5.4.8

No PCB or Swap Slots
An error message indicates that no process control block (PCB) or
are available. For example:
'/.UETP-1-BEGIN, UETLOADOO beginning at
2-0CT-1985 07:47:16.50
'/.UETP-I-BEGIN, UETL0ADO2.OOOO beginning at
2-0CT-1985 07:47:16.76
'/.UETP- I- BEGIN, UETLOAD03.0001 beginning at
2-0CT-1985 07:*7:16.92
'/.UETP-1-BEGIN, UETLOAD04.0002 beginning at
2-0CT-1985 07:47:17.13
'/.UETP-1-BEGIN, UETLOAD05.0003 beginning at
2-0CT-1985 07:47:17.35
'/.UETP-1-BEGIN, UETLOAD06.0004 beginning at
2-0CT-1985 07:47:17.61
•/.UETP-W-TEXT, The process -UETLOAD07.0005- was unable to be created,
the error message is
-SYSTEM-F-N0SL0T, 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 -UETL0AD10_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
2-0CT-1985 07:47:54.10
-UETP-W-TEXT, Aborted via a user CTRL/C.
***************************************************
END OF UETP PASS 1 AT 2-0CT-1985 07:48:03.17
*
*
***************************************************

Solution
To solve this problem, do the following:
•

Rerun individually the phase that caused the error message (w
would be the LOAD phase in the above example), to see if the
be reproduced.

•

Increase the size of the page file, using either the command p
SYS$UPDATE:SWAPFILES.COM or the System Generation U
the VAX/VMS System Generation Utility Reference Manual.

•

Increase the SYSGEN parameter MAXPROCESSCNT, if neces
reboot the system.

•

Increase both the page file size and the MAXPROCESSCNT, if

Running the UETP

7.5.4.9

Hangs
If there is no keyboard response and/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 purposes. To learn why the system hung, run the System
Dump Analyzer as described in the VAX/VMS System Dump Analyzer
Reference Manual. Possible reasons 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 VAX/VMS System Generation Utility

•

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

Reference Manual.

7.5.4.10

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

Solution
Call DIGITAL Field Service. This is often a hardware problem and there is
no easy way to solve a bugcheck or machine check. 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 recreated; you can verify this by running the UETP again.

7.6

UETP Tests and Phases
This section explains the organization of the UETP and the individual
components within the test package. Section 7.6.2.2 provides instructions for
testing specific devices.
You run the UETP by invoking a master command procedure, which contains
commands that in turn invoke each test phase. The procedure begins by
prompting you for responses that will provide information needed by the
various test phases. (See Section 7.3 for a detailed description of invoking
the UETP.)

7-30

Running the UETP

The master command procedure, UETP.COM, contains commands that
initiate each test phase in turn and perform such tasks as defining logical
names and manipulating files generated by the tests.
The UETP.COM procedure also issues commands to invoke the phase
controlling program, UETPHASOO.EXE, which in turn controls each test
phase. The phase controller starts up multiple detached processes and
reports their completion status and other information the processes report to
it.
The following sections describe the various UETP test phases.

7.6.1

Initialization Phase
The initialization phase prepares for the actual UETP tests in the following
ways:
•

The image UETINITOO.EXE prompts for input from the terminal (see
Section 7.3). The input defines certain variables that affect the execution
of the UETP tests.

•

The image UETINIT01.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 UETINIDEV.DAT, UETINIT01.EXE verifies
which devices in the system are operable by running the appropriate
device test, which performs 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, UETINIT01.EXE writes a line into a
file called UETCONTOO.DAT. The line associates a test file with the
controller it is to test.

A summary of UETINIDEV.DAT always exists in UETP.LOG, and
UETINIT01.EXE outputs 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 phase and presents instructions for running a single device
test. If you want to run the entire device test phase individually, refer to
Section 7.3.1.4.

7-31

Running the UETP

7.6.2.1

How the Device Phase Works
The UETP device test phase contains 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 the UETP creates a file called UETINIDEV.DAT
and a file called UETCONTOO.DAT. UETINIDEV.DAT contains data on
the VAX/VMS-supported controllers in the system and their associated
devices, while 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 invoke UETP.COM; you
can run only individual test images. UETINIDEV.DAT exists in SYS$TEST
unless you explicitly delete it.

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

The UETP prompts you for the controller designation, which you supply
together with 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.

7-32

Running the UETP

If you plan to repeat the run a number of times, you may find it more
convenient to use the DEFINE command as follows:
$ DEFINE CTRLNAME TTB
$ RUN UETTTYSOO

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

Format of UETINIDEV.DAT
The UETINIDEV.DAT file is an ASCII sequential file that you can type out
or edit if necessary. The contents of this file are as 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

Definition

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

UUUUU

device unit number

UETINIDEV.DAT contains a DDB (device data block) line for each controller
connected or visible to your system. Following the DDB line is a UCB (unit
control block) line for each unit connected to that controller. In addition, if
your system uses MA780 memory in a loosely coupled CPU configuration,
UETINIDEV.DAT includes one UCB line for each MA780 memory. A device
test will test a particular device only if both the DDB line and the UCB line
indicate that the device is testable.

7-33

Running the UETP

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-1-TEXT, End of pass 1 with 980 iterations at 26-0CT-1985 16:18:51:03
~C

You must use CTRL/C to terminate the test run. If you use CTRL/Y, the
UETP will not perform 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$OUTPUT, and deletes the disk files.
When you run the disk test phase in a cluster environment, the test will
access all disks that are mounted by the system being tested, and users of the
disk being tested may encounter an insufficient disk space problem. Unless
you issue a warning to the users on remote nodes who share disks with users
on the local system, they will be unaware that the UETP is testing a disk that
they may be 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 finishes
by reinitializing the magnetic tape.
The terminal and line printer test generates several pages or screens of
output, where 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 (LPA11-K), the test image
determines the configuration on the LPAll-K's I/O bus. The image loads all
types of microcode to the LPA11-K and reads or writes data for each device
on the LPA11-K I/O 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.

7-34

Running the UETP

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; it then verifies that modifications can
be made. You can run MA780 tests in parallel from separate systems so that
the tests interact with each other through common MA780 memories.
The DEUNA test performs self-test diagnostics on the device and then
performs read and write operations with test data that uses various DEUNA
modes (such as internal loopback, external loopback, and broadcast).
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

UETTAPEOO.EXE

Magnetic tapes

UETTTYSOO.EXE

Terminals and line printers

UETLPAKOO.EXE

LPA1 1-K

UETCOMSOO.EXE

DMC1 1, DMR1 1

UETDMPFOO.EXE

DMF32, DMP1 1

UETDR1W00.EXE

DR1 1-W

UETDR7800.EXE

DR780, DR750

UETMA7800.EXE

MA780

UETUNASOO.EXE

DEUNA

System Load Test Phase
The purpose of the system load test is to simulate a number of terminal
users who are simultaneously demanding system resources. 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.

7-35

Running the UETP

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.3.1.2) 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.
Whether the load test runs as part of the entire UETP or as an individual
phase, the UETP excerpts 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.3.1.4).

7.6.4

DECnet Test Phase
If DECnet is included in your VAX/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, the UETP shuts down DECnet for the duration of the
initialization and device test phases (approximately 3 to 5 minutes each). It
then 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.3.1.4.

7-36

Running the UETP

7.6.4.1

Environment
The DECnet test will work successfully on VAX/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 in
order to copy files between systems. The DECnet phase tests the following:
•

The node the UETP is running on

•

All circuits in sequence

•

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

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

7.6.4.2

How the DECnet Phase Works
Controlled by UETPHAS00.EXE, the UETP reads the file UETDNET00.DAT
and performs the following steps to complete the DECnet phase:
1

Executes a set of NCP LOOP EXECUTOR commands to test the node on
which the UETP is running.

Uses NCP to execute the command SHOW ACTIVE CIRCUITS. The
results are placed in UETININET.TMP, from which the 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:
•

The circuit name

•

The node address

•

The node name (if one exists)

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

Uses the UETININET.TMP file to create an NCP command procedure
for each testable circuit; each command procedure contains a set of NCP
commands to zero the circuit and node counters and to test the circuit
and adjacent node by copying files back and forth.
Note
If you do not want the counters zeroed, do not test DECnet.

7-37

Running the UETP

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 2

•

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, UETNETS00.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 2-0CT-1985 13:45:33.18
'/.UETP - S - TEXT, Circuit DMC-0 to ( NODENAME 1) OK.
'/.UETP-I-TEXT, Node
(N0DENAME2) over DMC-1 response timeouts = 1.
'/.UETP-I-TEXT, Circuit DMC-1 to (N0DENAME2) local buffer errors = 34.
'/.UETP-I-TEXT, Node
(N0DENAME3) over DMP-0 response timeouts = 3.
'/.UETP - S - ENDED, UETNETSOO ended at 2-0CT-1985 13:45:36.34

Since degradation is not necessarily an error, only you can determine
the success of the test. The following counters are considered to indicate
possible degradation:

For Circuits
•

Arriving congestion loss

•

Corruption loss

•

Transit congestion loss

•

Line down

•

Initialization failure

•

Data errors inbound

•

Data errors outbound

•

Remote reply timeouts

•

Local reply timeouts

•

Remote buffer errors

•

Local buffer errors

•

Selection timeouts

7-38

Running the UETP

•

Remote process errors

•

Local process errors

•

Locally initiated resets

•

Network initiated resets

For Nodes

7.6.5

•

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

Cluster-Integration Test Phase
The cluster-integration test phase consists of a single program and a
command file, and depends heavily on DECnet. It uses DECnet to create
SYSTEST—CLIG processes on each VAX/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 password must be empty.

•

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

•

The account can allow login only via DECnet.

•

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

7-39

Running the UETP

The latter two items are necessary to ensure the security and privacy of
your system. If the test cannot create a SYSTEST—CLIG process on some
VAX/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.
UETCLIG00.EXE has two threads of execution. The first, or master thread,
checks the cluster configuration; that is, the VAX/VMS and HSC nodes and
the disks attached to each of them that can be seen from the node running
the test. For each VAX/VMS node, it attempts to start up a SYSTEST—CLIG
process via DECnet. Those nodes where it succeeds run the command file,
UETCLIGOO.COM, which starts up UETCLIG00.EXE and runs the second
(slave) execution thread.
The process running the master thread checks to see that it can communicate
with the processes running the slave threads. It then instructs them to take
out locks so that a deadlock situation is created.
The master tries to create a file on some disk on each VAX/VMS and HSC
node in the cluster. It writes a block, reads it back and verifies it. The master
selects one VAX/VMS node at random and asks that node to read the block
and verify it. The master extends the file by writing another block and has
the slave read and verify the second block. The file is deleted.
The slave processes exit. They copy to the master 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.
During the test run, the master process announces the beginning and ending
of the test using cluster $BRKTHRU to each VAX/VMS node's console.
You can define the logical name MODE to the equivalence string DUMP to
trace most events as they occur.

7-40

Running the UETP

7.6.6

Termination of the 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 the UETP needs to be restarted. (You can request
multiple passes when you start up the test package; see Section 7.3.1.1).
At the end of an entire UETP run, UETP.COM deletes temporary files and
performs other cleanup activity.

7-41

Files of the VAX/VMS System

This appendix contains the names and brief descriptions of the files provided
by DIGITAL on the VAX/VMS system distribution medium. The files on this
medium can be found in eleven directories, three of which are reserved for
system use. The names of the remaining eight directories and descriptions of
their contents follow.
1

[SYSCBI]
This directory is reserved for EDTCAI files.

[SYSERR]
This directory is reserved for the error log file (ERRLOG.SYS).

[SYSEXE]
This directory, listed in Table A-l, contains commonly used executable
images of the operating system.

[SYSHLP]
This directory, listed in Table A-2, contains text libraries for the Help
Utility and other components.

[SYSHLP.EXAMPLES]
This subdirectory, listed in Table A-3, contains sample driver programs,
user-written system service programs, and other source code examples of
interest.

[SYSLIB]
This directory, listed in Table A-4, contains various macro and object
libraries as well as other files used for general reference.

[SYSMAINT]
This directory is reserved for system hardware diagnostic programs.

[SYSMGR]
This directory, listed in Table A-5, contains files used in managing the
operating system. This directory is the default directory for the system
manager's account.

[SYSMSG]
This directory, listed in Table A-6, contains system message text files.

10 [SYSTEST]

A—1

Files of the VAX/VMS System

This directory, listed in Table A-7, contains files used to run the User
Environment Test Package (UETP).
11 [SYSUPD]
This directory, listed in Table A-8, contains files used in applying system
updates.

Table A-1

Files Contained in Directory [SYSEXE]

File Name

Description

ACC.EXE

Accounting Utility

ACLEDT.EXE

Access Control List (ACL) Editor

ANALIMDMP.EXE

ANALYZE/PROCESS—DUMP image

ANALYZBAD.EXE

ANALYZE/MEDIA image

ANALYZOBJ.EXE

ANALYZE/IMAGE and ANALYZE/OBJECT image

ANALYZRMS.EXE

ANALYZE/RMS—FILE image

AUTHORIZE.EXE

User authorization program

BACKUP.EXE

Backup Utility

BADBLOCK.EXE

Dynamic bad block Files-11 ACP subprocess

BOOT58.EXE

Reserved for future use

BOOTBLOCK.EXE

Reserved for future use

CDU.EXE

Command Definition Utility

CHECKSUM.EXE

Used during installation of VAX/VMS updates

CIA.EXE

SHOW INTRUSION and DELETE/INTRUSION—RECORD
image

CLUSTRLOA.EXE

Loadable VAXcluster support code

CLUSTRLOA.MAP

Map of loadable VAXcluster support code

CLUSTRLOA.STB

Symbol table for CLUSTRLOA.EXE

CNDRIVER.EXE

DECnet Cl data link driver

CONFIGURE.EXE

Dynamic device configure process

CONINTERR.EXE

Connect-to-lnterrupt driver

CONVERT.EXE

Convert Utility

COPY.EXE

Copy utility

CRDRIVER.EXE

Card reader driver

CREATE.EXE

File and directory creation utility

CREATEFDL.EXE

CREATE/FDL image

CSP.EXE

Cluster server process image

A—2

Files of the VAX/VMS System

Table A-1 (Cont.)

Files Contained in Directory [SYSEXE]

File Name

Description

CTDRIVER.EXE

CTERM driver

CVDRIVER.EXE

8600/8650 console driver

CVTNAF.EXE

Convert NETUAF.DAT utility

CVTUAF.EXE

Convert SYSUAF.DAT utility

CWDRIVER.EXE

8800 console driver

DBDRIVER.EXE

RP05 and RP06 disk driver

DCL.EXE

Command interpreter

DCLDEF.STB1

Global definitions for DCL structures

DDDRIVER.EXE

TU58 driver

DELETE.EXE

File deletion/purge utility

DIFF.EXE

File compare utility

DIRECTORY.EXE

Directory utility

DISKQUOTA.EXE

Disk Quota Utility

DISMOUNT.EXE

Volume dismount utility

DLDRIVER.EXE

RL02 disk driver

DMDRIVER.EXE

RK07 disk driver

DQDRIVER.EXE

RB730 driver

DRDRIVER.EXE

RM03 disk driver

DSRINDEX.EXE

RUNOFF/INDEX image

DSRTOC.EXE

RUNOFF/CONTENTS image

DTR.COM

DTRECV.EXE server initiating procedure

DTRECV.EXE

DTSEND server

DTSEND.EXE

DECnet logical links test program

DUDRIVER.EXE

UDA disk driver

DUMP.EXE

Dump utility

DXDRIVER.EXE

RX01 console floppy diskette driver

DYDRIVER.EXE

RX02 floppy diskette driver

DZDRIVER.EXE

DZ1 1 port driver

EDF.EXE

File definition language editor

EDT.EXE

EDT text editor

ENCRYPFAC.EXE

ENCRYPT command image

^ot supported by DIGITAL

A—3

Files of the VAX/VMS System

Table A-1 (Cont.)

Files Contained in Directory [SYSEXE]

File Name

Description

ERF.EXE

ANALYZE/ERROR image

ERF*.EXE

ANALYZE/ERROR routines

ERRFMT.EXE

Error logging facility

EVL.COM

Command file used by DECnet error logging

EVL.EXE

DECnet event logging program

EXCHANGE.EXE

RT-11/DOS file transfer utility

FI 1AACP.EXE

Files-11 Structure Level 1 ancillary control process

FI 1BXQP.EXE

File system extended QIO processor

FAL.COM

FAL startup procedure

FAL.EXE

DECnet file access listener

FILESERV.EXE

File system cache flush server

FPEMUL.EXE

Floating point emulation for F-, D-, G- and H-floating point

FYDRIVER.EXE

DUP (Diagnostics/Utilities Protocol) driver

HLD.COM

Command procedure used by HLD.EXE

HLD.EXE

Downline task loading program

HSCPAD.EXE

SET HOST/HSC command processor

IMGDEF.STB1

Global definitions for image activator structures

INIT.EXE

Disk device initialization utility

INPSMB.EXE

Card reader input symbiont

INSTALL.EXE

Utility that installs known images

JOBCTL.EXE

Job controller/symbiont manager

LADRIVER.EXE

LPA-11 driver

LALOAD.EXE

Accepts commands from or sends requests to LALOADER
to load LPA-11 microcode

LALOADER.EXE

Loads LPA-11 microcode upon power recovery or upon
request from LALOAD

LATCP.EXE

LAT-11 control program

LCDRIVER.EXE

DMF32 lineprinter driver

LIBRARIAN.EXE

Librarian

LIDRIVER.EXE

DMB32 line printer driver

LINK.EXE

Linker

^ot supported by DIGITAL

A—4

Table A-1 (Cont.)

Files Contained in Directory [SYSEXE]

File Name

Description

LOGINOUT.EXE

LPDRIVER.EXE

Line printer driver

LTDRIVER.EXE

LAT-1 1 driver

MACR032.EXE

VAX MACRO assembler

MAIL.COM

Command procedure used by DECnet mail

MAIL.EXE

Mail Utility

MAILEDIT.COM

Default MAIL editing command procedure

MBXDRIVER.EXE

Shared memory mailbox driver

MESSAGE.EXE

Message compiler

MIRROR.COM

MIRROR startup procedure

MIRROR.EXE

DECnet node loopback server

MOM.COM

Maintenance operations module DECnet comm
procedure

MOM.EXE

Maintenance operations module image

M0NIT0R.EXE

Monitor Utility

MP.EXE

VAX-1 1/782 multiprocessing code

MP.MAP

Map to VAX-1 1/782 multiprocessing code

MP.STB1

Symbol table for MP.EXE

MP_8NN.MAP

Map to MP_8NN.MSKEXE

MP_8NN.MSKEXE

VAX multiprocessing code

MP_8NN.STB

Symbol table for MP_8NN.MSKEXE

MP_8SS.MAP

Map to MP_8SS.MSKEXE

MP_8SS.MSKEXE
MP_8SS.STB

VAX multiprocessing code
Symbol table for MP_8SS.MSKEXE

MSCP.EXE

MSCP server

MTAACP.EXE

Magnetic tape ancillary control process

NCP.EXE

Network control program

NDDRIVER.EXE

DECnet pseudo data link driver

NETACP.EXE

DECnet ancillary control process

NETDEF.STB1

Symbol table for network definition

NETDRIVER.EXE

DECnet logical link driver

^ot supported by DIGITAL

Files of the VAX/VMS System

Table A—1 (Cont.)

Files Contained in Directory [SYSEXE]

File Name

Description

NETSERVER.COM

Network server DECnet command procedure

NETSERVER.EXE

Network server image

NICONFIG.COM

Ethernet configurator DECnet command procedure

NICONFIG.EXE

Ethernet configurator image

NML.COM

NML server startup procedure

NML.EXE

DECnet network management listener

NODRIVER.EXE

Asynchronous DECnet driver

NOTICE.TXT

Text file that can contain announcements to system users

OPCCRASH.EXE

System shutdown utility

0PC0M.EXE

Operator communications utility

PADRIVER.EXE

CI780 port driver

PAGEFILE.SYS

System paging file

PARAMS.DAT

Data file for parameter values

PATCH.EXE

Patch Utility

PHONE.COM

PHONE startup procedure

PH0NE.EXE

Phone Utility

PRTSMB.EXE

Print symbiont

PUDRIVER.EXE

Cl UDA port driver

QUEMAN.EXE

Queue managing utility

RECLAIM.EXE

CONVERT/RECLAIM image

REMACP.EXE

Remote device ACP

RENAME.EXE

File rename utility

REPLY.EXE

Message broadcasting facility

REQUEST.EXE

Operator request facility

RMS.EXE

Record Management Services

RMS.MAP

Map to RMS.EXE

RMS.STB1

RMS symbol table

RMSDEF.STB1

Global definitions for VAX RMS structures

RTB.EXE

Utility that writes an RT-11 bootstrap on disk

RTPAD.EXE

Remote terminal command interface

RTTDRIVER.EXE

Remote terminal driver

’Not supported by DIGITAL

A—6

Files of the VAX/VMS System

Table A-1 (Cont.)

Files Contained in Directory [SYSEXE]

File Name

Description

RUNDET.EXE

Facility that runs detached images

RUNOFF.EXE

DIGITAL Standard Runoff text formatting utility

RXDRIVER.EXE

Console RX50 driver

SCSDEF.STB1

Symbol table for loadable routines

SCSLOA.EXE

Loadable routines used by SCS

SDA.EXE

System Dump Analyzer

SDLNPARSE.EXE

SDL; Used for installing optional software

SEARCH.EXE

File search utility

SET.EXE

SET command processor

SETPO.EXE

SET MESSAGE command processor

SETRIGHTS.EXE

SET RIGHTS—LIST command processor

SETSHOACL.EXE

SET and SHOW ACCESS CONTROL LIST commands

SHOW.EXE

SHOW command processor

SHUTDOWN.COM

System shutdown command procedure

SHWCLSTR.EXE

SHOW CLUSTER command

SMGBLDTRM.EXE

Compiler for TERMTABLE definition file

SMGMAPTRM.EXE

Termtable global section, run at system startup

SMGTERMS.TXT

ASCII source file for DIGITAL terminal definitions

SORTMERGE.EXE

SORT and MERGE commands

SRTTRN.EXE

SORT specification file translator image

STABACCOP.EXE

Copy program for building standalone BACKUP kit

STABACKUP.EXE

Standalone Backup Utility

STACONFIG.EXE

HSC system disk configurator image

STANDCONF.EXE

Standalone BACKUP configure image

STARTUP.COM

System startup command procedure

STASYSGEN.EXE

Standalone System Generation Utility

STOPREM.EXE

Stop REMACP utility

SUBMIT.EXE

Batch job submission utility

SUMSLP.EXE

Source file editor

SWAPFILE.SYS

System swap file

SYS.EXE

Operating system image file

^ot supported by DIGITAL

A—7

Files of the VAX/VMS System

Table A—1 (Cont.)

Files Contained in Directory [SYSEXE]

File Name

Description

SYS.MAP

Map of the operating system

SYS.STB

Global symbol table of operating system

SYSBOOT.EXE

System bootstrap utility

SYSDEF.STB1

Global definitions for executive structures

SYSDUMP.DMP

System dump file

SYSGEN.EXE

System Generation Utility

SYSINIT.EXE

Operating system initialization image

SYSLOA730.EXE

VAX-11/730 system image file

SYSLOA750.EXE

VAX-11/750 system image file

SYSLOA780.EXE

VAX-11/780 system image file

SYSLOA790.EXE

VAX 8600/8650 system image file

SYSL0A8NN.EXE

VAX 8800 system image file

SYSL0A8SS.EXE

VAX 8200/8300 system image file

SYSUAF.RL2

Unmodified copy of SYSUAF.DAT

TECO.EXE

TECO text editor

TERMTABLE.EXE

Binary terminal definitions file

TERMTABLE.TXT

Terminal definitions source file

TFDRIVER.EXE

TU78 driver

TKDRIVER.EXE

TK50 driver

TMDRIVER.EXE

Magnetic tape driver

TPU.EXE

VAXTPU text processing utility

TSDRIVER.EXE

TS1 1 magnetic tape driver

TTDRIVER.EXE

Terminal driver

TTRDVFY.EXE

Auxiliary terminal driver module

TUDRIVER.EXE

Magnetic tape class driver

TYPE.EXE

Type utility

UNLOCK.EXE

File unlock utility

VAXVMSSYS.PAR

System parameter file

VERIFY.EXE

ANALYZE/DISK_STRUCTRURE image

VMB.EXE

VAX/VMS primary bootstrap

VPM.EXE

Cluster monitor

'Not supported by DIGITAL

A—8

Table A-1 (Cont.)

Files Contained in Directory [SYSEXE]

File Name

Description

VMOUNT.EXE

Volume mount utility

VMSHELP.EXE

Help Utility

WRITEBOOT.EXE

System volume bootblock writing utility

WTDRIVER.EXE

VaxStation device driver

WTDRIVER.STB

Symbol table for VaxStation device driver

XADRIVER.EXE

Reserved for future use

XDDRIVER.EXE

DECnet DMP11 data link driver

XEDRIVER.EXE

UNA driver

XFDRIVER.EXE

DR32 system interconnect interface driver

XFLOADER.EXE

DR32 microcode loader utility

XGDRIVER.EXE

DECnet DMF datalink driver

XMDRIVER.EXE

DMC11 Synchronous Communications Line Inter

XQDRIVER.EXE

QNA driver

XWDRIVER.EXE

DUP1 1 device driver

YCDRIVER.EXE

DMF32 asynchronous port driver

YFDRIVER.EXE

DHU port driver

YIDRIVER.EXE

DMB32 terminal port driver

Table A-2

Files Contained in Directory [SYSHLP]

File Name

Help Library

ACLEDT.HLB
ANLRMSHLP.HLB

Access Control List Editor
ANALYZE/RMS—FILE command

DEBUGHLP.HLB

Debugger

DISKQUOTA.HLB

Disk Quota Utility

EDFHLP.HLB

File Definition Language

EDTHELP.HLB

EDT

EDTVT100.DOC

EDT keypad layout for VT100

EDTVT52.DOC

EDT keypad layout for VT52

EXAMPLES.DIR

Examples directory

EXCHNGHLP.HLB

Exchange Utility

Files of the VAX/VMS System

Table A-2 (Cont.)

Files Contained in Directory [SYSHLP]

File Name

Help Library

HELPLIB.HLB

Default (DCL) help library

INSTALHLP.HLB

Install Utility

LATCP.HLB

LAT Control Program

MAILHELP.HLB

Mail Utility

MNRHELP.HLB

Monitor Utility

NCPHELP.HLB

Network Control Program

PATCHHELP.HLB

Patch Utility

PHONEHELP.HLB

Phone Utility

SDA.HLB

System Dump Analyzer

SHWCLHELP.HLB

Show Cluster Utility

SYSGEN.HLB

System Generation Utility

TECO.HLB

TECO

TPUHELP

VAXTPU utility help file

UAFHELP.HLB

User authorization file

VMSTLRHLP.HLB

Tailoring facility

Table A-3

Files Contained in Directory [SYSHLP.EXAMPLES]

File Name

Description

ADDRIVER.MAR

Example device driver for ADI 1-K

CONNECT.COM

Command procedure that connects device for LABIO system

DOD—ERAPAT.MAR

Example loadable erase pattern generator

DRCOPY.PRM

Parameter file for DRCOPY routines

DRCOPYBLD.COM

Command procedure to build DRCOPY.EXE

DRMAST.MAR

VAX RMS interface for DRMASTER.FOR

DRMASTER.FOR

Master subroutines for DRCOPY

DRSLAVE.FOR

Slave subroutines for DRCOPY

DRSLV.MAR

VAX RMS interface for DRSLAVE.FOR

DTE_DF03.MAR

SET HOST/DTE modem support

GBLSECUFO.MAR

Opens file used as a global section for LABIO system

A—10

Files of the VAX/VMS System

Table A-3 (Cont.)

Files Contained in Directory [SYSHLP.EXAMPLES]

File Name

Description

LABCHNDEF.FOR

Defines information associated wth each A/D for LABIO
system

LABIO.OPT

Linker options file for linking modules to be used in LABIO

LABIOACQ.FOR

Acquires data for LABIO system

LABIOCIN.MAR

Contains connect-to-interrupt call for LABIO system

LABIOCIN.OPT

Linker options file for linking LABIO_DATA_ACQ

LABIOCOM.FOR

Attaches a LABIO user program to the LABIO system
modules of the LABIO system

LABIOCOMP.COM

Command procedure to compile and assemble the modules
of the LABIO system

LABIOCON.FOR

Handles user requests and modifies the database for LABIO
system

LABIOLINK.COM

Command procedure to link LABIO system

LABIOPEAK.FOR

Samples channel for peak data in LABIO system

LABIOSAMP.FOR

Samples channel in intervals, reporting date, time, and
average value on logical device for LABIO system

LABIOSEC.FOR

Places LABIO—SECTION on page boundary

LABIOSTAT.FOR

Displays A/D channel status for LABIO system

LABIOSTRT.COM

Command procedure to start LABIO system

LABMBXDEF.FOR

Defines mailbox block for LABIO system

LBRDEMO.COM

Command procedure to create Librarian DEMO.EXE

LBRDEMO.FOR

Librarian demo (first part)

LBRMAC.MAR

Librarian demo (second part)

LPATEST.FOR

LPA1 1-K test program

LPMULT.B32

Example program for line printer

MAILCOMPRESS.COM

Sample procedure to compress mail files

MAILCVT.COM

Sample procedure to convert VAX/VMS Version 3.0 mail
files

MAILUAF.COM

Sample procedure to manipulate
SYS$SYSTEM: VMSMAIL.DAT

MONITOR.COM

Command procedure to generate MONITOR recording file

MONSUM.COM

Command procedure to generate cluster multi-file summaries

MSCPMOUNT.COM

Example cluster disk mount procedure

A—11

Files of the VAX/VMS System

Table A-3 (Cont.)

Files Contained in Directory [SYSHLP.EXAMPLES]
Description

File Name
PEAK.FOR

Peak selection routine in LABIO system

SCRFT.MAR

Optional screen package (SCR$ ... in RTL) extension to
handle foreign terminals

SYSGTTSTR.MSG

Sample SYSGEN TERMINAL/ECHO message file

TDRIVER.MAR

Template for user-written driver

TESTLABIO.FOR

Tests LABIO system

USSDISP.MAR

Sample user system service dispatch and service examples

USSLINK.COM

Link command procedure for USSDISP

USSTEST.MAR

Sample program to invoke one of the example user services
implemented in USSDISP

USSTSTLNK.COM

Link command procedure for USSTEST

XADRIVER.MAR

DR11 driver

XALINK.MAR

Sample DR1 IW-to-DRI 1W link program

XAMESSAGE.MAR

DR1 1 test program

XATEST.COM

Used to set up XALINK.MAR

XATEST.FOR

Companion program for XAMESSAGE

XIDRIVER.MAR

Example driver for parallel port on DMF32

Table A-4

Files Contained in Directory [SYSLIB]
Description

File Name
ACLEDIT.INI

Access Control List Editor initialization file

ACLEDIT.TPU

VAXTPU Access Control List Editor initialization file

ACLEDTSHR.EXE

VAXTPU ACL Editor routines

ACLSECINI.TPUSSECTION

Shareable VAXTPU Access Control List Editor initialization
file

ADARTL.EXE

VAX ADA Run-Time Library

BASRTL.EXE

VAX BASIC Run-Time Library

BASRTL2.EXE

VAX BASIC Run-Time Library (part 2)

CDDSHR.EXE

Dummy CDD image for layered products

CLIMAC.L32

BLISS interface to CLI$ routines

CLIMAC.REQ

BLISS interface to CLI$ routines

A-12

Files of the VAX/VMS System

Table A-4 (Cont.)

Files Contained in Directory [SYSLIB]

File Name

Description

COBRTL.EXE

VAX COBOL Run-Time Library

CONVSHR.EXE

CONVERT and CONVERT/RECLAIM shareable image

CRFSHR.EXE

Cross-reference shareable image

DBGSSISHR.EXE

VAX DEBUG system service intercept handler

DCLTABLES.EXE

DCL command tables

DCXSHR.EXE

Data compression support

DEBUG.EXE

VAX/VMS Debugger

DEBUG.TPU

Debug support for VAXTPU

DELTA.EXE

DELTA multimode debugging tool image

DELTA.OBJ

Alternate debugging tool

DISMNTSHR.EXE

DISMOUNT shareable image

DTE_DF03.EXE

SET HOST/DTE support for DF03 modem

DTE_DF112.EXE

SET HOST/DTE support for DF1 12 modem

DTKSWITCH.EXE

DECtalk utility routines

DYNSWITCH.EXE

Asynchronous DECnet-VAX routines

EDTSECINI.TPU

EDT Keypad Emulator interface to the VAXTPU text
processing utility

EDTSECINI.TPUSSECTION

Shareable EDT Keypad Emulator interface to the VAXTPU
text processing utility

EDTSHR.EXE

EDT editor

ENCRYPSHR.EXE

Dummy VAX Encryption support module

ERFCOMMON.EXE

ANALYZE/ERROR common data structures

ERFCTLSHR.EXE

ANALYZE/ERROR routines

ERFLIB.TLB

ANALYZE/ERROR device descriptions

ERFSHR.EXE

ANALYZE/ERROR common routines

EVESECINI.TPU

EVE interface to the VAXTPU text processing utility

EVESECINI.TPUSSECTION

Shareable EVE interface to the VAXTPU text processing
utility

FDLSHR.EXE

FDL parsing shareable image

FORDEF.FOR

FORTRAN INCLUDE file: FOR$ symbols

FORIOSDEF.FOR

FORTRAN INCLUDE file: IOSTAT error codes

FORRTL.EXE

VAX FORTRAN Run-Time Library

A-13

Files of the VAX/VMS System

Table A-4 (Cont.)

Files Contained in Directory [SYSLIB]

File Name

Description

IMAGELIB.OLB

System default shareable image library

IMGDMP.EXE

Image dump procedures

LBRSHR.EXE

Librarian shareable image

LIB.L32

Operating system BLISS library

LIB.MLB

Operating system macro library

LIB.REQ

Structure definitions of executive internals for use by BLISS
programs

LIBDEF.FOR

FORTRAN program utility INCLUDE files

LIBRTL.EXE

VAX Common Run-Time Library

LIBRTL2.EXE

VAX Common Run-Time Library (part 2)

MOUNTSHR.EXE

MOUNT shareable image

MTHDEF.FOR

FORTRAN INCLUDE files: MATH$ symbols

MTHRTL.EXE

VAX math support Run-Time Library

NMLSHR.EXE

DECnet management listener shareable image

PASRTL.EXE

VAX Pascal Run-Time Library

PLIRTL.EXE

VAX PL/I Run-Time Library

RPGRTL.EXE

VAX RPG Run-Time Library

SCRSHR.EXE

RTL terminal screen procedures shareable image

SCNRTL.EXE

VAX SCAN Run-Time Library

SECURESHR.EXE

Rights database (RIGHTSLIST.DAT) service routines

SIGDEF.FOR

FORTRAN program utility INCLUDE files

SMBSRVSHR.EXE

Print symbiont service routines

SMGSHR.EXE

VAX Screen Management Run-Time Library

SORTSHR.EXE

VAX Sort/Merge Run-Time Library

STARLET.L32

BLISS system library

STARLET.MLB

System macro library

STARLET.OLB

System object library and Run-Time Library

STARLET.REQ

User interface structures for use by BLISS programs

STARLETSD.TLB

Text library of STARLET definitions; used during layered
product installations.

SUMSHR.EXE

Source update merge shareable image

TPAMAC.L32

BLISS TPARSE macros

A-14

Files of the VAX/VMS System

Table A—4 (Cont.)

Files Contained in Directory [SYSLIB]

File Name

Description

TPAMAC.REQ

Structure definitions for BLISS programs using TPARSE

TPUSECTINI.TPU$SECTION

Shareable VAXTPU text processing utility

TPUSHR.EXE

VAXTPU text processing utility

TRACE.EXE

VAX/VMS error traceback facility

VAXCCURSE.OLB

VAX C Run-Time Library

VAXCRTL.EXE

VAX C Run-Time Library

VAXCRTL.OLB

VAX C Run-Time Library

VMSRTL.EXE

Run-Time Library shareable image

XFDEF.FOR

Definitions available for programs using DR780 support
routines

Table A—5

Files Contained in Directory [SYSMGR]

File Name

Description

ACCOUNTNG.DAT

Accounting data file

ADDUSER.COM

Command procedure to add users to SYSUAF.DAT

ALFMAINT.COM

Command procedure to maintain
SYS$SYSTEM:SYSALF.DAT

LOADNET.COM

Command procedure to create network ACP process

LPA1 1STRT.COM

LPA1 1 site-specific startup command procedure

LTLOAD.COM

Command procedure to load and start LAT

MAKEROOT.COM

Command procedure to add new roots to cluster common
system disk

NETCONFIG.COM

Command procedure to configure network database

RTTLOAD.COM

Remote terminal loader

SECAUDIT.COM

Command procedure to extract information from the
operator's log

SOFTWARE_HISTORY.DAT

A history of software installations

STARTNET.COM

DECnet startup procedure

SYSHUTDWN.COM

Site-specific system shutdown command procedure

SYSTARTUP.COM

Site-specific system startup command procedure

A—15

Files of the VAX/VMS System

Table A-5 (Cont.)
File Name

Files Contained in Directory [SYSMGR]
Description

VMSIMAGES.COM

Invoked at startup to install known images

VMSIMAGES.DAT

Data file for VMSIMAGES.COM

Table A—6

Files Contained in Directory [SYSMSG]

File Name

Description

ADAMSG.EXE

ADA Run-Time Library

CLIUTLMSG.EXE

ANALYZE/MEDIA, EXCHANGE, MAIL, PHONE, PRINT,
SUBMIT, RUN, SET, SHOW, SEARCH

DBGTBKMSG.EXE

DEBUG, TRACE

FILMNTMSG.EXE

ANALYZE/OBJECT, ANALYZE/IMAGE, EDIT/FDL,
ANALYZE/DISK

NETWRKMSG.EXE

NCP, SET HOST

PASMSG.EXE

PASCAL Run-Time Library

PLIMSG.EXE

PL/I Run-Time Library

PRGDEVMSG.EXE

CDU, DIFF, DUMP, LIBRARY, LINK, MACRO, MESSAGE,
PATCH, ANALYZE/SYSTEM, ANALYZE/CRASH

RPGMSG.EXE

RPG Run-Time Library

SHRIMGMSG.EXE

CONVSHR, DCXSHR, FDLSHR, SORTSHR, SMGSHR,
EDTSHR

SYSMGTMSG.EXE

ACC, EDIT/ACL, BACKUP, INSTALL, MONITOR,
AUTHORIZE

SYSMSG.EXE

System message file

TPUMSG.EXE

VAXTPU text processing utility message file

VAXCMSG.EXE

VAX C message file

A—1 6

Files of the VAX/VMS System

Table A-7

Files Contained in Directory [SYSTEST]

File Name

Description

TCNTRL.CLD

Defines commands to invoke the UETP Test Controller

UETCLIGOO.COM

Command procedure to run the cluster-integration phase

UETCLIG00.DAT

Used by UETP Test Controller to start cluster-integration
phase

UETCOMSOO.EXE

DMC and DMR device test

UETDISK00.EXE

Disk device test

UETDMPF00.EXE

DMP and DMF32 device test

UETDNETOO.COM

Command procedure for the DECnet phase

UETDNET00.DAT

Used by UETP test controller to start DECnet phase

UETDR1W00.EXE

DR11-W device test

UETDR7800.EXE

DR780 and DR750 device test

UETFORT01.DAT

FORTRAN data file used by UETFORTOI

UETFORT01.EXE

Artificial load in load test

UETFORT02.EXE

Artificial load in load test

UETFORT03.EXE

Artificial load in load test

UETINIT00.EXE

Checks UETP environment and sets overall parameters

UETINIT01.EXE

Quick checks devices and builds UETINIDEV.DAT

UETLOADOO.DAT

Used by UETP test controller to start load test phase

UETLOAD02.COM

User script for load test

UETLOAD03.COM

User script for load test

UETLOAD04.COM

User script for load test

UETLOAD05.COM

User script for load test

UETL0AD06.COM

User script for load test

UETL0AD07.C0M

User script for load test

UETLOAD08.COM

User script for load test

UETLOAD09.COM

User script for load test

UETL0AD10.C0M

User script for load test

UETL0AD1 1 .COM

User script for load test

UETLPAK00.EXE

LPA1 1-K device test

UETMA7800.EXE

MA780 device test

UETMEMY01.EXE

Artificial load for load test

UETNETS00.EXE

Reports nonzero counters as part of DECnet phase

A—17

Files of the VAX/VMS System

Table A-7 (Cont.)

Files Contained in Directory [SYSTEST]
Description

File Name
UETP.COM

Main command procedure for entire UETP

UETPHAS00.EXE

Test controller

UETRSXF0R.EXE

Artificial load for load test

UETSUPDEV.DAT

Supported device data file

UETTAPE00.EXE

Magnetic tape device test

UETTTYS00.EXE

Terminal and line printer device test

UETUNAS00.EXE

DEUNA device test

Table A-8

Files Contained in Directory [SYSUPD]

File Name

Description

730CNSL.DAT

Data file to build an 11/730 console medium

750CNSL.DAT

Data file to build an 11/750 console medium

780CNSL.DAT

Data file to build an 11/780 console meduim

AUTOGEN.COM

Command procedure to determine parameter values

BACKUSER.COM

Command procedure to back up user files and some system
files

BASEINSTAL.COM

Command procedure to install the MicroVMS Common
Utilities Option

BLISSREQ.TLR

List of files in the BLISS tailoring group

BOOTBLDR.COM

Multiprocessing console floppy diskette command
procedure

BOOTUPD.COM

Command procedure to update VAX/VMS bootstrap file on
console floppy diskette

CONSCOPY.COM

Command procedure that copies console floppy diskette

CONSOLBLD.COM

Command procedure to build a VMS console medium

CVTNAF.COM

Command procedure to convert NETUAF.DAT

CVTUAF.COM

Command procedure to convert SYSUAF.DAT

DECNET.TLR

List of files in the DECnet tailoring group

DIRCLENUP.COM

Command procedure to clean up dangling entries on a
Version 3 or Version 4 VAX/VMS system

DISKITBLD.COM

Command procedure to build a VMS or MicroVMS kit

A—18

Files of the VAX/VMS System

Table A—8 (Cont.)

Files Contained in Directory [SYSUPD]

File Name

Description

DEVELOP.TLR

List of files in the DEVELOP tailoring group

DXCOPY.COM

Command procedure that copies files from console floppy
diskette and restores files to floppy diskette

EXAMPLES.TLR

List of files in the EXAMPLE tailoring group

FILETOOLS.TLR

List of files in the TOOLS tailoring group

HELP.TLR

List of files in the HELP tailoring group

LIBDECOMP.COM

Command procedure to expand libraries shipped in datareduced format

LIBRARY.TLR

List of files in the LIBRARY tailoring group

MAKE_IMAGE_MASK.CLD

Describes the MAKE—IMAGE—MASK utility command line

MANAGER.TLR

List of files in the MANAGER tailoring group

MISCTOOLS.TLR

List of files in the MISCTOOLS tailoring group

MOVE.COM

Command procedure to move files from one directory to
another while maintaining the order of the version numbers

QUEUES.TLR

List of files in the QUEUES tailoring group

REMOVE.COM

Command procedure to remove system files in an orderly
manner

RESTUSER.COM

Command procedure to restore user and some system files
from a backup done with BACKUSER.COM

REQUIRED.TLR

List of files in the REQUIRED tailoring group

SETDEFBOO.COM

Command procedure that sets default boot command file

SPKITBLD.COM

Command procedure to build software product kits

STABACKIT.COM

Command procedure that builds standalone BACKUP to
media

STA_MSCPKIT.COM

Command procedure to build a standalone VMS system kit
for MSCP operation

SWAPFILES.COM

Command procedure that creates swapping, paging, and
system dump files of appropriate size for system being
installed

TEXTTOOLS.TLR

List of files in the TEXTTOOLS tailoring group

UETP.TLR

List of files in the UETP tailoring group

UVINSTAL.COM

Command procedure to install the MicroVMS Common
Utilities Option

UVKITBLD.COM

Command procedure to build MicroVMS kits

A—1 9

Files of the VAX/VMS System

Table A-8 (Cont.)

Files Contained in Directory [SYSUPD]

File Name

Description

VMBUVAX1.COM

Command procedure to build a floppy disk which can be
used on MicroVAX I's to boot from disks with floating
CSR's

VMSINSTAL.COM

Command procedure to install EDTCAI and maintenance
updates

VMSKITBLD.COM

Command procedure that builds and copies VAX/VMS
distribution disk

VMSKITBLD.DAT

List of files in VAX/VMS system that drives
VMSKITBLD.COM

VMSMEDIA.COM

Command procedure to build any VMS media kit

VMSOPT.COM

Command procedure to install the optional file set to the
VAX/VMS operating system

VMSTAILOR.COM

Tailoring facility command procedure (supported only on
VAX-11/730)

VMSUPDATE.COM

System update command procedure

A—20

RESTORING THE VAX/VMS SOURCE KIT

This material is included for users who purchase the source license. It is
limited to telling you how to invoke the command procedure that directs
the building of the source kit and references to appropriate supporting
documentation.
The VAX/VMS source kit is shipped on a set of magnetic tapes that contain
the source files, object files, command files, language processors, and utilities
you need to build any standard VAX/VMS component. The kit may be
restored to any system that has sufficient storage capabilities.

Note
The languages and utilities used to build operating system
components are not supported by DIGITAL.
Before you restore the source kit to a disk storage system, be sure you have
enough free disk space. A single component may use as much as 40,000 free
blocks. To restore the entire kit, you will need a disk drive with a storage
capacity of at least 250,000 blocks. When doing a complete system build,
you will need a result disk device with a storage capacity of approximately
900,000 blocks.
To restore the source kit, you must first mount the tape labeled VMSRC1
and restore the file [SYSBLDCOMJSRCINSTAL.COM. When you invoke
SRCINSTAL.COM, it asks you for information it needs to define the system
building environment.
1

Allocate a tape drive with the following command:
$ALLOCATE ddcu:

See Chapter 4 for help with device names.

Load the tape into the allocated drive.

Mount the tape as foreign with this command:
$M0UNT/F0REIGN ddcu:

VMSRC1

Restore the source installation command procedure with this command:
$BACKUP ddcu:SYSBLDC0M/SELECT=(SRCINSTAL.COM)

ddcu:[...]

After you restore the file, dismount the tape.

B—1

RESTORING THE VAX/VMS SOURCE KIT

Invoke the source installation command procedure by entering
$®ddcu:[SYSBLDCOM]SRCINSTAL.COM

The command procedure creates a system build account containing the
logical name definitions and private command definitions needed to set
up the proper environment for a system build. To log in to this account,
specify the user name SYSTEMBUILD and the password CAVEAT—
EMPTOR.
To obtain a general description of the source kit, you can print a copy of the
file [SYSBLDCOMJSOURCEKIT.DOC.

B—2

Using VMSUPDATE

This appendix outlines the procedure for installing optional products using
VMSUPDATE.

Note
VMSUPDATE is not supported on tailored systems nor on cluster
configurations that share a common system disk.
The procedure for installing optional software products with VMSUPDATE
requires little involvement on your part beyond setting up the proper
conditions for the installation and responding to queries and prompting
messages displayed as the installation proceeds.
When you invoke VMSUPDATE, command procedures contained in the
distribution media direct the installation by means of queries and instructions
sent to the terminal. Most queries require only that you provide a YES or
NO response.

C.1

Preparing to Install Optional Software
Optional software products are distributed on one or more pieces of console
media depending on the products. Each piece is labeled with a unique
name and serial number that differentiates it from others in the distribution
kit. Check that your kit contains all the console media listed in the bill of
materials.
To prepare for the installation, do the following:
1

Back up your system disk (see Chapter 4). Because optional software
products may delete older product versions before installing new ones, it
is advisable to back up your system disk before attempting any software
installation. It is also advisable because a system failure at a critical point
of the installation could leave unusable files.

Note
If the SYSGEN parameters MOUNTMSG or DISMOUMSG
are set to 1, you will receive a message from OPCOM each
time a disk, tape, or piece of console media is mounted or
dismounted. These messages are normally disabled, but
C-1

console terminal, they will appear from 1 to 30 seconds after
each mount or dismount.

Prevent users from gaining access to the system by executing the
SHUTDOWN.COM command procedure. Then reboot the system.

Set the login quota to 0.
$ SET LOGINS/INTERACTIVE = 0

Be sure that you have set your default to the disk that is to receive
the product. This is typically the system disk with the logical name
SYS$SYSROOT.
If you are installing optional software on a system disk other than the
disk from which you booted, you must define a logical name for the
target disk. For example, if you are installing software on an RK07 disk
on the first drive, issue the following commands:
$ DEFINE TARGET DMA1:[SYSO.]
$ SET DEFAULT TARGET:[SYSUPD]

Note
Check the documentation for your product to be sure it can
be installed on a device other than the system disk.

If you are installing to the current system disk, establish the following
default:
$ SET DEFAULT SYS$UPDATE

C.2

Performing the Installation
Enter the following command to begin the installation:
$ ®VMSUPDATE

You will receive the following message text at your terminal:
VMS Update Procedure
This command procedure performs VAX/VMS software updates and optional
software installations for VAX/VMS Version 4.4. During this sequence, the
standard console medium will not be present in the console drive.
Therefore, the system may be vulnerable to a power failure or other fatal
crash. If a system crash should occur during this period the update
sequence can be restarted at the beginning of the first incomplete
update.
Dismount the current console medium.
Please place the first floppy in the console drive.

C—2

Using VMSUPDATE

Note
The examples used here relate to the use of floppy diskettes in
console drive CSA1 on a VAX-11/780 system. If your system is
not a VAX-11/780, the console media is TU58 cartridges and the
console drive is CSA1. See Chapter 2 for help in locating the
console drives.
After placing the first piece of media in the CSA1 drive, the installation
procedure asks
Are you ready to continue?:

If you enter the letter Y, the installation proceeds.
If you type N, the request to insert the first piece of media will be repeated
together with the question "Are you ready to continue?".
When the installation resumes, the following message is displayed:
'/.MOUNT-1-MOUNTED

<label> mounted on _CSA1:

The remaining questions and prompts depend on the product you are
installing.

C.3

Completing the Installation
When the installation is completed, control is returned to
VMSUPDATE.COM, which asks
Are there more kits to process?:

If you enter the letter Y, the installation procedure resumes with the
following request:
Please place the first floppy in the console drive.

If you have no more products to install, enter the letter N. VMSUPDATE
responds by sending the you the following message and then returning you
to command level:
Requested update sequence complete.

To use the new product(s), you will have to shut down the processor and
reboot the system.

C—3

Operating System Distribution Kits

This appendix lists the software components of the distribution kits for
the various VAX processors. Each kit also contains appropriate supporting
documentation.

D.1

VAX 8600 Distribution Kit
VAX/VMS software for the VAX 8600 is distributed on magnetic tape.
In addition to the madia tape and other materials in the software distribution
kit, you will need a console RL02 before you can install or upgrade a
VAX/VMS system. If you are installing a new system, the console RL02 was
shipped with the hardware. If you are upgrading an existing system, your
current console RL02 will be upgraded as part of the upgrade procedure.
The VAX 8600 magnetic tape software distribution kit contains the following
materials:
•

The VAX/VMS Version 4.4 distribution tape. The asterisk (*) denotes
the latest version.
Part number: BB-BT05*-BE
Part description: VAX/VMS V4.4 BIN 16MT9

•

The VAX/VMS Version 4.4 mandatory update tape. The asterisk (*)
denotes the latest version.
Part number: BB-FY83*-BE
Part description: VAX/VMS V4.4 BIN 16MT9 MANDATORY
UPDATE

•

One RL02 disk containing standalone BACKUP. The asterisk (*) denotes
the latest version.
Part number: BC-EZ69*-BE
Part description: VAX/VMS V4.4 BIN RL02 S/A BACKUP

D—1

Operating System Distribution Kits

D.2

VAX 8200 Distribution Kit
VAX/VMS software for the VAX 8200 is distributed on an RA60 disk.
The VAX 8200 RA60 software distribution kit contains the following:
•

The RA60 Version 4.4 distribution disk. The asterisk (*) denotes the
latest version.
Part number: BD-BT09*-BE
Part description: VAX/VMS V4.4 BIN RA60

•

The VAX/VMS Version 4.4 mandatory update diskette. The asterisk (*)
denotes the latest version.
Part number: BLHC59*-BE
Part description: VAX/VMS V4.4 BIN RX50 MANDATORY UPDATE

•

Four floppy diskettes containing standalone BACKUP. The asterisk (*)
denotes the latest version.
Part number: BLHC51*-BE
Part description: VAX/VMS V4.4 S/A BKUP RX50 1/3
Part number: BLHC52*-BE
Part description: VAX/VMS V4.4 S/A BKUP RX50 2/3
Part number: BLHC53*-BE
Part description: VAX/VMS V4.4 S/A BKUP RX50 3/3

In addition to the media and other materials in the software distribution kit,
you will need a console floppy before you can install or upgrade a VAX/VMS
system. If you are installing a new system, the console floppy was shipped
with the hardware. If you are upgrading an existing system, your current
console floppy will be upgraded as part of the upgrade procedure.

D.3

VAX-11/780 Distribution Kit
VAX/VMS software for the VAX-11/780 is distributed in one of three media:
•

Magnetic tape

•

RK07 disk

•

RA60 disk

In addition to the media and other materials in the software distribution kit,
you will need a console floppy before you can install or upgrade a VAX/VMS
system. If you are installing a new system, the console floppy diskette was
shipped with the hardware. If you are upgrading an existing system, your

D—2

Operating System Distribution Kits

current console floppy diskette will be upgraded as part of the upgrade
procedure.

D.3.1

Magnetic Tape Kit
The VAX-11/780 magnetic tape software distribution kit contains the
following materials:
•

The VAX/VMS Version 4.4 distribution tape. The asterisk (*) denotes
the latest version.
Part number: BB-BT05*-BE
Part description: VAX/VMS V4.4 BIN 16MT9

•

The VAX/VMS Version 4.4 mandatory update diskette. The asterisk (*)
denotes the latest version.
Part number: AS-FY81*-BE
Part description: VAX/VMS V4.4 BIN RX01 MANDATORY UPDATE

•

Four floppy diskettes containing standalone BACKUP. The asterisk (*)
denotes the latest version.
Part number: AS-CT94*-BE
Part description: VAX/VMS V4.4 S/A BKUP RX01 1/4
Part number: AS-CT95*-BE
Part description: VAX/VMS V4.4 S/A BKUP RX01 2/4
Part number: AS-CT96*-BE
Part description: VAX/VMS V4.4 S/A BKUP RX01 3/4
Part number: AS-HP49*-BE
Part description: VAX/VMS V4.4 S/A BKUP RX01 4/4

D.3.2

RK07 Kit
The VAX-11/780 RK07 software distribution kit contains the following
materials:
•

The RK07 Version 4.4 distribution disk. The asterisk (*) denotes the
latest version.
Part number: AY-BT10*-BE
Part description: VAX/VMS V4.4 BIN RK07

•

The VAX/VMS Version 4.4 mandatory update diskette. The asterisk (*)
denotes the latest version.
Part number: AS-FY81*-BE
Part description: VAX/VMS V4.4 BIN RX01 MANDATORY UPDATE

D—3

Operating System Distribution Kits

D.3.3

RA60 Kit
The VAX-11/780 RA60 software distribution kit contains the following:
•

The RA60 Version 4.4 distribution disk. The asterisk (*) denotes the
latest version.
Part number: BD-BT09*-BE
Part description: VAX/VMS V4.4 BIN RA60

•

The VAX/VMS Version 4.4 mandatory update diskette. The asterisk (*)
denotes the latest version.
Part number: AS-FY81*-BE
Part description: VAX/VMS V4.4 BIN RX01 MANDATORY UPDATE

D.4

VAX-11/750 Distribution Kit
VAX/VMS software for the VAX-11/750 is distributed in one of four kits:
•

Magnetic tape

•

RK07 disk

•

RA60 disk

•

RL02 disks

The contents of each kit are listed in a bill of materials that accompanies each
kit.
In addition to the media and other materials in the software distribution
kit, you will need a console TU58 cartridge before you can proceed with an
installation or an upgrade. If you are installing a newly purchased system,
the console TU58 cartridge was shipped with the hardware. If you are
upgrading an existing sytem, your current console TU58 cartridge will be
upgraded as part of the VAX/VMS upgrade procedure.

D—4

Operating System Distribution Kits

D.4.1

Magnetic Tape Kit
The VAX-11/750 magnetic tape software distribution kit contains the
following materials:
•

The VAX/VMS Version 4.4 distribution tape. The asterisk (*) denotes
the latest version.
Part number: BB-BT05*-BE
Part description: VAX/VMS V4.4 BIN 16MT9

•

Four TU58 cartridges that contain standalone BACKUP for installing your
system. The asterisk (*) denotes the latest version.
Part number: BE-CT97*-BE
Part description: VAX/VMS V4.4 S/A BKUP T58 1/4
Part number: BE-CT98*-BE
Part description: VAX/VMS V4.4 S/A BKUP T58 2/4
Part number: BE-CT99*-BE
Part description: VAX/VMS V4.4 S/A BKUP T58 3/4
Part number: BE-GZ53*-BE
Part description: VAX/VMS V4.4 S/A BKUP T58 4/4

•

One TU58 cartridge that contains the mandatory update. The asterisk
(*) denotes the latest version.
Part number: BE-FY82*-BE
Part description: VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE

D.4.2

RK07 Kit
The VAX-11/750 RK07 software distribution kit contains the following
materials:
•

The RK07 Version 4.4 distribution disk. The asterisk (*) denotes the
latest version.
Part number: AY-BT10*-BE
Part description: VAX/VMS V4.4 BIN RK07

•

One TU58 cartridge that contains the mandatory update. The asterisk
(*) denotes the latest version.
Part number: BE-FY82*-BE
Part description: VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE

D—5

Operating System Distribution Kits

D.4.3

RA60 Kit
The VAX-11/750 RA60 software distribution kit contains the following
materials:
•

The RA60 Version 4.0 distribution disk. The asterisk (*) denotes the
latest version.
Part number: BD-BT09*-BE
Part description: VAX/VMS V4.4 BIN RA60

•

One TU58 cartridge that contains the mandatory update. The asterisk
(*) denotes the latest version.
Part number: BE-FY82*-BE
Part description: VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE

D.4.4

RL02 Kit
If you have an an RL02/RA80 system configuration, the operating system is
distributed on an RL02 kit that include three disks.
The first disk contains the required save set, which includes all the files you
need to build a bootable system. The second distribution disk contains the
library save set that includes the rest of the operating system files. The third
disk contains the optional files save set, which includes additional pieces of
the VAX/VMS operating system; VAX BLISS files, programming examples
and the system map.
•

The VAX/VMS Version 4.4 Required #1 distribution disk. The asterisk
(*) denotes the latest version.
Part number: BC-BT06*-BE
Part description: VAX/VMS V4.4 REQUIRED RL2 #1

•

The VAX/VMS Version 4.4 Required #2 distribution disk. The asterisk
(*) denotes the latest version.
Part number: BC-BT07*-BE
Part description: VAX/VMS V4.0 REQUIRED RL2 #2

•

The VAX/VMS Version 4.4 Required #3 distribution disk. The asterisk
( * ) denotes the latest version.
Part number: BC-HP50*-BE
Part description: VAX/VMS V4.0 REQUIRED RL2 #3

•

One TU58 cartridge that contains the mandatory update. The asterisk
(*) denotes the latest version.
Part number: BE-FY82*-BE

D—6

Operating System Distribution Kits

Part description: VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE

D.5

VAX-11 /730 Distribution Kits
VAX-11/730 software is distributed on three different kits. One of the kits,
the RL02 kit, is used to distribute the operating system to users who have
IDC-based VAX-11/730 systems.
The other two kits, magnetic tape and RA60 disk, are used to distribute the
operating system to users who have UDA-based VAX-11/730 systems.

D.5.1

RL02 Distribution Kit
This kit includes three disks. The first disk contains the required save set,
which includes all the files you need to build a bootable system. The second
distribution disk contains the library save set that includes the rest of the
operating system files. The third disk contains the optional files save set,
which includes additional pieces of the VAX/VMS operating system; VAX
BLISS files, programming examples and the system map.
•

The VAX/VMS Version 4.4 Required #1 distribution disk. The asterisk
(*) denotes the latest version.
Part number: BC-BT06*-BE
Part description: VAX/VMS V4.4 REQUIRED RL2 #1

•

The VAX/VMS Version 4.4 Required #2 distribution disk. The asterisk
(*) denotes the latest version.
Part number: BC-BT07*-BE
Part description: VAX/VMS V4.4 REQUIRED RL2 #2

•

The VAX/VMS Version 4.4 Required #3 distribution disk. The asterisk
( * ) denotes the latest version.
Part number: BC-HP50-BE
Part description: VAX/VMS V4.4 REQUIRED RL2 #2

•

One TU58 cartridge that contains the mandatory update. The asterisk
(*) denotes the latest version.
Part number: BE-FY82*-BE
Part description: VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE

D—7

Operating System Distribution Kits

D.5.2

Magnetic Tape Distribution Kit
The magnetic tape distribution kit contains the following materials:
•

The VAX/VMS Version 4.4 distribution tape. The asterisk (*) denotes
the latest version.
Part number: BB-BT05*-BE
Part description: VAX/VMS V4.4 BIN 16MT9

•

One TU58 cartridge that contains the mandatory update. The asterisk
(*) denotes the latest version.
Part number: BE-FY82*-BE
Part description: VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE

D.5.3

RA60 Kit
The RA60 distribution kit contains the following materials:
•

The RA60 Version 4.4 distribution disk. The asterisk (*) denotes the
latest version.
Part number: BD-BT09*-BE
Part description: VAX/VMS V4.4 BIN RA60

•

One TU58 cartridge that contains the mandatory update. The asterisk
(*) denotes the latest version.
Part number: BE-FY82*-BE
Part description: VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE

D—8

Operating System Distribution Kits

D.6

VAX-11/725 Distribution Kit
The VAX-11/725 software distribution kit contains the following materials:
•

The RC25 Version 4.4 distribution disk cartridge. The asterisk (*)
denotes the latest version.
Part number: BK-BT11*-BE
Part description: VAX/VMS V4.4 BIN RC25

•

One TU58 cartridge that contains the mandatory update. The asterisk
(*) denotes the latest version.
Part number: BE-FY82*-BE
Part description: VAX/VMS V4.4 BIN TU58 MANDATORY UPDATE

D—9

Index
A
Aborting UETP execution • 7-16, 7-17
Alternate root*4-39
creating on common system disk *6-20
specification format *5-4
VMSINSTAL option
restriction *5-10
Alternate system root
VMSINSTAL option* 5-10
Answer file* 5-7
Area selection
DECnet-VAX option *6-8
AST limit (ASTLM)*5-2
Authorize Utility (AUTHORIZE)
MODIFY SYSTEM command *5-3
SHOW SYSTEM command *5-2
to check UAF limits *5-2
Auto-answer
VMSINSTAL option *5-7
AUTOGEN.PAR
creation of • 6-17
Automatic shutdown *5-6
AUTO RESTART/BOOT switch *2-14
installation setting *2-15
operational setting *2-15
AUTO RESTART switch *2-9

B
Backup
dual-RL02 • 4-28
R80/RL02 • 4-26
RC25 • 4-29, 4-31
regular or standalone • 4-19
use during installation • 4-18
Backup of system disk
VAX-1 1/730*4-26, 4-28
VAX-1 1/750*4-24
VAX-1 1/780*4-22
VAX 8600*4-19

Bad Block Locator Utility (BAD)
to check new console volume
Battery backup *2-14
Block storage
use during installation • 4-1 1
VAX-1 1/730*2-24
VAX-1 1/750*2-24
VAX-1 1/780*2-18
VAX 8600/8650*2-16
BOOT58 • 2-24
use in booting a VAX 8200*4
use in booting VAX-1 1 /750•
BOOT/NOSTART command *2-2
BOOT command *2-2
Boot command procedure
creating *4-40
editing *4-6, 4-9
naming convention • 4-40
BOOT DEVICE switch *2-11, 2-2
setting for booting VAX-1 1 /7
upgrade* 6-4
Booting
during installation • 4-2
from HSC disk *4-4
VAX-1 1/750
from disk*4-2
using BOOT58*4-3
using BOOT DEVICE switc
VAX 8200
using BOOT58*4-3
VAX 8200 or VAX-1 1/750 •
Boot name *4-4
short form • 4-4
VAX-1 1/750*4-15
VAX-1 1/785*4-14
Boot procedure
name code *4-4
Bootstrapping
See Booting
BOOT switch *2-9

Index

Buffered byte count quota limit (BYTLM)*
5-2
Buffered I/O limit (BIOLM) • 5-2

c
Cl (computer interconnect)
environment for upgrading • 6-7
Cluster
common system disk*6-7
Code
controller* 4-12
device* 7-6, 7-32
device type *4-12
unit address *4-12
user identification (UIC) • 7-6
Command procedure • 7-35
copying *4-6, 4-9
master* 7-30, 7-41
STABACKIT *4-33, 4-36, 4-38
to boot standalone BACKUP *4-40
Common system disk
on cluster*6-7
Connect console volume
how to • 4-6, 4-9
Console commands
BOOT *2-2
BOOT *2-2
BOOT/NOSTART *2-2
DEPOSIT *2-2
DEPOSIT *2-2
HALT *2-2
START *2-2
used during installation • 2-2
Console dialog*7-3, 7-12, 7-15, 7-16
Console floppy
inserting *2-18
Console mode
console subsystem • 2-2
entering • 2-2, 4-2
Console prompt *2-2, 4-2
Console report *7-12
error message • 7-15, 7-18, 7-19
format • 7-15
Console subsystem • 2-1

Index—2

Console subsystem (cont'd.)
components* 2-1
console mode *2-2
console terminal • 2-1
program mode *2-1
VAX 8200 processor
processor control panel *2-6
Console terminal
console subsystem • 2-1
Console volume
building new site-specific • 6-9, 6-12
build to boot from SYSF*6-9, 6-12
Controller *7-31, 7-32
code *4-12
designation • 7-32
phase
See UETPHAS00.EXE
Counters*7-38, 7-39
Creating alternate roots on a common
system disk*6-20
CTRL/C *7-16, 7-17
CTRL/Y *7-16, 7-17

D
DECnet* 7-1, 7-36, 7-37
failure* 7-28
DECnet-VAX
area selection option *6-8
how to shut down • 5-2
license requirement for upgrade *6-7
shutting down for upgrade *6-5
Decompressing library files
space requirement *6-19
Decompression of library
using LIBDECOMP.COM • 6-18
DEFBOO.CMD
setting up for HSC boot *4-6, 4-9
use in creating boot command procedure*
4-40
DEFBOO.COM
setting up for HSC boot *4-6
DEPOSIT command *2-2
Detached process • 7-15, 7-21, 7-31, 7-32,
7-35, 7-38

Index

Device code *4-12, 7-6, 7-32
format • 6-6
VAX-1 1/725 systems • 4-18
VAX-11/730 systems *4-18
VAX-11/750 systems*4-17
VAX-1 1/780 systems *4-16
VAX 8200 systems *4-16
VAX 8600 systems *4-15
Device name
examples *4-13
for installing software *4-11
format *4-11
in bootstrap operations • 4-13
Devices
VAX-1 1/725 systems *4-18
Device test
See Test, device
Device type code *4-12
Diagnostics* 7-18
Direct I/O limit (DIOLM)*5-2
DIRECTORY command
for VMSINSTAL product list *5-6
Disk
initializing • 7-6
preparing for test* 7-2, 7-5, 7-6
scratch • 7-4, 7-6
system *7-4, 7-19
test of • 7-35
error* 7-20, 7-23, 7-24
test image name *7-35
Disk cartridges
loading and unloading • 3-16
Disk controller* 7-32
Disk device
how to specify *4-3
Diskette
inserting into VAX 8200 block storage
device *2-16
Disk packs
loading and unloading • 3-18
Disk space *7-2, 7-5, 7-24
requirements for upgrade *6-4
Dual-RL02
backup *4-28

E
Enqueue quota limit (ENQLM)*5-2
ERRLOG.SYS • 7-28
Error logging
See Log file
Error Log Utility *7-3, 7-18
Error message • 7-15, 7-18, 7-19
bugcheck* 7-30
DECnet • 7-28
disk test* 7-24
issued by VMSINSTAL*5-13
no PCB or swap slots *7-29
OPCOM • 7-23
UETDISK00 • 7-24
UETINIT01 *7-23
wrong account *7-22
wrong privileges • 7-21
wrong quotas* 7-21
EXCHANGE utility
for copying command procedure • 4-9
Exchange Utility (EXCHANGE)
for copying command procedure • 4-6
Executable image
device test • 7-35
UETINIT00.EXE* 7-13, 7-14, 7-31
UETINIT01.EXE *7-20, 7-23, 7-31
UETPHAS00.EXE *7-31, 7-32

F
Failure to reboot
how to handle *6-11
File log
VMSINSTAL option • 5-7
File log option
VMSINSTAL *5-8

G
GET save set option
VMSINSTAL *5-7

Index—3

Installing standalone BACKUP (cont'd.)

alternate disk directory root *4-40

HALT command *2-2
Handling disk media *3-16
Hang
See System hang
HSC50 controller • 3-31
HSC70 controller • 3-31
HSC boot setup*4-6, 4-9
HSC device name *6-7
HSC Operator Control Panel (OCP)
controls and indicators • 3-31

i
I/O bus *7-34
I/O device failure *7-30
I/O privileges, quotas, limits *7-21
Image, executable
See Executable image
Indicator lights
ALERT *2-3
REMOTE ACTIVE *2-3
REMOTE ENABLE *2-3
VAX-1 1/725,VAX-1 1/730*2-14
VAX-11/750*2-10
VAX-1 1/780*2-9
VAX STATE *2-3
Initialization
of disk • 7-6
of magnetic tape • 7-6
Initialization phase*7-7, 7-31
INIT switch
See RESET switch
Installation
in tailored environment • 5-1 1
kinds of* 1-1
overview* 1-1
scenarios* 1-1
Installation summary
newly purchased system* 1-2
system upgrade* 1-3
update/optional product* 1-3
Installing standalone BACKUP

Index—4

K
Keylock switch
VAX-11/725,VAX-11/730*2-15
VAX-1 1/750*2-12
VAX-1 1/780*2-9

L
LED activity indicators • 2-25
Library
using LIBDECOMP.COM to decompress*
6-18
Library disk
requirement in tailored configuration • 5-3
Line printer
preparing for test *7-3, 7-7
test of • 7-31
test image name *7-35
test output • 7-34
Load device *3-1, 4-11
VAX-11/730 systems *4-18
VAX-11/750 systems *4-17
VAX-11/780 systems *4-17
VAX 8600 systems *4-15, 4-16
Loading and unloading
disk cartridges*3-16
disk packs *3-18
Load test *7-15, 7-35
defining user load* 7-13, 7-15
failure* 7-27
running *7-16
Log file *7-5, 7-18
See also UETP.LOG
load test • 7-27
NETSERVER.LOG • 7-26
OLDUETP.LOG *7-19
UETP.LOG *7-19
Logical name
CTRLNAME • 7-33
LOADS *7-36
MODE *7-13, 7-15

Logical name (cont'd.)

Newly purchased system (cont'd.)

SYSSlNPUT • 7-32
SYSSOUTPUT • 7-34
SYSSTEST • 7-4, 7-19, 7-32
Log in
as system manager*4-1
for UETP testing *7-2, 7-4
Long report format

installation summary* 1-2
Node naming
for dual-ported disks*4-7, 4-1
Node number
for HSC boot
how to specify *4-4

See Console dialog. Console report

M
Magnetic tape
initializing • 7-6
preparing for test *7-2, 7-6
test of *7-31, 7-34
test image name *7-35
Magnetic tape kit*D-8
MAKEROOT
how to invoke *6-20
requirements to execute *6-20
use in creating alternate roots *6-20
Master command procedure
See UETP.COM
Message
See also Error message
informational *7-17
status* 7-18
MicroVAX installation
reference to*ix
MODIFY SYSTEM command
use of • 5-3
MOUNTMSG/DISMOUMSG parameters
effect on product installation • 5-2

N
Name code
boot procedure *4-4
Naming devices *4-1 1
Network Control Program (NCP)
command to shut off DECnet*5-2
invoking • 5-2
Newly purchased system

OLDUETP.LOG • 7-19
OPCOM message *7-23
during product installation • 5-2
Open file quota (FILLM)*5-2
Operating instructions
summary* 7-2
Operating modes
console subsystem • 2-1
OPTIONS keyword *5-4
Output • 7-1
console report *7-12, 7-15, 7interpreting* 7-18
terminal and line printer *7-34
UETP.LOG • 7-15
Overview of installation* 1-1

Page file size
use in making alternate root *6
Password • 7-4
Peripheral devices
list of • 3-1
Phase
cluster* 7-16
DECnet *7-16, 7-20, 7-28, 7-3
device *7-16, 7-31
initialization • 7-31
load *7-16, 7-35
running individual • 7-16
Phase controller
See UETPHAS00.EXE
POWER ON ACTION switch *2-1
Preparing a tailored system for UE
Preparing devices *7-5

Preparing devices (cont'd.)

RA60, RA80, RA81 (cont'd.)

disk *7-2, 7-5
line printer* 7-3, 7-7
magnetic tape *7-2, 7-6
summary* 7-2
terminal • 7-3, 7-7
VAXcluster • 7-9
Privilege* 7-4, 7-20
error message • 7-21
for running UETP*7-21
Processor control panel *2-3
VAX-1 1/730,VAX-11/725*2-13
VAX-11/750*2-10
VAX-1 1/780*2-8
VAX 8200 processor *2-6
keylock switches *2-6
Restart push button *2-8
status lights *2-7
Product installation
preparation • 5-1
Product list
VMSINSTAL parameter* 5-3
syntax* 5-5
Program mode
console subsystem • 2-1

disk drive *3-13
RC25 backup
fixed system disk *4-29
removable system disk *4-31
RC25 controls and indicators*3-15
RC25 distribution kit
contents* D-9
Rebooting
from BOOT58 level *6-14
to restart upgrade *6-11, 6-14
Release notes option
VMSINSTAL *5-9
Removing files after upgrade
instructions for *6-19
RESET switch *2-12
Restart
on VAX-11/730*6-11
switch positions*6-4
Restart control switch *2-4
Restoring LIBRARY and OPTIONAL save set
variations *6-15
Revised files
handling during product installation • 5-13
RK07
controls and indicators • 3-3
disk drive *3-3
RL02
as block storage device *2-16
controls and indicators • 3-2
disk drive*3-2
RM03, RM05
controls and indicators • 3-9
disk drive*3-9
RP05, RP06
controls and indicators • 3-5
disk drive *3-5
RP07
controls and indicators • 3-8
disk drive*3-8

Q
Question mark (?)
to get help from VMSINSTAL* 5-6
Queues
during upgrade *6-5
Quota • 7-20
error message • 7-21
for running UETP*7-21

R
R80, RM80
controls and indicators • 3-12
disk drive *3-11
R80/RL02
backup • 4-26
RA60, RA80, RA81
controls and indicators *3-13

Index—6

s
Short report format
See Console dialog. Console report

Index

SHOW SYSTEM command
use of • 5-2
SHUTDOWN.COM command procedure• C-2
Small-disk systems *5-11
installing optional products on *5-12
list of 5-11
space problems*5-12
Software installation booklets
brief desription of* 1-2
Source parameter
for VMSINSTAL • 5-4
Space requirement
for decompressing library files *6-19
Space shortage
what to do *5-12
STABACKIT command procedure • 4-33,
4-36, 4-38, 4-40
Standalone BACKUP
booting from alternate root SYSE*4-40,
4-42
booting from disk *4-42
building
on console media *4-33
building
on an RL02 disk *4-38
on floppy diskettes *4-33, 4-36
on TU58 tape cartridges • 4-33
using on disk *4-39
START command *2-2
Summary
installation of system upgrade* 1-3
installation on newly purchased system*
1-2

installation update/optional product* 1-3
Swap file size
use in making alternate root *6-21
Switch
AUTO RESTART *2-9
AUTO RESTART/BOOT *2-14
BOOT *2-9
BOOT DEVICE *2-1 1
BOOT DEVICE *2-24
keylock
VAX-1 1/725,VAX-1 1/730*2-15
VAX-11/780*2-9

Switch (cont'd.)
keylock
VAX-1 1/750*2-12
POWER ON ACTION *2-1 1
RESET *2-12
restart control • 2-4
terminal control *2-4
SYS$INPUT • 7-32
S YS$M AN AGER: VMSIMAGES.DAT
use in deleting redundant files *6-20
SYS$OUTPUT • 7-34
SYS$TEST • 7-4, 7-19, 7-32
SYSE
booting standalone BACKUP from *4-40,
4-42
System
bootstrapping
See Booting
logging in to • 7-2
SYSTEM account
required limits • 5-2
System device *3-1,4-11
VAX-11/730 systems *4-18
System disk backup
purpose of • 5-1
System failure
effect on working copy *5-1
VMSINSTAL response to *5-10
System Generation Utility (SYSGEN)
how to invoke *4-6, 4-9
System hang *7-20, 7-30
System resources • 7-2, 7-15, 7-35
System security
password change requirement • 6-9, 6-12
System shutdown procedure • 4-42
System upgrade
installation summary* 1-3
[SYSTEST] directory *7-4, 7-6, 7-17
SYSTEST_CLIG account *7-9
SYSTEST account *7-2, 7-4, 7-20, 7-21,
7-22, 7-32

T
Tailored system

Index—7

Tailored system (cont'd.)
installation • 5-1 1
preparing for UETP*7-10
TE16
controls and indicators • 3-23
tape drive *3-23
Terminal
console* 7-4
controller* 7-32
hardcopy • 7-15
output *7-15, 7-18, 7-32
preparing for test* 7-3, 7-7, 7-13
simulated users *7-35
test of* 7-9, 7-31, 7-32
test image name *7-35
test output • 7-34
Terminal control switch *2-4
Test
DECnet • 7-37
device *7-24, 7-32, 7-34, 7-36
disk *7-31, 7-35
line printer* 7-31, 7-34, 7-35
load *7-35
magnetic tape *7-2, 7-6, 7-31, 7-34,
7-35
running individual • 7-18, 7-24, 7-32
VAXcluster integration • 7-9, 7-25
Transmit message buffer *7-34
TS1 1
controls and indicators*3-22
tape drive*3-22
TU58
insertion • 2-21
locations
VAX-1 1/725*2-26
VAX-1 1/730*2-25
locations
VAX-1 1/730*2-25
TU77
controls and indicators • 3-25
tape drive*3-25
TU78
controls and indicators • 3-27
tape drive*3-27
TU80, TU81
controls and indicators • 3-29

Index—8

TU80, TU81 (cont'd.)
tape drive*3-29

ir
UAF limits
how to check*5-2
UETCONTOO.DAT *7-31, 7-32
UETDNET00.DAT • 7-37
UETINIDEV.DAT *7-31, 7-32, 7-33
format • 7-33
UETININET.DAT• 7-37, 7-38
UETINIT00.EXE *7-13, 7-14, 7-31
UETINIT01.EXE *7-20, 7-31
failure* 7-23
UETLOADOO.DAT • 7-35
UETNETS00.EXE • 7-38
UETP (User Environment Test Package)
interpreting output of *7-18
organization of *7-30
password*7-2, 7-4
preparing a tailored system *7-10
role of *7-1
running entire*7-3
running multiple passes*7-5, 7-13, 7-15,
7-19, 7-24, 7-41
termination • 7-41
test variables* 7-31
defining *7-12
typical failures reported by *7-20
username* 7-2
what it tests*7-1
UETP.COM *7-31, 7-32, 7-41
UETP.LOG *7-15, 7-19, 7-28, 7-36
UETPHAS00.EXE *7-31, 7-32, 7-37
Unit address
assigning *4-12
code *4-12
for HSC boot
how to specify *4-4
Update/optional product
installation summary* 1-3
Upgrade
materials needed *6-1
notes • 6-2

VAX-1 1/780 (cont'd.)
phase 1
VAX-1 1/725, VAX-1 1/730, VAX11/780 and VAX 8600 Systems
•6-9
VAX-11/750 and VAX 8200*6-12
phase 2*6-15
phase 3*6-16
phase 4*6-16
phase 5*6-17
preparation for *6-2
preparation procedure • 6-3
restriction • 6-2
User identification code *7-6
User load
defined for DECnet test *7-38
defining • 7-3, 7-13, 7-14
dialog example *7-13

v
VAX-11/725
TU58 locations • 2-26
VAX-1 1/725,VAX-1 1/730
indicator lights *2-14
keylock switch *2-15
processor control panel *2-13
VAX-1 1/725 backup
fixed system disk *4-29
removable system disk *4-31
VAX-11/730
backup of system disk *4-26, 4-28
TU58 locations • 2-25
VAX-1 1/730 software distribution kit
RA60 kit • D-8
VAX-1 1/750
boot names *4-15
indicator lights *2-10
keylock switch *2-12
processor control panel *2-10
VAX-1 1/750 software distribution kit
magnetic tape kit*D-5
RA60 kit • D-6
RK07 kit • D-5
VAX-1 1/780

indicator lights • 2-9
keylock switch *2-9
processor control panel *2-8
VAX-11/785
boot names *4-14
VAX 8600/8650
console subsystem *2-16
indicator lights *2-3
processor control panel *2-3
restart control switch *2-4
terminal control switch *2-4
VAXcluster
preparing for UETP*7-9
test failure • 7-25
VAX/VMS software distribution k
magnetic tape kit • D-1, D-3
RA60 kit* D-2, D-4
RK07 kit* D-3
VAX/VMS source kit
contents of • B-1
VMSINSTAL
action at installation completio
alternate root option
restriction *5-10
alternate system root option *5
answer file* 5-7
specification format *5-7
auto-answer option • 5-7
command line syntax *5-3
destination
for installing product *5-4
error messages *5-13
File log option • 5-8
file log option • 5-7
GET option
use of to store product sa
GET save set option *5-7
how to invoke *5-3
how used • 5-1
invoking for upgrade *6-6
manual recovery from system
5-10
options
auto-answer • 5-7
defined • 5-7

Index

VMSINSTAL
options (cont'd.)
how specified • 5-7
keyword • 5-4
listed • 5-6
option list* 5-4
options
file log • 5-7
GET save set • 5-7
parameters
product list* 5-3
source • 5-4
product save set format *5-8
recovery from system failure
standard system *5-10
tailored system *5-10
Release notes option *5-9
small-disk installation considerations*
5-11
storing product save sets using GET
option • 5-8
system failure
conditions *5-10
recovery • 5-10
VMSINSTAL.COM
See VMSINSTAL
VMSUPDATE • 5-1
summary • C-1
VMSUPDATE product installation
completion • C-3
interactive requirement • C-1
preparing for • C-1
procedure *C-2
setting default disk*C-2

w
Working copy
description • 5-1

Index—10

AI-Y5

READER'S
COMMENTS

Note: This form is for document comments only.
DIGITAL will use comments submitted on this form
the company's discretion. If you require a written
and are eligible to receive one under Software Perf
Report (SPR) service, submit your comments on an
form.

Did you find this manual understandable, usable, and well organized? Please
suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page num

Please indicate the type of user/reader that you most nearly represent:
□
□
□
□
□
□

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify) _

Name _Date_
Organization _
Street _
City _State_Zip Code .
or Country

iDQSD

United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

I,...I.II.I.,1,1.,1.1.,11.Ml
Do Not Tear - Fold Here

AI-Y5

READER'S
COMMENTS

Note: This form is for document comments only
DIGITAL will use comments submitted on this for
the company's discretion. If you require a written
and are eligible to receive one under Software Per
Report (SPR) service, submit your comments on a
form.

Did you find this manual understandable, usable, and well organized? Pleas
suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page num

Please indicate the type of user/reader that you most nearly represent:
□
□
□
□
□
□

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify) _

Name _Date_

Organization _

Street _

City _State_Zip Code
or Country

Iddsd

United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

1.11111 m 111111 n 11111111111111111111.1,11

Do Not Tear - Fold Here