Download Autolog User`s Guide, 3rd ed., 9/02 (773 Kbytes)

46
Autolog User’s Guide
Slave program. Slave is supported by UNIX and AIX, DOS/Windows,
and AMOS computers; you may provide remote systems with which you
transfer files with a copy of the Slave utility so that you can use Autolog’ s
receive and transmit commands to easily exchange files with those
system. Instructions for installing Slave on remote systems are found in
the Autolog Installation and Platform Guide.
SMT protocol supports error detection and correction, data
compression, and buffering, making it one of the fastest and most reliable
file transfer protocols. It is also frequently the easiest to use, since
typically no advance preparation of the remote system is necessary before
beginning a file transfer, once the Slave program has been installed. (On
remote DOS and Windows systems, the Slave program must already be
running before you call in.)
Uploading Files with transmit
If the remote system has a copy of Slave, you can send it a copy of a file
on your system with the transmit command. Enter the command
transmit file(s)
where file(s) is the specification(s) of the file(s) you wish to send. The file
specification may be a single file, may contain wildcard symbols to send a
group of files, or may consist of a list of files (with or without wildcard
symbols). For example,
transmit myfile.lit
transmit my*.exe
transmit new* old* myfile.txt
are all acceptable transmit commands.
If no account or directory is indicated, Autolog will look for files only
in the current local directory. You may indicate a different directory in the
file specification, according to the conventions honored by your operating
system.
)
transmit sys:*.lit (AMOS)
transmit *.lit[1,4] (AMOS)
transmit usr/bin/myfile (UNIX or AIX)
transmit ../[a-c]* (UNIX or AIX)
transmit c:\usr\myfile.exe (DOS/Windows)
transmit ..\my* (DOS/Windows)
If you give only one file specification to be used for both the local
and remote systems, and that specification includes a path or
directory as in the preceding examples, the same path or directory
will be used on the remote system as well. This means the remote
system must also have the same path or directory in which to place
the files, or your file transfer will fail. However, Ashell users can