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