1 TTNET
	TTNET is an asynchronous terminal interconnection program
that allows a user on a local VAX/VMS system to login on a remote
system, issue commands, and, if the remote system is also VAX/VMS,
transfer files in both directions.

	Format:

	   TTNET (node::)[filespec[,...]] (node::)[filespec[,...]]

2 Parameters

	(node::)[filespec[,...]] (node::)[filespec[,...]]
	+----------++----------+ +----------++----------+
		   P1                       P2

	where "node::" may be the TERMR logical name that is assigned
to the modem or directly connected __TTXX: terminal line and "filespec"
is any valid VMS file specification. P1 is the "from" specification
and P2 is the "to" specification.

2 Qualifiers

/LOCAL (D)
/NOLOCAL

   Indicates whether TTNET is to be run on the "local" or "remote"
(nolocal) machine. The NOLOCAL qualifier disables all other qualifiers
and puts TTNET into "slave" operation.

/LOG (D)
/NOLOG

   Causes TTNET to "log" its activities on the user's terminal. In
batch mode the default is NOLOG, but may be overridden on the command
line.

/CRC (D)
/NOCRC

   Enables cyclic redundancy checking of all TTNET data packets.

/AUTODIAL(=sequence)

   If a modem sequence is not specified on the command line
this qualifier causes TTNET to prompt for an autodialer activation
sequence. Control characters must be represented by preceding the
character by a caret (^) as in "^E".

/HOST

   This qualifier causes TTNET to enter "virtual terminal" mode
so as to allow a user to access a remote machine as if having
a terminal directly connected to that machine.

/INSTALL

   This qualifier causes TTNET to propagate itself automatically
to a remote machine. The user must first log onto the remote
machine. The usual procedure is to first enter "virtual terminal"
mode, log in, and then exit as in: TTNET/HOST/INSTALL.

/STARTUP
/NOSTARTUP (D)

   The STARTUP qualifier causes a "local" machine to automatically
startup a "remote" machine TTNET. The user must first log onto the
"remote" machine and execute any necessary setup commands before
exiting back to the "local" machine. The usual sequence is:
TTNET/HOST/STARTUP filename1 TERMR::filename2.

/REDO(=value)

   REDO allows the user to specify a virtual block number for
a re-start transfer. This qualifier only has meaning if used
with a single file.

/LLINE=(characteristics,...)

   This qualifier allows the user to override his/her default
terminal settings. The characteristics are specified as they
are for the SET TERMINAL command, e.g., SPEED=9600.

/RLINE=(characteristics,...)

   This qualifier allows the user to override the default
terminal settings for the modem or direct connect serial line
that connects the "local" and "remote" machines. The characteristics
are specified as they are for the SET TERMINAL command, e.g., SPEED=9600.

/STATISTICS
/NOSTATISTICS (D)

   The STATISTICS qualifier causes TTNET to display in histogram
form packet information as it sends/receives packets across the serial
link.

/COMPRESS (D)
/NOCOMPRESS

   Indicates to TTNET to perform or not perform any data compression.

/VERSION
/NOVERSION (D)

   Causes TTNET to display the current version/revision level of
TTNET.EXE.

/ESCAPE

   Allows the user to set the "magic" escape character for exiting
TTNET. The specification must be a three digit decimal (000-255)
that represents a valid ASCII character. Any character is allowed
so be careful not to choose one that can't be input from the local
terminal keyboard or system. The default value is 030, "(cntrl) ^".

2 Examples

  $ TTNET/STARTUP/RLINE=(SPEED=19200) [...]*.* TERMR::[...] <return>

  $ TTNET/HOST <return>

  $ TTNET/HOST/INSTALL TTNET.EXE TERMR::* <return>

  $ TTNET/STARTUP/NOCRC TERMR::[...] [.DATA...] <return>

  $ TTNET/STARTUP/REDO=3 TEST.DAT;1 TERMR:: <return>

  $ TTNET/HOST/AUTODIAL=^E^MD^M555-5555^M^M <return>

2 Installation

   To install TTNET correctly on your "local" and "remote" machines
there are two methods you may use. These are (1) the user method and
(2) the system method. With the user method, the assignments,
command definition, and help facility are all established by
an individual user for his/her own use. The TTNET files
must merely be placed in a publicly available place and then
the users can tailor TTNET to their own specific requirements.
With the system method, the system manager places TTNET.EXE in
SYS$SYSTEM:TTNET.EXE, TTNET.HLB in SYS$HELP:HELPLIB.HLB or in
a locally defined help library, and TTNET.CLD into SYS$LIBRARY:
DCLTABLES.EXE (it may be added through a logon procedure invocation
of SET COMMAND).

2 Setup

   There are two methods for setting up TTNET: user mode and
system mode. These are described under their own headings.

3 User Mode

   (1) Invoke the DCL command "$ SET COMMAND TTNET <return>" first
on your "local" VAX to add the TTNET command to your process tables.
Be sure that the file TTNET.CLD contains the proper file specification
for where TTNET.EXE lives.

   (2) Make the following assignment:
       "$ ASSIGN outgoing_terminal_line_name: TERMR: <return>".

   (3) Allocate the line connected to the "remote" VAX with:
       "$ ALLOCATE TERMR: <return>". Contact the "remote" machine
       with "$ TTNET/HOST <return>". Please note that the
       "magic" escape character is <control>^.

   (4) Logon to the "remote" VAX and setup TTNET with: "$ SET COMMAND
       TTNET <return>" (note: This description assumes you already
       have the necessary files on both the "local" and "remote"
       VAXes). If you do not have any of the TTNET files on the
       "remote" VAX at this point exit TTNET and re-enter it with
       the /INSTALL qualifier turned on. You MUST be in the
       same directory as the TTNET.CLD file for /INSTALL to work.
       After the installation is complete, proceed to issue the
       following command on the "remote" machine:
       "$ SET COMMAND TTNET <return>"

   (5) You are now ready to use TTNET on both the "local" and "remote"
       machines.

3 System Mode

   If the TTNET files have been placed in their proper places,
the TTNET command has been properly defined in the user's process
tables, and the following assignment is in the "local" system logical name
space, TTNET may be executed on the "local" and "remote" machines
after allocating the outgoing line on the "local" machine.

       "$ ASSIGN/SYSTEM the_outgoing_modem_or_direct_line TERMR: <return>"
       "$ ALLOCATE TERMR: <return>"

   On the "remote" machine, everything but the assignment should
be the same (unless the files reside in different directories). There
is no assignment on the "remote" machine and nothing to allocate.
