This chapter describes using the communications facilities distributed with RT--11. As distributed, RT--11 provides the software necessary for establishing and maintaining communications between one computer system running RT--11 and another running RT--11, RSX--11, or VMS.

This chapter describes: (unnumbered) What constitutes communications between computers and the fundamental hardware required. It then describes the software components distributed with RT--11 that support that fundamental hardware. How to configure the components to form a successful communications chain. How to establish communications between two computers. How to use the communications functionality. It describes, for example, how to capture (log) information from the host computer and how to transfer files.

If you intend to use the RT--11 communications facilities, you should read all the first three sections and those parts of the last section that apply to your particular communications configuration.

Use the on-line index utility, INDEX, and see the on-line help utility, HELP, for more information on topics described in this chapter. In this chapter, the phrase (transfer files between) one computer and another means to transfer files (in either direction).

The term (communications port) means the port on a computer to which you attach the transmission medium for connection with another computer. That port may or may not be marked as a communications port and may in fact be a console port or other serial port.

The term (data) can mean code, control sequences, or text data. Functionally, in this chapter, these terms are interchangeable. (Components\comm_comp_sec)

Communication between two computers occurs whenever data is transferred between them. Data transfer occurs when information located at one computer is accessed by or transferred to another computer.

For communications to occur successfully, the computers must be connected using a consistent hardware and software chain so that data passing between them is understood. That requires compatible hardware and software components.

It is beyond the scope of this chapter to discuss specific communications hardware. However, in general, the computer communications hardware chain consists of: (unnumbered) Two computers at opposite ends of the communications chain. A communications port controller on each computer that converts data for transmission and reception. A transmission medium that passes serial data between the communications ports. Other optional hardware that manages the transmission medium, such as a modem or switching device.

The relationship of those hardware components to communications software components is described in the following sections. (Local and Host Computers)

In software terms, the two computers that communicate with each other are called the (local) computer and the (host) computer. (Local computer)

The local computer is that computer to which your console terminal is attached; the computer that is local to you and running RT--11. The RT--11 software component that manages communications on your local computer is VTCOM. VTCOM is the RT--11 (virtual terminal communications) utility.

VTCOM is supported under only the mapped and FB monitors; you cannot run VTCOM with the distributed SB monitor. If, for some reason, you require support for VTCOM under an SB monitor, you must perform a system generation procedure and build an SB monitor with timer support. You also must use a VTCOM.REL file under SB that has never been run under FB.

VTCOM provides you with the following functionality: (unnumbered) Lets your local computer behave as a terminal that is directly connected to the host computer. As such, VTCOM lets you log onto the host computer and use all the software and hardware facilities available on that computer. Manages all file operations on your local computer when you transfer files between your local computer and the host. Lets you open a logging file on your local computer. That logging file records everything transmitted from the host computer to your local computer's terminal screen. Supports some commands and customizations that let you send, for example, a particular dial string to your modem. (Host computer)

The host computer is that computer with which you want to communicate; the computer at the other end of the transmission medium. The host computer can be running RT--11, RSX--11, or VMS.

If possible, you should install the appropriate version of the RT--11 distributed component, TRANSF, on the host computer. TRANSF is the (native mode transfer) utility. You can then run TRANSF from the host computer to transfer files between the local and host computers.

TRANSF has the following capabilities: (unnumbered) Lets you specify options to send files formatted as ASCII, BINARY, or FORTRAN between the hosts and local computers. Performs error checking on all file transfers; you are ensured of a reliable transfer. Supports command options that can produce a log of statistical information at the completion of the transfer. You can also specify a /PROGRESS option that displays transfer statistics as the transfer occurs. Decreases the size of each transfer segment automatically when it encounters line-noise or other interference, and increases the segment size automatically when the line clears. Therefore, the speed of the transmission is optimized.

RT--11 distributes specific versions of TRANSF that run in native mode on supported host computers running the RT--11, RSX--11, or VMS operating systems. (Communications Port Controllers)

RT--11 is distributed with device handlers that manage the communications port controller on the local computer. For CTI Bus-based local computers, that device handler is XC. For Q-bus and UNIBUS local computers, that device handler is XL which supports the DL11 and DVL11 port controllers.

The communications port controller on the host computer is managed by software installed on that computer.

A communications port controller converts data that is contained within the transmitting computer to a form that is suitable for transmission. At the other end of the transmission medium, a communications port controller converts data from the form in which it was transmitted to a form that is usable by the computer receiving that data. (Port Addressing)

The local computer communications port controller and communications device handler pass information to each other using two addresses, the (CSR) and (vector) addresses. (Baud Rate)

The (baud rate) is the speed at which the communications ports send and receive data. The baud rate must be compatible throughout the communications chain. If one link in the chain can function only at a particular baud rate, all other links in the chain must function at, or support, that baud rate. (Transmission Medium)

The transmission medium is not controlled by any software distributed with RT--11. Using distributed RT--11 software, you can only transmit data by using one type of transmission medium -- the serial line. However, a serial line can connect the communications ports of two computers in two ways: (unnumbered) (Unconverted Signal ---- Hardwired Serial Line Connections\bold)

When computers are relatively close together, they can communicate through a hardwire connection between the communications port of the local computer and a console port on the host, using a single section of serial line cabling. That type of connection is the fastest way of transmitting data between computers when using the distributed RT--11 software. Depending on the length of the serial line cabling, the power of the computers involved, and the current work load of those computers, you can often transmit data at the highest baud rates supported by the computer port controllers. (Converted Signal ---- Telephone Connections Using a Modem\bold)

When computers are far enough from each other that hardwiring is not possible, they communicate using a modem and telephone lines. That type of connection is considerably slower than hardwiring because of the conversion performed by the modem and the nature of telephone lines in general. With this type of connection, the speed of the transmission medium usually determines the baud rate for the communications chain. (Optional Hardware)

Other optional hardware can manage the transmission medium. Such hardware could be a modem or switching device.

RT--11 distributes no software component that directly controls modems or switching devices. RT--11 does provide some commands and customizations that let you pass information, such as a dial string, to some modems. (Configuring the Components\comm_con_sec)

The two computers for which you want to establish communications must be connected so that both the hardware and software components form a consistent chain. (Local Computer)

Make sure that the correct version of VTCOM is located on your local computer's system (SY) device. RT--11 distributes two versions of VTCOM. Which version of VTCOM you use is determined by the RT--11 monitor you are running at your local computer: (2\16) (RT--11 Monitor\Version of VTCOM) (XM or ZM\VTCOM.SAV) (FB\VTCOM.REL) (Host Computer)

Install the correct version of TRANSF on the host computer. RT--11 distributes the following versions of TRANSF for the following operating systems:

(2\16) (Version\Host Computer Operating System) (TRANSF.SAV\RT--11) (TRANSF.TSK\RSX--11) (TRANSF.EXE\VMS)

If your host computer is a PDP--11 running RT--11, make sure TRANSF.SAV is located on the host system (SY) device.

If your host computer is a PDP--11 running RSX--11, have the host computer system manager install TRANSF.TSK. Have your host system manager read the TRANSFER/TRANSF chapter of the (Sum_book).

If your host computer is a VAX running VMS, have the host computer system manager install TRANSF.EXE. Have your host system manager read the TRANSFER/TRANSF chapter of the (Sum_book). You do not need to install TRANSF on the host to initiate and maintain communications with that host. You install TRANSF on the host to perform error-free file transfers between the host and your local computer. If it is not possible for you to install TRANSF on a host computer, you can still communicate with that host computer and use its facilities. (Local Computer Communications Port Controller)

Because the communications port controller provides the connection between the computer and the transmission medium, you must configure the port controller with both the computer's communications device handler and the transmission medium. (Communications Port Controller --- Communications Device Handler)

Perform the following steps to configure the communications port controller with the communications device handler: (unnumbered) Make sure that the correct communications device handler is located on your local computer's system (SY) device. The following table shows the correct communications device handler file for each computer and monitor combination:

(2\20) (Computer (Monitor)\Required Communications Device Handler on SY) (CTI Bus-based(XM or ZM)\XCX.SYS) (CTI Bus-based (FB)\XC.SYS) (PDP--11 (XM or ZM)\XLX.SYS) (PDP--11 (FB)\XL.SYS) Make sure the CSR and vector addresses used by the local computer's communications port are known to the communications device handler.

You configure the port controller with the computer by setting the port controller device handler to recognize the addresses that controller uses to receive data from and send data to that computer.

The CSR and vector address are fixed and known on CTI Bus-based computers and do not require your attention.

If your computer is a Q-bus or UNIBUS PDP--11, do the following: (numbered) Find out which CSR and vector address your communications port controller uses. You can find that information in the User Guide supplied with that controller or with your computer system documentation. Issue the SHOW DEVICE command: (.)(SHOW DEVICE (RET))

That command displays the CSR and vector addresses for various device handlers on your computer system. Verify that the displayed CSR and vector address for XL match those used by the communications port controller. If either or both of the displayed addresses do not match those listed for your communications port controller, issue the following commands to match the device handler addresses with the listed port controller addresses. In the commands, the symbols (nnnnnn) and (nnn) represent respectively the correct CSR and vector addresses listed in the communications port documentation: (.)(UNLOAD XL (RET)) (.)(SET XL CSR=nnnnnn (RET)) (.)(SET XL VECTOR=nnn (RET)) (Communications Port Controller --- Transmission Medium)

You configure the port controller with the transmission medium by specifying the speed (baud rate) the controller should use to send data over the medium.

Make sure the transmission speed (baud rate) you set for the communications device handler matches the transmission speed of the entire communications chain.

On CTI Bus-based computers, use the following SET command, where (n) represents the baud rate, to specify the transmission speed: (.)(SET XC SPEED=n (RET))

On Q-bus and UNIBUS PDP--11 computers, set the baud rate directly on the communications port controller. (Transmission Medium)

If the transmission medium is a hardwired serial line, connect that line between a communications port on your local computer and a console port on the host computer.

If the transmission medium is a telephone line using a modem or routed through a switching device, be sure the modem or switching device is configured for the baud rate you set for your local computer's communications handler. (In fact, a telephone transmission line will probably limit the baud rate.) (Establishing Communications\comm_est_sec)

Once you have configured the communications chain, you can establish communications between the computers. Establishing communications involves starting VTCOM on your local computer and from your local computer, logging in to the host computer. (Starting VTCOM)

The first step in establishing communications between your local computer and the host is starting VTCOM on your local computer. The procedure you use to start VTCOM is determined by which RT--11 monitor you are running. If you are running a mapped monitor, you can start VTCOM as a system job or the foreground job. Typically, you would start VTCOM as a system job. If you are running the FB monitor, start VTCOM as the foreground job. (As a System Job under Mapped Monitors)

Running VTCOM as a system job lets you keep access open to the system, foreground, and background environments and to perform other tasks while maintaining communications with the host. To start VTCOM as a system job, issue the following commands. To start VTCOM as a system job each time you boot your system, include the following commands in your start-up command file. (For local CTI Bus-based computers, replace XL with XC in the second command line.) (.)(SRUN VTCOM.SAV/PAUSE (RET)) (.)(LOAD XL=VTCOM (RET)) (.)(RESUME VTCOM (RET)) (As the Foreground Job under FB)

Running VTCOM as the foreground job lets you keep access open to the background environment and perform other tasks while maintaining communications with the host. To start VTCOM as the foreground job, issue the following commands. To start VTCOM as the foreground job each time you boot your system, include the following commands in your start-up command file, STRTFB.COM. (For local CTI Bus-based computers, replace XL with XC in the second command line.) (.)(FRUN VTCOM.REL/PAUSE (RET)) (.)(LOAD XL=VTCOM (RET)) (.)(RESUME (RET)) (Connecting with the Host)

Once you have started VTCOM on your local computer, how you make connection with the host computer is determined by the manner you used to start VTCOM. (VTCOM as a System Job)

Perform the following procedure to connect with the host after starting VTCOM as a system job: (numbered) Press (CTRL/X) In response to the system job environment prompt, type VTCOM and press (RETURN): (Job?)(VTCOM (RET)) Log in to the host computer as you would from a directly attached console terminal. (VTCOM as the Foreground Job)

Perform the following procedure to connect with the host after starting VTCOM as the foreground job: (numbered) Press (CTRL/F) In response to the foreground job environment prompt, press (RETURN): (F>)( (RET)) Log in to the host computer as you would from a directly attached console terminal. (Using Communications\comm_use_sec)

Assuming you have performed the operations described in the previous two sections, you are now connected to a host computer. Connection to a host computer from your local computer can provide you the following functionality: (unnumbered) You have access to all the facilities available on the host.

If the host is connected to other computers through a network system, you, too, have access to those other computers through your connection to the host. You can open a logging file on your local computer and preserve in that file everything that is displayed on your terminal screen that originates from the host. You can transfer files between your local computer and the host. If TRANSF is installed on the host computer, you can transfer any files reliably because of error checking. If TRANSF is not installed on the host, you can transfer only ASCII files, and those transfers are performed without error checking. (Host Facilities)

You have access to all host facilities once you establish connection. There is no functional difference, other than perhaps speed, between being connected to the host through VTCOM or through a console terminal located at the host. (Capturing Information from the Host --- The Logging Facility)

VTCOM provides a logging file facility. You can open a logging file on your local computer and preserve in that file everything that is displayed on your terminal screen that originates from the host.

For example, you could log in to a timesharing host system that provides weather information. You could open a logging file on your local system, display the weather information on the host system, and then close (preserve) the logging file for examination after you logged out of the timesharing host system. (Caution) VTCOM does not check for the existence of files on your system that might match the logging file name.

Therefore, if a current file with the same name already exists, VTCOM writes over (destroys) the current file without warning. You must be careful to specify either a unique (new) logging file name or a current file that contains information you no longer want.

You will find it helpful to use a particular file type for all logging files you create to capture information from the host, such as .LOG. You can then easily obtain a directory of all logging files (DIR *.LOG) and then determine which file name you want to use. (Example)

The following procedure shows how you might capture and preserve weather information located on a timesharing host system. You can use this example as a general procedure for logging other kinds of information from a host computer. (numbered) Establish connection with the host computer. Decide on a name for the logging file. For the purpose of this example, assume you want to open the logging file WEATHR.LOG. Go to the background environment and display the directory of all files of type .LOG. If WEATHR.LOG exists, determine if you want the contents of that file. ((CTRL/B)) (.)(DIR *.LOG (RET))

For the purpose of this example, assume WEATHR.LOG does not exist in your directory.

Reestablish connection with VTCOM. Open a logging file on your local computer: (numbered) Press (CTRL/P).

VTCOM displays its command prompt: TT::VTCOM> Type OPENLOG and press (RETURN). (TT::VTCOM>)(OPENLOG (RET)) VTCOM prompts for the logging file name: TT::VTCOM> Log file? Type WEATHR.LOG and press (RETURN). (TT::VTCOM> Log file?)(WEATHR.LOG (RET))

From this point until you close the logging file, everything displayed on your local computer terminal screen that originates from the host is logged in the file WEATHR.LOG. Press (RETURN) to display the host computer command prompt. Access the weather information. You log only information that is displayed on your terminal screen. Close the logging file: (alphabetic) Press (CTRL/P).

VTCOM displays its command prompt: TT::VTCOM> Type CLOSELOG and press (RETURN). (TT::VTCOM>)(CLOSELOG (RET)) You can then continue connection with the timesharing host system, open another logging file, or disconnect from the host. You now have a logging file named WEATHR.LOG on your local computer. You can edit that file, type it, or print it.

In this manner, you can transfer any ASCII information located on a host computer to your local computer.

Although it is possible to transfer all or a portion of an ASCII file from a host to your local computer by using this procedure, you should, if possible, use TRANSF to transfer files. The VTCOM logging file functionality performs no error checking. Use the VTCOM logging file functionality only when the information you want to capture is not a file or you cannot install TRANSF on the host. (Transferring Files)

As described in the previous section, you can transfer the contents of any file between your local computer and the host computer if the TRANSF utility is installed on the host computer.

If it is not possible to install TRANSF on the host, you can transfer only ASCII files by using the VTCOM logging file functionality. That functionality does not provide error checking and should be used only if you cannot install TRANSF on the host computer.

The following two sections describe transferring files when TRANSF is installed on the host computer and when it is not. (With TRANSF Installed on the Host)

With TRANSF installed on the host computer, you can transfer any kind of file between your local computer and the host. Although you use TRANSF to transfer files in either direction, you always run TRANSF from the host computer.

Each version of TRANSF is written to run in native mode on the host computer's operating sytem. Therefore, this section is divided into descriptions of using TRANSF with the three supported operating system combinations. (With a VMS Host)

A VMS host has a different file structure than your local computer. The difference in file structure characteristics has two ramifications: (unnumbered) A VMS host supports a file specification with file names longer than six characters and file types longer than three characters. When you transfer a file that has an invalid (too large) file specification from the host to your local computer, you must supply a valid local computer file specification. Otherwise, TRANSF truncates the host file specification to make it valid on your local computer. The difference in file structures requires TRANSF to perform file format translations. TRANSF provides options you use to specify the type of file you are transferring.

The following is the general command syntax you issue from a VMS host to transfer files: $ TRANSF infile.ext/options outfil.ext/options (RET)

In general, you should ask the following four questions to determine which options to use: (unnumbered) Where is the file I want to transfer; where is (infile.ext)?

If the file is currently on your local computer, you must indicate that by including the /TERMINAL option with (infile.ext). The /TERMINAL option tells TRANSF which file, (infile.ext) or (outfil.ext), resides on the local computer file. Where is the file to be transferred; where is (outfil.ext)?

If the file is to be transferred to your local computer, you must indicate that by including the /TERMINAL option with (outfil.ext). What kind of file am I transferring?

TRANSF recognizes a number of standard file types and performs the file transfer according to those types. However, you should generally specify the type of file format you are transferring. You tell TRANSF what format to use by specifying one of the following options:

(2\10) (Option\Meaning) (/ASCII\This is an ASCII file transfer.) (/BINARY\This is a BINARY object (.OBJ) code file transfer.) (/FORTRAN\This file has FORTRAN carriage control.) (/IMAGE\Transfer this file in IMAGE mode. IMAGE mode transfers are bit-for-bit image copies.)

Any file type not recognized by TRANSF is transferred in IMAGE mode, possibly producing unexpected results. Use the /HELP qualifier to display those file types recognized by TRANSF. Do I want any information about this transfer during or after the transfer completes?

TRANSF provides options you can specify that cause additional information concerning the transfer to be displayed before the transfer, during the transfer operation or after the transfer completes. The following table lists useful information options:

(2\14) (Option\Meaning) (/HELP\Displays limited information about TRANSF, including the default transfer mode for various file types.) (/LOG\Displays a log of the transferred files at the end of the transfer. Very useful.) (/PROGRESS[:n]\Displays the progress of the transfer as the transfer takes place. The value (n) specifies the message display interval. By default, the interval is every 10 blocks or records transferred. Useful if you have questions about the quality of the transmission medium or have experienced other recent problems with transfers.) (/PROMPT\Places TRANSF in interactive mode. TRANSF then displays questions about the transfer, displays defaults, and prompts for your response. Useful as a beginning aid.) (/SPOOL\Directs transfer output to the default host printer queue.) (/STATISTICS\Displays useful information at the end of the transfer.)

The following examples demonstrate types of transfers: (ASCII Transfers)

The following command line, issued at the host, transfers the ASCII file LOCAL.TXT from your local computer to a file named HOST.TXT on the host. Note the placement of the /TERMINAL option. The command requests logging and statistical information at the end of the transfer: ($)( TRANSF LOCAL.TXT/TERMINAL/ASCII/LOG/STATISTICS HOST.TXT (RET))

The following command line, issued at the host, transfers the ASCII file HOST.TXT from the host computer to a file named LOCAL.TXT on your local computer. Note the placement of the /TERMINAL option. The command requests logging and statistical information at the end of the transfer: ($)( TRANSF HOST.TXT/ASCII/LOG/STATISTICS LOCAL.TXT/TERMINAL (RET))

The following command line, issued at the host, transfers the ASCII file LOCAL.TXT from your local computer to a file of the same name (LOCAL.TXT) on the host. Note the placement of the /TERMINAL option and the absence of (outfil.ext). The command requests logging and statistical information at the end of the transfer: ($)( TRANSF LOCAL.TXT/TERMINAL/ASCII/LOG/STATISTICS (RET)) (BINARY and FORTRAN-Formatted Transfers)

BINARY and FORTRAN-formatted files are transferred in the same manner as ASCII files, except you use the /BINARY or /FORTRAN format option in place of the /ASCII option. (IMAGE Transfers)

The following command line, issued at the host, performs a bit-for-bit transfer of the file LOCAL.FOO from your local computer to a file named HOST.FOO on the host. Note the placement of the /TERMINAL option and the absence of any formatting option; an IMAGE mode transfer is done because the FOO file type is not recognized by TRANSF. The command requests logging and statistical information at the end of the transfer: ($)( TRANSF LOCAL.FOO/TERMINAL/LOG/STATISTICS HOST.FOO (RET))

The following command line, issued at the host, performs a bit-for-bit transfer of the file HOST.FOO from the host computer to a file named LOCAL.FOO on your local computer. Note the placement of the /TERMINAL option and the absence of any formatting option; an IMAGE mode transfer is again done because the FOO file type is not recognized by TRANSF. The command requests logging and statistical information at the end of the transfer: ($)( TRANSF HOST.FOO/LOG/STATISTICS LOCAL.FOO/TERMINAL (RET))

The (SRN_BOOK) contains a complete description of the TRANSF utility for VMS host computers. You should also use the RT--11 on-line index facility, INDEX, to find the latest information about TRANSF. (With an RSX--11 Host)

An RSX--11 host has a different file structure than your local computer. The difference in file structure characteristics produces two ramifications: (unnumbered) An RSX--11 host supports a file specification with file names longer than six characters. When you transfer a file from the host to your local computer that has an invalid (too large) file specification, you must supply a valid local computer file specification. Otherwise, TRANSF truncates the host file specification to make it valid on your local computer. The difference in file structures requires TRANSF to perform file format translations. TRANSF provides options you use to specify the type of file you are transferring.

The following is the general command syntax you issue from an RSX--11 host to transfer files: $ TRANSF infile.ext/options outfil.ext/options (RET)

In general, you should ask the following four questions to determine which options to use: (unnumbered) Where is the file I want to transfer; where is (infile.ext)?

If the file is currently on your local computer, you must indicate that by including the /TERMINAL option with (infile.ext). The /TERMINAL option tells TRANSF which file, (infile.ext) or (outfil.ext), resides on the local computer file. Where is the file to be transferred; where is (outfil.ext)?

If the file is to be transferred to your local computer, you must indicate that by including the /TERMINAL option with (outfil.ext). What kind of file am I transferring?

TRANSF recognizes a number of standard file types and performs the file transfer according to those types. However, you should generally specify the type of file format you are transferring. You tell TRANSF what format to use by specifying one of the following options:

(2\10) (Option\Meaning) (/ASCII\This is an ASCII file transfer.) (/BINARY\This is a BINARY object (.OBJ) code file transfer.) (/FORTRAN\This file has FORTRAN carriage control.) (/IMAGE\Transfer this file in IMAGE mode. IMAGE mode transfers are bit-for-bit image copies.)

Any file type not recognized by TRANSF is transferred in IMAGE mode, possibly producing unexpected results. Use the /HELP qualifier to display those file types recognized by TRANSF. Do I want any information about this transfer during or after the transfer completes?

TRANSF provides options you can specify that cause additional information concerning the transfer to be displayed during the transfer operation or after the transfer completes. The following table lists useful information options:

(2\14) (Option\Meaning) (/HELP\Displays limited information about TRANSF, including the default transfer mode for various file types.) (/LOG\Displays a log of the transferred files at the end of the transfer. Very useful.) (/PROGRESS[:n]\Displays the progress of the transfer as the transfer takes place. The value (n) specifies the message display interval. By default, the interval is every 10 blocks or records transferred. Useful if you have questions about the quality of the transmission medium or have experienced other recent problems with transfers.) (/PROMPT\Places TRANSF in interactive mode. TRANSF then displays questions about the transfer, displays defaults, and prompts for your response. Useful as a beginning aid.) (/STATISTICS\Displays useful information at the end of the transfer.)

The following examples demonstrate types of transfers: (ASCII Transfers)

The following command line, issued at the host, transfers the ASCII file LOCAL.TXT from your local computer to a file named HOST.TXT on the host. Note the placement of the /TERMINAL option. The command requests logging and statistical information at the end of the transfer: ($)( TRANSF LOCAL.TXT/TERMINAL/ASCII/LOG/STATISTICS HOST.TXT (RET))

The following command line, issued at the host, transfers the ASCII file HOST.TXT from the host computer to a file named LOCAL.TXT on your local computer. Note the placement of the /TERMINAL option. The command requests logging and statistical information at the end of the transfer: ($)( TRANSF HOST.TXT/ASCII/LOG/STATISTICS LOCAL.TXT/TERMINAL (RET))

The following command line, issued at the host, transfers the ASCII file LOCAL.TXT from your local computer to a file of the same name (LOCAL.TXT) on the host. Note the placement of the /TERMINAL option and the absence of (outfil.ext). The command requests logging and statistical information at the end of the transfer: ($)( TRANSF LOCAL.TXT/TERMINAL/ASCII/LOG/STATISTICS (RET)) (BINARY and FORTRAN-Formatted Transfers)

You transfer BINARY and FORTRAN-formatted files in the same manner as ASCII files, except you use the /BINARY or /FORTRAN format option in place of the /ASCII option. (IMAGE Transfers)

The following command line, issued at the host, performs a bit-for-bit transfer of the file LOCAL.FOO from your local computer to a file named HOST.FOO on the host. Note the placement of the /TERMINAL option and the absence of any formatting option; an IMAGE mode transfer is done because the FOO file type is not recognized by TRANSF. The command requests logging and statistical information at the end of the transfer: ($)( TRANSF LOCAL.FOO/TERMINAL/LOG/STATISTICS HOST.FOO (RET))

The following command line, issued at the host, performs a bit-for-bit transfer of the file HOST.FOO from the host computer to a file named LOCAL.FOO on your local computer. Note the placement of the /TERMINAL option and the absence of any formatting option; an IMAGE mode transfer is done because the FOO file type is not recognized by TRANSF. The command requests logging and statistical information at the end of the transfer: ($)( TRANSF HOST.FOO/LOG/STATISTICS LOCAL.FOO/TERMINAL (RET))

The (SRN_BOOK) contains a complete description of the TRANSF utility for RSX--11 host computers. You should also use the RT--11 on-line index facility, INDEX, to find the latest information about TRANSF. (With an RT--11 Host)

RT--11 host computers have the same file structure as your local computer. Therefore, TRANSF performs no format translation and you do not need to specify format options. All file transfers take place in image mode.

The following is the general command syntax you issue from an RT--11 host to transfer files: .TRANSF infile.ext/options outfil.ext/options (RET)

In general, you should ask the following three questions to determine which options to use: (unnumbered) Where is the file I want to transfer; where is (infile.ext)?

If the file resides on your local computer, you must indicate that by including the /T option with (infile.ext). The /T option tells TRANSF which file, (infile.ext) or (outfil.ext), is the local computer file. Where is the file to be transferred; where is (outfil.ext)?

If the file is to be transferred to your local computer, you must indicate that by including the /T option with (outfil.ext). Do I want a log of statistical information after completion of the transfer?

If you want statistical information, include the /W option. (Example Transfers)

The following two examples illustrate transferring files between the host and your local computer.

The following command line, issued at the host, performs a bit-for-bit transfer of the file LOCAL.FOO from your local computer to a file named HOST.FOO on the host. Note the placement of the /T option. The command requests logging and statistical information at the end of the transfer: (.)(TRANSF LOCAL.FOO/T/W HOST.FOO (RET))

The following command line, issued at the host, performs a bit-for-bit transfer of the file HOST.FOO from the host computer to a file named LOCAL.FOO on your local computer. Note the placement of the /T option. The command requests logging and statistical information at the end of the transfer: (.)(TRANSF HOST.FOO/W LOCAL.FOO/T (RET))

The (SUM_BOOK) contains a complete description of the TRANSF utility for RT--11 host computers. You should also use the RT--11 on-line index facility, INDEX, to find the latest information about TRANSF. (Without TRANSF Installed on the Host)

When you cannot install TRANSF on the host computer, you can still transfer the contents of ASCII files between the local and host computers by using the VTCOM logging file and SEND. You use the logging file functionality to transfer ASCII files from the host to your local computer. You use SEND to transfer ASCII files from your local computer to the host. (Caution) The VTCOM logging file functionality and SEND command perform no error checking. You should verify the contents of any file transferred using this functionality; that file could contain errors.

Do not use this functionality to transfer critical information. (Transfers from the Host to the Local Computer)

You use the VTCOM logging file functionality to transfer an ASCII file between the host and your local computer. The following example illustrates the general procedure you can use. The example assumes you want to transfer the contents of a ASCII file named HOST.TXT from the host to a file named LOCAL.TXT on your local computer. (numbered) Establish connection with the host computer. At the host computer, type the following command (do not press (RETURN)): ($)( TYPE HOST.TXT) Press (CTRL/P) and open the logging file, LOCAL.TXT, on your local computer: (TT::VTCOM>)(OPENLOG (RET)) (TT::VTCOM> Log file?)(LOCAL.TXT (RET)) ((RET))

The last (RETURN) you press issues the command, TYPE HOST.TXT, on the host computer. That displays the contents of HOST.TXT on your terminal screen. Therefore, VTCOM logs the contents of HOST.TXT.

Let the contents of HOST.TXT scroll on your screen. When HOST.TXT has finished scrolling on your screen and you have been returned to the host monitor prompt, press (CTRL/P) and close the logging file: (TT::VTCOM>)(CLOSELOG (RET)) ((RET))

The last pressing of (RETURN) returns you to the host monitor prompt. You can now return to your local computer and edit the file, LOCAL.TXT, to remove any characters captured by the logging file that were not part of the file HOST.TXT.

If you want to abort the VTCOM logging file operation: (numbered) While the file you are typing is scrolling on the terminal screen, press the (CTRL/C) sequence, to abort this operation from the host. Press (CTRL/P). In response to the VTCOM command prompt, type CLOSELOG: (TT::VTCOM>)(CLOSELOG (RET)) Optionally delete the partially transferred file on your local computer. (From the Local to the Host Computer)

You use the VTCOM SEND facility to transfer an ASCII file from your local computer to the host. The VTCOM SEND facility performs no error checking on the file transfer.

By default, the VTCOM SEND facility transfers the contents of a local file to the host in SLOW mode. SLOW mode transfers the contents of a file very slowly.

VTCOM also supports FAST mode for the SEND facility. FAST mode transfers characters as quickly as possible. However, the host computer terminal service may not be able to correctly process characters in FAST mode. Symptoms of an overloaded terminal service are a beeping terminal bell and/or displayed error messages. If you attempt FAST mode and your terminal beeps and/or you receive error messages from the host, return to SLOW mode.

The following example illustrates the general procedure you can use to transfer an ASCII file from your local computer to the host by using the VTCOM SEND facility. The example procedure uses SLOW mode. The example assumes you want to transfer the contents of an ASCII file named LOCAL.TXT from your local computer to a file named HOST.TXT on the host. (numbered) Establish connection with the host computer. At a VMS or RT--11 host computer, issue the following command: ($)( COPY TT: HOST.TXT (RET))

At an RSX host computer, issue the following command: ($)( COPY TI: HOST.TXT (RET))

In either case, the host cursor rests on the next line, waiting for input. Press (CTRL/P) and respond in the following manner to the VTCOM prompts: (TT::VTCOM>)(SEND (RET)) (TT::VTCOM> Send file?)(LOCAL.TXT (RET))

You see the contents of LOCAL.TXT scroll slowly across your terminal screen. When the complete file has scrolled on your terminal screen, press (CTRL/Z) to close the file on the host computer.

If you want to abort the file send operation, you must abort it from your local computer. You cannot use the (CTRL/C) sequence to abort this operation from the host. Use the following procedure: (numbered) Press (CTRL/P). In response to the VTCOM command prompt, type RESET: (TT::VTCOM>)(RESET (RET)) Press (CTRL/Z), and optionally delete the partially transferred file on the host computer.