% VAX-11 Librarian V04-00@/6܎6܎5 TTNET6܎1 TTNET: TTNET is an asynchronous terminal interconnection programAthat allows a user on a local VAX/VMS system to login on a remoteBsystem, issue commands, and, if the remote system is also VAX/VMS,"transfer files in both directions. Format:; TTNET (node::)[filespec[,...]] (node::)[filespec[,...]] 2 Parameters2 (node::)[filespec[,...]] (node::)[filespec[,...]]2 +----------++----------+ +----------++----------+ P1 P2> where "no de::" may be the TERMR logical name that is assignedGto the modem or directly connected __TTXX: terminal line and "filespec"Cis any valid VMS file specification. P1 is the "from" specification!and P2 is the "to" specification. 2 Qualifiers /LOCAL (D)/NOLOCALB Indicates whether TTNET is to be run on the "local" or "remote"F(nolocal) machine. The NOLOCAL qualifier disables all other qualifiers&and puts TTNET into "slave" operation./LOG (D)/NOLOGB Causes TTNET to "log" its activities on the user's terminal. InEbatch mode the default is NOLOG, but may be overridden on the commandline./CRC (D)/NOCRC@ Enables cyclic redundancy checking of all TTNET data packets./AUTODIAL(=sequence); If a modem sequence is not specified on the command lineBthis qualifier causes TTNET to prompt for an autodialer activationAsequence. 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 remoteAmachine. The usual procedure is to first enter "virtual terminal"6mode, log in, and then exit as in: TTNET/HOST/INSTALL./STARTUP/NOSTARTUP (D)B The STARTUP qualifier causes a "local" machine to aut omaticallyBstartup 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 usedwith a single file./LLINE=(characteristics,...)= This qualifier allows the user to override hi s/her default<terminal settings. The characteristics are specified as they3are for the SET TERMINAL command, e.g., SPEED=9600./RLINE=(characteristics,...)9 This qualifier allows the user to override the default=terminal settings for the modem or direct connect serial lineDthat connects the "local" and "remote" machines. The characteristicsIare specified as they are for the SET TERMINAL command, e.g., SPEED=9600. /STATISTICS/NOSTATISTICS (D)@ The STATISTICS qualifier causes TTNET to display in histogramFform packet information as it sends/receives packets across the seriallink. /COMPRESS (D) /NOCOMPRESSE 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./ESCAPEB Allows the user to set the "magic" escape character for exiting@TTNET. The specification must be a three digit decimal (000-255)Athat represents a valid ASCII character. Any character is allowedBso be careful not to choose one that can't be input from the localCterminal keyboard or system. The default value is 030, "(cntrl) ^". 2 ExamplesD $ TTNET/STARTUP/RLINE=(SPEED=19200) [...]*.* TERMR::[...]  $ TTNET/HOST 2 $ TTNET/HOST/INSTALL TTNET.EXE TERMR::* 8 $ TTNET/STARTUP/NOCRC TERMR::[...] [.DATA...] 4 $ TTNET/STARTUP/REDO=3 TEST.DAT;1 TERMR:: 4 $ TTNET/HOST/AUTODIAL=^E^MD^M555-5555^M^M 2 InstallationC To install TTNET correctly on your "local" and "remote" machinesDthere 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 by7an 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:CDCLTABLES.EXE (it may be added through a logon procedure invocationof 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 ModeB (1) Invoke the DCL command "$ SET COMMAND TTNET " firstDon your "local" VAX to add t he TTNET command to your process tables.FBe sure that the file TTNET.CLD contains the proper file specificationfor where TTNET.EXE lives.% (2) Make the following assignment:? "$ ASSIGN outgoing_terminal_line_name: TERMR: ".< (3) Allocate the line connected to the "remote" VAX with:A "$ ALLOCATE TERMR: ". Contact the "remote" machine9 with "$ TTNET/HOST ". Please note that the. "magic" escape character is ^.E (4) Logon to the "remote" VAX and setup TTNET with: "$ SET COMMANDB TTNET " (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 theA "remote" VAX at this point exit TTNET and re-enter it with; the /INSTALL qualifier turned on. You MUST be in theA same directory as the TTNET.CLD file for /INSTALL to work.? After the installation is complete, proceed to issue the1 following command on the "remote" machine:% "$ SET COMMAND TTNET "F (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,Athe TTNET command has been properly defined in the user's processJtables, and the following assignment is in the "local" system logical nameAspace, TTNET may be executed on the "local" and "remote" machines:after allo cating the outgoing line on the "local" machine.J "$ ASSIGN/SYSTEM the_outgoing_modem_or_direct_line TERMR: "# "$ ALLOCATE TERMR: "@ On the "remote" machine, everything but the assignment shouldEbe the same (unless the files reside in different directories). ThereAis no assignment on the "remote" machine and nothing to allocate.ww