73 lines
5.4 KiB
HTML
73 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="concept" />
|
|
<meta name="DC.Title" content="Why use the integrated file system" />
|
|
<meta name="abstract" content="The integrated file system enhances the already extensive data management capabilities of i5/OS with additional capabilities to better support emerging and future forms of information processing, such as client/server, open systems, and multimedia." />
|
|
<meta name="description" content="The integrated file system enhances the already extensive data management capabilities of i5/OS with additional capabilities to better support emerging and future forms of information processing, such as client/server, open systems, and multimedia." />
|
|
<meta name="DC.subject" content="integrated file system, why use it?, stream file, benefit, file system, integrated file system interface, national language support, code page, character conversion" />
|
|
<meta name="keywords" content="integrated file system, why use it?, stream file, benefit, file system, integrated file system interface, national language support, code page, character conversion" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxoverview.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxfsknow.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="rzaaxwhyifs" />
|
|
<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>Why use the integrated file system</title>
|
|
</head>
|
|
<body id="rzaaxwhyifs"><a name="rzaaxwhyifs"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Why use the integrated file system</h1>
|
|
<div><p>The integrated file system enhances the already extensive data
|
|
management capabilities of <span class="keyword">i5/OS™</span> with
|
|
additional capabilities to better support emerging and future forms of information
|
|
processing, such as client/server, open systems, and multimedia.</p>
|
|
<p>You can use the integrated file system to do the following things:</p>
|
|
<ul><li>Provide fast access to <span class="keyword">i5/OS</span> data,
|
|
especially for applications such as iSeries™ Access that use the <span class="keyword">i5/OS</span> file server.</li>
|
|
<li>Allow more efficient handling of types of stream data, such as images,
|
|
audio, and video.</li>
|
|
<li>Provide a file system base and a directory base for
|
|
supporting open system standards based on the UNIX<sup>®</sup> operating system, such as Portable
|
|
Operating System Interface for Computer Environments (POSIX) and X/Open Portability
|
|
Guide (XPG). This file structure and this directory structure also provides
|
|
a familiar environment for users of PC operating systems, such as Disk Operating
|
|
System (DOS) and Windows<sup>®</sup> operating systems.</li>
|
|
<li>Allow file support with unique capabilities (such as record-oriented database
|
|
files, UNIX operating
|
|
system-based stream files, and file serving) to be handled as separate file
|
|
systems, while allowing them all to be managed through a common interface. <div class="fignone"><span class="figcap">Figure 1. A common interface to separate file systems</span><br /><img src="rv3n062.gif" alt="A common interface to separate file systems" /><br /></div>
|
|
</li>
|
|
<li>Allow PC users to take better advantage of their graphical user interface.
|
|
For example, Windows users can use the Windows graphical tools to operate on iSeries server
|
|
stream files and other objects in the same way they operate on files stored
|
|
on their PCs.</li>
|
|
<li>Provide continuity of object names and associated object information across
|
|
national languages. For example, this ensures that individual characters remain
|
|
the same when switching from the code page of one language to the code page
|
|
of another language.</li>
|
|
</ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxoverview.htm" title="Read about the integrated file system on your iSeries server and how it can be of use on your server.">Overview of the integrated file system</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><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>
|
|
</body>
|
|
</html> |