RFC 379 (rfc379) - Page 2 of 5
Using TSO at CCN
Alternative Format: Original Text Document
(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
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.