z/VM: TCP/IP User's Guide - z/VM - IBM

FTP Subcommands
►►
(1)
filename . filetype
yourid (2)
filepoolid: . . filename . filetype
userid .
▼ subdir
/
(3)
▼ subdir bfs_filename
/../VMBFS:filepoolid:filespace/ /
▼
subdir
(3)
bfs_filename
►◄
Notes:
1 Format for minidisk and reader files.
2 Format for SFS files.
3 Formats for BFS files.
To reference minidisk or reader files, the appropriate working directory must be
established on the foreign VM host. Fully-qualified SFS and BFS foreign files can
be referenced regardless of whether they reside in the current working directory on
the foreign host.
For more information about CMS file names and limitations, see the z/VM CMS
Command Reference. For details regarding BFS file-naming conventions, refer to the
z/VM: OpenExtensions User’s Guide.
File Name Pattern Matching
When subcommands are issued that affect multiple CMS files, such as MDELETE,
MGET, and MPUT, pattern matching can be used to affect the scope of the set of
files affected by these subcommands (as can be done with the CMS LISTFILE
command). Pattern matching is accomplished by specifying an asterisk (*) as a
portion of, or in place of, filename or filetype when a file name is specified for these
commands.
Pattern matching can also be used with the name operand that is used in DIR and
LS subcommands. In addition to the pattern matching just described for filename
and filetype (when name is specified using the format filename.filetype), the name
operand itself can be used for pattern matching. Pattern matching based on the
name operand is accomplished by specifying an asterisk (*) as a portion of, or in
place of, the name operand.
Notes:
1. When the foreign host working directory is a virtual reader, pattern matching
characters that are used as a portion of the filename, filetype or name operands
must be specified as a leading or trailing character. An asterisk (*) can still be
used in place of these operands.
2. Pattern matching cannot be used for BFS files and directories.
File Name Case Considerations
When FTP operations are performed between hosts that are based on differing file
system implementations, it may be necessary to account for differences that can
arise due to case sensitive file naming conventions.
Chapter 2. Transferring Files Using FTP 31