Digital PDFs

AA-L671A-TC

November 1981

107 pages

Original

6.4MB

Document:	RSX-11M/M-PLUS Batch and Queue Operations Manuai
Order Number:	AA-L671A-TC
Revision:	0
Pages:	107
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V4.1_Apr83/2_Operation/AA-L671A-TC_batch_198111.pdf

OCR Text

RSX-11 M/M-PLUS

Batch and Queue
Operations Manuai
Order No. AA-L671 A-TC

RSX-11 M Version 4.0
RSX-11 M-PLUS Version 2.0

digital equipment corporation · mayncrd, massachusetts

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

1981 Digital Equipment Corporation
All Rights Reserved.

Printed in U.S.A.

The postage-paid READER'S COMMENTS form on the last
document
requests the user's critical evaluation
preparing future documentation.

page of this
to assist in

The following are trademarks of Digital Equipment Corporation:
DEC
DEC US
DIGITAL
PDP
UNIBUS
VAX
DECnet

DECsystem-lo
DECSYSTEM-20
DECwriter
DIBOL
Edusystem
IAS
MASSBUS

PDT
RSTS
RSX
VMS
VT

~nmnomo
ZK2052

CONTENTS

Page
vii

PREFACE
SUMMARY OF TECHNICAL CHANGES
CHAPTER 1
1.1
l. 2

1. 3
1. 4
1. 4.1
1. 4. 2
1. 5
1. 5.1
CHAPTER 2
2.1
2.2
2.3
2.4
2.4.1
2.4.2
2.5
2.5.1
2.5.2
2.5.3
2.6
2.6.1
2.6.2
2.7
2.8
2.8.1
2.8.2
CHAPTER 3
3.1
3.2
3.3
3.3.1
3.4
3.4.1
3.4.2
3.4.3
3.4.4

INTRODUCTION TO THE QUEUE MANAGER
QUEUE MANAGER
QUEUE ASSIGNMENTS
PRINT COMMAND • • • •
BATCH PROCESSING • •
SUBMIT Command Example
User Batch Job Example
SHOW QUEUE (QUE /LIST) COMMAND
SHOW QUEUE - QUE /LI • • • •

• •
•
• •
• •
•
• •

1-1
1-2
1-3
1-7
1-7
1-8

• 1-9
1-9

QUEUING JOBS
SPOOLING OUTPUT
• • • • • • •
• 2-1
PRINT COMMAND
• • • • • • •
• • 2-2
DELETE COMMAND •
• • • • • • •
• • • • 2-10
PRINT JOBS QUEUED BY SYSTEM TASKS
2-12
Maps, Logs, and Listings • • • • •
• • • • 2-12
PIP, CLis, and Output Files
2-12
PRINT JOBS QUEUED BY USER TASKS •
2-13
Opening a File on Disk and Using .PRINT •
2-13
Opening a File on Disk and Using the PRINT
Command • • • • • • • • • • • • • • • • •
2-13
Opening a File on LPn: (RSX-llM-PLUS)
2-14
SHOW QUEUE AND SHOW PROCESSOR
2-14
SHOW QUEUE (QUE /LI) • • • • • • •
2-14
SHOW PROCESSOR (QUE /LI:DEV)
2-18
SET QUEUE (QUE/MOD)
• • • •
2-19
HOLDING AND RELEASING JOBS •
2-22
HOLD (QUE/HO)
• • • •
2-22
RELEASE (QUE/REL)
• • • •
2-23
PREPARING A USER BATCH JOB
THE VIRTUAL TERMINAL • •
•
A USER BATCH JOB • • • •
•
THE BATCH COMMAND LINE • • • • • •
• • • • •
Line Continuation
• • • • • • • • • •
• • •
BATCH-SPECIFIC COMMAND DESCRIPTIONS
• • • • •
JOB
EOJ
•

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

• 3-3
• 3-3

• 3-5
3-5
• • 3-7

DATA •

EOD
iii

CONTENTS
Page
3.4.5
3.4.6
3.4.7
3.4.8
3.4.9
3.4.10
3.4.11
3.5
3.6

STOP • • •
• • • • • • •
CONTINUE • • • • • • •
•
GOTO • • • • •
• • • •
•
ON • • •
• • • •
• • • • • •
SET
• • • • • • • • • • • • • •

•
•
•
•

3-8
3-8
3-8
3-9
3-11

• • • • •

3-11

Comments ( ! )
. • • • •
INDIRECT COMMAND FILES •
• • • • • • •
ALLOCATING DEVICES AND MOUNTING VOLUMES FROM
BATCH JOBS • • • • • •
QUEUING BATCH JOBS • •
• • • • • •
3.7
THE BATCH LOG • • • •
• • • • • • • •
3.8
CARD READER INPUT SPOOLING • • • • • •
3.9
3.9.1
Card Deck Format • • • • • • • • • • • •
The $SUBMIT Card • • • • • • • • •
3.9.1.1
The $PRINT Card • • • • •
• • • • • • •
3.9.1.2
The $PASSWORD Card • • • • •
• • • •
3.9.1.3
Card Reader Processor Operation • • • •
3.9.2

3-12
3-13

CHAPTER 4
4.1
4.2
4.2.1
4.2.2

4.2.3
4.3
4.4
4.5
4.6
4.7
4.7.1
4.7.2
4.8
APPENDIX A
A.l
A.1.1
·A. l. 2
A. l. 3

A.2
A.3

IF • • • • • • • • • • • • • •

3-13
3-14
3-19
3-23
3-24
3-25
3-26
3-27
3-27

AT-A-GLANCE GUIDE
PRINT (PRI) COMMAND • • • • • • • • • • • • • • • 4-1
BATCH-SPECIFIC COMMAND SUMMARY (RSX-llM-PLUS)
• • 4-2
Opening and Closing Batch Jobs • • • •
4-2
Data in Batch Jobs • • • • • • • • •
• • 4-3
Sequence Control Commands • • • •
• • 4-3
SUBMIT (SUB) COMMAND (RSX-llM-PLUS)
• • • • • • • 4-5
SHOW QUEUE (QUE/LI) COMMAND • • • • •
• •• 4-6
SHOW PROCESSOR (QUE /LI:DEV) COMMAND •
• 4-7
SET QUEUE (QUE /MOD) COMMAND • • • •
• • • • • 4-7
HOLD (QUE /HO) AND RELEASE (QUE /REL) COMMANDS • • 4-8
HOLD (QUE /HO) • • • • • • • •
4-8
RELEASE (QUE /RE)
• • • • •
• 4-9
DELETE (QUE /DEL) COMMAND
• • • • •
• • • 4-9
ERROR MESSAGES
BATCH PROCESSING ERROR MESSAGES • • • • • • • • • A-1
Error Messages in Batch Logs • • • • • • • • • • A-1
Error Messages to the Operator's Console . . . . A-4
Error Messages from the Card Reader Processor • A-5
OUTPUT DESPOOLER ERROR MESSAGES • • • • • • • • • A-9
DCL AND MCR ERROR MESSAGES FROM QUEUE MANAGER
COMMANDS • • • • • • • • • • • • • • • • • • • • A-11

GLOSSARY
INDEX

CONTENTS
Page
EXAMPLES
EXAMPLE 1-1
3-1
3-2
3-3
3-4
3-5

SHOW QUEUE Display • • • • • • • • • • • • •
User Batch Job Orwell • • • • • •
• • • •
Log File for User Batch Job Orwell • • • • •
User Batch Job Friend • • • • • • • •
Log File for User Batch Job Friend •
User Batch Job to be Submitted by CRP

1-10

3-20
3-21
3-22
3-22
3-24

FIGURES
FIGURE

1-1
1-2

Queue Assignments to Output Devices • • • •
How the PRINT Command is Processed • •

• 1-2

1-4

TABLES
TABLE

3-1

Batch-Specific Commands

• • • • • • • • • • • • • 3-3

PREFACE

MANUAL OBJECTIVES
The RSX-llM/M-PLUS Batch and
Queue Manager (QMG)-.~~ ~-

Queue

Operations

Manual

explains

the

On RSX-llM/RSX-llM-PLUS systems, the QMG provides for the orderly
queueing and dequeueing of print jobs to line printers or other output
devices. The QMG commands that control these print queue functions
are explained in detail in this manual.
QMG print processor operations are controlled through PRINT commands
and command qualifiers and switches. Files are printed as the result
of a PRINT command or as the result of a request for a listing or map
from some system task.

.:d'f £~r; :1latelf . . ::· pr·o~ess

..··

,,,:,;·

.'·T~~'.2~:0
.:,.:m•.~.· · :_· ~.t:~.·.:. :.'.·.,~.
lr~; 8m us'. :.:'.~nI;·:T•.a.'.;·.;:.·:·s.·L.:.«.·t0
.

l'l

...••.

~····>.. '..'G.:.'.' ~t9h)::·.3~~~·.,.r
wittiotit.... . tti
'·. . . ,....... .

'.et•.·,.·:.•. '..er.iar··: ...• .ts
.•. :.·,i··.•· ,·:. . .

:··hn•.·
•.
:.:· •. '..·.::_oe:.,.:.;n·.P···.·

U<U-

·•••.•-;:~~~~H'::,':·:·~~]~~~·~~1r

. .

'oll'I.

·t:.em

Each RSX-llM/M-PLUS system is tailored for a particular set of
software applications ~nat must work within the confines of your
installation's hardware system. This manual is a general description
of how batch and queue operations should proceed, but your system
manager may have special information on these processes in your
installation.

INTENDED AUDIENCE
This manual is intended for all RSX-llM/M-PLUS users. The manual has
been particularly designed to meet the needs of users new to operating
systems.
System managers should consult the RSX-llM/M-PLUS System
Guide for information on setting up and running QMG.

Management

STRUCTURE OF THIS DOCUMENT
The manual is organized as follows:
Chapter 1

Introductory material, examples of how to queue
print
jobs
and
batch jobs, and how to get
information on queue contents.

Chapter 2

Details on the PRINT command,
information
on
displaying and modifying both print and batch jobs
in a queue, and writing applications tasks that
spool output.
vii

PREFACE
Chapter 3

Batch job preparation and SUBMIT commands.

Chapter 4

At-a-glance summaries of chapter material.

Appendix A

Explanations of all error messages
for appropriate user actions.

Glossary

Definitions
operations.

terms

used

and
batch

suggestions
and

queue

ASSOCIATED DOCUMENTS
RSX-llM/M-PLUS Command Language Manual
RSX-llM/M-PLUS MCR Operations Manual
RSXllM/M-PLUS System Management Guide

CONVENTIONS USED IN THIS DOCUMENT
DCL and MCR are the two Command Line Interpreters (CL!s) used
manual examples.

the

DCL QMG commands are generally in the following format:
DCL>command/commandqualifier file/filequalifier
The DCL qualifiers either define the
that operation for a file.

operation

(command)

MCR commands, unlike DCL, do not follow one general
The position of command elements a~d parameters
command to another.

command

modify
format.
from o:-lc

DCL is presented as the primary CL! in this manual. When specific DCL
commands or qualifiers are discussed in manual text, they are always
followed by the MCR equivalents.
The RETURN symbol has been omitted from the examples. You can
that every command is terminated by pressing the RETURN key.

assume

A number of conventions are used in the command descriptions in this
manual. With the exception of /qualifier (DCL) and /switch (MCR), the
terms and conventions are the same for both DCL and MCR.
The ellipsis
( • • • ) denotes batch-stream
elements without significance to the point
being discussed.
[

. . .]

Jelem~nt

Any command
optional.

field

enclosed

brackets

Two or more command elements enclosed in braces
indicate
that you must choose one of the
elements when you issue the command.

element n

viii

PREFACE

lowercase

Any command field in
substitute.
Usually
identify what kinds
expected.

/qualifier
(DCL)

Any command element preceded by a slash (/)
is a DCL qualifier: Command qualifiers alter
the action of a command they follow. File
qualifiers modify the action of the command as
it affects that file. If a file qualifier is
used as a command qualifier, it affects all
files in the command line.

/switch
(MCR)

Any command element preceded by a slash (/)
is
an MCR switch. Job switches alter the action
of a command. You can apply a switch directly
to the command or to a command parameter. If a
switch
follows the file, it modifies the
attributes of that file and all other files
that follow in the command line.

parameter

Any required field for a command is called a
parameter. The most common parameters are file
specifications.
Parameters are preceded by
blanks.

filespec

A full file specification includes device, UFD,
file name, file type, and version number, as in
this example:

lowercase must have a
the lowercase word will
of
substitutions
are

DBl: [303,5]MORAN.TXT;2
Full file specifications are rarely needed. If
you do not give a version number the highest
numbered version will be used. Some files may
not have a file type.
Many commands will
accept a wildcard (*) in place of the file
type.
See the command descriptions in the
RSX-llM/RSX-llM-PLUS Command Language Manual.
Red ink

In command examples, commands or other input
that the user types at the terminal are printed
in red. System output is printed in black.
The symbol ~
indicates that you must
press
the
key
labeled
CTRL
while you
simultaneously press another key, for example
CTRL/C, CTRL/Z, CTRL/O.

Shading

Shaded portions of text describe only one
operating system. Gray shading indicates that
the text describes only RSX-llM-PLUS operating
systems.
Pink shading indicates that the text
describes only RSX-llM operating systems.
The
smallest shaded portion of text is a paragraph.
Portions of text that are not shaded describe
both operating systems.

SUMMARY OF TECHNICAL CHANGES

This manual reflects changes and additions to RSX=llM Version 4.0
RSX-llM-PLUS Version 2.0.

and

The following technical changes described in
made to both RSX-llM and RSX-llM-PLUS:

been

user

when

job

this

manual

has

been

have

QMG notifies the
queued.

successfully

Job names can be nine characters.

A new 3-digit job number format replaces the up
job number format.

10-digit

Processors and queues are now named directly for the
For example:

device.

Processor LPO for device LPO
Queue LPO for device LPO

Two new qualifiers (switches) have been added
(PRI) command:

the

SHOW

Three new qualifiers (switches) have been added to
PROCESSOR (QUE /LI:DEV} command:

the

SHOW

/JOBCOUNT:n

(/CO:n)

/[NO]JOB_PAGE

(/[NO]JO)

Four new qualifiers (switches} have been added
QUEUE (QUE/LI) command:
/BRIEF

(/BR}

/FILE

(/LI)

/FULL

{/FU)

/DEVICE

(/LI: DEV)

/DEVICE

(/LI: P)

/INPUT

(/LI: I)

/PRINT

(/LI: P)

SUMMARY OF TECHNICAL CHANGES
8.

Three new qualifiers (switches) have been added
QUEUE (QUE /MOD) command:
/COPIES:n

(/CO:n)

/[NO]DELETE

(/[NO]DE)

/FILE_POSITION

(/FI:n)

Two new qualifiers (switches) have been added to
{QUE /DEL) command:

·.··

/ENTRY:nnn

(/EN :nnn)

/File_POSITION

(/FI :n)

. .

. . . ··

·····

the

SET

DELETE

~ The)T~~SFER (TR).iquaii.:fier

replaces /NOORIGINAL
'/NOTRANSFER (NOTRJ .qualifier ·replaces /()RIGINAL.
-:·The /N<JPRINT
log:file·.

(/NOPR:INJ, qilaliflet

lqnger

spools

iJ'l'Pil;t spgoWJng Js availaple. ~~>r:· !:)Ubrn~tting .Ci, q~~k
: 'o.f c.:}rd·s• :to · a : l'>.at;Ch q9~µ~ ~ .

5~ .. C~rd r~~qe.r

xii

CHAPTER 1
INTRODUCTION TO THE QUEUE MANAGER

This chapter briefly introduces features of the Queue Manager (QMG).
The chapter begins with an explanation of the queue assignments.
Queues are assigned by system managers. You should consult with your
system manager for information on queue
assignments
at
your
installation.
The chapter also gives exampies for queueing print JOOS and displaying
the contents of queues. DCL is presented as the primary CLI in all
examples, followed by the MCR equivalents.
Finally, there
RSX-llM-PLUS.

1.1

brief

introduction

batch

processing

QUEUE MANAGER

The Queue Manager is a system program that provides for the orderly
processing of print and (on RSX-llM-PLUS only) batch jobs. Most
functions of the QMG are transparent.
Every PRINT command, every
SUBMIT command (RSX-llM-PLUS only) , and every request for a spooled
listing or map from a system program is passed automatically to the
QMG.
The QMG then places these requests in the appropriate "queues."
A queue is a waiting line of jobs that are scheduled or processed
according to system or user priorities.
The Queue Manager distributes these jobs out to batch processors, line
printers, or other output devices as the processors become available.
You can check the progress of your job with the SHOW QUEUE commands.
You can delete a job from a queue if you wish, or you can hold the job
in a queue for later processing.
The RSX-llM-PLUS Queue Manager records all its queues in the file
SPO: [l,7]QUEUE.SYS, which is kept on a mass storage disk. This means
that your job will not be lost if the system should be out of
operation for any reason.
Likewise the RSX-llM Queue Manager records its queues in the disk file
LBO: [l,7]QUEUE.SYS.
Of} ~:)X-llM-PLus, . . . Y(>U can S(lb~tJtute. <t:he .•. 1ev~C,e

nalll~ :·.of. : (il'); : outpU:t;

a.~y.f,B~· .· ..·<=p11tpf>1·1~<l·:hY the ·qu~11_e . . ·.f'lg;11~g~i;: · .fc>r.·•··a. :~i;:J.;.~·. ·s;J?:~p.$f ~9a..~.·f <>n . . ~·Pi.af1;~:
. ~Y:-?·~·Er~....t,a.§kJ:frat·.· .·.··creates ..a.n ql.ltJ?:~.t·,fil'.e·~ · Thi-:s;_:is . . s•?lled ····~J:.r~p9_;e.<;l:;17~·F .
._s.pc)oI•irig·.11.· ·

1-1

INTRODUCTION TO THE QUEUE MANAGER
1.2

QUEUE ASSIGNMENTS

You should consult your system manager for information pertaining to
special applications of the Queue Manager at your installation.
Depending upon the needs of your installation, the system manager
chooses the number of queues to be set up and where the output of
these queues will be directed.
Your installation may have certain printers designated to receive
output for special hardcopy forms (such as numbered invoices or
inventory forms). A listing of these forms and their designated
output devices will be helpful to you in your understanding of the
information contained in this manual. Your system manager can supply
you with a list of these special forms and their corresponding
devices.
A single queue can be assigned to one or more devices or to no
devices.
A single device may have one or more queues assigned to it
or no queues. Figure 1-1 shows some of the possible assignments of
queues to devices.

Processors

Queues

LPO

Devices

LPO

I PO:

DCL>PRINT /QUEUE:queuename
MCR>PRI queuename:
LP1
LP1

LP1:

TT3

TT3:
ZK-238-81

Figure 1-1

Queue Assignments to Output Devices

The /QUEUE:queuename qualifier (queuename:=} to the PRINT command
directs output to the designated queue. When you do not specify a
particular queue in the PRINT command, output goes into the default
queue PRINT. In Figure 1-1 the PRINT queue sends output to one of two
printers. The printers are also served by their device-specific
queues.
The queue CHECKS has not been assigned to any output device.
Jobs can be placed in this queue, but they will not be taken out of
1-2

INTRODUCTION TO THE QUEUE MANAGER
the queue until it is assigned to an output device by the system
manager. The queue JIMBO and TT3 are both assigned to the same output
device.
The same functionality applies for batch queues and batch processors
on RSX-llM-PLUS systems. In this case, the default queue is BATCH.
When a line printer or other output device is under control of the
Queue Manager, it is said to be a spooled device. Spooled devices
have been initialized with certain attributes. These attributes are
defined by the PRINT command qualifiers. Figure 1-2 illustrates the
way the Queue Manager handles PRINT commands specifying printers with
certain attributes~

1.3

PRINT COMMAND

The Queue Manager handles the orderly printing of files for an
RSX-llM/RSX-llM-PLUS system through software tasks called despoolers
or print processors. There is a print processor for every spooled
line printer on the system. Even if the system does not have a line
printer, it will have some device designated as the system output
device.
Your system may have as many as 15 output devices to which
the Queue Manager directs output.
This output includes all requests to system tasks for maps or listings
and print jobs entered through the PRINT command, as well as output
from applications tasks unique to your installation.
On RSX-llM-PLUS, the output could also include logs from batch jobs.
A line printer and its associated processor are
simply as a "printer."
The PRINT command supplies most
example:

entries

the

usually

referred

queue.

For

DCL>PRINT/LOWER/AFTER:(14:00) ERIKA.TXT/COPIES:3
MCR>PRI /LOWER/AF:14:00=ERIKA.TXT/COP:3
This command queues a QMG print job that prints three copies of the
file ERIKA.TXT on a line printer with lowercase characters after 2
P.M. today. The QMG print job has the name ERIKA, which is also the
name of the first file in the job.
Here is an example of a PRINT command naming several files:
DCL>PRINT/NAME:MORAN/FLAG_PAGE KIRSTEN.TXT JOHANNA,ERIKA
MCR>PRI MORAN/FL=KIRSTEN.TXT JOHANNA,ERIKA
These files are queued together as one QMG print
job.
The.
/NAME:jobname qualifier (jobname) gives the print job the name MORAN.
The QMG accepts jobnames up to nine characters in length (the limit
for filenames).
The files are printed in the order listed, on the
same line printer, and without interruption. The /FLAG PAGE qualifier
(/FL) means that each file is separated by a flag page bearing the
name of the file. These file flag pages are in addition to the job
flag pages that bear the name of the job and that appear at the
beginning of the job output.

1-3

INTRODUCTION TO THE QUEUE MANAGER

The Queue Manager controls line printers through output processor tasks which "own" the devices. Often the line
printer and its associated processor are referred to collectively as "the printer." The printer hardware and software
were brought together in the Queue Manager, when your system manager "initialized" the queues.
Initialization established the characteristics of the printer. You can then specify printers with those characteristics
using the PRINT command.
Default qualifiers to the PRINT command also determine which printer will handle a print job. The following examples illustrate the interaction between the PRINT command and the printers.

Q"e"~

Printer
Software

PRINT
{

---L""'P"'O_ _..

{

LPO

LP1

DCL>INITIALIZE/PROCESSOR
Processor? LPO/UPPERCASE/FORMS:1 /FLAG_PAGE:O

LP1

• Full character set
• Line printer paper

• Only uppercase characters
• Short invoice paper

Hardware

LPO:

DCL>INITIALIZE/PROCESSOR
Processor? LP1 /LOWERCASE/FORMS:O/FLAG_PAGE:2

LP1:

The printer software is set up through the INITIALIZE/PROCESSOR command. Printer LPO: has no lowercase
characters; it is initialized with the /UPPERCASE qualifier. The printer is loaded with a special form used in the
installation, short invoice paper. The printer is initialized with the /FORMS:1 qualifier. The system manager has
previously defined FORMS:1 for the width and length of the invoice paper. The printer is initialized /FLAG_PAGE:O
because the invoices are numbered. Print jobs are printed on the invoice forms. Therefore, no flag pages should be
printed on the invoice forms.
Printer LP1: has the full character set and is loaded with standard line-printer paper. Since system output and text
fiies go to this prinier, iin:~ µrirH~r· is if1itiaiiz~u witl1 tl1e /FLAG_PAGE:2 quaHfier, so that any rne ptiiit~d Oil the

printer will be identified by a flag page.
ZK-23911-81

Fig:Jre 1-2

How the PRINT Command Is Processed

1-4

INTRODUCTION TO THE QUEUE MANAGER

DCL>PRINT JPAUL.TXT
MCR>PRI JPAUL.TXT - - - - - - - - -

(
~

Queues

LPO

LP1

Printer
Software

{I---.

DCL >INITIALIZE/PROCESSOR
Processor? LPO/UPPERCASE/LP--o FORMS:1 /FLAG_PAGE:O

l UJ
f

""'dwa"

! LPOo'

•

LP1

DCL >INITIALIZE/PROCESSOR
Processor? LP1 iLOWERCASEiFORMS:O/FLAG_PAGE:2

•
•

Only uppercase characters

Full character set
Line printer paper

• Short '"'oioe pape•
LP1:

The PRINT command specifies no queue, so the job goes into the default queue PRINT. Since the default /FORMS
qualifier (/FO:) is /FORMS:O (/FO:O), the job goes from the PRINT queue to processor LP1 and thence to device LP1:
to be printed.
DCL>PRINTIFORMS:1 INVOICE.CHK - - - -.....
MCR>PRI /F0:1 . INVOICE.CHK

Q"e"e'

{

___L_,P,.o_ __.

Printer
Software

{

LPO

LP1

DCL >INITIALIZE/PROCESSOR
Processor? LPO/UPPERCASE/FORMS:1 /FLAG_PAGE:O

LP1

DCL >INITIALIZE/PROCESSOR
Processor? LP1 /LOWERCASE/FORMS:O/FLAG_PAGE:2

I
Hardware

f[[J
-----l

•
•

• Only uppercase ch.aracters
• Short invoice paper

LP 0:

Full character set
Line printer paper

LP1:

The PRINT command specifies no queue so the job goes into the default queue PRINT. Since the /FORMS qualifier
(/FO:) is /FORMS:1 (/F0:1 ). the job goes from the PRINT queue to processor LPO and thence to device LPO: to be
printed.
ZK-23912-81

Figure 1-2 (Cont.)

How the PRINT Command Is Processed

1-5

INTRODUCTION TO THE QUEUE MANAGER

DCL>PRINT /DEVICE:LP1 :/FORMS:2 CHECK.PAY
MCR>PRI LP1:/F0:2=CHECKS.PAY
-----------

O••••• {

LPO

Printer
Software

LPO

{

LP1

DCL>INITIALIZE/PROCESSOR
Processor? LPO/UPPERCASE/FORMS:1/FLAG_PAGE:O

LP1

DCL>INITIALIZE/PROCESSOR
Processor? LP1 /LOWERCASE/FORMS:O/FLAG_PAGE:2

• Full character set
• Line printer paper

• Only uppercase characters
• Short invoice paper

LP1:

The PRiNT command specified u~vice LPI, so the job goes to the device-specific queue Lr~. The PR~NT command
specified the /FORMS:2 qualifier (/F0:2), however, so the job will not be printed until LP1 is reinitialized to
/FORMS:2 (IF0:2). In addition, the paper in the machine must be changed.
DCL>PRINT/LOWERCASE INVOICE BKS
MCR>PRI ILOW~INVOICE BKS
~

""""". l

Printer
Software

r
1

,~~

LPO

...

-._....no-1~1-;-

DCL >INITIALIZE/PROCESSOR
Processor? LPO/UPPERCASE/FORMS:1 /FLAG_PAGE:O

LP1

DCL>INITIALIZE/PROCESSOR
Processor? LP1 /LOWERCASE/FORMS:O/FLAG_PAGE:2

•
•

• Only uppercase characters
• Short invoiGe paper

Hardware

LPO:

Full character set
Line printer paper

LP1:

The PRINT command specified no queue, so the job goes to the default queue PRINT. The /FORMS qualifier (IFO:)
is /FORMS:O (IFO:O) by default. The user specified a printer initialized with the /LOWERCASE qualifier (/LOW), so
the job goes to processor LP1 and thence to device LP1 to be printed.
You should note that initialization with the /LOWERCASE qualifier (/LOW) does not necessarily mean that the device
itself has the lowercase character set. In most cases, it has. but in emergencies, devices without the lowercase
character set may be initiaiized wiih ihe ii...OWERCASE qualifier (/LOW) so that jobs whosa PRiNT commands
included the /LOWERCASE qualifier (/LOW) will not be blocked in their queues.
ZK-23913-81

E. igure 1-2 (Cont.}

Row the ?RINT Command Is i?rocessed

1-6

INTRODUCTION TO THE QUEUE MANAGER

systems

1.4.1

SUBMIT Command Example

Batch jobs are entered in batch queues through thB SUBMIT command.
Each SUBMIT command defines a QMG batch job consisting of one or more
user batch jobs.

1-7

INTRODUCTION TO THE QUEUE MANAGER

A user batch job must log itself in, issue commands, and log itself
out.
However, LOGIN (HELLO) and LOGOUT (BYE) are replaced in batch
jobs ,by JOB and EOJ, respectively.

1-8

INTRODUCTION TO THE QUEUE MANAGER
1.5

SHOW QUEUE (QUE /LIST) COMMAND

The SHOW QUEUE command displays information about print and
(in the
case of RSX-llM-PLUS systems)
batch queues.
These commands are
discussed in detail in Section 3.4.1.
However, the most useful form
of the command, and its output, are described briefly in the following
sections.

1.5.1

SHOW QUEUE - QUE /LI

The SHOW QUEUE (QUE /List) command lists all jobs in all queues.
On RSX-llM systems this command lists the print queues.
On RSX-llM-PLUS systems
queues.

this

command

lists

Type one of the following commands on your
RETURN key.

both

and

batch

terminal,

and

press

the

will

similar

DCL> SHOW QUEUE
MCR> QUE /LI
The information you see on your
information in Example 1-1.

terminal

1-9

the

INTRODUCTION TO THE QUEUE MANAGER
Example 1-1

0
** I pi:;:INT
1J.UEUES **
NT
l... POfJ
Pl~:

:::::>

[7,40::1

SHOW QUEUE Display

ACT I lJE ON 1...PO

GEF:IKf.l ENTf;:y: :I.

1 DB7![7~40::1JOHANNA.ASD;1
HEAD
ENTRY:8
1 DB7:r7,40::1HEAD.AKE;1

COP:3

FOF~M: 2

[7,40]

JOB1
ENTRY!3
1 DB7![7,40::1MOUTH.WSH;1
. .JOB2
ENTl~Y i. 4

[7Y40]

JOB3

[7,40]
!...PO

:::::>

1...PO

[}y4()]

ENTRY:5
1 DB7:C7,40JMOUTH.WSH;1
JOB4
ENTRY!6

[7Y40J

HFl...D

PRINT AFTER 23-FFB-83 22:00

1 DB7![7,40JMOUTH.WSH;1
1...P 1

::::>

l...P 1
HEARTBURN ENTRY:2
1 DB7:[7,40Jl...IT.MAC;1

[7,40::1

r·1.. r.ii: ...I , •+ 1·.. 7. •. 4 i'J~ ."] F:· 1·.,"\ F.:·... INc·:.. 1-1 • 1::· 1:;·"
·1
, T. "
¥ •.

A
~ ':)
•..

{

3 DB7:C7140JAPPl...E.PIE;1
[7140::1
Y
ENTRY:"?
1 DB7![J,40JY.ME;1
BATCH QUEUES

** TC:H
B1~

1~CTIVE

:::::>

ON 1...Pl

CClPt2

Bt1PO

>
ZK-240-81

The circled numbers
t.P.rmin.i=\l

identify

rP~11l t

of n

those

SHOW QIJF.IJF.

elements

that

(QtlF.

~0mm~nn_

/T. T)

appear

Th~

your

~l~~~~t~

are interpreted as follows:

Shows a print queue or (for RSX-llM-PLUS systems) a batch
queue header. This header indicates that the information it
precedes is either for a print queue or batch queue.

Shows the queue and the spooled devices or batch
assigned to it.
Shows the u~c of ~ne job. A privileged
different UIC from the login UIC.

user

Shows the QMG print job name. The name may be
one to nine alphanumeric characters.

processors
may

have

composed

Shows the job entry number (the range is 1 through 999).
The QMG assigned this number when it placed the job in
queue.
Shows the form number for the printer on which the job is to
be printed.

Shows the queue status of a job.
or BLOCKED UNTIL (time blocked).

A job may be ACTIVE, HELD,

Shows the entrv order of the file in a job and its full file
specification.~

Shows the number of copies of a file to be printed within
-.-..

·-

--.. . - ..

-..

,Pd J. •~ J. 1_; U. .L d L

J-~ 0--.. '--l,J ~

1-10

CHAPTER 2
QUEUING JOBS

The Queue Manager (QMG) is a system task that distributes jobs to
output devices or batch processors. Passing jobs to the Queue Manager
is called "queuing jobs." When the Queue Manager releases jobs for
processing, it is called "dequeuing jobs."
The Queue Manager distributes jobs queued by user tasks, by system
tasks that output listings such as MACRO listings or task builder
maps, and jobs queued by the PRINT command.

·::i~l Fi.... ·.~.!.ft~~·~.~~~$··.::;.~~~~ms·,i·.:tffe..· ®ea~ ·r.ici•l'la·g~f<:•·als~<>: . · ~~st:rft>,#t:es•)·Jof)s .... ~ 9
::::·~~~ch:-·.• :f?fce>c7~~<i>f~."·····.··.:.· T~E!s:/ J.l~er.·. i·.ba·t::qn:··. jQb.~·.·.~··~·~.·. ·.··~µE:!uecl•·.~y<t.~t··~HBfl-1~.·'l'
·:::c9 .•.
·11:~:::.~r:r~"'~·~.~ •.•.·.s.C1~J~~1 "~~: . • ·t>·p.rtcr1l: :.·J<:>t>~· ~ . ~·.··.·Qt-1:~··.• ·t>~"t:ch ;.j.·qb•·· .·.•·.• ~·~···· ci·:;<::·t-tci.·~··.9.·.·•.·.·:·.·?·f
:.;-~•9~•., .•. :9<·.:·~p·t-e . . . •.·.··Y~r'r:·.·£.a,·t::·s~··.·.·.5?·~~.·. Jt·?i. ~:r Pfpc.~s$E!a .••: ·:r.tie: . •. §tJBfv1I:'l'·. commari.9· .

. ·.

.;i·:i.~P~Stf 'tit~§·: . .~.: ..~~- . R~:~-s.l't<·.j:R;l,:)';: J:9·~~,..S.t"i~p~·~r<.~.J . ~ •. · .

.·.· ;. .

Once jobs are in queues, you can display queue information with the
SHOW QUEUE (QUE /LI) command. You can alter the status of jobs in
queues with the SET QUEUE (QUE /MOD) command. You can hold jobs in
queues with the HOLD/JOB (QUE /HO) command or release them from queues
with the RELEASE/JOB (QUE/REL) command.
All these aspects of using the Queue Manager, including writing
that spool output, are discussed in this chapter.

2.1

tasks

SPOOLING OUTPUT

A spooled output device is the hardware device plus its processor.
Spool is an acronym for Shared Peripheral Operations On Line.
Spooling refers to the process of sending output to a peripheral
device, such as a line printer, in an orderly fashion.
Output
requests are gathered into queues and then these requests are
"dequeued" in a serial manner. The spooled device services only one
request at a time.
The most common output device for the Queue Manager is a line printer.
Most RSX-llM/llM-PLUS systems will have a line printer or some other
device designated as the system output device that assumes the role of
the line printer.
(:)n: RSX-llMv-PLUS,, you can substitute the deviCe name of a spooled
output device for the output file specification in any system task or
use:r:""'written task that creates an output file.
This is called
t.I".Cin~par~nt spooling.
'!'bus, the following .commands are legal and wil1
que:ue fi le.s to an output device:

DCL>COPY MORAN.MAC LPO:
MCR>PI P LPO: =MORAN. MAC
2-1

QUEUING JOBS

When you successfully submit a job for queuing with either the QMG
PRINT or SUBMIT command, you will receive a submission notification
message on your terminal. For example:
DCL>PRINT MORAN.DMP
MCR>PRI MORAN.DMP
The following message will appear:
PRI-JOB 123, name "MORAN

" submitted to queue "PRINT "

PRI

Indicates that the job was submitted by the PRINT command.
If you use the SUBMIT command, SUB will take the place of
PRI.

123

The unique job entry number given

the

job

through

999) •

MORAN

The name of your job. Jobnames can be up to nine characters
in length.
If you do not specify a jobname, the jobname
will be derived from the first file name in your job.

The queue into which the job is submitted.

2.2

PRINT COMMAND

The PRINT {PRI) command queues files for printing on a line printer.
More specifically, the output you desire to be printed on a line
printer is first placed into a waiting line by the Queue Manager
(QMG).
QMG places the print job into the waiting line according to
the job's print status.
Status is determined by PRINT command
qualifiers and switches described in this section.
The PRINT command can also be used to queue jobs for other output
devices and applications processors. These jobs are referred to as
"print" jobs even if they do not involve any hardware printing.
The PRINT command gives you control over how, when, and where your job
will be printed through the use of PRINT command qualifiers and
switches.

2-2

QUEUING JOBS
Format
DCL>PRINT[/commandqualifier[s]]

filespec[s] [/filequalifier[s]]

MCR>PRI [ [queuename:] [jobname] [/jobswi tch] =] filespec [s] [/fileswi tch [s]]
DCL Command Qualifiers

MCR Job Switches

/JOBCOUNT:n

/CO:n

/QUEUE:queuename

queuename:

/UPPERCASE

/NO LOW

/LOWERCASE

/LOW

/[NO]HOLD

/[NO]HO

/PAGE_COUNT:n

/PA:n

/NAME:jobname

jobname=

/PRIORITY:n

/PRIO:n

/FORM:n

/FO:n

/LENGTH:n

/LE:n

/[NO]RESTART

/[NO]RES

/[NO]FLAG_PAGE

/[NO]FL

/AFTER:(dd-mm-yy hh:mm)

/AF:hh:mm:dd-mmm-yy

/DEVICE:ddnn:

queuename:

/[NO]JOBPAGE

/NOJO

DCL File Qualifiers

MCR File Switches

/[NO]DELETE

/[NO]DE

/COPIES:n

/CO:n

/[NO]TRANSFER (RSX-llM-PLUS Only)

/[NO]TR (RSX-llM-PLUS Only)

Parameter
filespec[s]
Specifies the file(s}

to be printed.

Separate multiple filespecs with commas.
You can use wildcards
(*)
in the UFD and file name, type, and version fields of the
f ilespec.
If your filespec includes no file type, the default file type
.LST.

2-3

QUEUING JOBS
Command Qualifiers (DCL) and Job Switches (MCR)
/JOBCOUNT:n
/CO:n
Specifies the number of copies (n) of the print job. A QMG print
job is made up of one or more files that are printed in the order
they were listed.
NOTE
/JOBCOUNT:n (/CO:n) is a qualifier to the QMG PRINT
command. Do not confuse it with the /COPIES:n qualifier,
(/CO:n) which is a qualifier to the file(s) contained
inside a QMG print job.
/QUEUE:queuename
queuename:=
Specifies the name of the print queue in which the job is
placed. The default is the PRINT queue.

/UPPERCASE
/NO LOW
Specifies that the print job can be sent to a line printer
initialized without the lowercase character set. This is the
default.
/LOWERCASE
/LOW
Specifies that the print job must be sent to
initialized with the lowercase character set.

line

printer

/[NO]HOLD
/[NO]HO
Specifies that the job be held in its queue and is therefore not
eligible for printing. You can release the job with RELEASE/JOB
(QUE/RE). See Section 2.8.2 •
./n"",....r.'I

/ r.M.\.:11:.1

rtl""\TT'IHm--

\..VUL'I .l ; 11

/PA:nSets the limit on the number of pages a
range is 1 through 65535.

job

may

produce.

The

Without this qualifier, the number of pages is unlimited (n=O).
/NAME: j obname
jobname=
Specifies a job name for the print job.
to nine alphanumeric characters.

The job name can

If you specify a job name, that name appears on the flag page at
the beginning of the printed output. Otherwise, the name of the
first file in the iob is the job name.

2-4

QUEUING JOBS
/PRIORITY: n
/PRIO:n
Sets the queue priority of the print job.
For nonprivileged
users, n can be from 0 through 150. Privileged users can set n
up through 250. The default is 50.
The Queue Manager runs the highest-priority job first.
If two
jobs have the same priority, the job that has been waiting longer
runs first.
/FORMS:n
/FO:n
Specifies the type of form that the job is to be printed on. The
value of n can be from 0 through 255. Default is O. See your
system manager for details on how to specify the particular forms
used at your installation.
/LENGTH:n
/LE:n
Sets the length of a logical page; n can be any number from 0 to
255.
The default is O. If you set a length, a form feed will be
automatically generated if one is not found within n lines.
This qualifier has no effect on how the printer handles form-feed
characters.
A form feed still moves the printer to the top of
the next physical form, such as the perforation in a sheet of
line-printer paper.
This qualifier simply adds the requirement
that the printer move to the top of the next physical page if no
form-feed character is encountered within n lines.
When you set the length at 0 (the default), no form feeds will be
inserted ..
/[NO]RESTART
/[NO]RES
Controls requeuing of your job if it is stopped or aborted
being processed.

while

If /RESTART (/RES) is specified, your job will start
the beginning if it is stopped or aborted.

from

again

/NORESTART (/NORES) is the default. If the printer is stopped
while your job is active, the job will pick up where it left off
when the printer is started.
In neither case will you be missing any of your job,
/RESTART (/RES) your job will be all in one piece.

but

with

/[NO]FLAG_PAGE
I r"t.Tf'\ 1 1"T

/LnVJ"'..,

Adds flag pages before each file in your print job.
is /NOFLAG_PAGE (/NOFL).

The

default

With /NOFLAG PAGE (/NOFL), your job is still preceded by a job
flag page, but the files in the job are printed without any file
flag page.
(See /[NO]JOB_PAGE.)

2-5

QUEUING JOBS
/AFTER:

(dd-mmm-yy hh:mm)
(mm/dd/yy hh:mm)
/AF:hh:mm:dd-mmm-yy
Blocks the job until after the specified time. Depending on the
print queues at that time, your job may be run immediately or
later when its turn comes up in the queue.
The time and date are in the same format as the format
by the SET TIME (DCL) and TIM (MCR) commands.
If you do not specify /AFTER
eligible for printing.

(/AF),

your

job

generated
immediately

/DEVICE:ddnn:
queuename:
Specifies the device on which you want your output to appear.
The default is the device or devices served by the PRINT queue.
(/DEVICE is a DCL synonym for /QUEUE.)
/[NO]JOB PAGE
/[NO]JO Controls the printing of a job flag page before the
default is /JOB_PAGE (/JO).
(See /[NO]FLAG_PAGE.)

job.

The

File Qualifiers {DCL) and File Switches {MCR)
If you specify a file qualifier as a command qualifier in DCL,
that attribute applies to all files. You can, however, override
that attribute for a specific file by using the qualifier as a
file qualifier.
On systems using MCR, any file specifications that follow a file
specification that is altered by a switch will {by default) be
altered as well. In the following example, you would have to use
the /CO:l switch after JPAUL if you did not want four copies
printed:
DCL>PRINT JOHANNA.TXT,KIRSTEN/COPIES:4,JPAUL,DAD.MEE
MCR>PRI =JOHANNA.TXT,KIRSTEN/C0:4,JPAUL/CO:l,DAD.MEE
/COPIES:n
/CO:n
Sets the number of copies for a particular file in
default is one copy.

job.

The

default

/[NO]DELETE
/[NO]DE
Deletes the
/NODELETE.

files

after

they

are

printed.

The

/[NO]TRANSFER {RSX-llM-PLUS only}
/[NO]TR
(RSX-llM-PLUS only}
Allows the copying of a file from a private device.
is /TRANSFER.

2-6

The

default

QUEUING JOBS
Examples
The following PRINT command examples appear in both DCL
syntax:
1.

and

MCR

DCL>PRINT JOHANNA.TXT
MCR>PRI JOHANNA.TXT

This example prints the most recent version of JOHANNA.TXT on the
line printer.
2.

DCL>PRINT/NOJOB_PAGE KIRSTEN.TXT
MCR>PRI /NOJO=KIRSTEN.TXT

This example prints KIRSTEN.TXT without a job flag page.
3.

DCL>PRINT/JOBCOUNT:4 JOHANNA.TXT
MCR>PRI /C0:4=JOHANNA.TXT

This example prints four copies of the print job JOHANNA, each
containing one copy of the file JOHANNA.TXT. They are printed
end-to-end with a job flag page preceding each printed copy.
4.

DCL>PRINT/JOBCOUNT:4/FLAG_PAGE KIRSTEN.TXT
MCR>PRI /C0:4/FL=KIRSTEN.TXT

This example prints four copies of the print job KIRSTEN, each
containing one copy of the file KIRSTEN.TXT preceded by a job
flag page and a file flag page.
5.

DCL>PRINT/FLAG_PAGE JOHANNA.TXT,KIRSTEN.TXT,JIMBO.TXT
MCR>PRI /FL=JOHANNA.TXT,KIRSTEN.TXT,JIMBO.TXT

This example prints one copy of each file,
file flag page.
6.

each

preceded

DCL>PRINT/NAME:FATHER/FLAG_PAGE JOHANNA.TXT,KIRSTEN.TXT,JPAUL.TXT,ERIKA.TXT
MCR>PRI FATHER=JOHANNA.TXT,KIRSTEN.TXT,JPAUL.TXT,ERIKA.TXT

This example prints one copy of each file preceded by a file flag
page and gives the name FATHER to the job as a whole. The name
FATHER appears on the job flag page.
7.

DCL>PRINT/LENGTH:55 DAD.MAC
MCR>PRI /LE:55=DAD.MAC

This example prints a single copy of the source program file
DAD.MAC.
This source program file does not contain form-feed
characters. To avoid printing over the perforations, the user
has specified a logical printed page length of 55 lines. Each
time 55 lines are printed, the logical page is complete and the
printer moves to the top of the next physical page.
If you specify a file with form feeds in it, the printer would
move to the top of a physical page each time it encountered a
form feed and each time it printed 55 lines before encountering a
form feed.

2-7

QUEUING JOBS
8.

DCL>PRINT/JOBCOUNT:4

JIMBO.DOC~MOUTH.DOC,QUACK.DOC

MCR>PRI /C0:4=JIMBO.DOC,MOUTH.DOC,QUACK.DOC
This example prints the QMG print job four times.
Each copy of
the print job contains one copy of the file JIMBO.DOC, one copy
of the file MOUTH.DOC, and one copy of the file QUACK.DOC.

DCL>PRINT/JOBCOUNT:3 LIT.MAC,FRENCH.FRY,APPLE.PIE/COPIES:2,MOUTH.WSH
MCR>PRI /C0:3•LIT.MAC,FRENCH.FRY,APPLE.PIE/C0:2,MOUTH.WSH/CO:l

This example prints three copies of the print job named LIT.
Each copy of the print job contains one copy of the file LIT.MAC
and FRENCH.FRY, two copies of the file APPLE.PIE, and one copy of
the file MOUTH.WSH.
Note the difference between the /JOBCOUNT:3 qualifier (/C0:3)
to
the print command and the /COPIES:2 qualifier (/C0:2) to the file
APPLE.PIE.
If you are using DCL as
your
command
line
interpreter,
the difference between /JOBCOUNT:n and /COPIES:n is
easy to see.
If you are using MCR as your command line interpreter the
differences between the two /CO:n switches may not appear so
distinct to you. When you use /CO:n as a switch to the PRINT
command, you are instructing the Queue Manager to print n copies
of the print job as separate print jobs. When you use /CO:n as a
switch to a
filespec,
contained within a print job, you are
instructing the Queue Manager to print n copies of that file
end-to-end within that print job.
10.

DCL>PRINT/NAME:SAILOR/JOBCOUNT:2/DELETE JIMBO.DOC,MOUTH/COPIES:3,QUACK
MCR>PRI SAILOR/C0:2=JIMBO.DOC/DE,MOUTH/C0:3,QUACK/CO:l

The QMG print job has the name SAILOR and is printed two times.
Each of the two printed listings contains one copy of the file
JIMBO.DOC, three copies of the file MOUTH.DOC, and one copy of
the file QUACK.DOC.
All
the files are deleted after they are
printed.
Again note the difference between the /JOBCOUNT:2 qualifier
(/C0:2)
to the PRINT command and the /COPIES:3 qualifier (/C0:3)
to the file MOUTH.DOC.
11.

DCL>PRINT/AFTER:(12:15 10-AUG-83) JIMBO.TXT
MCR>PRI /AF:12:15:10-AUG-83=JIMBO.TXT

This example blocks the job in queue until the specified date and
time.
12.

DCL>PRINT/AFTER:(10:30) KIRSTEN.TXT
MCR>PRI /AF:l0:30=KIRSTEN.TXT

This example blocks the job in queue until 10:30 on the date the
PRINT command was entered.
If you entered this command at any
time after 10:30, the job KIRSTEN would have been immediately
eligible for printing.

2-8

QUEUING JOBS
13.

DCL>PRINT DXO: [303,14]KIRSTEN.TXT
MCR>PRI DXO: [303,14]KIRSTEN.TXT

:9tf,J~$x ... +•J.,r~f-PLJ.I~,i·,y91i•:··:cail·\prg~:t lobs· ;.•_i'.t<?n{·.·~···••.••·I>r.iy.~t.e. :a·evlce·

:•t:fre. "lfWR~N$E'.l!;~t '.~V!iJ;qlj{

4$~I19,.·:

The /TR~NSE'ER: quRTifieI" :l/lf'R) •clCle!;·> •• p()t • . • :.11aye···.·.·· te> <·• 6e········ ~peq·iifi#a;::
.:l'JTC::.~µ~T· •. •.• .•. t~ .·• .,i'f;· • .• ~ljT··•i q~ifiJ{l~H•. . . . . .!rhe •.J>~ix~~ely•••··~·ht9.c.iiteq.•,aeytc~•··}')i{~·=:r<
f•~·•·••llioµnt~<,l·.•!1·it;t1.· ii:Y?~ume ·q<>:11t<i;.ining.••'.t~·T••· file•.····KIR.~T~l'l•'r){T~ . . ·.· · ·13e·~~'.I"e/:
t~.t;~ . . . f.i.Ie.·······.:.i~··••·· .p(iri.t:ed.···•·::OI)..:.•c:(•••·lin:e· :l?F~:Il,·~~rr••.·•it:· .. ·is '9?B~~q···t9: .~·~£:i.:•
"·P~eP<ie>::a.evice•<·s;e:. •·· ..•.. :.??t1e.17ecf<:>t"e,·•··.~he. •yq.±ull.le. n:taY:.f>e •. . ;.dis~ot),l'l.i:e<l .•·· .~r1~: . ;
.•• t};)~ i: Cf·~·yi.q·e.. : •. cle~:l..·+g~·~t:e?····> i:>:~{e>pe.••·. . .• ·the . • :f i:l~:. i~•· 'EI"~fl~ed. -prt •. 1:~$···J. ~n.e:.···
:pr:inter ~· .· . ··.The·:. .·.·.f:ile:. will> remain.·. on·:• ·the•··d ismounted•··• volume ·:Out'': wi1Ji<

· iJ\f~.9~~.t . ~.#~t ~(r·: •. ~:f=u ;q~~ ~-t~~ ;:~;i~~, ,,;§·5.;,,t:+ ~:Y.l_:: ~f~~it: :Pr:~ri~ *-ni ~:.::: ....
14.

·· ·· ···...

DCL>PRINT/NOTRANSFER DXO: [303,i4jKIRSTEN.TXT
MCR>PRI=DXO: [303,14]KIRSTEN.TXT/NOTR

·I:~··J¥i~:,':~*ari1~~:~.~;:·t:t~~fU't

::·fs:.:.-'~9-~:.·::~:9p~e~··•· ~g_..,>tl'•.·•··• · p~e\.lqq•• -~~y-ip,ei~ '.

\tJiere·fo.re ·.' ·t:fi:g" :·y:o·!tijn.¢:. . ;g·t;:·: r·e.in.;:i;in<I110.unted ·\1rrt::·t1:,··the.' pri.ri,t:~ ·j·<>'b!'.i_~>
··s: 0 1nPl~.'t~9.}.

". ... ;.

Notes
Once your job is in a queue, you can modify some
with SET QUEUE (QUEUE /MOD). See Section 2.7.

job

attributes

The /LOWERCASE (/LOW) and /UPPERCASE (/NOLOW) qualifiers have no
effect on the nature of your output. They do not cause your job
to be printed in uppercase or lowercase.
Specifying /LOWERCASE
(/LOW) means that a printer with the lowercase attribute must be
used. Specifying /UPPERCASE (NOLOW) means that the printer need
not (but may) have the lowercase attribute.
Despite your setting of the /[NO]RESTART qualifier (/[NO]RES)
your system manager may restart your job by commands to the Queue
Manager over which you have no control. See the RSX-llM/M-PLUS
System Management Guide.
The job flag pages and the file flag pages have different
formats.
The job flag page shows the UIC the PRINT command was
issued under on the first line (or the user name on RSX-llM-PLUS
systems with CPU accounting) and a nine-character job name
derived from an explicit job name or the file name of the first
file in the job. The file flag page shows the file name on the
first line and the file type and version number on the second
line.

2-9

QUEUING JOBS
The /JOBCOUNT:n qualifier (/CO:n) to the QMG PRINT command
specifies the number of copies of the job to be printed. You
should not confuse this job qualifier with the /COPIES:n file
qualifier (/CO:n).
A QMG print job is made up of one or more
files. If you desire to print two or more copies of a file
contained in a single QMG print job, you would use the /COPIES:n
file qualifier (/CO:n).

'.1:¥. ::_:.y<:)~, ·~#.~hF{t~#~<

.·~~:~.~.~,

.· ti~'litie~r:·'c/NoifR)''.:';y61J<>' ·j:/:·:.

:::v.01· ume·>'., 1nol:li1t ed···· ..

··1 ..::·· . #11 ii .:·y'"#outrin.ff·flsi:il·oeibsi

ia,sr·•••e.~i~cf ip~r1•·ie.' a· i ~· ;

"·d.'~)~#.'p.¥·t·.. ',;i~sW~~~~~·~~':: :..<.t:;r,;ft>·i . /· . i
<. •.·.· · .·.·.•.·.. < i ·.•· . . i..·.· · •· · · ·.· ·.·.
.19:c,c;t.•t.ro,·11. ··>······~~.r1~·:.:c·.?l'.l~•·•··:.'(?·t()<Il.l111~.·•·•·Fi~J1····t>,e····c1:'i·$JJ19.~.111~r~~··'·.··:i'ft"·'••¥Ji~·r.·99,:'-~,·
-~¥R:·~;:r·:·•.",f~i~'t~-~>".•·r«' . :·~7: ·~:FG7~~i·~J..e.i...t~.•p:tn~:r'· '~Y*;?~~····.··~'7 7 r·~:i/o;r• .·*;Ti'.
:'.'nP:>$P~i~:e: ...;Qti>··,,9·P::·~..·,:µ;~~· .. J:i.l;l~:;:/NQ'I'R/\:NrSl?;F?~:;;o··c~;Q~'R,). . . :.'.i;iti~(J.:;i'.f:.fi~r:. :;:,·
i.•········

. . -. <··

no·

<····.··....

~f~~:~~~~~~l~~i~R~t~~()·~~~~~~~f~~lr~cr10~~~1~~irI1~~~.~~M0

2.3

DELETE COMMAND

The DELETE command is used to delete jobs from a queue or files from a
job.
Formats
DCL>DELETE/ENTRY:nnn[/FILE_POSITION:n]
DCL>DELETE/JOB queuename, jobname[/FILE_POSITION:n]
MCR>QUE /EN:nnn[/FI:n]/DEL
MCR>QUE

queuename~jobname[/F!~n]/DEL

These commands allow the deletion of a job in queue by specifying
either the job's entry number or job name. You can also delete a
single file in a job by specifying the /FILE_POSITION:n qualifier
(/FI:n).
Parameters
queuename
Specifies the name of the queue containing the job
delete.

you

wish

HELD

jobname
Identifies a job to be deleted from the specified queue.
The same job name may appear in a queue more than once.
ACTIVE jobs will be deleted before WAITING jobs.
/ENTRY:nnn
/EN:nnn
Deletes a queue entry by number.
The number is unique.
entry number replaces both the queue name and the job name.

2-10

The

QUEUING JOBS
/FILE POSITION:n
/FI:nIdentifies the file by the file's position in the job.
Examples
1.

DCL>DELETE/ENTRY:301
MCR>QUE /EN:301/DEL

This command deletes the job from queue by referencing the job's
unique entry number (in this example, job number 301). Jobs may
share the same job name but never ~ne same job entry number.
When you delete a job by its entry number, you are deleting that
particular job with greater confidence.
It is possible to delete
the wrong job when a job is referenced by its jobname. Deleting
a job by its unique entry number protects you from such mistakes.
2.

DCL>DELETE/JOB LPO KIRSTEN
MCR>QUE LPO:KIRSTEN/DEL

This command deletes the job KIRSTEN by first referencing the
job's queue, LPO, and then deleting the job KIRSTEN from LPO.
3.

DCL>DELETE/ENTRY:301/FILE_POSITION:2
MCR>QUE /EN:301/FI:2/DEL

This example deletes only the second file appearing in job 301.
You may only refer to the file you wish to delete by the file's
position in the print job
(the numbered order in which you
entered the file specification). You cannot specify the file you
wish to delete by referring to its file specification.
Notes
Associating a particular file specification with the numbered
order in which it was entered into a queue can be accomplished by
entering a SHOW QUEUE command (QUE /LI), and examining the output
on your terminal.
See Figure 1-1 for an example of the entry
order of file specifications.
Using the /ENTRY:nnn qualifier to delete a job saves keystrokes.
You are also deleting a job with greater confidence. Remember a
job may share a job name but never a job entry number.
If, for
example, you decided to delete a job by referring to the job
name, and you have several jobs sharing the job name, you would
succeed in deleting only the first occurrence of the job and not
necessarily the job that you wanted to delete.
DELETE/QUEUE {QUE /DEL) works on all categories of jobs in auy
queue.
You can delete ACTIVE jobs, WAITING jobs, TIME-BLOCKED
jobs, or HELD jobs.
There can be more than one job with the same name from the same
UIC.
The DELETE/QUEUE (QUE /DEL) command will delete the first
job of a given name in the queue.

2-11

QUEUING JOBS
2.4

PRINT JOBS QUEUED BY SYSTEM TASKS

A number of system tasks can also pass print jobs to the Queue
Manager.
These jobs include listings from language compilers and the
MACR0-11 Assembler and maps from the Task Builder.
Print jobs can
also pass to the Queue Manager through CLI commands or PIP.

AF!+<.··· ·:.;;:. :;}!:f:i;::·:•.kf:h_· ···•;;.• ;:·.r·,,· ·· : ·. J:f t:>t-•; :::.•5/:;+··

· ~µt,:put··.1:.~::i;;e:· ,~·cin:.:]:)t!.·.···~·p~~1i1,e:j:·~ . . . ;;;·:·:,,:;;' ·.·: ;: :

2.4.1

Maps, Logs, and Listings

A number of system tasks can create printable output.
Examples of
these
are
Task
Builder
maps,
MACR0-11
assembly
listings,
batch-processing logs (RSX-llM-PLUS only), and listings from the
high-level language compilers.
These tasks are accessible directly
from MCR or through DCL commands. These tasks follow their own rules
for spooling output, but when you request that such output be spooled,
the request will be handled by the Queue Manager.
You cannot control the printing of such output directly, as you can
through the PRINT command. Once the jobs appear in a queue, however,
you can alter their attributes through the SET QUEUE (QUE/MOD)
commands. See Section 2.7.

2.4.2

PIP, CLis, and Output Files

On RSX-llM/llM-PLUS you can
Program, to queue print jobs.

use

PIP,

the

Peripheral

Interchange

ThP. following PIP command:

PI P>NAME. TYP /SP
causes the file NAME.TYP to be queued for printing.
The print job
will have a name derived from the name of the file (in this case,
NAME), and the SHOW QUEUE (QUE /LI) display will give the file
specification.
On RSX--11M:....PLUS systems, you can also send files directly
print~r:: via· Pti?, as shown

Line

ln the commc.tnd:

PIP>LPl:=NAME.TYP
,

...

. .... , ..

The print job will have ;:!. nam~ derived from<the name ofthe tasJ<; such
as PIPTIO, and the SHOW ,QUEUE (QUE /LI) .qiSplay Wi.11 n.ot giye the file
specification, })ut only. the file ID number/ 1abe1eq .FID •. 'I'he job \Vill
appear in ·the 9evice-specific queue cofr:esponding to tJ1e d.evice you
specify lin th:ls case~ LPl}.
·With the QUeue f.1anager present, yoµr Hl·es will
with someone else• s fires.
()n RS~-11M-P~US syst~ms~ you can us~ :the
files:._'to· tb~.,line .printer.

DCL>COPY
From? NAME. TYP
To? LPl:

2-12

DCL

not. be
COPY

in_terspe~sec.l

command

send

QUEUING JOBS

··~~~l~~·.J,:~~~~~~;~~~~~~~·
. . . . .~.~·· ·:i1)ipp~·a·r
~~,~~~
~~~~'t~~~~~ ri~~
an'd::. not:.tb~:·•fiie :.spec>i;U:Cat:£pi'l!,:.·.
'<ii) th~ <3:~~plq}1' from SHOW
Wq~·~ t!:~.LD~,g~.n~:: i!¥1S±Jt~: . ••.•··>•,.\.·.'.• :_:;;:UL. :::,y·_w.,,:." ..·: ........."...... .... .

···:, . ·.·::··"":.:.•· .

'.·9p:·••:1l·~~7:t.JM~~tus.··.•~r~~:§ll'l·,•·•··•••.~.·~~···•·•sv~t:·~Bi.•:?·r ~cil?]Jli;~a·t..•~'.?ns<.:~;a~.~i< t.fi~t:.·••··.•.•.••.•·c:r~at..e~·:·
'al'l. i?~1;·p~t,·· • f i~·~:·•·q·.al'l•··· '·~~9·•.• t.:~~·t, ·• ·~·~+·~·····t.{)'.· .~.···• J>.~ i-pt~·t"····· <:rr .• ·.·.c»t}i~:.r····s.p<?'pl . ~~···•9&Jt:put.
·@~~.~:<=;¢.·,. :.r~;t;p~:~·<,:~b<:lp":~r· ~·;:i:tjg··i·.J;.:· ;,1:9•• t:.P.~{~:~ $k;~: .. · . s·~inE>.1}t•; r,~·p1 cipe\1;h~······qµt_put
:+·~}e: . ··~PE1¢tt ·~9.(;l.t. ~<>l'.l.. ·'. ~:~·t,~:::.-::;;h:e'fl~lll~···•?•~:.:·t,•B~ : . 4.~viB-~> t.9<·-wnich·· yq~:: wi.:!:>;11, t::o
Us~~~-.' 'tl'l.~· 9.9:1:~~.'t-:•< · T:l14'e ·.t•s·:,: 9'~.l:'l: ep t~~~-Q-~:pp·;r;:~:(i.1; ·. ·~-~·P~- ~·ri~ ~ ·
· ·
*WRITE filespec [range]

*WRITE LPO:

2.5

200:400

PRINT JOBS QUEUED BY USER TASKS

There are several methods for spooling output from user-written tasks.
When you spool output from within a task, you cannot control the
printing directly as you can through the PRINT command.
Once the
print job appears in queue, however, you can alter its attributes
through the SET QUEUE (QUE/MOD) command. See Section 2.7.

2e5el

Opening a File on Disk and Using .PRINT

Your task can open a file on disk, output to it, and close it using
the PRINT$ macro call or call the .PRINT subroutine to spool the
output.
(Refer to the IAS/RSX-llM I/O Operations Manual.)
The file will be placed in the default queue PRINT.
In
FORTRAN
IV,
FORTRAN
IV-PLUS,
and
FORTRAN-77
on
RSX-llM/RSX-llM-PLUS, the equivalent is to use the DISP= 'PRINT' in
your OPEN or CLOSE statement.

2.5.2

Opening a File on Disk and Using the PRINT Command

Your task can open a file on disk, output to it, and close
your task exits, print the file with the PRINT command.

it.

Once

While this is not the simplest method of spooiing, it is the only
method that gives you access to the PRINT command qualifier. You can
accomplish much the same thing using the two methods described in
Section 2.5.1 by waiting until the job is in the queue and then
altering its attributes with the SET QUEUE command.

2-13

QUEUING JOBS
If you run your task from an indirect command file or batch job that
includes a
PRINT command after task exit, the difference between
spooling from within the task or from outside it will probably not be
noticeable.
You can also have the task issue the PRINT command by using the SPWN$
directive.
{Refer to RSX-llM/M-PLUS Executive Reference Manual.)

2.6

SHOW QUEUE AND SHOW PROCESSOR

You may use the commands described in this section to display
information about queues, the jobs in the queues, spooled devices and
{in the case of RSX-llM-PLUS systems) batch processors.
The commands described
in Section 2.6.1 allow you
to
access
informntion nhout QMG print johs (and for RSX-llM-PLUS systems~ batch
jobs) •
A SHOW QUEUE (QUE/LI) command will show all
jobs in all queues.
Qualifiers
{switches)
can be used to limit the display to specific
queues, specific jobs, and the like.
You may examine the contents of your system's queues
{in decreasing
degree of detail) by entering one of the following command qualifiers
(switches) •
/FULL (/FU)
/FILES (/LI)
/BRIEF (/BRIEF)
The commands described in Section 2.6.2 display information about
spooled devices and batch processors under the control of the Queue
Manager.

2.6.1

SHOW QUEUE {QUE /LI)

SHOW QUEUE (QUE /LI) displays information about
Q~X-11M-PT.ll~
- - - - •
- -- - - -

h;:itC"'h
-· - - --

;oh~- -- -

2-14

QMG

jobs

and

QUEUING JOBS
Format
DCL>SHOW QUEUE [queuename] [/qualifier [ s]]
MCR>QUE [queuename:] [ [uic]] [jobname]/switch[es]
DCL Qualifiers

MCR Switches

/FULL

/FU

/FILES

/LI

/BRIEF

/BR

/DEVICE

/LI:P

/ENTRY:nnn

/EN:nnn

/FORMS [ :n]

/FO[:n]

/NAME:jobname

jobname

/OWNER_UIC:uic

[uic]

/PRINT

/LI:P

/BATCH (RSX-llM-PLUS)

/LI:B (RSX-llM-PLUS)

Command Qualifiers {DCL) and Job Switches {MCR)
/FULL
/FU
Displays detailed information about queues, queue assignments,
jobs, the attributes of jobs in queues, and files that compose
jobs in queues.
/FILES
/LI
Displays information about queues, queue assignments, jobs in
queues, and files that compose jobs in queues. The attributes of
the jobs are not displayed. This display format is the default
of SHOW QUEUE (QUE/LI).
/BRIEF
/BR
Displays only queues, queue assignments, and jobs in queues.
You may examine specific attributes of queues by entering one

the

SHOW QUEUE queuename
QUE queuename:/LI
Displays QMG information for a single
displayed may be for either print
RSX-llM-PLUS systems) batch queues.
/DEVICE
/LI:P
Limits information to print queues.
2-15

queue.
The information
queues or (in the case of

QUEUING JOBS
/J;:NTRY:nnn
/EN:nnn
Limits information to a particular job entry
job's unique entry number.

referenced

the

Limits information to Print queues.
This qualifier produces
same information as the /DEVICE qualifier (DCL).

the

/NAME:jobname
jobname
Limits information to jobs with the specified jobname.
/OWNER UIC:uic
[uic] Limits information to jobs owned by the specified uic.
/PRINT
/LI:P

/FORMS [ :n]
/FO [ :n]
Limits information to jobs that are to be printed on a specified
form.
If n is omitted, the display shows all jobs that are other
then Form O.

Examples
The following examples show the three different output displays
(FULL, FILE, BRIEF).
(In order to include information pertaining
to batch queues,
the examples were done on an RSX-llM-PLUS
system.)
1.

DCL>SHOW QUEUE/FULL
MCR>QUE /FU

** PRINT QUEUES **
PRINT => LPO (LPl)
[7,25] DRGCL
ENTRY:22
FORM:O
ACTIVE ON LPO
PRI:SO LEN:O PAGE:O NORESTART FLAG:JOB NOLOWER
> 1 DBO: [ll,34]DRGCL.LST;l
COP:l
NODELETE
[7,40] LOGIN
ENTRY:24
FORM:O
PRI:SO LEN:O PAGE:O NORESTART FLAG:JOB NOLOWER
1 DB7: [7,40]LOGIN.CMD;l20
COP:l
NODELETE
LPO
=> LPO
LPl
=> (LPl)
** BATCH QUEUES **
BATCH => BAPO
[7,40] X
ENTRY:23
ACTIVE ON BAPO
PRI:SO NORESTART LOG PRINT:PRINT
> 1 DB7: [7,40]X.BAT;l
NODELETE
>

2-16

COP:l
COP:l

QUEUING JOBS
This display shows all information about the queues and jobs in
.queues.
In this example, the Queue PRINT can send jobs to LPO or
LPl.
LPl has been stopped by the System Manager and is therefore
not eligible to accept jobs.
(This is indicated by the processor
name enclosed in parentheses.)
There are two print jobs in the Queue PRINT:
o

[7,25]DRGCL, entry number 22, which is currently being printed
on LPO

[7,40]LOGIN, entry number 24, which is waiting to be printed.

The attributes of the job are indicated in the display, and the
files that make up each job are also listed. The angle bracket
(>) indicates which file of a job is currently being processed.
2.

DCL>SHOW QUEUE [/FILE]
MCR>QUE /LI

** PRINT QUEUES **
PRINT => LPO (LPl)
[7,25] DRGCL
ENTRY:22
> 1 DBO: [11, 34]DRGCLa LST;l
[7,40] LOGIN
ENTRY:24
1 DB7: [7,40]LOGIN.CMD;l20
LPO
=> LPO
LPl
=> (LPl)
** BATCH QUEUES **
BATCH => BAPO
[7,40] X
ENTRY:23
> 1 DB 7: [ 7, 4 0] X. BAT; 1

ACTIVE ON LPO

ACTIVE ON BAPO

This display, the default format, shows the queues in the same
state.
It does not show the attributes of the job.
It only
shows the form number of the job and the attributes of the files
if other than the default values were specified.
3.

DCL>SHOW QUEUE/BRIEF
MCR>QUE /BR

** PRINT QUEUES **
PRINT => LPO (LPl)
(7,25] DRGCL
ENTRY:22
[7,40] LOGIN
ENTRY:24
LPO

;;;;:) LPO

LPl

=> (LPl)

ACTIVE ON LPO

** BATCH QUEUES **
BATCH => BAPO
[7,40] X

ENTRY:23

ACTIVE ON BAPO

This display only shows the names, entry numbers, and status of
the jobs in the queues. Also, if a form other than Form 0 is
specified for a print job, the form will appear in the display.

2-17

QUEUING JOBS
2.6.2

SHOW PROCESSOR (QUE /LI:DEV)

SHOW PROCESSOR
(QUE /LI:DEV)
displays
information
about
the
initialized characteristics of spooled devices and (on RSX-llM-PLUS
systems) batch processors, printers, and other output devices under
control of the Queue Manager.
Format
DCL>SHOW PROCESSOR [processorname]
MCR>QUE [processorname:]/LI:DEV
Displays information about all processors.

DCL>SHOW PROCESSOR/BATCH
MCR>QUE /LI:DEV:B

·.:. ·;~· )g~~:s,x.~'~t>;~J.t~·:m~:·¥~:.~~~:~.·~• s.Jibi4.s':::··~·:~ll:;T:'6~.:tq·i:i; ;E>:f;~c;:.~·*~'c:>:J;R':~.
DCL>SHOW PROCESSOR/PRINT or SHOW PROCESSOR/DEVICE
MCR>QUE /LI:DEV:P
On RSX-llM/llM-PLUS Systems, shows all Print processors.
DCL>SHOW PROCESSOR/INPUT or SHOW PROCESSOR/CARD_READER
MCR>QUE /LI:DEV:I

: Ori RS:X.0:1,JJ~:--:PL.US: ·s::y:st;ems"
{Refer to Section 3.9.)

shows. .sP6oled':

cai:d. :.iead·er:'; deliic.es.

Example
Enter one of the following commands on your terminal:
DCL>SHOW PROCESSOR
MCR>QUE /LI: DEV
Information about print processors and (on RSX-llM-PLUS systems)
batch processors and spooled input devices will be displayed at
your terminal as shown in the following RSX-llM-PLUS example.
** SPOOLED DEVICES **
LPO
<= PRINT LPO
LOWER
FORM:O
FLAG:2
CURRENT JOB:
[301,3l]CAESAR
LPl
(STOPPED) <= LPl
NOLOWER
FORM:l
FLAG:l
**BATCH PROCESSORS **
BAPO
<= BATCH

ENTRY:59

This display shows all
information about spooled devices and
batch processors.
In this example, spooled device LPO can
receive jobs from queues PRINT and LPO.

2-18

QUEUING JOBS
Spooled device LPl has been stopped by the System Manager and
therefore not eligible for receiving jobs for printing.
::~n~ <Jn~-y-·f)·at:¢b ·pr()9e~$pr.,•,~~go.f f·~P pp1.~. .·.. i;.~p~·.~•1e·
.
..
.
. ·
.. .

:·;oti,~b:e.: $ATCH.;

•·tp:e:

LPO is currently printing job [301,3l]CAESAR, entry number 59.

2.7

SET QUEUE (QUE/MOD)

SET QUEUE (QUE /MOD) modifies attributes given to either print jobs,
batch jobs, or files that compose jobs in queues. Such jobs and files
have been entered in queues by either the PRINT command or (on
RSX-llM-PLUS
systems)
SUBMIT
command.
You cannot change the
attributes of an active job.
Job Formats
DCL>SET QUEUE quename jobname/qualifier[/qualifier[s]]
DCL>SET QUEUE/ENTRY:nnn/qualifier[/qualifier[s]]
MCR>QUE queuename:jobname/MOD/switch[/switch[es]]
MCR>QUE /EN:nnn/MOD/switch[/switch[es]]
DCL Qualifiers

MCR Switches

/AFTER: (hh:mm dd-mmm-yy)

/AF:hh:mm:dd-mmm-yy

/JOBCOUNT:n

/CO:n

/FORMS:n

/FO:n

/LENGTH:n

/LE:n

/LOWERCASE

/LOW

/PAGE_COUNT:n

/PA:n

/PRIORITY: n

/PRIO:n

/[NO]RESTART

/[NO]RE

/UPPERCASE

/NOLOW

File Formats
DCL>SET QUEUE queuename jobname/FILE_POSITION:n/qualifier[/qualifier[s]]
DCL>SET QUEUE/ENTRY:nnn/FILE_POSITION:n/qualifier[/qualifier[s]]
MCR>QUE queuename:jobname/MOD/FI:n/switch(/switch[es]]
MCR>QUE /EN:nnn/MOD/FI:n/switch[/switch[es]]
DCL Qualifiers

MCR Switches

/COPIES :n

/CO:n

/[NO]DELETE

/[NO]DEL

2-19

QUEUING JOBS
Job Qualifiers and Switches
/AFTER:(dd-mmm-yy hh:mm)
/AF:hh:mm:dd-mmm-yy
Changes the time after which your job will be printed.
The job
will be BLOCKED until the time and date you specify. The job
will not necessarily be printed at exactly the time you state but
will be eligible after the time you state.
If you do not supply the calendar field, the default is the
current date. If you do not supply the clock field, the default
is midnight on the date given in the calendar field.
If you supply both the clock and calendar fields,
separate them with a space (DCL) or a colon (MCR).

you

must

/JOBCOUNT:n
/CO:n
Changes the number of copies of a job you wish to have printed.
See File Qualifiers for an explanation of how to modify the
number of copies of a file contained inside of a job.
See
Section 2.2 for an explanation of the COPIES attribute as it
applies to print jobs.
/FORMS:n
/FO:n
Changes the FORMS attribute of your print job. See Section 2.2
for an explanation of the FORMS attribute as it applies to print
jobs.
/LENGTH:n
/LE:n
Changes the length of a logical page (number of lines per printed
page) of your print job. A line printer will move to the top of
a physical page every time n lines have been printed on a page.
See Section 2.2 for an explanation of the LENGTH attribute as it
applies to print jobs.
/LOWERCASE
/LO
Prints your job on a line printer initialized /LOWERCASE by
system manager.

your

/PAGE COUNT
/PA:nChanges the limit on the number of pages your job may produce.
See Section 2.2 for an explanation of the PAGE COUNT attribute as
it applies to print jobs.
/PRIORITY:n
/PRIO:n
Changes the queue priority of a print job.
Nonprivileged users
may set priorities up through 150. Privileged users may set
priorities up throuqh 250. See Section 2.2 for an explanation of
the PRIORITY attribute as it applies to print jobs. -

2-20

QUEUING JOBS
/[NO]RESTART
/[NO]RE
Changes the restartability of your job.
If you specify /RESTART
(/RE), your job will start again from the beginning if it is
interrupted while ACTIVE.
If you specify /NORESTART (/NORE), the
default, your job will pick up where it left off, if it is
interrupted while ACTIVE.
/UPPERCASE
/NOLO
Changes the attribute of the job from lower- to uppercase.

File Qualifiers and Switches
/FILE POSITION:n
/FI :nChanges the operation of /COPIES:n
(/CO:)
or
/[NO]DELETE
(/[NO]DEL)
as they apply to a file contained in a job in queue.
The number n refers to the file position in the job.
Use SHOW
QUEUE to determine its position.
/COPIES:n
/CO:n
Changes the number of copies of a file you wish to
within a single printing of a print job.

have

printed

/[NO]DELETE
/[NO]DEL
Changes the delete status of a single file contained in
job.

Example
DCL>PRINT/JOBCOUNT:2 KIRSTEN.TXT,JPAUL.TXT/COPIES:3
MCR>PRINT/C0:2=KIRSTEN.TXT,JPAUL.TXT/C0:3
The SHOW QUEUE/FULL (QUE/FU) command output might look like this:

** PRINT QUEUES **
PRINT => (LPO)
[303,5]
KIRSTEN
ENTRY:696
FORM:O
PRI:50 LEN:O PAGE:O NORESTART FLAG:JOB
1 DB7: [303,S]KIRSTEN.TXT;l COP:l
2 DB7: [303,S]JPAUL.TXT;l
COP:3
LPO
=> LPO
LPl
=> LPl

NOLOWER COP:2
NODELETE
NODELETE

To print two copies cf the file JPAUL.TXT instead cf the three
copies specified in the initial print command, you would type one
of the following SETQUEUE (QUE /MOD) commands on your terminal
and enter it:
DCL>SET QUEUE/ENTRY:696/FILE_POSITION:2/C0:2
MCR>QUE /EN:696/MOD/FI:2/C0:2

2-21

QUEUING JOBS
The SHOW QURUE/FULL (QUE /FU) command
would look like this:

output

your

terminal

** PRINT QUEUES **

PRINT => (LPO)
[303,5]_
KIRSTEN
ENTRY:696
FORM:O
PRI:SO LEN:O PAGE:O NORESTART FLAG:JOB
1 DB7: [303,S]KIRSTEN.TXT;l
COP:l
2 DB7: [303,S]JPAUL.TXT;l
COP:2
LPO
=> LPO
LPl
=> LPl

Note that the file in position 2,
copies instead of 3 printed.

JPAUL.TXT,

will

NOLOWER COP:2
NODELETE
NODELETE

now

have

Notes
When you issue the PRINT command
(or the SUBMIT command for
RSX-llM-PLUS batch processing), you specify attributes of the QMG
job through command qualifiers (switches). SET QUEUE (QUE /MOD)
command qualifiers (switches) change the matching attributes.
You cannot change the attributes of an active job.
You can delete files or change the number of copies to be printed
by specifying /FILE_POSITION:n (/FI:n) in your SET QUEUE command
line.

2.8

HOLDING AND RELEASING JOBS

You can specify that a print job be HELD in queue when you
PRINT command.

issue

the

You can release such jobs with the RELEASE (QUE /REL) command.

2.8.1

HOLD (QUE/HO)

HOLD (QUE /HO) blocks a job
released.

its

queue

until

explicitly

Format
DCL>HOLD/JOB queuename jobname
DCL>HOLD/ENTRY:nnn
MCR>QUE queuename:jobname/HO
MCR>QUE /EN:nnn/HO
Specifying the job's entry number saves you keystrokes. When you
reference a job by its unique job entry number, you are avoiding
ambiguity between job names.
The entry number
identifies both
the queue the job is in and its name.
If you supply the entry
number, do not name the queue or the job.

Remember; jobs may share the same name but never the

same

entry

number.
If you name the queue and job, do not supply the entry number.

2-22

QUEUING JOBS
2.8.2

RELEASE (QUE/REL)

RELEASE (QUE /REL) unblocks a job that has been held in queuee

Format
DCL>RELEASEiJOB queuename jobname
DCL>RELEASE/ENTRY:nnn
MCR>QUE queuename:jobname/REL
DCL>QUE /EN:nnn/REL

Example
DCL>PRINT/HOLD/NAME:KIRSTEN JPAUL.TXT
MCR>PRI KIRSTEN/HO=JPAUL.TXT
The SHOW QUEUE/FULL (QUE /FU)
this:

command

output

might

look

** PRINT QUEUES **
PRINT => LPO
[303,5]
KIRSTEN
ENTRY:698
FORM:O
HELD
PRI:50 LEN:O PAGE:O NORESTART FLAG:JOB NOLOWER COP:l
1 DB7: [303,5]JPAUL.TXT;l
COP:l
NODELETE
LPO
=> LPO
LPl
=> LPl
To unblock KIRSTEN.TXT, you would type one
RELEASE (QUE /REL) commands on your terminal:

the

following

DCL>RELEASE/ENTRY:698
DCL>RELEASE/JOB PRINT KIRSTEN
MCR>QUE /EN:698/REL
MCR>QUE PRINT:KIRSTEN/REL
The SHOW QUEUE /FULL (QUE /FU) command
this:

output

would

look

** PRINT QUEUES **
PRINT => LPO
[303,5]
KIRSTEN
ENTRY:698
FORM:O
ACTIVE ON LPO
PRI:50 LEN:O PAGE:O NORESTART FLAG:JOB NOLOWER COP:l
>
1 DB7: [303,5]JPAUL.TXT;l
COP:l
NODELETE
LPO
=> LPO
LPl
~> LPl
Note, the HELD status of the job in the previous example was
first changed to WAITING, and then, since there were no jobs in
queue, became ACTIVE.

2-23

CHAPTER 3

PREPARING A USER BATCH JOB

3.2

A USER BATCH JOB

A user batch job must duplicate a complete interactive terminal
session. It must issue commands and supply data to any tasks that run
from the virtual terminal. Labels and sequence control commands make
it possible for you to_ program responses to errors from within_ your
user batch job.

3-1

PREPARING A USER BATCH JOB

$(label:]

(command]

All commands in batch jobs must be preceded by a dollar sign ($). The
dollar sign
($)
informs the batch processor that the line is to be
interpreteo as a command! and not as data. The dollar sign ($) is not
part of the command.
Commands may be batch-specific commands, designed exclusively for
batch
processing, or CLI commands like DCL and MCR commands.
Batch-specific commands work with CLis, not as replacements for CLis.
There are certain-DCL and MCR commands that should
be used in
batch jobs.
The DCL commands LOGIN and LOGOUT
their MCR
equivalents HEL and BYE are not necessary. The
$JOB
and $EOJ perform th~ login and loyout functions of a CLI.

3-2

PREPARING A USER BATCH JOB

beginning of a user
in 'a QMG batch job.

3-3

batch

job

PREPARING A USER BATCH JOB

: You need not include a
brackets.
The UIC is
entered.
If you do not include a UIC, then any user who_h(iS read access to
the file c~ri~ubmit th~ job.
If you include a UIC and you are non-privileged, the UIC must be
the same UIC that the SUBMIT command will be issued under. I t
need not be the same number as that of the UFD where the batch
juL fil~ ls k~pL.
Privileged users can have their batch jobs log in under any UIC.
If you use the slash format for the UIC [g/m] , you can suppres~
most login messages. If you do not specify a UIC, login messages

will not be suppressed.
Command Qualifiers
/'rtM E: ( hh: mm)

or
/TIME:m
Limits the job to hours (hh)
default is thre~ minutes~
Examples
L

$JOB

This is <the simplest form of the JOB command.:
onto a terminal. The UIC is the same
command was issued under~
Informational ·
included in the hatch

,.,
£..

$JOB

r..,,nl#tni

L£V/£VJ

This· example logs the user in under f20, 201··. and suppresses· ·loglri.
messages.

3-4

PREPARING A USER BATCH JOB

The DATA command marks the beginning of a data block included in the
batch job.
EOD is required to end the data block. Data is any
required user input, other than DCL, MCR, or any other CLI commands.
The DATA command is optional unless one of its qualifiers is needed.
When used, the DATA command in batch jobs should immediately follow
the command that requests input.

3-5

PREPARING A USER BATCH JOB

BEATLES.FAS
P.EPPER. SGT
$PRINT PEPPER.SGT
$RENAME
$DATA
BEATI.ES.FAB
PEPPER.SGT
$PRINT PEPPER.SGT
The two examples are equivalent~
PEPPER.SGT and print PEPPER.SGT.

They

rename

BEATLES.FAS

The data is input for the RENAME command. In the first example,
the first line without the dollar sign {$) is taken as data,
because the previous command called for user input.
In the
second example, the DATA command identifies the following text as
a data block for the RENAME command. In both examples, the next
dollar sign ($} encountered marks the end of the data block.

3-6

PREPARING A USER BATCH JOB

in the log file.

marks the end of a data block.
Format
$EOD

3-7

PREPARING A USER BATCH JOB

The.. STOP c·ommand ·~rthoui •. a qu~lifier. is . a batch-specific command.
A STOJi> command followed by a qualifier or any other command line
el.ement will ~e pa~sed to the current CLI.
If the batch processor reache·s a STOP command, it conside.rs the
command equivalent t6 an EOJ command. You can have more than one
STO:"'c~~~~~~_..in a batch, job, when it is used with the
GOTO, ON,
or J.t' l.,;UllUUd!lU.
If the QMG batch job includes another user batch job,
processor continues with the next user batch job.

You can stop a QMG job interactively
QUE/DEL command. See Section 2.3.

3.4.6

with

the

batch

DELETE/JOB

CONTINUE

The CONTINUE command is a. no-operation.
the ON or the IF command.

It can be used alone or

with

Formats
$CONTINUE
$ON WARNING THEN CONTINUE

Notes
For the most part, this command< is used· with the IF or the ON
command..
Its main use is ·to keep the batch processor from
stopping the job when it encounters a status return code other
than SUCCESS.

3.4.7

GOTO

The GOTO command directs the batch processor to skip directly to the
line beginning with .. .3. sp~cHie:d·lahel andcontinue processing from
th.ere. It can be used alo!l.e: :Qr:wJt:b. the>ON or. the IF command.

3-8

PREPARING A USER BATCH JOB

command defines an exit status code and specifies the action to
taken by the batch processor when that code or a more severe code
is returned by subsequent commands and tasks. The default setting is:
$ON WARNING THEN STOP

3-9

PREPARING A USER BATCH JOB

This is the default setting.
ct her

I f you do not· override it with some
qommand, then any \AJF'.. RNING c r

code will st:op the

bat~h

j<)b.

$ON ERROR THEN GOTO NEXT
After it executes this command, the batch processor
WARNINGS.

Wht:(1 ii.. ft::-l;t:dvt::::S cm ERROR or

ignores

SEVEREERROR code,

directly to the line labeled $NEXT: and processes
and all -subsequent commands following the label.

the

all

it goes

command

Notes
Once the condition specified by the ON command is encountered,
the ON command is canceled and the default setting, ON WARNING
THEN STOP, is restored. You can reset the ON command at any
point in the user batch job.
The conditions that produce a particular
determined individually by each system task.

status

code

command remains set until superseded by· another· ON
command, by the specified error condition~ by a SE;T NO ON command·
(Se:ction 3.4. 9), or by the end of the user batch job•
Compare
wi tn the. IF command.
UFD [200,l] on the. system disk cont.ains :tasks that do nothing but
exit . :wltl1 st.atus ~ >Y~o.ucan copy these<t(!sks and:use t,heni to t:¢~t:.
uses: of. t.he s~quemce c9.rrt:ro1· commaJ'ldS.• ··.· They :are:
Sl1GG.E$$'!'l:'$I<.i.
WARNING.c•. 'J:'SKr .ERROR.TSK, 'and . . S~VERE.TSK•.

3-10

PREPARING A USER BATCH JOB

IF SUCCESS is not legal •

.·if no co~e is returned, the batch processor assumes SUCCESS.

3-11

PREPARING A USER BATCH JOB

·exit status, then the

3.4.11

Comments

(l)

The exclamation point (!) is used to include comments in the batch
log.
It is the only comment character that should be used in user·
batch jobs.
The batch processor does not send text preceded by the exclamation
point (!) to the CLI. Comments beginning with any other characters
will be passed to the CLI and could cause problems with
processing.

Formats
$!comment
$[label:]batch-specific
This field can include
not process anything
(! ) .

Examples

$!$BIG QUESTION?

3-12

PREPARING A USER BATCH JOB

possible if you want your batch job
run in yo.ur absence at a later time. First, you have no way of
determining which drive will be available when it is time for your job
to be .run, and, second, you will need an operator to load the device
and mount the volume when the drive does become available.
The ALLOCATE command has a keyword that handles the first problem, and
the MOUNT command has a keyword that handles the second problem.
It is necessary to first. include a generic ALLOCATE
batch job. The command format is as follows:
(DCL) $ALLOCATE [/TYPE:devtype] dd ddnn:
(MCR) $ALL dd=ddnn: {/TYPE:devtype]

3-13

command

your

PREPARING A USER BATCH JOB

In this example, you do not know the physical device name, so you
give it a logical device name, INO:.
If you intend to ·load the device yourself on a specific drive,
you need only use the standard form of the ALLOCATE and MOUNT
command as shown in the following example.

a full directory listing
already loaded and spun up.

3-14

PREPARING A USER BATCH JOB

Command

/AFTER: (dd-mmm-yy hh:mm}
(mm/dd/yy hh:mm)
/AF:hh:mm:dd-mmm-yy
Blocks the job until after the specified time. Depending on the
batch queues at that time, your job may be run immediately or
later when its turn comes up in the queue.

3-15

PREPARING A USER BATCH JOB

.Jf • • y9ur ~Y~{em ··ctt:.• i!;·····.•.:·.oc~~<·· :t~~····P~t·E?•nth~:s~·5··~····· h}'pfaells··: {or.JsJ.a.~~e!3S.?•·

c:ol?n_s·t··~'.gnd ·. ·.:-t:b·e·:.·:spet9e····~etwee~?·t:he c.a~endC!r•·••·Cifi<l'. cloq·k :fteta~: ·ai·~
neces$ary syr1t~~.- ... Note· 'that a. :i:;~ac~ .is ·.·t1s~9 <>nly be1:ween th~·
calendar and clock fields •. The· sp(;ice is .na·t .usea .. Jf. eithe.r· field
:. is omitted.
.
·a.~1

.',Yql.l Can ,sp~cify the .cafenaar f1,~¥(j~n 't~ltb~r. of· t:w(.) .fa.>tmat:s-.•.

dd~mmm--cyy

Uses· a·· 011e- ·or ~\tlo~a~~i~.· ~·llffiP~P< . .f()~ ··the. day,.· . . . ·~··~·~··
Hrst, .. t~I!ee. lett:ers. ~9.r;.:t:he-)Qontb,· a·n~l .t"!o> n•umt;e:r.s;:
for :the ye·ar;
··
,:·: ... ·.·

· .. ,

.uses •. a 6-ri~~ •.
f:woia'.f~ft:' ~µmber: . : for ·the· ·mofrth,.• a
one- -or< . . . t:·w979tgi.t: . l1:t1~ber ·for. the :d.iiY#. :~r1d
numbers ~Or>tbe YEH~~.~·:.>.·. .
·.. •··

.mm/dd/Y'i'

.two.

tf ¥ol11eave .••6ut ·the Ycal~~d~r: fl~ia, t:h~. '·~:~:~; · ·aei~~its

- c=u·r:r e_n:t~:: _ q.:.a ~Er-•

-=.-~·· =· · ··_:_·, :-: : :.; :··.·_:=,; ~. ·-~

'tile::

£he.•6iacl<·•·•fl~1(:1, ttie time: defaults t?> oo:•o-o::uo~
,.

:·.:·

·.

·:

.·:··

·,.· .. ·

···:: ······.···· .. · .. · ..... :

··,·:

:·.·.

If your sys~enr::9L! .. is MC:R,:. yo:ll~ j·hb ts> .tlme~l:>locked in its<. queue
until after the stated time: · ·
Must c6l1ta1n · the first thr~e characte.rs. of the month•
yy

Can be from 00 to 99

net specify the
until after. other jobs in the queue· are despooled.

I f you de

/[NO]HOLD
/[NO] HO

Specifies that the job be held in its queue.
job with the RELEASE/JOB command.

You can release the

/NAME:jobname
jobname=
Specifies a job name for the QMG batch job.
up to nine alphanumeric charac·ters.

The job name can

If you specify a job name, that name appears in the

output from
QUEUE (QUE /LI) commands. Otherwise, the· file name of the
first file specification submitted will be used as the job hame6

SHOW

I f you have specified /NOPRINT (/NOPRIN') and a job name, then the
permanent file copy of the batch log will have the job name as
its file name and .the type • LOG~

Note that individual jobs in the. chain can label thf!il' portion of
the log with the label field of the JOB command.
/[NO} RESTART
/{NOJRE

Indicates whethei
riot a.·. Job . should
beg inning· i f 1 t is ·interrupted for any reason •.
The default is /NORESTART .(/NORU. If a
aborted, i t is deleted from the iqueue.

nonrestartable

j-0b

/RESTART ()RE) means the_job "1Pl begin again at the beginning .if
it is aborted.'

3-16

PREPARING A USER BATCH JOB

one is
the log
SHOW

The default

3-17

/LOGFILE

PREPARING A USER BATCH JOB

The /PRINT, qualifier (/PRIN) is
equivalent to the previous one.
3.

the

default.

DCL>SUBMIT/NOPRINT JANE.BAT

MCR>SUB /NOPRIN=JANE.BAT
In this example, a permanent log file is created in your UFD.
After the batch job completes, you may examine the log file
JANE.LOG at 'your terminal or use the PRINT command to spool it to
a line printer.
DCL>8UBMIT/NO_LOGFILE JANE.BAT

3-18

PREPARING A USER BATCH JOB

of the batch processor

3-19

PREPARING A USER BATCH JOB

'l'h~. user job ._ttag ~J?pe~is 91recti:Y at:t~p .tne -5e>t?'. commana
··.. ·.· arspra-Ysf ·
- ---- ·-•

{Jser job:

•

Devlce·nam~

•

urc under which· the :batch· job was ).C)gged in

terminal

of the

, ....... · .

and

-~-"''·-'-CC.C.,_

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

: •.This fnfcfrrnation is
silc.cessful .login.
,.

........ ,

rema.i11i·ng . . •. P()·~·.~·i()n of·. the .rog .·.Ji.1e:aocumeni:s the activir~r
the! us~r · batch .job,. whic~ incluqes tbe fdl1owlrig:

Coltlmanp lines Ci·r_ia comm~nts· p:receded by a time starnP:
~

. .

. . . . . . . . . .: :

: ... :

Out:put·.• from···.•r.=61m.nands.·.··arid•··.t~sks friorillally wri_tten
·terminal)·

-Lines.• •skipped:. by .•

y<>:ut . /

a. . ·GOTO statement

EXIT STATUS MESSAGES
There are three line identifiers that appear in the space between the
t:.J.me stamps cn1d i:.he comman<l lines 1n the log f.ile. These identifiers
are TERM, DAT.1\, .. or SKIP.
TERM identifies the line as output from a
terminal.

task

the

virtual

DATA identifies the line as inP:ut data to a task.

SKIP indicates that the
command.

was

skipped

because

Periods that appear below an identifier

indicate

that particular line

line

continuation

GOTO

identifier~

Your batch log file may also contain a message that indicates that the
severity level in a previous ON command has been met or exceeded when
A
t-~~1c ,::ivit-iprf_
-------- 'T'h,::i
-,-- miPc::c::AnP rtic::n1Avc::
---r--.i- t-h,::i
---:- exit status returned by the
task~--

~-------:1-

Examples 3-1 through 3-4 show user batch jobs and the log
produce.

files

they

Example 3-2 shows the output for the user batch job in Example 3--L
The UIC is not specified in the job but is displayed in the user job
flag. The systE?m messages' therefore, are not suppressed.
Note when data:<appears on··the same1ine as a
line to be labeled.TERM rather than DATA ..

prompt,

it. causes·

.•Al~o, pote ..that w~en. t~.e. GOTO. speCifi.ed in the ()N ··and· .IF
enabled, the liries that are skipped are labeled as SKIP.

3-20

commands

the

PREPARING A USER BATCH JOB

3-21

PREPARING A USER BATCH JOB

11: 04: 04

TERM
11:04:08
TERM

$DIFFQ: PRI LPO:jHO=l984.CALjCO:lO
", submitted to queue "LPO
PRI - Job 850, name "1984
$STOP
Connect time: 1
mins.
CPU time used: 4
secs.
Task total:
16

In Example 3-3, PIP requires input from the virtual terminal TI:
to
create the file GREET.FTN therefore, the program itself is identified
as DATA. Example 3-4 shows the output file for the user batch job in
Example 3-3.
Example 3-3

User Batch Job Friend

Program

3-22

PREPARING A USER BATCH JOB

the Card
Processor (CRP)
When you place a
- deck of cards in the hopper of a spooled card reader and press the
RESET button on the reader, CRP reads the deck, copies the cards to a
file, and requests the Queue Manager to create a job containing this
- file.
While a batch job submitted from an interactive terminal may
-contain several files, each executing as a separate batch job, the
- entire -deck of cards is read into a single file and this file is
submitted as one batch job.
You may also submit a deck of cards to be printed a You can then check
the listing for the accuracy of the card deck contents.

3-23

PREPARING A USER BATCH JOB

--:=.:::=·... ·.···=.:-.:.=-:· . =· . .·.·:.. :· .. ···... ·· =···::·.:··.. :··'.

The :£o:r:i~.af:: of ~: ~~tch:job.~ar~ deck· is .... similar .•. ·to•. ·t.he ..... forma~

of · a••

sing.~.E!·••· .. b9tchqQmma;ncL•.~iTE:?. o.n.. qisk.'. :· ·.liowE:?ver, •.· . for •Y()u;r.card·d~ck .:to b~:
~l1cc~s~.f.~11yr~c.q)>y .~h~ Car~·:···~e~d.e:r:- E>roces~()r; you must . •·:iJ·1clude a. few.
addi:tiohal:·conttol··carqs;,; •Y'our •card• de6k,.E;-hoUld ~ook like t~~.s:<
'"

·:·:::::: :_:_:: :=:-:: ··: :·-.:;·:.: :·::: ':.:" ·:·, :.·:: :,::._·:

:_:.~:. '-~-:·: :;::; :.; :_: ~ '.:}: ::=:·:·:;: :·: :·:: :·::·:1

$SUBMlTor>$:PRIN·T. Ca:td
. . . : . :. : . . . . . . . . .
~

;:-: . :::::'/<·.··'..-:.; . . _: :·..-

.3:/. ·c~rds ib . be ; sJb~rtiti~d or; priht:ea:
$JOB
...

<: · •

$EOJ
~

.. . .

. .: . '

The $SU8Mrr· and .$PRINT ·card$ ha\1e<a format· similar to the format of
t.he DCL. c:ommands SUI?ft\IT a11d PRIN'.l"~ They i¢ientify the beginning of a
ccird deck and .. ~et'ermine whether the .cards will bf3. subniitted for . batc.h
proce.f>sing. or printing.• They· are described in more detail in Sections
3.9.1 and 3.9.2•
·
The $PASSWORD card is used to spec:ify yo.ur password. This should be
the same password that you use to login to an interactive terminal.
It· i·s used wtth userllame or user· Uie information specified ·on the
$SUBMIT or $PRINT card to identify and authorize you to enter batch
jobs.
The next cards in the deck make up the actual batch

job.

These

are

The end-of-file card is used to signal the end of your card deck.
It
consists of the punches i2:..11-0-lc-6-7-8-9 in column one. This card is
not copied to the file.
Example 3-5 shows a user batch job ·that is to be submitted by the Card
Reader Process.
Example 3-5

user Batch Job to be submitted by CHP

$S USM IT/QUEUE : B.AT.2/PRI NT .:.LPl/USER: KENT KRYPTON
$PASSWORD CLARK
. .
.$JOB XRAY [20/20]

$RUN · PL.ANET
$DATA

.:J. Olson

L• Lane
P,.>White
$EQD
$EOJ ..... ·.·.· ..

enq;.;.Of;;_;file .card

3-24

PREPARING A USER BATCH JOB

is specified, columns 73 through
b~·

as a sequence field.
A sequence field may
consist of any eight alphanumeric characters.
In a sequenced
card deck, the sequence fields should be ascending from one card
to the next, although not necessarily by any fixed amount.
(MYJOB335, MYJOB336, MYJOB447 is a valid sequence, for example.)
A sequence field consisting of all blanks is allowed anywhere in
the deck, however.
No sequence fields may appear on control
cards.
wiii

interpreted

3-25

PREPARING A USER BATCH JOB

/FORMS:n
/[NOJHOLD
/[NO]JOB _PAGE

/LENGTH:n
/LOWERCASE
/NAME:jobname

/PAGE_COUNT :n

3-26

PREPARING A USER BATCH JOB

you can remove your card
the- problem, and put the

3-27

PREPARING A USER BATCH JOB
•

< ,_,. •• ,,_, ••

w'-:'•w••

"•

~···

·t::-J:f ·. c·~~P-'-~l~-~e?t-~ --~ -C¥ir-d; :o~t ::'.e:f:- !:)~que~c·e·~---~y·ou\·_ '<:iar{-~:' t"eplas:e :·:the':; $Stli\MI:T_.::·:·
L:.c~:r4 . -1r1·ttb.··•. a $·_P.~JN~.-- _c ar<it;._ ._.Pr+J1t.:: ~h~•·•.·.• c:ar(j>d~<::k·--· the11• ·_.i,nspec~ . ·th~ >$e-c1µ.~n6¢) ·
':;•numbers anq:ji-e:termine to. What e:Kt:ent ;~lje ca•rd-s . are< Sbt1ffledi0
-:::-·.:::.: .:::::.·.>-".:=.:_.:. . ·:=..~:;
. .
. . .. . . . , .
'

-:···~?.•u···::11ta'Y: w~nt··••••.:#;o •.·•.•.re:fe•·r•·•·-·•'t():.• _.•.• • :fh.~.- :_.'ksx.i1\1-M/M_j~I.us_ . . .• •. .•. • r·7·0·.··.••_·····I>r'·.1ve·r·s•·-•··•·:····•. Re.fe•r.erib-._~.•--·····>:Manual·'·- fo.r., .• •IJ}·o·i:;e<d7.~Bi l,~q·.• -•. ~·nform~t:..lc>n!. ·-·~pop·t:.:·:·-.h<:>""•-.·.~tie.:· . 9a-•ra. -r~ad•~r- d;ev ip~·.,·
:_ :wo-r;ks ~: ·· ~-~·i:>ec:,-~j~;l':·[ ··p~ef_µ+ ·is-·' 'the·.: t~f)lie.<·pt,<~~yI'I . -c·t1af'(lP~et:$•·•'- ~n<;t· ·. tbe'-~r·: '
:.iQ:t\ ,:.+r+··>;t\\'9.. -• (ji~~er;er1~.·c-a ~ : .• spde~ ~·-pE994,9 :apd- :.p~cq.~~······.· . . ¥lt\e
•.• m~.!(; •. ~9';P:··~.PI>~:~·~--· ·~·~:..• ·_.-_':;t:he·. ·.··.:
_f~~I."9 -J;<>·+· ..• -·.¥~.~~.; :_:_;··.~~~PL1~-s·p:j0\ .·: hFo:r-:::
:::::Ml:l:I;
· -·- :tp:;;:'l:c:>~:k ·~e
character-" l:tl.-'·:-~M tap·~-~ ::~i

•.• _•.

n·e·'.:co:

~-: '.'.}-~;·:~ :':f0'. ):~t-~1~;

3-28

... ::t_ '"
,.,<X?i~

",' .

CHAPTER 4
AT-A-GLANCE GUIDE

This chapter consists of summaries of command information from the
previous chapters. These summaries do not include full information on
the commands, but just enough to remind you of how the commands work.
The commands covered in this chapter are listed below:
PRINT {PRI)

BATCH-SPECIFIC Commands (RSX-llM-PLUS)
SUBMIT (SUB)

(RSX-llM-PLUS)

SHOW QUEUE (QUE /LI)
SHOW PROCESSOR (QUE /LI:DEV)
SET QUEUE (QUE /MOD)
HOLD (QUE /HO) and RELEASE (QUE /REL)
DELETE (QUE /DEL)

4.1

PRINT (PR!) COMMAND

PRINT queues files for printing on a line printer.
used to queue jobs for other output devices.

may

also

Format
DCL>PRINT/commandqualifier[s] file[s]/filequalifier[s]
MCR>PRI [queuename:] [jobname] [/jobswi tch] [=]file [s] [/fileswi tch [s]]
DCL Command Qualifiers

MCR Job Switches

/JOBCOUNT:n

/CO:n

/QUEUE:queuename

queuename:

/UPPERCASE

/NOLO

/LOWERCASE

/LO

/[NO]HOLD

I [NO] HO

/PAGE_COUNT:n

/PA:n

4-1

AT-A-GLANCE GUIDE
/NAME:jobname

jobname=

/PRIORITY: n

/PRIO:n

/FORMS:n

/FO:n

/LENGTH:n

/LE:n

/[NO]RESTART

/[NO]RES

/[NO]FLAG_PAGE

/[NO]FL

/AFTER: (dd-mmm-yy hh:mm)

/AF:hh:mm:dd-mmm-yy

/DEVICE:ddnn:

queuename:

/NOJOBPAGE

/NOJO

DCL File Qualifiers

MCR File Switches

/[NO]DELETE

/[NO]DEL

/COPIES:n

/CO:n

/[NO]TRANSFER (RSX-llM-PLUS Only)

/[NO]TR (RSX-llM-PLUS Only)

Notes
DCL file qualifiers override settings of command qualifiers.
The default file type for PRINT is .LST.
If you want your job restarted, you must use the /RESTART
qualifier.
For /AFTER:
(/AF:),
today's date.

omit

the

calendar

field

BATCH-SPEC IFI_C··. COMMANI) . -~uMMARY •. . (RSXo;.l lM-PLUS)

4-2

(/RES)

default

AT-A-GLANCE GUIDE

STOP stops
$STOP
$ON status-code
$IF status-code

4-3

AT-A-GLANCE GUIDE

The label can be any six
_colon on the GOTO line.
$label:{command]
The label must be terminated by a
GOTO may reference forwards or backwards.

4-4

AT-A-GLANCE GUIDE

/[NO]DELETE

/(NO]DEL

/[NO]TRANSFER

/[NO)TR

4-5

AT-A-GLANCE GUIDE

4.4

SHOW QUEUE (QUE/LI) COMMAND

SHOW QUEUE (QUE /LI) displays information about QMG print jobs and (in
the case of RSX-llM-PLUS systems) batch jobs.
Format
DCL>SHOW QUEUE [queuename]/qualifier[s]
MCR>QUE [queuename:] [ [uic]] [jobname] /switch [s]
DCL Qualifiers

MCR Switches

/FULL

/FU

/FILES

/LI

/BRIEF

/BR

/DEVICE

/LI:P

/ENTRY:nnn

/EN:nnn

/FORMS [ :n]

/FO[:n]

/NAME:jobname

jobname

/OWNER_UIC:uic

[uic]

/PRINT

/LI:P

/BATCH (RSX-llM-PLUS Only)

/LI:B (RSX-llM-PLUS only)

Notes
There are no prompts from this command.

4-6

AT-A-GLANCE GUIDE
4.5

SHOW PROCESSOR (QUE /LI:DEV) COMMAND

SHOW PROCESSOR
(QUE /LI:DEV)
about
the
displays
information
(RSX-llM-PLUS
initialized
characteristics
of
batch
processors
systems), printers, and other devices under control of the Queue
Manager.
Format
DCL>SHOW PROCESSOR/qualifier
MCR>QUE [processorname:]/switch

4.6

DCL Qualifiers

MCR Switches

processorname[:]

/LI:DEV

/PRINT or /DEVICE

/LI:DEV:P

SET QUEUE (QUE /MOD) COMMAND

SET QUEUE (QUE /MOD) modifies attributes given to either print jobs,
batch jobs, or files that compose jobs in queues. Such jobs and files
have been entered in queues by either the PRINT command or
(on
RSX-llM-PLUS systems) SUBMIT command.
Job Format
DCL>SET QUEUE queuename:jobname/qualifier[/qualifier[s]]
DCL>SET QUEUE /ENTRY:nnn/qualifier[/qualifier[s]]
MCR>QUE queuename:jobname/MOD/switch[/switch[s]]
MCR>QUE /EN:nnn/MOD/switch/[/switch[s]]
DCL Qualifiers

MCR Switches

/AFTER:(hh:mm dd-mmm-yy)

/AF:hh:mm:dd-mmm-yy

/JOBCOUNT:n

/CO:n

/FORMS :n

/FO:n

/LENGTH:n

/LE:N

/LOWERCASE

/LO

/PAGE_COUNT:n

/PA:n

/PRIORITY:n

/PRIO:n

/[NO]RESTART

/[NO]RE

/UPPERCASE

/NOLO

4-7

AT-A-GLANCE GUIDE
File Format
DCL>SET QUEUE/ENTRY:nnn/FILE_POSITION:n/qualifier[/qualifier[s]J
DCL>SET QUEUE queuename jobname/FILE_POSITION:n/qualifier[/qualifier[s]J
MCR>QUE /EN:nnn/MOD/FI:n/switch[/switch[s]]
MCR>QUE queuename:jobname/MOD/FI:n/switch[/switch[s]]
DCL Qualifiers

MCR Switches

/COPIES:n

/CO:n

/[NO]DELETE

/[NO]DEL

Notes
When you issue the PRINT or SUBMIT command, you
specify
"attributes" of the QMG job.
SET QUEUE changes the matching
attribute. You cannot change the attributes of an active job.
You can change some attributes of files that make up a QMG print
job by specifying the FILE POSITION:n (FI:n) qualifier in the SET
QUEUE command line.

4.7

HOLD (QUE /HO) AND RELEASE (QUE /REL) COMMANDS

You can specify that a job be held when you issue your PRINT or SUBMIT
command.
You can also hold jobs with the HOLD command and release
such jobs with the R~L~A~~ command.

4.7.l

HOLD (QUE /HO)

HOLD (QUE /HO) blocks a job
released.

its

Format
DCL>HOLD/JOB queuename jobname
DCL>HOLD/ENTRY:nnn
MCR>QUE queuename:jobname/HO
MCR>QUE /EN:nnn/HO

4-8

queue

until

explicitly

AT-A-GLANCE GUIDE
4.7.2

RELEASE (QUE /RE)

RELEASE (QUE /RE) unblocks a job that has been held in queue.

Format
DCL>RELEASE/JOB queuename jobname
DCL>RELEASE/ENTRY:nnn
MCR>QUE queuename:jobname/REL
MCR>QUE /EN:nnn/REL

4.8

DELETE (QUE /DEL) COMMAND

DELETE deletes queues or QMG jobs by name or by the job's unique entry
number.
Format
DCL>DELETE/JOB queuename jobname[FILE_POSITION:n]
DCL>DELETE/ENTRY:nnn[/FILE_POSITION:n]
MCR>QUE queuename:jobname/FI:n/DEL
MCR>QUE /EN:nnn/FI:n/DEL
Notes
Use these commands to delete a job in a queue by specifying
either the job's entry number or-job name. You can also delete a
single file in a job by specifying the /FILE_POSITION:n (/FI:n)
qualifier.
Nonprivileged users can delete only their own
users can delete any job.

jobs;

privileged

There can be more than one job in a queue with the same name.
The DELETE command will delete the first job of a given name in
the queue. You can distinguish between jobs with the same name
by using the unique entry number instead.

4-9

APPENDIX A
ERROR MESSAGES

A.l

BATCH PROCESSING ERROR MESSAGES

Commands in batch jobs can send error messages
batch log.

that

appear

your

In addition, the batch processors themselves can send error messages
concerning your batch jobs. Some of these messages result from system
problems and are returned to the operator's console.
Others reflect
difficulties in processing your batch job and are returned to your
batch log.

A.1.1

Error Messages in Batch Logs

BPR

Batch file already open
Explanation: QMG or BPR attempted to
when it was already open.

open

the

User Action:
manager.

your

operator

System

problem.

See

specified
or

file
system

BPR -- Batch file close failure
Explanation:

BPR failed to close the specified file.

User Action: The batch job should not be affected.
Check the
UFO to see if the file is locked. If so, issue the DCL UNLOCK
command or the MCR PIP/UN command.
BPR -- Batch file deletion failure
Explanation:
to execute.

The /DELETE qualifier to the SUBMIT command

failed

User Action~ Check the directory. Ine ~1ie may not be in ~ne
directory, or the batch job lacked delete access to the file.
Delete the file with the DCL DELETE command.
BPR -- CPU time limit exceeded, user job terminated
Explanation: The batch job ran longer than the
to the JOB command permitted.

/TIME

qualifier

User Action: Retry the batch job and increase the amount of
time using the /TIME qualifier.

A-1

(pu

ERROR MESSAGES
BPR -- I/O error
Explanation: The batch processor failed to read from or w~ite to
the virtual terminal, or the batch processor was unable to open
the batch file.
User Action: Retry the batch job. This may
error. See your operator or system manager.

indicate

system

BPR -- Virtual terminal I/O was aborted
Explanation:
aborted.

The task sending I/O to the

User Action:

None.

virtual

terminal

was

BPR -- Label label undefined
Explanation:
job.

The batch job specified a label that was not in the

User Action:
proper form.
with a colon

Check the job to see that the label is present in
The label must begin with a dollar sign ($) and end
(:}

BPR -- Log file directory not found - aborted batch job
Explanation: The SUBMIT command included the /NOPRINT qualifier,
but the batch job cannot find the directory for the batch log.
User Action:

See your system manager.

BPR -- Logon privilege violation
Explanation:

The $JOB command gave an incorrect UIC.

User Action: Check the command for proper syntax and retry the
job.
For nonprivileged users, the UIC in $JOB must match the
login UIC in effect when the SUBMIT command was entered.
BPR -- Output request from incorrect virtual terminal
Explanation:

System error.

User Action:

See your operator or system manager.

BPR -- Spawn failure
Explanation:

System error.

User Action:

See your operator or system manager.

BPR -- Specified maximum CPU time too large
Explanation: The largest amount of CPU time that
specified is 65535. minutes (1092 hours, 15. minutes)
User Action:

Speciry less CPU time.

A-2

may

ERROR MESSAGES
BPR -- Syntax error
Explanation: A command line in the batch job does not start with
a dollar sign ($), or special batch commands (Table 2-1) have
improper syntax.
User Action:
the job.

Check the batch file for proper

syntax

and

retry

BPR -- Syntax error -- $JOB does not appear first
Explanation: $JOB logs in the user batch job on
terminal and must appear first in the batch file.
User Action:

the

virtual

Edit the batch file so that $JOB appears first.

BPR -- Virtual terminal output too long for buffer
Explanation: A stream of characters from
was too long to fit in a storage buffer.

the

virtual

User Action: Make sure that the task outputs
LINE-FEED characters when performing terminal I/O.

A.1.2

Error Messages to the Operator's Console

BPR

Batch file input error
Explanation:

terminal

RETURN

and

BPR could not read from the batch file.

User Action: Check the batch file status.
in the directory.

The file may

not

BPR -- Batch job jobname still in progress
Explanation: System error. QMG attempted to start the batch job
while another job was in progress.
User Action:

Inform the system manager.

BPR -- Error during send to QMG

BPR

Explanation:

System error.

User Action:

Inform the system manager.

Illegal error

Explanation:

severity code n

System error.

User Action: Inform the system manager.
An SPR should be
submitted including the console output and any other relevant
information. If possible, reproduce the error.

A-3

ERROR MESSAGES
BPR -- Incorrect Emit Status Block (ESB) address returned by spawned task
Explanation:

System error.

User Action:

Inform the system manager.

BPR -- Log file close failure
Explanation:

BPR failed to close the log file.

User Action: Check the log file status. The device may
available or the file may not be in the directory.

not

The device may

BPR -- Log file open error
Explanation:

BPR failed to open the log file.

User Action: Check the log file destination.
write-locked.
BPR -- Log file output error
Explanation:

BPR failed to write to the log file.

User Action: Check the log file status. The device may
available or the file may not be in the directory.

not

BPR -- Output request from incorrect virtual terminal
Explanation:

System error.

User Action:

Inform the system manager.

BPR -- Unable to create virtual terminal

A.1.3

Explanation:

The system does not support virtual terminals.

User Action:

A new system generation is required.

Error Messages from the Card Reader Processor

The User Action suggested for these errors is directed to both
privileged
and
nonprivileged users.
In most cases where the
suggestion to see your operator or system manager is included, the
condition can only be corrected by a privileged user.
CRn -- Reader spooled
Explanation: The card reader has been initialized and
to read cards.
User Action:

None.

A-4

ready

ERROR MESSAGES
CRn -- Reader unspooled
Explanation: The card reader processor has been
can no longer be read.
User Action:

removed.

Jobs

None.

CRn -- Job (jobname) was entered in queue (queuename)
Explanation:
queue.

A job has been successfully read and entered

User Action:

None.

CRn -- Illegal $SUBMIT or $PRINT card - job flushing
Invalid card was " "
Explanation:

A syntax error was encountered.

User Action:
deck.

Repunch the control card

and

resubmit

your

card

CRn -- $PASSWORD card illegal or missing - job (jobname) flushing
Explanation:

A syntax error was encountered.

User Action:
deck.

Repunch the control card

and

resubmit

your

card

CRn -- Invalid account was given - job (jobname) flushing
Explanation: The account information tQken from the /USER:userid
qualifier and the $PASSWORD card do not match any entries in the
account file.
User Action: Inspect your control cards and see if your password
or userid was mispunched.
CRn -- Sequence number check - job (jobname) flushing
Invalid card was " ".
Explanation: The CRP read a card whose sequence number in
columns 72 through 80 was not larger than the sequence number of
the previous card.
User Action: Replace the $SUBMIT card with a $PRINT card to get
a listing of your card deck. Determine where your cards got out
of sequence.
CRn -- Job (jobname) flushing due to operator request
Explanation: An operator issued a command that aborted your
while it was being read.
User Action:

See your operator or system manager.

A-5

job

ERROR MESSAGES
CRn -- Queue (queuename) does not exist - job (jobname) flushing
Explanation: The queue specified for your job (either by default
or explicitly with the /QUEUE:queuename qualifier) does not
exist.
User Action: Repunch the $SUBMIT or $PRINT card
existing queue.

specify

CRn -- Queue (queuename) marked for delete - job (jobname) flushing
Explanation: The queue specified for your job
deletion and no new jobs may be entered into it.
User Action:

marked

for

See your operator or system manager.

CRn -- No queue file space available - job (jobname) flushing
Explanation: The queue file QUEUE.SYS is full and no
can be entered in any queues.
User Action: Wait until the queue file
reinitialized. Resubmit your card deck.

has

jobs

been

emptied

CRn -- Card reader not ready
Explanation: Usually, this message means that the hopper was
emptied while a job was being read. This message may also be
given if a pick check, read check, or stack check occurred.
User Action:

Check the card

reader.

hopper ann push the RF.SET hntton to

CRn

Illegal error message number

Put

~t<=1rt

cards

the

rPaning rignin,

nn - parameter address

Explanation:

System error.

User Action:

See your operator or system manager.

nnnnnn

Account file open error
Explanation:
opened.

System

error.

User Action:

See your operator or system manager.

The

account

file

could

not

could

not

CRn -- Account file close error
Explanation:
closed.

System

error.

User Action:

See your operator or system manager.

The

account

file

CRn -- Account record locked

Explanation:
not be read.

System error.

A record in the account

User Action:

See your operator or system manager.
A-6

file

could

ERROR MESSAGES
CRn -- Couldn't find physical LB
Explanation:

System error.

User Action:

See your operator or system manager.

CRn -- Account file read error nn
Explanation: System error.
account file.
User Action:

An error

occurred

reading

the

copying

the

See your operator or system manager.

CRn -- Card reader read error nn
Explanation:

An error occurred in reading a card.

User Action:

See your operator or system manager.

CRn -- Output file write error nn
Explanation: System error. An error occurred
contents of a card to the card image file.
User Action:

See your operator or system manager.

Crn -- Output file open error nn
Explanation:

The card image file could not be opened.

User Action:

See your operator or system manager=

CRn -- Output file close error nn
Explanation:

The card image file could not be closed.

User Action:

See your operator or system manager.

CRn -- Error code nn returned by QMG - function code of packet sent = nnn
Explanation:

System error.

User Action:

See your operator or system manager.

CRn -- Send directive failed - DSW=nn

User Action:

See your operator or system manager.

CRn -- Exiting due to fatal error
Explanation: An unrecoverable error condition occurred,
CRP to exit immediately.
User Action:

See your operator or system manager.

A-7

causing

ERROR MESSAGES
A.2

OUTPUT DESPOOLER ERROR MESSAGES

All of these messages indicate a FATAL exit status for the job. These
error messages from the output despooler task appear on the operator's
console and in the listing on the output device.
When these errors
occur, the despooler task prints the job flag pages first and then the
error messages on the first page of the listing.
The messages are preceded by the name of the output despooler
(desp,
in the following list), This name is derived from the name of the
output device owned by the despooler, such as, LPO: and TT2:.
I/O error code numbers are explained in the IAS/RSX-11
Reference Manual.

I/O

Operators

desp -- Attempt to space nn pages beyond eof on- f ilespec
Explanation: A
privileged
user's
START/PROCESSOR
attempted to start beyond the end of the specified file.
User Action:

command

Correct the command and retry.

desp -- I/O Error nn on file- filespec
Explanation: The task encountered an I/O error nn, which is
I/O error code number.
These codes are explained in
IAS/RSX-11 I/O Operations Reference Manual.
User Action:

Look up the error and take corrective

the
the

action~

desp -- Job limit of nn pages exceeded on file- filespec
Explanation: The PRINT command included the /PAGES:nn qualifier.
The job exceeded this limit.
User Action: Shorten the file or issue the PRINT command with
higher iimit.

desp -- Open error nn on file- f ilespec
Explanation: Tha task could not open the file named in ~ne error
message for output. The value nn is the I/O error code number.
These codes are explained in the IAS/RSX-11 I/O Operations
Reference Manual.
User Action: Check the directory listing for the
file.
Look up the error.

state

the

desp -- Print error nn on file- filespec
Explanation: The task could not print the file named in the
error message. The value nn is the I/O error code number. These
codes are explained in the IAS/RSX-11 I/O Operations Reference
Manual.
~User Action: Check the directory listing for the
file.
Look up the error.

A-8

state

the

ERROR MESSAGES
A.3

DCL AND MCR ERROR MESSAGES FROM QUEUE MANAGER COMMANDS

These error messages appear on your terminal as you issue DCL
commands.

MCR

The error message is preceded by the first
erroneous command. For instance, the message

the

three

letters

might result from several commands, including HOLD or
you might see either of the following error messages:

DELETE.

Thus,

first

-- JOB DOES NOT EXIST

HOL

JOB DOES NOT EXIST

DEL

JOB DOES NOT EXIST

If your CLI is MCR, the error message is also preceded
three letters of the command.

the

QUE -- JOB DOES NOT EXIST
The messages are listed in alphabetical order.
The User Action suggested for these errors is ~irected to both
privileged
and
nonprivileged users.
In most cases where the
suggestion to see your operator or system manager is included, the
condition can only be corrected by a privileged user.
corn -- Bad queue name
Explanation:
characters.

The

queue

User Action:
characters.

Try

name

new

queue

included

illegal

name.

Limit:

six

too

many

Radix-50

corn -- QMG not active
Explanation: The Queue Manager task is not active.
It may
stopped, aborted, not running, not installed, or the like.

User Action: Wait and retry the command.
return, see your operator or system manager.

not

QMG

does

corn -- Processor does not exist
Explanation:

A command named a device that is not set spooled.

User Action:

Retry the command with the proper device name.

com -- Directive failure
Explanation:

System error.

User Action:

See your operator or system manager.

A-9

ERROR MESSAGES
com -- Illegal argument value
Explanation: A command
qualifier (switch).
User Action:
command.

Check

specified

illegal

proper

value

range

for

argument
and

for

retype

the

too

many

com -- Bad processor name
Explanation:
characters.

The processor name includes

invalid

User Action: Retry the command with the proper processor name.
Names are limited to six Radix-SO characters. Print processors
must be named after the device the control, such as, LP2:
controlled by LP2. Batch processors must have names in the form
BAPn. Applications processors can have any legal name.
com -- I/O Error
Explanation:

System error.

User Action: Try again.
the error persists.

See your operator or system manager, if

com -- Job does not exist
Explanation: A command named a job that does not exist in the
form the command recognized or under the name the command
recognized. The job name includes UIC.
User Action: Issue SHOW QUEUE (QUE/LI). Determine the name and
status of the job.
Check for the proper command syntax and
retype the command.
com -- Operation inconsistent with job state
Explanation:
job state.

A command attempted action

inconsistent

with

the

User Action: Issue SHOW QUEUE (QUE/LI). Determine the status of
the job. Check for the proper syntax and retype the command.
com -- Queue does not exist
Explanation: A command named a queue that does not exist in
current system.

the

User Action: Issue SHOW QUEUE (QUE/LI). Retry the command with
the name of an existing queue.
See your operator or system
manager.

A-10

ERROR MESSAGES
com -- Queue file full
Explanation: The queue file [l,7]QUEUE.SYS on LB for RSX-llM
SP for RSX-llM-PLUS is full.

User Action: Wait and try again.
If the error message persists,
see your operator or system manager.
com -- Queue marked for delete
Explanation:
delete.

New jobs cannot be added

User Action:

Send the job to another queue.

queue

marked

for

has

been

com -- Redundant operation
Explanation:
done.

A command requested

User Action:

None.

A-11

operation

that

GLOSSARY

This

glossary

contains

brief

definitions

terms

used

the

RSX-llM/M-PLUS Batch and Queue Operations Manuai.
ACTIVE JOB
An active job is a job currently being processed.
APPLICATIONS PROCESSOR

An output despooler written by the user for a special purpose

or
specific job.
See your system manager for information on any
applications processors in your installation.
Applications
processors are treated like print processors in most cases.

A batch command is a CLT command
commands must be preceded by
position of the command line~
command.
BATCB~SPECTFTC

COMMAND

(RSX-llM:~PLU~

only)

J}c:itch-$PE!ciflc· C()mmc:tQds·· ar.e .. 9.0ltlltl'3nd$ that ~.I'e . . :independent ef:••yc;>ut
CLI . and designed .. ~xcru~ive1y .. f~~ -~at~·~ . prc:)C€s•sJtjtj~
·These
cpmmands can be llSed for logging t.he l>at:q}l jqb. on and off the
systE!m, ·.for includJ11gdat;Cl, >and ~()J' ~:requence .Gcmt.rol in the batch
jot>> when· ··ert:¢rs aI'e· return~<]. 'I'h-ey must.• be ptecedecl by. a: -doH•aoi::
s:i.g11 ($).
BATCH JOB (RSX-llM-PLUS

There are two kinds of hatch job:s
BATCH JOBS and QMG BATCH' Joas•.

BATCH LOG (RSX-llM-PLUS only)
Each QMG batch job produces a log: ''that ;·repr~'sen-ts:· 'the output that
"appeared" on the virtual terminal. You: can :sav•e a permanen·t
copy <of the log file. You can also include comments> in the log
- fil·e. Y·cu can ·prf-nt the· leg "fi1e.
Regardless of the number of user lobs· in the -OMG- job, the'r·e · will
be only one log. You c·an differenti·at·e· hetween use·r tab's- w·ithiJl
the log by using the log label field of the JOB command that logs
in each batch job.

Gloss-1

GLOSSARY

, ; . . : : ' .: ·:,. : ·: : ~

dn•<•Rsx ...1:J.~;!'~us·.ol1iY't:·•····~i::~~ads :6f·•·••••~··.1.1#:01J1~1:J~;·~1·1~· . :•:pC}J;$l?l9 ..•.. ¢<>rii~~:rid·k··

.•

·a~d . .•. datp .·f9;-: Pl'QS~~sJn9-~·: t~atsh..-sPE?.c:ffit?·· cqmmands, •GLl' commar}d$:{'
....a?l4 'd(l'f:.(1·· are Pl<!¢eq:
a :file CltlP: S\lbinitted :to: .. :the:· ··S;yst.ein :'::··,;~it;<

·Jl'l

execution.····

•· You··<10·• not hitv.ei tn.• h~ pr<l!l.O.t1t . wlle11 X() \)X".•. ;S~~~~ :i~t) •fs rllnf n()r/ .~.,
·oatch. ·... jql)$ ..,r~.~utr:7.:>a: . . Rnyi:; i:c:aT••· ~~pnf~I'.litl.·;t<>,::r·~·q .•·... · -~~~ph·.•·Rr?e.~~·~i::f.if3·!!

•.•

ils~s

vlttua1: term'inars··and · thus • .a:o~s

:_t:ermlh~~~.; .·>•·•
<.. ·..·..: :·.··•<·······
.. .. . ... ..

· n·ot ·:.ti~

-~:p ·· i•nt:~r·<!,9t;~y,~:.;

.......

,; .. \i' ,

.BATCH >pROC.ESSOR (~S~~~J.M~P~'l.Js _()n].y)

·_.·:K· ~~£c.H: !tii()9ksso1· -is. •a·:.ta.sk . :t~~·l:. . p~·#:~.•~.·~··: s·<>iTI~~n~ s: . . ~~a·:: ~:~t.~·.:.:t.tj.ii#;Bi$:i:
·and ·other ·:tasks·.-· li~#:rg . a

termi nail.

sof:!t.:ware< /t~rmtrtal · q.atl.~a;:«~f •1 vlitu~I:'

ff.

~-:=;:.::·c::·: . ··:·:·::·_·:·::."'-:::_.:; :·::·_:·'.'.

.BA'J.'C:ll: ':QUEUE
: BATCll queue refe.I"s t:.0- 'ithe ·ae,faliJ.t.· :queue• for biit·cl:( jo_bs~· A . hatch::·
· flo~fcas~} quEfU~' >ireif~r.s to ·:any qiJ'e!ue·.:·.~l)a~·· isi 'ti,$ed <to contain<a
list <>£ .bat«~:h j~l?:S.·· ·.·{A. quew~ ::J[lay :t>e ~!\l.§~;911~~· ·t.o ':Rt<??;~:. tQ.ari : one·

··P,i<>;c~~~:r.)

CLI
An acronym standing for Command Line Interpreter.
CLis act
interpreters between people and computer operating systems.

(See MCR and DCL.)
COMMAND

A comm2nd is =n instruction or request for the
to perform a particular action. See CLI.

nn~ r~t- inn

-,------··::1

c::vc::r~m

- - - -···
~

COMMAND LINE INTERPRETER
See CLI.
COMMAND QUALIFIER
A command qualifier (DCL) or job switch (MCR)
is a command
element preceded by a slash (/j
that alters the action of a
command. See FILE QUALIFIER.
DATA
On RSX--11McPLUS only, .any infonna1:ion. that is required. i11put toa
batch job. This {sa special definition us~d in batch processing·
on RSX•-11M-PLUS. The '.term "data"· includes not o'nly data in the
conventional sens,e .·.·pf· 1n·fo~ina~i6n fo l:>e p;.ocessed b)f a j~rogram
but also responses to pronlpts f:rom· CLI commands :or froin . indirect
commanq file$..
In fact~ cinythlng ·
except Gommands: -~ that
·would ··hav·e .to be ~ypea·· hYi . tl)e . . ·:. user: :i:l'l···. an 1nt~ractive session·· is·
called "data~·
·
·
·
DCL
DIGITAL Command Language.
An RSX-llM/llM-PLUS supported CLI
designed for ease of use. DCL uses English language words and
prompts you for necessary parameters. Compare with MCR.

Gloss-2

GLOSSARY
DEFAULT
A default is a value or condition that is
operating system and performed automatically.

assumed

the

For example: The default queue for the PRINT command is PRINT.
There are other queues available on the system, but, to place
your job in one of these other queues, you must specify the queue
in the PRINT command. If you do not specify one of these other
queues, your print job will default to the queue called PRINT.
DE SPOOLER
A print processor may also be called a despooler.
DEVICE
Any peripheral hardware or software connected to the processor
and capable of receiving, storing, or transmitting data. Line
printers and terminals are examples of record-oriented devices.
Magnetic tapes and disk devices are examples of mass-storage
devices. Terminal line interfaces and interprocessor links are
examples of communication devices.
DEVICE-SPECIFIC QUEUE
Some print queues have names derived from the names of the output
devices on the system, such as LPO, named after LPO:a These
queues are needed for certain system tasks that send print jobs
to line printers directly. These queues will usually send their
output to the printer they are named after, but they need not do
so.
DIGITAL COMMAND LANGUAGE
See DCL.
DISK
A disk is a high-speed,
RSX-llM/M-PLUS
systems
mass-storage device.

random access
use disks as

mass storage device.
their major form of

ERROR MESSAGE
Error messages are sent by the system when some action
requested fails.
Each error message identifies the particular part of
that detected the error.

Gloss-3

you
the

have

GLOSSARY
EXIT STATUS CODE
All system tasks on the RSX-llM/M-PLUS systems, DCL and MCR
commands, and utilities send a status-return code when they have
completed their operations. The codes are:
SUCCESS
WARNING
ERROR
SEVERE ERROR

Results should be as expected
Task succeeded but irregularities are
possible
Results unlikely to be as expected
One or more fatal errors, or ABORT
encountered

As a rough rule, you can expect that any error message you
receive on your terminal will reflect an exit status less than
success. Again, roughly, any error message tagged *FATAL* will
probably represent a status return of ERROR or SEVERE ERROR, and
any error message tagged *DIAG* will probably represent a status
return of WARNING.
These are by no means hard and fast
standards. Each system task follows its own rules.
You can use the ON and IF commands inside your
program responses to status-return codes job.

batch

job

FIELD
A field is a portion of a command or a command element.
FILE QUALIFIER
A file qualifier (DCL) or switch (MCR) is a command element
preceded by a slash (/) that alters or modifies the action of a
command as it affects that particular file. Depending upon the
position of the file qualifier (switch), all or only certain
fil~~

m~y

~ffpr.tPn.

S~P.

COMMAND QUALIFIER.

FORMS
All standard-length forms use form feeds, which are set on the
hardware.
All nonstandard forms use simulated form feeds, which
are set through the software by replacing the form feed character
with the appropriate number of line feeds.
Whether a form length is standard or not depends on whether it
can be set using hardware facilities on the line printer. i~ it
can be set on the line printer, then it is a standard form
length.
Your system manager can tell you what /FORM:n option to specify
in your PRINT command for any particular form. In this way, your
print jobs will be queued for the proper printer and held until
the proper forms are placed on the printer.
FORM FEED
A form feed is a character that directs the line printer to move
to the top of the next continuous-feed form page. The line
printer moves past the perforation in the paper to the top of a
new form.

Gloss-4

GLOSSARY
GENERAL QUEUE
Queues with names not derived from hardware devices.
Each
hardware
output device has a queue named after it.
See
DEVICE-SPECIFIC QUEUE. All other queues are general, including
the default PRINT queue, other print queues, and all batch
queues.
HARD-COPY TERMINAL
Terminals that
terminals.

output

paper

are

called

hard-copy

INDIRECT COMMAND FILES
A means of automatically passing commands for processing on an
RSX-llM/M-PLUS Operating System. Indirect command files remain
active at the terminal from which they are invoked.
Indirect
command file directives permit symbol substitution, testing
system functions, and such programming techniques as loops,
counters, and subroutines.
INSTALLATION
The installation is the full computer system (hardware and
software) at your location. This includes the operating system,
the programming languages, and all applications tasks, as well as
the computer and all its hardware devices.
INTERACTIVE TERMINAL
A standard hardware terminal with a keyboard from which you
type responses to prompts. Compare with VIRTUAL TERMINAL.

can

LINE PRINTER
An output device that prints files a line at a time.
Even if
your system does not have an actual hardware device of the
line-printer type, it will have some device designated as the
system output device and taking the part of the line printer.

LOG
A log is a record of activity. In this manual, the term
to a file produced by a batch processor. See BATCH LOG.

refers

LOGICAL PAGE
The line printer moves to the top of a new PHYSICAL PAGE each
time a form-feed character (CTRL/L) is encountered. If you use
the /LENGTH qualifier on the PRINT command, you define a LOGICAL
PAGE length. If the line printer does not encounter a form-feed
character within the length of the logical page, it will
automatically supply one at the end of the logical page, moving
the printer to the top of the next physical page.
LOGIN
The LOGIN command identifies you to the operating system and
informs the system that you have certain privileges and are using
a particular terminal.

Gloss-5

GLOSSARY
LOGOUT
The LOGOUT command informs the operating
finished using a particular terminal.

system

that

you

have

MCR
Monitor Console Routine.
An RSX-llM/llM-PLUS supported CLI.
Most MCR commands use mneumonics in strict syntax. See DCL.
NONPRIVILEGED USER
Nonprivileged users have access to most
facilities but cannot alter the system.

the

system's

OPERATING SYSTEM
An operating system is a set of tasks that collectively automate
the
management of computer resources to provide efficient
computer operation.
An operating system is used for user communication with the
computer, for program development, and for scheduling the use of
the central processing unit and its peripherals for efficiency.
OPERATOR
The person who is in direct charge of the computer.
OPERATOR'S CONSOLE
A hard-copy terminal, usually located near the computer, used by
the operator.
This terminal has the logical name CO: and
records certain system information.
PERIPHERAL DEVICES
Any unit, distinct from the CPU and memory, that can provide the
system with input or accept output from it, is called a
peripheral device, or peripheral.
PHYSICAL PAGE
A physical page is
-

--~-

___

.._~

pe.ti.o.tdl...Luu

_ _ ..:1

duu

the

.._L._

t.uc

part

----.&..

11cA1..

printer

___
,c _ _ _ .._.:__
k"t::1.L.v1.a1...Lv11.

form

.... """,:i-"'.,...,:i

u1..a11ua1.u

between
,

one

.;..,.,...,_Y"'\.;"""+-~W""

..........

.t' ............. ..

paper has a physical page length of 66 lines. Each time the line
printer encounters a form-feed character (CTRL/L), the line
printer moves the paper to the top of the next physical page.
Compare LOGICAL PAGE.
PRINT COMMAND
The PRINT command queues files for printing on a line printer.
The PRINT command may also be used to enter jobs in queues for
other output devices, such as plotters or punches.
The PRINT
command is to print jobs as the SUBMIT command is to batch jobs.
PRINT PROCESSOR
Each spooled output device has a print processor, a task that
attaches the device and directs output to it. The Queue Manager
handles the orderly printing of files through
the
print
processor.

Gloss-6

GLOSSARY
PRINT QUEUE
PRINT queue refers to the default queue for print jobs. A print
{lowercase) queue refers to any queue that is used to contain a
list of print jobs.
PRIORITY
Priority is a rank assigned to a task to determine its precedence
in obtaining system resources when the task is run. The default
priority for a task is 50.
QMG jobs are also assigned a
priority. The default priority for a job is 50.
PRIVILEGED USER
Privileged users can alter the operating system through
of privileged commands.

the

use

QMG PRINT JOB
A QMG print job consists of one or more files to be printed at
the same time.
Jobs in a QMG print job go to the same line
printer in the order they were listed and without interruption.
The print job has a name derived from the name of the first file
in the job or from a name given in the PRINT command.
QUALIFIER
See COMMAND QUALIFIER and FILE QUALIFIER.
QUEUE
A queue is a waiting line of jobs that are scheduled or processed
according to system or user priorities.
QUEUE FILE
A disk file used by the Queue Manager for storage of control
information and entries for all batch and print processors, all
jobs and files to be processed, and all queues. On RSX-llM this
file is LBO: [l,7]QUEUE.SYS and on RSX-llM-PLUS the file is
SPO: [l,7]QUEUE.SYS. Since this information is retained on disk,
your job will not be lost should the system stop operating.
QUEUE MANAGER
The Queue Manager (QMG) is a system program that provides for the
orderly processing of print and (on RSX-llM-PLUS only) batch
jobs.

Gloss-7

GLOSSARY

·· ,. :, . "'" :- _'"'i:{U:iL:~cL ,,. , .,_,_, ',''',.',>~.·;~'2:E~-" ,» ,, . , . -,--;,/)( ,~:;
..• .~El r~~ ~'~.f~ ~~~1~i liaii:ci~·!~§fi, · · · .·. ~.!#.'t:ll~i: • ·go~........ ········· i<~h~. . 2tl11t¢'1i... 'i:J~;~1

-<~-~:OY.:~~PJ/;/-~9!!1i<?,~F_PJ~~~~J!p~~

·::.:

·.~h~-r:l, ·::t:!f r(;)P,·~--" ~'7~ »-.~!l-C,P'1.J1'l·~:er~<1t···,,,,_,·_·.'th~"f:,·::P'fp~,id,t;!,.·.:•. .~.-,/~~'at1~.- •. . '9,f ·:p.r.~g,E~~~!'~<J

"'r·.~:r~-otri"'::~·~'-~p()\l'.l$~:.:A·ti~g< ·th.e: ·p~t<!·r-~>,j"

. -'liN

·,p·F,:'g;<;l .

·, 'wJ:l.en.: ::•:i1>$~<f ;;:,wl't:i:r> \Eile>•'·c·c>1nm:" · : ·

SEVERE ERROR
Exit status code. This is usually returned when one or more
fatal errors are encountered or a task is aborted. When used in
a sequence control command, this term should be typed as a single
word: SEVEREERROR.
SPOOL
This is an acronym for Shared Peripheral Operations On Line.
It
refers to the process of sending output to a peripheral device,
particularly a line printer, in an orderly fashion.
Many users and tasks may be directing output to the line printer
at the same time. Rather than print three lines of one file and
then two of another, as might happen if the output was passed
directly to the line printer, the output is sent to a mass
storage device -- usually a disk -- to be saved in separate
files.
The process of saving files on disk in this fashion is called
spooling.
The orderly transfer of these files from the disk to
the output device is called despooling.
SPOOLED DEVICE
A spooled device is a line printer or other output device under
control of the Queue Manager. Spooled devices are initialized
with certain attributes.

SUCCESS
Exit status code.

Results should be as expected.

SYNTAX
Syntax is the form that a command must follow. Misspelled words
are the most common syntax errors, but misplaced delimiters are
also common.
SYSTEM MANAGER
The person responsible for setting
RSX-llM/M-PLUS Operating System.

Gloss-8

policies

for

using

the

GLOSSARY
TERMINAL
terminal is a hardware device with two functions:
(1)
sending
input to the operating system from a keyboard and displaying it
and {2} receiving output from the operating system and displaying

it.

UFD
All files on mass storage devices are cataloged in User File
Directories, or UFDs.
The UFD is a file listing all the files
included in the Directory. The UFD is a two-number code in the
form [g,m] that is included in every file specification, either
explicitly or by default, and that the file system uses to locate
the file.
In most cases, the UFD will be the same
as
the
User
Identification Code, or UIC, under which you logged in. See UIC.
UIC
User Identification Code.
Each RSX-llM/llM-PLUS user has a
two-number identification code enclosed in brackets that is used
{with password) for logging in.
The number is in the form
[g,m,], with g g1v1ng the user's group number and m giving the
user's member number5

WARNING
Exit status code.
possible.

The task

succeeded,

Gloss-9

but

irregularities

are

INDEX

Active job,
definition, Gloss-1
/AF job switch,
QUE /MOD command, 2-20
SUB command, 3-iS
/AF switch,
PRI command, 2-6
/AFTER job qualifier,
SET QUEUE command, 2-20
/AFTER qualifier,
PRINT command, 2-6
SUBMIT command, 3-15
Applications Processor,
See Queue Manager {QMG)
special applications,
definition, Gloss-1

/BATCH qualifier,
SHOW QUEUE command, 2-16
Batch-specific command, 3-2
command summary, 3-3
definition, Gioss-i
line continuation, 3-3
BPR, 3-1
See Batch processor
/BR switch,
QUE /LI command, 2-15
/BRIEF qualifier,
SHOW QUEUE command, 2-15

Batch command,
CLI commands, 3-2
definition, Gloss-1
dollar sign, 1-8, 3-2
format, 3-2
labeli 3-2
line continuation, 3-2
Batch job,
See also QMG batch job
See also User batch job
allocating device,
ALLOCATE command, 3-13
card deck, 3-23
card reader input spooling,
example, 3-24
deallocating device,
DEALLOCATE command, 3-14
definition, Gloss-1
dismounting volume,
DISMOUNT command, 3-14
mounting volume,
MOUNT command, 3-13
queuing, 3-14
scheduling, 1-7
submitting, 1-7
Batch log file, 3-2, 3-19
definition, Gloss-1
example, 3-20 to 3-23
line identifiers,
DATA, 3-20
SKIP, 3-20
TERM, 3-20
Batch processing, 1-7
definition, Gloss-2
Batch orocessor.
defi~ition, Gioss-2

Index-1

Card deck,
example, 3-24
format,
$EOJ, 3-24
$JOB, 3-24
$PASSWORD card, 3-24
$PRINT card, 3-24
$SUBMIT card, 3-24
sequence field, 3-26
Card reader input spooling,
3-23
Card Reader Processor (CRP),
3-23
error recovery, 3-27
operation, 3-27
/CO file switch,
PRI command, 2-6
QUE /MOD command, 2-21
/CO job switch,
PRI command, 2-4
QUE /MOD command, 2-20
Command Line Interpretor,
See CLI
definition, Gloss-2
Command summary, 4-1
Comment in batch job,
example, 3-12
format, 3-12
CONTINUE command,
See also ON and IF commands
format, 3-8
/COPIES file qualifier,
PRINT command, 2-6
SET QUEUE command, 2-21

Data, batch job,
definition, Gloss-2

INDEX

DATA command, 3-5
example, 3-6 to 3-7
format, 3-6
qualifiers, 3-6
DCL (DIGITAL Command
Language),
definition, Gloss-2
/DE file switch,
PR! command, 2-6
SUB command, 3-17
/DEL file switch,
QUE /MOD command, 2-21
DELETE command,
example, 2-11
format, 2-10
/DELETE file qualifier,
PRINT command, 2-6
SET QUEUE command, 2-21
SUBMIT command, 3-17
Despooler,
definition, Gloss-3
/DEVICE qualifier,
PRINT command, 2-6
SHOW QUEUE command, 2-15
/DOLLARS qualifier,
DATA command, 3-6

/FO job switch,
QUE /MOD command, 2-20
/FO switch,
PR! command, 2-5
QUE /LI command, 2-16
Form,
special hardcopy, 1-2
Forms,
definition, Gloss-4
/FORMS job qualifier,
SET QUEUE command, 2-20
/FORMS qualifier,
PRINT command, 2-5
QUE /LI command, 2-16
/FU switch,
QUE /LI command, 2-15
/FULL qualifier,
SHOW QUEUE command, 2-15

GOTO command, 3-8
See also ON and IF commands
example, 3-9
format,
label, 3-9

/EN switch,
QUE /DEL command, 2-10
QUE /LI command, 2-16
/ENTRY qualifier,
DELETE command, 2-10
SHOW QUEUE command, 2-16
EOD command,
format, 3-7
EOJ command,
format, 3--5
Exit Status Code,
definition, Gloss-4

/HO job switch,
SUB command, 3-16
/HO switch,
PR! command, 2-4
HOLD command,
format,
- - ~ - •.}'•
Clll-1.

- • · - '- - - f
11UlllUC1.

'1
'1 '1
£.-£.£.

job name, 2-22
/HOLD qualifier,
PRINT command, 2-4
SUBMIT command, 3-16

/FI file switch,
QUE /MOD command, 2-21
/FI switch,
QUE /DEL command, 2-11
/FILE POSITION file qualifier,
SET-QUEUE command, 2-21
/FILE POSITION qualifier,
DELETE command, 2-11
/FILES qualifier,
SHOW QUEUE command, 2-15
/FL switch,
PRI command, 2-5
/FLAG PAGE qualifier,
PRINT command, 2-5

Index-2

IF command,
See also STOP, CONTINUE,
GOTO commands
example, 3-12
format, 3-11
Indirect command file,
definition, Gloss-5
example; 3-13
format, 3-13
Interactive terminal,
definition, Gloss-5

INDEX

/JU switch,

/LOWERCASE qua11tier,
PRINT command, 2-4

PRI command, 2-6
Job,
deleting, 2-10
holding, 2-1
modifying, 2-1
releasing, 2-1
JOB command, 3-3
example, 3-4
format, 3-4
qualifiers, 3-4
/JOBCOUNT job qualifier,
SET QUEUE command, 2-20
/JOBCOUNT qualifier,
PRINT command, 2-3
Jobname= job switch,
SUB command, 3-16
Jobname= log file switch,
SUB command, 3-17
Jobname parameter,
DELETE command, 2-10
Jobname switch,
QUE /LI command, 2-16
Jobname= switch,
PRI command, 2-4
/JOB PAGE qualifier,
PRINT command, 2-6

/NAME log file qualifier,
SUBMIT command, 3-17
/NAME qualifier,
$PRINT card, 3-25
SHOW QUEUE command, 2-16
$SUBMIT card, 3-25
SUBMIT command, 3-16
/NAME:jobname qualifier,
PRINT command, 2-4
/NOCOPY qualifier,
DATA command, 3-6
/NOLO job switch,
QUE /MOD command, 2-21
/NOLOW switch,
PRI command, 2-4

ON command,
See also STOP, CONTINUE,
GOTO commands
default setting, 3-9
example, 3-10
format, 3-10
/OWNER U!C qualifier,
SHOW-QUEUE command, 2-16

/LE job switch,
QUE /MOD command, 2-20
/LE switch,
PRI command, 2-5
/LENGTH job qualifier,
SET QUEUE command, 2-20
/LENGTH qualifier,
PRINT command, 2-5
/LI switch,
QUE /LI command, 2-15
/LI:B switch,
QUE /LI command, 2-16
Line printer,
definition, Gloss-5
/LI:P switch,
QUE /LI command,
2-15 to 2-16
/Tr\
/J...JV

..::-1...
JVU

/PA job switch,
QUE /MOD command, 2-20
/PA switch,
PRI command, 2-4
/PAGE COUNT job qualifier,
SET-QUEUE command, 2-20
/PAGE COUNT qualifier,
PRINT command, 2-4
$PASSWORD card,
format, 3-27
PRI command,
file switches, 2-3
format, 2-3

. : _,_ -··:

-·•~'--1..

j VU

;:)W.Ll..~Ut

QUE /MOD command, 2-20
/LO log file switch,
SUB command, 3-17
/LOGFILE qualifier,
SUBMIT command, 3-17
Logical page,
definition, Gloss-5
/LOW switch,
PRI command, 2-4
/LOWERCASE job qualifier,
SET QUEUE command, 2-20

~-t...--

;:,w .L 1..\,;lJt::;:) I

. . . -,

.G-:J

/PRIN log file switch,
SUB command, 3-18
$PRINT card,
command qualifiers, 3-26
See PRINT command
format, 3-26
PRINT command, 1-3, 2-2
command qualifiers, 2-3
definition, Gloss-6
example, 2-7
file qualifiers, 2-3

Index-3

INDEX

PRINT command (Cont.)
format, 2-3
processing, 1-4 to 1-6
Print job,
definition, Gloss-7
queued by system tasks,
DCL COPY command, 2-12
maps, logs, listings, 2-12
PIP, 2-12
PIP line printer, 2-12
queued by user tasks,
opening file on LPn:, 2-14
.PRINT, 2-13
PRINT command, 2-13
submission notification, 2-2
/PRINT log file qualifier,
SUBMIT command, 3-18
Print processor, 1-3
See also Despooler
definition, Gloss-6
/PRINT qualifier,
SHOW QUEUE command: 2-lfi
/PRIO job switch,
QUE /MOD command, 2-20
SUB command, 3-17
/PRIO switch,
PRI command, 2-5
Priority,

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

~oF;n;~;An
.............................. ....

QUE /MOD command (Cont.)
switches, 2-19
QUE /REL command,
format,
entry number, 2-23
job name, 2-23
Queue, 1-1
assignments, 1-2
BATCH queue,
definition, Gloss-2
definition, Gloss-7
device,
definition, Gloss-3
device-specific, 1-2,
Gloss-3
disk file,
definition, Gloss-7
disk file (QUEUE.SYS),
RSX-1 lM, 1-1
RSX-llM-PLUS, 1-1
displaying information, 2-1

genP.ral:

1-?,:

Gloss-5

job,
holding, 2-1
releasing, 2-1
status,
altering, 2-1
PRINT,

~1~~~-~
.....
'
~

,,_,..-....,

/PRIORITY job qualifier,
SET QUEUE command, 2-20
/PRIORITY qualifier,
PRINT command, 2-5
SUBMIT command, 3-17

Queue Manager (QMG), 1-1
definition, Gloss-7
dequeuing jobs, 2-1
output, 1-3
queuing jobs, 2-1
special applications, 1-2
/QUEUE qualifier,
SUBMIT command, 3-17
Queuename job switch,
SUB command, 3-17
Queuename parameter,
DELETE command, 2-10
Queuename switch,
PR! command, 2-4
/QUEUE:queuename qualifier,
PRINT command, 2-4

QMG batch job, 1-7, 3-2
definition, Gloss-7
QUE /DEL command,
format, 2-10
QUE /HO command,
format,
entry number, 2-22
job name, 2-22
QUE /LI command, 2-14
batch queue, 1-9
display, 2-16 to 2-17
format, 2-15
print queue, 1-9
QUE /LI display, 1-10
switches, 2-15
QUE /LI:DEV command,
format, 2-18

/RE job switch,
QUE /MOD command, 2-21
SUB command, 3-16
RELEASE command,
format,
entry number, 2-23
job name, 2-23
/RES switch,
PR! command, 2-5
/RESTART job qualifier,
SET QUEUE command, 2-21

QUE /MOD command,
example, 2-21
file format,
switches, 2-19
job format,

Index-4

INDEX

/RESTART qualifier,
PRINT command, 2-5
SUBMIT command, 3-16

Sequence Control Commands,
See also STOP, CONTINUE,
GOTO and SET ON
definition, Gloss-8
/SEQUENCE qualifier,
$SUBMIT command, 3-25
SET command,
format, 3-11
SET QUEUE command,
example, 2-21
file format,
qualifiers, 2-19
job format,
qualifiers, 2-19
SHOW PROCESSOR command,
format, 2-18
SHOW QUEUE command, 2-14
batch queue, 1-9
display, 2-16 to 2-17
format, 2-15
print queue, 1-9
qualifiers, 2-15
SHOW QUEUE display, 1-10
Spool,
card reader input spooling,
3-23
definition, Gloss-8
spooling output, 2-1
Spooled device, 1-3, 2-1
definition, Gloss-8
line printer, 1-3
output, 1-3
Status code, 3-11
ERROR, 3-10
definition, Gloss-4
SEVERERROR, 3-10
definition, Gloss-4
SUCCESS, 3-10
definiton, Gloss-4
WARNING, 3-10
definition, Gloss-4
STOP command,
See also ON and IF commands
format, 3-8
SUB command, 3-14
example, 3-18 to 3-19
file switches, 3-15
format, 3-15
job switches, 3-15
log file switches, 3-15
$SUBMIT card,
command qualifiers, 3-25

$SUBMIT card(Cont.)
format, 3-25
SUBMIT command, 1-7, 3-14
command qualifiers, 3-15
definition, Gloss-8
example, 3-18 to 3-19
file qualifiers, 3-15
format, 3-15
log file qualifiers, 3-15

/TIME qualifier,
JOB command, 3-4
/TR file switch,
PRI command, 2-6
SUB command, 3-17
/TRANSFER file qualifier,
PRINT command, 2-6
SUBMIT command, 3-17
Transparent spooling,
definition, Gloss-9
(EDT) WRITE command, 2-1
/TYPE keyword,
ALLOCATE command, 3-14

Index-5

[uic] switch,

QUE /LI command, 2-16
/UPPERCASE job qualifier,
SET QUEUE command, 2-21
/UPPERCASE qualifier,
PRINT command, 2-4
User batch job, 1-7
batch chain, 1-7
command, 3-2
comment, 1-8
creating, 3-1
data, 3-2
definition, Gloss-9
example, 1-8
/USER qualifier,
$PRINT card, 3-25
$SUBMIT card, 3-25

Virtual terminal,
definition, Gloss-9
login UIC,
default, 3-1
privileged user, 3-1

/WAIT keyword,
MOUNT command, 3-14

RSX-llM/M-PLUS
Batch and Queue
Operations Manual
AA-L671A-TC

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

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

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

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

D
D
D
D
C
D

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

Organization
Street
City _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __

State _ _ _ _ _ _ Zip Code _ _ _ _ __
or Country

DoNotTear-FoldHereandTape -

No Postage
Necessary
if Mailed in the
United States

1111

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

I
I

BSSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 0306~

· -

Do Not Tear - Fold Here

I
I
lj
1