120 lines
4.1 KiB
HTML
120 lines
4.1 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>Enabling Your File System to HFS</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>Enabling Your File System to HFS</h2>
|
||
|
|
|
||
|
|
<p>To make your file system available for use with the HFS APIs, take these
|
||
|
|
steps:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li>Read <a href="hfs3d.htm">Standard HFS API and Exit Program Functions</a>
|
||
|
|
carefully. It describes which functions the HFS APIs perform for you and which
|
||
|
|
functions your file system's exit programs must perform.<br>
|
||
|
|
<br>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li>Define your own file and directory objects. These objects can be any of the
|
||
|
|
following:<br>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>i5/OS<SUP>(TM)</SUP> objects, such as user spaces and user indexes</li>
|
||
|
|
|
||
|
|
<li>Objects on external devices attached to your iSeries<SUP>(TM)</SUP> server</li>
|
||
|
|
|
||
|
|
<li>Objects on other systems that are attached to your iSeries server by
|
||
|
|
communications lines</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>Your file system controls the structure, format, and location of the file
|
||
|
|
and directory objects it defines. It also controls security and authority for
|
||
|
|
those objects.</p>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li>Create these programs:<br>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>A program or command to call the Register File System (QHFRGFS) API, which
|
||
|
|
enrolls the file system for use with the HFS APIs.</li>
|
||
|
|
|
||
|
|
<li>A Start Job Session exit program, which is called the first time a job
|
||
|
|
tries to use the file system. See <a href="xstjbssn.htm">Start Job Session Exit
|
||
|
|
Program</a> for details.</li>
|
||
|
|
|
||
|
|
<li>An End Job Session exit program, which is called at job end to perform job
|
||
|
|
cleanup. See <a href="xndjbssn.htm">End Job Session Exit Program</a> for
|
||
|
|
details.</li>
|
||
|
|
|
||
|
|
<li>An exit program for every HFS API function that you want your file system
|
||
|
|
to support. For a list of exit programs you can supply, see the list of
|
||
|
|
qualified exit program names parameter in the <a href="qhfrgfs.htm">
|
||
|
|
Register File System (QHFRGFS) API</a>. If your file system is written in a
|
||
|
|
high-level language that supports a variable number of input parameters, you
|
||
|
|
can specify the same exit program for more than one function.
|
||
|
|
|
||
|
|
<p>Your file system does not need to support every function. However, if you
|
||
|
|
supply an Open Stream File or Open Directory function to support the QHFOPNSF
|
||
|
|
or QHFOPNDR API, you must supply the corresponding close function.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li>Register your file system with HFS, specifying the exit programs you want
|
||
|
|
to make available. See <a href="qhfrgfs.htm">Register File System
|
||
|
|
(QHFRGFS) API</a> for complete instructions.<br>
|
||
|
|
<br>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li>Give the file system's users authority to the <a href="xstjbssn.htm">Start
|
||
|
|
Job Session Exit Program</a>. Authority to this program gives users authority
|
||
|
|
to the file system as a whole.<br>
|
||
|
|
<br>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li>Give the file system's users authority to the HFS APIs that you support
|
||
|
|
with exit programs and that you want to make public. A user needs *USE
|
||
|
|
authority to an API to call the API from a program.<br>
|
||
|
|
<br>
|
||
|
|
</li>
|
||
|
|
|
||
|
|
<li>Provide the file system's users with complete documentation, so they know
|
||
|
|
which HFS APIs are supported, and whether any of the HFS APIs work differently
|
||
|
|
from the way they are described in this information.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<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>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|