ibm-information-center/dist/eclipse/plugins/i5OS.ic.ifs_5.4.0.1/rzaaxudfspath.htm

77 lines
5.4 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="Path names in an integrated file system user-defined file system" />
<meta name="abstract" content="A block special file (*BLKSF) represents a user-defined file system (UDFS) when the entire UDFS and all of the objects within it need to be manipulated." />
<meta name="description" content="A block special file (*BLKSF) represents a user-defined file system (UDFS) when the entire UDFS and all of the objects within it need to be manipulated." />
<meta name="DC.Relation" scheme="URI" content="rzaaxudfsfs.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxunicode.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxtype2.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaaxpath.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaaxudfspath" />
<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>Path names in an integrated file system user-defined file system</title>
</head>
<body id="rzaaxudfspath"><a name="rzaaxudfspath"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Path names in an integrated file system user-defined file system</h1>
<div><p><span>A block special file (*BLKSF) represents
a user-defined file system (UDFS) when the entire UDFS and all of the objects
within it need to be manipulated.</span></p>
<div class="section"><div class="p"> If your UDFS resides on the system or on a basic user ASP, block
special file names must be of the form <pre>/dev/QASPXX/udfs_name.udfs</pre>
where <samp class="codeph">XX</samp>
is the ASP number where you store the UDFS, and <samp class="codeph">udfs_name</samp>
is the unique name of the UDFS within that ASP. Note that the UDFS name must
end with the <samp class="codeph">.udfs</samp> extension.</div>
</div>
<div class="section"><div class="p">If your UDFS resides on an independent ASP, block special file
names must be of the form <pre>/dev/asp_name/udfs_name.udfs</pre>
where <samp class="codeph">asp_name</samp> is
the name of independent ASP where you store the UDFS and <samp class="codeph">udfs_name</samp>
is the unique name of the UDFS within that independent ASP. Note that the
UDFS name must end with the <samp class="codeph">.udfs</samp> extension.</div>
</div>
<div class="section"><p>Path names for objects within a UDFS are relative to the directory
over which you mount a UDFS. For example, if you mount the UDFS <samp class="codeph">/dev/qasp01/wysocki.udfs</samp> over <samp class="codeph">/home/dennis</samp>,
then the path names for all objects within the UDFS will begin with <samp class="codeph">/home/dennis</samp>.</p>
</div>
<div class="section"><p>Additional path name rules:</p>
</div>
<div class="section"> <ul><li>Each component of the path name can be up to 255 characters long. The
full path name can be up to 16 MB long.</li>
<li>There is no limit to the depth of the directory hierarchy other than program
and server space limits.</li>
<li>The characters in names are converted to UCS2 Level 1 form (for *TYPE1
directories) and UTF-16 (for *TYPE2 directories) when the names are stored.</li>
</ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxudfsfs.htm" title="The user-defined file systems (UDFSs) reside on the auxiliary storage pool (ASP) or independent auxiliary storage pool (ASP) of your choice. You create and manage these file systems.">User-defined file systems (UDFSs)</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzaaxunicode.htm" title="When you use the root (/), QOpenSys, and user-defined file systems, you can take advantage of system support that ensures characters in object names remain the same.">Name continuity</a></div>
<div><a href="rzaaxtype2.htm" title="The &#34;root&#34; (/), QOpenSys, and user-defined file systems (UDFS) in the integrated file system support the *TYPE2 directory format. The *TYPE2 directory format is an enhancement of the original *TYPE1 directory format.">*TYPE2 directories</a></div>
<div><a href="rzaaxpath.htm" title="A path name (also called a pathname on some systems) tells the server how to locate an object.">Path name</a></div>
</div>
</div>
</body>
</html>