Digital PDFs

AA-K410C-TE

December 1982

99 pages

Original

4.0MB

Document:	VAX-11/750 Software Installation Guide
Order Number:	AA-K410C-TE
Revision:	000
Pages:	99
Original Filename:

OCR Text

VAX-11/750
Software Installation Guide
Order No. AA-K41 OC-TE

December 1982
This document contains detailed instructions for installing, upgrading, and
updating the VAX/VMS operating system on a VAX-11 /750 processor.

REVISION/UPDATE INFORMATION:

This revised document supersedes
the VAX-11 /750 Software
Installation Guide (Order No.
AA-K41 OB-TE) and Update Notice
No. 1 (Order No. AD-K410B-T1 ).

SOFTWARE VERSION:

VAX/VMS Version 3.2

digital equipment corporation . maynard, massachusetts

First Printing, September
Revised, May
Updated, August
Revised, December

1980
1982
1982
1982

The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation.
Digital Equipment Corporation assumes no
responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a
license
and may be used or copied only in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by Digital Equipment Corporation or its
affiliated companies.

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
DECnet
DECsystem-10
DECSYSTEM-20
DEC US
DECwriter
DIBOL

EduSystem
!AS
MASS BUS
PDP
PDT
RSTS

RSX
UNIBUS
VAX
VMS
VT

~omoomo
ZK2354

HOW TO ORDER ADDITIONAL DOCUMENTATION
In Continental USA and Puerto Rico call

800-258-1710

In New Hampshire. Alaska, and Hawaii call
In Canada call

603-884-6660

613-234-7726 (Ottawa-Hull)
800-267-6146 (all other Canadian)

DIRECT MAIL ORDERS (USA & PUERTO RICO)*
Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (CANADA)
Digital Equipment of Canada Ltd.
940 Belfast Road
Ottawa, Ontario K1G 4C2
Attn: A&SG Business Manager

DIRECT MAIL ORDERS (INTERNATIONAL)
Digital Equipment Corporation
A&SG Business Manager
c!o Digital's local subsidiary or
approved distributor

*Any prepaid order from Puerto Rico must be placed
with the local Digital subsidiary (809-754-7575)
Internal orders should be placed througr the Software Dis~r'bu:'on Cer:ter {SOC). Digital Eoui:J,"lent
Corporation. Northboro, Massachusetts 01532

CONTENTS

Page
PREFACE

vii

SUMMARY OF TECHNICAL CHANGES

CHAPTER 1
1.1
1.2
1. 2 .1
1. 2. 2
1.2. 3
1. 2. 4
1.2. 5
1. 3
CHAPTER 2

OVERVIEW OF SOFTWARE INSTALLATION
VAX-11/750 CONSOLE SUBSYSTEM
• • • • • • • • 1-1
VAX-11/750 PROCESSOR CONTRQL PANEL •
1-2
Indicator Lights • • •
• • 1-2
POWER-ON-ACTION Switch •
• • • • 1-3
BOOT DEVICE Switch • •
• • • . . • • 1-4
INITIALIZE Button
• • • 1-4
Keylock Rotary Switch
• 1-4
OVERVIEW OF SYSTEM INSTALLATION
• • • • • • • 1-5
BUILDING A BOOTABLE SYSTEM DISK

2.1
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.4.1
2.2.4.2
2.3
2.4
2.4.1
2.4.2

OVERVIEW OF BUILDING A BOOTABLE SYSTEM DISK
2-1
VAX/VMS SOFTWARE DISTRIBUTION KITS
• • 2-2
Magnetic Tape Kit
• • • •
• 2-2
RK07 Kit • • • • • • • • • • • • •
• • 2-3
RA60 Kit • • • • • • • • • • • • •
• • • • 2-3
RL02 Kit • • • • • • • • • • • • •
•
2-3
The Primary Software Distribution Disk • • • • 2-4
The Optional Software Distribution Disk
• • • 2-4
SPECIFYING DEVICE NAMES
• • • • • • • • • • • • • 2-4
POWERING UP THE SYSTEM • • • • • • • • • • • • • • 2-5
Checking the Switches and Panel Indicators
• 2-5
Checking for the Attention of the Console
Program • • • • • • • • • •
• • • • • • • • 2-6
RESTORING THE DISTRIBUTION KIT • • • • •
• • 2-6
2.5
Loading Stand-alone BACKUP • • • • • •
• • 2-6
2.5.1
Loading Stand-alone BACKUP from Disk
2-6
2.5.1.1
Loading Stand-alone BACKUP from TU58 Cartridge 2-7
2.5.1.2
Restoring the Required Save Set to the Target
2.5.2
Device . . . . . . . . . . . . . . . . . . . . . 2-7
BOOTING THE TARGET DEVICE AND RESTORING THE REST
2.6
OF VMS • • • • • • • • •
• • • • • • • • 2-8
2.6.1
Restoring the Optional Kit on an RL02/RA80
Configuration
• • • •
• • • • •
2-10
CHAPTER 3
3.1
3 .. 2

3.3
3.4
3.5

SITE-SPECIFIC MODIFICATIONS TO VAX/VMS
LOGGING IN TO THE SYSTEM • •
SITE-SPECIFIC MODIFICATIONS
SYSTEM SHUTDOWN AND REBOOT •
MODIFYING SYSTEM PARAMETERS
VAX/VMS USER ENVIRONMENT TEST PACKAGE

iii

• • •
• • •
•
•
•

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

CONTENTS
Page
3.6
3.7
CHAPTER 4
4.1
4.2
4.3
4.4
4.5
4.6
CHAPTER 5
5.1
5 .1.1
5 .1.2
5.2
5.2.1
5.2.2
5.2.3
5.3
5.3.1
5.3.2
5.4

THE VMSINSTAL COMMAND PROCEDURE
EXAMINING THE DISTRIBUTION KITS
PREPARING TO USE VMSINSTAL • •
INVOKING VMSINSTAL • • • •
CHOOSING VMSINSTAL OPTIONS
RECOVERING FROM SYSTEM FAILURE •
INSTALLING EDTCAI
• • . • • .

APPENDIX B

USING THE TU58 TAPE CARTRIDGE

B.5
B.6

4-1
4-1
4-3
4-4
4-6
• 4-6

WHEN TO BOOTSTRAP FROM THE TU58 TAPE CARTRIDGE • •
BOOTSTRAPPING THE SYSTEM USING STAND-ALONE BOOT58
Conversational Bootstrap Using Stand-Alone
BOOT58 • • • • • • • • • • • • • • • • • • • • •
Nonstop Bootstrap Using Stand-Alone BOOT58 • • •
THE DEFAULT BOOTSTRAP COMMAND PROCEDURE
• •
REBOOTING USING THE DEFAULT BOOTSTRAP COMMAND
PROCEDURE
• • • •
• • • • • • • • • • •
COPYING FILES TO OR FROM THE CONSOLE TU58 TAPE
CARTRIDGE
• • • .
• • • • •
WRITEBOOT UTILITY
• • • • • • • • • • •

APPENDIX C

BOOT58 COMMANDS

APPENDIX D

MICRO VERIFY ERROR CHARACTERS

APPENDIX E

INSTALLING OPTIONAL SOFTWARE PRODUCTS

E.l
E.2
E.3
E.4

•
•
•
•

BACKING UP THE CONSOLE MEDIUM
• • • . • • • • . •
Restoring Files to TU58 Cartridge
•••••••
Reading Command Procedures From Console Media
•
BOOTING THE SYSTEM AFTER INSTALLATION
• •
Rebooting Stopping in SYSBOOT
• • • . •
.
Nonstop Bootstrap from the System Disk • •
•
Rebooting Using the Default Bootstrap
•
BUILDING AND COPYING A VAX/VMS SYSTEM DISK • • • •
Building a VAX/VMS System Disk •
Copying a VAX/VMS System Disk
•
BUILDING A STAND-ALONE BACKUP KIT
• • • • •
FILES OF THE VAX/VMS SYSTEM

B.2.2
B.3
B.4

•
•
• •
•

THE SYSTEM AFTER INSTALLATION

APPENDIX A

B.l
B.2
B.2.1

BACKING UP YOUR SYSTEM DISK TO A SCRATCH DISK OR
TAPE • • •
• . • • • • • • • . • .
. • 3-3
THE SYSTEM AFTER INSTALLATION
• • • • • • • • • • 3-4

DISTRIBUTION KITS
• • • • •
PREPARATIONS FOR AN OPTIONAL
INSTALLING OPTIONAL SOFTWARE
INSTALLATION COMPLETION

• • • • • • • • • • •
SOFTWARE INSTALLATION
PRODUCTS
•
• • • • • • • • • • •

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

B-1
B-1
B-3
B-4
B-6
B-6
B-6
B-7

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

CONTENTS
Page
APPENDIX F

BUILDING THE VAX/VMS SOURCE KIT

APPENDIX G

UPGRADING THE SYSTEM

G.l
G.2
G.3
G.3.1
G.3.2
G.3.3
G.3.4
G.3.5
G.4
G.5
G.6
APPENDIX H

RESTARTABLE UPGRADE PROCEDURE
• • •
PREPARING TO UPGRADE THE SYSTEM • •
UPGRADING VAX/VMS
Upgrade Phase 1 • • • • . • • •
Upgrade Phase 2
Upgrade Phase 3
Upgrade Phase 4 • • • • •
Upgrade Phase 5 • • • • • • • • •
THE AUTOGEN.PAR PARAMETER FILE •
SPECIAL FILE HANDLING DURING UPGRADE
INSTALLED IMAGES • • • • • • • • • •

• • • • • • • G-1
• • • • • • • G-2
" " " " G-2
• G-3
• • • • • • G-6
• • G-6
• • G-7
• • • • • • • G-7
G-7
• • • • • • • G-8
•
• • G-8

. I.

VMSINSTAL ERROR MESSAGES

INDEX

FIGURES
FIGURE

1-1
1-2

VAX-11/750 Console Subsystem • •
• • • • • • 1-2
The VAX-11/750 Processor Control Panel •
1-3

TABLES
TABLE

2-1
5-1
A-1
A-2
A-3
A-4
A-5
A-6
A-7
A-8
B-1
D-1

..........
...........

. . 2-5
. . . . 5-5
A-2
. . . . . .. A-6
A-6
. . A-7
. . . . . . A-8

Device Type Codes
SYS BOOT Commands
Files Contained in Directory [SYSEXE]
Files Contained in Directory [ SYSHLP]
Files Contained in Directory [SYSLIB]
Files Contained in Directory [SYSMGR]
Files Contained in Directory [SYSMSG]
Files Contained in Directory [SYSTEST]
Files Contained in Directory [SYSUPD]
Files Contained in Directory [SYSHLP.EXAMPLES]
VAX/VMS Boot Command Procedures
Micro Verify Error Characters

A-8
A-12

. A-13

.....
. . B-2
. . . . . . . . . . D-1

PREFACE

MANUAL OBJECTIVES
The VAX-11/750 Software Installation Guide presents step-by-step
procedures
for
installing software on a VAX-11/750 processor.
VAX-11/750 software installation falls into three general categories:
•

Installing software on a newly purchased VAX/VMS system

•

Applying system maintenance updates to a VAX/VMS system

•

Upgrading an existing VAX/VMS system

INTENDED AUDIENCE
This manual is intended for
those users who
managing and controlling the operating system.

are

responsible

for

STRUCTURE OF THIS DOCUMENT
This manual is divided into the following chapters and appendixes:
•

Chapter 1,
Overview of
Software
Installation,
briefly
describes the process of bootstrapping and
installing a
VAX/VMS operating system and describes the VAX-11/750 console
subsystem.

•

Chapter 2, Building a Bootable System Disk, describes the
procedures for
restoring
the software distribution kit to a
bootable format.

•

Chapter 3, Site-Specific Modifications to VAX/VMS,
describes
how to make modifications to VAX/VMS so that it more closely,
fits your site's needs.

•

Chapter 4, The VMSINSTAL Command Procedure, describes how to
use VMSINSTAL.COM to
install system maintenance updates,
optional software products, and EDTCAI.

•

Chapter 5, The System After Installation, describes different
procedures that can be performed after installation.
These
include backing up the console TU58 cartridge, booting the
system after
installation,
building and copying a VAX/VMS
system disk, and building a stand-alone BACKUP kit.

•

Appendix A,
Files of the
DIGITAL-supplied directories
contents.

vii

VAX/VMS
on the

System,
lists
the
system disk and their

PREFACE
•

Appendix B, Using the TU58 Tape Cartridge, describes in detail
the steps to be taken when bootstrapping the system using the
TU58 tape cartridge as the primary bootstrap device.

•

Appendix C, BOOT58 Commands, describes the commands
be entered to the stand-alone BOOT58 program.

•

Appendix D, Micro Verify Error Characters,
describes micro
verify routines that
test
the
reliability of VAX-11/750
hardware.

•

Appendix E, Installing Optional Software Products, describes
the VMSUPDATE.COM command procedure used
to
install some
optional software products.

•

Appendix F, Building the VAX/VMS Source Kit,
describes
steps to be taken to copy the VAX/VMS source kit.

•

Appendix G, Upgrading the System, describes the steps required
to upgrade a system from a Version 2.5 system to a 3.0 system.

•

Appendix H, VMSINSTAL Error Messages,
describes the
messages issued by the VMSINSTAL command procedure.

that

can

the

error

ASSOCIATED DOCUMENTS
There are no prerequisites to using this document, but it is strongly
recommended
that you read
the VAX/VMS Release Notes supplied with
Versions 3.0, 3.1 and 3.2, for
the most current information about
VAX/VMS before installing software.
In addition, an understanding of the
information presented
in
the
the VAX/VMS Command
VAX/VMS Summary Description and Glossary and
Language User's Guide may prove~lpful.
The following documents, which are referred to in this manual, provide
the
information needed
to manage the day-to-day operation of the
VAX/VMS system once it is initialized.
•

VAX/VMS System Management and Operations Guide

•

VAX-11 Utilities Reference Manual

For a complete list and description of
optional
software product documents,
Directory and Index.

VAX-11 documents,
including
see the VAX-11
Information

Further documentation on
installing optional
included with each optional software product.

viii

software

products

PREFACE
CONVENTIONS USED IN THIS DOCUMENT
Convention

Meaning
A symbol
with a oneto
three-character
abbreviation indicates that you press a key on
the terminal, for example, (5IT).

CTRL/x

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

$ SHOW TIME

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.

file-spec, •••

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

SUMMARY OF TECHNICAL CHANGES

The following technical changes have been made
Software Installation Guide for Version 3.2:

the

VAX-11/750

•

Chapter 4, The VMSINSTAL Command Procedure, has been rewritten
to
reflect significant changes and additions to the VMSINSTAL
command procedure.

•

The procedure for upgrading a Version 2.5 VAX/VMS system to
Version 3.0 VAX/VMS system has been moved to Appendix G.

•

Appendix H,
VMSINSTAL Error Messages, has been added to
explain
error messages issued by the VMSINSTAL command
procedure.

•

Installation information about RA60 disks has been added.

•

Information about remastered distribution kits has been added.

CHAPTER 1
OVERVIEW OF SOFTWARE INSTALLATION

There are
three
installation:

general

categories

VAX-11/750

software

•

Bootstrapping and installing a newly purchased VAX/VMS system

•

Applying system maintenance updates to a VAX/VMS system

•

Upgrading an existing VAX/VMS system

Installation refers to setting up a VAX/VMS operating system on a new
VAX-11/750 processor. Updating refers to applying system maintenance
updates, and consists primarily of a set of patches distributed on
TU58 cartridges. Upgrading refers to bringing a Version 2.5 system up
to the next major version, Version 3.0; and is done substantially by
file replacement.
All installation procedures are performed using the VAX-11/750 console
subsystem.

1.1

VAX-11/750 CONSOLE SUBSYSTEM

The console subsystem consists of three hardware components (a console
terminal, a TU58 cartridge drive, and an optional remote diagnostics
port) and a microcode program.
These hardware components and the
microcode program perform the actual bootstrap operation based on:
(1) the positions of the switches on the processor control panel, and
(2) the interactive commands entered at the console terminal.
You can request that the system
following ways:

bootstrapped

either

•

Directly from the system disk

•

Using the stand-alone BOOT58 program on the TU58 cartridge

the

Both methods require the assistance of the console subsystem.
The
recommended approach for daily operation is from the system disk with
the TU58 cartridge as backup. Using the first method, you issue a
BOOT command to the console subsystem to bootstrap the system from a
particular device. Using the second method, you issue a BOOT command
to the console subsystem to bootstrap the stand-alone BOOT58 program.
With stand-alone BOOT58, you can then bootstrap the system by
specifying either stand-alone BOOT58 commands or a command procedure
stored on the console TU58 cartridge.
(See Appendix B for more
information on the BOOT58 program.)
Figure 1-1 shows a diagram of the basic console subsystem.

1-1

OVERVIEW OF SOFTWARE INSTALLATION

VAX-11/750 CPU

Processor
control panel

Console-processor
interface

Remote diagnosis
interface (optional)

Console
terminal

TU58 tape
cassette
drive
ZK-994-82

Figure 1-1:

1.2

VAX-11/750 Console Subsystem

VAX-11/750 PROCESSOR CONTROL PANEL

The VAX-11/750 processor control panel consists of seven indicator
lights, four switches, and the TU58 cartridge drive. These switches
and indicator lights reflect the current state of the system and
dictate how the system will react to initial bootstrapping, shutdowns,
and restarts. Figure 1-2 shows a diagram of a VAX-11/750 processor
control panel.

1.2.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.
CPU State Indicators
POWER

When lit, this green light indicates that the
power is present in the processor and that the
keyswitch is in the ON position.

RUN

When lit, this green
processor is running.

ERROR

When dimly lit, this red light indicates the
processor is running normally. When brightly lit,
this red light indicates that the processor has
experienced an unrecoverable error.
Push the
white INITIALIZE button to reset the machine.
(The ERROR light will remain dimly lit.) During
normal operation, if the light is not on at all,
the bulb has burned out.

1-2

light

indicates

that

the

OVERVIEW OF SOFTWARE INSTALLATION

BOOT DEVICE

CPU STATE

~D~DD~D

!!·:--:··

Figure 1-2:

·::::1!

REMOTE D

RD FAULT

POWER

RUN

ERROR

INITIALIZE

I RD TEST RD CARRIER

~=@
o-·

POWER ON ACTION

LOCAL

M"~

SECUR@REMOTE/
mSECURE
OFF
REMOTE

RESTART
HALT

RESTART

The VAX-11/750 Processor Control Panel

Remote Diagnostic Indicators
The remote diagnostic indicator lights are invisible until
they
lit on a machine that has a remote diagnostic ROM installed.

are

REMOTE D

When lit,
this red
light
indicates that the
keylock rotary switch is in the REMOTE position.

RD FAULT

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

RD TEST

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

RD CARRIER

When lit,
this amber light indicates that
carrier signal is present on a dial-in line.

1.2.2

POWER-ON-ACTION Switch

The POWER-ON-ACTION switch controls the processor's power-up 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
HALT instruction executed in kernel mode)

example,

a
the

positions that instruct
The POWER-ON-ACTION switch has four
The instructions are:
processor how to power up the system.
BOOT

Bootstraps 'the system from the device selected
the BGOT DEVICE switch.

RESTART/BOOT

Restarts the system.
If the
restart fails
(if
memory
battery
backup fails during a power
failure, for example), bootstraps the system from
the device selected by the BOOT DEVICE switch.

HALT

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

RESTART/HALT

Restarts the system.
the system.

1-3

console

prompt

If the restart fails,

halts

OVERVIEW OF SOFTWARE INSTALLATION
During normal system operation, the POWER-ON-ACTION switch should be
set to
the RESTART/BOOT position.
This switch setting provides for
the most comprehensive system recovery procedure.

1.2.3

BOOT DEVICE Switch

The BOOT DEVICE switch can be 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:
•

When you issue the console BOOT command without
device name

•

When the system attempts an automatic bootstrap

specifying

In both situations, the processor examines the BOOT DEVICE switch and
assumes that the controller character is A and that the unit number of
the drive is O.
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 local 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.

1.2.4

INITIALIZE Button

When you press the white INITIALIZE button,
the system performs an
automatic 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.

1.2.5

Keylock Rotary Switch

The keylock rotary switch controls the actions of
the console subsystem.

the

processor

and

OFF

Power is off.

SECURE

Processor can be run;
however,
the
console
commands,
remote diagnostic line, and INITIALIZE
button are disabled.

LOCAL

Processor can respond to console commands, and the
remote diagnostic line is disabled.

REMOTE/SECURE

Console commands and
the
INITIALIZE button are
disabled,
and the optional remote diagnostic line
replaces the console terminal.

REMOTE

Console commands are disabled;
however, they can
be activated by means of the optional remote
diagnostic line.

1-4

OVERVIEW OF SOFTWARE INSTALLATION
1.3

OVERVIEW OF SYSTEM INSTALLATION

Installation can be performed by any system user who has access to the
console terminal.
To bootstrap and install a VAX/VMS operating
following steps at the console terminal:

system,

perform

the

Restore the required save set
(the files required for a
bootable system) from the distribution kit to disk, using the
stand-alone version of the Backup Utility (BACKUP).

Bootstrap the system.
(When booting, additional files will be restored from the
distribution kit. These files are referred to as the library
and optional save sets.)

Shut down the system and reboot.

Run the User Environment Test Package (UETP).

This installation process is restartable at any point. Steps one and
two are described in Chapter 2, Building a Bootable System Disk.
Steps three and four are described in Chapter 3, Site-Specific
Modifications to VAX/VMS.
The updating procedure is described in
procedure is described in Appendix G.

1-5

Chapter

The

upgrading

CHAPTER 2
BUILDING A BOOTABLE SYSTEM DISK

The VAX-11/750 software distribution kit
system contains the following:

for

the

VAX/VMS

operating

•

The distribution tape, RK07 disk, RA60 disk, or RL02 disk(s)

•

Two TU58 cartridges containing stand-alone BACKUP
(only with
magnetic
tape distribution kits;
RK07,
RA60,
and
RL02
distribution kits contain two blank TU58 cartridges to be used
in creating a stand-alone BACKUP kit)

•

One blank TU58 cartridge to be used in creating a new
TU58

console

The distribution tape or disks contains all the files needed to create
a
VAX/VMS
operating
system.
However,
as
they exist in the
distribution kit, the VAX/VMS files are split into three groups called
BACKUP save sets.
The save sets are in a compressed format and do not
comprise a usable system.
The files in the save sets must be restored
to
another disk,
using
the
stand-alone Backup Utility that
is
contained on the distribution disk (or on TU58 cartridge for magnetic
tape distribution kits).
The restoration process reformats the files
into a usable VAX/VMS system.
The three save sets are composed of different types of files.
save set contains all the files required for a bootable system;
others consist of the VAX/VMS library and VAX/VMS optional files.

One
the

NOTE
Only new installation sites using
the
VAX/VMS
Version
3.2
remastered
distribution kit should
install
their
system using
the
instructions in this
chapter.
If you are already operating
on a VAX/VMS Version 3 operating system,
you must perform updates to your
system
using
the
instructions in Chapter 4 of
this manual.
If you are operating on a
VAX/VMS Version 2.5 operating system or
lower, see Appendix G.

2.1

OVERVIEW OF BUILDING A BOOTABLE SYSTEM DISK

There are four steps to building a bootable system disk:
1.

Stand-alone BACKUP is booted, either from the RK07
RK07
distribution
kits,
from the RA60 disk

2-1

disk for
for
RA60

BUILDING A BOOTABLE SYSTEM DISK
distribution kits, from the primary distribution disk for the
RL02 distribution kits, or
from
the TU58 cartridges for
magnetic tape distribution kits.

Stand-alone BACKUP restores the required save set from the
distribution kit to
the
target disk, creating a kernel
VAX/VMS system.

The kernel VAX/VMS system is booted.

Once booted, the kernel VAX/VMS system restores the library
and optional save sets from the distribution kit to the
target disk.
On RL02/RA80 configurations the optional save
set is distributed on a separate RL02 disk and may be
restored at a later date, if desired.

Before you can build a bootable system disk, you must verify that you
have received all needed VAX/VMS V3.2 software.
You must also know
how to specify device names and power up the system.
Sections 2.2
through 2.4 describe these procedures in detail.

2.2

VAX/VMS SOFTWARE DISTRIBUTION KITS

VAX/VMS software for the VAX-11/750 is distributed on either
disk, an RA60 disk, two RL02 disks, or on magnetic tape.
The bill of materials
contents of that kit.
listed.

RK07

that comes with the kit lists the entire
Check to make sure you have received everything

In addition to the materials contained in the software distribution
kit, you will also need a console TU58 cartridge before you can
proceed with an installation or upgrade.
If you are a new customer,
the console TU58 cartridge was shipped with the hardware.
For other
customers, your current console TU58 cartridge will be upgraded as
part of the VAX/VMS upgrade procedure.

2.2.1

Magnetic Tape Kit

The VAX-11/750 magnetic tape software distribution
following:
•

contains

The VAX/VMS Version 3.2 distribution tape
Part number:

BB-D782F-BE

Part description:
•

kit

VAX/VMS V3.2 BIN 16MT9

Two TU58 cartridges that contain stand-alone BACKUP
Part number:

BE-M757A-BE

Part description:
Part number:

V3.2 S/A BKUP T58 1/2

BE-M758A-BE

Part description:

V3.2 S/A BKUP T58 2/2

2-2

the

BUILDING A BOOTABLE SYSTEM DISK
•

One blank TU58 cartridge to be used in creating a new
TU58
Part number:

36-15809-00

Part description:

2.2.2

console

BLANK TU58 CASSETTE

RK07 Kit

The VAX-11/750 RK07 software distribution kit contains the following:
•

The RK07 Version 3.2 distribution disk
Part number:

AY-H020F-BE

Part description:

VAX/VMS V3.2 BIN RK7

in creating a
two to be used
blank TU58 cartridges:
• Three
stand-alone BACKUP kit, one to be used in creating a new
console TU58

2.2.3

RA60 Kit

The VAX-11/750 RA60 software distribution kit contains the following:
•

•

The RA60 Version 3.2 distribution disk
Part number:

BD-R379A-EE

Part description:

VAX/VMS V3.2 BIN RA6

Three blank TU58 cartridges:
in creating a
two to be used
• stand-alone
BACKUP kit, one to be used in creating a new
console TU58

2.2.4

RL02 Kit

The VAX/VMS operating system on an
distributed on two separate RL02 disks:
•

A primary distribution disk

•

An optional distribution disk

RL02/RA80

configuration

The primary distribution disk contains the files needed
VAX/VMS operating system.

create

It consists of two BACKUP save sets that are composed of different
types of files.
One save set contains all the files required for a
bootable system, and the other consists of the VAX/VMS library files.
The optional distribution disk contains additional pieces of the
VAX/VMS operating system, including compatibility mode files, VAX-11
BLISS files, programming examples, and miscellaneous other files.
The
optional disk also contains the EDTCAI course, which is not part of
the operating system.
The optional distribution disk may be restored
either at installation time or at a later date.

2-3

BUILDING A BOOTABLE SYSTEM DISK
2.2.4.1 The Primary Software Distribution Disk - To restore both the
files required for a bootable system and the VAX/VMS library files,
you need the following:
•

The VAX/VMS Version 3.2 primary distribution disk
Part number:

BC-M761B-BE

Part description:
•

VAX/VMS V3.2 REQUIRED RL2

Three blank TU58 cartridges

The three blank TU58 cartridges are provided for building stand-alone
BACKUP and copying the console media.
Procedures for both of these
operations are described in Chapter 4.

2.2.4.2 The Optional Software Distribution Disk - To
optional VAX/VMS files, you need the following:
•

the

The VAX/VMS Version 3.2 optional distribution disk
Part number:

BC-M762B-BE

Part description:

2.3

restore

VAX/VMS V3.2 OPTIONAL RL2

SPECIFYING DEVICE NAMES

You will need to specify a device name twice in order to build a
bootable system disk: once when specifying the location of the target
disk for the required save set, and once when responding to the data
prompt asking which device is holding the distribution kit.
All hardware devices supported on a VAX/VMS system have a device
code.
Examples of these codes are listed in Table 2-1.

type

The device name identifies the physical device on which a file is
stored. The device name contains three fields, in the format ddcu:
•

The device type (dd).
For example, an RK07 disk is DM
TE16 magnetic tape is MT.

and

•

A controller designator
(c).
The controller
designator
identifies the hardware controller to which the device is
attached.
The first or only controller is always designated
A.

•

The unit number (u).
panel of the disk
device unit.

The unit number button on the front
drive uniquely identifies a particular

Some examples of device names are:
Name

Device

DMA2

RK07 disk on controller A, unit 2

DLAl

RL02 disk on controller A, unit 1

MTAO

TE16 magnetic tape on controller A, unit 0

DUAlO

RA81 disk on UDA controller A, unit 10

2-4

BUILDING A BOOTABLE SYSTEM DISK
Table 2-1: Device Type Codes
Code

Device Type

Console Storage Device

RP05, RP06 Disks

TU58 Cartridge Tape

RL02 Cartridge Disk

RK06, RK07 Cartridge Disks

RM03, RM05, RM80, RP07 Disks (See note below)

RA60, RASO, RA81 Disks

RX02 Floppy Diskette

Line Printer on LPll

TU78 Magnetic Tape

TSll Magnetic Tape

TE16, TU45, TU77 Magnetic Tapes

Operator's Console

Remote Terminal

Interactive Terminal on DZll

NOTE: When booting any of these devices at the console program prompt
(>>>),use the mnemonic DB.

2.4

POWERING UP THE SYSTEM

To power up the system, check the switches and
see that you have the console prompt (>>>).

2.4.1

panel

indicators

and

Checking the Switches and Panel Indicators

To power up the system,
positions indicated:

the

following

switches

should

•

The ON-OFF power switch on the console terminal: ON

The POWER-ON-ACTION
panel: HALT

•

The rotary key switch on the processor control panel: LOCAL

switch

the

processor

Also, be sure the POWER control panel indicator is lit.

2-5

the

control

BUILDING A BOOTABLE SYSTEM DISK
2.4.2

Checking for the Attention of the Console Program

See that you have the attention of the console program by checking for
the three-angle-bracket {>>>) prompt.
If this prompt does not appear,
perform the following steps:

2.5

Make sure the POWER-ON-ACTION switch is in the HALT position.

Make sure the rotary key is in the LOCAL position.

If the power is already on, press CTRL/P to cause the console
program to prompt with three angle brackets (>>>).

RESTORING THE DISTRIBUTION KIT

The first step in restoring the distribution kit
is
loading
stand-alone BACKUP.
When stand-alone BACKUP is loaded, use it to
restore the required save set to the target disk.
Once booted, the
kernel VAX/VMS system that is created automatically restores the
library and optional save sets to the target disk.
If you receive any error messages during installation, refer
VAX/VMS System Messages and Recovery Procedures Manual.

2.5.1

the

Loading Stand-alone BACKUP

Stand-alone BACKUP can be loaded from either the RK07 disk
(RK07
d is tr i bu t i on k i ts) , the RA 6 O disk
{RA 6 0 dist r i but ion kits) , the
TU58
primary RL02 disk
(RL02 distribution kits), or from the
cartridges (magnetic tape distribution kits).

2.5.1.1 Loading Stand-alone BACKUP from Disk - The
loading stand-alone BACKUP from a disk is as follows:

procedure

for

Place the distribution disk in the appropriate drive.
Sites
using
the RL02 distribution kit must use the primary
distribution disk in this step. Write protect the disk by
pressing the WRITE PROTECT button, and spin it up by pressing
the RUN button or the LOAD button, depending on the drive you
are using.

At the console prompt, boot stand-alone BACKUP by typing a
"B" with the appropriate device type.
For example, the
following boots an RK07 disk:

»> B DMcu
(where c is the controller letter and u is the unit number)
Two percent signs {%%) will appear on the console terminal.
3.

After about 10 seconds, you will observe the following
message and DIGITAL Command Language (DCL) prompt ($) on the
console terminal
VAX/VMS Version V3.2

<date

2-6

hh:mm>

BUILDING A BOOTABLE SYSTEM DISK
2.5.1.2 Loading Stand-alone BACKUP from TU58 Cartridge - If you have
a magnetic tape distribution kit, you will be booting BACKUP from TU58
cartridge.
The procedure for loading stand-alone BACKUP from TU58
cartridges is as follows:
1.

Place the distribution tape on a magnetic tape drive.
Press
the LOAD button. When the tape has loaded, press the ONLINE
button.

Insert the BACKUP TU58 marked VAX/VMS V3.0 S/A BKUP T58 1/2.

At the console prompt, type:

>» B DDAO
4.

When BACKUP has finished
loading
the
first TU58,
after
approximately 15 minutes, you will receive this message:
VAX/VMS Version V3.2 <date hh:mm>
Please mount second stand-alone system diskette or
cartridge and press RETURN.

Remove the first stand-alone BACKUP TU58, replace it with the
second stand-alone BACKUP TU58 marked VAX/VMS V3.0 S/A BKUP
T58 2/2, and press RETURN.

When BACKUP has completed loadinq, after approximately five
minutes, the DCL pr~mpt ($) will-appear, and you are ready to
continue.

\ ·-·-··----------~--===---=--=====--=~=~~
i

2.5.2

Leave the second BACKUP TU58 in
restored the required save set.

the

drive

until

you

have

Restoring the Required Save Set to the Target Device

After stand-alone BACKUP has been loaded, the procedure for
restoring
the required save set to the target disk is the same for both magnetic
tape and disk distribution kits.
1.

Place the target disk in the drive and spin up the disk by
pressing the RUN button.
In
the case of the RL02/RA80
configuration the target device is a nonremovable disk and
need only be spun up.

At the dollar sign prompt, type the
following form:

BACKUP

command

the

BACKUP/VERIFY ddcu:REQUIRED/SAVE ddcu:
It is important to type the exact
including all colons and spaces.

syntax

the

command,

For example, when your magn-etic tape distribution kit
is on
drive MSAO:
and your target disk is DMAl. :,iou would type:
~

_,__ ·r -

$ BACKUP /VERIFY MSAO: REQUIRED/SAVE OMA .;

The /VERIFY qualifier specifies that the distribution medium
and the target disk should be read and compared.
Optionally,
the /LOG qualifier can be used in addition to the /VERIFY
qualifier,
if you want BACKUP to list each file on the
console terminal as it is restored.

2-7

BUILDING A BOOTABLE SYSTEM DISK
You will then receive the following message:
%BACKUP-I-STARTVERIFY, starting verification pass

($)

BACKUP

After a few minutes, you will receive the DCL prompt
the console terminal.
3.

Halt the processor and
terminate
pressing CTRL/P and then typing H.

stand-alone

If you loaded stand-alone BACKUP from TU58
(magnetic tape
distribution kit),
remove the second BACKUP TU58 from the
drive and replace it with the console TU58.
NOTE
The BACKUP command creates a system disk
with a
DIGITAL-provided set of volume
parameters, including a cluster factor
of
1.
Most of these parameters, except
for the cluster factor, can be modified
after
installation with the SET VOLUME
command.
To alter the cluster factor,
however,
you must back up the system
disk, using the /NOINITIALIZE qualifier,
to
another
volume
that
has been
initialized with the desired values.

2.6

BOOTING THE TARGET DEVICE AND RESTORING THE REST OF VMS

To boot the partially built operating system and restore the
VAX/VMS, proceed as follows:
1.

At the console terminal, boot the target disk by
following:

rest

typing

the

>>>B ddcu
For example:
>>> B DMAl
The system will respond with the following message:
VAX/VMS Version V3.2 <date hh:mm>
%0PCOM, <date hh:mm:ss.s>, logfile initialized
by operator OPAO
logfile is SYS$MANAGER:OPERATOR.LOG
Login quotas - Interactive limit=64,
Current interactive value=O
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM)
2.

Enter the date and time in the twenty-four hour clock format,
and press RETURN.
For example:
If it is June 1,
01-JUN-1983 14:05.

1983,

2:05

The system will prompt you as follows:
Enter drive holding distribution kit (DDCU):

2-8

P.M.,

enter

BUILDING A BOOTABLE SYSTEM DISK
Enter the name of the device holding the distribution kit.
For example:
MSAO
The installation procedure uses this information
the library and optional save sets.

restore

In the case of the RL02/RA80 configuration, the optional save
set
is distributed
on a separate disk and may be installed
either at installation time (described in Step 5), or at a
later date (described in Section 2.6.1).
4.

The
following
messages will
appear over
the course of
approximately 15 minutes, while the files are being restored.
%MOUNT-I-MOUNTED,VMS032

mounted on <device>

Restoring library save set.
%BACKUP-I-STARTVERIFY, starting verification pass
5.

This step applies only to the RL02/RA80
configurations.
If
you are installing any other configuration you should skip to
Step 6.
You will receive the following prompt.
Do you wish to install the OPTIONAL distribution kit
[No]?
Press RETURN if you do not wish to install the optional
kit.
If you do not install the optional kit, the next message you
will receive is the "Running AUTOGEN"
message
in Step 6.
Continue the installation from that point.
If you respond with
following prompt.

the

letter

you

will

receive

the

Dismount the Primary distribution kit from drive DLAO.
Mount the OPTIONAL distribution kit in drive DLAO, press return when ready.

Spin down the primary disk and replace it with
the optional
disk.
Spin
up the optional
disk and
press RETURN.
A
confirmation of the disk mount will appear:
MOUNT-I-MOUNTED, VMSOPT mounted on
6.

DLAO:

You will now receive the following messages:
Restoring optional save set.
%BACKUP-I-STARTVERIFY, starting verification pass
Running AUTOGEN -- Please wait.
While AUTOGEN is running, you will receive messages telling
you which files have been created or extended.
When it has
completed running, you will receive the following message:
%0pcom, <date hh:mm:ss.s>, message from user SYSTEM
%SYSGEN-I-WRITECUR, CURRENT system parameters modified by process ID
00010045 into file SYS$SYSROOT: [SYSEXE]SYS.EXE;l

System shutting down to allow boot of complete V3.2 system.
You must manually reboot the system after it halts.
2-9

BUILDING A BOOTABLE SYSTEM DISK
While the system is shutting down,
the command procedure
displays shutdown messages. When the shutdown is complete,
you receive the following message:
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM
7.

Halt the system, by
pressing RETURN.

pressing

Reboot the system by typing:

CTRL/P,

typing

"H",

and

>>> B ddcu
Restoration of the distribution disk is complete; you have a
running
system.
Refer to Chapter 3 for any site-specific modifications you
might want to make to the system.

2.6.1 .Restoring the Optional Kit on an RL02/RA80 Configuration
Restoration of the save sets on the optional disk to
the RL02/RA80
configuration can be done at a later date by invoking a command
procedure (VMSINSTAL.COM) that uses the Backup Utility. The two save
sets contained on the disk are restored separately; you can restore
one without the other by specifying different parameters for
the
command procedure.
To restore the optional kit to the system disk, perform the
procedure:

following

Remove any disk currently in the RL02 drive and
replace it
with the optional distribution disk. Write protect the disk
by pressing the WRITE PROT button and spin up the disk.
The
unit number light will come on when the disk is ready.

performing

the

Press RETURN.

In response to the system's request for your
type SYSTEM.

In response to the system's request
type the system manager password.

for

your

following

user

name,

password,

The system returns the following message and DCL prompt:
Welcome to VAX/VMS Version V3.2
$
3.

When the DCL prompt ($) appears on the console terminal,
your default directory to SYS$UPDATE by typing:
$ SET DEFAULT SYS$UPDATE
The system responds with another DCL prompt.

2-10

set

BUILDING A BOOTABLE SYSTEM DISK
4.

Type:

$ @VMSINSTAL VMSOPT
This command invokes the VMSINSTAL command
prompts with:

procedure,

which

Enter drive holding distribution kit:
5.

Assuming that the RASO drive is designated as unit 0 and the
RL02 drive is designated as unit 1, enter DLAl.
The system
responds with:
%MOUNT-I-MOUNTED, VMSOPT mounted on DLAl
The command procedure then prompts:
Enter the device to which the optional save-set should
be restored (DDCU):

When you enter DUAO, the system responds:
Restoring optional files.
After approximately 5 minutes, the following message
on the terminal:

appears

%BACKUP-I-STARTVERIFY, starting verification pass
After approximately 5 minutes
completion messages:

more,

you

will

receive

the

OPTIONAL file set restoration complete.
Kit installation complete.
The optional VAX/VMS files are now restored to your system disk.
You
install the EDTCAI course from the optional disk by using the
parameter EDTCAI in place of VMSOPT (See Chapter 4).

2-11

CHAPTER 3
SITE-SPECIFIC MODIFICATIONS TO VAX/VMS

The VAX/VMS operating
system that exists at this point in the
installation procedure
is already set for
your
site's hardware
configuration.
During initial bootstrap the AUTOGEN command procedure
automatically set the system parameters, paging file, swapping file,
system dump file, and
installed
images list to values considered
appropriate for your system.
On most systems no further modifications
to these files should be required.
Your
site-specific start-up command
procedure
is blank and
the
bootstrap command
procedure is a default.
The procedures are set to
these defaults to allow the initial bootstrap of the systrem and may
require site-specific modifications.

To create a system that more closely suits the
site, you may do either of the following:

3.1

requirements

•

Modify system parameters for
special
hardware
needs or special workload requirements

•

Perform other site-specific modifications

your

configuration

LOGGING IN TO THE SYSTEM

Before you can perform any modifications to the system, you must log
in as the system manager.
Once the system
is initialized, it
announces itself with the following message:
Login quotas - Interactive limit=64,
Current interactive
SYSTEM
Job terminated at <date hh:mm:ss.s>
At this point, you can log into the system as the system
performing the following steps at the console terminal:

value=O

manager

Press RETURN.

In response to the system's request for your user name,
SYSTEM.

type

In response to the system's request for your
MANAGER.

type

password,

The system displays the following message:
Welcome to VAX/VMS Version V3.2
and the Digital Command Language (DCL) issues its prompt
($).
When
this prompt appears on the console terminal, you can begin modifying
the system.

3-1

SITE-SPECIFIC MODIFICATIONS TO VAX/VMS
3.2

SITE-SPECIFIC MODIFICATIONS

There are several site-specific modifications that
while you are logged in as system manager.

may

performed

When the system is bootstrapped, it uses a default start-up command
procedure,
SYS$SYSTEM:STARTUP.COM.
This command procedure, in turn,
requests the execution of a site-specific start-up command
procedure,
SYS$MANAGER:SYSTARTUP.COM, which is
initially blank and should be
customized for your site.
For example,
SYSTARTUP.COM could contain
the commands that initialize and start up your site's batch and print
queues.
You may also want to customize the user authorization file and
user file directories.

create

To perform these site-specific modifications,
System Management and Operations Guide.

VAX/VMS

3.3

consult

the

SYSTEM SHUTDOWN AND REBOOT

In order to ensure that all the modifications you perform are accepted
by VAX/VMS, you must shut down and then_reboot the system.

Shut down the
procedure:

system

executing

the

following

command

$ @SYS$SYSTEM:SHUTDOWN

This command procedure prompts for
the number of minutes
until
system shutdown, the reason for the shutdown, whether
to spin down the disks, the expected time the system will be
restored, and whether automatic reboot should be enabled.
If you enabled automatic reboot, the
POWER-ON-ACTION switch
is already set to RESTART/BOOT;
the BOOT DEVICE switch is
already set to your current system disk,
and
the system
handles rebooting by itself. You can skip steps 2 and 3.
2.

In response to the statement, "SYSTEM SHUTDOWN COMPLETE - USE
CONSOLE TO HALT SYSTEM,"
halt the processor by pressing
CTRL/P to obtain the console prompt (>>>).

To boot the system, make sure the BOOT DEVICE switch is
to boot from your newly built system disk, and type B.

The system will respond with the message:
VAX/VMS Version V3.2 <date hh:mm>
The system is now completely installed.
For more information on ways to boot the system, see Section 5.2.

3-2

set

SITE-SPECIFIC MODIFICATIONS TO VAX/VMS
3.4

MODIFYING SYSTEM PARAMETERS

The AUTOGEN command procedure
is automatically run upon initial
bootstrap of your
system.
This procedure generates your VAX/VMS
system with system parameter values suitable for your hardware.
However in cases of unusual hardware configuration or special workload
requirements, modifications of the system parameters may be necessary.
The file SYS$SYSTEM:PARAMS.DAT contains the system parameters and can
be edited to suit your needs.
If you make changes or additions to the PARAMS.DAT file, when you are
finished
you must invoke the AUTOGEN command procedure with the
command:

$ @SYS$UPDATE:AUTOGEN
Invoking AUTOGEN establishes your changes as the current values.
For detailed information about system parameters refer to the
Management and Operations Guide.

VAX/VMS

~ystem

3.5

VAX/VMS USER ENVIRONMENT TEST PACKAGE

The first thing you should do with your newly installed system is run
the VAX/VMS User
Environment Test Package
(UETP).
The UETP is a
collection of tests designed to demonstrate that the hardware and
software components of a VAX/VMS system are in working order.
Details
of running the UETP are described in the VAX/VMS UETP User's Guide.
When the UETP runs to completion without encountering nonrecoverable
errors, the system is ready for use.

3.6

BACKING UP YOUR SYSTEM DISK TO A SCRATCH DISK OR TAPE

To back up your system disk to a scratch disk or tape use
BACKUP TU58 cartridges.
The procedure is as follows:

stand-alone

Shut down your system.

Write protect your system disk by pressing the WRITE
button.

Boot stand-alone BACKUP from the TU58 cartridges _(see Section
2.5.1.2).

Place a scratch volume on an appropriate drive.

Issue one of the following BACKUP commands:
For disk:
For tape:

PROTECT

BACKUP/VERIFY system-disk: scratch-disk:
BACKUP/VERIFY system-disk: tape device:save-set name

For example, where the system disk is DMAO
disk is DMAl:
$ BACKUP/VERIFY DMAO:

and

the

scratch

DMAl:

For more details on using BACKUP, see the BACKUP chapter of the VAX-11
Utilities Reference Manual.
If you received an RK07 or RA60 distribution kit, see Section
build stand-alone BACKUP on TU58 cartridges.

3-3

5.4

SITE-SPECIFIC MODIFICATIONS TO VAX/VMS
3.7

THE SYSTEM AFTER INSTALLATION

Now that your
system
is installed,
and any needed
site-specific
modifications have been made,
there are several procedures you may
want to perform on the system.
You can back up the console medium,
perform several methods of boostrapping, build and copy a VAX/VMS
system disk, or build a stand-alone BACKUP kit.
See Chapter 5 for
instructions on these procedures.

3-4

CHAPTER 4
THE VMSINSTAL COMMAND PROCEDURE

The command procedure VMSINSTAL is used to install system
updates and optional software products.

maintenance

Eventually, all optional software products will be installed
using
VMSINSTAL.
However, at the present time, VMSINSTAL is used to install
only some optional software products.
DIGITAL is in the process of
converting
the remaining optional software product installations to
the use of VMSINSTAL.
Until they have been converted, these optional
software products will continue to be installed using the VMSUPDATE
command procedure (see Appendix E).
This chapter describes what to look for
in the software product
distribution kits, how to prepare for installation, how to invoke
VMSINSTAL, how to choose among
installation procedure options, and
what to do in the event of a system failure during installation.
This
chapter does not describe the specific
installation procedures for
each update and product.
The questions, prompts, and information that
you receive during installation will differ from product to
product.
For specific installation details, consult the installation guide that
comes with each update or product.
This chapter also describes
installation of EDTCAI, a software product that is included with some
VAX/VMS distribution kits.
For information explaining
the error messages
VMSINSTAL command procedure, see Appendix H.

4.1

received

from

the

EXAMINING THE DISTRIBUTION KITS

System updates and optional software products are distributed on TU58
cartridges or magnetic
tape.
EDTCAI
is a save set on the VAX/VMS
distribution kit, which can be either disk or magnetic tape.
Each cartridge, disk, or tape is labeled with both a name and a serial
number
that differentiates it from others in the distribution kit.
Check that your
kit contains everything
listed
in the bill of
materials.
Included in each distribution kit is the installation
to that update or product.

4.2

guide

specific

PREPARING TO USE VMSINSTAL

In order for
following:

VMSINSTAL

run

properly,

4-1

you

must

first

the

THE VMSINSTAL COMMAND PROCEDURE
1.

Back up your system disk (see Section 3.6).
A system failure
at a critical point of the installation could leave unusable
files.
In addition, optional software
products may delete
older
product versions before installing new ones, so it is
advisable to back up your system disk before attempting
any
software
installation.
The backup copy you create should be
used for the installation to verify that the backup copy
contains a
working
system and because, of the two, it has
more
free contiguous space,
which you
may
need
for
installation.

under

the

system

manager's

(If the SYSGEN parameters MOUNTMSG or DISMOUMSG at your
site
have been set to
1, you will receive a message from OPCOM
each time a disk or tape is mounted
or dismounted.
These
messages are normally disabled,
but if
they have been
activated and you are installing from an operator's terminal,
they will appear from one to thirty seconds after each mount
or dismount.)

Ensure that all users are logged out and that all batch
are completed.

Prevent users from gaining access to the system
at the DCL prompt ($):

jobs

entering

$ SET LOGINS/INTERACTIVE=O
5.

Shut down
entering:

DECnet-VAX

(if

your

system

includes

it)

prompt

(NCP>).

the

$ RUN SYS$SYSTEM:NCP
The system responds with
prompt, enter:

the

NCP

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
the NCP by typing EXIT at the prompt.

Ensure that the limits in the
SYSTEM account authorization
record have values that are equal to or greater than the
following designated default values:
Buffered I/O byte count quota (BYTLM)
Enqueue quota (ENQLM) = 20
Buffered I/O limit (BIOLM} = 12
Direct I/O limit (DIOLM) = 12
Open file quota (FILLM) = 20
AST limit (ASTLM) = 20

20480

To check these values, enter the following command at the DCL
prompt:
$

SHO~

PROCESS/QUOTA

The system will display the current
account's authorization record.

values

the

SYSTEM

If necessary, you ca:-1 change these values by entering at
DCL prompt:

4-2

the

THE VMSINSTAL COMMAND PROCEDURE
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
The system responds with
prompt, enter:

the

UAF

prompt

(UAF>).

the

MODIFY SYSTEM/limit=new-value
For example:
UAF> MODIFY SYSTEM/DIOLM=l2
To return to DCL command level, type EXIT at the UAF prompt.
You must log out and log in again for any changes to take
effect.
NOTE
Beyond this point in the
installation
procedures, installations vary according
to update or product.
The following
section is a general description of how
to
invoke
VMSINSTAL.
Consult
the
specific update or product installation
guide before invoking VMSINSTAL.

4.3

INVOKING VMSINSTAL

This section is a general description of how to invoke the VMSINSTAL
command procedure.
Section 4.4 describes options that may be used
when invoking this procedure.
To initiate installation using VMSINSTAL, enter the following
at the DCL prompt:

command

@SYS$UPDATE:VMSINSTAL product-list ddcu:
product-list
A list of the product(s) being installed
from
the distribution
volume.
Items in a product list are separated by commas with no
spaces and are of the format:
f acvvu
In this format:
fac is the facility name (1-6 alphanumeric characters).
vv is the major version number (2 digits).
u is the update number (1 digit).
For example, the VAX/VMS
number 2 is:

operating

system,

version

update

VMS032
Items in this format allow you to install a specific version and
update of a product from a distribution volume containing several
versions and updates.
If you specify only the
facility name,
with no version or update number, then all versions and updates
present on the volume are installed in chronological order.
You

4-3

THE VMSINSTAL COMMAND PROCEDURE
may specify a wildcard character (*) for
the
product list,
in
which case all versions and updates of all products present on
the volume are installed in chronological order.
At the present
time,
DIGITAL generally distributes only a single version of a
product per distribution volume.
You will be
parameter.

prompted

for

product

list

you

omit

this

ddcu:
The device specification of the drive on which the distribution
volume for the optional software product or maintenance update is
to be mounted.
You will be prompted for this parameter
if you
omit it.
At this point, if the conditions described in Section 4.2 are not met,
you will
receive a warning
that explains the problem and a prompt
asking if you wish to continue.
It is strongly recommended
that you
correct the situation before reinvoking VMSINSTAL.
If you continue,
the resulting installation may not be supported by DIGITAL.
You will also be asked if you are satisfied with the backup of your
system disk (see Section 4.2).
Again, if you are not satisfied, it is
strongly recommended that you correct the situation before continuing.
Once you invoke VMSINSTAL you will
receive several
prompts and
messages that direct and explain the installation.
These prompts and
messages differ depending on the update or software product.
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 the acceptable responses to that prompt.
At the end of an installation, VMSINSTAL will do one of two
things,
depending
on the
requirements of the
update or product.
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.
Finally, after installing the update or optional software
you should back up the updated system disk.

4.4

product(s),

CHOOSING VMSINSTAL OPTIONS

use of three options;
The VMSINSTAL command procedure permits the
Auto-answer,
File Log, and Alternate Root.
These options perform the
following functions:
Auto-answer
Allows you to record the answers you give to queries and
prompts
during
installation. When you install an update or product, you
receive several prompts and queries to which you respond.
When
you use the Auto-answer option VMSINSTAL creates a file with the
specification SYS$UPDATE:facvvu.ANS (if such a
file does not
already exist)
and saves your responses in this file.
If you
reinstall a software product in the future (as you must when a
major version of the VAX/VMS operating system is distributed) and
you use the Auto-answer option, VMSINSTAL will check for
the
existence of facvvu.ANS and use the answers you have saved.
If
you reinstall without using
the Auto-answer option,
you will
again receive prompts and queries during installation.

4-4

THE VMSINSTAL COMMAND PROCEDURE
Note that if you wish to record
new answers in a
subsequent
installation, you must first delete the existing answer file and
then
install
the product again, specifying
the Auto-answer
option.
File Log
Logs all file activity to the terminal during installation9
File
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.
ac~1v1~y

Alternate Root
Permits you to install 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
specific product's installation documentation to determine whether
it
is possible.
The format for invoking VMSINSTAL with these options is as follows:
@SYS$UPDATE:VMSINSTAL product-list ddcu: OPTIONS option-list [root]
OPTIONS
A keyword that must be entered along with one or more options in
the option list to guarantee against accidentally invoking an
option.
If you enter an option-list and the OPTIONS parameter is
not
entered,
you will
receive an error message and
the
installation will be terminated.
option-list
A list of the options requested.
This list consists of one
letter option abbreviations separated by commas, with no spaces.
The abbreviations are: A for Auto-answer, L for File Log, and R
for Alternate Root.
You may specify any option or all three.
However, if you specify Alternate Root, you must also specify the
root parameter (see below).
root
The alternate system root to which you
product(s).
It must be of the format:

wish

install

the

~ddcu:[SYSn.]

(Note that two leading underscores are required.)
In this format:
ddcu is the device on which the alternate root resides
[SYSn.]

is the top level directory of the alternate root

You may specify a logical name that has been defined for an
root.

4-5

alternate

THE VMSINSTAL COMMAND PROCEDURE
The following is an example, of using VMSINSTAL with options:
$ @SYS$UPDATE:VMSINSTAL VMS032 CSAl:

OPTIONS L,R ~DMAl: [SYSO.]

In this example, update version 3.2 of the VAX/VMS operating system is
being
installed to the alternate root, [SYSO.], on the device, DMAl.
The file activity during installation is being logged to the terminal,
as we 11.

4.5

RECOVERING FROM SYSTEM FAILURE

If you experience a system failure, such as power loss, during
installation of an update or optional software product, VMSINSTAL will
attempt to automatically continue the installation upon rebooting.
If
you are booting from the console TU58, you will have to place the
console TU58 back in the console TU58 drive in order to reboot.
Depending on the point in the installation at which the system failed,
one of three conditions will exist:
1.

The system disk will not have undergone any changes before
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 4. 2) , and restart the
installation.

VMSINSTAL will continue the installation.
In this case,
VMSINSTAL performs most of the installation and then informs
you that you must manually purge replaced files, even if you
requested that they be purged automatically. If VMSINSTAL
instructs you to do so, reboot the system, log in as system
manager, and purge all system files by entering at the DCL
prompt ( $) :
$PURGE/LOG SYS$SYSROOT: [* ••• ]*.*
When you
complete.

4.6

have

performed

these

tasks,

installation

INSTALLING EDTCAI

The installation of EDTCAI uses neither VMSINSTAL as it is described
above nor VMSUPDATE.
It uses a version of VMSINSTAL without options
that does not attempt to recover from a system failure.
To install
the EDTCAI course, perform all the steps described in Section 4.2,
then proceed as follows:
1.

Mount your distribution disk or tape.

Type the following command to initiate
EDTCAI:

the

$ @SYS$UPDATE:VMSINSTAL EDTCAI

You will receive the following request:
Enter drive holding distribution kit:

4-6

installation

THE VMSINSTAL COMMAND PROCEDURE
dd
is the
You must type your response in the format ddcu:
device code;
c,
the controller letter,
and u, the unit
number.
You will then see the following message text at the terminal:
This procedure will install the EDTCAI course on your system.
This course will work on either the VT52 or a VTlOO compatible
terminal.
However, the display library for each terminal type
is over 500 blocks, and if you do not have a particular terminal
type on your system, you might wish to save disk space by not
installing that particular library.
You will receive the following query:
Do you wish to install the display library for VT52 terminals?:
Respond YES or NO.
You will then receive the next question:
Do you wish to install the display library for VTlOO terminals?:
Answer YES or NO.
You must install at least one of
files for the EDTCAI course to run on your system.
After answering YES to at least one of the
you receive this message:

two

the

two

preceding

library

questions,

Added course EDT, the EDTCAI Primer
If you have upgraded from a previous version of EDTCAI, at this
you will be asked:

point

Do you wish to copy student records from EDTCAI Vl to this
version?:
Answer YES or NO.
If you answer YES, the names of the students will
be displayed as they are copied. When all the names have been copied,
the following will be displayed:
Now that the student records are copied, you may delete the old
records to save disk space.
Do you wish to delete the old student records (Y or N):
Answer YES or NO.

If you answer YES, the following will be displayed:

The old student records have been deleted.
If you answer NO, the following will be displayed:
The old student records have not been deleted.
When the installation of the EDTCAI
receive this message:
Kit installation complete.

4-7

course

completed,

you

will

CHAPTER 5
THE SYSTEM AFTER INSTALLATION

You will want to perform
installed:

several

operations

after

•

Backing up the console TU58 cartridge

•

Performing several methods of bootstrapping

•

Building and copying a system disk.

•

Building a stand-alone BACKUP kit.

your

system

BACKING UP THE CONSOLE MEDIUM
It is important that you have a backup copy of the console medium.
To
back up the console medium,
use
the command
procedure CONSCOPY
contained in the SYS$UPDATE directory.
CONSCOPY copies files from the
TU58 cartridge to an empty scratch directory on a disk.
From the
scratch directory,
the files can be restored
to another
TU58
cartridge.
{The blank TU58 cartridge included in your distribution
kit may be used for this purpose if it was not used during the upgrade
procedure.) To use CONSCOPY, proceed as follows:
1.

Create a scratch directory if one is not
If a directory already exists, make
files.
To create a directory, type:

already available.
sure it contains no

CREATE/DIRECTORY ddcu: [directory name]
For example:

$ CREATE/DIRECTORY DMAl: [WRK.CNSL]
3.

At the DCL prompt ($), enter the following:

$ @SYS$UPDATE:CONSCOPY
4.

You will receive the following question:
Which kit do you want to build (780!750!730):
Answer by typing 750.

5-1

THE SYSTEM AFTER INSTALLATION
5.

A brief description of the SAVE and RESTORE
appear.

operations

You will then be asked whether you want to
your console medium.

SAVE

will

RESTORE

Answer by typing SAVE.
6.

The following will then appear:
Enter Files-11 device and directory (DDCU: [DIR]):
Type in the device code for the disk to be copied
specify the empty directory to contain the files.

and

For example:
DMAl: [WRK.CNSL]
7.

At this point, you will receive the following prompt:
Enter the console device drive (DDCU:):
Answer by typing CSAl:.

Put your console TU58 into the drive on the processor control
panel and press RETURN when ready.

When the files have been copied from the TU58
you will receive this message:
SAVE of your console

5.1.1

medi~~

the

disk,

is complete.

Restoring Files to TU58 Cartridge

To restore files to another TU58 cartridge, proceed as follows:
1.

Invoke CONSCOPY by typing:
$ @SYS$UPDATE:CONSCOPY

You will receive the following question:
Which kit do you want to build (780!750!730):
Answer by typing 750.

A brief description of the SAVE and RESTORE
appear.

operations

You will then be asked whether you want to
your console medium.

SAVE

will

RESTORE

Answer by typing RESTORE.
4.

The following will then appear:
Enter Files-11 device and directory (DDCU: [DIR]):
Type in the device code for
the
directory that contains the files.

5-2

disk

and

specify

the

THE SYSTEM AFTER INSTALLATION
5.

At this point, you will receive the following prompt:
Enter the console device drive (DDCU:):
Answer by typing CSAl:.

Put the scratch TU58 into drive CSAl and
ready.

press

RETURN

When the files have been restored from the disk to the
you will receive this message:

when
TU58,

RESTORE of your console medium is complete.
This newly created TU58 will be your console TU58.
Keep the
as a backup copy.
Press RETURN to mount this new TU58.

5.1.2

original

Reading Command Procedures From Console Media

To read bootstrap command procedures from the console TU58,
you must
first copy the files from the console TU58, using the DXCOPY command
procedure in the directory [SYSUPD].
To
use DXCOPY.COM for
this
purpose, proceed as follows:
1.

Invoke the command procedure by typing:
$ @SYS$UPDATE:DXCOPY

The command
mounted:

procedure

asks

whether

the

console

TU58

Is the system console storage medium mounted (Y/N)?:
Place the console TU58 in the CSAl drive, type NO, and
RETURN, as prompted.
3.

press

The command procedure then asks whether the copy operation is
from the console TU58:
Copy from console medium (Y/N)?:
Type YES to indicate a copy from
default directory.

the

console

TU58

the

Finally, the command procedure requests the name of the file
to be copied from the console TU58.
Type the name of the
file and press RETURN.

You can now read the file from the default directory.

5.2

BOOTING THE SYSTEM AFTER INSTALLATION

During installation, a default bootstrap is used
for simplicity's
sake.
However, once the system has been installed, you can bootstrap
the system in either of the following ways:
•

Conversational - Request that SYSBOOT stop and
allow you
modify the system parameters that configure the system.

5-3

THE SYSTEM AFTER INSTALLATION
•

Nonstop - Allow SYSBOOT to
intervention.

run

completion

without

your

Whether you perform a conversational bootstrap or a nonstop bootstrap,
the following options are available to you:
•

Bootstrap the system directly from the system disk

•

Bootstrap the system using the stand-alone BOOT58
the console TU58 cartridge

5.2.1

program

Rebooting Stopping in SYSBOOT

The system bootstrap program, SYSBOOT.EXE, is the secondary bootstrap
program that loads and configures the system.
Because you can request
that SYSBOOT prompt for commands during the bootstrap operation,
this
procedure
is
known
as a conversational bootstrap operation.
Using
this procedure, you can do the following:
•

Designate the name of the file that contains system
values

parameter

•

Set and show individual parameter values

•

Specify an alternate site-independent start-up procedure

To halt the processor and reboot stopping in SYSBOOT:
1.

Shut down the
procedure:

system

executing

the

following

command

$ @SYS$SYSTEM:SHUTDOWN
This command procedure prompts for
the number of minutes
until
system shutdown, the reason for the shutdown, whether
to spin down the disks, the expected
time when the
system
will
be
restored,
and
whether
automatic reboot should be
enabled.
2.

In response to the statement, "SYSTEM SHUTDOWN COMPLETE - USE
CONSOLE TO HALT SYSTEM," halt the processor and obtain the
console prompt (>>>) by pressing CTRL/P.

Bootstrap the system, using the following command:
>>> B/l ddcu

(dd is the device type, c
is the unit number.)

is the controller designator, and u

When SYSBOOT is ready
follows:

commands,

prompts

%%
SYS BOOT>
The two percent signs (%%) that precede
the
SYSBOOT prompt
indicate a
successful micro verify check.
If the percent
signs do not appear, discontinue the bootstrap operation and
contact your field service representative.
When SYSBOOT prompts, you may use any of the subset of SYSGEN
commands listed in Table 5-1 to examine or modify the system.

5-4

THE SYSTEM AFTER INSTALLATION
The following is an example of the SYSBOOT program:
SYSBOOT> USE CURRENT
SYSBOOT> SET WSMAX 512
SYSBOOT> CONTINUE
In this example 1 the program is told to use the current parameter file
as a
source for values, WSMAX is set to 512, and the bootstrap
operation is continued.
When VAX/VMS announces itself, the new
parameter value you have designated is in use. More information about
these SYSGEN commands can be found in the VAX-11 Utilities Reference
Manual.
Table 5-1: SYSBOOT Commands
Command

Description

CONTINUE

Resumes the bootstrap procedure

DISABLE CHECKS

Inhibits checking of parameter
specified with the SET command

values

ENABLE CHECKS

Permits checking of
parameter
specified with the SET command

values

HELP

Displays a summary of the SYSBOOT commands
at your terminal

SET parameter value

Establishes the
value
generation parameter

SET/STARTUP procedure

Specifies the start-up command
to be executed after SYSBOOT

SHOW

Displays specific parameters

USE

Specifies the parameter file to be used as
a source of values (if a parameter file is
specified, you must specify the entire
file specification)

5.2.2

system

procedure

Nonstop Bootstrap from the System Disk

To perform a bootstrap operation from
stopping in SYSBOOT, proceed as follows:
1.

Shut down the
procedure:

system

the

executing

system
the

disk,

without

following

command

$ @SYS$SYSTEM:SHUTDOWN
2.

In response to the statement, "SYSTEM SHUTDOWN COMPLETE - USE
CONSOLE TO HALT SYSTEM,"
halt the processor by pressing
CTRL/P to obtain the console prompt (>>>), and type the HALT
command.

5-5

THE SYSTEM AFTER INSTALLATION
3.

Type the
format:

console

>>> B

BOOT

command

the

following

command

ddcu

(dd is the device type, c
is the unit number.)

5.2.3

is the controller designator, and u

Rebooting Using the Default Bootstrap

Under normal system operation, you do not need
to
interrupt the
bootstrapping
of the system to type commands to SYSBOOT;
parameter
values have already been established.
To
reboot using
the default
bootstrap, proceed as follows:
1.

Shut down the
procedure:

system

executing

the

following

command

$ @SYS$SYSTEM:SHUTDOWN
2.

In response to the statement, "SYSTEM SHUTDOWN COMPLETE - USE
CONSOLE TO HALT SYSTEM,"
halt the processor by pressing
CTRL/P to obtain the console prompt (>>>), and type the HALT
command.

Either type BOOT or press the
BOOT push button on the
processor control panel.
The processor will attempt to boot
from the device selected by the Boot Device Switch on the
front panel.

Appendix B contains a description of bootstrapping
TUSS.

5.3

from

the

console

BUILDING AND COPYING A VAX/VMS SYSTEM DISK

Occasionally, you may want to build or make a copy of your
system
software.
VAX/VMS provides a command procedure named VMSKITBLD.COM as
part of the system software for the purposes of building and copying a
VAX/VMS operating system.
NOTE
Do not press CTRL/C or CTRL/Y while
running VMSKITBLD.COM unless
you want
the command procedure to terminate.

5.3.1

Building a VAX/VMS System Disk

You can use VMSKITBLD.COM to build a VAX/VMS system binary disk.
For
example,
if you have a mixed-disk system (with RK07 and either RP06,
RP07, RM03, RMOS, RA60, RASO, or RASl disks, but no magnetic
tape
drives),
you can use VMSKITBLD.COM to transfer your VAX/VMS system
from an RK07 disk cartridge to a
larger,
faster
RP06,
RP07,
RM03,
RMOS, RA60, RASO, or RASl disk.
Before you can use VMSKITBLD.COM to build a VAX/VMS system
(on an
RP06,
for example)
you must boot your system, as described at the
beginning of this chapter. With this RK07 system running, proceed
as
fol lows:
5-6

THE SYSTEM AFTER INSTALLATION
1.

Establish the following default directory:
$ SET DEFAULT SYS$UPDATE

Place either an RP06, RP07, RM03, RM05, RA60, RASO,
or RA81
disk on an appropriate drive and place it online.
This will
be the target disk in the system building procedure.

Type the following command to initiate the
system:

building

the

$ @VMSKITBLD
5.

Supply the needed information about
disks as prompted.

the

source

and

target

You then receive the following query:
Is this a BUILD, ADD, or COPY operation?:
Answer by typing BUILD.
NOTE
The BUILD option destroys all previous
information on the target disk before it
builds the system.
Continuation of the system disk-building procedure is indicated by the
display of messages at your
terminal.
These messages either (1)
prompt you for information needed to complete the copy operation, or
(2)
inform you of the current status of the building procedure.
Each
response should be followed by pressing the RETURN key.
For example:
Enter mounted source disk name (DDCU:): SYS$SYSDEVICE:
Enter SOURCE disk top level system directory [default
SYSO]:
Enter target disk name (DDCU:): DRAO:
Enter the target disk's label [default= VAXVMSRL3]:
Enter TARGET disk top level system directory [default = SYSO]:
It will be necessary to initialize the target disks(s).
Is the target disk, DRAO:, ready to be initialized? (Y/N): Y
DRAO: allocated
%MOUNT-I-MOUNTED, VAXVMSRL3
mounted on DRAO:
Create directory entries on the target disk.
Copy the system executive files.
Copy the system library files.
Copy the system message files.
Copy the system manager files.
Copy the system update command files.
Copy the system EXE files.
Copy the system help files.
Write a bootblock.
Copy BLISS require files.
Copy coding examples.
Copy the EDTCAI files.
Copy the UETP files.

5-7

THE SYSTEM AFTER INSTALLATION
VMSKITBLD.COM informs you when the system disk is built by sending the
following message to your terminal:
Kit is complete.
At this point, the disk contains all the required VAX/VMS files for a
complete
system.
The
system
can be properly configured by
bootstrapping using the default parameters and then using the AUTOGEN
procedure to configure the target system.
To boot the system with the default parameters invoke the GEN
of the boot command file by typing:

version

>» B/l ddcu
When you have the SYSBOOT prompt (SYSBOOT>)

type the following:

SYSBOOT> USE DEFAULT
SYSBOOT> CONTINUE
The system will boot at this point. You can then log
in as system
manager and
run the AUTOGEN procedure described in Chapter 12 of the
VAX/VMS System Management and Operations Guide.

5.3.2

Copying a VAX/VMS System Disk

You can also use VMSKITBLD.COM to copy the files of the VAX/VMS system
disk to a target disk that already contains a valid VAX/VMS system.
The copy operation modifies only system files;
it leaves all user
files intact.
Before you can use VMSKITBLD.COM to copy one system disk to another,
your VAX/VMS system must be running
and the source disk that you
intend to copy must be mounted.
Often, this source disk is the system
disk from which the system was booted.
Proceed as follows to copy the
source disk to a target disk:
1.

Establish the following default directory:

$ SET DEFAULT SYS$UPDATE
3.

Place the target disk on an appropriate drive.

Type the following command to initiate the copy operation~
$ @VMSKITBLD

Supply the information needed about
disks as prompted.

the

source

and

target

You then receive the following query:
Is this a BUILD, ADD, or COPY operation?
Answer by typing COPY.
Continuation of the copy operation is indicated by the display of
messages at your terminal.
These messages either (1) prompt you for
information needed to complete the copy operation, or (2)
inform you
of the current status of the copy operation (see the example in
Section 5.3.1).
5-8

THE SYSTEM AFTER INSTALLATION
VMSKITBLD.COM informs you when the copy operation
sending the following message to your terminal:

complete

Kit is complete.
At this point, the disk is ready to be bootstrapped.

5.4

BUILDING A STAND-ALONE BACKUP KIT

If you received your distribution kit on RK07 or RA60 disk,
the
stand-alone Backup Utility is contained on that disk.
In order to
have a kit for
stand-alone operations, you must copy stand-alone
BACKUP from
the disk to TU58 cartridges.
To create a stand-alone
BACKUP kit, proceed as follows:
1.

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

You will receive this request:
Specify target device (DDCU:):
Respond by typing the device name of the console drive:
CSAl:

The following message will appear:
Please place the first TU58 in drive CSAl:.
Press return when ready to continue:

After you have placed the TU58
in the
RETURN, you will receive these messages:

drive

and

pressed

%MOUNT-I-MOUNTED, STABACKUPA mounted on CSAl:
%CREATE-I-CREATED, CSAl: [SYSEXE] created
If you are working at a console terminal, or if your terminal
is enabled as an operator's terminal, you will also receive
the following messages:
%0PCOM, (DD-MMM-YYYY HH:MM:SS), message from user SYSTEM
%SYSGEN-I-WRITECUR, CURRENT system parameters
modified by process ID <ID number> into
file SYS$SYSROOT:[SYSUPD]SYS.EXE;l
These messages will be followed with a
list of the
files
copied.
When you have received
the complete list of the
files copied, the following message will appear:
Please place the second TU58 in drive CSAl:.
Press return when ready to continue:
6.

After you have placed
the second TU58
in the
pressed RETURN, you will receive these messages:
%MOUNT-I-MOUNTED, STABACKUPB mounted on CSAl:
%CREATE-I-CREATED, CSAl: [SYSEXE] created

5-9

drive

and

THE SYSTEM AFTER INSTALLATION

They will be followed with a list of the files copied.
you will receive the following message:

Then

Kit is complete.
Please replace the console medium.
Press return when ready to continue.
Replace the console TU58 and press RETURN.
At this point, you
BACKUP kit.

have

completed

5-10

building

stand-alone

APPENDIX A
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 are cataloged in ten directories.
The names of
the directories and descriptions of their contents follow.
1.

[SYS CBI]
This directory is reserved for EDTCAI files.

(SYS ERR]
This directory
(ERR LOG. SYS) •

reserved

for

the

error

log

file

As shown in Table A-1, this directory contains commonly
executable images of the VAX/VMS operating system.

used

[SYS EXE]

[SYSHLP]
As shown in Table A-2, this directory contains text libraries
for the HELP utility and other components.
Table A-8 lists
the
contents
of
the
subdirectory,
(SYSHLP.EXAMPLES].
This subdirectory contains sample driver
programs, user-written system service programs,
and other
source code examples of interest.

(SYS LIB]
As shown in Table A-3, this directory contains various macro
and object libraries as well as other files used for general
reference.

(SYSMAINT]
This directory is reserved
programs.

for

system

hardware

diagnostic

(SYSMGR]
As shown in Table A-4, this directory contains files used
in
managing the operating system. This directory is the default
directory for the system manager's account.

(SYSMSG]
As shown in Table A-5, this directory contains system message
text files.

A-1

FILES OF THE VAX/VMS SYSTEM
9.

[SYS TEST]
As shown in Table A-6, this directory contains files used
run the User Environment Test Package (UETP).

10.

(SYS UPD]
As shown in Table A-7, this directory contains files used
applying system updates.
Table A-1:

Files Contained in Directory [SYSEXE]

File Name

Description

ACC.EXE
ANALYZOBJ. EXE
ANALYZRMS. EXE
AUTHORIZE.EXE
AUTOGEN.PAR
BACKTRANS.EXE
BACKUP.EXE
BAD.EXE
BADBLOCK. EXE
BCK.EXE
BOOT58.EXE
BOOTBLOCK.EXE
CANCEL.EXE
CHECKSUM. EXE
CHKSUM. CLD
CLEDITOR.EXE
CNDRIVER.EXE
CNV.EXE
CNVACC. EXE
CONFIG.DAT
CON INT ERR. EXE
CONVERT. EXE
COPY.EXE
CRDR IVER. EXE
CREATE.EXE
CREATEFDL.EXE
CRF.EXE
DBDR IVER. EXE
DCL.EXE
DCLDEF. STB
DDDRIVER.EXE
DEF.EXE
DELETE.EXE
DFN. EXE
DIFF.EXE
DIRECTORY.EXE
DISKQUOTA. EXE
DISMOUNT.EXE
DLDRIVER.EXE
DMDRIVER. EXE
DMP. EXE
DQDRIVER. EXE
DRDR IVER. EXE
DSCl. EXE

Accounting Utility
ANALYZE/IMAGE and ANALYZE/OBJECT image
ANALYZE/RMS FILE image
User authorTzation program
Parameter file for the Autogen command procedure
Back translator of DCL into MCR commands
Backup Utility
Bad Block Locator Utility
Dynamic bad block Files-11 ACP subprocess
RMS-11 backup utility
Reserved for future use
Reserved for future use
CANCEL command
Used during installation of VAX/VMS updates
Used during installation of VAX/VMS updates
Command Definition Utility
DECnet CI datalink driver
RMS-11 file conversion utility
Convert V3.0 account file to V2.0 format
Data file for configuration
Connect-to-Interrupt driver
Convert Utility
File copy utility
Card reader driver
File and directory creation utility
CREATE/FDL image
Compatibility mode cross-reference utility
RPOS and RP06 disk driver
Command interpreter
Global definitions for DCL structures
TU58 driver
RMS-11 interactive file definition utility
File deletion/purge utility
RMS-11 noninteractive file definition utility
File compare utility
Directory utility
Disk Quota Utility
Volume dismount utility
RL02 disk driver
RK07 disk driver
RSX-11 File dump utility
RB730 driver
RM03 disk driver
Files-11 Structure Level 1 disk save and
compress utility
(continued on next page)

A-2

FILES OF THE VAX/VMS SYSTEM
Table A-1

(Cont.):

Files Contained in Directory [SYSEXE]

File Name
DSC2.EXE
DSP~ EXE
DTR.COM
DTRECV.EXE
DTSEND.EXE
DUDRIVER. EXE
DUMP. EXE
DXDRIVER. EXE
DYDRIVER.EXE
DZ DRIVER. EXE
EDF. EXE
EDI.EXE
EDT.EXE
ERRFMT.EXE
EVL.EXE
EVL.COM
FllAACP. EXE

FllBACP. EXE
FAL.COM
PAL.EXE
FLX.EXE
HEXZAP. EXEl
HLD. COM
HLD.EXE
IFL. EXE
IMGDEF.STB
INILOA. EXE
INIT. EXE
INPSMB. EXE
INSTALL. EXE
JBCSYSQUE.EXE
JOBCTL.EXE
LADRIVER. EXE
LA LOAD. EXE
LALOADER.EXE
LBR. EXE
LCDRIVER. EXE
LIBRARIAN.EXE
LINK. EXE
LOGINOUT.EXE
LPDRIVER.EXE
MAC.EXE
MACR032.EXE
MAIL. EXE
MAIL.COM
MAILEDIT. COM
MBXDRIVER.EXE
MCR.EXE

Description
Files-11 Structure Level 2 disk save and
compress utility
RMS-11 file attribute display utility
DTRECV.EXE server initiating procedure
DTSEND server
DECnet logical links test program
UDA disk driver
DUMP u t il i t y
RXOl console floppy diskette driver
RX02 floppy diskette driver
DZll port driver
File definition language editor
RSX-llM text editor
EDT text editor
Error logging facility
DECnet event logging program
Command file used by DECnet error logging
Files-11 Structure Level 1 ancillary
control process
Files-11 Structure Level 2 ancillary
control process
FAL start-up procedure
DECnet file access listener
File Transfer Utility
Hexadecimal image patching utility
Command procedure used by HLD.EXE
Down line task loading program
RMS-11 utility index load program
Global definitions for image activator
structures
System initialization program
Disk device initialization utility
Card reader input symbiont
Utility that installs known images
Queuing facility
Job controller/symbiont manager
LPA-11 driver
Accepts commands from or sends requests to
LALOADER to load LPA-11 microcode
Loads LPA-11 microcode upon power recovery
or upon request from LALOAD
RSX-llM librarian
DMF-32 lineprinter driver
Librarian Utility
Linker
Login/logout utility
Line printer driver
MACR0-11 assembler
VAX-11 MACRO assembler
Mail Utility
Command procedure used by DECnet mail
Default MAIL editing command procedure
Shared memory mailbox driver
MCR command interpreter

1. Not supported by DIGITAL.
(continued on next page)

A-3

FILES OF THE VAX/VMS SYSTEM
Table A-1

(Cont.):

Files Contained in Directory [SYSEXE]

File Name

Description

MERGE.EXE
MESSAGE.EXE
MIRROR. COM
MIRROR. EXE
MONITOR.EXE
MP.EXE
MP.STB
MTAAACP.EXE
NCP. EXE
NETACP.EXE
NETDEF.STB
NETDRIVER.EXE
NML.COM
NML. EXE
NOTICE.TXT

Merge Utility
Message compiler
MIRROR start-up procedure
DECnet node loopback server
Monitor Utility
VAX-11/782 multiprocessing code
Symbol table for MP.EXE
Magnetic tape ancillary control process
Network control program
DECnet ancillary control process
Symbol table for network definition
DECnet logical link driver
NML server start-up procedure
DECnet network management listener
Text file that can contain announcements to
system users
System shutdown utility
Operator communications utility
CI780 port driver
System paging file
Data file for parameter values
RSX-llM object module patch utility
VAX-11 image file patch utility
PHONE start-up procedure
Phone Utility
RSX-llM peripheral interchange utility
Print symbiont
CI UDA port driver
Queue managing utility
CONVERT/RECLAIM image
Remote device ACP
File rename utility
Message broadcasting facility
Operator request facility
Record Management Services
Global definitions for VAX-11 RMS structures
File sharing utility program
RMS-11 file restoration utility
RSX-llM application migration executive main
program
Utility that writes an RT-11 bootstrap on disk
Remote terminal command interface
Remote terminal driver
Facility that runs detached images
Text formatting utility
Symbol table for loadable routines
Loadable routines used by SCS
System Dump Analyzer Utility
File search utility
DECnet downline secondary loader for DMCll
DECnet downline secondary loader for DPll
DECnet downline secondary loader for DPll
DECnet downline secondary loader for DQll
DECnet downline secondary loader for DUPll
DECnet downline secondary loader for DUVll
SET command processor

OPCCRASH. EXE
OPCOM. EXE
PADRIVER. EXE
PAGEFILE. SYS
PARAMS. DAT
PAT. EXE
PATCH. EXE
PHONE. COM
PHONE. EXE
PIP.EXE
PRTSMB.EXE
PUDRIVER.EXE
QUEMAN.EXE
REC LA IM. EXE
REMACP.EXE
RENAME.EXE
REPLY.EXE
REQUEST.EXE
RMS.EXE
RMSDEF.STB
RMSSHARE.EXE
RST.EXE
RSX.EXE
RTB.EXE
RTPAD.EXE
RTTDRIVER.EXE
RUNDET.EXE
RUNOFF. EXE
SCSDEF.STB
SCSLOA. EXE
SDA. EXE
SEARCH.EXE
SECDMC.SYS
SECDP.SYS
SECDQ.SYS
SECDU.SYS
SECDUP.SYS
SECDUV.SYS
SET.EXE

{continued on next page)

A-4

FILES OF THE VAX/VMS SYSTEM
Table A-1

(Cont.):

Files Contained in Directory [SYSEXE]

File Name
SETPO.EXE
SHOW. EXE
SHUTDOWN. COM
SLP.EXE
SORT32.EXE
SOS.EXE
SRT.EXE
STABACKUP.EXE
STARTUP.COM
STARTUP.MIN
STASYSGEN.EXE
STOPREM.EXE
SUBMIT. EXE
SUMS LP. EXE
SWAPFILE.SYS
SYE.EXE
SYS. EXE
SYS.MAP
SYS.STB
SYSBOOT.EXE
SYSDEF.STB*
SYS DUMP. DMP
SYSGEN.EXE
SYS INIT. EXE
SYSLOA730. EXE
SYSLOA750.EXE
SYS LOA 780. EXE
SYSUAF. DAT
SYSUAF. RL2
TCX. EXE
TECO. EXE l
TERDMC. SYS
TERDP.SYS
TERDQ.SYS
TERDU.SYS
TERDUP.SYS
TERDUV.SYS
TFDRIVER.EXE
TKB. EXE
TMDRIVER. EXE
TOC. EXE
TSDRIVER. EXE
TTDRIVER.EXE
TTRDVFY. EXE
TYPE.EXE
UFD. EXE
UNLOCK. EXE
VERIFY.EXE
VMB. EXE
VMOUNT. EXE
VMSHELP.EXE
WRITEBOOT.EXE
XADRIVER. EXE

Description
SET MESSAGE command processor
SHOW command processor
System shutdown command procedure
RSX-llM source file editing utility
SORT command processor
SOS text editor
SORT-11 utility
Stand-alone Backup Utility
System start-up command procedure
System minimum start-up command procedure
Stand-alone System Generation Utility
Stop REMACP utility
Batch job submission utility
Source file editor
System swap file
Utility that formats the error log file
Operating system image file
Map of the operating system
Global symbol table of operating system
System bootstrap utility
Global definitions for executive structures
System dump file
System Generation and Configuration Utility
Operating system initialization image
VAX-11/730 system image file
VAX-11/750 system image file
VAX-11/780 system image file
User authorization data file
Unmodified copy of SYSUAF.DAT
Runoff indexing utility
TECO text editor
DECnet downline tertiary loader
DECnet downline tertiary loader
DECnet downline tertiary loader
DECnet downline tertiary loader
DECnet downline tertiary loader
DECnet downline tertiary loader
TU78 driver
RSX-llM task builder
Magnetic tape driver
Runoff table of contents utility
TSll Magnetic tape driver
Terminal driver
Auxiliary terminal driver module
Type utility
User file directory creation utility
File unlock utility
ANALYZE/DISK STRUCTRURE image
VAX/VMS primary bootstrap
Volume mount utility
Help Utility
System volume bootblock writing utility
Reserved for future use

1. Not supported by DIGITAL.
(continued on next page)

A-5

FILES OF THE VAX/VMS SYSTEM
Table A-1 (Cont.):

Files Contained in Directory [SYSEXE]

File Name

Description

XDDRIVER.EXE
XFDRIVER. EXE
XFLOADER. EXE
XGDRIVER. EXE
XMDRIVER. EXE

DECnet DMP-11 datalink driver
DR32 system interconnect interface driver
DR32 microcode loader utility
DECnet DMF datalink driver
DMC-11 Synchronous Communications Line Interface
driver
DUP-11 device driver
DMF32 asynchronous port driver
RSX-llM task/file octal patch utility

XWDRIVER. EXE l
YCDRIVER. EXE
ZAP.EXE

1. Not supported by DIGITAL.
Table A-2:

Files Contained in Directory [SYSHLP]

File Name

Description

ANLRMSHLP.HLB
DEBUG. HLB
DISKQUOTA.HLB
EDFHLP. HLB
EDTHELP.HLB
EDTVTlOO. DOC
EDTVT 52. DOC
EXAMPLES.DIR
HELPLIB. HLB
INSTALHLP. HLB
MAILHELP.HLB
NC PHELP. HLB
PATCHHELP. HLB
PHONEHELP. HLB
SDA. HLB
SYSGEN.HLB
TECO. HLB
UAFHELP.HLB
VMSTLRHLP. HLB

Help library for ANALYZE/RMS FILE command
Debugger help library
Help library for Disk Quota Utility
Help library for FDL
EDT help library
EDT keypad layout for VTlOO
EDT keypad layout for VT52
Examples directory
Default (DCL) help library
Help library for Install Utility
Mail Utility help library
Help library for NCP
Help library for PATCH
Help library for PHONE
System Dump Analyzer help library
Help library for SYSGEN
TECO help library
Help library for user authorization file
Help library for the tailoring facility

Table A-3:

Files Contained in Directory [SYSLIB]
Description

File Name
CDDSHR.EXE
CLIMAC.REQ
CONVSHR.EXE
CRFSHR.EXE
DCLTABLES. EXE
DEBUG.EXE
DELTA. EXE
DELTA. OBJ

Dummy CDD image for layered products
Structure definitions for BLISS programs
interfacing with the command language
interpreter
·
CONVERT, CONVERT/RECLAIM shareable image
Cross-reference shareable image
DCL command tables
VAX/VMS debugging facility
DELTA multimode debugging tool image
Alternate VAX/VMS debugging tool
(continued on next page)

A-6

FILES OF THE VAX/VMS SYSTEM
Table A-3 (Cont.):

Files Contained in Directory [SYSLIB]

File Name

Description

DISMNTSHR.EXE
FDLSHR.EXE
FORDEF.FOR
FORIOSDEF. FOR
IMAGELIB. OLB
LBRSHR. EXE
LIB. MLB
LIB. REQ

DISMOUNT shareable image
FDL parsing shareable image
FORTRAN INCLUDE file: FOR$ symbols
FORTRAN INCLUDE file: IOSTAT error codes
System default shareable image library
Librarian shareable image
Operating system macro library
Structure definitions of executive internals
for use by BLISS programs
FORTRAN program utility INCLUDE files
MCR command tables
MOUNT shareable image
FORTRAN INCLUDE files: MATH$ symbols
DECnet management listener shareable image
RSX-llM debugging tool
RMS-11 sample overlay description
RMS-11 overlay descriptor
RMS-11 overlay descriptor
RMS-11 overlay descriptor
RMS-11 object library
RMS-11 macro library
RSX-llM compatibility mode macro library
Shareable image of RSX~llM application
migration executive
Shareable image of RSX-llM application
migration executive
VMSRTL.EXE vector (reserved for DIGITAL use)
RTL terminal screen procedures shareable image
FORTRAN program utility INCLUDE files
System macro library
System object library and Run-Time
Library
User interface structures for use by BLISS
programs
Source update merge shareable image
RSX-llM object library
Structure definitions for BLISS programs using
TPARSE
VAX/VMS error traceback facility
Run-Time Library shareable image
Definitions available for programs using DR780
support routines

LIBDEF. FOR
MCRTABLES.EXE
MOUNTSHR.EXE
MTHDEF.FOR
NM LS HR. EXE
ODT. OBJ
RMSll. ODL
RMSllS. ODL
RMSllX. ODL
RMS12X.ODL
RMS LIB. OLB
RMSMAC.MLB
RSXMAC.SML
RSXSHR.EXE
RSXUSR.EXE
RTLVECTOR.OBJ
SCRSHR. EXE
SIGDEF.FOR
STARLET.MLB
STARLET.OLB
STARLET.REQ
SUMSHR. EXE
SYS LIB. OLB
TPAMAC.REQ
TRACE.EXE
VMSRTL.EXE
XFDEF. FOR

Table A-4:

Files Contained in Directory [SYSMGR]

File Name
ACCOUNTING. DAT
CHARTYPE.DAT
FORMSTYPE. DAT
LPAllSTRT. COM

Description
Accounting data file
Line printer characteristics for print
symboint
Line printer f.orms description for print
symbiont
LPAll site-specific start-up command procedure
(continued on next page)

A-7

FILES OF THE VAX/VMS SYSTEM
Table A-4 (Cont.):

Files Contained in Directory [SYSMGR]

File Name

Description

NETICP. COM 1
OPERATOR.LOG
RTTLOAD.COM
STARTNET.COM
SYSHUTDWN. COM

DECnet checkout procedure
Operator message log file
Remote terminal loader
DECnet start-up procedure
Site-specific system shutdown command
procedure
Site-specific system start-up command
procedure
Invoked at start-up to install known images
Data file for VMSIMAGES.COM

SYSTARTUP.COM
VMS IMAGES. COM
VMS IMAGES.DAT

1. Requires DECnet-VAX optional product for use.
Table A-5:

Files Contained in Directory [SYSMSG]

File Name
QIOSYM. MSG
SOS.HLP
SYSMSG.EXE
SYSMSG.TLB
Table A-6:

Description
RSX-llM compatibility mode QIO message file
Help file for SOS text editor
System message file
System message file text library
Files Contained in Directory [SYSTEST]

File Name

Description

APPEND.PIP
DMPASRC. DMP
DMPBYOC. DMP
DMPDATA. DMP
DM PDCWD. DM P

Tests PIP append function
Master file to test ASCII mode in DMP
Master file to test byte octal format in DMP
Good input file for DMP test
Master file to test decimal word format in
DMP
Macro to test LBR utility
Macro to test LBR utility
Macro to test LBR utility
Object module to test LBR utility
Object module to test LBR utility
Object module to test LBR utility
Tests PAT utility
Patch file to test PAT utility
Good input file for PIP test
Tests FLX utility
Tests for event flag services and $SETEXV
service
Tests for event flag services
Tests for logical name services
Tests for time services
Tests for process control services
Tests for process control services
Tests for process control services

MCLBRl. MAC
MCLBR2.MAC
MCLBR3.MAC
OBJLBRl. OBJ
OBJLBR2. OBJ
OBJLBR3. OBJ
PATCHED. PAT
PATCHPAT.OBJ
PIPDATA.PIP
RANDOM.FLX
SATSSFOl. EXE
SATSSF02.EXE
SATSSF03.EXE
SATSSF04.EXE
SATSSFOS.EXE
SATSSF06.EXE
SATSSF07.EXE

(continued on next page)

A-8

FILES OF THE VAX/VMS SYSTEM
Table A-6 (Cont.):

Files Contained in Directory [SYSTEST]

File Name
SATSSF08.EXE
SATSSF09.EXE
SATSSFlO.EXE
SATSSFll. EXE
SATSSF12.EXE
SATSSF 13. EXE
SATSSF14.EXE
SATSSF15.EXE
SATSSF16.EXE
SATSSF17.EXE
SATSSF18.EXE
SATSSSOl. EXE
SATSSSOS.EXE
SATSSS07.EXE
SATSSS08.EXE
SATSSS09.EXE
SATSSSlO.EXE
SATSSS22.EXE
SATSSS26.EXE
SATSSS30.EXE
SATSSS35.EXE
SATSSS36.EXE
SATSSS37.EXE
SATSSS38.EXE
SATSSS39.EXE
SATSSS40.EXE
SATSSS41. EXE
SATSSS42.EXE
SATSSS43.EXE
SATSSS44.EXE
SATSSS45.EXE
SATSSS46.EXE
SATSSS47.EXE
SATSSSSO.EXE
SATSSS52.EXE
SATSSS53.EXE
SATSSS54.EXE
SATSSSSS.EXE
SATSSS56.EXE
SATSSS60.EXE
SATSSS61. EXE
SATSSS70.EXE
SATSSS71. EXE
SATSSS72. EXE
SATSSS73.EXE
SATSSS74.EXE
SATSSS78.EXE
SATSSS79.EXE
SATSSS80.EXE
SATSSS81.EXE
SATSSS82.EXE
SATSSS83.EXE

Description
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
services
Tests for
services
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
services
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for
disabled)
Tests for
Tests for
Tests for
Tests for
Tests for
Tests for

$CMEXEC and $GETMSG services
I/O services
send system services
I/O services
memory management services
memory management services
memory management services
handler services and $ADJ
$FAO services and $SNDERR
$INPUT, $OUTPUT, $QIO, and $QIOW
$CREPRC, $SETPRV, and $UNWIND
I/O services
send message services
$CREMBX, $DELMBX services
$BRDCST service
$FAO, $FAOL SERVICES
$GETMSG and $PUTMSG services
condition handling services
timer and AST services
logical name services
$CREPRC service
$DELPRC service
$SUSPND service
$RESUME service
$HIBER service
$WAKE service
$EXIT service
$FORCEX service
exit- and change mode-handling
$SETPRN service
$SETPRI service
$SETRWM service
$SETPRV service
$ASCEFC, $DACEFC services
$DLCEFC service
$SETEF service
$CLREF service
$READEF service
wait services
time conversion services
$SCHDWK, $CANWAK services
$EXPREG service
$CNTREG service
$CRETVA service
$DELTVA service
global section services (currently
$LKWSET, $ULWSET services
$LCKPAG, $ULKPAG services
$PURGWS service
$ADJWSL service
$SETPRT service
$SETSWM service
(continued on next page)

A-9

FILES OF THE VAX/VMS SYSTEM
Table A-6 (Cont.):

Files Contained in Directory [SYSTEST]

File Name

Description

SATSSS90.EXE
SATSSS91.EXE
SATSUTOl.EXE

Tests for change mode services
Tests for $ADJSTK service
Utility module for SATSSFOS, SATSSF18, and
SATSSS35
Utility module for SATSSSSO
Utility module for SATSSS38
Utility module for SATSSS40
Utility module for SATSSS61
Utility module for SATSSS37, SATSSS45
Utility module for SATSSS41
Utility module for SATSSS52
Utility module for SATSSS56
Utility module for abort feature
Utility module for SATSSS42
Utility module for SATSSS36
Input data to test SLP utility
Good output file for SLP test
Good output file for SLP test
Master data file for VAX-11 SORT test
Master data file for VAX-11 SORT test
Master data file for VAX-11 SORT test
Master data file for VAX-11 SORT test
Input data file for VAX-11 SORT tests
Tests FLX utility
Test for QIO, QIOW (RSX-llM directive)
Test for QIO, QIOW {RSX-llM directive)
Test for event flags (RSX-llM directive)
Test for GET TIME, MARK TIME, RUN (RSX-llM
directive)
Test for GET TIME, MARK TIME, RUN (RSX-llM
directive)
Test for MCR command line, specify SST vector
table (RSX-llM directive)
Test for AST services (RSX-llM directive)
Test for SUSPEND, RESUME (RSX-llM directive)
Test for SUSPEND, RESUME (RSX-llM directive)
Test for ABORT, EXIT-IF (RSX-llM directive)
Test for ABORT, EXIT-IF {RSX-llM directive)
Test for ASSIGN LUN, GET LUN {RSX-llM
directive)
Test for CANCEL SCHEDULED requests (RSX-llM
directive)
Test for CANCEL SCHEDULED requests (RSX-llM
directive)
Test for CANCEL SCHEDULED requests {RSX-llM
directive)
Test for CANCEL MARK TIME request (RSX-llM
directive)
Test for CANCEL MARK TIME request (RSX-llM
directive)
Test for GET TASK PARAMS, REQUEST, RUN
(RSX-llM directive)
Test for GET TASK PARAMS, REQUEST, RUN
{RSX-llM directive)
Main script for compatibility mode utility
tests

SATSUT04.EXE
SATSUTOS. EXE
SATSUT06.EXE
SATS UT07. EXE
SATSUT08.EXE
SATSUT09.EXE
SATS UT 10. EXE
SATSUTll. EXE
SATSUT12.EXE
SATSUT13. EXE
SATSUT14.EXE
SLPDATA.SLP
SLPLIST. SLP
SLPOUT.SLP
SMFILEl. DAT
SMFILE2. DAT
SMFILE3. DAT
SMFILE4. DAT
SORT.DAT
SORTED.FLX
TSTOlA. EXE
TSTOlB.EXE
TST02A.EXE
TST03A.EXE
TST03B.EXE
TSTOfiA.EXE
TST07A.EXE
TSTllA. EXE
TSTllB. EXE
TST12A.EXE
TST12B.EXE
TST15A.EXE
TST16A.EXE
TST16B.EXE
TST16C.EXE
TSTl 7A. EXE
TSTl 7B. EXE
TST20A.EXE
TST20B.EXE
UETCOMPOO. COM

(continued on next page)

A-10

FILES OF THE VAX/VMS SYSTEM
Table A-6 (Cont.):

Files Contained in Directory [SYSTEST]

File Name

Description

UETCOMPOO. DAT
UETCOMP02. COM

Data file for compatibility mode utility test
Main script for RSX-llM executive directive
test
DMC and DMR test file
Data file for SOS test
Commands for SOS test
Known good data after SOS editing
Disk device test
DMP and DMF32 test file
Command procedure for DECnet test
Data file for DECnet test
DRllW device test
DR780 device test
FORTRAN data file used by UETFORTOl
Compiled version of UETFORTOl for load test
Compiled version of UETFORT02 for load test
Compiled program for load test
Gets VAX/VMS configuration and builds
UETINIDEV. DAT
Quick checks all devices for testability
_ Controls load test with various numbers
of users

UETCOMSOO. EXE
UETCSOSOl.DAT
UETCSOS02.CMD
UETCSOS03.DAT
UETDISKOO.EXE
UETDMPF 00. EXE
UETDNETOO.COM
UETDNETOO.DAT
UETDRlWOO.EXE
UETDR7800.EXE
UETFORTOl. DAT
UETFORT97.EXE
UETFORT98.EXE
UETFORT99.EXE
UETINITOO. EXE
UETINITOl. EXE
UETLOADOO.DAT
UETLOAD02. COM

User script for load test

UETLOAD03. COM
UETLOAD04. COM
UETLOADOS. COM
UETLOAD06. COM
UETLOAD07.COM
UETLOAD08.COM
UETLOAD09.COM
UETLOADlO.COM
UETLOADl 1. COM
UETLOCKOO.EXE
UETLPAKOO.EXE
UETMA7800.EXE
UETMEMYOl. EXE
UETNATVOO.DAT
UETNETSOO.EXE
UETNRMSOO. COM
UETNRMSOO. DAT
UETNRMSOl.EXE
UETNUTLOO.DAT
UETNUTLOO. COM
UETP. COM
UETPHASOO.EXE
UETSSMMOO.EXE
UETSUPDEV.DAT
UETTAPEOO.EXE
UETTTYSOO.EXE

User script for load test
User script for load test
User script for load test
User script for load test
User script for load test
User script for load test
User script for load test
User script for load test
User script for load test
Local lock manager test file
LPAll-K test file
MA 780 test file
Tests high page faulting rates in load test
Script that runs VAX/VMS system service tests
DECnet counter test file
Main script for VAX-11 RMS tests
VAX-11/RMS test data file
Test program to exercise VAX-11 RMS functions
Native mode utility data file
Native mode utilities command procedure
Main command procedure for entire UETP
Phase controller test file
Memory management system service test file
Supported device data file
Tests magnetic tapes on one controller
Tests terminals for one controller

A-11

FILES OF THE VAX/VMS SYSTEM
Table A-7:
File Name
AUTOGEN.COM
BLISSREQ.TLR
BOOTBLDR.COM
BOOTUPD.COM
CONSCOPY.COM
DECNET.TLR
DEVELOP. TLR
DXCOPY. COM
EXAMPLES. TLR
FILETOOLS. TLR
HELP.TLR
LIBRARY. TLR
LINE PAGE. COM
LINE PAGE. DAT
MANAGER.TLR
MISCTOOLS.TLR
OBSOLETE. TLR
QUEUES. TLR
REQUIRED. TLR
RSX.TLR
SETDEFBOO.COM
STABACKIT.COM
SWAPFILES. COM
TEXTTOOLS.TLR
UETP.TLR
VMSINSTAL. COM
VMSKITBLD. COM
VMSKITBLD. DAT
VMSTAILOR.COM
VMSUPDATE.COM

Files Contained in Directory [SYSUPD]
Description
Command procedure to determine parameter values
List of files in the BLISS tailoring group
Multiprocessing console floppies command
procedure
Command procedure that updates VAX/VMS bootstrap
file on console floppy diskette
Command procedure that copies console floppy
diskette
List of files in the DECnet tailoring group
List of files in the DEVELOP tailoring group
Command procedure that copies files from console
floppy diskette and restores files to floppy
diskette
List of files in the EXAMPLE tailoring group
List of files in the TOOLS tailoring group
List of files in the HELP tailoring group
List of files in the LIBRARY tailoring group
Command procedure to change number of lines per
page
Datafile used by LINEPAGE.COM
List of files in the MANAGER tailoring group
List of files in the MISCTOOLS tailoring group
List of files in the OBSOLETE tailoring group
List of files in the QUEUES tailoring group
List of files in the REQUIRED tailoring group
List of files in the RSX tailoring group
Command procedure that sets default boot command
file
Command procedure that builds stand-alone BACKUP
to media
Command procedure that creates swapping, paging,
and system dump files of appropriate size for
system being installed
List of files in the TEXTTOOLS tailoring group
List of files in the UETP tailoring group
Command procedure to install EDTCAI and
maintenance updates
Command procedure that builds and copies VAX/VMS
distribution disk
List of files in VAX/VMS system that drives
VMS KI TB LD. COM
Tailoring facility command procedure (supported
only on VAX-11/730)
System update command procedure

A-12

FILES OF THE VAX/VMS SYSTEM
Table A-8:
File Name
ADDRIVER.MAR
CONNECT. COM
DRCOPY.PRM
DRCOPYBLD. COM
DRMAST.MAR
DRMASTER.FOR
DRS LAVE. FOR
DRSLV.MAR
GB LS EC UF 0. MAR
LABCHNDEF. FOR
LAB IO. OPT
LAB IOACQ. FOR
LAB roe IN. MAR
LAB IOC IN. OPT
LAB IOCOM. FOR
LABIOCOMP. COM
LABIOCON. FOR
LAB IO LINK. COM
LABIOPEAK .. FOR
LABIOSAMP.FOR
LAB IOSEC. FOR
LABIOSTAT. FOR
LABIOSTRT. COM
LABMBXDEF. FOR
LBRDEMO. COM
LBRDEMO. FOR
LBRMAC.MAR
LPATEST.FOR
LPMULT. B32
PEAK.FOR
SCRFT.MAR
TDRIVER.MAR
TESTLABIO. FOR
USSDISP. MAR
USS LINK. COM
USSTEST.MAR
USSTSTLNK. COM
XADRIVER. MAR
XALINK.MAR
XAMESSAGE.MAR
XATEST.COM
XATEST.FOR
XI DRIVER.MAR

Files Contained in Directory (SYSHLP.EXAMPLES]
Description
Example device driver for ADll-K
Command procedure that connects device for LABIO
system
Parameter file for DRCOPY routines
Command procedure to build DRCOPY.EXE
VAX-11 RMS interface for DRMASTER.FOR
Master subroutines for DRCOPY
Slave subroutines for DRCOPY
VAX-11 RMS interface for DRS LAVE. FOR
Opens file that is to be used as a global
section for LABIO system
Defines information associated wth each A/D for
LABIO system
Linker options file for linking modules to be
used in LABIO system
Acquires data for LABIO system
Contains connect-to-interrupt call for LABIO
system
Linker options file for linking LABIO DATA ACQ
Attaches a LABIO user program to the LABIOsystem modules of the LABIO system
Command procedure to compile and assemble the
modules of the LABIO system
Handles user requests and modifies the data base
for LABIO system
Command procedure to link LABIO system
Samples channel for peak data in LABIO system
Samples channel in intervals, reporting date,
time, and average value on logical device for
LABIO system
Places LABIO SECTION on page boundary
Displays status of the A/D channels for LABIO
system
Command procedure to start LABIO system
Defines mailbox block for LABIO system
Command procedure to create Librarian DEMO.EXE
Librarian demo (first part)
Librarian demo (second part)
LPAll-K test program
Example program for line printer
Peak selection routine in LABIO system
Optional screen package (SCR$ ••• in RTL)
extension to handle foreign terminals
Template for user-written driver
Tests LABIO sytem
Sample user system service dispatch
and service examples
Link command procedure for USSDISP
Sample program to invoke one of the example
user services implemented in USSDISP
Link command procedure for USSTEST
DR-11 driver
Sample DRllW to DRllW link program
DR-11 test program
Used to set up XALINK.MAR
Companion program for XAMESSAGE
Example driver for parallel port on DMF32

A-13

APPENDIX B
USING THE TU58 TAPE CARTRIDGE

This appendix supplements the information on bootstrapping a VAX/VMS
system by describing how to perform conversational and nonstop
bootstrap operations using the stand-alone BOOT58 program on the TU58
tape cartridge.
This appendix also describes the command procedures
stored on the console TU58 tape cartridge and how you can manipulate
them.

B.l

WHEN TO BOOTSTRAP FROM THE TU58 TAPE CARTRIDGE

In most cases it is quicker, easier, and
recommended procedure, to
bootstrap the system directly from the system disk. When you do, the
microcode program must read and execute the boot block (block uJ.
~L
this block is corrupted, and the rest of the disk is intact, the only
way to safely bootstrap the system is to use stand-alone BOOT58.
Later, you can use the WRITEBOOT utility to replace the bad boot block
(see Section B.6).

B.2

BOOTSTRAPPING THE SYSTEM USING STAND-ALONE BOOT58

The stand-alone BOOT58 program resides on the console TU58 tape
cartridge
and
is
used to supplement the console subsystem's
bootstrapping functions.
When you request a bootstrap from the
console TU58 tape cartridge
(device DDAO),
the console subsystem
microcode reads the TU58 boot block (block 0) into memory and executes
it.
The effect of executing the TU58 boot block is to load and
transfer control to stand-alone BOOT58.
With stand-alone BOOT58, you can bootstrap the system in either of the
following ways:
•

Conversational
Request that SYSBOOT stop and allow you
modify the system parameters that configure the system.

•

Nonstop -- Allow SYSBOOT to run
intervention.

completion

without

to
your

Stand-alone BOOT58 commands are used to request the bootstrapping of
the system.
The console TU58 tape cartridge contains a number of
command procedures that contain the necessary stand-alone BOOT58
commands to bootstrap the system from the console TU58 tape cartridge.
Appendix C documents the BOOT58 commands.

B-1

USING THE TU58 TAPE CARTRIDGE
The console TU58 tape cartridge contains these files in two sets:
•

A conversational set that bootstraps the system from the
specified device and then stops in the SYSBOOT program to
accept changes to the parameters used to configure the system.
See Section B.2.1.

•

A nonstop set that bootstraps the system from the specified
device
without stopping
in SYSBOOT for changes to the
parameter values.
See Section B.2.2.

Table B-1 lists the names of the bootstrap command procedures
console TU58 tape cartridge.
Table B-1:

VAX/VMS Boot Command Procedures
Name of Command Procedure

Type of Command Procedure
Conversational bootstrap
from RK07

DMOGEN
DMlGEN
DM2GEN
DM3GEN
DMAGEN
DMBGEN

Conversational bootstrap
from RM03, RM80, RP06,
RP07, or RMOS

DB OGEN
DB lGEN
DB2GEN
DB3GEN
DB4GEN
DB4GEN
DBSGEN
DB6GEN
DB 7GEN
DBAGEN
DBBGEN

Conversational bootstrap
from RA60, RA80, or
RA81, controlled by a
UDA
.

DU OGEN

Nonstop bootstrap from
RK07

DMOBOO. CMD
DMlBOO. CMD
DM2BOO.CMD
DM3BOO.CMD
DMABOO.CMD
DMBBOO.CMD

Nonstop bootstrap from
RM03, RMOS, RM80, RP06
or RP07

DBOBOO. CMD
DB 1800. CMD
DB2BOO. CMD
DB3BOO. CMD
DB4BOO.CMD
DBSBOO. CMD
DB6BOO.CMD
DB7BOO. CMD
DBABOO.CMD
DBBBOO.CMD

Nonstop bootstrap from
RA60, RA80, RA81
Controlled by a UDA

DUOBOO.CMD

B-2

the

USING THE TU58 TAPE CARTRIDGE
B.2.1

Conversational Bootstrap Using Stand-Alone BOOT58

the stand-alone BOOTSB program and
To bootstrap the system using
request that SYSBOOT stop to allow you to change parameter values,
proceed as follows:
1.

Insert the console TU58 tape cartridge
(part description:
TU58#1 VAX-11/750 Local Console) in to the console drive.

See that the rotary key switch on the processor control panel
is set to LOCAL.

Set the POWER-ON-ACTION switch to HALT.

Press CTRL/P to obtain the console program prompt >>>.

Enter the following console BOOT command
tape cartridge:
>>>B

boot

the

TU58

DDAO

In response to the BOOT58 prompt, enter the name of a command
procedure in the following command format:
BOOTSB>@DxyGEN

@
Indicates that the rest of the line contains the name of
a command procedure located on the console TU58 tape
cartridge.

x
Indicates
volume:
B
M

the

device

type

the

desired

bootstrap

RM03, RM80, or RP06
RK07

Indicates the unit number of the desired bootstrap device
volume.
Specify a number in the range of 0 through 7.
When SYSBOOT is ready to accept commands, it prompts as follows:
SYS BOOT>
You can now issue any one of the SYSBOOT commands listed in Chapter 5.
If your system will not boot, you can use the following
sequence
SYSBOOT commands to boot using default system parameter values:

SYSBOOT> USE DEFAULT
SYSBOOT> CONTINUE
The following
example shows a
console
printout
obtained
by
bootstrapping the system using the stand-alone BOOT58 program and
altering the WSMAX system parameter:

B-3

USING THE TU58 TAPE CARTRIDGE
»>B DDAO
%%
BOOT58>@DMOGEN

DMO CONVERSATIONAL BOOT COMMAND FILE - DMOGEN
BOOT FROM DMO AND STOP IN SYSBOOT TO ALTER PARAMETER VALUES

D/G 0 1

CARTRIDGE DISK

D/G 1 FFEOOO

BASE OF UNIBUS I/O PAGE

D/G 2 3FF20

CSR ADDRESS OFFSET

D/G 3 0

CONTROLLER UNIT = 0

D/G 4 0

BOOT BLOCK LBN

D/G 5 1

SOFTWARE BOOT FLAGS

D/G E 200

ADDRESS OF WORKING MEMORY + AX200

LOAD VMB.EXE/START:200

LOAD PRIMARY BOOTSTRAP

START 200

START PRIMARY BOOTSTRAP

(UNUSED)
(CONVERSATIONAL)

SYS BOOT> SET WSMAX 512
SYSBOOT> CONTINUE
VAX/VMS Version V3.2 <date hh:mm>
Opcom, <date hh:mm:ss.ss>, logfile initialized, operator=_OPAO:
Login quotas - Interactive limit=64, Current interactive value=O
SYSTEM
job terminated at <date hh:mm:ss.ss>

B.2.2

Nonstop Bootstrap Using Stand-Alone BOOT58

To bootstrap the system using the stand-alone BOOT58 program,
stopping in SYSBOOT, proceed as follows:

without

Insert the console TU58 (part description:
Local Console) into the console drive.

See that the rotary key switch on the processor control panel
is set to LOCAL.

Set the POWER-ON-ACTION switch to HALT.

Press CTRL/P to obtain the console program prompt >>>.

Issue the following console BOOT
TU58:

»>B DDAO

B-4

command

TU58#1 VAX-11/750

bootstrap

the

USING THE TU58 TAPE CARTRIDGE
6.

In response to the BOOT58 prompt, type the name
bootstrap command procedure in the following format:

Indicates that the rest of the line contains the name
a command procedure located on the console TU585

BOOT58>@DxyBOO.CMD
@

x
Indicates
volume:
B
M

the

device

type

the

desired

bootstrap

RM03, RM80, or RP06
RK07

Indicates the unit number of the desired bootstrap
volume. Specify a number in the range of 0 through 7.
Note that you can also type a command procedure
format to perform a nonstop bootstrap operation:

the

following

BOOT58> BOOT 0 ddcu
Typing BOOT DMO is equivalent to typing @DMOBOO.CMD.
long form
(that is, @DxyBOO.CMD), the contents
procedure are displayed on the console terminal.

If you use the
of the command

The following example shows a
console
printout
obtained
bootstrapping the system using the command procedure DMOBOO.CMD:

>»B DDAO
%%

BOOT58>@DMOBOO.CMD

DMO BOOT COMMAND FILE - DMOBOO.CMD
D/G 0 1

CARTRIDGE DISK

D/G 1 FFEOOO

BASE OF UNIBUS I/O PAGE

D/G 2 3FF20

CSR ADDRESS OFFSET

D/G 3 0

CONTROLLER UNIT = 0

D/G 4 0

BOOT BLOCK LBN

D/G 5 0

SOFTWARE BOOT FLAGS

D/G E 200

ADDRESS OF WORKING MEMORY + "X200

LOAD VMB.EXE/START:200

LOAD PRIMARY BOOTSTRAP

START 200

START PRIMARY BOOTSTRAP

(UNUSED)

VAX/VMS Version V3.2 <date hh:mm>
Opcom, <date hh:mm:ss.ss>, logfile initialized, operator=_OPAO:
Login quotas - Interactive limit=64, Current interactive value=O
SYSTEM
job terminated at <date hh:mm:ss.ss>
B-5

USING THE TU58 TAPE CARTRIDGE
B.3

THE DEFAULT BOOTSTRAP COMMAND PROCEDURE

VAX/VMS provides a command procedure named
SETDEFBOO.COM
that
simplifies the copying of the default bootstrap command procedure to
the console TU58.
To use SETDEFBOO, log in under the system manager's
account, SYSTEM, then type the following:
$ @SYS$UPDATE:SETDEFBOO
SETDEFBOO asks you to confirm that the TU58 is in the console drive
and
requests the name of the bootstrap command procedure that is to
become the default:
Is the console medium ready to be mounted?
Enter name of default boot command file:

(Y/N):

Once you enter the name of the appropriate bootstrap
command
procedure,
SETDEFBOO copies the specified bootstrap command procedure
to DEFBOO.CMD on the console TU58.
When
it finishes copying,
SETDEFBOO issues the following message:
Default boot command file now replaced with <file-name>
Are you satisfied with this file as the default boot
command file?
(Y/N)
If you reply NO, the procedure will
ask you for
the name of the
default boot command file again.
If you are satisfied with this file
as the default boot command file, answer YES and proceed.

B.4

REBOOTING USING THE DEFAULT BOOTSTRAP COMMAND PROCEDURE

Under normal BOOT58 operation, you do not need to
interrupt the
bootstrapping of the system to type commands to SYSBOOT;
that is,
parameter values have been established.
Rather, you can bootstrap the
system using the default bootstrap command procedure that you copied
to the file DEFBOO.CMD.
To do so, proceed as follows:
1.

Shut down the
procedure:

system

executing

the

following

command

$ @SYS$SYSTEM:SHUTDOWN
This command procedure prompts for
the number of minutes
until
system shutdown,
the
reason for
the shutdown, and
whether to spin down the disks.

B.5

In response to the statement, "SYSTEM SHUTDOWN COMPLETE - USE
CONSOLE TO HALT THE SYSTEM," halt the processor by pressing
CTRL/P.

In response to the console prompt (>>>), type:

In response to the BOOT58 prompt (BOOT58>), type:

B DDAO:.
BOOT.

COPYING FILES TO OR FROM THE CONSOLE TU58 TAPE CARTRIDGE

Occasionally, you may want to copy files other than DEFBOO.CMD from
the console TU58,
edit them, and place them back on the cartridge.
VAX/VMS provides a command procedure named DXCOPY.COM to simplify the
copying of text files (that is, ASCII files such as bootstrap command

procedures) to and from the console TU58.
B-6

USING THE TU58 TAPE CARTRIDGE
To request the execution of the command procedure
copy the files, proceed as follows:
1.

DXCOPY.COM

and

console

TU58

Invoke the command procedure by typing:
$ @SYS$UPDATE:DXCOPY

The command
mounted:

procedure

asks

whether

the

Is the system console storage medium mounted

(Y/N)?:

Mount the TU58 and type YES.

The command procedure then asks whether the copy operation is
from the console TU58:
Copy from console medium

(Y/N)?:

Type YES to indicate a copy from
default directory.

the

console

TU58

the

Type NO to indicate a copy from the current default directory
to the console TU58.
4.

B.6

Finally, the command procedure requests the name of the
file
to
be copied to or from the console TU58.
Type the name of
the file and press RETURN.

WRITEBOOT UTILITY

This section discusses the WRITEBOOT
block on a bootable disk.

Utility,

which

writes

boot

The normal bootstrap operation on the VAX-11/750 is done from the boot
block
(block
0) of the system disk.
If this block is corrupted, the
system can only be bootstrapped from the TU58.
Once the system
is
running
again,
the bad boot block can be rewritten by using the
WRITEBOOT Utility.
To invoke WRITEBOOT, type:

S RUN SYS$SYSTEM:WRITEBOOT
WRITEBOOT will ask you three questions.

The first is:

Target system device (and boot file if not VMB.EXE):?
Enter the name of the device on which you want to
block
(DMAO for
example).
The
target system
specified as any VAX/VMS disk device (ddcu):

rewrite the boot
device should be

dd is the code name for the device type
c
is the controller designation
u is the unit number
For example, DMAO would be an RK07
number O.
The second question is:

RK611

controller

Enter VBN of boot file code (default is one):

B-7

device

USING THE TU58 TAPE CARTRIDGE
If you are rewriting the boot block, press RETURN.
is:

The third question

Enter load address of primary bootstrap in HEX (default is 200):
Again, if you are rewriting the boot block, press RETURN.
WRITEBOOT will then write the boot file that you specified in
first line, to the address that you entered in the third line.

the

NOTE
To use WRITEBOOT
privilege.

you

need

the

LOG IO

The WRITEBOOT Utility may issue the following error messages.
You lack LOG_IO privilege
Explanation: You do not have the correct
WRITEBOOT.
Consult with your system manager.
You lack READ and/or WRITE access to TARGET DEVICE.

privilege

use

DISMOUNT and reMOUNT

Explanation: The access to the target device is limited.
the write protect button.

Check

VBN must be >= l
Explanation: You cannot specify a
Number (VBN) •

B-8

zero

the

Virtual

Block

APPENDIX C
BOOT58 COMMANDS

This appendix lists and describes the commands that can be entered
the
stand-alone
BOOT58
program.
The commands are listed
alphabetical order.

to
in

BOOT (device-name]
Bootstraps the system from the specified device.
If you omit the
device name,
the system
is bootstrapped using
the default
bootstrap command procedure (DEFBOO.CMD).
Note that you cannot
enter the name of a command procedure to the BOOT command and you
cannot specify this command within a command procedure.
DEPOSIT (loc-qual,size-qual]

location value

Deposits a value in the specified location.
The location is
interpreted according
to the location and size qualifiers.
The
location qualifier can be expressed as follows:
/G

general register

internal process register

physical memory

The size qualifier can be expressed as follows:
/B

byte

word

longword

If you do not specify the location and size qualifiers,
default values established by a previous command are used.
EXAMINE (loc-qual,size-qual]

the

location

Displays the contents of the specified location.
The location is
interpreted according
to the location and size qualifiers.
The
location qualifier can be expressed as follows:
/G

general register

internal process register

physical memory

C-1

BOOT58 COMMANDS
The size qualifier can be expressed as follows:
/B

byte

word

longword

If you do not specify the location and size qualifiers,
default values established by a previous command are used.

the

Displays the BOOT58 help file at the console terminal.
cannot specify this command within a command procedure.

You

HELP

LOAD file-spec [/START:address]
Loads a file from the bootstrap device into memory,
starting at
the address specified with the /START qualifier.
If you omit the
/START qualifier, the file is loaded into memory beginning at the
first free address.
START value
Transfers control to the value specified.
command with the LOAD command.

You generally use this

@file-spec
Executes the name of the command procedure specified.
You cannot
specify
a
command
procedure file-spec of more than six
characters, nor can you specify nested command procedures.

C-2

APPENDIX D
MICRO VERIFY ERROR CHARACTERS

Micro verify routines test the reliability of the VAX-11/750 hardware.
At the start of the micro verify routines, a percent sign (%) is
displayed at the console terminal.
If the routines run successfully,
a second percent sign is displayed after the first percent sign.
If,
however, an error is detected while the routines are running, a single
error character
is displayed in place of the second percent sign and
the processor is halted in console mode.
Table D-1 lists the possible micro verify error characters and
the micro verify routines associated with those characters.
Table D-1:

Micro Verify Error Characters

Error Character

Routine Name

R-BUS, W-BUS, D-REG TEST
CACHE TEST
TB PARITY CHECKER
CONTROL STORE PARITY CHECKER
M-BUS, C-REG TEST
SCRATCH PAD TEST
SCRATCH PAD EXPLICIT ADDR MTEMPS
SCRATCH PAD EXPLICIT ADDR RTEMPS
SCRATCH PAD EXPLICIT ADDR IPRS
SCRATCH PAD EXPLICIT ADDR GPRS
SCRATCH PAD DUAL PORT ADDRESS
XB, IR, OSR TEST
EX, PC PC+ISIZE TEST
DSIZE TEST
DSIZE TEST
CACHE PARITY CHECKER

[
]

c
E
F

I
J

L
L
0
Q

R
T

D-1

names

APPENDIX E
INSTALLING OPTIONAL SOFTWARE PRODUCTS

The procedure for
performing
optional
software
installations is
automated,
and
thus requires little involvement on your part beyond
(1) setting up the proper conditions for
the
installation and
(2)
responding
to queries and
prompting messages displayed as the
installation proceeds.
The VMSUPDATE.COM procedure drives optional
software
installations.
Once invoked, it uses command procedures contained in the distribution
media.
These command procedures direct the installation procedure by
means of queries and instructions sent to the terminal. Most queries
require simple YES or NO answers.
You respond
with Y or N,
as
appropriate.

E.l

DISTRIBUTION KITS

Optional software installations for the VAX-11/750 are distributed
TU58 cartridges (one or more depending on the installation).

Each TU58 is labeled with both a
name and
a
serial
number
that
differentiates
it from others
in the distribution kit.
Check that
your kit contains all the cartridges listed in the bill of materials.

E.2

PREPARATIONS FOR AN OPTIONAL SOFTWARE INSTALLATION

To prepare for the installation, do the following:
1.

Back up your
system disk
(see Section 3.6).
Optional
software products may delete older product versions before
installing new ones, so it is advisable to back up your
system disk before attempting any software installation.
i~
is also advisable because a
system failure at a critical
point of the installation could leave unusable files.

under

the

system

manager's

(If the SYSGEN parameters MOUNTMSG or DISMOUMSG at your
site
have been set to
1, you will receive a message from OPCOM
each time a disk, tape, or TU58
is mounted
or dismounted.
These messages are normally disabled, but if they have been
activated and you are installing
from a console terminal,
they will appear from one to thirty 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.

E-1

INSTALLING OPTIONAL SOFTWARE PRODUCTS
4.

Set the login quota to 0 by typing:
$ SET LOGINS/INTERACTIVE = 0

Be sure that you have set your default to the disk that is to
receive the update. 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 ~DMAl: [SYSO.]
$ SET DEFAULT TARGET: [SYSUPD]
Note that not all optional software kits allow installation
to a device other than the system disk.
Consult the
documentation that came with the optional software kit.

If you are installing to the current system
the following default:

disk,

establish

$ SET DEFAULT SYS$UPDATE

E.3

INSTALLING OPTIONAL SOFTWARE PRODUCTS

Type the following command to initiate the installation:
$ @VMSUPDATE
You will receive the following message text at the terminal:
VMS Update Procedure
This command procedure performs VAX/VMS software updates and
optional software installations for VAX/VMS Release 3.
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 cartridge in the console drive
After placing the TU58
following query:

the

CSAl

drive,

you

will

receive

the

drive

and

Are you ready to continue?:
If you type Y, the installation proceeds.
If you type N, the request to insert the cartridge in the
the query "Are you ready to continue?" will be repeated.
Continuation of
messages:

the

%MOUNT-I-MOUNTED

update

indicated

<label> mounted on
E-2

by
CSAl:

the

display

the

INSTALLING OPTIONAL SOFTWARE PRODUCTS

These messages are followed by questions and prompts, the
which depends on the product.

E.4

content

INSTALLATION COMPLETION

When the installation is completed, control is returned to the command
procedure VMSUPDATE.COM, which sends the following messages to the
terminal:
Are there more kits to process?:
If you type Y, you will receive the
installation procedure begins again.

following

request,

and

the

receive

the

Please place the first cartridge in the console drive.
If you have no further installations, type N.
following message and DCL prompt:

You

then

Requested update sequence complete.
$
The procedure is now complete.
To transfer control of the system to the updated version
halt the processor and reboot the system.

Finally, after installing an optional
back up the system disk.

you

E-3

software

product,

VAX/VMS,
should

.~PPENDIX

BUILDING THE VAX/VMS SOURCE KIT

The VAX/VMS source kit is a set of three magnetic tapes that contains
the source files,
object files, command files, language processors,
and utilities necessary to build any of the standard components of the
VAX/VMS operating
system.
(The languages and utilities used in this
building operation are not supported by DIGITAL.)
Before you begin building, you must make sure there
is enough disk
space available.
A single component might require up to 40,000 free
blocks.
To build the entire system you will need at 1 east one RP06
(or
its equivalent)
for
the source kit and
one RMOS
(or
its
equivalent) to use as the target of the build
(for object files,
1 is ting s , and so on) •
To use the VAX/VMS source kit, you must mount the first
reel
of the
kit
(the
tape
labeled
VMSRCl)
and
restore
the
file
[SYSBLDCOM]SRCINSTAL.COM.
(This command procedure, when invoked, will
ask you questions in order
to properly define the system building
environment.)
To mount the reel
commands:

and

restore

the

file,

type

the

following

DCL

ALLOCATE MTcn:
MOUNT/FOREIGN MTcn:
VMSRCl
BACKUP MTcn:SYSBLDCOM/SELECT={SRCINSTAL.COM) DBcn: [* ••• ]
When the file has been restored, dismount the tape.
Then complete the
source kit installation
(for either a partial or the entire system
build) by issuing the following DCL command:
@DBcn: [SYSBLDCOM]SRCINSTAL.COM
This invokes a command procedure to create 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 username SYSTEMBUILD
and the password CAVEAT_EMPTOR.
Finally, to obtain a general description of the source
print a copy of the file [SYSBLDCOM]SOURCEKIT.DOC.

F-1

kit

you

can

APPENDIX G
UPGRADING THE SYSTEM

If for some reason you have not already upgraded your system from
Version 2.5 to Version 3.0, this appendix describes the procedure you
should follow.
CAUTION
Do not attempt to apply any Version 3
maintenance
updates
without
first
upgrading the system to Version 3.0.
The upgrade works only on a Version 2.5
system.
All that the user needs in order to perform the upgrade is the Version
3.0 software distribution kit and a blank TU58 cartridge.
You should read this entire
upgrade to make sure you
upgrade.

appendix before attempting to do an
are aware of all the requirements of the

It is important to note that the upgrade procedure will work correctly
only as long as your system directories are consistent with those set
up by the VAX/VMS installation procedure. If you have changed the
names of the directories, or deleted files from them, the upgrade
procedure may not work correctly.
NOTE
As part of the upgrade, the paging,
swapping, dump, and authorization files
are purged
back
to
one
version.
Everything in the (SYSERR] directory is
deleted. All operator and accounting
logs are deleted. If you want to keep
any logs, move them to a user directory
before starting the upgrade. It is also
suggested you back up your system disk
before upgrading because some V2.5 files
have been made obsolete by V3.0 and will
be deleted when you upgrade.

G.l

RESTARTABLE UPGRADE PROCEDURE

The upgrade procedure can be restarted. The system is booted three
times as part of the upgrade, and a restart will continue from the

G-1

UPGRADING THE SYSTEM
last time the system was booted.
The system manager must boot in the
manner
requested by the upgrade procedure after the last planned
system shutdown for the upgrade to automatically continue.
In order to make the upgrade procedure restartable at any time,
the
new Version 3.0 system files are placed in a different directory from
the existing V2.5 system files.
Therefore, at least one set of system
files is bootable at all times.
(More information on top-level system
directories can be found in the VAX/VMS Release Notes.)

G.2

PREPARING TO UPGRADE THE SYSTEM

the

system

manager's

account,

Because available disk space is always at a
premium,
remove all
unwanted or
redundant files before upgrading the system.
You can
remove them with the DCL commands DELETE or PURGE.
For
instance,
because all
DIGITAL optional software must be reinstalled after an
upgrade, you can delete the existing optional software files.
To upgrade the system, there must be a minimum of 7000 free blocks on
the system disk.
You can confirm the free block count with the
following command:
SHOW DEVICES

device-name

Note that during the upgrade, the system disk and the distribution kit
cannot be moved from one device to another.
Before upgrading your system, you must also back up the system disk to
a scratch disk.
Users who received magnetic tape distribution kits
can use the stand-alone BACKUP procedure described
in Section 3.6.
Users who
received RK07 distribution kits should back up the system
using the stand-alone Disk Save and Compress Utility documented in the
VAX-11 Software Installation Guide,
Version 2.0.
When this is
completed, boot the scratch disk, which will become the Version 3.0
system disk.
Make sure the POWER-ON-ACTION switch on the processor control panel is
set to
RESTART/BOOT.
The upgrade will continue automatically after
shutdowns as long as this switch is in the RESTART/BOOT position.

G.3

UPGRADING VAX/VMS

After bootstrapping your system with the new system disk, you are
ready to begin the
upgrade procedure.
Proceed as follows at the
console terminal:
1.

Set the boot device switch on the processor control panel
boot from the disk drive containing the new system disk.

If you do not have a position for this device, set the boot
device switch to
position A to bootstrap from the TU58
cartridge, and place your console TU58 in the drive in the
processor control panel.
If you are booting from the TU58,
reply YES when the upgrade procedure asks if you want to boot
from TU58.
2.

G-2

UPGRADING THE SYSTEM
3.

Prevent users from logging into the system by typing:
$ SET LOGINS/INTERACTIVE=O

If you are running
typing:

DECnet-VAX,

shut

down

the

network

$ RUN SYS$SYSTEM:NCP
When the NCP> prompt is displayed, type:
SET EXECUTOR STATE OFF
To exit from NCP, type either CTRL/Z or EXIT.

Issue a STOP/QUEUE/NEXT command for batch and
if there are any jobs in the queues.

ptint

queues,

These queues will be initialized during the upgrade, and
jobs contained in the queues will be lost.

any

Place the distribution medium in the
place the drive online.

and

Execute the following DCL command:

appropriate

drive

$ SET DEFAULT [SYSUPD]
8.

Type the following:
$ @VMS INSTAL

You now receive a request to enter the device name of the
You must type your
drive holding
the distribution kit.
response in the format ddcu:
the
dd is the device code, c,
The upgrade
controller letter,
u,
the unit number.
and
procedure will abort if it believes the format is incorrect.

10.

At this point, the upgrade procedure displays:
VAX/VMS V3.0 Upgrade Procedure
A brief description of the upgrade procedure will
displayed, and a cautionary note about preserving files.

The upgrade procedure then asks:
Do you want to continue?

(Y/N):

If you respond YES, the upgrade continues to Phase 1.

Upgrade Phase 1

G.3.1

The first phase of upgrade requires some user interaction.
procedures below:
1.

Follow the

The upgrade begins by informing you that the default
for VAX/VMS V3.0 is EDT.
The procedure then asks:

editor

Would you like SOS to be the default editor for the EDIT
command, as it was in VMS V2.0?
(Y/N)
Respond YES or NO to that question.

G-3

UPGRADING THE SYSTEM
2.

Next, the upgrade procedure turns off the disk quotas on the
system disk and
removes directory entries that point to
nonexistent files.
The procedure then asks:
Do you want to boot from the TU58?

(Y/N)

If you do not want to boot from TU58, answer NO
to step 9 below.

and

proceed

If you set your boot device switch to boot from TU58 as
Make sure the
described in Section G.3, you must answer YES.
upgrade
to
switch position is set correctly for
the
automatically continue.
3.

At this point, a new, site-specific TU58 must be
allow reboot of a kernel VAX/VMS V3.0 system.

created

The upgrade procedure asks you the following question:
DEFBOO.CMD must be set to boot from your current
system disk.
You must set this up if it has not been done previously.
Do you want to do this now?
(Y/N)
This means that the DEFBOO.CMD command procedure on your old
console TU58 must be set to boot your current system disk.
If you have already done this, enter NO and move to step 7
below.
If you have not yet done this, enter YES and proceed
as follows:
4.

Answer YES when you receive this message:
Please place the system console medium in the console
drive.
Is the console medium ready to be
mounted?
(Y/N)

After you type YES, you receive this message:
%MOUNT-I-MOUNTED, CONSOLE mounted on CSAl:
Enter name of default boot command file:
Enter the appropriate name in the form dduBOO.CMD.
Note that
you must not do an interactive boot.
The upgrade kit is set
with parameters that boot any system.

The following is then displayed:
Default boot command file replaced with dduBOO.CMD
Are you satisfied with this file as the default boot
command file?
(Y/N)
If you are satisfied with this file as the default boot
If you are not satisfied, return to
command
file,
proceed.
step 1.

Put your old console TU58 into drive CSl.
you receive the following message:
Is the old console TU58, CSl:, ready to
be mounted?
(Y/N)

G-4

Answer

YES

when

UPGRADING THE SYSTEM
The system will respond:
%MOUNT-I-MOUNTED, mounted on

CSAl:

The TU58 is copied to the system disk for editing.
8.

Now, put a scratch console TU58 into the console drive.
(The
blank TU58 provided with your distribution kit may be used.)
The upgrade procedure now checks the new console TU58 for any
defective blocks by running the Bad Block Locator Utility.
The new console TU58 will be written just before the system
is rebooted in order to boot from the V3.0 kernel system.
Do
not put your normal console media back in the console drive
during the remainder of the upgrade procedure.
The upgrade procedure now asks:
Is a scratch console TU58 now in CSl:?

(Y /N):

Answer YES.
The system responds:
%MOUNT-I-MOUNTED, mounted on
9.

CSAl:

The upgrade procedure now removes all VAX/VMS V2.5 files not
needed to complete the upgrade, and causes the V3.0 required
save set to be copied to the system disk.
BACKUP then starts
a verification pass to make sure all the files in the save
set have been correctly copied.
When the verification pass is complete, the upgrade procedure
purges the paging,
swapping, dump, and authorization files
back to one version.
(Ignore any file not found messages.)
If you are booting from the TU58, the upgrade procedure now
initializes the new console TU58, copies unmodified files to
the new console TU58,
and sets the DEFBOO.CMD command
procedure to boot V3.0 from the directory [SYSF.SYSEXE].
(More information on top-level system directories can be
found in the VAX/VMS Release Notes.)
When the upgrade procedure reaches this
the following message:

point,

you

receive

System shutting down to boot a kernel V3 system.
If you are booting from the TU58,
leave the newly created
site-specific console TU58 in the console drive for the
remainder of the upgrade procedure.
10.

Leave the distribution kit and the system disk where they are
for the remainder of the upgrade procedure.

11.

The SYSGEN parameters are set to boot any system.
Do not
change them during
the reboot, or the upgrade may fail to
execute properly.

12.

The system shuts down as part of the upgrade procedure.
If
you are booting from the TU58, you will have to type B after
each reboot when the BOOT58> prompt is displayed.

G-5

UPGRADING THE SYSTEM
If
rebooting
from
completes, type:

the

disk,

after

the

system

shutdown

CTRL/P
B/FOOOOOOO ddcu:
From this point on, all reboots from the
without user intervention.

disk

will

execute

At this point, a kernel V3.0 system is booted and announces:
VAX/VMS Version V3.0 <date hh:mm>
$ SET NOVER
Continuing with VAX/VMS V3.0 Upgrade Procedure.

G.3.2

Upgrade Phase 2

At the beginning of the second
message:

phase

upgrade

you

receive

this

%0PCOM, <date hh:mm>,
logfile initialized by operator
OPAO logfile is SYS$MANAGER:OPERATOR.LOG
%MOUNT-I-MOUNTED, VMS300 mounted on <ddcu>
The upgrade procedure then starts a directory cleanup.
This takes a
varying amount of time depending on the number of files on the disk.
When the directory cleanup is complete, the upgrade
removing the remainder of the VAX/VMS V2.5 files.

procedure

begins

Next, the library save set is merged
into the
kernel
When this is oone, BACKUP starts a verification pass.

V3.0

system.

Then the optional save set is merged
into the kernel
When this is done, BACKUP starts a verification pass.

V3.0

system.

When the verification pass
is complete,
the user authorization
accounts are modified to handle V3.0 changes.
This includes providing
each account with an ENQLM quota of at least 20 and changing default
directories of SYS$SYSDISK and null default devices.
At this point, the distribution kit may be removed.

G.3.3

Upgrade Phase 3

The third phase of the upgrade merges the VAX/VMS-distributed files
that are commonly edited by system managers with new VAX/VMS files.
Ignore any undefined symbol and file not found 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],
and so
on.
This takes a varying amount of time, depending upon the number of
user files.

G-6

UPGRADING THE SYSTEM
G.3.4

Upgrade Phase 4

If you are booting from TU58, you receive the following message:
Now the new site-specific TU58 must be modified
to allow reboot of the complete VAX/VMS V3 system.
The new site-specific console TU58 should already
be in CSl:.
The new site-specific TU58 created in Phase 1 should still be
console TU58 drive.
SOS is now established
requested it.

the

default

editor,

you

the

previously

You then receive the following message:
System shutting down to boot the complete V3.0 system.
If you are booting from TU58, leave the newly created site-specific
console TU58 in the console drive.
The system disk must remain where
it is in order to proceed to the next phase of the upgrade.
The system automatically reboots after the shutdown.
Then the following appears:
VAX/VMS Version V3.0 <date hh:mm>

G.3.5

Upgrade Phase 5

This part of the upgrade procedure creates a new site-specific
parameter file, AUTOGEN.PAR.

SYSGEN

After a directory cleanup, and the announcement that the upgrade
VAX/VMS Version 3.0 is complete, several messages will appear.

The upgrade has automatically created a new parameter file called
AUTOGEN.PAR that combines the default values for V3.0 and the sitespecific values you were using under V2.0.
When the system reboots,
it will be using the values contained in the AUTOGEN.PAR file.
If you asked to boot from TU58, the upgrade procedure has also created
a new site-specific console TU58.
This TU58 should be used instead of
your old one.
The upgrade is complete after the reboot.

G.4

THE AUTOGEN.PAR PARAMETER FILE

AUTOGEN.PAR contains some SYSGEN parameter values identical to those
used under V2.0.
These are usually set by each site to values
specific to that site. An example is REALTIME SPTS.
Other SYSGEN parameter values have been set to the maximum of your
V2.0 site-specific value and the V3.0 default value. An example is
INSTKPAGES.
The remainder of the SYSGEN parameters have been handled
individually
or set to the default values for V3.0.
To see which category a
particular parameter falls in,
refer to the SAVPARAMS section in
SYS$UPDATE:AUTOGEN.COM.
G-7

UPGRADING THE SYSTEM
See Section
parameters.

G.5

3.4

for

additional

information

modifying

system

SPECIAL FILE HANDLING DURING UPGRADE

After you have completed the upgrade, you may wish to remove files you
no longer need.
In order to do so, you need to know that certain
VAX/VMS-distributed files are handled specially during the upgrade.
These include files that may have been edited by users, and shareable
images that may have been linked into user images.
For the following files, the V3.0 distribution kit copy of the file is
made an older version, and any existing V2.0 copies become more recent
versions of the file:
[SYSMGR]FORMSTYPE.DAT
[SYSMGR]CHARTYPE.DAT
For the next list of files, the V3.0 distribution kit copy of the file
is made the latest version, and any existing V2.0 copies become older
versions of the file:
[SYSLIB]LBRSHR.EXE
[SYSLIB]RSXUSR.EXE
[SYSLIB]SUMSHR.EXE
[SYSLIB]VMSRTL.EXE
(SYSMGR]STARTNET.COM
[SYSEXE]STARTUP.COM
[SYSEXE]SHUTDOWN.COM
[SYSEXE]STARTUP.M!N
(SYSHLP]HELPLIB.HLB
The system manager may wish to reconcile the new versions with any
local modifications to these files before deleting the older versions.
The upgrade procedure does not copy these files to the system disk
all; you are left with the older versions of these files:

[SYSMGR]SYSTARTUP.COM
(SYSMGR]SYSHUTDWN.COM
[SYSEXE]SYSUAF.DAT
[SYSEXE]NOTICE.TXT
The upgrade procedure may have changed the size of the following files
to better fit a V3.0 system, so their use should be monitored to make
sure they are satisfactory:
(SYSEXE]SYSDUMP.DMP
[SYSEXE]PAGEFILE.SYS
[SYSEXE]SWAPFILE.SYS

G.6

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 in your
site's SYS$MANAGER:SYSTARTUP.COM file and should be
removed.

G-8

APPENDIX H
VMSINSTAL ERROR MESSAGES

This appendix lists the error messages issued by the VMSINSTAL command
procedure.
Each message consists of an abbreviation followed by a
text message.
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 (UAFj has been updated accordingly.
User Action:

None, this message is informational.

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 asken if you want to continue the
installation.
It
is recommended that you remedy this situation
before continuing.
AUTOSYNC, Auto-answer file is out of sync with questions.
AUTOFILE, question\answer
QUESTION, 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
coincide with 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.
BADCONDEV, Please specify an existing console device.
Explanation:
You have specified a console device on which the
distribution volumes are to be mounted, but the device specified
is a console device.
User Action:

Specify an existing console device.

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.

H-1

VMSINSTAL ERROR MESSAGES
BADLIBDEV, Please specify an explicit disk drive.
Explanation:
For Dual RL02 installations, you have specified a
device on which the library disk is to be mounted, but the device
is not a disk.
User Action:
CTRLY,

Specify a disk device.

Installation cancelled via CTRL/Y.

Explanation:
CTRL/Y.

You have cancelled the installation by entering

User Action:

None, this message is informational.

DECNET, 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.
INTEGER, Please enter an integer value.
Explanation:
VMSINSTAL asked a question which must be
with an integer number.
User Action:

answered

Answer the question again, specifying an integer.

INVOPTIONS, 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
the correct format.

IVPFAIL, The IVP for 'product' has failed.
Explanation:
VMSINSTAL
has
invoked
the
Installation
Verification Procedure
(IVP) for the specified product, and th~
IVP has failed.
User Action:
If you can deter~ine the problem and
resolve
it,
then simply install the product again.
Otherwise, Contact your
local DIGITAL support representative.
LIBDIFF, The following system and library disk files do not match.
LIBDIFF2, You must resolve these differences before continuing.
Explanation:
For Dual
RL02 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:
VMSINSTAL.

You must resolve the differences before reinvoking

H-2

VMSINSTAL ERROR MESSAGES
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 4.2 in this guide~
MOVEFILES, Files will now be moved to their target directories
Explanation:
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:

None, this message is informational.

NEXTVOL, The next volume will be mounted 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
volume,
so
VMSINSTAL will examine the next volume.
User Action:
This message will be preceded by various serious
BACKUP messages, which can be
ignored.
You will be asked to
mount the next distribution volume.
NOCONSOLE, Unknown CPU type;

console volume not remounted.

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

[new]

volume,

Contact your local DIGITAL support representative.

file 'file' does not exist.

Explanation:
VMSINSTAL is attempting to locate an existing
(or
perhaps new)
file with the given name, but the file does not
exist.
This message should be proceeded by other messages that
explain it in greater detail.
User Action:
If you can determine the problem and
resolve it,
then simply install the product again.
Otherwise, contact your
local DIGITAL support 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 Dual RL02 system.
For
some reason, the library disk could not be mounted.
User Action:
Correct the situation that prevented mounting
library disk and begin the installation again.

H-3

the

VMSINSTAL ERROR MESSAGES
NOPRINT, File 'file' cannot be printed.
Explanation:
one or more
printing.

The product installation required the printing of
files, but the files could not be queued for

User Action:
This error is most likely caused by the fact that
a SYS$PRINT queue is not defined 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.
NOPROC, The kit's installation procedure is missing.
Explanation:
The main installation procedure for
could not be located on the distribution volumes.
User Action:

the

product

Contact your local DIGITAL support 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
exist on the volumes.
User Action:

Specify products which exist on the volumes.

NOREINSTALL, Image 'image' could not be reinstalled.
Explanation:
VMSINSTAL was attempting to use the INSTALL
utility to make an image known to the system. The INSTALL
utility failed.
User Action:
This message should be preceded by a message from
the INSTALL utility explaining the problem. Correct the problem
and begin the installation again.
NOSAVESET, Required saveset '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 local DIGITAL support 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.
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.
H-4

VMSINSTAL ERROR MESSAGES
NOTSYSTEM, 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.
You will be asked if you want to continue the
User Action:
It
is recommended that you remedy this situation
installation.
before continuing.
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.
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.
In order to accomplish this,
the remaining uninstalled products must be skipped.
User Action:
is rebooted.

Reinstall the remaining products after the

system

REBOOT, This product requires that the system be rebooted.
Explanation:
The product that was just installed requires
the system be rebooted to complete the installation.
User Action:

that

Reboot the system after shutdown completes.

RECORDANS, Auto-answer file will be recorded.
Explanation:
The Auto-answer options 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
answers will be recorded.
RECOVER,

usual.

Your

'product' was being installed when the system crashed.

Explanation:
The specified product was being installed when the
system crashed due to a power failure or other problem.
User Action:
proceed.

You will receive additional instructions on how to

RESTORE, Restoring product saveset 'letter' •••
Explanation:
The specified product save set is about to
restored from the distribution volumes by the Backup utility.
User Action:

This message is purely informational.

H-5

VMSINSTAL ERROR MESSAGES
RETAILOR, Your original tailoring environment will now be restored.
Explanation:
system disk
disk.

The tailoring files that were
removed
from your
for installation, will be copied back to the system

User Action:

None, this message is informational.

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
rewino
the tape in case the savesets were not recorded in
order.
User Action:
This message will be preceded by
BACKUP messages, which can be ignored.

various

serious

SMALLDISK, This is a small disk system.
Explanation:
VMSINSTAL has determined that you are
running
a
dual
RL02 system.
It will temporarily remove all nonessential
files from the system disk
in order to make
room for
the
installation.
User Action:
to proceed.

You will receive additional instructions as to how

STEP8FAIL, The installation of 'product' has failed.
STEP9FAIL, The installation of 'product' has failed.
Explanation:
The installation of the product has failed due
some unrecoverable error.

User Action:
Additional messages should precede this one.
These messages will
explain the problem in greater detail.
If
you can remedy the situation, then simply install
the
product
again.
Otherwise,
contact
your
local
DIGITAL
support
representative.
SYSDIR, This product creates system directory 'directory'.
Explanation:
The product being installed creates the
system directory.
User Action:

specified

This message is purely informational.

SYSDISK, This product creates system disk directory 'directory'.
Explanation:
The product being installed creates a directory on
the system disk.
User Action:

This message is purely

H-6

informational~

VMSINSTAL ERROR MESSAGES
TAMPER, 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, then they
be updated by DIGITAL software installations.

cannot

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
local DIGITAL support representative.
UPDATED, File 'file'

is already updated.

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

text

This message is purely informational.

USEANS, Auto-answer file will be useo.

Explanation:
The
Auto~answer
specified
was
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 Dual RL02
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.
If, however, the system crashes during the
installation, then you must restore the configuration and delete
the file manually.
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.
YESNO, Please enter YES or NO.
Explanation:
VMSINSTAL asked a question which must be
with YES or NO.

answered

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

H-7

NO.

INDEX

Optional kit restoration,
RL02/RA80, 2-10
Overview,
of building a bootable
system disk, 2-1
of system installation, 1-5

AUTOGEN.PAR parameter file,
G-7

Backup Utility (BACKUP),
save set, 2-1
BOOT58 program, 1-1
Bootstrap,
conversational, 5-3
initial,RL02/RA80, 2-9
nonstop, 5-3
Building a bootable system
disk, 2-1

Software distribution kit,
See VAX-11/750 software
distribution kit
STABACKIT.COM command
procedure, 5-9
Stand-alone BACKUP,
building a kit, 5-9
loading, 2-6
SYSBOOT program, 5-4
commands, 5-4
System update, 4-1
distribution kit, 4-1
System upgrade, G-1
preparation, G-2
restart, G-1

Command procedures,
CONSCOPY.COM, 5-1
STABACKIT.COM, 5-9
VMSINSTAL.COM, 2-10
VMSKITBLD.COM, 5-6
CONSCOPY.COM command
procedure, 5-1
Console subsystem, 1-1

Device name specification, 2-4
Distribution kit,
See VAX-11/750 software
distribution kit

EDTCAI, 2-3

Maintenance update,
See System update

Index-1

VAX-11/750 console subsystem,
1-1
VAX-11/750 software
distribution kit, 2-1
magnetic tape kit, 2-2
optional, 2-3 to 2-4
primary, 2-3
RA60 kit, 2-3
RK07 kit, 2-3
VMSINSTAL command procedure,
4-1
VMSINSTAL option, 4-4
VMSINSTAL product list, 4-3
VMSINSTAL.COM command
procedure, 2-10
VMSKITBLD.COM command
procedure, 5-6

EK-SI750-IN-CN1

PCS 750 INSTALLATION PROCEDURE

ADDENDUM
to the
VAX-11/750 INSTALLATION AND ACCEPTANCE MANUAL
(EK-SI750-IN-003)

June 1983

Prepared by Educational Services
of Digital Equipment Corporation

PCS 750 INSTALLATION PROCEDURE

INSTALLATION PROCEDURE
To install the PCS (Patchable Control
procedure below:
1.

Remove the L0005 from slot 5.

Install the L0008 in slot 5.

Store)

boar~,

the

If you are removing the L0005 without the WCS daughter
board, install an L0008-YA.

If you are removing the L0005 with
board, install an L0008-YB.

the

WCS

daughter

DIAGNOSTICS

Power up the system.

Boot the Diagnostic Supervisor to automatically
PCS for testing.

load

the

NOTE
The m1n1mum revision level
of
the
Diagnostic Supervisor (ECSAA) that will
load the PCS with microcode is 6.108.
UPDATING VMS (TO LOAD THE PCS)

Boot VMS.
NOTE
Booting VMS will
not load
the PCS
unless
SYSTARTUP.COM has been updated
to do so.

Set the default to [SYSUPD].

Insert \the PCS750KIT TU58 cassette (BE-T538A-ag)

Type @VMSUPDATE.

in CSAl.

NOTE
You will be asked some questions, the
first one being MAre you ready?" This
is just to see if the TUSS is loaded~
Answering "yes" will mount the TU58.
From this point on, the command file on
the TU58 will be run.
~
6.

Answer the two questions asked by the update command
program.
a•

file

Quest ion . 1 :
If you have battery
recovery?

backup,

you

want

powerfail

NOTE
Powerfail recovery does not work at
this
time with all VMS Version 2
systems.
The answer to this question determines how a power
failure is to be handled.
If you have a power failure
and you have battery backup, the PCS will not be
reloaded unless the PCS device driver is included
along with the proper command file that defines that
device driver.
Answering "yes" to this question means the device
driver
{PCS750DRV)
will be included with the PCS
loader utility {PCS750UTL). Also, the command file
PCS750RES.COM will be added to the system manager
account ( (S'YSMGR]) and SYSTARTUP.COM will be appended
to call that command file.
If a power failure occurs
with battery backup, the driver will be awakened by
the system to reload the PCS.
If you answer "no" to this question, the driver will
not be included with the utility and the command file
PCS750.COM will be added to [SYSMGR] with a call to
that command file from SYSTARTUP.COM.
b.

Question 2:
Do you want SYSTARTUP.COM updated to load PCS?
1

This question is whether to append PCS750.COM or
PCS750RES.COM to SYSTARTUP.COM (depending on your
answer to Question 1).

Answer "yes" to this question if this
is the
first
time you are running the update command to install PCS
loaders.
Answer "no" to this question if you are just updating
the binary file
or software, if you already have a
call to the command files in SYSTARTUP>COM, or if you
plan to use a different command file to load the PCS~

VMS UPDATE CHECKS
After the above two questions have been answered,
the update
command file will put the files in the proper locations and modify
SYSTARTUP.COM to load the PCS upon power-up or restart. When the
update command file is complete, do the following checks:

All files named PCS*.* are deleted out of [SYSUPD].

The following are in

[·~]:

[S';'SExE)

a•

PCS 7 5 0 • BIN

PCS? 50UTL. EXE

PCS750DRV.EXE
(only if you answered "yes" to Question 1).

If you answered "yes" to Question 1:

/JO

/VO

Check that PCS750RES.COM is in [SYSMGR].

Check that SYSTARTUP.COM has $ @PCS750RES
(as the last command) •

If you answered "no" to Question 1:
a.

Check that PCS750.COM is in [SYSMGR].

Check that SYSTARTUP.COM has $ @PCS750
{~i the last command).

Edit SYSTARTUP.COM so that either @PCS750 or @PCS750RES is
near the beginning.

Check that there is only one call to
SYSTARTUP.COM.

Reboot the system to load patches.

load

the

PCS

from

LJ•_ e rr1.iml':

SYSTFM

F' cl s s: 1iu I' tJ :
~

Wt'lcomt'
@Vl1Sl'JF'[ll"ITE

~:DCL-E-OF·E NIN r

lo VAX/VMS version V3.2

oPerii n!J SYS $SYSROOT: [ SYSMGR JVMSU
file not fo1Jr1d
11

-·nHS-E-F'NFr

._. l'l'O r

.COM; .:is inP•Jt

• SET. J;IEF C9YSUPf•1'
t

IH/MSUPill"ITE

VH8 UPdale Procedure
This con1lllcrH1d r:-rocedure Performs VllX/VHS software w-date5 '11•U
111-t.'~.onal
~ortwart.!
i11stallations
for
VAX/VMS
Reledst!'
J,
ltlJt•ir1!1 this ~l·01JE>nc:e1 the ·.:.tar1darrJ
cohsol!J
n1edi•Jm will inol
t•e .:,.l'!~ent ·in tl1e eonsolP
(frive. Therefurer
the s~sleni il•d':I
l•P. vulr1erabltt l.o '' f•ower
failure or olt11?r fatal cr;;ish, If u
· ·- ,, !!! t "'"'
t· '"1 '•II
., h u 111 d
o cc' Jr d •J r i n g th i s ·,,. e r i o d the u,, d <1 t e
s .. r11H·nce
c'"'
t•e
rl!'startPd
<it
the besinnin!1 of the f1 r~.t
i r1cu1111- le t1• 11>-d ... li:.

Ple-<!c ~,.lace

tl11•

volume ir1 lhe co11sole drive

f1tl:>l

_tr101J11ted 'on _CSA1 I

xc or ~ - s··cu F 1 [ ti , r. : 1.t : cs '( sur· r1 J f·· c El 7 ~; o • It IN ; 1 2 co r- i ,~ d to s Ys .s vs r, ooT : rn vs uf· [1 J f" cs 7 ~; o , B IN ; 1 2 < =~ 2 ti 1 o ck .., >
r. ~it'd: l '.' (!;[JF' fl J1·csnrnUTL' Dl'•J; ::i COP .i Pd lo SYS•fj y Sf\OOT: [!}'( SUf-'[I JPU; l'.iOUTL 'OllJ; 2 ( 6 l• lock~)
L ,, (1 1 : l !.i s IJ F'
r' cs 7 '.:i 0 Ms (i ' (J ll J ; 3 c 0 f' i L' d t 0 s ., s \ sys Fi 0 0 I : ( !) y s u ,. [I ]f' c s 7 5 0 Ms G • 0 fl J ; 3 ( 3 b l 0 ck!> )
/.COf-"(-5-LOf IEl11 CSrd:UiYSUF'VJf"Cfli'50,COM;l copied to SYS\SY~iROOTlnlYSUf·[1Jr·c57::;0,COM;1 <1 block)
I.CO F"f - S - C(J f- IE [1 , C S ~. 1 : f !i YSU f· n H' CS SYS , C0 M; l c e> r- i e d I. u SYS$ 5 Y Sr; 0 0 T l [ SYS lJ Ht Jr· CS SYS , C 0 M I 1 < 1 b 1 o d )
~ LI tit< F·C ~ 750iJT L, r· Cc 7 ~ OHSG/E XE> [ S YSEXE: J F'C S 7:JOUTL /NOTf.:1'\CE: l1ACh

·:coF (-S·-COF'l LI•'

··: c 0 I y - s - c rw J l I• '

I S[T •i'.,' .. ~·r. rr'
:: LI EL L Tl·- I - H Li r [[1 , S '( S Vi) ~ 1::0 0 T : l SYS lW [I JP CS 7 5 0 UT L , 0 IlJ i 2 de I tt t l"J
~'.[I [LE 1 E. - I .. [I [ L [ r E [I , '...· ( <; I·~; y sR() 0 T : r fjy s ll p LI) f·' cs 7 5 0 Mfj G ' 0 [iJ ; 3 de 11:' LI:' <..I
i;COF'Y-5-COf" I [ i i ' s ( s ! '3Y ,f·:UOT: [ s n;un1 J F'CS750. [!IN; 12 CUP i ed to SYS"5YSROOT: [ SYSEX[]f'CS750. [IJN; 12 ( 22 bl od ~)
":I' EL l TE - l - 1: LL [TE J1 , :, YS ~SYS f( Cl 0 T : [SYS lJ f' [I J f' CS 7 5 0 , [I IN i 12 de le Led
i;COf·(-'3-c :1f'llf•1 ~,1 ;1.S'(~;f·:OOJ:rsvsur·r1Jf''CS750.CQM;1 copied lo SYS$SYSr\OOT:CSYSMGRJf"CS750.COHi1 (1 block)
·~M·F·[ 1H1- J ··· r ('"TE f1, ~, YS i· S Y!.iRllOT: [ S Y!>Uf'[t Jt1YSTARTUF', COM; 1 c r1.1.; led
~J,f' r : ; ; L - L' '- l f j l 11 • s y s i : _, '( s I\ 0 0 T : u; y s MG f{ J s YS TMn u r· • c 0 M; 1 c 0 ,. i I! d t. 0 sys $ s y 5 R0 0 T I [ s y s u F' [I ] s y s T r~ RTu F' • c 0 M; 1 <O I' e c 0 I' u '.:> )
~;fit r !:IHI-<.,- M f t.rit•L [1, S 'f •J1; ~j ·r~;r\UOT: rn YSllf' [t JF'CSS YS, COM; 1 <lf'f'tH1dl!d lo SYS~; SYSFiOO T: [ SYSIJF'[I JS YSTARTUF', COH; 1 ( 3 re co rd!.)
/.COPY-·S-CO' IE [1. s fS$GYCJl\OOT: [ SYSUf'l'I] SYSTARTUF'. COM; 1 COP i ed to SYS$SHir\OOT: [ SYSHGr\ JSYUTARTUP I COH; 2 ( 1 bl od<.)
~~I1CL ( H - I - I~-~ l 1 t:[1, S '( <31i '> YSF\OOT: [ SY!lUf-'[t HIYSTAlnUF', COM; 1 •fol e Led
~. r1 [ L [ 1 : - I - : 1 i. L [ Tl l• , S '( '.; 1iS 'ffJI·: 0 0 T I UJ YGU f' l• JP CS 7 5 0 1 C0 MI 1 de l e t.I! d
•• 11 [ U H - I l• r L l l Lit , :; Y':d-::; YS IW 01 : l S Yti UI' Li J f· CS SYS , C0 Hi 1 de 1 c Lc d

'3 ( 1_; t Ii '1 tr MJ U.: : !3Y ~1 Tfil~ TU I' , C 0 H. ha Ii bf..' en mo rJ i: f i Rd to
Ju~>:: n.icr•Jcorfe 1·dt.t:hl!s witho11l batter~ buck•JP

/\IO Tr :

··vi•' r f' J J. I

1 l'COYt? r

. : •' ~ 1 ~ .:. N,:, Li r R : u Y fj T Mn u 1· 1 c UM · s Ii n u 1 d b"

:II

_;,,,i_

·or r:.-··

t•1

'" t·•· '-"J1·1

,:,,_.. ·1

'•

ed i t ed so
lo ·tt1c 'cciniu1~H11f file to lo&d PCR
l~F'CS'.l~10f;:ESl' J ~ 111 . 'dl' tlH! l!1H:linnir1!J,

•.:,,,. •.'idl

SYSH1Ald1CJU·

01·

1111•1·<·

i~ .•

·01il\I or1t• r:all

~'(')tSYSTEM· lld.,,L' ·r-,ut

to loud PC!)

tieer1 l"ur!'.led

rliP.

REliCJfJT

SYSTEM. TO Lf)AfJ HICF:OCOl!f': ·PATCHES

-:'

. I

'i
1'11l'

'JIJ•.J

l'l~firh··tu

1'u11t.111•Jv?:

":MOU.,,T-I-HOU~!TU1,

f-: • ' ll'.ll! ·~ t l' d
Ha'• f 11 L".
Sff. r•FT

tj I .

d .., l L'

CONSOLE
'., l' {I IJ l' n L' L'

f Lll.JJl•J •.

~Ys•svsroor:rsvsuPDJ
~[T

PEF SYSILOGIN

'YEfl

111our1led 011 _CSi'd l
i "' (.' 0 111 p 1 l! l e •

VAX-11/750
Software Installation Guide
AA-K410C-TE
READER'S COMMENTS
NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company's discretion. If you require a written reply and are eligible to receive one under Software
Performance Report (SPR) service, submit your comments on an SPR form.

Did you find this manual understandable, usable, and well organized? Please make suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent.

D
D
D
D
D
D

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student. programmer
Other (please specify)

Organization
Street
State _ _ _ _ _ _ Zip Code - - - - - or Country

Do Not Tear - Fold Here and Tape -

~nmnomn

No Postage
Necessary
if Mai led in the
United States

11111 1

BUSINESS REPL V MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

BSSG PUBLICATIONS ZK1-3/J35
DIGIT AL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03061

Do Not Tear - Fold Here