191 lines
13 KiB
HTML
191 lines
13 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="User-defined file systems (UDFSs)" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="file system, User-Defined file system, characteristics and limitations, User-Defined file system, characteristics and limitations" />
|
||
|
|
<meta name="keywords" content="file system, User-Defined file system, characteristics and limitations, User-Defined file system, characteristics and limitations" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxfsknow.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfscase.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfspath.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfslink.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfsifscom.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfsapi.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfsgraphic.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxcreateudfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxdeludfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxdisudfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxmountudfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxunudfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxsaveudfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfsjournal.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfsiasp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxlinkifs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtudfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxstmfile.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="rzaaxudfsfs" />
|
||
|
|
<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>User-defined file systems (UDFSs)</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaaxudfsfs"><a name="rzaaxudfsfs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">User-defined file systems (UDFSs)</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"><p>In addition, they:</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="p"> <ul><li>Provide a hierarchical directory structure similar to PC operating systems
|
||
|
|
such as DOS and OS/2<sup>®</sup></li>
|
||
|
|
<li>Are optimized for stream file input and output</li>
|
||
|
|
<li>Support multiple hard links and symbolic links</li>
|
||
|
|
<li>Support local sockets</li>
|
||
|
|
<li>Support threadsafe APIs</li>
|
||
|
|
<li>Support *FIFO objects</li>
|
||
|
|
<li>Support the journaling of object changes</li>
|
||
|
|
<li>Support the scanning of objects using the integrated file system scan-related
|
||
|
|
exit points</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>You can create multiple UDFSs by giving each a unique name. You can specify
|
||
|
|
other attributes for a UDFS during its creation, including:</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="p"> <ul><li>An ASP number or independent ASP name where the objects that are located
|
||
|
|
in the UDFS are stored.</li>
|
||
|
|
<li>The case-sensitivity characteristics of the object names that are located
|
||
|
|
within a UDFS. <p>The case-sensitivity of a UDFS determines whether uppercase
|
||
|
|
and lowercase characters will match when searching for object names within
|
||
|
|
the UDFS.</p>
|
||
|
|
</li>
|
||
|
|
<li>The create object scanning attribute which defines what the scan attribute
|
||
|
|
should be for objects created in a UDFS. </li>
|
||
|
|
<li>The restrict rename and unlink attribute.</li>
|
||
|
|
<li>The auditing value for a UDFS.</li>
|
||
|
|
<li>The different stream file formats, *TYPE1 and *TYPE2.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">User-defined file system concepts</h4><p>In a user-defined
|
||
|
|
file system (UDFS), as in the <span class="q">"root"</span> (/) and QOpenSys file systems, you
|
||
|
|
can create directories, stream files, symbolic links, local sockets, and *FIFO
|
||
|
|
objects.</p>
|
||
|
|
<p>A single block special file object (*BLKSF) represents a UDFS.
|
||
|
|
As you create UDFSs, you also automatically create block special files. The
|
||
|
|
block special file is only accessible to the user through the integrated file
|
||
|
|
system generic commands, APIs, and the QFileSvr.400 interface.</p>
|
||
|
|
<p>A UDFS
|
||
|
|
exists only in two states: <strong>mounted</strong> and <strong>unmounted.</strong> When you mount
|
||
|
|
a UDFS, the objects within it are accessible. When you unmount a UDFS, the
|
||
|
|
objects within it become inaccessible.</p>
|
||
|
|
<p>In order to access the objects
|
||
|
|
within a UDFS, you must mount the UDFS on a directory (for example, <samp class="codeph">/home/JON</samp>).
|
||
|
|
When you mount a UDFS on a directory, the original contents of that directory,
|
||
|
|
including objects and subdirectories, become inaccessible. When you mount
|
||
|
|
a UDFS, the contents of the UDFS become accessible through the directory path
|
||
|
|
that you mount the UDFS over. For example, the <samp class="codeph">/home/JON</samp> directory
|
||
|
|
contains a file <samp class="codeph">/home/JON/payroll</samp>. A UDFS contains three
|
||
|
|
directories <samp class="codeph">mail, action,</samp> and <samp class="codeph">outgoing</samp>.
|
||
|
|
After mounting the UDFS on <samp class="codeph">/home/JON</samp>, the <samp class="codeph">/home/JON/payroll</samp> file
|
||
|
|
is inaccessible, and the three UDFS directories become accessible as <samp class="codeph">/home/JON/mail</samp>, <samp class="codeph">/home/JON/action</samp>,
|
||
|
|
and <samp class="codeph">/home/JON/outgoing</samp>. After unmounting the UDFS, the <samp class="codeph">/home/JON/payroll</samp> file
|
||
|
|
is accessible again, and the three directories in the UDFS become inaccessible. <span>An initial program load (IPL) of the system unmounts
|
||
|
|
all UDFSs. Therefore, the UDFSs need to be remounted after any IPL.</span></p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> A
|
||
|
|
UDFS on an independent ASP cannot be mounted over.</div>
|
||
|
|
<p>To learn more
|
||
|
|
about mounting file systems, see <a href="../books/sc415714.pdf" target="_blank">OS/400<sup>®</sup> Network File System Support</a> <img src="wbpdf.gif" alt="Link to PDF" />.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Use user-defined file system through the integrated file system
|
||
|
|
interface</h4><p>A user-defined file system (UDFS) can be accessed through
|
||
|
|
the integrated file system interface using either the <span class="keyword">i5/OS™</span> file
|
||
|
|
server or the integrated file system commands, user displays, and APIs.</p>
|
||
|
|
<p>In
|
||
|
|
using the integrated file system interface, you should be aware of the following
|
||
|
|
considerations and limitations.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfscase.htm">Case-sensitivity in an integrated file system user-defined file system</a></strong><br />
|
||
|
|
<span>You can specify whether object names in
|
||
|
|
the user-defined file system (UDFS) will be case-sensitive or case-insensitive
|
||
|
|
when you create it.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfspath.htm">Path names in an integrated file system user-defined file system</a></strong><br />
|
||
|
|
<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></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfslink.htm">Links in an integrated file system user-defined file system</a></strong><br />
|
||
|
|
<span>A user-defined file system (UDFS) allows
|
||
|
|
multiple hard links to the same object and fully supports symbolic links.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfsifscom.htm">Use integrated file system commands in a user-defined file system</a></strong><br />
|
||
|
|
<span>All of the commands that are listed
|
||
|
|
in Access using CL commands topic and the displays that are described in Access
|
||
|
|
using menus and displays topic can operate on a user-defined file system.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfsapi.htm">Use integrated file system APIs in a user-defined file system</a></strong><br />
|
||
|
|
All of the APIs that are listed in Perform operations using APIs topic can operate on a user-defined file system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfsgraphic.htm">Graphical user interface for a user-defined file system</a></strong><br />
|
||
|
|
<span class="keyword">iSeries™</span> Navigator,
|
||
|
|
a graphical user interface on your PC, provides for easy and convenient access
|
||
|
|
to user-defined file systems (UDFSs).</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxcreateudfs.htm">Create an integrated file system user-defined file system</a></strong><br />
|
||
|
|
The <span class="cmdname">Create User-Defined File System (CRTUDFS)</span> command
|
||
|
|
creates a file system that can be made visible through the integrated file
|
||
|
|
system namespace, APIs, and CL commands.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxdeludfs.htm">Delete an integrated file system user-defined file system</a></strong><br />
|
||
|
|
<span>The <span class="cmdname">Delete User-Defined File
|
||
|
|
System (DLTUDFS)</span> command deletes an existing, unmounted user-defined
|
||
|
|
file system (UDFS), and all the objects within it.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxdisudfs.htm">Display an integrated file system user-defined file system</a></strong><br />
|
||
|
|
<span>The <span class="cmdname">Display User-Defined File
|
||
|
|
System (DSPUDFS)</span> command presents the attributes of an existing
|
||
|
|
user-defined file system (UDFS), whether mounted or unmounted.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxmountudfs.htm">Mount an integrated file system user-defined file system</a></strong><br />
|
||
|
|
The <span class="cmdname">Add Mounted File System (ADDMFS)</span> and <span class="cmdname">MOUNT</span> commands
|
||
|
|
make the objects in a file system accessible to the integrated file system
|
||
|
|
namespace.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxunudfs.htm">Unmount an integrated file system user-defined file system</a></strong><br />
|
||
|
|
<span>The unmount command makes the contents
|
||
|
|
of a user-defined file system (UDFS) inaccessible to the integrated file system
|
||
|
|
interfaces.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxsaveudfs.htm">Save and restore an integrated file system user-defined file system</a></strong><br />
|
||
|
|
<span>You can save and restore all user-defined
|
||
|
|
file system (UDFS) objects, as well as their associated authorities.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfsjournal.htm">Journal object changes in a user-defined file system</a></strong><br />
|
||
|
|
<span>Objects in user-defined file systems (UDFSs)
|
||
|
|
can be journaled. This function enables you to recover the changes to an object
|
||
|
|
that have occurred since the object was last saved.</span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfsiasp.htm">User-defined file system and Independent Auxiliary Storage Pools (ASP)</a></strong><br />
|
||
|
|
When you vary on an independent ASP, several changes occur within the "root" (/) file system.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxfsknow.htm" title="A file system provides you the support to access specific segments of storage that are organized as logical units. These logical units on your server are files, directories, libraries, and objects.">Work with file systems</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaaxlinkifs.htm" title="A link is a named connection between a directory and an object. A user or a program can tell the server where to find an object by specifying the name of a link to the object. A link can be used as a path name or as part of a path name.">Link</a></div>
|
||
|
|
<div><a href="rzaaxstmfile.htm" title="A stream file is a randomly accessible sequence of bytes, with no further structure imposed by the system.">Stream file</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../cl/crtudfs.htm">Create UDFS (CRTUDFS) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|