čťťťĘĘťť
DPOUSPMGSFBLT PSH
'(6.723&<%(5 23(5$725¶6$1'86(5¶6*8,'(
&'&23(5$7,1*6<67(06 0(&&126365
90001100 2 i INDEX OF CONSOLE COMMANDS
Command Mode Page Command Mode Page
* DSD 2-15 LOCK DSD 2-13 Account Management DSD 2-22 LOGOFF DSD 2-13 ASSIGN DSD 2-12 MESSAGE DSD 2-13 AUTO DSD 2-12 MOVE O26 2-21 BLITZ DSD 2-12 O26 DIS 2-18 CFO DSD 2-12 O26 Special Keys O26 2-19 CHECK POINT SYSTEM DSD 2-12 OFF DSD 2-14 CKP DSD 2-12 OFFSW DSD 2-14 COMMENT DSD 2-12 ON DSD 2-14 COPY O26 2-21 ONSW DSD 2-14 D O26 2-21 OUT O26 2-21 DCP DIS 2-18 OVERRIDE DSD 2-14 DEBUG DSD 2-12 P O26 2-21 DIAL DSD 2-13 PURGE DSD 2-14 DIS DSD 2-13 RCP DIS 2-18 DIS O26 2-20 READ O26 2-20 DIS Displays DIS 2-16 REWIND O26 2-20 DISABLE DSD 2-13 RNR O26 2-21 DROP DSD 2-13 RNS DIS 2-18 DROP DIS 2-18 ROLLIN DSD 2-14 DROP O26 2-20 ROLLOUT DSD 2-14 DSD Displays DSD 2-9 ROLLOUT DIS 2-19 ELS DIS 2-18 RS O26 2-21 ENA DIS 2-18 STEP DSD 2-14 ENABLE DSD 2-13 SUI DIS 2-19 ENB DIS 2-18 SUN DIS 2-19 ENP DIS 2-18 UCC O26 2-21 ENS DIS 2-18 UNLOAD DSD 2-15 ENX DIS 2-18 UNLOCK DSD 2-15 FILE O26 2-20 UNSTEP DSD 2-15 FORM DSD 2-13 VSN DSD 2-15 GO DSD 2-13 WARN DSD 2-15 HOLD DIS 2-18 WRITE O26 2-21 IDLE DSD 2-13 X DSD 2-15 KILL DSD 2-13 XDIS O26 2-20 L O26 2-21 XDROP O26 2-20 LOAD Operator 2-41 Interface
90001100 A REVISION RECORD REVISION DESCRIPTION 1 Change bars will be made in the text to reflect edits made before the first production (1-1-2005) release. These change bars will be cleared on the first production revision (A).
2 Clarified the purpose of the punch queue and made other minor clarifications (1-5-2005) and typographical corrections.
3 Added console commands on inside front cover. Indexed Chapter 2. Wrote Preface. (1-9-2005)
A Manual released. This manual supports Paul Koning’s delta of 25 August 2004 based upon Tom Hunter’s (??-??-2005) Desktop Cyber 2.1b0 running MECC NOS 1.4 at PSR 552.
Publication No. 90001100 THIS IS A PRE-RELEASE DRAFT FOR YOUR REVIEW
Address comments concerning this REVISION LETTERS I, O, Q, V, AND X ARE NOT USED manual to:
J. Phillip Draughon © 2004, 2005 [email protected] by J. Phillip Draughon This document may be modified and redistributed under the terms of the license to Desktop Cyber 2.1b0 (see license.txt). www.controlfreaks.org iv 90001100 2 PREFACE
INTRODUCTION AUDIENCE AND ORGANISATION
Desktop Cyber is an emulator which brings This document assumes that you are familiar back to life the revolutionary design of Control with the host on which Desktop Cyber is being Data Corporation (CDC) 6000 series and run. No familiarity with the emulator hardware Cyber series mainframes. The first CDC or operating system is assumed. Cybers were designed and built by a small team headed by Seymour Cray at CDC’s This manual is organised as follows: Chippewa Falls labs in the early 1960s. Desktop Cyber emulates this series of Section 1 Installation and mainframes and peripherals in software. configuration. This section covers both NOS and host The software provides emulation of typical configuration matters. This 6000 and Cyber 7x and 17x systems including section is intended primary common peripherals such as operator console, for the individuals who will tape and disk drives, central memory, extended be installing the system and core storage, card readers and punches, maintaining the host/NOS printers, and terminal multiplexers. interface, but may not necessarily be involved in Desktop Cyber successfully dead starts and running the system or using it runs the following CDC operating systems: on a day-by-day basis. Chippewa OS (COS), SMM, KRONOS 2.1, NOS 1.2, NOS 1.3, NOS 1.4, NOS 2.2, NOS Section 2 Operations. This section 2.8.1, and NOS/BE 1.5. covers the day-to-day maintenance of the system This manual contains information necessary to including setting up user install, configure, operate, and use Desktop accounts, job management, Cyber running the Minnesota Educational and managing the Computing Consortium (MECC) version of host/system interface. The the Control Data Corporation’s Network intended audience is Operating System (NOS) 1.4. individuals who will keep the system running on a daily NOTE basis.
While Desktop Cyber runs many CDC operating systems on several hardware platforms, this Section 3 Usage. This section covers manual assumes the emulator will be running how to use NOS from the MECC NOS 1.4 on a Linux host. perspective of the end user running interactive and batch origin jobs.
90001100 2 v CONVENTIONS NOS Version 2 Installation Handbook, may not appear to be directly useful since it Literal messages displayed on the console (as addresses a later release of NOS, but many of opposed to a terminal) are shown in Paul the concepts still apply. Koning’s SEYMOUR font, which closely resembles the font used on early Control Data Publication Control Data Publication display consoles. Terminal sessions are shown Number and Year in upper case LIKE SO with terminal input NOS Version 1 Reference Manual, vol. 1 60435400J 1979 set from the corresponding lower case. NOS Version 1 Reference Manual, vol. 2 60445300E 1977
Command syntax descriptions and keystrokes NOS Version 1 Applications Programmers 60436000H 1980 are shown in upper case LIKE THIS with Instant command parameters (control point, user NOS Version 1 System Programmers 60449200G 1981 number, etc.) in italics. Keys with Instant multicharacter names are shown in small caps NOS Version 1 Operator’s Guide 60435600M 1980 as in ENTER, ESC, and ALT. NOS Version 1 System Maintenance 60455380H 1981 RELATED PUBLICATIONS Reference Manual NOS Version 2 Installation Handbook 60459320B 1983
This manual is not intended to be exhaustive. ALGOL 60 Version 3 Reference Manual 60329000D 1973 We know that setting up and running a mainframe—even when that mainframe is BASIC 2.1 Reference Manual 19980300B 1974 being emulated on a palmtop computer—is COBOL Version 5 Reference Manual 60497100H 1980
daunting if you don’t have extensive previous COMPASS Version 3 Reference Manual 60492600G 1979 experience with the computer or its operating system, so the purpose of this document is to FORTRAN 4 Reference Manual 60305600E 1974 get you over the initial hump. Other Control Fortran 5 Reference Manual 60481300H 1985 Data manuals cover the topics in this manual FORTRAN Common Library 60498200 1978 in greater depth. Mathematical Routines Reference Manual
The Controlfreaks maintain an extensive Sympl Version 1 Reference Manual 60496400F 1980 online library of publications with the Modify Reference Manual 60450100D 1978 generous permission of CDC’s successor, Text Editor Reference Manual 60436100 1979 British Telecom Consulting. Here are some of the manuals in the Controlfreaks inventory Update Reference Manual 60342500H 1978 which you may find useful. Some, such as the Xedit Version 3 Reference Manual 60455730 1978
vi 90001100 2 ACKNOWLEDGEMENTS Seymour Cray was born in 1925 in Chippewa Falls, Wisconsin; he died in 1996 in Colorado Springs, Tom Hunter expresses his thanks to the Colorado, from injuries suffered in a car accident. following people who have encouraged him and helped in various ways: COLOPHON The particular and peculiar variation of Wanee Hunter John Gibbins typefaces and the use of whitespace cannot be Clare Johnstone Steve Peltz preserved by any existing OCR technology. It David Webb Dave Mausner forms part of the aesthetic that made CDC a thing of interest to me. It's not just about Douglas Quebbeman Dennis Henriksen retrocomputing, it’s a gestalt. Jeff Woolsey Jeffrey Katcher Walter Spector Gerard van der Grinten —Douglas Hurst Quebbeman, Tony Epton Mike Arrington Founder of the Controlfreaks Paul Repacholi Joe Cychosz John Zabolitzky Tim Smart (BTC) The look and feel of the Desktop Cyber 2.1 Freddy Meerwaldt Barry Murphy (BTC) Operator’s and User’s Guide is based upon the James Wiley Peter Bartsch layout of manuals produced by CDC in the late John Laird Phillip Draughon 1970s and early 1980s. Because of the Kent Olsen Ken Hunter consistency in CDC documentation, Paul Koning experienced users could pick up an unfamiliar CDC manual and quickly locate needed information. CDC documentation appeared in A special thank you goes to the man who was one- and two-column formats depending upon responsible for the design of Control Data the subject matter. We have chosen to use the Corporation’s most successful large-scale two-column format since it looks better with computer, the CDC 6600 system. the many short paragraphs in the reference sections.
Most CDC manuals of the time were set with section titles and headings in Linotype Helvetica and body text in Times Roman. Owing to licensing restrictions on the PDF-embedded use of these fonts, we have substituted Arial for Helvetica—the differences between Arial and Helvetica are subtle—and Times New Roman for Times Roman.
Most body text in original CDC documentation was set with six percent letterspacing (like this instead of this), apparently because adding the letterspacing made it easier, if need be, to later compress the copy and add new material without changing the pagination. However, Seymour Cray
90001100 2 vii typographers today deprecate letterspacing As opposed to American convention, we have mixed-case copy, and in light of how this adopted international English spelling in this document is distributed and reproduced, its document as a tip of the hat to Desktop original purpose is now an anachronism, so Cyber’s designer and principal developer, Tom letterspacing is one attribute we have not Hunter, who also made substantial text reproduced. contributions to this document.
We’ve also made the point size a bit larger This publication was composed and finished in since the Controlfreaks are a bit older. In doing Adobe FrameMaker 7.0 using scanned so, we made the right margin ragged, since overlays of actual CDC manuals for page and space-filling a large point, narrow column paragraph layout. Screen captures were done looks rather sparse and is difficult to read. with Nestegg Software Screen Capture 1.4.6 and enhanced for readability with Adobe Photoshop CS and Adobe Illustrator CS.
viii 90001100 2 CONTENTS
Index of Console Commands Front Cover Entering Characters not on the Keyboard 2-21 PREFACE iii To Create a Text File from DIS 2-22 Introduction iii To Browse a File from DIS 2-22 audience and Organisation iii Account Management 2-22 Conventions iv User Indices 2-22 Related Publications iv Vanity Hash Codes 2-23 Acknowledgements v Account Creation 2-24 Colophon v Closing an Account 2-34 Job Management 2-34 2. BASIC OPERATION 2-1 Job Origin Types 2-34 Tape Jobs 2-35 Introduction 2-1 How to Handle a Tape Console Keyboard Usage 2-1 Request on the E,P Display 2-37 Dead Start Panel 2-1 How to Handle a Tape Dead Start 2-1 Request on the B Display 2-40 Shutdown 2-7 Unloading Tapes 2-43 Console Operation 2-7 Batch Jobs 2-44 DSD Displays 2-8 Interactive Jobs 2-45 DSD Commands 2-12 To log a session off 2-45 DIS Operation 2-15 To determine the terminal Auto Mode 2-16 number of an interactive DIS Displays 2-16 user 2-46 DIS Special Keys 2-17 To send a message to one or DIS Commands 2-18 more terminals 2-46 Memory Entry 2-19 Output Jobs 2-46 Using O26 2-19 Print Jobs 2-46 O26 Special Keys 2-19 Punch Jobs 2-47 System Commands 2-20 Fun and Games 2-48 File Commands 2-20 Bulding and Running 99 Bottles 2-48 Editing Commands 2-21 Miscellaneous Commands 2-21 Index of Control Statements Back Cover
90001100 2 1 2 90001100 2 BASIC OPERATION 2
INTRODUCTION By default, Desktop Cyber’s console emulator isn’t pedantic about key rollover—on a true This chapter is primarily for the person who 6612 console, the operator couldn’t type very will operate Desktop Cyber. Just like the real fast; the console would only accept one key at thing, many people may use Desktop Cyber at a time, so the operator had to develop a the same time, but the operator is the person somewhat awkward punch-and-wait who interacts with the system through the keyboarding technique when sitting at the console, while users interact with the system console. You don’t have to worry about that— through the timesharing system or through just type as you normally would. batch jobs. DEAD START PANEL CONSOLE KEYBOARD USAGE Obviously, there is no real dead start panel or Desktop Cyber’s console window is a 6612 dead start button. The dead start panel display console emulator. Since the 6612 switches are configured in the cyber.ini file, didn’t have a full keyboard, not all keys are and the dead start button is “pushed” by supported. If you try to enter a key which isn’t starting Desktop Cyber. supported, the emulator just ignores it. DEAD START Most keys map obviously. Although the 0 on the 6612 was to the left of the 1, Desktop The process of initializing Desktop Cyber and Cyber uses the 0 right where it’s found on the its hosted operating system is called dead conventional keyboard. start. Usually, the process is initiated by an operator, but then proceeds without The CR key maps to ENTER. intervention.
The only non-obvious mapping is for the two Here is how you normally dead start your keys present on the 6612 but not seen on Desktop Cyber: conventional keyboards—the left and right blank keys. The left blank maps to [ and the 1. Log in to the Linux host on its graphical right blank to ]. console.
NOTE 2. Start an xterm. You will keep this xterm open the entire time the system is up, since The left blank clears the text you have entered on the command line (as a control-U in many UNIX Desktop Cyber prints status messages in shells), and the right blank tabs through several this window. console displays. 3. Verify that the DISPLAY environment var- iable is set correctly. It should be set to
90001100 2 2-1 your Linux host name followed by “:0.0” 4. Change to the Desktop Cyber home direc- as in goldfinger.draughon.org:0.0 tory.
NOTE 5. Type the command ./dtcyber as shown below: Desktop Cyber does not support the -display command line option. It must obtain the display server name from the environment.
FIGURE 2-1. Starting Desktop Cyber
6. The following X window will appear:
2-2 90001100 2 FIGURE 2-2. Initial Options Display
If you wish to accept the default set of dead 7. The following will be briefly displayed as start options, you may simply press ENTER the system goes through its hardware veri- and a level zero dead start will proceed fication sequence: without displaying the configuration decks.
NOTE
If you wish to perform a dead start other than level zero, display the configuration decks, or override the dead start panel options, instead of pressing ENTER, press O, then P, and enter your desired options. Once done, press ENTER to proceed with the dead start.
90001100 2 2-3 FIGURE 2-3. Initial Tests
After the hardware verification sequence, you will be prompted to enter the date and the operating system will load. You will time on the left display. see its progress on the right display, and
FIGURE 2-4. Date/Time Entry
2-4 90001100 2 Enter the date and time when prompted, 8. If the last dead start were more than a few using the form shown, and pressing ENTER days ago (even if the system were up the after each entry. entire time), you will see the following. Note the message at control point 1 on the right-hand side.
FIGURE 2-5. CMS Requesting Date Confirmation
The message is CHECK POSSIBLE DATE ENTRY ERROR. N.GO. If the date is correct, type 1.GO. and press ENTER.
90001100 2 2-5 9. The rest of the system will now come up, with IAF, MAGNET, and BATCHIO checking in.
NOTE
It really isn’t the IAF you may recall. Actually, it’s more like a tricked-up TELEX, so if you are accustomed to NAM IAF, you are in for a gentle re-education. See [ Interactive Use Xref ] use for details. Here, though, is a brief summary of what you need to know about the subtle, yet significant, differences:
• To terminate a running job, type STOP ENTER.
• To terminate a running job which is issuing output, just type S while the output is being printed.
• To interrupt a running job which is issuing output, just type I while the output is being printed. Press ENTER to continue.
• To cancel a line of input you have entered, press ESC.
• To exit text mode, type CONTROL + C. To obtain a job status report at any time other than when the job is requesting input, type E ENTER.
2-6 90001100 2 FIGURE 2-6. Display Following Successful Dead Start
The system is now completely up and 5. Type ALT + O and issue the Desktop Cyber ready for interactive sessions and batch command SHUTDOWN. Desktop Cyber jobs. will exit.
SHUTDOWN CONSOLE OPERATION
To shut down Desktop Cyber: Most operator functions at the console are done through a PP program called DSD. DSD 1. If users are logged on, you may wish to accepts commands from the keyboard and warn them. See the WARN command on updates the various displays on the console. page 2-15 and the DIAL command on page 2-13. DSD is interpretive—that is, when the operator is typing a command, DSD completes 2. If the console keyboard is locked (see Fig- it as soon as it recognizes enough characters to ure 2-7 on page 2-11), issue the UNLOCK establish the uniqueness of the command. As command. soon as the operator has entered a complete command, the echoed characters on the 3. Issue the CHECK POINT SYSTEM com- console “twinkle” to indicate that DSD is mand. ready to process the command. DSD will not permit the entry of syntactically incorrect 4. When the message SYSTEM CHECK- commands. If an entered command is POINT COMPLETE. appears at the SYS control point, issue the command STEP.
90001100 2 2-7 syntactically correct but operationally general-purpose displays, but the operator will impossible (such as trying to drop a job at an often bring up the other common displays— inactive control point), DSD responds with the E,A; E,T; E,P; K; Q; and T—on the left side as message NO. over the command line. needed, and usually returning to the A display when done. Most DSD commands must end with a period. Commands which place messages somewhere The DSD displays are selected with the (such as in a dayfile or on a user’s terminal) do command xy. where x is the left display and y not have to terminate with periods. is the right display. For example, to bring up the T display on the left side and the B display DSD DISPLAYS on the right, the operator would enter TB.
DSD provides data to the operator through Some displays (A, C, D, E, F, G, and K) have several displays, rather than by printing reports subdisplays which can be activated on the left in response to commands as is done with most side with the command x,s. where x is the command-line systems. Most of the displays display and s the subdisplay. For example, are dynamic—as the data being reported on E,T. brings up the tape status display on the changes, the display is updated automatically. left side.
The console shows two displays at once—one Here is a review of the operator console on each side. Typically, the operator keeps the displays: A display on the left and B display on the right, since these are the two most
2-8 90001100 2 TABLE 2-1. DSD Displays
Display Purpose
A Displays system dayfile, account file, and error log. A,0. Shows the system dayfile. A,n. Shows the dayfile for the job at control point n. A,ACCOUNT FILE. Shows the account dayfile. A,ERROR LOG. Shows the system error log. B Displays control point activity. C, D Displays central memory contents. Each display shows 40B (the B means octal, remember?) 60-bit words at a time which you can page through with the + and - keys if you have the display on the left, or the ( and ) keys if on the right. Each word is shown in five groups of 12 bits. The only difference between the C and D displays is that the C display begins at location 0B and D begins at 40B. Thus, you may dis- play the first 100B locations of central memory by bringing up the C and D displays simultaneously with the command CD. The C and D displays may also be used to show central memory relative to a control point. In the discussion below, C may also be any of the central memory displays (C, D, F, or G): C,0. Returns to the absolute address display. C,n. Shows central memory relative to control point n. E Equipment status tables. The E display is actually a group of five separate displays: E,A. Equipment status table. E,C. Mass storage configuration. E,M. Mass storage table. E,P. Pending tape requests. E,T. Tape drive status. F, G Displays central memory contents. Just like the corresponding C and D displays except each word is shown in four groups of 15 bits.
90001100 2 2-9 Display Purpose
H File name table (FNT). Lists the name, FNT ordinal, and type of each file currently in use by the system. The most common file types (by far) are— CM Central memory resident (common) file. FA Fast-attach file (a direct access permanent file with the disk address kept in central memory). IN Input file. LI Library file (locked central memory file). LO Local file. PM Direct access permanent file. PR Print file. PT Primary terminal file (a local file which has been designated as such by an interactive user for ease of use). PH Punch file. RO Rollout file. TE Timed/event rollout file. Consult the NOS Version 1 Systems Programmer’s Instant, page 1-2 (included in your distribution) for a full listing of the file types. I BATCHIO status. Shows the status of unit record equipment (card readers, punches, and printers). J Control point status. Shows the status of a specified control point. You specify the control point with J,n. where n is the control point number. K, L Programmable displays which a program may use to interact with the operator. A program requests operator assignment of the K or L displays by placing a message on the B display, for example:
20. 5. MODVAGUS PR70.QP7761.RA 7537 FL 240. X. REQUEST *K* DISPLAY. The operator assigns the K display with K,n. where n is the control point number (20, in this case) as in K,20. The operator may now type in data for that program by preceding it with K. as in K.C,JPD (which is the MODVAL K display com- mand to create a new user JPD). M ECS display. Shows contents of extended core storage in the same manner as the C display shows for central memory. N File display. You may use this display to show the contents of any active file. Use the DISPLAY,fntord. command (where fntord is the FNT ordinal of the file from the H display) to show the specified file on the N display. O Transaction facility status. The transaction facility is not included in this distribu- tion, so this display, while supported by NOS, isn’t supported in this particular dis- tribution.
2-10 90001100 2 Display Purpose
P PP communications area. For each peripheral processor, the following is listed: first line, input register; second line, output register; third line, first word of message buffer. Q Queue status. Shows the status of input, output, and rollout queues, along with their corresponding FNT ordinals. R Export/Import status. Export/Import is the predecessor to RBF. It’s not included in this distribution, so this display isn’t supported. S System control information. Displays the priorities and scheduling parameters for the different queue types for the different job origin types. T Timesharing system status. Shows users currently logged in along with their termi- nal numbers and last operations. Y Monitor functions. Lists the several monitor mnemonics and codes. Z Directory. Gives an abbreviated listing of the various console displays (in other words, it’s similar to the table you are reading).
The console also displays some system status at the top and bottom of the screen no matter what displays are selected, as shown in the diagram below:
FIGURE 2-7. Status on all DSD and DIS Displays
Control Point the CPU is Running Channel Status Login Banner (D-Inactive, E-Empty, F-Full) 13 OS Release PP Using That Channel Example: PP 1 is using CH10. Mainframe ID Available ECS Base-32 Job Count Available CM Contents of P Register Debug Mode Warning Console Keyboard Unlock Warning
ANY DSD OR DIS ANY DSD OR DIS DISPLAY DISPLAY
Control Point Number PP Program PP Number
Example: PP 1 is running PP program DSD for control point 21.
90001100 2 2-11 DSD COMMANDS CFO n.CFO.dd..d Places command string Many operator commands act on individual dd..d starting in word 70B jobs executing at a control point. These of the control point’s field commands are preceded by n. indicating that length as a command from the operator needs to enter the control point the operator. The job run- number and a dot prior to entering the ning at the control point command. For example, 6.DROP. will drop must be paused, expecting the job running at control point 6. and know what to do with ASSIGN n.ASSIGN,dd. this data. Usually used for Assigns device dd to the obtaining brief commands job. The job must be from operator (hence the requesting a device (such as name) without having to go a tape mount) via the through the K display. REQUEST command for CHECK POINT SYSTEM. this to do anything; this CHECK POINT SYSTEM. command is not used to sat- Prepares the system for isfy requests for tape immediate shutdown. The mounts requested by the console must be unlocked. LABEL control statement; see How to Handle a Tape CKP n.CKP. Request on the B Display on Checkpoints the job and page 2-40. starts it over again. AUTO AUTO. COMMENT n.COMMENT.comment Instructs the system to start Places comment in the job’s the services which have dayfile. been previously enabled DEBUG DEBUG. (see the ENABLE com- Places the console in or out mand on page 2-13). of debug mode. The word BLITZ BLITZ. DEBUG appears at the top Drops every job running on of the console over the left the system except subsys- display to indicate when the tems. Use AUTO. to start system is in debug mode. subsystems back up. The The console must be console must be unlocked. unlocked to issue this com- You don’t need this danger- mand. In debug mode, users ous command very often— with system origin privi- it was dropped from NOS leges can issue many sys- 2—but, as your author tem control commands recalled one VIM member from interactive sessions in saying, “when you need it, addition to the system con- you need it!” sole.
2-12 90001100 2 DIAL DIAL,t,message VALIDATION Sends message to terminal Requires verifica- number t. tion of mass stor- age tables. See also: Use the T display to determine which terminal a FORM FORMnn,fc. user is on. Tells the system that the special forms indicated by DIS n.DIS. fc are now mounted on Takes the job at the control printer with EST ordinal nn. point into DIS. See DIS Use E,A. to see a list of Operation on page 2-15. equipment and associated X.DIS. EST ordinals. Starts a new system origin FORMnn,. job at any available control Clears the forms code on point and starts DIS. printer with EST ordinal nn. DISABLE DISABLE,something. GO n.GO. Stops a subsystem or disa- Resumes execution of a bles an option. See ENA- paused job. BLE. IDLE n.IDLE. DROP n.DROP. Asks the subsystem running Drops the job, but allows at that control point to fin- EXIT error processing. ish what it’s doing and exit. ENABLE ENABLE, something. KILL n.KILL. Allows a subsystem to start Drops the job without EXIT or enables an option. Some error processing. options are: BATCHIO Allows automatic LOCK LOCK. startup of print, Locks the console to pre- punch, and card vent accidentally entering reader system. dangerous commands. MAGNET Allows automatic LOGOFF LOGOFF,t. startup of magnetic tape management Logs off the interactive ter- system. minal number t. SECONDARY USER CARDS See also: The T display shows Allows users to the terminal number for each issue additional user. USER cards once they’ve validated MESSAGE MESSAGE,message. themselves initially Changes the login banner to to the system (akin message. Users will see this to UNIX su). message before they log in, TELEX Allows automatic and users already logged in startup of interac- will not see it at all. tive access system.
90001100 2 2-13 See also: WARN to display a ROLLIN ROLLIN,xxx. message after the user has Assigns job with FNT ordi- logged in. nal xxx maximum queue OFF OFFnn. priority, making it immedi- Used to logically turn off ately eligible for being equipment with EST ordi- scheduled to a control nal nn. point. See also: You may determine OFFSW n.OFFSW,x. the FNT ordinal of a job by Turns off logical sense looking at the Q display. switch x ()1 ≤≤x 6 for ref- erence by the job. ROLLOUT n.ROLLOUT. Removes job currently ON ONnn. assigned to control point n Used to logically turn on and places it in the rollout equipment with EST ordi- queue. The job will remain nal nn. rolled out until explicitly ONSW n.ONSW,x. rolled back in. Turns on sense switch x n.ROLLOUT,xxxx. ()1 ≤≤x 6 for reference by Removes job currently the job. assigned to control point n OVERRIDE n.OVERRIDE. and places it in the rollout Removes the job from the queue for xxxx seconds, at executing job table. The the end of which it is eligi- console must be unlocked; ble for rescheduling to a see the UNLOCK com- control point. mand. STEP n.STEP. PURGE PURGE,nnn. Places the monitor in step Purges job with FNT ordi- mode for the job at that con- nal nnn from the system. trol point. Setting the moni- Often used to delete a mas- tor in step mode stops all sive print job before it central memory I/O opera- starts, or to drop a job tions and prevents the sys- which isn’t running at a tem from processing PP control point (awaiting, for requests when the next example, a tape mount monitor function is encoun- request). tered. Pressing the space bar releases the present step See also: DROP and KILL, and stops again for each which may be used to terminate subsequent monitor func- jobs running at a control point; tion. The console must be Q display to see the list of jobs unlocked to issue this com- and their FNT numbers. mand.
2-14 90001100 2 STEP. X X.cmd(opts) Places the monitor in sin- Starts a system origin job to gle-step mode. The console run the specified command must be unlocked to issue cmd with the specified this command. options opts. UNLOAD UNLOAD,xx. X.cmd. Unloads the tape on unit xx. Starts a system origin job to The tape must not be run the specified command assigned to a job. cmd. UNLOCK UNLOCK. * * Unlocks the console to per- When in DIS, relinquishes mit the entry of potentially display back to the com- dangerous commands. mand console interface UNSTEP n.UNSTEP. (DSD). When in DSD, Takes the CPU out of step returns control back to DIS. mode for that job. Only has an effect if the job had been DIS OPERATION previously STEPped. DIS is a job display package which: UNSTEP. Takes the CPU out of sin- • Allows the operator to interact with gle-step mode. an already-executing job on-the-fly. VSN VSN,xx,vvvvvv. This can be done to investigate what Informs system that the the job is doing, what files it has operator has mounted tape open, see what job steps are next, and with VSN vvvvvv on unit even change what that job does. It is xx. See How to Handle a a powerful debugging tool in its own Tape Request on the E,P right. DIS is started in this way by the Display on page 2-37. console command n.DIS. where n is the control point number of the WARN WARN,message. executing job. A job of system origin Displays message to or with system origin privileges (see TELEX users as they log in. the CSOJ permission on page 2-31) For users already logged in, may bring itself into DIS by issuing the message is displayed the control statement. when they exit their next DIS. command. • Allows the operator to interact with WARN,. job control so that control statements Clears warning message. may be entered conveniently without See also: MESSAGE, which having to log in to a terminal. Jobs displays a message before the initiated through DIS are system user logs in. origin (see Job Origin Types on page 2-34) and have privileges that non-system origin jobs do not have.
90001100 2 2-15 For example, logging in with a user enter additional commands or number and password is not required. directives. DIS is started this way by the console command X.DIS. • DIS encounters an error which would have aborted the job had it not been NOTE under DIS control. While DIS is certainly interactive, it isn’t like a terminal where you type a command and view • DIS is manually taken out of auto output on the screen. Job input is read from mode, whereupon execution is the mass storage file INPUT, and job output is written to mass storage file OUTPUT. Thus, to suspended at the conclusion of the generate input or read output on the display, current job step. you must use the O26 editor and WRITE.INPUT. or READ.OUTPUT. DIS is placed into auto mode by pressing the accordingly. period key; it is taken out of auto mode manually by pressing the left blank key. Auto Mode DIS Displays No matter how DIS is started, execution of the job is temporarily suspended at the end of each Like DSD, DIS has several displays you may job step (that is, command) unless DIS is select, and you may change them at any time, placed in auto mode. Auto mode causes DIS to even while the job is executing. You specify read control statements and continue execution the displays the same way you do with DSD: until either: xy. The left display, x, may be any of the displays listed below; the right display, y, must • DIS reaches the end of the job, be one of B, C, D, N, T, or U. whereupon job execution is again suspended and the operator may
TABLE 2-2. DIS Displays
Display Purpose
A Dayfile messages and files in use. B Job status, control statements, and register contents. C, D Central Memory displays in five groups of four octal digits and the display code translation. F Central Memory displays in four groups of five octal digits and the display code translation. G Central Memory displays in four groups of five octal digits with COMPASS mne- monic translation. H File name table entries.
2-16 90001100 2 Display Purpose
M ECS memory displays in five groups of four octal digits with display code transla- tion. N Blank screen. Useful for the right display when the left display creeps data over to the right as in the T display. T, U Displays 240 (T) or 300 (U) words from central memory as coded lines of text. V Displays 512 words direct from central memory without interpretation. Y Displays function mnemonics and values. Z Display directory.
DIS Special Keys
The following keys have special significance when entered as the first character on a line. These characters do not require a terminating ENTER to take effect.
TABLE 2-3. DIS Special Keys
Key Significance * Temporarily releases DIS control of the display console back to DSD. From DSD, press * to return to DIS. = Toggles memory references between absolute and relative. + If the C, D, F, G, M, T, or U displays are active, advances the display by 40B words. - If the C, D, F, G, M, T, or U displays are active, decrements the display by 40B words. / In DIS, advances the left screen C, D, F, G, M, T, or U displays by the amount in the rightmost 18 bits (six octal digits) of the first word displayed. . Causes DIS to automatically read control statements from the control statement buffer. The message AUTO MODE. appears above the command line.
ENTER Sets repeat entry. The message REPEAT ENTRY. appears above the command line. Subsequent commands are executed, but the command is not cleared from the com- mand line so that the command may be issued again by pressing ENTER.
LEFT Clears the entered command and, if active, terminates repeat entry. BLANK
90001100 2 2-17 DIS Commands ENB ENBi,xxxxxx. Sets register Bi to xxxxxx. NOTE ENP ENP,xxxxxx. Unlike DSD, DIS is not interpretive—DIS does Sets program counter P to not fill in parts of a command as it recognizes xxxxxx. it. You must terminate each command with ENTER. ENS ENS,command. Enter next statement. Clears All DIS commands must contain a terminator the existing control state- (either a period or right parenthesis). ment buffer and enters com- mand as the next statement. DIS is used primary to enter control ENX ENXi,xxxxx xxxxx statements. In addition to control statements xxxxx xxxxx. (see [ Batch Commands Xref ]), the following Sets register Xi to xxxxx commands may also be used: xxxxx xxxxx. DCP DCP. ENXi,Lvalue. Drops the central processor Sets register Xi left justified (that is, suspends execution to value. of the program until either ENXi,b,xxxx. the command RCP. is Sets byte b of register Xi to entered (which causes xxxx. Each word consists of resumption where the pro- five 12-bit bytes (four octal gram left off) or a new com- digits) numbers 0 through mand is entered, which 4, left to right. causes the suspended pro- gram to stop before the new HOLD HOLD. command is executed. Holds the job at its current status but drops the display DROP DROP. console channel. Drops DIS. Does not drop the job if there are control O26 O26. statements remaining in the (Oh-two-six.) Calls the O26 control statement buffer. full screen text editor. See Using O26 on page 2-19. ELS ELS.command. Enter last statement. Enters RCP RCP. control statement command Request central processor. in the control statement Used to resume execution buffer after the last state- following a DCP command. ment. This allows you to RNS RNS. add on to an existing job. Read next statement. Reads ENA ENAi,xxxxxx. and executes the next state- Sets register Ai to xxxxxx. ment in the control state- ment buffer.
2-18 90001100 2 ROLLOUT ROLLOUT. loc,b,val. Places the job in the rollout Changes contents of central queue until the job sched- memory address loc, byte b, uler rolls it back in. On to val. Each word consists Desktop Cyber, that’s not of five 12-bit bytes (four likely to be very long. octal digits), numbered 0 ROLLOUT,xxxx. through 4, left to right. Places the job in the rollout loc,Dchars. queue for approximately Changes contents of central xxxx seconds. memory address loc to dis- SUI SUI,index. play code characters chars, Sets the active user index to left justified, zero filled. index without having to specify a user number and USING O26 password. NOTE SUN SUN,usernumber. Sets the active user number Like DSD, but unlike DIS, O26 is interpretive; O26 fills in characters in a command as soon to usernumber without hav- as you have entered enough of the command ing to specify a password. for it to be unique.
NOTE O26 Special Keys To perform any permanent file operations, you must either specify a user index via SUI, a The following keys have special significance user number via SUN, or a user number and when entered as the first character on a line. password via USER. These characters do not require a terminating ENTER to take effect. Memory Entry loc,val. Changes contents of central memory word at address loc to val.
TABLE 2-4. O26 Special Keys
Key Significance 0 Sets insertion point at first line. 8 Sets marker 8 at current line. 9 Sets marker 9 at current line. + Displays next page.
90001100 2 2-19 Key Significance - Displays previous page. * Holds display and returns control to DSD. / Toggles display scrolling. ( Advances insertion point by one line. ) Decrements insertion point by one line. = Clears insert flag. , Moves display to insertion point. . Deletes the line following the insertion point.
ENTER Sets repeat entry mode.
SPACE Begins text insertion.
System Commands XDROP XDROP. DIS DIS. Transfers control back to Writes the buffer, rewinds DSD without writing or the output file, and returns rewinding the file. control to DIS. This is the normal way to exit O26. File Commands See also: XDIS, which permits FILE FILE.filename. returning to DIS without writ- Sets the default file name to ing the file. filename. DROP DROP. READ READ.filename. Writes the buffer, rewinds Reads filename into the the output file, and returns O26 buffer. control to DSD. READ. See also: XDROP, which per- Reads the default file name mits returning to DSD without into the O26 buffer or, if no writing the file. default file has been speci- fied by the FILE command, XDIS XDIS. then it reads the most previ- Transfers control back to ously-specified file. DIS without writing or rewinding the file. REWIND REWIND.filename. Rewinds filename.
2-20 90001100 2 REWIND. the command line. Use the Rewinds the default file or, space bar to position the if no default file has been pointer and enter the new specified, rewinds the most text. previously-specified file. MOVE MOVE. RNR RNR.filename. Cuts lines of text between 8 Clears the O26 buffer and and 9 markers and pastes at reads the next record on insertion point. filename. P P.text RNR. Inserts text beginning at Clears the O26 buffer and insertion point. After enter- reads the next record on the ing the line, the P. prompt default file. If no such file will remain, allowing the has been specified, reads continued entry of text. the next record on the most When finished entering previously-specified file. lines, press LEFT BLANK. WRITE WRITE.filename. RS RS/oldtext/newtext/ Writes filename from the Replaces oldtext with new- O26 buffer. text on following line. / may WRITE. be any delimiting character. Writes the default file or, if no default file has been Miscellaneous Commands specified, writes the most OUT OUT. previously-specified file. Transfers the file OUTPUT to the print queue, and Editing Commands PUNCH to the punch COPY COPY. queue. Copies lines of text between UCC UCC=c. 8 and 9 markers and pastes Sets the shift escape charac- at insertion point. ter to c. To enter a literal c, D D,*. enter cc. Deletes text between 8 and UCC=. 9 markers. Clears the shift escape char- L L.text acter. Replaces following line. Use for when you want to Entering Characters Not on the Keyboard make small changes to the line. As soon as L. is You may use O26 to enter characters which entered, the line is listed on aren’t on the keyboard. Locate the character to be entered in table 2-5 on page 2-22 and enter the shift escape character followed by the listed character. For example, if the escape
90001100 2 2-21 character is /, to enter a $, press / and then S. 3. Continue entering text, pressing ENTER after O26 will show the octal display code of the each line. character. For example, $ will display on the 5 4. When done entering text, press LEFT BLANK. input line as 3 . 5. Enter the command WRITE.filename. TABLE 2-5. Character Escapes 6. Enter the command DIS. To Type the UCC Escape Display Enter: Character and Then: Code To Browse a File from DIS $S 53 1. Issue the command O26. #0 60 2. Once in O26, issue the command [1 61 READ.filename. ]2 62 3. You may use the / key to slowly scroll 63 %3 down the file, or you may use the ( and ) "4 64 keys to move up and down a line at a time, or you may use + and - to move around a _5 65 screenful at a time. !6 66 4. Issue the command XDIS. to return back &7 67 to DIS. 'Q 70 ACCOUNT MANAGEMENT ?W 71 Accounts are created, modified, and deleted
2-22 90001100 2 The hash code is a 17-bit, base-32 digest of the All hash codes, because of the digest user index utilizing the alphabet A to Z and 0 algorithm, are four characters long consisting to 5. The sequence number is a of the characters A through Z and 0 through 5. monotonically-increasing base-26 quantity The fourth character must be either A, I, Q or using the alphabet A to Z. Y.
Exceptions: To compute the user index corresponding to a specified hash code: • For system origin jobs (see Job Origin Types on page 2-34), the first 1. Issue the command X.DIS. four characters of the job name (left-justified, A-filled) are used 2. Issue the command SUN,JPD. instead of the hash code. Thus, a system origin job started by X.DIS. 3. Issue the command GET,UNHASH. This will have a job name of DISA is a Fortran V source code file. followed by a three-character sequence number, and a system 4. Compile the program with the command origin job started by X.MODVAL. FTN5,I=UNHASH,L=0. will have a job name of MODV followed by a three-character 5. Execute the compiled program with sequence number. LGO,hash. where hash is the desired hash code. • For interactive origin jobs, the terminal number is used instead of 6. Read the corresponding user index on the the sequence number, expressed as a DIS A or B display. This is the index you three-digit, right-justified, zero-filled will specify for the FUI= directive when octal number. creating the account.
VANITY HASH CODES Example. The corresponding user index for hash code UGLY is 241457B as shown in the When creating an account, MODVAL will following figure. automatically assign a user index, and, consequently, a hash code. The automatic user index selection can be overriden, however. One reason for specifying a specific user index is that it permits a custom, vanity-style hash code.
90001100 2 2-23 FIGURE 2-8. Computing a Vanish Hash Code
ACCOUNT CREATION 2. Note the control point number requesting the K display. In the example below, 1. At the console, type X.MODVAL. MODVAL is running at control point 20.
NOTE
Users will not be able to log in while you are in MODVAL, so don’t dilly-dally.
2-24 90001100 2 FIGURE 2-9. Starting MODVAL
3. Type K,n. where n is the control point number. In this example, you would type K,20. and the following would appear:
FIGURE 2-10. Initial MODVAL Display
90001100 2 2-25 4. Type K.C,unum where unum is the user The following is displayed after typing number you wish to create. For this exam- K.C,PIB: ple, we’ll create the account PIB.
NOTE
User numbers consist of one to seven characters. The characters may be 0 through 9, A through Z, and the asterisk (*). The asterisk in a user number is somewhat like a wildcard; it allows the user implicit read access to the permanent file catalogs of matched user numbers. For example, user EESUM** has implicit read access to the permanent files belonging to EESUMPD and EESUMHA, but not to MESUMTS. Passwords consist of four to seven characters. Like user numbers, the characters may be 0 through 9, A through Z, and the asterisk.
FIGURE 2-11. MODVAL User Creation
5. Select a password for the user and enter it 6. If you wish to set a vanity hash code for with PW=password. Here, we’ll give this user (see Vanity Hash Codes on PIB the password BOZOS by specifying page 2-23), enter the directive PW=BOZOS. FUI=indexB where index is the com- puted user index from the UNHASH pro- gram.
2-26 90001100 2 7. If you wish to accept the default permis- 8. You may now change any of the following sions for this user (you probably do not— permissions. You may specify multiple see note below), go to step 9 on page 2-34. permissions on the same line, delimited by commas, up to 50 characters. You may NOTE enter as many lines as you wish. Sugges- tions on values are listed at the end of this The default permissions were appropriate 30 years ago, but for Desktop Cyber, they are step. probably inadequate. For example, the default permissions do not give the user access to tapes. Nevertheless, even today full permissions are most likely inappropriate, since NOS 1.4 provides powerful user monitoring features which allow a fully privileged user to monitor the individual keystrokes of others. For a list of what to type to give reasonable permissions to a typical user, see the example at the end of the next step.
TABLE 2-6. MODVAL User Resource Use Permissions
Allowable How the Value is Permission Values You Suggested Meaning Interpreted to Give the Keyword May Set in MODVAL Entry Actual Limit MODVAL (I)
MT Allowable magnetic 0-7 MT=I MT=7 tapes If MT=7, Unlimited RP Removable packs 0-7 RP=I RP=7 If RP=7, Unlimited SC Security count 0-77B SC=I SC=77B If SC=77B, Unlimited MS Mass storage PRUs 0-77B MS=4096*I+512 MS=77B MS=10000B*I+1000B If MS=77B, Unlimited CM Central memory field 0-77B CM=60*I+17 CM=77B length/100B CM=74B*I+21B If CM=77B, Unlimited EC ECS field 0-77B EC=16*I EC=77B length/1000B EC=20B*I If EC=77B, Unlimited TL Time limit/10B, in 0-77B TL=64*I+8 TL=77B seconds TL=100B*I+10B If TL=77B, Unlimited
90001100 2 2-27 Allowable How the Value is Permission Values You Suggested Meaning Interpreted to Give the Keyword May Set in MODVAL Entry Actual Limit MODVAL (I)
NF Number of local files 0-7 NF=8*I+8 NF=7 NF=10B*I+10B, If NF=7, Unlimited OF Number of simulta- 0-7 OF=4*I OF=7 neous output files If OF=7, Unlimited DB Number of simulta- 0-7 DB=2*I DB=7 neous deferred batch If DB=7, Unlimited jobs PL Peak connect limit 0-77777777B PL=I PL=77777777B If PL=77777777B, Unlimited NL Non-peak connect 0-77777777B NL=I NL=77777777B limit If NL=77777777B, Unlimited DS Direct access file size 0-7 Index Value DS=7 in PRUs (there are 64 0 Job orig. default CM words (640 char- 1 512 2 1024 acters) in a PRU) 3 2560 4 4096 5 20480 6 32768 7 Unlimited FS Indirect access file 0-7 Index Value FS=7 size 0 Job orig. default 18 224 340 464 5 104 6 504 7 Unlimited FC Number of perma- 0-7 Index Value FC=7 nent files 0 Job orig. default 18 216 324 432 540 664 7 Unlimited
2-28 90001100 2 Allowable How the Value is Permission Values You Suggested Meaning Interpreted to Give the Keyword May Set in MODVAL Entry Actual Limit MODVAL (I)
CS Cumulative file size, 0-7777B CS=32*I CS=0 in PRUs CS=40B*I If CS=0, Unlimited LP Lines printed per 0-77B LP=1024*I+512 LP=77B print job LP=2000B*I+1000B If LP=77B, Unlimited CP Cards punched per 0-77B CP=64*I CP=77B job—this must be CP=100B*I non-zero if you wish If CP=77B, Unlimited to allow the user to mount their own tapes by issuing directives to the emu- lator CC Control cards per job 0-77B CC=16*I+64 CC=77B CC=20B+100B If CC=77B, Unlimited DF Dayfile messages per 0-77B DF=16*I+64 DF=77B job DF=20B*I+100B If DF=77B, Unlimited SL System Resource 0-77B SR=64*I+8 SL=77B Unit (SRU) limit per SR=100B*I+10B job If SR=77B, Unlimited CN Charge number Leave blank PN Project number Leave blank AB Terminal answer- Leave blank back string PA Terminal parity EVEN, ODD EVEN PO Rubouts between 0-37B PO=I 37B carriage returns If PO=37B, System default PX Echoplexing FULL, HALF FULL TT Terminal type TTY TTY
90001100 2 2-29 Allowable How the Value is Permission Values You Suggested Meaning Interpreted to Give the Keyword May Set in MODVAL Entry Actual Limit MODVAL (I)
TC Character set ASCII, STANDAR STANDAR (sic) IS Initial interactive BATCH, BATCH subsystem BASIC, COBOL, EXECUTE, FORTRAN, FTNTS, MNFTS, M77TS, NULL, PASCAL, SNOBOL, ABASIC, FCOBOL, ACCESS AW Access control word See below See below For users: AP specifying up to 60 AP=ALL, ON permission bits. AW=ALL, OFF OFF=CSOJ, OFF=CTPC
For systems programmers: AW=ALL, AP=ALL
The Access Control Word (AW) is a not running on this system, so MECC has 60-quantity which specifies various user redefined some of the NAM application capabilities. They are toggled in MODVAL bits. Application bits are specified with the by specifying AW=cname. Using AP=appl directive. ON=cname turns on the permission, OFF=cname turns it off, and AW=cname For both AP= and AW=, you may specify toggles it. (The ON and OFF directives are ALL to set all of the bits and NUL to clear undocumented features.) all of the bits. Thus, K.AW=ALL,AP=ALL sets every possible bit and Also supported, but not implemented here, K.AW=NUL,AP=NUL clears every are NAM application permissions. NAM is possible bit.
2-30 90001100 2 Here is a list of the capabilities supported by MODVAL, not all of which have applicability here:
NOTE TO REVIEWERS
Does anyone know what some of these permission bits mean? I got these from the MODVAL source. Most of them are obvious, but the mystery bits I have so marked.
TABLE 2-7. MODVAL Capability Descriptions
MODVAL Bit Capability Significance Name 0 CPWC Password change permitted. 1 CTPC Telex privileged commands permitted. (This allows use of the ACCESS subsystem. Set this bit with great caution since under NOS 1, this gives far greater privileges than under NOS 2; an ACCESS user may monitor any user’s keystrokes, send unsolicited (and anonymous) messages to any user’s terminal, and may log any user off the system.) 2 CLPF Create large (direct access) permanent files. 3 CSPF Create small (indirect access) permanent files. 4 CSOJ System origin privileges. This means that the user may issue many com- mands which require system origin (that is, being run from the console) from any job origin (interactive or batch). Using this privilege requires the system be in debug mode (see the DSD DEBUG command). Set this bit with great caution since it permits the sufficiently-clever user to steal files belonging to other people. Whether the system is in debug mode or not, this bit also permits the user to assign equipment by EST ordinal. 5 CASF Create and access system library files—in other words, the user may use the COMMON command. 6 CAND Assign nonallocable devices—that is, request tapes. 7 CCNR Charge not required. This bit should always be set. 8 CSRP Access removable disk packs. 9 CSTP Special transaction privileges. Not applicable here. 10 CTIM User’s terminal will not time out from inactivity. 11 CUCP System Control Point facility use permitted.
90001100 2 2-31 MODVAL Bit Capability Significance Name 12 CSAP Special accounting privileges; this gives the user special access to charge and project number data. Not applicable here. 13 CBIO Special BATCHIO privileges—specifically, the user may override the form control used on printers via the V carriage control character. 14 CPRT User may use the PROTECT command to save ECS across job steps. 15 CPLK Access link for permanent files. Not applicable here. 16 CQLK Access link for queued files. Not applicable here. 17 CUST Use ST on ROUTE and LINK statements. Not applicable here. 19 CSFC Special forms code permitted on ROUTE statement. 24 CIAF Interactive access permitted. 25 CRBF Batch job access permitted. 26 CTAF Transaction facility access permitted. Not applicable here. 27 CMCS Message control system access permitted. Not applicable here. 28 CTVF Terminal verification facility access permitted. Not applicable here. 29 CNOP Network operator access. Not applicable here. 30 CLOP Local operator access. Not applicable here. 31 CNLO Network/local operator access. Not applicable here. 40 COPE Account is active. Should always be set. 41 COPR Access alternate catalogs. The effect of this bit is a mystery to me. 42 CACC Issue secondary user cards. The user may issue additional USER cards after logging in, usually to give access to that user’s permanent files. 43 CPPF Protected permanent file creation allowed. The effect of this bit is a mystery to me. 44 CATP Access group catalogs. The effect of this bit is a mystery to me. 45 CDSD May use the DSD command—an interactive command which gives access to console displays. 46 CANG Access non-group catalogs. The effect of this bit is a mystery to me.
2-32 90001100 2 MODVAL Bit Capability Significance Name 47 CSTF Computer center staff access, presumably provides access to the accounting system. 48 CAC2 Allow access via secondary user card. If this bit is not set, the account can- not be USERed to. 49 CSMU Special master user. This is a feature of the accounting system allowing master users to control some permissions of their subordinate accounts. 50 CRCP Remote console privileges. Not applicable here. 58 CNTM Non-peak hours access. Should always be set. 59 CCTM Peak hours access. Should always be set.
For our new user PIB (and these limits are appropriate for most users), we select:
FIGURE 2-12. Typical User Permissions
K.MT=7,RP=7,SC=77B,MS=77B,CM=77B,EC=77B,TL=77B 8 K.NF=7,OF=7,DB=7,PL=77777777B,DS=7,FS=7,FC=7,CS=0 K.LP=77B,CP=77B,CC=77B,DF=77B,PX=FULL,IS=BATCH K.AP=ALL,AW=ALL,OFF=CSOJ,OFF=CTPC
The display now looks like:
90001100 2 2-33 FIGURE 2-13. MODVAL User Entry
If you wish, you may page through the two 2. Type K,n. where n is the control point other MODVAL pages by using the + and - number. keys followed by ENTER, but if you are following the example, you have already 3. Type K.U,unum where unum is the user set everything which needs setting. number you wish to delete.
9. Type K.END to go back to the main MOD- 4. Type K.SC=0,OFF=COPE VA L d is p l ay. 5. Type K.END 10. If you want to add more users, go to step 4 on page 2-26. 6. If you have more accounts to delete, go to step 3 on page 2-34. 11. Type K.END to exit MODVAL. 7. Type K.END CLOSING AN ACCOUNT JOB MANAGEMENT NOTE JOB ORIGIN TYPES Despite what you read on the K display, you cannot use K.D,unum to delete an account. It doesn’t work. NOS provides different scheduling priorities, limits, and, when applicable, billing rates to 1. At the console, type X.MODVAL. Note the jobs according to how the job was initiated. control point number requesting the K dis- For example, jobs submitted through the card play. reader for an overnight run would typically get low-priority access to the CPU and other
2-34 90001100 2 resources but get charged a lower rate than TAPE JOBS interactive jobs, which typically get more preferential access to system resources but get NOTE billed at a higher rate for that preferential The system comes configured for two tape treatment. units—NT50 and NT51. This particular release does not support more than two tape Although there are many job origin types, drives, even if you configure more in the there are but three commonly used: CMRDECK and cyber.ini.
• Interactive, timesharing, or telex jobs A job may request a tape in several ways: (all three terms refer to the same thing) are those run from interactive • The job may issue a LABEL control terminals. statement, which requests tape mounting and assignment through • Batch jobs are not interactive. They MAGNET, the resource executive. run all of their job steps in sequence This is the most common approach. detached from the user’s immediate Tape requests go into a queue which control. Batch jobs come from three the operator views on the E,P display. sources: In a bygone era, they were If the operator does not check E,P most commonly submitted by regularly, though, the requesting job punched card decks; they may also may be in for a long wait. be submitted by a control statement from any origin job (see [ Submit • The job may issue a REQUEST and Route Xref ]); and they may be control statement, which, depending submitted by an external Desktop upon supplied parameters, will either Cyber protocol which permits queue the request as if it had been submission via email and host made by LABEL, or flash a command language (see [External user-supplied message on the B Interfaces Xref ]). display requesting the tape mount. In large installations, this last approach • System jobs are those submitted is considered rather rude, since it either as part of the dead start process occupies a control point while the or submitted from the console by request is outstanding, and it does an either the X. command or through end-run around the regular queue of DIS. System origin jobs have special tape requests. However, for such a privileges that other jobs do not; for lightly-loaded system (so one example, system origin jobs do not expects), REQUEST has the need to validate the user, and can get advantage of getting the operator’s easy access to all permanent files on attention from across the room. the system. • If the job is of system origin or has system origin privileges (see the LIMITS command on page [ LIMITS Xref ] and MODVAL
90001100 2 2-35 access control permissions in Table VSN refers, of course, to the volume serial 2-7 on page 2-31), and the tape is number of the tape. USERNUM is precisely already mounted but not assigned to that, so you can identify the requesting user if a job, the job may use the ASSIGN you have a question. command to directly assign the tape unit without going through the RING will be either IN, OUT, or “--.” This operator. refers to a plastic ring which the operator can fit around the inner rim on the back of the tape • The user’s program may use an to permits writing on the tape. IN means that operating system interface to make a the tape should be mounted writable; OUT tape request without using a control means read-only, and “--” means that the user statement. This is rare; it’s typically did not specify. done by system backup and restore software. LABEL indicates whether the requesting user has specified if the tape has ANSI labels on it. For Desktop Cyber, “tapes” are actually ANSI labels permit the system to encapsulated disk files which typically have automatically identify the tape and assign it to been read and converted offline from actual the requesting job automatically; they also tape volumes. These files reside on the system guard against the operator accidentally hosting Desktop Cyber, not as NOS permanent assigning the wrong tape to the job. files. We suggest that tape files have the same name as the original tape’s VSN. If a requested tape is labelled, the operator merely has to mount the tape. If the tape is not Like tapes, these files must be “mounted,” or labelled, the operator must issue a VSN made available to Desktop Cyber. To NOS, command so that the system knows which tape such files have precisely the same behaviour as unit to assign. (See the VSN command, conventional tapes. page 2-15.)
Tape mounts requested via LABEL (or If the tape has been mounted incorrectly, the REQUEST with enough parameters to identify STATUS field will explain what’s wrong. The the specific tape volume) will appear on the most common (by far) problem is a ring E,P display. Here is an example: conflict—you mounted the tape read-write
RESOURCE MOUNTING PREVIEW. when read-only was requested, or you NO. EQ PN/VSN USERNUM RING LABEL STATUS 5. PE DSTAPE JPD IN -- mounted it read-only and the ring in was requested. The number refers to the job’s FNT entry; you would use this number to PURGE the job if the To mount a tape, you need not have a pending VSN did not exist. request. Thus, if there is a tape which you frequently use, you could just keep it mounted EQ refers to the specific equipment being (by appropriate configuration grammar in the requested, which you may ignore—it may be host cyber.ini file) at dead start and use it at either PE (meaning phase encoding, or 1200 your leisure. cpi density) or GE (group encoding, or 6250 cpi density).
2-36 90001100 2 How to Handle a Tape Request on the E,P 1. Check the E,P display and note the Display requested VSN and ring. See Figure 2-14 below. In this procedure, we will assume that you wish to mount a tape on NT51, which under the released configuration, is on channel 13, unit 1 (see the E,A display). To use NT50 instead of NT51, just substitute NT51 for NT50, and channel 13, unit 0 for channel 13, unit 1.
FIGURE 2-14. Example E,P Display
VSN to be mounted Read only Not labeled, so we will have to issue a VSN command after mounting the tape
2. Check the E,T display and make sure that NT51 is not in use. See Figure 2-15 on page 2-38.
90001100 2 2-37 FIGURE 2-15. Example E,T Display
Both NT50 and NT51 are available but NT50 still has a tape mounted from dead start (but can be UNLOADed if we want). We’ll use NT51 since it’s one less command we have to type in.
3. At the console, type ALT + O to enter Desk- LOAD,13,1,filename top Cyber’s operator mode. where filename is the name of the 4. If the tape is to be mounted with the write encapsulated tape file. ring in, issue the command: NOTE LOAD,13,1,filename,W. Do not type a period at the end of filename unless the file name really does have a final If the tape is to be mounted ring out issue period in its name. the command: See Figure 2-16 on page 2-39.
2-38 90001100 2 FIGURE 2-16. Desktop Cyber Operator Interface
Command
Reply
5. Issue the command END. to return to If the tape is labelled, you do not need to Desktop Cyber’s emulation mode. issue a VSN command; the system will assign the tape to the job automatically, 6. If the tape is unlabelled, issue the com- provided that the correct VSN were mand VSN,51,vvvvvv. where vvvvvv is specified. the VSN of the tape you just mounted. See Figure 2-17 on page 2-40.
90001100 2 2-39 FIGURE 2-17. E,T Before and After VSN Command
VSN,51,C5340.
7. Verify that the tape request was satisfied by How to Handle a Tape Request on the B checking E,P and correcting any problems. Display (If the request were properly satisfied, the request will no longer appear on E,P.) In this procedure, we will assume that you wish to mount a tape on NT51, which under the released configuration, is on channel 13, unit 1 (see the E,A display). To use NT50 instead of NT51, just substitute NT51 for NT50, and channel 13, unit 0 for channel 13, unit 1.
1. Whenever a tape is requested via the B dis- play, a message will flash with the request
2-40 90001100 2 as shown in the example below at control the B display as a comment on the point 20. Note that there is no correspond- REQUEST control statement. The message ing request on the E,P display. reads:
REQUEST,TAPE.PLS MOUNT VSN You will note that most of the request is in C5340, RING IN. plain English; the message was passed to
FIGURE 2-18. Tape Request via the B Display
Mount the tape precisely as you would for If the tape is to be mounted ring out. issue a request made through the E,P display: the command:
2. Check the E,T display and make sure that LOAD,13,1,filename NT51 is not in use. See Figure 2-15 on page 2-38. where filename is the name of the encapsulated tape file. 3. At the console, type ALT + O to enter Desk- top Cyber’s operator mode. NOTE 4. If the tape is to be mounted with the write Do not type a period at the end of filename unless the file name really does have a final ring in, issue the command: period in its name.
LOAD,13,1,filename,W. See Figure 2-19 on page 2-42.
90001100 2 2-41 FIGURE 2-19. Desktop Cyber Operator Interface
Command
Reply
5. Issue the command END. to return to B Displays Before and After Assignment on Desktop Cyber’s emulation mode. page 2-43.
6. Now you must manually assign the tape to NOTE the job whether the tape is labelled or not. Users may also use REQUEST to make Assuming you mounted the tape on NT51, requests unrelated to tape devices. If you the command to do this is: merely wish to acknowledge the request n.ASSIGN,51. where n is the control without assigning a device, you may assign null equipment (device 77) to satisfy the point number where the tape request is REQUEST. flashing (in our example, 20). See E,T and
2-42 90001100 2 FIGURE 2-20. E,T and B Displays Before and After Assignment
Note that even after the assignment, the system still doesn’t know the VSN if the tape is unlabelled.
Unloading Tapes If the job is of system origin or if the user requested via a control statement option to Any time the tape unit status is listed as idle in inhibit automatic unload, the tape will remain the E,T display, the unit may be unloaded via loaded but unassigned to a job, and if you need the UNLOAD command (see the UNLOAD the unit later, you will have to explicitly command, page 2-15). Usually this isn’t UNLOAD the device. necessary, though, since most jobs automatically unload the tape unit when Unloaded tapes, whether explicitly by the they’re done with the tape or at the end of the operator or implicitly by the system, do not job. need to be unloaded in the Desktop Cyber Operator Interface.
90001100 2 2-43 BATCH JOBS Batch jobs do not require operator intervention very often. Possibilities—rare though they Users may submit batch input jobs through any be—include: of the following mechanisms: • The simplest thing a batch job can • Building a text file (typically from an ask the operator to do is simply to interactive session) which resembles give the job a GO (see page 2-13). a batch card deck, and then releasing The COBOL5 and FTN5 compilers, the file into the input queue with the and the COMPASS assembler, offer ROUTE control statement, easy ways for the programmer to specifying a disposition code (DC) of place messages on the B display and either IN or NO. Specifying DC=IN then simply wait for the operator’s will cause the job output to be printed permission to proceed. If it isn’t a at job termination; DC=NO causes good time to run the job, the operator the job output to be discarded at the may, according to the user’s end of the job. instructions, either drop the job, roll it out (via the ROLLOUT command, • Building a text file as in the previous page 2-14) indefinitely until the bullet, but submitting it with appropriate time, or, if the job load is SUBMIT instead of ROUTE. light, just let it sit there at a control SUBMIT offers the advantage of point until the time is right. allowing the user, with appropriate directives, to simplify somewhat the • A user may request the operator to input file structure and to omit his or set sense switches for the job to her password in the file. specify program options. These aren’t real switches (although on • Building a text file offline using any computers from other manufacturers familiar text editor (such as of the era, they actually were a literal Microsoft Notepad) and submitting it bank of toggle switches on the front via email from anywhere on the panel), but rather are virtual switches Internet and having the output peculiar to each job rather than to the returned by email. entire computer system. Users may set and query these switches via • Building a text file on the host and control statements and library submitting it via the routines as well, so operator create_interstate_connection intervention is usually not required. command. • User programs can place short Regardless of how the job enters the system, as messages on the A and B displays soon as it enters the input queue, it is assigned and solicit simple operator input via a File Name Table (FNT) ordinal, which it the CFO command (COBOL5 in keeps throughout the job’s duration as it moves particular provides a native through the input, rollout, and output queues. mechanism for this without having to call external routines, but programs
2-44 90001100 2 written in other languages can do so subsystems (IAF, MAGNET, or by calling COMPASS routines). BATCHIO), use the IDLE command (see page 2-13). • More complex interactions with the operator may be made through the K • If the job is rolled out, it must be display. The program will alert the rolled in before it can be dropped. operator by placing the message Unless the job is in an event wait REQUEST *K* DISPLAY on the B (such as waiting for a tape mount), display. you can roll the job in with the ROLLIN command (see page 2-14), The most common thing you might be and then DROP the job. If the job is expected to do for a batch job is to terminate it, in an event wait, use the E,T or Q though. Some reasons for terminating a job: displays to find the job’s FNT ordinal and then use the PURGE command • The user asks you to. NOS 1 does not (see page 2-14) to drop the job. provide users with a means for PURGE rolls the job in briefly just so terminating their own jobs, so they it can be dropped. rely upon the operations staff to do it for them. INTERACTIVE JOBS
• The job is requesting a tape which You will typically need to do only three things for or to an interactive job: doesn’t exist.
• The job is giving some other part of • Log the session off. the system fits. This isn’t as common as you might think; the system does a • Report the terminal number of a pretty good job of session so the user may recover the compartmentalization. session following an accidental disconnection. (This information is To terminate a job: provided to the user at login, but most users ignore it.) • If the job is executing (that is, you see it on the B display), use the • Place a message on one or more DROP command (see page 2-13). terminals. This is a maskable signal and will allow the job to perform cleanup To log a session off: before exiting. If the job does not respond to a DROP, you may use the 1. Look at the T display and find the user KILL command (see page 2-13), number. The terminal number is listed in which is not maskable. To terminate the line column. See 2-21 on page 2-46.
90001100 2 2-45 FIGURE 2-21. Using the T Display
User number Terminal number
2. Use the LOGOFF command with the ter- message as soon as their jobs become minal number to log that user off. idle or right after they log in.
To determine the terminal number of an • If you wish to send a message to interactive user: users which they will see before they log in, use the MESSAGE command Simply consult the T display. See Figure 2-21. (page 2-13). Users already logged in will not see the message. To send a message to one or more terminals: OUTPUT JOBS • If you wish to send a message to a single terminal, use the T display to Desktop Cyber is concerned with two types of determine the terminal number, and output jobs: print and punch. use the DIAL command (page 2-13) to send the message. The message Print Jobs will be displayed immediately on the terminal. Desktop Cyber handles print jobs four ways in the order listed: • If you wish to send a message to all users and new users as they log in, • Jobs routed with a forms code of EM use the WARN command (FC=EM) are emailed to the owner (page 2-15). Users will receive the of the hash code registered in Desktop Cyber’s print manager. Embedded output directives, if any,
2-46 90001100 2 are ignored. See [ Setting Up the mounted, the job will wait in the output queue Print System Xref ] for details. until the specified form is mounted or the job is purged (See the PURGE command, NOTE page 2-14).
To submit a job for automatic emailing, the user must be validated for special forms NOTE TO REVIEWERS mounts (see CSFC, page 2-32). Does anyone know how the operator can get a list of output jobs showing the requested • Output from batch jobs originating forms code? One would think this is in the Q display, but it’s not. via email will be returned via email to the sender. We suggest that if your users need special forms mounted that they email the output back • Jobs with embedded output to themselves and print it themselves rather directives will be processed than request special forms mounts. according to those directives. See [ Setting Up the Print System Xref ] The FORM command (see page 2-13) is used for details. to change the forms code mounted on a specific printer. • Jobs without any embedded output directives are printed on the host’s NOTE default printer. Never change the forms code on LP63. That printer has its forms code set at EM On true Cybers, there are all sorts of automatically during dead start and if its forms commands available to operators to control code is changed, output will not be output by doing things such as reprinting parts automatically emailed. of the job, terminating the current output job, and changing the form characteristics (such as Punch Jobs lines per page) on the fly. Since Desktop Cyber isn’t printing directly, but rather going through The Desktop Cyber punch queue is connected the host’s native print services, most of these to a backend process on the host which is used features don’t have any relevance, since by the for processing emulator directives. These time you discover a problem, Desktop Cyber is directives are coded one per line in a local file already out of the loop. Thus, most printing which the user subsequently routes to the issues will be addressed with the host’s punch queue. The directives are described in operating system rather than with BATCHIO [ Tape Mounting for Users Xref ]. One on Desktop Cyber. purpose of this mechanism is to provide a means for allowing properly-validated users to Handling special forms mounts must still be mount their own tapes without the intervention handled by the Desktop Cyber operator, of an operator. This is especially helpful when though. Users with appropriate validation may a large number of tapes have been route output jobs with a forms code specifying encapsulated and the user wishes to a specific type of paper to be mounted on the experiment to recover the tape format. printer. If no printer has the requested form
90001100 2 2-47 To access this service, the user must be • Wink at Operators. X.EYE. If you’d validated for punching cards (see the CP like the winking to loop, use validation limit on page 2-29), disposing of X.EYE(1) and use D to terminate files with special forms codes (see CSFC the program. permission, page 2-32) and have permission to use the DSD command (see the CDSD • Lunar. Written at Northwestern permission, page 2-32) to ensure that the University, this is one of the first desired tape unit is not in use. You should take graphical flight simulators. It exists care that only responsible users are given this as indirect access file LUNAR in permission. UN=CALLPRG. You’ll want to start it from DIS. FUN AND GAMES • 99 Bottles. Written by Control Freak Try these diversions which can only be run Paul Koning, NI1D, this PP program from the console: provides step-by-step instructions on how to have a very bad morning. It • 6000 Series Baseball. This was was written because, well, it just had certainly one of the first video games to be done. The source code exists as ever. Start it with X.BAT. To pitch, indirect access file BOTPP in press P; to swing press S. You want UN=JPD. You’ll want to assemble the bat to pass over the plate at the and SYSEDIT it onto the system same time the ball does. You’ll be from DIS, and then run it from the able to figure out the rest. If the console with X.BOT. operations manager is hovering close by, * will suspend the display and Try building it and running it you’ll look hard at work. Pressing * yourself by following the instructions again brings it back where you left below. off. If the ball moves preposterously fast, you need to increase the CPU BULDING AND RUNNING 99 BOTTLES ratio in cyber.ini so that the CPU gets stepped more often than the PPs. See 1. From DSD, give the command [ Adjusting the CPU Ratio Xref ] for details. X.DIS.
• Andy Capp Display. X.ADC. This starts DIS at any available control D terminates the program. point.
• Worms Display. X.WRM. D 2. Issue the command terminates the program. SUI,1. • Snoopy. X.DOG. D terminates the program. since you may not issue any permanent file commands until the user index is set.
2-48 90001100 2 3. Issue the command 7. Now you are ready to SYSEDIT the new PP program onto the system. Rewind file GET,BOTPP/UN=JPD. LGO and SYSEDIT the program with these commands: This makes a local copy of indirect access file BOTPP from user number JPD. REWIND,LGO. SYSEDIT. See [ Indirect Access Files Xref ] for more information on indirect access files. See [ Creating a New Dead Start Tape Xref ] for more information on SYSEDIT. 4. Attach the system program library with 8. Now, cause DIS to drop the console dis- ATTACH,OPL=WPL/UN=SYSLIB. play:
See [ Direct Access Files Xref ] for more HOLD. information on indirect access files. NOTE
5. Assemble BOTPP with the command You must use HOLD instead of * because you need to drop the display channel to run the COMPASS,I=BOTPP,S=PPTEXT. BOT program.
This causes COMPASS to read BOTPP as 9. Start the BOT program with the input source, use PPTEXT as a macro source text, generate binary output on X.BOT. LGO (since B= was omitted, it defaults to LGO) and generate the assembler listing (The name is BOT instead of BOTPP on file OUTPUT (since L= was omitted, it because COMPASS uses the name defined defaults to OUTPUT). in a pseudoinstruction instead of the file name, since a single file may contain See [ Common Default Parameters Xref ] multiple programs.) for more information on the consistency across products of default parameter 10. Follow the instructions printed on the values. screen, if you dare.
6. If you would like to inspect the list output, 11. After the program exits, you will see the go into O26 and issue the command following message flashing on the B dis- READ.OUTPUT. Then use the ( and ) play: keys to scroll through the output listing. REQUEST DISPLAY. (DIS) Use the XDIS. command to get back to DIS. 12. Stop for a moment and think what you should do to get back to DIS. Hint. Check See DIS Operation on page 2-15 for more E,A. for the EST ordinal of the display information on how to use DIS and Using console (DS). O26 on page 2-19.
90001100 2 2-49 13. Manually assign the display with the com- 15. When you are through with DIS, drop it mand n.ASSIGN,20. with the command
(E,A. shows that the EST ordinal for the DROP. DS (display console) equipment is 20.)
14. If you wish to make BOT a permanent part of the system, you will need to generate a new dead start tape. See [ Creating a New Dead Start Tape Xref ] for more informa- tion.
2-50 90001100 2 INDEX
Numerics dayfile, system 2-9 99 bottles 2-48 DCP 2-18 dead start 2-1 A date and time entry 2-4 access control word 2-30 dead start panel 2-1 account creation 2-24 DEBUG 2-12 account file 2-9 DEBUG mode 2-12 account management 2-22 DIAL 2-13 andy capp display 2-48 DIS 2-13, 2-20 application permission bits 2-30 DIS commands 2-18 ASSIGN 2-12 DIS displays 2-16 AUTO 2-12 DIS Operation 2-15 auto mode 2-16 DIS special keys 2-17 DISABLE 2-13 B -display option 2-2 baseball 2-48 display, X window 2-2 batch jobs 2-44 DROP 2-13, 2-18, 2-20 batch origin 2-35 DSD 2-7 BATCHIO 2-6, 2-10, 2-13 displays 2-8 BLITZ 2-12 E C ELS 2-18 capability permissions 2-31 emailed job output 2-46 central memory contents 2-9 ENABLE 2-13 CFO 2-12, 2-44 ENAi 2-18 CHECK POINT SYSTEM 2-12 ENBi 2-18 CKP 2-12 ENP 2-18 CMS 2-5 ENS 2-18 COBOL5 2-44 enter last statement 2-18 command from operator 2-44 enter next statement 2-18 COMMENT 2-12 ENXi 2-18 COMPASS 2-45 equipment status table 2-9 console keyboard 2-1 error log 2-9 control point activity 2-9 es 2-48 control point status 2-10 EYE 2-48 create_interstate_connection 2-44 F D file browsing in DIS 2-22 date entry error 2-5 file creation in DIS 2-22 dayfile 2-16 file name table 2-10, 2-44
90001100 2 Index-1 FNT 2-44 messages, sending to users 2-46 FORM 2-13 MODVAL 2-24 forms codes 2-46 FTN5 2-44 N NAM 2-6 G games 2-48 O GO 2-13, 2-44 O26 2-18 O26, using 2-19 H OFF 2-14 HOLD 2-18 OFFSW 2-14 ON 2-14 I ONSW 2-14 IAF 2-6 operator interface 2-39 IAF jobs 2-45 operator, winking 2-48 IAF origin 2-35 output jobs 2-46 IDLE 2-13 OVERRIDE 2-14 interactive jobs 2-45 interactive origin 2-35 P print jobs 2-46 J punch jobs 2-47 job management 2-34 job origin types 2-34 Q job output, emailed 2-46 queue status 2-11 job termination 2-45 jobs, IAF 2-45 R jobs, interactive 2-45 RCP 2-18 jobs, print 2-46 REQUEST 2-35 jobs, punch 2-47 request central processor 2-18 jobs, telex 2-45 resource use limits 2-27 ring 2-36 K RNS 2-18 keyboard, console 2-1 ROLLOUT 2-19 KILL 2-13 ROUTE 2-44
L S LABEL 2-35 SECONDARY USER CARDS 2-13 LOCK 2-13 sense switches, setting 2-44 LOGOFF 2-13 set user index 2-19 logoff 2-45 set user number 2-19 LUNAR 2-48 shutdown 2-7 Snoopy 2-48 M STEP 2-14 MAGNET 2-6, 2-13 SUBMIT 2-44 MESSAGE 2-13 SUI 2-19
Index-2 90001100 2 SUN 2-19 UNLOCK 2-15 system origin 2-35 UNSTEP 2-15
T V tape job management 2-35 VALIDATION 2-13 tape requests, processing 2-37 VSN 2-15, 2-36 tape ring 2-36 tapes, requesting 2-36 W tapes, unloading 2-43 WARN 2-15 TELEX 2-6, 2-13 winking at operator 2-48 telex jobs 2-45 worms display 2-48 telex origin 2-35 write ring 2-36 text mode, exiting 2-6 timesharing origin 2-35 X timesharing status 2-11 X 2-15 transaction facility 2-10 X window -display 2-2 XDIS 2-20 U XDROP 2-20 UNLOAD 2-15
90001100 2 Index-3