NETWORK WORKING GROUP R.T. BRADEN REQUEST FOR COMMENTS #379 UCLA/CCN NIC 11121 AUGUST 11, 1972 CATEGORIES : OBSOLETES: UPDATES:
IBM's Time Sharing Option ("TSO") is now available at CCN for use via
(1) Conversational Remote Job Entry
Using TSO you can prepare an OS job stream using the TSO EDIT command, SUBMIT the job to batch execution, monitor its STATUS, and ship the OUTPUT back to EDIT for examination. This allows those of you with TIP'S to process jobs at CCN without using NETRJS via a friendly TENEX machine. Any batch job can be submitted this way.
(2) Foreground Execution
Many OS/360 programs can be run, with varying degrees of inconvenience, directly from the terminal. There are TSO commands providing the facilities of EXEC and DD cards; the output stream can be directed to the user's terminal. There are some important limitations to fore- ground operation, however:
(1) The foreground region size is limited; at present, it is 128K, though this will be expanded.
(3) Since you are time-sliced and swapped, it can be very slow.
There are two important cases of foreground execution:
(A) The TEST command provides DDT-like debugging capability for foreground programs.
(B) The user's own program can interact with his terminal.
Monday through Friday, 6 A.M. - Noon PDT (or 9 A.M. - 3 P.M. EDT). These hours will be extended before September 1, 1972.
The document "USING TSO VIA ARPA NETWORK VIRTUAL TERMINAL", RFC #377 describes the use of a Telnet NVT to access TSO. There are some signi- ficant differences from using a real 2741 locally. RFC #377 describes the current server Telnet, complete with an annoying bug. A later version will include the following capabilities not presently available:
(a) "FULL DUPLEX", i.e., CCN echoing.
(b) Lower case input.
(c) The special character translation included in NETRJS users with Model 33 Teletypes. (see RFC #338).
(d) Optional specification of single CR or single LF as end-of-line indication
(e) Hopefully, the input attention bug described in RFC #377 will be fixed.
TSO will automatically place datasets created in the foreground (e.g., by EDIT or ALLOC) on the proper resident disk pack. All TSO datasets are cataloged, and can be referenced by name alone (no volume or unit specifi- cation is necessary). For most purposes, you can pretend we have one big
disk. --- --- ----
The standard IBM version of TSO uses the TSO user-id as the highest index of each dataset name. At CCN, the _two_ highest levels are the charge number and the user-id of the person who created the dataset. TSO has been modified accordingly.
In general, under TSO a user can access for reading, writing, or execution any dataset named with the charge number with which he is logged on. In addition, he can rename or scratch any dataset with the logon charge number. There is no provision for public or read-only datasets a present.
Most Network users will need only the simple form of LOGON:
logon <user-id> EXAMPLE: NOTES: ------- ----- user: logon uid (Use your user-id) TSO: LOGON UID (TSO repeats line for reasons of its own) TSO: ENTER PASSWORD (TSO asks for password)
TSO: UID LOGON IN PROGRESS AT 11:37:43 ON AUGUST 9, 1984
come every 30 seconds.)
TSO: WELCOME TO TSO. GOOD LUCK
User-id's are created in TSO with a blank password. To add or change your password, use the CHANGE command. If you have TSO access under more than one charge number, LOGON will prompt you for the charge number to be used for the session.
User: send 'hello' user(wdd)
TSO: USER WDD NOT LOGGED ON TSO: READY
user: send 'hello' user(pcn)
user: send 'edit is acting funny' user(pcn)
Here "PCN" was logged on and got your message. You can, therefore, converse with him through SEND. The text in one SEND is limited to 115 characters.
//<charge number> JOB 'BIN=9906',MSGLASS=C //* <message> //* //* //* //* etc.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by BBN Corp. under the ] [ direction of Alex McKenzie. 1/97 ]