Using TSO via ARPA Network Virtual Terminal
How to reach IBM TSO at UCLA-CCN over the ARPANET using a plain Telnet connection.
Braden, R.T., "Using TSO via ARPA Network Virtual Terminal", RFC 377, DOI 10.17487/RFC0377, August 1972, <https://www.rfc-editor.org/info/rfc377>.
@misc{rfc377,
series = {Request for Comments},
number = 377,
howpublished = {RFC 377},
publisher = {RFC Editor},
doi = {10.17487/RFC0377},
url = {https://www.rfc-editor.org/info/rfc377},
author = {R.T. Braden},
title = {{Using TSO via ARPA Network Virtual Terminal}},
pagetotal = 4,
year = 1972,
month = aug,
} RFC text
NETWORK WORKING GROUP R.T. BRADEN
REQUEST FOR COMMENTS #377 UCLA/CCN
NIC 11119 AUGUST 10, 1972
CATEGORIES:
OBSOLETES:
UPDATES:
USING TSO VIA ARPA NETWORK VIRTUAL TERMINAL
A. Connecting to TSO
-----------------
IBM's Time Sharing Option (TSO) is available at UCLA-CCN on Socket 1
using the standard Telnet protocol.
1. To access TSO, the remote user performs ICP to Socket 1 at CCN
and executes the command:
TSO CR LF
-- --
2. Possible responses to the TSO command are:
a. "WELCOME TO UCLA/CCN TSO"
followed by a herald ("!"). TSO is available. A TSO LOGON
command should be entered following the herald.
b. "TSO NOT AVAILABLE AT THIS TIME"
The user should check the TSO schedule and verify that it
should be available. If so, he can call the CCN on-line help
phone, 213-825-1652 for availability information, or send a
message to the operator through NETRJS.
c. "ALL TSO PORTS BUSY"
The user should try again after a short time. If this
condition recurs frequently, notify the Technical Liaison at
CCN so that more Network ports can be added.
3. When first connected to CCN server Telnet, the user has a choice
of several commands besides "TSO". The TSO-related commands are:
HELP - A listing of commands at this level, and other
general information.
BBOARD - List operational notices.
4. Local echoing (i.e., by the user site) is required.
5. Server-Telnet will time-out and disconnect the user if:
a. Output to the Network does not complete within 5 minutes, or
b. An INS, DATA MARK pair does not match within 2 minutes, or
c. TSO waits for the user to enter input for 20 minutes.
B. Conversing with TSO
-------------------
1. TSO is strictly a line-at-a-time system. Input is not scanned
until either an end-of-line or an INS (interrupt) is received at
CCN. TSO sends the user an exclamation mark ("!") as a herald
when waiting for input.
2. The end-of-line indication for input and output lines is the
standard CR LF sequence.
3. The remote user my interrupt TSO output by sending an INS and
DATA MARK (Telnet X'80'). Note to TIP users: this may be
accomplished with the TIP command "SEND SYNC". Each such
interrupt is passed to TSO, which interprets it as an output
break, i.e., as if the user pressed the ATTention key on his
2741 while the keyboard was _locked_.
On the Network, "attentions" are not used to delete lines being
entered. The CCN Server-Telnet provides line editing functions
for TSO users: the ASCII control CAN deletes the line being
entered, while BS deletes the preceding character.
4. There is a third interrupt case to be considered: suppose a
program has placed the user's terminal into input state, but the
user wants to suspend its execution and take control up a level
without satisfying the pending input request. This is supposed
to be accomplished by sending an INS/DATA MARK pair.
Unfortunately, due to a bug in our Network interface to TSO, the
interrupt will be ignored in this case. To circumvent this
problem, we recommend that you define a software break string,
such as "!!!!". This may be accomplished with the command:
TERM INPUT (!!!!)
Note that there are no quotes around the string. You can enter
this command when you first log on, and it will remain in effect
for the session (or until you issue a new TERM command). Then
any input line containing four successive exclamation points
will be interpreted as if an interrupt (attention) had been
sent. If that line contains other characters preceding the
exclamation marks, the latter will be interpreted as line
delete; otherwise, the result will be to take control up a
level.
C. Character Sets
--------------
1. Both upper and lower case input are allowed, but the server
Telnet will translate all lower case to upper. Output is
normally upper case.
2. Line-editing is provided by the Server-Telnet program before
passing the input line to TSO.
INPUT ACTION
----- ------
CAN (control X) delete current line.
BS (control H) delete previous character on
same line
(NOTE: Telnet control char-
acters are not deleted; they
are bypassed in the backspace
operation.)
HT (control I) insert one space in input.
All other ASCII controls are deleted from the input before
line-editing is performed.
3. Input lines are translated to EBCDIC by the rules used for a
NETRJS remote operator console (see Appendix B in RFC189).
Specifically:
a. ASCII controls are ignored except for BS, CAN, HT, and CR
LF.
b. The following correspondence is used for the EBCDIC graphics
not in ASCII:
[In the original, the ASCII and EBCDIC graphics were handwritten; in ]
[this version the ASCII graphics are typed and the EBCDIC graphics are]
[omitted.]
ASCII TSO
----- ---
! (Vertical bar)
~ (EBCDIC "not")
\ (Cent)
c. The six ASCII graphics not in EBCDIC are translated into
EBCDIC question marks.
4. All Telnet controls except DATA MARK are ignored.
RTB/gjm
8/10/72
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 9/99 ]
AI ELI5
On this page
§1Connecting to TSO
IBM's Time Sharing Option (TSO) is available at UCLA-CCN on Socket 1 using the standard Telnet protocol. The remote user performs ICP to Socket 1 at CCN and sends the command TSO followed by CR LF.
There are three possible responses. WELCOME TO UCLA/CCN TSO followed by a herald (!) means TSO is available, and a TSO LOGON command should follow. TSO NOT AVAILABLE AT THIS TIME means the user should check the TSO schedule or call the CCN on-line help phone. ALL TSO PORTS BUSY means to try again shortly, and to tell the Technical Liaison if this recurs often.
You knock on the door with the word TSO. The computer says welcome, come back later, or all the seats are full.
§2Talking to TSO
TSO is strictly line at a time. Input is not scanned until an end of line or an INS (interrupt) arrives, and TSO sends ! as a herald when it waits for input. Local echoing is required. The end of line indication is the standard CR LF.
A user can interrupt TSO output by sending an INS and DATA MARK pair (Telnet X'80'); TIP users can use the TIP command SEND SYNC. TSO treats this as an output break. The server Telnet disconnects the user if output to the network does not finish in 5 minutes, if an INS and DATA MARK pair does not match within 2 minutes, or if TSO waits 20 minutes for input.
You type one line at a time and press enter. If the computer talks too long, you can send a special signal to make it stop. If you wander off for too long, it hangs up.
§3A Known Bug and Its Workaround
If a program has put the terminal in an input state and the user wants to suspend it without answering, an INS and DATA MARK pair is supposed to take control up a level. Because of a bug in the network interface to TSO, that interrupt is ignored in this case.
The workaround is to define a software break string, for example TERM INPUT (!!!!), with no quotes. After that, any input line containing four successive exclamation points is treated like an interrupt. If other characters precede them, the exclamation marks act as a line delete.
One stop button did not work in one situation. So the note gives a secret code word you can type instead.
§4Character Sets and Line Editing
Both upper and lower case input are allowed, but the server Telnet translates lower case to upper, and output is normally upper case. Line editing is done by the server Telnet: CAN (control X) deletes the current line, BS (control H) deletes the previous character, and HT (control I) inserts one space. Other ASCII controls are deleted before editing.
Input is translated to EBCDIC by the rules used for a NETRJS remote operator console, described in RFC 189. For example, ASCII ! maps to a vertical bar and ~ to the EBCDIC not sign. Six ASCII graphics not in EBCDIC become question marks, and all Telnet controls except DATA MARK are ignored.
The big computer speaks a different alphabet than your terminal. A translator changes your letters, makes everything capital, and lets you fix typos with special keys.