ADA014398_Users_Guide_to_the_Terminal_IMP_Aug75 ADA014398 Users Guide To The Terminal IMP Aug75

ADA014398_Users_Guide_to_the_Terminal_IMP_Aug75 ADA014398_Users_Guide_to_the_Terminal_IMP_Aug75

User Manual: ADA014398_Users_Guide_to_the_Terminal_IMP_Aug75

Open the PDF directly: View PDF .
Page Count: 68

Download
Open PDF In Browser	View PDF

A D - A 0 14 3 9^
TERMINAL INTERFACE MESSAGE PROCESSOR:
USER'S GUIDE TO THE TERMIN A L I M P
J .

M a 1 ir a n

Bolt B e r a n e k and New m an,

Incorporated

Prepared for:
Advanced Research Projects Agency

/\ugust 1975

DISTRIBUTED BY:

tm

National Technical Information Service
U. S. DEPARTMENT OF COMMERCE

J

258110

T

\

1^«
/ -

ü
<

«>

^

\-

}

D D C
SEP
Approved for public releoMf
Dldtnbuticm unlimited

NATIONAl TECHNICAL
INFORMATION SERVICE
SpftoflftoM. VA. «151

8

1975

Report Mo. 2183

Bolt Boranek and Nnwman Inc.

NIC No. 10916

USER'S GUIDE TO THE TERMINAL IMP
August 1975 Revision

Sponsored by:
Advanced Research Projects Agency
ARPA Order No. 2351
Contract No. F 08606-75-C-0032

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

UPDATE HISTCV.Y
Originally written Dec. 1971 by W.R. Crowther
Updated July 1972 by D.C. Waiden
Completely revised Sept. 1972 by D.C. Waiden
Updated Oct. 1972 by D.C. Waiden
Updated Jan. 1973 by D.C. Waiden
Completely revised June 1973 by D.C. Waiden
Updated Nov, 1973 by J. Malman
Updated June 1974 by J. Malman
Updated Dec. 1974 by J. Malman
Completely revised August 1975 by J. Malman

il

Report No. 2183
August 1975 Revision

Seit Beranok and Newman Inc.

TABLE OF CONTENTS
Page
1.

INTRODUCTION

1-1

2.

THE NETWORK VIRTUAL TERMINAL

2-1

3.

THE TIP COMMAND FORMAT

3-1

4.

TYPICAL USE OF THE TIP

4-1

A.
B.
C.
D.
E.
F.

4-2
4-6
4-8
4-10
4-12
4-13

5.

6.

Hardware Stage
Establishing Parameters
Connection to Remote Sites
Use of Remote Sites
Connection Loss and Restoration
TIP News and User Feedback

UNUSUAL USES OF THE TIP

5-1

A.
B.
C.
D.
E.
F.
G.
H.
1.
J.
K.

5-2
5-4
5-f'
5-7
5-8
5-9
5-10
5-11
5-12
5-13
5-1u

Device Parameters
Talking to Another TIP
Binary Mode
Setting Another Terminal's Parameters
The DIVERT OUTPUT Command
Editing
Wild
Low Level Protocol Commands
Commands from the Network
The RESET Device Command
TIP Configuration and Device Pre-initialization

MAPPING THE VARIOUS DEVICES INTO THE NETWORK
VIRTUAL TERMINAL

6-1

A.
B.
C.

6-1
6-1
6-2

TTY and TTY-like Devices
2741 and 2741-like Devices
ASCII/2741 Conversion Table

7.

TIP MESSAGES TO THE TERMINAL USER

7-]

8.

THE TIP MAGNETIC TAPE OPTION

8-1

9.

CONNECTION OF TERMINALS TO THE TIP

9-1

APPENDICES

A-l

A.
B.
C.
D.

A-l
B-l
C-l
0-1

Host Addresses
Command Summary
Bibliography
Terminals Used with the TIP
111

Report No. 21d3
August 1975 Revision
1.

Bolt Boranok and Nownan Inc.

INTRODUCTION

This report describes the use of a terminal connected to a
Terminal IMP (TIP) in the ARPA Network. The report assumes that the
user knows how to operate a server Hose system somewhere on the
network once he becomes connected to that system, and the report
defines the procedures and options the user has available to establish
that connection.
The ARPA Network, IMPs and TIPs, hardware maintenance,
operation, and formats and protocols are not described here.
bibliography (Appendix C) lists the relevant documents.

TIP
The

At the time of this writing we at Bolt Beranek and Newman
Inc. (BBN) have operated the TIP extensively with the following
terminal types:
KSR-33 Teletype
KSR-37 Teletype
IBM-2741 (Correspondence)*
IBM-2741 (P.T.7.C.)*
DATA 100 (at 3 10, 150, 300, 600, and 1200 bps)
EXECUPORT (at 110, 150, and 300 bps)
INFOTON VISTAP I (at 110, 150, 300, 600, 1200,
1800, 2400, and 9600 bps)
IMLAC PDS-l (at 1800, 9600 bps, and synchronous)
ODEC 132 LINE PRINTER
TELETYPE INKTROMICS (Lino printer)
TI 733
DATA PRODUCTS LINE PRINTER MODEL 2410 or 2411
Where possible, all these devices have been operated with
connections to the TIP and also over a 103A dial-up modem.

direct

We have also briefly operated the TIP or heard of the TIP being
operated with a variety of other types of terminals. These are listed
in Appendix D. For your own safety, before you purchase any terminal
listed in Appendix D or any other terminal for use with the TIP, you
should check with BBN and try it with a TIP.
The TIP can also be configured with
discussed m Section 8.

a

magnetic

*For a 2741 to operate with the TIP, the 2741 must have
interrupt option and receive option.

1-1

tape

the

drive

as

transmit

Report No. 218 3
August 1975 Revision
2.

Bolt Beranek and Ncwnan Inc.

THE NETWORK VIRTUAL TERMINAL

IV key concept in the use of the network is the notion of the
Virtual terminal.
Instead of asking each Host system to cope with
every iterminal type at every other Host in the network, we ask the
Host Ito cope with a single (imaginary) terminal called the Network
Virtual Terminal. Your TIP will translate the data you type to make
it look like virtual terminal code, and translate the remote system's
response back into your terminal's code. While we will often pretend
that this translation does not exist, it is, in fact, always present
and of crucial importance to the user.
It is probable that the manual describing the use of the remote
system is written in terms of a user at the virtual terminal, most
likely as a system description based on local terminals plus an add-on
piece telling how to use the virtual terminal as a local terminal.
Virtual terminal code may include symbols which do not exist on your
own keyboard.
Combinations of your available characters are used in
such cases. You may even find that the translation makes your
terminal different from a local terminal of the same make. We have
tried to minimize this problem.
The Network Virtual Terminal has 128 keys, often in apper
case/lower case pairs. These keys correspond to the full ASCII set.
In addition, there are a few control keys, like the "BREAK" key.
The
terminal is capable of full and half duplex operation, under control
of a user-orientec switch. The meaning of the control keys and the
way to enter the full 128 keys from each of the terminal types which
the TIP supports is described in Section 6 of this report.
The user talks to the TIP after the code conversion has been
made; that is, the TIP expects virtual terminal characters. The
descriptions below are in terms of virtual terminal codes.

2-1

Report No. 218 3
August in7r) Revision
3.

Bolt Boranok nun Mowninn Ine

TUT Tip COMMANP FORMAT

The user at a terminal will at various times be talkinq directly
to his TIP instead of to the remote Host. A typical message of this
sort miqht look like:
OPFN

i >-,

Such a command always starts with symbol P and ends with either a
linefeed* or a rubout, depending on whether the user is satisfied with
the command or wishes to abort it. "he only exception to this rule is
the specific command
ja a

which inserts an 0 in the data stream to the Host. Commands may occur
anywhere, and need not start on a new line. Upper and lower case may
be freely intermixed in the command.
Between the 'a and the
more words to identify
parameter. The TIP is not
important thing about a
user to abbreviate a bit;
example miqht be:

linefeed there will typically be one or
the command, perhaps followed by a single
very sophisticated, and thinks the or1y
word is its first letter. This permits the
the more usual renderinq of the first
fan is

Once the user has started typing the parameter of a command the
old value of the command will have been destroyed, and cannot be
recovered by aborting the command.
Almost without exception the effect of a TIP. command is to set a
parameter or mode for the terminal. Even apparently direct commands
like
rd OPEN 15
(which initiates an elaborate exchange of messages resultinn in a
connection to the remote Host system) actually set a mode flaq to
request the appropriate action when the TIP is free to undertake it.
To understand the TIP behavior is really to understand the complete
set of parameters and the commands to change them.
Normally, any
parameter can be changed at any tine by the user at his terminal.
Exceptions occur when the user tries to change connection parameters
*0n 2741 terminals the return key transmits carriage-return/ linefeed
to the TIP and ASCII terminals are normally operated in a mode where
typing a carriage-return is interpreted as carriage-return/linefeed;
both car be used to terminate TIP commands in addition to a linefeed
alone.
3-1

Report No. 218 3
Auqust 1975 Revision

Bolt Boranek and bowman Inc.

on an open connection. An (aoPEN 13 executed while talkinq to Host IS
would generate the error message "Can't" (the connection to Host 15
must be closed before a connection can be opened to Host 13).
Commands often consist of several command wo^ds; for example,
0 DEVICE CODE ASCII
Such commands may be abbreviated; tor example
0 D C A
The spaces are required; 0 DCA is not a legal
lower case letters may be freely intermixed.

command.

Upper

and

An unusual variation in command format is to place a number
between the 0 and the first word of the command. In this case, the
command is not meant for the terminal typing but for the terminal
attached to the port of that nr.aber on the same TIP as the user. This
feature is described in some detail in the section on unusual uses of
the TIP, section 5.

W

Report Nr. 2183
August 1975 Revision
4.

BoU Boranok and Newman Inc.

TYPICAL USE OF TMF TIP

In the normal course of thinqs, a user will qo throuqh four more
or less distinct staqes in typinq into the net. First, he will be
concerned with hardware-power, dialinq in, etc.
Then ho
will
establish a dialogue with the TIP to get a comfortable set of
parameters for this usage. Next, he will instruct the TIP to open a
connection to a remote Host; and finally, he will mostly ignore the
TIP as he talks to the remote Host.
The following sections will
describe these stages in more detail.

14-1

Report No. 2183
August 1975 Revision
A.

Bolt Efranek and Newman Inc.

Hardware Stage

The hardware stage is primarily described in Section 9.
This
section describes only the final step of this stage, when the TIP
detects a terminal on one of its previously idle lines. At that point
the TIP normally goes into a "hunt" mode. In this mcde it expects the
very first character it sees to describe the terminal, according to
the following scheme
ASCII Terminals at 110, 150, or 300 baud type E.
that this must be upper case.)

(Note

2741 Correspondence Terminals type j, 4, o, or 1 depending
on the element used with the terminal — see Table 4-A.
2741 PTTC Terminals type:
6
o
v
f

for
for
for
for

model* 938, 939, 96], 362, or 997
model 942 or 943
model 94 7 or 94 8
model 963, 996, or 998

ASCII Terminais transmitting at 110 but receiving at
1200 baud type D.
(Again, upper case)
The TIP will deduce terminal rate, character size, and code
conversion based on the character typed.
When the TIP makes its
decision it types out TIP's name in the terminal's own language
followed by the version number of the TIP software system and the
octal port number. Then it is ready to go. If no TIP name appears,
or if garbage appears, hang up your data set and redial. For direct
connections Power Off is usually equivalent to hanging up.
Some terminals need special delays at the end of their lines in
order not to lose characters when running at high speed. The TIP
currently knows how to do this timing for the ODEC line printer and
several other devices. The two commands
0 DEVICE CODE EXTRA-PADDING
/a DEVICE CODE OTHER-PADDING
will instruct the TIP to insert these delays. One device we know of,
a Model 37 Teletype, requires a special parity computation to be able
to print correctly. The command
@ DEVICE CODE 37

*The model name and number is stamped on the top of the element.
you can't find it, trial and error works. Try "f" first.
iU2

If

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

instructs the TIP to insert the proper parity; when not in this mode
the TIP sets the parity bit to zero for all output characters. Echoed
characters are echoed without parity calculation. These commands are
discussed more fully in section 5.
On all terminals which hunt to
300
baud,
Device
Code
Extra-padding ((a D C E) automatically will be in effect. On all
terminals which hunt to 150 baud, Device Code 37
(0 D C 3)
automatically will be in effect. These effects can be canceled with
the command ^DEVICE CODE ASCII (0 D C A).

I-."5

Bolt Beranek and Newman Inc.
August 1975 Revision

TAi^E 4-A
Hunt- Character to be ..sed for
Type Elements

NUMBER

001
005
006
007
008
010
012
014
015
019
020
021
025
026
027
028
029
030
031
032
033
034
035
036
039
043
050
053
055
059
060
06 7

068
070
085
086
090
123
129
130
131
132
133

NAME
Scribe
Letter Gothic
Manifold 72
Elite 72 *
Pica 72 *
Manifold 72
Prestige Elite *
Light Italic
Courier 72 *
Manifold 72
Dual Gothic
Dual Gothic
Scribe
Elite 72 *
Pica 72 *
Manifold 72
Courier 72 *
Adjutant
Adj atant
Light Italic
Prestige Elite *
Script
Delegate
Advocate
Letter Gothic
ASCII
Advocate
Artisan 12-72
Artisan 12-12
Orator
Orator
Courier 12
Courier 12
Delegate
Courier 72
Courier 12 Italic
Script
Prestige Pica
Adjutant
Advocate
Artisan 12-72
Courier
Courir r 12 Italic

41 Correspondence

HUNT CHARACTER

4
4
j
4
4
j
4
I

4
j
4
o
o
0
0

o
o
4
o
o
o
o
o
o
o
1
4
4
o
j
o
4
o
4
4
o
j
o
0

o
<

o

* These type elements can be customized for you. Contact your
local IBM office fo: information. . .

Report No , 2183
August 1975 Revision
134
135
136
137
138
139
140
141
142
143
144
145
154
158
161

Courier 72
Delegate
Dual Gothic
Elite 72
Letter Gothic
Light Italic
Manifold 72
Orator
Pica 12
Prestige Elite 72
Scribe
Script
ASCII
Bookface Academic 72
Large Elite 72

Bolt Beranek and Newman Inc.

o
o
o
o
o
o
o
o
o
o
o
o
1
o
o

iu^

Report No. 2183
August 1975 Revision
B.

Bolt Beranek and Newman Inr-.

Establishing Parameterr

In stage two, the user is concerned with initiaüizinq
parameters.
The naive user should skip stage two and accept the
TIP's default parameters until an obvious problem arises.
The
following questions are answered in stage two:
1. When shall the TIP send off messages to the remote Host?
Here there are several options.
(The TIP is initialized to send
on every character, which is simple but inefficient.)
(9
(3
(3
(3

TRANSMIT
TRANSMIT
TRANSMIT
TRANSMIT

NOW
ON MESSAGE-END
ON LINEFEED
EVERY #

TRANSMIT NOW causes the message currently being accumulated
to be sent as soon as possible. TRANSMIT ON MESSAGE-END causes a
message to be sent as soon as possible after an ASCII DC3
(control-S) is encountered. TRANSMIT ON LINEFEED causes a message
to be sent as soon as possible after a linefeed is encountered.
Additionally,
both TRANSMIT ON MESSAGE-END and TRANSMIT ON
LINEFEED cause characters to be accumulated in the message buffer
until it is almost full. TRANSMIT EVERY * causes a message to be
sent as near as possible to every #th character.
The command
TRANSMIT EVERY 0 will reset the TIP to its initial state,
transmitting every character. If the parameter to TRANSMIT EVERY
is a large number (e.g., 250) the TIP will save up as many
characters as it can before sending a message, but does not offer
any guarantee that the total number specified can be buffered.
2.
Who shall echo, and when? Echoing is a complex problem,
without any neat solution. We have chosen to give the user the
means to tell us how he wants it done, since it is hard to guess
correctly in advance.
Basically, echoing can occur at the
terminal hardware, in the TIP, or m the remote Host.
The
corresponding TIP commands are:
0
(a
«a
(a

ECHO
ECHO
ECHO
ECHO

HALFDUPLEX
ALL
NONE
REMOTE

0 ECHO LOCAL

< *cho at terminal)
( :hc at TIP)
(bcho at remote Host)
(Send TELNET "remote echo" a1 id
perform internal P E N)
(Send TELNET "local echo" and
perform internal (a E A)

In the ECHO NONE mode, although characters for the remote Host are
not
echoed, the TIP will echo commands.
Network protocol
specifies that echoing shall start out in the ß ECHO ALL or 0 FCHO
HALF modes.
The TIP will try to guess from the terminal type
which of the two is appropriate. The goal of echoing strategy is
to avoid the unreadable alternatives of the blank page and the
doubling of every character. The naive user is advised to accept
14-6

Report No, 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

the TIP's default parameters until trouble of this sort arises. A
2741 is incapable of changing echo mode; it is always echo
halfduplex.
To allow more complex echoing conventions, the
TELNET
protocol provides a mechanism whereby the remote terminal user may
instruct the serving Host whether or not to echo chara.!:ers.
The
ECHO REMOTE and ECHO LOCAL commands at the TIP allow TIP users to
use this mechanism after the connection is made.
Finally, many Hosts which provide service request the TIP to
allow them to do the echoing. The TIP always grants this request
(even for 2741 terminals)r The user, if he does not desire this
mode, must cancel it AFTER the connection to the Host is
established.

^-7

Report No. 2183
August 1975 Revision
C.

Bolt Beranek and Newman Inc.

Connection to Remote Sites

In stage three, the user isconnection to a remote site.

concerned

with

establishing

a

0 OPEN 15
This amounts to "set the Host number parameter" and "add the user
to the queue of users waiting for the Tip's connection nechanism".
Appendix A lists the Host numbers of all the sites currently in
the network.
Connecting to a Host requires establishing a bi-directional
link, so that the terminal can send characters to the Host and
vice versa. The request to connect to a Host is thus really a
request to establish both transmit and receive sections.
When the user reaches the head of the queue waiting for
TIP'S "connection" mechanism, the TIP will type "Trying...".

the

Following the message "^rying", the user will receive some of
the following messages:
Open
Net Trouble
Refused
Host Scheduled

success*
remote site cannot be reached
remote site up but refusing
Down Until Sat. at 1850 GMT
Host will be back up at time and date
indicated
Host rnscheduled Down Until Sat. at 1850 GM^
Host will Lick up at time and date
indicated
Host not responding
Remote site not up, unknown when up
service will resume
ICP Interfered With
The Host has not performed the ICP
correctly and the TIP has refused
to open a connection.

The connection mechanism will run continuously until a state
described above occurs. This can be annoying when the remote site
is obviously not going to respond. The command

o cLosr
-"Open" indicates both halves of the TELNET connection have been
opened simultaneously.
Sometimes "Open R" followed by "Open T'
(or vice versa) will be printed; this too indicates both halves of
the connection have been opened, but not simultaneously. If only
"Open R" or "Open T" is printed, then the server Host has failed
to open one half of the TELNET connection.

^-6

Report No. 2183
August 1975 Revision

Bolt Beranek and Newnan Inc.

will abort the current connection attempt. The user is then free
to reattempt to open the connection or to attempt to open a
connection to some other Host.
The TIP's connection mechanism has caused
users
some
problems.
Perhaps a discussion of what the connection mechanism
is doing and how it works will alleviate some of the grief.
First of all, users attempting to connect to different Hosts
will
never
interfere
with
each
other,
although
users
simultaneously attempting to connect to the same Host will be
serviced serially.
For the user, opening proceeds in three phases.
In the
first, the user is queued up waiting to "c,et" the TIP's connection
mechanism.
In the second,
the user has gotten the
TIP's
connection mechanism and is beginning the connection sequence.
In
the third, the user has completed the connection sequence and i?
waiting for the Host to open up the actual data connections. Many
of the problems stem from the fact that only one user may be
proceeding through phase 2 at a given time -o a given Host.
Hence
the the TIP types out "Trying" when you get off the queue and the
connection mechanism begins trying to open your connections. Thus
the "Trying" message signifies the transition from phase 1 to
phase 2.

i*-9

Report No. 2183
August 1975 Revision
D.

Bolt Beranek and Newman Inc.

Use of Remote Sites

In stage four, the user is
without concern for the TIP.
available.

normally talking to the Host
All the TIP commands are still

One command that will eventually be of interest here is
0 CLOSE
This command starts the shut-down procedure. The TIP will echo
"Closed"* when the process is finished. The TIP does not know how
to log you out of the remote Host.
You must do this yourself
before closing the connection.
The virtual terminal has a key labeled "BREAK".
Some real
terminal have a break key, and some Host systems expect to see
breaks. Those terminals with a break key (but not the 2741 ATTN
key) may simply use it. Others must type the command
(9 SEND BREAK
The interpretation of the break is entirely up
Host -- many Hosts ignore it.

to

the

receiving

The virtual terminal also has a key labeled "SYNC". No real
terminals have such a key, and the function is unique to network
use. The "SYNC" key is a clue to the remote Host that there is an
important message which seems to be buffered in an "inaccessible"
place. The TIP and the Host go to some trouble to get the SYNC
indication over a different channel which bypasses the normal
buffering conventions. The command to send a SYNC is
(3 SEND SYNC
Typical usage of these commands might be (a S B followed by ß S S.
As stated earlier, the TIP nominally treats a carriagereturn typed by a user as a carriage-return/linefeed. The user
may cause the TIP to treat carriage-return as only caniage-return
by executing the command
(aCLEAR INSERT LINEFEED
*"Closed" indicates that the server Host, agreed to close both
halves of the TELNET connection simultaneously. If the halves of
the connection are closed one after another, "Closed R" followed
by "Closed T"
(or vice versa) will be printed.
If only one of
"Closed T" or "Closed R" is printed, wait a minute and the TIP
will force the other half of the connection to be closed.
^-10

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

To return to the nominal
coirunand

moae

of

carriage-return/lincfeod,

the

(?INSERT LINEFEED
should be executed.
If at any given time the user types characters faster than a
server Host will take them from the TIP, the TIP discards
characters it can not buffer and echos them with ^n ASCII BEL (on
a 2741, the type element is wiggled).
The user may sometimes use a server Host with which it is
desirable not to have (9 be a TIP reserved character. The user can
change the character which introduces TIP commands using the
command
(aINTERCEPT #
By typing ^INTERCEPT followed by a decimal number representing an
ASCII character, the user changes the TIP command character for
his device to the ASCII character represented by the number.
The
INTERCEPT ESC command resets the TIP command character to at-sign
(§). Thus,
0INTERCEPT 42
♦INTERCEPT ESC
changes the TIP command character to asterisk (*) and back to
at-sign C3) assuming the device was in the nominal mode (G) before
the first command was executed.
If the user attempts to change the intercept character but
fails to type a valid decimal number (or a character string
beginning with E) the TIP will type the diagnostic "Num" and will
set the intercept character to at-sign.

^-11

Report No. 2183
August 1975 Revision
i-.

Bolt Beranek and Newman Inc.

Connection Loss and Restoration

Starting with TENEX Hosts* running Software Version 1.32, if
TEMEX halts, the TIP will notify users connected to it of this
fact by typing "Connection Suspended". At this point the users
are free to do one of two things. First, they can wait till TENEX
restores service, in which case the TIP will type out "Connection
Restored" (or if after the the service interruption the connection
could not be restored, the TIP will type out "Host broke the
connection").
Alternatively,
the user is free to open a
connection to any other Host, in which case the TIP will invisibly
close the TENEX connection.
It is also important to point out
that if a user just leaves his terminal unattended across a TENEX
service outage without releasing the connection (any network
related command such as @H, (30, (QN, (ac will do the job) his job,
directory, etc., are left at the mercy of anyone who acquires that
terminal.

Other Hosts may also implement the mechanisms which will allow
the suspension and restoration of connections.
4-12

Report No 2183
August 1975 Revision
r

.

Bolt Beranek and Newman Inc.

TIP News and User Feedback

There is frequently information which the group developing
and debugging the TIP system wishes to convey to TIP users. For
instance, when a bug is detected, we may wish to warn users not to
use a certain feature until the bug is fixed. When a minor
improvement is made, we may wish to notify users. Further, there
is frequently news about the state of the network or the state of
a particular Host which should ha conveyed to TIP users. Finally,
TIP userr may wish to communicate with the TIP development staff
or the Network Control Center staff about problems or suggested
improvements for the TIP or the network. Consequently, we have
constructed a mechanism which we
hope
will
provide
for
communication in all the above directions. This mechanism is the
Network Virtual TIP Executive.* To activate this mechanism, the
TIP user may give the TIP command (aN. This command causes the TIP
to perform the necessary protocol to make a connection to the
Network Virtual TIP Executive which resides on severa] of the
network TENEX systems. Once the Network Virtual TIP Executive has
Deen activated, we think its operation is self-explanatory.
Presently available features within the Network Virtual TIP
Executive are a Network News feature, a Host Status feature, and a
"Gripe" feature. The latter provides users with a mechanism for
sending messages to the TIP development or NCC staffs. We
recommend that TIP use^s get the network news at the beginning of
every TIP session.
The TIP will normally prompt the user to consider reading the
news by typing the message:
Latest net news DATE
Use "QlKcrs" followed by "netnews"
at some point (s) during the usei'«5 session. The point chosen is
at the time of terminal recognition for "hunting" terminals (see
Section 4.A), or at each time a connection is closed for
"non-huntirg" terminals (see Section 5.A).
When a user issues an ^N command, the TIP requests support
from all cooperating servers. Thus, the user should be able to
reach a news facility. somewhere, almost all of the time.
However, in the event that no cooperating server is available the
TIP will time out the (3N command in about thirty seconds.
An @C
command will abort an (^N immediately.

*A version of the Resource Sharing Executive
the BBN TENEX Group.

4-13

being

developed

by

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman inc.

Of course, TIP users with an immediate need for communication
with the NCC or TIP development staffs should telephone (collect)
the Network Control Center (617-661-0100).
Users with general
questions about network usage (How do I find out if Host X is ever
going to be up again? What's happening with a Host/Host protocol
for graphics?) may also call the NCC.

H-1H

Report No. 218 3
August 1975 Revision
5.

Bolt Beranek and Newnan Inc.

UNUSUAL USES OF THE TIP

The "usual" use of a TIP is to connect one of the terminals
which the TIP supports to a remote Host. We have tried to make
this operation as easy and natural as possible for the user.
"Unusual" uses of the TIP are such things as connectincr a
non-standard terminal, talking terminal-to-terminal, or using
unusual protocols.
Such uses are possible, but within the
constraints of the TIP's size it has not always been feasible to
make them easy.

5-1

Report No. 2183
August 1975 Revision
A.

Bolt Beiranek and Newman Inc.

Device Parameters

The TIP uses a Hunt algorithm to aetermine device parameters.
On standard low speed terminals it works well and easily. If
something more complicated is desired, like entablishinq a rate
over 300 bps, the user must set these parameters himself.
The ^DEVICE RATE command does not affect the hunt-bit.
Therefore, the only way to change a port to, or from, being
hunting is to have the TIP site liaison call the NCC and have it
done.
The TIP stores device parameters in a 10-bit field
below:

as

shown

bits
1 2 !
t

i

!

Input rate

i

Character size
Output rate

where character size is 5 less than the number of bits per
character and the 16 rates are zero, 75, 110, 134.5, 150, 300,
600, 1200, 1800, 2400, 4800, 9600, 19200, unused, unused, and
external clock. The 4800, 9600 and 19.2K rates are available only
for output.
The user can change device parameters with the command
0 DEVICE RATE #
where # is the decimal equivalent of the 10-bit field the user
wishes to establish.
The command will often be executed from
another terminal (see Section 5-D below).

Report No. 2183
August 1975 Revision

Bolt Poranek and Newman Inc.

Some examples follow:
@D R
178
308
373
438
503
568
633
754

bps
110
ASCII i
150
300
600
1200
1800
2400
110 in 9600 out

243

134.5

2741 in and out

The user can set device code conversion with the commands
(3
(9
«3
fa

DEVICE
DEVICE
DEVICE
DEVICE

CODE
CODE
CODE
CODE

ASCII
EXTRA-PADDING
OTHEP-PADDING
37

EXTRA-PADDING is ASCII with a slow carriacre-return. This mode has
been found to be useful with EXECUPORT, T.I., AND DATAPOINT 3300.
DEVICE CODE OTHEP-PADDING is ASCII for a line-printer which
requires special timinn for a slow linefeed as well as a slow
carri age-return and also requires a minimum number of characters
per line of output. Two line-printers are currently handled via
the DEVICE CODE OTHER-PADDING option. These are the ODEC printer
and the MEMOREX printer. A qiven ^IP can be co-ifinured so that
DEVICE CODE OTHER-PADDING refers to either the OUKC nr the MFMOREX
printer but not both.
Often the device code commands will be executed by one
terminal for another terminal, as described in Section 5-D below.
Sometimes they are executed as the last step before changing a
terminal's
rate.
The code sets ASCII, EXTRA-PADDING, and
OTHER-PADDING are similar enough so that a terminal shifting from
one to another will still be able to talk to the TIP. All are
basically ASCII with different timing for the 3nd of line. DEVICE
CODE ASCII clears the effect of the other three DEVICE CODE
commands. The command
ODEVICE CODE 37
can be used to set up the TIP to correctly handle a Model 37
Teletype, namely to compute even-parity for output characters
(echoed characters have the parity they had when sent from the
terminal to the TIP).

5-3

Report No. 2183
igust 1975 revision
B.

Bolt Beranek and Newman Im

Talking to Another TIP

One can talk to a device on another TIP (or your own TIP)
using the TIP as a fancy telephone connection. This is not
particularly easy, especially since the only label a TIP knows for
a device is its hardware port number, which neither user may
happen to know. Supposing the port numbers arc known, one must
establish a pair of connections between the two ports. The
protocol for makinc- connections specifies that each end of each
connection will be labeled by a 32-bit socket number. The TIP
puts the port number in the high order 16 bits of the r cket
number, and 2 (or 3) in the low order bits for the receiving (or
sending) socket. The user must tell the TIP the Host number (in
decimal) and socket number (in octal) for the foreign end of both
the transmit and receive connections, for example, the commands
0
(9
(d
(a

SEND TO
RECEIVE
SEND TO
RECEIVE

HOST 158
FROM HOST 15 8
SOCKET 1600002
FROM SOCKFP 1600003

Simultaneously the far end must establish the corresponding
parameters for his half of the connection. Then one side or the
other must initiate the connections usinn the two commands
% PROTOCOL TO TRANSMIT
a PROTOCOL TO RECEIVE
This will open the full duple:-: connection.
the connection is to Pore 7 -it Host 158.
sequence of commancls nay be used, namely
(a
0
ut)
output)
output)
outnut)

or BS (output only)
or HT (output onlv)
or LF (output onlv)
(no output)
(no output)
or NL (outnut onlv)
(no output)
(no output)
(no output)
(no output)
(no output)
(no outnut)
(no output)
(no output)
(no output)
(no outnut)
(no output)
(no output)
(no output)
or <; (no output)*
(no output)
(no output)
(no output)
(no output)

*A ccnt-siyn will print if the r741 has one, otherwise there
will bo no output.

n-j

11/73

Report No,. 2183
June 1974 Update
40
41
42
43
44
45
46
47
50
51
52
53
54
55
56
57
60
61
62
63
6a
65
66
67
70
71
72
73
74
75

76
77

32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
43
49
50
51
52
53
54
55
56
57
5B
59
60
61
62
65

Bolt Beranek and Newman Inc.

SP

space
i

space
! or t
,,M
(inout) and " foutput)
# or " =
$ or M&

% or "7
& or "$
1
or •I
( or ••<
) or ">

•

*

+

+ or -H-h

/
')

2
2

/
0
1 or
2
3

'4

a

")

5
6
7
0
0
•

1

6
7
3
')

•
•
<

0

t

<

or " (
or A
> or ")

>
o

s
•?

6-4

or a

Report No.. 2183
June 1974 Update
100
101
102
103
10U
105
106
107
110
111
112
113
114
115
116
117
120
121
122
123
12U
125
126
127
130
131
132
133
134
135
136
137

Bolt Beranck and Newman Inc.

64
65
6G
67
68
69
70
71
72
73
74
75
76
77
78
79
80
31
82
83
34
85

3
A
B
C
D
E
F

n6

V

\r

^7
88
0
>9
yo

w

W
M
Y
7
M
[ or B
or V
\
1 or "E
/N or ^ or
or t

yi

)2
^3
04
95

3 or "+
A
B
C
D
F
F
g
ii
i

r,
H
I
J
K
L
M
N
0
P
0
R
S
T

J

K
L

n
M
0
P
0
R
S
T
U

V

X
Y

z
1
\
]

i
"«-

6-5

or

•» +

Bolt Deranck aivl :icwm5
1C0

1G7
170
171
172
173
174
175
170
177

"*

f

)6
97
98
99
100
101
102
103
104
105
106
107
10^
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127

a
b
c
6

a
b
c
c
f

f
9
h
i
j
k
1
m
n
o
P
n
r
s
t
u

'L

j
k
1
TTl

n
o
q
r
G

t
u

V

V
;'
X

w
X

if

y

7.

"6
j nr "V

'{
1
;
/i

tilde
DEL

rubout

6-6

-ior ,,"D (no output)

Report No. 2183
August 1975 Revision
7.

Bolt Beranek and Newman Inc.

TIP MESSAGES TO THE TERMINAL USER

BAD

The TIP doesn't recognize the conunand

Closed

Connection closed, usually by server Host

Connection Restored
Destination Host has restored the connection as it
was before the Host halted.
Connection Suspended
Destination Host has halted operation.
Host broke the connection
The Destination Host's service is restored but all
network connection tables have been reset.
Host not responding
Destination Host not up from the network's point
of view. It is not known when service
will resume.
Host Scheduled Down Until ...
Destination Host is scheduled down until the
date and time indicated.
Host UnscheduJ. d Down Until ...
destination Host is unscheduled down until the
date and time indicated.
ICP Interferred With
The Host has not performed the ICP correctly
and the TIP has refused to open a connection.
Latest Net news...
Use M(aN"
The TIP is conveying to the user Lhe date the
latest news item for TIP users was generated.
Net Trouble

Destination IMP cannot be reached due to some
kind of trouble in the network.

NO

Parameters may not be set for specified terminal.

Num

The TIP expected a number — command terminated.

Open

Connection opened by server Host.

R

Refers to the Receive side of a connection.

Refused

The remote Host rejected the attempt to establish
connections.
7-1

Report No. 2183
August 1975 Revision
T
TIP GOING DOWN

Bolt Beranek and Newman Inc.

Refers to the Transmit side of a connect!en.
The TIP is going down in the number of minutes
indicated — quickly stop what you are doing
and stop using the TIP.

TIP NAME

The TIP heard the user d.'.al in and establish rate.
The number following NAME is the TIP software
system version number. It is followed by the
octal port number.

Trying

The TIP is now servicing the user's OPEN request.

Wait

The TIP is attempting to contact an RSEXEC Server.

7-2

Report No. 2183
August 1975 Revision
8.

Bolt Beranek and Newman Inc.

TIP MAGNETIC TAPE OPTION

As one method of increasing the usefulness of the Terminal
IMP, we have developed a magnetic tape transfer capability as a
TIP option. The first such option was delivered to the field
during the first quarter of 1972. In order to ease the problems
of interfacing such a specialized terminal type, we chose to
specify the attachment of a standard Honeywell peripheral unit
rather than attempting to solve the problem of tape drive
attachment in a more generalized way. The unit chosen is the
Honeywell 316-4021 option which consists of a
tape
drive
controller and one drive unit (tae controller itself is capable of
handling up to
seven
additional
316-4022
drives).
The
characteristics of the tape drive include:
-

Read/write speed of 26 inches per second
Seven-track tapes
Even or odd parity (program selectable)
Industry compatible 200, 556, or 800 bpi

In addition to the tape drive and controller, the problem of
programming for the controller and the buffering of tape records
dictated the addition of a separate 4K memory bank to TIPs
equipped with this option.
The most immediate pressure for the addition of a magnetic
tape option to the TIP was the desire to enable a pair of TIP
users to copy tapes over the network from one TIP to another,
rather than shipping physical tapes by mail.
The magnetic tape system communicates with the network
through the TIP, although in many cases it bypasses the usual TIP
code, substituting its own procedures to allow for the special
nature and relatively high data rate of a magnetic tape terminal.
In nost respects, however, the tape nnit appears as a standard
terminal, arbitrarily designated number 77. On a TIP equipped
with magnetic tape, line 77 cannot be used as an external
terminal.
An additional terminal is required to issue commands to the
tape and receive status information and error comments. This may
be of any type and may be connected to any line. Its use as the
tape-controlling terminal can be concurrent with its normal usage.
The specific hardware design of the magnetic tape units used
dictates some constraints.
Tape format is 7-track usincr either
odd or even parity. In memory, tape frames are stored two to a
word occupying the high order twelve bit' of each word. Frames
can only be written in pairs; reading a record with an odd number
of frames causes the control unit to append an extra null frame to
the record in memory.
8-1

Report No. 218 3
August 1975 Revision

Bolt Beranek and Newman Inc.

The maximum record length is 2400 characters (frames).
This
limit is based on the amount of TIP core available for buffering.
If all maximum length records are used, this results in an 80%
utilization
of
tape
space at 800 bpi
(the remainder is
inter-record gaps).
The commands relating to magnetic tapes are of a less general
form than other TIP commands. Neither multiple spaces nor word
completion are presently permitted, and numbers are used to
distinguish different commands. The format is 3 M #1 #2, where #1
and #2 are the command number and its argument respectively.
The
commands, their numbers and arguments are:
Rewind
Forward Space Record
Forward Space File
Backward Space Record
Backward Space File
Read Record
Read File
Write Record
Write File
Transfer Files
Setup TIP-TIP Copy
Abort and Initialize
Write File Mark
Set Pa.- ity

1
2
3
4
5
6
7
8
9
10
11
12
13
14

decimal-count
decimal-count
decimal-count
decimal-count
decimal-count
decimal-count
decimal-count
decimal-count
decimal-count
decimal-count
foreign-TIP-number
parity (i.e. even or odd)
decimal-count
even-or-odd

A file mark is treated by the hardware as a record and must thus
be accounted for when spacing or reading by the RECORD commands.
The SETUP COPY command is used in the establishment of a
connection between TIis, described below.
There are some important things to note about magnetic tape
commands.
All regular TIP commands given for the tape, e.g.,
those specifying Host or socket parameters, must be preceded by
77.
This, of course, captures the tape drive for the terminal
giving the commands. All special tape commands
(those beginning
with M), implicitly capture device 77 in the same way. Thus once
any terminal issues a command for device 77 or any MAG command, it
has captured the magnetic tape; no one else is permitted to
control it until the owning terminal has issued the 077 GIVE BACK
command.
A network connection must exist before information may be
transferred.
A typical sequence of TIP commands which might
establish a connection between two magnetic tapes follows: at each
TIP,
the operator would issue a Setup Copy command to the Host
number of the other TIP. This command establishes socket numbers
for the "standard" TIP-to-TIP magnetic tape connection. Status
information about this connection such as Open, Closed, etc. will
be followed by MTR and MTT rather than the usual R and T to
differentiate magnetic tape activity from other activity of the
8-2

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

controlling terminal.
Then the write side would qive a Transfer
tiles command which would close MTT and MTR if necessary, and open
MTT.
When MTT opens, a request is sent to the other TIP, and MTT
is closed. The request prompts the other TIP to open MTR (his
MTT), rewind his tape, read and send the requested r.umber of
files, rewind his tape, and close the connection. The writing TIP
also rewinds its tape after writing the last file.
Errors and abnormal status conditions are detected and
messages are typed out on the controlling terminal. Errors whxch
will be of significance to the operator include:
UNREC ERR

Unrecoverable read or write errors
after 20 retries — a bad spot in
the tape or tape drive hardware
problems. The results of the
20tn try are used.

TIMEOUT

The tape controller remains busy
or no network activity occurs for
too long. The command is aborted.

OFFLINE

The mag tape unit is somehow not
operational (power off, no tape
mounted, vacuum off, wrong unit
number, etc.). The command
is aborted.

EOT

The tape has moved past the end-of-tape
marker. The command is aborted.

The error messages may be followed by MTR or MTT to denote which
side of the connection originated the message. At the request of
the TIP sites with magnetic tape option, records read in error
presently are reread many times and then transmitted anyway after
printing an error message. If aborted by an error condition, the
Transfer Files command will attempt to restart the transfer
requesting the other TIP to rewind '.ts tape, skip over as many
files as have already been written and send the remaining files.

8-3

Report No. 2183
August 1975 Revision

Bolt Beranek and Newirian Inc.

9.

CONNECTION OF TERMINALS TO THE TIP

A.

General Comments

The TIP allows the connection of most terminals that conform
to the EIA RS232 standard. The TIP is built such that it appears
to a terminal to be a modem and appears to a modem as a terminal.
If
a
terminal
has
a
25 pin connector (DD25P, several
manufacturers) and works with a 10 3 modem or equivalent, it will
probably work when plugged into an LIU card marked "T". Appendix
D lists terminals that have been used.
This section specifies the interface between a terminal and
the TIP.
See Section 4 for connections involving modems. It is
hoped that by examining this section, an engineer will be able to
determine whether he has met the conditions necessary for proper
operation of a terminal connected to the TIP.
To a large extent, the TIP follows EIA Standard RS-232C.
Familiarity
with
that
document
is recommended.
The pin
allocations specified by that standard are given inside the front
cover.
In order to connect a terminal to the TIP without modems,
each must look like a modem to the other. Input and output
connections are therefore cross-connected at the LIU pads, as
shown in Table 9-1.
Expansions to this specification are planned in the future
(particularly
as this relates to control signals).
It is
therefore very important that this section be kept up-to-date as
revisions are provided.
Connector - The connector from the terminal should be
equivalent to a Cinch DB-25P. It is recommended that extension
cords for terminals provide for all 25 pins in order to allow for
future changes.
Signal Levels - All signals are represented by bipolar low
voltage levels.
All signals are measured with respect to signal
ground. The source of a signal shall deliver a voltage of
magnitude between 5 and 25 volts into a load of not less than 3000
ohms. The reactive component of the load shall not be inductive,
and the capacitance shall not exceed 2500 pfd. measured at the
interface connector. The signals shall be interpreted in this
way:

9-1

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

Data Signals
-25
Computer

Status/
System

156

110

ADR

(VDH)->
PDP-ll

User
ELF

260

176

AFWL-TIP

TIP

244

164

ALOHA-TIP

TIP

320

208

AMES-11

(PDP-ll/45)->
CDC 7600

User

u:o

16

AMES-67

IBM 360/67

Server
TSS/360

220

144

AMES-TIP

067

55

ANL

TIP
(VARIAN-73)->
IBM 370/1^5

Server
OS-MVT

002

2

ARC-RD

PDP-11/40

User
ELF

034

28

ARPA-DMS

PDP-15

Iimited Server
Keydata DMS

234

156

ARPA-TIP

160

112

ASL

(VDH)->
PDP-11/10

User
ELF

350

232

BBN-1D

PDP-1

User

261

177

BBN10X-TIP

105

69

BBN-11X

PDP-11

Server
ELF

205

133

BBK-11XB

PDP-U

User
ELF

050

40

BBN-NCC

H-316

User

161

113

BBN-riAT

(vni-)->

User
ELF, R^--11

TIP

TIP

PPP-ll/40
A-l

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

062

50

BBN-SPEECH-•11

(PDP-11/40)->
SPS-41

Summer ' 75
ELF

361

241

BBN-TENEX

PDP-10

Server
TENEX

305

197

BBN-TENEXA

PDP-10

limited Server
TENEX

061

49

BBN-TENEXB

PDP-10

limited Server
TFNEX

162

114

BBN-TENEXD

PDP-10

limited Server
TENEX

236

158

BBN-TESTIP

033

27

BELVOIR

(PDP-ll)->
CDC 6600

User
(ANTS) Scope

035

29

BRL

PDP-11/40

User
ANTS

337

223

CCA-SIP

PDP-11/40

User
ELF

037

31

CCA-TENEX

{PDP-10)-:>
DatacomT3uter

dedicated Serv
TENEX,Datacomp

237

159

CCA-TIP

203

131

CHII

(VDH)->
Signal-1

Server

116

78

CMU-1CA

PDP-10

limited Server
DEC 10/50

016

14

CMU-10B

PDP-10

Server
DEC 10/50

216

142

CMU-11

C.mmp

Summer '75
Hydra

316

206

CMU-CC

(PDP-ll)->
Summer '75
IBM 360/67 + UNIVAC 1108

231

153

DOCB-TIP

065

53

EGLIN

TIP

TIP

TIP
CDC 6600

A-2

User
SCOPE

Report No. 2183
Augvit 1975 Revision

Bolt Beranek and Newman Inc,

024

20

ETAC

r.24

148

ETAC-TIP

041

33

FNWC

241

161

FNWC-TIP

015

13

GUNTER

230

152

GWC-TIP

111

73

HARV-1

PDP-1

User

Oil

9

HARV-10

PDP-in

limited Server
DEC 10/50

311

201

HASKINS

(VDH)->
PDP-11/45

User
ELF, RSX-11D

344

228

HAWAII-500

(PDP-11)-:
BCC 500

limited Server
(ELF) BKY OpSys

044

36

HAWAII-ALOHA

HP 2100

User
Menehune

117

79

I4-FLF

(PDP-11)->
ILLIAC IV

Server
(ELF)

017

15

I4A-TENEX

(PDP-'0)->
Ser^ er
ILLIAC IV + B6700

(PDP-11/45)->
CDC-6600

Sununer
(ANTS)

,

75

TIP
(CDC 3200)->
CDC 6500

Not Active
SCOPE
TIP

(PDP-11/35)-:
B4700

User
(ELF) MCPV
TIP

(TENEX)

217

143

I4B-TENEX

(PDP-10)->
ILLIAC IV

limited Server
(TENEX)

014

12

ILL-CAC

PDP-11/20

User
ANTS

114

76

ILL-NTS

PDP-11/50

User
UNIX

026

22

ISI-SPFECH11

(PDP-11/45)-'
SPS-41

User
ELF, DOS

264

180

ISI-TIP

326

214

ISI-XGP11

PDP-11/40

User
ELF

042

34

LBL

(CDC 6600)->
CDC 7600

Server
(Sesame) BKY

TIP

A-3

Report No. 218 3
August 1975 Revision

Bolt Beranek and Newman Inc.

052

42

LONDON

252

170

LONDON-TIP

152

106

LONDON~VDH

(VDH)->
(PDP-9)->
ATLAS II

User
CMAS

012

10

LL

IBM 370/168

limited Server
VM-370

312

202

LL-11

(PDP-11/45)-->
SPS-41

User
ELF, RSX-11M

137

95

LL-ASG

(VDH)->
PDP-11/50

User
ELF

212

138

LL-TSP

TSP

User

025

21

LLL-RISOS

PDP-11/45

limited Server
RATS

206

134

MIT-AI

PDP-10

limited Server
ITS

006

6

MIT-DEVMULTICS

H-68/80

User
Multics

106

70

MIT-DMS

PDP-10

Server
ITS

306

198

MIT-ML

PDP-10

Server
ITS

054

44

MIT-MULTICS

H-6180

Server
Multics

221

145

MITRE-TIP

023

19

NBS-ICST

223

147

NBS-TIP

TIP

250

168

NCC-TIP

TIP

351

233

NORSAR-40A

IBM 360/40

Fall '75
DOS/360

051

41

NORSAR-40B

IBM 360/40

Fall '75
DOS/360

251

169

NORSAR-T1P

(PDP-9)->
IBM 360/195

limited Server
OS/MVT ?
TIP

TIP
PDP-11/45 + PDP-10 Not Active.

TIP
A-4

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc,

071

57

NSA

PDP-1Ü

Fall '75
TENEX

053

43

OFFICE-1

PDP-10

dedicated Server
TENEX,NLS

040

32

PAROMAXC

(Nova)->
MAXC

limited Server
TENEX

140

96

PARC-VTS

Nova 800

User
VTS

046

38

PURDUE

PDP-11/45

User
ANTS

022

18

RADC-MULTICS

H-6180

User
Multics

222

146

RADC-TIP

107

71

RAND-ISD

PDP-11/45

Server
UNIX

RAND-RCC

IBM 370/158

Server
OS-MVT

Sigmri 7

User
BPS

007

TIP

045

37

RNL-7

245

165

RML-TIP

056

46

RUTGERS-10

256

174

RUTGERS-TIP

055

45

SCI-TENEX

PDP-10

limited Server

166

118

SCRL-ELF

(VDH)->
PDP-11/45

User
ELF

066

54

SCRL-ELFDEVEL

PDP-11/20

User
ELF

032

26

SDAC-4 4

IBM 360/44

limited Ser '«r
DOS/360, USC-PS

TIP
PDP-10/70

Server
TOPS-10
TIP

A-5

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

332

218

SDAOCC*5

BBN-Pluribus

alternate to
#39 decimal

047

39

SDAC-CCP

BBN-Pluribus

User

14 7

103

SDAC-DP

IBM 360/40

User
DOS/360

247

167

SDAONEP

IBM 360/40

User
DOS/360

232

154

SDAC-TIP

110

7^

SDC-CC

IBM 370/158

Server
VS2

010

8

SDC-LAB

IBM 370/145

limited Server
SDC-VM

102

66

SRI-AI

(PDP-10)->
PDP-15

limited Server
TENEX

202

130

SRI-ARC

PDP-11/40

User
ELF

263

179

SRI-CBC11

PDP-11/10

User

163

115

SRI-IA11

PDP-11/40

User
RSX-llM

063

51

SRI-NSC11

(PDP-ll/40)->
SPS-41

User
ELF, DOS

363

243

SRI-PKT

PDP-11

Summer '75

013

11

SU-AI

PDP-10

Server
DEC 10/50

113

75

SU-DSL

(VDH)->
PDP-11/20

User
ELF

070

56

SUMEX-AIM

PDP-10

Server
TENEX

253

171

TYMSHARE-TIP

142

98

UCB

(VDH)->
PDP-11/45

User
ELF, DOS

001

1

UCLA-ATS

PDP-11/45

User
ANTS, ELF

101

65

UCLA-CCN

IBM 360/91

Server
TSO, OS-MVT

TIP

TIP

A-6

Report No. 2183
August 1975 Revision
201

129

003

Bolt Beranek and Newman Inc.

UCLA-CCBS

(PDP-15)->
PDP-10

limited Server
DEC 10/50

UCSB~MOD75

IBM 360/75

Server
OLS, OS-MVT
Server
MCP

043

35

UCSD-CC

(Micro 810)->
B6700

214

140

UNIVAC

(VDH)->
User
(UNIVAC 1218)- >
UNIVAC 1616

027

23

USC-44

IBM 360/44

Server
USC-PS

327

215

USC-ECL

PDP-10

Server
TENEX

126

86

USC-ISI

PDP-10

^rver
TENEX

226

150

USC-ISIB

PDP-10

limited Server
TENEX

364

244

USC-ISIC

PDP-10

Server
TENEX

227

151

USC-TIP

004

4

UTAH-10

204

132

UTAH-TIP

TIP

257

175

WPAFB-TIP

TIP

TIP
PDP-10

A-7

limited Server
TENEX

Report No. 2183
August 1975 Revision
APPENDIX B:

Bolt Deranek and Newman Inc,

COMMAND SUMMARY*
Section

BINARY INPUT END
Leave 8-bit binary input mode

5-C

BINARY INPUT START
Enter 8-bit binary input mode

5-C

BINARY OUTPUT END
Leave 8-bit binary output mode

5-C

BINARY OUTPUT START
Enter 8-bit binary output mode

5-C

CLEAR DEVICE WILD
Set device to be unwild

5-G

CLEAR INSERT LINEFEED
Stop inserting linefeed after carriage-return

4-B

CLOSE
Close all outstanding connections, or abort current Host
login
4-D
DEVICE CODE 37
Establish parity computation for Model 37 Teletype

5-A

DEVICE CODE ASCII
Establish code conversion for an ASCII terminal

5-A

DEVICE CODE EXTRA-PADDING
Establish code conversion for a terminal with slow CR

5-A

DEVICE CODE OTHER-PADDING
Establish code conversion for a line printer

5-A

DEVICE RATE #
# is a 10-bit code specifying hardware rate and
character size settings

5-A

# DIVERT OUTPUT
Capture device # and divert this terminal's output
to it. # is an octal number.

5-F

ECHO ALL
Local TIP-generated echo — TIP echoes everything

*

# denotes a decimal number unless otherwise stated
B-l

4-B

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

ECHO HALFDUPLEX
Terminal-generated echo — TIP echoes nothing

4-B

ECHO LOCAL
Send the Telnet "ECHO LOCAL" character and
perform internal E A

4-B

ECHO NONE
Remote Host-generated echo for data —
TIP echoes commands

4-B

ECHO REMOTE
Send the Telnet "ECHO REMOTE" character and
perform internal E N

4-B

FLUSH
Delete all characters in input buffer

5-F

# GIVE BACK
Release control of captured device #.
# is an octal number.

5-D

HOST #
Simultaneous ''OS T H" and "OR F H"

5-B

INITIAL CONNECTION PROTOCOL
Start the initial connection protocol

5-H

INSERT LINEFEED
Insert linefeed after carriage-returns

4~D

INTERCEPT #
Use # as TIP command character

4-D

INTERCEPT ESC
Leave 7-bit binary mode

4-D
5-C

INTERCEPT NONE
Enter 7-bit binary mode

4~D
5-C

LOGIN a
An obsolete form of OPEN
M # #
Mag tape command # with argument *
NETWORK-VIRTUAL-TIP-EXECUTIVE
Connects the user to the Network-VirtualTIP-Executive.
OPEN #
Open a bi-directional connection to the Host
decimal address is specified
E-2

8
4-F

4-C

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc.

PROTOCOL BOTH
Simultaneous "PP T TM and "OP T R"

5-B

PROTOCOL TO RECEIVE
Manually initiate connection protocol

5-B

PROTOCOL TO TRANSMIT
Manually initiate connection protocol

5-B

RECEIVE FROM HOST #
Establish Host # parameter for manual
initialization

5-B

RECEIVE FROM SOCKET #
Establish socket # parameter for manual
initialization of connection -- socket # is
given in octal

5-B

RECEIVE FROM WILD
Equivalent to

M

^R F S

any^"

5-G

RESET
Reset current TIP port parameters

5-J

Reset NCP
Resets NCP

5-H

SEND BREAK
Send the Telnet "BREAK" character

4-D

SEND COMMAND
Send the command escape character

5-1

SEND SYNC
Send the Telnet "SYNC" character and
an "INTERRUPT SENDER" message

4-D

SEND TO HOST #
Establish Host # parameter for manual
initialization of connection

5-B

SEND TO SOCKET #
Establish socket # parameter for manual
initialization of connection — socket # is
given in octal
SEND TO WILD
Equivalent to "^S T S "
SET DEVICE WILD
Equilvalent to the commands "PR F H ",
"0S T H "r and "OR p S ".
B-3

5-B

5-G
5-G

Report No. 2183
August 1975 Revision

Bolt Beranek and Newman Inc,

TRANSMIT EVERY #
Send off input buffer at least every #th
character where 0<#<256
TRANSMIT NOW
Send off input buffer now

4-B

4-B

TRANSMIT ON LINEFEED
Send input buffer every time a linefeed is
encountered

4-B

TRANSMIT ON MESSAGE-END
Send input buffer every time an end-of-message
is encountered

4-B

B~k

Report No. 2183
August 1975 Revision
APPENDIX C:

Bolt Beranok ana Newman Inc.

BIBLIOGRAPHY

Most of the following should be available through your
Network Information Center Station Agent or the
ARPA Network Information Center
Augmentation Research Center
Stanford Research Institute
33 3 Ravenswood Avenue
Menlo Park, California 94025
Specifications for the Interconnection of a Host and an IMP, BBM
Report No. 1822 (IMP-HOST section of NIC 7104).
IMP Operating Manual, BBN Report No. 1877.
The Interface Message Processor for the ARPA Computer Network,
Heart et al, Proceedings AFIPS 1970 Spring Joint Computer
Conference (NIC 4655).
The Network Working Group "Request for Comment " Series: A Set of
Working Papers on Host Protocol.
The Network Resource Notebook, NIC 6740.
The BBN Terminal Interface Message Processor (Hardware Manual),
BBN Report No. 2184.
Specifications fcr the Interconnection of Terminals and the
Terminal IMP, BBN Report 2277.
ARPA Network Current Network Protocols, NIC 7104.
The Terminal IMP for the ARPA Computer Network, Ornstein et al,
Proceedings AFIPS 1972 Spring Joint Computer Conference.
Terminal Access to the ARPA Network: Experience and Inprcvements,
Mimno et al, COMPCON 73, Proceedings Seventh Annual IFFE Computer
Society International Conference, San Francisco, February 27 March 1, 1973.
TIP Users Group Notes, a series of informal
increase communication among the developers
and Hosts frequently used from TIPs. To be
distribution list for these notes, apply to

C-l

notes designed to
of the TIP, TIP users,
put on the
the NIC Station Agent.

Report No. 2183
August 1975 Revision
APPENDIX D:

TIP.

Bolt Beranek and Newman Inc.

TERMINALS USED WITH THE TIP

The following terminals are reputed to have worked with the
See the Introduction (Section 1).
A. B. DICK VIDEOJET 9600 LINE PRINTER (2400 bps)
ANDERSON-JACOBSON (models 630 and 841)
ARDS
KSR-35 Teletype
CALCOMP 565
CDI 1030/ "MULTICS" Terminal
DATA 100 (model 73)
DATAPOINT (models 2200, 3000, and 3300)
DELTA TELTERM 2
DIGITAL EQUIPMENT CORP. (models VT05 and GT40A)
EDT 1200
HAZELTINE 2000
LINEOLEX (model A)
MEMOREX 1240
SUGARMAN (model S-4 300)
TECTRAN CASSETTE
TKKTRONICS (models 4010 and 4013)
TELETERM (model 10 30)
TELETYPE (MODEL 38)
TERMIKET 300
TI S?lent 700
TYCOM
TRENDATA (model 1000)
UNIVAC DCT 500
VIDEO SYSTEMS (models 1200 and 5000)

We would be pleased to hear of any other terminals that have
operated on a TIP.
At the International Conference on Computer Communications
held in Washington, D.C., in October 1972, we had the opportunity
to personally test a number of the above terminals with the TIP.
As a result of this experience we now hold opinions as to the
methods and difficulty of connecting a number of these terminals
to the TIP. We suggest you call the Network Control Center to be
put ii touch with someone about this subject.

D-l



File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : Yes
XMP Toolkit                     : Adobe XMP Core 5.2-c001 63.139439, 2010/09/27-13:37:26
Metadata Date                   : 2012:11:01 10:02:54-04:00
Creator Tool                    : LuraDocument PDF Compressor Server 5.8.75.52
Create Date                     : 2012:10:31 18:59:01-05:00
Modify Date                     : 2012:11:01 10:02:54-04:00
Producer                        : LuraDocument PDF v2.52
Part                            : 1
Conformance                     : B
Document ID                     : uuid:uuid:4513f68b-c21e-1c69-3315-e1a2dfdd26e2
Version ID                      : 1
Instance ID                     : uuid:e091ec5e-d38b-4a49-87d5-5d2689d35e58
Format                          : application/pdf
Page Mode                       : UseNone
Page Count                      : 68
Creator                         : LuraDocument PDF Compressor Server 5.8.75.52