OPRCOM
TOPS-20
TOPS-20
Operator's Command Language
Operator's Command Language
Reference Manual
Reference Manual
| Electronic Distribution
July 1990
| July 1990
This manual describes all operator
commands that use the Operator Interface
Command Language (OPR), LCP, Privileged
Commands, and PTYCON commands.
Change bars in margins indicate material
that has been added or changed since the
previous release of this manual.
Bullets indicate that material has been
deleted.
This manual supersedes the manual of the
| same name and order number, AA-H600C-TM.
OPERATING SYSTEM:
OPERATING SYSTEM: TOPS-20 (KL Model B) Version 7.0
SOFTWARE:
SOFTWARE: GALAXY Version 6
digital equipment corporation
maynard, massachusetts
First Printing, January 1980
Updated, April 1982
Updated, December 1982
Revised, September 1985
Revised, June, 1988
| Software Update Tape 3, July 1990
The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
and may only be used or copied in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by Digital Equipment Corporation or its
affiliated companies.
Copyright C 1980, 1982, 1985, 1988, 1990 Digital Equipment
Corporation.
All Rights Reserved.
Printed in U.S.A.
The Reader's Comments form on the last page of this document requests
the user's critical evaluation to assist in preparing future
documentation.
The following are trademarks of Digital Equipment Corporation:
CI DECtape LA50 SITGO-10
DDCMP DECUS LN01 TOPS-10
DEC DECwriter LN03 TOPS-20
DECmail DELNI MASSBUS TOPS-20AN
DECnet DELUA PDP UNIBUS
DECnet-VAX HSC PDP-11/24 UETP
DECserver HSC-50 PrintServer VAX
DECserver 100 KA10 PrintServer 40 VAX/VMS
DECserver 200 KI Q-bus VT50
DECsystem-10 KL10 ReGIS
DECSYSTEM-20 KS10 RSX d i g i t a l
CONTENTS
PREFACE
CHAPTER 1 INTRODUCTION
CHAPTER 2 THE OPERATOR INTERFACE, OPR
2.1 INTRODUCTION TO THE OPERATOR INTERFACE . . . . . . 2-1
2.2 RUNNING OPR AND EXITING FROM IT . . . . . . . . . 2-2
2.2.1 Issuing OPR Commands to and from Remote Stations 2-5
2.2.2 Multiple OPRs on the System . . . . . . . . . . 2-6
2.3 RUNNING SEMI-OPR . . . . . . . . . . . . . . . . . 2-6
2.3.1 SEMI-OPR Limitations and Restrictions . . . . . 2-7
2.3.2 SEMI-OPR Commands . . . . . . . . . . . . . . . 2-8
2.4 OPR COMMAND FEATURES . . . . . . . . . . . . . . . 2-8
2.4.1 ? (Question Mark) - Listing Available Commands . 2-9
2.4.2 ESCape - Using Recognition . . . . . . . . . . 2-11
2.4.3 - Reprinting Faulty Commands . . . . 2-13
2.4.4 Continuing OPR Command Lines . . . . . . . . . 2-14
2.5 OPR MESSAGES . . . . . . . . . . . . . . . . . . 2-15
2.5.1 ORION-To-OPR Messages . . . . . . . . . . . . 2-15
2.5.2 OPR Error Messages . . . . . . . . . . . . . . 2-16
CHAPTER 3 OPR COMMAND DESCRIPTIONS
ABORT - Aborting Jobs . . . . . . . . . . . . . . 3-2
ALIGN - Aligning Printer Paper . . . . . . . . . . 3-8
BACKSPACE - Backspacing Files by Page . . . . . 3-13
CANCEL - Canceling Requests . . . . . . . . . . 3-18
CLOSE - Closing the Log Buffer File . . . . . . 3-22
CONTINUE - Restarting a Stopped Job . . . . . . 3-24
DEFINE - Defining a Node . . . . . . . . . . . . 3-30
DEFINE - Defining Aliases for Printer
Specifications . . . . . . . . . . . . . . . . . 3-34
DISABLE - Stopping System Process Features . . . 3-39
DISMOUNT - Dismounting a Structure or Tape-drive 3-48
ENABLE - Allowing System Process Features . . . 3-52
ENTER - Entering Another Command Level . . . . . 3-61
EXIT - Leaving OPR Level . . . . . . . . . . . . 3-63
FORWARDSPACE - Forward Spacing into Pages . . . 3-64
HELP - Getting Help on OPR Commands . . . . . . 3-68
HOLD - Holding Job Requests in the Queue . . . . 3-70
IDENTIFY - Identifying Tape Mounts . . . . . . . 3-73
MODIFY - Modifying the Priority of Requests . . 3-77
MOUNT - Mounting Structures . . . . . . . . . . 3-80
NEXT - Specifying the Next Request to Run . . . 3-83
iii
PUSH - Pushing Out of OPR Command Level . . . . 3-88
RELEASE - Releasing Job Requests Held in the
Queue . . . . . . . . . . . . . . . . . . . . . 3-90
REPORT - Reporting Comments to SYSERR . . . . . 3-93
REQUEUE - Rescheduling Job Requests . . . . . . 3-95
RESPOND - Responding to Messages . . . . . . . . 3-101
ROUTE - Routing Output Between Nodes . . . . . . 3-104
SEND - Sending Messages . . . . . . . . . . . . 3-112
SET - Setting Parameters for System Devices . . 3-115
SET BATCH-STREAM - Setting Batch Stream
Parameters . . . . . . . . . . . . . . . . . . 3-116
SET CARD-PUNCH - Setting Card Punch Parameters 3-119
SET DISK-DRIVE - Setting Disk-Drive Parameters 3-123
SET JOB - Setting Characteristics for Jobs . . 3-126
SET NODE - Setting Node Parameters . . . . . . 3-128
SET ONLINE - Setting a Device On-Line . . . . 3-132
SET PAPER-TAPE-PUNCH - Setting
Paper-Tape-Punch Parameters . . . . . . . . . 3-134
SET PLOTTER - Setting Plotter Parameters . . . 3-137
SET PORT CI - Controlling the CI port . . . . 3-140
SET PORT NI - Controlling the NI Port . . . . 3-145
SET PRINTER - Setting Line Printer Parameters 3-147
SET SCHEDULER - Setting System Performance . . 3-153
SET STRUCTURE - Setting Structure Parameters . 3-156
SET TAPE-DRIVE - Setting Tape-Drive Parameters 3-161
SHOW - Displaying System Information . . . . . . 3-167
SHOW ALIAS - Displaying Printer Alias Names . 3-168
SHOW BROADCAST-MESSAGES - Displaying Status of
Remote Broadcasting of ORION Messages . . . . 3-173
SHOW CLUSTER-GALAXY-LINK-STATUS - Displaying
Cluster Link Status . . . . . . . . . . . . . 3-175
SHOW CONFIGURATION - Displaying Disk Drive
Configuration . . . . . . . . . . . . . . . . 3-177
SHOW CONTROL-FILE - Displaying Batch Control
Files . . . . . . . . . . . . . . . . . . . . 3-180
SHOW MESSAGES - Displaying Outstanding
Messages . . . . . . . . . . . . . . . . . . . 3-182
SHOW OPERATORS - Displaying Operators on the
System . . . . . . . . . . . . . . . . . . . . 3-184
SHOW PARAMETERS - Displaying Device Settings . 3-187
SHOW QUEUES - Displaying Queued Job Requests . 3-193
SHOW ROUTE-TABLE - Displaying Node Routing
Tables . . . . . . . . . . . . . . . . . . . . 3-197
SHOW SCHEDULER - Displaying the System
Scheduler . . . . . . . . . . . . . . . . . . 3-199
SHOW STATUS - Displaying Device/System
Information . . . . . . . . . . . . . . . . . 3-201
SHOW TIME - Displaying Date and Time . . . . . 3-211
SHUTDOWN - Terminating Device Scheduling . . . . 3-212
START - Starting Device Scheduling . . . . . . . 3-217
STOP - Stopping Devices Temporarily . . . . . . 3-222
SUPPRESS - Suppressing Printer Form-Feeds . . . 3-227
iv
SWITCH - Switching Tape Drives and Volids . . . 3-231
TAKE - Executing OPR Commands Automatically . . 3-233
UNDEFINE - Removing Structure Parameters . . . . 3-235
WAIT - Controlling Input from Batch Jobs . . . . 3-237
CHAPTER 4 LCP COMMANDS
4.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . 4-1
4.2 LOADING AND DUMPING LAT TERMINAL SERVERS . . . . . 4-3
4.3 OPR COMMANDS AVAILABLE IN LCP . . . . . . . . . . 4-3
4.4 LCP COMMANDS . . . . . . . . . . . . . . . . . . . 4-5
CLEAR - Clearing LAT host parameters . . . . . . 4-8
SET - Setting LAT host parameters . . . . . . 4-11
SHOW - Displaying LAT Host and Terminal Server
Parameters . . . . . . . . . . . . . . . . . . 4-14
START - Making the LAT Host Available . . . . 4-19
STOP - Making the LAT Host Unavailable . . . . 4-20
ZERO - Resetting LAT Counters to Zero . . . . 4-21
CHAPTER 5 ^E PRIVILEGED COMMANDS
5.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . 5-1
5.2 PRIVILEGED COMMAND DESCRIPTIONS . . . . . . . . . 5-2
^ECEASE - Scheduling System Shutdown . . . . . . . 5-3
^ECREATE - Creating/Removing Directories . . . . . 5-8
^EDEFINE - Defining and Deleting System Logical
Names . . . . . . . . . . . . . . . . . . . . . 5-46
^EEDDT - Debugging the EXEC . . . . . . . . . . 5-49
^EPRINT - Print Directory Parameters . . . . . . 5-50
^EQUIT - Halting the EXEC . . . . . . . . . . . 5-55
^ESEND - Sending Messages to Users Immediately . 5-57
^ESET - Setting Job, System, and Terminal
Parameters . . . . . . . . . . . . . . . . . . . 5-59
^ESPEAK - Giving Commands To SYSJOB . . . . . . 5-71
CHAPTER 6 PTYCON COMMAND LANGUAGE
6.1 INTRODUCTION TO PTYCON . . . . . . . . . . . . . . 6-1
6.2 STARTING PTYCON . . . . . . . . . . . . . . . . . 6-1
6.3 COMMUNICATION WITH PTYCON AND ITS SUBJOBS . . . . 6-4
6.3.1 Subjobs . . . . . . . . . . . . . . . . . . . . 6-4
6.3.2 Creating Subjobs . . . . . . . . . . . . . . . . 6-6
6.3.3 Communicating with Subjobs through PTYCON . . . 6-6
6.3.4 Communicating Directly with Subjobs . . . . . . 6-9
6.3.5 Subjob Output . . . . . . . . . . . . . . . . 6-11
6.3.6 Logging Out Subjobs . . . . . . . . . . . . . 6-12
6.4 PTYCON COMMAND FEATURES . . . . . . . . . . . . 6-13
6.4.1 Listing Available Commands and Arguments with a
Question Mark . . . . . . . . . . . . . . . . 6-13
v
6.4.2 Using Recognition Input . . . . . . . . . . . 6-14
6.5 PTYCON COMMAND DESCRIPTIONS . . . . . . . . . . 6-14
ACCEPT - Accepting Output on Your Terminal . . 6-16
BELL - Sounding Bell for Output Waiting . . . 6-18
CONNECT - Connecting to a Subjob . . . . . . . 6-19
DEFINE - Defining a Subjob . . . . . . . . . . 6-21
DISCARD - Eliminating Subjob Output . . . . . 6-23
EXIT - Leaving PTYCON Command Level . . . . . 6-25
GET - Executing an Auto-File . . . . . . . . . 6-27
HELP - Printing PTYCON Commands . . . . . . . 6-30
KILL - Killing PTYCON Subjobs . . . . . . . . 6-31
LOG - Recording Interactions with PTYCON . . . 6-33
PUSH - Performing Tasks at EXEC Level . . . . 6-35
REDEFINE - Changing the PTYCON ESCape Character 6-37
REFUSE - Refusing Output from Unconnected
Subjobs . . . . . . . . . . . . . . . . . . . 6-38
SAVE - Recording Input to PTYCON Subjobs . . . 6-40
SILENCE - Silencing Output to Your Terminal . 6-42
WHAT - Displaying the Status of Subjobs . . . 6-44
6.6 PTYCON WARNING AND ERROR MESSAGES . . . . . . . 6-46
INDEX
TABLES
5-1 Summary of ^ECREATE Subcommands . . . . . . . . 5-12
vi
vi
PREFACE
PREFACE
_______ __________ _______ ________
The commands described in the TOPS-20 Operator's Command Language
_________ ______
Reference Manual are arranged in an alphabetical order within the
command language being described: OPR, ^E privileged commands, or
PTYCON.
This manual is designed primarily for the beginning operator as well
as the experienced operator who needs additional information about the
various TOPS-20 operator commands. It assumes that the reader has
OPERATOR, SEMI-OPERATOR, or WHEEL privileges and knows how to login as
an operator.
This manual assumes that you, the operator, have read all or parts of
the following manuals:
_______ ______ _____
TOPS-20 User's Guide
_______ __________ _____
TOPS-20 Operator's Guide
In addition, you may need to reference the following manuals for
information related to the operational tasks you must perform:
_______ __ _____ _ ____________ _____
TOPS-20 KL Model B Installation Guide
_______ _________ _____
TOPS-20 Utilities Guide
_______ ________ _________ ______
TOPS-20 Commands Reference Manual
_______ ___ _____________________ ______
TOPS-20 IBM Emulation/Termination Manual
__________ _______ ______ ___ _____ ______ ___ __________ _____
DECnet/SNA TOPS-20 Remote Job Entry User's and Operator's Guide
__________ _______ __________ _____
DECnet/SNA Gateway Management Guide.
________________ ______ _________ _____
DECnet-20/PSI-20 System Manager's Guide
_______ ______ _________ ______
TOPS-20 DECnet Reference Manual
vii
The contents of this manual are as follows:
1. Chapter 1 briefly introduces OPR, ^E privileged commands, and
PTYCON.
2. Chapter 2 is an introduction to OPR, the Operator Interface.
3. Chapter 3 describes all OPR commands, their keywords,
arguments, switches, and values. The OPR commands are listed
in alphabetical order.
4. Chapter 4 contains an introduction to LCP, the LAT Control
Program, and describes all LCP commands, their keywords,
arguments, switches, and values. The LCP command
descriptions are in alphabetical order.
5. Chapter 5 describes all ^E () privileged commands for
special operator tasks.
6. Chapter 6 describes all PTYCON commands.
Conventions Used In This Manual
Symbol Meaning
Press the key labeled RETURN or CR.
Press the key labeled ESC, ESCAPE, ALT, or PRE.
Press the keys labeled CTRL and C simultaneously.
Press the keys labeled CTRL and E simultaneously.
Press the keys labeled CTRL and I simultaneously
or press the key labeled TAB.
Press the keys labeled CTRL and X simultaneously.
Press the keys labeled CTRL and H simultaneously.
viii
1-1
CHAPTER 1
CHAPTER 1
INTRODUCTION
INTRODUCTION
OPR is the operator interface. The operator's command language allows
you to communicate with certain components of TOPS-20, to control the
batch streams and the input and output devices. You also use OPR to
send messages to jobs, terminals, and batch-streams, and to respond to
requests for operator action, such as from the PLEASE program.
Chapter 2 contains a thorough introduction to using OPR. Chapter 3
describes all OPR commands in alphabetical order. LCP is the LAT
Control Program. LAT (Local Area Transport) is a protocol to control
communication between LAT terminal servers and LAT hosts on the
Ethernet. Chapter 4 contains a detailed introduction to LAT functions
that you can control with LCP, and also describes the LCP commands, in
alphabetical order.
^E (Control-E) privileged commands are commands that can affect the
entire system, and therefore can be used only by those with OPR or
WHEEL privileges enabled. The first character of each command is
(typed in by pressing the keys labeled CTRL and E
simultaneously), which echoes on your terminal as ^E.
^E privileged commands allow you to shut down the system, create
accounts, define system-wide logical names, and send messages to all
users simultaneously. ^E privileged commands and their functions are:
o ^ECEASE - shuts down the system
o ^ECREATE - creates a directory
o ^EDEFINE - defines system-wide logical names
o ^EEDDT - debugs the EXEC
o ^EPRINT - displays directory parameters
o ^EQUIT - halts the EXEC
o ^ESEND - sends system-wide messages
1-1
INTRODUCTION
INTRODUCTION
o ^ESET - sets system-wide and local parameters
o ^ESPEAK - gives commands to SYSJOB
^E commands are described in Chapter 5 in alphabetical order. PTYCON
is a program that allows you to RUN more than one job simultaneously,
without requiring each job to have an associated timesharing terminal.
PTYCON runs each job as a subjob controlled by a pseudo-terminal
(PTY). PTYCON can send information to each PTY and receive
information from each PTY. Each PTY is in effect a software
simulation of a timesharing terminal.
PTYCON allows the many operator jobs, such as GALAXY, OPR, and NMLT20,
to be run from a single terminal, under the control of the operator.
PTYCON commands are described in Chapter 6 in alphabetical order.
Chapter 6 also contains an introduction to using PTYCON.
1-2
CHAPTER 2
CHAPTER 2
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
2.1 INTRODUCTION TO THE OPERATOR INTERFACE
2.1 INTRODUCTION TO THE OPERATOR INTERFACE
OPR, the Operator Interface, is both a component and the main command
language used in the TOPS-20 operating system. This component
provides you, the operator, with the language to communicate with the
following components of the TOPS-20 operating system:
1. QUASAR, the GALAXY Scheduler
2. BATCON, the Batch Controller
3. LPTSPL, the Line-Printer Spooler
4. SPRINT, the Reader Interpreter
5. CDRIVE, the Card-Reader Spooler
6. SPROUT, the Card-Punch, Paper-Tape-Punch, and Plotter Spooler
7. MOUNTR, the Tape-Drive and Disk-Drive Controller
8. NEBULA, the Cluster GALAXY Message Router
_______
Further information on these components can be found in the TOPS-20
__________ _____
Operator's Guide.
You also use the OPR command language to communicate with:
o Any program requesting operator action (such as the PLEASE
program)
o Any user on the system
o All users on a remote system in the cluster
The component that receives the OPR commands and communicates with all
the other operating system components is ORION.
2-1
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
2.2 RUNNING OPR AND EXITING FROM IT
2.2 RUNNING OPR AND EXITING FROM IT
To start OPR, you must have WHEEL or OPERATOR privileges. (See your
System Manager to get these privileges if you do not already have
either of them.)
To handle all batch software tasks and all PLEASE, MOUNT, and DISMOUNT
requests, you must have OPR running. Normally, commands in the
PTYCON.ATO file start OPR automatically as a PTYCON subjob. An
example of this command file is shown on the next page.
SILENCE
LOG
DEFINE ^$OPR
CONNECT OPR
LOG OPERATOR FOO OPERATOR
ENABLE
!NEW OPERATOR INTERFACE PARSER
OPR
TAKE SYS:SYSTEM.CMD
PUSH
ENABLE
^ESET LOGIN ANY
S
^ESEND SYSTEM IN OPERATION
POP
The command TAKE SYS:SYSTEM.CMD in the above PTYCON.ATO example can
contain any number of OPR commands to set and start devices and
streams automatically. An example of a SYSTEM.CMD command file is
shown below.
SET BATCH-STREAM 0 TIME-LIMIT 5
SET BATCH-STREAM 1 TIME-LIMIT 10
SET BATCH-STREAM 2:3 TIME-LIMIT 11000
SET BATCH-STREAM 3 PRIORITY-LIMITS 20:63
SET BATCH-STREAM 0:1 PRIORITY-LIMITS 1:19
START BATCH-STREAM 0:3
SET PRINTER 0 PAGE-LIMIT 20000
SET PRINTER 1 PAGE-LIMIT 500
START PRINTER 0:1
START READER 0
START CARD-PUNCH 0
_______
These commands are described in various sections of the TOPS-20
__________ _____
Operator's Guide and in Chapter 3 of this manual.
NOTE
It is the responsibility of your System Manager to
determine whether OPR is to run as a subjob of PTYCON.
In addition, your System Manager should determine
whether any other program or utility should be started
as a PTYCON subjob.
2-2
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
To start OPR yourself under a job with OPERATOR privileges, all you
need to do is to type ENABLE and then type OPR.
___________
@ENABLE
________
$OPR
OPR>
OPR is your primary interface with the operating system and its
devices. Thus, it is recommended that if your installation has a
hardcopy central terminal (CTY), it should be dedicated to OPR. To do
this, LOGIN and ATTACH to PTYCON; the OPR> prompt then appears at the
CTY. In the following example, your password is FOO and your account
number is OPERATOR.
________
CLOYD Development System, TOPS-20 Monitor 7(20753)
___ ________ ___ _____________
@LOG OPERATOR FOO OPERATOR
Job 12 on TTY21 30-Apr-79 07:10:32
___________
@ENABLE
______ _____________
$SYSTAT OPERATOR
0 DET SYSJOB OPERATOR
1 205 PTYCON OPERATOR
2 207 BATCON OPERATOR
3 210 EXEC OPERATOR
4 211 OPR OPERATOR
.
.
______ ________ ______
$ATTACH OPERATOR 1
_____
[Attached to TTY205, confirm]
Detaching Job # 12
________
Password: FOO
_____
OPR>
If your installation has more than one terminal assigned to its
operators, you can run separate OPRs from different terminals. (See
Section 2.2.2.) Thus, OPR can run as a subjob under PTYCON at one
terminal and as a job by itself at another terminal. All OPRs have
the same functionality as the OPR running as a subjob of PTYCON and
CONNECTed to the CTY. ORION, the OPR-controlling component, can
handle an unlimited number of terminals running OPR. Multiple OPRs
are discussed in Section 2.2.2.
If you want OPR as a subjob under PTYCON and the PTYCON.ATO file did
not automatically start OPR, you can either CONNECT to a subjob to
start OPR or DEFINE a subjob as OPR and then CONNECT to it. The
examples below show both methods of creating an OPR subjob.
_______ ______
PTYCON> CONNECT 0
[CONNECTED TO SUBJOB 0]
2-3
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
CLOYD Development System, TOPS-20 Monitor 7(20753)
___ ________ ___ _____________
@LOG OPERATOR FOO OPERATOR
Job 37 on TTY211 2-DEC-79 09:23:01
___________
@ENABLE
________
$OPR
OPR>
or
______ _ ________
PTYCON> DEFINE 0 OPR
_______ ________ ___ _____________
PTYCON> OPR-LOG OPERATOR FOO OPERATOR
PTYCON>
**** OPR(0) 09:32:01 ****
CLOYD Development System, TOPS-20 Monitor 7(20753)
@LOG OPERATOR OPERATOR
@
_______ ______
PTYCON> CONNECT 0
[CONNECTED TO SUBJOB OPR(0)]
_____
___________
@ENABLE
________
$OPR
OPR>
When you issue a command to OPR, OPR validates the syntax of the
command and generates error messages for any errors it may find. If
there are no errors, the command is passed to the correct process to
be executed.
If you receive an error message, you can retype the entire OPR
command, or press to reprint the command up to the point
where the error occurred in the command. (Refer to Section 2.4.2.)
To exit from OPR at any time, simply issue the command EXIT. You
immediately return to TOPS-20 command level and you are prompted by
the dollar-sign ($). For example:
_________
OPR>EXIT
$
If OPR is a subjob of PTYCON, you can type to return to
PTYCON command level. For example:
__
OPR>^X
^
|
PTYCON>
In addition, you can give the PUSH command to OPR to return to TOPS-20
command processor level. Then, you can execute any program or task
2-4
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
and then give the POP command to return to OPR. However, you cannot
LOGOUT while PUSHed to OPR.
_________
OPR>PUSH
TOPS-20 Command processor 7(4138)
___________
@ENABLE
___________
$DUMPER
DUMPER>
.
.
.
____________
$DISABLE
________
@POP
OPR>
2.2.1 Issuing OPR Commands to and from Remote Stations
2.2.1 Issuing OPR Commands to and from Remote Stations
In a data networking environment, a DECSYSTEM-20 communicates with one
or more separate computer processors. Each processor in a network is
called a "node." The DECSYSTEM-20, running TOPS-20, is a "host" node.
The host node is the only type of node in the TOPS-20 network that can
support interactive users on a timesharing basis. The operator at the
host node is the system operator. The system operator controls the
devices connected to his host node and those connected to the remote
stations that are controlled by his host node.
In a DECnet network, two or more hosts may communicate. The host
operator logs into his "local" host. The other hosts are called
"remote" hosts. The host operator cannot control devices at remote
hosts.
The processors in the TOPS-20 network, other than host nodes, are
known as remote stations. These remote stations do not support
interactive users, and usually have one card reader and one line
printer. Remote stations are used for remote submission of batch jobs
to a host node. The operator at a remote station is a remote
operator. The remote operator can control only those devices
connected to his remote station. He cannot control devices at the
host node.
The remote station is an IBM-type node. Your remote station operators
should have additional documentation. The following manual is
___ _____________________
available for remote station operators: IBM Emulation/Termination
______
Manual is useful for IBM-type remote stations.
This manual helps the remote station operator determine those
functions he can perform at the remote station. The commands that the
remote station operator uses will work on his remote station; no
further specification is necessary.
2-5
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
The system operator can perform any of the functions in this manual.
However, no operator can control devices at a remote host node.
The OPR program allows the operator to specify a remote node as the
destination for a command. Many OPR commands recognize the /NODE
switch. The /NODE switch can specify either a DECnet or IBM-type
remote station, or it can specify the operator's host node; any node
name may be specified. However for remote DECnet nodes, these
commands have no effect. To use the /NODE switch, type the following
in the command line:
/NODE:node-name::
Two colons (::) following the node name are optional.
2.2.2 Multiple OPRs on the System
2.2.2 Multiple OPRs on the System
You can have more than one OPR running on the same operating system.
ORION keeps track of each OPR and sends the appropriate
acknowledgement messages to the OPR that sent the command.
Only the host system can have more than one OPR running
simultaneously. Remote stations can only have one OPR running. Thus,
if you have remote stations at your installation, any message sent
from a remote station to the host system displays at all OPR's running
at the host. If a message is sent to a remote station from the host
(the /NODE: switch), the message displays only at that node.
Each OPR that is processing can be set to enable or disable the types
of messages to be displayed at that OPR console. For example, one OPR
could be responsible for only tape and disk mounts and dismounts, and
another OPR could be responsible for everything else. Refer to the
detailed descriptions of the DISABLE and ENABLE commands elsewhere in
this manual.
2.3 RUNNING SEMI-OPR
2.3 RUNNING SEMI-OPR
SEMI-OPR is a new user privilege that permits a designated user to use
a subset of OPR commands. This subset of OPR commands are those
commands for accessing information (such as SHOW) and controlling
certain devices (such as FORWARDSPACE). A user may be given the
SEMI-OPR privilege by another user who has WHEEL or OPERATOR
privileges.
The System Administrator can enable the SEMI-OPR privilege for a
particular user with the ^ECREATE command (or BUILD command) at EXEC
command level. For example, you can authorize user to have
the SEMI-OPR privilege by performing the following:
2-6
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
________ _____________
$^ECREATE
[Old]
__________________
$$SEMI-OPERATOR
_____
$$
$
The System Administrator can also determine which devices a SEMI-OPR
can control when a GALGEN is performed. The devices are printer,
card-reader, tape drive, plotter, card punch, and paper-tape-punch.
The operator of your system can turn on or turn off SEMI-OPR system
wide with the OPR commands ENABLE and DISABLE. For example, to ENABLE
SEMI-OPR:
______ _____________
OPR>ENABLE SEMI-OPR
OPR>
13:06:10 --SEMI-OPERATOR enable--
OPR>
To DISABLE SEMI-OPR:
_______ _____________
OPR>DISABLE SEMI-OPR
OPR>
13:06:19 --SEMI-OPERATOR disable--
OPR>
When the user activates SEMI-OPR by typing OPR at EXEC command level
followed by a carriage-return, the SEMI-OPR> prompt appears. When the
user types a "?" for the SEMI-OPR> prompt, only those commands
applicable to SEMI-OPR appear.
___________
@ENABLE
________
$OPR
_
SEMI-OPR>?
ALIGN BACKSPACE CONTINUE EXIT
FORWARDSPACE HELP IDENTIFY PUSH
SHOW SHUTDOWN START STOP
SUPPRESS TAKE WAIT
SEMI-OPR>
2.3.1 SEMI-OPR Limitations and Restrictions
2.3.1 SEMI-OPR Limitations and Restrictions
The following limitations and restrictions should be remembered when
designating and using SEMI-OPR:
o The user must ENABLE capabilities at EXEC command level to
run SEMI-OPR.
2-7
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
o The system must be running a Release 7 monitor and GALAXY 6.
o SEMI-OPR can execute only certain OPR commands.
o SEMI-OPR cannot run LCP and NCP (ENTER command), or another
application program by way of OPR.
2.3.2 SEMI-OPR Commands
2.3.2 SEMI-OPR Commands
For users to utilize SEMI-OPR, they must have SEMI-OPERATOR privileges
enabled and SEMI-OPR must be enabled. SEMI-OPR commands allow a user
to access information and to have limited control over devices. The
following are the permitted SEMI-OPR commands:
ALIGN BACKSPACE CONTINUE EXIT
FORWARDSPACE HELP IDENTIFY PUSH
SHOW SHUTDOWN START STOP
SUPPRESS TAKE WAIT
NOTE
The above list contains all the possible SEMI-OPR
commands. However, the System Administrator can
define a subset of the SEMI-OPR commands based on
device types. Therefore, when a SEMI-OPR requests a
list of available commands by typing a "?", only
commands enabled by the System Administrator are
displayed.
For a more detailed description of the above commands, refer to
Chapter 3, and remember the limitations and restrictions listed in
Section 2.3.1.
2.4 OPR COMMAND FEATURES
2.4 OPR COMMAND FEATURES
The OPR command language has three command features that allow you to
do the following:
1. List available commands - ?
2. Use recognition -
3. Reprint faulty commands -
These features are described in detail in the following sections of
this chapter.
If you are a remote station operator (that is, if your installation
2-8
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
has DECnet software), you will not have the above features. However,
you can obtain help with the HELP command at OPR command level. Refer
to Chapter 3 for a description of the HELP command.
In addition, CTRL/character commands such as CTRL/R and CTRL/U
function at OPR command level as they do at TOPS-20 command level.
2.4.1 ? (Question Mark) - Listing Available Commands
2.4.1 ? (Question Mark) - Listing Available Commands
You can type a question mark at command level or while in the process
of typing a command.
When you type a question mark to the OPR> prompt, it lists the
available OPR commands. When you type a question mark in the process
of entering an OPR command, it lists the available keywords to that
command. When you type a question mark after the keyword, OPR lists
the available values, arguments, and/or switches to that keyword. If
you type a question mark after an entire OPR command, OPR replies with
the message: "confirm with carriage return", retypes your entire
command, and waits for you to press the carriage return key.
----- Restriction -----
If you type a question mark after an OPR command argument or switch
and there are no additional arguments that can be supplied, OPR
responds with the message: "confirm with carriage return" and then
retypes your complete OPR command and waits for you to press the
carriage return key. (All OPR commands must end with a carriage
return; the ESCape, , and ? features do not require the
carriage return.)
----- Examples -----
1. Start OPR and, after the system prompts you with OPR>, type a
question mark.
___________
@ENABLE
________
$OPR
_
OPR>? one of the following
ABORT ALIGN BACKSPACE CANCEL CLOSE
CONTINUE DEFINE DISABLE DISMOUNT ENABLE
ENTER EXIT FORWARDSPACE HELP HOLD
IDENTIFY MODIFY MOUNT NEXT PUSH
RELEASE REPORT REQUEUE RESPOND ROUTE
SEND SET SHOW SHUTDOWN START
STOP SUPPRESS SWITCH TAKE UNDEFINE
WAIT
or one of the following:
LCP NCP
OPR>
2-9
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
NOTE
The NCP command appears in the above example
when your installation has DECnet software
and your system has been generated for
_______
network communication. Refer to the TOPS-20
______ _________ ______
DECnet Reference Manual for a description of
NCP commands.
2. Type a question mark after typing a letter. OPR responds
with the commands that begin with that letter.
__
OPR>A? one of the following:
ABORT ALIGN
OPR>A
3. Type a question mark after typing the ABORT command to the
OPR> prompt; OPR then lists the available arguments for the
ABORT command, retypes your command, and waits for one of the
arguments.
_____ _
OPR>ABORT ?
BATCH-STREAM CARD-PUNCH PAPER-TAPE-PUNCH
PLOTTER PRINTER READER
_____ _______ ______
OPR>ABORT PRINTER 0
OPR>
08:56:41 Printer 0 --Aborting--
Job BATCH9 Req #133 for BHARDY
OPR>
08:56:47 Printer 0 --End--
Job BATCH9 Req #133 for BHARDY
-- Job Aborted by Operator --
OPR>
4. Type the same ABORT command as above with the argument
PRINTER and then type a question mark. OPR replies with the
following:
_____ _______ _
OPR>ABORT PRINTER ? unit number
or one of the following:
CLUSTER DQS LAT
OPR>ABORT PRINTER
Supply the unit number (0) and then type another question
mark. OPR replies with any additional switches that may be
supplied.
_ _
OPR>ABORT PRINTER 0 ? /PURGE
or /REASON:
or confirm with carriage return
_______________ ________
OPR>ABORT PRINTER 0 /REASON:PRINTER JAM
OPR>
2-10
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
09:30:45 Printer 0 --Aborting--
Job BATCH9 Req #133 for BHARDY
OPR>
09:30:53 Printer 0 --End--
Job BATCH9 Req #133 for BHARDY
-- Job Aborted by Operator --
OPR>
2.4.2 ESCape - Using Recognition
2.4.2 ESCape - Using Recognition
The ESCape feature allows recognition input and guide words to appear
on your console when you give an OPR command.
To give the ESCape feature, you must press the key labeled ESC, SEL,
PRE, or ALT depending on the type of terminal at your installation.
NOTE
All OPR commands accept recognition input when you
press the ESCape key, and most OPR commands provide
guide words within parentheses. However, only this
section of the manual describes this ESCape feature of
the OPR command language.
ESCape is not available at remote station terminals.
If you are at a remote station, use the HELP command.
To use the ESCape key for recognition, type the first one or more
letters of an OPR command to make it unique from all other OPR
commands, such as REQ (for the REQUEUE command), and press the ESCape
key. OPR responds with the remainder of the command REQUEUE, the
guide words within parentheses (current job on), and waits for an
argument for the REQUEUE command.
|
V
__
OPR>REQUEUE (current job on)
Now type the first one or more letters of a REQUEUE argument, such as
PR (for PRINTER) and press the ESCape key. OPR responds with the
remainder of the keyword PRINTER, the guide words within parenthesis
(unit number or remote printer type), and waits for a unit number to
be specified.
|
V
__
OPR>REQUEUE (current job on) PRINTER (unit number or remote printer
type)
Now type the unit number of the line printer followed by the REASON
switch to the REQUEUE command. After you type the slash and the first
2-11
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
letter of the switch, press the ESCape key. OPR responds with the
remainder of the switch name.
OPR>REQUEUE (current job on) PRINTER (unit number or remote printer
_
type) 0
|
V
____ _______ ________
/REASON:PRINTER JAM
OPR>
09:04:33 Printer 0 --Requeued--
Job CBUILD Req #188 for SAMBERG
OPR>
09:04:45 Printer 0 --End--
Job CBUILD Req #188 for SAMBERG
-- Job Requeued by OPERATOR --
OPR>
----- Examples -----
1. Type the OPR command DISABLE using the ESCape key for
recognition.
| | |
V V V
____ _ _ _____
OPR>DISABLE OUTPUT-DISPLAY (of) FILE-RETRIEVAL-MESSAGES
OPR>
2. Type the OPR command ABORT with the use of the ESCape key for
recognition and guide words.
| |
V V
__ _ _
OPR>ABORT (Current Job on) BATCH-STREAM (Stream Number) 1
|
V
____ _____
/NOERROR-PROCESSING
OPR>
10:23:02 Batch-stream 1 --Aborted--
Job TBUILD Req #127 for HURLEY
No Reason Given with Noerror-processing
OPR>
10:23:17 Batch-stream 1 --End--
Job TBUILD Req #127 for HURLEY
-- Job Aborted by Operator --
OPR>
2-12
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
2.4.3 - Reprinting Faulty Commands
2.4.3 - Reprinting Faulty Commands
The feature prints the command you issued that resulted in an
OPR error message. An OPR error message occurs when a command does
not have the correct format, syntax, switch, or value.
When you press after the error message appears on your
terminal, OPR retypes your entire command up to the point you entered
the incorrect command input.
To use the feature, type an OPR command such as SET with the
argument BATCH-STREAM but misspell the word STREAM.
___ ____________ _ _______________________
OPR>SET BATCH-STRAEM 0 NOOPR-INTERVENTION
? Does not match switch or keyword:"BATCH-STRAEM"
________
|
V
OPR>SET
Now retype the keyword BATCH-STREAM correctly, but type an O instead
of a 0 (zero) for the same command.
____________ _ _______________________
OPR>SET BATCH-STREAM O NOOPR-INTERVENTION
? First nonspace character is not a digit:
________
|
V
OPR>SET BATCH-STREAM
Now retype the correct stream number of 0 and misspell the parameter
NOOPR-INTERVENTION. After the error message appears, you complete the
command correctly.
_ ______________________
OPR>SET BATCH-STREAM 0 NOPR-INTERVENTION
? Does not match switch or keyword
________
|
V
_______________________
OPR>SET BATCH-STREAM 0 NOOPR-INTERVENTION
OPR>
11:32:34 Batch-stream 0 --Set Accepted--
OPR>
----- Example -----
You specify the OPR command to show the status of printers on
cluster-node GIDNEY, but you mispell GIDNEY as GIDDNEY. After you
press , you type the correct node name.
____ ______ _______ __________________________
OPR>SHOW STATUS PRINTER /CLUSTER-NODE:GIDDNEY
2-13
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
? Does not match switch or keyword: "GIDDNEY"
________
|
V
___________
OPR>SHOW STATUS PRINTER /CLUSTER-NODE:GIDNEY
OPR>
12:15:28 -- System Device Status --
Printer Status:
Local printers
| Alias Unit Status
| ----- ----- ----------
| FOO 0 Idle
DQS printers
| Alias DQS queue name Node Status
| ----- -------------------------- ------ ------
| BAR SI$8700 JUNIPR Idle
| BINN SWE$LN03 LATOUR Idle
OPR>
2.4.4 Continuing OPR Command Lines
2.4.4 Continuing OPR Command Lines
While you are using the OPR program, you may find it necessary to type
a command line that is longer than the maximum line length allowed by
your terminal. You may continue typing the command past the end of
the line and onto the next line, without pressing RETURN. OPR will
accept arguments which are divided between lines. Note the divided
word, ACCESS-NAME, in this example:
______ ____ ________ _______________ _______ ______ ________
OPR>DEFINE NODE IBMNOD:: SNA-WORKSTATION GATEWAY IBMNAM ACCESS-N
___ ___________
AME ACCNAM
If you want to avoid divided words, you may use the continuation
feature. At the end of the first line, type a space, then a hyphen
(-), and press RETURN. Then finish the command on the next line.
______ ____ ________ _______________ _______ ______ ______
OPR>DEFINE NODE IBMNOD:: SNA-WORKSTATION GATEWAY IBMNAM -
___________ ______ _____
ACCESS-NAME ACCNAM
Note that the OPR> prompt does not appear on the second line, after
you press RETURN the first time. The space and hyphen indicate that
you wish to continue typing on the next line.
2-14
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
2.5 OPR MESSAGES
2.5 OPR MESSAGES
There are two types of messages that can appear at your OPR terminal:
1. ORION-to-OPR messages (Section 2.4.1)
2. OPR error messages (Section 2.4.2)
2.5.1 ORION-To-OPR Messages
2.5.1 ORION-To-OPR Messages
The types of messages from ORION to OPR that can appear at your OPR
terminal are messages about:
1. Errors generated when ORION accepts an OPR command, but does
not have the appropriate devices, streams, nodes, or jobs
2. Jobs that start processing within a stream or device
3. Jobs that end processing within a stream or device
4. Actions that you must perform for various devices, streams,
or jobs
5. Information you must respond to
6. Results from TAKE command files
Each OPR command that is sent to ORION is time stamped by ORION when
the command is accepted and executed. The acceptance and execution of
the command is then returned to the OPR terminal in the form of a
message with the time stamp as the first eight characters of the
message. For example, the OPR command:
___ _______ _ __________ ___________
OPR>SET PRINTER 0 FORMS-TYPE NARROW
returns to your terminal an ORION message in the format:
hh:mm:ss Printer 0 --Set Accepted--
where hh is the hour, mm is the minutes, and ss is the seconds that
the command was accepted and executed.
Likewise, when ORION accepts an OPR command but returns an error
message, that message also contains a time stamp. For example, the
OPR command:
OPR>SHOW MESSAGES
displays the following information message when there are no
outstanding messages to respond to:
2-15
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
hh:mm:ss --No Outstanding Messages--
When a particular job starts to process within a batch stream or on a
device, ORION displays a message at your OPR terminal to notify you
that the stream or device is active. For example:
hh:mm:ss Batch-stream 0 --Begin--
Job TEST Req #274 for ZINA
OPR>
appears on your terminal when a job named TEST begins to process in
batch stream 0 for user ZINA. The hh:mm:ss at the beginning of this
message is the time that the job started to process (hours, minutes,
seconds).
Likewise, when a particular job ends its processing within a batch
stream or on a device, ORION displays a message at your OPR terminal
to notify you that the stream or device is not active and the job has
completed. For example:
hh:mm:ss Batch-stream 0 --End--
Job TEST Req #274 for ZINA
OPR>
appears on your terminal when a job named TEST ends the process in
batch stream 0 for user ZINA. The hh:mm:ss at the beginning of this
message is the time that the job ended the process (hours, minutes,
seconds).
2.5.2 OPR Error Messages
2.5.2 OPR Error Messages
In the course of using OPR to enter commands, you will probably
encounter some error messages. All OPR error messages begin with a
question mark. Error messages can not be abbreviated with system
switches or parameters as in some system programs. In addition, the
question mark does not represent a fatal error in OPR as it does in
some other system programs.
When you receive an error message, you can press CTRL/H (to retype
your OPR command up to the point where you entered the incorrect
keyword, switch, or value) and then specify the correct input to the
command. As with all OPR commands, if you do not know the command
format or you have forgotten the keywords, switches, or values, type a
question mark and OPR lists the command arguments that you can
specify.
Each error message described below and on the following pages explains
the error message and a possible solution.
2-16
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
? Ambiguous:
ERROR: ? Ambiguous:
Reason: You abbreviated a keyword or switch but it is not
unique; one or more other keywords or switches also
have the same abbreviation.
Recovery: Press CTRL/H or retype the command and include enough
letters of the keyword or switch to make the
abbreviation unique.
? Does not match switch or keyword: "argument"
ERROR: ? Does not match switch or keyword: "argument"
Reason: You have specified a switch or keyword for an OPR
command that does not take the switch or keyword
specified. The invalid switch or keyword is displayed
in quotes.
Recovery: Type the command again and specify the correct switch
or keyword.
? File not found "file"
ERROR: ? File not found "file"
Reason: You have specified an OPR command that takes a file
specification as a keyword or switch value, but the
file was not found.
Recovery: Press CTRL/H or retype the command and specify the
correct file specification.
? First nonspace character is not a digit:
ERROR: ? First nonspace character is not a digit:
"character"
"character"
Reason: You have specified a keyword or switch value that must
be numeric, but the first character is an alphabetic or
is a special character.
Recovery: Press CTRL/H or retype the command and specify a
numeric keyword or switch value with any alphabetic
character.
2-17
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
? Invalid character in number
ERROR: ? Invalid character in number
Reason: You have specified a numeric value to an argument or
switch that is less than or greater than the allowed
value range.
Recovery: Press CTRL/H or retype the command and specify a
numeric value that is within the allowable range of
values.
? Invalid device terminator: "device name"
ERROR: ? Invalid device terminator: "device name"
Reason: You have specified a device with an illegal character
in its name or you did not include the colon at the end
of the device name.
Recovery: Press CTRL/H or retype the command and specify the
device name with the correct characters and include the
colon.
? Invalid guide word
ERROR: ? Invalid guide word
Reason: You have specified a guide word that does not pertain
to the OPR command that you specified, or you
misspelled the guide word, or you used recognition (you
pressed the ESCape key) and then pressed
before you pressed the carriage return.
Recovery: Press CTRL/H or retype the command. If you must have
guide words with the OPR command, use recognition with
the ESCape key.
? Invalid node name
ERROR: ? Invalid node name
Reason: You have specified a node name or number to a /NODE:
switch that has not been enabled, does not exist, is
currently off-line, or has been misspelled.
Recovery: Press CTRL/H or retype the command and specify the
correct node name or number to the /NODE: switch. You
might have to ENABLE the node before you reissue the
command.
2-18
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
? Invalid OPR Command Specified "command"
ERROR: ? Invalid OPR Command Specified "command"
Reason: You have specified an invalid OPR command.
Recovery: Type a question mark to the OPR prompt to get a list of
valid OPR commands.
? Invalid wildcard designator
ERROR: ? Invalid wildcard designator
Reason: You have specified a wildcard character (* or %) within
a file specification for a keyword or switch value.
Recovery: Press CTRL/H or retype the command and specify the file
specification without any wildcard characters.
OPR/ORION will not accept wildcard characters within
the file specifications.
% No help available for "command"
ERROR: % No help available for "command"
Reason: You have specified an invalid OPR command as a keyword
to the HELP command.
Recovery: Give the HELP HELP command to get a list of valid
keywords (OPR commands) to the HELP command.
? No such filename
ERROR: ? No such filename
Reason: You have specified a filename as a keyword or switch
value, but the filename does not exist as you specified
it.
Recovery: Press CTRL/H or retype the command and specify the
correct filename as the keyword or switch value.
? No such file type "file-name"
ERROR: ? No such file type "file-name"
Reason: You have specified a file type as a keyword or switch
value, but the file type does not exist as you
specified it.
Recovery: Press CTRL/H or retype the command and specify the
correct file type as the keyword or switch value.
2-19
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
? Not a quoted string - does not begin with double
ERROR: ? Not a quoted string - does not begin with double
quote
quote
Reason: You have specified a message text, but did not include
it within double quotes ("message text").
Recovery: Press CTRL/H or retype the command and specify the
message text within the required double quotes.
? Not confirmed
ERROR: ? Not confirmed
Reason: You have specified too many keywords or switches to an
OPR command. OPR expected a carriage return after one
of the keywords or switches specified.
Recovery: Press CTRL/H; OPR will retype the command up to the
point where a carriage return is expected. Then press
carriage return.
? Null switch or keyword given
ERROR: ? Null switch or keyword given
Reason: You have specified an OPR command without giving the
required switch or keyword to the command.
Recovery: Press CTRL/H; OPR will retype the command up to the
point where you omitted the required switch or keyword.
If you do not know the required switch or keyword for
the command, type a question mark and OPR will display
the necessary arguments.
? Number must be positive "negative-number"
ERROR: ? Number must be positive "negative-number"
Reason: You have specified a negative value for a device or
stream number. OPR will not accept negative numbers.
Recovery: Press CTRL/H or retype the command and specify a
positive integer as a device or stream number.
? Only one file allowed
ERROR: ? Only one file allowed
Reason: You have specified the BACKSPACE or FORWARDSPACE
command with the /FILE switch and a numeric value
greater than 1.
Recovery: Press CTRL/H; OPR will retype the command up to the
point where you entered the number of files. You can
then enter 1 or press carriage return. The /FILE
switch value defaults to 1.
2-20
THE OPERATOR INTERFACE, OPR
THE OPERATOR INTERFACE, OPR
? Priority not in range "nn"
ERROR: ? Priority not in range "nn"
Reason: You have specified a priority number in the SET
JOB-PRIORITY command that is not in the range from 0 to
63.
Recovery: Press CTRL/H or retype the command and specify a
priority number from 0 to 63.
? Too many characters in node name "node-name"
ERROR: ? Too many characters in node name "node-name"
Reason: You have specified too many characters in a node name
specification to the /NODE: switch. The /NODE:
switch can only have from one to six alphanumeric
characters.
Recovery: Press CTRL/H or retype the command and specify the
correct node name for the /NODE: switch with six
characters or less.
2-21
3-1
CHAPTER 3
CHAPTER 3
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
This chapter describes each of the OPR commands in detail. All OPR
commands must end with a carriage return (that is, you must press the
key labeled RETURN or CR).
The OPR commands are in alphabetical order.
3-1
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ABORT)
(ABORT)
ABORT - Aborting Jobs
ABORT - Aborting Jobs
Function
Function
The ABORT command terminates a job request that is in progress on
an input/output device or in a batch stream.
Format
Format
OPR>ABORT keyword nn /switch
where keyword can be one of the following:
BATCH-STREAM
CARD-PUNCH
PAPER-TAPE-PUNCH
PLOTTER
PRINTER argument
READER
followed by its stream/unit number:
nn
or the argument for the PRINTER keyword:
| aliasname
followed by: CLUSTER nn
n:m
followed by: NODE node-name::
or DQS queuename
followed by: NODE node-name::
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
and, one or more of the following switches:
| /CLUSTER-NODE:cluster-node-name
/NODE:node-name::
/PURGE
/REASON:comment
or one of these switches (BATCH-STREAM only):
3-2
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ABORT)
(ABORT)
/ERROR-PROCESSING
/NOERROR-PROCESSING
Keywords
Keywords
BATCH-STREAM specifies a particular batch stream that has a
job currently active within it. A batch
stream is a pseudo-terminal that interacts
with the system to execute a batch job.
CARD-PUNCH specifies a particular card-punch device that
has a job currently being output on it.
PAPER-TAPE-PUNCH specifies a particular paper-tape-punch device
that has a job currently being output on it.
PLOTTER specifies a particular plotter device that has
a job currently being output on it.
PRINTER argument specifies a particular line printer device or
| a range of line printer devices. You can use
| an alias name defined with the DEFINE ALIAS
| command to reference a printer specification
| in this command. The argument can be:
| nn specifies the unit number of the line printer.
| You must specify this unit number; there is no
| default.
CLUSTER nn specifies a printer, or a range of printers,
n:m on a remote node within a TOPS-20 cluster. A
TOPS-20 cluster is a loosely coupled
configuration of between two and four TOPS-20
processors. Each processor in the
configuration is identified by a node name.
For example, HUEY::, DEWEY::, and LOUIE:: can
be three nodes within a cluster of TOPS-20
processors.
NODE node-name::
specifies that the printer device for a
cluster be started. The double colon (::)
following the node name is not needed.
For the CLUSTER argument, NODE node-name::
specifies a node within the cluster and cannot
be the local node or an alias.
DQS queuename
3-3
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ABORT)
(ABORT)
specifies the Distributed Queue Service
allowing users to queue print requests to VMS
systems using DECnet. DQS accepts the user
specified print request and transmits it to
the remote VMS node. The "queuename"
specifies the VMS queuename and can be a
string of 1 to 31 characters, consisting of
alphanumeric characters, underscores, and
dollar signs.
NODE node-name::
specifies the VMS node where the print request
is processed. The double colon (::) following
the node name is not needed.
For the DQS argument, NODE node-name::
specifies the VMS nodename and cannot be an
alias.
LAT specifies the Local Area Transport service
used to control communication between LAT
hosts and terminals on the Ethernet. With the
LAT keyword, you specify the SERVICE or PORT
and its SERVER name to establish communication
between your system, running LAT software, and
the resource printer terminal.
You cannot use the following
SERVICE/PORT/SERVER specifications:
SERVICE name only
SERVER name only
PORT name only
SERVICE name and PORT name
SERVICE, SERVER, and PORT names
Refer to Chapter 4 for additional information
about LAT communications.
PORT "name"
specifies the communication path between the
host system and the printer resource or the
access point that the node represents to the
user. The "name" is the port name and can
have from 1 to 16 characters consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
SERVICE "name"
3-4
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ABORT)
(ABORT)
specifies the resource and establishes the LAT
access path to the resource. The "name" is
the service name and can have from 1 to 16
characters consisting of alphanumeric
characters, underscores, dashes, and dollar
signs.
SERVER "name"
specifies the server name of the resource
printer terminal. This name can be the LAT
box with the proper LAT software running in
it. The name can be from 1 to 6 alphanumeric
characters in length.
READER specifies a particular card-reader device that
has a job currently being read into the
system. Jobs read through the card reader
become job requests in the batch input queue.
nn specifies the stream number of the batch
stream to be aborted or the unit number of the
input/output device that is currently
processing a job. You must specify this
stream/unit number.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
double colon (::) following the node name is
optional.
/ERROR-PROCESSING specifies the default of the ABORT
BATCH-STREAM command if you do not specify
either the /NOERROR-PROCESSING or /PURGE
switch. The /ERROR-PROCESSING switch
specifies that if a user provides error
recovery procedures in his batch job, the
error recovery procedures are not ignored.
3-5
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ABORT)
(ABORT)
/NOERROR-PROCESSING
specifies that, if the user who submitted the
batch job provided error recovery procedures,
these procedures are ignored when the batch
job is aborted.
/PURGE specifies that the entire job be removed from
the system. All output from the job is also
aborted. That is, there will be no header
and/or trailer pages from the line printer.
The job is completely flushed from the system.
When you purge a batch job, no log file is
printed.
/REASON:comment allows you to include a comment as to why the
job has been aborted. This comment appears in
the batch log file and at the user's terminal.
If the comment is more than one line in
length, you can end the first line with a
hyphen and a carriage return and continue the
comment on the next line. If you press
carriage return immediately after the colon,
OPR responds with the instruction: ENTER TEXT
AND TERMINATE WITH ^Z. You can then enter as
many lines of text as necessary. When your
comment(s) have been entered, press the CTRL
key and the key labeled Z simultaneously
(CTRL/Z) and the OPR> prompt reappears.
Restrictions
Restrictions
When you use the READER keyword, the only switches available are
the /NODE: and /REASON: switches. This is because a reader
input job does not become a request until the last card ($EOJ
card) has been read.
The /ERROR-PROCESSING and /NOERROR-PROCESSING switches are valid
only with the BATCH-STREAM keyword.
Examples
Examples
1. Specify the ABORT command to abort a batch-stream job with
NOERROR-PROCESSING because you were instructed to do so by
the user who submitted the job.
_____ ____________ _ ___________________________ _____
OPR>ABORT BATCH-STREAM 2 /NOERROR-PROCESSING/REASON:
ENTER TEXT AND TERMINATE WITH ^Z
__ __________ ___ __________ __ __ __ __ ___________________
AS OPERATIONS WAS INSTRUCTED TO DO SO BY USER
3-6
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ABORT)
(ABORT)
^Z
^
|
OPR>
12:31:05 Batch-stream 2 --Aborted--
Job TEST09 Req #132 for P.HURLEY
AS OPERATIONS WAS INSTRUCTED TO DO SO BY USER
with Noerror-processing
OPR>
12:31:17 Batch-stream 2 --End--
Job TEST09 Req #132 for P.HURLEY
-- Job Aborted by Operator --
OPR>
2. Specify the ABORT command to abort a job currently being read
through the card reader.
_____ ______ ______
OPR>ABORT READER 0
OPR>
9:34:45 Reader 0 --Aborted--
OPR>
3-7
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ALIGN)
(ALIGN)
ALIGN - Aligning Printer Paper
ALIGN - Aligning Printer Paper
Function
Function
The ALIGN command prints a "forms-alignment" file on the line
printer so that you can align the paper.
At various times, you may have to align special forms for a
particular line printer job, such as payroll checks or invoices.
The ALIGN command allows you, at these times, to adjust the forms
and the line printer, if need be, as many times as necessary to
print the job correctly.
Format
Format
OPR>ALIGN keyword nn (or) LAT /switch (or) argument
where keyword must be: PRINTER
| followed by its alias name
or followed by its unit number:
nn
|
| optionally followed by the switch:
|
| /NODE:node-name::
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
and, optionally, one or more of the following switches:
| /CLUSTER-NODE:cluster-node-name
/PAUSE:nnnn
/REPEAT-COUNT:nnnn
/STOP
or, optionally, the following argument:
alignment-filespec
3-8
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ALIGN)
(ALIGN)
Keywords
Keywords
PRINTER specifies the line printer (output device).
| You can use an alias name defined with the
| DEFINE ALIAS command to reference a printer
| specification in this command.
nn specifies the unit number of the line printer
that will print the forms to be aligned (for
example, 0 for LPT0, 1 for LPT1, and so
forth). You must specify this unit number.
LAT specifies the Local Area Transport service
used to control communication between LAT
hosts and terminals on the Ethernet. With the
LAT keyword, you specify the SERVICE or PORT
and its SERVER name to establish communication
between your system, running LAT software, and
the resource printer terminal.
You cannot use the following
SERVICE/PORT/SERVER specifications:
SERVICE name only
SERVER name only
PORT name only
SERVICE name and PORT name
SERVICE, SERVER, and PORT names
Refer to Chapter 4 for additional information
about LAT communications.
PORT "name"
specifies the communication path between the
host system and the printer resource or the
access point that the node represents to the
user. The "name" is the port name and can
have from 1 to 16 characters consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
SERVICE "name"
specifies the resource and establishes the LAT
access path to the resource. The "name" is
the service name and can have from 1 to 16
characters consisting of alphanumeric
characters, underscores, dashes, and dollar
signs.
3-9
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ALIGN)
(ALIGN)
SERVER "name"
specifies the server name of the resource
printer terminal. This name can be the LAT
box with the proper LAT software running in
it. The name can be from 1 to 6 alphanumeric
characters in length.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
|
| /NODE:node-name:: specifies the name of your host node, a remote
| station, a VMS node, or a LAT server. The
| double colon (::) following the node name is
| optional.
/PAUSE:nnnn specifies the time in seconds (nnnn) that the
line printer waits between repeats of the
particular print job. The default of the
/PAUSE: switch is 10 seconds.
/REPEAT-COUNT:nnnn
specifies the number of times to print the
file (starting from the beginning). The
default of the /REPEAT-COUNT: is 25.
/STOP specifies that normal printing be resumed and
stops the alignment of forms on the line
printer.
Argument
Argument
alignment-filespec
specifies a file to be printed for aligning
the forms. This file is usually supplied by
those individuals at your installation who are
responsible for the applications the file
would be used for. The default file
specification is SYS:formsname.ALP, where
3-10
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ALIGN)
(ALIGN)
formsname is the name of the form to be
aligned, such as NARROW. This alignment file
(or any supplied by an application individual)
has a format of one printed page of output
that can be repeated on the line printer so
that you can align the paper.
Restrictions
Restrictions
If you specify the ALIGN command and the alignment file cannot be
found, the following error message appears:
hh:mm:ss Printer n --Alignment Error--
Cannot read ALIGN file 'filespec'
If you specify the ALIGN command with the /STOP switch while the
print request is printing, the following error message appears:
hh:mm:ss Printer n --/STOP Illegal--
Alignment not in Progress
If you specify the ALIGN command while an alignment is in
progress, the following error message appears:
hh:mm:ss Printer n --Alignment already in Progress--
Examples
Examples
1. Specify line printer 0 in the ALIGN command to align some
special forms and specify a repeat-count of 15.
_____ _______ _ _____________________
OPR>ALIGN PRINTER 0 /REPEAT-COUNT:15
OPR>
10:12:07 Printer 0 --Alignment Scheduled--
OPR>
2. Specify line printer 0 in the ALIGN command for forms
alignment with the use of the alignment file PAYCHK.ALP. By
the default values of the /REPEAT-COUNT and the /PAUSE
switches, the ALIGN command repeats the file 25 times with a
pause of 10 seconds between repeats.
_____ _______ _ _______________
OPR>ALIGN PRINTER 0 PAYCHK.ALP
OPR>
9:34:12 Printer 0 --Alignment Scheduled--
OPR>
3. Specify line printer 3 in the ALIGN command for forms
alignment with a pause of 30 seconds between repeats. The
forms are aligned after one repeat and you stop the alignment
3-11
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ALIGN)
(ALIGN)
of forms on line printer 3.
_____ _______ _ ______________
OPR>ALIGN PRINTER 3 /PAUSE:30
OPR>
10:34:03 Printer 3 --Alignment Scheduled--
_____ _______ _ __________
OPR>ALIGN PRINTER 3 /STOP
OPR>
10:38:29 Printer 3 --Alignment Discontinued--
OPR>
3-12
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(BACKSPACE)
(BACKSPACE)
BACKSPACE - Backspacing Files by Page
BACKSPACE - Backspacing Files by Page
Function
Function
The BACKSPACE command reprints pages in the file currently
printing on the line printer.
At various times, you may have to backspace a particular file
that is currently being printed on the line printer, for example
when the forms become jammed in the printing mechanism. The
BACKSPACE command allows you to backspace the print file so that
the pages of the file that were jammed or miscorrectly printed
can be repeated.
Format
Format
OPR>BACKSPACE keyword nn (or) LAT /switch
where keyword must be: PRINTER
| followed by its alias name
or followed by its unit number:
nn
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
and, optionally, one or more of the following switches:
| /CLUSTER-NODE:cluster-node-name
/COPIES:nnnn
/FILE
/PAGES:nnnn
Keywords
Keywords
PRINTER specifies the line printer (output device).
| You can use an alias name defined with the
| DEFINE ALIAS command to reference a printer
| specification in this command.
3-13
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(BACKSPACE)
(BACKSPACE)
nn specifies the unit number of the line printer
that will backspace the file currently
printing (for example, 0 for LPT0, 1 for LPT1,
and so forth). You must specify this unit
number; there is no default.
LAT specifies the Local Area Transport service
used to control communication between LAT
hosts and terminals on the Ethernet. With the
LAT keyword, you specify the SERVICE or PORT
and its SERVER name to establish communication
between your system, running LAT software, and
the resource printer terminal.
You cannot use the following
SERVICE/PORT/SERVER specifications:
SERVICE name only
SERVER name only
PORT name only
SERVICE name and PORT name
SERVICE, SERVER, and PORT names
Refer to Chapter 4 for additional information
about LAT communications.
PORT "name"
specifies the communication path between the
host system and the printer resource or the
access point that the node represents to the
user. The "name" is the port name and can
have from 1 to 16 characters consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
SERVICE "name"
specifies the resource and establishes the LAT
access path to the resource. The "name" is
the service name and can have from 1 to 16
characters consisting of alphanumeric
characters, underscores, dashes, and dollar
signs.
SERVER "name"
specifies the server name of the resource
printer terminal. This name can be the LAT
box with the proper LAT software running in
it. The name can be from 1 to 6 alphanumeric
3-14
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(BACKSPACE)
(BACKSPACE)
characters in length.
3-15
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(BACKSPACE)
(BACKSPACE)
Switches
Switches
You must specify one of the following switches:
/COPIES:nnnn specifies the number of additional copies to
be printed. The number you specify is added
to the number of copies that the user queued
with the PRINT command. For example, if a
user issues the command:
PRINT FOO.BAR/COPIES:25
and you issue the BACKSPACE command with
/COPIES:10 while FOO.BAR is printing on the
line printer, the total number of copies
printed will be 35.
/FILE specifies that one file be backspaced when a
multifile PRINT request has been given by a
user. For example, if a user issues the
command:
PRINT FOO1.BAR,FOO2.BAR,FOO3.BAR
and you issue the BACKSPACE command with /FILE
while FOO3.BAR is printing on the line
printer, FOO2.BAR will be printed again.
/PAGES:nnnn specifies the number of pages to be backspaced
for the file that is currently being printed.
The /PAGES: switch is the default of the
BACKSPACE command. If you do not specify
either the /COPIES: or the /FILE switch, then
you must specify the /PAGES: switch. The
number (nnnn) you specify refers to the
physical number of pages and not to the number
of pages that contains the file on disk.
| Followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Restrictions
Restrictions
3-16
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(BACKSPACE)
(BACKSPACE)
When you give a BACKSPACE PRINTER command, the system prints the
output in the printer buffer (which may contain on or more
printed pages) before BACKSPACing the number of pages you
specify. Therefore, when you use the /PAGES: switch, you should
add two or three pages to the total number of pages you wish to
BACKSPACE.
Examples
Examples
1. Specify line printer 0 in the BACKSPACE command to add an
additional 15 copies to a print request of 15 copies.
_________ _______ _ _______________
OPR>BACKSPACE PRINTER 0 /COPIES:15
OPR>
13:43:53 Printer 0 --Backspaced 15 Copies--
OPR>
2. Specify line printer 2 in the BACKSPACE command to backspace
one file from the file currently printing.
_________ _______ _ __________
OPR>BACKSPACE PRINTER 2 /FILE
OPR>
11:34:23 Printer 2 --Backspaced 1 File--
OPR>
3. Specify line printer 1 in the BACKSPACE command to backspace
12 pages from the page currently printing because of a paper
jam.
_________ _______ _ _____________
OPR>BACKSPACE PRINTER 1 /PAGE:12
OPR>
10:23:50 Printer 1 --Backspaced 12 Pages--
OPR>
3-17
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CANCEL)
(CANCEL)
CANCEL - Canceling Requests
CANCEL - Canceling Requests
Function
Function
The CANCEL command cancels any job request that is being
processed or is waiting to be processed. In addition, the CANCEL
command can be used to cancel any user's request for a tape or
structure mount.
When a user submits a request for a job to be processed or a
request to mount a tape or structure, the system assigns a
request number to the request. To display the requests at any
time, give the OPR command SHOW QUEUES. The requests will be
displayed with the request numbers and the names of the users who
submitted the jobs. You cancel requests by specifying either the
request number or the user name. Optionally, you can cancel all
requests for a particular device or those of a particular type on
the specified device.
Format
Format
| OPR>CANCEL keyword argument /switch
where keyword can be one of the following:
BATCH-REQUEST
CARD-PUNCH-REQUEST
MOUNT-REQUEST
PAPER-TAPE-PUNCH-REQUEST
PLOTTER-REQUEST
PRINTER-REQUEST
followed by one of these arguments:
request-id-number
user-name
*
and for MOUNT-REQUEST, the argument:
structure-name:
and, optionally, the switch: /REASON:comment
and, optionally for the * argument, followed by the switch:
/NODE:node-name::
3-18
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CANCEL)
(CANCEL)
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
BATCH-REQUEST specifies either a job in the batch queue
waiting to be processed or a batch job that is
currently processing in a batch stream.
CARD-PUNCH-REQUEST
specifies either a job for the card punch
waiting to be processed or a job that is
currently being output on the card punch.
MOUNT-REQUEST specifies either a mount request for a tape
mount or a structure mount. With the
MOUNT-REQUEST keyword, you can specify a
single mount request-id-number or a structure
name, and an optional /REASON:. If you
specify a structure name, the CANCEL command
cancels all requests for that structure.
PAPER-TAPE-PUNCH-REQUEST
specifies either a job for the paper-tape
punch waiting to be processed or a job
currently being output on the paper-tape
punch.
PLOTTER-REQUEST specifies either a job for the plotter waiting
to be processed or a job currently being
output on the plotter.
PRINTER-REQUEST specifies either a job for the line printer
waiting to be processed or a job currently
printing on a line printer.
Arguments
Arguments
request-id-number cancels a single request as specified by the
appropriate keyword for a particular user.
The number can be a job that is either waiting
to be processed or is currently processing on
a device or in a batch stream.
user-name cancels all jobs as specified by the
appropriate keyword for a particular user.
3-19
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CANCEL)
(CANCEL)
The user name can be from 1 to 39 alphanumeric
characters (normally the user's surname) that
identifies the user and his logged-in
directory. Do not enclose the user name in
angle brackets. This argument cannot be used
with the MOUNT-REQUEST keyword.
* cancels all jobs as specified by the
appropriate keyword for all requests, waiting
and processing, from all users. This argument
cannot be used with the MOUNT-REQUEST keyword.
structure-name: specifies a 1- to 6-character structure name
that users have requested you to mount. The
name must end with a colon (:). When you
cancel a MOUNT-REQUEST for a structure name,
all requests for that structure mount are
canceled providing that the requests are in
the waiting status. (Refer to the description
of the SHOW QUEUES MOUNT-REQUESTS command in
this chapter.) If the structure is in the
dismount status, you must cancel the structure
separately, using the request-id-number with
the CANCEL command.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
double colon (::) following the node name is
optional. This switch can only be used with
the * argument.
/REASON:comment allows you to include a comment as to why the
MOUNT-REQUEST to mount a tape or structure has
been canceled. This comment appears in the
batch log file and at the user's terminal. If
the comment is more than one line in length,
you can end the first line with a hyphen and a
carriage return and continue the comment on
the next line. If you press carriage return
3-20
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CANCEL)
(CANCEL)
immediately after the colon, OPR responds with
the instruction: ENTER TEXT AND TERMINATE
WITH ^Z. You can then enter as many lines of
text as necessary. When your comment(s) have
been entered, press the CTRL key and the key
labeled Z simultaneously (CTRL/Z) and the OPR>
prompt reappears.
Restrictions
Restrictions
You cannot cancel any mount request after the tape or structure
has been mounted on the device. If you need to do this, you must
ABORT the job and DISMOUNT the tape or structure.
Examples
Examples
1. Specify the CANCEL MOUNT-REQUEST command to cancel all
requests for the mounting of structure SNOOPY:. All mount
requests for this structure are in the waiting status.
______ _____________ _______ _____________
OPR>CANCEL MOUNT-REQUEST SNOOPY: /REASON:
[Enter text and terminate with ^Z]
______ ____ _________ ___________
CANNOT FIND STRUCTURE SNOOPY
_____ ___ _ __________
THANK YOU - OPERATIONS^Z
^
|
OPR>
15:32:08 --3 Mount Requests Canceled--
OPR>
2. Specify the CANCEL BATCH-REQUEST for all batch requests from
user HOVSEPIAN.
______ _____________ ______________
OPR>CANCEL BATCH-REQUEST HOVSEPIAN
OPR>
12:09:34 --2 Jobs Canceled--
OPR>
3. Specify the CANCEL PAPER-TAPE-PUNCH-REQUEST to cancel all
requests from all users for that device.
______ ________________ ______
OPR>CANCEL PAPER-TAPE-PUNCH *
OPR>
09:34:56 --7 Jobs Canceled--
OPR>
3-21
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CLOSE)
(CLOSE)
CLOSE - Closing the Log Buffer File
CLOSE - Closing the Log Buffer File
Function
Function
The CLOSE command closes the current ORION log buffer file and
creates a new log buffer file. The closed log file is written to
disk so that you can copy or print an up-to-date file.
The ORION log buffer file records all OPR-to-ORION commands and
transactions performed at the operator's console. When the CLOSE
command is issued, these commands and transactions are
transferred to the ORION-SYSTEM.LOG file and the buffer file is
cleared. You can then print the ORION-SYSTEM.LOG file on the
line printer to obtain a hard-copy of all the operating processes
for a given time period.
You may choose a name other than ORION-SYSTEM.LOG for the ORION
log buffer file at GALGEN time. Please see your System Manager
in reference to GALGEN.
Format
Format
| OPR>CLOSE keyword /switch
where keyword must be: LOG
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keyword
Keyword
LOG specifies the ORION log buffer file that was
created with the start-up of ORION. For this
logging facility to occur, you must have
previously given the ENABLE LOGGING command.
The ENABLE LOGGING command is described in
this chapter. To stop the logging facility,
you must give the DISABLE LOGGING command.
The DISABLE LOGGING command is described in
this chapter.
Switch
| Switch
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
3-22
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CLOSE)
(CLOSE)
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Example
Example
1. Specify the CLOSE command in its full context to close the
ORION log file and open a new log file automatically.
_____ ________
OPR>CLOSE LOG
OPR>
3-23
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CONTINUE)
(CONTINUE)
CONTINUE - Restarting a Stopped Job
CONTINUE - Restarting a Stopped Job
Function
Function
The CONTINUE command continues a job request on a device that was
temporarily stopped with the STOP command.
Format
Format
OPR>CONTINUE keyword nn /switch
where keyword can be one of the following:
BATCH-STREAM
CARD-PUNCH
PAPER-TAPE-PUNCH
PLOTTER
PRINTER argument
READER
followed by the stream/unit number:
nn
or a range of numbers: n:m
| and, optionally, one or both of the following switches:
|
| /CLUSTER-NODE:cluster-node-name
/NODE:node-name::
or the argument for the PRINTER keyword:
| followed by its alias name
or followed by its unit number:
nn
|
| optionally followed by the switch:
|
| /NODE:node-name::
CLUSTER nn
n:m
followed by: NODE node-name::
or DQS queuename
followed by: NODE node-name::
3-24
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CONTINUE)
(CONTINUE)
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
3-25
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CONTINUE)
(CONTINUE)
Keywords
Keywords
BATCH-STREAM specifies a particular batch stream (or range
of batch streams) that was temporarily stopped
from processing a batch job. A batch stream
is a pseudo-terminal that interacts with the
system to execute a batch job.
CARD-PUNCH specifies a particular card-punch device (or
range of card-punch devices) that was
temporarily stopped from processing a
card-punch job.
PAPER-TAPE-PUNCH specifies a particular paper-tape-punch device
(or range of paper-tape-punch devices) that
was temporarily stopped from processing a
paper-tape-punch job.
PLOTTER specifies a particular plotter device (or
range of plotter devices) that was temporarily
stopped from processing a plotter job.
PRINTER argument specifies a particular line printer device or
| a range of line printer devices. You can use
| an alias name defined with the DEFINE ALIAS
| command to reference a printer specification
| in this command. The argument can be:
CLUSTER nn specifies a printer, or a range of printers,
n:m on a remote node within a TOPS-20 cluster. A
TOPS-20 cluster is a loosely coupled
configuration of between two and four TOPS-20
processors. Each processor in the
configuration is identified by a node name.
For example, HUEY::, DEWEY::, and LOUIE:: can
be three nodes within a cluster of TOPS-20
processors.
NODE node-name::
specifies that the printer device for a
cluster be started. The double colon (::)
following the node name is not needed.
For the CLUSTER argument, NODE node-name::
specifies a node within the cluster and cannot
be the local node or an alias.
DQS queuename
specifies the Distributed Queue Service
3-26
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CONTINUE)
(CONTINUE)
allowing users to queue print requests to VMS
systems using DECnet. DQS accepts the user
specified print request and transmits it to
the remote VMS node. The "queuename"
specifies the VMS queuename and can be a
string of 1 to 31 characters, consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
NODE node-name::
specifies the VMS node where the print request
is processed. The double colon (::) following
the node name is not needed.
For the DQS argument, NODE node-name::
specifies the VMS nodename and cannot be an
alias.
LAT specifies the Local Area Transport service
used to control communication between LAT
hosts and terminals on the Ethernet. With the
LAT keyword, you specify the SERVICE or PORT
and its SERVER name to establish communication
between your system, running LAT software, and
the resource printer terminal.
You cannot use the following
SERVICE/PORT/SERVER specifications:
SERVICE name only
SERVER name only
PORT name only
SERVICE name and PORT name
SERVICE, SERVER, and PORT names
Refer to Chapter 4 for additional information
about LAT communications.
PORT "name"
specifies the communication path between the
host system and the printer resource or the
access point that the node represents to the
user. The "name" is the port name and can
have from 1 to 16 characters consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
SERVICE "name"
3-27
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CONTINUE)
(CONTINUE)
specifies the resource and establishes the LAT
access path to the resource. The "name" is
the service name and can have from 1 to 16
characters consisting of alphanumeric
characters, underscores, dashes, and dollar
signs.
SERVER "name"
specifies the server name of the resource
printer terminal. This name can be the LAT
box with the proper LAT software running in
it. The name can be from 1 to 6 alphanumeric
characters in length.
READER specifies a particular card-reader device (or
range of card-reader devices) that was
temporarily stopped from processing a
card-reader job.
nn specifies the stream number of the batch
stream to be continued or the unit number of
the input/output device that has been
temporarily stopped. You must specify this
stream/unit number.
n:m specifies a range of stream/unit numbers. You
can specify this range instead of a single
stream/unit number. The colon must separate
the two numbers. The n represents the
low-order number and the m represents the
high-order number.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
3-28
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(CONTINUE)
(CONTINUE)
Examples
Examples
1. Specify the CONTINUE command to continue the card reader
after it was stopped to prevent a card-reader jam.
________ ______ ______
OPR>CONTINUE READER 0
OPR>
9:23:19 Reader 0 --Continued--
OPR>
2. Specify the CONTINUE command to continue a batch stream that
was previously stopped.
________ ____________ ______
OPR>CONTINUE BATCH-STREAM 2
OPR>
12:10:12 Batch-stream 2 --Continued--
OPR>
3. Specify the CONTINUE command to continue all line printers
after they were stopped temporarily.
________ _______ ________
OPR>CONTINUE PRINTER 0:1
OPR>
11:40:23 Printer 0 --Continued--
OPR>
11:40:24 Printer 1 --Continued--
OPR>
3-29
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE)
(DEFINE)
DEFINE - Defining a Node
DEFINE - Defining a Node
Function
Function
The DEFINE command specifies the name and characteristics of a
node that is to perform IBM communications. DEFINE sets the
node's parameters to the default parameters of the SET NODE
command. Refer to the SET NODE command.
The DEFINE command is applicable only if your installation has
IBM communications software. For more information about IBM
_______ ___
communications software, refer to the TOPS-20 IBM
_____________________ _______
Emulation/Termination Manual.
__________
For information about SNA workstations, refer to the DECnet/SNA
_______ ______ ___ _____ ______ ___ __________ _____
TOPS-20 Remote Job Entry User's and Operator's Guide and the
__________ _______ __________ _____
DECnet/SNA Gateway Management Guide.
Format
Format
OPR>DEFINE NODE node-name[::] keyword /switch arguments
where:
node-name must be: a valid node name in your network,
optionally followed by two colons
(::).
keyword, switch and argument format is:
2780 / \
3780 / /SIGNON-REQUIRED mode port line \
HASP \ /NO-SIGNON-REQUIRED /
SNA-WORKSTATION \ ACCESS-NAME name GATEWAY gateway-name /
keyword is one of: 2780
3780
HASP
SNA-WORKSTATION
switch (for 2780, 3780, AND HASP) is one of:
/SIGNON-REQUIRED
/NO-SIGNON-REQUIRED
arguments (for 2780, 3780, AND HASP) are all of the following,
separated by spaces:
3-30
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE)
(DEFINE)
mode is one of: EMULATION
TERMINATION
port is a valid portnumber:
nn
line is a valid line number:
n
arguments (for SNA-WORKSTATION) are all of the following,
separated by spaces:
ACCESS-NAME name
GATEWAY gateway-name::
DEFINE NODE parameters are further described below:
node-name specifies the node name of the node to perform
IBM communications. The double colon (::)
following the node name is optional.
Keywords
Keywords
2780, 3780, HASP, or SNA-WORKSTATION
specifies a protocol to use (2780, 3780,
SNA-WORKSTATION, or HASP multileaving). HASP
is the default.
Switches
Switches (for 2780, 3780, AND HASP):
/SIGNON-REQUIRED specifies that the remote station must sign on
when starting up the node. For emulation, a
signon card must be sent to the IBM system.
For termination, a signon card must be
verified from the station (node) and the card
must be the first one read. In addition, a
signon file must exist in the area in
the format of .SON.
3-31
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE)
(DEFINE)
/NO-SIGNON-REQUIRED
specifies that the user at the node does not
need to sign on when starting up the node (see
/SIGNON-REQUIRED). The default is
/SIGNON-REQUIRED.
Arguments
Arguments (for 2780, 3780, AND HASP)
EMULATION or TERMINATION
specifies the mode. EMULATION specifies that
the node is to communicate with a host.
TERMINATION specifies that the node is to
communicate with a remote station.
TERMINATION is the default.
nn specifies the port number from the front end
to the TOPS-20 host.
n specifies the line number from the front end
to the modem communicating with the remote
site.
CAUTION
For a KL10, the port number can be either 11 (for
DTE1), 12 (for DTE2), or 13 (for DTE3). For a KS10,
the port number can be either 0 (for KMC/DMC line 0)
or 1 (for KMC/DMC line 1). Never use port 0 on a
KL10.
For a KL10, the line number must be from 0 to 5; for a
KS10, the line number must be either 0 or 1.
Arguments
Arguments (for SNA-WORKSTATION only):
ACCESS-NAME name is the name of a list of access information,
as defined in the .CFG file for the SNA
gateway.
GATEWAY gateway-name::
is the name of the SNA gateway optionally
followed by a double colon (::).
3-32
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE)
(DEFINE)
Examples
Examples
1. You use the DEFINE command to define node IBM2.
______ ____ ______ ____ _________ __ ______
OPR>DEFINE NODE IBM2:: HASP EMULATION 11 0
OPR>
9:18:34 -- Define for Node IBM2 Accepted --
OPR>
2. You use the DEFINE command to define a remote station as an
IBM 3780 to communicate from the host.
______ ____ ______ ____ ___________ __ ______
OPR>DEFINE NODE IBM3:: 3780 TERMINATION 12 1
OPR>
15:32:09 -- Define for Node IBM3 Accepted --
OPR>
3. You use the DEFINE command to define a node as an
SNA-WORKSTATION.
______ ____ ______ _______________ _________________
OPR>DEFINE NODE IBM4:: SNA-WORKSTATION ACCESS-NAME-
___ _______ __________
RJE GATEWAY TOIBM
OPR>
16:32:09 -- Define for Node IBM4 Accepted --
OPR>
3-33
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE ALIAS)
| (DEFINE ALIAS)
DEFINE - Defining Aliases for Printer Specifications
| DEFINE - Defining Aliases for Printer Specifications
|
|
|
Function
| Function
|
| The DEFINE ALIAS command allows you to define, redefine, or
| undefine an alias name for printer specifications for DQS, LAT,
| local, and cluster printers. Once an alias is defined for a
| printer, that printer can be specified either by its alias or its
| printer specification.
|
| The SHOW ALIAS command displays each printer alias name relative
| to its printer specification.
|
| Once you have defined an alias name for a printer, you can
| reference that printer by its alias in the syntax of the
| following commands:
|
| ABORT PRINTER
| ALIGN PRINTER
| BACKSPACE PRINTER
| CONTINUE PRINTER
| DEFINE ALIAS
| FORWARDSPACE PRINTER
| NEXT PRINTER
| REQUEUE PRINTER
| ROUTE PRINTER
| SET PRINTER
| SHOW ALIAS
| SHOW PARAMETERS PRINTER
| SHOW STATUS PRINTER
| SHUTDOWN PRINTER
| START PRINTER
| STOP PRINTER
| SUPPRESS PRINTER
|
|
Format
| Format
|
| OPR>DEFINE ALIAS alias-name keyword nn argument /switch
|
| where:
|
| alias-name is a unique name up to six
| alphanumeric characters long,
| including the non-alphabetic
| characters: '$', '.', or '_'. The
| first character of an alias name
| must be a non-numeric character and
| cannot begin with a 'C', 'D', or
3-34
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE ALIAS)
| (DEFINE ALIAS)
| 'L'.
|
| and, optionally, one or both of the following switches:
|
| /CLUSTER-NODE:cluster-node-name
| /NODE:node-name::
|
| where keyword is one of the following:
|
| CLUSTER nn
| n:m
| followed by: NODE node-name::
|
| or DQS queuename
| followed by: NODE node-name::
|
| or LAT
|
| followed by: SERVICE "name"
| SERVER "name"
|
| or followed by: PORT "name"
| SERVER "name"
|
| followed by the unit number:
|
| nn
|
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
|
|
Keywords
| Keywords
|
| CLUSTER nn specifies a printer on a remote node within a
| TOPS-20 cluster. A TOPS-20 cluster is a
| loosely coupled configuration of between two
| and four TOPS-20 processors. Each processor
| in the configuration is identified by a node
| name. For example, HUEY::, DEWEY::, and
| LOUIE:: can be three nodes within a cluster
| of TOPS-20 processors.
|
| NODE node-name::
|
| specifies that the printer device for a
| cluster be started. The double colon (::)
| following the node name is not needed.
|
| For the CLUSTER argument, NODE node-name::
3-35
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE ALIAS)
| (DEFINE ALIAS)
| specifies a node within the cluster and cannot
| be the local node or an alias.
|
| DQS queuename specifies the Distributed Queue Service
| allowing users to queue print requests to VMS
| systems using DECnet. DQS accepts the user
| specified print request and transmits it to
| the remote VMS node. The "queuename"
| specifies the VMS queuename and can be a
| string of 1 to 31 characters, consisting of
| alphanumeric characters, underscores, dashes,
| and dollar signs.
|
| NODE node-name::
|
| specifies the VMS node where the print request
| is processed. The double colon (::) following
| the node name is not needed.
|
| For the DQS argument, NODE node-name::
| specifies the VMS nodename and cannot be an
| alias.
|
| LAT specifies the Local Area Transport service
| used to control communication between LAT
| hosts and terminals on the Ethernet. With the
| LAT keyword, you specify the SERVICE or PORT
| and its SERVER name to establish communication
| between your system, running LAT software, and
| the resource printer terminal.
|
| You cannot use the following
| SERVICE/PORT/SERVER specifications:
|
| SERVICE name only
| SERVER name only
| PORT name only
| SERVICE name and PORT name
| SERVICE, SERVER, and PORT names
|
| Refer to Chapter 4 for additional information
| about LAT communications.
|
| PORT "name"
|
| specifies the communication path between the
| host system and the printer resource or the
| access point that the node represents to the
| user. The "name" is the port name and can
| have from 1 to 16 characters consisting of
| alphanumeric characters, underscores, dashes,
3-36
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE ALIAS)
| (DEFINE ALIAS)
| and dollar signs.
|
| SERVICE "name"
|
| specifies the resource and establishes the LAT
| access path to the resource. The "name" is
| the service name and can have from 1 to 16
| characters consisting of alphanumeric
| characters, underscores, dashes, and dollar
| signs.
|
| SERVER "name"
|
| specifies the server name of the resource
| printer terminal. This name can be the LAT
| box with the proper LAT software running in
| it. The name can be from 1 to 6 alphanumeric
| characters in length.
|
|
Switches
| Switches
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
|
|
Examples
| Examples
|
| 1. Use the DEFINE ALIAS command to define an alias to a printer
| specification.
|
______ _____ ___ _______ _ ____ _____________
| OPR>DEFINE ALIAS FOO CLUSTER 1 NODE GIDNEY::
| OPR>
| 9:18:34 -- Alias FOO Defined --
| OPR>
|
| This command assigns the alias FOO to the CLUSTER printer 1
| for node GIDNEY.
|
| 2. Use the DEFINE ALIAS command to redefine the alias FOO to
| alias BAR.
|
______ _____ ___ ________
| OPR>DEFINE ALIAS BAR FOO
| OPR>
| 15:32:09 -- Alias FOO Defined --
3-37
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DEFINE ALIAS)
| (DEFINE ALIAS)
| OPR>
|
| This command changes the alias name from FOO to BAR.
|
| 3. Use the DEFINE ALIAS command to undefine the alias BAR.
|
______ _____ ________
| OPR>DEFINE ALIAS BAR
| OPR>
| 16:32:09 -- Alias BAR Undefined --
| OPR>
|
3-38
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
DISABLE - Stopping System Process Features
DISABLE - Stopping System Process Features
Function
Function
The DISABLE command allows you to turn off (or stop) the
following features:
1. Automatic Volume Recognition feature (AVR) for magnetic tape
mounts.
2. Class scheduling for various job processings and the
accounting of CPU time assigned to different job classes.
3. File retrieval requests for off-line files.
4. The ORION logging facility for recording OPR/ORION commands
and transactions.
5. The output display of various groupings of messages that were
enabled with the ENABLE command.
6. Queue requests so that users can request jobs to be
processed.
7. Limit the output display for unprivileged users at a remote
node.
8. Printing of log files on specific local printer(s).
9. DECnet connection attempts by NEBULA to remote NEBULAs in the
TOPS-20 cluster.
10. Reporting by NEBULA of DECnet connection failures to remote
NEBULAs in the cluster.
11. SEMI-OPR commands for accessing information and limited
control of some output devices.
|
| 12. The sending of ORION messages to one or more remote nodes in
| a TOPS-20 cluster.
|
| 13. Unprivileged users from seeing all queued print jobs on a
| remote node in the TOPS-20 cluster.
Format
Format
OPR>DISABLE keyword argument /switch
3-39
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
where keyword can be one of the following:
AUTOMATIC-VOLUME-RECOGNITION
| BROADCAST-MESSAGES
CLASS-SCHEDULER
DECNET-CONNECTION-ATTEMPTS
FILE-RETRIEVAL-WAITS
LOGFILES-TO-SPECIFIC-PRINTERS
LOGGING
OUTPUT-DISPLAY
PRINT-LOGFILES n
QUEUE-REQUESTS
REPORT-CONNECTION-FAILURES
SEMI-OPR
UNPRIVILEGED-USER-ENTIRE-REMOTE-OUTPUT-DISPLAY
followed by one of these arguments: (AVR only)
TAPE-DRIVES
tape-drive-name:
or followed by one of these arguments: (OUTPUT-DISPLAY only)
ALL-MESSAGES
BATCH-MESSAGES
BUGCHK-MESSAGES
BUGINF-MESSAGES
CARD-PUNCH-MESSAGES
CARD-READER-INTERPRETER-MESSAGES
DECNET-EVENT-MESSAGES
DECNET-LINK-MESSAGES
FILE-RETRIEVAL-MESSAGES
LCP-MESSAGES
MOUNT-MESSAGES
NCP-MESSAGES
PAPER-TAPE-PUNCH-MESSAGES
PLOTTER-MESSAGES
PRINTER-MESSAGES
READER-MESSAGES
SYSTEM-MESSAGES
USER-MESSAGES
and, optionally, one or more of these switches: (OUTPUT-DISPLAY
keyword only, not for BUGCHK-, BUGINF-, DECNET-, or
SYSTEM-MESSAGES arguments)
/INFORMATION-MESSAGES
/JOB-MESSAGES
/OPR-ACTION-MESSAGES
| and optionally the following keyword for the OUTPUT-DISPLAY
3-40
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
| keyword:
|
| NODE
or for DECNET-CONNECTION-ATTEMPTS and
REPORT-CONNECTION-FAILURES, the optional switch:
/NODE:node-name::
| or the optional switch (except for OUTPUT-DISPLAY):
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
AUTOMATIC-VOLUME-RECOGNITION
specifies that this AVR system feature be
disabled. AVR allows you to mount labeled
tapes without the need to IDENTIFY the tapes
to the system with a keyin. When this AVR
feature is disabled, you must IDENTIFY each
labeled tape you mount. Unlabeled tapes must
always be identified to the system with the
IDENTIFY command. (Refer to the description
of the IDENTIFY command.)
| BROADCAST-MESSAGES
|
| specifies to disable broadcast messages, which
| allows ORION messages generated on the local
| node to be sent to one or more remote nodes.
| It also allows selective sending of these
| messages.
CLASS-SCHEDULER specifies a system program be disabled that
allocates portions (or percentages) of the
central processor unit (CPU) to individual
groups of users. These groups are called
classes and are set up by your System Manager
in the n-CONFIG.CMD file at system generation
time. When the CLASS-SCHEDULER is disabled,
all jobs entered into the system receive an
equal amount of CPU time; allocation is on a
first-come-first-served basis.
DECNET-CONNECTION-ATTEMPTS
specifies to disable DECnet connections from
being made by NEBULA to remote systems within
the TOPS-20 cluster or to a particular remote
3-41
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
system.
FILE-RETRIEVAL-WAIT
specifies that when a user or batch job
requests a file that is off-line due to an
archival or a migration, the job does not wait
until the request has been satisfied. (Refer
to the TOPS-20 Operator's Guide for a
discussion of archived and migrated files.)
Instead, the user receives an error message
indicating that the file cannot be retrieved
and the batch job ends in an error (if error
recovery has not been specified in the control
file). If error recovery has been specified
in the control file, the job continues to
process.
LOGFILES-TO-SPECIFIC-PRINTERS
specifies to return from enabled printers
(ENABLE PRINT-LOGFILES n), thus disabling the
printing of batch log files and spooled files
on specific local printers. (See ENABLE
LOGFILES-TO-SPECIFIC-PRINTERS.)
LOGGING specifies that the centralized logging
facility of ORION be disabled (this facility
logs all messages passing through the
operating system and stores these messages in
a log file buffer). When this facility is
disabled, there are no records kept of the
messages and interactions between ORION and
the system. However, the CTY shows all
messages and interactions if you have not
DISABLEd the OUTPUT-DISPLAY of ALL-MESSAGES at
the CTY.
OUTPUT-DISPLAY specifies that the display of specified
message groupings on your console be disabled.
The groupings are specified as the valid
arguments and switches to this keyword.
| NODE allows you to selectively choose which ORION
| messages from the indicated node in the
| cluster are displayed on the operator
| terminal. You can specify the local node or
| an asterisk (*). The asterisk specifies all
| nodes within the cluster.
PRINT-LOGFILES n specifies to stop an enabled local printer (n)
3-42
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
from printing batch log files and spooled
files. (See ENABLE PRINT-LOGFILES.)
QUEUE-REQUESTS specifies that all users be disabled from
making any queue request. When queue requests
are disabled, no user can submit a batch or
reader job, a card-punch, paper-tape-punch,
plotter, or a printer request to the system.
If the user attempts to submit a job of any
kind, the message "?Operator Has Restricted
Queue Entry Commands" appears at the user's
terminal.
REPORT-CONNECTION-FAILURES
specifies to discontinue reporting DECnet
connection failures to remote systems or a
specific remote system in the cluster.
SEMI-OPR specifies to disallow users with SEMI-OPERATOR
privilege to have limited control of certain
output devices and to access operator
information. The OPR commands permitted and
their limitations are defined in Chapter 2.
UNPRIVILEGED-USER-ENTIRE-REMOTE-OUTPUT-DISPLAY
specifies that an unprivileged user may only
view his own print requests on a remote node
in the cluster as a result of that user giving
an @INFORMATION OUTPUT /DESTINATION-NODE:
command.
Arguments
Arguments
The following arguments are valid for the AUTOMATIC-VOLUME-
RECOGNITION keyword:
TAPE-DRIVES specifies that all tape drives on the system
be disabled from using AVR.
tape-drive-name: specifies the tape drive name that is disabled
from using AVR. The colon must be included.
The name is in the format of MTAn:, where n is
the tape drive number.
The following arguments are valid with the OUTPUT-DISPLAY
keyword. Each argument suppresses the printing of a type of
message on your OPR terminal.
3-43
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
Message Type Cause
ALL-MESSAGES all the types of messages defined by the
following arguments
BATCH-MESSAGES users requesting BATCH processing
BUGCHK-MESSAGES BUGCHKs encountered by the system
BUGINF-MESSAGES BUGINFs encountered by the system
CARD-PUNCH-MESSAGES
users requesting card punch output
CARD-READER-INTERPRETER-MESSAGES
card reader file processing or batch jobs
submitted with the /READER switch
DECNET-EVENT-MESSAGES
DECnet events generated by NMLT20
DECNET-LINK-MESSAGES
failure of an attempt to establish a link to
another node
FILE-RETRIEVAL-MESSAGES
users requesting retrieval of files that have
been archived or migrated to tape
LCP-MESSAGES LAT events noted by LCP
MOUNT-MESSAGES users requesting tape and structure mounts and
dismounts
NCP-MESSAGES users starting and shutting down network nodes
(valid only if your installation has DECnet
software)
PAPER-TAPE-PUNCH-MESSAGES
users requesting paper-tape-punch output
PLOTTER-MESSAGES users requesting plotter output
PRINTER-MESSAGES users requesting line printer output
3-44
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
READER-MESSAGES users requesting card reader input (card
reader jobs become batch requests)
SYSTEM-MESSAGES various system messages such as: job 0
crashes, swapping space, SPT space, disk
space, and parity error conditions encountered
by the system
USER-MESSAGES users making requests to you through the
PLEASE program
Switches
Switches
You can specify the following switches with any of the
OUTPUT-DISPLAY arguments except BUGCHK-, BUGINF-, DECNET-, and
SYSTEM-MESSAGES. If you do not specify one of these switches
with any OUTPUT-DISPLAY argument, all three are assumed by
default.
/INFORMATION-MESSAGES
prohibits the printing of messages that are
informational, such as errors due to problems
in an application program. Note that one-way
PLEASE messages from users are considered
information messages, since no response from
you is necessary.
/JOB-MESSAGES prohibits the printing of messages that notify
you when a device or stream has begun to
process a job request and when the job request
has ended its processing.
/OPR-ACTION-MESSAGES
prohibits the printing of messages that notify
you of some action to be performed as
requested by a user or a processing job. Also
included are messages that require action to
be taken, but are not job or WTOR related.
All operator-action messages must be answered
with the RESPOND command.
| NODE prohibits an operator from selectively
| filtering which WTOs and WTORs from remote
| nodes are displayed on the operator terminal.
You can specify the following switch with the
DECNET-CONNECTION-ATTEMPTS and REPORT-CONNECTION-FAILURES
keywords:
3-45
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
/NODE:node-name:: specifies the name of a remote node in the
cluster. The double colon (::) following the
node name is optional.
| You can specify the following switch with all keywords except the
| OUTPUT-DISPLAY keyword:
|
3-46
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISABLE)
(DISABLE)
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Examples
Examples
1. You have scheduled a system shutdown in two hours and your
queues have approximately two hours' worth of jobs left to be
processed. You disable queue requests so that the queues can
be emptied before the system shutdown.
_______ ___________________
OPR>DISABLE QUEUE-REQUESTS
OPR>
16:34:03 --System Queue's Entry Processing Disabled--
OPR>
2. You have started OPR and want to display only information
messages. By default when OPR is started, all messages are
displayed. Therefore, you must disable all messages except
information messages.
@ENABLE
$OPR
_______ ____________ ________________________________
OPR>DISABLE ALL-MESSAGES /JOB-MESSAGES/USER-MESSAGES
OPR>
8:45:18 Output display for OPR modified --
OPR>
3. You DISABLE AVR on tape drive MTA2: before you mount and
ready a scratch tape to be initialized.
_______ ____________________________ __________
OPR>DISABLE AUTOMATIC-VOLUME-RECOGNITION MTA2:
OPR>
3-47
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISMOUNT)
(DISMOUNT)
DISMOUNT - Dismounting a Structure or Tape-drive
DISMOUNT - Dismounting a Structure or Tape-drive
Function
Function
The DISMOUNT command allows you to dismount (and remove) a
structure currently mounted on a disk drive or a magnetic tape
currently mounted on a tape drive.
You can dismount a structure without removing the structure from
the disk drive. The structure is then dismounted from the local
system and users on the system are prevented from mounting the
structure from the EXEC.
You can also dismount a structure and remove the structure from
the disk drive. When the DISMOUNT WITH REMOVAL command is
issued, the structure is queued for removal. If other local or
remote users have mounted the structure, a message asks you if
you want to proceed. If you answer NO, the request is canceled.
If you answer YES, the structure is dismounted from every system
in the cluster, and you are asked to remove it.
When you issue the DISMOUNT command for a tape drive, the tape
rewinds itself completely from the take-up wheel, providing that
no user is currently using the tape. If a user is using the tape
on the specified tape drive, OPR will reject the DISMOUNT
command.
Format
Format
| OPR>DISMOUNT keyword argument /switch
where keyword can be: STRUCTURE
TAPE-DRIVE
followed by the argument: structure-name:
or the argument: tape-drive-name:
optionally followed by one of NO-REMOVAL
these arguments: (STRUCTURE only) REMOVAL
| optionally followed by the
| switch: /CLUSTER-NODE:cluster-node-name
3-48
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISMOUNT)
(DISMOUNT)
Keywords
Keywords
STRUCTURE specifies a disk structure currently mounted
on a disk drive.
TAPE-DRIVE specifies a tape drive that has a magnetic
tape mounted and ready on it.
Arguments
Arguments
structure-name: specifies the logical name of the structure to
dismount and remove. The colon must be
included with the structure name specified.
An example of a logical name is DSKC: for
Disk C.
REMOVAL specifies that the system giving the DISMOUNT
command is to have exclusive control of the
structure. The system checks for use of the
structure by users on another system within
the cluster. If users on another system
within the cluster have mounted the structure,
a message asks you whether or not to proceed
with the dismount. If the response is
PROCEED, then the structure is automatically
dismounted with NO REMOVAL from all the other
systems within the cluster, and then the
structure is dismounted for removal on the
local system.
If the structure is not in use by another
system, the structure is dismounted and you
are asked to remove it.
On a non-cluster system, REMOVAL is the
default to the STRUCTURE keyword.
NO-REMOVAL dismounts the structure without checking for
use of the structure by users on another CFS
system and prints a message telling you not to
physically remove the structure.
On a CFS system, NO-REMOVAL is the STRUCTURE
keyword default.
tape-drive-name: specifies the logical name of the tape drive
which currently has the desired tape to
dismount on it. The colon must be included
with the tape drive name. The name is in the
format of MTAn:, where n is the tape drive
3-49
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISMOUNT)
(DISMOUNT)
number.
Switch
| Switch
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Restrictions
Restrictions
If there are other users who have mounted the structure and you
really wish to remove the structure, it is recommended that you
send a message to all users of the system before you respond with
YES, to allow all users to complete their tasks on that
structure.
A structure can be DISMOUNTed only if set ACKNOWLEDGED; you
cannot DISMOUNT a structure that is set IGNORED.
Examples
Examples
1. Specify the DISMOUNT with REMOVAL command to dismount the
structure DEMO: from all systems within the cluster.
________ _________ _____ ____________
OPR>DISMOUNT STRUCTURE DEMO: REMOVAL
OPR>
10:14:41 <1> -- DISMOUNT QUERY --
Structure DEMO: (Alias DEMO:) is in use by
RONCO::, GIDNEY::, THEP::
and can't be removed from the cluster
unless it's dismounted with NO-REMOVAL
from the systems.
Respond with PROCEED to dismount
the structure from the above systems or
Respond with ABORT to terminate
the dismount request
_______ _ ____________
OPR>RESPOND 1 PROCEED
OPR>
10:15:00 -- REMOTE DISMOUNT STATUS --
Structure DEMO: dismounted from RONCO::,
GIDNEY::, THEP::
3-50
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(DISMOUNT)
(DISMOUNT)
OPR>
10:15:01 -- STRUCTURE DISMOUNTED --
Structure DEMO dismounted
10:15:01 -- DISMOUNT STRUCTURE --
Remove DEMO: (alias DEMO:)
User OPERATOR, Job 66, Terminal 233
DISK DRIVE INFORMATION DISK PACK INFO...
Chan-Cont Disk Mount Mount Usage
Type Drive Status Status Count Name Options
---- --------- -------- ------- ----- ------------ -------
RA81 7,03,12 Avail Free DEMO (1/1)
Structure cannot be mounted again unless MOUNTed via OPR
or until removed
OPR>
2. Specify the DISMOUNT command to dismount the tape volume
currently mounted on tape drive MTA0:.
________ __________ __________
OPR>DISMOUNT TAPE-DRIVE MTA0:
OPR>
16:45:01 -- MTA0: Unloaded --
OPR>
3-51
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
ENABLE - Allowing System Process Features
ENABLE - Allowing System Process Features
Function
Function
The ENABLE command allows you to turn on (or start) the following
features:
1. Automatic Volume Recognition feature (AVR) for magnetic tape
mounts.
2. Class scheduling for various job processings and the
accounting of CPU time assigned to different job classes.
3. File retrieval requests for off-line files.
4. The ORION logging facility for recording OPR/ORION commands
and transactions.
5. The output display of various groupings of messages that were
enabled with the ENABLE command.
6. Queue requests so that users can request jobs to be
processed.
7. Limit the output display for unprivileged users at a remote
node.
8. Printing of log files on specific local printer(s).
9. DECnet connection attempts by NEBULA to remote NEBULAs in the
TOPS-20 cluster.
10. Reporting by NEBULA of DECnet connection failures to remote
NEBULAs in the cluster.
11. SEMI-OPR commands for accessing information and limited
control of some output devices.
|
| 12. The sending of ORION messages to one or more remote nodes in
| a TOPS-20 cluster.
|
| 13. Unprivileged users from seeing all queued print jobs on a
| remote node in the TOPS-20 cluster.
Format
Format
OPR>ENABLE keyword argument /switch
where keyword can be one of the following:
3-52
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
AUTOMATIC-VOLUME-RECOGNITION
| BROADCAST-MESSAGES
CLASS-SCHEDULER
DECNET-CONNECTION-ATTEMPTS
FILE-RETRIEVAL-WAITS
LOGFILES-TO-SPECIFIC-PRINTERS
LOGGING
OUTPUT-DISPLAY
PRINT-LOGFILES n
QUEUE-REQUESTS
REPORT-CONNECTION-FAILURES
SEMI-OPR
UNPRIVILEGED-USER-ENTIRE-REMOTE-OUTPUT-DISPLAY
followed by one of these arguments (AVR only):
TAPE-DRIVES
tape-drive-name:
or followed by one or more of these switches:
(CLASS-SCHEDULER only)
/CLASS-ASSIGNMENTS:ACCOUNT
POLICY-PROGRAM
/WINDFALL:ALLOCATED
WITHHELD
or followed by one of these arguments: (OUTPUT-DISPLAY only)
ALL-MESSAGES
BATCH-MESSAGES
BUGCHK-MESSAGES
BUGINF-MESSAGES
CARD-PUNCH-MESSAGES
CARD-READER-INTERPRETER-MESSAGES
DECNET-EVENT-MESSAGES
DECNET-LINK-MESSAGES
FILE-RETRIEVAL-MESSAGES
LCP-MESSAGES
MOUNT-MESSAGES
NCP-MESSAGES
PAPER-TAPE-PUNCH-MESSAGES
PLOTTER-MESSAGES
PRINTER-MESSAGES
READER-MESSAGES
SYSTEM-MESSAGES
USER-MESSAGES
and, optionally, one or more of these switches: (OUTPUT-DISPLAY
keyword only, not for BUGCHK-, BUGINF-, DECNET-, or
3-53
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
SYSTEM-MESSAGES arguments)
/INFORMATION-MESSAGES
/JOB-MESSAGES
/OPR-ACTION-MESSAGES
| and optionally the following keyword for the OUTPUT-DISPLAY
| keyword:
|
| NODE
or for DECNET-CONNECTION-ATTEMPTS and
REPORT-CONNECTION-FAILURES, the optional switch:
/NODE:node-name::
| or the optional switch (except for OUTPUT-DISPLAY):
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
AUTOMATIC-VOLUME-RECOGNITION
specifies that this AVR system feature be
enabled. AVR allows you to mount labeled
tapes without the need to identify each tape
to the system with a keyin. However,
unlabeled tapes must always be identified to
the system with the IDENTIFY command. (Refer
to the description of the IDENTIFY command.)
| BROADCAST-MESSAGES
|
| specifies to enable broadcast messages. This
| allows ORION messages generated on the local
| node to be sent to one or more remote nodes.
| It also allows selective sending of these
| messages. For example, if the local node is
| generating an excessive amount of BUGCHKS, you
| may want to send all messages except BUGCHKs.
CLASS-SCHEDULER specifies a system program be enabled that
allocates portions (or percentages) of the
central processor unit (CPU) to individual
groups of users. These groups are called
classes and are set up by your System Manager
in the n-CONFIG.CMD file at system generation
time. When the CLASS-SCHEDULER is enabled,
all jobs entered into the system are executed
3-54
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
according to their class. You should consult
your System Manager before you ENABLE or
DISABLE the CLASS-SCHEDULER as this action
affects the performance of your system.
DECNET-CONNECTION-ATTEMPTS
specifies to enable NEBULA to attempt DECnet
connections to remote NEBULAs in the TOPS-20
cluster. The remote systems must be running
cluster GALAXY in order for the connection to
be successful.
FILE-RETRIEVAL-WAIT
specifies that when a user or batch job
requests a file that is off-line due to an
archival or a migration, the job waits until
the request has been satisfied, provided that
the user has given the TOPS-20 command SET
_______
RETRIEVAL-WAIT. (Refer to the TOPS-20
__________ _____
Operator's Guide for a discussion of archived
_
and migrated files, and to the ^TOPS-20
Commands Reference Manual for a description of
the SET RETRIEVAL-WAIT command.) Once the
request has been satisfied, the job (batch or
timesharing) continues to process.
LOGFILES-TO-SPECIFIC-PRINTERS
specifies to direct the printing of batch log
files and spooled files to specific local
printers. Normally, printing of spooled files
(batch or otherwise) is scheduled for the
first available local printer. With
LOGFILES-TO-SPECIFIC-PRINTERS enabled, you can
specify the printer with the OPR command
ENABLE PRINT-LOGFILES n. In this way, only
the local printer(s) specified print batch log
or spooled files. To check if this keyword is
enabled, use the OPR command SHOW PARAMETER
PRINTER.
If LOGFILES-TO-SPECIFIC-PRINTERS is directed
to specific printers (ENABLE PRINT-LOGFILES
n), and you issue the OPR command DISABLE
LOGFILES-TO-SPECIFIC-PRINTERS, the ENABLEd
printer(s) are remembered by OPR. Therefore,
if LOGFILES-TO-SPECIFIC-PRINTERS is ENABLEd
later during system operation, you do not have
to re-issue ENABLE PRINT-LOGFILES command(s).
3-55
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
LOGGING specifies that the centralized logging
facility of ORION be enabled (this facility
logs all messages passing through the
operating system and stores these messages in
a log file buffer). When this facility is
enabled, there are records kept of the
messages and interactions between ORION and
the system.
OUTPUT-DISPLAY specifies that the display of specified
message groupings on your console be enabled.
The groupings are specified as the valid
arguments and switches to this keyword.
| NODE allows you to selectively choose which ORION
| messages from the indicated node in the
| cluster are displayed on the operator
| terminal. You can specify the local node or
| an asterisk (*). The asterisk specifies all
| nodes within the cluster.
PRINT-LOGFILES n specifies the local printer "n" to print batch
log files and spooled files. The OPR command
ENABLE LOGFILES-TO-SPECIFIC-PRINTERS must
precede this command. If
LOGFILES-TO-SPECIFIC-PRINTERS is reverted
(DISABLEd) and then ENABLEd at a later time
during system operation, OPR remembers the
printer as ENABLEd, thus you do not have to
re-issue the ENABLE PRINT-LOGFILES command.
QUEUE-REQUESTS specifies that all users be enabled to make
any queue request. When queue requests are
enabled, a user can submit a batch or reader
job, a card-punch, paper-tape-punch, plotter,
or a printer request to the system.
REPORT-CONNECTION-FAILURES
specifies that NEBULA is to report DECnet
connection attempt failures to remote NEBULAs
in the cluster on your terminal.
SEMI-OPR specifies to allow users with SEMI-OPERATOR
privilege to have limited control of certain
output devices and to access operator
information. The OPR commands permitted and
their limitations are defined in Chapter 2.
UNPRIVILEGED-USER-ENTIRE-REMOTE-OUTPUT-DISPLAY
specifies that an unprivileged user may view
all print requests on a remote node in the
3-56
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
cluster as a result of that user giving an
@INFORMATION OUTPUT /DESTINATION-NODE:
command.
Arguments
Arguments
The following arguments can be used with the AUTOMATIC-VOLUME-
RECOGNITION keyword:
TAPE-DRIVES specifies that all tape drives on the system
be enabled with AVR.
tape-drive-name: specifies the tape-drive name that is enabled
with AVR. The colon must be included. The
name is in the format of MTAn:, where n is the
tape-drive number.
The following arguments are valid with the OUTPUT-DISPLAY
keyword. Each argument allows a type of message to be displayed
on your OPR terminal.
Message Type Cause
ALL-MESSAGES all the types of messages defined by the
following arguments
BATCH-MESSAGES users requesting BATCH processing
BUGCHK-MESSAGES BUGCHKs generated by the system
BUGINF-MESSAGES BUGINFs generated by the system
CARD-PUNCH-MESSAGES
users requesting card punch output
CARD-READER-INTERPRETER-MESSAGES
card reader file processing or batch jobs
submitted with the /READER switch
DECNET-EVENT-MESSAGES
DECnet events generated by NMLT20
DECNET-LINK-MESSAGES
failure of an attempt to establish a link to
another node
FILE-RETRIEVAL-MESSAGES
3-57
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
users requesting retrieval of files that have
been archived or migrated to tape
LCP-MESSAGES LAT events noted by LCP
MOUNT-MESSAGES users requesting tape and structure mounts and
dismounts
NCP-MESSAGES users starting and shutting down network nodes
(valid only if your installation has DECnet
software)
PAPER-TAPE-PUNCH-MESSAGES
users requesting paper-tape-punch output
PLOTTER-MESSAGES users requesting plotter output
PRINTER-MESSAGES users requesting line printer output
READER-MESSAGES users requesting card reader input (Card
reader jobs become batch requests.)
SYSTEM MESSAGES various system messages such as: job 0
crashes, swapping space, SPT space, disk
space, and parity error conditions encountered
by the system
USER-MESSAGES users making requests to you through the
PLEASE program
Switches
Switches
The following switches can be used as arguments of the
CLASS-SCHEDULER keyword:
/CLASS-ASSIGNMENTS:
specifies that users of the system have been
divided into classes and have been allocated a
certain amount of CPU time. The two arguments
available with this switch are ACCOUNTS and
POLICY-PROGRAM.
ACCOUNTS specifies that class assignments are assigned
by the accounts set up in the n-CONFIG.CMD
file and the ACCOUNTS-TABLE.BIN file.
POLICY-PROGRAM specifies that your System Manager or System
Programmer has initiated the Access Control
3-58
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
Job to assign a user to a class upon login.
The Access Control Job is a user written
program that provides the accounting functions
for your installation.
/WINDFALL: specifies what happens with the unused CPU
time. You can specify either ALLOCATED or
WITHHELD.
ALLOCATED specifies that excess CPU time is awarded
proportionately to the active classes (users
currently requesting CPU time).
WITHHELD specifies that excess CPU time is withheld
from all users and becomes idle time.
You can specify the following switches with all OUTPUT-DISPLAY
arguments except BUGCHK-, BUGINF-, DECNET-, or SYSTEM-MESSAGES.
If you do not specify one of these switches with an
OUTPUT-DISPLAY argument, all three are assumed by default.
/INFORMATION-MESSAGES
specifies that messages be displayed that are
informational, such as errors that occur due
to an application problem. Also, one-way
PLEASE messages from users are considered
information messages, since no response from
you is necessary.
/JOB-MESSAGES specifies that messages be displayed that
notify you when a device or stream has begun
to process a job request and when the job
request has ended its processing.
/OPR-ACTION-MESSAGES
specifies that messages be displayed that
notify you of some action to be performed as
requested by a user or a processing job. Also
included are messages that require action to
be taken, but are not job or WTOR related.
All operator action messages must be answered
with the RESPOND command.
You can specify the following switch with the DECNET-CONNECTION-
ATTEMPTS and REPORT-CONNECTION-FAILURES keywords:
/NODE:node-name:: specifies the name of a remote node in the
cluster. The double colon (::) following the
node name is optional.
3-59
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENABLE)
(ENABLE)
| You can specify the following switch with all keywords except the
| OUTPUT-DISPLAY keyword:
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Examples
Examples
1. You have previously disabled queue requests to allow those
requests in the queues to be processed before a shift
turnover. You can now enable queue requests.
______ ___________________
OPR>ENABLE QUEUE-REQUESTS
OPR>
16:34:03 --System Queue's Entry Processing Enabled--
OPR>
2. You have started OPR on a terminal to display only mount
messages. By default when OPR is started, all messages are
displayed. Therefore, you must disable all messages and then
enable mount messages.
_______ ______________ _________________
OPR>DISABLE OUTPUT-DISPLAY ALL-MESSAGES
OPR>
8:45:18 -- Output display for OPR modified --
______ ______________ ___________________
OPR>ENABLE OUTPUT-DISPLAY MOUNT-MESSAGES
OPR>
8:45:47 -- Output display for OPR modified --
OPR>
3. You ENABLE AVR on tape drive MTA2: after you have disabled
AVR and initialized some scratch tapes.
______ ____________________________ __________
OPR>ENABLE AUTOMATIC-VOLUME-RECOGNITION MTA2:
OPR>
3-60
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENTER)
(ENTER)
ENTER - Entering Another Command Level
ENTER - Entering Another Command Level
Function
Function
The ENTER command exits OPR and enters another command interface,
such as:
o LCP the LAT Control Program
o NCP the Network Control Program
to perform control and monitor functions appropriate to the
selected command interface.
Format
Format
OPR>ENTER keyword
where keyword is one of the following: LCP
NCP
Keywords
Keywords
LCP specifies that you exit OPR and enter LCP (the LAT Control
Program) to control and monitor LAT (Local Area Transport)
activity at a TOPS-20 node.
When you enter LCP, your prompt becomes the LCP prompt,
LCP>. You can use the ESCAPE key and command recognition
for LCP commands as for OPR commands.
LCP commands and functions are described in a separate
chapter of this manual.
NCP specifies that you exit OPR and enter NCP (the Network
Control Program for DECnet. This keyword is applicable only
if your installation has DECnet software.
When you specify the ENTER command to enter DECnet, your
prompt becomes the DECnet prompt, NCP>. Once you are in
NCP, you can use the ESCAPE key and recognition on NCP
commands as you can for OPR commands.
NCP commands and functions are described in the
________________ ______ _________ _____
DECnet-20/PSI-20 System Manager's Guide.
Use the ENTER command when you need to give many commands at the other
(non-OPR) command level. If you need to give only a few commands, you
3-61
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ENTER)
(ENTER)
can give them from OPR without entering the new command level. To do
this, type the command-level keyword (and a space) followed by the
command to the other interface, as:
___ ____ ____________________
OPR>LCP SHOW CHARACTERISTICS
3-62
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(EXIT)
(EXIT)
EXIT - Leaving OPR Level
EXIT - Leaving OPR Level
Function
Function
The EXIT command exits OPR command level and returns to TOPS-20
command level.
You can return to OPR command level with the TOPS-20 CONTINUE
command, providing that you do not alter memory. Refer to the
_______ ______ _____ _______ ________ _________ ______
TOPS-20 User's Guide or the TOPS-20 Commands Reference Manual for
additional information about the CONTINUE command.
The EXIT command has no keywords, arguments, or switches.
Format
Format
OPR>EXIT
Restrictions
Restrictions
Because OPR takes time to respond to some commands, the EXIT
command may prevent you from seeing output from previously issued
commands. However, the processing of the previous commands will
not be interrupted when you EXIT from OPR.
Examples
Examples
1. Specify the EXIT command to leave OPR and return to TOPS-20
command level.
_________
OPR>EXIT
$
2. After completing your task with commands that do not alter
memory, you now give the TOPS-20 command CONTINUE to return
to OPR.
_____________
$CONTINUE
OPR>
3-63
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(FORWARDSPACE)
(FORWARDSPACE)
FORWARDSPACE - Forward Spacing into Pages
FORWARDSPACE - Forward Spacing into Pages
Function
Function
The FORWARDSPACE command spaces the print file on the line
printer in a forward direction, so that you can skip the printing
of a job, file, or page(s). The FORWARDSPACE command allows you
to forwardspace the print file so that you can save paper and
print only what is needed as output.
At various times, you may have to forwardspace a particular file
that is currently being printed on the line printer, for example
when a user requires only a portion of some printed output.
Format
Format
OPR>FORWARDSPACE keyword nn (or) LAT /switch
where keyword must be: PRINTER
| followed by its alias name
|
| or followed by its unit number:
|
| nn
|
| followed optionally by the switch:
|
| /NODE:nodename::
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
and, optionally, one or more of the following switches:
| /CLUSTER-NODE: cluster-node-name
/COPIES:nnnn
/FILE
/PAGES:nnnn
Keywords
Keywords
PRINTER specifies the line printer (output device).
| You can use an alias name defined with the
3-64
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(FORWARDSPACE)
(FORWARDSPACE)
| DEFINE ALIAS command to reference a printer
| specification in this command.
nn specifies the unit number of the line printer
that can forwardspace the forms currently
printing (for example, 0 for LPT0, 1 for LPT1,
and so forth). You must specify this unit
number.
LAT specifies the Local Area Transport service
used to control communication between LAT
hosts and terminals on the Ethernet. With the
LAT keyword, you specify the SERVICE or PORT
and its SERVER name to establish communication
between your system, running LAT software, and
the resource printer terminal.
You cannot use the following
SERVICE/PORT/SERVER specifications:
SERVICE name only
SERVER name only
PORT name only
SERVICE name and PORT name
SERVICE, SERVER, and PORT names
Refer to Chapter 4 for additional information
about LAT communications.
PORT "name"
specifies the communication path between the
host system and the printer resource or the
access point that the node represents to the
user. The "name" is the port name and can
have from 1 to 16 characters consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
SERVICE "name"
specifies the resource and establishes the LAT
access path to the resource. The "name" is
the service name and can have from 1 to 16
characters consisting of alphanumeric
characters, underscores, dashes, and dollar
signs.
SERVER "name"
specifies the server name of the resource
3-65
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(FORWARDSPACE)
(FORWARDSPACE)
printer terminal. This name can be the LAT
box with the proper LAT software running in
it. The name can be from 1 to 6 alphanumeric
characters in length.
Switches
Switches
You must specify one of the following switches:
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/COPIES:nnnn specifies the number of copies to be skipped
from printing. The number you specify is
subtracted from the number that was queued
with the PRINT command. For example, if a
user issued the command
PRINT FOO.BAR/COPIES:25
and you issue the FORWARDSPACE command with
/COPIES:10 while FOO.BAR is printing on the
line printer, the total number of copies
printed will be 15.
/FILE specifies that you forward space one file when
a multifile PRINT request has been given by a
user. For example, if a user issues the
command
PRINT FOO1.BAR,FOO2.BAR,FOO3.BAR
and you issue the FORWARDSPACE command with
/FILE while FOO1.BAR is printing on the line
printer, FOO2.BAR starts printing on the line
printer. The remaining pages of FOO1.BAR are
skipped.
|
| /NODE:node-name:: specifies the name of a remote node in the
| cluster. The double colon (::) following the
| node name is optional.
/PAGES:nnnn specifies the number of pages to be
forwardspaced for the file that is currently
3-66
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(FORWARDSPACE)
(FORWARDSPACE)
being printed. If you do not specify either
the /COPIES: or the /FILE switch, then you
must specify the /PAGES: switch. The number
(nnnn) you specify refers to the physical
number of pages and not to the number of pages
that contains the file on disk.
Restrictions
Restrictions
When you give the FORWARDSPACE PRINTER command, the system prints
the output in the printer buffer (which may contain one or more
printed pages) before FORWARDSPACing the number of pages you
specify. Therefore, when you use the /PAGES:nn switch, you
should subtract two or three pages from the total number of pages
you wish to FORWARDSPACE.
Examples
Examples
1. Specify line printer 0 for the FORWARDSPACE command to skip
15 copies of a print request of 25 copies.
____________ _______ _ _______________
OPR>FORWARDSPACE PRINTER 0 /COPIES:15
12:34:34 Printer 0 --Forward Spaced 15 Copies--
OPR>
2. Specify line printer 2 with the FORWARDSPACE command to
forwardspace one file from the file currently printing.
____________ _______ _ __________
OPR>FORWARDSPACE PRINTER 2 /FILE
13:21:09 Printer 2 --Forward Spaced 1 File--
OPR>
3. Specify the FORWARDSPACE command to forwardspace twelve pages
from the page currently printing on line printer 1 because of
a user request.
____________ _______ _ _____________
OPR>FORWARDSPACE PRINTER 1 /PAGE:12
10:20:30 Printer 1 --Forward Spaced 12 Pages--
OPR>
3-67
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(HELP)
(HELP)
HELP - Getting Help on OPR Commands
HELP - Getting Help on OPR Commands
Function
Function
The HELP command displays information about an OPR command.
Format
Format
OPR>HELP command
where command can be any available OPR command
Restrictions
Restrictions
If you specify an invalid OPR command as a keyword with the HELP
command, OPR responds with:
%No help available for "command"
You can then press CTRL/H or retype the HELP command and specify
a correct OPR command as a keyword with HELP.
Examples
Examples
1. Specify the HELP command itself to get help on the HELP
command.
____ _________
OPR>HELP HELP
-- Help for HELP command --
The HELP command allows you to display the function, format,
arguments, and
switches of any OPR command.
The format is:
HELP keyword
where keyword can be any of the following OPR commands:
ABORT ALIGN BACKSPACE CANCEL CLOSE
CONTINUE DEFINE DISABLE DISMOUNT ENABLE
ENTER EXIT FORWARDSPACE HELP HOLD
IDENTIFY MODIFY MOUNT NEXT PUSH
RELEASE REPORT REQUEUE RESPOND ROUTE
SEND SET SHOW SHUTDOWN START
STOP SUPPRESS SWITCH TAKE UNDEFINE
WAIT
3-68
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(HELP)
(HELP)
or one of the following:
LCP NCP
OPR>
2. Specify the HELP command with TAKE as its keyword.
____ _________
OPR>HELP TAKE
-- Help for TAKE command --
The TAKE command allows you to execute a series of OPR
commands from a specified command file.
The format is:
TAKE filespec
where filespec is the name of the command file,
followed by one of these optional switches:
/DISPLAY
/NODISPLAY
OPR>
3-69
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(HOLD)
(HOLD)
HOLD - Holding Job Requests in the Queue
HOLD - Holding Job Requests in the Queue
Function
Function
The HOLD command keeps job requests in a queue from being
processed.
The jobs that are held with the HOLD command can be rescheduled
with the RELEASE command. Refer to the description of the
RELEASE command in this chapter.
To examine any jobs waiting in a queue to be processed, give the
SHOW QUEUES command. Refer to the description of the SHOW QUEUES
command in this chapter.
Format
Format
OPR>HOLD keyword argument /switch
where keyword can be one of the following:
BATCH-JOBS
CARD-PUNCH-JOBS
PAPER-TAPE-PUNCH-JOBS
PLOTTER-JOBS
PRINTER-JOBS
followed by one of these arguments:
request-id-number
user-name
*
and optionally for the * argument, followed by the switch:
/NODE:node-name::
| or optionally the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
BATCH-JOBS specifies one or more jobs in the batch input
queue waiting to be processed.
CARD-PUNCH-JOBS specifies one or more jobs in the card-punch
output queue waiting to be processed.
3-70
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(HOLD)
(HOLD)
PAPER-TAPE-PUNCH-JOBS
specifies one or more jobs in the
paper-tape-punch output queue waiting to be
processed.
PLOTTER-JOBS specifies one or more jobs in the plotter
output queue waiting to be processed.
PRINTER-JOBS specifies one or more jobs in the line printer
output queue waiting to be processed.
Arguments
Arguments
request-id-number specifies that a single job be held as
specified by the appropriate keyword, for a
particular user.
user-name specifies that all jobs be held as specified
by the appropriate keyword for a particular
user. The user name can be from 1 to 39
alphanumeric characters (normally the user's
surname) that identifies the user and his
logged-in directory. You do not need to
enclose the user name in angle brackets.
* specifies that all jobs be held as specified
by the appropriate keyword for all jobs
waiting to be processed, from all users.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
This switch can only be used with the *
argument.
3-71
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(HOLD)
(HOLD)
Restrictions
Restrictions
The HOLD command is effective only for the jobs currently waiting
to be processed. Any jobs submitted after the HOLD command was
issued are not held.
You cannot hold any job that is currently processing in a batch
stream or on an output device. If you need to stop the job from
processing, give the STOP command. Refer to the description of
the STOP command in this chapter.
Examples
Examples
1. Specify the OPR command to HOLD a line printer job whose
request-id-number is 127. This particular job will not
become rescheduled again until you issue a RELEASE command
for this job.
____ ____________ ________
OPR>HOLD PRINTER-JOBS 127
10:54:07 --1 Job Held--
OPR>
2. Specify the OPR command to HOLD all card-punch jobs.
____ _______________ ______
OPR>HOLD CARD-PUNCH-JOBS *
11:34:35 --10 Jobs Held--
OPR>
3. Specify the OPR command to HOLD all batch jobs for user
HOVSEPIAN.
____ __________ ______________
OPR>HOLD BATCH-JOBS HOVSEPIAN
12:20:32 --15 Jobs Held--
OPR>
3-72
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(IDENTIFY)
(IDENTIFY)
IDENTIFY - Identifying Tape Mounts
IDENTIFY - Identifying Tape Mounts
Function
Function
The IDENTIFY command services tape mount requests by enabling you
to:
o Satisfy a user's mount request for an unlabeled tape.
o Satisfy a user's request for a labeled tape that is mounted
on a drive that has AVR disabled.
o Pre-place and identify an unlabeled tape.
When a user issues a mount request for an unlabeled tape, you
must physically locate, mount, and ready the requested tape on an
available tape drive and then 'IDENTIFY' the tape-mount request
to the tape drive.
When more than one user issues a mount request for a scratch
tape, the IDENTIFY SCRATCH command applies to the first request
received. If you need to service a request other than the first,
use the IDENTIFY REQUEST-ID command.
If you have AVR enabled and your installation uses labeled tapes,
you do not need to give the IDENTIFY command after you mount and
ready a tape on a tape drive.
Format
Format
| OPR>IDENTIFY keyword argument /switch
where keyword must be the tape-drive name:
MTAn:
followed by one of these arguments:
REQUEST-ID nn
SCRATCH
VOLUME-ID volid
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
3-73
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(IDENTIFY)
(IDENTIFY)
Keyword
Keyword
MTAn: specifies the physical tape drive unit (n)
where you mounted and readied the tape. You
must specify this colon at the end of the unit
number.
Arguments
Arguments
REQUEST-ID nn specifies that you are attempting to use the
tape on drive MTAn: to satisfy
tape-mount-request number nn.
SCRATCH specifies that a user has requested that a
scratch tape be mounted. The tape must be
unlabeled, or the label must have expired.
VOLUME-ID volid specifies the volume identifier (volid) of the
tape volume you have mounted on the tape
drive. The volid can consist of from 1 to 6
alphanumeric characters. If the volid
contains nonalphanumeric characters
(characters other than A through Z and 0
through 9), the volid must be enclosed in
double quotes.
In addition, this argument allows you to
pre-place an unlabeled tape or an expired
labeled tape on a drive with AVR disabled (see
Example 4 below).
Switch
| Switch
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Examples
Examples
1. A user requests that you mount an unlabeled scratch tape.
After the tape-mount request appears, you mount and ready a
write enabled, scratch tape and then identify the tape as a
scratch tape.
3-74
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(IDENTIFY)
(IDENTIFY)
OPR>
14:34:20 --Tape Mount Request # 43--
Mount scratch tape, WRITE-ENABLED
User R.ACE, Job 27, Terminal 9
OPR>
14:36:12 --MTA2: Unlabeled tape mounted--
________ _____ ____________
OPR>IDENTIFY MTA2: SCRATCH
OPR>
14:36:15 --MTA2: Given To Request 43--
scratch tape now in use by
User R.ACE, Job 27, Terminal 9
OPR>
2. A user requests that you mount a labeled tape. However, you
have AVR disabled and you must identify the labeled tape to
the system.
OPR>
13:29:04 --Tape Mount Request # 87--
Mount ANSI volume 100555, READ-ONLY
User HOVSEPIAN, Job 19, Terminal 9
OPR>
13:32:14 --MTA0: tape mounted--
________ _____ _________ ___________
OPR>IDENTIFY MTA0: VOLUME-ID 100555
OPR>
13:32:18 --MTA0: Given To Request 87--
Volume 100555 now in use by
User HOVSEPIAN, Job 19, Terminal 9
OPR>
3. A user has requested an unlabeled tape to be mounted. After
you mount and ready the requested tape, you use the IDENTIFY
command to associate the tape mount request-id with the tape
drive.
OPR>
16:30:00 --Tape Mount Request # 127--
Mount Unlabeled volume DUMP01, WRITE-ENABLED
User SARTINI, Job 43, Terminal 7
Volumes in set DUMPER: DUMP01,DUMP02
OPR>
16:33:45 --MTA1: Unlabeled tape mounted--
________ _____ __________ ________
OPR>IDENTIFY MTA1: REQUEST-ID 127
OPR>
16:33:49 --MTA1: Given To Request 127--
Volume DUMP01 now in use by
User SARTINI, Job 43, Terminal 7
OPR>
4. You load an unlabeled tape on tape drive MTA1: and pre-place
it for a future user request.
3-75
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(IDENTIFY)
(IDENTIFY)
17:22:10 --MTA1: Unlabeled tape mounted--
________ _____ _________ ___________
OPR>IDENTIFY MTA1: VOLUME-ID NOVA01
OPR>
At some time in the future, a user will issue a mount request
for tape NOVA01. The system will automatically satisfy the
request with the tape NOVA01 on tape drive MTA1:.
3-76
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(MODIFY)
(MODIFY)
MODIFY - Modifying the Priority of Requests
MODIFY - Modifying the Priority of Requests
Function
Function
The MODIFY command changes the priority of a job request waiting
in a queue for processing. The higher the priority number is in
the MODIFY command, the greater the importance of the job
request.
When any job request is submitted for processing by a user, its
priority number defaults to a value that is set at GALGEN time.
The user who requests the job can set the priority value with the
/PRIORITY: switch. However, the MODIFY command permits you to
change the priority value for any job request.
Format
Format
| OPR>MODIFY keyword argument /switch PRIORITY nn /switch
where keyword can be one of the following:
BATCH-REQUEST
CARD-PUNCH-REQUEST
PAPER-TAPE-PUNCH-REQUEST
PLOTTER-REQUEST
PRINTER-REQUEST
followed by one of these arguments:
request-id-number
user-name
*
and optionally for the * argument, followed by the switch:
/NODE:node-name::
followed by the argument: PRIORITY nn
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
BATCH-REQUEST specifies one or more batch job requests
waiting in the batch input queue to be
processed.
3-77
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(MODIFY)
(MODIFY)
CARD-PUNCH-REQUEST specifies one or more card-punch job requests
waiting in the card-punch
PAPER-TAPE-PUNCH-REQUEST
specifies one or more paper-tape-punch job
requests waiting in the paper-tape-punch
output queue to be processed.
PLOTTER-REQUEST specifies one or more plotter job requests
waiting in the plotter output queue to be
processed.
PRINTER-REQUEST specifies one or more line printer job
requests waiting in the line printer output
queue to be processed.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
This switch can only be used with the *
argument.
Arguments
Arguments
request-id-number specifies that a single request from a
particular user be modified as specified by
the appropriate keyword.
user-name specifies that all requests from a particular
user be modified as specified by the
appropriate keyword.
* specifies that all requests from all users be
modified as specified by the appropriate
keyword.
PRIORITY nn specifies the priority number (nn) that the
request(s) will be set to. The number can be
in the range from 1 to 63. The higher the
3-78
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(MODIFY)
(MODIFY)
number is, the greater the importance of the
request.
Restriction
Restriction
You cannot MODIFY the priority of a job request once it has begun
to process in a batch stream or on an output device.
Examples
Examples
1. Modify a printer request so that its priority will be greater
than the next request to be printed. Thus, if print request
13 was the next print request and you modify print request 15
to be 50, print request 15 prints before print request 13.
______ _______________ __ ________ _______
OPR>MODIFY PRINTER-REQUEST 15 PRIORITY 50
OPR>
13:54:19 --1 Job Modified--
OPR>
2. Modify all card-punch requests for user CARLSON so that these
requests will output on the card punch before any other
card-punch requests.
______ __________________ _______ ________ _______
OPR>MODIFY CARD-PUNCH-REQUEST CARLSON PRIORITY 63
OPR>
16:13:20 --8 Jobs Modified--
OPR>
3-79
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(MOUNT)
(MOUNT)
MOUNT - Mounting Structures
MOUNT - Mounting Structures
Function
Function
The MOUNT command mounts a structure and allows users to access
it. Give the MOUNT command after physically mounting a structure
or after a physically mounted structure has been DISMOUNTed but
not removed from the disk drive. The MOUNT command also allows
you to assign the structure an alias name when two file
structures have the same name.
Unlike the EXEC MOUNT command, the OPR MOUNT command does not
place a mount request in the mount queue or identify you as a
user of the structure. If the structure is physically mounted in
the drive, the MOUNT command is executed immediately. If the
structure is not mounted in the drive, you receive a MOUNT
request. The MOUNT command is then executed automatically when
the structure is physically mounted.
The structure is MOUNTed only when it is physically mounted in a
disk drive and has AVAILABLE and ACKNOWLEDGED attributes.
Format
Format
OPR>MOUNT keyword argument /switch
where keyword must be: STRUCTURE
followed by the argument: alias:
optionally followed by the switches:
/STRUCTURE-ID:structure-name:
/CLUSTER-NODE:cluster-node-name
Keyword
Keyword
STRUCTURE specifies a disk structure that is on a disk
drive and has been DISMOUNTed.
Arguments
Arguments
alias: specifies the name to be used in referencing
the mounted structure. The alias must be 1 to
6 alphanumeric characters in length followed
by a colon.
3-80
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(MOUNT)
(MOUNT)
_______ ______ _________ _____
See the TOPS-20 System Manager's Guide for
more information on alias names.
Switches
Switches
/STRUCTURE-ID:structure-name:
specifies the physical name of the structure.
Specify this switch when the alias is not the
same as the physical structure name. The
structure name must be followed by a colon.
/CLUSTER-NODE:cluster-node-name
specifies the particular cluster node within
the TOPS-20 cluster where the command is
processed. The "cluster-node-name" qualifier
can be any node name within the cluster or an
asterisk (*). The asterisk specifies all
nodes within the cluster.
NOTE
If a structure was previously dismounted on behalf of
a remote system within the cluster, by way of the
DISMOUNT STRUCTURE name: REMOVAL command, only that
remote system can successfully use the MOUNT
/CLUSTER-NODE: command to remount the structure on
the remote system. Once this is accomplished, all
other systems within the cluster can use the
/CLUSTER-NODE: switch to remotely remount the
structure.
Examples
Examples
1. Give the MOUNT command to mount the DISMOUNTed structure
WORK:
_____ _________ __________
OPR>MOUNT STRUCTURE WORK:
OPR>
11:32:15 -- Mount request by operator completed --
Structure WORK: mounted as alias WORK
OPR>
2. Give the MOUNT command to mount structure SHARE: with the
alias MISC:
3-81
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(MOUNT)
(MOUNT)
_____ _________ _____ ________________________
OPR>MOUNT STRUCTURE MISC: /STRUCTURE-ID:SHARE
OPR>
11:32:15 -- Mount request by operator completed --
Structure SHARE: mounted as alias MISC
3-82
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(NEXT)
(NEXT)
NEXT - Specifying the Next Request to Run
NEXT - Specifying the Next Request to Run
Function
Function
The NEXT command specifies the request that will be serviced next
by the specified device. After you issue this command, the
request that you specified will start immediately.
Format
Format
| OPR>NEXT keyword nn /switch REQUEST-ID mm /switch
where keyword can be one of the following:
BATCH-STREAM
CARD-PUNCH
PAPER-TAPE-PUNCH
PLOTTER
PRINTER argument
followed by the stream/unit number:
nn
optionally followed by the switch:
/NODE:node-name::
or the argument for the PRINTER keyword:
| aliasname
or CLUSTER nn
followed by: NODE node-name::
or DQS queuename
followed by: NODE node-name::
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
and the word: REQUEST-ID
followed by the request identification number:
3-83
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(NEXT)
(NEXT)
mm
|
| optionally followed by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
BATCH-STREAM specifies the batch stream in which the job
will run.
CARD-PUNCH specifies the card punch that will punch the
job.
PAPER-TAPE-PUNCH specifies the paper tape punch that will punch
the job.
PLOTTER specifies the plotter that will plot the job.
PRINTER argument specifies a particular line printer device or
| a range of line printer devices. You can use
| an alias name defined with the DEFINE ALIAS
| command to reference a printer specification
| in this command. The argument can be:
CLUSTER nn specifies a printer on a remote node within a
TOPS-20 cluster. A TOPS-20 cluster is a
loosely coupled configuration of between two
and four TOPS-20 processors. Each processor
in the configuration is identified by a node
name. For example, HUEY::, DEWEY::, and
LOUIE:: can be three nodes within a cluster
of TOPS-20 processors.
NODE node-name::
specifies that the printer device for a
cluster be started. The double colon (::)
following the node name is not needed.
For the CLUSTER argument, NODE node-name::
specifies a node within the cluster and cannot
be the local node or an alias.
DQS queuename
specifies the Distributed Queue Service
allowing users to queue print requests to VMS
systems using DECnet. DQS accepts the user
3-84
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(NEXT)
(NEXT)
specified print request and transmits it to
the remote VMS node. The "queuename"
specifies the VMS queuename and can be a
string of 1 to 31 characters, consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
NODE node-name::
specifies the VMS node where the print request
is to be processed. The double colon (::)
following the node name is not needed.
For the DQS argument, NODE node-name::
specifies the VMS nodename and cannot be an
alias.
LAT specifies the Local Area Transport service
used to control communication between LAT
hosts and terminals on the Ethernet. With the
LAT keyword, you specify the SERVICE or PORT
and its SERVER name to establish communication
between your system, running LAT software, and
the resource printer terminal.
You cannot use the following
SERVICE/PORT/SERVER specifications:
SERVICE name only
SERVER name only
PORT name only
SERVICE name and PORT name
SERVICE, SERVER, and PORT names
Refer to Chapter 4 for additional information
about LAT communications.
PORT "name"
specifies the communication path between the
host system and the printer resource or the
access point that the node represents to the
user. The "name" is the port name and can
have from 1 to 16 characters consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
SERVICE "name"
specifies the resource and establishes the LAT
access path to the resource. The "name" is
3-85
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(NEXT)
(NEXT)
the service name and can have from 1 to 16
characters consisting of alphanumeric
characters, underscores, dashes, and dollar
signs.
SERVER "name"
specifies the server name of the resource
printer terminal. This name can be the LAT
box with the proper LAT software running in
it. The name can be from 1 to 6 alphanumeric
characters in length.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
Restriction
Restriction
The NEXT command ignores most attributes of a request. For
example, if a print request has the attribute /UNIT:0, the NEXT
command can print the request on a different printer.
You should attempt to honor request attributes when possible.
Example
Example
A user has requested that his job be printed as soon as possible.
Use the NEXT command to queue job HURRY to be printed after the
current job is finished.
____ _______ _ __________ ________
OPR>NEXT PRINTER 0 REQUEST-ID 107
OPR>
15:39:51 Printer 0 -- NEXT request #107 scheduled --
OPR>
15:40:20 Printer 0 -- End --
3-86
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(NEXT)
(NEXT)
Job D60SPD Req # 105 for PERKINS
OPR>
15:40:32 Printer 0 -- Begin --
Job HURRY Req #107 for OPERATOR
OPR>
3-87
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(PUSH)
(PUSH)
PUSH - Pushing Out of OPR Command Level
PUSH - Pushing Out of OPR Command Level
Function
Function
The PUSH command leaves OPR command level and enters a new
operating system (EXEC) command level. You can then perform any
software task or run any utility. To return to OPR, type the POP
_______ ________ _________ ______
command. (Refer to the TOPS-20 Commands Reference Manual for
further information on the POP command.)
NOTE
Do not run OPR at the new EXEC command level.
Return to OPR by using the TOPS-20 POP command.
You can use the PUSH command to create a lower copy of an EXEC of
your choice. Normally, PUSH creates the EXEC defined by the
system logical name, DEFAULT-EXEC:. Use the TOPS-20 DEFINE
command to define the job-wide logical name DEFAULT-EXEC:, with
the filespec for the EXEC you want to use each time you PUSH.
Format
Format
OPR>PUSH
Restriction
Restriction
When you have used the PUSH command, you cannot logout. If you
attempt to do so, the following error message will appear:
?LOG capability required
Not logged off
To logout, you must POP to OPR, EXIT from OPR, and then LOGOUT.
Examples
Examples
1. You give the PUSH command to enter operating system command
level and mount a tape for the DUMPER program.
_________
OPR>PUSH
TOPS-20 Command processor 4(554)
_____ ____ _______ _________________________________________
@MOUNT TAPE DUMPER: /LABEL-TYPE:UNLABELED/SCRATCH/NOWAIT
13:45:00 --Tape Mount Request # 60--
Mount Unlabeled scratch tape, WRITE-ENABLED
3-88
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(PUSH)
(PUSH)
User OPERATOR, Job 6, Terminal 1
.
.
.
___________
@DUMPER
DUMPER>
.
.
.
2. After completing the DUMPER tasks, you can dismount the tape
and type POP to return to OPR command level.
_________
DUMPER>EXIT
________
$POP
OPR>
3-89
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(RELEASE)
(RELEASE)
RELEASE - Releasing Job Requests Held in the Queue
RELEASE - Releasing Job Requests Held in the Queue
Function
Function
The RELEASE command releases job requests that were held with the
HOLD command. When you RELEASE any previously held job request,
the job is rescheduled for processing. Refer to the description
of the HOLD command in this chapter.
To examine any jobs waiting in the queue to be processed or any
jobs being held, give the SHOW QUEUES command with the /ALL
switch. Refer to the description of the SHOW QUEUES command in
this chapter.
Format
Format
OPR>RELEASE keyword argument /switch
where keyword can be one of the following:
BATCH-JOBS
CARD-PUNCH-JOBS
PAPER-TAPE-PUNCH-JOBS
PLOTTER-JOBS
PRINTER-JOBS
followed by one of these arguments:
request-id-number
user-name
*
and optionally for the * argument, followed by the switch:
/NODE:node-name:
| or optionally the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
BATCH-JOBS specifies one or more jobs held in the batch
input queue.
CARD-PUNCH-JOBS specifies one or more jobs held in the
card-punch output queue.
3-90
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(RELEASE)
(RELEASE)
PAPER-TAPE-PUNCH-JOBS
specifies one or more jobs held in the
paper-tape-punch output queue.
PLOTTER-JOBS specifies one or more jobs held in the plotter
output queue.
PRINTER-JOBS specifies one or more jobs held in the line
printer output queue.
Arguments
Arguments
request-id-number specifies that a single job for a particular
user be released as specified by the
appropriate keyword.
user-name specifies that all jobs held for a particular
user be released as specified by the
appropriate keyword. The user name can be
from 1 to 39 alphanumeric characters (normally
the user's surname) that identifies the user
and his logged-in directory. You do not need
to enclose the user name in angle brackets.
* specifies that all jobs held for all users be
released as specified by the appropriate
keyword.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the request is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
This switch can only be used with the *
argument.
3-91
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(RELEASE)
(RELEASE)
Examples
Examples
1. Specify the RELEASE command to release a line printer request
for user C.MULLEN.
_______ ____________ _____________
OPR>RELEASE PRINTER-JOBS C.MULLEN
OPR>
14:23:45 --1 Job Released--
OPR>
2. Specify the RELEASE command to release all card-punch job
requests held in the queue.
_______ _______________ ______
OPR>RELEASE CARD-PUNCH-JOBS *
OPR>
15:23:01 --10 Jobs Released--
OPR>
3. Specify the RELEASE command to release batch job request 117.
_______ __________ ________
OPR>RELEASE BATCH-JOBS 117
OPR>
17:18:20 --1 Job Released--
OPR>
3-92
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(REPORT)
(REPORT)
REPORT - Reporting Comments to SYSERR
REPORT - Reporting Comments to SYSERR
Function
Function
The REPORT command enters various comments or error conditions
into the system error file ERROR.SYS. To list these entries, you
_______________ _____
can run the SPEAR program. (Refer to the TOPS-10/TOPS-20 SPEAR
______
Manual for more information.)
Format
Format
| OPR>REPORT user-name device: /switch text
where user-name is the name of the user making the report
followed by the subject of the report (device:)
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
followed by a single- or multiple-line message (text)
Keywords
Keywords
user-name identifies the user making the report, or the
user that the report refers to. Only the
first six characters of the user name are
entered into the file ERROR.SYS.
device specifies one of the system devices that is
the subject of the report.
text after specifying the device, you can enter a
single- or multiple-line response and confirm
with a carriage return, or you can confirm
with carriage return immediately after the
user name or device. OPR responds with Enter
text and terminate with ^Z. You then enter as
many lines of text for a response as you need.
When you press CTRL/Z, the OPR> prompt returns
and your report is logged into the ERROR.SYS
file.
3-93
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(REPORT)
(REPORT)
Switch
| Switch
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Examples
Examples
1. Specify the REPORT command for a previous cancellation of a
job being read into the system through the card reader.
______ _______ _______ ___ ____ ____ ___________
OPR>REPORT SARTINI CDR260: TOO MANY PICK CHECKS
OPR>
12:19:00 --Entry made in ERROR.SYS--
OPR>
2. Specify the REPORT command to describe a possible hardware
problem that seems serious.
______ __________________
OPR>REPORT LEAD-OPERATOR
Enter text and terminate with ^Z
_____ ___ ____ _ ____ _____ __ _________ __________
THERE WAS JUST A HEAD CRASH ON STRUCTURE MISC:
___ _____ ____ __ ________
ALL FILES WILL BE RESTORED^Z
^
|
OPR>
15:18:01 --Entry made in ERROR.SYS--
OPR>
3-94
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(REQUEUE)
(REQUEUE)
REQUEUE - Rescheduling Job Requests
REQUEUE - Rescheduling Job Requests
Function
Function
The REQUEUE command stops a job request that is in progress and
puts it back in the queue in the HOLD state. You can reschedule
the request with the RELEASE command.
Format
Format
| OPR>REQUEUE keyword nn /switch argument /switch
where keyword can be one of the following:
BATCH-STREAM
CARD-PUNCH
PAPER-TAPE-PUNCH
PLOTTER
PRINTER argument
followed by the stream/unit number:
nn
and, optionally, one or more of the following switches:
/NODE:node-name::
/REASON:comment
or the argument for the PRINTER keyword:
| aliasname
CLUSTER nn
followed by: NODE node-name::
or DQS queuename
followed by: NODE node-name::
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
or one of the following arguments (not valid for BATCH-STREAM):
3-95
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(REQUEUE)
(REQUEUE)
BEGINNING-OF COPY
FILE
JOB
CURRENT-POSITION
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
BATCH-STREAM specifies a particular batch stream that has a
job currently active within it.
CARD-PUNCH specifies a particular card-punch device that
has a job currently being output on it.
PAPER-TAPE-PUNCH specifies a particular paper-tape-punch device
that has a job currently being output on it.
PLOTTER specifies a particular plotter device that has
a job currently being output on it.
PRINTER argument specifies a particular line printer device or
| a range of line printer devices. You can use
| an alias name defined with the DEFINE ALIAS
| command to reference a printer specification
| in this command. The argument can be:
CLUSTER nn specifies a printer on a remote node within a
TOPS-20 cluster. A TOPS-20 cluster is a
loosely coupled configuration of between two
and four TOPS-20 processors. Each processor
in the configuration is identified by a node
name. For example, HUEY::, DEWEY::, and
LOUIE:: can be three nodes within a cluster
of TOPS-20 processors.
NODE node-name::
specifies that the printer device for a
cluster be started. The double colon (::)
following the node name is not needed.
For the CLUSTER argument, NODE node-name::
specifies a node within the cluster and cannot
be the local node or an alias.
DQS queuename
3-96
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(REQUEUE)
(REQUEUE)
specifies the Distributed Queue Service
allowing users to queue print requests to VMS
systems using DECnet. DQS accepts the user
specified print request and transmits it to
the remote VMS node. The "queuename"
specifies the VMS queuename and can be a
string of 1 to 31 characters, consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
NODE node-name::
specifies the VMS node where the print request
is to be processed. The double colon (::)
following the node name is not needed.
For the DQS argument, NODE node-name::
specifies the VMS nodename and cannot be an
alias.
LAT specifies the Local Area Transport service
used to control communication between LAT
hosts and terminals on the Ethernet. With the
LAT keyword, you specify the SERVICE or PORT
and its SERVER name to establish communication
between your system, running LAT software, and
the resource printer terminal.
You cannot use the following
SERVICE/PORT/SERVER specifications:
SERVICE name only
SERVER name only
PORT name only
SERVICE name and PORT name
SERVICE, SERVER, and PORT names
Refer to Chapter 4 for additional information
about LAT communications.
PORT "name"
specifies the communication path between the
host system and the printer resource or the
access point that the node represents to the
user. The "name" is the port name and can
have from 1 to 16 characters consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
SERVICE "name"
3-97
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(REQUEUE)
(REQUEUE)
specifies the resource and establishes the LAT
access path to the resource. The "name" is
the service name and can have from 1 to 16
characters consisting of alphanumeric
characters, underscores, dashes, and dollar
signs.
SERVER "name"
specifies the server name of the resource
printer terminal. This name can be the LAT
box with the proper LAT software running in
it. The name can be from 1 to 6 alphanumeric
characters in length.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the request is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
/REASON:comment allows you to include a comment as to why the
job has been requeued. This comment will
appear in the batch log file and at the user's
terminal. If the comment is more than one
line long, you can end the first line with a
hyphen and a carriage return and continue the
comment on the next line. If you press RETURN
immediately after the colon, OPR responds with
the instruction: ENTER TEXT AND TERMINATE
WITH ^Z. You can then enter as many lines of
text as necessary. When you finish entering
the text, type a CTRL/Z and the OPR> prompt
reappears.
Arguments
Arguments
BEGINNING-OF specifies the requeuing starts at the
beginning of the COPY, FILE, or JOB. This
3-98
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(REQUEUE)
(REQUEUE)
argument is valid when you requeue a job
currently processing on a device, such as the
line printer. This argument is invalid with
the BATCH-STREAM keyword.
COPY specifies the requeuing starts at the
beginning of the current copy being processed.
(Refer to the BACKSPACE and FORWARDSPACE
commands.)
FILE specifies the requeuing starts at the
beginning of the current file being processed.
(Refer to the BACKSPACE and FORWARDSPACE
commands.)
JOB specifies the requeuing starts at the
beginning of the current job being processed.
With JOB, the entire job is requeued.
CURRENT-POSITION specifies the current position (line number)
of the job on unit number nn at the time you
issue the REQUEUE command.
Restriction
Restriction
The REQUEUE PRINTER command immediately stops sending a job
request to the printer. However, the printer finishes printing
the data already in its buffer. Therefore, when you give the
REQUEUE PRINTER command, the printer may continue to print a few
more pages of a job request before it stops or prints another
request.
Examples
Examples
1. Specify the REQUEUE command to hold and cancel a job in batch
stream 5.
_______ ____________ _ _____
OPR>REQUEUE BATCH-STREAM 5
OPR>
10:23:56 Batch Stream 5 --Requeued--
Job TEST Req #56 for BROWN
OPR>
10:23:57 Batch Stream 5 --End--
Job TEST Req #56 for BROWN
-- Job Requeued by Operator --
OPR>
2. Specify the REQUEUE command to hold and cancel the current
processing job on the card punch.
3-99
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(REQUEUE)
(REQUEUE)
_______ __________ _ ____________ ___ _____________
OPR>REQUEUE CARD-PUNCH 0 BEGINNING-OF JOB /REASON:
Enter text and terminate with ^Z
___ ________ _______ __ ____ _____ _________
JOB REQUEUED BECAUSE OF CARD PUNCH JAM.
_____ _______ ____________
FIELD SERVICE CALLED.
_______________
OPERATOR-JONES.^Z
^
|
OPR>
16:09:43 Card-punch 0 --Requeued--
Job PUNCH9 Req #99 for HOVSEPIAN
OPR>
16:09:44 Card-punch 0 --End--
Job PUNCH9 Req #99 for HOVSEPIAN
-- Job Requeued by Operator --
OPR>
3. Specify the REQUEUE command to hold and cancel the current
processing job on the line printer, unit number 0, at the
current position.
_______ _______ _ _____________________
OPR>REQUEUE PRINTER 0 CURRENT-POSITION
OPR>
12:34:09 Printer 0 --Requeued--
Job BATCH1 Req #177 for HURLEY
OPR>
12:34:10 Printer 0 --End--
Job BATCH1 Req #177 for HURLEY
-- Job Requeued by Operator --
OPR>
3-100
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(RESPOND)
(RESPOND)
RESPOND - Responding to Messages
RESPOND - Responding to Messages
Function
Function
The RESPOND command to replies to any message sent to you via
WTOR (Write To Operator with Response) from a user or from a
software task.
When a user or software task sends you a message that requires a
response, OPR assigns the message a number so that you can keep
track of all messages sent to operations. With the use of the
SHOW MESSAGES command, you can find out at any time if there are
any outstanding messages.
There are no keywords or switches for the RESPOND command, but
you must specify the message number. Also, you may be required
to include a message; therefore you may specify a message in the
RESPOND command.
Format
Format
| OPR>RESPOND nnn /switch text
where nnn is the outstanding message number
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
and text is a single- or multiple-line response
Keywords
Keywords
nnn specifies the message number of a message that
was sent to you via WTOR (Write To Operator
with Response).
text specifies a single- or multiple-line response,
which you terminate with a carriage return.
If you press carriage return immediately after
the message number, OPR responds with ENTER
TEXT AND TERMINATE WITH ^Z. You can then
enter as many lines of text as needed. To end
the text input, press CTRL/Z and the OPR>
prompt returns.
3-101
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(RESPOND)
(RESPOND)
Switch
| Switch
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Examples
Examples
1. Specify the RESPOND command to reply to message number 23,
which was a Page Limit Exceeded message for printer 1.
12:30:00 <23> Printer 1 --Page Limit Exceeded--
Job OPRC Req #147 for REILLY
Type 'Respond CANCEL' to Cancel the
Job
Type 'Respond IGNORE' to Ignore the
Error
_______ __ ___________
OPR>RESPOND 23 IGNORE
OPR>
2. Specify the RESPOND command to reply to message number 67,
which was a request to remove a structure (TOPS-20 DISMOUNT
command).
13:57:01 <67> --DISMOUNT QUERY--
Removal of structure PERF20: (Alias PERF20:)
requested.
Other jobs are currently using it. Should
removal request be processed (YES or NO)?
User KONEN, Job 26, Line 115
_______ __ _______
OPR>RESPOND 67 NO
OPR>
3. Specify the RESPOND command to reply to message number 12,
which was a user's inquiry to whether timesharing is
available after 18:00.
9:32:54 <12> --Message from Timesharing User--
JOB 31 PTAYLOR at Terminal 121
WILL TIMESHARING BE AVAILABLE AFTER 18:00
_______ _______
OPR>RESPOND 12
___________ __ _________ _____ _____ _______
TIMESHARING IS AVAILABLE UNTIL 23:00 TONIGHT^Z
^
|
3-102
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(RESPOND)
(RESPOND)
OPR>
3-103
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ROUTE)
(ROUTE)
ROUTE - Routing Output Between Nodes
ROUTE - Routing Output Between Nodes
Function
Function
The ROUTE command changes the destination of output requests, so
that the output intended for a specific unit (the source unit)
will automatically be output on another unit (the destination
unit). The source and destination units may be on the same node,
or they may be on different nodes.
This function is useful when a unit malfunctions and the output
from that device is immediately necessary.
If you are an operator at a central site, you can route output
from one unit to another, on the same or any other node.
However, output cannot be processed on another host system. If
output is routed to another host node, the request(s) will remain
in the queue indefinitely, because the request cannot be
processed. If you are an operator at a remote node, you can
route requests from one unit to another on your node.
All device routing is entered into the system route table, which
can be examined using the OPR command SHOW ROUTE-TABLE, described
in this chapter. The ROUTE command also allows you to end
routing and delete the entry from the system route table, by
omitting the information pertaining to the destination unit(s)
and node.
Format
Format
OPR>ROUTE keyword source-argument destination-argument
where keyword can be one of the following:
ALL-DEVICES
CARD-PUNCH
PAPER-TAPE-PUNCH
PLOTTER
PRINTER
followed by one of these source arguments:
unit-number
ALL-UNITS
or the argument for the PRINTER keyword:
| aliasname
3-104
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ROUTE)
(ROUTE)
CLUSTER nn
followed by: NODE node-name::
or DQS queuename
followed by: NODE node-name::
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
optionally followed by the switches:
| /CLUSTER-NODE:cluster-node-name
/NODE:node-name::
ALL-DEVICES is followed by one of these source arguments:
node-name::
ALL-NODES
followed by one of these destination arguments:
unit-number
ALL-UNITS
or the argument for the PRINTER keyword:
|
| aliasname
CLUSTER nn
followed by: NODE node-name::
or DQS queuename
followed by: NODE node-name::
or LAT
followed by: SERVICE "name"
SERVER "name"
or followed by: PORT "name"
SERVER "name"
optionally followed by the switches:
| /CLUSTER-NODE:cluster-node-name
/NODE:node-name::
ALL-DEVICES is followed by this destination argument:
node-name::
3-105
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ROUTE)
(ROUTE)
The source-information is always required. It specifies the
source unit and node from which routing is to occur.
The destination-information is optional, and specifies the
destination unit and node to which routing is to occur. If you
omit the destination-information, any existing entries in the
system route table that refer to the source will be deleted, and
the appropriate routing will be ended.
Because the format and arguments used with the ROUTE depend
largely on the keyword you use, it is highly recommended that you
use the recognition feature () until you feel comfortable
with the command format.
Keywords
Keywords
ALL-DEVICES specifies all device output (card punch, paper
tape punch, plotter, and printer) at the node.
CARD-PUNCH specifies card-punch output.
PAPER-TAPE-PUNCH specifies paper-tape-punch output.
PLOTTER specifies plotter output.
| PRINTER specifies printer output. You can use an
| alias name defined with the DEFINE ALIAS
| command to reference a printer specification
| in this command.
Arguments
Arguments (for ALL-DEVICES)
source-information
specifies the node(s) from which the output is
to be routed. The source-information for
ALL-DEVICES is specified by the node name
followed by two colons (for example:
KL2102::) or by the keyword ALL-NODES.
destination-information
specifies the node(s) to which the output will
be routed. For ALL-DEVICES, the
destination-information is specified by the
node name, followed by two colons (for
example: KL2102::).
3-106
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ROUTE)
(ROUTE)
Arguments
Arguments (for keywords CARD-PUNCH, PAPER-TAPE PUNCH, and PLOTTER)
source information
specifies the unit and node from which the
output will be routed. The unit number is
specified as either n (for a specific unit) or
ALL-UNITS, to designate that all output for
the appropriate device is to be routed. Note
that if you specify a unit number, only the
requests made for that specific unit (with the
/UNIT switch) will be routed. The node is
specified by the switch /NODE:name::
(described below). If you omit the node
specification, the node to which you are
connected is assumed.
destination-information
specifies the unit and node to which the
output will be routed. The unit is specified
by n, the unit number, or ALL-UNITS. The node
is specified by the switch /NODE:name::, which
is described below. If you omit the /NODE
switch, the node to which you are connected is
assumed.
Arguments
Arguments (for the PRINTER keyword)
| aliasname specifies an alias name defined with the
| DEFINE ALIAS command to reference a printer
| specification.
CLUSTER nn specifies a printer on a node within a
cluster. A cluster is a configuration of
processors with similar internal
characteristics. Each processor in the
configuration is identified by a node name.
For example, HUEY::, DEWEY::, and LOUIE:: can
be three nodes within a cluster of TOPS-20
processors.
NODE node-name::
specifies that the printer device for a
cluster be started. The double colon (::)
following the node name is not needed.
For the CLUSTER argument, NODE node-name::
specifies a node within the cluster and cannot
3-107
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ROUTE)
(ROUTE)
be the local node or an alias.
DQS queuename specifies the Distributed Queue Service
allowing users to queue print requests to VMS
systems using DECnet. DQS accepts the user
specified print request and transmits it to
the remote VMS node. The "queuename"
specifies the VMS queuename and can be a
string of 1 to 31 characters, consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
NODE node-name::
specifies the VMS node where the print request
is to be processed. The double colon (::)
following the node name is not needed.
For the DQS argument, NODE node-name::
specifies the VMS nodename and cannot be an
alias.
LAT specifies the Local Area Transport service
used to control communication between LAT
hosts and terminals on the Ethernet. With the
LAT keyword, you specify the SERVICE or PORT
and its SERVER name to establish communication
between your system, running LAT software, and
the resource printer terminal.
You cannot use the following
SERVICE/PORT/SERVER specifications:
SERVICE name only
SERVER name only
PORT name only
SERVICE name and PORT name
SERVICE, SERVER, and PORT names
Refer to Chapter 4 for additional information
about LAT communications.
PORT "name"
specifies the communication path between the
host system and the printer resource or the
access point that the node represents to the
user. The "name" is the port name and can
have from 1 to 16 characters consisting of
alphanumeric characters, underscores, dashes,
and dollar signs.
3-108
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ROUTE)
(ROUTE)
SERVICE "name"
specifies the resource and establishes the LAT
access path to the resource. The "name" is
the service name and can have from 1 to 16
characters consisting of alphanumeric
characters, underscores, dashes, and dollar
signs.
SERVER "name"
specifies the server name of the resource
printer terminal. This name can be the LAT
box with the proper LAT software running in
it. The name can be from 1 to 6 alphanumeric
characters in length.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the request is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the node(s) from and to which
output is to be routed. In the
source-information, /NODE designates the
source node. In the destination-information,
/NODE designates the destination node. The
double colon (::) following the node name is
optional.
Restriction
Restriction
You cannot route output from ALL-UNITS to a specific unit number.
If you type this command, the following error occurs:
_____ _______ __________________ ______
OPR>ROUTE PRINTER ALL-UNITS/KL2102:: 0
OPR>
15:15:36 --Cannot Route a Generic Unit--
OPR>
This error is produced to prevent output from being processed on
a unit that does not have certain necessary characteristics. For
3-109
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ROUTE)
(ROUTE)
example, if printer 0 does not have lowercase capability, and if
the requests being routed require a printer with lowercase
capability, then the requests cannot be processed on printer 0.
3-110
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(ROUTE)
(ROUTE)
Examples
Examples
1. To route the output that is destined for printer unit 0 to
printer unit 1, on the same node, use the following command:
_____ _______ _ ______
OPR>ROUTE PRINTER 0 1
OPR>
15:33:12 --Printer 0 [KL2102] Routed to Printer 1 [KL2102]--
OPR>
2. To end the routing for printer 0 and to delete the entry from
the routing table, use the following command:
_____ _______ ______
OPR>ROUTE PRINTER 0
OPR>
15:40:10 --Routing for Printer 0 [KL2102] Deleted--
OPR>
3. To route all the output that is going to node DN200 to node
KL2102, use the following command:
_____ ___________ ________ _____________
OPR>ROUTE ALL-DEVICES GIDNEY:: KL2102::
OPR>
15:43:08 --Node DN200 Routed to KL2102--
OPR>
3-111
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SEND)
(SEND)
SEND - Sending Messages
SEND - Sending Messages
Function
Function
The SEND command sends single- or multiple-line messages to a
specific destination as defined by the keyword. The SEND command
allows you to specify a one-line message terminated with a
carriage return or a multiple-line message terminated with a
CTRL/Z.
If you specify SEND ALL, you can only specify a single-line
message terminated by a carriage return.
Format
Format
| OPR>SEND keyword nn /switch message
where keyword can be one of the following:
ALL
BATCH-STREAM
JOB
OPERATOR
TERMINAL
followed by a stream/unit number:
nn
and optionally, for the BATCH-STREAM and OPERATOR keywords:
/NODE:node-name::
/CLUSTER-NODE:cluster-node-name
followed by a single- or multiple-line message
Keywords
Keywords
ALL specifies that a message be sent to all
terminals in the entire system. If you
specify the ALL keyword with the
/CLUSTER-NODE: switch, all terminals for that
node receive the text. You can give only
single-line messages when you specify ALL.
BATCH-STREAM specifies that a message be sent to a
particular batch job, or over an IBM emulation
3-112
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SEND)
(SEND)
node to a remote IBM host. The stream number
must be supplied with this keyword.
JOB specifies that a message be sent to a
particular job that is currently processing
under timesharing or within the batch system.
The job number must be supplied with this
keyword.
OPERATOR specifies that a message be sent to another
operator at another node with the /NODE:
switch. If you do not specify the /NODE:
switch, the message is sent to all operators
at all nodes.
TERMINAL specifies that a message be sent to a
particular logged-in terminal. The terminal
number must be supplied for this keyword.
Switches
Switches
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
This switch cannot be used with the ALL
keyword.
/CLUSTER-NODE:cluster-node-name
specifies the particular cluster node within
the system cluster that your message is sent.
The "cluster-node-name" qualifier can be any
node name within the cluster or an asterisk
(*). The asterisk specifies all nodes within
the cluster. (This switch is valid only for
the ALL keyword.)
Examples
Examples
1. Specify the SEND command to notify all users that timesharing
ends in 30 minutes.
____ ___ ___________ ____ __ __ ____________
OPR>SEND ALL TIMESHARING ENDS IN 30 MINUTES
OPR>
14:57:05 --SEND Command Completed--
OPR>
3-113
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SEND)
(SEND)
2. Specify the SEND command to notify all operators that a new
stand-alone schedule has been posted.
____ ________ ___ ___________ ________ __ ___________
OPR>SEND OPERATOR NEW STAND-ALONE SCHEDULE IS POSTED
OPR>
12:05:35
From Operator Terminal 1: NEW STAND-ALONE SCHEDULE IS POSTED
OPR>
12:05:39 --SEND Command Completed--
OPR>
3. Specify the SEND command to notify job 32 to stop queueing
print requests due to a problem with the line printer at the
central site.
____ ___ __ __ ___ ___________
OPR>SEND JOB 32 DO NOT QUEUE-
___ _____ ____ _____ _____________
ANY PRINT JOBS UNTIL NOTIFIED
OPR>
10:39:05 --SEND Command Completed--
OPR>
3-114
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET)
(SET)
SET - Setting Parameters for System Devices
SET - Setting Parameters for System Devices
Function
Function
The SET command sets various system parameters for the system's
devices and features.
In addition, the SET command can be issued before a particular
device (queue) or stream has been started or becomes active. In
particular, the SET command is very useful within the PTYCON.ATO
file for system start-up and it can be used during normal system
operation as well.
Because the SET command is complex with multiple keywords,
arguments, switches, and numeric values, each SET keyword command
is described in the same format as individual OPR commands.
Format
Format
OPR>SET keyword
where keyword can be one of the following:
BATCH-STREAM
CARD-PUNCH
DISK-DRIVE
JOB
NODE
ONLINE
PAPER-TAPE-PUNCH
PLOTTER
PORT
PRINTER
SCHEDULER
STRUCTURE
TAPE-DRIVE
followed by one or keywords, arguments, switches, and values
described in the SET command subsections.
3-115
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET BATCH-STREAM)
(SET BATCH-STREAM)
SET BATCH-STREAM - Setting Batch Stream Parameters
SET BATCH-STREAM - Setting Batch Stream Parameters
Function
Function
The SET BATCH-STREAM command sets the characteristics of a
particular stream or a range of streams. These characteristics
remain in effect until you reissue the SET BATCH-STREAM command.
Format
Format
| OPR>SET BATCH-STREAM nn /switch argument /switch
where nn must be the stream number
or a range: n:m
and, optionally, the switch:
/NODE:node-name::
followed by one of these arguments:
ATTRIBUTE BATCON
SITGO
NOOPR-INTERVENTION
OPR-INTERVENTION
PRIORITY-LIMITS nn
n:m
TIME-LIMITS nn
n:m
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Arguments
Arguments
nn specifies a batch-stream number. The number
is usually from 0 to 5, but can be larger if
your installation uses additional batch
streams.
n:m specifies a range of batch streams.
ATTRIBUTE specifies whether the batch stream operates
with the BATCON or with the SITGO program.
3-116
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET BATCH-STREAM)
(SET BATCH-STREAM)
BATCON specifies that the batch stream use the BATCON
controller. This is the system default batch
controller.
SITGO specifies the SITGO batch processor, which
consists of a fast FORTRAN compiler for
compiling FORTRAN programs in a batch stream.
NOOPR-INTERVENTION specifies that a user cannot make any requests
in the batch job that require you to perform
an action of some kind or require you to send
a message. If a batch job has
NOOPR-INTERVENTION set, any messages it sends
are ignored and you are not asked to perform
any action. If the batch job requests
mountable devices, and if the job must wait
until the device is mounted, the job will
receive an error.
OPR-INTERVENTION specifies that the user can pass messages to
you and that you are available to perform
actions that a user or batch job requests.
PRIORITY-LIMITS nn specifies the priority limits of a batch
stream or a range of batch streams at the
central site or at a node. The numeric value
associated with this argument means that only
batch jobs submitted by users with the
/PRIORITY: switch specifying the number (or
range) you set for the batch stream can
execute in that stream. The numeric value for
the PRIORITY-LIMITS argument can be from 1 to
63. The higher the number, the higher the
priority.
TIME-LIMITS nn specifies the maximum execution time limit for
a given batch stream or a range of batch
streams. When a batch job enters a batch
stream, it receives a default execution time,
such as five minutes. If the job exceeds this
time limit and if the user who submitted the
batch job set up his control file to handle
time limits, the batch system gives the job an
additional 10% of the allocated time. If the
job exceeds this additional 10%, the job is
canceled. The TIME-LIMITS argument allows you
to specify that batch jobs that are set to run
a certain length of time will run in the
specified batch-stream number (or range). The
numeric value for the TIME-LIMITS argument can
be from 0 to 99999, representing minutes.
3-117
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET BATCH-STREAM)
(SET BATCH-STREAM)
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the request is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
Examples
Examples
1. Specify the SET BATCH-STREAM command to set stream number 3
to have a priority limit of 63.
___ ____________ _ _______________ _______
OPR>SET BATCH-STREAM 3 PRIORITY-LIMITS 63
OPR>
13:20:54 Batch-stream 3 --Set Accepted--
OPR>
2. Specify the SET BATCH-STREAM command to set streams 0 through
2 for no operator intervention.
___ ____________ ___ _______________________
OPR>SET BATCH-STREAM 0:2 NOOPR-INTERVENTION
OPR>
16:11:17 Batch-stream 0 --Set Accepted--
16:11:21 Batch-stream 1 --Set Accepted--
16:11:24 Batch-stream 2 --Set Accepted--
OPR>
3-118
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET CARD-PUNCH)
(SET CARD-PUNCH)
SET CARD-PUNCH - Setting Card Punch Parameters
SET CARD-PUNCH - Setting Card Punch Parameters
Function
Function
The SET CARD-PUNCH command specifies what kind of jobs are
scheduled on this device. You can set the form type, output
limits (card limits), priority limits, and the action to be taken
when a job exceeds the output limit that you specify. This
command allows you to change the parameters that are set at
GALGEN time. You can specify a specific unit number or a range
of unit numbers.
The card-punch device handles standard 12-row 80-column cards.
The defaults for the card punch are set by your System Manager at
software-installation time through the generation of the
SPFORM.INI file.
Format
Format
| OPR>SET CARD-PUNCH nn /switch argument /switch
where nn must be a unit number
or a range: n:m
and, optionally, the switch:
/NODE:node-name::
followed by one of these arguments:
DESTINATION quoted string
FORMS-TYPE name
LIMIT-EXCEEDED-ACTION word
OUTPUT-LIMITS cards
PRIORITY-LIMITS nn
n:m
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Arguments
Arguments
nn specifies a card-punch unit number. The
number is usually from 0 to 5, but can be
3-119
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET CARD-PUNCH)
(SET CARD-PUNCH)
larger if your installation has acquired more
card-punch devices.
n:m specifies a range of card-punch unit numbers.
DESTINATION node"user password account"::device:[directory]
specifies the destination to receive IBM card
punch output. This is valid only if node has
been defined as an SNA-WORKSTATION with the
__________
DEFINE NODE command. See the DECnet/SNA
_______ ______ ___ _____ ______ ___ __________
TOPS-20 Remote Job Entry User's and Operator's
_____
Guide for more information.
FORMS-TYPE name specifies the name of the type of card-punch
forms. Your installation can have different
names for different types of card-punch forms.
By setting the FORMS-TYPE, you are specifying
the type of forms in the card punch.
LIMIT-EXCEEDED-ACTION word
specifies what action, if any, should be taken
if a card-punch job that is currently punching
on the unit number you specify exceeds the set
limit of output. The limit is set by the
OUTPUT-LIMITS argument. There are three
possible words associated with the
LIMIT-EXCEEDED-ACTION argument. They are:
ASK specifies that you are asked what to do if the
card-punch job exceeds the card limit on
output. You then have the option to continue
or abort the card-punch job.
CANCEL specifies that the card-punch job is
automatically canceled when the limit has been
exceeded.
IGNORE specifies that the card-punch job continues
automatically and the set output (card) limit
is ignored.
OUTPUT-LIMITS cards
specifies the maximum card limit for punched
output. This argument can also specify a
range of card limits. The card limit refers
to the number of output cards that are
punched. This command restricts the size of
3-120
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET CARD-PUNCH)
(SET CARD-PUNCH)
jobs that is sent to the card punch you
specify.
PRIORITY-LIMITS nn specifies the priority limits (numeric
importance) of a card punch or a range of card
punches at the central site or at a node. The
numeric value associated with this argument
means that only card-punch jobs submitted by
users with the /PRIORITY: switch specifying
the number (or range) you set for the card
punch can execute on that card punch. The
numeric value for the PRIORITY-LIMITS argument
can be from 1 to 63. The higher the number
is, the higher the priority is.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, or an SNA workstation. The default
is your own node. The double colon (::)
following the node name is optional.
Examples
Examples
1. Specify the SET CARD-PUNCH command to set the forms type to
5081s for all card-punch devices at your installation.
___ __________ ___ __________ _________
OPR>SET CARD-PUNCH 0:2 FORMS-TYPE 5081
OPR>
10:13:17 Card-Punch 0 --Set Accepted--
10:13:20 Card-Punch 1 --Set Accepted--
10:13:23 Card-Punch 2 --Set Accepted--
OPR>
2. Specify the SET CARD-PUNCH command to set all card-punch jobs
for a maximum output limit of 200 cards per job.
3-121
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET CARD-PUNCH)
(SET CARD-PUNCH)
___ __________ ___ ____________ ________
OPR>SET CARD-PUNCH 0:2 OUTPUT-LIMIT 200
OPR>
10:30:16 Card-Punch 0 --Set Accepted--
10:30:19 Card-Punch 1 --Set Accepted--
10:30:22 Card-Punch 2 --Set Accepted--
OPR>
3-122
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET DISK-DRIVE)
(SET DISK-DRIVE)
SET DISK-DRIVE - Setting Disk-Drive Parameters
SET DISK-DRIVE - Setting Disk-Drive Parameters
Function
Function
The SET DISK-DRIVE command sets the availability characteristics
of a particular disk drive device. With the use of this command,
you can allow or disallow users from mounting and dismounting
structures on the disk drive. You must specify the channel and
drive numbers, and either the AVAILABLE or UNAVAILABLE argument.
Format
Format
OPR>SET DISK-DRIVE CHANNEL nn argument DRIVE nn argument
where nn must be the channel number
optionally followed by the argument:
CONTROLLER nn
followed by the drive unit number
and either of the following arguments:
AVAILABLE
UNAVAILABLE
| optionally followed by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keywords
Keywords
CHANNEL nn specifies the channel number that connects the
disk drive with the central processing unit.
The SHOW STATUS DISK-DRIVE command displays
the available channels on your system.
DRIVE nn specifies the physical unit number of the disk
drive. The SHOW STATUS DISK-DRIVE command
displays the drive numbers that are associated
with the channels on your system.
Arguments
Arguments
CONTROLLER nn specifies the number of the disk drive
3-123
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET DISK-DRIVE)
(SET DISK-DRIVE)
controller. The SHOW STATUS DISK-DRIVE
command displays the controller numbers that
are associated with the disk drives on your
system.
AVAILABLE specifies that users can now MOUNT structures
on this particular disk drive. This argument
cancels the effect of the UNAVAILABLE
argument. The PTYCON.ATO file determines
whether each of the disk drives at your
installation are available or unavailable at
system start-up.
UNAVAILABLE specifies that users cannot MOUNT structures
on this particular disk drive. This argument
cancels the effect of the AVAILABLE argument.
If a user is currently using a structure on
this disk drive, the disk drive becomes
unavailable after the user completes his work.
If the system crashes or is shutdown, the
command SET DISK-DRIVE CHANNEL nn DRIVE nn
UNAVAILABLE remains in effect after the system
is in operation again.
When you specify the UNAVAILABLE argument, you
can enter a single- or multiple-line response
and confirm with a carriage return, or you can
confirm with a carriage return immediately
after the UNAVAILABLE argument and OPR
responds with ENTER TEXT AND TERMINATE WITH
^Z. You then enter as many lines of text for
a response as you need. When you press
CTRL/Z, the OPR> prompt returns and your
report is logged into the ERROR.SYS file.
Switch
Switch
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
3-124
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET DISK-DRIVE)
(SET DISK-DRIVE)
Examples
Examples
1. Specify the SET DISK-DRIVE command to set drive 2 on channel
2 to be unavailable. Any users currently using this device
are allowed to finish their work before the device becomes
unavailable to them. Any users requesting a structure mount
on this device receives a message notifying them that the
structure is unavailable.
___ __________ _______ _ _____ _ ________________
OPR>SET DISK-DRIVE CHANNEL 2 DRIVE 2 UNAVAILABLE
Enter Text and Terminate with ^Z
_____ ____ __ ________
DRIVE MUST BE ADJUSTED^Z
^
|
OPR>
10:23:56 --Disk Drive Set Unavailable--
Chan 2 Drive 2 set unavailable for mounting by MOUNTR
OPR>
2. Specify the SET DISK-DRIVE command to make any structure on
disk drive 2 on channel 2 available for mounts and dismounts.
___ __________ _______ _ _____ _ ______________
OPR>SET DISK-DRIVE CHANNEL 2 DRIVE 2 AVAILABLE
OPR>
12:02:24 --Disk Drive Set Available--
Chan 2 Drive 2 set available for mounting by MOUNTR
OPR>
3-125
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET JOB)
(SET JOB)
SET JOB - Setting Characteristics for Jobs
SET JOB - Setting Characteristics for Jobs
Function
Function
The SET JOB command sets the characteristics for a particular job
number. You can set the job for operator intervention allowed,
no operator intervention allowed, or you can change the scheduler
class of the job.
Format
Format
| OPR>SET JOB nn argument /switch
where nn must be the job number
followed by one of these arguments:
NOOPR-INTERVENTION
OPR-INTERVENTION
SCHEDULER-CLASS n
| optionally followed by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Arguments
Arguments
nn specifies a job number currently in the
system. The numeric value can be from 0 to
99999.
NOOPR-INTERVENTION specifies that a user cannot make any requests
in the job that require you to perform an
action of some kind and/or produce a message
to be answered by you. If the job has a
NOOPR-INTERVENTION setting, the messages are
ignored; you are not asked to perform any
action.
OPR-INTERVENTION specifies that a user associated with the
specified job number can pass messages to you
and you can perform the requested actions.
SCHEDULER-CLASS n specifies the scheduler class for the job be
changed. This keyword can be used only when
POLICY-PROGRAM is controlling your
class-scheduling. Refer to your System
3-126
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET JOB)
(SET JOB)
Manager about a POLICY-PROGRAM accounting
system before you issue this command.
Switch
| Switch
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Restrictions
Restrictions
If you attempt to set the SCHEDULER-CLASS for a particular job
without the POLICY-PROGRAM initiated at your installation, you
will receive the following error message:
hh:mm:ss --Set Job Scheduler Error: Cannot change class--
Examples
Examples
1. Specify the SET JOB command to allow operator intervention
for job number 100.
___ ___ ___ _____________________
OPR>SET JOB 100 OPR-INTERVENTION
OPR>
15:55:15 Job 100 --Modified--
OPR>
2. Specify the SET JOB command to not allow operator
intervention for job number 50.
___ ___ __ _______________________
OPR>SET JOB 50 NOOPR-INTERVENTION
OPR>
16:43:34 Job 50 --Modified--
OPR>
3-127
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET NODE)
(SET NODE)
SET NODE - Setting Node Parameters
SET NODE - Setting Node Parameters
Function
Function
The SET NODE command is applicable only if your installation has
IBM communications software.
The SET NODE command sets the modem-related and
data-transfer-related parameters for DN60 nodes, and sets the
characteristics for SNA workstations.
Before you set the parameters for a node, you must define the
node name, type, and mode with the DEFINE command. Refer to the
DEFINE command in this chapter.
Format
Format
OPR>SET NODE keyword arguments
where keyword is: node-name::
followed by one of these arguments:
BYTES-PER-MESSAGE b
CLEAR-SEND-DELAY d
RECORDS-PER-MESSAGE r
TIMEOUT-CATEGORY PRIMARY
SECONDARY
TRANSPARENCY ON
OFF
or for SNA workstations, one of these arguments:
APPLICATION name
CHARACTER-SET filespec
CIRCUIT circuit-id
DATA string
LOGON-MODE name
Keyword
Keyword
node-name:: specifies the node name of the remote station
for IBM communications. The double colon (::)
following the node name is optional.
3-128
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET NODE)
(SET NODE)
Arguments
Arguments
BYTES-PER-MESSAGE b
specifies the number of bytes, b, per message
that the front end uses to communicate with
the remote site. There is no limit to the
number of bytes you can supply.
CLEAR-SEND-DELAY d
specifies a clear-to-send delay, where d = 0,
1, 3, 9, or 13 milliseconds. The default is 3
milliseconds.
RECORDS-PER-MESSAGE r
specifies the number of records per message,
where r can equal:
0 for unlimited number of records (the default
for 3780)
2 for a unit with no multirecord feature
7 for a unit like an IBM 2780 with the
multirecord feature (the default for 2780)
TIMEOUT-CATEGORY PRIMARY
SECONDARY
specifies the timeout category used by the BSC
protocol to determine how connecting systems
bid for use of the line. Two systems bidding
for the use of a line must not be in the same
timeout category, since this condition can
result in simultaneous bids for a line and a
"deadly embrace". To prevent this, one system
is placed in the PRIMARY (p) category and the
other in the SECONDARY (s) category.
The timeout category for the HASP spooler is
always SECONDARY so when the TOPS-20 host
connects to a HASP system, it must be placed
in the PRIMARY timeout category. The timeout
category for IBM 2780s and 3780s is usually
hardwired as PRIMARY, so when the TOPS-20 host
connects to stations like these, it must
usually be placed in the SECONDARY timeout
category. The timeout category for the ASP
spooler may be PRIMARY. The default timeout
3-129
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET NODE)
(SET NODE)
category is PRIMARY.
TRANSPARENCY ON specifies a transmission mode where the
OFF specifies a transmission mode where the
recognition of most control characters is
suppressed (TRANSPARENCY ON argument). The
argument can only be specified when using
HASP. The default TRANSPARENCY is OFF.
Arguments
Arguments (for SNA workstations)
__________
For more information about SNA workstations, refer to the DECnet/SNA
_______ ______ ___ _____ ______ ___ __________ _____
TOPS-20 Remote Job Entry User's and Operator's Guide.
APPLICATION name Specifies the name of the
application in the IBM host to
which the workstation connects.
CHARACTER-SET filespec Specifies the name of the file that
contains the ASCII/EBCDIC
translation table used by the
workstation.
CIRCUIT circuit-id Specifies the name of the circuit
that the Gateway uses to reach the
IBM host.
DATA string Supplies additional log-on
information required by the job
entry subsystem in the IBM host.
LOGON-MODE name Specifies a name that the IBM host
uses to obtain predefined
characteristics for the session
being established.
These arguments for the SET NODE command correspond to parameters set
by the IBM host's system manager. The SET NODE command gives you the
option of changing or adding to information associated with the access
name you specified in the DEFINE command. If you specify a null
argument for any parameter, the parameter is automatically cleared and
reset to the information specified in the access name.
To use the APPLICATION parameter, you must know the name of the IBM
application to which you want to connect. Contact your IBM system
manager for this information.
3-130
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET NODE)
(SET NODE)
Examples
Examples
1. You specify the SET NODE command to change the TRANSPARENCY
from the OFF default to ON for node IBM2::.
___ ____ ______ ____________ _______
OPR>SET NODE IBM2:: TRANSPARENCY ON
OPR>
16:32:43 -- Set for Node IBM2 Accepted --
OPR>
2. You specify the SET NODE command to set the clear-to-send
delay of 3 milliseconds for node IBM1::.
___ ____ ______ ________________ ______
OPR>SET NODE IBM1:: CLEAR-SEND-DELAY 3
OPR>
17:23:45 -- Set for Node IBM1 Accepted --
OPR>
3-131
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET ONLINE)
(SET ONLINE)
SET ONLINE - Setting a Device On-Line
SET ONLINE - Setting a Device On-Line
Function
Function
The SET ONLINE command sets the devices listed below on-line when
the device has been newly installed at your operations site.
This command is valid only if your site has a DX20 channel
controller installed and on-line.
The devices that are interfaced through the DX20 are:
1. TX01 - tape controller
2. TX03 - channel selector
3. TX05 - tape drive selector
4. TU70 - tape drive
5. TU71 - tape drive
6. TU72 - tape drive
In addition, this command is helpful when Field Service takes one
of these devices off-line for repair and then returns the device
back to you for your control.
The SET ONLINE command's arguments are channel number, device
unit number, and controller number, separated by commas. If the
device has no controller number, type -1.
NOTE
This command currently accepts an alternate
channel number, device unit number, and
controller number separated by commas. However,
these alternate arguments are not used by the
system and are provided for future use.
Format
Format
| OPR>SET ONLINE ch,unit,cntrlr /switch
where ch is the channel number
unit is the device unit number
cntrlr is the controller number
3-132
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET ONLINE)
(SET ONLINE)
| optionally followed by the switch:
|
| /CLUSTER-NODE:cluster-node-name
|
|
Switch
| Switch
|
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Restriction
Restriction
Once the monitor has been reloaded, you do not need to SET the
device ONLINE again. The device is automatically recognized by
the monitor as being on-line.
Examples
Examples
1. You set the hardware device TX05 on-line after it has been
installed during timesharing with an address of channel 1,
unit 1, controller 1.
___ ______ __________
OPR>SET ONLINE 1,1,1
OPR>
8:32:13 --Set Online Accepted--
OPR>
2. You set the hardware device TU70 on-line after Field Service
repaired the tape unit.
___ ______ __________
OPR>SET ONLINE 1,2,1
OPR>
14:43:09 --Set Online Accepted--
OPR>
3-133
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PAPER-TAPE-PUNCH)
(SET PAPER-TAPE-PUNCH)
SET PAPER-TAPE-PUNCH - Setting Paper-Tape-Punch Parameters
SET PAPER-TAPE-PUNCH - Setting Paper-Tape-Punch Parameters
Function
Function
The SET PAPER-TAPE-PUNCH command specifies what kind of jobs will
be scheduled on this device. You can set the forms type, output
limits (fold limits), priority limits, and the action to be taken
when a job exceeds the output limit that you specify. This
command allows you change the parameters that are set at GALGEN
time. You can specify a specific unit number or a range of unit
numbers.
The defaults for the paper-tape punch are set by your System
Manager at software-installation time through the generation of
the SPFORM.INI file. These defaults are normally
referred to as NORMAL in most installations.
Format
Format
| OPR>SET PAPER-TAPE-PUNCH nn /switch argument /switch
where nn must be a unit number
or a range: n:m
and, optionally, the switch:
/NODE:node-name::
followed by one of these arguments:
FORMS-TYPE name
LIMIT-EXCEEDED-ACTION word
OUTPUT-LIMITS folds
PRIORITY-LIMITS nn
n:m
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Arguments
Arguments
nn specifies a paper-tape-punch unit number. The
number is usually from 0 to 5, but can be
larger if your installation has acquired more
paper-tape-punch devices.
3-134
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PAPER-TAPE-PUNCH)
(SET PAPER-TAPE-PUNCH)
n:m specifies a range of paper-tape punches.
FORMS-TYPE name specifies the name of the type of paper-tape
forms. Typically in some installations, the
normal paper-tape form is referred to as a
1-inch wide fan-fold, and can be abbreviated
as 1WFF or NORMAL. Your installation can have
different form names for different types of
paper-tape. By setting the FORMS-TYPE, you
are specifying the type of forms in the
paper-tape punch.
LIMIT-EXCEEDED-ACTION word
specifies what action, if any, should be taken
if a paper-tape job that is currently punching
on the unit number you specify exceeds the set
limit of output. The limit is set with the
OUTPUT-LIMITS argument. There are three
possible words associated with the
LIMIT-EXCEEDED-ACTION argument. They are:
ASK specifies that you are asked what to do if the
paper-tape job exceeds the fold limit on
output. You then have the option to continue
or abort the paper-tape job.
CANCEL specifies that the paper-tape job is
automatically canceled when the limit has been
exceeded.
IGNORE specifies that the paper-tape job continues
automatically and the specified output fold
limit will be ignored.
OUTPUT-LIMITS folds
specifies the maximum fold limit for punched
paper-tape output. This argument can also
specify a range of fold limits. The fold
limit refers to the number of output folds
that are punched. This command restricts the
size of jobs that are sent to the paper-tape
punch you specify.
PRIORITY-LIMITS nn
n:m
specifies the priority limits (numeric
importance) of a paper-tape punch or a range
of paper-tape punches at the central site or
3-135
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PAPER-TAPE-PUNCH)
(SET PAPER-TAPE-PUNCH)
at a node. The numeric value associated with
this argument means that only paper-tape jobs
submitted by users with the /PRIORITY: switch
specifying the number (or range) you set for
the paper-tape punch can execute on that
paper-tape punch. The numeric value for the
PRIORITY-LIMITS argument can be from 1 to 63.
The higher the number is, the higher the
priority is.
Switches
Switches
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the commmand is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Examples
Examples
1. Specify the SET PAPER-TAPE-PUNCH command to set the default
form type to 1WFF for a paper-tape-punch device at your
installation.
___ ________________ _ __________ _________
OPR>SET PAPER-TAPE-PUNCH 0 FORMS-TYPE 1WFF
OPR>
12:45:09 Papertape 0 --Set Accepted--
OPR>
2. Specify the SET PAPER-TAPE-PUNCH command form, to set all
paper-tape-punch jobs for a maximum output limit of 25 folds
per job.
___ ________________ ___ ____________ _______
OPR>SET PAPER-TAPE-PUNCH 0:1 OUTPUT-LIMIT 25
OPR>
13:45:07 Papertape 0 --Set Accepted--
OPR>
3-136
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PLOTTER)
(SET PLOTTER)
SET PLOTTER - Setting Plotter Parameters
SET PLOTTER - Setting Plotter Parameters
Function
Function
The SET PLOTTER command specifies what kind of jobs are scheduled
on this device. You can set the forms type, output limits (step
limits), priority limits, and the action to be taken when a job
exceeds the output limit that you specify. This command allows
you change the parameters that are set at GALGEN time. You can
specify a specific unit number or a range of unit numbers.
The plotter device draws (or plots) ink plots of
computer-generated data. Its movement in producing the output is
measured in "steps". The steps refer to the speed per second of
the plotter and the distance (or size) that the pencils move on
the output paper. The paper for the plotter is either drum feed
or bed feed.
The defaults for the plotter are set by your System Manager at
software-installation time through the generation of the
SPFORM.INI file. At some installations, the default
settings for the plotter are referred to as NORMAL.
Format
Format
| OPR>SET PLOTTER nn /switch argument /switch
where nn must be a unit number
or a range: n:m
and, optionally the switch:
/NODE:node-name::
followed by one of these arguments:
FORMS-TYPE name
LIMIT-EXCEEDED-ACTION word
OUTPUT-LIMITS steps
PRIORITY-LIMITS nn
n:m
| followed optionally by the switch:
|
| /CLUSTER-NODE:cluster-node-name
3-137
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PLOTTER)
(SET PLOTTER)
Arguments
Arguments
nn specifies a plotter unit number. The number
is usually from 0 to 5, but can be larger if
your installation has more plotter devices.
n:m specifies a range of plotter unit numbers.
FORMS-TYPE name specifies the name of the type of plotter
forms. Typically, the normal plotter paper
form is referred to as roll feed or bed feed.
This can be referred to as type ROLL, DRUM, or
BED. Your installation can have different
form names for different plotter types.
LIMIT-EXCEEDED-ACTION word
specifies what action, if any, should be taken
if a plotter job that is currently plotting on
the unit number you specify exceeds the set
limit of output. The limit is set with the
OUTPUT-LIMITS argument. There are three
possible words associated with the
LIMIT-EXCEEDED-ACTION argument. They are:
ASK specifies that you are asked what to do if the
plotter job exceeds the step limit on output.
You then have the option to continue or abort
the plotter job.
CANCEL specifies that the plotter job is
automatically canceled when the limit has been
exceeded.
IGNORE specifies that the plotter job continues
automatically and the specified output (step)
limit will be ignored.
OUTPUT-LIMIT steps
specifies the number of plotter steps per
second. A step is the horizontal and vertical
movement of the pen within the grid on the
paper. This is referred to as the size (or
distance). The number you specify represents
nnK steps (K = 1000). For example,
OUTPUT-LIMIT 3 is equal to 3000.
3-138
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PLOTTER)
(SET PLOTTER)
PRIORITY-LIMITS nn
n:m
specifies the priority limits (numeric
importance) of a plotter or a range of
plotters at the central site or at a node.
The numeric value associated with this
argument means that only plotter jobs
submitted by users with the /PRIORITY: switch
specifying the number (or range) you set for
the plotter can execute on that plotter. The
numeric value for the PRIORITY-LIMITS argument
can be from 1 to 63. The higher the number
is, the higher the priority is.
Switches
Switches
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
/NODE:node-name:: specifies the name of your host node, a remote
station, a VMS node, or a LAT server. The
default is your own node. The double colon
(::) following the node name is optional.
Examples
Examples
1. Specify the SET PLOTTER command to change the forms type of
the plotter.
___ _______ _ __________ _________
OPR>SET PLOTTER 1 FORMS-TYPE ROLL
OPR>
9:34:12 Plotter 1 --Set Accepted--
OPR>
2. Specify the SET PLOTTER command to change the output limit.
___ _______ _ ____________ ______
OPR>SET PLOTTER 0 OUTPUT-LIMIT 8
OPR>
10:11:12 Plotter 0 --Set Accepted--
OPR>
3-139
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PORT CI)
(SET PORT CI)
SET PORT CI - Controlling the CI port
SET PORT CI - Controlling the CI port
Function
Function
The SET PORT CI command allows or disallows using the CI20 port.
You can use this command only if your system has a CI20.
Set the CI port UNAVAILABLE to run diagnostics on the CI hardware
or to remove a TOPS-20 system from a CFS cluster. Never set the
CI port UNAVAILABLE without approval from your system manager.
_______ ______ _________ _____
See the TOPS-20 System Manager's Guide for more information.
Setting the CI port UNAVAILABLE helps you perform an orderly
TOPS-20 shutdown in a CFS configuration.
Format
Format
| OPR>SET PORT keyword argument /switch
where keyword must be: CI
and argument is one of the following:
AVAILABLE
UNAVAILABLE
| optionally followed by the switch:
|
| /CLUSTER-NODE:cluster-node-name
Keyword
Keyword
CI specifies the CI port.
Arguments
Arguments
AVAILABLE specifies that TOPS-20 start using the CI20
again. When you give this command, the system
asks you whether there is another TOPS-20 node
in the cluster. If yes, you will be
instructed to reboot the system. If you
answer no and the system discovers another
TOPS-20 system on the CI, one of the systems
will BUGHLT.
This argument cancels the effect of the
3-140
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PORT CI)
(SET PORT CI)
UNAVAILABLE argument. Once this command is
given and the CI20 microcode is successfully
loaded, the CI port remains AVAILABLE until it
is set UNAVAILABLE.
AVAILABLE is the default.
UNAVAILABLE specifies that TOPS-20 should stop using the
CI.
When you SET PORT CI UNAVAILABLE, the system
lists the structures that will be affected and
asks you to respond with ABORT, PROCEED or
FORCE. You must be sure that all multiaccess
structures are dismounted properly, or the
users will be "hung." Notify the users to
dismount the affected structures.
The SET PORT CI UNAVAILABLE command remains in
effect until you use the SET PORT CI AVAILABLE
command, even if the system crashes or is shut
down and rebooted.
If a massbus disk drive is dualported, it may
be necessary to switch to single port so
access to the drive can continue on one
system.
After giving the users time to dismount the
structure, use the RESPOND command with one of
the following options:
ABORT cancels the command without changing the
status of the CI or any structures.
PROCEED begins the procedure to set the CI port
unavailable.
FORCE dismounts all structures and sets the CI port
unavailable. (Use caution with this response;
structures are dismounted whether or not users
are accessing the structure.)
If a massbus drive is dualported, the system informs you with a
message. Respond by manually setting the port switch to a single
system. Then type the PROCEED response.
3-141
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PORT CI)
(SET PORT CI)
Switch
Switch
| /CLUSTER-NODE:cluster-node-name
|
| specifies the particular cluster node within
| the TOPS-20 cluster where the command is
| processed. The "cluster-node-name" qualifier
| can be any node name within the cluster or an
| asterisk (*). The asterisk specifies all
| nodes within the cluster.
Examples
Examples
1. Set the CI UNAVAILABLE to stop using the CI20.
___ ____ __ ___________ _____
OPR>SET PORT CI UNAVAILABLE
OPR>
12:14:48 <1> -- Port Unavailable Procedure Notice --
Setting CI Port 7 UNAVAILABLE
The following structure(s) need to be dismounted or removed.
DISK DRIVE INFORMATION DISK PACK INFO...
Chan-Cont Disk Mount Mount Usage
Type Drive Status Status Count Name Options
----- ---------------- ------ ----- ------------ -------
*RP06 0, ,2 Avail Mounted 1 AP02 (1/1)
RA81 7,07,5 Avail Mounted 1 EXODUS (1/1)
RA60 7,07,254 Avail Mounted 1 DRV354 (1/1)
RA81 7,07,18 Avail Mounted 0 DRV18 (1/1)
NOTE: Channel 7 indicates CI channel
(*) indicates dual ported disk drives
Type 'RESPOND option' where 'option' is one of the
following:
ABORT To cancel Port Unavailable Procedure.
PROCEED To follow normal port unavailable
procedure verifying each structure
change.
FORCE To proceed with no further notification.
Use this option with extreme caution.
_______ _ _______ _____
OPR>RESPOND 1 PROCEED
OPR>
12:15:33 -- Port Unavailable Procedure Notice --
Structure CHIP set exclusive due to
port unavailable operation
.
3-142
OPR COMMAND DESCRIPTIONS
OPR COMMAND DESCRIPTIONS
(SET PORT CI)
(SET PORT CI)
.
.
12:21:24 -- Port Unavailable Operation Completed --
Port Set Unavailable
OPR>
2. Set the CI AVAILABLE to allow use of the CI20 (single CI
system).
___ ____ __ _________ _____
OPR>SET PORT CI AVAILABLE
OPR>
17:40:31 <16> -- Port Available Procedure Notice --
Is there another TOPS-20 system
currently running on the CI?
'RESPOND Yes or No'
_______ __ __ _____
OPR>RESPOND 16 NO
OPR>
17:40:42 -- Port Available Operation Completed --
The following disk structures have been
returned to available:
Structure DISK1 set shared due to
port available operation
Channel 7 Controller 1 Drive 1 set available
Channel 7 Controller 7 Drive 8 set available
Channel 7 Controller 7 Drive 9 set available
Channel 7 Controller 8 Drive 254 set available
Port set available
3. Set the CI AVAILABLE to allow use of the CI20 (multiple CI
system).
___ ____ __ _________ _____
OPR>SET PORT CI AVAILABLE
OPR>
17:42:33 <18> -- Port Available Procedure Notice --
Is there another TOPS-20 system
currently running on the CI?
'RESPOND