V4/man/man1/tss.1

Compare this file to the similar file:
Show the results in this format:

.th TSS I 3/15/72
.sh NAME
tss \*- interface to MH-TSS
.sh SYNOPSIS
.bd tss
.sh DESCRIPTION
.it Tss
will call the Honeywell 6070 on
the 201 data phone.
It will then go into direct access with
MH-TSS.
Output generated by MH-TSS is typed on the standard output and
input requested by MH-TSS is read from the standard input
with UNIX typing conventions.
.s3
An interrupt signal
is transmitted
as a `break' to MH-TSS.
.s3
Input lines beginning with
`!'
are interpreted as UNIX
commands.
Input lines beginning with
`~'
are interpreted as commands
to the interface routine.
.s3
.lp +15 10
~<file	insert input from named UNIX file
.lp +15 10
~>file	deliver tss output to named UNIX file
.lp +15 10
~p	pop the output file
.lp +15 10
~q	disconnect from tss (quit)
.lp +15 10
~r file	receive from HIS routine csr/daccopy
.lp +15 10
~s file	send file to HIS routine csr/daccopy
.s3
.i0
Ascii files may be most efficiently transmitted using
the HIS routine csr/daccopy
in this fashion.
Bold face text comes from MH-TSS.
.it Aftname
is the 6070 file to be dealt with;
.it file
is the UNIX file.
.s3
.bd SYSTEM?
csr/daccopy (s)
.it aftname
.br
.bd "Send Encoded File"
~s
.it file
.s3
.bd SYSTEM?
csr/daccopy (r)
.it aftname
.br
.bd "Receive Encoded File"
~r
.it file
.sh FILES
/dev/dn0,
/dev/dp0,
/etc/msh
.sh DIAGNOSTICS
Most often, `Transmission error on last message.'
.sh BUGS
When
problems occur,
and they often do,
.it tss
exits rather abruptly.