27.11.2014 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

FTP Subcommands<br />

If quotes are encountered that enclose a subcommand string which does not<br />

contain embedded blanks, the z/<strong>VM</strong> FTP client assumes the supplied quotes are<br />

inherent to this string. Thus, the delimiting quotes are retained, and are passed on<br />

to the FTP server on the foreign host.<br />

Fully-Qualified Pathnames<br />

For certain FTP subcommands, the z/<strong>VM</strong> FTP server allows a fully-qualified<br />

pathname.<br />

For example, assume the SFS directory FPSERV1:TSTUSER.TESTCASES is the<br />

working directory, but that information about all TEST007 files that reside in the<br />

FPSERV1:TSTUSER.TESTDATA directory needs to be obtained at a given time. This<br />

information can be obtained using the DIR command that follows:<br />

dir fpserv1:tstuser.testdata.test007.*<br />

If these files reside on the NOTSECUR 191 minidisk (for which a read password of<br />

ALL is in effect), this information would be retrieved using this command:<br />

dir notsecur.191/test007.*<br />

A fully-qualified pathname can be specified for these FTP subcommands:<br />

v APPEND (APPE)<br />

v DELETE (DELE)<br />

v DIR (LIST)<br />

v LS (NLST)<br />

v GET, MGET (RETR)<br />

v SIZE (SIZE)<br />

v PUT, MPUT (STOR)<br />

v PUT, MPUT with SUNIQUE active (STOU)<br />

Note: When fully-qualified path names are used with FTP subcommands, the FTP<br />

server temporarily acquires the appropriate z/<strong>VM</strong> file system resource<br />

necessary to satisfy a request. This action by the FTP server does not alter<br />

the working directory that has been established through use of either the<br />

CD or CWD commands.<br />

Storage Space Requirements for Transferred Files<br />

The information that follows must be considered when files are stored on a z/<strong>VM</strong><br />

host, especially when minidisk or SFS storage space is constrained, or when<br />

attempts are made to minimize the use of such space.<br />

As part of necessary overhead required by the FTP server and by CMS for<br />

performing file system management, a number of storage blocks must be reserved<br />

and used for other than data storage purposes. For instance, some blocks are used<br />

as control blocks to maintatin the minidisk file directory (for which additional<br />

block space may be required as new files are created), while others are used as<br />

pointer blocks to manage file structure.<br />

However, these various reserved blocks are not reflected in the output returned for<br />

the CMS QUERY DISK or QUERY LIMITS commands. This means the results<br />

obtained from these commands must be used only as an approximation of storage<br />

block usage and availability when determining whether a file can be stored on a<br />

z/<strong>VM</strong> host.<br />

Chapter 2. Transferring Files Using FTP 33

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!