148 lines
12 KiB
HTML
148 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="concept" />
|
|
<meta name="DC.Title" content="Work with file systems" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.subject" content="file system, what is it?, interface, integrated file system interface, file server, i5/OS file server, PC file server, file server I/O processor" />
|
|
<meta name="keywords" content="file system, what is it?, interface, integrated file system interface, file server, i5/OS file server, PC file server, file server I/O processor" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxkickoff.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxfscmp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrootfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxopenfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudfsfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxlibfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxiaspfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxdocfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxoptfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqnetw.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxqntcfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrfsfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxnfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxwhatifs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxifsdsp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxifscmd.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxcmdpath.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxprogapi.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxmovingobjects.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415310.pdf" />
|
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415714.pdf" />
|
|
<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="rzaaxfsknow" />
|
|
<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>Work with file systems</title>
|
|
</head>
|
|
<body id="rzaaxfsknow"><a name="rzaaxfsknow"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Work with file systems</h1>
|
|
<div><p>A <dfn class="term">file system</dfn> 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.</p>
|
|
<p>Each file system has a set of logical structures and rules for interacting
|
|
with information in storage. These structures and rules may be different
|
|
from one file system to another. In fact, from the perspective of structures
|
|
and rules, the <span class="keyword">i5/OS™</span> support
|
|
for accessing database files and various other object types through libraries
|
|
can be thought of as a file system. Similarly, the <span class="keyword">i5/OS</span> support
|
|
for accessing documents (which are really stream files) through the folders
|
|
structure might be thought of as a separate file system.</p>
|
|
<p>The integrated file system treats the library support and folders support
|
|
as separate file systems. Other types of file management support that have
|
|
differing capabilities are also treated as separate file systems.</p>
|
|
<p>You can interact with any of the file systems through a common interface.
|
|
This interface is optimized for the input and output of stream data, in contrast
|
|
to the record input and output that is provided through the data management
|
|
interfaces. The provided commands, menus and displays, and application program
|
|
interfaces (APIs) allow interaction with the file systems through this common
|
|
interface.</p>
|
|
<div class="fignone"><span class="figcap">Figure 1. File systems, file servers, and the integrated file system interface</span><br /><img src="rv3n721.gif" alt="File systems, file servers, and the integrated file system interface" /><br /></div>
|
|
<div class="section"><h4 class="sectiontitle">Use Network File Systems through the
|
|
integrated file system interface</h4><p>The Network File System (NFS) is
|
|
accessible through the integrated file system interface. Be aware of these
|
|
considerations and limitations.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzaaxfscmp.htm">File system comparison</a></strong><br />
|
|
These tables summarize the features and limitations of each file system.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxrootfs.htm">"root" (/) file system</a></strong><br />
|
|
The <span class="q">"root"</span> (/) file system takes full advantage of the stream
|
|
file support and hierarchical directory structure of the integrated file system.
|
|
It has the characteristics of the DOS and OS/2<sup>®</sup> file systems.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxopenfs.htm">Open systems file system (QOpenSys)</a></strong><br />
|
|
<span>The QOpenSys file system is compatible
|
|
with open system standards based on UNIX<sup>®</sup>, such as POSIX and X/Open Portability
|
|
Guide (XPG). Like the "root" (/) file system, this file system takes advantage
|
|
of the stream file and directory support that is provided by the integrated
|
|
file system.</span></li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxudfsfs.htm">User-defined file systems (UDFSs)</a></strong><br />
|
|
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.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxlibfs.htm">Library file system (QSYS.LIB)</a></strong><br />
|
|
The QSYS.LIB file system supports the <span class="keyword">iSeries™ server</span> library
|
|
structure. </li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxiaspfs.htm">Independent ASP QSYS.LIB</a></strong><br />
|
|
The independent ASP QSYS.LIB file system supports the <span class="keyword">iSeries™ server</span> library structure in independent
|
|
auxiliary storage pools (ASPs) you create and define. This file system provides
|
|
access to database files and all of the other <span class="keyword">iSeries™ server</span> object
|
|
types that the library support manages in the independent ASPs.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxdocfs.htm">Document library services file system (QDLS)</a></strong><br />
|
|
The QDLS file system supports the folders structure. It provides access to documents and folders.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxoptfs.htm">Optical file system (QOPT)</a></strong><br />
|
|
The QOPT file system provides access to stream data that is stored on optical media.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxqnetw.htm">NetWare file system (QNetWare)</a></strong><br />
|
|
<span>The QNetWare file system provides access
|
|
to data on stand-alone PC servers that are running Novell NetWare 5.1 or 6.0.</span></li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxqntcfs.htm">iSeries NetClient file system (QNTC)</a></strong><br />
|
|
<span><img src="./delta.gif" alt="Start of change" />The QNTC file system provides access to
|
|
data and objects that are stored on an <span class="keyword">Integrated xSeries<sup>®</sup> Server for iSeries™</span> running Windows
|
|
NT<sup>®</sup> 4.0 Server or later, or Linux<sup>®</sup>. The QNTC file system also provides
|
|
access to data and objects that are stored on remote servers running Windows
|
|
NT<sup>®</sup> 4.0 or later, Linux<sup>®</sup> Samba 3.0 or later, or supported versions of iSeries™ NetServer™.<img src="./deltaend.gif" alt="End of change" /></span></li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxrfsfs.htm">i5/OS file server file system (QFileSvr.400)</a></strong><br />
|
|
<span>The QFileSvr.400 file system provides
|
|
transparent access to other file systems that reside on remote iSeries™ servers.
|
|
It is accessed through a hierarchical directory structure.</span></li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxnfs.htm">Network File System (NFS)</a></strong><br />
|
|
<span>The Network File System (NFS) provides
|
|
the user with access to data and objects that are stored on a remote NFS server.</span></li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxkickoff.htm" title="The integrated file system is a part of i5/OS that lets you support stream input/output and storage management similar to personal computer and UNIX operating systems, while providing you with an integrating structure over all information stored in the server.">Integrated file system</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaaxwhatifs.htm" title="The integrated file system is a part of i5/OS that supports stream input/output and storage management similar to personal computer and UNIX operating systems, while providing an integrating structure over all information stored in your server.">What the integrated file system is</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzaaxifsdsp.htm" title="You can perform operations on files and other objects in the integrated file system by using a set of menus and displays provided by your server.">Access using menus and displays</a></div>
|
|
<div><a href="rzaaxmovingobjects.htm" title="Each file system has its own unique characteristics. However, moving objects to a different file system might mean losing the advantages of the file system in which the objects are currently stored. You might want to move objects from one file system to another to take advantage of those characteristics.">Move files or folders to another file system</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rzaaxifscmd.htm" title="All of the operations that you can do through the integrated file system menus and displays can be done by entering control language (CL) commands. These commands can operate on files and other objects in any file system that are accessible through the integrated file system interface.">Access using CL commands</a></div>
|
|
<div><a href="rzaaxcmdpath.htm" title="When using an integrated file system command or display to operate on an object, you identify the object by supplying its path name.">Path name rules for CL commands and displays</a></div>
|
|
<div><a href="rzaaxprogapi.htm" title="Many of the application program interfaces (APIs) that perform operations on integrated file system objects are in the form of C language functions.">Perform operations using APIs</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../books/sc415310.pdf" target="_blank">Optical support</a></div>
|
|
<div><a href="../books/sc415714.pdf" target="_blank">Network file system support</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |