Digital PDFs

AA-DQ21C-TE

March 1980

114 pages

Original

4.3MB

Document:	VAX-11 Software Installation Guide
Order Number:	AA-DQ21C-TE
Revision:	000
Pages:	114
Original Filename:

OCR Text

VAX-11
Software Installation Guide
Order No. AA-0021 C-TE

March 1980

This document contains detailed instructions for installing, upgrading, and updating the VAX/VMS operating system.

VAX-11
Software Installation Guide
Order No. AA-0021 C-TE

SUPERSESSION/UPDATE INFORMATION:

This revised document supersedes
the VAX-11 Software Installation
Guide (Order No. AA-D0218-TE)

OPERATING SYSTEM AND VERSION:

VAX/VMS V02

SOFTWARE VERSION:

VAX/VMS V02

To order additional copies of this document, contact the Software Distribution
Center, Digital Equipment Corporation, Maynard, Massachusetts 01754

digital equipment corporation · maynard, massachusetts

First Printing, August 1978
Revised, February 1979
Revised, March 1980
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 thi~ document.
The software described in this document is furnished under a license
and may only be used or copied 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 or its affiliated companies.

@) 1978, 1979, 1980 by Digital Equipment Corporation

The postage prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in
preparing future documentation.
The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC
PDP
DECUS
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM
ASSIST-11
VAX
DECnet
DATATRIEVE

DECsystem-lo
DECtape
DIBOL
EDU SYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8
DECSYSTEM-20
RTS-8
VMS
IAS
TRAX

MAS SB US
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-11
TMS-11
ITPS-10
SBI
PDT

CONTENTS

Page
PREFACE

vii

SUMMARY OF TECHNICAL CHANGES

CHAPTER

OVERVIEW OF SOFTWARE INSTALLATION

1-1

1.1
1.1.1
1.1.2

1-2
1-2

1.6

VAX-11/780 CONSOLE SUBSYSTEM
Using the Console Subsystem
Using the System Console Block
Storage Device
OVERVIEW OF SYSTEM INSTALLATION
Stand-Alone Disk Save and Compress Utility
System Bootstrap Program
System Generation Utility
System Parameter Files
System Installation Summary
OVERVIEW OF SYSTEM_UPGRADING
System Upgrade Summary
OVERVIEW OF MAINTENANCE UPDATE AND OPTIONAL
SOFTWARE INSTALLATION
COMPUTER-ASSISTED INSTRUCTION COURSE FOR EDT
THE RSX-llS UPDATE CONSOLE FLOPPY DISKETTE

PREPARING TO BOOTSTRAP THE SYSTEM

2-1

2.1
2 .1.1
2 .1. 2
2.2
2.2.1
2.2.2
2.2.3

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

2.2.4

VAX/VMS SOFTWARE DISTRIBUTION KITS
Magnetic Tape Kit
RK07 Kit
COPYING THE DISTRIBUTION MEDIUM
Loading Stand-Alone DSC-2
Copying Tape to Disk
Copying Disk to Disk
Terminating Stand-Alone DSC-2

BOOTSTRAPPING AND INSTALLING THE SYSTEM

3-1

3.1
3.2
3.2.1
3.2.2

ENTERING COMMANDS TO THE CONSOLE PROGRAM
BOOTSTRAPPING THE SYSTEM
Conversational Bootstrap
Nonstop Bootstrap
LOGGING IN TO THE SYSTEM
MODIFYING THE SYSTEM PARAMETER FILE
ALTERING PAGING, SWAPPING, AND SYSTEM DUMP
FILE SIZES
DEFAULT BOOTSTRAP COMMAND PROCEDURE
Copying the Default Bootstrap
Command Procedure
Booting with Interleaved Memory
Automatic Restart
REBOOTING THE SYSTEM STOPPING IN SYSBOOT
REBOOTING USING THE DEFAULT BOOTSTRAP

3-2
3-2
3-4
3-7
3-8
3-8

1.2
1. 2 .1
1.2.2
1. 2. 3
1. 2 .4
1. 2. 5
1.3
1.3.1
1.4
1.5
CHAPTER

CHAPTER

3.3
3.4
3.5
3.6
3.6.1

3.6.2
3.6.3
3.7
~.8

iii

1-2
1-3
1-4
1-4
1-4
1-5
1-5
1-6
1-6
1-7
1-7
1-7

2-~
2-~

2-7

3-11
3-11

3-12
3-1/.
3-12
3-13
3-13

CONTENTS

Page

3.10
3.10.1
3.10.2

COPYING FILES TO OR FROM THE CONSOLE FLOPPY
DISKETTE
BUILDING AND COPYING A VAX/VMS SYSTEM DISK
Building a VAX/VMS System Disk
Copying a VAX/VMS System Disk

3-ln

THE SYSBOOT PROGRAM

4-1

4.1
4.2
4.3
4.4
4.5

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

4.7
4.8
4.9

INVOKING AND TERMINATING SYSBOOT
CONTINUE
DISABLE CHECKS
ENABLE CHECKS
HELP
SET (PARAMETER VALUE)
SET (START-UP FILE)
SHOW
USE

UPGRADING THE SYSTEM

5-1

5.1
5 .1.1
5 .1. 2
5.2
5.2.1
5.2.2
5.3
5.4
5.5

VAX/VMS UPGRADE MEDIA
Upgrade Components in Magnetic Tape Kit
Upgrade Components in RK07 Disk Kit
PREPARING TO UPGRADE THE SYSTEM
Freeing Up Space on the System Disk
Recording System Parameter Values
UPGRADING VAX/VMS
COMPLETING THE UPGRADE
TAILORING THE SYSTEM PARAMETER FILE

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

INSTALLING MAINTENANCE UPDATES AND OPTIONAL
SOFTWARE

3.9

CHAPTER

4.n

CHAPTER

6.1
6.2

3-14
3-14
3-15

4-n

4-7
4-8
4-9
4-12

5-7
5-8

6-1
6-1
6-1

6.2.1
6.2.2
6.3

DISTRIBUTION KITS
GENERAL INSTALLATION PROCEDURES
Preparing for Installation
Installation Completion
INSTALLING MAINTENANCE UPDATES

6-2
6-3
6-3

SYSBOOT MESSAGES

A-1

A. l

A.2

BOOT MESSAGES
SYSBOOT MESSAGES

A-1
A-2

APPENDIX

FILES OF THE VAX/VMS SYSTEM

B-1

APPENDIX

BOOTSTRAP COMMAND PROCEDURES

C-1

APPENDIX

VAX/VMS SOURCE KIT

D-1

APPENDIX

BOOT PROCESS

E-1

APPENDIX

Index-1

INDEX

CONTENTS

Page
FIGURES
FIGURE

1-1
1-2

VAX-11/780 Console Subsystem
Transferring the Software Distribution Kit to
Disk and Bootstrapping the System

1-2
1-3

TABLES
TABLE

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

3-4
4-1

B-1
B-2
B-3

B-4
B-5
B-6
B-7
B-8

How to Use this Manual
VAX/VMS Bootstrap Command Procedures
Parameter Files Provided by VAX/VMS
Parameter Values in Parameter Files Provided
by VAX/VMS
Recommended Paging, Swapping, and System Dump
File Sizes
Summary of the SYSBOOT 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 [SYSTF.ST]
Files Contained in Directory [SYSUPD]
Files Contained in Directory [SYSHLP.EXAMPLES]

1-1
3-3
3-9
3-10
3-11

4-1
B-2

B-n
B-n
B-7

B-7
B-8
B-11

B-12

PREFACE

MANUAL OBJECTIVES
The VAX-11 Software Installation Guide describes the
to:

procedures

used

•

Install a newly purchased VAX/VMS operating system on a VAX-11
processor

•

Upgrade an existing VAX/VMS operating system

•

Install maintenance updates and optional software products
an existing VAX/VMS operating system

INTENDED AUDIENCE
This manual is intended for VAX/VMS system managers or those users who
are responsible for managing and controlling the operating system.

STRUCTURE OF THIS DOCUMENT
This manual is organized as follows:
•

Chapter 1 presents three overviews of:
(1) installing a
system;
(2)
upgrading
a system;
and (3)
installing
maintenance updates and optional software products.

•

Chapter 2 describes the procedures for
distribution kit.

•

Chapter 3 describes the steps to be taken when bootstrapping a
system and lists the system parameters most likely to be
modified during the bootstrap process.

•

Chapter 4 describes the commands that can
system bootstrap program (SYSBOOT).

•

Chapter 5 describes the steps to
existing VAX/VMS operating system.

•

Chapter n describes the procedure for installing maintenance
updates to the system software. It also describes the general
procedure for installing optional software products.

•

Appendix A describes the error messages issued during
and includes corrective actions.

vii

copying

taken

the

issued
to

software

the

upgrade

SYSBOOT

•

Appendix B lists the DIGITAL-supplied
system disk and their contents.

•

Appendix C provides
procedures.

•

Appendix D describes the steps performed to copy
source kit.

the

•

Appendix E details the
initialize the system.

generate

samples

directories

console

steps

performed

bootstrap

the

command
VAX/VMS
and

ASSOCIATED DOCUMENTS

This document has no prerequisites; however, an understanding of the
information presented in the VAX/VMS Summary Description and Glossary
may prove helpful.
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 installed:
e

VAX/VMS Systef!l_.~.-~El~<J-~E~_l:;_(:Jl.l~cj~-

•

VAX/VMS

•

VAX-11 Utilities Reference Manual

OE~ra_!or__ '__~ __g~_!_de
- - - - - -~--~ ... ___ ,., .~. ~ •• , • .,._ ~ ~....,._~---•---~-------- ..- - - - - - - · · · - · · - · .. •'<"

For a complete list and descriptions of VAX-11 documents, including
optional software products documents, see the VAX-11 Information
Directory and Index.

viii

SUMMARY OF TECHNICAL CHANGES

The following technical changes have been made to the VAX-11
Installation Guide for version 2.0z

Software

•

A complete procedure for upgrading an existing VAX/VMS
has been incorporated in this manual.

•

The information on the system generation utility program
(SYSGEN) and the system parameters has been removed from this
manual and incorporated in the VAX/VMS System Manager's Guide.

•

The procedures for installing VAX-11
optional
software
products (for example, VAX-11 FORTRAN and VAX-11 COBOL-74)
have been removed from this manual.
Installation procedures
for VAX-11 optional software products are described in the
documentation shipped with those products.

•

Appendix B has been updated to reflect the addition and
deletion of files provided by DIGITAL on the VAX/VMS system
binary distribution medium.

system

CHAPTER 1

OVERVIEW OF SOFTWARE INSTALLATION

VAX-11 software installation falls into three general categories:
(1)
bootstrapping and installing a newly purchased VAX/VMS system;
(2)
upgrading an existing VAX/VMS system; and (3) applying maintenance
updates to a VAX/VMS system or installing optional VAX-11 software
products.
You can determine which type of installation procedures you should use
as follows:
•

If you have purchased a new VAX/VMS Version 2.0 operating
system, use the bootstrapping procedures described in Chapters
2 and 3.

•

If you have a VAX/VMS Version l.n operating system, and you
have not added user files to the system disk, use the
bootstrapping procedures described in Chapters 2 and 3.

•

If you have a VAX/VMS Version 1.6 operating system, and you
have added user files to the system disk, use the upgrading
procedures described in Chapter 5.
Table 1-1
How to Use this Manual
Relevant Chapters

Type of Installation
First system installation

1, 2, 3, 4

First system installation
and maintenance update/
optional software
installation

1, 2, 3, 4, 6

System upgrade

1, 5

System upgrade and
optional software
installation

1, 5, 6

Maintenance update/optional
software installation

1, 6

All installation procedures are performed using the VAX-11 console
subsystem. The remainder of this chapter describes this subsystem and
provides an overview of all three types of software installation.

1-1

OVERVIEW OF SOFTWARE INSTALLATION
1.1

VAX-11/780 CONSOLE SUBSYSTEM

You use the VAX-11/780 console subsystem to:
•

Bootstrap and install a VAX/VMS operating system

•

Upgrade a VAX/VMS operating system

•

Update a VAX/VMS
software products

operating

system

and

install

optional

The console subsystem consists of an LSI-11 microcomputer with loK
bytes of read/write memory and 8K bytes of read-only memory, or ROM
(used to store the LSI diagnostics;
the LSI
bootstrap,
and
fundamental console routines); a system console block storage device
(the floppy diskette drive); a console terminal, and an optional
remote diagnostic port.
Figure 1-1 shows a diagram of the basic
console subsystem.
Central
Processor
Unit

LSl-11

Port for

Microcomputer

remote===~

diagnostics

Figure 1-1

1.1.1

M
E

M...--0
R
y

VAX-11/780 Console Subsystem

Using the Console Subsystem

During system generation and start-up, the system manager uses the
console subsystem to bootstrap and initialize the operating system.
Later, the system manager uses the console subsystem to upgrade the
system software or to install maintenance updates or one or more
optional software products.
The console subsystem also serves as a diagnostic console fbr
operators and system specialists, and as a VAX/VMS system terminal for
system users.

1.1.2

Using the System Console Block Storage Device

The system console block storage device, that is, the floppy diskette
drive, is an integral part of the VAX/VMS operating system. During
system installation, the hardware bootstrap reads a program from the
console floppy diskette, which, in turn, loads the operating system
from the system disk.

1-2

OVERVIEW OF SOFTWARE INSTALLATION
The system console block storage device is also used to read:

1.2

•

Hardware diagnostic programs

•

Maintenance updates and optional software products

OVERVIEW OF SYSTEM INSTALLATION

The procedure to bootstrap and install a VAX/VMS operating system is
performed at the console terminal and includes the following steps:
1.

Copying the software distribution kit to disk using the
stand-alone version of the Disk Save and Compress Utility

Bootstrapping the system using the SYSBOOT program

Modifying (if desired) system parameters
SYSBOOT program or the SYSGEN utility

using

either

Figure 1-2 outlines the general installation procedure.
Place the console
bootstrap floppy
in console drive and
bootstrap
stand-alone DSC-2
STEP 1

-;
Copy the distribution
medium to disk using
stand-alone DSC-2
(tape-to-disk or
disk-to-disk)

•
STEP 2

Place the console
bootstrap floppy
in the console
floppy drive and
bootstrap VAX/VMS

STEP 3

Optionally, set any
system generation
parameters to the
desired values and tell
SYSBOOT to continue
bootstrapping VAX/VMS

Figure 1-2

Transferring the Software Distribution Kit to
Disk and Bootstrapping the System

1-3

the

OVERVIEW OF SOFTWARE INSTALLATION
1.2.1

Stand-Alone Disk Save and Compress Utility

The first step in installing a VAX/VMS system is to copy the software
distribution kit to a bootable medium. This means copying the kit to
a disk volume. To perform the copy operation, you use the stand-alone
version of the Disk Save and Compress Utility (stand-alone DSC-2).
Stand-alone DSC-2 lets you create a bootable medium if you received
your system on magnetic tape or lets you create a back-up volume if
you received your system on an RK07 disk.

1.2.2

System Bootstrap Program

In a VAX/VMS system, system generation
and
start
up
occur
automatically when the system is bootstrapped.
You provide the
information needed for system generation and start up by supplying to
the system bootstrap program (SYSBOOT) the names of files that contain
the system parameter values and start-up commands.
You can request that SYSBOOT prompt for commands during the bootstrap
operation.
This is referred to as a conversational bootstrap
operation. If you do so, you can perform the following functions:
the name of a file that
• Designate
values

contains

• Set and show individual parameter values
site-independent
an alternate
• Specify
procedure

system

parameter

start-up

command

If you do not specify an alternate site-independent start-up command
procedure, SYSBOOT uses the command procedure SYSSSYSTEM:STARTUP.COM
by default.
SYS$SYSTEM:STARTUP.COM
requests
execution
of
a
site-specific
start-up
command procedure (SYSTARTUP.COM), which
contains commands specified by the system manager
to
perform
site-specific start-up functions.
For example, SYSTARTUP.COM could
contain the SET TERMINAL commands that set the characteristics of the
installation's terminals.
SYSTARTUP.COM resides in the directory
[SYSMGR]. For detailed descriptions of the site-independent and
site-specific start-up command procedures, see the VAX/VMS System
Manager' ~-q-~_!_9_~.

1.2.3

System Generation Utility

Once all the system initialization steps have occurred, the system
creates a process to execute SYS$SYSTEM:STARTUP.COM.
Among the
commands contained in SYS$SYSTEM:STARTUP.COM are, by default, the
following:
$ RUN SYS$SYSTEM:SYSGEN
AUTOCONFIGURE ALL
These commands request the running of the system generation utility
(SYSGEN) and automatically configure the system to recognize all
standard (DIGITAL-supplied) devices attached to it. I/O drivers for
these devices also are loaded.

1-4

OVERVIEW OF SOFTWARE INSTALLATION
With SYSGEN you can perform the following functions:
•

Modify parameter values and create a system parameter
that can be used in a subsequent bootstrap operation.

file

•

Create contiguous files that can be used as the
swapping and paging files, and the system dump file.

•

Create and install noncontiguous files that can be used as
secondary swapping and paging files. These files can exist on
more than one volume in a multivolume set.

•

Dynamically connect new devices to the system and
I/O drivers.

•

Dynamically alter some of the current system parameter values.

•

Initialize multiport memory units.

primary

load

their

Anyone can run SYSGEN; however, you must have certain privileges to
execute device-related SYSGEN commands.
See the VAX/VMS System
Manager's Guide for complete information on using SYSGEN.

1.2.4

System Parameter Files

VAX/VMS provides several system parameter files that contain values
suitable
for the smallest through the largest VAX-11 hardware
configurations. Each system parameter has four values associated with
it:
•

The current value

•

The default or typical value

•

The minimum allowable value

•

The maximum allowable value

In SYSBOOT, the initial parameter values are the current values (that
is, the values in effect the last time the system was bootstrapped).
In SYSGEN, the initial parameter values are the default values.
You can specify the SET command to SYSBOOT
parameter to a value in the allowable range.

1.2.5

SYSGEN

set

any

System Installation Summary

The complete installation procedure encompasses the following
(references to descriptions of each step are in parentheses):

steps

Copy the software distribution kit to disk (Chapter 2)

Perform a conversational bootstrap operation (Section 3.2.1)

Select the appropriate system parameter
changes to be made (Section 3.4).

Compute the sizes of paging, swapping, and system dump
(Section 3.5)

1-5

file,

noting

any
files

OVERVIEW OF SOFTWARE INSTALLATION

Run SYSGEN to modify the
Section 3.4)

Alter the sizes of the primary paging and swapping files, and
the size of the system dump file (optional; Section 3.5)

Copy the bootstrap command procedure to
diskette (Section 3.6)

Reboot the system, using a conversational bootstrap operation
{Section 3.7)

10.

11.

Create the user authorization file and necessary
directories (VAX/VMS §_y_~t:~-~..... 1'1~.~Ci9.~_r 's_GuJ~~)

12.

Reboot, with default

system

bootstrap

parameter

command

the

file

(optional;

console

procedure

floppy

start-up
user

file

(Section

3.8)

13.

Install one or more optional software products (Chapter fi and
the documentation set for each product)

The system is now ready for use.

1.3

OVERVIEW OF SYSTEM UPGRADING

When a major revision of the operating system has been released (for
example, Version 2.0), you can replace your current system software
with the new system software. This process, referred to as system
upgrading, replaces only system software; all user-written software
remains intact. Thus, user files need not be copied from the system
disk to a back-up volume and then restored later.
A system command procedure (VMSUPDATE.COM) controls the system upgrade
operation.
(This command procedure is also used to apply maintenance
updates to the system software and to install optional software
products.) You provide the information to upgrade a system by (1)
setting up the proper conditions for the upgrade and (2) responding to
the messages displayed at the console terminal as the upgrade
procedure continues.

1.3.1

System Upgrade Summary

The complete system upgrading procedure encompasses the following
steps (references to descriptions of each step are in parentheses):
1.

Remove unimportant files from the system disk (Section 5.2.1)

Obtain a console printout of the current parameter values and
the original parameter values (Section 5.2.2)

Back up the system disk (Section 5.2.2)

Reboot from the newly created system disk (Section 5.2.2)

1-6

OVERVIEW OF SOFTWARE INSTALLATION
5.

system

upgrade

procedure

(Section

5.3)

Restore the user authorization file (Section 5.4)

Tailor the system parameter file (Section 5.5)

Install one or more optional software products (Chapter
the documentation set for each product)

Back up the system disk (Section 5.5)

n and

The system is now ready for use.

1.4

OVERVIEW OF MAINTENANCE UPDATE AND OPTIONAL SOFTWARE INSTALLATION

Updating a VAX/VMS operating system consists of adding to or replacing
one or more modules of system software between major releases of the
operating system; for example, between Version 1.0 and Version 2.0.
You update VAX/VMS by using the command procedure VMSUPDATE.COM.
You also use VMSUPDATE.COM to install optional VAX-11 software
products that are purchased separately. VAX/VMS supports a diverse
selection of optional software
products,
including
compilers,
communications facilities, and an interactive query facility.
This installation guide describes, in Chapter n, the
complete
procedure for updating the system software, but only the preparatory
and completion steps for installing optional software products.
The
complete procedure for installing an optional software product is
described in that product's documentation set.

1.5

COMPUTER-ASSISTED INSTRUCTION COURSE FOR EDT

The VAX/VMS software distribution kit includes seven floppy diskettes
that constitute the EDT Computer-Assisted Instruction (EDT CAI)
course. This course presents introductory material and lessons on the
DIGITAL Standard Editor, EDT.
To install EDT CAI, follow the
installation procedure described in the Introductio~,~- the~,~DT
Editor, Course Administrator Guide.

l.n

THE RS~-llS UPDATE CONSOLE FLOPPY DISKETTE

Accompanying the VAX/VMS software distribution kit is the RSX-llS
update console floppy diskette (part description: RSX-118 UPDATE
RXOl). With this floppy diskette, you can modify RSX-llS Version 2.2
software to let you generate an RSX-llS system on a VAX/VMS system.
NOTE
The
RSX-llS
Version
2.2
software
distribution kit is available under a
separate license.
To use the RSX-llS update console floppy diskette and perform a
subsequent
RSX-llS
system
generation, see the RSX-llS System
Generation and Installation Guide (order number:
AA-2874D-TC) and
Update #1 (AD-2874D-Tl).

1-7

CHAPTER 2
PREPARING TO BOOTSTRAP THE SYSTEM

The first step in installing the VAX/VMS operating system is to copy
the software distribution kit to your system dis~ (for example, an
RK07, RM03, or RP06), by using the stand-alone version of the Disk
Save and Compress Utility (stand-alone DSC-2) supplied as part of the
distribution kit. You copy the distribution kit to your system disk
for one of the following reasons:

2.1

•

To create a bootable medium, if you received a
kit

magnetic

•

To preserve the distribution medium, if you received
kit

tape
RK07

VAX/VMS SOFTWARE DISTRIBUTION KITS

There are two media for VAX/VMS software distribution kits:
•

Magnetic tape, in which the system binary distribution
is a 1600 bpi, 9-track magnetic tape

•

RK07 disk, in which the system binary distribution
an RK07 disk

medium

The bill of materials that comes with the kit lists exactly what your
VAX/VMS software distribution kit contains. After receiving a VAX/VMS
software distribution kit, you should check that
it
contains
everything listed in the bill of materials.

Magnetic Tape Kit

2.1.1

The following components are needed to copy the magnetic tape
distribution medium to\a bootable medium and bootstrap the system:

•

The system binary distribution tape
Part number:

BB-D782C-BE

Part description:

VMS V2.0 BIN MT9

2-1

PREPARING TO BOOTSTRAP THE SYSTEM
•

The floppy diskettes that contain stand-alone DSC-2
Part number:

AS-E808I-BE

Part description:
Part number:

AS-J831A-BE

Part description:
•

STAND/ALONE 11780 DSC2 FLP 1

STAND-ALONE 11780 DSC2 FLP 2

The console floppy diskette that contains the VAX/VMS
2.0
bootstrap
loading
programs
and bootstrap
procedures
Part number:

version
command

AS-Eh33I-YE

Part description:

RX 1/ 11780 LOCAL CNSL PKG

The following components, also contained in the magnetic tape kit, are
needed to upgrade the system to Version 2.0:
•

The system binary upgrade tape
Part number:

BB-J806A-BE

Part description:
•

The floppy diskette that drives the version
upgrade procedure
Part number:

l.~

to Version 2.0

AS-J803A-BE

Part description:

2.1.2

VMS V2.0 UPGRADE MT9

VMS V2.0 RXOl UPG

RK07 Kit

The following components are needed to back up the
medium and bootstrap the system:
•

distribution

The RK07 system binary distribution disk 1
Part number:

AY-H020C-BE

Part description:
•

RK07

VAX/VMS V2.0 BIN RK07

The floppy diskettes that contain stand-alone DSC-2
Part number:

AS-E808I-BE

Part description:
Part number:

STAND/ALONE 11780 DSC2 FLP 1

AS-J831A-BE

Part description:

STAND/ALONE 11780 DSC2 FLP 2

1. The RK07 system binary distribution
binary upgrade disk; see Chapter 5.

2-2

disk

doubles

the

system

PREPARING TO BOOTSTRAP THE SYSTEM
•

The console floppy diskette that contains
the
VAX/VMS
bootstrap loading programs and bootstrap command procedures
Part number:

AS-E633I-YE

Part description:

RX 1/ 11780 LOCAL CNSL PKG

The following component, also contained in the
needed to upgrade the system to Version 2.0:
•

The floppy diskette that drives the Version
upgrade procedure
Part number:

l.~

disk

kit,

to Version 2.0

AS-J803A-BE

Part description:

2.2

RK07

VMS V2.0 RXOl UPG

COPYING THE DISTRIBUTION MEDIUM

The VAX/VMS system can be bootstrapped only from disk. Thus, if you
receive a magnetic tape kit, you must copy the distribution tape to a
disk before you can bootstrap the system. You should then retain the
tape as a back-up copy of the distributed system.
If you receive an RK07 kit, you should back up the system by copying
the distribution disk to another disk before you bootstrap the system.
You should then use the newly created system disk to bootstrap the
system and retain the original disk as a back-up copy of the
distributed system.
To copy either a magnetic tape or an RK07 disk, use stand-alone DSC-2.
The VAX-11 Utilities Reference Manual contains a complete description
of the Disk Save and Compress Utility (DSC). The following sections
provide information specific to the use of stand-alone DSC-2 when
preparing to install a VAX/VMS operating system.

2.2.1

Loading Stand-Alone DSC-2

The procedure for loading stand-alone DSC-2 is as follows:
1.

Power up the system and halt the central processor.
following switches should be in the positions indicated:
a.

The ON-OFF rocker switch on the console terminal: ON.

The AUTO RESTART rocker switch on the
panel: OFF.

The rotary key
panel: LOCAL.

switch

the

The

processor

control

processor

control

See that the following processor control panel indicators are
lit: ATTN and POWER.

Turn on the needed disk drives and magnetic tape drives.

2-3

PREPARING TO BOOTSTRAP THE SYSTEM
4.

Place the console floppy diskette (part description:
RX l/
11780 LOCAL CNSL PKG) into the console floppy diskette drive,
as follows:
a.

Unlock and
processor.

open

the

cabinet

doors

the

Swing out the drive assembly until it is at a right angle
to the cabinet.

central

The drive assembly is a rectangular, unpainted steel box
in the lower right-hand corner of the central processor
cabinet. There is a black handle on the right of the
drive assembly.
Pull the handle to swing out the drive
assembly. The diskette cannot be inserted unless the
drive is swung all the way out.
c.

Insert the diskette into the drive.
Squeeze the black pushbutton to unlock the slot cover;
the cover will spring open. As you insert the diskette,
its label (on the smooth side of the diskette) should be
at the top and should face the right-hand cabinet door.
The oval slot on the diskette should be at the bottom.

Close the diskette slot cover.

Swing the drive assembly back into the central
cabinet.

processor

See that you have the attention of the console program:
it
will prompt with three angle brackets (>>>). If this prompt
does not appear, perform the following steps:
a.

Check that the console floppy diskette (part description:
RX 1/ 11780 LOCAL CNSL PKG) is in the console drive.

Set the AUTO RESTART switch to the OFF position.

Turn the rotary key to the LOCAL position, if it is not
already set to LOCAL.
Turning the power on boots the
console floppy diskette and causes the console program to
prompt.

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

In response to the console program prompt (>>>) displayed
the console terminal, type the following command:

>>>BOOT DSC
7.

Observe the following message on the console terminal:
CPU HALTED
!NIT SEQ DONE
LOAD DONE, 00002000 BYTES LOADED
Please insert first system diskette or cartridge and type <ret>

2-4

PREPARING TO BOOTSTRAP THE SYSTEM
8.

Remove the console floppy diskette from the drive and place
the first floppy diskette that contains stand-alone DSC-2
{part description: STAND/ALONE 11780 DSC2 FLP 1) in the
console floppy diskette drive and press <RETURN>.
NOTE
Do not type on the console terminal
while the system is being bootstrapped
unless prompted for input. If you do so
accidentally,
the fol~owing messages
will be printed:

SYSBOOT-W-FPLA,PCS or WCS version less than minimum required for VMS
SYSBOOT-W-Continue from halt to proceed with boot if desired
Either continue from the point where the
system halted or reboot. To continue,
type CONTINUE.
If you do not type on the console
terminal
while the system is being
bootstrapped and the messages
shown
above are printed, your machine is not
up to the correct ECO level.
Please
contact
your
local
field
service
representative.
9.

Observe, after about five minutes, the following
the console terminal:

message

Please insert second system diskette or cartridge and type <ret>
10.

Remove the first stand-alone DSC-2 floppy diskette from the
drive and place the second stand-alone DSC-2 floppy diskette
{part description: STAND/ALONE 11780 DSC2 FLP 2)
in the
console floppy diskette drive and press <RETURN>. After
about one minute, the following prompt will be displayed:
DSC2>
Stand-alone
commands.

DSC-2

now

running

and

ready

NOTE
Do not replace the stand-alone DSC-2
floppy with the console floppy until the
copy operation is complete.

2-5

PREPARING TO BOOTSTRAP THE SYSTEM

2.2.2

Copying Tape to Disk

To copy a magnetic distribution tape medium
follows:

disk,

proceed

Place the magnetic tape distribution medium on a magnetic
tape drive
(MTAO, for example), removing the write-enable
ring to protect the contents of the tape and place the drive
online.

Place a scratch disk on an appropriate disk drive (DBAO,
example) and place the drive online.

At the console terminal, enter the following DSC command:

for

DSC2> DBAO:/VE=MTAO:/RW
This command copies the contents of the magnetic tape
distribution medium on drive MTAO to an RPOn disk on drive
DBAO. The qualifier /RW causes the tape to be rewound before
the copy operation. The qualifier /VE causes the contents of
the disk and tape to be compared to make certain the copying
operation was a success.
Successful completion of the
copying and verification is signaled by the reappearance of
the prompt DSC2>.
Any messages you receive while stand-alone DSC-2 is running
are explained in the VAX-11 Utilities Reference Manual.

2.2.3

Copying Disk to Disk

To copy a RK07 distribution medium to a disk, proceed as follows:
1.

Place the RK07 distribution medium on an RK07 disk drive
(DMAl, for example).
Press the WRITE PROT push button on
this disk drive to protect the contents of the disk, then
place the drive online.

Place a scratch disk on an appropriate disk drive (DMAO,
example) and place the drive on line.

At the console terminal, enter the following DSC command:

for

DSC2> DMAO:/VE=DMAl:
This command copies the contents of the RK07 distribution
medium on drive DMAl to an RK07 disk on drive DMAO. The
qualifier /VE causes the output and the input to be compared
to
make certain the copying operation was a success.
Successful completion of the copying and verification is
signaled by the reappearance of the prompt DSC2>.
Any messages you receive while stand-alone DSC-2 is running
are explained in the VAX-11 Utilities Reference Manual.

2-n

PREPARING TO BOOTSTRAP THE SYSTEM
2.2.4

Terminating Stand-Alone DSC-2

To terminate stand-alone DSC-2, proceed
terminal:

follows

the

console

In response to the prompt DSC2>, press
following prompt will be displayed: >>>.

<CTRL/P>.

In response
<RETURN>.

HALT

this

prompt

(>>>),

The following confirming message and
displayed on the console terminal.

>»

type
prompt

and

will

The
press

then

HALTED AT •••

This message displays the contents of the program counter at
the time the processor was halted. The subsequent prompt is
a request for the next console command.
3.

Remove the distribution medium and the floppy diskette that
contains stand-alone DSC-2 from their respective drives.

Place
the
bootstrap
console
floppy
diskette
(part
description:
RX 1/ 11780 LOCAL CNSL PKG) in the console
floppy diskette drive.

For instructions on
Chapter 3.

bootstrapping

and

2-7

installing

the

system,

see

CHAPTER 3
BOOTSTRAPPING AND INSTALLING THE SYSTEM

Once you have copied the distribution medium to disk, you are ready to
bootstrap the VAX/VMS operating system. Proceed as follows to perform
the initial bootstrap:
1.

Bootstrap the system, stopping in SYSBOOT to specify that the
parameter file MINIMUM.PAR is to be used, as described in
Sections 3.1 and 3.2.1.

Select the appropriate DIGITAL-supplied parameter file and
note any changes to be made, as described in Section 3.4.

Compute the sizes of the paging file, swapping
system dump file, as described in Section 3.5.

file,

and

Run the SYSGEN utility to customize
the
selected
parameter file, if desired, as described in Section 3.4.

Use the SWAPFILES.COM command procedure to alter the
sizes of the primary paging and swapping files, and the
size of the system dump file, if desired, as described in
Section 3.5.

Copy the bootstrap command procedure to DEFBOO.CMD on
console floppy diskette, as described in Section 3.h.

Reboot the system, stopping in SYSBOOT to specify the name of
the selected parameter file, as described in Section 3.7.

Log in to the system again and customize the site-specific
start-up
command
procedure
([SYSMGR]SYSTARTUP.COM), as
described in the VAX/VMS System Manager's Guide.

Run the AUTHORIZE program to create the user authorization
file and the necessary user file directories, as described in
the VAX/VMS System Manager's Guide.

Install one or more optional software products, if desired,
as described in Chapter n and the documentation set for each
product.

10.

Reboot the system, as described in Section 3.8.

11.

Optionally, copy the system disk using the command
VMSKITBLD.COM, as described in Section 3.10.

The system is now ready for use.

3-1

the

procedure

BOOTSTRAPPING AND INSTALLING THE SYSTEM
3.1

ENTERING COMMANDS TO THE CONSOLE PROGRAM

To bootstrap the system, you must first invoke the console program.
To ensure that the console program is available for use, perform the
following steps:
1.

Check that the console floppy diskette (part description:
1/ 11780 LOCAL CNSL PKG) is in the floppy diskette drive.

Set the AUTO RESTART switch to the OFF position.

Turn the rotary key to the LOCAL position,
if it is not
already set to LOCAL. Turning the power on boots the console
floppy diskette and causes the console program to prompt
(>»).

If the power is already on,
press <CTRL/P> to cause the
console program to prompt (>>>). Type REBOOT to reboot the
console.

Before proceeding further, ensure that the disk to be
is write enabled.

booted

You are now ready to bootstrap your system.

3.2

BOOTSTRAPPING THE SYSTEM

You can bootstrap the system in either of the following ways:
•

Conversational -- Request that SYSBOOT stop and allow you to
modify the system parameters that configure the system. This
is the option to use the first time you bootstrap the system.

•

Nonstop -- Allow SYSBOOT to run
intervention.

completion

without

your

Console commands are used to request the bootstrapping of the system.
VAX/VMS provides a number of command procedures that contain the
necessary console commands to request a bootstrap from an RM03 or RPOh
disk device on the first MASSBUS controller, or from an RK07 disk
device on the UNIBUS.
The console floppy diskette contains these command procedures
sets:

two

•

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

•

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

3-2

BOOTSTRAPPING AND INSTALLING THE SYSTEM
Table 3-1 lists the names
console floppy diskette.

bootstrap

command

procedures

the

Table 3-1
VAX/VMS Bootstrap Command Procedures
Type of Command
Procedure

Name of Command
Procedure

Conversational bootstrap from
RK07

DMOGEN
DMlGEN
DM2GEN
DM3GEN

Conversational bootstrap from
RM03 or RP0611

DB OGEN
DBlGEN
DB2GEN
DB3GEN
DB4GEN
DBSGEN
DBnGEN
DB7GEN

Nonstop bootstrap from RK07

DMOBOO.CMD
DMlBOO.CMD
DM2BOO.CMD
DM3BOO.CMD

DBOBOO.CMD
DBlBOO.CMD
DB2BOO.CMD
DB3BOO.CMD
084800.CMD
DBSBOO.CMD
DBnBOO.CMD
.___________________.____n_s_7_s_o_o_. ~M~
Nonstop bootstrap from RM03
or RP0611

1. The bootstrap command procedures for RM03 and RPOn disks bootstrap
the disks from only the first MASSBUS adapter. To bootstrap an RM03
or RP06 from the second MASSBUS adapter, change the bootstrap command
procedure to deposit the value 9 rather than the value 8 into register
Rl. For an example, see the DBBBOO.CMD bootstrap command procedure on
the console floppy diskette.

3-3

BOOTSTRAPPING AND INSTALLING THE SYSTEM

NOTE
Do not type on the console terminal
while the system is being bootstrapped
unless prompted for input. If you do so
accidentally, the following messages may
be printed:
SYSBOOT-W-FPLA,PCS or WCS version less than minimum required for VMS.
SYSBOOT-W-Continue from halt to proceed with boot if desired.
Either continue from the point where the
system halted or reboot. To continue,
type CONTINUE.
If you do not type on the console
terminal
while the system is being
bootstrapped and the messages
shown
above are printed, your machine is not
up to the correct ECO level.
Please
contact
your
local
field
service
representative.

3.2.1

Conversational Bootstrap

To bootstrap the system and request that SYSBOOT stop to allow you to
change system parameters, type a command procedure name with the
following command format:
>>> @DxyGEN
@

Indicates that the rest of the line contains the name
command procedure located on the console floppy diskette.

Indicates the device type of the desired bootstrap device:
M RK07
B = RM03 or RP06

Specifies the unit number of the drive containing the volume to
be booted. This number is in the range of 0 through 3 if you are
booting from an RK07, or O through 7 if you are booting from an
RM03 or RP06.
When SYSBOOT is ready to accept commands, it prompts as follows:
SYS BOOT>
You can now issue any of the commands listed in Chapter 4.
The first time you bootstrap the system, type the following commands:
SYSBOOT> USE MINIMUM.PAR
SYSBOOT> CONTINUE
The second time you bootstrap the system, issue a USE command
specifying the name of the parameter file that you want ?YSBOOT to use
to generate your system. This can be one of the file names listed in

3-4

BOOTSTRAPPING AND INSTALLING THE SYSTEM
Table 3-2 (in Section 3.4) or it can be the name of a file created by
means of the SYSGEN utility.
The following example shows a
console
printout
obtained
by
bootstrapping the system using the bootstrap command procedure DMOGEN
and specifying the parameter file MYPARAM.PAR:
»> @DMOGEN

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

HALT

HALT PROCESSOR
C ')U

HALTED

UNJAM

UNJAM SB!

!NIT

!NIT PROCESSOR

!NIT SEQ DONE
DEPOSIT/I 11 20003800

SET UP SCBB

DEPOSIT RO 1

CARTRIDGE DISK

DEPOSIT Rl 3

UBA TR=3

DEPOSIT R2 3FF20

CSR ADDRESS OFFSET

DEPOSIT R3 0

CONTROLLER UNIT = 0

DEPOSIT R4 0

BOOT BLOCK LBN (UNUSED)

DEPOSIT RS 1

SOFTWARE BOOT FLAGS (CONVERSATIONAL BOOT)

DEPOSIT FP 0

SET NO MACHINE CHECK EXPECTED

START 20003000

START ROM PROGRAM

WAIT DONE

WAIT FOR COMPLETION

= 3FF20

HALT INST EXECUTED
HALTED AT 200034F9

EXAMINE SP
SHOW ADDRESS OF WORKING
G OOOOOOOE 00000200
LOAD VMB.EXE/START:@
l LOAD PRIMARY BOOTSTRAP
START @

MEMORY+~X200

LOAD DONE, 00002000 BYTES LOADED
l AND START IT

<@EOF>
<@EXIT>

3-5

BOOTSTRAPPING AND INSTALLING THE SYSTEM
SYSBOOT> HELP
Major SYSBOOT Commands are:
CONTINUE - Continue with boot process
EXIT
- Continue with boot process
SET
- Set parameter value
SET parameter-name value
SET /STARTUP file-spec
SHOW
- Show parameter value (s)
SHOW parameter name
/ACP - Show ACP parameters
/ALL - Show ALL parameters
/GEN - Show generative parameters
/MAJOR - Show MAJOR parameters
/NAMES - Show parameter names
/PQL - Show Process Quota List values
/RMS - Show RMS parameters
/STARTUP - Show Startup command file name
/SYS - Show SYSTEM parameters
USE
- Set parameter file name
USE file spec.PAR
Res~rved filespecs are:
DEFAULT - Use permanent defaults
CURRENT - Use current values
SYSBOOT>
SYS BOOT>

USE MYPARAM.PAR
SHOW /MAJOR

Parameter Name

Current

Default

Minimum

Maximum

GBLSECTIONS
GBLPAGES
MAXPROCESSCNT
SYSMWCNT
BALSETCNT
IRPCOUNT
WSMAX
NPAGEDYN
PAGEDYN
VIRTUALPAGECNT
QUANTUM
MPW WRTCLUSTER
MPW HILIM
MPW-LOLIMIT

127
80
3072
64
100
40
240
700
109568
32768
8192
30
64
128
96

10
40
2048
64
48
24
80
256
40448
8192
8192
30
16
24
12

0
20
512
12
20
4
0
60
16384
8192
512
2
0
0
0

127
-1
-1
256
111384
1024
32768
111384
-1
-1
1155311
32767
127
16384
10384

PAGES
SECTIONS
PAGES
PROCESSES
PAGES
SLOTS
PACKETS
PAGES
BYTES
BYTES
PAGES
lOMS
PAGES
PAGES
PAGES

512

65531)

PAGES

-------------PFCDEFAULT

-------

SYS BOOT>

SET BALSETCNT 8

SYS BOOT>

SET VIRTUALPAGECNT 999999

%SYSBOOT-W-Value set to maximum
SYS BOOT> SHOW VIRTUALPAGECNT
VIRTUALPAGECNT
65536
SYS BOOT>
VAX/VMS

------- -------

8192

Unit

CONTINUE
Version V2.0 30-MAR-1980 15:40

Opcom, 30-MAR-1980 15:25:24.26 Logfile initialized, operator=_OPAO:
Login quotas - Interactive limit=64, Current interactive value=O
SYSTEM
job terminated at 30-MAR-1980 15:27:51.47

3-6

BOOTSTRAPPING AND INSTALLING THE SYSTEM
3.2.2

Nonstop Bootstrap

To perform a bootstrap operation without stopping in SYSBOOT,
command procedure name with the following command format:

type

>>> @DxyBOO.CMD
@
Indicates that the rest of the line contains the name of a
command procedure that is located on the console floppy diskette.

x
Indicates the device type of the desired bootstrap device:
M = RK07
B
RM03 or

RPO~

Specifies the unit number of the drive containing the volume to
be booted. This number is in the range of 0 through 3 if you are
booting from an RK07, or 0 through 7 if you are booting from an
RM03 or RPOn.
Note that you can type a command in the following format to perform
nonstop bootstrap operation:

>>> BOOT Dxy
For example, BOOT DMO is equivalent to @DMOBOO.CMD.
If you use the
long form
(@DxyBOO.CMD),
the contents of the command procedure are
displayed on the console.
If you use the short form,
they are not
displayed.
The following console printout was obtained by bootstrapping
system using the bootstrap command procedure DMOBOO.CMD:

the

>>> BOOT DMO
CPU HALTED
INIT SEQ DONE
HALT INST EXECUTED
HALTED AT 200034F9
G OOOOOOOE 00000200
LOAD DONE, 00002000 BYTES LOADED
VAX/VMS Version V2.0 30-MAR-80 15:40
Opcom, 30-MAR-1980 15:42:01.87, Logfile initialized, operator=_OPAO:
Login quotas - Interactive limit=n4, Current interactive value=O
SYSTEM
job terminated at 30-MAR-1980 15:42:28.91

3-7

BOOTSTRAPPING AND INSTALLING THE SYSTEM
3.3

LOGGING IN TO THE SYSTEM

Once the system is loaded into memory and initialized, it announces
itself as illustrated above.
At this point, you can log in to the
system as the system manager by performing the following steps at the
console terminal:
1.

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

The system prints the following message and
Language (DCL} command interpreter prompts:

the

password,
DIGITAL

Command

console

WELCOME TO VAX/VMS Version V2.0
$

When the DCL command interpreter prompt ($}
terminal, the system is now ready for use.

3.4

appears

the

MODIFYING THE SYSTEM PARAMETER FILE

The VAX/VMS software distribution kit contains
several
system
parameter files, each of which generates a system appropriate for a
particular hardware configuration. These files are listed in Table
3-2. The parameter values defined in each file are generally suitable
for the intended configuration. By selecting the system parameter
file that best matches your hardware, you can produce a working system
in a relatively short period.
Once you have selected the system parameter file most appropriate for
your configuration, you can modify the values of individual parameters
and write a new file. The most common changes are:
e

Increasing the values of the
WSMAX
or
VIRTUALPAGECNT
parameters to accommodate a particular application

Increasing the value of
additional devices

the

NPAGEDYN

parameter

support

Table 3-3 lists the major system parameter values and the system
parameter values most likely to change in the parameter files provided
by VAX/VMS.
To modify individual parameter values and write a new parameter
proceed as follows:
1.

Set your default device and directory to SYS$SYSTEM using the
following DCL command:
$

file,

SET DEFAULT SYS$SYSTEM

Invoke the SYSGEN utility with the following command:
$ RUN SYSGEN

3-8

BOOTSTRAPPING AND INSTALLING THE SYSTEM
3.

Enter a USE command specifying the parameter file to be
as the source of parameter values. For example:

used

SYSGEN> USE 16USER.PAR
4.

Change the values in the parameter file.
SYSGEN> SET VIRTUALPAGECNT

Create a file that contains the
For example:

For example:

8192
modified

parameter

values.

SYSGEN> WRITE MYPARAM.PAR
6.

Exit from SYSGEN, as follows:
SYSGEN> EXIT
$

The VAX/VMS System Manager's Guide contains a complete description
the SYSGEN utility and the system parameters.
Table 3-2
Parameter Files Provided by VAX/VMS
Parameter File Name

Description

!-------------------·-· ------------

MINIMUM. PAR

512KB memory
Console terminal
Console floppy
Bootstrap disk

BUSER.PAR

512KB memory
2 RK07 disks
8 DZll lines

16USER.PAR

7'18KB-1024KB memory
2 RM03 disks
H DZll lines

32USER.PAR

1024KB-153nT<B memory
2 RPOn disks
32 DZll lines

48USER.PAR

153nKB-2048T<B memory
2 RPOn disks
48 DZll lines

64USER.PAR

2048KB-3072KB memory
2 RPOn disks
o4 DZll lines

VIRT32MB.PAR

1024KB memory
2 RP06 disks
Hi DZll lines
Support of 32MB virtual
address space

3-9

Table 3-3
Parameter Values in Parameter Files Provided by VAX/VMS

Parameter Name

1I
I MINIMUM

w
I

......
0

16
PFCDEFAULT
GBL SECT IONS
20
GBLPAGES
1024
MAXPROCESSCNT
12
SYSMWCNT
80
BALSETCNT
5
IRPCOUNT
0
i
WSMAX
256
I
NPAGEDYN
32128
16384
PAGEDYN
4096
VIRTUAL PAGECNT
I
60
QUANTUM
8
I MPW WRTCLUSTER
I MPW-HILIM
10
MPW-LOLIM
4
SPTREQ
700
0
I WSINC
FREELIM
10
BUGCHECKFATAL
0
TTY DEFCHAR
268440224
MAX~RINTSYMB
1
DEFPRI
4
IJOBLIM
4
1
BJOBLIM
I
1
NJOBLIM
I
16
ACP _SHARE
I
0
1
ACP MAPCACHE
1
ACP-HDRCACHE
I
4
ACP=DIRCACHE
;
4
ACP FI DC ACH
I
8
ACP-EXTCACHE
8
ACP=EXTLIMIT
200

I
I

Parameter File Name
BUSER
16
30
2048
20
100
12
200
256
51200
24576
4096
60
16
24
12
650
21
10
0
268440224
1
4
9
l
16
0
2
6
8
8
8
200

32USER

48USER

64USER

3VIRT32MB

64
48
3072
48
140
34
530
512
131072
409fi0
l
8192
60
64
92
32
700
21
16
0
268440224
4
4
33
4
16
1
12
40
50
12
16
I
200

127
80
3072
fi8
160
52
650
700
159744
49152
8192
fiO
127
220
100
700
21
lfi
0
268440224
8
4
49
8
16
1
20
80
100
16
32
I
200

127
80
3072
84
180
fi8
750
1024
179712
65536
8192
60
127
320
200
700
21
10
0
268440224
8
4
65
8
16
1
20
120
150
Hi
32
200

127
32
2048
28
120
8
300
1024
921')0
32768
fi553fi
60
127
220
96
700
21 I
10
0
268440224
2
4
17
4
11)
1
4
12
16
8
16
200

16USER
32
32
2048
28
120
20
275
25fi
74240
28672
4096
60
32
44
16
700
21
10
0
268440224
1
4
17
1
Hi
0
4
12
10
8
16
200

°'

0
0

Cll

".,,.,,>
1-4

>
z
0

1-4

Cll
~

>
~
~

1-4

Cl
~

:c
tSJ

Cll

tSJ

BOOTSTRAPPING AND INSTALLING THE SYSTEM
3.5

ALTERING PAGING, SWAPPING, AND SYSTEM DUMP FILE SIZES

VAX/VMS provides a command procedure in the directory [SYSUPD]
to
simplify the alteration of the of the sizes of the primary paging and
swapping file, and the size of the system dump file. To execute the
command procedure, log in as the system manager, as described in
Section 3.3, and type the following command:
$ @[SYSUPD]SWAPFILES

The command procedure prints the current value of the paging,
swapping, and system dump files, then prompts for new file sizes. In
response to each request for a file's size, either press <RETURN> to
leave the file size unchanged; or, type a new file size, then press
<RETURN>. To avoid a system failure, do not delete the old files
until the system is rebooted.
Table 3-4 lists the recommended paging file, swapping file, and system
dump file sizes, in blocks, for the system parameter files that
VAX/VMS provides. The VAX/VMS System Manager's Guide describes size
guidelines for these files in greater detail.
Table 3-4
Recommended Paging, Swapping, and System Dump File Sizes
Parameter File Name
File Type

MINIMUM

BUSER

HUSER
----1

PAGEFILE.SYS
SWAPFILE.SYS
SYSDUMP.DMPl

8192
3072
516

8192
5120
1028

16384
7lfi8
2052
.

32USER

·-,

48USER

fi4USER

VIRT32MB

98304
8fi0lfi
fil48

98304
28fi72
'2052

- - - - - -t - - - - - - - ·327fi8
2457fi
3076

fil440
47fi00
4100
.

_..

1. To calculate the exact size of the system dump file, use the
following equation:SYSDUMP.DMP =number-of-pages-of-physical-memory+ 4

3.6

DEFAULT BOOTSTRAP COMMAND PROCEDURE

Once you have selected the bootstrap command procedure to be used for
your system, you should copy it to the console floppy diskette, giving
it a file name of DEFBOO.CMD. This establishes it as the default
bootstrap command procedure.
The default bootstrap command procedure is used in several situations:
Section

•

When the system automatically reboots itself;
describes the automatic bootstrap operation

•

When you press the BOOT switch on the processor control panel

•

When you issue the console command BOOT without
device name

3-11

3.h.3

specifying

BOOTSTRAPPING AND INSTALLING THE SYSTEM
3.6.1

Copying 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 floppy diskette. To use SETDEFBOO, first log in to the
system as the system manager and type the following:
$ @[SYSUPD]SETDEFBOO

SETDEFBOO asks you to confirm that the console floppy diskette is in
the console drive and requests the name of the bootstrap command
procedure that is to become the default:
Is the system console storage medium mounted? (Y/N):
Enter name of default boot command file:
Once you enter the name of the appropriate bootstrap
command
procedure, for example, DMOBOO.CMD, SETDEFBOO copies the specified
bootstrap command procedure to DEFBOO.CMD on the console floppy
diskette.
When it finishes the copying operation, SETDEFBOO issues
the following message:
Default boot command file replaced with <file-name>

3.6.2

Booting with Interleaved Memory

To bootstrap the system with interleaved memory, the system must
conform to certain requirements, as described in the VAX-11/780
Hardware Handbook. If your system meets these requirements and you
wanE--··--·IEe-····m-em-or·y--to be interleaved, edit the default bootstrap command
procedure and the restart command procedure (RESTAR.CMD) to include
commands that modify the memory controller registers. Appendix C
contains examples of command procedures (DMOBOO.ILV,DBOBOOILV, and
RESTAR.ILV) used to bootstrap systems with interleaved memory.

3.6.3

Automatic Restart

The VAX-11 processor is designed for unattended, continuous operation.
It is able to restart or reboot itself in the event of power failure
and recovery or any processor halt condition. To enable the automatic
restart feature, set the AUTO RESTART rocker switch on the processor
control panel to the ON position.
Automatic restarting should be
disabled during the installation procedure, but should be enabled once
the installation procedure is completed.
When automatic restart is enabled and a power failure and recovery or
halt occurs, the processor deposits the contents of the progr~m
counter (PC) and the processor status longword (PSL) at the time of
the halt into registers RlO and Rll and deposits a code giving the
reason for the restart into the Argument Pointer (AP) • The processor
then invokes the command procedure RESTAR.CMD, which is listed in
Appendix c. After a power recovery, the restart ROM program checks to
determine whether the contents of memory are still valid (battery
back-up required) and whether the VAX/VMS restart routine can be
located.
If both conditions are satisfied, the restart ROM program
passes control to the restart routine;
otherwise, the system is
rebooted using DEFBOO.CMD.
Any condition other than power recovery results in a VAX/VMS fatal
bugcheck and an automatic rebooting of the system using DEFBOO.CMD.

3-12

BOOTSTRAPPING AND INSTALLING THE SYSTEM
3.7

REBOOTING THE SYSTEM STOPPING IN SYSBOOT

To halt the processor when VAX/VMS
system, proceed as follows:
1.

Shut down the
procedure:

system

running

executing

and

the

reboot

following

the

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

Bootstrap the system, using
procedures:

one

the

following

command

>>> @DMyGEN
>>> @DByGEN
The letter y denotes the unit number of the drive containing
the volume to be booted. This number is in the range of 0
through 3 if you are booting from an RK07, or 0 through 7 if
you are booting from an RM03 or RPOfi.
4.

When SYSBOOT prompts, issue a USE command specifying the name
of the parameter file that you wrote and continue. For
example:
SYSBOOT>

USE MYPARAM.PAR

SYSBOOT>

CONTINUE

When VAX/VMS announces itself, the new parameter values
paging, swapping, and system dump files are in use.

3.8

and

the

new

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; that is,
parameter values have been established. Rather, you can bootstrap the
system using the default bootstap 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.

3-13

BOOTSTRAPPING AND INSTALLING THE SYSTEM

3.9

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
processor control panel.

the

BOOT

push

button

the

COPYING FILES TO OR FROM THE CONSOLE FLOPPY DISKETTE

Occasionally, you may want to copy files, other than DEFBOO.CMD, from
the console floppy diskette, edit them, and place them back on the
diskette. VAX/VMS provides a command procedure named DXCOPY.COM in
the directory· [SYSUPD] to simplify the copying of text files (that is,
ASCII files such as bootstrap command procedures) to or from the
console floppy diskette.
To request the execution of the command
files, proceed as follows:
1.

procedure

and

copy

the

Invoke the command procedure by typing:
$ @[SYSUPD]DXCOPY

The command procedure asks whether
diskette is mounted, as follows:

the

console

floppy

Is the console floppy diskette mounted (Y/N)?:
a.

If it is not,
instructions:

type

and

observe

Please place the console floppy diskette in
drive and type <ret> when ready.
b.
3.

following

the
the

console

If it is, type Y to continue

The command procedure then asks whether the copy operation is
from the console floppy diskette, as follows:
Copy from console medium (Y/N)?:
You can type Y to indicate a copy from the console floppy
diskette to the current default directory, or you can type N
to indicate a copy from the current default directory to
console floppy diskette.

3.10

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

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. Sections 3.10.1 and 3.10.2, below, describe
how to use VMSKITBLD.COM.

3-14

BOOTSTRAPPING AND INSTALLING THE SYSTEM
NOTE
Do not press <CTRL/C> or <CTRL/Y> while
running VMSKITBLD.COM.
Doing so causes
the command procedure to unconditionally
terminate.

3.10.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 RPOn or
RM03 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 or RM03 disk.
NOTE
The building procedure destroys
all
previous information on the target disk
before it builds the system.
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
follows:
1.

Establish the following default directory:

$ SET DEFAULT [SYSUPD]
3.

Place either an RPOn or RM03 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

Supply the needed information about
disks as prompted.

the

source

and

target

You then receive the following query:
Is this a BUILD or COPY operation?
Answer by typing BUILD.
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.

3-15

BOOTSTRAPPING AND INSTALLING THE SYSTEM
In the process of building a bootable VAX/VMS system on an RP06 or
RM03 disk, this command procedure automatically creates a larger swap
file, a larger page file, and a larger system dump file than were in
the original RK07 binary distribution kit.
Thus, the resulting
VAX/VMS system is suitable for running off an RPOn or RM03 system
disk.
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 is ready to be bootstrapped.

3.10.2

Copying a VAX/VMS System Disk

You can also use VMSKITBLD.COM to copy the files of the VAX/VMS system
binary disk onto 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 [SYSUPD]

Place a target disk on an appropriate drive.

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

Supply the needed information about
disks as prompted.

the

source

and

target

You then receive the following query:
Is this a BUILD 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.
VMSKITBLD.COM informs you when the copy operation
sending the following message to your terminal:
Kit is complete.
At this point, the disk is ready to be bootstrapped.

3-16

complete

CHAPTER 4
THE SYSBOOT PROGRAM

You can use a subset of the commands of the SYSGEN utility with the
SYSBOOT
program, which actually allocates the necessary system
structures based on the system parameter values.
The commands that
can be used with SYSBOOT are listed in Table 4-1 along with a brief
description of each command. Detailed descriptions of these commands
are in Sections 4.2 through 4.9. The SYSGEN utility is described in
the VAX/VMS System Manager's Guid~.
Table 4-1
Summary of the SYSBOOT Commands
Description

Command
CONTINUE

Resumes the bootstrapping operation

DISABLE CHECKS

Inhibits checking of system parameter
values specified with the SET command

ENABLE CHECKS

Permits checking of system parameter
values specified with the SET command

HELP

Displays a summary of
commands at your terminal

SET (parameter-value)

Establishes
parameter

SET (start-up file)

Specifies the start-up command procedure
to be executed after SYSBOOT

SHOW

Displays specific system parameters

USE

Specifies the system parameter
be used as a source of values

4-1

the

value

the
of

SYS BOOT
a

system

file

THE SYSBOOT PROGRAM
4.1

INVOKING AND TERMINATING SYSBOOT

You invoke SYSBOOT by typing the name of a bootstrap command procedure
in response to the console program prompt (>>>). The name of the
command procedure represents the following information:
•

The device and
bootstrapped

unit

containing

the

disk

volume

•

Whether you want SYSBOOT to prompt
bootstrap operation

for

commands

during

the

To resume bootstrapping of the system, if you stopped in SYSBOOT, type
CONTINUE.
The following example demonstrates
operation, stopping in SYSBOOT:

typical

system

bootstrap

>>>@DBOGEN

SYSBOOT> CONTINUE
This console command invokes the DBOGEN command procedure, which will
bootstrap VAX/VMS from the RPOn or RM03 (unit 0) device and stop in
SYSBOOT. After the necessary modifications are made, the CONTINUE
command resumes the bootstrap operation.

4-2

THE SYSBOOT PROGRAM

CONTINUE
4.2

CONTINUE

The CONTINUE command allows the system
continue without further intervention.

bootstrapping

operation

Format

CONTINUE
Examples

SYSBOOT> CONTINUE
This command
system.

causes

SYSBOOT

4-3

resume

bootstrapping

the

THE SYSBOOT PROGRAM

DISABLE CHECKS
4.3

DISABLE CHECKS

The DISABLE CHECKS command inhibits the range checking SYSBOOT
performs on parameter values. By default, range checking is enabled
for SYSBOOT. When range checking is enabled, if you attempt to set a
parameter to a value that is above the maximum, SYSBOOT will set it to
the maximum and issue a warning message to inform you. If you attempt
to set a parameter to a value that is below the minimum, SYSBOOT will
set it to the minimum and issue a warning message.
Format
DISABLE CHECKS
Examples
SYSBOOT> SET WSMAX 20
%SYSBOOT-W-Value set to minimum
SYSBOOT> DISABLE CHECKS
SYSBOOT> SET WSMAX 20
SYSBOOT> SHOW WSMAX
WSMAX
20
25n

PAGES

In this sequence of commands, the user first attempts to set
WSMAX to 20 while range checking was enabled; SYSBOOT issues a
warning message. The user then issued the second command to
disable range checking.
Subsequent commands set the current
value of WSMAX to 20 and displayed WSMAX values, respectively.
Note
If you create a parameter file containing values that are outside the
normal range, and want to use the parameter file with SYSBOOT, you
must issue a DISABLE. CHECKS command to SYSBOOT.
Otherwise, SYSBOOT
does not allow you to use parameter values that are not in the
standard range.

4-4

THE SYSBOOT PROGRAM

ENABLE CHECKS
4.4

ENABLE CHECKS

The ENABLE CHECKS command requests that SYSBOOT ensure that parameter
values changed using the SET command remain in the allowable range.
By default, range checking is enabled.
If you attempt to set a
parameter to a value that is above the maximum, SYSBOOT will set it to
the maximum and issue a warning message to inform you. If you attempt
to set a parameter to a value that is below the minimum, SYSBOOT will
set it to the minimum and issue a warning message.
Format
ENABLE CHECKS
Examples
SYSBOOT> ENABLE CHECKS
SYSBOOT> SET GBLSECTIONS 18
%SYSBOOT-W-Value set to minimum
SYS BOOT>
In the sequence above, the first command enables range checking.
The second command attempts to limit the number of global
sections in the system to 18;
the m1n1mum value for that
parameter is 20.
SYSBOOT sets the parameter value to 20 and
issues the warning message.

4-5

THE SYSBOOT PROGRAM

HELP
4.5

HELP

The HELP command displays a summary of
during SYSBOOT.

commands

that

are

available

Format

HELP
Examples

SYSBOOT> HELP
Major SYSBOOT Commands are:
CONTINUE
- Continue with boot process
EXIT
- Continue with boot process
SET
- Set parameter value
SET parameter name value
SET /STARTUP file spec
SHOW
- Show parameter value(s)
SHOW parameter name
/ACP - ~how ACP parameters
/ALL - Show ALL parameters
/GEN - Show generative parameters
/MAJOR - Show MAJOR parameters
/NAMES - Show parameter names
/PQL - Show Process Quota List values
/RMS - Show RMS parameters
/STARTUP - Show Startup command file name
/SYS - Show SYSTEM parameters
USE - Set parameter file name
USE file spec.PAR
Reserved f ilespecs are:
DEFAULT - Use permanent defaults
CURRENT - Use current values
The HELP command displays the HELP information
SYSBOOT.

4-6

available

during

THE SYSBOOT PROGRAM

SET (PARAMETER VALUE)
4.6

SET (PARAMETER VALUE)

The SET (Parameter Value) command allows you to establish the value of
a
system
parameter.
If SYSGEN is not used to make further
modifications, the parameter values currently established are carried
over to the next bootstrapping of the system.
Format

SET parameter-name value
parameter-name
Specifies the name of the parameter for which the new value is to
be established. The VAX/VMS System Manager's Guide provides the
names of and describes all the parameters.
value
Specifies the value of the parameter. The value can be either a
decimal number in the allowable range for that parameter or the
keyword DEFAULT.
If you specify DEFAULT, SYSBOOT uses the default or typical value
assumed by SYSBOOT.
Examples
1.

SYSBOOT> SHOW PFCDEFAULT
PFCDEFAULT
16
ln
SYSBOOT>

SET PFCDEFAULT

127

PAGES

The first command above displays the current, default,
m1n1mum, and maximum values for the page fault cluster
default size. The SET command raises the cluster size to 20.
2.

SYSBOOT>

SET GBLSECTIONS DEFAULT

This command sets the number of global section descriptors to
be allocated by SYSBOOT to the default value of 40.

4-7

THE SYSBOOT PROGRAM

SET (START-UP FILE)
4.7

SET (START-UP FILE)

The SET (Start-up File) command specifies the name of an alternate
site-independent start-up command procedure to be executed as the
system is bootstrapped. By default, the start-up process executes the
SYS$SYSTEM:STARTUP.COM command procedure.
Format

SET /STARTUP file-spec
/STARTUP
Indicates that the SET command is to designate a start-up command
procedure.
file-spec
Specifies the name of the start-up command procedure to be
The file must be located on the system disk.

used.

Examples

SYSBOOT>

SET /STARTUP SYS$SYSTEM:NEWSTART.COM

This command establishes
SYS$SYSTEM:NEWSTART.COM.

the

start-up

command

procedure

Note

If you use the parameter file MINIMUM.PAR, the site-independent
start-up command procedure is SYS$SYSTEM:STARTUP.MIN

4-8

THE SYSBOOT PROGRAM

SHOW
4.8

SHOW

The SHOW command displays the names of system parameters, or the
values associated with system parameters. The SHOW command displays
four values for each parameter and indicates the unit of measure
associated with the values:
e

Current value

•

Default value

•

Minimum allowable value

•

Maximum allowable value

A -1 in the minimum or maximum value column indicates that no
or maximum value exists for the parameter.

minimum

Format
SHOW parameter-name
Command Qualifiers
/ACP
/ALL
/DYNAMIC
/GEN
/JOB
/MAJOR
/NAMES
/PQL
/RMS
/STARTUP
/SYS
~arameter-name

Specifies the name of a single parameter for which the value is
to be displayed.
If you specify a parameter name, you cannot
include a qualifier in the command.
You can issue the following command to display the names
parameters:

all

names

SHOW /NAMES
The most frequently used parameter names (that is, the
parameters in the major category) follow:
BALSETCNT -- balance set count
GBLPAGES -- global pages
GBLSECTIONS -- global sections
IRPCOUNT -- I/O request packet count
MAXPROCESSCNT -- maximum process count
MPW HILIM -- modified page list high limit
MPW-LOLIMIT -- modified page list low limit
MPW-WRTCLUSTER -- modified page write cluster size
NPAGEDYN -- nonpaged dynamic memory

4-9

THE SYSBOOT PROGRAM

PAGEDYN -- paged dynamic memory
PFCDEFAULT -- page fault cluster default size
QUANTUM -- time quantum
SYSMWCNT -- system maximum working set count
VIRTUALPAGECNT -- virtual page count
WSMAX -- working set maximum
These and all other system system parameters are described
in the VAX/VMS System Man~ge!'.:~__ Guide.

detail

Command Qualifiers

/ALL
Displays the values for all parameters.
/ACP
Displays all the system parameters
ancillary control processes (ACPs).

associated

with

Files-11

/DYNAMIC
Displays the system parameters that can be changed by the
utility after the system has been bootstrapped.

SYSGEN

/GEN
Displays the structure-generating system parameters and other
parameters that have effect only when the system is bootstrapped.
/JOB
Displays all job controller system parameters.
/MAJOR
Displays the major system parameters. These are
that are most likely to require adjustment
installations.

the
for

parameters
individual

/NAMES
Displays the names of all the system parameters.
/PQL
Displays the values associated with process creation
quotas.

limits

and

/RMS
Displays the values associated with VAX-11 RMS.
/STARTUP
Displays the name of the start-up command procedure.
/SYS
Displays the system parameters
operation.

4-10

associated

with

overall

system

THE SYSBOOT PROGRAM
Examples
1.

SYSBOOT>

SHOW /JOB

Parameter Name
MAXPRINTSYMB
DEFPRI
IJOBLIM
BJOBLIM
NJOBLIM

Current

Default

Minimum

Maximum

A
4
n4
Hi

8
4

255
31
1024
1024
10/.4

1
1
0
0

lf.)

lfi

The SHOW/JOB command causes the parameters
the job controller to be displayed.
2.

SYSBOOT>
WSMAX

Unit
PROCESSES
,JOBS
,JOBS
,JOBS

associated

with

SHOW WSMAX
256

256

ln384

PAGES

The SHOW WSMAX command shows the values associated with the
parameter that controls the maximum working set size of all
processes in the system.

4-11

THE SYSBOOT PROGRAM

USE
4.9

USE

The USE command specifies the source of system parameter values.
You
can specify a file that you created or that DIGITAL supplied as part
of the operating system, or you can indicate that either the current
parameter values or the default parameter values are to be used.
Having established the source, you can modify individual parameters by
means of the SET command.
Formats

USE file-spec
USE CURRENT
USE DEFAULT
file-spec
Indicates the name of the parameter file whose values are to be
used to bootstrap the system. You can specify a file that you
created by use of the SYSGEN WRITE command or that DIGITAL
distributed with the system.
The parameter file must be located in the [SYSEXE] directory on
the system; and the file type, usually PAR, is required syntax.
CURRENT
Indicates that the values in effect the last time the system was
bootstrapped are to be used. When the system is first copied
from the distribution medium, the CURRENT and DEFAULT values are
the same.
DEFAULT
Indicates that the default values established by VAX/VMS
be used to bootstrap the system.

are

Examples

SYSBOOT>
SYSBOOT>
SYSBOOT>

USE DEFAULT
SET IJOBLIM 80
SET BJOBLIM 10

The first command sets the values of the system parameters to the
defaults supplied by VAX/VMS. The two SET commands establish new
values for the limits on the number of interactive and batch
jobs, respectively.

4-12

CHAPTER 5
UPGRADING THE SYSTEM

As described in Chapter l, if you have a VAX/VMS Version 1.6 system,
and you have added user files to the system disk, you should use the
system upgrading procedure described
in this chapter to
install
Version 2.0.
To upgrade a system, proceed as follows:
1.

Confirm that your VAX/VMS software distribution kit contains
the components needed to upgrade your system, as described in
Section 5.1.

Remove unimportant files from the system disk,
in Section 5.2.1.

described

Obtain a record of the original and current system
values, as described in Section 5.2.2.

parameter

Make a copy of the system disk and boot this
system disk, as described in Section 5.2.2.

newly

Turn off the network, if it is currently in use, as described
in Section 5.3.

Flush all batch and printer queues, as described
5.3.

Prepare the system disk and the upgrade kit volume
upgrade operation, as described in Section 5.3.

for

the

Invoke the command procedure VMSUPDATE.COM to
initiate
system upgrade operation, as described in Section 5.3.

the

10.

Reboot the system from the upgraded system disk and log
in
under the temporary account provided by the system, as
described in Section 5.4.

11.

Use the command procedure UPGRADFIN.COM to complete the
upgrading of the system and to restore the user authorization
file, as described in Section 5.4.

12.

Tailor the system parameter
described in Section 5.5.

5-1

file

quota

suit

your

copied

zero,

Section

needs,

UPGRADING THE SYSTEM

13.

Back up the upgraded system disk,
5.5.

described

14.

Reboot the system from the back up copy of
system disk, as described in Section 3.2.2.

Section

the

upgraded

After you complete the final step, the system is ready for use.

5.1

VAX/VMS UPGRADE MEDIA

The VAX/VMS software distribution kit, as described in Chapter 2, also
contains the components needed to upgrade an existing Version l.h
system. This kit is distributed as either:
•

A magnetic tape kit

•

An RK07 kit

Sections 5.1.1 and 5.1.2, below, describe the required system upgrade
components in the magnetic tape and RK07 kits. However, before
proceeding any further, you should check that your kit contains all
the components listed in the bill of materials that comes with the
kit.

5.1.1

Upgrade Components in Magnetic Tape Kit

The following components
magnetic tape:
•

are

upgrade

your

system

from

The system binary upgrade tape
Part number:

BB-J830A-BE

Part description:
•

needed

VMS 2.0 UPGRADE MT9

The floppy diskette that drives the Version l.n to Version 2.0
upgrade procedure
Part number:

AS-J803A-BE

Part description:

VMS V2.0 RXOl UPG

console floppy diskette that contains the VAX/VMS
• The
2.0
bootstrap
loading
programs
and bootstrap
procedures
Part number:

AS-Efi33I-YE

Part description:

RX 1/ 11780 LOCAL CNSL PKG

5-2

Version
command

UPGRADING THE SYSTEM
The following component, also contained in the magnetic tape kit, may
be used to back up the system during various stages of the upgrade
operation:
•

The floppy diskettes that contain the stand-alone version
the Disk save and Compress Utility (stand-alone DSC-2)
Part number:

AS-E808I-BE

Part description:
Part number:

STAND/ALONE 11780 DSC2 FLP 1

AS-J831A-BE

Part description:

5.1.2

STAND/ALONE 11780 DSC2 FLP 2

Upgrade Components in RK07 Disk Kit

The following components are needed to upgrade your system
disk:
•

AY-H020C-BE

Part description:

VAX/VMS V2.0 BIN RK07

The floppy diskette that drives the Version l.h to Version ?..O
upgrade procedure
Part number:

AS-J803A-BE

Part description:
•

RK07

The RK07 system binary upgrade diskl
Part number:

•

from

VMS V2.0 RXOl UPG

The console floppy diskette that contains the VAX/VMS Version
2.0 bootstrap loading programs and boostrap command procedures
Part number:

AS-En33I-YE

Part description:

RX l/ 11780 LOCAL CNSL PKG

The following component, also contained in the RK07 disk kit, may be
used to back up the system during various stages of the upgrade
operation:
•

The floppy diskettes that contain the stand-alone version
the Disk Save and Compress Utility (stand-alone DSC-2)
Part number:

AS-E808I-BE

Part description:
Part number:

STAND/ALONE 11780 DSC2 FLP l

AS-J831A-BE

Part description:

STAND/ALONE 11780 DSC2 FLP 2

1. The RK07 system binary upgrade disk doubles as the
distribution disk;
see Chapter 2.
5-3

system

binary

UPGRADING THE SYSTEM
5.2

PREPARING TO UPGRADE THE SYSTEM

Before upgrading a VAX/VMS system, be sure that you have:
•

A minimum of 12,000 free blocks on the system disk

•

A console printout of the current system parameter values and
the original system parameter values {that is, the values
established by DIGITAL)

The sections below explain why these precautions must
contain suggested procedures for accomplishing them.

taken

and

Freeing Up Space on the System Disk

5.2.1

Because available disk space is always at a premium, you should remove
all unwanted or redundant files from the current system disk before
upgrading your system. To do so, use any one of the following DCL
file manipulation commands: COPY, DELETE, or PURGE. Use the command
appropriate for the type of operation desired.
Note that to upgrade the system, there must be a minimum of 12,000
free blocks on the system disk. You can confirm the free block count
with the following command:
$ SHOW DEVICES

device-name

Recording System Parameter Values

5.2.2

After a VAX/VMS system has been bootstrapped and installed, the values
of the system parameters can be modified to fit the needs of the
particular installation. If you have changed any parameter values at
your installation, it will be necessary for you to obtain a record of:
e

The parameter file you used to generate your system

The DIGITAL-supplied parameter file
resembles your hardware configuration

that

closely

most

With this record, you can calculate the difference in
parameter
values.
After upgrading the system, you
calculations to again modify the parameter values.

individual
use th~se

To obtain a record of the two parameter files, proceed as
the console terminal:

follows

Establish the following default:
$

SET DEFAULT SYSSSYSTEM

Invoke the SYSGEN utility with the following command:
$

RUN SYSGEN

5-4

UPGRADING THE SYSTEM
4.

Obtain a console printout of the current parameter values and
the
original
parameter
values
(that
is,
the values
established by DIGITAL),
as demonstrated
in the example
below:
SYSGEN>
SYSGEN>
SYSGEN>
SYSGEN>

USE CURRENT
SHOW/ALL
USE 16USER.PAR
SHOW/ALL
NOTE

Save this listing.
You may need to
refer to
it
if you tailor your system
parameter file (see Section 5.5).
5.

Terminate the SYSGEN utility with the command:
SYSGEN> EXIT

At this point, you are ready to upgrade your system.
However,
before
proceeding any further,
you should back up your system disk and use
the newly created copy to reboot the system.
By doing so, you:
•

Preserve the original disk for future reference

•

Confirm that the newly created disk is a usable
original disk

•

Simplify the task of upgrading the disk by
free space into one contiguous area

copy

the

consolidating

all

You can back up the system disk using the back-up procedure described
in Chapter
2.
(Chapter
2 uses stand-alone DSC-2 to back up the
system.)

5.3

UPGRADING VAX/VMS

Before actually upgrading the system, you must proceed as
the console terminal:

follows

Bootstrap your system using the back-up copy of
the system
disk
that you created
in Section 5.2.2.
The Version l.h
console floppy diskette should be in the console drive.

Prevent users from logging in to the system by typing:
$ SET LOGINS/INTERACTIVE = 0

If you are running DECnet-VAX, shut down the network.

Flush all batch and printer queues, if
the queues.

Be sure that the logical name SYS$DISK
is assigned
to the
system disk that is to be upgraded.
The disk to be upgraded
is assumed to be the disk you used to bootstrap the system.

5-5

th~re

are any jobs

UPGRADING THE SYSTEM
7.

Place the upgrade kit volume (that is, the RK07 disk or
magnetic
tape
contained
in the upgrade kit) on the
appropriate drive and place it online.

Write-lock the upgrade kit volume to protect the contents
the volume

Establish the following defaults:

$ SET UIC [1,4]

$ SET DEFAULT [SYSUPD]

These commands are to be executed in the order shown.
10.

Delete all
commands:

user-defined

DCL

symbols

with

the

following

command

procedure

DELETE/SYMBOLS/GLOBAL/ALL
DELETE/SYMBOLS/LOCAL/ALL

To initiate the upgrade operation,
VMSUPDATE.COM, as shown below:

execute

the

$ @VMSUPDATE

An introductory message, explaining the upgrade operation, will then
be sent to the console terminal. Read the text carefully and follow
the instructions accordingly.
Note that you will receive a device-not-mounted message, if the
console floppy diskette is not mounted. Ignore the message, and place
the upgrade floppy diskette (part description: VMS V2.0 RXOl UPG)
in
the console drive.
NOTE
If at any time during the
upgrade
operation a system failure occurs, you
must restart the upgrade operation using
another copy of your Version 1.6 system
disk.
You will receive the following query:
Are you ready to continue?:
If you type Y, the upgrade proceeds.
If you type N, the request to put the upgrade floppy diskette in the
console drive and the query "Are you ready to continue?:" will be
repeated.
Continuation of the upgrade operation is signaled by
the following question:
What is the source media name?

the

display

(DDCU:):

Respond by entering the name of the device that contains the upgrade
kit volume. This is either an RK07 disk drive (for example, DMA2) or
a magnetic tape drive (for example, MTAO).

5-6

UPGRADING THE SYSTEM
You then receive the following messages:
Allocate and mount the source media.
Is the source media, DDCU:, ready to be mounted?

(Y/N}:

When you type Y, the upgrade kit volume is allocated and
the upgrade operation proceeds.

mounted

and

At the console terminal, various messages are displayed that report
the status of the upgrade operation. These messages include (1) those
that inform you of the set of files being copied, and (2)
those that
indicate that certain files cannot be deleted. The latter of these
messages can be ignored if the message indicates that the file does
not exist.
Messages of this type appear for new files that are
included in this version of the system software and were not part of
the system software in any past version.
When the installation
of
the
upgraded
system
is
complete
(approximately one hour}, the following message is displayed at the
console terminal:
Kit is complete.
Place console floppy back in drive for reboot.
You should immediately insert the Version 2.0 console floppy diskette
(part description:
RX 1/ 11780 LOCAL CNSL PKG} into the console
drive.
At this point, the system is shut down.
system.

Use the console to

To transfer control of the system to the upgraded version of
perform the steps listed in Section 5.4.

5.4

halt

the

VAX/VMS,

COMPLETING THE UPGRADE

To complete the system upgrade operation, you must execute the command
procedure UPGRADFIN.COM. This command procedure automatically:
•

Renames and deletes files
system

left

over

from

the

Version

1.6

•

Converts your user authorization file to the new
format

Version

2.0

•

Sets protection on strategic files to ensure system security

Failure to execute this command procedure may result in
system consequences.

unpredictable

A temporary user authorization file in Release 2.0 format is supplied
to allow you to log in to the system and complete the upgrade
operation. To complete the upgrade operation, proceed as follows:
1.

Check that the Version 2.0 console floppy diskette (part
description:
RX l/ 11780 LOCAL CNSL PKG} is in the console
drive.

Boot the upgraded system stopping in SYSBOOT and specify
system parameter file MINIMUM.PAR.

the

UPGRADING THE SYSTEM
4.

Establish the following defaults:
$ SET UIC [1,4]
$SET DEFAULT SYS$SYSDISK:[SYSUPD]
These commands are to be executed in the order shown.

Type the following command to initiate the conversion:
$ @UPGRADFIN

At the completion of the conversion (approximately
following message is sent to the console terminal:

minutes),

the

SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM
Halt the system as directed.

5.5

TAILORING THE SYSTEM PARAMETER FILE

Before permitting users to gain access to the system, you must reboot
the system stopping in SYSBOOT and specify the DIGITAL-supplied system
parameter
file
that
most
closely
resembles
your
hardware
configuration.
Using the SYSGEN utility, you can then tailor this
parameter file to meet the needs of your installation.
The VAX/VMS System Manager's Guide contains chapters on tailoring the
system___ pa_r. amefer---·n1e-·to--·1mprove-system performance. However, before
reading that manual, you can make the following simple change:
use
the adjustments you made to your Version 1.0 parameter file as a guide
for making adjustments to your Version 2.0 parameter file.
Making
these types of adjustments generally produces favorable results,
provided you have not altered your system's hardware resources and/or
workload.
Finally, after editing is complete, reboot the system stopping in
SYSBOOT and specify the new parameter file. Then, to establish the
default bootstrap command procedure, execute the command procedure
SETDEFBOO.COM, as described in Section 3.6.1. As a precautionary
measure, you should back up the system disk and save the original for
future reference.

5-8

CHAPTER n
INSTALLING MAINTENANCE UPDATES AND OPTIONAL SOFTWARE

This chapter describes the procedures for installing maintenance
updates to a VAX/VMS system and installing optional VAX-11 software
products available for VAX/VMS, such as, VAX-11 FORTRAN and VAX-11
COBOL-74.
The procedures for installing a maintenance update or optional
software product are automated, and thus require 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. Most queries are simple "Yes"
or "No" questions. You respond with Y or N, as appropriate.

6.1

DISTRIBUTION KIT8

Maintenance
distributed
component.

updates and optional
on floppy diskettes,

VAX-11 software
products
two or more depending o~

are
the

Each diskette is labeled with both a name corresponding to the
software product and a serial number that differentiates that floppy
diskette from others in the distribution kit. You should check that
your kit contains all the floppy diskettes listed in the bill of
materials.
The floppy diskette contains files, including command procedures that
copy the components to the system disk. These command procedures
direct the installation procedure by means of queries and instructions
sent to the terminal.

6.2

GENERAL INSTALLATION PROCEDURES

This section describes the steps you take to prepare for the
installation of a maintenance update or optional software product.
For a complete description of the installation procedure for a
particular software product, refer to the documentation set for that
product.

6-1

INSTALLING MAINTENANCE UPDATES AND OPTIONAL SOFTWARE
Preparing for Installation

6.2.1

To prepare for the installation of a maintenance update or optional
software product, proceed as follows at the console terminal:
1.

Be sure that you have set the default to the disk that is to
receive the update or optional software product. This is
typically the
system
disk
(with
the
logical
name
SYS$SYSDISK).

Establish the following defaults:
$ SET UIC

[1,4)

$ SET DEFAULT [SYSUPD]
These commands are to be executed in the order shown.
4.

Type the following command to initiate the installation of
maintenance update or optional software product:

$ @VMSUPDATE
You will then see 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 2. 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 volume in the console drive
Note that you will receive a device-not-mounted message if no console
floppy diskette is mounted.
Ignore the message, and place your first
update or optional software floppy diskette in the console drive.
You will receive the following query:
Are you ready to continue?:
If you type Y, the installation proceeds.
If you type N, the request to put the first update or optional
software floppy diskette in the console drive and the query "Are you
ready to continue?:" will be repeated.
At this point, you are ready to install a maintenance update or an
optional software product. The procedure for installing a maintenance
update is described in Section ~.3;
the procedure for
installing an
optional software product is described in that product's documentation
set.

6-2

INSTALLING MAINTENANCE UPDATES AND OPTIONAL SOFTWARE

6.2.2

Installation Completion

When the installation of the maintenance update or optional software
product 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

You

then

Please place the first volume in the console drive.
If you have no further installations or updates,
receive the message:

type

Please place the system console medium in the console drive.
You should immediately restore the
console drive.

console

floppy

diskette

the

Next, you will receive the following query:
Are you ready to continue?:
If you type Y, the console floppy diskette
and you receive the following message:

automatically

mounted

Requested update sequence is complete.
Finally, after installing the maintenance update or optional software
product, you should back up the system disk and save the original for
future reference. Backing up the system disk is described in Chapter
2.

6.3

INSTALLING MAINTENANCE UPDATES

A distribution kit to update the VAX/VMS system
more floppy diskettes.

consists

one

To install a maintenance update to your system, follow the procedure
described in Section 6.2.1 and perform the following modifications
before you invoke the VMSUPDATE.COM command procedure:
1.

Prevent users from gaining access to the system by executing
the SHUTDOWN.COM command procedure. Then reboot the system.
Executing SHUTDOWN.COM and rebooting the system are described
in the VAX/VMS Operator's Guide.

Set the login quota to O by typing:
$ SET LOGIN/INTERACTIVE

As a precautionary measure, copy the contents of
disk to another disk.

the

system

When directed to place the update floppy diskette in the console
drive, replace the console floppy diskette with the first update
floppy diskette. Then enter Y to the query:
Are you ready to continue?:

fi-3

INSTALLING MAINTENANCE UPDATES AND OPTIONAL SOFTWARE
Continuation of
announcement:

the

update

indicated

the

display

the

VAX/VMS version 2.xx Update
This message is followed by three questions.
The first question is:
Do you want all the updates applied?

(Y/N, YES RECOMMENDED):

A "yes" (Y) to this question is recommended, because it is the option
supported by DIGITAL.
Answering "no" (N) lets you accept or reject
each patch. Rejecting a patch, however, may make it difficult for
DIGITAL to answer problem reports and difficult for you to apply
future patches supplied by DIGITAL.
The second question is:
Do you want an explanation of each update
update? (Y/N) :

displayed

during

the

If you type Y, brief descriptions of the patches will be displayed
the console terminal.

The third question is:
Do you want previous versions of updated file purged?

(Y/N):

Type N if there is enough disk space to preserve previous versions
the updated files.

When updating has been completed, the completion messages described in
Section 6.2.2 are displayed.
To transfer control of the system to the updated version of VAX/VMS,
halt the processor and reboot the system as described in Chapter 3.

fi-4

APPENDIX A
SYSBOOT MESSAGES

This appendix lists the messages issued by SYSBOOT.
Each
consists of a prefix followed by message text, in the form:

message

%component-x-text
component
The component issuing the message, that is, BOOT or SYSBOOT.

x
The severity level of the error:
E (error)
F (fatal error)
W (warning)
text
The message text. Within the two sections that follow,
are described in alphabetic order by message text.

messages

A warning message (W) indicates that BOOT or SYSBOOT has altered a
user-specified parameter value because that value was not within the
allowable range. An error message (E) indicates that a command
contains an error or that an I/O error occurred during execution of a
command. Commands in which an error occurs have no effect.
A fatal
error message (F} indicates that the current attempt to boot the
system has been terminated.

A.l

BOOT MESSAGES

%BOOT-F-Bootfile not contiguous
Explanation:
contiguous.

The file [SYSEXE]SYSBOOT.EXE was located but is not

User Action: The disk you are attempting to boot
booted. Obtain another copy of the system disk.

cannot

%BOOT-F-I/O error reading boot file
Explanation: An uncorrectable read error occurred while the file
[SYSEXE]SYSBOOT.EXE was being read.
User Action: Try booting the disk again. If subsequent attempts
fail, obtain another copy of the system disk.
A-1

SYSBOOT MESSAGES

%BOOT-F-Nonexistent drive
Explanation:

The specified drive number does not exist.

User Action: Specify an appropriate device unit to the console
program, or use a different console bootstrap command procedure.

%BOOT-F-Unable to locate boot file
Explanation:

The file [SYSEXE]SYSBOOT.EXE could not be found.

User Action: You are attempting to boot a volume that does not
contain a VAX/VMS binary system. Attempt to boot again using an
appropriate disk volume.

%BOOT-F-Unexpected exception
Explanation: An unexpected exception occurred while the primary
bootstrap (VMB.EXE) was being executed. This condition probably
indicates a corrupted SYSBOOT.EXE file or a hardware failure.
User Action: Determine the source of the error, and either
obtain a new copy of the system disk or call your local field
service representative.

%BOOT-F-Unexpected machine check
Explanation: An unexpected machine check occurred while the
primary bootstrap (VMB.EXE) was being executed. This condition
probably indicates a corrupted SYSBOOT.EXE file or a hardware
failure.
User Action: Determine the source of the error, and either
obtain a new copy of the system disk or call your local field
service representative.

A.2

SYSBOOT MESSAGES

%SYSBOOT-W-Continue from halt to proceed with boot if desired
Explanation: A potentially serious condition (for example, a
missing hardware ECO) has been detected, causing the processor to
halt.
User Action:

Call your local field service representative.

%SYSBOOT-E-File not contiguous
Explanation:
contiguous.

The

file

specified

User Action:

Create a contiguous parameter file.

A-2

USE

command

not

SYSBOOT MESSAGES
%SYSBOOT-W-FPLA, PCS, or WCS version less than
VMS.

Explanation:

The hardware ECO level
is
required for correct software operation.

User Action:

minimum
below

required
that

which

for
is

Call your local field service representative.

%SYSBOOT-E-I/O error reading file

Explanation: An unrecoverable I/O error occurred while SYSBOOT
was
reading a parameter file or the system image.
If the error
occurred while a parameter file was being read, SYSBOOT does not
perform the requested action.
If the error occurred while the
system image was being
read,
SYSBOOT terminates the
boot
operation.
User Action:

Attempt to reboot the system

try

different

drive.
%SYSBOOT-W-Maximum WS raised to PHD+MINWSCNT

Explanation:

SYSBOOT has raised the maximum working set size you
specified, to accommodate the minimum working set size allowed by
VAX/VMS. To execute, every process requires a minimum fluid
working set (MINWSCNT) plus space for its process header (PHD).

user Action:

None.

%SYSBOOT-E-No such parameter

Explanation:

A parameter name specified in a SET or SHOW command
is not a recognized parameter name.

User Action:

Reissue the command

specifying

correct

parameter

names.
%SYSBOOT-E-Syntax error

Explanation:

You

issued

command

that

was

syntactically

incorrect.

User Action:

Reissue the command using proper syntax.

%SYSBOOT-F-Unable to allocate physical memory

Explanation:

The sum of pages
required for
the
table,
nonpaged dynamic pool,
interrupt stack,
executive exceeds available physical memory.

system page
and resident

User Action: Reconfigure the system to require less physical
memory and reboot the system.
Reduce one or more parameters
controlling the allocation of physical
memory:
NPAGEDYN,
BALSETCNT, and VIRTUALPAGECNT.

A-3

SYSBOOT MESSAGES
%SYSBOOT-F-Unable to allocate SPT
Explanation:
SYSBOOT cannot
find enough contiguous pages of
physical memory to contain the required system page table (SPT).
User
Action:
Reduce
parameters
controlling
SPT
VIRTUALPAGECNT, BALSETCNT, REALTIME_SPTS, and SPTREQ.

size:

%SYSBOOT-F-Unable to locate driver for boot device
Explanation:
SYSBOOT cannot locate the driver image file for the
boot device in directory [SYSEXE] on the volume to be booted.
User Action:
[SYSEXE] •

Put the correct driver image file in the

Device Type

Driver Name

RK06/RK07
RM03
RP05/RP06

DMDRIVER.EXE
DRDRIVER.EXE
DBDRIVER.EXE

directory

%SYSBOOT-E-Unable to locate file
Explanation:
SYSBOOT cannot locate a file
command on the volume to be booted.
User Action:
name.

Reissue the command

specified

specifying

the

correct

USE
file

%SYSBOOT-F-Unable to locate SYS.EXE
Explanation:
SYSBOOT cannot locate the
directory [SYSEXE] on the boot volume.

system

image

file

User Action:
The system disk is either defective or corrupted;
or the disk you are accessing is not the system disk.
Obtain a
new copy of the VAX/VMS system disk.
%SYSBOOT-F-Unexpected exception
Explanation:
An unexpected exception has occurred
probable hardware error or SYSBOOT logic error.
User Action:

indicating

Call your local field service representative.

%SYSBOOT-F-Unexpected machine check
Explanation:
An unexpected machine check occurred
probable hardware error or SYSBOOT logic error.
User Action:

indicating

Call your local field service representative.

A-4

SYSBOOT MESSAGES
%SYSBOOT-F-Unknown processor
Explanation: The
processor
identification register does
model of a VAX-11 processor.
User Action:

type
code
in
the
system
not correspond to any supported

Call your local field service representative.

%SYSBOOT-W-Value set to maximum
Explanation: You attempted to set a parameter to a value greater
than the maximum allowable value. SYSBOOT has set the parameter
to the maximum permissible value.
User Action:

None.

%SYSBOOT-W-Value set to minimum
Explanation: You attempted to set a parameter to a value that is
less than the allowable minimum value.
SYSBOOT has set the
parameter to the minimum permissible value.
User Action:

None.

%SYSBOOT-W-WS default and quota raised to PDH+MINWSCNT
Explanation: SYSBOOT has raised the default working set size you
specified to accommodate the sizes of the process header plus the
minimum fluid working set size.
User Action:

None.

A-5

APPENDIX B
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 binary distribution medium.
The files on this medium are cataloged in eight directories;
two
other directories on the medium are provided for later use by the
system. The names of all ten directories and descriptions of their
contents follow.
1.

[SYSERR]
This directory
(ERRLOG.SYS).

reserved

for

the

error

log

file

[SYS EXE]
As shown in Table B-1, this directory contains commonly used
executable
images of the VAX/VMS operating system and
installation.

[SYSHLP]
As shown in Table B-2, this directory contains text libraries
for the HELP utility and other com9onents.
(Source examples
are listed in the subdirectory [SYSHLP.EXAMPLES]
Table
B-8.)

[SYSLIB]
As shown in Table B-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 B-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 B-5, this directory contains system message
text files.

B-1

FILES OF THE VAX/VMS SYSTEM
8.

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

[SYSUPD]
As shown in Table B-7, this directory contains files used
applying system updates.

10.

[ SYSHLP. EXAMPLES]
As shown in Table B-8, this directory contains sample driver
programs, user-written system service programs, and other
source code examples of interest.
Table B-1
Files Contained in Directory [SYSEXE]

File Name

Description

4USER.PAR
16USER.PAR
32USER.PAR
48USER.PAR
64USER.PAR
SUS ER.PAR
ANALYZ.EXE
AUTHORIZE.EXE
BACKTRANS.EXE
BAD.EXE
BADBLOCK.EXE
BCK.EXE
BOOT58.EXE
BOOTBLOCK.EXE
CANCEL.EXE
CLEDITOR.EXEl
CNV.EXE
CON INT ERR. EXE
COPY.EXE
CRDRIVER.EXE
CREATE.EXE
CRF.EXE
CVTHELP.EXE
CVTUAF.EXE

Reserved for future use
VAX/VMS system parameter file
VAX/VMS system parameter file
VAX/VMS system parameter file
VAX/VMS system parameter file
VAX/VMS system parameter file
VAX/VMS object module analyzer
User authorization program
Back translator of DCL into MCR commands
Bad block locator utility
Dynamic bad block Files-11 ACP subprocess
RMS-11 back-up utility
Reserved for future use
Reserved for future use
CANCEL command
Command language editor
RMS-11 file conversion utility
Connect-to-Interrupt driver
File copying· utility
Card reader driver
File and directory creation utility
Compatibility mode cross reference utility
Version 1.0 to version 2.0 help file upgrade
Version 1.0 to Version 2.0 user authorization
file upgrade
RPOS and RPOn disk driver
Command interpreter
Global definitions for DCL structures
Reserved for future use
RMS-11 interactive file definition utility
File deletion/purge utility
RMS-11 noninteractive file definition utility
File compare utility

DBDRIVER.EXE
DCL.EXE
DCLDEF.STB
DDDRIVER.EXE
DEF.EXE
DELETE.EXE
D
. . FN. EXE
DIF.EXE

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

B-2

FILES OF THE VAX/VMS SYSTEM

Table B-1 (Cont.)
Files Contained in Directory [SYSEXE]
File Name
DIRECTORY .EXE
DISKQUOTA.EXE
DISMOUNT.EXE
DISPLAY .EXE
DLDRIVER.EXE
DMDRIVER.EXE
DMP.EXE
DRDRIVER.EXE
DSCl.EXE
DSC2.EXE
DSP.EXE
DXDRIVER.EXE
DYDRIVER.EXE
EDI. EXE
EDT.EXE
ERRFMT.EXE
FllAACP .EXE
FllBACP .EXE
FLX.EXE
HELP.EXE
HEXZAP.EXE 1
I FL.EXE
IMGDEF.STB
INFO.EXEl
IN IT.EXE
INPSMB.EXE
INSTALL.EXE
JBCSYSQUE.DAT
JBCSYSQUE.EXE
JOBCTL.EXE
LADRIVER.EXE
LALOAD.EXE
LALOADER.EXE
LBR. EXE
LIBRARIAN. EXE
LINK .EXE
LOG IN OUT. EXE
LPDRIVER.EXE
MAC.EXE
MACR032.EXE
MAIL. EXE
MAILEDIT.COM
MBXDRIVER.EXE

Description
Directory utility
Disk quota utility
Volume dismount utility
Utility that displays system performance
statistics
RL02 disk driver
RK07 disk driver
File dump utility
RM03 disk pack driver
Files-11 Structure Level 1 disk save and
compress utility
Files-11 Structure Level 2 disk save and
compress utility
RMS-11 file attribute display utility
RXOl console floppy diskette driver
RX02 floppy diskette driver
RSX-llM text editor
EDT text editor
Error logging facility
Files-11 Structure Level 1 ancillary
control process image
Files-11 Structure Level 2 ancillary
control process image
RT-11 file transfer utility
Help ut i U. ty
Hexadecimal ima9e patching utility
RMS-11 utility index load program
Global definitions for image activator
structures
Process information utility
Disk device initialization utility
Card reader input symbiont
Utility that installs known images
Data file for queuing facility
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
Librarian utility
Linker
Login/logout utility
Line printer driver
MACR0-11 assembler
VAX-11 MACRO assembler
Mail utility
Default MAIL editing command procedure
Shared memory mailbox driver
----···------- - - - - - - - - - - - - - - - - - - - -

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

B-3

FILES OF THE VAX/VMS SYSTEM
Table B-1 (Cont.)
Files Contained in Directory [SYSEXEl
File Name

Description

MCR.EXE
MDL.EXE 1
MESSAGE.EXE
MINIMUM.PAR

MCR command interpreter
Structure definition translator
Message compiler
VAX/VMS system parameter file for minimum
hardware configuration
Magnetic tape ancillary control process image
Runoff indexing utility
DECnet logical link driver
Text file that can contain announcements to
system users
System shutdown utility
Operator communications utility
System paging file
RSX-llM object module patch utility
VAX-11 image file patch utility
VAX-11 object module patch utility
Page fault monitor analyzer utility
Page fault monitor file writer
RSX-llM peripheral interchange utility
Print symbiont
Queue mana9ing utility command image
Remote device ACP
Remote device data base
File rename utility
Message broadcasting facility
Operator request facility
Record management services image
Utility to display file attributes
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
System dump analyzer utility
File search utility
SET command processor
Utility to set process name
SET command processor
System file analyzer utility
SHOW command processor
System shutdown command procedure
RSX-llM source file editing utility
SORT command processor
sos text editor
SORT-11 utility

MTAAACP.EXE
NDXDMP.EXEl
NETDRIVER.EXE2
NOTICE.TXT
OPCCRASH.EXE
OPCOM.EXE
PAGEFILE.SYS
PAT.EXE
PATCH.EXE
PAX.EXE!
PFMANALYZ. EXE.i
PFMFILWRT.EXE
PIP.EXE
PRTSMB.EXE
QUEMAN.EXE
REMACP.EXE 2
REMDEVICE.DAT2
RENAME.EXE
REPLY.EXE
REQUEST.EXE
RMS.EXE
RMSANLZ. EXE,l
RMSDEF.STBl
RMSSHARE.EXE
RST.EXE
RSX.EXE
RTB.EXE
RTPAD.EXE2
RTTDRIVER .EXE2
RUNDET.EXE
RUNOFF.EXE!
SDA.EXE
SEARCH.EXE!
SET.EXE
SETNAME.EXEl
SETPO.EXE
SFA.EXEl
SHOW.EXE
SHUTDOWN.COM
SLP.EXE
SORT32.EXE
SOS.EXE
SRT.EXE

1. Not supported by DIGITAL.
2. Requires DECnet-VAX optional product for use.
(continued on next page)

B-4

FILES OF THE VAX/VMS SYSTEM

Table B-1 (Cont.)
Files Contained in Directory [SYSEXE]
File Name

Description

STARTUP.COM
STARTUP.MIN

System start-up command procedure
Alternate system start-up command procedure for
system with minimum hardware configuration
Stop REMACP utility
Batch job submission facility
Source file editor
System swap file
Utility that formats the error log file
Operating system image file
Map of the operating system image
Global symbol table of operating system
System bootstrap utility
Global definitions for executive structures
Crash dump of system image
System generation and configuration utility
Operating system initialization image
Reserved for future use
Reserved for future use
VAX-11/780 system image file
User authorization data file
version-2.0- supplied SYSUAF file
Interterminal communications utility
Runoff indexing utility
TECO text editor
RSX-llM task builder
Magnetic tape driver
Runoff table of contents utility
TSll Magnetic tape driver
Terminal driver
TYPE command processor
User file directory creation utility
File unlock utility
Interactive users display utility
Files-11 Structure Level 1 file structure
verification utility
Files-11 Structure Level 2 file structure
verification utility
VAX/VMS system parameter file that supports
system with large virtual address space
VAX/VMS primary bootstrap
Volume mount utility
Performs UIC <---> user name translation
System volume bootblock writing utility
Reserved for future use
DR32 system interconnect interface driver
DR32 microcode loader utility
DMC-11 Synchronous Communications Line Interface
driver
DUP-11 device driver
RSX-llM task/file octal patch utility

STOPREM.EXE2
SUBMIT.EXE
SUMSLP.EXE
SWAPFILE.SYS
SYE.EXE
SYS.EXE
SYS.MAP
SYS.STB
SYSBOOT.EXE
SYSDEF.STBl
SYSDUMP.DMP
SYSGEN.EXE
SYSINIT.EXE
SYSLOAYYY.EXE
SYSLOAZZZ.EXE
SYSLOA780.EXE
SYSUAF.DAT
SYSUAF.RL2
TALK.EXEl
TCX.EXEl
TECO.EXE 1
TKB.EXE
TMDRIVER.EXE
TOC.EXEl
TSDRIVER.EXE
TTDRIVER.EXE
TYPE.EXE
UFO.EXE
UNLOCK.EXE
USERS.EXEl
VFYl.EXE
VFY2.EXE
VIRT32MB.PAR
VMS.EXE
VMOUNT.EXE
WHO.EXEl
WRITEBOOT.EXE
XADRIVER.EXE
XFDRIVER.EXE
XFLOADER.EXE
XMDRIVER.EXE
XWDRIVER.EXEl
ZAP.EXE

· - - · · - · - - · · · - - - - - - - ·---~----- ------····-

1. Not supported by DIGITAL.
2. Requires DECnet-VAX optional product for use.

B-5

FILES OF THE VAX/VMS SYSTEM
Table B-2
Files Contained in Directory [SYSHLP]
File Name

Description

DEBUG.HLB
DISKQUOTA.HLB
EDTHELP.HLB
EDTVTlOO.DOC
EDTVT52.DOC
HELPLIB. HLB
MAIL.HLB
PFMON.HLP
SDA.HLP
SFA.HLPl
SYSGEN.HLB
WHO.HLBl

Debugger help library
Help library for disk quota utility
EDT help library
EDT keypad layout for VTlOO
EDT keypad layout for VT52
Default (DCL) help library
Mail utility help library
Help text for page fault monitor
System dump analyzer help file
Help file for SFA
Help file for SYSGEN
Help file for UIC <---> user name translation

1. Not supported by DIGITAL.
Table B-3
Files Contained in Directory [SYSLIB]
Description
CLIMAC.REQ
CRFSHR.EXE
DCLINTPRT. EXE
DCLTABLES.EXE
DEBUG.EXE
DELTA.EXE
DELTA.OBJ
FORDEF.FOR
FORIOSDEF.FOR
LBRSHR.EXE
LIB.MLB
LIB.REQ
LIBDEF. FOR
LOCAL. TEC\l
MTHDEF.FOR
CDT.OBJ
PGFALTMON.OBJl
RMSll .ODL
RMSLIB .OLB
RMSMAC.MLB
RMSRES.ODL
RMSVECTOR.OBJ
RSXMAC.SML
RSXSHR.EXE

Structure definitions for BLISS programs
interfacing with the command language
interpreter
Cross-reference shareable image
Shareable image for DCL (interpreter part)
Shareable image for DCL (table part)
VAX/VMS debugging facility
DELTA multimode debugging tool image
Alternate VAX/VMS debugging tool object
FORTRAN INCLUDE file: FOR$ symbols
FORTRAN INCLUDE file: IOSTAT error codes
Librarian shareable image
Operating system mac·ro library
Structure definitions of executive internals
for use by BLISS programs
FORTRAN program utility INCLUDE files
TECO macro to reorder local labels
FORTRAN INCLUDE files: MATH$ symbols
RSX-llM debugging tool
Module that initiates page fault
monitoring
RMS-11 sample overlay description
RMS-11 object library
RMS-11 macro library
RMS-11 shared resident library sample build
file
Reserved for future use
RSX-llM compatibility mode macro library
Shareable image of RSX-llM application
migration executive

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

B-n

FILES OF THE VAX/VMS SYSTEM

Table B-3 (Cont.)
Files Contained in Directory [SYSLIB]
File Name

Description

1-------·------··-·---·----i-------

RSXUSR.EXE

Shareable image of RSX-llM application
migration executive
TECO macro to search files for strings
FORTRAN program utility INCLUDE files
Condense TECO macros
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
TYPE command utility
RSX-llM work file support routines
Shareable image for Run-Time Library
TECO macro that provides a keypad-scope TECO
editor
VT52/VT100 keypad editor
Definitions available for programs using DR780
support routines

SEARCH.TECl
SIGDEF.FOR
SQU.TECl
STARLET.MLB
STARLET.OLB
STARLET.REQ
SUMSHR.EXE
SYSLIB .OLB
TPAMAC.REQ
TRACE.EXE
TYPE .TECil
VMLIB .OLB
VMSRTL.EXE
VT52.TEC1
VTEDIT.TECl
XFDEF.FOR

1----------+--·----------.--- --·-------

1. Not supported by DIGITAL.

Table B-4
Files Contained in Directory [SYSMGR]
File Name

Description
Line printer characteristics for print
symboint
Line printer forms description for print
symbiont
LPAll site-specific start-up command procedure
Remote terminal loader
Site-specific system shut-down command
procedure
Site-specific system start-up command
procedure

CHARTYPE.DAT
FORMSTYPE.DAT
LP All STRT. COM
RTTLOAD.COMl
SYSHUTDWN.COM
SYSTARTUP.COM

....__ _ _ _ _ _ _ _ ___.___ _ _ _ _ _ _ _ - - - - - - - - - - - - · - - -

-··--------1

1. Requires DECnet-VAX optional product for use.
Table B-5
Files Contained in Directory [SYSMSG]
Description

File Name

RSX-llM compatibility mode QIO message file
Help file for SOS text editor
System message file

QIOSYM.MSG
SOS.HLP
SYSMSG.EXE

________ _________ - - - - - - - - - - -

.__

__.

B-7

FILES OF THE VAX/VMS SYSTEM
Table B-6
Files Contained in Directory [SYSTEST]
Description

File Name
APPEND.PIP
DMPASRC.DMP
DMPBYOC.DMP
DMPDATA.DMP
DMPDCWD.DMP
GLOBALSl.COM
GLOBALS2.COM
MCLBRl.MAC
MCLBR2.MAC
MCLBR3.MAC
OBJLBRl.OBJ
OBJLBR2.0BJ
OBJLBR3.0BJ
PATCHED.PAT
PATCHPAT.OBJ
PIPDATA.PIP
RANDOM.FLX
SATSSFOl.EXE
SATSSF02.EXE
SATSSF03.EXE
SATSSF04.EXE
SATSSFOS.EXE
SATSSFOn.EXE
SATSSF07.EXE
SATSSF08.EXE
SATSSF09.EXE
SATSSFlO.EXE
SATSSF 11. EXE
SATSSF12.EXE
SATSSF13.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

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
Command procedure that contains global symbols
Command procedure that contains global symbols
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
Tests for $CMEXEC and $GETMSG services
Tests for I/O services
Tests for send system services
Tests for I/O services
Tests for memory management services
Tests for memory management services
Tests for memory management services
Tests for handler services and $ADJ
Tests for $FAQ services and $SNDERR
Tests for $INPUT, $OUTPUT, $QIO, and $QIOW
services
Tests for $CREPRC, $SETPRV, and $UNWIND
services
Tests for I/O services
Tests for send message services
Tests for $CREMBX, $DELMBX services
Tests for $BRDCST service
Tests for $FAO, $FAOL SERVICES
Tests for $GETMSG and $PUTMSG services
Tests for condition handling services
Tests for timer and AST services
Tests for logical name services
Tests for $CREPRC service
Tests for SDELPRC service
Tests for $SUSPND service
Tests for $RESUME service
Tests for $HIBER service
Tests for $WAKE service
Tests for $EXIT service
(continued on next page)

B-8

FILES OF THE VAX/VMS SYSTEM
Table B-6 (Cont.)
Files Contained in Directory [SYSTEST]
File Name

Description

SATSSS42.EXE
SATSSS43.EXE

Tests f or $FORCEX service
Tests f or exit and change mode handling
service s
Tests f or $SETPRN service
Tests f or $SETPRI service
Tests f or $SETRWM service
Tests f or $SETPRV service
Tests f or $ASCEFC, $DACEFC services
Tests f or $DLCEFC service
Tests f or $SETEF service
Tests f or $CLREF service
Tests f or $READEF service
Tests f or wait services
Tests f or time conversion services
Tests f or $SCHDWK, $CANWAK services
Tests f or $EXPREG service
Tests f or $CNTREG service
Tests f or $CRETVA service
Tests f or $DELTVA service
Tests f or global section services (currently
disable d)
Tests f or $LKWSET, $ULWSET services
Tests f or $LCKPAG, $ULKPAG services
Tests f or $PURGWS service
Tests f or $ADJWSL service
Tests f or $SETPRT service
Tests f or $SETSWM service
Tests f or change mode services
Tests f or $ADJSTK service
Utility module for SATSSFOS, SATSSF18, and
SATSSS3 5
Utility module for SATSSS50
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
Command procedure that scans service list
Command procedure that executes test modules
Input d ata to test SLP utility
Good OU tput file for SLP test
Good ou tput 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 d ata file for VAX-11 SORT tests
Tests F LX utility
Master script for VAX-11 SORT test

SATSSS44.EXE
SATSSS45.EXE
SATSSS46.EXE
SATSSS47.EXE
SATSSS50.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
SATSSS90.EXE
SATSSS91.EXE
SATSUTOl.EXE
SATSUT04.EXE
SATSUT05.EXE
SATSUT06.EXE
SATSUT07.EXE
SATSUT08.EXE
SATSUT09.EXE
SATSUTlO.EXE
SATSUTll. EXE
SATSUT12.EXE
SATSUT13.EXE
SATSUT14.EXE
SCAN.COM
SETEXEC.COM
SLPDATA.SLP
SLPLIST.SLP
SLPOUT.SLP
SMFILEl.DAT
SMFILE2.DAT
SMFILE3.DAT
SMFILE4.DAT
SORT.DAT
SORTED.FLX
SORTUETP.COM

(continued on next page)

B-9

FILES OF THE VAX/VMS SYSTEM
Table B-6 (Cont.)
Files Contained in Directory [SYSTEST]
File Name
SSHELP.COM
SSTEST.COM
TSTOlA.EXE
TSTOlB.EXE
TST02A.EXE
TST03A.EXE
TST03B.EXE
TST06A.EXE
TST07A.EXE
TSTlOA.EXE
TSTlOB.EXE
TSTllA. EXE
TSTllB. EXE
TST12A.EXE
TST12B.EXE
TSTlSA.EXE
TSTHA.EXE
TST16B.EXE
TST16C.EXE
TST17A.EXE
TST17B.EXE
TST20A.EXE
TST20B.EXE
UETCOMPOO.COM
UETCOMPOl.COM
UETCOMP03.COM
UETCSOSOl.DAT
UETCSOS02.CMD
UETCSOS03.DAT
UETDISKOO .COM
UETDISKOO .EXE
UETFORTOl.DAT
UETFORT97.EXE
UETFORT98.EXE
UETFORT99.EXE
UETINITOO. EXE

Description
Command procedure that contains help
information for system service tests
Master command procedure for system service
tests
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 SEND DATA, RECEIVE DATA (RSX-llM
directive) currently disabled
Test for SEND DATA, RECEIVE DATA (RSX-llM
directive) currently disabled
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
Command procedure for verifying the
compatibility mode utility tests
Main script for RSX-llM executive directive
test
Data file for SOS test
Commands for SOS test
Known good data after SOS editing
Logs in and runs the disk test
Disk 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
(continued on next page)

B-10

FILES OF THE VAX/VMS SYSTEM
Table B-6 (Cont.)
Files Contained in Directory [SYSTEST]
File Name

Description

UETINITOl.EXE
UETLOADOl.EXE

Quick checks all devices for testability
Controls load test with various numbers
of users
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
user script for load test
Tests high page faulting rates in load test
Script that runs VAX/VMS system service tests
Creates a process to run VAX/VMS system
service tests
Main script for VAX-11 RMS tests
Test program to exercise VAX-11 RMS functions
Main command procedure for entire UETP
Creates detached process to run I/O device
tests
Logs in and runs the printer test
Tests printer
Logs in and runs the magnetic tape test,
including MOUNT and DISMOUNT commands
Tests magnetic tapes on one controller
Creates logical names used for mounting
magnetic tapes
Delivers exit status from tape test to
UETPDEVOl
Logs in and runs terminal test
Tests terminals for one controller

UETLOAD02.COM
UETLOAD03.COM
UETLOAD04.COM
UETLOAD05.COM
UETLOAD06.COM
UETLOAD07.COM
UETLOAD08.COM
UETLOAD09.COM
UETLOADlO.COM
UETLOADll.COM
UETMEMYOl.EXE
UETNATVOO.COM
UETNATVOl.EXE
UETNRMSOO.COM
UETNRMSOl.EXE
UETP.COM
UETPDEVOl.EXE
UETPRINOO.COM
UETPRINOO.EXE
UETTAPEOO.COM
UETTAPEOO.EXE
UETTAPEOl.EXE
UETTAPE02.COM
UETTTYSOO.COM
UETTTYSOO.EXE

- - - - - - - - - - - ·-··-Table B-7
Files Contained in Directory [SYSUPD]
Description

File Name
BOOTUPD.COM
CONSCOPY.COM
CVTUAF.COM
DIRCLENUP .COM
DXCOPY.COM

Command procedure that updates VMS bootstrap
file on console floppy diskette
Command procedure that copies console floppy
diskette
Command procedure that converts Version 1.0
SYSUAF files to Version 2.0 format
Command procedure that removes dangling
directory entries
Command procedure that copies files from console
floppy diskette and restores files to floppy
diskette

~-------~-------·

·-··

(continued on next page)

B-11

FILES OF THE VAX/VMS SYSTEM
Table B-7 (Cont.)
Files Contained in Directory [SYSUPD]
File Name
SETDEFBOO.COM
SWAPFILES.COM
UPGRADBLD.COM
UPGRADFIN.COM
VMSKITBLD.COM
VMSKITBLD.DAT
VMS UPDATE.COM

Description
Command procedure that sets default boot command
file
Command procedure that creates swapping, paging,
and system dump files of appropriate size for
system being installed
Command procedure that builds and applies
upgrade kits
Command procedure that completes upgrade
operation
Command procedure that builds and copies VAX/VMS
distribution disk
Files in VAX/VMS system disk that drive
FLDKITBLD, FLDKITFIN, and VMSKITBLD
System update command procedure

Table B-8
Files Contained in Directory [SYSHLP.EXAMPLES]
File Name
ADDRIVER.MAR
CONNECT.COM
DRCOPY.PRM
DRCOPYBLD.COM
DRMAST.MAR
DRMASTER.FOR
DRSLAVE.FOR
DRSLV.MAR
GBLSECUFO.MAR
LABCHNDEF.FOR
LABIO.OPT
LABIOACQ.FOR
LAB roe IN • MAR
LABIOCIN .OPT
LABIOCOM.FOR
LABIOCOMP .COM
LABIOCON.FOR
LABIOLINK.COM
LABIOPEAK.FOR
LABIOSAMP.FOR

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 (the
DR32 file transfer program)
Slave subroutines for DRCOPY (the
DR32 file transfer program)
VAX-11 RMS interface for DRSLAVE.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 LABIO- ·
system 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
(continued on next page)

B-12

FILES OF THE VAX/VMS SYSTEM

Table B-8 (Cont.)
Files Contained in Directory [SYSHLP.EXAMPLES]
.------------.------------------·-----·--------

File Name
LABIOSEC.FOR
LABIOSTAT.FOR
LABIOSTRT.COM
LABMBXDEF.FOR
LBRDEMO.COM
LBRDEMO.FOR
LBRMAC.MAR
LPATEST.FOR
PEAK.FOR
SCRFT.MAR
TESTLABIO.FOR
TDRIVER.MAR
USSDISP.MAR
USSLINK.COM
USSTEST.MAR
USSTSTLNK.COM
XADRIVER.MAR
XAMESSAGE.MAR
XATEST.FOR

Description
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
Peak selection routine in LABIO system
Optional screen package (SCR$ ••• in RTL)
extension to handle foreign terminals
Tests LABIO sytem
Template for user-written driver
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
DR-11 test program
Companion program for XAMESSAGE

B-13

APPENDIX C

BOOTSTRAP COMMAND PROCEDURES

This appendix contains samples
bootstrap the system.

the

C-1

command

procedures

used

BOOTSTRAP COMMAND PROCEDURES

OBJGEN,,1
50
55
57

100
200

0B3 CONVERSATIONAL BOOT COMMAND FILE • DSlGEN,
Boor FROM 083 AND STOP IN SYSBOOT TO ALTER P4RAMETERS
'''
HAL.T PROCESSOR
'
UNJAM
UNJAM SBI
HAL.T

300
400
5011

INIT
DEPOSIT/I 11 20003800
DEPOI IT Re 0

H0
700

DEPOSIT Rt 8
DEPOSIT R2 3
DEPOSIT R] 3
DEPOSIT Rq 0
DEPOSIT R5 1
D!POI IT f'p 0

800

H0
10011

1100
1200

1410
1500

Pao• 1

ST ART 2Hl03000
WAIT DONE

1'90

!)(AMIN! IP
LOAD VMa,EXE/START1t

1'700

START t

INIT PROCESSOR
SET UP SCBB
DISK PAC~ DEVICE TYPE
MBA TR•S
ADAPTER UNIT • 3
CONTROLLER UNIT • 3
BOOT BLOCK L.BN (UNUSED)
SOFTWARE BOOT FLAGS (CONVERSATIONAL. BOOT>
SET NO MACHINE CHECK EXPECTED
START ROM PROGRAM
WAIT FOR COMPLETION
SHOW ADDRESS OF WORKING MEMORv+•x200
LOAD PRIMARY BOOTSTRAP
AND START IT

C-2

BOOTSTRAP COMMAND PROCEDURES

Paoe t

DB6GEN,r1
50

55
57
60
100

200
300
400
50el
U0

700
8H
4'00

1100
1200

1400
15H

1 7110

''
'
HAL.T
'UNJAM

086 CONVERSATIONAL BOOT COMMAND FILE • 086GEN,
Boor FROM DB6 AND STOP IN SYSBOOT TO ALTER PARAMETERS

INIT
DEPOSIT/I 11 ~0003800
D!POS IT R0 0

DEPOSIT Rt 8
DEPOSIT R2 b
DEPOSIT R3 b
DEPOSIT Rt.t id

DEPOSIT R5 l
DEPOSIT FP 0

ST ART 20003000
WAIT DONE
!UMINE SP

LOAD VMB,!XE/START1•
START •

HAL.T PROCESSOR
UNJAM SBI
INIT PROCESSOR
SET UP SCBB
DIS~ PACK DEVICE TYPE
MBA TR•8
ADAPTER UNIT • 6
CONT~OL.L.ER UNIT • 6
800T BL.OCK LBN (UNUSED)
SOFTWARE BOOT FLAGS (CONVERSATIONAL BOOT)
SET NO MACHINE CHECK EXPECTED
START ROM PROGRAM
WAIT ~OR COMPLETION
SHOW ADDRESS OF WORKING M!MORv+•x200
LOAD PRIMARY BOOTSTRAP
ANO START IT

C-3

BOOTSTRAP COMMAND PROCEDURES
DB1BOO,C~Dr2

100
200
300
400
500
b00
700
800
900
1000
1100
1200
1300

Page 1

DBl BOOT COMMAND FILE

MALT
UNJAM
INIT
DEPOSIT/I 11 20003800
DEPOSIT R0 ~
DEPOSIT Rt 8
DEPOSIT R2 1
DEPOSIT RJ 1
DEPOSIT R4 ~
DEPOSIT RS 0
DEPOSIT Fp ~
START 20003000
~AIT DONE

1400

1500
1600
1700

081800,CMD

l HALT P~OCESSOR
l UNJAM SBI
1 INIT PROCESSOR
1 SET UP SCB8
1 DISK PACK DEVICE TYPE
1 ~BA TR:6
1 ADAPTER U~IT : 1
1 CONTROLLER UNIT : 1
l BOOT ~LOCK LBN (UNUSED)
l SOFT~AQE BOOT FLAGS
l SET NO MACHINE CHECK EXPECTED
1 STAQf ROM PROGRAM
1 WAIT FOR COMPLF.TIO~
1

EXAMINE Sp
LOAD VMB,EX~/START1•
START f

l SHO~ ADDRESS OF ~ORKING MEMORv+·x200
1 LOAD P~JMARY BOOTSTRAP
1 A~O START IT

C-4

BOOTSTRAP COMMAND PROCEDURES

Page 1

OB0BOO,CMDJ2
50

55
b0

''
MALT
'

oa0 BOOT COMMAND FILE • oa0soo.cMD

100
200
300
400
500

DEPOSIT R0 Id

600

DEPOSIT Rt 6

700

UNJAM
INIT

DEPOSIT/I 11 20003800
DEPOSIT R2 0

HALT PROCESSOR
UNJ•M SBI
INIT PROCESSOR
SET UP SCBl3
DISK PACK DEVICE
MBA Th8
ADAPTER UNIT a 0

TYPE

1000

DEPOSIT Rt.i "'
DEPOSIT Rs 0

1100
1200

START 200030et0

1300

WAIT DONE

CONTROLLER UNIT s 0
BOOT BLOCK LBN (UNUSED)
SOFTWARE BOOT FLAGS
SET NO MACHINE CHECK EXPECTED
START ROM PROGRAM
wAIT FOR COMPLETION

EXAMINE SP
LOAD VMB,EXE/STARTlf
START f

LOAD P~IMARY BOOTSTRAP
ANO START IT

800

DEPOSIT R3 0

q(lJ0

1400
1500
1U0
1700

DEPOSIT FP 0

SHOW

C-5

ADD~ESS

OF WORKING MEMORY+•x200

BOOTSTRAP COMMAND PROCEDURES
Page 1

55
60
100
200
300
400
500
600

l
DBBi BOOT COMMAND FILE • DEF900,CMD
'
MALT
I HALT PROCESSOR
UNJAM
1 UNJA~ SBI
!NIT
I INIT PROCESSOR
DEPOSIT/I 11 20093800
I SET UP SCBB
DEPOSIT Re 0
I DISK PACK DEVICE TVPE
DEPOSIT Rt 9
I MBA TRsq r SECOND ~BA
DEPO!IT R2 2
I ADAPTER U~IT • 2
DEPOSIT R3 2
I CONTROLLER UNIT c 2
DEPOSIT R4 ~
l BOOT BLOCK LBN (UNUSED)
DEPOSIT RS 2
1 SOFTWARE BOOT FLAGS C~EEP DEBUG CODE)
DEPOSIT 'P 0
I SET NO MACHINE CHECK EXPfCTEO
START 20003000
I START ROM PROGRAM
WAJT DONE
& WAIT FOR CO~PLETION
'
EXAMINE SP
' SHOW ADDRESS OF WORKING ME~O~v+·x2~0
LOAD VMB,EXE/STARTa•
1 LOAD PRI~ARV BOOTSTRAP
START •
I ANO START IT

T00

800

qe0
1000
1100
1200
1300
1400
1500
1600
1700

C-n

BOOTSTRAP COMMAND PROCEDURES
Page 1

RESTAR,CMDJ2

''
HALT
'

RESTART COMMMAND FILE •

RESTAR.C~D

THIS COMMAND FILE IS INVOKED IN THE fVENT OF POWER RECOVERY AND
OTHER CONSOLE DETECTED RESTART CONDITIONS IF THE AUTO RESTART SWITCH
IS SET, IT CAN ALSO BE INVOKED MANUALLY WITH THE COMMAND:

lNIT

D!POSIT/I 11 20003800
DEPOSIT R0 0
DEPOSIT R1 3
DEPOSIT R2 0

DEPOSIT Rl 0
D!POUT R4 0
D!POIIT RS 0
D!POUT f'P 0
START 20003004

•RESTAR.CMD

HALT PROCESSOR
INITIALIZE PROCESSOR
SET ADDRESS OF sea BASE
CLEAR UNUSED REGISTERS
USA TR•3
CLEAR UNUSED REGISTER
CLEAR UNUSED REGISTER
CLEAR UNUSED REGISTER
CLEAR UNUSfD REGISTER
NO MACHINE tHECK EXPECTED
START ~ESTA~T REFEREE

C-7

BOOTSTRAP COMMAND PROCEDURES
DM0B00,1LV'1
100

zee

P1ge 1

300
4H
SH

0M0 BOOT COMMAND FILE FOR INTERLEAVED MEMORIES • DM0BOO,ILV
THIS IS A TEMPLATE eOMMAND FILE FOR BOOTING ,ROM RK06/RK07 DISKS
IN SYSTEMS WITH TWO INTERLEAVED MEMORY CONTROLLERS, THE MEMORV
CONTROLLERS ARE ASSUMED TO BE AT TR NUMBERS 0 AND 11

560
6H
700
HI

THIS COMMAND FILE SHOULD BE EDITED TO CHANGE THE UNIT NUMBER IF
NECCESSARV ANO USED TO REPLACE THE DEFAULT BOOT COMMAND FILE,

550
555

1110

UH
1300
1400
l!H
1600
1710
1705
1710
1115
1720
18eeJ
1q00
2000

2100
22011J
2300

I
I
I
I
I
I

WAIT DONE

HALT PROCESSOR
UNJ.lM SBI
INIT PROCESSOR
SET UP SCBB
CARTRIDGE DISK
UBA TR:sl
CSR ADDRESS OFFSET • 3FF20
CONTROLLER UNIT • 0
BOOT BLOCK LBN CUNUSED)
SOFTWARE BOOT FLAGS
SET NO M.lCHINE CHECK EXPECTED
EN•BLE INTERLEAVE ,OR TR #1 MEMORY CONTROLLER
FORCE ~ STARTING ADD~ESS
ENABLE INTERLEAVE FOR TR #~ MEMORY CONTROLL!R
FORCE 0 STARTING ADDRESS
START ROM PROGRAM
WAIT FOR COMPLETION

EXAMINE SP
LOAD VMB,EXE/START1•
START •

SHOW ADDRESS OF WORKING MEMORY+•x200
LOAD PRIMARY BOOTSTRAP
ANO START IT

HALT
UNJAM
INIT
DEPOlIT/I 11 20003800
DEPOSIT R0 1
DEPOSIT Rt 3
DEPOSIT A2 lFF20
DEPOSIT R3 ra
DEPOSIT R4 0
OEPOS IT R5 ~
DEPOSIT FP 0
DEPOSIT 20002000 101
DEPOSIT 20002004 4000
DEPOSIT 20004000 101
DEPOSIT 20004004 4000
ST ART 20003000

C-8

BOOTSTRAP COMMAND PROCEDURES
D80BOO,Il.Vs1
100
200
212

224
236

Z48
2U
272

284
300
400

500

700
800
900
UHi
1100

1200
1300

14QJ0
1420

1440
1460
1480
1500
1600
1700

1800
1900
i!QJ00

''
''
''
'
UNJAM
1

Pege 1

080 BOOT COMMAND FILF FOR iNTERl.EAVEO MEMORIES • D80BOO,ILV
THIS IS A TEMPLATE COM~ANO FILE FOR BOOTING ~ROM RM03/AP06 DISKS
IN SYSTEMS wITH T~O INTERLEAVED ~EMORY CONTROLLERS, THE M!MORY
CONTROLLERS ARE ASSUMEO TO BE AT TR NUMBERS 0 ANO 1,
THIS COMMAND FILE SHOULD BE EDITEO TO CHANGE THE UNIT NUMBER I'
NECCESSARY AND USED TO REPLACE THE DEFAULT BOOT COMMAND ,IL!,

DEPOSIT 20002004 4000
DEPOSIT 20004000 101
DEPOSIT 20004004 4000
START 20003000
WAIT DONE

HALT PROCESSOR
UNJAM SBI
INIT PROCESSOR
SET UP SCBB
DISK PACK DEVICE TYPE
MBA TR•8
ADAPTER UNIT • 0
CONTROLLER UNIT • 0
BOOT BLOC~ LBN (UNUSED)
SOFTWARE BOOT FLAGS
SET NO MACHINE CHECK EXPECTED
ENABLE INTERLEAVE FOR TR #l MEMORY CONTROLL!R
FORC~ 0 STARTING ADDRESS
ENABLE INTERLEAVE FOR TR #2 MEMORY CONTROLLER
FORCE 0 STARTING ADDRESS
START ROM PROGRAM
WAIT FOR COMPLETION

EXAMINE SP
LOAD VMB,EXE/START1f
ST ART tt

SHOW ADDRESS OF WORKING MEMORV+Axzee
LOAD PRIMARY BOOTSTRAP
AND START IT

HALT

HUT

DEPOSIT/I 11 20003800
DEPOSIT R0 0
DEPOSIT Rt 8
DF.POS IT R2 Id

DEPOSIT R3 0
DEPOSIT R4 0
DEPOSIT R5 0
DEPOSIT Fp 0
DEPOSIT 20002000 101

C-9

BOOTSTRAP COMMAND PROCEDURES
DB0BOO,Il.Vr1
100
200
212
224
236
248
260
27i?
284
300

400

''
''
I

P1ge 1
080 BOOT COMMAND FILf FOR INTERLEAVED MEMORIES • 080800,ILV
THIS IS A TEMPI.ATE COMMAND FILE FOR BOOTING FROM RM03/RP06 DISKS
IN SYSTEMS ~ITH Two INTERLEAVED MEMORY CONT~OLLERS, THE MEMORY
CoNTROLLERS ARE ASSUMED TO BE AT TR NUMBERS 0 AND 1,

'
1

TMIS COMMAND FILE SHOULD BE EOITEO TO CHANGE THE UNIT NUMBER IF
NECCESSARY AND USED TO REPLACE THE DEFAULT BOOT COMMAND FILE,

tilALT
UNJAM
HUT
DEPOSIT/I 11 20003800
DEPOSIT Re 0

1611
17H
IHI

WAIT DONE

l-IALT PROCESSOR
UNJAM SBI
INIT PROCESSOR
SET UP SCBB
DISK PACK DEVICE TYPE
MBA YR•8
ADAPTER UNIT • 0
CONTROLLER UNIT • 0
BOOT BLOCK LBN (UNUSED)
SOFTWARE BOOT FL~GS
SET NO MACHINE CHECK EXPECTED
!NABLE INTERLEAVE FOR TR #l MEMORY CONTROLl.ER
'ORCE 0 STARTING ADDRESS
!NABLE INTERLEAVE FOR TR #Z MEMORY CONTROLLER
'ORCE 0 STARTING ADDRESS
START ROM PROGRAM
WAIT 'OR COMPLETION

EXAMINE: SI'

SHOW ADDA~SS 0, WORKING M!MORv+•x211

1'811
2181

START f

500
600

700
800

900
1000
1100

1280
1100
1400
14Z0
1440

DEPOSIT Rt 8
DEPOSIT R2 · 0
DEPOSIT RJ 0

DEPOSIT R4 0
DEPOSIT R5 0
DEPOSIT Fp 0
DEPOSIT 20002000 101
DEPOSIT 20002004 4000

1461

DEPOSIT 20004000 101

1480

D!POIIT 20004004 4000
ST ART 2011103000

1500

LOAD VM8,!XE/START1f

LOAD PAIMAAV BOOTSTRAP
ANO START IT

C-10

BOOTSTRAP COMMAND PROCEDURES

Page 1

D80BOO,IL.V,1
100
200
212

2Z4
236
Z48
2b0

272
284
300
400

500

''
''
'
'''
HAL.T
'
l

080 BOOT COMMAND FILF. FOR INTERL.EAVEO MEMORIES • 080800,ILV
THIS IS A TEMPLATE COM~ANO FILE FOR BOOTING ,ROM RM03/AP06 DISKS
IN SYSTEMS WITH Two INTERLEAVED MEMORY CONTROLLERS, THE M!MORV
CONTROLLERS ARE ASSUMED TO BE AT TR NUMBERS 0 AND 1,
THIS COMMAND FILE SHOULD BE EDITED TO CHANGE THE UNIT NUMBER I'
NfCtESSARY AND USED TO REPLACE THE DEFAULT BOOT COMMAND ~IL!,

UNJAM

f,0QJ

INIT

700

DEPOSIT/I 11 20003800

800
900
1000

1100
1Z00

uee

14QJ0
1420
1440
t4bll!l

1480
1500
1600
1700

1800
14100
i?000

DEPOSIT
DEPOSIT
OEPOS IT
DEPOSIT

R0 0
Rt 8

111

R3 Id

DEPOSIT Rq 0
OEPOS IT R5 0

DEPOSIT Fp 0
DEPOSIT 20002000 101
DEPOSIT 20002004 4000
DEPOSIT 20004000 101
O!POSIT 20004004 4000
START 20003000
WAIT DONE

EXAMINE SP
LOAD VMB,EXf/STARTa•
ST ART '

HALT PROCESSOR
UNJAM SBI
PUT PROCESSOR
SET UP SCBB
DISK PACK DEVICE TYPE
MBA TR•8
ADAPTER UNIT • 0
CONTROLLER UNIT • 0

BOOT BLOC~ LBN (UNUSED)

SOFTWARE BOOT FLAGS

SET NO MACHINE CHECK EXPECTED
ENABLE INTERLEAVE FOR TR #1 MEMORY CONTROLL!R
FORC~ 0 STARTING ADDRESS
ENABLE INTERLEAVE FOR TR #2 MEMORV CONTROLLER
FORCE 0 STARTING ADDRESS
START ROM PROGRAM
WAIT FOR COMPLETION
SHO~ ADDRESS OF WORKING MEMORv+•x20e
LOAD PRIMARY BOOTSTRAP

AND START IT

C-9

BOOTSTRAP COMMAND PROCEDURES
080800,ILV,1
100

DB0 BOOT COMMAND FILF FOR INTERLEAVED MEMORIES • 080800,ILV
''
THIS IS A TEMPLATE
FILE FOR BOOTING FROM RM03/RP0& DISKS
IN SYSTEMS wITM TWO INTERLEAVED MEMORY CONTROLLERS, THE MEMORY
''
CONTROLLERS ARE ASSUMED TO BE AT TR NUMBERS. ANO 1,
'
THIS COMMAND FILE SHOULD BE EDITED TO CHANGE TME UNIT NUMBER IF
2n '
' NECCESSARY AND USED TO REPLACE THE DEFAULT BOOT COMMAND FILE,
MALT
HALT PROCESSOR
'
UNJAM
UNJAM SBI

200
212

COM~AND

224

23b

248
2b0

28/J

300
400
500
b1110
700

INIT
DEPOSIT/I 11 20003800

800
9eJ0

1000
1100
UH

1400

1420
1440

uu
1480

1500
1680

DEPOSIT R0 0

DEPOSIT R1 8
DEPOSIT R2 0
DEPOSIT R3 0
DEPOSIT R4 0
DEPOSIT R5 0
DEPOSIT Fp 0
DEPOSIT 20002000 101
DEPOSIT 2e00Z004 4000
DEPOSIT 20004000 101
D!POIIT 20014004 4000
ST ART 2He3000
WAIT DONE

1111

l9H
2HllJ

EXAMINE IP

LOAD VM8,EXE/START1•
START ti

INIT PROCESSOR

SET UP SCBB

DISK PACK DEVICE TYPE
YR•8
ADAPTER UNIT • 0
CONTROLLER UNIT • 0
BOOT BLOC~ LBN (UNUSED)
SOFTWARE BOOT FL4GS
MBA

!ET NO MACHINE CHECK EXPECTED

!NABLE INTERLEAVE FOR TR #1 MEMORY CONTROLLER
'ORCE 0 STARTING ADDRESS
!NABLE INTERLEAVE FOR TR #Z MEMORY CONTROLLER
'ORC! 0 STARTING ADDRESS
START ROM PROGRAM
WAIT FOR COMPLETION
SHOW ADDR~SS 0, WORKING M!MORv+•xzaa
LOAD PRIMARY BOOTSTRAP
AND START IT

C-10

BOOTSTRAP COMMAND PROCEDURES

RE 8 TA~-. IL VJ 2

''
''
''
'
I

3•APR•1980 15125105.70

P1oe

RESTART COMMMAND FILE FOR INTERLEAVED MEMORIES • RESTAR.ILV
THIS COMMAND FILE SHOULD REPLACE RESTAR.CMD FOR SYSTE~S WITH TWO
INTERLEAVED MEMORY CONTROLLERS. MEMORY CONTROLLERS ARE ASSUMED
TO BE AT TR NUMBERS 1 ANO 2.

THIS COMMAND FILE IS INVOKED IN THE EVENT OF POWER RECOVERY AND

OTHER CONSOLE DETECTED RESTART CONDITIONS IF THE AUTO RESTART SwlTCH

IS SET,

IT CAN ALSO BE INVOKED MANUALLY WITH THE COMMANDa
•RESTAR.CMD

HALT

!NIT

DIPOIITII 11 20003800
D!POl!T R0 0
D!POUT R1 3

DEPOSIT R2 0
O!POIIT RJ 0
DEPOSIT R4 0
DEPOSIT RS 0

DEPOSIT 'P 0
D!POIJT 20102000 101
D!POIIT 20002004 4000
D!POIIT 20014000 101

D!POIIT 20004004 4000

IT ART 21103004

HALT PROCESSOR
INITIALIZE PROCESSOR
SET ADDRESS OF see BlSE
CLEAR UNUSEO REGISTERS
UBA TR•3
CLEAR UNUSED REGISTER
CLEAR UNUSED REGISTER
CLEAR UNUSED REGISTER
CLEAR UNUSED REGISTER
NO MACHINE CHECK EXPECTED
ENABLE INTERLEAVE FOR TR #1 MEMORY CONTROLLER
FORCE 0 STARTING ADDRESS
ENABLE INTERLEAVE FOR TR #2 MEMORY CONTROLLER
FORCE 0 STARTING ADDRESS
START RESTART REFEPEE

C-11

BOOTSTRAP COMMAND PROCEDURES
Bootstrao Helo Ftle •

l
I

'
I
1
I

ROOT.~LP

Thts ff le d•1crtbe1 t~e fnout per1~eter1 to the boot1trap progr1m
VMB.EXE. ~orme11v the bootltr10 will 1ooku~ the ff le [SYSEXE]SYSBOOT,EXE
on the •Pecf fted device, load ft into memory and tranefer control
to ft,

l
I
I

l
l
1
1

Two 1et1 of command ft1e1 ere provided on t"• VAX/VMS con101t flopov
to Perform t~e neee11arv bootstra~ ooer1tf on1, One aet of the1e commend
ff lea wf 11 boot 1el1ctfnQ en ootfon to atoo tn SVSBOOT to 1lter 1v1t1m
perimeters, T~ev ere tnvoked a1 eon1ole fndtroct command ff lee,
•OM~GEN

I
I
I
I
l
I
I

l
I
I

'
'
''
'
'
'''
'
I

I
I

l
l

I
1
I

Boot frol'fl RK07 unf t 0
Ul"lit 1
unit 2
unit l
Boot from RM03/AP06 unit 0
unh 1

•OM1GEN
•oM2GEN
f[)M3GEN
•oB0GEN
•oB1GEN
•oB2GEN
•oB3GEN
•OB4GEN
•oBSGEN
•oBbGEN
•oB7GEN

Ul'l1t

unh 3
unft 4
unft 5
unit b
untt 1

T"• other 1et of t"••• command ff 111 fa norm111v invoked onlv vi•
the BOOT commend but mey be tnvoked •~pltcftlv 11 f"direct commend ff1e1,
Thele commend ff lee Derform 1 nol"mal, non•fnter1ctive boot wfthout env
atop f n SySBOOT to ch1"ge p1r1meter1 1
o ..

BOOT OM0
BOOT DM1
BOOT OM2
BOOT OM3
BOOT 080
BOOT 081
BOOT 082
BOOT 0133
BOOT 084
BOOT DBS
BOOT OBb
BOOT 087

•OM0BOO,CMD

Boot RK07 unf t 0
Ul"I ft 1
unit 2
unf t 3
Boot Rt-103 o I" RP06 unit 0
untt 1
unit 2
unit 3
un ft 4
U!"I ft 5
untt b
unf t 7

The boot•tr•p t1 loaded into memory at lea1t o~e Dege above the ff r1t
evaf lab1e workfng memory to allow 1p1ce for the Restart Parameter
Block, T~e eddre1a of the base of the bootstrap f 1 p111ed through
SP, the •tack DOfnter, w"ere ft also serve• •• a tempor1ry stack pof"ter,

1
I
I Input Parameter11

I
I

<3s0>=Devtee Tvpe Code
Df sk Paek
CRM03/RP04/RP05/RP06/RP07)
1 => Cartridge Disk
CRK06/RKA7)

<l11~>ZMBZJ

0 :>

1
1

1
1
I

<3s0>•System Bus Addre11C"TR" Numbe .. )
For moat eonffgurattons t~e following eonventton
u1eo1
TR· NumbtH
Adapter I Contro11er

<311~>=MBZJ

3
8

···----·------~----·
UNIBUS
adaDter
MASSBUS adapter number

C-12

~••been

BOOTSTRAP COMMAND PROCEDURES
MASS8US adapter number 2

For UBAa
<31118>=MBZs <1713>sUNI8US Address of Contro1 Regf1ter'
<210>:MBZ
RK06/RK07 CSR s 3FF20
<3114>:MBZJ <l10>=Contro1ler/Formatter Number

R3
R4
RS

<3114>•~BZJ <3a0>=Unft Number
<311~>=Logfc11 Block Number to read
<311~>•Software Boot Control fleQI
Bit
~eenfng

...0

11 boot block

··----·

Conversatfona1 boot, At vorfoua pofnt1 fn the 1v1ttm
boot procedure, parameter and other fnput wf 11 bt
solfcfttd from the con101e,
Debug, This flag f 1 passed through to VMS end c1u1e1
the code for the exec debugger to be included fn
the running ayatem,

Inf tfal breakpoint, If thf s flag 11 set, end th• exec
debugger code f 1 included Cf1ag bf t 1) then 1 breakpofnt
wf 11 occur fmmediately ofter the exec enables m1ppfng,

Boot block, If this flag f1 1et then tho boot block
wf 11 be read and control tran1fered to ft,

Ofagnoatic boot, Thie flag c~uses a boot by ff le
name for the df eonostfc auporvf sor,

8oot1trap ~reakpoint, This fleg c1u1e1 the bOot1tr1p
to stop a breekDof nt after performfno nece111rv fnf t•
falfzatfon ff ft has been buflt with debug code,

Image header, If this flag is set th• tr1"1fer addre1s
from the image needer of the boot file w111 be used,
Otherwise control w111 transfer to the fi~1t byt of t~e
boot f11e,

Memory teat fnnibit, This f11g 1nnibit1 the te1tino
of ~•mory during bootstrapping,

Ff le name, Causes the bootstrap to solicit the name
of the boot f11e,

Halt before transfer, Cauaea a HALT instruction
to be e~ecuted prfor to the tranafer to the bootf11e,
This ootfon is useful for debugging purposea,

ADoRfSS+c•x200) of first workfng 6UKb memory region
usab1e es both stack pointer and pointer to good memory,

Output Parameters•
R10

R11
SP
PPS.SCBB •

Base address of reoion containing oecondary bootstrap
Pointer to Restart Parameter Block (RPS)
Stac~ Pointer
System Control Block base register

C-13

BOOTSTRAP COMMAND PROCEDURES

''
'

'''
'
'
I

+••••••••·••••••••••••••••••••••••••••••••+
Re1tart Parameter Block

1BASE

CRP~)

+••••••••·••••••••••••••••••••••••••••••••+ 1BASE+•x200
Primary BootstraD Code

''
'

+·········································+ 1PRs.sce0

'
I
I
l

+•••••••••••••••••••••••••••••••••••••••••+

PFN Bitmap

1
I

'''
''

Sy1tem Control 8loek
1PFN~AP

+········-·······-------------------------+ 1PFNMAP+•xe00
Bootatrap Stack

+··························---------······+ ICSP)
+••·······································+

C-14

APPENDIX D
VAX/VMS SOURCE KIT

The VAX/VMS source kit is a multivolume tape set that contains source
files and object files for all standard components of the VAX/VMS
system, and command procedures, languages, and utilities needed to
build a source kit on disk.
(The languages and utilities used in this
building operation are not supported by DIGITAL.)
Before you can begin building a source kit, you must have two free
RP06 disks: one is used to store the source kit, the other is used to
store the output of the system build.
To use the VAX/VMS source kit, you must mount the first volume of the
kit (the tape labeled VAX/VMS V2.0 VMSRCl SCR MT9) and the RPOn disk
and copy the files from tape to disk.
This copying operation
continues until all the files are copied to disk. To do this, use the
following sequence of DCL commands:
$ ALLOCATE MTcn:
$ ALLOCATE DBcn:
$ MOUNT/FOREIGN MTcn:
$ MOUNT/FOREIGN DBcn:
$ MCR DSC2 DBcn:

= MTcn:

When the last tape has been copied to disk, dismount both the tape and
disk, and remount the disk using the /SYSTEM command qualifier (the
label on the disk is VMSMASTER) • Then execute the following command
procedure to install the source kit:
$ @DBcn:[SYSBLDCOM]SRCINSTAL

This command procedure creates a system build account on the system
that contains the logical name definitions and private commands needed
to set up the proper environment to run a system build. To log in to
this account, specify the user name SYSTEMBUILD and the password
CAVEAT EMPTOR.
Finally, to obtain a general description of the source kit, either
display (by means of the TYPE command) or list (by means of the PRINT
command) the file [SYSBLOCOM]SOURCEKIT.DOC.

D-1

APPENDIX E
BOOT PROCESS

This appendix details the steps required to produce a running
system.

VAX/VMS

Power up occurs.

Code in LSI-11 read-only memory (ROM) reads block O from
floppy diskette into LSI-11 memory.

the

This code reads CONSOL.SYS (the console
floppy diskette into LSI-11 memory.

the

CONSOL.SYS now has control of
performs the following steps:

the

program)

LSI-11.

from

This

program

Loads WCS from the floppy diskette file wcsxxx.PAT.

Accepts commands interactively
procedure on the floppy to:

from

command

(1) Set up SCBB for memory controller ROM code.
(2) Set up registers that indicate boot device type,
unit, CSR, and boot flags.

TR,

(3) Initiate execution of memory controller ROM code;
find the first good contiguous ~4K bytes of VAX/VMS
memory.
(Use adapter mapping register space for
scratch space.) Return base address + AX200 in stack
pointer (SP).
(4) Load VMB.EXE (the primary bootstrap)
diskette into base +AX200 and start
address is a restart parameter block
filled in at different stages of the
5.

VMB is the
capable of
drivers will
performs the

from. the floppy
it. At the base
(RPB) which is
boot process.

primary bootstrap.
It contains I/O drivers
reading and writing all bootstrap devices. The
be available to the second~ry bootstrap.
VMB
following steps:

Saves the register values and some values calculated from
the register values in the RPB.

Determines the amount and pattern of memory.
A page
frame
number
(PFN) bitmap is constructed.
Unless
inhibited by a boot flag, memory is tested for gross,
uncorrectable parity errors. VMB constructs, in the RPB,
a table indexed by TR number of all memory controller and
I/O adapter types.

E-1

BOOT PROCESS

Based on register values, one of the following occurs:
(1) A boot block at the designated LBN will be read
VAX/VMS memory and given control.

into

(2) A file named [SYSEXE]SYSBOOT.EXE
given control.

will

read

and

(3) A file named [SYSMAINT]DIAG.EXE
given control.

will

read

and

(4) A file specified by the user in response to a
will be read and given control.

SYSBOOT is the standard secondary bootstrap.
initialization
suitable
for
the unmapped
SYSBOOT performs the following steps:

prompt

It performs
environment.

Reads the current parameter settings from SYS.EXE.

Looks up the boot device
information about it.

If register values so indicate, prompts the user to
modify current system parameter settings. The user may
change the start-up command procedure name and modify
system parameters using SET or a previously created
parameter file.
New parameters become the
current
parameters on the next boot.

Sets up the SPT, SYSPHD, and PFN data structures.

Reads the resident executive into high physical memory.
The PFN data structure can be smaller because it need not
contain data about the resident executive.

Locates and transfers to INIT code.

INIT is part of SYS.EXE.

driver

file

and

stores

It performs the following:

Enables mapping and sets the PC to system space.

Announces the system.

Initializes the map for I/O adapters.
For MASSBUS,
allocates and initializes ADP, CRB, IDB. For UNIBUS,
allocates and initializes ADP.
Initializes hardware
registers.

Loads the boot disk driver into nonpaged pool and, based
on
driver
prologue
data, finishes allocating and
initializing the data structures for the boot device.

Creates SYS$SYSTEM, SYS$SYSDISK,
names.

Moves a piece of INIT code to the pool and REis to it.
This segment of code releases INIT pages to the free list
and jumps to the scheduler.

E-2

and

SYS$SHARE

logical

BOOT PROCESS
8.

10.

SYSINIT process:
a.

If necessary or requested, prompts for time of day

Writes back system parameters to SYS.EXE

Creates some logical names

Sets up swap and page files

Installs VAX-11 RMS image and system message
pageable system section

Mounts the disk

Creates job controller, OPCOM, and ERRFMT

Creates STARTUP process

file

(ACP process created)

STARTUP reads start-up command procedure, which causes it to:
a.

Create logical names

Run SYS$SYSTEM:SYSGEN to configure the I/O system

Install images

Invoke [SYSMGR]SYSTARTUP.COM

Logout

SYSGEN is run by STARTUP or at any other time.

SYSGEN:

Provides for dynamic loading of and connecting to drivers
(the operator, null, and mailbox drivers are permanently
part of the executive image)

Provides for creation of new parameter files
an encoded format)

Creates paging, swapping, and system dump files

E-3

(which

have

INDEX
BUSER.PAR parameter file, 3-9,
3-10
16USER.PAR parameter file, 3-9,
3-10
32USER.PAR parameter file, 3-9,
3-10
48USER.PAR parameter file, 3-9,
3-10
64USER.PAR parameter file, 3-9,
3-10

Copying a system disk, 3-14
Copying default bootstrap
command procedure, 3-12
Copying distribution medium, 2-3
disk to disk, 2-6
tape to disk, 2-6

A
Automatic restart, 3-12

B
Backing up VAX/VMS, 2-1
BOOT error messages, A-1
Booting with interleaved
memory, 3-12
Bootstrap command procedures, 3-3
samples of, C-1
Bootstrapping VAX/VMS, 3-1
conversational, 3-4
internal operation when, E-1
nonstop, 3-7
Building a system disk, 3-14

Default bootstrap command
procedure, 3-11, 3-13
DEFBOO.CMD command procedure,
3-11, 3-12
DIGITAL standard editor, 1-7
DIGITAL-supplied parameter files,
see System parameter files
Directories of VAX/VMS system, B-1
DISABLE CHECKS command, 4-4
Disk Save and Compress Utility,
stand-alone version, 2-1
loading, 2-3
terminating, 2-7
used to copy magnetic tape, 2-6
used to copy RK07 disk, 2-6
Distribution kit, See VAX/VMS
software distribution kit
DSC-2, see Disk Save and Compress
Utility, stand-alone version
DXCOPY.COM command procedure, 3-14
Dump file, system,
altering the size of, 3-11

Command procedures,
DEFBOO.CMD, 3-11, 3-12
DXCOPY.COM, 3-14
SETDEFBOO.COM, 3-12, 5-8
SHUTDOWN.COM, 3-13
STARTUP.COM, 1-4
SWAPFILES.COM, 3-11
SYSTARTUP.COM, 1-4
UPGRADFIN.COM, 5-7, 5-8
VMSKITBLD.COM, 3-14
VMSUPDATE.COM, 1-6, 1-7, 5-5, 6-2
Completing the update, ~-3
Completing the upgrade, 5-7
Console drive, 1-2
Console floppy diskette, 3-2
copying files to and from, 3-14
Console, getting attention of, 3-2
Console subsystem, 1-2
CONTINUE command, 4-3
Conversational bootstrap, 3-2, 3-4

EDT, 1-7
ENABLE CHECKS command, 4-5
Entering commands to console
program, 3-2
Error messages, A-1
from BOOT, A-1
from SYSBOOT, A-2

F
Files of VAX/VMS system, B-1
in [SYSERR] directory, B-1
in [SYSEXE] directory, B-1, B-2
in [SYSHLP] directory, B-1, B-~
in [SYSHLP.EXAMPLES] directory,
B-2, B-12
in [SYSLIB] directory, B-1, B-~

Index-1

INDEX

Files of VAX/VMS system, (Cont.)
in [SYSMAINT] directory, B-1
in [SYSMGR] directory, B-1, B-7
in [SYSMSG] directory, B-1, B-7
in [SYSTEST] directory, B-2, B-8
in [SYSUPD] directory, B-2, B-11
Floppy diskette drive, 1-2
Freeing up space on system disk,
5-4

0
Optional software, 1-1
installing, 6-1
overview, 1-7
Overview of,
optional software installation,
1-7
system installation, 1-3
system update, 1-7
system upgrade, 1-6

HELP command, 4-6

Installing maintenance updates,
1-1, 1-7, 6-1, 6-3
Installing optional software, 1-1,
1-7, 6-1
Installing VAX/VMS, 1-1, 3-1
overview, 1-3
summary, 1-5
Interleaved memory, 3-12

PAGEFILE.SYS file, 3-11
Paging file, altering the size of,
3-11
Parameter files,
see System parameter file
Parameter values in DIGITAL
parameter files, 3-10
Preparing to bootstrap, 2-1
Preparing to update, 6-2
Preparing to upgrade, 5-4

R
Rebooting system,
stopping in SYSBOOT, 3-13
using default bootstrap, 3-13
Recording system parameter
values, 5-4
Restart, automatic, 3-12
RK07 kit, 2-2
RSX-llS update floppy, 1-7

L
Loading stand-alone DSC-2, 2-3
Logging in, 3-8

M
Magnetic tape kit, 2-1
Maintenance updates, 1-1
installing, 6-1
overview, 1-7
MINIMUM.PAR parameter file, 3-9,
3-10
Modifying system parameter files,
3-8, 5-8

N
Nonstop bootstrap, 3-2, 3-7

s
SETDEFBOO.COM command procedure,
3-12, 5-8
SET (PARAMETER VALUE) command,
4-7
SET (START-UP FILE) command, 4-8
SHOW command, 4-9
SHUTDOWN.COM command procedure,
3-13
Software distribution kits,
see VAX/VMS software distribution kits
Software installation, overview,
1-1
Source kit, VAX/VMS, D-1

Index-2

INDEX

Stand-alone DSC-2, see Disk Save
and Compress utility,
stand-alone version
STARTUP.COM command procedure,
1-4
Summary of,
system installation, 1-5, 3-1
system upgrade, 1-6, 5-1
SWAPFILES.COM command procedure,
3-11
SWAPFILES.SYS file, 3-11
Swapping file, altering the size of,
3-11
SYSBOOT commands,
CONTINUE, 4-3
DISABLE CHECKS, 4-4
ENABLE CHECKS, 4-5
HELP, 4-6
SET (PARAMETER VALUE), 4-7
SET (START-UP FILE), 4-8
SHOW, 4-9
USE, 4-12
SYSBOOT messages, A-1, A-2
BOOT messages, A-1
SYSBOOT program, 1-4, 3-4, 3-13,
4-1
command descriptions, 4-3
through 4-12
command summary, 4-1
invoking, 4-2
messages, A-1
terminating, 4-2
SYSDUMP.DMP file, 3-11
[SYSERR] directory, B-1
[SYSEXE] directory, B-1, B-2
SYSGEN utility, 1-4, 3-8, 5-4
[SYSHLP] directory, B-1, B-6
[SYSHLP.EXAMPLES] directory,
B-2, B-12
[SYSLIB] directory, B-1, B-6
[SYSMGR] directory, B-1, B-7
[SYSMSG] directory, B-1, B-7
SYSTARTUP.COM command procedure,
1-4
System bootstrap program,
see SYSBOOT program
System console block storage
device, 1-2
System dump file, altering the
size of, 3-11
System generation utility, 1-4,
3-8, 5-4
System parameter files, 1-5, 5-4
DIGITAL-supplied, 3-9
modifying, 3-8, 5-8
parameter values in, 3-10

System software,
installing, 1-1, 1-3, 3-1
updating, 1-1, 1-7, 6-1
upgrading, 1-1, 1-6, 5-1
[SYSTEST] directory, B-2, B-8
[SYSUPD] directory, B-2, 8-11

T
Tailoring system parameter files,
3-8, 5-8
Terminating stand-alone DSC-2,
2-7

u
Update distribution kits, n-1
Updating VAX/VMS, 1-1, 1-7, 6-1
Upgrade components in distribution kits, 5-2
in magnetic tape kit, 5-2
in RK07 kit, 5-3
UPGRADFIN.COM command procedure,
5-7, 5-8
Upgrading VAX/VMS, 1-1, 1-6, 5-1,
5-5
completion steps, 5-7
preliminary steps, 5-4
USE command, 4-12

v
VAX-11/780 console subsystem,
1-2
VAX/VMS
installing, 1-1, 1-3, 3-1
updating, 1-1, 1-7, 6-1
upgrading, 1-1, 1-6, 5-1
VAX/VMS software distribution
kits, 2-1
magnetic tape kit, 2-1
RK07 kit, 2-2
VAX/VMS source kit, D-1
VAX/VMS system disk, 3-14
building, 3-15
copying, 3-16
VIRT32MB.PAR parameter file, 3-9,
3-10
VMSKITBLD.COM command procedure,
3-14
VMSUPDATE.COM command procedure,
1-6, 1-7, 5-5, 6-2

Index-3