67 lines
4.3 KiB
HTML
67 lines
4.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="concept" />
|
|||
|
|
<meta name="DC.Title" content="How the server stores user-defined file systems" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiurzaiu158.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415714.pdf" />
|
|||
|
|
<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="rzaiu160" />
|
|||
|
|
<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>How the server stores user-defined file systems</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="rzaiu160"><a name="rzaiu160"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">How the server stores user-defined file systems</h1>
|
|||
|
|
<div><p>In a UDFS, as in the <span class="q">"root"</span> (/) and QOpenSys file systems, users can
|
|||
|
|
create directories, stream files, symbolic links, and local sockets.</p>
|
|||
|
|
<div class="p">A single block special file object (*BLKSF) represents a UDFS. When you
|
|||
|
|
create a UDFS, the server also creates an associated block special file. You
|
|||
|
|
can only access the block special file through the Integrated File System
|
|||
|
|
generic commands, application programming interface (API), and the QFileSvr.400
|
|||
|
|
interface. Block special file names must be of the form: <pre>/dev/QASPxx/udfs_name.udfs</pre>
|
|||
|
|
</div>
|
|||
|
|
<div class="p">Where <samp class="codeph">xx</samp> is the system or basic ASP number (1–32) where
|
|||
|
|
the user stores the UDFS and <samp class="codeph">udfs_name</samp> is the unique name
|
|||
|
|
of the UDFS. Note that the UDFS name must end in the <samp class="codeph">.udfs</samp> extension.
|
|||
|
|
If the UDFS is stored in an independent ASP, the block special file name will
|
|||
|
|
be of the form: <pre>/dev/device-description/udfs_name.udfs</pre>
|
|||
|
|
</div>
|
|||
|
|
<p>A UDFS exists only in two states: mounted and unmounted. When you mount
|
|||
|
|
a UDFS, you can access the objects within it. When you unmount a UDFS, you
|
|||
|
|
cannot access the objects within it.</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, you cannot access the original contents of that directory.
|
|||
|
|
Also, you can access the contents of the UDFS through that directory.
|
|||
|
|
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 mail, action, and outgoing. 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 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 you unmount the UDFS, the <samp class="codeph">/home/JON/payroll</samp> file
|
|||
|
|
is accessible again, and the three directories in the UDFS become inaccessible.</p>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiurzaiu158.htm">Save user-defined file systems</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|||
|
|
<div><a href="../books/sc415714.pdf" target="_blank">OS/400 Network File System Support</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|