HP ARPA File Transfer Protocol User's Guide (36957-90159)

Appendix A 81
MPE/iX and POSIX Differences
FTP Default Name Space
ftp> dir ./bytestrm
200 PORT command successful.
150 Opening ASCII mode data connection for /bin/ls.
-rw-r--r-- 1 jph network 35 Jun 20 16:19 ./bytestrm
226 Transfer complete.
66 bytes received in 0.18 seconds (0.37 Kbytes/sec)
FTP Default Name Space
FTP default name space is “almost always” MPE name space when specifying files to be
transferred with FTP commands (PUT or GET as examples). The only exception to this is the
FTP MKDIR and RMDIR commands which only operate with POSIX directories; thus, if you
did not specify the (./) POSIX prefix, FTP/iX specifies it for you.
For example, assume the POSIX current working directory “cwd” is: /SYS/WORK
Transferring Files
File names are taken as they are presented, as opposed to the directory commands
described in previous sections (directory commands which preface (./) to the file name).
Directory commands are always dealing with POSIX files, so prefacing a (./) is helpful to
the user. When transferring files, files prefaced with a (.) or (/) will reference a file in the
POSIX name-space as opposed to the MPE/iX name-space.
NOTE If the path specified for the source file does not exist on the target system, the
target file must be specified in the FTP/iX file transfer command. If the target
file is not specified, FTP/iX will attempt to create the file with the path
specified. If the target file is to be copied to the current working directory,
FTP command Result of FTP command
dir /SYS/PUB/CATALOG Display existing file (MPE space)
put
put
put
testdata
testdata ./testdata
testdata
/SYS/WORK/testdata
/SYS/WORK/TESTDATA (MPE space)
/SYS/WORK/testdata (posix space)
/SYS/WORK/testdata (posix space)
put
put
testdata longfilename
testdata ./longfilename
{failed – invalid MPE space name}
/SYS/WORK/longfilename (posix)
put
put
testdata name_name
testdata ./name_name
{failed – invalid MPE space name}
/SYS/WORK/name_name (posix space)