210 lines
12 KiB
HTML
210 lines
12 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="File names for client-transfer subcommands" />
|
||
|
|
<meta name="abstract" content="You can use default source and target file names for some subcommands; however, you must specify a file name for other subcommands." />
|
||
|
|
<meta name="description" content="You can use default source and target file names for some subcommands; however, you must specify a file name for other subcommands." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqcsubcs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqappend.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqget.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqput.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqput.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqappend.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqget.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqmput.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqmget.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqdebugt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqlcd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqcd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqdelete.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqmdelete.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqcsaq.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqcslarf.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaiqctsdfl" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>File names for client-transfer subcommands</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiqctsdfl"><a name="rzaiqctsdfl"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">File names for client-transfer subcommands</h1>
|
||
|
|
<div><p>You can use default source and target file names for some subcommands;
|
||
|
|
however, you must specify a file name for other subcommands.</p>
|
||
|
|
<div class="section"><p>The FTP client provides a default file name if the target file
|
||
|
|
name for the PUT, APPEND, and GET subcommands is omitted. Because you can
|
||
|
|
specify source file names for the MPUT and MGET subcommands, the FTP server
|
||
|
|
also generates target file names for MPUT and MGET. See the following Data
|
||
|
|
Transfer Subcommands table for the syntax of these subcommands. The table
|
||
|
|
column labeled <em>Target</em> is the parameter for which a default name is
|
||
|
|
provided.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e41">Subcommand</th>
|
||
|
|
<th valign="top" id="d0e43">Source</th>
|
||
|
|
<th valign="top" id="d0e45">Target</th>
|
||
|
|
<th valign="top" id="d0e47">Other</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e41 ">APPEND</td>
|
||
|
|
<td valign="top" headers="d0e43 ">local filename</td>
|
||
|
|
<td valign="top" headers="d0e45 ">[server filename]</td>
|
||
|
|
<td valign="top" headers="d0e47 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e41 ">PUT</td>
|
||
|
|
<td valign="top" headers="d0e43 ">local filename</td>
|
||
|
|
<td valign="top" headers="d0e45 ">[server filename]</td>
|
||
|
|
<td valign="top" headers="d0e47 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e41 ">GET</td>
|
||
|
|
<td valign="top" headers="d0e43 ">server filename</td>
|
||
|
|
<td valign="top" headers="d0e45 ">[local file name]</td>
|
||
|
|
<td valign="top" headers="d0e47 ">[(Replace]</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e41 ">MPUT</td>
|
||
|
|
<td valign="top" headers="d0e43 ">local filename</td>
|
||
|
|
<td valign="top" headers="d0e45 "> </td>
|
||
|
|
<td valign="top" headers="d0e47 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e41 ">MGET</td>
|
||
|
|
<td valign="top" headers="d0e43 ">server filename</td>
|
||
|
|
<td valign="top" headers="d0e45 "> </td>
|
||
|
|
<td valign="top" headers="d0e47 ">[(Replace]</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">PUT and APPEND subcommands</h4><p>For the PUT and APPEND
|
||
|
|
subcommands, the rules for forming default names are divided into two categories:</p>
|
||
|
|
<ul><li>iSeries™ server
|
||
|
|
case <ul><li>If the target file system is a library file system or a document library
|
||
|
|
system, the default name complies with the naming rules for these systems,
|
||
|
|
including their name format.</li>
|
||
|
|
<li>If the target file system is neither a library file system nor a document
|
||
|
|
file system it is one of two names: <ul><li>The default name is the name after the last slash in the source file name</li>
|
||
|
|
<li>The <em>same</em> as the source file name if there is no slash.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Non-iSeries server case <ul><li>If the source file is a library file system file, then the default name
|
||
|
|
consists of the <em>file name.member name</em>. If there is no member name,
|
||
|
|
the file name is the default name.</li>
|
||
|
|
<li>If the source file is a document library services file, the default name
|
||
|
|
is the file name and the extension.</li>
|
||
|
|
<li>If the source file is neither a library file system nor a document library
|
||
|
|
services file, the name after the last slash in the source name is the default
|
||
|
|
name. If there is no slash, the default name is the same as the source name.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>If the server is an iSeries server, then the server generates the default
|
||
|
|
name in these subcommands using the same rules as applied for the PUT subcommand.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">GET and MGET subcommand</h4><p>If the server is not an iSeries server,
|
||
|
|
it bases the default name for the GET and MGET subcommands on the part of
|
||
|
|
the source name that follows the last slash. If there is no slash, the entire
|
||
|
|
source name is the default name. Here are the rules for forming default names:</p>
|
||
|
|
<ul><li>If the client file system is the <em>library file system</em> (iSeries database),
|
||
|
|
these rules apply: <ul><li>If the remote file name contains a period (.), the characters preceding
|
||
|
|
the period are truncated to 10 characters to form the local file name. The
|
||
|
|
characters after the period are truncated to 10 characters to form the member
|
||
|
|
name.</li>
|
||
|
|
<li>If the remote file name does not contain a period, both file and member
|
||
|
|
names are set to the remote file name truncated to 10 characters to form the
|
||
|
|
local file name.</li>
|
||
|
|
<li>If the name format is 1, the server adds the appropriate extensions to
|
||
|
|
the file and member parts of the name.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>If the client file system is <em>document library services</em>, these rules
|
||
|
|
apply: <ul><li>If the remote name contains a period, the characters preceding the period
|
||
|
|
are truncated to 8 characters. The characters after the period are truncated
|
||
|
|
to 3 characters.</li>
|
||
|
|
<li>If the remote name does not contain a period, the name is truncated to
|
||
|
|
8 characters without an extension.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>For other file systems, the name after the last slash in the remote name
|
||
|
|
is the default name.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Notes:</span> <ol><li>Save files do not have members, so default names for save files do not
|
||
|
|
have a member part.</li>
|
||
|
|
<li>The server displays the default names when the DEBUG mode is on.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<p><strong>More details on syntax:</strong></p>
|
||
|
|
<p>FTP client syntax conventions</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Naming files for transfer</h4><p>The FTP client subcommands
|
||
|
|
that you use for transferring data can have a <span class="uicontrol">localfile</span> or
|
||
|
|
a <span class="uicontrol">remotefile</span> parameter or both. You can use these
|
||
|
|
parameters to name the data you want to transfer. The transfer subcommands
|
||
|
|
are:</p>
|
||
|
|
<ul class="simple"><li>APPEND localfile [remotefile]</li>
|
||
|
|
<li>DELETE remotefile</li>
|
||
|
|
<li>GET remotefile [localfile]</li>
|
||
|
|
<li>MDELETE remotefiles</li>
|
||
|
|
<li>MGET remotefiles</li>
|
||
|
|
<li>MPUT localfiles</li>
|
||
|
|
<li>PUT localfile [remotefile]</li>
|
||
|
|
</ul>
|
||
|
|
<p>The names for the localfile and remotefile parameters can be either
|
||
|
|
partially qualified or fully qualified. A partially-qualified name includes
|
||
|
|
the name of the data itself as well as one or more names in the hierarchical
|
||
|
|
sequence above the data. A fully-qualified name includes all names in the
|
||
|
|
hierarchical sequence above the data.</p>
|
||
|
|
<p>When the name is partially qualified,
|
||
|
|
the current working directory identifies the file to be processed. You can
|
||
|
|
set the working directory on the local client system with the LCD subcommand.
|
||
|
|
You can set the working directory on the remote server system with the CD
|
||
|
|
subcommand.</p>
|
||
|
|
<p>The format of the localfile name parameters must conform
|
||
|
|
to iSeries file
|
||
|
|
naming rules. The remotefile names must adhere to the file naming rules of
|
||
|
|
the remote system.</p>
|
||
|
|
<p><strong>More details on syntax:</strong></p>
|
||
|
|
<ul><li>Enclosing subcommand parameters: You can use either a single quotation
|
||
|
|
mark (') or quotation marks (") to enclose parameters.</li>
|
||
|
|
<li>FTP client syntax conventions: FTP client subcommands make use of these
|
||
|
|
syntax conventions.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqcsubcs.htm" title="The File Transfer Protocol (FTP) client subcommands described in this topic make use of syntax conventions:">File Transfer Protocol client syntax conventions</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzaiqcsaq.htm" title="You can use either a single quotation mark (') or quotation marks (") to enclose parameters from this topic.">Enclose subcommand parameters</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzaiqappend.htm">APPEND (Append a Local File Member to a Remote File)</a></div>
|
||
|
|
<div><a href="rzaiqget.htm">GET (Copy a File from a Remote System to the Local System)</a></div>
|
||
|
|
<div><a href="rzaiqput.htm">PUT (Copy a File Member from the Local System to a File on a Remote System)</a></div>
|
||
|
|
<div><a href="rzaiqmput.htm">MPUT (Send Multiple File Members from the Local System to a Remote System)</a></div>
|
||
|
|
<div><a href="rzaiqmget.htm">MGET (Copy Multiple Files from a Remote System to the Local System)</a></div>
|
||
|
|
<div><a href="rzaiqdebugt.htm">DEBUG (Change Client Time-Out Limit Values)</a></div>
|
||
|
|
<div><a href="rzaiqlcd.htm">LCD (Change Working Library or Directory on Local System)</a></div>
|
||
|
|
<div><a href="rzaiqcd.htm">CD (Change Working Directory or Library)</a></div>
|
||
|
|
<div><a href="rzaiqdelete.htm">DELETE (Delete a File on a Remote System)</a></div>
|
||
|
|
<div><a href="rzaiqmdelete.htm">MDELETE (Delete Multiple Files on a Remote System)</a></div>
|
||
|
|
<div><a href="rzaiqcslarf.htm" title="Use the localfile and remotefile parameters to transfer data.">Naming files for transfer</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|