Browse Prior Art Database

Using TSO at CCN (RFC0379) Disclosure Number: IPCOM000003561D
Original Publication Date: 1972-Aug-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 5 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Braden: AUTHOR

Related Documents

10.17487/RFC0379: DOI

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.



IBM’s Time Sharing Option ("TSO") is now available at CCN for use via the Network with Telnet Protocol. TSO is not yet considered "production" by CCN, since there are a number of restrictions and glitches to be removed or documented. However, TSO is now quite stable and is up on a regularly scheduled basis; the system will allow an experienced programmer to work productively at CCN. To use TSO, you will need a valid CCN charge (billing) number, and a user-id. To obtain a charge number (if you do not already have one), or to obtain a TSO user-id, contact Barbara Noble at (213) 825-7438 or (213) 825-7452. At present we are not charging for TSO use (although any batch jobs submitted from TSO will be charged to your account). Barbara can assign on overhead charge number for experimental use of TSO if you do not have a paid account.

Modes of TSO Use ----------------

(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.

[Page 1]

(2) All datasets referenced must be on resident disk packs; no disks or tapes can be mounted.

(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.

NOTE: It is not yet possible for a program, either in batch or foreground, to open direct Network connections.

Hours of Operation ------------------

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.

Telnet Protocol ---------------

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 use...