91 lines
5.3 KiB
HTML
91 lines
5.3 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 systems and naming conventions" />
|
||
|
<meta name="abstract" content="The File Transfer Protocol (FTP) server arranges the information units of a file system in a multiple-level tree-like structure." />
|
||
|
<meta name="description" content="The File Transfer Protocol (FTP) server arranges the information units of a file system in a multiple-level tree-like structure." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiqreference.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiqnamefmt.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../ifs/rzaaxkickoff.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../rzahg/rzahgffs.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiqquote.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaiqnamefmt.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="rzaiqftpconvn" />
|
||
|
<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 systems and naming conventions</title>
|
||
|
</head>
|
||
|
<body id="rzaiqftpconvn"><a name="rzaiqftpconvn"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">File systems and naming conventions</h1>
|
||
|
<div><p>The File Transfer Protocol (FTP) server arranges the information
|
||
|
units of a file system in a multiple-level tree-like structure.</p>
|
||
|
<div class="section"><p>The i5/OS™ file systems that you can use with
|
||
|
FTP vary depending on the release level of the operating system. File systems
|
||
|
on i5/OS can
|
||
|
use different terms for data and the hierarchical grouping of data.</p>
|
||
|
</div>
|
||
|
<div class="section"><h4 class="sectiontitle">Naming conventions</h4><p>Each i5/OS file system
|
||
|
has its own set of rules for naming files. The format you use to name any
|
||
|
file must adhere to the naming conventions of the file system in which it
|
||
|
resides. Formats and examples of file names for FTP-enabled i5/OS file systems
|
||
|
are described in the topic <a href="../ifs/rzaaxkickoff.htm">Integrated file system</a>. The server can provide
|
||
|
naming information for files on non-iSeries servers when you use the QUOTE
|
||
|
HELP subcommand.</p>
|
||
|
<p><strong>FTP server NAMEFMT</strong></p>
|
||
|
<p>When
|
||
|
an FTP server session is started, NAMEFMT is set to a value of 0. You can
|
||
|
change the NAMEFMT value by using the SITE subcommand.</p>
|
||
|
<p>The server automatically
|
||
|
switches from the default of NAMEFMT 0 to NAMEFMT 1 when the 'first' file
|
||
|
or pathname parameter received in a subcommand either:</p>
|
||
|
<ul><li>Starts with a slash (/) or a tilde (~) character</li>
|
||
|
</ul>
|
||
|
<p>or</p>
|
||
|
<ul><li>Is blank (except for the LIST and NLST subcommands)</li>
|
||
|
</ul>
|
||
|
<p>Any subsequent server subcommands with a file or path name parameter
|
||
|
will not affect the NAMEFMT value. In addition to changing the NAMEFMT, the
|
||
|
server reply for the subcommand will include a statement saying that the NAMEFMT
|
||
|
value has been changed.</p>
|
||
|
<p>For example, the server NAMEFMT value will be
|
||
|
changed to "1" if the first server subcommand with a file or path name is:</p>
|
||
|
<pre> CWD /DIR1/DIR2A</pre>
|
||
|
<p>The server reply will be:</p>
|
||
|
<pre> 250-NAMEFMT set to 1.
|
||
|
250 Current directory changed to /DIR1/DIR2A.</pre>
|
||
|
<div class="note"><span class="notetitle">Note:</span> This capability
|
||
|
enables the typical Web browser, which requires NAMEFMT 1, to interact with iSeries™ FTP
|
||
|
servers without issuing a SITE NAMEFMT 1 subcommand.</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqreference.htm" title="You can find information about server and client subcommands, File Transfer Protocol (FTP) exit programs, data transfer methods, and more.">File Transfer Protocol reference information</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="../ifs/rzaaxkickoff.htm">Integrated File System</a></div>
|
||
|
<div><a href="../rzahg/rzahgffs.htm">Files and file systems</a></div>
|
||
|
</div>
|
||
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
<div><a href="rzaiqnamefmt.htm">NAMEFMT (Select File Naming Format)</a></div>
|
||
|
<div><a href="rzaiqquote.htm">QUOTE (Send a Subcommand to an FTP Server)</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|