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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Automatic File Translation<br />

The z/<strong>VM</strong> FTP server can be configured by the system administrator to<br />

automatically perform EBCDIC-ASCII file translation based on the value of a file<br />

extension, which is defined to be the last component of a file name — that is, the<br />

characters that follow the last period in a path name. For file extensions, up to<br />

eight characters are matched and mixed case is not respected.<br />

Automatic file translation, when enabled, is applicable to only the Image (TYPE I)<br />

file transfer type. Thus, if the transfer type is changed to other than Image — for<br />

example, ASCII — during a session for which automatic file translation is active,<br />

automatic translation ceases and files are transferred in accordance with the newly<br />

established transfer type. In such a case, automatic file translation can be reinstated<br />

by changing back to the Image transfer type.<br />

Automatic file translation is recommended when a web browser or graphical FTP<br />

client is used to interact with a z/<strong>VM</strong> FTP server, because these clients often<br />

default to using a transfer type of Image (or, binary) and do not offer a way for a<br />

different file transfer type to be specified.<br />

The associations between file extensions and file translation are configured by the<br />

z/<strong>VM</strong> system administrator, as is the initial automatic file translation setting for an<br />

FTP session. While file extension associations cannot be changed by an FTP client,<br />

whether automatic file translation is performed by the server can be controlled by<br />

using the AUTOTRANS operand of the SITE subcommand. For more information,<br />

see “SITE” on page 68.<br />

File List Formats<br />

After an FTP connection has been established with a z/<strong>VM</strong> foreign host, the FTP<br />

server can be instructed to provide DIR subcommand responses (file lists) inone<br />

of two different list formats:<br />

v<br />

v<br />

<strong>VM</strong>-format (<strong>VM</strong>), or<br />

Unix-format (UNIX), sometimes referred to as Unix long-list format.<br />

These formats are described in more detail in the following sections.<br />

<strong>VM</strong>-format Lists<br />

The <strong>VM</strong>-format list response provides file information in a format that — for the<br />

minidisk and Shared File System (SFS) directory file groups — closely resembles<br />

that produced by the CMS LISTFILE command. A sample <strong>VM</strong>-format list response<br />

follows:<br />

Command:<br />

dir<br />

>>>PORT 9,117,32,30,4,53<br />

200 Port request OK.<br />

>>>LIST<br />

125 List started OK<br />

ENDTRACE <strong>TCP</strong><strong>IP</strong> F 80 1 1 1999-07-28 12:24:01 TCM191<br />

LASTING GLOBALV V 43 10 1 1999-11-16 9:05:22 TCM191<br />

NOTRACE <strong>TCP</strong><strong>IP</strong> F 80 1 1 1999-12-16 13:39:21 TCM191<br />

OBEY EXEC V 72 153 2 1996-01-03 16:07:07 TCM191<br />

PACKMODL TESTFILE F 1024 468 117 1996-07-28 13:56:36 TCM191<br />

PROFILE EXEC V 30 10 1 1999-11-16 9:01:10 TCM191<br />

RECF80 TESTFILE F 80 5 1 2000-01-17 14:47:19 TCM191<br />

SETX XEDIT V 46 13 1 1999-11-04 9:13:53 TCM191<br />

<strong>TCP</strong><strong>IP</strong> DATA V 72 99 2 1999-11-18 17:24:05 TCM191<br />

<strong>TCP</strong>MNT2 NETLOG V 108 48 2 2000-01-17 14:49:09 TCM191<br />

<strong>TCP</strong>MNT2 SYNONYM F 80 10 1 1999-11-10 8:46:12 TCM191<br />

<strong>TCP</strong>SLVL EXEC V 37 23 1 1999-02-05 13:20:46 TCM191<br />

FTP Subcommands<br />

Chapter 2. Transferring Files Using FTP 35

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

Saved successfully!

Ooh no, something went wrong!