Digital PDFs

AA-D025B-TE

March 1980

161 pages

Original

5.9MB

Document:	VAX/VMS Operator’s Guide
Order Number:	AA-D025B-TE
Revision:	000
Pages:	161
Original Filename:

OCR Text

VAX/VMS
Operator's Gulde
Order No. AA-00258-TE

March 1980
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-00258-TE

SUPERSESSION/UPDATE INFORMATION: This revised document supersedes
VAX/VMS Operator's Guide
(Order No. AA-D025A-TE).
OPERATING SYSTEM AND VERSION:

VAX/VMS V02

SOFTWARE VERSION:

VAX/VMS V02

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

digital equipment corporation · maynard, massachusetts

First Printing, August 1978
Revised, March 1980
The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in 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 on
equipment that is not supplied by DIGITAL or its affiliated companies.

@ 1978, 1980 by Digital Equipment Corporation

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

DIGITAL
DEC
PDP
DECUS
UNIBUS
COMPUTER LABS
COMTEX
DD'l'
DEC COMM
ASSIST-11
VAX
DECnet
DATATRIEVE

DECsystem-IO
DECtape
DIBOL
EDU SYSTEM
FLIP CHIP
FOCAL
IND AC
LAB-8
DECSYSTEM-20
RTS-8
VMS
IAS
TRAX

MASS BUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-11
TMS-11
ITPS-10
SB!
PDT

CONTENTS

Page
PREFACE

vii

SUMMARY OF TECHNICAL CHANGES

CHAPTER

INTRODUCTION

1-1

1.1
1.2
1.3
1.4
1.4 .1
1.4. 2

DUTIES OF THE OPERATOR
OPERATOR PRIVILEGES
THE OPERATOR'S TERMINAL
COMMANDS USED BY OPERATORS
Command Line Format
Summary of DCL Commands Used by Operators

1-1

HANDLING FILES AND VOLUMES

?.-1

2.1
2.2
2.2.1

2.5.4
2.5.5
2.5.n
2.5.7
2.5.8
2.5.9
2.5.10

2-1
ACCESSING TAPE AND DISK VOLUMES
2-2
REQUESTS TO MOUNT VOLUMES
User Requests to Physically Mount Tape and
Disk Volumes
File System Requests to Physically Mount
Additional Tape Volumes
2-3
File System Requests to Physically Mount
2-4
and Initialize Tape Volumes
2-4
ERRORS WHEN MOUNTING TAPE AND DISK VOLUMES
2-5
BACKING UP TAPE AND DISK VOLUMES
2-5
Disk Save and Compress Utility
2-7
COPY Command
File Transfer (FLX) Utility
2-7
2-7
RMSBCK and RMSRST Utilities
2-7
Scheduling Back-Ups
2-7
PROCEDURES FOR HANDLING FILES AND VOLUMES
Operator Assistance in Handling Disks and
Single-Volume Tapes
2-8
Operator Assistance in Handling Multivolume
Tape Sets
2-9
Operator Assistance in Creating a Multivolume
Tape or Disk Set
2-10
Mounting Public Disks
2-12
2-13
Backing Up the System Disk to Tape
Restoring the System Disk from Tape
2-15
2-17
Backing Up a Public Disk to Disk
2-20
Selective Back-Up of Files
Backing Up the Console Medium
2-23
2-2t1
Restoring the Console Medium from Disk

CONTROLLING PRINT AND BATCH QUEUES

3-1

3.1

DEFINITION OF QUEUE
COMMANDS FOR CONTROLLING PRINT AND BATCH
QUEUES
PROCEDURES FOR CONTROLLING PRINT AND BATCH
QUEUES

3-1

2.2.2
2.2.3
2.3
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.5
2.5.1
2.5.2
2.5.3

CHAPTER

3.2
3.3

iii

1-2
1-3

1-3
1-3
1-3

3-1
3-3

CONTENTS

Page
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5

CHAPTER

Merging Print Queues
Preventing Loss of Data When the Line
Printer Runs Out of Paper
Terminating the Execution of a Batch Job
Terminating the Printinq of a Print Job
Removing a Batch or Print Job from a Queue
USING THE CARD READER

4.1
TYPES OF CARD DECKS
Batch Job Card Deck
4 .1.1
Checking Batch Job Card Deck Input
4.1.1.1
4.1.1.2
Checking Batch Job Output
A Data Card Deck
4 .1. 2
Checking Data Deck Input
4.1.2.1
4.2
CARD READER TRANSLATION MODES
Setting the Translation Mode
4.2.1
4.3
TENDING THE CARD READER
Replacing Physically Defective Cards
4.3.1
Operating the Card Reader
4.3.2

CHAPTER

3-fi

3-7
3-8
4-1
4-1
4-1

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

4-4

THE ERROR LOG FILE

5-1

5.1
5.2

MAINTAINING THE ERROR LOG FILE
PRINTING THE ERROR LOG FILE

5-1
5-2

THE OPERATOR'S LOG FILE

e:\-1

11.3.5

MAINTAINING THE OPERATOR'S LOG FILE
PRINTING THE OPERATOR'S LOG FILE
MESSAGES IN THE OPERATOR'S LOG FILE
Initialization Messages
Device Status Messages
Terminal Enable and Disable Messages
Time Stamp Messages
User Request and Operator Reply Messages

SHUTTING DOWN AND RESTARTING THE SYSTEM

6.1

n.2
~.3

fl.3.1
11.3.2
n.3.3
11.3.4

SHUTTING DOWN THE OPERATING SYSTEM
RESTARTING THE OPERATING SYSTEM
The Start-Up Command Procedure
Restarting Problems
Hardware Problems
7.7..2.1
7.2.2.2
Software Problems
7.3
PROCEDURES FOR SHUTTING DOWN AND RESTARTING
THE SYSTEM
Orderly Shutdown of the System
7.3.1
7.3.2
Emergency Shutdown of the System
Forcing the System to Fail
7.3.3
Restarting the System
7.3.4
7.1
7.2
7.2.1
7.2.2

CHAPTER

3-5

CHAPTER

1-4

n-1
fi-2
fi-3
"1-3

'1-3
t:i-3

fi-4
fi-4
7-1
7-1

7-2
7-2
7-2
7-2
7-2
7-2
7-3
7-h
7-7
7-10

DCL COMMANDS USED BY OPERATORS

8-1

8.1
8.2
8.3
8.4

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

8-2
8-3

8-5
8-h

CONTENTS

Page
8.5
8.6
8.7
8.7.1
8.7.2
8.7.3
8.7.4
8.7.5
8.7.6
8.7.7
8.8
8.9

INITIALIZE/QUEUE
REPLY
SET
SET ACCOUNTING
SET DEVICE
SET LOGINS
SET PRINTER
SET PROTECTION/DEVICE
SET TIME
SET UIC
START/QUEUE
STOP/QUEUE

8-7
8-13
8-21
8-24
8-26
8-28
8-30
8-33
8-36
8-38
8-40
8-44

APPENDIX

SUMMARY OF DCL COMMANDS

A-1

APPENDIX

DEVICE CODES

B-1

B.l

DEVICE CODE TABLE

B-1
Index-!

INDEX

FIGURES
FIGURE

6-1

The Operator's Log File (OPERATOR.LOG)

n-5

TABLES
TABLE

1-1
1-2
2-1
3-1
4-1
8-1
8-2
8-3
8-4
8-5
B-1

Operator Privileges
DCL Commands Commonly Used by Operators
Mounting Volume Errors: Causes and Corrective
Action
Commands for Controlling Print and Batch
Queues
Card Reader Errors: Causes and Corrective
Actions
CPU Time Limit Specifications and Action
Working Set Default and Working Set Quota
Decision Table
REPLY/ENABLE and REPLY/DISABLE Keywords
Options for the Set Command
SET ACCOUNTING/DISABLE and SET
ACCOUNTING/ENABLE Keywords
Device Codes

2-5
3-2
4-5
8-9
8-11
8-18
8-21
8-25
B-1

PREFACE

MANUAL OBJECTIVES
The VAX/VMS Operator's Guide contains information that is useful in
Its
the day-to-day operation of the VAX/VMS operating system.
objectives are twofold:
1.

To give the reader an understanding
VAX/VMS system operator

the

duties

the

To gather in one volume the procedures, commands, and system
messages that specifically pertain to the operation of the
VAX/VMS system

INTENDED AUDIENCE
This guide is intended for operators of the VAX/VMS system and for
persons who must occasionally perform an operator's functions on the
system. Section 1.1 outlines and briefly describes the duties of an
operator.

STRUCTURE OF THIS DOCUMENT
This operator's guide consists of eight chapters and
as follows:

two

appendixes,

•

Chapter 1 briefly describes the duties of the system operator.

•

Chapter 2 explains how to handle files and volumes.

•

Chapter 3 describes how to control print and batch queues.

•

Chapter 4 describes how to use the card reader.

•

Chapter 5 describes the error log file.

•

Chapter 6 describes the operator's log file.

•

Chapter 7 describes how to shut down and restart the system.

•

Chapter 8 describes the DIGITAL Command Language
(DCL)
commands commonly used by the operator. Most of the commands
in this chapter are not included in the VAX/VMS Command
Language User's Guide.

•

Appendix A briefly summarizes all DCL commands.

•

Appendix B contains a table of
section for operator's notes.

vii

VAX/VMS

device

codes

and

The section called VAX/VMS Operator's Notes has been
included
following Appendix B, so that any new procedures or chanqes to
procedures specific to the operator's installation can be recorded.

ASSOCIATED DOCUMENTS
The VAX-11 Information Directory and Index provides a complete list of
all VAX-lT-do-cum-ents.-irnd includes a brief description of each.
For general background information about the VAX/VMS system, see
VAX/VMS -~E_i_~e_r. and the VAX/VMS Summ_9_!J_'___ I)_~~cr~_r>!_~__?n _a_f1~~~~-·~-Ci_EX.·

the

The following VAX/VMS documents may also be useful:

•
• VAX/VMS Guide to Using Command Procedures
• VAX/VMS Release Notes
e

VAX-11/RSX-llM User's Guide

•

VAX-11 Software Installation Guide

•

VAX/VMS

•

VAX/~f':!§___ ~y~~~~-~~ssa9_~_s__ a_~~-~~'?_ove:_ry

•

VAX-11 Utilities Reference Manual

•

RMS-11 User's Guide

Syste~---~~1:1~9-_e_r 's

Guide
Procedures Manual

For hardware operating instructions, refer to the appropriate hardware
manual for VAX-11 users.
For controlling network operations, refer

the

DECnet-VAX

System

Manage_~~---q~-~d-~.

CONVENTIONS USED IN THIS DOCUMENT
Convention

Meaning

THE expression <CTRL/X> indicates that the
user enters control character x by pressing
the appropriate letter while simultaneously
pressing
the
CTRL
key
(for example,
<CTRL/Y>, <CTRL/C>, <CTRL/Z>).

$ INITIALIZE/QUEUE
$_Queue: LPAO:

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

$ START/QUEUE LPBO:

Vertical ellipsis indicates that not all of
the data that the system would display is
shown.

viii

Convention

Meaning

Keyword, •••

Horizontal
ellipsis
indicates
additional
parameters,
values,
information may be entered.

[queue-name]

Square brackets mean that the
enclosed
expression is optional.
However, square
brackets are not optional in:
-

that
or

The syntax of a directory name
A file specification
The syntax of a substring specification
The SET UIC command

ANGLE brackets (<>) which contain a 1- to
3-character abbreviation indicate that a
particular key on the terminal is pressed
(for example, <RET> for the RETURN key or
<ESC> for the ESCAPE key).
Note that both symbols, <CR> and <RET>,
indicate the same action: press the RETURN
key.

SUMMARY OF TECHNICAL CHANGES

This section summarizes the technical changes made for Version 2.0
the VAX/VMS Operator's Guide.

The following command has been added:
SET TIME
The following qualifiers have been added to the following commands:
Command

Qualifier

INITIALIZE/QUEUE

/CHARACTERISTICS={c[, ••• ])
/CPUDEFAULT=t
/CPUMAXIMUM=t
/PROCESS=process-name
/WSDEFAULT=n
/WSQUOTA=n

START/QUEUE

/CHARACTERISTICS={c[, ••• ])
/CPUDEFAULT=t
/CPUMAXIMUM=t
/PROCESS=process-name
/WSDEFAULT=n
/WSQUOTA=n

In addition, the following miscellaneous changes have been made:
•

Information concerning the Bad Block Locator Utility {BAD),
the Disk File Structure Verification Utility (VFY), and Disk
Save and Compress (DSC) Utilities can now be found in the
VAX-11 Utilities Reference Manual

Information
concerning
RUN SYS$SYSTEM:SYE
and
RUN
• SYS$SYSTEM:INSTALL
commands can now be found in the VAX/VMS
System Manager's Guide
The following appendixes have been added to this volume:
•

Appendix A contains a summary of all DIGITAL Command
(DCL) commands

•

Appendix B contains the Table of Device Codes
called VAX/VMS Operator's Notes

and

Language
a

section

CHAPTER 1
INTRODUCTION

The VAX/VMS system operator is responsible for keeping the VAX/VMS
operating system running smoothly and for providing the best possible
service to system users.

1.1

DUTIES OF THE OPERATOR

The VAX/VMS system runs, to a great extent, without
operator
intervention.
However, in many installations, one or more operators
keep the system running smoothly.
Typically, the system operator
performs the following tasks:
•

Physically mounts magnetic tapes and disks at the
the users who own them

•

Initializes and mounts system volumes

•

Backs up critical public files and volumes

•

Carries out user requests

•

Sends messages to specific users

•

Broadcasts messages to all users

•

Controls print and batch queues

•

Tends line printers

•

Tends card readers

•

Monitors the system and notes and responds to emergencies

•

Prints copies of the operator's log file
file

•

Shuts down and restarts the system

•

Brings up and shuts down network components

and

the

request

error

log

To carry out their tasks, operators of the VAX/VMS system may have to:
1.

Establish working
system

relationships

Interact with the VAX/VMS operating system

Interact directly with the
operating system runs
1-1

VAX-11

with

other

processor

the

which

the

users

INTRODUCTION
The relationships between the VAX/VMS operator and users 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 printed on the operator's terminal; the messages are also entered
in the operator's log file for later reference.
The interactions between the operator and the VAX/VMS operating system
are 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. System messages and
messages that pass between the operator and other users, are entered
in the operator's log file.
Interactions between the operator and the VAX-11 processor require the
operator to operate and to maintain the peripheral devices supported
by the system. For detailed instructions on operating and maintaining
these peripheral devices, see the appropriate hardware manual for
VAX-11 users.

1.2

OPERATOR PRIVILEGES

Operators are granted privileges to perform functions that are denied
to most other users. These privileges always include the privilege of
performing operator functions
(the OPER privilege).
Table
1-1
summarizes the privileges an operator needs to use certain procedures
and commands documented in this manual.
The system manager is
responsible
for
granting
these
and other privileges to the
authorization record of the operator. The VAX/VMS System Manager's
Guide fully describes these and all other prlvileges and how to set up
authorization records for operators.
Table 1-1
Operator Privileges
Privilege

Function

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

BYPASS

Bypass user identification code (UIC)
accessing files

CMKRNL

Change execution mode to kernel

GROUP

Affect processes within the same group

GRPNAM

Insert logical names
table

LOG IO

Issue logical I/O requests

NETMBX

Create network devices

OPER

Execute operator functions

PHY IO

Issue physical I/O requests

PRMCEB

Create or delete permanent common event flag clusters

into

the

group

protection

logical

name

(continued on next page)

1-2

INTRODUCTION

Table 1-1 (Cont.)
Operator Privileges
Privilege

Function

PR MM BX

Create permanent mailboxes

SY SN AM

Insert system logical names into the
name table

SY SP RV

Assume system UIC protection in accessing files

TMPMBX

Create temporary mailboxes

VOLPRO

Override volume protection

1.3

system

logical

THE OPERATOR'S TERMINAL

Operators of the VAX/VMS system can perform many of their duties from
user terminals.
However, one of the operator's chief functions,
communicating with other users, must be performed at a terminal that
has been defined as an operator's terminal. An operator can define a
terminal to be an operator's terminal by using the privileged command,
REPLY/ENABLE (described in Section h.3.3 and Chapter 8).
Other operator functions can be performed only from the system console
terminal.
These functions include bootstrapping and halting the
system and examining physical memory.

1.4

COMMANDS USED BY OPERATORS

This manual contains descriptions of the DIGITAL Command Language
(DCL)
commands that operators of the VAX/VMS system most often use to
keep the system running smoothly. Most of these commands require the
OPER privilege.
See Chapter 8 for detailed descriptions of these
commands. For information on DCL commands not discussed in this
manual, refer to the VAX/VMS Command Language User's Guide.

1.4.1

Command Line Format

The general format of a DCL command is:
command-name [/qualifiers ••• ] parameter [/qualifiers ••• ] [ ••• ]
Because a command can be continued on more than one line, the term
"command string" is used to define the entire command that is passed
to the system. A command string is the complete specification of a
command,
which
includes the command name, command qualifiers,
parameters, and parameter qualifiers.
See the VAX/VMS
Command
Language User's Guide for a detailed description of command syntax.

1.4.2

Summary of DCL Commands Used by Operators

Table 1-2
operators.

briefly

describes

the
1-3

DCL

commands

commonly

used

INTRODUCTION

Table 1-2
DCL Commands Commonly Used by Operators

-----------··..

-~·-···---

____....... ____
.,

·--·-·-----·----·--···--·------------,~-·-·~--·~

........

_.~

...... ,,_....

___ ~

.....

Punction

Command

1------------·-------------1--------------. ····---·---···-···--·-··-··. -----·-·"
ALLOCATE 1

Reserves a device for use by a
single user and, optionally,
assigns a logical name to the
device

ASSIGN/MERGE

Removes all jobs from one queue
and places them in another queue

ASSIGN/QUEUE

Assigns a logical queue to a
specific device

COPY l

Copies one or more files into one
or more additional files

DEALLOCATE l

Relinquishes use of a previously
allocated device, thus making the
device available to other users

DEASSIGN/QUEUE

Deassigns a queue from a specific
device

DELETE/ENTRY 1,2

Deletes an entry from a print or
batch queue or stops processing
the current job

DELETE/QUEUE

Deletes batch and print queues

DIRECTORY l

Displays information about a file
or group of files

DISMOUNT l

Releases the connection between a
user and a disk or tape volume
that is currently mounted on a
device

INITIALIZE/QUEUE

Creates batch and print queues

MOUNT l

Makes a disk or tape volume
available for the reading or
writing of files and, optionally,
assigns a logical name to the
device on which the volume is
mounted

PRINT l

Queues a file for printing on a
specific device

1. Described in the VAX/VMS Command Language User's Guide.
2. Allows a user with either operator
privilege to affect any job in the system.

(OPER)

world

(WORLD)

{continued on next page)

1-4

INTRODUCTION

Table 1-2 (Cont.)
DCL Commands Commonly Used by Operators
Function

Command
- - - - - - - - - - - - - - - -.. - - - - !

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

_ _ _ _ _ _ ______,

Allows the operator to
communicate with system users,
selectively enable and disable
operator status, and examine the
operator's log file

SET ACCOUNTING

Selectively enables and disables
the recording of particular kinds
of accounting information

SET DEVICE

F.stablishes the spooling and
error-logging status on a
specific device

SET LOGINS

Establishes the maximum number of
users able to log in to the
system

SET PRINTER

Establishes the characteristics
of a specific line printer

SET PROTECTION/DEVICE

Establishes the protection for a
non-file-structured device

SET QUEUE/ENTRYl, 2

Changes the status or attributes
of jobs in print or batch queues
that have not yet been processed
by the system

SET TIME

Resets the system time

SET UIC

Establishes a new user
identification code (UIC) as the
process UIC

SHOW DEFAULT l

Displays the current default
directory and disk device

SHOW DEVICESl

Displays the status of devices in
the system

SHOW QUEUEl

Displays the names, job
identification numbers, and
status of current and pending
jobs in print and batch job
queues

_________________ _____________ _________

,___

--·

..__

____ ___,

1. Described in the VAX/VMS Command Language User's Guide.
2. Allows a user with either operator
privilege to affect any job in the system.

(OPER)

world

(WORLD)

(continued on next page)

1-5

INTRODUCTION

Table 1-2 (Cont.)
DCL Commands Commonly Used by Operators
Command

Function

SHOW TIMEl

Displays the current date and
time on the terminal

START/QUEUE

Starts batch and print queues

STOPl,2

Halts execution of a command
procedure, program, subprocess,
or detached process

STOP/ABORTl,2

Stops printing a job that is
currently being printed

s·roP /ENTRY l, 2

Stops executing a batch job that
is currently running and deletes
it

STOP/QUEUE

Suspends batch and print queues

S'fOP/REQUEUE l, 2

Stops printing a job currently
being printed; then requeues
that job and gives it a priority
of 1

SUBMIT l

Queues one or more command
procedure(s) to a batch job queue

TYPE l

Displays the contents of a file
or files at the current output
device

1. Described in the VAX/VMS Command Language User's Guide.
2. Allows a user with either operator
privilege to affect any job in the system.

1-11

(OPER)

world

(WORLD)

CHAPTER 2
HANDLING FILES AND VOLUMES

Generally, users prepare their own volumes for use.
Bowever,
depending on the physical arrangement of the installation and the type
of volume to be accessed, the operator may he called upon to assist in
the preparation of volumes for use. The following list provides some
of the reasons why operator assistance may be required:
•

The processor and its peripheral devices are off limits to
remotely located from some or all users

•

The magnetic tape file system has requested that a tape volume
be mounted

•

A system or public disk needs to be mounted

Therefore, at some installations, communication with a system operator
is required for users to either gain access to or create files. Tape
and disk volumes must be physically mounted on devices, and the files
contained on these volumes must be backed up regularly.
Physically mounting a volume means placing the volume on a specific
drive and starting the drive. For tape drives, the operator loads the
tape into the drive and then presses the LOAD button to start the tape
drive.
For disk drives, the operator places the disk in the disk
drive and then presses the START or RUN button to start the disk
drive.
The operator also may assist in backing up a volume.
Backing up a
volume means copying the contents of the volume to another volume or
set of volumes (for example, another disk or tape).
Backing up
vo~µmes
is a precautionary measure to prevent the loss or destruction
of va~uable information.

2.1

ACCESSING TAPE AND DISK VOLUMES

Before a user can access a tape or disk volume,
must be performed:

the

following

The device on which the volume is placed
using the ALLOCATE command.

The volume must be physically mounted on the device.

If it is a new volume, then it must be initialized using
INITIALIZE command.

The user must mount the volume using the MOUNT command.

2-1

must

steps

allocated

the

HANDLING FILES AND VOLUMES
Allocating devices and initializing and mounting volumes are fully
described in the VAX/VMS Command Language User's Guide under the
ALLOCATE, INITIALIZE, and MOUNT commands and-!n-tne-----~Cnapter in that
manual pertaining to disk and tape volumes.
The following sections discuss when and how the operator assists users
in gaining access to files on particular volumes. The latter part of
the chapter contains step-by-step procedures for accessing tape and
disk volumes.

2.2

REQUESTS TO MOUNT VOLUMES

The operator receives requests to physically mount volumes from users
and from the magnetic tape file system. Generally, a user sends a
request to physically mount either disk or tape volumes.
However,
sometimes the file system contacts the operator when the next tape in
the tape volume set must be physically mounted.
When users and the file system send messages to the operator, the
messages are produced on the operator's terminal by the Operator's
Communication Process (OPCOM) and are preceded by the label Opcom.
After rece1v1ng a request and performing the task, the operator
responds to the request using the privileged REPLY command.
The following sections describe the different types of requests an
operator can receive and how the operator responds to them. For
additional information on tapes and disks, see the VAX/VMS Command
Language User's Guide.

2.2.1

user Requests to Physically Mount Tape and Disk Volumes

System users specify the REQUEST command to send messages to the
operator.
Below is a typical message sent to the operator's terminal
after a user requests the operator to physically mount a tape volume:
Opcom, 02:53:13.79, LORENZO
Accnt=SALARY
Opcom, TTA4:, "Mount PAYROLLOl on MTAO:"

REPLY-ID=24

LORENZO
Indicates the user's process name.
Accnt=SALARY
Indicates an accounting information file
cumulative resource usage statistics.

used

for

collecting

REPLY-ID=24
Indicates a unique identification number that the system assigns
to a request and that the operator uses to respond to a request.
TTA4:
Indicates the terminal from which the request was sent.
"Mount PAYROLLOl on MTAO:"
Indicates the message that the user sent.

2-2

HANDLING FILES AND VOLUMES
After placing the tape on the specified drive and readying the device,
the operator issues a REPLY command to notify the user that the tape
is available for use:
$REPLY/T0=24
This command informs the user that the volume is ready for
user then can issue a MOUNT command to mount the tape.

use.

The

Alternatively, the operator can issue one of the following
commands to notify the user that the tape is not ready for use:

RF.PLY

$REPLY/ABORT=24
This REPLY
satisfied.

command

indicates

that

the

request

cannot

$REPLY/PENDING=24
This REPLY command indicates that the user's request cannot be
satisfied immediately. Eventually, the operator must follow the
REPLY/PENDING command with either a REPLY/TO command or a
REPLY/ABORT command.
If the REPLY/PENDING command is used by the operator, the user's
terminal is "locked". The user's process associated with the terminal
remains in a wait state until the operator either satisfies or aborts
the request.

2.2.2

File System Requests to Physically Mount Additional Tape Volumes

Requests to place a volume on a device usually come from a user.
However, sometimes the magnetic tape file system requests that a tape
volume be mounted. A request from the file system usually occurs when
the tape reaches end-of-tape, and the file system needs another tape
to finish the operation. The file system suspends processing and
sends a request to the operator to mount another tape, as in the
following example:
Opcom, 11:21:07.Sfi, MARCELLO
Accnt=TESTPROC Reply-ID=31~
Opcom, MOUNT RELATIVE VOLUME 3 (PAD003) ON MTAO:
The above message exemplifies a standard message from the file system.
A request from the file system is identical to a user request except
that no terminal name is included.
After placing the volume on the device and readying the device, the
operator issues a REPLY command to notify the file system that the
tape is available for use:
$ REPLY/T0=3lfi
OPCOM verifies the REPLY-ID and then the file system verifies the
volume name.
If both the identification number and volume name are
correct, processing continues.

2-3

HANDLING FILES AND VOLUMES
Alternatively, the operator can issue the following REPLY command
notify the file system that the tape cannot be readied for use:

$ REPLY/ABORT=3lfi

This REPLY command indicates that the file system request cannot
be satisfied. This command usually causes the user's program to
terminate.

2.2.3

File System Requests to Physically Mount and Initialize Tape Volumes

When a tape reaches end-of-tape and the user has not previously
initialized additional tape volumes, the operator must initialize the
new tape after placing it on the drive.
When the tape reaches end-of-tape, the file system suspends processing
and sends a message to the oparator to mount the next tape. The
message is similar to the one that the file system sends when a user
needs the next tape in a volume set:
Opcom, ln:43:28.08, RUTAD ACCNT=DOCUMENT REPLY-ID=34
Opcom, MOUNT RELATIVE VOLUME 2 () ON MTAl:
Note that in the message the parentheses are empty. This is because
there is not another tape in the tape volume set to be mounted. If
the file system wants another tape, the operator finds a blank or
scratch tape, places it on the device, and initializes the tape. To
initialize a tape that previously has been written to, the operator
specifies the volume-label and /INITIALIZE when responding to the file
system request, as shown below:
$ REPLY/T0=34 "DGB002/INITIALIZE"

Note that the message is enclosed within double quotation marks.
NOTE
All tapes that have been processed by a
verifying machine or that never have
been written to
before
should
be
initialized using the INITIALIZE command
described
in
the
VAX/VMS
Command
Language user's Guide.
Alternatively, the operator can issue the following REPLY command
notify the file system that the tape cannot be re~died for use:

$ REPLY/ABORT=34

This REPLY command indicates that the request cannot be satisfied.

2.3

ERRORS WHEN MOUNTING TAPE AND DISK VOLUMES

After the operator has mounted a tape or disk volume, a message may
appear on the operator's terminal indicating that the volume is not
properly mounted. Table /.-1 lists the probable causes for an error
message and the operator action required to remedy the situation. For
more information on error messages, refer to the VAX/VMS System
Messages and-· Re~ove U'__ J'~c:=~.9.l:1-.!'.:_e~.-~.?~~~~.
2-4

HANDLING FILES AND VOLUMES
Table 2-1
Mounting Volume Errors: Causes and Corrective Action
Cause

Corrective Action

The operator mounted the wrong
volume on the device

Remove the volume and replace
it with the correct one

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

Press the LOAD button on the
tape drive
Press the LOAD button and then
press the ONLINE button on the
tape drive
Press the RUN or START button
on the disk drive

The WRITE-LOCK indicator is
illuminated, but the user
wants to write to the volume

Insert the write-ring into the
tape
Push the WRITE-LOCK switch to the
OFF position on the disk drive

The operator mounted a used
tape that had not been
initialized and did not
specify the volume label and
/INITIALIZE

2.4

Reissue the REPLY command and
include the volume label and
/INITIALIZE

BACKING UP TAPE AND DISK VOLUMES

The operator can choose one of the following ways to back up tape and
disk volumes. The type of back-up desired determines which method is
used. The methods are:
•

Disk Save and Compress Utilities (DSC)

•

COPY command

•

File Transfer Utility (FLX)

RMSBCK and RMSRST Utilities

For information on the RMSBCK and RMSRST Utilities, refer to the
RMS-11 User's Guide. Information concerning FLX and DSC Utilities can
be found in the VAX-11 Utilities Reference Manual.
The following section discusses various ways an operator can back up
volumes
and
files.
The latter part of the chapter contains
step-by-step procedures for backing up tape, disk, and console medium
volumes.

2.4.1

Disk Save and Compress Utility

The operator uses the Disk Save and Compress (DSC) Utilities to back
up and restore disk volumes.
These utilities copy all the blocks
allocated to files onto a target or scratch volume.
DSC has three
forms: DSCl, DSC2 and Stand-Alone DSC-2. The DSCl Utility is used to

2-5

HANDLING FILES AND VOLUMES

back up Files-11 Structure Level 1 volumes. The DSC2 and Stand-Alone
DSC-2 Utilities are used to back up Files-11 Structure Level 2
volumes.
The Stand-Alone DSC-2 Utility enables operators with single-disk
systems to back up and restore system disks. The procedures for
backing up and restoring disk volumes on a single-disk system are
documented in Sections 2.5.5 and 2.5.~. The Stand-Alone DSC-2 Utility
also allows operators on double-disk systems to back up data disks.
The command string format is identical for all three DSC Utilities
(DSCl, DSC2, and Stand-Alone DSC-2). Note that the left side of the
equal sign denotes output parameters; the right side denotes input
parameters, as specified below:
devcu:

[,devcu: ••• ] [dsclabel]
devcu:

[/qualifier(s)]=

[,devcu: ••• ] [dsclabel]

[/qualifier]

Parameters

devcu:

[,devcu: •.• ]

The above format describes the physical device(s) to or from
which data is to be transferred. The components of the devcu
format are as follows:
dev is the 2-character device code
c

is the device controller letter

is the device unit number

The colon acts as a delimiter, and
device specification. For example:

therefore

must

the

specify

each

and

DMAO:
If there is more than one output device,
separate them with commas. For example:
DMAO:,DMA1:,DMB2:
dsclabel
This is an optional file label for the DSC file created when a
disk-to-magnetic tape operation is performed.
If specified,
dsclabel must be a 1- through 12-character alphanumeric label.
If dsclabel is not specified in the output specification, the
volume label of the input disk volume becomes the output volume
label.
If dsclabel is not specified in the input specification,
the DSC Utility uses the first file specification on the first
input device specified in the command string for the volume
label.
For disk-to-disk operations, the dsclabel that the operator
specifies becomes the volume label of the output disk. If
dsclabel is not specified, the output disk volume label remains
the same as the input disk volume label.
Specify dsclabel before any qualifiers.

2-fi

HANDLING FILES AND VOLUMES
/qualifier(s)
Output file qualifiers determine which operations will
he
performed.
They can be specified in any order; for example
/DENS=l600/VE has the same effect as /VE/DENS/=l~OO.
Refer to
the VAX-11 Utilities Reference Manual for specific information on
DSC Utilities and their quali~iers.

2.4.2

COPY Command

The operator uses the DCL COPY command to copy selected files from one
volume to another.
This command is fully described in the VAX/VMS
Command Language User's Guide.

2.4.3

File Transfer (FLX) Utility

Distributed with the VAX/VMS software is a command procedure that
copies and restores the contents of RT-11-formatted floppy diskettes.
This command procedure uses the File Transfer Utility (FLX) to perform
the copy operation.
Invoking and using the command procedure that
employs the FLX Utility is described in Sections 2.5.9 and 2.5.10.
For more information on the File Transfer Utility (FLX), refer to
VAX-11 Utilities Reference Manual.

2.4.4

the

RMSBCK and RMSRST Utilities

The RMSBCK Utility creates back-up copies of one or more files on a
storage medium. The RMSRST Utility reverses the process performed by
the RMSBCK Utility. RMSRST reads back-up files as input and produces
standard
RMS-11 files as output.
The structure, context, and
attributes of these restored files is the same as the original files
at the time they were backed up.
For more information on these
utilities, refer to the RMS-11 User's Guide.

2.4.5

Scheduling Back-Ups

The system manager generally is responsible for setting up a schedule
for backing up files and volumes. This schedule should inform the
operator of the frequency with which the volumes are updated and the
importance of the files contained on these volumes. Once the schedule
is established, the system operator is usually responsible for
maintaining this schedule.

2.5

PROCEDURES FOR HANDLING FILES AND VOLUMES

This section contains step-by-step procedures for accessing tape and
disk volumes and for performing back-up and restore operations on
different types of volumes.

2-7

HANDLING FILES AND VOLUMES
Operator Assistance in Handling Disks and Single-Volume Tapes

2.5.1

The procedure below describes how to physically mount a specific disk
or tape on a device,
when requested by a user issuing the REQUEST
command.

Procedure
1.

Observe the following message on the operator's terminal:
OPCOM, hh:mm:ss.cc, process-name ACCNT=account-name REPLY-ID=identification-number
Opcom, terminal-name:, "mount-message"

Locate the volume and place it on the specified device.

Ready the device by pressing either:

The LOAD button if it is a magnetic tape drive

The RUN/STOP button or the START/STOP switch if it
disk drive.

Issue one of the following REPLY commands in response to
user's request:
a.

REPLY/TO=identification-number ["message-text"]

REPLY/ABORT=identification-number ["message-text"]

REPLY/PENDING=identification-number ["message-text"]

For more information on the REPLY command, see Section
or Chapter 8.

a
the

2.2.l

Examples
1.

OPCOM, 12:54:57.07, BOBA
ACCNT=CIRCUS REPLY-ID=29
Opcom, _TTFl:, "MOUNT SYSFILE ON DBAl:"

$ REPLY/T0=29 "SYSFILE MOUNTED ON DBAl:"
$

OPCOM, 01:03:43.90, REQUEST COMPLETED, operator=_OPAO:, ID=29
OPCOM alerts the operator to place the disk volume named
SYSFILE on DBAl. The operator locates the volume, places it
on the device, readies the device, and then informs the user
that the volume is ready for use.
2.

OPCOM, 09:45:23.74, LEBB
ACCNT=WATER REPLY-ID=4
Opcom, _TTF3:, "MOUNT TESTER ON MTAO:"

$ REPLY/PENDING=4 "PLEASE WAIT A FEW MINUTES"
$ REPLY/T0=4 "MTAO:
IS DOWN -- TESTER MOUNTED ON MTA2:"
$

Opcom, 10:02:34.12, REQUEST COMPLETED, operator=_OPAO:, ID=4
OPCOM sends a message to the operator's terminal to inform
the operator that a user wants the magnetic tape named TESTER
placed on MTAO. The operator issues a REPLY/PENDING command
to inform the user that the task cannot be performed on the
device that the user requested.
Later, the operator mounts
the magnetic tape on MTA2 and notifies the user that the tape
volume is on MTA2.

2-8

HANDLING FILES AND VOLUMES
Operator Assistance in Handling Multivolume Tape Sets

2.5.2

The procedure below describes how to
initialized tapes in multivolume sets.

physically

mount

previously

Procedure
1.

Observe the following message, which is sent from the file
system
and displayed on the console terminal and all
operators' terminals:
OPCOM, hh:mm:ss.cc, process-name
ACCNT=account-name REPLY-ID=identification-number
Opcom, MOUNT RELATIVE VOLUME x {label-name) ON device-name:

Locate the tape and place it on the specified device.
the device by pressing the LOAD button.

Issue one of the following REPLY commands in response to
request:
a.

REPLY/TO=identification-number

REPLY/ABORT=identification-number

Ready
the

Note that if the REPLY command does not
include a message,
OPCOM usually issues a default message.
For more information
on the REPLY command, see Section /..2.2 or Chapter 8.

Examples
1.

OPCOM, 14:24:07.53, GREICO
ACCNT=MASTERS REPLY-ID=4
Opcom, MOUNT RELATIVE VOLUME 3 (GMBOOA) ON MTAl:

$ REPLY/T0=4
$
Opcom, 14:31:43.71, REQUEST COMPLETED, operator=_OPAO:, ID=4
A user is reading or writing to the first tape in the volume
set GMBOOA.
The first OPCOM message informs the operator
that the user needs the second volume of the tape set.
After
mounting it, the operator issues the REPLY command to inform
the file system that the tape has been mounted and the system
can resume processing.

2-9

HANDLING FILES AND VOLUMES
2.5.3

Operator Assistance in Creating a Multivolume Tape or Disk Set

The procedure below describes how to physically mount
additional tapes or disks in multivolume sets.

and

initialize

Procedure
1.

Observe the following message on the operator's terminal:
OPCOM, hh:mm:ss.cc, process-name
ACCNT=account-name
Opcom, MOUNT RELATIVE VOLUME x () ON device-name:

REPLY-ID=identification-number

If the user previously did not tell the operator that an
additional tape or disk might be needed and specify the
volume label of the tape or disk, the operator should try to
contact the user to obtain this information:
a.

Does the user want another tape or disk?

What is the volume label of the tape or disk?

Enter the following command if the user does not want another
tape or if the user cannot be contacted:
$ REPLY/ABORT=identification-number

NOTE
Steps 4, 5, and n below should be
ignored if the operator aborts the user
request. Aborting the request usually
aborts the user's program.
For more
information on the REPLY command, see
Section 2.2.3 or Chapter 8.
4.

Apply a visible label to the outside of the tape or disk
volume specifying the volume label and the relative volume
number.

Place the tape on the specified drive and ready the device by
pressing either:

The LOAD button if it is a magnetic tape drive

The RUN/STOP button or START/STOP switch if it is a disk
drive.
If the drive does not come online automatically,
press the ONLINE button.

Issue the following REPLY command to initialize the tape and
inform the file system that the tape is available for use:
$ REPLY/TO-identification-number "volume-label/INITIALIZE"

For more information on the REPLY command, see Section
or Chapter 8.

2-10

2.2.3

HANDLING FILES AND VOLUMES

Examples
1.

OPCOM, 14:16:24.98, RACHEL ACCNT=NAMES REPLY-ID=6
Opcom, MOUNT RELATIVE VOLUME 2 () on MTAl:
$ REPLY/TO=fi "GMB002/INITIALIZE"
$

Opcom, 14:23:3n.10, REQUEST COMPLETED, operator=_OPAO:,ID=6
The OPCOM message notifies the operator that a user needs a
second tape.
~fter
mounting the tape, the operator issues
the REPLY/TO command to indicate the tape is mounted.
The
volume
label
GMBOO/. is assigned to the tape by the
/INITIALIZE message.
OPCOM, 09:15:32.~7, JOHN ACCNT=HISTORY REPLY-ID=B
Opcom, MOUNT RELATIVE VOLUME 2 (CIVIL) ON DBAl:

2.
$
$

REPLY/TO=B
Opcom, 09:21:29.74, REQUEST COMPLETED, operator=OPAO:,ID=B

The OPCOM message indicates that the user needs another disk.
After mounting the disk, the operator issues the REPLY/TO
command to indicate the disk is mounted.
3.

OPCOM, 12:56:03.7~, RAP ACCNT=SESSIONS REPLY-ID=l5
Opcom, MOUNT RELATIVE VOLUME 3 () on MTAl:
$ REPLY/ABORT=l5
$

Opcom, 13:03:12.42, REQUEST ABORTED, operator=_OPAO:,ID=lS
The first OPCOM message indicates that the user needs another
tape.
Upon notifying the user, the operator discovers that
the user does not want another tape.
The operator cancels
the request using the REPLY/ABORT command. The second OPCOM
message confirms that the request has been canceled.

2-11

HANDLING FILES AND VOLUMES
2.5.4

Mounting Public Disks

This procedure describes how to mount a disk as a public disk.
Public disks are disks that contain more than one user's files. These
disks must be designated as shareable at the time they are mounted, so
that the files can he accessed by all users on the system.
Use the
/SYSTEM qualifier with the MOUNT command to create a shareable disk.
Procedure
1.

Allocate a drive by issuing the following command:
$ ALLOCATE device-name:

Locate the disk and put a visible volume label on the outside
of the volume if one is not already there. Place the disk on
the allocated drive.

Ready the device by pressing the
RUN/STOP button.

Issue the MOUNT/SYSTEM command to allow all users
files on the disk:
$ MOUNT/SYSTEM

device-name:

START/STOP

switch
to

the

access

volume-label

NOTE
To use the /SYSTEM
qualifier,
the
operator needs the SYSNAM privilege.
5.

Optionally, inform all users on the system that the
available for use:

disk

$ REPLY/USER/BELL "message-text"

Examples
1.

$ ALLOCATE DBB2:

DBB2:

ALLOCATED

$ MOUNT/SYSTEM DBB2:

USERFILES
%MOUNT-I-MOUNTED, USERFILES
mounted on
DBB/.:
$ REPLY/USER/BELL "PUBLIC VOLUME MOUNTED ON TIBB2:"
The ALLOCATE command requests the allocation of DBB2;
the
response from the system indicates that DBB/. is allocated.
The MOUNT/SYSTEM command ensures the disk mounted on DBB2 is
available to all users. The system response indicates that
the disk was successfully mounted.
The REPLY/USER/BELL
command broadcasts a message that informs all users logged in
to the system that the disk mounted on DBB2 can be accessed.

2-12

HANDLING FILES AND VOLUMES
2.5.5

Backing Up the System Disk to Tape

The procedure below uses the Stand-Alone DSC-2 Utility to copy the
contents of the system disk onto magnetic tapes. To restore the
contents of the tapes to disk, the operator uses the procedure
described in Section 2.5.h.
User files with protection codes denying read access to
will not be backed up.

system

users

This procedure must be performed from the system console terminal.
Procedure
1.

Run the SHUTDOWN.COM
Section 7.3.1.

command

Write-protect the system disk by setting the
switch on the disk drive to the ON position.

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

Verify that the system
drive.

Halt the CPU hy typing:

console

procedure

menium

described

~RITE-PROTECT

the

console

»> HALT
h.

Type the following command to bootstrap the Stand-Alone DSC-2
Utility:
>» BOOT DSC
The following
terminal:

console

message

will

printed

the

cartridge

ann

into

the

CPU HALTED
IN IT SEQ DONE
LOAD DONE, 00002000 BYTES LOADED
Please insert first system
type <RET>

diskette

Load the first Stand-Alone DSC-2 console
console device and press the RETURN key.

mediu~

After the operator presses the RETURN key, the console
subsystem loads the Stand-Alone DSC-2 Utility on the console
medium. This takes approximately h minutes.
Approximately
three minutes later, the following message will be displayed
at the console terminal:
VAX/VMS Version 2.0 17-MAR-80 18:1
Please insert second
<RET>

diskette

cartridge

and

type

At this point, load the second Stand-Alone nsc-2 Utility
console medium into the console drive and press the RETURN
key.

2-13

HANDLING FILES AND VOLUMES
Approximately one minute later, at the completion of loading,
the following prompt will be printed at the console terminal:
DSC2>
7.

A copy of the Stand-Alone DSC-2 Utility for
Files-11
Structure Level 2 disks is now running. Type the appropriate
DSC-2 command for the system disk and the kind of back-up
needed.
The following commands are examples of different
types of back-ups:
DSC2>MTAO:/RW/DENS=ln00/VE = DBAO:
The above command copies the contents of the disk mounted on
DBAO to the tape mounted on MTAO. The /RW qualifier causes
the tape to be rewound before the copy operation begins. The
/DENS=l~OO
qualifier requests that the data be copied to the
tape at 1600 bits per inch. The /VE qualifier requests that
the contents of the tape be compared with the contents of the
disk to insure the copy operation was successful.
DSC2>MTAO:,MTA1:/RW/VE = DBAO:
In this example, the Stand-Alone DSC-2 Utility copies the
contents of the disk mounted on DBAO to the output devices
MTAO and MTAl. When the Stand-Alone DSC-2 Utility finishes
copying data to the first tape, MTAO, the first tape is
rewound while data is written to the second tape, thus
hastening the copy operation. When the density of the target
tape is not specified, the Stand-Alone DSC-2 Utility copies
the data onto the tape at the density at which the tape was
written previously. The /VE qualifier requests that the
contents of the tape be compared with the contents of the
disk to nake certain the copy operation was successful.

To terminate the Stand-Alone DSC-2 Utility,
following commands from the console terminal:
a.

type

the

Type <CTRL/P> in response to the prompt DSC>. The system
will respond with the console system prompt as follows:

»>
b.

Type HALT or the H command and press the RETURN key in
response to the above console system prompt. A message
confirming that the system has halted and the console
system prompt should be printed at the terminal as
follows:
HALTED AT •••
>>>

See the VAX-11 Utilities Reference Manual if the
DSC-2 Utility returns any errormessages.

10.

Label each magnetic tape with the following information:
•

The volume label of the disk backed up

•

The current date

•

The density at which the data was recorded

•

The relative volume number.
2-14

Stand-Alone

HANDLING FILES AND VOLUMES
2.5.~

Restoring the System Disk from Tape

The procedure below describes how to copy the contents of a magnetic
tape to disk. To perform this procedure, the operator must enter the
commands from the console terminal.
Procedure

Shut down the system by following the
procedure documented in Section 7.3.1.

Place a target volume in an available drive and ready the
device by pressing the RUN/STOP button or START/STOP switch.

Place the magnetic tape that contains the data to be restored
on a tape drive.
If this data is stored on more than one
tape, place the additional tapes on additional tape drives.

Verify that the system
drive.

Halt the CPU by typing:

console

SHUTDOWN.COM

medium

the

command

console

>»HALT

Type the following command to bootstrap the Stand-Alone DSC-2
Utility:
>>>BOOT DSC
The following
terminal:

message

will

printed

the

console

CPU HALTED
IN IT SEQ DONE
LOAD DONE, 00002000 BYTF.S LOADED
Please insert first system
type <RET>

diskette

Load the first Stand-Alone DSC-2 console
console drive and press the RETURN key.

cartridge

medium

into

and
the

After the operator presses the RETURN key, the console system
loads
the
Stand-Alone
DSC-2
Utility.
This
takes
approximately n minutes. Approximately three minutes later,
the following message will be displayed at the console
terminal:
VAX/VMS Version 2.0 19-0CT-79 18:1
Please insert second
<RET>

diskette

cartridge

and

type

At this point load the second Stand-Alone DSC-2 Utility
console medium into the console drive and press the RETURN
key.
Approximately one minute later·, at the completion of loading,
the following prompt will be printed at the console terminal:
DSC2>

2-15

HANDLING FILES AND VOLUMES

7•

A copy of the s tan d-A 1 one Ds C- 2 Ut i li t y fo r
F i 1 e s-11
Structure
Level
2 volumes is now running.
Type the
appropriate Stand-Alone DSC-2 Utility command to restore the
system disk as desired.
The following commands exemplify
different types of restoration.
DSC2>DBAO:/VE =MTAO:/RW
This command copies the contents of the tape mounted on MTAO
to the disk mounted on DBAO. The /RW qualifier causes the
tape to be rewound before the copy operation is started. The
/VE qualifier requests that the contents of the tape and disk
be compared to ensure the copy operation was successful.
DSC2>DBAO:/VE ::: MTAO: ,MTAl:/RW
In this example, the Stand-Alone DSC-2 Utility copies the
contents of the tapes mounted on MTAO and MTAl to the disk
mounted on DBAO. First, the Stand-Alone DSC-2 Utility copies
the contents of the tape mounted on MTAO. When all the data
on the tape has been copied and verified, the Stand-Alone
DSC-2 Utility begins to copy the contents of the second tape.
The /RW qualifier ensures both tapes are rewound before
either copy operation begins.
The /VE qualifier requests
that the Stand-Alone DSC-2 Utility perform a verification
pass after each volume reaches end-of-tape. When the verify
pass reaches end-of-tape on the first volume, the copy
operation continues on the second volume.

To terminate the Stand-Alone DSC-2 Utility type the following
commands from the console terminal:
a.

Type <CRTL/P> in response to the prompt DSC>. The system
will respond with the console system prompt (>>>) as
follows:

»>
b.

Type HALT or the H command and press the RETURN key in
response to the above console system prompt. A message
confirming that the system has halted should be printed
at the terminal as follows:
HAL'I'ED AT •••

Refer to the VAX-11 Utilities Reference Manual jf the
Stand-Alone DSC-2 Utility returns any ve-rTffcatTon--messages.

10.

Label the disk with the following information: the name of
the tape from which the data was restored and the current
date.

2-15

HANDLING FILES AND VOLUMES
2.5.7

Backing Up a Public Disk to Disk

The procedure below describes how to copy the contents of a public, or
nonsystem, disk to another disk. A public disk is a disk that has
been mounted by use of the /SYSTEM qualifier.
This procedure is performed online. The operator need only write-lock
the device to prevent users from changing any data on the disk.
However, users still can read data.
Procedure
1.

Issue the following command to warn all users that the disk
will be dismounted and write-locked so the contents of the
disk can be copied to another disk:
$ REPLY/ALL/BELL "message-text"
This message should include the name of the source disk being
write-locked and indicate in how many minutes the write-lock
will occur.

At the time
indicated
DISMOUNT/NOUNLOAD command
disk as follows:

by
to

the
message,
issue
the
logically dismount the source

$ DISMOUNT/NOUNLOAD device-name
3.

Write-lock the source disk by pressing the WRITE-PROTECT
switch to the ON position. This switch is located on the
front panel of the disk drive.

Mount the source
follows:

disk

again

using

$ MOUNT/SYSTEM device-name:
5.

the

MOUNT

command

volume-label

Allocate a drive for the target volume by typing:
$ ALLOCATE device-name:

Place the target volume in the allocated drive and ready the
device by pressing the RUN/STOP button or the START/STOP
switch.

Mount the target volume by issuing the following command:
$ MOUNT/FOREIGN device-name:

Issue the following command to find out the
of the source disk:

structure

level

$DIRECTORY device-name:[O,O]
The above DIRECTORY command requests a listing of the master
directory.
If the directory listing is alphabetized, it
usually is a Files-11 Structure Level 2 volume;
otherwise,
it usually is a Files-11 Structure Level 1 volume.

2-17

HANDLING FILES AND VOLUMES
9.

Run the appropriate
following commands:
a.
b.

DSC

Utility

typinq

one

the

$ RUN SYS$SYSTEM:DSC1
DSC> output-device-name:/VE

input-device-name:

$ RUN SYSSSYSTEM:DSC2
DSC> output-device-name:/VE

= input-device-name:

10.

See the VAX-11 Utilities Reference Manual if the DSC
returns any ve r if i caET6-n-·er_r_6_r___messages.

11.

Dismount and deallocate the target volume by typing:

Utility

$ DISMOUNT device-name:
$ DEALLOCATE device-name:

12.

Remove the target volume from the drive and put n label on
the outside of the volume that specifies the volume lnbel and
current date.

13.

Dismount the source
command as follows:
$

disk

typing

DISMOU~T/NOUNLOAD

DISMOUNT/NOUNLOAD device-name:

14.

Write-enable the source disk by
switch to the OFF position.

15.

Remount the source
follows:

disk

pressing

typinq

$ MOUNT/SYSTEM device-name:
l~.

the

WRITE-PROTECT

MOUNT

command

volume lnbel

Inform all users that the source disk is
write-locked by issuing the following command:

longer

$ REPLY/ALL/BELL "message-text"

Examples
1.

$REPLY/ALL/BELL "DMA2:

WILL BE WRITE-LOCKED IN 5 MINS.

FOR BACK-UP."

OPAO:,SYSTEM
0h:31:?.9.78
"DMA2: WILL BE WRITE-LOCKED IN 5 MINS FOR BACr<-UP."
$ DISMOUNT/NOUNLOAD DMA2:
$ MOUNT/SYSTEM DMA2: DMA4
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, DMA4
mounted on DMA2:
$ ALLOCA'rE DMAl:
DMAl: ALLOCATED
$ MOUNT/FOREIGN DMAl:
%MOUNT-I-MOUNTED, RUTH
mounted on DMAl:
$DIRECTORY DMA2:[0,0J

2-18

HANDLING FILES AND VOLUMES
Directory _DMA2: [000,000]
000000.DIR;l
BITMAP.SYS;l
SYSTEST.DIR;l

BACKUP.SYS;l
CONTIN.SYS;l
VOLSET.SYS;l

BADBLK.SYS;l
CORIMG.SYS;l

BADLOG.SYS;l
INDEXF.SYS;l

Total of 10 files.
$ RUN SYS$SYSTEM:DSC2
DSC2>DMA1:/VE=DMA2:
DSC -- 45 STARTING VERIFY PASS
DSC2>~Z

$ DISMOUNT DMAl:
$ DEALLOCATE DMAl:
$ DISMOUNT/NOUNLOAD DMA2:
$ MOUNT/SYSTEM DMA2: DM4
%MOUNT-I-MOUNTED, DM4
mounted on DMA2:
$ REPLY/ALL/BELL "DMA2: IS NO LONGER-WRITE-LOCKED."

OPAO:,SYSTEM
On:46:44,23
"DMA2: IS NO LONGER WRITE-LOCKED."
$

The operator informs all system users that DMA2 will
dismounted
and write-locked for back-up purposes.
operator logically dismounts the source disk, write-locks
and then remounts it. After remounting the source disk,
operator performs the necessary steps to mount and ready
target disk.

be
The
it,
the
the

The operator uses the DIRECTORY command to request a listing
of
the
master
directory.
When
this
directory is
alphabetized, the volume usually has a Files-11 Structure
Level 2 format.
When the master directory is randomly
ordered, the volume usually has a Files-11 Structure Level 1
format.
The operator then performs the copy operation by using the
RUN SYS$SYSTEM:DSC2 command. The qualifier /VE requests that
the contents of both disks be checked against each other to
ensure that the copy operation was successful. DSC informs
the operator when the verify pass begins. At completion, the
prompt DSC2> returns.
To terminate the DSC2 Utility, the
operator presses <CTRL/Z>.
The dollar sign prompt ($)
returns.
The operator then dismounts and deallocates the target disk,
dismounts, write-enables, and remounts DMA2, and finally,
informs all users that DMA2 can be written to.

2-19

HANDLING FILES AND VOLUMES

Selective Back-Up of Files

2.5.8

The procedure below describes how to copy selected files from one disk
to ~nother.
Generally, if 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 nnd the
system will begin processing the commands in the command procedure.
For more information on creating command procedures,
VAX/VMS G~id~~-~-~- _us i_!1_5J_~ol'.1~~11-~.~!:_~cedur_es.

refer

the

Procedure
1.

Allocate a drive for the target volume by typing:
$ALLOCATE device-name:

Place the target volume in the allocated drive.
Ready that
device
by pressing either the RUN/STOP button or the
START/STOP switch.

Mount the target volume by typing:
$MOUNT output device-name:

volume-label

NOTE
When the target volume has not been
initialized previously or is an RP05 or
an RPOn, mount the volume using the
/FOREIGN qualifier, run BAD, dismount
the volume, and then initialize it.
Refer to the VAX-11 Utilities Reference
Manual for more information on BAD.
4.

Type the following command to allocate a drive for the source
disk:
$ ALLOCATE source-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 source-device-name:

volume-label

Create directories on the target volume by typing:
$CREATE/DIRECTORY output-device-name:[directoryJ
Generally, the operator creates a separate directory for each
user who has files to be backed up.

2-20

HANDLING FILES AND VOLUMES

Copy the files from the source disk to the target
typing the following command:
$COPY

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

volume

output-device: [directory]

This command is repeated for each file that is to be copied.
If a user has several files of the same file name, type, or
version, the operator can use wild card characters to
indicate them. See the VAX/VMS Command Language User's Guide
for more information on wild card characters.
9.

Dismount and deallocate the target volume by typing:
$ DISMOUNT device-name:

$ DEALLOCATE device-name:

10.

Remove the target volume from the device and affix a label to
the outside of it that indicates the volume label and the
current date.

11.

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

12.

Remove the source disk from the device.

Examples

ALLOCATE DMAO:
DMAO: ALLOCATED
$ MOUNT DMAO:
MYVOLUME
%MOUNT-I-MOUNTED, MYVOLUME
mounted on DMAO:
$ ALLOCATE DMAl:
DMAl: ALLOCATED
$ MOUNT DMAl:
DATCOM
%MOUNT-I-MOUNTED, DATCOM
mounted on DMAl:
$ CREATE/DIRECTORY DMAO: [RMSTST]
$ CREATE/DIRECTORY DMAO: [FORMAB]
$ CREATE/DIRECTORY DMAO: [SYSTEM]
$COPY DMAl:[RMSTST]*.*
DMAO: [RMSTST]
$COPY DMAl:[FORMAB]*.COM
DMAO: [FORMABl
$COPY DMAl:[SYSTEM]DUNGEON.*
DMAO: [SYSTEM]
$ DISMOUNT DMAO:
$ DEALLOCATE DMAO:
$ DISMOUNT DMAl:
$ DEALLOCATE DMAl:
$

The operator copies files from three directories on DMAl to
three newly created directories on DMAO. After performing
the necessary steps to mount and ready the target and source
volumes, the operator creates three directories [RMSTST],
[FORMAB], and [SYSTEM] on the target volume. Using the COPY
command, the operator copies:
•

All the files in the [RMSTST] directory on the source
disk to the [RMSTST] directory on the target volume

All the files of the file type COM in the [FORMAB]
directory on the source disk to the [FORMAB] directory
on the target volume

2-21

HANDLING FILES AND VOLUMES

•

All the files with the file name DUNGEON in the
[SYSTEM] directory on the source disk to the [SYSTEM]
directory on the target volume

Upon completion of the copy operation, the operator dismounts
and deallocates the target and source volumes.

2-22

HANDLING FILES AND VOLUMES
Backing Up the Console Medium

2.5.9

The procedure below outlines steps required to back up the console
medium to a Files-11 structured volume. Included in this procedure is
CONSCOPY.COM, the command procedure used for backing up the console
medium.
CONSCOPY.COM backs up the console medium by copying the
medium onto a Files-11 structured volume such as tape, disk, or floppy
diskette. To restore the console medium from a Files-11 volume, refer
to the procedure that follows this one.
Procedure

Allocate a device for the target volume as follows:
$ ALLOCATE device-name:

Then mount the target volume as follows:
$ MOUNT device-name:

volume-label

The system should respond with an information message similar
to the one below:
%CLI-I-MOUNTED,volume-label

mounted on

device-name:

The above message informs the operator the volume was mounted
successfully and notes the name of the device on which the
volume was mounted.
3.

Create an empty directory on the target volume by typing:
$ CREATE/DIRECTORY device-name: [directory]

Insert the console medium into the console drive.

Type the following command string to invoke CONSCOPY.COM:
$ @[SYSUPD]CONSCOPY

CONSCOPY.COM responds with the informative message:
This command file requires CMEXEC, CMKRNL privileges.

After the above message informs the operator which user
privileges are needed to execute the CONSCOPY.COM command
procedure, a brief summary of CONSCOPY.COM follows.
7.

CONSCOPY.COM then prompts for the target
directory names:

volume

device

and

What is the files-11 device and directory (DDUC: [DIRECTORY]):
Type the target volume device and directory names.
8.

The procedure then asks:
rs your console medium a floppy diskette?

(Y/N):

Answer SAVE to the following question:
Do you wish to SAVE or RESTORE your console

2-23

~edium?:

HANDLING FILES AND VOLUMES
10.

The procedure then instructs:
Insert the medium to be saved into the
type <ret> when ready:

console

device,

11.

After pressing the RETURN key, the system will respond with
an information message, similar to the one in Step 2. The
message informs the operator that the console medium was
successfully mounted and provides the device name on which
the medium was mounted. CONSCOPY.COM proceeds to back up the
console medium onto the target volume.

12.

When CONSCOPY.COM completes the back-up
message below is printed at the terminal:
Backup of the console medium is now
the medium from the console <lrive.

13.

procedure,
complete.

the
Remove

Mount the console medium by typing:
$ MOUNT/FQREIGN/SYSTEM/PROTECTION=(SYSTEM:RWLP) CSAl: CONSOL

Examples
1.

ALLOCATE DMAl:
DMAl: ALLOCATED
S MOUNT DMAl:
% MOUNT-I-MOUNTED,SURE mounted on DMAl:
$ CREATE/DIRECTORY DMAl: [WHYNOT) $ @[SYSUPD) CONSCOPY
$

This command file requires CMEXEC,CMKRNL privileges.
This command file saves the contents of the console medium on the
user-specified device and directory, or restores the console medium from
the files in the user-specified device and directory.
On a restore operation, the entire contents of the specified directory are
transferred to the output device; therefore only the files necessary to rebuild the medium should be placed in the directory.
What is the files-11 device and directory (DDCU: [DIRECTORY]): DMAb[WHYNOT]
Is your console medium a floppy diskette? (Y/N): Y
Do you wish to SAVE or RESTORE your console medium?:
SAVE
Insert the medium to be saved into the console device,
type <ret> when ready: ~
%MOUNT-I-MOUNTED,
mounted on CSAl:
!
!

Backup of the console medium is now complete.
from the device.

Remove the medium

MOUNT/FOREIGN/SYSTEM/PROTECTION: (SYSTEM:RWLP) CSAl: CONSOLE
%MOUNT-I-MOUNTED, CONSOLE
mounted on CSAl:

In this example, the operator backs up the console Medium to
a disk on the device DMAl in the directory WHYNOT. The
operator begins the back up operation by allocating the disk
drive DMAl.
Then the operator mounts the disk labeled SURE
on the disk drive.
Once the
operator
receives
the
information message that the disk was successfully mounted,
the operator invokes the CONSCOPY.COM command procedure.
CONSCOPY prompts the operator for the following information:
•

The name of the device and directory to which the
contents of the console medium are to be backed up

2-24

HANDLING FILES AND VOLUMES

•

Whether the console medium is a floppy diskette

•

Whether the
restored

•

Whether the console medium is in the console drive

console

medium

should

saven

The CONSCOPY.COM command procedure then proceeds to back up
the console medium to the disk volume. CONSCOPY.COM informs
the operator when the back up procedure has finished backing
up the console medium.
The operator removes the console
medium from the console drive. The operator then Mounts the
standard console medium.

2-25

HANDLING FILES AND VOLUMES
2.5.10

Restoring the Console Medium from Disk

The procedure below outlines steps required to restore the contents of
the console medium from a Files-11 structured volume. Included in the
procedure below is CONSCOPY.COM, the command procedure that restores
the contents of the console medium from the Files-11 structured
volume. To back up the console medium to a Files-11 structured
volume, refer to the preceding procedure.
Procedure
1.

Locate the directory on the Files-11 structured volume that
contains the contents of the console medium to be restored.

Dismount and remove the current console medium,
by typing:
$

mounted,

DISMOUNT CSAl:

Type the following command string to invoke CONSCOPY.COM.
$

@[SYSUPD] CONSCOPY

The above command string invokes CONSCOPY.COM which
with the informative message:

responds

This command file requires CMEXEC,CMKRNL privileges.

After this message informs the operator which user privileges
are required to execute the CONSCOPY.COM command procedure, a
brief summary of the procedure follows.
5.

CONSCOPY.COM then
directory names:

prompts

for

the

Files-11

device

and

What is the Files-11 device and directory (DDUC: [DIRECTORY]):
Type the device and directory names.
~.

The procedure then asks:
Is your console medium a floppy diskette?

(Y/N):

Answer RESTORE to the following question:
Do you wish to SAVE or RESTORE your console medium?:

The procedure instructs:
Insert the medium to be saved into the
type <ret> when ready:

console

device,

After the operator presses the RE'rURN key, the system
responds with an information message similar to the one
below:
%MESSAGE-I-MOUNTED, volume-label

mounted on

CSAl:

The above message informs the operator that the console
medium has been successfully mounted on CSAl. CONSCOPY.COM
proceeds with the restoration of the console medium, which
takes approximately 5 minutes.

HANDLING FILES AND VOLUMES
10.

When CONSCOPY.COM completes the
restore
operation,
a
directory listing the files that were restored to the volume
is printed at the terminal.

11.

CONSCOPY.COM then prints the informative message:
If no bootstrap file is to be written on the console
medium type only a <RET> in response to the next query.
The name of
CONSOL.SYS.

12.

the

bootstrap

file

supplied

DEC

The query asks:
What is the name of the bootstrap file?:
If the file name CONSOL.SYS is typed in response to the above
query, a bootstrap block that directs the system to the
bootstrap file CONSOL.SYS will be written onto the restored
console medium.
A bootstrap block must be present if the
console medium being restored will be used to bootstrap a VMS
system.
If the RETURN key is pressed, no bootstrap block
will be written to the console medium being restored.

13.

When restoration of
procedure informs:

the

console

medium

Restoration of the console medium is
the medium from the device drive.
14.

Remove the console medium that
standard console medium.

was

copied

complete,

complete.
and

the

Remove

insert

the

Mount the standard console medium and type:
$ MOUNT/FOREIGN/SYSTEM/PROTECTION=(SYSTEM:RWLP) CSAl: CONSOLE

Examples
1.

S Dismount CSAl:
S @. [SYSUPD] CONSCOPY
This command file requires CMEXEC,CMKRNL privileges.
This command file saves the contents of the console ~edium on the
user-specified device and directory, or restores the console medium from
the files in the user-specified device and directory.
On a restore operation, the entire contents of the specified directory are
transferred to the output device; therefore only the files necessary to rebuild the medium should he placed in the directory.
hat is the files-11 device and directory (DDCU: (DIRECTORY]): DMAl: [WHYNOTl
Is your console medium a floppy diskette? (Y/N): Y
Do you wish to SAVE or RESTORE your console medium?: RESTORE
Insert a scratch medium into the console device drive.
type <ret> when ready: (BITl
%MOUNT-I-MOUNTED, SCRTCH
mounted on CSAl:

2-27

HANDLING FILES AND VOLUMES
DIRECTORY CSl:
l-APR-80
ABBREV.HLP
BOOT .HLP
CONSOL.HLP
CONSOL.SYS
CRASH

11.
11.
31.
1.

< UNUSED >

80.

l-APR-80
l-APR-80
l-APR-80
l-APR-80
l-APR-80

80. FREE BLOCKS
TOTAL 400. BLOCKS IN 83. FILES
If no bootstrap file is to be written on the console medium type only a <RET>
in response to the next query.
The name of the bootstrap file supplied by DEC is CONSOL.SYS
What is the name of the bootstrap file?: CONSOL.SYS
!
!

Restoration of the console device is complete.
from the device drive.

Remove the medium

$ MOUNT/FOREIGN/SYSTEM/PROTECTION=(SYSTEM:RWLP) CSA!: CONSOLE
%MOUNT-I-MOUNTED, CONSOLP.
mounted on CSA!:

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

command

procedure

requests

the

following

•

The names of the device and directory that contain
the data to be restored onto the console medium. The
operator responds with DMAl:[WHYNOT].

•

Whether the console medium is a floppy diskette.

•

Whether to save or restore the console
operator responds by typing RESTORE.

•

Whether the console medium is inserted in the console
device drive. The operator responds by pressing the
RETURN key to indicate that the console medium is
inserted into the console device drive.

medium.

The

The CONSCOPY command procedure then performs the restoration
operation and, at completion, displays the directory listing
of the disk. Then CONSCOPY.COM requests the name of the
bootable
system
image.
The
operator
responds with
CONSOLE.SYS. A bootstrap block is written on the console
medium
and
the CONSCOPY.COM informs the operator the
restoration of the console medium is complete.
After the
operator removes the restored console medium from the console
drive, the operator then inserts and mounts the standard
console medium in the drive.

2-28

CHAPTER 3
CONTROLLING PRINT AND BATCH QUEUES

Although the system manager is responsible for creating print and
batch queues, the operator must be able to control these queues so
that the system can run smoothly.
This chapter describes the
procedures for controlling print and batch queues. Procedures for
creating new print and batch queues are described in the VAX/VMS
System Manager's Guide.

3.1

DEFINITION OF QUEUE

A queue is a list containing jobs that are
Jobs are executed according to priority.

waiting

executed.

Print jobs are placed in print queues by means of the PRINT command.
Batch jobs are placed in batch queues by means of the SUBMIT command.
Print queues can be any one of the following:

3.2

•

Physical-device queues -- queues associated
named for) a specific print device.

with

(that

is,

•

Generic queues -- queues from which jobs can be given to
available print device that has matching characteristics.

any

•

Named, or logical, queues -- queues that are not associated
with a print device. To obtain printed output from a logical
queue, the operator must explicitly assign the queue to a
print device. The ASSIGN/QUEUE command, described in Chapter
8, is used for this purpose.

COMMANDS FOR CONTROLLING PRINT AND BATCH QUEUES

The commands listed in Table 3-1 allow the operator to manipulate
queues and the jobs that they contain. The print and batch queue
commands that require special privileges are described in Chapter 8.
Appendix A alphabetically lists and gives a brief summary description
of all DCL commands.

3-1

CONTROLLING PRINT AND BATCH QUEUES
Table 3-1
Commands for Controlling Print and Batch Queues
Function

Command

1------- --·-~·-·----------------+--------------- ---------1

ASSIGN/MERGE

Removes all jobs from one print
queue and places them in another
queue

ASSIGN/QUEUE

Assigns a
queue

DEASSIGN/QUEUE

Deassigns a device from a queue

DELETE/ENTRY l, 2

Deletes an entry from a print or
batch job queue or stops printing
the current job

DELETE/QUEUE

Deletes print and batch queues

INITIALIZE/QUEUE

Creates print and batch queues

PRINT 1

Queues one or more files for
printing, either on a default
system printer or other device

SET DEVICE

Establishes the
spooling
and
error-logging status on a device

SET QUEUE/ENTRY 1, 2

Changes the status or attributes
of jobs in print or batch queues
that have not yet been processed
by the system

SHOW DEVICES 1

Displays the status of devices in
the system

SHOW QUEUE 1

Displays
the
names,
job
identification
numbers,
and
status of current and penning
jobs in print or batch queues

START/QUEUE

Starts print or batch queues

STOP 2

Halts execution of
procedure, program,
or detached process

STOP/ABORT l, 2

Stops printing a
currently printing

device

1. This command is described in the VAX/VMS
Guide.

Command

2. Allows a user with either operator
privilege to affect any job in the system.

(OPER)

logical

command
a
subprocess,
job

that

Language

User's

world

(WORLD)

(continued on next page)

3-2

CONTROLLING PRINT AND BATCH QUEUES
Table 3-1 (Cont.)
Commands for Controlling Print and Batch Queues
Function

Command
STOP /ENTRY l, 2

Stops executing a batch job that
is currently running and deletes
it

STOP/QUEUE

Suspends print queues
batch quet1e:3

STOP /REQUEUE l, 2

Stops printing a job that is
currently printing and requeues
that job, giving it a priority of

and

stops

SUBMIT l

Enters a job in a batch queue

1. This command is described in the VAX/VMS
Guide.

Command

2. Allows a user with either operator
privilege to affect any job in the system.

(OPER)

3.3

Langua!I~~er's

world

(WORLD)

PROCEDURES FOR CONTROLLING PRINT AND BATCH QUEUES

The following section contains step-by-step procedures for controlling
print and batch queues established on the VAX/VMS operating system.

3-3

CONTROLLING PRINT AND BATCH QUEUES

3.3.1

Merging Print Queues

When a problem occurs with a print device, the queue associated with
that print device should be rerouted to another print device. The
procedure below describes how to merge two print queues without losing
j-0bs in either queue.

Procedure
1.

Stop the queue associated with the malfunctioning
device by issuing the following command:

$ STOP/QUEUE/NEXT queue-name!

This command inhibits further dequeuing but permits the
current job to be completed. However, if the print device is
inoperable, the current job will not be completed.
2.

Requeue the current job by typing the following command:
$ STOP/REQUEUE queue-name!
By requeuing the current job, this command ensures this job
will be printed in its entirety. Other jobs in the queue
will not be dequeued because the queue is stopped.

Take the device offline.

Reroute the jobs queued to the malfunctioning print device to
another print device by entering the following command:
$ ASSIGN/MERGE queue-name2 queue-name!
The operator should check that the characteristics of the new
print device are appropriate for the new jobs.

Optionally,
delete
the
queue
associated
malfunctioning print device by typing:
$ DELETF./QUEUE

with

the

queue-name

Example
1.

$STOP/QUEUE/NEXT

LPBO

$ STOP/REQUEUE
LPBO
$ ASSIGN/MERGE LPAO
LPBO
$ DELETE/QUEUE
LPBO

The STOP/QUEUE/NEXT command prevents further dequeuing from
the LPBO queue. The STOP/REQUEUE command terminates the job
currently being printed or attempting to print and places it
back in the queue with a priority of 1. The next job in the
LPBO queue will not be dequeued because the queue has been
stopped.
The ASSIGN/MERGE conmand removes the jobs from the
print queue LPBO and places them in the print queue LPAO.
The print queue LPBO is then deleted by means of the
DELETE/QUEUE command.

3-4

CONTROLLING PRINT AND BATCH QUEUES
Preventing Loss of Data When the Line Printer Runs Out of Paper

3.3.2

The procedure below describes how to prevent loss of data while
is loaded in the line printer.

paper

When a line printer runs out of paper,
OPCOM prints the
following
message on the operator's terminal to indicate that the device is not
ready:
Opcom, hh:mm:ss.cc, device is offline, device-name

Procedure
1.

Suspend the current queue operation by issuing the
command:

following

$ STOP/QUEUE queue-name
The SHOW QUEUE queue-name command will now show the queue
PAUSED.

Take the printer offline.

Load a new box of paper in the printer and return the printer
to the online condition.

Resume printing by entering the command:

$ START/QUEUE/optional-qualifier queue-name
Note that the operator can optionally append one of
the
following qualifiers
to
the above command to insure the
output of the interrupted print job is complete:
/BACKSPACE

Backspaces
resumes.

/TOP_OF_FILE

Starts at the
beginning of the
job and
prints the job that was being printed when
the paper ran out.

one

page

before

printing

Example
1.

Opcom, 22:08:43.40, device is offline, LPAO:
$ STOP/QUEUE LPAO
$ START/QUEUE/TOP_OF_FILE

LPAO

OPCOM notifies the operator that
line printer LPAO went
offline
at 22:08:43.40.
The operator stops the queue
associated with the printer and takes
the printer offline.
After loading a new box of paper in the printer, the operator
returns
the printer
to the online condition.
Printing
resumes after
the operator types the START/QUEUE command.
The /TOP OF FILE qualifier indicates that the job which was
being printed when the operator issued the STOP/QUEUE command
will be restarted at the beginning of the file.

3-5

CONTROLLING PRINT AND BATCH QUEUES
Terminating the Execution of a Batch Job

3.3.3

The procedure below describes how to terminate the execution of a
batch job. The operator usually performs this task only if the system
manager or the owner of a job requests that the job be terminated.

Procedure
1.

Type the following command to determine the job number of the
batch job and the name of the queue in which the job is
located:
$ SHOW QUEUE/BATCH/ALL

Delete the
commands:

batch

job

issuing

$ STOP /ENTRY=j ob-number
$ DELETE/ENTRY=job-number

one

the

following

queue-name
queue-name

Example
1.

$ SHOW QUEUE/BATCH/ALL

* Batch Queue "SYS$BATCH" Joblim=n, Basepri=4, Swap
Current Job
current Job
Current Job
Current Job
Current Job
$ STOP/ENTRY=207

37n
315
313
312
207

DEBUG
JEROME
SYSTEM
SYSTEM
LANGLEY

DBGBUILD
BEGINBLD
DELETE LO
LNK32
FORPROG

Pr i=4,
Pri=4,
Pri=4,
Pr i=4,
Pri=4,

24-,JUL-1980
24-JUL-1980
24-JUL-1980
24-JUL-1980
24-JUL-1980

SYSSBATCH

A user has requested that job 207 be stopped.
The operator
types the SHOW QUEUE/BATCH/ALL command to determine the queue
in which the job has been entered. The display shows that
job 207 is in the SYS$BATCH queue. The operator then deletes
the job by typing the STOP/ENTRY command.

3-n

11: 09
10:05
09:57
09:57
09:24

CONTROLLING PRINT AND BATCH QUEUES
Terminating the Printing of a Print Job

3.3.4

The procedure below describes how to terminate a print job that is
currently being printed on a print device. The operator usually
performs this task only if the system manager or the owner of a job
requests that the job be terminated, or if the operator observes
garbled output on the print device.
Procedure
1.

Enter the following command:
$ STOP/ABORT print-device

The above command terminates the current
printing the next job in the queue.

job

and

begins

Example
1.

$ STOP/ABORT

LPAO

This command terminates the printing of the current print job
on LPAO.
The next job in the queue is immediately dequeued
for printing.

3-7

CONTROLLING PRINT AND BATCH QUEUES
Removing a Batch or Print Job from a Queue

3.3.5

The procedure below describes how to delete a batch or print job that
has been entered in a queue but has not yet been processed. The
operator usually performs this task only if the system manager or the
owner of the job requests that the job be deleted.

Procedure
1.

Type the following command to determine the job number
the name of the queue in which the job is located:

and

$ SHOW QUEUE/DEVICES/ALL
2.

Delete the job by issuing the following command:
$ DELETE/ENTRY=job-number queue-name

Example
1.

$ SHOW QUEUE/DEVICES/ALL

* Generic Device Queue "SYSSPRINT" Flag

* Device Queue "LPAO" Forms=O, Genprt lower flag
Current Job 1327 RAP

ASHLEY , Pri=4,

5-JUL-80

15:~

* Device Queue "LPBO" Forms=O, Genprt Lower Flag
* Device Queue "LPDO" Forms=O, Nogen Lower
* Device Queue "SYS$HOUSTON" Forms=O, Nogen
This queue assigned to LPDO

* Device Queue "SYSSLPDOC" Forms=O, Nogen Flag
This queue assigned to LPCO

* Devi~e Queue "LPCO" Forms=O, Nogen lower Flag
Current Job 1328 SMITH
$

DELETE/ENTRY

OEUVRE

Pri=4,

5-JUL-80

= 1328 LPCO

A user has requested that job 1328 be deleted. The operator
types the SHOW QUEUE/DEVICES/ALL command to determine in
which queue the job has been entered. The display shows that
job 1328 is in the LPCO queue. The operator then aborts the
job by typing the DELETE/ENTRY command and by specifying the
job-number 1328.

3-8

1~:10

CHAPTER 4
USING THE CARD READER

The card reader is used by the operator to read card decks. Users may
submit to the operator the two following types of card decks for
processing:
•

Batch job card decks

•

Data card decks

An operator must understand the two types of card decks and how to
tend the card reader in order to use the card reader and ensure card
decks are processed efficiently. This chapter describes which cards
the operator should check before processing a card deck through the
card reader and how to determine which cards are damaged.
Section
4.3.2 outlines a procedure for processing a card deck through the card
reader.

4.1

TYPES OF CARD DECKS

Before loading a card deck into the card reader, the
determine:

4.1.1

operator

should

•

Whether the deck is a batch job or a data deck, because
processing requirements differ.

their

•

Whether the card reader is
mode.

set

the

correct

translation

Batch Job Card Deck

A batch job card deck can be divided into three segments: the initial
cards, those that follow, and the last card. The initial two cards in
a batch job card deck are the $JOB and the $PASSWORD cards.
These
cards log in the user and the batch job to the system. Following the
initial two cards are program cards.
Program
cards
contain
instructions which direct the system to libraries, routines, and data
needed to complete the batch job. The last card must be either an
End-Of-Job command card ($EOJ) or an End-Of-File (EOF) card. Both of
these cards tell the system this is the end of the job.

4-1

USING THE CARD READER
4.1.1.1 Checking Batch Job Card Deck Input - When a batch job is
inserted into the card reader input hopper for processing, the first
two cards in the card deck must be:
•

A $JOB card

•

A $PASSWORD card

The system cannot execute the job without these cards.
If the
operator is given a card deck with these cards omitted, the operator
should return the deck so the user can insert these cards.
The last card in the deck must be one of the following:
•

A $EOJ card

•

An EOF card (12-11-0-1-n-7-8-9 overpunch)

If the last card is not one of these end cards, the operator can
one on the card punch and insert it at the end of the deck.

type

4.1.1.2 Checking Batch Job· Output - The log file produced by a card
reader batch job is queued for printing to the default system print
queue, SYS$PRINT. To have the log file queued to a different queue,
the user can include an $ASSIGN or $DEFINE card in the job to redefine
SYS$PRINT. The VAX/VMS Command Language User's Guide explains how to
use the ASSIGN and DEFINE commands.
If an error occurs while the system is attempting to validate the $JOB
and $PASSWORD cards, a listing containing the error message is queued
to SYS$PRINT. The user's name (if any) on the listing flag page is
the user's name from the $JOB card. The job name is INPBATCH.ERR.
When the user's name cannot be determined from the $JOB card, the deck
is simply flushed through the card reader and no listing is queued.

4.1.2

A Data Card Deck

A data deck is a deck of cards containing data that either will be
read by a program or copied to a file for later use. The process that
will read the data deck usually is associated with an interactive user
at a terminal or a batch job that is submitted by an interactive user.
Since the user and process already are logged in to the system, the
first card can contain any data the user wants to specify. However,
the program must read the exact number of cards supplied, or the last
card should be an EOF card (12-11-0-1-fi-7-8-9 overpunch) to inform the
program that this is the end of the data deck.

4.1.2.1 Checking Data Deck Input - When a user wants a data deck to
be read, the operator should ensure that the user has allocated the
card reader. If the card reader is not allocated, the system tries to
submit the deck as a batch job and subsequently just flushes the deck
through the reader, rejecting the job.
If the program does not read the exact number of cards, as with the
COPY command, the EOF card (12-11-0-1-6-7-8-9 overpunch) must be the
last card in the deck to inform the program that this is the end of
the deck. Without this card, the program waits indefinitely for more
cards and the system prints "card reader offline" messages on the

4-2

USING THE CARD READER

operator's terminal. If the card deck lacks an EOF card, the operator
can type an EOF card on a card punch and insert it at the end of the
deck.

4.2

CARD READER TRANSLATION MODES

For the system to read input properly, the card reader must be set to
the correct translation mode. The translation mode used must be the
same as the translation mode of the card punch on which the cards were
punched.
VAX/VMS
supports 02n and 029 card punches.
(These
translation modes are discussed in detail in the VAX/VMS I/O User's
Guide and the VAX/VMS Guide to Using Command Procedures.)

4.2.1

Setting the Translation Mode

For the operator to set the card reader
mode either:

the

correct

translation

•

The first card in the deck must be the translation mode
or

card,

•

The operator must know
punched

were

the

mode

which

the

cards

Without the above information, the operator cannot set the card reader
to the correct translation mode.
To set the translation mode of the card reader for many decks of the
same type, use the SET CARD READER command. This command is fully
described in the VAX/VMS Command Language User's Guide.
By default,
when the system is bootstrapped, the translation mode is set to 029.

4.3

TENDING THE CARD READER

The operator's job of tending the card reader includes:
•

Ensuring that the cards in batch jobs and oata decks
properly ordered as discussed in the preceding pages

•

Replacing physically defective cards

•

Operating the card reader
NOTE
For more information on card reader
batch
jobs
from
a
system user's
viewpoint, refer to the VAX/VMS Guide to
Using Command Procedures.

4-3

are

USING THE CARD READER
4.3.1

Replacing Physically Defective Cards

Even when the card deck contains all the required cards, the card
reader may not be able to read the deck. This usually occurs because
one or more cards are physically defective.
If the deck contains a faulty card, one of the error indicators
located on the front panel of the card reader lights up when the card
is read. The card reader goes offline, and operator intervention is
required to put it back online. Table 4-1 at the end of this chapter
describes the error indicators, reasons why they may light up, and the
operator action required to correct the situation.

4.3.2

Operating the Card Reader

The following section contains a step-by-step procedure for processing
card decks through the card reader.
Procedure

This procedure describes how to load and process a card deck through a
card reader.
1.

Remove the card weight from the input hopper.
Place the
cards, face down and with column 1 on the left, in the
hopper. Ensure that the first card to be read is at the
bottom of the hopper.
NOTE
Do not pack the input hopper so full
that the air from the blower cannot
riffle the cards.
If the cards are
packed too tightly, the vacuum picker
cannot operate properly.

Press the RESET button. The HOPPER CHECK error indicator and
the STOP light will go out and the cards will be read.
~OTE

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

Remove the cards from the output stacker when the
CHECK error indicator and the STOP light are lit.
NOTE
If the STOP button is
accidentally
pressed while the card deck is being
read, return the last card in the output
hopper to the bottom of the input hopper
and press the RESET button.

4-4

HOPPER

USING THE CARD READER
4.

If the cards are not read properly after the RESET button has
been
pressed,
refer to Table 4-1 below for recovery
procedures.
Table 4-1
Card Reader Errors: Causes and Corrective Actions

.----------~----------

Error Indicator
READ CHECK

--·---·-··-- Corrective Action

·-----,.------------·-

Causes
Card edges torn
Punch in column O or 81

Remove the f aulty card from the
output stac ker, duplicate the
card, place it in the input
hopper, and press the RESET
button
If READ CHECK occurs for all
cards, the read logic of the
card reader is malfunctioning

PICK CHECK

Damage to leading edge
Torn webs
Cards stapled together

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

STACK CHECK

HOPPER CHECK

Badly mutilated card

Correct the jam and/or remove
the mutilat ed card from the
output stac ker, duplicate the
card, place it in the input
hopper, and press the RESET
button

Input hopper empty

Load the input hopper

Output stacker full

Unload the output stacker

Jam in the card track

~---------'----------------'------------------·----

4-5

CHAPTER 5
THE ERROR LOG FILE

The system automatically writes messages to the latest version of
error log file as the following events occur:

the

•

Errors
Device errors, machine
checks,
bus
errors,
Synchronous Backplane Interconnect (SBI) alerts, soft Error
Correction Code (ECC) errors, asynchronous write errors, hard
ECC errors

•

Configuration Changes -- Volume mounts and dismounts

•

System Events -- Cold start up, warm start up, crash start up,
message from Send Message to Error Log system service, time
stamp

Because the information in the error log file is essential for
efficient maintenance of the system, the operator may be asked to
maintain this file and to print copies of the file for the system
manager.

5.1

MAINTAINING THE ERROR LOG FILE

The error log file
(SYS$SYSDISK: [SYSERR]ERRLOG.SYS)
system disk in the [SYSERR] directory.

resides

the

The error-logging facility consists of three parts:
•

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

•

A program called ERRFMT that periodically empties the error
log buffers, transforms the descriptions of the errors into
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 by ERRFMT

the

The executive routines and the ERRFMT program operate continuously
without operator intervention.
The routines fill the error log
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
file.
Then SYE can use ERRLOG.SYS as its input file to create an
error log report as its output file.
While SYE is accessing
information into it.

ERRLOG.SYS, ERRFMT cannot write any error
If SYE is accessing the highest version of

5-1

THE ERROR LOG FILE

ERRLOG.SYS when ERRFMT needs to log an error, ERRFMT creates a new
version of the file. The new version continues logging errors where
the previous version stopped.
All versions of the ERRLOG.SYS file remain on the system disk
(SYS$SYSDISK)
until they are explicitly deleted.
Therefore, the
system manager or the operator must devise a plan for regular
maintenance of the error log file.
One way to maintain the versions of this file is to rename the highest
version of the ERRLOG.SYS file on a daily hasis. To free space on the
system disk, the operator can then back up the old versions of the
file onto a different volume and delete these versions from the system
disk. The operator should not delete an error loq file that has not
been backed up. A detailed example of this maintenance procedure is
provided below.

5.2

PRINTING THE ERROR LOG FILE

The procedure below describes how to rename a formatted error log file
and obtain a copy of it.
Note that these instructions are for
renaming and printing one version of the error log file at a time.
For a complete description of the SYE Utility, refer to the VAX/VMS
Systef!l Ma_~ge~~-_g~id. ~.
Procedure

Set the default disk to the system disk and the default
directory to [SYSERR] by typing the following command:
$ SET DEFAULT SYSSSYSDISK: [SYSERR)

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

the

$ DIRECTORY ERRLOG.SYS
3.

Rename all versions of the ERRLOG.SYS file, one at a time, to
ERRLOG.OLD by issuing the command:
S RENAME/LOG ERRLOG;n

ERRLOG.OLD

NOTE
To preserve the chronological order of
the files after renaming, first rename
the oldest version of ERRLOG.SYS (the
version with the lowest version number,
n), then rename versions n+l, n+2, and
so on.
Do not use a wild card character in the
version field of the file specification
to rename more than one version of
ERRLOG.SYS at a time. When a wild card
character is used for n, the most recent
version of ERRLOG.SYS is renamed first,
thereby reversing
the
chronological
order of the renamed files.

5-2

THE ERROR LOG FILE
4.

Invoke the SYE Utility to format the error log file
readable error log report by typing the command:

into

$ RUN SYS$SYSTEM:SYE
After the above command string is processed, the SYE Utility
prompts for input and output file specifications, options, a
device name, and entry dates.
5.

Respond to the SYE prompt by specifying the name of the error
log file and the type of output desired. Note that if the
operator responds to all the SYE Utility prompts by pressing
the
RETURN
key,
the
SYE
Utility
defaults to the
specifications contained in the square brackets (as shown in
the example below) •

Obtain a printed copy of the error log report by entering an
output file name in response to the SYE prompt for an output
file as shown in the example below. Then enter the following
command:
$ PRINT file-name
The file name indicates the name of the file
error log report.

containing

the

Example
1.

$ SET DEFAULT SYS$SYSDISK: [SYSERR]
$ DIRECTORY ERRLOG.SYS
Directory DBAO: [SYSERR]
ERRLOG.SYS;l
Total of 1 File.
$ RENAME ERRLOG.SYS ERRLOG.OLD
$ RUN SYS$SYSTEM:SYE
SYE VERSION 2.1
input file:
[ [SYSERR]ERRLOG.OLD
-output file:
[SYS$0UTPUT]
-options:
[ROLL-UP]
-device name:
[<CR>]
-after date:
[FIRST ENTRY]
-before date:
[LAST ENTRY]

?ID
?ERRLOG.LIS
?ID
?ID
?ID
?ID

%SYE-I-SUCCOM, SUCCESSFUL COMPLETION
$ PRINT ERRLOG.LIS
The SET DEFAULT command sets the operator's default disk and
directory to DBB2:[SYSERR]. The DIRECTORY command lists all
the ERRLOG.SYS files contained in the [SYSERR] directory. In
this
example,
[SYSERR]
contains only one version of
ERRLOG.SYS.
The RENAME command renames
ERRLOG.SYS
to
ERRLOG.OLD;
a new version number is assigned if a file of
this name already exists.

5-3

THE ERROR LOG FILE
The operator then invokes the SYE Utility by typing RUN
SYS$SYSTEM:SYE.
The SYE Utility lists the defaults enclosed
in square brackets for each of the following parameters and
prompts for any changes in these:
•

The name of the file to be
manipulated
ERRLOG.OLD, the default input file).

(here,

•

The name of the file that is to contain the error log
report. The error log file in the preceding example is
written to ERROLOG.LIS, which facilitates obtaining a
printed copy of the error log file later. The default
output file, SYS$OUTPUT, is printed at the operator's
terminal.

type of report that SYE should generate. The type
• The
of report here is a summary ROLL-UP report. For a
description of other
Guide.

Manage~'s

types,

see

the

VAX/VMS

System

~~~~~~~~

•

The devices for which SYE should report errors.
By
pressing the RETURN key, the operator requests error
reports for all devices.

•

The time from which SYE should record errors.
By
pressing the RETURN key, the operator requests that SYE
report all errors that occurred since the error log
file was created.

•

The time until which SYE should record errors.
By
pressing the RETURN key, the operator requests that SYE
report the occurrence of errors up to and including the
last error in the error log file.

The SYE Utility creates a readable error log report.
The
operator obtains a hard copy of this report by pressing the
return key in response to the final SYE prompt provided the
operator previously had not specified an output file name. If
the operator had chosen an output file name other than
SYS$0UTPUT as in the preceding example, an additional step (use
of the PRINT command) is required to produce a printed copy of
the report.

5-4

CHAPTER n
THE OPERATOR'S LOG FILE

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

Initialization of the operator's log file

•

Status reports for devices attached to the system

•

Terminals enabled and disabled

•

Time stamps

•

User requests and operator replies

•

DECnet status messages

These messages are produced by the operator's communication process
(OPCOM) and are preceded by the label Opcom. Figure n-1 at the end of
this chapter shows some of the typical messages that appear in the
operator's log file. Section n.3 explains the messages in detail.

6.1

MAINTAINING THE OPERATOR'S LOG FILE

The operator's log file (SYS$SYSDISK: [SYSMGR]OPERATOR.LOG) resides on
the system disk in the [SYSMGR] directory. This file is in ASCII
format and can be printed as readable text. The operator should print
copies of the operator's log file regularly, and the system manager
should retain these copies for reference. Section 6.2 describes how
to print copies of the operator's log file.
A new version of the operator's log file is created each time the
system is rebootstrapped. The operator or the system manager should
devise a plan for regular maintenance of these files.
One way to maintain these files is to rename the highest version of
the operator's log file on a daily basis. For example, the operator
might rename the current version of OPERATOR.LOG to OPERATOR.OLD every
morning at 9:00 A.M. To free space on the system disk, the operator
then could back up the renamed version of the file on a different
volume and delete the renamed file from the system disk. The operator
should not delete versions of the operator's log file that have not
been backed up.
The procedure for renaming the operator's log file is the same as that
described in Section 5.2 for renaming the error log file.

n-1

THE OPERATOR'S LOG FILE

n.2

PRINTING THE

OPERATOR'S LOG FILE

The procedure below describes how to produce a printed copy of the
current version of the operator's log file
(OPERATOR.LOG).
An
operator should periodically print a copy of this file for the system
manager to review.
Procedure
1.

Close the current log file and open a new one by entering the
following command from the operator's terminal:
$ REPLY/LOG

Set the default to the system disk by typing:
$SET DEFAULT SYS$SYSDISK: [SYSMGR]

Use the following command to examine the directory [SYSMGR]
to see which versions of the operator's log file are on the
disk:
$

DIRECTORY OPERATOR.LOG

Obtain a printed copy of the operator's log file by
the following command from an operator's termi~al:

issuing

$PRINT OPERATOR.LOG;n
NOTE

The version number, n, must be one less
than the highest version of this file.
The highest version number
is
the
current operator's log file.

Example
1.

S REPLY/LOG
Opcom, 16-JUL-1980 12:29:24.52, logfile initialized, operator=_TTA2:
$SET DEFAULT SYS$SYSDISK: (SYSMGR]
S DIRECTORY OPERATOR. LOG
Directory _ORAS: [SYSMGR]
OPERATOR.LOG;582

OPERATOR.LOG;581

Total of 2 Files.
$ PRINT OPERATOR. LOG; 581

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 issues the PRINT command to
request that the second-most recent version of the operator's
log file (OPERATOR.LOG) be printed.

'1-2

THE OPERATOR'S LOG FILE
6.3

MESSAGES IN THE OPERATOR'S LOG FILE

This section describes the six types of message
operator's log file.

6.3.1

that

appear

the

Initialization Messages

When the operator issues the REPLY/LOG command, the current operator's
log file is closed and a new version of that file is created and
opened. All subsequent OPCOM messages are recorded in this new log
file.
When a new log file is created, the first message recorded in it is an
initialization message that tells the operator when and by whom the
log file was initialized.
This message appears in the following
format:
Opcom, dd-mmm-yyyy, hh:mm:ss,cc, logfile initialized, operator=operator-name

6.3.2

Device Status Messages

Some VAX/VMS I/O drivers send messages to OPCOM concerning changes in
the status of the devices they control. For example, when a device
goes offline, an OPCOM message is written into the operator's log file
at 30-second intervals until the device is explicitly returned to
online status.
The device status message appears in the operator's log
following format:

file

the

Opcom, hh:mm:ss,cc, device is offline, device-name
The devices for which this message can appear are card readers, line
printers, and magnetic tapes.
For information on DECnet status
messages, see the DECnet-VAX Syste~ Manager's Guide.

6.3.3

Terminal Enable and Disable Messages

The operator designates a terminal as an operator's terminal by
issuing the REPLY/ENABLE command from the desired terminal. OPCOM
confirms the request by displaying the following message at the
operator's terminal and in the operator's log file:
Opcom, dd-rnrnrn-yyyy hh:mm:ss,cc, terminal enabled, operator=operator-name

This message tells the operator which terminal has been established as
an operator's terminal and when it was so established.
If a terminal has been designated as an operator's terminal for a
particular function, OPCOM displays the name of that function. For
example, if the operator issues the command REPLY/ENABLE=TAPES, OPCOM
displays the following message:
Opcorn, 14-AUG-1980 10:25:35/74, terminal enabled, operator=_TTEl:
$

Opcom, 10:25:38.82, operator terminal status,
TAPES,

n-3

TTEl:

THE OPERATOR'S LOG FILE
OPCOM confirms that the terminal is established as an operator's
terminal and indicates that the terminal can only receive and respond
to requests concerning the mounting and dismounting of tapes.
A terminal that has been designated as an operator's terminal is not
automatically returned to nonoperator status when the operator logs
off. To return the terminal to normal
(nonoperator) status, the
operator must issue the REPLY/DISABLE command from the terminal.
OPCOM confirms that the terminal is no longer an operator's terminal
by displaying a message in the following format both at the operator's
terminal and in the operator's log file:
Opcom, dd-mmm-yyyy hh:mm:ss.cc, terminal disabled, operator=operator-name

This message tells the operator which terminal has been
nonoperator status and when the transition occurred.

restored

If a terminal is designated as an operator's terminal and only partial
operator status is disabled, OPCOM displays a status message. This
message lists which requests the terminal can still receive and
respond to. This message is displayed at the operator's terminal and
in the operator's log file in the following format:
Opcom, hh:mm:ss.cc, Operator terminal status, operator=operator-name
status-report

For example, suppose an operator designates a terminal as
an
operator's terminal that receives messages concerning magnetic tapes,
disks, and operator 1.
Later, the operator
relinquishes
the
terminal's ability to receive messages concerning tapes. When the
operator issues the REPLY/DISABLE=TAPES command, OPCOM returns the
following message:
Opcom, 09:23:45.32, Operator terminal status, operator=_TTA3:
DISKS, OPER(l)
This message tells the operator that terminal TTA3 still receives
can respond to messages about disks and operator 1.

n.3.4

and

Time Stamp Messages

A time stamp message is recorded at 30-minute intervals in the
operator's log file. These messages serve as markers for estimating
when a system failure o~curred.
A time stamp message appears in the log file in the following format:
Opcom, dd-mmm-yyyy hh:mm:ss.cc, logfile time stamp

6.3.5

User Request and Operator Reply Messages

To communicate with the operator, the user issues the REQUEST command,
specifying either the /REPLY or /TO qualifier.
If the user issues a REQUEST/REPLY command, the request is recorded in
the operator's log file in the following format:
Opcom, hh:mm:ss.cc, Username Accnt=account-name Reply-ID=identification-number
Opcom, terminal-name, "message-text"

n-4

THE OPERATOR'S LOG FILE
This message tells the operator, which user sent the message, the time
the message was sent,
the
identification number assigned to the
message, and the message itself.
If the user issues a REQUEST/TO command, the request
is
recorded
in
the operator's log file in the format described above, but without an
identification number.
When the operator responds to a user's request and specifies either
the /ABORT qualifier or the /TO qualifier, the response is recorded in
the operator's log file in the following format:
Opcom, hh:mm:ss.cc, operator-response, operator=operator-name
This message indicates how the operator
responded to the user's
request,
as well as when the response was issued and which operator
responded.
When the operator responds to a
user's
request using the /PENDING
qualifier,
the
response
is not recorded in the operator's log file
because the request has not yet been completed (that is,
the
request
has not been fulfilled or aborted).
When a user issues a REQUEST/REPLY command and
the operator has
disabled all terminals as operator's terminals, OPCOM records all
subsequent user's requests in the log file in the format shown above,
but returns a message to the user indicating that no operator coverage
is available.
All other OPCOM responses
to REPLY commands,
except
responses
involving the REPLY/ENABLE, REPLY/DISABLE, and REPLY/LOG commands, are
not logged in the operator's log file.
Opcom,
9-JUL-1980
Opcom,
9-JUL-1980
Opcom,
9-JUL-1980
Opcom,
9-JUL-1980
Opcom,
9-JUL-1980
Opcom,
9-JUL-1980
Opcom,
9-JUL-1980
Opcom, 21:18:42.77,
Opcom, _TTAl:'
II ARE

18:52:10.61,
logfile initialized, operator= OPA2:
19:22:13.85,
logfile time stamp
19:40:37.95,
terminal enabled, operator= TTAl:
19:40:50.31,
terminal disabled, operator~ TTAl:
20:12:13.78,
logfile time stamp
20:47:13.78,
logfile time stamp
21:17:26.84,
terminal enabled operator=_TTA2:
SWORDS
Accnt=DOCUMENT
YOU READY?"

Opcom, 21:22:31.65, PARDON
Opcom, _TTAl:, "ARE YOU READY?"

Accnt=DOCUMENT Reply-ID=O

Opcom,
Opcom,
Opcom,
Opcom,
Opcom,

06:58:58.70,
06:59:2n.70,
07:00:01.70,
07:00:30.70,
07:01:05.70,

Opcom,
Opcom,
Opcom,
Opcom,
Opcom,

11:31:19.70,
device is offline, LPAO:
11:31:51.70,
device is offline, LPAO:
14-JUL-1980
13:59:30.27, terminal enabled, operator=_TTC3:
13:59:41.88, SPAR LP
Accnt=VMS
TTC3:, "TEST
PLEASE"
THIS

Opcom, 15:26:42.73,

device
device
device
device
device

is
is
is
is
is

offline,
offline,
offline,
offline,
offline,

LPAO:
LPAO:
LPAO:
LPAO:
LPAO:

device is offline, CRAO:

Figure n-1 The Operator's Log File (OPERATOR.LOG)

n-5

CHAPTER 7
SHUTTING DOWN AND RESTARTING THE SYSTEM

Occasionally, the operator may need to shut down and restart the
VAX/VMS operating system.
Reasons for halting the system include
danger of power loss, the need to back up the system disk, a hardware
or software problem, or the need to use the computer system for a
specific application. The operator restarts the system once the
problem is solved or when the specific application begins.

7.1

SHUTTING DOWN THE OPERATING SYSTEM

This chapter describes three procedures the operator can use
down the system:
1.

An orderly shutdown of the system

Two emergency shutdowns of the system

shut

The first procedure is a command procedure that is distributed with
the VAX/VMS software.
This command procedure, named SHUTDOWN.COM,
resides in the SYS$SYSTEM directory.
Once invoked, SHUTDOWN.COM
automatically performs specific 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
procedure
also invokes a site-specific command procedure named
SYSHUTDWN.COM that is tailored by the system manager to the needs of
the specific installation.
SYSHUTDWN.COM file is present in the
distribution kit but contains no commands.
If the operating system cannot be shut down by means of the
SHUTDOWN.COM command procedure, the operator should use the second
emergency shutdown procedure, RUN SYS$SYSTEM:OPCCRASH.
This program
shuts down the system immediately. The error log buffers are written
to the system dump file. Pages on the modified list are written to
disk.
Then the system disk is dismounted. Data may be lost, since
the OPCCRASH command procedure performs only minimal housekeeping
functions.
Therefore, an emergency shutdown of the system should be
used only if the orderly shutdown procedure fails.
The CRASH command procedure also is an emergency shutdown procedure
that is stored on the system console medium and is distributed with
the VAX/VMS software. By forcing the system to fail, the CRASH
command procedure shuts down the system. Data may be lost since no
housekeeping functions are performed. Therefore, the CRASH command
procedure should not be used unless the system will not accept command
input.

7-1

SHUTTING DOWN AND RESTARTING THE SYSTEM
7.2

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 properly. Generally, when the system fails,
it automatically
restarts itself.
However, sometimes operator assistance is required
to restart the system. This usually occurs after the operator has
halted the operating system by one of the methods described in the
previous section.

7.2.1

The Start-Up Command Procedure

When the operating system is bootstrapped, the command procedure
SYS$SYSTEM:STARTUP.COM
is
automatically executed.
This command
procedure contains commands for performing site-independent operations
that must be performed if the system is to run properly. These
operations include assigning system-wide logical names, installing
executable images as known images, and creating permanent global
sections. The SYS$SYSTEM:STARUP.COM command procedure also invokes a
site-specific command procedure named [SYSMGR)SYSTARTUP.COM in which
the system manager places site-specific initialization commands. This
file is furnished in the distribution kit without commands.

7.2.2

Restarting Problems

Sometimes the operating system does not bootstrap after the operator
has issued the restart command.
This can be caused by either a
hardware or software malfunction.

7.2.2.1 Hardware Problems - A read error on a tape drive or floppy
diskette,
or
a
machine check error may indicate a hardware
malfunction. Whenever a hardware problem occurs, a question mark
(?)
character usually precedes the error message that is displayed on the
system console terminal. When a hardware problem occurs, the operator
should:
•

Notify the system manager

•

Consult the appropriate hardware manual for VAX-11 users

•

Contact the appropriate DIGITAL field service representative

7.2.2.2 Software Problems - When the operating system is loaded into
memory, but the STARTUP.COM command procedure is not executed, a
software malfunction has probably occurred. The operator can perform
one or more of the following actions to correct the situation:

7.3

•

Repeat the start-up procedure

•

Start the system from another drive or disk

PROCEDURES FOR SHUTTING DOWN AND RESTARTING THE SYSTEM

The following section contains step-by-step procedures
down and restarting the VAX/VMS operating system.
7-2

for

shutting

SHUTTING DOWN AND RESTARTING THE SYSTEM
7.3.1

Orderly Shutdown of the System

The command procedure below describes how to shut down the system in
an orderly fashion.
This procedure is contained in a command file.
At the discretion of the system manager or operator, commands can be
added to the SYSHUTDWN.COM command procedure to perform additional
housekeeping functions.
Procedure
1.

Type the following command to begin the shutdown procedure:
$ @SYS$SYSTEM: SHUTDOWN

Enter an integer in response to the following question:
How many minutes until shutdown?:

In response to the following
shutting down the system:

prompt,

give

the

reason

for

Reason?:
4.

Respond by typing a Y
question:

(Yes)

(No)

the

following

Do you want to spin down the disks?:
The execution of the shutdown procedure continues while
following events occur and are printed on the terminal:

the

A message that requests users to log out is broadcast
to
all users on the system.
This message is
broadcast at decreasing time intervals.

Batch and device queues are stopped and all future
nonoperator logins are disabled when there are four
or fewer minutes left until system shutdown.

The site-specific command procedure SYSHUTDWN.COM is
invoked.
This command procedure contains commands
inserted by the system manager to tailor the shutdown
procedure to the needs of the installation.

All mounted volumes are dismounted and, if
by the operator, the disks are spun down.

All user processes are stopped.
However,
the
following
processes
continue:
NULL,
SWAPPER,
JOB CONTROL,
OPCOM,
ERRFMT,
ancillary
control
processes
(ACPs),
and the process running the
SHUTDOWN.COM command procedure.
ACPs may delete
themselves when their mounted volumes are finally
dismounted.

The operator's log file is closed.

The program SYS$SYSTEM:OPCCRASH is
down the system.

invoked

requested

shut

Observe the following message typed on the system console:
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

7-3

SHUTTING DOWN AND RESTARTING THE SYSTEM
5.

Enter the following two console commands to halt the system:
©!flt:~

>»HALT
The control character <CTRL/P> will not be echoed at the
console terminal. The console command language prompt (>>>)
will be printed at the terminal after <CTRL/P> is typed.
Typing <CTRL/P> places the console terminal under the control
of the console subsystem instead of the VAX/VMS operating
system.
The HALT or the H command halts the system
completely.

Examples
@SYS$SYSTEM: SHUTDOWN
System shutdown command procedure.
17-MAR-1980 11:11:34
How many minutes until shutdown?: 5
Reason?:
WEEKLY SYSTEM DISK BACK-UP
Do you want to spin down the disks?: NO
Opcom, 11:12:20:32, Operator terminal status, OPAO:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS~ NETWORK,
OPER(l,2,3,4,5,n,7,8,9,10,11,12)
$

OPAO:,SYSTEM
11:12:20.72
"SYSTEM SHUTDOWN IN 5 MINUTES.
0

OPAO:,SYSTEM
11:12:22.73
WEEKLY SYSTEM DISK BACK-UP
Login quotas - Interactive limit-0, Current interactive value=l
Non-operator logins are disabled.

_OPAO:,SYSTEM
11:14:27.30
"BATCH AND DEVICE QUEUES HAVE BEEN STOPPED"
0

OPAO:,SYSTEM
11:14:29.8n
SYSTEM SHUTDOWN IN 2 MINUTES. LOGINS ARE DISABLED, PLEASE LOGOFF.

OPAO:,SYSTEM
11:14:31.54
"WEEKLY SYSTEM DISK BACK-UP
OPAO:,SYSTEM
11:15:32.62
"SYSTEM SHUTDOWN IN 1 MINUTE.
LOGINS ARE DISABLED, PLEASE LOGOFF.
OPAO:,SYSTEM
11:15:34.2n
"WEEKLY SYSTEM DISK BACK-UP
OPAO:,SYSTEM
11:16:35.39
"SYSTEM SHUTDOWN IN 0 MINUTES. LOGINS ARE DISABLED, PLEASE LOGOFF.
OPAO:,SYSTEM,
11:16:37.08
"WEEKLY SYSTEM DISK BACK-UP
Invoke installation dependent shutdown procedure.
Stop all user processes.
Dismount all mounted volumes.
OPCOM, 11:16:43.62, SYSTEM
Accnt=SYSTEM
Opcom, _OPAO:, "OPERATOR REQUESTED SHUTDOWN"
Opcom, 17-MAR-1980 11:16:45.02, logfile closed, operator=_OPAO:
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

7-4

SHUTTING DOWN AND RESTARTING THE SYSTEM

((J'RL/P)

>»HALT
HALTED AT 80007100
In this example, the operator requests that the system be shut
down in 5 minutes to allow a system disk back-up. The operator
indicates when and why the system will be shut down and whether
the disks should be spun down.
The system then performs
housekeeping functions that ensure a clean shutdown.
When
housekeeping operations are complete, a system message requests
the operator to halt the system using the console terminal.
The
operator types <CTRL/P> and the HALT or H command to complete the
system shutdown procedure.

7-5

SHUTTING DOWN AND RESTARTING THE SYSTEM
7.3.2

Emergency Shutdown of the System

The procedure below describes how to 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
orderly shutdown procedure described previously.
However,
if that procedure fails,
the operator can perform an
emergency shutdown.
To perform this procedure, the operator must enter the
the system console.

commands

from

Procedure
1.

Enter the following command to force an immediate shutdown of
the system:
$ RUN SYS$SYSTEM:OPCCRASH

If the system fails to accept or to respond to the command
issued in step 1 use the CRASH command procedure that is
described on the pages following this procedure.

Observe the
console:

following

information

typed

the

system

SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM
4.

Type <CTRL/P> after the above message is printed at the
console terminal.
The system responds with the console
system prompt (>>>) as shown below. Then type the HALT or H
command to halt the system.
tTRL/P)

»>HALT
5.

The console program reports that the system is halted by
printing the contents of the system program counter at the
time of the halt.
HALTED AT "address"

Example
1.

$ RUN SYS$SYSTEM:OPCCRASH
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM
tlR~/PJ

»>HALT
HALTED AT 8000708A
The operator types the command string for an emergency
shutdown.
The system then instructs the operator to use the
console to halt the system. The operator presses <CTRL/P> to
return the console terminal to the control of the console
subsystem. The console subsystem responds with the console
command language prompt (>>>). The operator then types the
HALT or H command to halt the system.

7-n

SHUTTING DOWN AND RESTARTING THE SYSTEM
7.3.3

Forcing the System to Fail

The CRASH command procedure described below forces the system to fail,
which results in an immediate shutdown of the system. After the CRASH
command procedure is invoked, a fatal bug check message is printed at
the console terminal and the system dump file is written to the disk.
Later, these can be used to determine why the system did not
respond
to command
input.
However,
data may be lost,
since no other
housekeeping functions are performed.
Therefore,
the CRASH command
procedure only should be used if the system will not accept command
input;
that is, if the system fails
to accept or
respond to the
OPCCRASH procedure described on the preceding pages.
Note that, if a copy of the system dump file later is sent to DIGITAL
for analysis, a copy of the console listing also should be sent.
This
listing displays fatal bug check information that is not contained
in
the system dump file (for example, program counter (PC) and processor
status longword (PSL) data).
All commands that invoke the CRASH command
from the system console terminal.

procedure

must

console

typed

Procedure
1.

Type <CTRL/P> to return control
language level, as follows:

the

command

(Cl][/P)

»>
2.

The system responds by printing the console command language
prompt, (>>>).
After the prompt, type @CRASH as follows:
»>@CRASH

NOTE
Not all
VAX-11
console
processors
execute
command procedures.
If the
processor does not
support
command
procedures,
the operator can type each
command individually.
The example that
follows displays the information needed
for the operator to enter the commands.

The @CRASH command invokes the CRASH command procedure.
The
system initially responds by printing the following message
at the console terminal:
Command file to crash VMS abnormally
Additional messages and information, such as the fatal bug
check message are printed at the console terminal, as shown
in the example below and the system dump file is wiitten to
the disk.

7-7

SHUTTING DOWN AND RESTARTING THE SYSTEM

Example
(CTRL/P)

>»@CRASH

Command f il~ to crash VMS abnormally

HALT

! HALT SYSTEM, EXAMINE PC,

HALTED AT 8000702A
EXAMINE PSL
PSL,
00000000
EXAMINE/INTERN/NEXT:4 0
00000000
00000001
00000002
00000003
I
I
00000004
DEPOSIT PC=-1

And all stack pointers
80001048
00000000
00000000
00000000
8009E'100
Invalidate PC

I
I
I

DEPOSIT PSL=lFOOOO

! Kernel mode, IPL 31

CONTINUE
<@EOF>
<@EXIT>

**** FATAL BUG CHECK, VERSION
ASTDEL or on interrupt stack

2.0 INVEXCEPTN, Exception while

CURRENT PROCESS = NULL
REG !STER DUMP
RO
OOOOOOlF
Rl
OOlFOOOO
R2
00000000
R3 = 00000000
R4
00000000
RS = 00000000
Rn
00000000
R7 = 00000000
RB
00000000
R9
00000000
RIO= 00000000
Rll= 00000000
AP
00000000
FP = 00000000
SP = 80001Dl4
PC = 800038Cl
PSL= 001F0009
KERNEL/INTERRUPT STACK
80001DlC
80001020
80001024

00000004
00000000
FFFFFFFD

7-8

above

SHUTTING DOWN AND RESTARTING THE SYSTEM

80001D28

00000000

HALT INST EXECUTED
HALTED AT 80007183

>>>
Typing @CRASH invokes the CRASH command procedure.
This procedure
instructs the system to examine the program counter (PC), the
processor status longword (PSL), and the stack pointers.
Values are
deposited in the PC and PSL to cause an exception condition that
forces a system dump. The fatal bug check message is printed at the
console terminal.
Finally, the system halts and prints the contents
of the program counter. The console system prompt (>>>) returns.
If enabled, some systems will halt and then automatically rebootstrap.
However, systems which are not enabled to automatically rebootstrap,
must be rebootstrapped by the operator.

7-9

SHUTTING DOWN AND RESTARTING THE SYSTEM
7.3.4

Restarting the System

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

Enter the following console command to bootstrap the system:

>>> BOOT [device-name]
2.

Observe the
console.

bootstrap

information

Press the RETURN key to log
routine operations.

printed
the

the

system

and

resume

Example
1.

>>>BOOT OMO
CPU HALTED
INIT SEQ DONE
HALT INST EXECUTED
HALTED AT 200034F9
G OOOOOOOE 00000200
LOAD DONE 00002000 BYTES LOADED
VAX/VMS Version 2.0 14-APR-1980 10:30
opcom, 27-SEP-1980 11:25:55.98, logfile initialized, operator=_OPAO:

After the operator enters the BOOT command, the operating
system is loaded into memory and the STARTUP.COM file is
executed. Upon completion, the system is initialized and
ready to accommodate system users.

7-10

CHAPTER 8
DCL COMMANDS USED BY OPERATORS

This chapter describes the DCL commands most commonly used by
operators;
that is, commands that can only be executed by users who
have the operator (OPER) privilege. Typically, only system managers
and system operators have this privilege.
Some commands require one or more privileges in addition to the OPER
privilege;
these requirements are noted in the command descriptions.
An operator who does not have these privileges but needs to use a
command that requires them should see the system manager.
Most commands that do not require the OPER privilege, are
in the VAX/VMS Command Language User's Guide.
That
contains an introduction for using DCL commands.

8-1

documented
guide also

DCL COMMANDS USED BY OPERATORS

ASSIGN/MERGE
8.1

ASSIGN/MERGE

Description
This command removes jobs from one print queue and
another queue.

merges

them

with

Before the merge operation can take effect, the operator stops the
source queue (that is, the queue to be merged) using the STOP/QUEUE
command described in Section 8.9. The operator need not stop the
target queue (that is, the queue that will accommodate the source
queue).
The ASSIGN/MERGE command is particularly useful when a line printer
malfunctions:
by issuing an ASSIGN/MERGE command, the operator can
reroute the queue to a different print device. Note that to perform
the merge operation without losing or disrupting any jobs, the
operator should follow the procedure described in Section 3.3.1.
The
original queue then can be deleted.

Format
queue-name[:]

ASSIGN/MERGE device-name[:]
Command Qualifiers

Defaults

None •

None.

......_----~---·--·-···-··-····~------------------------------

Prompts
Device:
Log_Name:

device-name[:]
queue-name[:]

Command Parameters
device-name[:]
Specifies the name of a line printer or device to which the files
will be directed.
queue-name [: J
Specifies the name of a queue that is going to be reassigned to a
new print queue.

Example
1.

$ STOP/QUEUE

$ ASSIGN/MERGE

LPBO
LPAO

LPBO

The STOP/QUEUE command
stops
the
print
queue
LPBO
immediately.
The ASSIGN/MERGE command removes the jobs from
the LPBO print queue and places them in the LPAO print queue.

8-2

DCL COMMANDS USED BY OPERATORS

ASSIGN/QUEUE
8.2

ASSIGN/QUEUE

Description
This command assigns, or redirects, a
device.

logical

queue

specific

Jobs in a logical queue cannot be initiated from the queue unless
operator:

the

Assigns the logical queue to a physical-device queue

Starts both the logical queue and the physical-device queue

To assign a logical queue to a physical-device queue, the operator
specifies the ASSIGN/QUEUE command.
To start printing jobs, the
operator specifies the START/QUEUE command for both queues (described
in Section 8 .8).
Format
. . . . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . , - - - - - --

ASSIGN/QUEUE

device-name[:]

logical-queue-name[:]

Command Qualifiers

Defaults

None.

'------------------~--°'--~--------------

__________,

Prompts
Device:
Log_Name:

device-name[:]
logical-queue-name[:]

Command Parameters
device-name[:]
Specifies the name of a queue associated with a specific device
(such as a line printer) that is to be associated with a logical
queue.
logical-queue-name[:]
Specifies the name of the logical queue that is to be assigned to
a specific device such as a line printer.
(A logical queue is a
queue whose name does not match a physical device and that is not
a generic queue.)

8-3

DCL COMMANDS USED BY OPERATORS

Examples
1.

$ INITIALIZE/QUEUE/FLAG TEST QUEUE
$ INITIALIZE/QUEUE/FLAG LPAO
$ ASSIGN/QUEUE LPAO TEST QUEUE

$ START/QUEUE LPAO
$ START/QUEUE TEST_QUEUE
The INITIALIZE commands crea~e the logical queue TEST_QUEUE
and the print queue LPAO. Both these queues are initialized
with a header page preceding each job.
The ASSIGN/QUEUE
command associates the logical queue TEST QUEUE with the
print queue LPAO and the printing of jobs begins when the
queues are' started with the START/QUEUE commands.
2.

$INITIALIZE/QUEUE LPBO
$ START/QUEUE LPBO
The ASSIGN/QUEUE command is not needed here because a logical
queue is not being initialized. A physical-device queue is
being initialized; LPBO is the name of a line printer.
Thus, to begin printing, only the START/QUEUE command is
needed.

8-4

DCL COMMANDS USED BY OPERATORS

DEASSIGN/QUEUE
8.3

DEASSIGN/QUEUE

Description
This command deassigns a logical queue from a specific device such as
a line printer.
(A logical queue is a queue whose name does not match
a physical device.) The DEASSIGN/QUEUE command is the complement of
the ASSIGN/QUEUE command described in Section 8.2.
Before issuing the DEASSIGN/QUEUE command, the operator must stop the
logical queue with the STOP/QUEUE command (described in Section 8.9).
Once the operator issues the DEASSIGN/QUEUE command, the jobs in the
logical queue remain in a hold state until the queue is reassigned to
another print queue or device.
Format
DEASSIGN/QUEUE

logical-queue-name[:]

Command Qualifiers

Defaults

None.

Prompts
Log_Name:

logical-queue-name[:]

·command Parameters
logical-queue-name[:]
Specifies the name of a logical queue that is
from a specific device or print queue.

deassigned

Example
1.

$ASSIGN/QUEUE LPAO

ASTER

$ STOP/QUEUE/NEXT ASTER
$ DEASSIGN/QUEUE ASTER
The ASSIGN/QUEUE command associates the logical queue ASTER
with the print queue LPAO.
Later, the operator decides to
deassign the queue ASTER from LPAO.
First, the operator uses
the STOP/QUEUE/NEXT command to stop the logical queue after
the current print job is printed.
Then,
the operator
deassigns the logical queue using the DEASSIGN/QUEUE command.

8-5

DCL COMMANDS USED BY OPERATORS

DELETE/QUEUE
8.4

DELETE/QUEUE

Description
This command deletes a specific print or batch queue and all the
the queue contains.

jobs

The DELETE/QUEUE command takes effect only if the specified queue has
been stopped.
The operator stops the queue using the STOP/QUEUE
command (described in Section 8.9) before issuing the DELETE/QUEUE
command.

Format
DELETE/QUEUE

queue-name[:]

Command Qualifiers

Defaults

None.

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

Prompts
File:

queue-name[:]

Command Parameters
queue-name[:]
Specifies the name of the print or batch queue to be deleted.

Example
1.

$ INITIALIZE/QUEUE/FLAG LPAO
$ START/QUEUE LPAO

$ STOP/QUEUE/NEXT LPAO
$ DELETE/QUEUE LPAO

The first two commands initialize and start the print queue
LPAO.
Later, the operator decides to delete that queue.
First the operator
stops
the
queue
by
using
the
STOP/QUEUE/NEXT command. The operator then deletes the queue
by issuing the DELETE/QUEUE command.

8-6

DCL COMMANDS USED BY OPERATORS

INITIALIZE/QUEUE
8.5

INITIALIZE/QUEUE

Description
This command creates or initializes print and batch queues.
The
operator uses this command to create print and batch queues and to
assign them names and attributes. Generally, these queues are created
by the operator who enters them in a site-specific system start-up
command procedure.
(The VAX/VMS S*stem Manager's Guide contains
examples of such entries.) However, t e operator can create additional
queues as they are needed.
To begin printing jobs from print queues and executing jobs from batch
queues, the operator issues the START/QUEUE command (described in
Section 8.9). Note that all the options that can be specified in the
INITIALIZE/QUEUE command also can be specified in the START/QUEUE
command.
When the operator creates a
required.

batch

queue,

the

qualifier

/BATCH

Format
INITIALIZE/QUEUE

queue-name[:]

Command Qualifiers

Defaults

/BATCH
/[NO]BURST
/CHARACTERISTICS=(c[, ••• ])
/CPUDEFAULT=t
/CPUMAXIMUM=t
/[NO]DISABLE SWAPPING
/[NO]ENABLE GENERIC PRINTING
/[NO]FLAG /FORMS TYPE=n
/[NO]GENERIC
/JOB LIMIT=n
/PRIORITY=n
/PROCESS=process-name
/TERMINAL
/WSDEFAULT=n
/WSQUOTA=n

/NOBURST

/NODISABLE SWAPPING
/ENABLE GENERIC PRINTING
/NO FLAG/NOGENERIC
/JOB LIMIT=l
/PRIORITY=4

Prompts
Queue:

queue-name[:]

Command Parameters
queue-name [:]
Specifies the name of
queue.

physical-device,

8-7

generic,

logical

DCL COMMANDS USED BY OPERATORS
Command Qualifiers
/BATCH
Indicates that this is a batch queue.
/BURST
/NOBURST
Control whether a burst header page is
job.

printed

for

each

Use the /BURST qualifier to print a header page over the paper
perforations so that the page header is visible from the side of
a stack of paper. A burst header uses an extra page for each job
but simplifies separating listings.
The default is /NOBURST.
/CHARACTERISTICS=(c[, ••• ])
Specifies one or more desired characteristic(s) for printing a
file.
If more than one characteristic is specified, separate
each with a comma and enclose the list in parentheses.
For
further information on specifying characteristics, refer to the
VAX/VMS System_~~~ager's Guide.
/CPUDEFAULT=t
Defines the default CPU time limit for batch jobs.
Specify the value t as a delta time value, the numeric value O,
or either the word NONE or INFINITE. The value O and the word
INFINITE allow a job unlimited CPU time, provided the CPU time
limit is not restricted by the /CPUMAXIMUM qualifier or the user
authorization file. Specify NONE when a default CPU time limit
is not desired.
The value for t cannot exceed the
/CPUMAXIMUM qualifier.

CPU

time

limit

set

the

/CPUMAXIMUM=t
Defines the maximum CPU time limit for batch jobs.
Use this
qualifier to override the CPU time limit specified in the user
authorization file.
Specify the value t as a delta time value, the numeric value O,
or either the word NONE or INFINITE. Specify ~ONE when a maximum
CPU time limit is not desired. Refer to Table 8-1 below for more
information on specifying CPU time limits.

8-8

DCL COMMANDS USED BY OPERATORS
Table 8-1
CPU Time Limit Specifications and Action
CPU time limit
specified by the
SUBMIT command?

Default CPU time
limit specified
for queue?

Maximum CPU time
s pecified for queue?

Use UAF value

Yes

Use smaller of
SUBMIT command
and UAF value

Yes

Use smaller of
SUBMIT command
and UAF value

Yes

Use smaller of
SUBMIT command
and maximum value

Yes

Use smaller of
SUBMIT command
and maximum value

Yes

Use smaller of
queue's default and
maximum value

Yes

Use maximum value

Yes

Use smaller of
UAF and queue's
default value

Action taken

A CPU time limit for processes is specified by each user record in the
system user authorization file (UAF}. An operator can also specify
the following:
a default CPU time limit for all jobs in a given queue
and a maximum CPU time limit for all jobs in a given queue.
The above
decision table shows the action taken for
each value specified and
possible combinations of specifications.
/DISABLE SWAPPING
/NODISABLE_SWAPPING
Control whether batch jobs executed from a queue can
in and out of memory.

swapped

The default is /NODISABLE SWAPPING.
/ENABLE GENERIC PRINTING
/NOENABLE_GENERIC_PRINTING
Specify whether files queued to a generic queue can be placed
this physical-device queue for printing.
The default is /ENABLE_GENERIC_PRINTING.

8-9

DCL COMMANDS USED BY OPERATORS
/FLAG
/NO FLAG
Specify whether a header page is printed at the beginning of
first file in each print job.

the

The default is /NOFLAG.
/FORMS_TYPE=n
Specifies the forms type for a 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 hold state.
Specify the forms type using a numeric value or an alphanumeric
code. Codes for forms type are installation-specific.
/GENERIC
/NOGENERIC
Specify that this a generic queue and any files placed in this
queue can be moved for printing to any available physical-device
queue that has matching characteristics.
The default is /NOGENERIC.
/JOB_LIMIT=n
Indicates the number of batch jobs that can be
executed
concurrently from the queue. The job limit default value (n) is
1.

/PRIORITY=n
Specifies the base process priority at which jobs are initiated
from batch queue. The default priority value (n) is 4.
/PROCESS=process-name
Allows users to specify their own print symbionts.
Specify the
print symbiont name using 1 through 15 character(s). The system
will supply the device and directory name SYS$SYSTEM and the file
type EXE.
/TERMINAL
Indicates that the generic queue will be associated
with
terminals instead of line printers.
The /TERMINAL qualifier
allows all jobs entered in the queue to be moved to any
physical-device
queue associated with a terminal that has
matching characteristics.
/WSDEFAULT=n
Defines a working set default for a batch job.
Use this
qualifier to override the value in the user authorization file.
A positive integer in the range 1 through ~5535, O, or the word
NONE may be specified for n. Specify 0 or NONE and the working
set default value becomes the value specified either in the user
authorization file or by the SUBMIT command (if specified). For
more information refer to Table 8-2 below.

8-10

DCL COMMANDS USED BY OPERATORS
/WSQUOTA=n
Defines the working set page size for a batch job.
This is
called the working set quota. use this qualifier to override the
value in the user authorization file.
Specify a positive integer in the range 1 through ~5535, O, or
the word NONE as the value for n. If O or NONE is specified for
n, the working set quota defaults to the value specified either
in the user authorization file or by the SUBMIT command (if
specified). For more information refer to Table 8-2 below.
Table 8-2
Working Set Default and Working Set Quota Decision Table
Value specified
by SUBMIT command

Value specified
for queue?

Action taken

1-----------------4--- ----------- --

Use UAF value

Yes

Use value for queue

Yes

Use smaller of the two

Yes

Compare specified
value with UAF
value; use smaller

A working set default size and a working set quota (maximum size) are
included in each user record in the system user authorization file
(UAF), and can be specified for individual jobs and/or for all jobs in
a given queue.
The above decision table shows the action taken for
different combinations of specifications that involve working set size
and working set quota values.
Examples
1.

$INITIALIZE/QUEUE/BATCH/JOB LIMIT=4 SYS$BATCH
$ START/QUEUE SYS$BATCH
$ INITIALIZE/QUEUE/FLAG LPAO
$ START/QUEUE LPAO
This sequence of commands initializes and starts the hatch
queue SYS$BATCH and the print queue LPAO. The /JOB LIMIT=4
qualifier allows as many as four batch jobs to be initiated
concurrently from the batch queue.
The /FLAG qualifier
causes a header page to precede each print job in the print
queue.

8-11

DCL COMMANDS USED BY OPERATORS
2.

$ INITIALIZE/QUEUE TESTER
$ INITIALIZE/QUEUE/FLAG LPAO
$ ASSIGN/QUEUE LPAO TESTER
$ START/QUEUE

$ START/QUEUE

TESTER
LPAO

This sequence of commands causes all jobs queued to the
logical queue TESTER to be printed on the print queue LPAO.
The INITIALIZE commands initialize the logical queue TESTER
and the print queue LPAO. The print 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 the print queue LPAO.
After the
START commands are issued, all jobs queued to TESTER and LPAO
will be printed on LPAO.

8-12

DCL COMMANDS USED BY OPERATORS

REPLY
8.6

Description
This command is used by the operator to:
•

Respond to user requests

•

Respond to magnetic tape file system requests

•

Display messages at a user's terminal

.•

Enable and disable operator status on a terminal

•

Close the operator's log file and open a new one

Thus, the operator uses the REPLY command to communicate
users.

with

system

Responding to User Requests: When a user issues the REQUEST/REPLY
command, the process associated with the requesting user's terminal is
put in a wait state until the operator responds using one of the
following REPLY commands:
•

REPLY/ABORT=identification-number

•

REPLY/PENDING=identification-number

•

REPLY/TO=identification-number

The /ABORT qualifier
canceled.

indicates

that

"message-text"
"message-text"

"message-text"
the

user's

request

has

been

The /PENDING qualifier sends a message to the user and keeps the
user's process in a wait state until the request can be fulfilled or
aborted.
The /TO qualifier
fulfilled.

indicates

that

the

user's

request

When a user issues the REQUEST/REPLY command, the message
the system console terminal as follows:
ACCNT=account-name
Opcom, hh:mm:ss:cc Username
Opcom, terminal-name:, "message-text"

has

been

appears

REPLY-ID=identification-numher

The user cannot enter any further commands until th€ 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 5-minute intervals on the operator's
terminal until the operator replies.
Chapter 2 describes several procedures
that
require
operator
assistance so that users can gain access to tape and disk volumes.
The REPLY command is an essential part of these procedures.

8-13

DCL COMMANDS USED BY OPERATORS
Responding to File System Requests: When a multivolume tape volume
reaches end-of-tape, the magnetic tape file system suspends processing
and sends a message to the operator to mount the next tape.
The
operator responds using one of the following REPLY commands:
•

REPLY/TO=identification-number

•

REPLY/TO=identification-number

•

REPLY/ABORT=identification-number

"label/INITIALIZE"

The /TO qualifier indicates that the file system request has been
fulfilled.
When the request from the magnetic tape file system
specifies a volume label, the operator mounts the specified tape and
issues the REPLY/TO command without including any message text.
However, if the file system request does not specify a volume label,
the operator mounts a scratch tape and issues the REPLY/TO command
with the message "label/INITIALIZE". The double quotation marks are
required syntax.
The /ABORT qualifier indicates that the file system request
canceled.

has

For more information on operator responses to
see Chapter 2.

requests,

file

system

been

Displaying Messages at Users' Terminals:
To contact one or more
system users, the operator issues one of the following REPLY commands:
•

REPLY/ALL

"message text"

•

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

REPLY/USER

"message text"

The /ALL qualifier sends a message to all terminals that are online
and connected to the VAX/VMS system.
Generally, to broadcast an
important message, such as a message that indicates a system shutdown,
the operator specifies the /ALL qualifier.
The /TERMINAL qualifier sends
terminals on the system.

message

one

The /USER qualifier sends a message to all terminals at
users are logged in.

more
which

specific
system

Note that the /TO qualifier is not used here because the operator is
not replying to a specific request from either the file system or a
user.
Enabling and Disabling Operator Status on a Terminal:
Any terminal
connected to the VAX/VMS operating system can be established as an
operator's terminal.
The operator logged into an account with
operator privilege enters the REPLY/ENABLE command at the designated
terminal, then that terminal can be used to respond to user requests
and monitor device status.
Operator messages are printed on the system console terminal unless it
is explicitly disabled as an operator's terminal.

8-14

DCL COMMANDS USED BY OPERATORS
When the operator enters the REPLY/ENABLE command, OPCOM confirms that
the terminal has been enabled by displaying the following message:
Opcom, dd-mmm-yyyy hh:mm:ss.cc, terminal enabled, operator=operator-name
Opcom, hh:mm:ss.cc, Operator terminal status, operator-name
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK.
OPER (l,2,3,4,5,n,7,8,9,10,11,12)

When the operator enters the REPLY/DISABLE command, OPCOM confirms
that the terminal is no longer an operator terminal by displaying the
following message:
Opcom, hh:mm:ss.cc, terminal disabled, operator=operator-name
To grant specific 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, l-AUG-1980 18:40:28.37, terminal enabled, operator=_TTE3:
$

Opcom, 18:40:31.47, Operator terminal status,
OPCOM ccnfirms
messages.

that

the

terminal

has

operator

TTE3:
status

TAPES,
for

tape

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 rece1v1ng 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(l,2,3,4,5,n,7,8,9,10,11,12)
Note that OPCOM lists the specific operator status still
the terminal.

assigned

When an operator disables operator status on all terminals,
including
the system console terminal, OPCOM records all subsequent user
requests in the operator log file and responds to these requests with
the following message:
%0PCOM-S-OPRNOTIF, operator notified, waiting. hh.mm.ss.cc
%0PCOM-S-OPREPLY, no operator response text
%0PCOM-S-NOPERATOR, no operator coverage
To determine the operator status and obtain a list of pending requests
for a particular terminal, the operator types the following command:
$ REPLY/STATUS

This command also shows all autstanding requests for this operator.

8-15

DCL COMMANDS USED BY OPERATORS
Closing the Operator's Log File and Opening a New One: To close the
current operator's log file and open a new one, the operator issues
the REPLY/LOG command. All subsequent messages are recorded in the
new log file.
To close the current log file without opening a new
one, the oparator 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 log file, see Chapter fi.
To
examine the contents of the operator's log file, use the procedure
documented in Chapter n.
Format
....-----------·----·~-~-------·----------

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

[message-text]

Command Qualifiers

Defaults

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

None.

Prompts
None.
Command Parameters
message-text
Indicates the message to be displayed at one or more user's
terminals.
The maximum length of a message is 128 characters;
if this limit is exceeded, an error occurs.
When a message
consists of more than one word, the message should be enclosed
within quotation marks.
Use the "label/INITIALIZE" message with the REPLY/TO command to
initialize a volume requested by the magnetic tape file system
whenever the file system request to mount a volume does not
specify the volume label.
Command Qualifiers
/ABORT=identification-number
Sends a message to the user or magnetic tape file system
corresponding to the unique identification number and aborts the
request.

8-10

DCL COMMANDS USED BY OPERATORS
/ALL
Broadcasts a message to all terminals that are attached to the
system, that have broadcast message reception enabled, and that
are turned on.
/BELL
Rings a bell at a terminal as it receives a message.
This
qualifier can be specified with one of the following qualifiers:
/ALL
/TERMINAL=(terminal-name[, ••• ])
/USER
/DISABLE.[= (keyword [, ••• ] ) ]
Restores to normal status (that is, nonoperator status) a
terminal at which the command is issued or whose name is
specified. The REPLY/DISABLE command cannot be issued from a
batch job.
To restrict the types of messages displayed on an operator's
terminal, specify one or more of the keywords in Table 8-3 at the
end of this section.
If no keywords are specified, all operator characteristics are
disabled.
If more than one keyword is specified, separate each
with a comma and enclose the entire list in parentheses.
/ENABLE[=(keyword[, ••• ])]
Designates the terminal at which the command is issued to be an
operator's terminal.
The REPLY/ENABLE command cannot be issued
from a batch job.
To designate a terminal to receive messages from a particular
facility, specify one or more of the keywords in Table 8-3 at the
end of this section.
/LOG
/NO LOG
Control whether a new operator's log file is opened.
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 not
open a new one.
Hence, no messages are recorded until the
operator opens another log file.
/PENDING=identification-number
Sends a message to the
user
indicated
by
the
unique
identification number and keeps the process from which the
request was issued in a wait state. The user cannot enter other
commands until the operator fulfills or aborts the request.
/STATUS
Reports the current operator status and all outstanding user
requests for the terminal from which this command was entered.

8-17

DCL COMMANDS USED BY OPERATORS

/TERMINAL={terminal-name[, ••• ])
Broadcasts a message to one or more specified terminals. If more
than one terminal is specified, separate them with commas and
enclose the entire list within parentheses.
/TO=identification-number
Sends a message to the user or file system indicated
identification number and completes the request.

the

Broadcasts a message to all terminals at which users
in to the system.

logged

/USER
are

Table 8-3
REPLY/ENABLE and REPLY/DISABLE Keywords
.-----------------··---· ····-·-·· ··-·--·-···-···--····

Keyword

Function

CENTRAL

Inhibits/allows messages sent to the
operator identified as the central
system operator.

DEVICES

Inhibits/allows messages pertaining to
mounting disks and tape volumes.

DISKS

Inhibits/allows messages pertaining to
mounting a~d dismounting disk volumes

NET

Inhibits/allows messages pertaining to
networks. The CENTRAL keyword must
also be specified to inhibit network
messages.

OPERl through OPER12

Inhibits/allows messages sent to
operators identified as OPERl,
OPER2, ••• , OPER12.

PRINTER

Inhibits/allows messages pertaining to
print requests.

TAPES

Inhibits/allows messages pertaining to
mounting and dismounting tape volumes.

Examples

$REPLY/ALL/BELL "SYSTEM GOING DOWN FOR BACK-UP.

PLEASE LOG OFF."

This command broadcasts a message to all terminals on the
system.
This message is prefixed with terminal name, the
user name of the sender, and, when DECnet is installed, the
node name.

8-18

DCL COMMANDS USED BY OPERATORS
2.

$ REPLY/ENABLE=DISKS
Opcom, 14-JUN-1980

10:21:56.04, terminal enabled, operator=_TTA3:

Opcom, 10:22:01.03, Operator terminal status, _TTA3:
DISKS,

The REPLY/ENABLE command designates the terminal TTA3 as an
operator
terminal that receives messages pertaining to
mounting and dismounting disks. The OPCOM message confirms
that terminal TTA3 is established as an operator's terminal.
3.

Opcom, 13:01:43.22, RALPH ACCNT=DOCUMENT REPLY-ID=57
Opcom, "TTAl":, "PLEASE MOUNT OPGUIDE ON DBA3:"
$ REPLY/PENDING=57 "YOU'LL HAVE T0 WAIT-THERE ARE SEVERAL REQUESTS BEFORE YOURS"
$

REPLY/T0=57
Opcom, 13:11:14.55, REQUEST COMPLETED, operator=TTA4: ID=57

The OPCOM message indicates that a user wants the operator to
place the disk volume labeled OPGUIDE 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 keeps the process associated with the
user in a wait state. Therefore, the user cannot enter other
commands until the operator fulfills or aborts the request.
The operator later mounts the specified disk on the specified
drive and sends a message to the user indicating that the
request has been fulfilled. When no message accompanies the
REPLY/TO command, OPCOM sends a standard message indicating
that the task has been performed.
4.

$ REPLY/STATUS

Opcom, 15:25:43.73, Operator terminal status, TTE3:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS~ NETWORK
OPER(l,2,3,4,5,~,7,8,9,lO,ll,l2)

The REPLY/STATUS command requests that the operator terminal
status for terminal TTE3 be displayed. The response from
OPCOM indicates that terminal TTE3 is enabled to receive
messages from all devices.
5.

REPLY/BELL/TERMINAL=TTCl:

"YOUR FILE HAS COMPLETED PRINTING.

BOB S."

This REPLY command sends a message to the user logged in at
terminal TTCl.
When the message is displayed, a bell rings
at that terminal.

8-19

DCL COMMANDS USED BY OPERATORS
6.

$REPLY/ENABLE
$
Opcom, 15:00:24.69, terminal enabled, operator=_TTCO:
$

Opcom, 15:00:27.53 Operator terminal status, TTCO:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK,
OPER(l,2,3,4,5,6,7,8,9,10,11,12)

$REPLY/DISABLE= (PRINTER, TAPES)
Opcom, 17:14:36.39, Operator terminal status,
CENTRAL, DISKS, DEVICES, CARDS, NETWORK,
OPER(l,2,3,4,5,6,7,8,9,10,11,12)

TTCO:

The REPLY/ENABLE command designates terminal TTCO to receive
messages from all facilities.
Later, the REPLY/DISABLE
command selectively disables TTCO from receiving messages
pertaining to print devices and tapes.

8-20

DCL COMMANDS USED BY OPERATORS

Set
8.7

SET

Description
The Set command options allow the operator to establish or change
characteristics of a process, job, or device.

the

The Set command options described on the following pages are confined
to those options that require privileges not normally given to users.
The options that do not require special privileges are described under
the Set command in the VAX/VMS Command Language User's Guide. Table
8-4, below, lists all Set command options.
Format
SET

option

Options
ACCOUNTING
DEVICE
LOGINS
PRINTER
PROTECTION/DEVICE
TIME
UIC
Prompts
What:

option
Table 8-4
Options'for the Set Command
Option

Description

ACCOUNTING

Selectively enables or disables
the recording of particular kinds
of accounting information

CARD READER 1

Defines the translation mode
a card reader

for

[NO] CONTROL_Yl

Enables or disables the
the
<CTRL/Y> function
interrupt an image

of
to

DEFAULT!

Changes the default
directory
and/or disk device used to locate
and catalog files

use
key

1. Described in the VAX/VMS Command Language User's Guide.

(continued on next page)

8-21

DCL COMMANDS USED BY OPERATORS
Table 8-4 {Cont.)
Options for the Set Command
Option

Description

DEVICE

Establishes the
spooling
and
error-logging status on a device
Establishes
a
virtual
communication
link
between a
terminal and a network node to
which
the
terminal
is
not
directly connected

LOGINS

Establishes the maximum number of
users able to log in to the
system

MAGTAPE 1

Defines the density of a magnetic
tape device or rewinds a tape

MESSAGE!

Overrides or
messages

[NO] ONl

Suppresses or restores command
interpreter error-checking in a
command procedure

PASSWORD!

Allows users to change their
passwords

PRINTER

Establishes the characteristics
of a specific line printer

PROCESS!

Defines execution characteristics
of a process

PROCESS/PRIORITYl

Changes the base
process

PROTECTION!

Changes the protection applied to
a file or a group of files,
restricting or allowing access to
the file by different categories
of users

PROTECTION/DEFAULT!

the
default
Establishes
protection
for
all
files
subsequently created during the
terminal session or batch job

PROTECTION/DEVICE

Establishes the protection for
non-file-structured device

QUEUE/ENTRY 1

Changes the current status or
attributes of jobs that have not
yet been processed, but are in
print or batch queues

'-···-----1. Described in the VAX/VMS Command

supplements

Languag~_yser's

priority

system

own

Guide.

(continued on next page)

8-22

DCL COMMANDS USED BY OPERATORS
Table 8-4 (Cont.)
Options for the Set Command
Option

Description

RMS DEFAULTl

Defines default multiblock and
multibuffer counts for VAX-11 RMS
file operations

TERMINALl

Defines the characteristics of
terminal

TIME

Resets the system time

UIC

Establishes
a
new
user
identification code (UIC) as the
process UIC

[NO] VER! FY l

Suppresses or causes all command
lines
in
command
procedures
subsequently
executed
to
be
displayed
at the terminal or
printed in a batch job

WORKING SETl

Establishes a default working set
size for images executed in the
current process

'-----------·-------------------~----~·-·--------'

1. Described in the VAX/VMS Command Language User's Guide.

8-23

DCL COMMANDS USED BY OPERATORS

SET ACCOUNTING
8.7.1

SET ACCOUNTING

Description
This command enables or disables the lpgging of various activities in
the accounting log file
(SYSSSYSDISK: [SYSMGR]ACCOUNTING.DAT). The
operator also can use SET ACCOUNTING to close the current accounting
log file and to open a new one with a version number incremented by 1.
As described in the VAX/VMS System -~-~E_ag~-E-'~ Guide, when the operator
enables accounting by use of the /ENABLE qualifier, the following
types of accounting records can be recorded in the accounting file:
1.

Records written when interactive processes terminate

Records written when batch processes terminate

Records written
terminate

Records written when printing jobs are completed

Records written when login failures occur

Records written
accounting file

when

subprocesses

users'

messages

detached

are

sent

processes

Note that when the system is initially bootstrapped all accounting
enabled. Accounting must be explicitly disabled.

the
is

For a detailed description of the accounting log file records, see the
discussion of the Send Message to Accounting Manager System Service in
the VAX/VMS System Services Reference Manual or the VAX/VMS _§_y_ste~
Manager's Guide.
----------- ---------------

Format
----------~····-----------------------······----·------··

----- --------------------------------------·--·----··-··

SET ACCOUNTING
Command Qualifiers

Defaults

/DISABLE[=(keyword[, ••• ])]
/ENABLE[=(keyword[, ••• ])]
/NEW_FILE

None.

---------·-

------------------ - - - - - - - · - _,,_______________________________________________ ---··

Prompts
None.

Command Parameters
None.

8-24

""'

DCL COMMANDS USED BY OPERATORS

Command Qualifiers
/DISABLE[=(keyword[, ••• ])]
Disables the logging of all activities in the accounting log
file.
To disable specific activities selectively, the operator
includes one or more keywords with /DISABLE. T~hen more than one
keyword is specified, each is separated by a comma and the entire
list is enclosed in parentheses. Table 8-5 lists and describes
the activities that can be disabled.
/ENABLE[=(keyword[, ••• ])]
Enables the logging of all activities in the accounting file. To
enable specific activities selectively, the operator includes one
or more keywords with /ENABLE. When more than one keyword is
specified, each is separated by a comma and the entire list is
enclosed within parentheses. Table 8-5 lists and describes the
activities that can be enabled.
/NEW_FILE
Closes the current accounting file named ACCOUNTNG.DAT, and opens
a new version of that file.
Table 8-5
SET ACCOUNTING/DISABLE and SET ACCOUNTING/ENABLE Keywords
Keyword

Function

BATCH

Inhibits/allows
termination

INTERACTIVE

Inhibits/allows the recording of interactive job
termination

Inhibits/allows the recording of login failures

Inhibits/allows the recording of all print jobs

PROCESS

Inhibits/allows the
termination

the

recording

batch

all

job

process

Examples
1.

$ SET ACCOUNTING/ENABLE=(BATCH,INTERACTIVE)

This command requests that all batch and interactive jobs
recorded in the accounting file at job termination.
2.

SET ACCOUNTING/NEW_FILE

This command closes the current accounting file and creates a
new version of it.

8-25

DCL COMMANDS USED BY OPERATORS

SET DEVICE
8.7.2

SET DEVICE

Description
This command establishes a print device or terminal as a spooled
device or establishes the status of error-logging for a device.
When the operator specifies the /SPOOLED qualifier, program output
that uses RMS or FCS and specifies the print device name is written
onto an intermediate disk rather than written directly to the print
device or terminal.
When the operator specifies the /ERROR LOGGING qualifier, all error
messages reported by the device on whi~h error-logging is enabled, are
recorded in the error log file.

Format
SET DEVICE device-name[:]
Command Qualifiers

Defaults

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

None.

Prompts
Device:

device-name[:]

Command Parameters
device-name(:]
Specifies the name of the device whose spooling or error-logging
status is to change.
The device must be a print device or a
terminal if its spooling status is to change;
the device must be
a disk, or magnetic tape if its error-logging status is to
change.

Command Qualifiers
/SPOOLED[=(queue-name(:] ,intermediate-disk-name[:])]
/NOSPOOLED
Control whether files will be spooled to an intermediate disk.
The queue name indicates the print queue to which a file
is
queued.
If a queue name is not supplied, it defaults to the name
of either the print device or terminal.
The intermediate disk name identifies the disk to whiah the
spooled files are written.
If the intermediate disk name is not
supplied, it defaults to SYS$DISK
(the current default disk).
The intermediate disk must be mounted before files can be written
to it.

s-2n

DCL COMMANDS USED BY OPERATORS

Once the device has been set spooled to a disk, that disk cannot
be dismounted until the spooled device is set /NOSPOOLED. All
channels must be deassigned from a print device before its
spooling characteristics can be changed. ~lso, the queue that is
assigned to the device must be stopped.
/ERROR LOGGING
/NOERROR_LOGGING
Control whether device errors are logged in the error log file.
By default, when the system is
enabled.
The current status
DEVICE/FULL command.

bootstrapped, error-logging is
can be determined with the SHOW

Examples
1.

$ SET DEVICE/SPOOLED={LPAO)

LPAO:

In this command, the /SPOOLED qualifier requests that the
print queue LPAO be spooled to an intermediate disk before
files directed to the disk are printed.
Because
no
intermediate
disk was specified, the intermediate disk
defaults to SYS$DISK.
2.

$ SET DEVICE/ERROR_LOGGING

DBB2:

This command requests that all device errors reported on DBB2
be logged in the error log file.

8-27

DCL COMMANDS USED BY OPERATORS

SET LOGINS
8.7.3

SET LOGINS

Description
This command imposes a limit on the number of users who can gain
access to the operating system.
This command also displays the
current interactive level as described below.
The SET LOGINS command is not retroactive. Therefore all users logged
in to the system before the operator issues the SET LOGINS command are
not affected by the command. However, once the limit set by the
operator is reached, no more users can log in to the system until
someone else logs out. Users with the OPER privilege are not affected
by the limit.
The SET LOGINS command, when issued without the
qualifier, has no effect.

/INTERACTIVE

command

If the operator does not specify a value for n in the /INTERACTIVE=n
qualifier, the SET LOGINS command displays the following information:
Login quotas - Interactive limit=x, Current interactive value=y
The value x represents the current interactive limit, and the value
represents the number of users currently logged in to the system.

Format
SET LOGINS
Command

Defaults

Qua~ll_!ers

/INTERACTIVE [ =n]

None.

Prompts
None.
Command Parameters
None.
Command Qualifiers
/INTERACTIVE [=n]
Establishes the number of interactive users allowed to gain
access to the system. When the operator does not supply a value
for the n, SET LOGINS displays the current status of the login
quotas.

8-28

DCL COMMANDS USED BY OPERATORS

Examples
1.

$ SET LOGINS/INTERACTIVE=S

Login quotas - Interactive limit=S, Current interactive value=3
This command specifies that only five interactive
be logged in to the system.
2.

users

can

$ SET LOGINS/INTERACTIVE

Login quotas - Interactive limit=l5, Current interactive value=4
When the SET LOGINS command is issued without a parameter,
the /INTERACTIVE qualifier requests that the current status
of the login quotas be displayed.
The message returned
indicates that the maximum number of interactive users
allowed on the system is 15 and that the number
of
interactive users currently logged in is 4.

8-29

DCL COMMANDS USED BY OPERATORS

SET PRINTER
8.7.4

SET PRINTER

Description
This command establishes the characteristics of a specific line
printer.
The defaults listed below are the defaults for an initially
bootstrapped system.
Format
SET PRINTER printer-name[:)
Command

Quali_!!_~S.

Defaults

/[NO)CR
/[NO)FF
/LAll
/LA180
/[NO]LOWERCASE
/LPll
/PAGE=n
/UNKNOWN
/[NO] UPPERCASE
/WIDTH=n

/NOCR
/FF
/NOLOWERCASE
/LPll
/PAGE='14
/UPPERCASE
/WIDTH=l32

Prompts
Device:

printer-name[:]

Command Parameters
printer-name[:]
Specifies the name of a line printer that will have its
characteristics set or modified. If the printer is set /SPOOLED,
the logical I/O privilege {LOG I/O) is required to modify its
characteristics.
Command Qualifiers
/CR
/NOCR
Control whether the printer driver outputs a carriage return
character; this characteristic is set for printers on which line
feeds do not imply carriage returns.
Specify /NOCR for printers where the line feed, form feed,
vertical feed, and carriage return characters empty the printer
buffer, so carriage return characters will be held back and
output only if the next character is not a form feed or vertical
tab. Carriage return characters are always output on devices
that have the carriage return function characteristic set.
The default is /NOCR.
8-30

DCL COMMANDS USED BY OPERATORS
/FF
/NOFF
Indicate whether the printer performs a mechanical form feed.
Use the /NOFF qualifier when the printer does not automatically
perform mechanical form feeds. This qualifier allows the driver
to convert form feeds into multiple line feeds and to output
them.
The default qualifier is /FF.
/LAll
Allows the operator to set the appropriate printer type when the
printer is an LAll line printer.
This qualifier provides
information for the SHOW PRINTER command which in turn provides
the user with information about specific printers.
/LA180
Allows the operator to set the appropriate printer type when the
printer is an LA180 line printer.
This qualifier provides
information for the SHOW PRINTER command which in turn provides
the user with information about specific printers.
/LOWERCASE
/NOLOWERCASE
Indicate whether the printer prints lowercase or
alphabetic
letters.
When
the
operator
/NOLOWERCASE, all alphabetic characters are
uppercase.

just uppercase
specifies
the
translated
to

The
/[NO] LOWERCASE
and
/[NO] UPPERCASE
qualifiers
complementary.
That
is,
/LOWERCASE
is
equivalent
/NOUPPERCASE, and /NOLOWERCASE is equivalent to /UPPERCASE.

are
to

The default is /NOLOWERCASE.
/LPll
Allows the operator to set the appropriate printer type when the
printer is an LPll line printer.
This qualifier provides
information for the SHOW PRINTER command which in turn provides
the user with information about specific printers.
/PAGE=n
Establishes the number of lines per page on the currently
installed forms;
the number of lines can range between 0 and
255. The print symbiont uses this value to determine when to
perform an automatic form feed. The printer driver uses this
value as described by the /NOFF qualifier to determine the number
of line feeds that must be issued to simulate a form feed.
The default value is n4 lines per page.
/UNKNOWN
Allows the operator to set the appropriate printer type when the
printer is an unknown printer type. This qualifier provides
information for the SHOW PRINTER command which in turn provides
the user with information about specific printers.

8-31

DCL COMMANDS USED BY OPERATORS

/UPPERCASE
/NOUPPERCASE
Indicate whether the printer prints lowercase or just uppercase
alphabetic characters.
When the operator specifies /UPPERCASE,
all alphabetic characters are translated to uppercase.
The
/[NO]UPPERCASE
and
/[NO] LOWERCASE
qualifiers
complementary.
That
is,
/UPPERCASE
is
equivalent
/NOLOWERCASE, and /NOUPPERCASE is equivalent to /LOWERCASE.

are
to

The default is /UPPERCASE.
/WIDTH=n
Establishes the number of characters per output line on currently
installed forms, where the width, n, can range between 0 and
n5535.

The default value is 132 characters per line.
Examples

$ SET PRINTER/PAGE=n0/WIDTH=80

LPAO:

The SET PRI~TER command establishes the size of an output
page as nO lines and the width of a line as 80 characters.
2.

$ SET PRINTER/LAll

LPBO:

The SET PRINTER command establishes the line printer LPBO
an LAll printer.
3.

$ SET PRINTER/LOWERCASE LPAO:

The SET PRINTER command requests that lowercase
enabled on line printer LPAO.

8-32

printing

DCL COMMANDS USED BY OPERATORS

SET PROTECTION/DEVICE
8.7.5

SET PROTECTION/DEVICE

Description
This command establishes the protection to be applied to a specific
non-file-structured device. The protection for the device thus limits
the type of access available to users.
Devices can be accessed by users in four categories:
•

System -- all users who have group numbers of 0 through 10
octal and users with physical or logical I/O privilege
(generally,
system
managers,
system
programmers,
and
operators).
The above group number for system users is the
default group number.
The group number parameter can be
changed at system generation time to any octal value in the 0
through 377 range.

•

Owner -- the user identification code (UIC) of the person who
issued the SET PROTECTION command and therefore owns the
device.

•

Group -- all users who have the same
UICs as the owner of the device.

•

World -- all users who do not fall into the categories above.

group

number

their

For shareable devices (such as the LPA-11), each category of users
below can be allowed or denied one of the following types of access:
•

Read -- the right to issue read requests to the device

•

Write -- the right to issue write requests to the device

•

Logical I/O -- the right to issue logical I/O requests to
device

the

•

Physical I/O -- the right to issue physical
the device

I/O

requests

For nonshareable devices, such as terminals and card readers, each
category of users either can be allowed or denied access to allocate
and assign channels to the device. The Read category controls whether
a user can allocate and assign channels to the device. All other
categories are not relevant for nonshareable devices.
Any combination of access types can be specified for any
user.
When the operator specifies a user access code, the
abbreviated to one character. The abbreviations are:
READ
WRITE
LOGICAL I/O
PHYSICAL I/O

category
code

must

of
be

R
W
L
P

The user-access codes and user categories can be specified in any
order.
If the operator omits a user access code for a user category,
that category of user is denied that type of access. If the operator
omits a user category, the user category is allowed all access.
8-33

DCL COMMANDS USED BY OPERATORS
To specify a protection code, the operator separates the user category
from the access type with a colon. To specify more than one user
category, separate each category by a comma and enclose the entire
protection encoding in parentheses.
Format
SET PROTECTION[=code]/DEVICE device-name[:]
Cornman~

Qualifiers

/OWNER_UIC=uic

Defaults
None.
----------------------------'

Prompts
File:

device-name[:]

Command Parameters
code
Establishes the protection code for a device.
The protection
code defines the user and type of access allowed the user. The
code should be specified according to the syntax rules explained
in the "Description" section.
If the operator does not specify a protection code, no protection
checks are made and all users are allowed to gain access to the
device.
device-name[:]
Specifies the name of the device whose protection is to be set or
modified. The device must be a non-file-structured device.
Command Qualifiers
/OWNER_UIC=uic
Requests that the identification code be assigned ownership of
the device for the purpose of access checks. The default owner
is the UIC of the process issuing the SET PROTECTION command.
Specify the UIC in the format:
[group,member]
In this format, group is an octal number from 0 through 377
representing the user's group number; and member is an octal
number from O through 377 representing the user's member number.
The square brackets ([ ]) are required to enclose the UIC.

8-34

DCL COMMANDS USED BY OPERATORS
Examples
1.

$SET PROTECTION=(SYS:RWLP,OWN:RWLP,G:,W:)/DEVICE LAAO:
This command requests that the protection for device LAAO be
set to allow all types of access to system processes and
processes with the UIC of the current process and to deny
access to anyone else.

$SET PROTECTION=(SYS:,OWN:RWLP,G:,W:)/DEVICE/OWNER_UIC=[l03,4] LABO:

This command requests that the protection for device LABO be
set to allow all types of access to processes with a UIC of
[103,4] and to deny access to anyone else.
3.

$SET PROTECTION=(SYS:R,O:G:,W:)/DEVICE/OWNER_UIC=[l,4] TTAl:
This command requests that the protection for the terminal
TTAl is to be set to allow only system processes to allocate
the device and denies accessibility to the device to anyone
else. This type of protection is recommended for interactive
terminals, if a secure system is desired.
Note that the
above protection code only restricts which users can allocate
the device, but does not restrict users from logging in to
the device.

8-35

DCL COMMANDS USED BY OPERATORS

SET TIME
8.7.6

SET TIME

Description

Resets the system time.
The system time
is
time-dependent activities in the VAX/VMS system.

used

for

all

Format
------··-·--···-···---·-----·-·

SET TIME=time
Command Qu.9_!_!. ~_!-~.~~

Defaults

None.

Prompts

None.
Command Parameters

=time
The VAX/VMS system contains an interval clock, which is used
both, as a timer to record intervals between various internal
events and as the source clock for displaying the time of day.
The SET TIME command allows the operator to reset the system
time. However, both, OPER and LOG_IO privileges are required.
To reset the system time, type the SET TIME command followed by
an explicit time value expressed in the standard absolute time
format, described below. The interval system clock is reset to
the time specified.
The date, the time, or both can be specified.
The
format is used to specify the absolute time parameter:
[dd-mmm-yyyy [:]]

following

[hh: mm: ss. c]

Field

Description

Day of the month (1 through 31}

mmm

Month; must be specified using one of
3-character abbreviations listed below:
JAN, FEB, MAR, APR, MAY, JUN
JUL, AUG, SEP, OCT, NOV, DEC

yyyy

Year

8-36

the

DCL COMMANDS USED BY OPERATORS

Field

Description

Hour of the day (0 through 23)

Minute of the hour (0 through 59)

Seconds (0 through 59)

Hundredths of seconds (0 through 99)

Note that the period between seconds and hundredths of seconds is
a delimiter; it is not a decimal point. For further information
on absolute time format, refer to the VAX/VMS Command Language
User's Guide.

Examples
1.

$SET TIME = 3:21:24.03
$ SHOW TIME
19-JAN-1980 3:22:19.53
The SET TIME command sets the system time to the specified
time.
The operator requests a display of the current time
with the SHOW TIME command.

8-37

DCL COMMANDS USED BY OPERATORS

SET UIC
8.7.7

SET UIC

Description
This command establishes a new user identification code as the
default.
The operator uses the SET UIC command to gain access to a
restricted file; that is, a file contained in a directory whose
protection restricts access to the owner of that directory.
Use of this command requires change-mode-to-kernel (CMKRNL) privilege.
By default, the SET UIC command changes the default directory name to
the UIC supplied.
Hence, to set the default directory to a code
different from the UIC, the operator must issue the SET DEFAULT
command aftar the SET UIC command.
Format
~-----·

-·--...-.........._.... _.

__·--·-·-----------------------------

SET UIC uic
Command Qualifiers

Defaults

None.

Prompts
File:

uic

Command Parameters
uic
Specifies the group number and member number.
UIC is:

The format for the

[group, member]
In this format, group is an octal number from O through 377
representing the user's group number; and member is an octal
number from 0 through 377 representing the user's member number.
Enclose the UIC within square brackets or angle brackets.

8-38

DCL COMMANDS USED BY OPERATORS
Examples

$ SET UIC

[370,10)

This command establishes the operator's UIC as [370,10]. The
operator can now read or modify any files whose access is
restricted to this UIC.
2.

$ SET UIC

[214,41

$ SET DEFAULT [ANDERS]

The SET UIC command sets the operator's UIC to (214,4];
the
SET DEFAULT command sets the default directory name to
[ANDERS] •

8-39

DCL COMMANDS USED BY OPERATORS

START/QUEUE
8.8

START/QUEUE

Description
This command starts or restarts specific print and batch queues.
The
operator uses the START/QUEUE to start executing or printing jobs in a
newly created queue or to restart executing or printing jobs in an
existing queue that was previously stopped.
To start a newly created queue, the operator must first initialize the
queue with the INITIALIZE/QUEUE command.
Note that any qualifier
specified with the INITIALIZE/QUEUE command also can be specified with
the START/QUEUE command. Also, this command can override options that
are common to itself and the INITIALIZE/QUEUE command such as
/ENAB-GEN, /BURST and /FORMS.

Format
START/QUEUE

queue-name[:]

Command Qualifiers

Defaults

/BACKSPACE
/BATCH
/[NO]BURST
/CHARACTERISTICS={c[, ••• ])
/CPUDEFAULT=t
/CPUMAXIMUM=t
/[NO]DISABLE SWAPPING
/[NO] ENABLE GENERIC PRINTING
/[NO]FLAG /FORMS TYPE=n
/[NO]GENERIC
/JOB LIMIT=n
/NEXT
/PRIORITY=n
/PROCESS=process-name
/TERMINAL
/TOP OF FILE
/WSDEFAULT=n
/WSQUOTA=n

/NOB UR ST

/NODISABLE SWAPPING
/ENABLE GENERIC PRINTING
/NO FLAG/NOGENERIC
/JOB_LIMIT=l
/PRIORITY=4

Prompts
Queue:

queue-name[:]

Command Parameter
queue-name[:]
Specifies the name of a queue to be started or restarted.

8-40

DCL COMMANDS USED BY OPERATORS
Command Qualifiers
/BACKSPACE
Backspaces one page before printing resumes.
used in restarting a queue.

This

qualifier

/BATCH
Indicates that this is a batch queue.
/BURST
/NOBURST
Control whether a burst header page is
job.

printed

for

each

Use the /BURST qualifier to print a header page over the paper
perforations;
so that the page header is visible from the side
of a stack of paper. Using this qualifier simplifies separating
listings.
The default is /NOBURST.
/CHARACTERISTICS=(c[, ••• ])
Specifies one or more desired characteristics for printing a
file(s).
If more than one characteristic is desired, separate
each with a comma and enclose the list in parentheses.
For
further information on specifying characteristics, refer to the
VAX/VMS System Manager's Guide.
/CPUDEFAULT=t
Defines the default CPU time limit for batch jobs.
Specify the value t with a delta time value, O, or, either the
word NONE or INFINITE.
Both 0 and the word infinite allow a
process unlimited CPU time when the CPU time limit is not
restricted by the /CPUMAXIMUM qualifier or the value in the user
authorization file. Specify NONE when a default CPU time limit
is not desired.
The value for t cannot exceed the CPU time limit set by the
/CPUMAXIMUM qualifier. For more information, refer to Table 8-1
in Section 8.5.
/CPUMAXIMUM=t
Defines the maximum CPU time limit for batch jobs.
Use this
qualifier to override the CPU time limit specified in the user
authorization file.
Use a delta time value, O, or the word NONE or INFINITE to
specify the value t. The values o and INFINITE allow the process
unlimited CPU time. Specify NONE when a maximum CPU time limit
is not desired.
For more information refer to Table 8-1 in
Section 8.5.

8-41

DCL COMMANDS USED BY OPERATORS

/DISABLE SWAPPING
/NODISABLE SWAPPING
Control whether batch jobs executed from the queue can be swapped
in and out of memory.
The default is /NODISABLE_SWAPPING.
/ENABLE GENERIC PRINTING
/NOENABLE_GENERIC_PRINTING
Specifies whether files queued to a generic queue can
in this physical-device queue for printing.

placed

The default is /ENABLE_GENERIC_PRINTING.
/FLAG
/NO FLAG
Specifies whether a header page is printed at
the first file in each print job.

the

beginning

The default is /NOFLAG.
/FORMS_TYPE=n
Specifies the forms type for a specific 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-specific.
/GENERIC
/NOGENERIC
Specifies that this is a generic queue and any files placed in
this
queue
can
be moved for printing to any available
physical-device queue that has matching characteristics.
The default is /NOGENERIC.
/JOB_LIMIT=n
Indicates the number of batch jobs that can be
executed
concurrently from the batch queue. The job limit default value
for n is 1.
/NEXT
Indicates whether the current job will be printed when the
is restarted.

queue

/PRIORITY=n
Specifies the base process priority at which jobs are initiated
from this batch queue. The queue priority default value of n is
4.

8-42

DCL COMMANDS USED BY OPERATORS

/PROCESS=process-name
Allows users to specify their own print symbionts.
Specify the
print symbiont name using 1 through 15 character(s). The system
will supply the device and directory name SYS$SYSTEM, and the
file type EXE.
/TERMINAL
Indicates that the generic queue
terminals instead of print devices.

will

associated

with

/TOP_OF FILE
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 a queue.
/WSDEFAULT=n
Defines a working set default for a batch job.
A positive integer in the range 1 through n5535, O, or the word
NONE may be be specified for n.
Specify 0 or NONE and the
working default set value becomes the value specified either in
the user authorization file or by the SUBMIT command (if
specified). For more information, refer to Table 8-2 in Section
8.5.
/WSQUOTA=n
Defines a working set page size for a batch job.
A positive integer in the range 1 through n5535, o, or the word
NONE may be specified for n. If O or NONE is specified for n,
the value for the working set quota is the value specified either
in the user authorization file or by the SUBMIT command. For
more information, refer to Table 8-2 in Section 8.5.

Examples
1.

$ START/QUEUE/BATCH SYS$BATCH
This command starts the batch queue named SYS$BATCH.
/BATCH qualifier indicates that this is a batch queue.

$ STOP/QUEUE LPAO
$ START/QUEUE/TOP_OF_FILE

The

LPAO

The STOP/QUEUE command suspends operation of the physical
queue LPAO. Then the START/QUEUE/TOP OF FILE command resumes
operation; however, the job currently printing is started
again from the beginning.
3.

$ INITIALIZE/QUEUE LPAO
$ START/QUEUE/NOFLAG LPAO
The INITIALIZE/QUEUE command initializes the queue named
LPAO.
The START/QUEUE command then starts the queue. The
/FLAG qualifier requests that a header page precede each job
in the queue.

8-43

DCL COMMANDS USED BY OPERATORS

STOP/QUEUE
8.9

STOP/QUEUE

Description
This command suspends or controls operations of specific batch and
print queues. When the operator issues the STOP/QUEUE command without
including any qualifiers, the current queue is placed in a paused
state.
To delete a queue, the
STOP/QUEUE.

operator

must

first

stop

the

queue

using

Format
STOP/QUEUE

queue-name[:]

Command Qualifiers

Defaults

/ABORT
/ENTRY
/NEXT
/REQUEUE

None.

Prompts
QUEUE:

queue-name[:]

Command Parameter
queue-name[:]
Specifies the name of the queue to be stopped.
Command Qualifiers
/ABORT
Aborts a print job that is currently being printed;
the next job
in the print queue is then started without a pause or stop. The
STOP/QUEUE/ABORT command is equivalent to the STOP/ABORT command.
This command is fully described in the VAX/VMS Command Language
User's Guide.
This qualifier can only be applied to jobs in a print queue.
/ENTRY
Terminates the execution of a batch job that is running.
This
qualifier terminates only jobs that are running. To delete an
entry that is in a queue and awaiting execution,
use the
DELETE/ENTRY command.
The STOP/QUEUE/ENTRY is equal to the
STOP/ENTRY command described
in the VAX/VMS Command Language
user's Guide.

8-44

DCL COMMANDS USED BY OPERATORS

/NEXT
Inhibits further dequeueing from a specific queue. When /NEXT is
specified, the current job is allowed to complete before the
queue is stopped. When this qualifier is omitted, the queue is
paused immediately.
/REQUEUE
Stops printing the current job, requeues the job, and gives it a
priority of 1. The next job in the queue is immediately dequeued
for printing. The STOP/QUEUE/REQUEUE command is equal to the
STOP/REQUEUE command described in the VAX/VMS Command Language
User's Guide.

Examples
1.

$STOP/QUEUE/ABORT

LPAO

This command aborts the job currently printing on LPAO.
next job in the queue then begins printing.
2.

$STOP/QUEUE/NEXT

The

LPBO

This command inhibits further printing of jobs in the queue
LPBO; the /NEXT qualifier allows the current job to complete
printing.
3.

Opcom, 01:15:34.28, device is offline, LPAO
$ STOP/QUEUE

LPAO

The OPCOM message indicates that print device LPAO is
malfunctioning.
The operator issues the STOP/QUEUE command
to suspend the queue associated with the malfunctioning print
device and to find out what is wrong.

8-45

APPENDIX A
SUMMARY OF DCL COMMANDS

This appendix summarizes all DCL commands. For complete descriptions
of commands not discussed in this manual, refer to the VAX/VMS Command
Language User's Guide, unless noted otherwise.
Description

Command
@

Execute procedure;
executes
a
command
procedure or places data in a command file in
the input stream
Arithmetic assignment;
equates
a
local
symbol name to an arithmetic expression or
constant
Arithmetic assignment;
equates a
global
symbol name to an arithmetic expression or
constant

String assignment; equates a local symbol
name to any character string;
defines a
local symbol name as a synonym for all or a
portion of a DCL command

:==

String assignment; equates a global symbol
name to any character string;
defines a
global symbol name as a synonym for all or a
portion of a DCL command

ALLOCATE

Reserves a device for use by a single user
and, optionally, assigns a logical name to
the device

ANALYZE

Describes the contents of an object file or
the
symbol
information
appended
to a
shareable image file

APPEND

Adds the contents of one or more files to the
end of another file

ASSIGN

Defines a file specification or a device name
to be associated with a logical name for
subsequent use in commands or programs

ASSIGN/MERGE!

Removes all jobs from one print
places them in another queue

1. Described in this manual.
A-1

queue

and

SUMMARY OF DCL COMMANDS

Command

Description

ASSIGN/QUEUE!

Assigns a device to a logical queue

BASIC

Invokes the VAX-11 BASIC compiler to enter
and compile BASIC languaqe source statements

BASIC/RSXll

Invokes the PDP-11 BASIC-PLUS-2 compiler to
enter
and compile BASIC language source
statements

BLISS

Invokes the VAX-11
BLISS-32 compiler
compile one or more BLISS source programs

CANCEL

Halts periodic
execution
of
an
scheduled for execution in a process

imaqe

Cancels an input or output
sequential file or device

COBOL/C74

Invokes the VAX-11 COBOL-74 compiler
compile COROL source statements

COBOL/RSXll

Invokes the PDP-11 COBOL-74/VAX compiler
compile COBOL language source statements

CONTINUE

Resumes execution of an interrupted
program, or command procedure

command,

COPY

Copies one or more files
additional files

CORAL

Invokes the
compile one
programs

CREATE

Creates a
file
from data entered
terminal or in the input stream

CREATE/DIRECTORY

Defines a new directory or
cataloging files

DEALLOCATE

Relinquishes use of a previously allocated
device,
thus making the device available to
other users

DEASSIGN

Cancels a logical name assignment made
the ALLOCATE, ASSIGN, or DEFINE command

DEASSIGN/QUEUE 1

Deassigns a device from a queue

DEBUG

Invokes the VAX-11 Symbolic Debugger to hegin
or continue interactive debugging

DECK

Marks the beginning of records to he read as
the input data stream for a command (required
only when data contains a dollar sign in the
first position of any record)

DEFINE

Equates
character
strings
specifications or logical names

1. Described in this manual.

A-2

into

path

one

VAX-11 CORAL nh compiler to
or more CORAL source language
at

the

subdirectory

for

with

file

SUMMARY OF DCL COMMANDS

Description

Command
DELETE

Removes a directory entry for a file or files
and
makes
any
data
in
the
file(s)
inaccessible

DELETE/ENTRY

Deletes an entry from a print or batch job
queue or stops processing the current job

DELETE/QUEUE!

Deletes batch and print queues

DELETE/SYMBOL

Deletes a local or global symbol definition

DEPOSIT

Replaces the contents of a location
in
virtual memory with new data or instructions

DIFFERENCES

Compares the contents of two files
displays the differences between them