Digital PDFs

AA-DO25A-TE

August 1978

162 pages

Original

5.6MB

view download

OCR Version

5.0MB

view download

Document:	VAX/VMS Operator's Guide
Order Number:	AA-DO25A-TE
Revision:	0
Pages:	162
Original Filename:

OCR Text

August 1978
This manual contains descriptions of operating procedures and
commands that a system operator uses to keep the VAX/VMS

operating system running smoothly. This manual also contains

the messages produced by the Operator’s Communication Process

(OPCOM).

VAX/VMS
Operator’s Guide
Order No. AA-DO25A-TE

SUPERSESSION/UPDATE INFORMATION:

This is a new document for this release.

OPERATING SYSTEM AND VERSION:

VAX/VMS V01

SOFTWARE VERSION:

VAX/VMS V01

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

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 responsibilit;
for any errors that may appear in this 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 ¢
equipment that is not supplied by DIGITAL or its affiliated companie:

1978 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 pre:
paring future documentation.

The following are trademarks of Digital Equipment Corporation:

7/79-15

DIGITAL

DECsystem-10

DEC

DECtape

MASSBUS
OMNIBUS

PDP

DIBOL

0S/8

DECUS
UNIBUS
COMPUTER LABS

EDUSYSTEM
FLIP CHIP
FOCAL

PHA
RSTS
RSX

COMTEX
DDT
DECCOMM
ASSIST-11

INDAC
LAB-8
DECSYSTEM-~20
RTS~-8

TYPESET-8
TYPESET-11
TMS-11
ITPS~-10

VAX

VMS

SBI

DECnet

IAS

CONTENTS

PREFACE

CHAPTER
L]
=
[
L]
W N

PHEE
N

THE

.
N

OPERATOR

OPERATOR'S

TERMINAL

OPERATING PROCEDURES

HANDLING FILES

°*

VAX/VMS

DUTIES

OPERATOR PRIVILEGES

CHAPTER

INTRODUCTION

AND

VOLUMES

Operator Assistance
Single-Volume Tapes
Operator Assistance

in Handling Disks

and

in Handling Multivolume

Tapes

Operator Assistance

Hi=Oo0oJdOYO0
b
= o

e
s
«

L]
«

L]
.
N
>

.
L]

a Floppy Diskette
AND

from Disk

QUEUES

Merging Line Printer Queues
Preventing Loss of Data When Line Printer
out

Paper

Terminating a Batch Job
Terminating

a Print Job

CARD

READER

Operator Assistance
Deck
MONITORING

o
¢
@
¢

o
o

Restoring

TENDING THE

Mounting Public Disks
Backing Up the System Disk to Disk
Backing Up the System Disk to Tape
Restoring of the System Disk from Tape
Backing Up a Nonsystem Disk to Disk
Selective Back-up of Files
Backing Up a Floppy Diskette to Disk

Runs

in Processing

SYSTEM STATUS

AND

a Card

ACTIVITY

Printing the Error Log File
Printing the Operator's Log
SHUTTING DOWN AND

in Creating a Multivolume

Set

CONTROLLING BATCH

wWwN
N

DNDDNDNDDNDN
NN

NNNFERERRRRRR

NDNNN

Tape

File

RESTARTING THE

VAX/VMS

wWnN
=

o
.

o
o
¢

NNN

CHAPTER

Ul orn

OPERATING SYSTEM

Orderly Shutdown
Emergency

Restarting
COMMANDS
SUMMARY

the System
of

the System

USED BY
OF

Shutdown

OPERATORS

COMMANDS

ASSIGN/MERGE
ASSIGN/QUEUE
DEASSIGN/QUEUE
DELETE/QUEUE

iii

USED

OPERATORS

CONTENTS

(Cont.)

Page

CHAPTER

3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.13.1
3.13.2
3.13.3
3.13.4
3.13.5
3.13.6
3.13.7
3.14
3.15
3.16
3.17
3.18
3.19

INITIALIZE/QUEUE
MCR BAD
MCR DSC
MCR VFY
REPLY
RUN SYSSSYSTEM:INSTALL
RUN SYSS$SYSTEM:SYE
SET
SET ACCOUNTING
SET DEVICE
SET LOGINS
SET PRINTER
SET PROTECTION/DEVICE
SET TERMINAL/PERMANENT
SET UIC
SHOW TERMINAL/PERMANENT
START/QUEUE
STOP/ABORT
STOP/ENTRY
STOP/QUEUE
STOP/REQUEUE

3-9
3=12
3-14
3-18
3-21
3-27
3-31
3-33
3-34
3-36
3-38
3-39
3-41
3-44
3-51
3=-52
3-53
3-56
3-57
3-58
3-60

THE OPERATOR'S LOG FILE

4-1

4.1
4.2
4.3
4.4
4.5
4.6

OVERVIEW OF THE OPERATOR'S LOG FILE
INITIALIZATION MESSAGES
DEVICE STATUS MESSAGES
TERMINAL ENABLE AND DISABLE MESSAGES
TIME STAMP MESSAGES
USER REQUEST AND OPERATOR REPLY MESSAGES

4~-1
4-1
4-2
4-3
4-4
4~-4

QUALIFIERS APPENDED TO THE MCR VFY COMMAND

A-1

VALIDITY CHECK
File Error Reporting
Files Marked-for-Delete
Deletion of Multiply-Allocated Blocks

A-1
A-1
A-3
A-3

APPENDIX A
A.l
A.l.1l
A.l.2
A.l1.3

A.l.4
A.l.5
A.2
A.2.1
A.2.2
A.2.3
A.2.4
A.2.5
A.2.6
A.2.7
A.2.8

APPENDIX B

Elimination of Free Blocks
Recovering Lost Blocks
FILE QUALIFIERS
Delete Qualifier (/DE)
Free Qualifier (/FR)
List Qualifier (/LI)
Lost Qualifier (/LO)
Read Check Qualifier (/RC)
Rebuild Qualifier (/RE)
Update Qualifier (/UP)
Validity Check (Default)
ERROR MESSAGES

UTILITY
VAX/VMS

PRODUCED BY THE

(BAD)

A-4
A-4
A-4
A-4
A-4
A-5
A-5
A-5
A-6
A-6
A-7

BAD BLOCK

B-1

OPERATOR'S NOTES

INDEX

Index-1

CONTENTS

(Cont.)

Page

FIGURES

FIGURE

4-1
A-1

The Operator's Log File (OPERATOR.IOG)
VFY Listing Sample Using the /LI Qualifier

4-2
A-5

TABLES

TABLE

1-1

Operator Privileges

2-1

Error

2-2

Error Alarm Causes

3-1
3-2
3-3

Commands Used by Operators
Output Qualifiers
Input Qualifiers

Causes

and

1-2

Remedies
and

2-2

Remedies

2-34

3-1
3-15
3-16

3~-4

DSC~-Supported Devices

3-17

3-5
3-6

File Qualifiers
Keywords Appended

3-19

3-7

Qualifiers
Default Characteristics

the /DISABLE

and /ENABLE

for Terminals

3=-35
3-45

PREFACE

MANUAL

OBJECTIVES

The VAX/VMS Operator's Guide contains information that
the
day-to-day
operation
of
the
VAX/VMS
operating
objectives

are

is
wuseful
system.

in
Its

twofold:

To give
VAX/VMS

the reader an understanding
system operator

To gather in one volume
messages
that
pertain
VAX/VMS system

the

duties

the

the procedures, commands, and
system
specifically to the operation of the

INTENDED AUDIENCE

This guide is intended
for
operators
of
the
VAX/VMS
system,
for
persons
who
want
to become operators of the system, and for persons
who must periodically perform an operator's functions on the system.

STRUCTURE

THIS

DOCUMENT

This operator's guide

consists

four

chapters,

follows:

Chapter
and the

1 briefly describes the duties of the system
operator
relationship between the system and the operator.

Chapter

presents

Chapter

describes

the
the

commonly

used

commands

The
commands
in this chapter
Command Language User's Guide.

commonly

are

not

that

procedures.

used

included

are

operators.

in the VAX/VMS

Chapter 4 summarizes
operations.

In addition, a section has been included in the back
manual
for
operator's
notes.
There, the operator
down any procedure not documented in Chapter 2.

ASSOCIATED

the messages

operating

system

of
this
can write

DOCUMENTS

The VAX-11 Information Directory
provides
a
complete
VAX-11 documents, including a brief description of each.
For general background information about the VAX/VMS
VAX/VMS Primer and VAX/VMS Summary Description.

1list

system,

all

see

the

The

following

VAX/VMS

documents

also

VAX/VMS

VAX-11/RSX-11M User's Guide

VAX/VMS

Release

VAX-11

Software

VAX/VMS

System Manager's Guide

VAX/VMS

System Messages

VAX-11l

For hardware
User's Guide

CONVENTIONS

Command

may

Disk

Save

useful:

Language User's Guide

Notes

Installation Guide

and

Recovery Procedures

Compress

User's Guilde

operating instructions, refer to
(Order Number EK-UG780-UG-PRE).

USED

CTRL/X

THIS

Manual

the VAX-11/780

DOCUMENT

The

expression

"CTRL/x"

indicates

that

key
labeled
CTRL and another key
pressed
simultaneously.
For

CTRL/Y,
$

INITIALIZE/QUEUE

$ Queue:

LPAO:

START/QUEUE

LPBO:

CTRL/C,

the

should be
example,

CTRL/Z.

In
all
examples,
the
output
1lines
and
prompting characters printed or displayed by
the
system
are
in
black
ink;
all
user-entered commands are in red ink.
Vertical

data

Keyword, ...

Hardware

the

ellipses indicate that
system would display is

not

all
shown.

the

Horizontal ellipses indicate that additional
parameters,
values,
or
information can be
entered.

[queue-name]

Square
brackets
mean
that
the
expression
1is
optional.
(Square

are,

however, required syntax in the
the
SET
DEFAULT command,
CREATE/DIRECTORY command.)
command,

vii

enclosed
brackets

SET
and

UIC
the

CHAPTER 1
INTRODUCTION

For
the
most
intervention.

part,
the
VAX/VMS
system
runs
However, in many installations the

smoothly when

attended

1.1

DUTIES OF THE OPERATOR

one

without
operator
system may function

operators.

The VAX/VMS system operator is
responsible
for
keeping
the
system
running
smoothly
and
providing
the best possible service to system
users.
Typically,
therefore,
the
system
operator
performs
the
following

tasks:

Initializing

Backing

Carrying

Sending messages

Broadcasting

Controlling

<dControlling printer queues

Tending

line

printers

Tending

card

readers

Physically mounting magnetic
the

and mounting

critical

out

users

user

Monitoring

public

batch

and

volumes

specified
to

all

users
users

processing

own

the

files

requests

messages

who

system volumes

tapes

and

disks

the

reguest

responding

them

system

and

noting

emergencies

and

them

Printing
file

copies

Chapters 2 and 3 of this
used in performing these
To carry out
1.

their

Establish

the

operator's

guide describe
tasks.

tasks,
working

operators

log

the

file

procedures

the VAX/VMS

relationships

with

Interact with

the VAX/VMS

operating

system

the

error

and

wusers

1log

commands
:

system may have

other

system

and

to:
the

INTRODUCTION

Interact directly with
operating

system

the VAX-11/780

hardware

which

the

runs

The relationships
of
the
VAX/VMS
operator
with
wusers
and
their
programs
are
based
on two-way communication:
messages pass between
the operator and other users.
A record of these messages is displayed
or
in

The
are

printed on the operator's terminal;
the messages
the operator's log file for later reference.

are

also

entered

interactions between the operator and the VAX/VMS operating system
based
on the operator's ability to use the entire set of VAX/VMS

commands and on the operator's understanding of
the
system
messages
displayed
or printed on the operator's terminal.
The system messages

are entered
messages

that

the
pass

operator's
between

log

the

file

along

with

and

other

operator

the

record

the

users.

The direct
interactions
between
the
operator
and
the
VAX-11/780
hardware
are
based
mainly
on the operator's ability to operate and
maintain
the
peripheral
devices
that
the
system
supports.
For
detailed
1instructions
on
operating
and
maintaining the VAX-11/780
peripheral devices, see the VAX-11/780 Hardware User's Guide.

1.2

OPERATOR PRIVILEGES

In many ways,

operators of

the VAX/VMS

system are

different

from

other
users of the system.
However, operators are granted privileges
to perform functions that are
denied
to
most
other
wusers.
These
privileges
always
include
the
privilege
of
performing
operator
functions (the OPER privilege).
Table 1-1 summarizes
the
privileges
an operator needs to perform the procedures and commands documented in
this manual.
The system manager is responsible for granting these and
other privileges to the operator.

Table 1-1
Operator Privileges

Privilege
CMKRNL

GROUP

Service
To

execute

issue

Change

process

Mode

control

Kernel

system

service

services within

group

GRPNAM

insert

group

LOG_IO

issue

logical

CPER

execute

PHY IO

issue

PRMCEB

create

logical
I/0

operator

physical
or

the

name

table

event

flag

name

table

requests
functions

I/0

delete

names

requests

permanent

common

clusters

PRMMBX

create

permanent mailboxes

SYSNAM

insert

system

TMPMBX

create

temporary mailboxes

VOLPRO

To override

logical

volume

names

protection

1-2

the

INTRODUCTION

The VAX/VMS System Manager's Guide
and how to set up accounts for the

1.3

fully
describes
operators.

these

privileges

THE OPERATOR'S TERMINAL

Operators of the VAX/VMS system can perform many of their duties
from
ordinary
wusers'
terminals.
However,
one
of
the chief operator's
functions, communicating
with
other
users,
must
be
performed
at
terminals
that
have been defined as operators' terminals.
Operators
themselves can set up operators' terminals by use
of
the
privileged

command

REPLY/ENABLE

(described

in Chapter

3).

Still other
operating
functions
can
be
performed
only
from
VAX-11/780
system
console.
These
functions
include
booting
system, halting the system, and examining physical memory.

the
the

CHAPTER

VAX/VMS OPERATING PROCEDURES

This chapter describes the procedures commonly used
by
operators
the
VAX/VMS
operating
system.
The procedures documented cover
following subjects:

All

Handling

Controlling

batch

Tending

card

Monitoring

Shutting

these

files

the

and

system

down

procedures

and
are

volumes

queues

and

Chapter

queues

and

activity

reader
status

restarting

the

skeleton models

VAX/VMS
and

system
manager
or
the
system
operator
installation.
All the commands used in the

of
the

the VAX/VMS

Command

operating

should

system

tailored

the

to
fit
the
needs of the
procedures
are
described

Language

User's

Guide.

VAX/VMS OPERATING PROCEDURES

2.1

HANDLING

FILES

AND VOLUMES

At some installations, the attendance of a system operator is required
for users to gain access to or to create files.
Tape and disk volumes
must be properly mounted on devices and the files contained
on
these
volumes
must be regularly backed up.
The procedures described on the
following

pages

explain

how

mount

and

back

up volumes.

Mounting Volumes:
Mounting a volume involves placing
the
volume
on
the
specified device and performing the necessary start-up procedure.
On disk drives, the start-up procedure requires pressing the START
or
RUN button;
on tape drives, it requires pressing the LOAD button.

Generally, when the operator receives a request to mount a volume on a
device,
the request is sent by a user.
However, sometimes the system
sends a request to mount
a
volume.
This
occurs
when
a
user
is
accessing
a
tape and the tape reaches end-of-tape.
1If the tape is a
new tape, the operator must initialize it by use
of
the
/INITIALIZE
keyword.

For

example:

$ REPLY/TO=107

"PADOO9/INITIALIZE"

The
system
performs
a
protection
and
expiration
check
before
initializing
the volume.
1If, however, the tape has been processed by
a verifying machine, the operator must specify the /BLANK
keyword
to
prevent
the
processing
of
protection information on the tape.
For
example:

The

REPLY/TO=1560

system

already

After

"KGK01l5/BLANK"

initializes

the

tape

and

ignores

the protection

information

there.

the

operator

has mounted

the

volume,

message

may

displayed on the operator's terminal indicating that the volume is not
properly mounted.
Table
2-1
1lists
the
probable
causes
for
this
condition and the operator action required to remedy the situation.

Table

Error

Causes

2-1

and

Remedies

Cause

Corrective Action

The operator mounted
volume on the device

the wrong

The ONLINE (for tapes)
the READY (for disks)
indicator is not 1lit

Remove the volume and replace
it with the correct one
Press

illuminated,

wants

indicator

but

to write

the

user

LOAD button

Press the LOAD button
by the ONLINE button
Press

The WRITE-LOCK

the

Insert

the

RUN

START

the write-ring

followed

button

into

the

tape

tape
Push the WRITE-LOCK
OFF position
(continued

switch

the

page)

VAX/VMS OPERATING PROCEDURES

(Cont.)

2-1

Table

Error Causes and Remedies

Corrective Action

Cause

The operator did not
initialize the tape volume

Reissue the REPLY command
including the /INITIALIZE

The operator mounted a tape
processed by a verifying

Reissue the REPLY command
including the /BLANK
keyword

keyword

but did not specify

machine,

keyword

the /BLANK

Backing up a volume means copying the contents of
Backing Up Volumes:
The
the volume to another medium, for example, another disk or tape.
to prevent the
operator backs up volumes as a precautionary measure
loss or destruction of valuable information.

to
volume
from one
Three commands enable the operator to copy data
the Disk Save and Compress (DSC) command, the COPY command,
another:
specifies one of
The operator
and the File Transfer (FLX) command.
these commands depending upon the type of back-up to be performed.

this
The operator uses the DSC command to back up entire volumes;
command automatically copies all the blocks allocated to active files
onto the back-up, or scratch volume.

The DSC command has

two

forms:

The DSC1l command copies files contained on Files-11
and DSC2.
DSC1
contained
Structure Level 1 volumes and the DSC2 command copies files
Structure Level

on Files~11

2 volumes.

the
version of
There is also an entirely self-contained stand-alone
This version enables operators with one-disk systems to
DSC2 command.
The procedures for backing up
back up and restore their system disks.
restoring volumes on a one disk system are documented in Sections
and
2.1.5

and

2.1.6.

For more information on the DSC command,

see the VAX-11 Disk Save

and

Compress User's Guide.

one
from
files
selected
The operator uses the COPY command to copy
volume
onto
another
volume.
This command is fully described in the

VAX/VMS Command Language User's Guide.

Distributed with the VAX/VMS software
is
a
command
procedure
file
which
copies
and
restores
the
contents
of RT-11 formatted floppy
This command file uses the FLX command to perform the copy
diskettes.
file is described in
command
this
wusing
and
Invoking
operation,
Sections

2.1.10

and

2.1.11.

Typically, the system manager is responsible for setting up a schedule
for

backing

which the
contained

for putting

volumes
on

This schedule depends on the frequency at

volumes.

are

updated

these volumes.

this

schedule

and

the

importance

the

files

Then the system operator is responsible

into effect.

VAX/VMS OPERATING PROCEDURES

2.1.1

This

Operator

procedure

device.
When
a device, the
terminal:

Assistance

describes

how

Handling

to mount

a user requests a
following type of

OPCOM,

hh:mm:ss.cc,

OPCOM,

terminal-name:,

Disks

the

and

Single-Volume

specified

disk

specific disk or tape
message
appears
on

process-name

ACCNT=[blank]

Tapes

tape on

to be
the

mounted on
operator's

REPLY-ID=identification-number

"mount-message"

logging

out

the

first

volume

and

terminal.

Procedure

Locate

Ready

the

place

1Issue the following
been fulfilled:

the

command

the

specified

$
For
If

user

did

not

REPLY/TO=18

more
the

request

wuser

following

requests

drive,

button

the

it
or

is
the

request

has

device,

the

where

operator

the

tape

MOUNTED ON DMA3:"

the

device.

["message-text"]

specific

command,

wunattainable

operator

see
disk

can

Chapter
or

respond

tape,

wusing

the

command:

REPLY/ABORT=identification-number

If the operator needs time to locate
user has asked for, the operator can

that

a message indicating
For example:

"MYVOL

information

unavailable

indicating

REPLY/TO=identification-number

should
respond
with
disk has been mounted.

the device by pressing either the LOAD
a
magnetic
tape
drive,
or
the
RUN/STOP
START/STOP switch if it is a disk drive.

["message-text"]

the
disk
or
respond with:

REPLY/PENDING=identification-number

tape

the

["message-text"]

Examples
1.

OPCOM,

12:54:57.07,

OPCOM,

TTFl:,

REPLY/TO=29
OPCOM,

volume,
informs

"SYSFILE

01:03:43.90,

In the above
disk
volume

REYNOLDS

"MOUNT

ACCNT=

SYSFILE

MOUNTED ON
REQUEST

REPLY-ID=29

DBAl:"

COMPLETED,

OPERATOR=_OPAO:,

example,

named

ID=29

OPCOM alerts the operator to place
SYSFILE on DBAl.
The operator locates

places it on the device,
the user that the volume

readies
is ready

the
device,
for use.

the

the
then

VAX/VMS OPERATING PROCEDURES

OPCOM,

09:45:23.74,

OPCOM,

TTF3:,

REPLY/PENDING=4

REPLY/TO=4

LEBB

"MOUNT

"PLEASE

"MTAO:

ACCNT=

TESTER ON

WAIT

DOWN --

REPLY-~ID=4

MTAO:"

FEW MINUTES"
TESTER MOUNTED

$
OPCOM,

10:02:34.12,

REQUEST

COMPLETED,

MTA2:"

OPERATOR=

OPA(Q:,

In this example, OPCOM notifies
the
operator
that
a
wants
the
magnetic
tape
named TESTER placed on MTAQ.
operator issues a REPLY/PENDING command to indicate that
task

can

mounts

the

tape

done,

magnetic

volume

but

not

tape

MTA2.

immediately.
MTA2

and

Later,

notifies

the

ID=4

user
The
the

operator

wuser

that

VAX/VMS OPERATING PROCEDURES

2.1.2

Operator Assistance

in Handling Multivolume Tapes

This procedure describes how to mount tapes,
in

a multivolume

tape

previously

initialized,

set.

When a user is in the process of reading or writing to a tape and
the
tape
reaches
end-of-tape, the system suspends processing and sends a
The user does not see
- next tape.
request to the operator to mount the
this
message
and
may
not
realize
that
another tape is needed to
complete the read or write operation.

sent by the system, appears on the system console and all

The message,

terminals designated to receive tape messages,
OPCOM, hh:mm:ss.cc, process-name
OPCOM,

MOUNT RELATIVE VOLUME x

ACCNT=[blank]

(label-name)

as follows:

REPLY-ID=identification-number

ON device-name:

The process name identifies the user.
This name is
either
the
name
under
which
the
wuser
1logged
1into
the
system
or the name of the
terminal at which the user is logged in.
The process name is the name
of a terminal when the user logs into a second terminal before logging
out on

the

first

The variable,
parentheses

terminal.

indicates the volume number.

indicates

the volume

label of

The

the

tape.

name

within

the

Procedure

ready
Locate the tape, place it on the specified device, and
the
device
by
pressing the LOAD button.
1If the drive does
not come online automatically,

press the ONLINE button.

Enter the following command, which indicates that the request
has

been

fulfilled:

$ REPLY/TO=identification~number

["message-text"]

See Chapter 3 for more information on the REPLY command.
Example

ACCNT=

OPCOM, 14:24:07.53, TURNER
OPCOM,

MOUNT RELATIVE VOLUME 2

$ REPLY/TO=4
$
OPCOM, 14:31:43.71,

(GMB002)

REQUEST COMPLETED,

REPLY-ID=4
ON MTAl:

OPERATOR= OPAQO:,

ID=4

In this example, a user is reading or writing
to
the
first
tape
in
the
volume
set
GMB002.
The first OPCOM message
indicates

that

the

user

needs

the

second volume of

the

tape

set.
After
mounting
1it,
the
operator
1issues
the REPLY
command to indicate that the tape has been
mounted
and
the
system
can
resume
processing.
The
second
OPCOM message
confirms that the operator's message has
been
sent
to
the
facility handling

tapes.

2-6

VAX/VMS OPERATING PROCEDURES

2.1.3

Operator Assistance

in Creating a Multivolume Tape Set

This procedure describes how
multivolume

tape

initialize

additional

tapes

set.

When a user is in the process of
writing
to
a
tape
and
the
tape
reaches
end-of-tape,
the
system
suspends
processing and sends the
operator a request to mount the next tape.
The user does not see this
message
and may not realize that another tape is required to complete
the write operation.
The message displayed on the system console
and
all terminals designated to receive tape messages is as follows:
OPCOM,
OPCOM,

hh:mm:ss.cc, process-name
MOUNT RELATIVE VOLUME x ()

ACCNT=[blank]
ON device-name:

REPLY-ID=identification-number

The process name identifies the user.
This name is
either
the
name
under
which
the
wuser
1logged
into
the
system
or the name of the
terminal at which the user is logged in.
The process name is the name
of a terminal when the user logs into a second terminal before logging
out on the first terminal.
The variable, x, indicates the
relative
volume
number.
The
empty
parentheses
(that is, a left parenthesis followed directly by a right
parenthesis) indicate that the volume label is
not
known.
Usually,
this
message
indicates
that
a new tape volume must be initialized.
Normally, when a user needs another tape and the tape has already been
initialized, the volume label is included between the parentheses.
Procedure

If the user did not previously
tell
the
operator
that
an
additional
tape
may
be needed and what the volume label of
the tape should be, the operator should try
to
contact
the
user

and

obtain
the

the

user

following

really want

information:

Does

If the user wants another tape, what is the
with which the tape should be initialized?

Enter the following
tape or if the user

another

tape?

command if the user does
cannot be contacted:

S REPLY/ABORT=identification-number

volume

not want

1label

another

["message—-text"]

NOTE

Steps 3,
the

Aborting

operator

the

See Chapter

and 5

request

for

below are

aborts

also

the

ignored

user

aborts

1if

request.

the

information on

user's program.

the

Write a visual label on the tape volume
label and the relative volume number.

4.,

Place the
pressing

command.

specifying

the volume

tape on the specified drive and ready the device by
the LOAD button.
If the drive does not come online

automatically,

press

the

ONLINE

button.

VAX/VMS OPERATING PROCEDURES

1Issue the following command, which initializes the
tape
informs the system that the request has been fulfilled:
$ REPLY/TO=identification-number

and

"volume-label/INITIALIZE"

Examples
1.

OPCOM,

14:16:24.98,

OPCOM,

MOUNT RELATIVE VOLUME 2

$ REPLY/TO=6

OPCOM,

HAUSER

ACCNT=

()

REPLY-ID=6

ON MTAl:

"GMB00O4/INITIALIZE"

14:23:36.10,

REQUEST

COMPLETED,

OPERATOR=_OPA0O:,ID=6

In this example, the OPCOM message notifies the operator that
a
user
needs
a
second tape.
After mounting the tape, the
operator issues the REPLY command to
indicate
the
tape
is
mounted.
The volume label GMB004 is assigned to the tape by
means of the /INITIALIZE keyword.
The second
OPCOM
message

confirms
facility.
2.

OPCOM,

that

the

request has

been

12:56:03.76, RYAN
ACCNT=
MOUNT RELATIVE VOLUME 3 ()

sent

the

tape

handling

REPLY-ID=15

MTAl:

$ REPLY/ABORT=15

OPCOM,

13:03:12.42,

REQUEST

ABORTED,

OPERATOR= OPA(:,ID=15

The first OPCOM message indicates that the user needs another
tape
and
the
tape must be initialized.
Upon notifying the
user, the operator discovers that
the
wuser
does
not
want
another
tape.
Hence, the operator cancels the request using
the REPLY/ABORT command.

VAX/VMS OPERATING PROCEDURES

2.1.4

Mounting

Public Disks

This procedure describes how to mount a disk as a public volume.
Public volumes are volumes that contain more than
one
users'
files.
These
volumes
must
be
designated as shareable at the time they are

mounted

they can be

accessed by all

system users.

Procedure

Allocate a drive by issuing
$

the

following command:

ALLOCATE device-name:

Locate the volume and place it on the allocated drive.

Ready the device by pressing the

Issue

RUN/STOP

button.

STOP/START

the MOUNT/SYSTEM command to allow all

the data

the

device:

MOUNT/SYSTEM

device-name:

switch
users

access

the
to

volume-label

NOTE

To
use
operator

the
/SYSTEM
qualifier,
needs the SYSNAM privilege.

The volume label

should be affixed

the

outside

the

volume.

Optionally,

inform all users on the system that the volume is

now available

for

use:

REPLY/USERS/BELL

"message-text"

Example

ALLOCATE
_DBB2:

DBB2:
ALLOCATED

$ MOUNT/SYSTEM DBB2:
USERFILES
$MOUNT-I-MOUNTED,
USERFILES
mounted on DBB2:
$ REPLY/USERS/BELL "PUBLIC VOLUME MOUNTED ON DBB2:"

The ALLOCATE COMMAND requests the allocation
of
DBB2;
the
response
from
ALLOCATE indicates that DBB2 was successfully
allocated.
The MOUNT/SYSTEM command makes the
disk
mounted
on
DBB2
available to all users.
The MOUNT command response
indicates
that
the
disk
was
successfully
mounted.
The
REPLY/USERS/BELL command broadcasts a message to all users on
the system that the disk mounted on DBB2 can be accessed.

VAX/VMS OPERATING PROCEDURES

2.1.5

Backing

This procedure
the
been

contents
booted.

follow
copies

the

describes how

closed

are

the

Disk

Save

and

Compress

of the system disk to another disk
1If the system is a one~-disk system,

the
procedure
the contents of

When backing
logged
into

System Disk

described
in
the system disk

after
the

utility

Section
2.1.6.
This
to magnetic tape.

up the system disk, the operator must be
the
the system.
This ensures that all the files

closed

and

that

the

copy

operation

copies

the system has
operator
must

can

procedure

only
user
that can be

performed

successfully.

perform

files

this

the

procedure,

the

operator

needs

read

access

all

the

1issuing

the

disk.

Procedure

Inform all users to
following command:

REPLY/ALL/BELL

This message
2.

Set

the

$
3.

after

logged

out

only

aborted

include

when

typing:

prescribed

typing

the

why

log

out.

time,

that

all

the

users

have

command:

copy

that

should

OPERATOR,

running

JOB_CONTROL,

operation.

All

other

and

the

are:

NULL,

process

processes

should

that

typing:

disk

drive

typing:

device-name:

scratch

disk

MOUNT/FOREIGN

and
ready
that
RUN/STOP button.

typing:

device-name:

Run

the Bad Block
(BAD)
wutility
entering the following command:

and

scratch disk in the allocated drive
by pressing the START/STOP switch or

the

ALLOCATE
a

Mount

system

STOP/IDENTIFICATION=process-id

the

Allocate

device

ERRFMT,

performs

Place

the

"message-text"

processes

SWAPPER,

count

SHOW SYSTEM

should

out

SET LOGINS/INTERACTIVE=0

Check,

The

log

the

scratch

MCR BAD device-name:
NOTE

Make
<certain
that
the
disk
analyzed
by BAD is the scratch
not the system disk.
When BAD
a
disk,
it
destroys
all the
data

recorded

the

disk.

disk

and

analyzes
previous

disk

VAX/VMS OPERATING PROCEDURES

BAD

analyzes

displays,

the

upon

integrity

completion,

the

blocks

number

Copy the files on the system disk
typing the following command.

MCR DSC2

the

disk

faulty blocks

the

output-device-name:/VE =

scratch

and

found.

disk

input-device-name:

NOTE

Make

certain

the
scratch
disk.
When

that

the

disk
DSC

output

device

1is

and
not
the source
copies
data
to
the

output
device,
it
destroys
all
previous data recorded on that disk.

DSC copies the files to
contents of both disks.

Run DMP
the

DSC

following

returns

the

scratch disk,

the

then

compares

any verification messages

the

entering

command:

MCR DMP SYSSOUTPUT = device-name:/FI:m:n/HD

NOTE

The variables m and n
identification number
verification

refer to the
indicated in

message.

This command displays the
identification
number.

file name associated
If
the
file
name

ACCOUNTNG.DAT,

JBCSYSQUE.DAT,

SWAPFILE.SYS,
usually can be

the
verification
message
ignored;
if the file name

make
sure
all
the
wusers
back-up procedure again.
10.

file
DSC's

Dismount and

deallocate

OPERATOR.LOG,

are

the

1logged

scratch disk

with the
file
1is ERRLOG.SYS,

PAGEFILE.SYS,

1is
1legitimate and
is any other
file,
out

and

perform

the

typing:

$ DISMOUNT device-name:
S DEALLOCATE device-name:
11.

Remove
label

12.

Return

$§
13.

the
to

Inform

the

scratch

disk

specifying

count

from
the

the

volume

its

drive
label

original

and

affix

and

current

state

visual

date.

typing:

SET LOGINS/INTERACTIVE=n
all

users

that

REPLY/ALL/BELL

the

system

"message-text"

back

normal

typing:

VAX/VMS OPERATING PROCEDURES

Example

REPLY/ALL/BELL

"PLEASE

LOG OUT --

_OPAO:,SYSTEM 22:49:52.89
"PLEASE LOG OUT -- SYSTEM DISK WILL

REPLY/ALL/BELL

_OPAO:,SYSTEM

"IN
$

SET

"IN

SYSTEM DISK WILL

BACKED UP

MIN."

22:49:52.89

MIN."
LOGINS/INTERACTIVE=(0

Interactive limit=0,

Processes on
Process Name
UIC
NULL
000,000
SWAPPER
000,000
ERRFMT
001,006

0001003cC

OPERATOR

001,004

0001003D
0001003E
0002003F

JOB_CONTROL
DMAOACP
SYSTEM

001,004
001,003
001,004

Current

interactive value=15

18-JUL-1978 22:50:15.54
State Pri Dir. I/0
CPU
Page
COM
0
0 00:10:14.03
HIB
16
0 00:00:00.41
HIB
7
5 00:00:00.17

LEF

HIB
HIB
CUR

13
9
5

2 00:00:00.08

74
103
4

00:00:00.83
00:00:01.14
00:00:00.45

flts Ph.Mem
0
0
0
0
26
29

31
30
119

61
78
92

ALLOCATE DMAl:

_DMAl:

ALLOCATED

$ MOUNT/FOREIGN DMAl:
$MOUNT-I-MOUNTED,

MCR BAD DMl:

MCR DSC2

BAD
DSC

TOTAL NO.
45

BAD

DMAl:/VE =
STARTING

mounted
BLOCKS

on _DMAl:

DMAO:

VERIFY

PASS

DSC -- *WARNING* 42 VERIFICATION ERROR ON DMl:
FILE ID 000503,000001,000000 VBN 000000,000001
$

MCR DMP SYS$OUTPUT =

pump of

DMO:[SYSERR].

ERRLOG.SYS;1

$
$
$
$

DMAO:/FI:503:1/HD
-

FILE

(503,001)

503,001,00

2./2.

File

08-JUN-78

Header

09:55

DISMOUNT DMAl:
DEALLOCATE DMAl:
SET LOGINS/INTERACTIVE=25
REPLY/ALL/BELL "DMAO:
RACK-UP IS COMPLETE"

_OPAO:,SYSTEM 23:07.33.09
"DMAO:
BACK-UP IS COMPLETE"

In this example, the operator performs the preliminary
steps
of ensuring that no users are logged into the system and that
BAD has been run on the scratch disk.
The operator then uses the
MCR
DSC2
command
to
copy
the
contents
of
the
system
aisk to the scratch disk.
The /VE
gualifier requests that after the copy operation is complete,
the
contents
of both disks be checked against each other to
verify that the copy operation was
successful.
During
the
verification
pass,
DSC
finds
a file that was not properly

VAX/VMS OPERATING PROCEDURES

copied.
To determine the file name, the operator issues
the
MCR
DMP command;
the parameter SYSSOUTPUT requests that the
information be displayed on
the
operator's
terminal.
The
file
name
associated
with
the
file identification number

1its
<closes,
Because this file never
503:001 is ERRLOG.SYS.
contents
are always changing, making it impossible to create
an exact copy of
can be

it.

Consequently,

the verification

message

ignored.

To complete the back-up procedure, the operator dismounts and
scratch disk and informs all users that the
the
deallocates
system disk

is operational

again.

VAX/VMS OPERATING PROCEDURES

2.1.6

This

Backing

procedure

the

uses

System

the

Disk

Tape

stand-alone

version

the

Disk

Save

and

Compress utility to copy the contents of the system disk onto magnetic
tapes for retention.
To restore the contents of the tape to disk, the
operator uses the procedure described in Section 2.1.7.
To perform this procedure,
on the system disk.
This procedure must

the

operator

performed

from

needs

the

read

system

access

all

files

console.

Procedure

Run the SHUTDOWN procedure as described

Write-protect the system disk
switch, on the disk drive, to

Place a magnetic tape on an available
drive
and
ready
device.
If
there
1is
more
than one tape drive, mount
ready additional magnetic tapes on each available drive.

the
and

Load the diagnostic floppy diskette
console floppy drive.

into

the

Turn
the
processor

the

Turn the DC ON/OFF switch on the LSI-11 control panel to
OFF
position.
The
LSI-11
control panel is located on
bottom left side of the VAX-11/780 CPU cabinet.

Return the
initiates
console

by
turning
the
the ON position.

labeled

AUTO-RESTART
switch
on
the
cabinet to the ON position.

DC
a

ON/OFF
switch
system
restart

in Section 2.5.1.

to
as

ZZ-ESZCC

top

the
ON
indicated

WRITE-PROTECT

front

the
the

position.
This
by the following

message:

CPU

HALTED,SOMM CLEAR,STEP=NONE,CLOCK=NORM
RAD=HEX ,ADD=PHYS ,DAT=LONG,FILL=00,REL=00000000
INIT

SEQ

HALTED

DONE

00000000

(RELOADING
LOAD

VER:

DONE,

WCS)
00003200

PCS=01

BYTES

WCS=03-10

LOADED

FPLA=03

CON=PX03-08

(AUTO-RESTART)
CPU

HALTED

INIT

SEQ

DONE

The console then loads the
approximately 1.5 minutes.
following
LOAD

message
DONE,

VAX/VMS
DSC>

displayed

00020400

DSC2,

stand-alone
system,
which
takes
At the completion of loading, the

A.l1

BYTES

the

LOADED

30-MAY-78

system

console:

VAX/VMS OPERATING PROCEDURES

A copy of the VAX-11
Disk
Save
and
Compress
utility
for
structure
level 2 disks (DSC2 utility) is now running.
Type
the DSC command appropriate for the system disk and the
kind
of
back
up
needed.
The following commands are examples of
different
DSC>

types

back-ups:

MTAO:/RW/DENS=1600/VE

DBAO:

The above command copies the contents of the disk mounted
on
The /RW qualifier causes
the tape mounted on MTAO0.
to
DBA0
operation
copy
the
before
rewound
be
the output tape to
begins.
The
/DENS=1600 qualifier requests that the data be
copied to the tape at 1600 bits per inch.
The /VE
qualifier
regquests
that
the contents of the tape be compared with the
contents of the disk to make certain the copy
operation
was
successful.

DSC>

MTAQ:,MTAl:/RW/VE

DBAO:

In this example, DSC copies the contents of the disk
mounted
on
DBAQ
to
the
output
devices
MTA0
and MTAl.
When DSC
finishes copying data to the first tape,
MTAO,
it
overlaps
writing
data
to
the
second
tape with rewinding the first
tape, thus quickening the copy operation.
Because no density
at
which the data should be copied to the tape is indicated,

qualifier
The /VE
DSC copies the data at 800 bits per inch.
requests
that
the contents of the tape be compared with the
contents of the disk to make certain the copy

operation

was

Guide

DSC

successful.

See the VAX-11l Disk Save and Compress
returns

10.

any verification messages.

User's

1if

the
Label each magnetic tape with the following information:
disk backed up, the current date, the
the
of
1label
volume
relative
the
and
recorded,
density at which the data was
volume

number.

2-15

VAX/VMS OPERATING PROCEDURES

2.1.7

Restoring

This procedure
to
disk.
To
commands

from

the

System Disk

describes
perform
the

system

from Tape

how to copy the contents of a
this
procedure,
the operator

magnetic
tape
must enter the

console.

Procedure

Shut

Place a scratch disk in an
available
device by pressing the RUN/STOP button

down the system by
Section 2.5.1.

Place

the magnetic

on
tape
drive
0.
more than one tape,
tape drives.

following

the

procedure

documented

drive
and
ready
the
or START/STOP switch.

tape which contains the
restoration
data
If the restoration material is stored on
place the additional tapes on
additional

Load the diagnostic floppy
console floppy drive.

diskette

labeled

Turn the AUTO-RESTART switch located on
processor cabinet to the ON position.

into

the

Turn the DC ON/OFF switch on the LSI-11 control panel to

the

Return the
initiates

the

ZZ-ESZCC

top

front

OFF
position.
The
LSI-11
control panel is located
bottom left side of the VAX-11/780 CPU cabinet.
DC

ON/OFF

a
system
console message:
CPU

HALTED,SOMM

switch
restart

the

indicated

the

position.
This
the following

CLEAR,STEP=NONE ,CLOCK=NORM

RAD=HEX ,ADD=PHYS .DAT=LONG,FILL=00,REL=0000000
INIT

SEQ

DONE

(RELOADING
LOAD DONE,

VER:

WCS)
00003200

PCS=01

BYTES

WCS=03-10

LOADED

FPLA=03

CON=PX03-08

(AUTO-RESTART)
CPU

HALTED

INIT

SEQ

DONE

The console then loads the
approximately 1.5 minutes.
following
LOAD

message
DONE,

displayed

00020400

VAX/VMS DSC2,

stand-alone
system,
which
takes
At the completion of loading, the

BYTES

VERSION A.l1

the

system

console:

LOADED

30-MAY-1978

DSC>

A copy of the VAX-1ll
Disk
Save
and
Compress
utility
for
structure
level
2
volumes
(DSC2
wutility) is now running.
Type the DSC command appropriate for the restorations
system
disk
and
the
kind
of
restoration desired.
The following
commands are examples of different types of restorations:
DSC>

DBAO:/VE

=MTAO:/RW

This command copies the contents of the tape mounted on
MTAQ
to
the
disk
mounted on DBAO.
The /RW qualifier causes the

VAX/VMS OPERATING PROCEDURES

tape to be rewound before the copy operation is
started
and
the
/VE qualifier requests that the contents of the tape and
disk be compared to
make
certain
the
copy
operation
was
successful.

DSC> DBAQ:/VE = MTAO:,MTAl:/RW
In this example, DSC copies the contents of the tapes mounted
on
MTAQ0
and
MTAl
to the disk mounted on DBAO.
First, DSC
copies the contents of the tape mounted on
MTAOQ.
When
all
the
data on the tape has been copied, DSC begins to copy the
contents of the second tape.
The /RW
gualifier
causes
the
first
tape
to
be
rewound
prior
to
starting
the
copy
operation.
The /VE qualifier requests that
DSC
performs
a
verification
pass
after
each
volume
reaches end-of-tape.
When the verify pass reaches end-of-tape, the copy
operation
continues.

See

the VAX-11 Disk Save

returns
10.

and

Compress

User's

Guide

1if

DSC

verification message.

Label the disk with the following information:
the
name
of
the
tape
the restoration was performed from and the current
date.

VAX/VMS OPERATING PROCEDURES

2.1.8

Backing

a Nonsystem

Disk

This procedure describes how to copy the
to
another
disk.
A nonsystem disk is
mounted by use of the /SYSTEM qualifier.

contents

disk,

public

nonsystem

This procedure is performed online.
The operator need
the
device which restrains system users from changing
disk.
They can, however, still read data.

which

only

disk

has

been

write-lock

the

data on

the

users

that

the

Procedure

1Issue the
specified
copied to

following
command
to
warn
disk
will
be write-locked
another disk:

REPLY/ALL/BELL

This message
write-locked
2.

should include the name
and when the write-lock

switch

located
a drive

S ALLOCATE

the

front

for

the

scratch disk

Place a scratch disk
device
by
pressing
switch.

Mount

$
6.

scratch

Issue the following
of the source disk:

panel

disk

being

the

disk

drive.

typing:

issuing

the

following

ready
the
START/STOP

command:

device-name:
command

f£ind

out

the

structure

1level

DIRECTORY device-name:[0,0]

If the directory
level 2 volume;
7.

the
source
disk
by
the ON position.
This

in the allocated
drive
and
the
RUN/STOP
button or the

disk

MOUNT/FOREIGN

can

device-name:

the

contents

of the source
will occur.

prescribed time,
write-lock
the
WRITE-PROTECT switch to

Allocate

its

"message-text"

After the
pressing

all

listing is
otherwise,

alphabetized,

it is
a
structure
structure level 1.

Run

the appropriate VAX-1l1l Disk Save and
typing one of the following commands:

Compress

utility

MCR DSC1

output-device-name:/VE

input-device-name:

$§

MCR DSC2

output-device-name:/VE

input-device-name:

NOTE

Make

certain

that

the

output

device

the
scratch
disk
and
not
the source
disk.
When
DSC
copies
data
to
the
output
device,
it
destroys
all
the

See

returns

the

any

data

VAX-11

recorded

Disk

Save

verification

and

errors.

that

disk.

Compress

User's

Guide

DSC

VAX/VMS OPERATING PROCEDURES

Dismount and deallocate the scratch disk by typing:
S DISMOUNT device-name:
$ DEALLOCATE device-name:

10.

Remove the scratch disk from the drive and affix a

11.

Write-—-enable the source disk, by pressing

12.

it,

label

specifying the volume label and current date.

switch to

Inform

the

WRITE-PROTECT

the OFF position.

all

that

wusers

the

source

disk

write-locked by issuing the following command:

longer

$ REPLY/ALL/BELL "message-text"
Example

$ REPLY/ALL/BELL "DMAO:

19:36:11.70

_OPAO: ,SYSTEM

"DMAO:

WILL BE WRITE-LOCKED IN 5 MIN FOR BACK-UP."

$ ALLOCATE DM:
DMAl:

ALLOCATED

$ MOUNT/FOREIGN DMAl:

mounted on DMAl:

$MOUNT-I-MOUNTED,
$ DIRECTORY DMAQO:[0,0]

DIRECTORY DM0:[0,0]
19:45
20-JUL-78

000000.DIR;1
001001.DIR;1
001002.DIR;1
001004.DIR;1
001005.DIR;1
001006 .DIR;1
001007.DIR;1
001010.DIR;1
001020.DIR;1
001040.DIR;1

BACKUP.SYS;1
BADBLK.SYS;1
BADLOG.SYS;1
BITMAP.SYS;1
CONTIN.SYS;1
CORIMG.SYS;1
INDEXF.SYS;1
SYSERR.DIR;1
SYSEXE.DIR;1
SYSHLP.DIR;1
SYSLIB.DIR;1
SYSMAN.DIR;1
SYSMGR.DIR;1
SYSTST.DIR;1
SYSUPD.DIR;1
VOLSET.DIR;1

2
4

C
C
C

4 .

1 .

9 .
1
1 .
7 .

C
c

2 22.

0 O.

O.
5 5.
0
0 O.

3 349.

7 7.

C
C

1 1.

4 4.

4 .
1 .
1 .
9 .

1 .
0

TOTAL OF 436./1132.

20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78

19:45
19:45
19:45
19:45

20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78

19:45
19:45
19:45
19:45
19:45
19:45
19:45
19:45

20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78

19:45
19:45
19:45
19:45
19:45
19:45
19:45
19:45

20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78
20-JUL-78

19:45
19:45
19:45
19:45
19:45
19:45

BLOCKS

26.

FILES

VAX/VMS OPERATING

MCR

DSC

DSC2

DMAl:/VE
STARTING

DISMOUNT

DEALLOCATE

REPLY/ALL/BELL

this

DMAO

write-locking

The

"DMAO:

operator

the

DSC2

contents
~-hsure

the

the
of

both

disks

the

copy

operator

when

the

sign

operation

was

operator

write-enables
written to.

The

and

necessary

the

this

the

order,
2 disk.

which

operation

/VE

using

the

other

DSC

that

the

users

the

that

informs

completion,

indicating

all

indicates

each

successful.

begins.

case,

requests

against

deallocates

informs

the

disk.

determine

was

pass

performs

copy

appears

that

After

checked

verify

users

purposes.

disk.

qualifier

operation

dismounts

DMAO,

the

system

command

source

prompt
(§)
successful.
then

scratch

DIRECTORY

performs

all

back-up

in alphabetical
structure level

command.
of

informs

for

operator

the

that

dollar

The

then

the

ready

types

1level

operator

LONGER WRITE~LOCKED"

operator

disk,

and

directory listing is
that the volume is a

MCR

write-locked
the

mount

structure

The

PASS

DMAl:

example,

DMAO:

VERIFY

DMAl:

will

steps

PROCEDURES

the

scratch

the

DMAO

the

copy

disk,

can

VAX/VMS OPERATING PROCEDURES

2.1.9

Selective Back-up of Files

This procedure describes how to copy selected files from one
disk
to
another.
Generally,
1if
files
must
be
backed
up
regularly, the
operator should create a command procedure that contains the
required
back-up
commands.
Then,
the operator need only specify the execute
command (@) before the command procedure file
specification
and
the
system will begin processing

the commands

in the command procedure.

Procedure

Allocate a drive in which the back-up

volume

1is

placed

typing:-

ALLOCATE device-name:

Place the back-up volume 1in che
that

device

START/STOP

pressing

allocated

either

drive

and

ready

the RUN/STOP button or

the

switch.

Mount the back-up volume by typing:
$

MOUNT device-name:

volume-label

NOTE

been
not
has
volume
back-up
the
If
be
must
it
initialized,
previously
initialized before
it
is
mounted
and
processed by the Bad Block (BAD) utility
after

is mounted.

the

which

Allocate a drive in

source

disk

1is

placed

typing:

ALLOCATE device-name:

Place the source disk in the allocated drive and
ready
that
device
by
pressing
the
RUN/STOP
button or the START/STOP
switch.

Mount the
$

source disk by typing:

MOUNT device-name:

volume-label

Create directories on the back-up volume by typing:
$ CREATE/DIRECTORY device-name:[directory]
Generally,
user

the operator creates a separate directory for

who has

files

be backed

up.

Copy the files from the source disk to the back-up volume
typing

the

$ COPY

each

following command:

input-device:[directory]filename.type.ver

output-device:[directory]

This command is repeated tor each file to be
copied.
If
a
user
has
several
files
of
the
same
file name, type, or
version, the operator can use
wild
cards
(*)
to
indicate
them.

VAX/VMS OPERATING PROCEDURES

Dismount

and

deallocate

the

back-up volume

typing:

S DISMOUNT device-name:
$ DEALLOCATE device-name:
10.

Remove

11.

the

back-up

specifying

Dismount

and

volume

the

from

volume

deallocate

the

label

the

device

and

source

and

affix

current

date.

disk

label

typing:

$ DISMOUNT device-name:
$ DEALLOCATE device-name:
12.

Remove

the

source

disk

from

the

device.

Example

$ ALLOCATE DMAOQ:
_DMAO:

ALLOCATED

$ MOUNT DMAQ:

MYVOLUME

$MOUNT-I-MOUNTED,

MYVOLUME

mounted

$ ALLOCATE DMAl]:
_DMAl:

on _DMAQ:

ALLOCATED

$ MOUNT DMAl:

DATCOM

3MOUNT-I-MOUNTED,

DATCOM

mounted

$ CREATE/DIRECTORY DMAO: [RMSTST]

on DMAl:

$ CREATE/DIRECTORY DMAO: [FORMAR]
$ CREATE/DIRECTORY DMAO: [SYSTEM]

$ COPY DMAl:[RMSTST]
*.*
$ COPY

DMA
: [RMSTST]
O

DMAl: [FORMAB]*.COM

DMA
: [ FORMAB]
Q

g COPY DMAl:[SYSTEM]DUNGEON.
*
DISMOUNT

$
$

DEALLOCATE

DISMOUNT

this

DMAO:

DMAl:

DEALLOCATE

DMAl:

example,

the

directories

DMAO.

performing

After

ready

three

the

DMAl

source

directories

back-up
copies:
e

DMAQ: [SYSTEM]

DMAO:

and

the

source

three

the

back-up

the

[RMSTST]

All

the

files

directory
directory
®

All

the

files

[SYSTEM]
[SYSTEM]

the

Upon

completion

deallocates

the

type

the

copy

source

file

on
the

the

operator

the

back-up

the

[FORMAB]

the

[FORMAB]

DUNGEON

the
source
disk
back-up volume.

the

operation,

and

name

the

on
and

creates

directory

COM

three

mount

operator

directory

source
disk
back-up volume

with

[SYSTEM]

[RMSTST]

file

from

directories

command,

the

directory
directory on

and

the

and

COPY

volume
¢

steps

volumes,

the

files

created

[FORMAB],

wusing

files
disk

copies

newly

necessary

[RMSTST],

volume.

All

operator

back-up

the

operator

volumes.

dismounts

VAX/VMS OPERATING PROCEDURES

2.1.10

Backing Up a Floppy Diskette

to Disk

This procedure describes how to copy the contents of a floppy diskette
to disk

for

retention.

Procedure

Create an empty directory
following

$ CREATE/DIRECTORY

back-up

volume

using

the

device-name: [directory]

be
to
diskette
1Insert, into the console device, the floppy
the floppy diskette is already inserted and
If
up.
backed
mounted, the operator must dismount it by typing:
S DISMOUNT

command:

the

Enter

console-device:

following

command:

S @[SYSUPD] CONSCOPY

This command executes the command procedure
CONSCOPY,
which
This command procedure
directory [SYSUPD].
the
1in
resides
steps the operator through the back-up procedure.

Supply the information reguested in the following questions:
WHAT IS THE FILES-11 DEVICE AND DIRECTORY
WHAT IS THE NAME OF THE CONSOLE DEVICE

(DDCU:[DIRECTORY]):

(DDCU:):

The first question asks for the device and directory to which
the
floppy
diskette will be backed up;
the second question
diskette
asks for the name of the device in which the floppy
is

inserted.

Answer

"Y"

to the following gquestion:

IS THE CONSOLE MEDIUM TO BE SAVED

(Y/N):

Follow the directions specified in the following instruction:
MOUNT THE MEDIA TO BE COPIED ON DEVICE "device-name", TYPE <CR> WHEN READY

medium
console
The MOUNT command then indicates whether the
If so, the copy operation
successfully mounted.
been
has
to
minutes
This operation takes approximately five
begins.
transcribe the contents of the floppy into the directory.
At
completion, control is returned to the command interpreter.

VAX/VMS OPERATING PROCEDURES

Example
1.

CREATE/DIRECTORY DBAl: [HOMER.CONSOL]

DISMOUNT

@[SYSUPD]CONSCOPY

Save

DXAl:

restore

the

contents

the

console

device

from

Files-11

medium

WHAT

THE

FILES-11

WHAT

THE

NAME

THE

MOUNT

DEVICE
THE

CONSOLE MEDIUM
MEDIA TO BE

THE

AND

Backup

from

the

DEVICE

(DDCU:[DIRECTORY])):

(DDCU:):

TO BE SAVED (Y/N):
Y
COPIED ON DEVICE DXAl:,

¥MOUNT-I-MOUNTED,

!
!

DIRECTORY

CONSOLE

mounted

console

device

now

DBAl:[HOMER.CONSOL]

DXAl:

TYPE

<CR>

WHEN

READY:

on DXAl:

complete.

Remove

the media

the

operator

device.

the

copy

the

contents

The

floppy

diskette

subdirectory
of

the

operator

perform

the

following

floppy,

then

copy

disk,

and

executes

DBAl,

which

dismounts

the

operation.

command
This

will
floppy

procedure

creates

store

the

diskette.

CONSCOPY

requests

to
the

information:

The

device

of
the
responds
®

[CONSOL]

and

directory names

floppy
with

The

device

the

operator

diskette

are

(yes)

Whether

the

contents

the

operator

inserted;

DBAl: [HOMER.CONSOL]

which

the

responds

floppy

with

diskette

DXAl

Whether the console
medium
(that
diskette)
1is
to
be
saved;
the

with Y

which

copied;

floppy

console
device;
the RETURN key to

diskette

the operator
indicate that

1is

1is,
the
floppy
operator responds

1inserted

responds by
the floppy

the

pressing
diskette

is mounted
The
CONSCOPY
operation and

command
procedure
informs the operator

then
when

performs
the
it is finished.

copy

VAX/VMS OPERATING PROCEDURES

2.1.11

Restoring a Floppy Diskette from Disk

This procedure describes how to
diskette

from

restore

the

contents

floppy

a disk.

Procedure

restored

floppy

diskette.

Locate the directory which contains the data to

1Insert,

floppy diskette.

into the console device, a scratch

scratch

diskette

operator must dismount

Enter

the

it by typing:

console-device:

S DISMOUNT
3.

is already inserted and mounted, the

following

command:

$ @[SYSUPD]CONSCOPY

This command executes the command procedure

CONSCOPY,

which

resides
1in
the
directory [SYSUPD].
This command procedure
will step the operator through the restoration procedure.

Supply the information requested in the following questions:
WHAT IS THE FILES-11 DEVICE AND DIRECTORY

WHAT

IS THE NAME OF THE CONSOLE DEVICE

(DDCU:[DIRECTORY])
:

(DDCU:)

The first question asks for the device
and
directory
which
contains the material to be restored on a floppy;
the second
floppy
guestion asks for the name of the device in which the
is

inserted.

Answer

"N"

to the

question:

IS THE CONSOLE MEDIUM TO BE SAVED

(Y/N):

Answer the following question by supplying the
bootable

WHAT

system
IS

image:

THE NAME OF THE

BOOTABLE

name

the

IMAGE:

NOTE

Generally,

the name of

this

file

is CONSOL.SYS.

Follow the directions specified in the following instruction:
MOUNT A SCRATCH MEDIUM ON

DEVICE

"device-name:",

TYPE

<CR> WHEN

READY:

The MOUNT command then indicates whether the
scratch
medium
has
been
successfully mounted.
If
so,
the
restoration
procedure begins.
It takes
approximately
£five
minutes
to
transcribe
the
contents
of
the
directory
to
the floppy

diskette.

completion,

directory are printed on the

the

contents

terminal.

the

diskette

VAX/VMS OPERATING PROCEDURES

Example

DISMOUNT

@[SYSUPD] CONSCOPY
Save

DXAl:

restore

the

WHAT

THE

FILES-11

WHAT

THE

NAME

THE

CONSOLE

response

For

MOUNT

bootable

THE

DEVICE
THE

MEDIUM

bootable

WHAT

contents

NAME

file

the

THE

BOOTABLE
DEVICE

CX0:

17APR7.VBO
ESZAB.VBO
CONSOL.SYS

0.
0.
31.

13-JUL-78

WCSMON.SYS

15.

13-JUL-78

WCSSRV.BIN

10.

13-JUL-78

PCS

«.PAT

97.

13-JUL-78

FILEA

.PAT

13-JUL-78

WCS115.PAT
WCSMON .HLP

25.
6.

13-JUL-78
13-JUL-78

CONSOL .HLP

10.
4.

13-JUL-78
13-JUL-78

ERROR

Files-11

medium

DBl:[CONSOL]

DXAl:

DEC,

the

console

13-JUL-78
13-JUL-78

.HLP

13-JUL-78

REMOTE .HLP

13-JUL-78

BOOT

.HLP

13-JUL-78

VMB

.EXE

11.

13-JUL-78

DMOBOO .CMD

13-JUL-78

DM1BOO.CMD
DM2B00 .CMD
DM3B00 .CMD
DMOGEN
DM1GEN
DM2GEN

2.
2.
2.
2.
2.
2.

13-JUL-78
13-JUL-78
13-JUL-78
13-JUL-78
13-JUL-78
13-JUL-78

DM3GEN

13-JUL-78

DMOXDT
DM1XDT
DBOBOO.CMD

2.
2.
2.

13-JUL-78
13-JUL-78
13-JUL-78

DB1BGO .CMD

13-JUL-78

DB2BOO.CMD
DB3BOO.CMD
DB4BOO.CMD

2.,
2.
2.

13-JUL-78
13-JUL-78
13-JUL-78

DB5B0O0O.CMD

13-JUL-78

DB6BOO .CMD
DB7BOO.CMD

2.
2.

13-JUL-78
13-JUL-78

DBOGEN
DB1GEN

2.
2.

13-JUL-78
13-JUL-78

DB2GEN
DB3GEN
DB4GEN
DB5GEN
DB6GEN

2.
2.
2.
2.
2.

13-JUL-78
13-JUL-78
13-JUL-78
13-JUL-78
13-JUL-78

the

name

IMAGE:

CONSOL.SYS

DXAl:,

TYPE

mounted

13-JUL-78

ABBREV.HLP

from

(DDCU:[DIRECTORY]):

(DDCU:):

(Y/N):

written

device

medium

type

only

<CR>

query.

supplied

console

DIRECTORY

SAVED

MEDIUM

the

DEVICE

%MOUNT-I-MOUNTED
DIRECTORY

AND

CONSOLE

floppies

SCRATCH

<CR>

on _DXAl:

this

WHEN

file

READY:

CONSOL.SYS.

VAX/VMS OPERATING PROCEDURES

DB7GEN

13-JUL-78

DBODXT
DBAXDT

2.
2.

13-JUL-78
13-JUL-78

DBABOO.CMD

13-JUL-78

DBAGEN

13-JuUL-78

DBBBOO.CMD

13-JUL-78

DEFBOO.CMD

13-JUL-78

DBBXDT

13-JUL-78

DBBGEN

13-JUL-78

RESTAR.CMD

13-JUL-78

UNUSED

175.

FREE

BLOCKS

TOTAL

305.

BLOCKS

50.

FILES

console

device

Restoration

from

the

of the
device.

complete.

Remove

the

media

In this example, a scratch diskette is already mounted in the
console
device
when
the
operator
begins
the restoration
operation.
The operator dismounts
the
floppy
diskette
by
typing
the
DISMOUNT
command
and
begins
the
restoration
operation by typing the command @[SYSUPD]CONSCOPY.
The

CONSCOPY
information:
)

The
be

command

procedure

device and directory names
restored
onto
a
floppy

responds

with

Whether the console medium
to be saved;
the operator

The

name

the

with

following

which contain the data to
diskette;
the
operator

bootable

(that is, floppy diskette)
responds with a N (no)

system

image;

the

operator

CONSOL.SYS

Whether the floppy diskette is inserted in
the
console
device;
the
operator
responds by pressing the RETURN
key to indicate that the floppy is mounted

The CONSCOPY command procedure
operation
and
at completion,

the

DBAl: [CONSOL]

responds

requests

the

disk.

then performs the
restoration
displays the directory listing

VAX/VMS OPERATING PROCEDURES

2.2

CONTROLLING

BATCH

AND

QUEUES

Although the system manager is responsible for creating
batch
queues
and print queues, the operator must be able to control these queues so
that the operating system can run smoothly.
The procedures
described
in
this
section tell how to control existing batch and print queues.
This section does not,
however,
contain
a
procedure
for
<creating
additional
queues.
This _ topic
1is
fully
described in the VAX/VMS
System Manager's Guide.

In brief, a queue is a list in which jobs are
placed
to
wait
their
turn
to be executed.
Unless a job is explicitly assigned a priority,
by use of the SET QUEUE command, the jobs are
executed
on
a
"first
come, first served" basis.
Print jobs are placed in print queues by means of
the
PRINT
command
and
batch
Jjobs
are
placed
1in
batch queues by means of the SUBMIT
command.
Print queues can be any one of the following:

Physical gqueues -- queues associated with
a specific line printer.

(that

is,

named

for)

Generic queues -- queues
on
any
available
1line
characteristic.

Logical gueues ~- queues that are not associated with
a
1line
printer.
To
obtain printed output from a logical queue, the
operator must explicitly assign that queue to a printer.
The
ASSIGN/QUEUE command, described in Chapter 3, is used for this

from which files can be
printed
out
printer
that has correctly matching

purpose.

and

control

able

gueues

use

and

the

batch

queues,

commands

the

that

operator

must

understand

regulate queueing.

These

commands allow the operator to manipulate
the
queues
and
the
jobs
contained
within
them.
These
commands
are described in detail in
Chapter

this

guide.

In addition, the operator
VAX/VMS commands:

should

also

SHOW QUEUE -- displays information
entered in batch or print queues

SET QUEUE -- changes the
entered in batch or print

These commands
User's Guide.

are described

fully

familiar

about

attributes
queues

the

with

two

other

file

(or

files)

file

(or

files)

VAX/VMS

Command

Language

VAX/VMS OPERATING PROCEDURES

Merging Line Printer Queues

2.2.1

When a problem occurs with a line printer, the queue associated with
that printer should be rerouted to another printer. This procedure
describes how to reroute a gueue without losing any of the jobs in
that

queue.

Procedure

Stop the gueue associated with the malfunctioning printer, by
issuing

the following command:

$ STOP/QUEUE/NEXT queue-namel[:]

This

command

inhibits

further

dequeuing;

however,

the

current job is permitted to complete.

Terminate the printing of the current job and requeue that
job at the end of the gqueue by entering the following
command:

:]
$ STOP/REQUEUE gueue-name|

Take the device offline by pressing the ON/OFF
the device

is offline.

Reroute the jobs queued

the

malfunctioning

another printer by entering the following command:

$ ASSIGN/MERGE device-name[:]

Optionally,

delete

the

qgueue

malfunctioning printer by typing:

$ DELETE/QUEUE

printer

the

new

queue-name|:]

The operator should check that characteristics
printer are appropriate for the new jobs.

switch,

LINE

of the line printer, to the OFF
top panel
on the
located
above the switch goes off when
light
indicator
The
position.

associated

with

the

gqueue-name[:]

Wy U -2

Example

LPBO:
STOP/QUEUE/NEXT
LPBO:
STOP/REQUEUE
LPBO:
ASSIGN/MERGE LPAO:
LPBO:
DELETE/QUEUE

The STOP/QUEUE/NEXT command stops dequeuing jobs in the gqueue
associated with printer LPBO after the current job completes
The STOP/REQUEUE command stops the Job currently
printing.
Then, the
places it at the end of the queue.
and
printing
ASSIGN/MERGE command removes the jobs in the queue LPBO and
places them in the gqueue LPAO. The gueue LPBO can now be
deleted using the DELETE/QUEUE command.

VAX/VMS OPERATING PROCEDURES

2.2.2

This

procedure

changed

When
on

Preventing

the

Loss

describes

how to
line printer.

the

printer

runs

operator's

OPCOM,

of Data When Line

out

terminal

hh:mm:ss.cc,

prevent

paper,

Printer
loss

Runs
data

out of Paper
while

the

paper

OPCOM prints the following message
that the device is not ready:

indicating

DEVICE

OFFLINE,

device-name[:]

Procedure

Suspend

the

current

queue

operation

issuing

command
:

$
Load

the

Resume

STOP/QUEUE

queue-name|:]

new

paper

box

online

the

printer

and

the

return

following

the

printer

condition.

printing

entering

the

command:

START/QUEUE/optional-qualifier

queue-name][:]

Note

that the operator can optionally
append
an
additional
qualifier
to
the
above
command
that
will
adjust
the
characteristics of the queue.
These qualifiers are:

/BACKSPACE [=n]

Backspaces

pages

before

printing.

Currently,

resuming

limited

the

one

page.

/TOP_OF FILE

Starting
the
job
paper

at the beginning of the job, print
that
was
being printed when the

ran

out.

Example

OPCOM,

$
$

22:08:43.40,

DEVICE

STOP/QUEUE
LPAO:
START/QUEUE/TOP_OF
FILE

OFFLINE,

LPAQO:

LPAO:

In the above example, OPCOM notifies the operator
that
1line
printer LPAO went offline at 22:08:43.40.
The operator stops
the gueue associated with the printer, loads
a
new
box
of
paper
into
the
printer,
then
returns
the printer to the
online condition.
The operator can then resume
printing
by

entering the START/QUEUE command.
The /TOP
OF FILE
indicates that the job currently printing will
be
beginning

the

file.

the

qualifier
restarted

VAX/VMS OPERATING PROCEDURES

2.2.3

Terminating

Batch Job

job.
batch
a
This procedure describes how to terminate execution of
This
1is a procedure that should be used only if the system manager or
the owner of a job requests that the job be terminated.
Procedure

Type the following command to determine the
entry number of the batch job that is to be
$

Delete

queue

name

and

terminated:

SHOW QUEUE/BATCH/ALL

the bad batch

job by

issuing

STOP/ENTRY=entry-number

the

following

command:

queue-name|
:]

Example

SHOW QUEUE/BATCH/ALL
*

Batch Queue

"SYSSBATCH"

Jobum=6,

Swap

DELETELO

LNK32

Pri=4,

24-JUL-1978

FORPROG

Pri=4,

24-JUL-1978

Job
Job
Current Job
Current Job

376

315
313
312

DEBUG
JEROME
SYSTEM
SYSTEM

DBGBUILD

Current

Job

207

LANGLEY

STOP/ENTRY=207

Inipriv=4,

Pri=4,
Pri=4,
Pri=4,

Current

BEGINBLD

24-JUL-1978

11:09

24-JUL-1978
24-JUL-1978

10:05
09:57

09:57
09:24

SYSSBATCH

be
that
job
207
requested
In this example,
a
user
has
deleted.
The operator types the SHOW QUEUE/BATCH/ALL command

to determine
The
display

the queue in
shows
that

The operator

then

command.

aborts

which

the

job 207 is
the job
by

job

has

in the
typing

been

entered.

SYSSBATCH queue.
the
STOP/ENTRY

VAX/VMS OPERATING PROCEDURES

2.2.4

Terminating

This procedure

describes

Job

how

printing
on
a line printer.
only if the system manager or
be
terminated,
or
if
the
printed on the line printer.

terminate

Jjob

that

1is

currently

This is a procedure that should be used
the owner of a job requests that the job
operator
observes
garbled output being

Procedure

Enter

the

following

command:

STOP/ABORT printer-namef(:]

Terminating a job while it is currently being
printed
is
a
one-step procedure.
The above command terminates the current
job and begins printing the next job in the queue
without
a
pause

stop.

Example

STOP/ABORT

LPAQ:

This command terminates
LPAO.
The next job in
printing.

the
the

printing
queue is

of the
current
job
immediately dequeued

on
for

VAX/VMS OPERATING PROCEDURES

2.3

TENDING THE

When

the

reader,

CARD READER

operator
the

operator

given

should

card

deck

process

through

1If the deck contains a batch job, that the
deck contain JOB and PASSWORD commands and
contains an EOJ command or is an EOF card

the deck

allocated

a data

the

card

check:

card

deck,

reader,

that
and

the

that

first cards in the
that the last card

wuser

the

deck

has

correctly

contains

EOF

card

That

Processing
card

and
the
the

the

card

reader

a Batch Job:

reader,

the

first

When
two

1is

set

batch

cards

PASSWORD commands.
Without
job.
If
the operator is
operator should return
the

necessary

The

last

card

job

the

these
given
deck

correct

card

translation

submitted
deck

must

mode

through

contain

the

JOB

cards, the system cannot execute
a card deck without these cards,
so
the
wuser
can
insert
the

the

deck must

contain

the

overpunch).
the card punch

EOJ

If
and

command

this
card is
insert it at

EOF

missing,
the
end

the
of

deck.

Processing
that
1is,
PASSWORD

a Data Deck:
When a user wants to
a deck that contains only data and

commands,

the

operator

should

allocated
the
card reader.
If the
system tries to submit the
deck
as
flushes the deck through the system.
The
the
the

make

process
does not

sure

a
data
deck,
contain JOB and

that

card reader is
a
batch
Jjob

the

user

has

not allocated, the
and
subsequently

EOF card (12-11-0-1-6-7-8-9 overpunch) must be the
last
card
in
deck.
This card signals the end of the deck.
Without this card,
system continually waits for more cards.
If the card
deck
1lacks

the

cards.

card
(12-11-0-1-6-7-8-9
operator can type one on
the

EOF

the

card,

end

the

operator

can

type

one

card

punch

and

insert

deck.

Card
the

Reader Translation Modes:
For the system to read input properly,
card
reader
must
be
set to the correct translation mode.
The
translation mode depends on the type of card punch on which the
cards
were
punched.
VAX/VMS supports 026 and 029 card punches.
(For more
information on the translation
modes,
see
the
VAX/VMS
I/0
User's
Guide.)
However,
unless the card deck contains, as the first card, a
mode translation card, or unless the operator knows the mode in
which
the

cards

were

punched,

the

operator

has

little

mode to which the card reader should be set.
explicitly
set
the translation mode of the

The
card

SET

fully

CARD_READER

VAX/VMS

Command

Correcting
deck
to

process
of

the

deck

located

This

command

the

knowing

the

described

1in

the

Language User's Guide.

Physically Defective Cards:

contains

one

command.

way

operator should then
reader by use of the

all

the

deck.

required
This

However,

cards,

the

generally

due

card
to

even

when

reader

may

physical

the
not

defect

card
able
on

cards.

contains

the

front

faulty

panel

card,

the

card

one

reader,

the

error

lights

indicators,

when

the

card

VAX/VMS OPERATING PROCEDURES

then
required
to
is read.
Operator
intervention
1is
the error indicators,
situation.
Table
2-2
describes
operator
action
cause of their illumination,
and
the
correct the situation.

Table

Error

Indicator

READ CHECK

Card

edges

Punch in
column

and

required

Remedies

Corrective Action

Cause

Remove

torn
or

the

the probable

2-2

Alarm Causes

Possible

correct

the

faulty

output
stacker,
card,
place
it

81lst

hopper
button

and

press

card

from

the

duplicate the
in the
input
the

RESET

If READ CHECK
occurs
for
all
cards,
it
indicates
a
malfunction in the card
reader
read logic

PICK

CHECK

Damage

leading

edge

Torn webs

Cards

stapled

together

Remove the cards from the input
hopper,
duplicate
the
faulty
card,
place the cards back
in
the
input hopper and press the
RESET button
If there is no evidence of card
damage,
check
for
excessive
warpage of the card deck and/or
a
build-up of ink glaze on the
picker face

STACK CHECK

Jam

the

card

Badly mutilated

track
card

Correct
the jam and/or
remove
the
mutilated
card
from
the
output
stacker,
duplicate the
card,
place
it
1in
the input
hopper

and

press

the

button

HOPPER CHECK

Input
Output

hopper

empty

stacker

full

Load

the

Unload

input

the

hopper

output

stacker

RESET

VAX/VMS OPERATING PROCEDURES

2.3.1

Operator

This

proc edure

card

read er.

Assistance

describes

how

Processing

load

and

weight

from

the

Card

Deck

process

card

deck

from

Procedure
l'

Remove

the

cards,

card

face

Make sure
hopper.

the

down

with

column

first

card

input
1

read

hopper
the

and

left,

the

place
the

bottom

the

hopper.
of

the

NOTE

Do not pack the
input
hopper
so
full
that
the
air
from
the
blower cannot
rifle
the
cards.
If
the
cards
are
packed
too
tightly,
the vacuum picker
cannot

Press the
indicator
be

operate

RESET
and

properly.

button;
the STOP

this causes the HOPPER
light to extinguish and

CHECK
error
the cards to

read.

NOTE

If the card deck is too large to fit
1in
the
1input
hopper, the excess cards can
be loaded while the reader is
operating
if
tension
1is
maintained on the front
portion of the deck.

Remove

the

CHECK

error

See
are

cards

from

the

indicator

and

output

the

stacker

STOP light

are

when

the

HOPPER

1lit.

Table 2-2 in Section 2.3 for recovery action if the
not read properly upon pressing the RESET button.

cards

VAX/VMS OPERATING PROCEDURES

2.4

MONITORING

SYSTEM STATUS AND ACTIVITY

Periodically,
the
operator
must
examine
the
error
(ERRLOG.SYS)
and the operator's log file (OPERATOR.LOG).

gather

log
file
These files

and maintain information on system errors and events.

Handling the Error Log File:

The error log facility consists of three

parts:

and
A set of executive routines that detect errors and events
write relevant information into error log buffers in memory

error
the
empties
A program called ERRFMT that periodically
the descriptions of the errors into
transforms
buffers,
log
standard formats, and stores the formatted
information
in
a
file on

the

system disk

A program called SYE that generates readable reports from
information

formatted

ERRFMT

the

The executive routines and the
ERRFMT
program
operate
continuously
error log
the
fill
routines
The
intervention.
operator
without
buffers in memory with raw data on every
detected
error
and
event.
When
one
of
the
available
buffers
becomes
full,
or when a time
allotment expires, ERRFMT writes the information into
the
ERRLOG.SYS

Then, the report generator SYE can use ERRLOG.SYS as its input

file.

file and create an error log report as its output file.

any
write
cannot
However, while SYE is accessing ERRLOG.SYS, ERRFMT
error information into it.
Therefore, if SYE is accessing the highest
version of ERRLOG.SYS when

needs

ERRFMT

1log

error,

ERRFMT

The new version picks up logging
new version of the file.
creates a
the
of
versions
All
off.
1left
errors where the previous version
system disk (SYSSSYSTEM) until the
the
file remain on
ERRLOG.SYS
operator

explicitly manipulates

them

Generating error log reports is simpler
operator

has

fewer

1log

files

some way.

and

to deal with.

The

efficient

1if

the

system manager or

operator can take steps to minimize or control the number of
versions
The procedure for obtaining a printed copy of the error log
created.
file includes creating a copy of the current ERRLOG.SYS file and using
1In this way, SYE does not close the file
as input to SYE.
copy
that
to

the

ERRFMT

program.

contains
file
1log
The operator's
Handling the Operator's Log File:
reports concerning the status of the devices currently attached to the
still
system, time stamps that serve as indicators that the system is
running,

and user requests and operator

replies.

Unlike the
error
log
file,
the
operator's
1log
file
1is
already
printable
text;
no intermediate program need be invoked to translate
it

into

readable

output.

For more information about the operator's log file,

see Chapter 4.

Either
File:
Maintaining the Error Log File and the Operator's Log
system manager or the operator is responsible for devising a plan
the
for maintaining the versions of the error log file and the
log

file.

operator's

VAX/VMS OPERATING PROCEDURES

One way to maintain these files is to rename the
highest
version
of
ERRLOG.SYS
file
and
the
OPERATOR.LOG
file
on a daily basis.
For
example, an operator could rename the files every morning at nine A.M.
To
free space on the system disk, the operator could then back up the
old versions of the files onto a different volume and purge the
files
on
the system disk.
Caution should be taken, however, to ensure that
the error log files are not deleted
inadvertently.
The
information

the

error

1log

files

operating

system.

of VAX/VMS

contained
maintenance

1is

essential

for

efficient

VAX/VMS OPERATING PROCEDURES

2.4.1

Printing

the Error

Log File

This procedure describes how to create an error log report and how
to
obtain
a
copy
of
it.
For
a
complete
description
of
the
RUN
SYSSSYSTEM:SYE command see Chapter 3.
Procedure

Set the default disk to
directory
$
$

[SYSERR]

the

system

by typing

the

disk

following

and

the

commands:

default

SET DEFAULT SYSS$SYSTEM
SET DEFAULT SYS$DISK:[SYSERR]

Examine the [SYSERR] directory to see what
ERRLOG.SYS file are on disk by typing:

versions

the

$ DIRECTORY ERRLOG.SYS;*

Rename all the versions of
by

issuing

the

the ERRLOG.SYS file to

ERRLOG.OLD

command:

RENAME ERRLOG.SYS;*

Invoke

the

SYE

utility by

RUN

SYSSSYSTEM:SYE

ERRLOG.OLD;*/NEW VERSION

typing

the command:

To create an error log report, see the description of the RUN
SYSSSYSTEM:SYE
command
1in
Chapter
3.
However, enter the
following file name in response
to
the
input
file
prompt
(input

file:):

ERRLOG.OLD

This is the file created in step 3
of
this
procedure.
By
default, SYE uses the highest version of the ERRLOG.OLD file.

Obtain a copy

following

The file name
the

the

error

1log

report

entering

the

in response

command:

output

filename

is the name of

file prompt

the file entered

(output

file:)

Example

S
$
$

SET DEFAULT SYSSSYSTEM
SET DEFAULT SYSSDISK:[SYSERR]
DIRECTORY ERRLOG.SYS

DIRECTORY DB22:[SYSERR]
18-JUL-78
15:13

ERRLOG.SYS;1
TOTAL OF

14./18.

14.
BLOCKS

18-JUL-78
IN

FILE

13:48

VAX/VMS OPERATING PROCEDURES

RENAME

RUN

SYE

ERRLOG.SYS;*

ERRLOG.OLD;*/NEW VERSION

SYSS$SSYSTEM:SYE

x0.6-0

_input

file:

[[1,6] ERRLOG.SYS]

? ERRLOG .OLD

_output file:
_options:
_device name:

[SYSSOUTPUT]
[ROLL-UP]
[<all>]

_after

[17-NOV-1858]

?R
?<CR>
?<CR>
17-NOV=1858
2<CR>

00:00:00.00

[31-DEC-9999]

31-DEC-9999

23:59:59.99

date:

_before

date:

Successful

?ERRLOG .DAT

completion

ERRLOG.DAT

The

SET DEFAULT commands set the operator's default disk
and
directory
to DBB2:[SYSERR].
The DIRECTORY command lists all
the ERRLOG.SYS files contained in the [SYSERR] directory.
1In
this
example,
[SYSERR]
contains
only
one
version
of
ERRLOG.SYS.

The

ERRLOG.OLD;
ERRLOG.OLD be

the
/NEW_VERSION
qualifier
assigned a new version number if

name

already

The

operator

RENAME

command

renames

ERRLOG.SYS

regquests
a file of

that
this

exists.

then

invokes

SYSSSYSTEM:SYE.

SYE

the

SYE

prompts

utility

for

the

typing

RUN

following

six

parameters:

The

name

the

file

manipulated;

the

operator

responds

with

The name
report;

of the file that is to contain the
error
the operator responds with ERRLOG.DAT

1log

The

the

type

operator

ERRLOG.OLD

report

responds

that

with

SYE

should

which

generate:

indicates

the

ROLL UP

report

The devices on which SYE
should
operator
responds
by
pressing
requests

SYE

report

the

report
errors;
rhe RETURN key,

occurrence

errors

the
which
all

devices
@

The time
operator
requests
November

from which
SYE
should
record
errors;
responds
by
pressing
the RETURN key,
SYE to report the occurrence of
errors
17, 1858

The time

SYE

responds
by
SYE to report

December

31,

SYE
<creates
the
ERRLOG.DAT
file.
report

which

operator
requests

using

the

should

record

pressing
the
the occurrence

the
which
after

errors;

the

RETURN key,
of
errors

which
until

9999

error
The
PRINT

1log
report
and
operator
obtains
command.

stores
a hard

it
copy

in
of

the
this

VAX/VMS OPERATING PROCEDURES

2.4.2

Printing

the Operator's

Log

File

This procedure describes how to produce a printed copy of the
current
version
of
the
operator's
1log file (OPERATOR.LOG), which should be
given to the system manager for retention.
This procedure
should
be
performed periodically.
Procedure

Close the current log
following

Set the default to the system disk by typing:
SET DEFAULT SYSS$SSYSTEM

Examine the directory [SYSMGR] to see what
versions
operator's log file are on disk using the command:
$

the

REPLY/LOG

file and open a new one by entering

command:

DIRECTORY

following
$

the

[SYSMGR]OPERATOR.LOG;*

Obtain a printed copy of the operator's log file
the

issuing

command:
[SYSMGR]OPERATOR.LOG;n

Note

The version number, n, must
than the highest version of

be
1
1less
this file.

Example

REPLY/LOG

OPCOM, 16-JUL-1978
12:29:24.52,
INITIALIZED, OPERATOR=_TTAZ2:

$
$

LOGFILE

SET DEFAULT SYS$SYSTEM
DIRECTORY [SYSMGR]OPERATOR.LOG;*

DIRECTORY DB22:[SYSMGR]
16-JUL-78 12:50

OPERATOR.LOG;
202
OPERATOR.LOG;
201
OPERATOR.LOG;
200
OPERATOR.LOG;199

1.
1.
5.
1.

TOTAL OF

8./186.

[SYSMGR]OPERATOR.LOG;201

BLOCKS

16-JUL-78
16-JUL-78
15-JUL-78
15-JUL-78
IN

12:29
12:21
17:02
14:05

FILES

The REPLY/LOG command closes the current log file and opens a
new
one;
the
response
from OPCOM verifies that a new log
file has

been opened.

The

SET

DEFAULT

command

sets

the

operator's default disk to the system disk, thus enabling the
operator to examine the
files
contained
in
the
directory
[SYSMGR] .
The
operator
then requests that the second most
recent version of the file OPERATOR.LOG be printed by use
of
the

command.

VAX/VMS OPERATING PROCEDURES

2.5

SHUTTING DOWN AND RESTARTING

THE VAX/VMS

Occassionally, the system operator may need
the VAX/VMS operating system to ensure that
for

halting

the

system

include

danger

to
it

OPERATING

SYSTEM

shut down
and
runs properly.

power

1loss,

the

restart
Reasons
need

back-up
the system disk, a hardware or software problem, or simply no
need to use the computer system.
The
operator
restarts
the
system
once
the
problem is solved or when there is a need to use the system
again.

Shutting Down
the
Operating
System:
This
by which the operator can shut down

procedures
1.

An Orderly

Shutdown

Emergency

Shutdown

the
of

section
describes
system:

two

the

System

the

System

The first procedure is a command file
distributed
with
the
VAX/VMS
software.
This
command
file,
named
SHUTDOWN,
resides
in
the
SYS$SSYSTEM
directory.
Once
invoked,
SHUTDOWN
performs
certain
housekeeping
functions
that
ensure a smooth shutdown of the system.
These housekeeping functions include disabling future logins, stopping
the batch and device queues, dismounting mounted volumes, and stopping
user processes.
This
file
also
invokes
a
site-specific
commana
procedure
named
SYSHUTDWN.COM that is tailored by the system manager
to the needs of the specific installation.
This
file
1is
furnished
without contents in the distribution kit.
If the operating system cannot be shut down by means of
the
SHUTDOWN
command
file,
the
operator
must
perform
the second procedure, An
Emergency Shut Down of the System.
This
procedure
shuts
down
the
system
immediately
without
performing
any
of
the
housekeeping
functions;
hence, data may be lost.
For this reason, this
procedure
should only be used if the first procedure fails.

Restarting the Operating System:
Restarting the system means
loading
the
operating
system
into
memory
and
performing
the
necessary
housekeeping functions for the system
to
run
smoothly.
Generally,
when
the
system crashes, it automatically restarts itself.
However,
sometimes operator intervention is required
to
restart
the
system.
This usually occurs after the operator has halted the operating system
by one of the methods described above.
When the operating system is
booted,
the
command
file
STARTUP
is
automatically
executed.
This
start-up
file
contains commands for
performing site-independent operations that must be performed
1if
the
system
1is
to
run
properly.
These
operations
include
assigning
system-wide logical
names,
installing
executable
images
as
known
images and creating permanent global sections.
This file also invokes
a site-specific command procedure file named
SYSTARTUP.COM
in
which
the system manager places site-specific initialization commands.
This
file is furnished without contents in the distribution kit.
Sometimes, the operating system does not boot after the
operator
has
entered
the
restarting
command.
This
can
be
caused by either a
software or hardware malfunction.
A read error on a
floppy
diskette
or
a
machine
<check
error indicate a hardware malfunction;
DIGITAL
field service should be contacted.

VAX/VMS OPERATING PROCEDURES

If,

however,

STARTUP

the

operating

command

file

1is

system

not

probably occurred.
The operator
following actions to correct the
1.

Repeat

the

Start the

Restart

the

followed

loaded

executed,

1into

memory,

but

the

a software malfunction has

can
perform
situation:

one

the

start-up procedure

system from an alternative drive or
LSI-11
typing

console

177300G

pressing

response

the

disk pack
the
@

BREAK
prompt

key,

VAX/VMS OPERATING PROCEDURES

2.5.1

This

Orderly

Shutdown

procedure describes

fashion.
modified

This
at the

the

how

procedure
discretion

System

shut

down

the

system

orderly

1is
contained in a command file and
of the system manager or operator.

can

Procedure

Type

the

$
2.

Enter

following

command

begin

the

shutdown

procedure:

@SYS$SYSTEM:SHUTDOWN
a

number

HOW

MANY

response

MINUTES

UNTIL

following

guestion:

SHUTDOWN?

Give the reason for shutting
the following prompt:

down

the

system

response

REASON?

The

execution of
following events

nonoperator

procedure

continues

printed

the

All

The batch and device queues are stopped
minutes left until system shutdown.

A message

that

all

decreasing

The

users

requests

the

time

site-specific

invoked.

inserted

This

procedure

the

needs

mounted

All

user

processes

are

not

stopped:

the

disabled.

log

when

out

there

This message

Procedure

are

broadcasted

volumes

are

the

contains

tailor

1is

commands

the

shutdown

installation.

dismounted.

stopped;

NULL,

process

SYSHUTDWN.COM

firbcedure

system manager

the

and
terminal:

intervals.
command

All

and

are

users

system.

command

ERRFMT,

logins

future

the shutdown
occur and are

the

SWAPPER,

running

following

processes

JOB_CONTROL,

OPCOM,

SHUTDOWN

command

the

procedure.

The

operator's

The

program

the

system.

This

the

contents

stacks,

log

file

The

system

closed.

SYSSSYSTEM:OPCCRASH

and

invoked

program performs

the

privileges.

is halted.

registers,
executive

stack

bug

shut

down

check

and

dumps

kernel/interrupt
and

the

process

VAX/VMS OPERATING PROCEDURES

Example

$ @SYSSSYSTEM:SHUTDOWN
SYSTEM

SHUTDOWN

COMMAND

27-JUN-1978 08:27:08
HOW MANY MINUTES UNTIL

PROCEDURE.

SHUTDOWN?:

REASON?:
WEEKLY SYSTEM DISK BACKUP
Login quotas - Interactive limit=64,
NON-OPERATOR

LOGINS

STOP

QUEUES.

RUNNING

_OPAO:,SYSTEM

ARE

DISABLED.

08:27:54.94

"SYSTEM SHUTDOWN

Current interactive value=4

IN 4 MINUTES.

LOGINS ARE DISABLED,

PLEASE LOGOFF

_OPAQ:,SYSTEM 08:27:58.87
"WEEKLY SYSTEM DISK BACKUP
_OPAQ:,SYSTEM

08:30:01.37
"SYSTEM SHUTDOWN IN 2 MINUTES.

LOGINS ARE DISABLED,

PLEASE

LOGOFF

_OPAO:,SYSTEM 08:30:05.30
"WEEKLY SYSTEM DISK BACKUP

_OPAO:,SYSTEM 08:31:07.82
"SYSTEM SHUTDOWN IN 1 MINUTE.

LOGINS ARE DISABLED,

PLEASE LOGOFF

_OPAO:,SYSTEM 08:31:11.73
"WEEKLY

SYSTEM

DISK

BACKUP

SHUTDOWN

IMMINENT.

INVOKE INSTALLATION DEPENDENT SHUTDOWN PROCEDURE
DISMOUNT

ALL

STOP ALL

"USER"

Opcom,

08:31:28.94,

Opcom, OPAO:,
Opcom,

***%*

MOUNTED

VOLUMES

PROCESSES
SYSTEM

Accnt=

"OPERATOR REQUESTED SHUTDOWN"

27-JUN-1978

08:31:32.95,

PATAL BUG CHECK OPERATOR,

logfile closed,

Operator

operator=_OPAOQ:

requested system crash

VAX/VMS OPERATING PROCEDURES

PROCESS

CURRENT

SYSTEM

RO = 00000024
R1 = 00000000
R2 = 00000004
R3 = 7TFFE9ABE
R4 = 800A5FDO
R5 = 7FFEE484
R6 = 31000513
R7 = T7FFEF99C
R8 = 7FFEF900
=

T7FFEF98C

R10=
Rl11=
AP =
FP =
SP =
PC =
PSL=

7FFEF9A4
7FFE7810
00000000
7FFEEDDO
T7FFEEDCS8
00000218
00C00000

KERNEL/INTERRUPT STACK
7FFEEDDO
7FFEEDD4
7FFEEDDS
7FFEEDDC
7FFEEDEO
7FFEEDE4

T7FFEEDES
7FFEEDEC
7FFEEDFO
7FFEEDF4
7FFEEDFS8
7FFEEDFC

EXEC

00000000
00000000
7FFDE178
7FFEEDE4
800120FA
00000000

00000000
7FFDE178
7FFDE160
80015EB7
80000096
03C00000

STACK

PROCESS

PRIVILEGES

800ABAOO
800ABA(O4

FFFFFFFF
FFFFFFFF

IMAGE NAME = DMAO:[10,40]OPCCRASH.EXE;8
INST

EXECUTED

HALTED AT

800131CD

HALT

>>>

In this example, the operator requests that the system be
shut down in 5 minutes to allow a system disk back-up. After
the
indicating when and why the system will be shut down,
are
shutdown
clean
a
ensure
that
functions
housekeeping
performed and the system is halted at 800131CD.

VAX/VMS OPERATING PROCEDURES

2.5.2

This

Emergency

procedure

Shutdown

describes

the

how

System

halt

the

system

immediately

without

performing

any
of
the
housekeeping
functions that ensure a smooth
shutdown.
Generally, the operator shuts down the system by
following
the
procedure
described
on
the
previous pages.
If, however, that
procedure fails, the operator must perform an emergency shutdown.
To

perform

the

system

this

procedure,

the

operator

must

enter

the

commands

force

immediate

the

RUN

from

console.

Procedure

Enter the following
the system:

command

shutdown

$ RUN SYSSSYSTEM:OPCCRASH

Note

Step

ignored

SYSSSYSTEM:OPCCRASH

command

successful.

Enter

does

the

not

following

respond

two

LSI-11

console

the

above

command:

commands

the

system

CTRL/P
>>>HALT

The

CTRL/P

control

command

operating

the

places

<console

system.

The

the

system

program

HALT

console

instead

command

halts

under

the

VAX/VMS

the

system

the

system

completely.

Observe
console:

the

HALTED

following

information

typed

"address"

The console program
typing the system's

reports
program

that
the
counter at

system
is
the time of

halted
by
the halt.

Example

CTRL/P
>>>HALT

HALTED

In
and

this
the

800172C0

example,
system

the

stops

operator
at

types

800172CO.

CTRL/P

followed

HALT,

VAX/VMS OPERATING PROCEDURES

2.5.3

Restarting

the

System

The procedure describes how to restart the
VAX/VMS
operating
system
after
it
has
been shut down and consequently needs to be explicitly
booted.
To perform
this
procedure,
the
operator
must
enter
the
commands

from

the

system console.

Procedure

Enter

the

following command to boot the

>>>BOOT

system:

[device-name:]

Observe the

bootstrap

information

printed

the

system

console.
Example
1.

>>>BoOT DMO:
CPU

HALTED

INIT

SEQ

DONE

G
0000000E
00000200
LOAD DONE
00001600 BYTES LOADED

VAX/VMS BASE

OPCOM,

LEVEL 6.0

02-AUG-1978

14:36:04.89,

08:25

LOGFILE INITIALIZED, OPERATOR=_OPAO:

In this example, after the operator enters the BOOT
command,
the
operating
system
is loaded into memory and the STARTUP

file is executed.

and

ready

Upon completion,

accommodate

system

the system is initialized

users.

CHAPTER
COMMANDS

USED

BY OPERATORS

This chapter contains descriptions of some of
the
commands
used
by
operators of the VAX/VMS system.
The use of most (but not all) of the
commands described in the chapter is restricted to users who have
the
operator
privilege
(OPER);
usually,
only system operators and the
system manager have this privilege.
Table
3-1
1lists
the
commands
described in this chapter.
For information about using the commands that
are
not
described
in
this
chapter
and
about
running utility programs, see the following
sources:

The VAX/VMS Command Language User's Guide, which contains both
a
general
introduction
to
the
wuse of VAX/VMS commands and
detailed descriptions of the VAX/VMS
commands
that
are
not
described

3.1

this chapter.

The VAX-11 Disk Save and Compress User's Guide, which contains
a detailed description for running the DSC utility.

SUMMARY OF

COMMANDS

USED

BY OPERATORS

Table 3-1
sections)

briefly describes
the
commands
used
by
operators.
following the table provide more detailed descriptions,

examples,

the

commands.

Commands

Table
Used

3-1
by Operators

Command

ASSIGN/MERGE

ASSIGN/QUEUE

The
with

Function

To remove the jobs from one gqueue
and place them in another queue
To assign a

logical

queue

device

DEASSIGN/QUEUE

To deassign a queue

from a device

DELETE/QUEUE

To delete batch queues

and

output

page)

queues

(continued

COMMANDS

USED

BY OPERATORS

Table 3-1
Commands Used

(Cont.)
by Operators

Function

Command

INITIALIZE/QUEUE

create

batch

queues

and

output

queues

MCR

BAD

MCR DSC1

To
1locate
and
count
blocks
contained
on
disks

the
bad
Files-11

To transfer
files
<contained
on
Files-11
Structure Level 1 disks
to tapes or disks for back-up and
storage

MCR DSC2

To transfer
files
contained
on
Files-11
Structure Level 2 disks
to tapes or disks for back-up and
storage

MCR VFY1

To
<check
the
readability
and
validity
of
Files-11
Structure
Level 1 disks

MCR

To
check
the
readability
and
validity
of
Files-11
Structure
Level 2 disks

VFY2

To communicate with system users,
to selectively enable and disable
operator status, and
to
examine

the

log

file

RUN

SYS$SSYSTEM: INSTALL

install

known

RUN

SYS$SYSTEM:SYE

create

from a binary

images

error

1log

formatted

report

file

SET

ACCOUNTING

To selectively enable or
disable
the recording of particular kinds
of accounting information

SET

DEVICE

To
establish
the
spooling
error
logging
status
on
specified device

SET

LOGINS

To
of

establish the
wusers
able

and
a

maximum
number
to
1log into the

system

SET

PRINTER

To
of

establish the
characteristics
a specified line printer

SET

PROTECTION/DEVICE

To establish
shareable,
device

the protection for a
non-file-structured

(continued

next page)

COMMANDS

USED BY OPERATORS

Table 3-1
Commands Used

(Cont.)
by Operators

Command

SET TERMINAL/PERMANENT

SET UIC

Function

To
modify
characteristics
terminal

the
of

To
establish
identification

process

permanent
specified

code

new

user
the

UIC

SHOW TERMINAL/PERMANENT

To display the current
characteristics
of
a
terminal

START/QUEUE

start batch queues

permanent
specified

and

output

queues

STOP/ABORT

To stop the

STOP/ENTRY

To stop the execution of a
batch
job that is currently running

STOP/QUEUE

that

suspend

output

STOP/REQUEUE

printing

currently being

batch

job

printed

queues

and

queues

stop the

printing

job

that
1is
currently being printed
and requeue that job at
the
end
of

3-3

the

queue

COMMANDS USED BY OPERATORS

ASSIGN/MERGE
3.2

ASSIGN/MERGE

Removes jobs from one gqueue and places them in another
original queue is then eligible for deletion.

queue.

The

Format

ASSIGN/MERGE device-name/[:]

gueue-name|
:]

Command Qualifiers
None.

Prompts

Device:

device-name]|:]

Log Name:
Command

queue-name[:]

Parameters

device~name]|
:]

Specifies the name of
which

the

files

will

the line printer

terminal

gueue-name|
:]

Specifies the name of the queue that is going to be
to

queue

be directed.

a new line printer

terminal.

reassigned

Description

The ASSIGN/MERGE command merges one queue with
another
queue.
However, before the merge operation can take effect, the source
queue (that is, the queue to be
merged)
must
be
stopped
by
issuing
the
STOP/QUEUE/NEXT
command.
The target queue (that
is, the queue that will accommodate the source queue) need
not
be

stopped.

This command

particularly

wuseful

when

output

device

malfunctions;
issue
ASSIGN/MERGE
to
reroute the queue to a
different
output
device.
However,
to
perform
the
merge

operation
without
losing
or
disrupting
any
user jobs, the
operator should
follow
the
procedure
described
in
Section
2.2.1.

Example

$
$

STOP/QUEUE/NEXT
LPBO:
ASSIGN/MERGE
LPA0:
LPBO:

The STOP/QUEUE/NEXT command
stops
the
queue
LPBO.
The
ASSIGN/MERGE
command
removes the jobs from the LPBO queue
and places

them

the queue LPAO.

COMMANDS

USED

BY OPERATORS

ASSIGN/QUEUE
3.3

ASSIGN/QUEUE

Assigns, or
terminal.

redirects,

logical

queue

1line

printer

that

Format

ASSIGN/QUEUE
Command

device-name[:]

logical-queue~name|
:]

Qualifiers

None.,

Prompts

Device:
Log

device-namel[:]

Name:

Command

logical-queue-name[:]

Parameters

device-name|:]
Specifies the physical name of a line printer
to be associated with a logical queue.

terminal

logical-queue-name|:]
Specifies the name of the logical queue that is to be assigned to
a line printer or terminal (a logical queue is a queue whose name
does not match a physical device).
Description
Jobs

been

logical

assigned

queue
a

cannot

physical

printed

device,

that

unless
is,

the
line

queue
printer

terminal.
The ASSIGN/QUEUE command allows the operator
to
this
assignment.
However, to print the jobs, the operator
then start the queue using the START/QUEUE command.
The ASSIGN/QUEUE command is not used
is,
a
queue
implicitly
assigned
initialized and started.

when a physical
to
a
physical

has
or

make
must

queue
(that
device)
is

Examples

$
$
$
$

INITIALIZE/QUEUE/FLAG/GENERIC TEST QUEUE
INITIALIZE/QUEUE/FLAG/GENERIC
LPAO:
ASSIGN/QUEUE LPAO:
TEST QUEUE
START/QUEUE
LPAO:

START/QUEUE TEST QUEUE

The INITIALIZE commands create the logical
queue
TEST QUEUE
and
the
physical
queue
LPAO.
Both
these
queues
are
initialized with generic printing enabled and a
header
page
preceding
each
job.
However, because the logical queue is
not
not

associated with a
have
a
device

ASSIGN/QUEUE command
with
the
physical
when

the

queues

are

printer, jobs entered
on
which
they
can

associates the
device
LPAO;
started

3-5

with

the

in
be

that queue
printed.

do
The

logical queue
TEST QUEUE
hence, printing can begin
START/QUEUE

commands.

COMMANDS USED BY OPERATORS

$
$

INITIALIZE/QUEUE/GENERIC
LPBO:
START/QUEUE

LPBO:

In this example,
the
ASSIGN/QUEUE
command
is
not
needed
because
a
1logical
queue
1is
not
being
initialized.
The
physical
gqueue
LPBO
1is
the
name
of
a
line
printer;
therefore,
for
printing
to
begin,
the gqueue need only be
started by use of the START/QUEUE command.

COMMANDS

USED

OPERATORS

DEASSIGN/QUEUE
3.4

DEASSIGN/QUEUE

Deassigns

a logical

queue

from a line printer

terminal.

Format

DEASSIGN/QUEUE

logical-queue-name/|:]

Command Qualifiers
None.

Prompts

Log Name:
Command

logical-queue-name|:]

Parameters

logical-queue-name|
:]

Specifies the
name
of
a
1logical
gqueue
that' was
previously
assigned to a line printer or to a terminal (a logical queue is a
gueue whose name does not match a physical device).
Description

This command takes effect only if the specified
queue
1is
idle.
That is, the queue must be stopped by the STOP/QUEUE/NEXT command
before

the

DEASSIGN/QUEUE

command

issued.

Once the DEASSIGN/QUEUE command has been issued, the jobs in
the
logical
queue
remain in a hold state until the queue is deleted
or reassigned to another physical device.
Example

ASSIGN/QUEUE

LPAQO:

ASTER

$
$

STOP/QUEUE/NEXT
ASTER
DEASSIGN/QUEUE
ASTER

The ASSIGN/QUEUE command associates the logical
gqueue
ASTER
with
the
physical
device
LPAO.
Later,
the operator may
decide to disassociate the queue ASTER from the device
LPAO.
First,
the
operator
stops
the
1logical
queue
wusing
the
STOP/QUEUE/NEXT command.
Then, the queue can
be
deassigned
with the DEASSIGN/QUEUE command.

COMMANDS

USED

BY OPERATORS

DELETE/QUEUE
3.5

DELETE/QUEUE

Deletes

jobs

specified

contained

batch

that

output

queue;

hence,

deletes

all

the

queue.

Format

DELETE/QUEUE
Command

gueue-name]:]

Qualifiers

None.

Prompts

File:

gueue-name]:]

Command

Parameters

qgueue-namef{
:]

Specifies

the

name

the

queue

be deleted.

Description

This
idle

command takes effect
state;
that
1is,

only
the

if the
queue

specified
must
be

STOP/QUEUE/NEXT command before a DELETE/QUEUE

queue
1is
stopped

command

in
by

an
the

issued.

Example

INITIALIZE/QUEUE/FLAG LPAO:

START/QUEUE

LPAOQ:

$
$

STOP/QUEUE/NEXT LPAO:
DELETE/QUEUE LPAO:

In the preceding sequence of commands the printer queue
LPA(Q
is
initialized
and started.
Later, the operator may decide
to delete that queue.
First, the operator stops the queue by

using
queue

the
STOP/QUEUE/NEXT;
then, the operator
by issuing the DELETE/QUEUE command.

3-8

deletes

the

COMMANDS

USED

OPERATORS

INITIALIZE/QUEUE
3.6

INITIALIZE/QUEUE

Creates

initializes

a batch gueue

output gqueue.

Format

INITIALIZE/QUEUE
Command

queue-namel:].

Qualifiers

Defaults

/BATCH
/ [NO] BURST
/[NO]DISABLE_SWAPPING
/[NO]ENABLE_GENERIC_PRINTING
/ [NO] FLAG
/FORMS_TYPE=n
/ [NO] GENERIC
/JOB_LIMIT=val
/PRIORITY=val
/TERMINAL

/NOBURST
/NODISABLE_SWAPPING
/ENABLE_GENERIC_PRINTING
/NOFLAG
/NOGENERIC
/JOB_LIMIT=1
/PRIORITY=4

Prompts

Queue:

gqueue-name]l:]

Command

Parameters

queue-name
[ :]

Specifies
qgueue, or

the name of a physical
a logical queue name.

device,

the

name

generic

Description
The INITIALIZE/QUEUE command creates
assigns
them names and attributes.

jobs
placed
in
the
START/QUEUE
command.
the
INITIALIZE/QUEUE
START/QUEUE command.

When the operator
required.
Command

batch and print
gqueues
and
However, to print or run the
queues,
the
operator
must
issue
the
All
the options that can be specified in
command
can
also
be
specified
in
the

creates

a batch queue,

the

qualifier

/BATCH

for

each print

job.

Qualifiers

/BATCH
Indicates
/BURST
/NOBURST
Controls

that

this

printing

batch

queue.

of a burst header

page

Use the /BURST qualifier to print a header page
over
the
paper
perforations;
hence, the page header is visible from the side of
a stack of paper'.
A burst header simplifies separating listings.
The default

qualifier

is /NOBURST.

COMMANDS

USED BY OPERATORS

/DISABLE_SWAPPING
/NODISABLE SWAPPING
Controls whether batch
jobs
swapped in and out of memory.
The default qualifier

executed

from

the

queue

default,

generic

device

printing

The default qualifier

The forms type
alphanumeric
defined.

the

queue

should
code.

/JOB_LIMIT=val
Indicates
the
number
concurrently
from the
is 1.

is printed

be specified
Codes
for

using
forms

this

the

beginning

numeric
type
are

the

not

specified,

the

of
batch
jobs
that
<can
queue.
The default value of

value
or
an
installation

a queue can be
printed
on
any
that
has
correctly
matching

/PRIORITY=val
Indicates the priority at
which
jobs
are
queue.
The default value of the priority of

that

with

type for the specified queue.
Once
a
dueue
a forms type, all jobs in that queue that do
forms type are placed in a holding state.

qualifier /GENERIC is
a nongeneric gqueue.

/TERMINAL
Indicates

associated

is /NOFLAG.

/GENERIC
/NOGENERIC
Controls whether files placed
available
line
printer
characteristics.

default

from

placed in
printing.

enabled.

/FLAG
/NOFLAG
Controls whether a header page
first file in each print job.

/FORMS_TYPE=n
Specifies the forms
has
been
assigned
not conform to that

/NODISABLE SWAPPING.

/ENABLE_GENERIC_PRINTING
/NOENABLE_GENERIC_PRINTING
Controls whether files queued to a generic queue can be
a physical queue (that is, a device-specific queue) for

physical

can

terminal

queue.

queue

be
the

1initiated
a queue is

1is

executed
job limit

from
4.

the

COMMANDS

USED

BY OPERATORS

Examples

$ INITIALIZE/QUEUE/BATCH/JOB
_LIMIT=4 SYS$SBATCH
$ START/QUEUE SYSS$BATCH
$ INITIALIZE/QUEUE/FLAG
LPAOQ:
$ START/QUEUE
LPAO:

The preceding sequence of commands initializes and starts the
batch
queue
SYS$BATCH and the line printer queue LPAO.
The
/JOB_LIMIT=4 qualifier allows up to four jobs to be initiated
concurrently
from
the
batch
queue.
The
/FLAG qualifier
causes a header page to
precede
each
Jjob
in
the
printer

-nnuvrn

queue.

INITIALIZE/QUEUE
TESTER
INITIALIZE/QUEUE/FLAG
LPAOQ:
ASSIGN/QUEUE
LPAO:
TESTER
START/QUEUE
TESTER
START/QUEUE
LPAO:

The preceding procedure causes all jobs queued to the logical
queue
TESTER
to
be
printed
on
the physical device LPAOQ.
First, the INITIALIZE commands initialize the
1logical
queue
TESTER
and the physical queue LPAO.
The physical queue LPAO
is enabled to print a header page at
the
beginning
of
the
first
file
in
each
job.
Next,
the ASSIGN/QUEUE command

associates

the

logical

queue TESTER with

LPAO.
After
the START commands
to TESTER or LPAO will be printed

the

are issued,
on LPAO.

physical
all

jobs

queue
queued

COMMANDS

USED

OPERATORS

MCR BAD
3.7

MCR

BAD

Determines

the

number

and

location of

bad blocks on Files-11

disks.

Format

MCR BAD device-name:

Command Qualifiers
None.

Prompts

None.

Command

Parameters

device-name:

Specifies a device containing
The device name consists of a
by a one- or two-digit number
device name terminator (:).
Alphabetic

controller

a volume on which BAD will be
run.
two-character device name, followed
that specifies the unit code and
a

designators

the

device

name

are

not

supported.

Description

The BAD command analyzes the condition of the blocks on
Files-11
disks.
BAD
writes
a
test
pattern onto each block, reads the
blocks into a buffer in storage, then compares the
data
in
the
buffer with the data that was written to the blocks.
If the data
does not compare exactly, the block is bad
and
cannot
reliably
store

data.

When BAD locates a bad block, it records the address of
the
bad
block in a separate buffer for reference.
When all bad blocks on
the disk are located, the addresses and extents of the bad blocks
are
recorded
on the last good block of the disk.
The disk must
have at least one good block for BAD to execute properly.

The operator must mount the disk to be analyzed with the /FOREIGN
gualifier.
This gualifier indicates that the disk volume is in a
format not recognized by the VAX/VMS operating system.
(See
MOUNT command in the VAX/VMS Command Language User's Guide.)
On system
disks,
block
zero
wusually
contains
the
record.
However, the bootstrap record is not required
and thus, if BAD prints a message warning the operator
the disk as a system disk, the message can be ignored.
While

BAD

other

programs.

analyzes

a disk,

that disk must not

the

bootstrap
by VAX/VMS
not to use

accessed

any

COMMANDS USED BY OPERATORS

BAD

stores

102

entries

for

addresses

and

extents

bad

blocks on all disks except RK0O6 and RK07 disks.
If more than 102
entries are recorded for a disk, BAD exits with an error message.
For
RK06 and RK07 disks, the maximum number of bad block extents
that can be written

is 126.

Example

$ ALLOCATE
_DBA2:

DBA2:

ALLOCATED

$ MOUNT/FOREIGN DBA2:
mounted on _DBA2:
$MOUNT-I-MOUNTED
DB2:
$ MCR BAD
BAD -- TOTAL NO.
OF BAD BLOCKS = 2.

a
specific
of
The ALLOCATE command requests the allocation
response from the ALLOCATE command
The
DBAZ2.
drive,
disk
indicates that the device was
successfully
allocated.
The

MOUNT/FOREIGN

command

disk.
The MOUNT command
successfully mounted.
block on the disk volume
tested all the
has
BAD
of

bad blocks on DBA2

mounts

the

disk volume as a foreign

response
indicates
that
DBA2
was
command analyzes each
MCR BAD
The
After
and records the bad
blocks.
blocks, it indicates that the number
2.

COMMANDS

USED

BY OPERATORS

MCR DSC
3.8

MCR DSC

Copies

files

Structure

reallocates

Files-11

contained

Level

and

Level

command

Command

Files-11

tapes

consolidates

Structure

MCR DSC1l

disks

the

Structure

disks

disk

Level

for

area

and

back-up and

used

for

data

Files-1l1

storage,

and

storage.

Format

string

Qualifiers

None.

Files-11

Structure

MCR DSC2

Level

Format

command-string

Command

Qualifiers

None.

Prompts

If the operator does not enter
the
command
command line, DSC prompts for it (DSC>), and

CTRL/Z

operator

the

typed.

DSC
executes
interpreter.
Command

string
on
the
initial
continues prompting until

enters
the

the

command

command,

string

then

returns

the

initial

control

command

the

line,

command

Parameters

command-string

Specifies

single DSC

the

contents

disk

The

operator

enters

DSC

command
to

that controls

tape

disk.

commands

the

how DSC

following

transcribes

format:

outdev:[filelabel] [/qualifier]=indev:[filelabel] [/qualifier]
outdev:

Lists
The

the physical

format

for

device(s)

outdev:

which data

transferred.

1is:

AAAN:

AAA

ASCII characters specifying the device
the alphabetic controller designator

1-digit

(octal)

unit

number

name

followed

COMMANDS

USED

The device name

When more than one
symbols must appear

BY OPERATORS

terminator

tape
drive
is
requested,
in a comma-separated list.

the

device

[filelabel]

Is
an
optional
1to
1l2-character
alphanumeric
name
identifying the tape file created when files are transferred
from disk to a set of magnetic tape volumes.
If
the
file
label
1is
not
specified
when
a tape file is created from
disk, the disk volume label is used as the identifier.

/qualifier

Specifies one or more optional output qualifiers, as
in Table

listed

3-2.

Table

3-2

Output Qualifiers

Qualifier

Format

Meaning

Append -

/AP

Bad Block

/BAD =(MAN
Allows manual
entry of bad block data
output disk's bad
the
supplement
NOAUTO | to
AUTO
block file;
ignores
the
bad
block
disk;
the
on
descriptor
blocks
bad
entered
manually
uses

Writes a file to the

first

specified

volume
of
a
tape
set that contains
only entire DSC-created files

exclusively

/CMP

Compare

contents

Creates magnetic tapes

Compares the

device with the contents of

the

input

1600

Dbits

the output

device

Density

/DENS=1600

Nonmerge

/NMG

per

inch density

Copies

files

consolidating

from

all

the

disks

without

extents

file

Rewind

/RW

Rewinds output tape volumes before DSC

Verify

/VE

Performs

starts writing

indev:

them

operation,

then

the contents of both devices

and

Lists the physical device(s)
The format for indev:
1is:

copy

compares
(input

output)

from which data

transferred.

AAAN:

AAA

ASCII characters

specifying

A 1-digit

unit number

the

device

abbreviation

followed by the alphabetic controller designator
(octal)

COMMANDS

The

device

When more

than

symbols must

USED BY OPERATORS

name
one

terminator
tape

appear

drive

1is

requested,

comma-separated

the

device

list.

[filelabel]
Is
an
optional
1to
12-character
alphanumeric
name
identifying a DSC-created tape file to be transferred to the
specified disk.
1If the file label
1is
not
specified,
DSC
copies
onto
the disk medium the first tape file it locates
on the first tape volume specified.

[/qualifier]
Specifies one
in Table 3-3.

or more

optional

input qualifiers,

listed

Table 3-3
Input Qualifiers

Qualifier

Format

Meaning

Nonmerge

/NMG

Copies files from one disk to
disk
without
<consolidating
extents of a file

Rewind

/RW

Rewinds first tape volume
copy operation begins

second
all
the

before

the

Description
The DSC1l
disk
to
command

command transfers data from a Files-11 Structure Level 1
another disk or set of magnetic tape volumes;
the DSC2
transfers

another

disk

data

from

set

Files-11

magnetic

perform the same copy operation
allocated to active files.

Structure

tape
they

Level

volumes.
copy

Both

only

the

disk

commands
blocks

DSC's, operation is a cycle, starting with
data
on
a
disk
and
concluding with that data, in compressed form, on another disk or
set of tapes.
The operation can be performed using
one
of
the
following methods:
@

A direct

disk-to-disk

disk-to-tape

transfer

followed

from

tape-to-disk

transfer

DSC

does

not

support data

transfer

For a complete description of
Disk Save and Compress User's

the DSC
Guide.

tape

utility,

tape.
see

the

VAX-11

Table 3-4 lists the devices that can be used with DSC.
Transfers
occur between devices of the same type.
Transfers from a smaller
disk to a larger disk are allowed;
however,
transfers
from
a
larger disk to a smaller one are not.

COMMANDS

USED

BY OPERATORS

Table

3-4

DSC~Supported

Abbreviation

Devices

Device

Class

RKO6

RK07

cartridge

RP06

RP05

disk

RM03

disk

RX01

console

TE16

9-track magnetic

disk

Block-structured

pack

Block-structured

pack

Block-structured

floppy

diskette

Block-structured

tape

Tape

All volumes, except input disks, that DSC uses
with
the
/FOREIGN
gqualifier.
Input
disks
either structured or foreign disks.

must
can

be
be

mounted

Examples

DSC>

MTAO:BACK_FILE/VE=DBAl:

DSC

writes the contents of the disk pack
DBAl
to
a
single
drive
MTAOQ.
After copying the data files from DBAl to
the tape file named BACK FILE, DSC compares the
contents
both
devices
to
make
certain
the
copy
operation
was
successful.
tape

DSC>
In

MTAl:,MTA2:SYSFILE/DENS=1600=DBA0:

the

above

example,

pack
DBAOQO
to
resulting tape
per

file

inch,
named

two
volume

contains
SYSFILE.

DSC
TEl6

writes

tape

set,

all

the
contents
MTAl1l
drives,

recorded

the

data

files

the

and MTA2,
density of 1600

from DBAQ

the

disk
The
bits

tape

COMMANDS USED BY OPERATORS

MCR VFY
3.9

MCR VFY

Checks the readability and validity of Files-11
Files~11] Structure Level 2 volumes.
Files-11

Structure

MCR VFY1l

Level

Structure Level

and

Format

[listfile,scratchdev:=]

indev:/qualifier

Command Qualifiers
None.

Files-11

Structure

MCR VFY2

Level

Format

[listfile,scratchdev:=]

indev:/qualifier

Command Qualifiers
None.

Prompts

If the operator does not enter
the
command
command
line,
VFY
prompts
for
it (VFY>).
until CTRL/Z

typed.

string
on
the
1initial
and continues prompting

If the operator enters the command string on the initial command line,
VFY
executes
the
command,
then
returns
control
to
the
command
interpreter.
Command

Parameters

listfile

Specifies the output listing

file

in the

following

format:

dev:|[ufd] filename.filetype;version

this

displayed

parameter
on

the

omitted,

the

output

1listing

file

terminal.

cratchdev:

Specifies the device on which the scratch file produced by VFY is
to be written.

This parameter

has the

following

format:

dev:

this

parameter

omitted,

SYSS$DISK:

automatically

inserted.

VFY uses the scratch file during the verification
scan
and
the
lost file scan.
The scratch file is created but not entered in a
directory;
hence,
it
1is
transparent
to
the
operator.
The
scratch file is automatically deleted upon termination of the VFY
program.

3-18

COMMANDS

If the
force

USED

system disk is faulty,
the
scratch
file
to

BY OPERATORS

this

parameter

should

used

another
device.
The scratch file
should always be assigned to another volume.
The scratch file is
not used for the /FR and /LI qualifiers.
indev
Indicates
following

the volume
format:

parameter

verified.

This

parameter

has

the

dev:

If
this
inserted.

omitted,

SYSSDISK:

automatically

/qualifier
is
be
performed.
If
no
qualifier
Specifies the function to
indicated,
VFY
validates the structure of the volume mounted on
the specified device.
see
Table 3-5 summarizes the qualifiers;
Appendix A for a complete description of each qualifier.

Table 3-5
File Qualifiers

Qualifier

Format

Meaning

Delete

/DE

Resets marked-for-deletion

Free

/FR

Indicates
the
blocks
on
the
used blocks on
total number of

number
of
volume, the
the
volume,
blocks

List

/LI

Lists the entire
identification

Lost

/LO

Scans

the

entire

file

files

that

are

Read

Check

indicators

index

not

available
number of
and
the
the volume

file

structure
any

for

directory

/RC[:n]

Checks readability of every
block
every file on the entire volume

Rebuild

/RE

Recovers
allocated
file

blocks
that
but
are not

appear
to
be
contained in a

Update

/UP

Allocates
available
to a file

blocks
that
but also have

appear
to
be
been allocated

Validity Check

DEFAULT

Validates the structure of the
mounted on specified device

volume

COMMANDS

USED BY OPERATORS

Description

By default, VFY validates the
structure
of
Level
1
and
Files-11l
Structure
Level
2
operator specifies
a
particular
qualifier,
function of that qualifier.

Only one qualifier can be specified

for

one qualifier

results.

supplied,

an error

Files-11
Structure
volumes.
When the
VFY
executes
the

a command;

if more

than

No other activity
should
occur
on
the
volume
while
VFY
is
executing.
In
particular,
activities
that
create new files,
extend existing files, or delete files should
not
be
attempted
while VFY

is executing

function.

VFY must not be aborted while a /UP, /RE,
or
/DE
qualifier
is
being
processed.
Aborting
VFY
while
it is in the process of
modifying the storage allocation or
index
files
may
seriously
endanger

the

integrity of

that volume.

Examples

MCR VFY2 DMA2:/LO
0.

LOST

FILES WERE

FOUND

The /LO gqualifier scans the
file
structure
of
the
volume
mounted on DMA2 looking for files that are not entered in any
directories.
1In this example, no files were found (that
is,
no

files

were

lost).

MCR VFY2 DMAO:/FR

DMO:

HAS 2768.

BLOCKS FREE,

The /FR
qualifier
available
for
use
24358

24358.

BLOCKS USED OUT OF 27126.

indicates
that
there
are
2768
blocks
on
the
volume mounted on DMAO and that

blocks have been used out of

27126

blocks.

COMMANDS

USED BY OPERATORS

REPLY
3.10

The

command:

Displays

a message

Responds

Designates

Restores

terminal

Closes

the

user

user's

terminal

requests

terminal

current

operator's

nonoperator

operator

log

terminal

status

file

and

opens

new

one

Format

"message-text"

Command Qualifiers

/ABORT=identification-number
/ALL
/BELL
/DISABLE [=(keyword [,... 1)1
/ENABLE [=(keyword [,...] )]
/ [NO] LOG
/PENDING=identification-number
/STATUS
/TERMINAL= (terminal-name [,...])
/TO=identification-number

/USER

Prompts

None.

Command

Parameters

message-text

Indicates the message
terminal(s).

The maximum length of
is exceeded, an error

a message
results.

displayed

128

the

specified

characters;

When a message consists of more than one
be enclosed in double quotation marks.

word,

the

this

message

wuser's

limit

should

Description
The REPLY command is
with
system
wusers,
terminals

log

file.

attached

the

tool

used by
create
and

the

to
the

system,

and

operator to communicate
inhibit operator status on
control

the

operator's

COMMANDS

USED

OPERATORS

When
a
Responding to User Requests:
operator responds using
command,
the
commands:

user
1issues
the
REQUEST
one of the following REPLY

REPLY/ABORT=identification-number

"message-text"

REPLY/PENDING=identification-number

REPLY/TO=identification-number

"message-text"

The /ABORT qualifier indicates that the
wuser
request
has
been
canceled.
The
/PENDING
qualifier places the user in a waiting
state until the request can be fulfilled
or
aborted.
The
/TO
gualifier indicates that the user request has been fulfilled.
When a
on the

user issues the REQUEST/REPLY command,
system console as follows:

OPCOM,

hh:mm:ss:cc

OPCOM,

terminal-name:,

user-—name

the

message

appears

REPLY-ID=identification-number

ACCNT=account
"message-text"

The user cannot enter any commands until
the
operator
responds
using the /ABORT or /TO qualifier or the user aborts the request.
If the operator does not respond and the user does not abort
the
request,
the request is repeated at five minute intervals on the

operator's terminal

until

the operator

Broadcasting Messages to
Terminals:
system
users,
the
operator
issues

replies.

To
contact
one
or
more
one of the following REPLY

commands:

REPLY/ALL

REPLY/TERMINAL=(terminal-name[,...])

REPLY/USER

to
all
terminals
that
are
qualifier sends a message
The /TERMINAL
to the VAX/VMS system and are turned on.
terminals
on
qualifier sends a message to one or more specified
the system.
The /USER qualifier sends a message to all terminals
Generally, to broadcast
an
at which system users are logged in.
message that indicates a system
important
message,
such
as
a
shutdown, the operator specifies the /ALL qualifier.

The /ALL
attached

Status
on
a
Terminal:
Any
Enabling and
Disabling
Operator
attached
to the VAX/VMS
terminal,
terminal,
except
a
remote
an
operator's
terminal.
operating system can be established as
the
command
REPLY/ENABLE
on the
The
operator
simply
enters

designated terminal,

and that terminal can then respond

requests

device

and monitor

When the operator enters the REPLY/ENABLE command,
that

has been enabled by displaying

terminal

the

user

status.

OPCOM confirms
the

following

message:

OPCOM,

dd-mmm-yyyy hh:mm:ss.cc,

OPCOM,

hh:mm:ss.cc,

CENTRAL,

OPER

PRINTER,

TERMINAL

OPERATOR TERMINAL

TAPES,

DISKS,

STATUS,

DEVICES,

(1,2,3,4,5,6,7,8,9,10,11,12)

ENABLED,

OPERATOR=operator-name

operator-name

CARDS,

NETWORK.

COMMANDS

When

the

confirms

operator

that

displaying

the

OPCOM,

the

USED

enters

terminal

BY OPERATORS

the

REPLY/DISABLE

is no longer

command,

an operator

OPCOM

terminal by

following message:

hh:mm:ss.cc,

TERMINAL DISABLED,

OPERATOR=operator-name

To grant partial operator status on a
particular
terminal,
the
operator
includes
one
or
more
keywords
after
the
/ENABLE
qualifier.
For example, to establish a terminal as
an
operator
terminal
that
receives
messages
pertaining
to
mounting
and
dismounting

tapes,

the

operator

types:

$ REPLY/ENABLE=TAPES
$

OPCOM,

1-AUG-1978

18:40:28.37,

OPCOM,

18:40:31.47,

TERMINAL ENABLED, OPERATOR=_TTE3:

OPERATOR TERMINAL STATUS, _TTE3:

TAPES,

OPCOM confirms that

the terminal has

operator

status

for

tape

messages.

To discontinue communication
with
a
particular
facility,
the
operator
includes
one
or
more
keywords
after
the
/DISABLE
qualifier.
For example, to inhibit
an
operator
terminal
from
receiving
messages pertaining to mounting and dismounting disks,
the

operator

types

the

following

command:

$ REPLY/DISABLE=DISKS
OPCOM, 18:44:04.48, OPERATOR TERMINAL STATUS, _TTE5:
CENTRAL, PRINTER, TAPES, DEVICES, CARDS, NETWORK,
OPER(1,2,3,4,5,6,7,8,9,10,11,12)

Note that OPCOM lists the partial operator
to

the

status still

assigned

terminal.

When an operator
disables
operator
status
on
all
terminals,
including
the
system console, OPCOM records all subsequent user
requests in
the
operator's
1log
file
and
responds
to
these
requests with

the

following messsage:

$OPCOM-S-OPRNOTIF,
%$OPCOM-S-OPREPLY,

operator
no

$OPCOM-S-NOPERATOR,

notified,

operator
no

waiting.

response

operator

To determine the operator status of a
operator types the following command:

hh.mm.ss.cc

text

coverage

particular

terminal,

the

$ REPLY/STATUS
Closing the Log File:
To close the current log file and
open
a
new
one,
the
operator
issues
the
REPLY/LOG
command.
All
subsequent messages are recorded in the new log file
for
future
reference.
To
close the current log file without opening a new
one, the operator issues the REPLY/NOLOG command.
All subsequent
messages are not recorded until the operator issues the REPLY/LOG
command.

For more information about the operator's
4.
To
examine
the contents of the log
documented in Chapter 2.

log file,
file, use

see
Chapter
the procedure

COMMANDS

Command

USED

BY OPERATORS

Qualifiers

/ABORT=identification-number
Sends a message to
the
number

and

aborts

the

user

indicated

the

identification

request.

/ALL
Broadcasts

a message

all

terminals

attached

the

system.

/BELL

Rings a bell at each terminal that receives
qualifier
should
be
specified
with
any
qualifiers:

/ALL
/TERMINAL=(terminal-name
/USER
/DISABLE[=(keyword

message.
This
of the following

[,...])

[,...])]

Restores a terminal at which the command
is
specified
to
normal
status
(that

This qualifier

the
one

can

impose

displayed on an operator's
the following keywords:

1limit

terminal,

Keyword

is issued or whose
name
is, nonoperator status).

the

types

specifying

of
one

messages
or

Meaning

CENTRAL

Inhibits
operator
system

receiving messages
identified
as

sent
the

to
the
central

operator

DEVICES

Inhibits receiving
messages
pertaining
to mounting disks and tape volumes

DISKS

Inhibits receiving
messages
pertaining
to mounting and dismounting disk volumes

OPER1

THROUGH

OPER12

Inhibits
operators
OPER12

receiving
identified

messages
as OPER1l,

sent
to
OPER2,...

PRINTER

Inhibits receiving
messages
to printer requests

pertaining

TAPES

Inhibits receiving
messages
pertaining
to mounting and dismounting tape volumes

If no keywords are specified, all
operator
characteristics
disabled.
If
more than one keyword is specified, separate
with commas and enclose the entire list in parentheses.

are
them

COMMANDS USED BY OPERATORS

/ENABLE
[= (keyword

[,...])]

Designates the terminal at which the command is issued to
be
an
operator's terminal.
To designate a terminal to receive messages
from a particular facility, specify one or more of the
following
keywords:

Keyword

Meaning

CENTRAL

Designates

messages

terminal

sent

the

central

receive

system

operator

DEVICES

Designates
a
terminal
to
receive
messages
pertaining
to
mounting disks
and

DISKS

tape

volumes

Designates

terminal

messages
pertaining
to
dismounting disk volumes

OPER1 THROUGH OPER12

receive

mounting

and

Designates
a
terminal
to
receive
messages
sent to an operator identified
as either OPER1, OPER2, ...
OPER12

PRINTER

Designates

terminal

tape

volumes

messages pertaining

TAPES

Designates

messages

dismounting

to printer

pertaining

receive

requests

receive

mounting

and

If no keywords are specified, all
operator
characteristics
are
prescribed.
If
more than one keyword is specified, they should
be separated with commas and the entire list should
be
enclosed
within parentheses.

/LOG
/NOLOG

The /LOG qualifier closes the current log file and
opens
a
new
one.
The
operator can examine the contents of the previous log
file.

The /NOLOG qualifier closes the current log
file
but
does
open
a
new
onhe.
Hence,
no
messages
are recorded until
operator opens another log file.
/PENDING=identification-number

Sends a message to
number

and places

the

wuser

request

indicated
in a wait

the

not
the

identification

state.

/STATUS

Reports the current operator
status
and
all
outstanding
requests for the terminal at which this command was entered.

user

/TERMINAL=(terminal-name[,...])

Broadcasts a message to one or more specified terminals.

/TO=identification-number

Sends a message to
number

/USER

and

completes

the
the

wuser

indicated

the

identification

request.

Broadcasts a message to all terminals at which users
into

the

system.

are

1logged

COMMANDS

USED BY

OPERATORS

Examples

REPLY/ALL

The
on

"SYSTEM GOING

REPLY/ALL
the

command

DOWN

FOR BACK-UP.

broadcasts

a message

PLEASE

all

LOG

OFF."

terminals

system.

REPLY/ENABLE=DISKS

OPCOM,

14-JUN-1978

10:21:56.04,

TERMINAL

ENABLED,

OPCOM,

10:22:01.03,

OPERATOR TERMINAL STATUS,

OPERATOR= TTA3:

_TTA3:

DISKS,

The REPLY/ENABLE command designates
the
terminal
at
which
this
command
1is
issued (terminal TTA3) to be an operator's
terminal that receives messages pertaining
to
mounting
and
dismounting
disks.
The OPCOM message confirms that terminal
TTA3
3.

is established

operator's

terminal.

OPCOM, 13:01:43.22, RALPH ACCT=DOCUMENT REPLY-ID=57
$
$

OPCOM,

TTAl:,

"PLEASE

OPCOM,

13:11:14.55,

REPLY/PENDING=57
REPLY/TO0=57

MOUNT MYFILE

DBA3:"

"YOU'LL HAVE TO WAIT-THERE ARE SEVERAL REQUESTS BEFORE YOUR REQUEST"

REQUEST

COMPLETED,

OPERATOR TTA4:

ID-57

The OPCOM message indicates that a user wants the operator to
place
the
disk
volume
with the visual label MYFILE on the
disk drive DBA3 and
ready
the
device.
The
REPLY/PENDING
command
indicates that the operator can perform the task but
not immediately.
The /PENDING qualifier
places
the
user's
terminal
in
a
wait
state;
that is, the user cannot enter
commands at the terminal.
The
operator
later
mounts
the
specified disk on the specified drive, and sends a message to
the user indicating the request has been fulfilled.
1In
this
example, no message accompanies the REPLY/TO command;
hence,

the

MOUNT

the

task

command
has been

sends a standard
performed.

message

indicating

that

REPLY/STATUS
OPCOM,

15:25:43.73,

CENTRAL,

PRINTER,

OPERATOR TERMINAL

TAPES,

DISKS,

STATUS,

DEVICES,

TTE3:

CARDS,

NETWORK

OPER(1,2,3,4,5,6,7,8,9,10,11,12)

The

REPLY/STATUS

status

for

enabled

TTE3.

command
The

requests

response

receive messages

the

operator

from OPCOM

indicates

from

all

devices.

terminal
that

TTE3

COMMANDS

USED

BY OPERATORS

RUN SYS$SYSTEM:INSTALL
3.11

RUN SYSSSYSTEM:INSTALL

Installs

executable

sections
by
known images

images

known

images,

installing shareable images as
from the system's list of known

creates

permanent

known images,
images.

and

global

deletes

Format

RUN

SYS$SSYSTEM:INSTALL<RET>

file-spec

option,...<RET>

Prompts

After the command line RUN SYSSSYSTEM:INSTALL is entered
1in
response
to
the
system
prompt,
the INSTALL utility program prompts (with an
asterisk) for the file specification of an image file that
is
to
be
installed
as a known image.
This file specification must be followed
by

one

the

options

described

below.

When

file

specification
and
the
option
or
options
associated
with
it are
entered,
INSTALL
responds
with
another
prompt
for
a
file
specification.
Images
that
are activated less frequently should be
installed first;
images that are activated more frequently should
be
installed
1last.
After
the
last file specification and its options
have been entered, the execution
of
INSTALL
can
be
terminated
by
entering <CTRL/Z> or <CTRL/Y> or <CTRL/C> in response to the prompt.
Program

Parameters

file-spec

Specifies 1) the image file that is to be installed
as
a
image, 2) a known image file that is to be replaced by the
version of that file, or 3) a known image
file
that
1is
deleted from the system's list of known images.

known
latest
to
be

INSTALL accepts a full file specification or simply a file
name.
If
the
latter
1is
entered in response to a program prompt, the
following defaults are applied to form a full file specification:

Logical

device

File

type:

File

version:

and directory name:

EXE
highest

SYSSSYSTEM

COMMANDS

USED

BY OPERATORS

Description
The INSTALL utility program is used in installing images as known
images.
Known
images
are
1images
that can have the following
characteristics that set them apart from other images:
e

They

can

shared

They can

quickly

all

users

accessible

the

with

system

minimum

disk

overhead

They can require privileges and yet be executed
who normally have few if any privileges

users

To run the INSTALL utility, a user needs the CMKRNL privilege
to
execute
the
Change
Mode
to
Kernel system service, the PRMGBL
privilege to create permanent global
sections,
and
the
SYSGBL
privilege

manager

the

Commonly,
on
which
installed

create

system

system global

operator

runs

sections.

Usually,

the

system

this program.

images are installed from the system device, the volume
the operating system resides.
1Images can, however, be
from other volumes.

Thus, a system may have more than
one
known
file
1list.
Each
known file list contains the names of known image files that have
the same device, directory, and file type.
Thus all known
image
files
with the device and directory name SYSSSYSTEM and the file
type EXE are included in one known file list.
All
known
image
files with the device and directory name SYSSLIBRARY and the file
type EXE are included in a second known file list.
At start-up time, the number of known
file
1lists
that
can
be
established on a system can be specified by use of the Known File
List Count parameter, which is described in the
VAX-11
Software
Installation Guide.
If images are installed as shared images from a volume other than
the
system
device,
this
volume cannot be dismounted until the
shared images are deleted from the appropriate
known
file
1list
(by
use
of
the
/DELETE
option).
The option /LIST is used to
determine which images must be deleted.
Because the deletion
of
a shared image from the known file list cannot be completed until
the last process using that image exits from it, the
dismounting
of
a volume containing shared images may be delayed for the same
reason.

The system's lists of known images must be restored each time the
system
1is
restarted
after it crashes or is shut down.
Thus, a
command to run the INSTALL
program
is
usually
included
1in
a
system

Refer
images

start-up

command

procedure.

the VAX/VMS System Manager's Guide

and

permanent global

sections.

for

known

COMMANDS

USED

BY OPERATORS

Options

/DELETE
Removes

the

images.

specified

Note

that

file

when

from

shared

the

system's

image

1list

deleted

file 1list, its associated global sections become
its
associated
open
file is closed only after
using that image exits from the image.

from

known

the

known

unavailable
and
the last process

/FULL
Displays statistics about the system resources being used
image files contained in the system's known file lists.

/GLOBAL
Displays
permanent

statistics
and

about

temporary

the

global

system

resources

being

the

used

sections.

/HEADER_RESIDENT
Causes
the
permanently

header
resident

of
in

the
specified
memory.

1image

file

remain

This option is
BACKTRANS.EXE

specified
for
frequently
used
files
such
as
(which
1is
the back translator of DCL commands to
MCR commands).
Keeping the header of an image
file
permanently
in
memory saves one access to disk whenever the file is referred
to,

cost

less

the

names

than

one

page

paged

dynamic

memory.

/LIST
Displays
contained
used with

and

brief

descriptions

the

in the system's known file lists.
This
the option /FULL or /GLOBAL or both.

image

option

files
often

/OPEN
Causes the specified image file to remain permanently open;
this
option
1is
specified
for frequently used utilities, such as SOS
and SHOW.
The cost is about
160
(decimal)
bytes
of
nonpaged
dynamic memory.
If a file is installed /SHARED, /HEADER_RESIDENT,
it
is
open
by default.
If a file from a volume
system device is installed /PRIVILEGED, it is open
A program file can
case, it is opened

be installed
each time the

without
program

/WRITABLE,
than the
by default.
other

being
open;
is activated.

that

/PRIVILEGED[=(privilege-name,...)]
Allows images that need special privileges to
run
by
wusers
who
do
not
normally
have
LOGINOUT.EXE

and

DISMOUNT

are

two

such

be executed
to
be
these
privileges.

images.

The

privileges that an image needs
should
be
included
in
the
optional list of privilege names.
Privilege names are documented
in the VAX/VMS System Manager's Guide.
1If the optional
1list
of
privilege
names
1is
omitted,
all
privileges
are given to the
specified image.

/REPLACE
Replaces the
images
with

specified

specified image file in the system's
the
1latest
version
of that file;

characteristics

the

3-29

image

file

are

list
all

of
known
previously

retained.

COMMANDS USED BY OPERATORS

/SHARED

Allows more than one user to share a single copy of the read-only
file and creates a
image
executable
specified
a
of
segments
permanent global section from a specified shareable image file.
This option can be specified
for
native-mode
executable
image
files
(such
as
PRTSMB.EXE,
the
executable image of the print
symbiont) and for native-mode
shareable
image
files
(such
as
the shareable image of the VAX-11 Common
SYSSLIBRARY:VMSRTL.EXE,
Run-Time Procedure Library).

In
addition,
this
option
can
be
specified
for
some
compatibility-mode utilities, commons, and libraries built by the
RSX-11M Task Builder.
/WRITABLE

Allows more than one user to share the read/write data
areas
of
the
specified
shareable image file;
the /SHARED option must be
specified with

the /WRITABLE option.

This option can be

specified

for

native-mode

FORTRAN

programs

that
have
common
regions.
Such
programs
must
be
1linked
/SHAREABLE.
These common regions
are
accessible
to
any
user
program that maps into them, that is, to any user program that is
linked with the

specified

shareable

image.

In
addition,
this
option
can
be
specified
for
some
compatibility-mode
tasks
built
with read/write common areas by
the RSX-11M Task

Builder.

Examples

RUN SYSSSYSTEM:INSTALL

BACKTRANS/OPEN/HEADER RESIDENT/SHARED

In this example, the executable image of the back
translator
of DCL commands to MCR commands is installed as a known image
file that is permanently open, whose
header
1is
permanently
resident
in memory, and whose read-only segments can be used
by more than one user at a time.
Note that
by
default
the
device
and
directory
name SYSSSYSTEM and the file type EXE
are applied

the

file

name

BACKTRANS.

RUN SYSSSYSTEM:INSTALL

SYSSLIBRARY:VMSRTL/OPEN/SHARED

In this example, the shareable image
of
the
VAX-11
Common
Run-Time Procedure Library is installed as a set of permanent
global sections.
Note that
SYSSLIBRARY,
the
name
of
the
device
and
directory
of this shareable image file, must be
specified.

COMMANDS

USED

BY OPERATORS

RUN SYS$SYSTEM:SYE
3.12

RUN SYSSSYSTEM:SYE

Creates
binary

error

log

report

from

file

containing

error

data

format.

Format

RUN

SYSSSYSTEM:SYE

Prompts

Input File:
input-file-spec
Output File:
output-file-spec
Option:
report-option
Device Name:
device-name[:]
After:
date time
Before: date time
Program

Parameters

input-file-spec
Specifies an

error log file created by the
ERRFMT
process.
default,
SYE
uses
the
highest
version
of
[SYSERR] ERRLOG.SYSfile, which resides on the system disk.

When the user specifies an input file, SYE defaults
any
fields
to
the defaults for FORTRAN unit 2, that is, the
version of SYSSDISK:[default-directory] FOR001.DAT.

By
the

omitted
highest

output-file-spec

Specifies the file to contain the error log
SYE
sends
the output to SYSSOUTPUT, which
terminal.

report.
By
default,
is usually the user's

If the
fields

user specifies an output file, SYE
defaults
any
to
the defaults for FORTRAN unit 2, that is, the
version of SYSS$SDISK:[default-directory] FOR0O02.DAT.
report-option
One of the

following

Roll

C
B

Cryptic
Brief

S
U

Standard
Unknown

By default,
specified.
The five
section.

omitted
highest

report options:

SYE

report

uses

the

options

Roll

are

(R)

explained

option when

below

1in

none

the

other

1is

Description

device~-name]|
:]

Instructs SYE
device
type
all devices.

to
or

report only errors encountered by the
device unit.
By default, SYE reports

3-31

specified
errors on

COMMANDS

date

USED

OPERATORS

time

Instructs SYE to report on errors
occurring
after
a
date
and
time (After:
absolute time) and/or before a
date and time (Before:
absolute time).
By

default, SYE reports
31, 9999.

errors

after

November

17,

1858

specified
specified

and

before

December

Description
The

types
@

Roll

reports
up

that
roll

SYE
up

can

generate

report

are

summary

follows:

errors.

each
erring
device
or
system component covered in
report, the report totals
the
number
of
hardware
software
errors.
The
summary
does
not
include
information about individual errors.
@

the
and
any

Brief - A brief report includes a descriptive, but brief,
entry
for
each error covered in the report.
Each entry
describes, at a minimum, the type of error, the device or
component
that
caused
the
error, the error's sequence
number,

For

and

when

the

error

was

logged.

Cryptic - A cryptic report applies to device errors only.
For
each device included in the report, the report shows
the contents of the device registers every time an
error
occurred.
The device register contents are shown without
explanation.

Standard - A standard report contains an entry for
every
error;
each entry includes all the information gathered
about the error.
In addition, each item
of
information
has a corresponding English explanation.

A standard report, which is 80
for displaying at a terminal.
e

Unknown invalid,

An
and

columns wide,

unknown
error
report
documents
undefined
errors.
Such
errors

errors on devices not recognized by SYE.
error
can
be
classified
as
unknown
information gathered
to
describe
the
corrupted in some way.
See Chapter 2 for
error log file.

information on

how

obtain

suitable

unknown,
1include

1In addition, an
the system
has
been

when
error

copies

the

COMMANDS

USED

BY OPERATORS

SET
3.13

SET

Allows

the operator to establish
process, job, or device.

change

the

characteristics

Format

SET

option

Options
ACCOUNTING
DEVICE

LOGINS
PRINTER

PROTECTION/DEVICE
TERMINAL/PERMANENT
UIC
Prompts

What:

option

Description
A description

each

the

SET

command

options

follows.

COMMANDS USED BY OPERATORS

SET ACCOUNTING
3.13.1

SET ACCOUNTING

Establishes the status of various activities in the account file.
Format

SET ACCOUNTING

Command Qualifiers

/DISABLE [=(keyword,... )]
E ]
[= (keyword,...)
/ENABL
/NEW_FILE
Prompts
None.

Command

Parameters

None.

Description

1logging

also close the current accounting file and open a new one with

The SET ACCOUNTING command enables or
activities

various

disables

the accounting file.

the

SET ACCOUNTING can

incremented by one.

version number

When accounting is enabled, five types of accounting records
be entered
e

Batch job termination

Interactive job termination

Print job completion

Process

failures

completion

For more information about the accounting file, see

System

can

into this file:

the

VAX/VMS

Manager's Guide and the VAX/VMS System Services Reference

Manual.

Command Qualifiers

/DISABLE[=(keyword,...)]

account
Disables the logging of the specified activities in the
Table 3-6 lists and describes the activities that can be
file.
disabled.

E
[= (keyword,...)]
/ENABL

in the account
Enables the logging of the specified activities
that can be
activities
the
describes
and
lists
3-6
Table
file.
enabled.

3-34

COMMANDS

USED

BY OPERATORS

/NEW_FILE
Closes the current
opens a new version

Keywords

Appended

accounting
file
of that file.

Table 3-6
the /DISABLE

Keyword

<called

and

ACCOUNTNG.DAT,

/ENABLE

and

Qualifiers

Meaning

BATCH

All

batch

jobs

are

INTERACTIVE

All

LOGIN_FAILURE

All

failures

are

All

jobs

recorded

PROCESS

All

processes

interactive
termination

are
are

recorded

Jjobs

are

job

termination

recorded

job

recorded

Examples

$ SET ACCOUNTING/ENABLE=(BATCH,INTERACTIVE)
The

SET ACCOUNTING/ENABLE command requests that all batch
interactive
jobs
be
recorded in the accounting file at
termination.

and

job

§$ SET ACCOUNTING/NE
FILE
W
This command closes
new version of it.

the

current

3-35

accounting

file

and

creates

COMMANDS USED BY OPERATORS

SET DEVICE
3.13.2

SET

DEVICE

Establishes a line printer
or
terminal
as
a
spooled
establishes the status of the error log facility.

device;

Format

SET DEVICE

device-name]|:]

Command Qualifiers

/ [NO] SPOOLED [= (queue~name|[:] ,intermediate-~disk-name[:])]
/[NO]ERROR_LOGGING
Prompts

Device:
Command

device-name|:]
Parameters

device-name|[:]

Specifies the name of the device whose spooling or error
logging
status
1is to be changed.
The device must be a line printer or a
terminal if its
spooling
status
1is
to
change;
or
a
disk,
magnetic
tape,
or
DMC-11
if
its
error
logging status is to
change.

Description

When the /SPOOLED qualifier is used, program
output
1is
written
onto
an
intermediate disk rather than directly to a terminal or
line

printer.

Once a device has been set spooled to a
device cannot be dismounted until it is

disk,
the
intermediate
set nospooled.

When the /ERROR LOGGING qualifier is
wused,
all
reported
on
the
device
on which error logging
recorded in the error log file.
Command

error
messages
is enabled, are

Qualifiers

/SPOOLED [= (queue-name[:] ,intermediate~disk-name[:])]
/NOSPOOLED[=(queue-name[:] ,intermediate~-disk—-name([:])]
Controls whether files will be spooled to an intermediate disk.
The queue name indicates
queued.
If
the
queue

the print
name
1is

gqueue
to
which
a
file
1is
not
supplied, it defaults to

SYSSPRINT.

The intermediate disk name
identifies
the
disk
to
which
spooled
files are written.
If the intermediate disk name is
supplied, it defaults to SYS$DISK.

the
not

The intermediate disk must be mounted before files can be written
onto

it.

No channels can

characteristics

are

assigned
changed.

device

once

its

spooling

COMMANDS

USED

BY OPERATORS

/ERROR_LOGGING

/NOERROR_LOGGING
Controls

whether

device

file.
Error
and

logging

the

can

errors

currently

will

enabled

logged

for

DMC-11.

the

disks,

error

magnetic

log

tapes,

Examples

SET

DEVICE/SPOOLED=(LPAO:)

LPAQ:

this command, the printer queue
intermediate
disk before the jobs

Because

disk
2.

SET

The

intermediate

defaults

disk

SET

DEVICE

command

DBB2

specified,

SYSSDISK.

DEVICE/ERROR _LOGGING

reported

was

LPA0
is
spooled
to
an
in that queue are printed.

logged

the

intermediate

DBB2:

requests
in

the

that
error

all
log

device

file.

errors

COMMANDS USED BY OPERATORS

SET LOGINS
3.13.3

SET

Controls

LOGINS

the

number

users

that

can log

into

the

system.

Format

SET

LOGINS

Command Qualifiers
/INTERACTIVE[=n]
Prompts

None.

Command

Parameters

None.

Description

The SET LOGINS command limits the number of users
access

the

who

<can

gain

system.

The SET LOGINS command is not retroactive;
that
1is,
all
users
logged
into the system before the operator issues the SET LOGINS
command are not affected by it.
However, once the limit
set
by
the
operator is achieved, no more users can log in to the system
until

someone

logs

out.

If the operator does not specify a value for
command displays the following information:

Interactive limit=m,

Current

the

SET

LOGINS

interactive value=n

Command Qualifiers
/INTERACTIVE=n

Sets the number of
the

interactive users allowed

gain

access

five

interactive

system.

Examples

SET LOGINS/INTERACTIVE=5

The SET LOGINS command specifies that only
users can be

logged

the

system.

SET LOGINS/INTERACTIVE

Interactive 1limit=15,

Current interactive value=4

In this example, the SET LOGINS command
indicates
that
the
maximum
number of users allowed on the system is fifteen and
that the number of users currently logged in is four.

COMMANDS

USED

BY OPERATORS

SET PRINTER
3.13.4

SET

Establishes

PRINTER

the

characteristics

the

specified

line

printer.

Format

SET PRINTER printer-name{:]
Command

Qualifiers

Defaults

/ [NO]CR

/NOCR

/[NO]FF

/NOFF

/ [NO] LOWER
/LP11
/PAGE=n
/UNKNOWN
/ [NO] UPPER
/WIDTH=n

/NOLOWER

/LAl1l
/LA180

/PAGE=64
/UPPER
/WIDTH=132

Prompts

Device:
Command

printer-namel:]
Parameters

printer-name|
:]
Specifies
the
characteristics
Command

name
set

of
or

the

printer

that

will

have

its

<carriage
return;
on which line feeds

this
imply

modified.

Qualifiers

/CR
/NOCR
Controls whether the printer
characteristic
1is
set
for
carriage returns.
The

default

qualifier

outputs
a
printers

/NOCR.

/FF
/NOFF
Controls

The

whether

default

the

qualifier

printer

/FF.

performs

form

feed.

/LAl11l

Sets

the

printer

type

that

LAll

/LA180
Sets

the

printer

type

that

LA180

line

printer.

COMMANDS USED BY OPERATORS

/LOWER
/NOLOWER
Controls whether
the
alphabetic letters.

When

the

operator

alphabetic

printer

specifies

characters

are

prints

the

1lowercase

/NOLOWER

translated

and

uppercase

gualifier,

all

uppercase.

The /NOLOWER qualifier is complementary to the
/UPPER
qualifier
that
is,
the
/LOWER
qualifier
1is
equivalent to the /NOUPPER
qualifier.

/LP11

The default qualifier

is /NOLOWER.

Sets

to that of an LP1ll

the printer

type

line printer.

/PAGE=n

Establishes the maximum number of lines
that
the
1line
printer
prints
on an output page;
the number of lines can range between
0

and

The

255

(decimal).

default value

/UNKNOWN
Sets

the printer

lines

per

page.

unknown printer

type.

/UPPER

/NOUPPER

Controls whether
to

the printer

translates all

lowercase

characters

uppercase.

When the /UPPER qualifier is specified, the
printer
performs
a
conversion
from lowercase to uppercase characters.
The /NOUPPER
qualifier is complementary to the /LOWER qualifier.
The default qualifier
/NOLOWER qualifier.

/UPPER,

which

1is

equivalent

/WIDTH=n

Establishes the number of chLaracters to
be
printed
line,r
where
the
width,
n,
can
range
between
0

the

per
output
and
65535

(decimal)
.

The default value

132

characters per

line.

Examples

SET PRINTER/PAGE=100/WIDTH=80

LPAO:

The SET PRINTER command establishes the
size
of
an
output
page as 100 lines and the width of a line as 80 characters.
2.

SET PRINTER/LAll

LPBO:

The SET PRINTER command establishes the line printer LPBO
as
an LAll printer and sets the default characteristics for that
printer

type.

SET PRINTER/LOWER LPAO:

The SET PRINTER command requests
enabled on line printer LPAQ.

that lowercase

printing

COMMANDS

USED

BY OPERATORS

SET PROTECTION/DEVICE
3.13.5

SET PROTECTION/DEVICE

Establishes

the protection to be applied to the
non-file-structured device.
The protection for
the type of access available to system users.

specified
the device

shareable,
thus limits

Format

SET

PROTECTION[=code] /DEVICE

Command

device-name/|:]

Qualifiers

/OWNER UIC=uic

Prompts

File:

device-name][:]

Command

Parameters

code

Establishes the protection
code
defines the user and
The code should
described below

code
type

for
a
device.
The
protection
of access available for the user.

be
specified
according
to
the
syntax
under "How to Specify Protection Codes."

If the operator does not specify a protection code,
checks
are
made and all users are allowed to gain
device.

device-name[:]
Specifies
modified.
device.

rules

no protection
access to the

the name of the device whose protection is to be set or
The
device
must be a shareable, non-file-structured

Description
The command qualifier
change the protection
How

users
®

Specify

four

/DEVICE
applied

Protection

must be
specified
to the device.

Codes:

Devices

can

set

accessed

categories:

System

octal

(generally,

all

users

who

have

system

group

numbers

managers,

system

through

programmers,

and

operators)
®

Owner

command
®

Group

UICs
®

World

as
--

the

and
all

the
all

UIC

the

therefore
users

owner
users

who

person

owns
have

the

who

the

issued

the

SET

PROTECTION

device

the

same

group

number

their

device
not

fall

into

the

directory

issue

the

SET

as [370,10].
contained in

The
that

command.

Examples

SET UIC

[370,10]

This command establishes the operator's UIC
operator
can
now read or modify any files
directory.

SET UIC

[214,4]

SET DEFAULT

The SET
DEFAULT

[ANDERS]

UIC sets the
command sets

operator's
the default

UIC

directory

[214,4];
name to

the

SET

[ANDERS].

COMMANDS USED BY OPERATORS

SHOW TERMINAL/PERMANENT
3.14

SHOW TERMINAL/PERMANENT

Displays

the

current

permanent

characteristics

the

specified

terminal.
Format

SHOW TERMINAL/PERMANENT

[device-name:]

Command Qualifiers
None.
Prompts

None.

Command

Parameters

device-name:

Specifies
the
name
of
the
terminal
whose
permanent
characteristics
are
to be displayed.
1If, however, the terminal
is allocated, the system cannot display the characteristics.

If
the
operator
does
not
include
a
device
name,
the
characteristics
of
the terminal at which the command was issued
are displayed.

Description

When the operator issues the SHOW TERMINAL/PERMANENT command, the
status
of
each
of
the
permanent
settable characteristics is
displayed.
To
use
the
SHOW
TERMINAL/PERMANENT
command,
the
operator needs PHY IO or LOG_IO privilege.
Example

SHOW TERMINAL/PERMANENT

TTFl:
/VT52, WIDTH=80, PAGE=16, OWNER=SELF
SPEED=(9600.9600), CRFILL=0, LFFILL=0, NOPARITY
INTERACTIVE, ECHO, TYPEAHEAD, NOESCAPE, NOHOSTSYNC,
LOWERCASE, TAB, WRAP, SCOPE, LOCAL, NOHOLDSCREEN,
NOEIGHTBIT, BROADCAST, NOREADSYNC
This

SHOW TERMINAL/PERMANENT

settable

characteristics

for

command

displays

terminal

TTF1l.

the

TTSYNC,

permanent

COMMANDS

USED

BY OPERATORS

START/QUEUE
3.15

START/QUEUE

Starts

restarts

specified

queue.

Format

START/QUEUE
Command

queue-name/|:]

Qualifiers

Defaults

/BACKSPACE=n
/BATCH
/ [NO] BURST
/[NO]DISABLE_SWAPPING
/[NO]ENABLE_GENERIC_PRINTING
/ [NO] FLAG
/FORMS TYPE=n
/ [NO]GENERIC
/ [NO] NEXT
/JOB_LIMIT=val
/PRIORITY=val
/TERMINAL
/TOP_OF FILE

/BACKSPACE=1
/NOBURST

/NODISABLE_SWAPPING
/ENABLE_GENERIC_PRINTING
/NOFLAG
/NOGENERIC
/NONEXT
/JOB_LIMIT=1
/PRIORITY=4

Prompts

Queue:

queue-namef:]

Command

Parameter

queue-name/|
:]
Specifies

the

name

queue

can

the

queue

started,

started

restarted.

Description
Before

INITIALIZE/QUEUE
can
Command

started

command.

and

must

However,

stopped

initialized

once

wusing

initialized,

the

queue

necessary.

Qualifiers

/BACKSPACE][
:n]
Backspaces

This

pages

then

qualifier

resumes

printing.

used

batch

queue.

header

page

Currently

restarting

limited

queue.

/BATCH
Indicates

that

this

/BURST
/NOBURST
Controls

whether

burst

printed

for

each

job.
Use

the

/BURST

perforations;
a

stack

qualifier
hence,

paper.

the

Using

page
this

default

qualifier

/NOBURST.

3-53

qualifier

listings.
The

a header

header

page

over

visible

from

simplifies

the
the

paper
side

separating

COMMANDS USED BY OPERATORS

/DISABLE SWAPPING
/NODISABLE_SWAPPING
Controls whether batch
Jjobs
swapped in and out of memory.

The default qualifier

executed

from

the

queue

can

is /NODISABLE SWAPPING.

/ENABLE_GENERIC_PRINTING
/NOENABLE_GENERIC_PRINTING

Controls whether files gueued to a generic queue can be placed in
a physical queue (that is, a device-specific queue) for printing.
By default, generic printing
physical device is enabled.

/FLAG
/NOFLAG

Controls whether a header page
first file in each print job.
The default gqualifier

from

queue

associated

with

is printed at the beginning of the

is /NOFLAG.

/FORMS TYPE=n

Specifies the forms type for the specified queue.
Once
a
queue
has
been
assigned
a forms type, all jobs in that queue that do
not conform to that forms type are placed in a holding state.

Specify the forms type using a numeric value or
an
alphanumeric
code.
Codes for forms type are installation defined.
/GENERIC
/NOGENERIC

Controls whether
any
available

files placed in a queue can be
printed
out
on
line
printer
that
has
<correctly matching

characteristics.

If the qualifier /GENERIC
nongeneric

is not used,

the queue

is by default

queue.

/JOB_LIMIT=val

Indicates
the
number
of
batch
Jjobs
that
can
be
executed
concurrently
from the queue.
The default value of the job limit
is

/NEXT
/NONEXT

Controls whether the current job will be printed when
is restarted.
The default is the /NONEXT qualifier.

This qualifier

used

in restarting

the

queues.

/PRIORITY=val

Indicates the priority at
which
Jjobs
are
initiated
from
queue.
The default value of the priority of a gueue is 4.

/TERMINAL
Indicates

that

this

/TOP_OF FILE

terminal

dqueue

the

queue.

Prints, starting from the beginning of the job, the job that
was
being printed when the queue was stopped.
This qualifier is used
in

restarting

queue.

COMMANDS

USED

BY OPERATORS

Examples

$ START/QUEUE/BATCH SYSSBATCH
This command starts the batch
queue
/BATCH qualifier indicates that this

$ STOP/QUEUE
LPAO:
$ START/QUEUE/TOP
OF FILE
The

STOP/QUEUE

command

queue

LPAO.

resumes
started

operation;
again from

The

LPAO:

suspends

Then,

named
SYSS$SBATCH.
is a batch queue.

the

operation

the

physical

START/QUEUE/TOP_OF
FILE

however, the job
the beginning.

currently

command
printing
is

$ INITIALIZE/QUEUE LPAO:
$ START/QUEUE/NOFLAG
LPAO:
The INITIALIZE/QUEUE
command
initializes
the
gqueue
named
LPAO.
The
START/QUEUE
command then starts the queue.
The

/FLAG qualifier
in the queue.

requests

that

a header

page precede

each

job

COMMANDS USED BY OPERATORS

STOP/ABORT
3.16

STOP/ABORT

The STOP/ABORT command aborts a job that is currently being printed.
Format

STOP/ABORT

printer-name|
:]

Command Qualifiers
None.
Prompts

Device:
Command

printer-namel:]
Parameters

printer-namef:]

Specifies the name of the printer queue

which

the

job

was

entered.

Description

The operator uses this command only to abort the printing of jobs
entered in the system output queues, that is, the line printer or
terminal

queues.

being
<currently
Jjob
the
STOP/ABORT,
When the operator issues
printed is terminated, and the next job in the queue is dequeued.
Example

$ STOP/ABORT LPAl:

This command
printer

LPAl.

aborts

the

job

currently

printing

line

COMMANDS

USED

BY OPERATORS

STOP/ENTRY
3.17

STOP/ENTRY

Deletes

entry

from

batch

queue.

Format

STOP/ENTRY=entry-number
Command

queue-name|
:]

Qualifiers

None.

Prompts

Queue:

queue-name]|:]

Command

Parameters

entry-number

Specifies the
batch queue.

entry

number

the

job

deleted

from

the

queue-name|
:]

Specifies

the

name

the

queue

in which

the

job

was

entered.

Description
This command is used to terminate the execution of
a
batch
while
it is running.
This command cannot, however, delete a
while it is waiting to be executed.

job
job

Example

STOP/ENTRY=230

The

STOP/ENTRY

entry

number

SYSSBATCH

command

230

the

deletes

the

batch

gqueue

job

associated

SYSSBATCH.

with

the

COMMANDS

USED

BY OPERATORS

STOP/QUEUE
3.18

STOP/QUEUE

Suspends or

controls operations of

specified output or

batch queue.

Format

STOP/QUEUE

Command

gueue-name]|:]

Qualifiers

Default

/ABORT

;

/ [NO] NEXT

/NONEXT

Prompts

QUEUE:

gueue-name]|:]

Command

Parameter

qgueue~name/|
:]

Specifies

the

name

the

queue

stopped.

Description

When the operator issues this command without
current gqueue operation is placed in a paused

any qualifiers,
state.

To delete a queue, the operator must first stop the
queue
this command with the /NEXT qualifier appended to 1it.
Command

the

using

Qualifiers

/ABORT
Aborts a job that is
the
gqueue
1is
then

STOP/QUEUE/ABORT
/NEXT
/NONEXT
Inhibits

further

currently being printed;
the
next
job
in
started
without
a
pause
or
stop.
The
command is equivalent to the STOP/ABORT command.

dequeuing

from

the

specified

queue.

When

the

/NEXT
qualifier
1is
specified,
the
<current
Jjob is allowed to
complete before the queue is stopped.
When the /NONEXT qualifier
is
specified,
the
dqueue
1is
stopped immediately.
The default
qualifier

/NONEXT.

Examples

$ STOP/QUEUE/ABORT
This
next

LPAOQ:

command aborts the job currently printing
job in the queue is then started.

$ STOP/QUEUE/NEXT

on LPAO.

The

LPBO:

The STOP/QUEUE/NEXT command inhibits further printing of jobs
in
the queue LPB0;
however, the current job is permitted to
complete.

COMMANDS

OPCOM,

01:15:34.28,

STOP/QUEUE

The

OPCOM message

suspend

and

DEVICE

OPERATORS

OFFLINE,

LPAO:

LPAO:
indicates

the
ready
state;
malfunctioning.
The

printer

USED

the

operator

queue

find

that

out

line

the

issues

the

associated

what

printer

is,

with

wrong.

LPA0

line

not

printer

STOP/QUEUE
the

command

malfunctioning

COMMANDS USED BY OPERATORS

STOP/REQUEUE
3.19

STOP/REQUEUE

Stops the printing of the job currently being printed and places
job at

the

end

the

that

output queue.

Format

STOP/REQUEUE

queue-name]|:]

Command Qualifiers
None.

Prompts

Queue:

gqueue-namel:]

Command

Parameters

gueue-name|
:]

Specifies the name of the queue

to be stopped.

Description

When the operator requeues a job,

that job is placed at

the gueue with its priority level lowered to 1.

in the queue is immediately dequeued for printing.

the

end

The next job

paper
of
out
This command is useful when the line printer runs
or when a large job of low priority
it is printing a job;
while
the
queue
in
Jjobs
is currently printing and one or more other

must be printed

immediately.

Example

STOP/REQUEUE

LPBO:

LPBO,
This command suspends the current print
operation
on
the job that was currently printing at the end of the
places
queue, and resumes the print operation.

CHAPTER 4

THE OPERATOR'S LOG

FILE

The operator's log file records the occurrence of events that
are
of
interest
to
the
system
managers and operators.
The following list
summarizes all the messages recorded in the operator's log file:
e

Initialization of

Status

Terminals

Time

stamps

User

requests

changes

the

for

enabled

and

operator's

devices
and

log

attached

file
to

the

system

disabled

operator

replies

These messages are produced by the
Operator's
Communication
Process
(OPCOM)
and
are
preceded
by
the
1label Opcom.
These messages are
explained in detail in the following sections.

4.1

OVERVIEW OF THE

OPERATOR'S

LOG

FILE

The operator's log file (OPERATOR.LOG)
the
[SYSMGR]
directory.
This
file
printed

when

resides on the system
disk
1in
is
in ASCII format and can be

needed.

When the system is shut down for whatever reason, then
rebooted,
the
operator's
log
file is purged;
only the two most recent versions of
the log file are saved.
Hence, if the manager
wants
to
maintain
a
complete
record of this file, the operator should print a copy of the
log file regularly.
See Chapter 2 for information on
how
to
obtain
copies of the operator's log file.
Figure 4-1
operator's

4.2

When
is

shows some
log file.

INITIALIZATION

the

operator

<closed

subsequent

and

the

typical

messages

that

appear

1in

the

MESSAGES

issues

the command

new version

OPCOM messages

are

REPLY/LOG,

that

recorded

file

this

the

current

created

new

log

and

1log

opened.

file.

file
All

THE OPERATOR'S

When

new

log

file

created,

initialization message.
Opcom,

dd-mmm-yyyy,

The initialization
file was created.

This

the

line

hh:mm:ss,cc,

line

tells

FILE

first message

appears

LOGFILE

the

LOG

the

INITIALIZED,

operator

when

recorded

following

format:

OPERATOR=operator-name

and

whom

the

log

Opcom,
Opcom,
Opcom,

9-JUL-1978
9-JUL-1978
9-JUL-1978

18:52:10.61,
19:22:13.85,
19:40:37.95,

Logfile initialized, operator=_ OPA2:
Logfile time stamp
Terminal enabled, operator=_TTAl:

Opcom,

9-JUL-1978

19:40:50.31,

Terminal

Opcom,
Opcom,

9-JUL-1978
9-JUL-1978

20:12:13.78,
20:47:13.78,

Logfile
Logfile

21:17:26.84,

Terminal

Opconm,

9-JUL-1978

Opcom,

21:18:42.77,

SWORDS

Opcom,

_TTAl:,

YOU

"ARE

21:22:31.65,

PARDON

TTAl:,

YOU

Opcom,

06:58:57.70,

Device

offline,

LPAQ:

Opcom,

06:59:29.70,

Device

offline,

LPAO:

Opcom,
Opcom,

07:00:01.70,
07:00:33.70,

Device
Device

offline,
offline,

LPAO:
LPAO:

Opcom,

07:01:05.70,

Device

offline,

LPAO:

Opcom,

11:31:19.70,

Device

offline,

LPAO:

Opcom,
Opcom,
Opcom,
Opcom,

11:31:51.70,
14-JUL-1978
13:59:41.88,
TTC3:, "TEST

Opcom,

15:26:42.73,

4.3

DEVICE

The VAX/VMS

STATUS

I/0

explicitly

Accnt=DOCUMENT

Device offline, LPAOQ:
13:59:30.27, Terminal
SPARLP
Accnt=VMS

Device

4-1

Reply-1ID=0

The

offline,

enabled,

operator=_TTC3:

CRAQ:

Operator's

Log

File

(OPERATOR.LOG)

messages

OPCOM

concerning

MESSAGES

send

device

A
change occurs and is recorded when a device goes
offline,
the
OPCOM
message
1is
written
into
the
file
at
30-second
intervals
until
the
device is

returned

online

The device status message
following format:
Opcom,

operator=_TTA2:

READY?"

drivers

status
changes.
offline.
Once
operator's
1log

enabled

READY?"

Opcom,

Figure

operator=_ TTAl:

stamp
stamp

Accnt=DOCUMENT

Opcom,

"ARE

disabled,

time
time

hh:mm:ss,cc,

status.

appears

DEVICE

the

OFFLINE,

operator's

log

file

the

device-name

The devices for which this message can appear are card
readers,
line
printers,
magnetic
tapes
and
networks.
See the DECnet-VAX User's

Guide

for

information.

THE OPERATOR'S

4.4

The

TERMINAL

operator

issuing

ENABLE

AND DISABLE

designates

the

command

Opcom,

dd-mmm-yyyy

terminal

This message tells the
an operator's terminal

the
request
terminal and

hh:mm:ss,cc,

operator's

the

desired

terminal

terminal.

by
displaying
the
in the operator's log

Terminal

operator
and when

FILE

MESSAGES

REPLY/ENABLE

operator program confirms
message at the operator's

LOG

enabled,

The

following
file:

operator=operator-name

which terminal has been
it was established.

established

If a terminal has been designated as
an
operator's
terminal
for
a
particular
function,
OPCOM
displays
which
function
it
is.
For

example,
displays

if the operator issues
the following message:
Opcom,

1l4-aug-1978

Opcom,

10:25:38.82,

the

command

10:25:35/74,

operator

REPLY/ENABLE=TAPES,

terminal

enabled,

status,

OPCOM

operator=

TTEl:

TAPES,

OPCOM confirms that the
terminal
1is
established
terminal
and indicates that the terminal can only
to requests concerning mounting and dismounting of
The

terminal

restored

which

normal,

REPLY/DISABLE.

The

REPLY/ENABLE
that

1is,

operator

command

program

confirms

longer an operator terminal by displaying
operator's terminal and in the operator's
Opcom,

dd-mmm-yyyy

hh:mm:ss.cc,

Terminal

the
log

been

that

tells

the

operator

which

nonoperator

status

and

when

transition

terminal

operator's
and respond

tapes.
issued

status

the

can

command

terminal

message

the

following
file:

disabled,

This message

the

has

nonoperator,

as
an
receive

operator=operator-name

has

been

restored

occurred.

If, however, a terminal is designated as an
operator's
terminal
and
only
partial
operator status is taken away from it, OPCOM displays a
status message.
This message tells the operator
which
requests
the
terminal
can still receive and respond to.
This message is displayed
at the operator's terminal and in
the
operator's
1log
file
in
the
following format:
Opcom,

hh:mm:ss.cc,

Operator

terminal

status,

operator=operator-name

status-report

For

example, if an operator designates a
terminal
as
an
terminal
that receives messages concerning magnetic tapes,

operator

Later,

receive

REPLY/DISABLE=TAPES

09:23:45.32,

DISKS,

OPER(1)

respond

tells

operator

the

to messages

relinquishes

concerning

command,

Opcom,

This message
can

the

messages

OPCOM

Operator

operator
about

tapes.

When

returns

terminal

that

disks

the

4-3

terminal's

the

operator

ability

issues

the

following message:

status,

terminal
and

the

operator's
disks, and

operator=

TTA3

operator

still

TTA3:

receives

and

THE OPERATOR'S

4.5

TIME

STAMP

LOG

FILE

MESSAGES

A time stamp
message
1is
recorded
at
30-minute
intervals
1in
the
operator's log file.
This message serves as an indicator as to when a
system crash occurred.
But, because the message only appears every 30
minutes, it can only approximate when the crash occurs.

A time

stamp message

Opcom,

4.6

the

dd-mmm-yyyy hh:mm:ss.cc,

USER REQUEST AND OPERATOR REPLY

To talk to
either the
If
in

appears

the
the

log

file

logfile

the

time

following

format:

stamp

MESSAGES

the operator the user issues
/REPLY or /TO qualifier.

the

user issues a REQUEST/REPLY command,
operator's log file in the following
Opcom,
Opcom,

REQUEST

command

that request
format:

1is

specifying

recorded

hh:mm:ss.cc, user-name Accnt=DOCUMENT Reply-ID=identification-number
terminal-name, "message-text"

This message tells the operator who sent the
message,
message
was
sent, the identification number assigned
and the message itself.

If the user issues a REQUEST/TO command,
the
operator's
1log
file
in
the same
without the identification number.

the
time
the
to the message,

the request
1is
recorded
format as a REQUEST/REPLY

in
but

When the operator responds to a user's request, specifying either
/ABORT qualifier or the /TO qualifier, the response is recorded in
operator's log file in the following format:

the
the

Opcom,

hh:mm:ss.cc,

operator-response,

operator=operator-name

This message indicates
how
the
operator
responded
to
the
user's
request, when the operator responded, and which operator responded.

When the operator responds
to
a
user
request
using
the
/PENDING
qualifier,
the
response
1is
not recorded in the operator's log file
because the request has not yet been completed (that is,
the
request
has

not

been

fulfilled

aborted).

When a user sends a REQUEST/REPLY and the operator
has
disabled
all
terminals
as
operator's terminals, OPCOM records all subsequent user
requests in the log file in the format
shown
above,
but
returns
a
message
to the users indicating that there is no operator coverage at
this

time.

All

other

OPCOM

responses

commands,

involving the REPLY/ENABLE, REPLY/DISABLE,
not logged in the operator's log file.

and

except

responses

REPLY/LOG commands,

are

APPENDIX

QUALIFIERS

APPENDED TO

THE

MCR VFY

COMMAND

This appendix presents a complete description of
all
the
qualifiers
that
can
be
appended
to the command string for the VERIFY command.
Section
A.l1
describes
the
validity
check
which
is
the
default
qualifier.
Section A.2 describes the remaining file qualifiers.
See

Table

A.l1

The

3-5

VALIDITY

validity

volume
all the

Chapter

for

the

summarized

list

qualifier)

validates

the

check

(no

for
1.

running
The

the

volume

validity

the

volume.

The

volume

may

The

not

When

the
printed.

must

mounted

write-protected

if:

the

system volume;

required

scratch

This

file

1is

After

the

have
given

been
file

volume

has

nn,mm

Files-11

another

Reporting

error.

the
results
below.

been

verified,

and

the

normal

printed,
error conditions are reported.
are preceded by a file identification line

FILE

directed

check is completed, a
1listing
of
output is described in Section A.l.1l,

Error

marked

volume.

validity

File

file

file header are
to that file).

check:

checked

structured

file-structured

the

structure

mounted on the specified device.
This feature entails reading
file headers in the index file and ensuring that all the
disk

referenced
in
the map area of each
allocated in the bit map (that is, allocated

A.l1.1

qualifiers.

CHECK

blocks

Rules

This

line

formatted

filename.filetype;version

the

file

the

system

identification

filename

1is

the

filename.

.filetype

the

filetype

(that

is,

OBJ

messages

follows:
OWNER

number

file-creation

output

All errors for a
that
identifies

[g,m]

assigned

the

time.

for

object

file).

file

QUALIFIERS APPENDED TO THE MCR VFY COMMAND

sversion

is the version number

[g,m]

is the UIC

the

that owns the

This file

identification line

following

messages:

file.

followed

I/0 ERROR READING FILE HEADER-ERROR CODE

Failed to read
BAD

FILE

the file header

for

MUTLIPLE

one

the

-32

the specified file

ID.

HEADER

Software checks on the validity of the
the

file.

header

has

been

ALLOCATION

file header

indicate

that

corrupted.

n,m

The
specified
(double
precision)
1logical
block
number
is
allocated
to more than one file.
If this error occurs, a second
pass, which is automatically taken, will indicate all files
that
share
each
multiply-allocated
block.
The second pass is taken
after all file headers have been checked (see Section A.1.3).
BLOCK

MARKED

FREE

n,m

The specified logical block number is allocated to the
indicated
file but is not marked as allocated in the storage allocation map
(see
BAD

Section A.l1.4).

BLOCK

NUMBER

n,m

The specified block number was found in the header for this
file
but
1is
1illegal for the device (out of range).
This indicates a

FILE

corrupted

file

IS,MARKED

FOR

header.
DELETE

A system failure occurred while
the
specified
file
was
being
deleted.
The
deletion
was
not
completed and the file header
still

HEADER MAP

exists

(see Section A.l.2).

OUT

SYNC

An error
file

in the

header map area which

The last error message
that

also

indicates

file,

for

the

file

followed by a summary line

MULT=nn,

MULT

is the number

of multiple block allocations.

is the number

been

BAD

for

follows:

SUMMARY:

FREE

corrupted

header.

FREE=nn,

BAD=nn.

blocks marked

free

that

should

have

allocated.

the number

bad

retrieval

pointers

the

file

header.

If the output for VFY is
directed
to
a
terminal
device,
and
the
operator does not wish to see all the error messages for a given file,
entering
for that

CTRL/O terminates the listing of all further
error
file, that is, all messages but the summary line.

messages

QUALIFIERS

A.1.2
If

Files
file

has

been

Restoring
To

marked-for-delete

restore

using
For

MCR VFY

COMMAND

Marked-for-Delete

completed, the operator
to recover the space it
when the system crashes

APPENDED TO THE

but

the

deletion

process

not
file
only

File
a

the

was

can either restore the file or delete the
was occupying.
This
situation
occurs
during file processing.

file

MOUNT

marked-for-delete,

command

with

mount

the /UNLOCK

the

disk

qualifier

volume

specified.

example:

$ MCR VFY2

DMAl:/UNLOCK

Then, run VFY
specifying
the
/DE
qualifier
to
reset
the
marked-for-delete indicators in file headers.
Once the delete
indicator has been reset, run VFY specifying the /LO qualifier
to

scan

The

the

entire

deletion

process

portion at the end
can be detected by
PIP/FULL command.

Deleting

Files

that

PIP,

once

file

structure.

may

of
a

have

proceeded

partially

the file may be missing.
This
directory
1listing
obtained

and

condition
with
the

File
are marked-for-delete
their
File
1ID
has

can be deleted
been obtained

directly
with
a validity

via

check.
The File ID appears as the first
entry
in
the
file
identification
1line
which
precedes each list of file errors
(see Section A.1.1).
The following
example
illustrates
how
the File ID is used with PIP to delete a file:
Example:

$ MCR PIP /FI:12:20/DE
In

this

the

example,

the

system

device.

PIP

FAILED

since

the

file

storage

A.1.3

Deletion

MARK

File
the

FILE

however,

have been
specified

allocation

with

issues

system denies

marked-for-delete;

Once files
qualifier

file
PIP

12,20

following

FOR

DELETE-NO

the

existence

the

file

deleted

error

SUCH

FILE

files

completely

from

message

already

deleted.

restored or deleted, run VFY with the /RE
to assure the consistency of the volume's

map.

Multiply-Allocated

Blocks

If the file structure contains multiply-allocated blocks, delete files
until
there
are
no
more
such
blocks.
An automatic rescan of the
volume
identifies
which
files
share
which
blocks.
Using
this
information,
the operator can determine which files can be saved and,

using
Be

the

PIP delete

function,

delete

the

rest.

careful when deleting multiply-allocated files.
have
been deleted, VFY should be run once again to
the multiply-allocated files have been deleted.

After
ensure

the
that

files
all of

QUALIFIERS APPENDED TO THE MCR VFY COMMAND

A.1.4

Elimination of Free Blocks

Once there are no multiply-allocated blocks, eliminate blocks that are
allocation map, but which are actually
storage
the
in
FREE
marked
storage
the
in
these blocks
reallocate
To
allocated to a file.
allocation map, rerun the validity check specifying the /UP qualifier.
as
marked
been
This qualifier allocates all blocks that should have
allocated.
See the description of the /UP qualifier.
Once there are no multiply-allocated blocks and no blocks marked
free
actually in use, the file structure is safe for writing new
that are
such
were
there
if
However,
files.
files and extending existing
there may be files which have had data blocks overwritten as
errors,
the result of multiple allocation.

Reccvering Lost Blocks

A.1.5

To determine whether any blocks on a file-structured volume have been
last two lines of output from the validity check.
the
examine
lost,
The
The last two lines of output give the free space on the volume.
first 1line of the two tells how much room is available according to
use by
the index file (that is, the number of blocks that are not in
The last line specifies how much room is
any file in the index file).
Assuming there are
available according to the storage allocation map.
If the index file
these two figures should agree.
errors,
no other
indicates that more blocks are free than the storage allocation map,
in the sense that they appear to be
"lost"
then those blocks are
Lost blocks may be recovered by
allocated, but no file contains them.
See the
the validity check specifying the /RE qualifier.
rerunning
description of the /RE qualifier.

A.2

FILE

QUALIFIERS

This section describes the file qualifiers that can be appended to the
VERIFY

command.

A.2.1

Delete Qualifier

The Delete qualifier
the

file

header

(/DE)

(/DE)
a

indicator

resets the marked-for-delete

1in

file that was marked for deletion, but never

actually deleted.

The volume must be mounted with the /UNLOCK qualifier.

The volume being deleted must be write-enabled;
access to the index file

VFY must be

A.2.2

running

under

Free Qualifier

The Free qualifier

([0.0] INDEXF.SYS).

VFY

requires

write

a system UIC.

(/FR)

(/FR) displays the available space on

specified

volume.

FREE qualifier output is the following message:

dev:

HAS nnnn.

BLOCKS FREE, nnnn.
A-4

BLOCKS USED OUT OF nnnn.

QUALIFIERS

A.2.3

List Qualifier

APPENDED TO

THE

MCR VFY

COMMAND

(/LI)

List
qualifier
The
lists
entire
index
file
the
file
(/LI)
by
identification.
The
output for each file specifies the file number,
file sequence number, file-name, and
ownher.
A
typical
index
file
listing is illustrated in Figure A-1.

VFY>DM1:
/LI
LISTING

FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE

ID
ID
ID
ID
ID
ID
ID
ID
ID
ID
ID

000001,000001
000002,000002
000003,000003
000004,000004
000005,000005
000006,000006
000007,000007
000010,000010
000011,000011
000012,000012
000013,000036

INDEXF.SYS;1
BITMAP.SYS;1
BADBLK.SYS;1
000000.DIR;1
CORIMG.SYS;1
001001.DIR;1
001002.DIR;1
EXEMC.MLB;1l
RSXMAC.SML;1
NODES.TBL;l
QIOSYM.MSG;311

OWNER
OWNER
OWNER
OWNER
OWNER
OWNER
OWNER
OWNER
OWNER
OWNER
OWNER

[1,1]
[1,1]
[1,1]
[1,1]
[1,1]
[1,1]
[1,2]
[1,1]
[1,1]
[1,1]
[1,2]

FILE

000014,000037

F4PCOM.MSG;1l

OWNER

[1,2]

Figure A-1

A.2.4

INDEX

VFY

Lost Qualifier

DMl:

Listing

Sample

Using

the /LI

Qualifier

(/LO)

The

Lost qualifier (/LO) scans the entire file structure
files
that
are not in any directory and, thus, are lost

that they cannot be referenced by file name.
A list of
produced, and if the "lost file directory" [1,3] exists
all the files will be entered in that directory.

A.2.5

Read

Check

Qualifier

1looking

the

for

the

sense
files
is

the

volume,

(/RC)

The Read Check qualifier (/RC) checks to ensure
every file on a specified volume can be read.

block

The optional parameter [:n]
is the blocking factor which indicates
number
of file blocks to be read at a time.
The default value is
maximum number of blocks in dynamic memory available to VFY.

the
the

Since the READ CHECK
write-protected.

When an error is detected,
following format:
FILE

nn,nn

read-only

a file

operation,

the

identification

line

file-name,type;version.

blocks

Following this line, an error message is listed.
other
than 1 is in use, an error message in the
be issued:
ERROR

STARTING

VBN

nl,n2

that

LBN

nl,n2

every

volume

listed

used/blocks

can

the

allocated

1If a blocking factor
following format will

ERROR

CODE

-err

Following

the

QUALIFIERS APPENDED TO THE

MCR VFY COMMAND

first

should

error

messages
1indicating
message line(s) will
ERROR AT VBN

nl,n2

If an ERROR STARTING
lines,
a multiblock
but

the

data

blocks

message,

there

ERROR

CODE

negative

indicate

The

error

second error

AT line is displayed without one or more ERROR AT
read operation on the selected device has failed,
appear

individually

number

printed

after

device

parity

error.

Appendix A of

one

-err

If the VBN of the unreadable block listed
beyond
the
block-used-count,
the
data
right.
The

the
-exact
block(s) in error.
be in the following format:

the VAX/VMS

the

System

in
the
ERROR
AT
1line
portion
of the file is

ERROR

Other

readable.

CODE

error

Messages

message

codes

and

are

is
all

-4

contained

Recovery

Procedures

Manual.

A.2.6

Rebuild

Qualifier

(/RE)

The

Rebuild gualifier (/RE) recovers
appear to be allocated but which are

Multiply-allocated

blocks must

before

can

The

the

rebuild

volume

write~access

VFY must

lost blocks, that is, blocks
not contained in any file.

removed

the

file

structure

write-enabled;

VFY

requires

run.

being

updated

storage

allocation map

under

system UIC.

the

running

from

that

must

([{0.0]

BITMAP.SYS).

The scratch file should be on another volume.
If this is
impossible,
the
volume
must
be
dismounted
immediately
after
VFY terminates.
(Failure to do this may result in
partial
updating
of
the
storage
allocation
map.)
Then
the
volume
should be mounted again, and the
scratch file must be deleted manually.
VFY issues a detailed
message
in this case, specifying the name of the scratch file to be deleted.

A.2.7

Update Qualifier

(/UP)

The Update qualifier (/UP) allocates
available but are actually allocated
Files

with multipy-allocated

structure

before

The
volume
write—access
VFY must

the

being
to the
running

update

blocks
can

all
to a
must

that

appear

deleted

from

write-enabled;
BITMAP.SYS).

VFY

the

file

run.

updated
storage

must
be
map ([0.0]

under

system

blocks
file.

UIC.

requires

QUALIFIERS APPENDED TO THE

MCR VFY COMMAND

The scratch file should be on another volume.
If this is
impossible,
the
wvolume
must
be
dismounted
immediately
after
VFY terminates.
(Failure to do this may result in
partial
wupdating
of
the
storage
allocation
map.)
Then
the
volume
should be mounted again, and the
scratch file must be deleted manually.
VFY issues a detailed
message
specifying

the

The message

VFY ~-

A.2.8

name

the

scratch

file

deleted.

is:

TO COMPLETE
THE
STORAGE
MAP
UPDATE
DISMOUNT
THE
VOLUME
IMMEDIATELY.
THEN
MOUNT
IT
AND
DELETE
THE
FOLLOWING
FILE:
[ufd]file-spec
[ufd]

the

file-spec

the name of

Validity Check

UFD.

the

file

to be deleted.

(Default)

A validity check is performed whenever
no
qualifiers
are
specified
with
the
VFY
command.
This default qualifier is fully described in
Section A.l.

APPENDIX

ERROR

This

MESSAGES

appendix

lists

of
the

the condition
condition.

BAD

BLOCK

can

unit

the

that

FILE

Description:
blocks.

PRODUCED

BAD error
causes

THE

BAD

BLOCK

messages,

gives

each message,

and

(BAD)

brief

suggests

description
a

response

OVERFLOW

BAD detected more

For

RK06

recorded

disks,

126.

the

This

than

102

maximum

message

User

Response:

Call

sets

number

the

contigquous

usually

failure.

Suggested

UTILITY

bad

blocks

indicates

DIGITAL

Field

bad
that

disk

Service

Representative.
BAD

BLOCK

BAD

NOT

USE

Description:
This is a
VAX/VMS
systems do not
as

other

RSX/IAS

SYSTEM

warning
use

block

systems

DISK

message

and

zero

bootstrapping

for

which

can

support

ignored.
purposes

Files-11l

on-disk

structure.

Suggested
BAD

DEVICE

User
NOT

Description:
system

Response:

1Ignore

The

requested
or

device

the

BAD

DISK

User

occurs,

DISK

cartridge

Suggested

I/0

User

error

Response:
check

ALIGNMENT

Description:
RKO6

made

not

that

the

part

exist

command

the

host

1line

was

the

same

ERROR

Suggested

BAD

Ensure

not

does

correctly.

Description:

error

Response:

was

device

configuration.

entered

message

SYSTEM

generation

Suggested

the

The

the

caused
Execute

integrity

BAD

BAD
of

terminate.

again
the

and,

unit.

CARTRIDGE

factory-written

indicates
Response:

label

alignment

the

last

cartridge.

Self-explanatory.

track

ERROR MESSAGES PRODUCED BY THE BAD BLOCK UTILITY

BAD

DISK

(BAD)

MOUNTED

Description:
The disk to be analyzed is mounted
as
a
Files-11
disk;
however, BAD cannot process disks unless they are mounted
using

the

/FOREIGN qualifier.

Suggested User Response:
Dismount the unit
wusing
the
DISMOUNT
command,
remount
the
unit
with
the
/FOREIGN
qualifier, and
reenter

the command

line.

See the description of the MOUNT command in the
VAX/VMS
Command
Language User's Guide for more information on this subject.
BAD

DISK

NOT

READY

Description:

The disk unit had not reached operating speed

BAD attempted

access

it.

Suggested User Response:
speed and

BAD

DISK

reenter

WRITE

Allow the disk unit to reach

the command

line.

when

operating

LOCKED

Description:

The disk unit

Suggested User Response:

is write-locked.

Unlock the unit and reenter the command

line.

BAD --

FAILED TO READ MANUFACTURER'S

Description:

disk-read

an RK06

cartridge.

BAD SECTOR FILE

hardware

error

occurred

while

attempting to read the factory-written bad block data on the last
track of

problem
the
If
Reenter the command.
Suggested User Response:
persists, call the DIGITAL Hardware Service Representative.
BAD --

FAILED

TO READ

MCR COMMAND BUFFER

Description:
BAD issued a $GMCR directive and no buffer
This condition occurs when BAD is invoked in the form:

exists.

$ MCR BAD
which

not

supported

for

Suggested User Response:

BAD.

Reenter

the command line

in the form:

$ MCR BAD device-name:
BAD

—--

FAILED

TO WRITE

Description:

BAD

BLOCK

BAD could not

condition usually results

FILE

write

the

bad

block

from a disk write error.

Suggested User Response:
Reenter the command.
persists, check the integrity of the disk unit.

file.
the

This
problem

ERROR MESSAGES

BAD

—-—

FATAL

HARDWARE

Description:

—-—-

ILLEGAL

User

supported

for

Response:

Response:
the

MANUFACTURER'S

Description:
track

SYNTAX

Suggested

BAD

-—

TOTAL

UTILITY

(BAD)

Call

the

DIGITAL

Field

Service

BAD

at
which
bad
device (disk).
Files-11

utility;
SECTOR

factory-written
cartridge

Response:

devices

other

FILE

block

are

devices

processing

the
are

only

devices

illegal.

CORRUPT

bad
an

Call

block

data

inconsistent
the

DIGITAL

the

last

format.
Field

Service

ERROR

Description:

reenter

BAD

The
RK06

Suggested
User
Representative.
BAD

BLOCK

DEVICE

Suggested

-—

BAD

ERROR

Description:
The
device
directed is not a Files-11

BAD

THE

Self-explanatory.

Suggested
User
Representative.
BAD

PRODUCED

BAD

User

the

detected
Response:

command

NO.

BAD

This

blocks

Suggested
label.

User

error

Determine

BLOCKS

number

bad

syntax

the

command

correct

line.

syntax

and

line.

Description:
of

an
on

Response:

nnnnnnnnn

information message
the

indicating

disk.

Write

the

bad

block

count

the

total

the

disk

VAX/VMS OPERATOR'S NOTES

VAX/VMS
OPERATOR'S

NOTES

VAX/VMS

Subject:

OPERATOR'S

NOTES

Date:

VAX/VMS OPERATOR'S NOTES

Subject:

Date:

VAX/VMS OPERATOR'S NOTES

Subject:

Date:

VAX/VMS OPERATOR'S NOTES

Subject:

Date:

VAX/VMS OPERATOR'S

Subject:

NOTES

Date:

VAX/VMS OPERATOR'S

Subject:

NOTES

Date:

VAX/VMS

Subject:

OPERATOR'S

NOTES

Date:

VAX/VMS

Subject:

OPERATOR'S

NOTES

Date:

VAX/VMS

Subject:

OPERATOR'S NOTES

Date:

INDEX

A
ASSIGN/MERGE
ASSIGN/QUEUE

Commands

command,
command,

3-4
3-5

disk, 2-18
Backing up the

system disk
disk, 2-10
Backing up the system disk
2-14
Backing up volumes, 2-3
error

messages,

job,

Batch queues, 2-28
terminating, 2-31
Brief error report,

3-44

3-51

error

report,

3-52

3-32

tape,

Data deck,

processing,

DEASSIGN/QUEUE
Default

2-33

command,

terminal

3-7

characteristics,

3-45
2-33

DELETE/QUEUE

3-32

Broadcasting messages
3-22

UIC,

Cryptic

B-1

processing,

SET

SHOW TERMINAL/PERMANENT,

Backing up a floppy diskette to
disk, 2-23
Backing up a nonsystem disk to

BAD

TERMINAL/PERMANENT,

START/QUEUE, 3-53
STOP/ABORT, 3-56
STOP/ENTRY, 3-57
STOP/QUEUE, 3-58
STOP/REQUEUE, 3-60

Batch

(Cont.),

SET

terminals,

command, 3-8
Deleting multiply-allocated
blocks, A-3
Device status messages, 4-2
Disabling operator status, 3-22

Disabling terminal messages,
Duties, operator, 1l-1

4-3

C
Card

reader,

correcting

defective cards, 2-33
procedure for processing a card
deck, 2-35

processing

a batch

2-33

processing

2-33

job,
data deck,

translation modes,

Correcting
Closing

cards,

the

log file,
CMKRNL privilege, 1-2
Commands,

ASSIGN/MERGE,
ASSIGN/QUEUE,

2-33

3-23

2-46
Enabling

Error

3-12

MCR

DSC,

3-14

MCR VFY,

3-18

REPLY,

3-4

SYS$SYSTEM:INSTALL, 3-27
SYS$SYSTEM:SYE, 3-31
SET, 3-33
DEVICE,

3-36

SET

LOGINS,

3-38

SET

PRINTER,

SET

3-32

3-9

RUN

ACCOUNTING,

File error messages,
Files and volumes,
handling, 2-1
procedures

GROUP
3-41

GRPNAM

Index-1

A-l

for management

3-34

3-39
PROTECTION/DEVICE,

system,

Reports,

standard,

RUN

SET

A-4

operator

unknown,

3-21

SET

the

brief, 3-32
cryptic, 3-32
roll up, 3-32

DELETE/QUEUE,
MCR BAD,

status, 3-22
terminal messages, 4-3
Error log (ERRLOG.SYS)
file, 2-36,
2-38

3-5
DEASSIGN/QUEUE, 3-7
3-8
INITIALIZE/QUEUE,

free blocks,

shutdown

Enabling

2-33

defective

Eliminating
Emergency

privilege,
privilege,

1-2
1-2

of,

2-4

(Cont.)

INDEX

H
Handling the error log file, 2-36
Handling files and volumes, 2-2
Handling the operator's log file,

Operator's terminal, 1-3, 4-3
Orderly shutdown of the system,
2-43

2-36

PHY IO privilege, 1-2
Preventing the loss of data when
line printer runs out of
paper, 2-30
Print queues, 2-28
merging, 2-29

INITIALIZE/QUEUE command, 3-9
Initializing the log file, 4-1

replacing paper in line printer,
2-30

L
Line printer,
2-30

Log file,

terminating,

changing paper in,
1-2,

operator's,

2-32

Printing the error log file, 2-38
Printing the operator's log file,
2-40

2-36,

Privileges, operator, 1-2
PRMCEB privilege, 1-2
PRMMBX privilege, 1-2

2-40, 3-1, 4-1
LOG_IO privilege, 1-2

Procedure

for,

emergency shutdown of system,

MCR BAD command,

3-12

MCR DSC command, 3-14
MCR VFY command, 3-18
Merging line printer queues,
Messages,

2-29

4-2

device status,
disable, 4-3
enable, 4-3

time stamp, 4-4
operator reply, 4-4
user request, 4-4
Mounting public disks,
Mounting volumes, 2-2

2-9

disks, 2-4
multivolume tapes,

o)
1-2

OPER privilege,

Operator assistance in creating a
multivolume tape set, 2-7
Operator assistance in handling
disks
2-4

and single-volume tapes,

multivolume tapes,

2-6

Operator assistance in processing
2-35

Operator duties, 1l-1
Operator privileges, 1-2

Operator reply messages,
(opcoM), 4-1

file,

1-2,

public

operator's log

2-40,

file, 2-38
(OPERATOR.LOG)

2-40

Procedure for restoring,
floppy diskette from disk, 2-25
system disk from tape, 2-16
Processing a batch job, 2-33
Processing a data deck, 2-33

Q
Queues,

(OPERATOR.LOG)

2-36,

2-9

disks,

Procedure for printing,
error log (ERROR.SYS)

4-4

Operator's commands, 3-1
Operator's communication process

Operator's log

2-6
single-volume tapes, 2-4
Procedure for mounting,

file,

Operator assistance in handling
a card deck,

2-46

merging line printer queues, 2-29
orderly shutdown of system, 2-43
processing a card deck, 2-35
replacing line printer paper, 2-30
restarting the system, 2-47
terminating a batch job, 2-31
terminating a print job, 2-32
Procedure for backing up,
floppy diskette to disk, 2-23
nonsystem disk to disk, 2-18
selected files to disk, 2-21
system disk to disk, 2-10
system disk to tape, 2-14
Procedure for creating,
a multivolume tape set, 2-7
Procedure for handling,

batch,
print,

3-1,

2-28
2-28

procedures that control queues, 2-29

4-1

Index-2

INDEX

(Cont.)

System

status

error

Recovering
REPLY

lost blocks,

command,

3-21

Responding

Restarting

the

procedure
Restoring

user

requests,

system,

for,

and

activity,

2-36
maintaining the error log file
and operator's log file, 2-36

A-4
3-22

log

file,

operator's
procedures

2-41

log file,
for, 2-38

2-36

2-47

files marked-for-delete,

A-3

Restoring

disk,
Restoring

floppy diskette from
2-25
the system disk from tape,

2-16

Roll

RUN

error

report,

RUN SYSS$SYSTEM:SYE
Running a validity

command,

command, 3-31
check, A-1l

Unknown

back-up of

SET

ACCOUNTING

SET

command,

files,

command,

User

2-21

3-34

3-33

DEVICE

command,

3-36

LOGINS

command,

3-38

SET

PRINTER

SET
SET

PROTECTION/DEVICE command, 3-41
TERMINAL/PERMANENT command,

command,

error

3-39

3-51

command,

starting

the operating

system,

2-41

procedures
Standard

for,

error

2-43

3-32
Starting the system, 2-41
procedure for, 2-47
START/QUEUE command, 3-53
STOP/ABORT command, 3-56

STOP/ENTRY
STOP/QUEUE
of

report,

command,
command,

STOP/REQUEUE
Summary

operating

procedures

3-52

down

operator's

SYSNAM privilege,

1-2

3-32
4-3

halting

the,

2-43

/FR,
/LI,

A-4
A-5
A-5
A-5
A-6

A-6
3-1

and

the, 2-41
shutting down the, 2-41
VERIFY (VFY) qualifiers, A-1
VFY file qualifiers,
/DE, A-4

3-60
commands,

systen,

for

restarting

3-57
3-58

command,

report,

'}
VAX/VMS

SHOW TERMINAL/PERMANENT

Shutting

4-3

REPLY/DISABLE command, 4-3
REPLY/ENABLE command, 1-3,

3-44
command,

1-3,
2-31

Using REPLY/LOG command, 4-1
Using REQUEST/REPLY command, 4-4
Using REQUEST/TO command, 4-4

SET

UIC

job,

request messages,

Using
Using

SET

a batch

S
Selective

the operator's,

Terminating

Terminating a print job, 2-32
Time stamp messages, 4-4
TMPMBX privilege, 1-2
Translation modes (for card reader),
2-33

3-32

SYS$SSYSTEM:INSTALL
3=-27

Terminal,

VFY validity check, A-1
privilege, 1-2

VOLPRO

Index-3

4-3

VAX/VMS
Operator's

Guide

AA~DQ25A~TE

READER'S

NOTE:

This
use

form

for

comments

COMMENTS

document

submitted

comments
this

form

only.

DIGITAL will

company's

the

discretion.
If you require a written reply and are
eligible to receive one under Software Performance
Report (SPR) service, submit your comments on an SPR
form.

Did you

find

Did you
page

this manual
suggestions

find errors

understandable,
for

Please

indicate

the

this manual?

Assembly

type

language

Higher-level
Occasional

User with
Student

Other

usable,

improvement.

number.

U0O0o0oadan

Please cut along this line.

Please make

reader

so,

and well-organized?

specify

that you most

the

nearly

programmer

language programmer

programmer

(experienced)

little programming

experience

programmer

(please

specify)

Name

Date

Organization
Street

City.

State

Zip Code
or

Country

error

and

represent.

the

— —

—

Do Not Tear - Fold Here and Tapg —

—

—
No Postage

dliigliltlall

Necessary
if Mailed in the

United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

RT/C SOFTWARE PUBLICATIONS

TW/A14

DIGITAL EQUIPMENT CORPORATION
1925 ANDOVER STREET
TEWKSBURY, MASSACHUSETTS

—_——

—

Do Not Tear - Fold Here

01876