73 lines
2.9 KiB
HTML
73 lines
2.9 KiB
HTML
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
|
||
|
|
<title>New File Systems</title>
|
||
|
|
<!-- 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. -->
|
||
|
|
<!-- Change History: -->
|
||
|
|
<!-- YYMMDD USERID Change description -->
|
||
|
|
<!--File Edited November 2001 -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
|
||
|
|
</head>
|
||
|
|
<body><!--End Header Records -->
|
||
|
|
<!--Java sync-link-->
|
||
|
|
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript">
|
||
|
|
</script>
|
||
|
|
|
||
|
|
<h2>New File Systems</h2>
|
||
|
|
|
||
|
|
<p>Two types of tools are necessary to use your own file system with the HFS
|
||
|
|
APIs. You must supply these tools:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Exit programs that do the work for the HFS APIs. You must provide these
|
||
|
|
exit programs. <strong>Exit programs</strong> enable application programs to
|
||
|
|
use the specific HFS APIs to work with files and directories in your file
|
||
|
|
system. The HFS Exit Program--Scenario that follows shows how an
|
||
|
|
application creates a directory in your file system using an exit program.</li>
|
||
|
|
|
||
|
|
<li>Programs that call the Register File System (QHFRGFS) and Deregister File
|
||
|
|
System (QHFDRGFS) APIs. Registration makes your file system and its exit
|
||
|
|
programs accessible to application programs using the HFS APIs. Deregistration
|
||
|
|
lets you remove a file system from use.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3><a name="HDRHEPSC">Scenario: HFS Exit Program</a></h3>
|
||
|
|
|
||
|
|
<p>Most exit programs correspond directly to APIs. For example, to allow
|
||
|
|
applications to create directories in your file system, you must write an exit
|
||
|
|
program that supplies the Create Directory function (CRTDR) for the Create
|
||
|
|
Directory (QHFCRTDR) API. When an application calls an HFS API, the system
|
||
|
|
routes the call to the appropriate exit program in the appropriate file system,
|
||
|
|
according to the API's function and the file system name specified in the API's
|
||
|
|
path-name parameter.</p>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> The abbreviation CRTDR in the following illustration
|
||
|
|
is the function name. See <a href="hfs3.htm">HFS Exit Programs</a> for more
|
||
|
|
information about function names.</p>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3><a name="Figure_3-1">Creating a Directory in Your File System</a></h3>
|
||
|
|
|
||
|
|
<center><img src="RBAFX504.gif" alt="HFS directory creation"></center>
|
||
|
|
|
||
|
|
<hr>
|
||
|
|
<center>
|
||
|
|
<table cellpadding="2" cellspacing="2">
|
||
|
|
<tr align="center">
|
||
|
|
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
|
||
|
|
"hfs1.htm">Hierarchical File System APIs</a> | <a href="aplist.htm">APIs by
|
||
|
|
category</a></td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
</center>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|