FTAM/9000 User's Guide

Chapter 3 47
Using Command-Line FTAM
Specifying File and Directory Names
The local host uses the login name betty to access the remote HP-UX
host named denver. You are prompted to supply betty's password. The
file name (memos/mymemo) accesses a file called mymemo in the memos
subdirectory of betty's home (default) directory. Notice that this example
file name uses normal HP-UX syntax; other vendors' responders require
the native syntax and conventions of the host.
Notes About Remote File and Directory Names
Note the following important points about remote file names:
• Directory names are legal only in fls and fcattr commands.
Directory names are not legal as source or destination file names.
• Wildcard characters are not legal. This applies to both source and
destination.
• For all FTAM commands, remote file names must be specified with
the native syntax, notation, and conventions for the remote host.
FTAM cannot translate or negotiate file names between different
hosts, so any name you provide has to be valid on the system that
uses it. This may require you to “escape” HP-UX metacharacters (like
“>”) if they appear in the remote file name. To “escape” a
metacharacter, precede it with a backslash, or enclose the whole file
(or directory) specification in quotation marks. Example:
“fairbanks:rush>gold” or fairbanks:rush\>gold
• All names are relative to the remote working directory, unless you
provide an absolute pathname for a file or directory (in whatever way
the remote system defines “absolute pathname”).
• The default remote directory for file transactions is determined by the
FTAM implementation on the remote host. HP FTAM/9000
responders set the default directory to be the home directory for the
user involved in the transaction. Other (non-HP-UX) FTAM
implementations are apt to use different default directories.