88 lines
5.8 KiB
HTML
88 lines
5.8 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="Programming interfaces (HPOFS)" />
|
||
|
|
<meta name="abstract" content="You can create or read files on HPOFS media by using either the Hierarchical File System (HFS) application programming interface (API) or the integrated file system application programming interface (API)." />
|
||
|
|
<meta name="description" content="You can create or read files on HPOFS media by using either the Hierarchical File System (HFS) application programming interface (API) or the integrated file system application programming interface (API)." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4highperfofs.htm" />
|
||
|
|
<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="rzam4hpofsproginter" />
|
||
|
|
<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>Programming interfaces (HPOFS)</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzam4hpofsproginter"><a name="rzam4hpofsproginter"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Programming interfaces (HPOFS)</h1>
|
||
|
|
<div><p>You can create or read files on HPOFS media by using either the
|
||
|
|
Hierarchical File System (HFS) application programming interface (API) or
|
||
|
|
the integrated file system application programming interface (API).</p>
|
||
|
|
<p> The following are items specific to the i5/OS™ implementation of the HPOFS media
|
||
|
|
format that application developers need to know.</p>
|
||
|
|
<dl><dt class="dlterm">National Language Support</dt>
|
||
|
|
<dd>The integrated file system interfaces assume that the coded character
|
||
|
|
set identifier (CCSID) represents the path in effect for the job. The system
|
||
|
|
then converts the path from the job CCSID to an internally used CCSID. The
|
||
|
|
HFS interface makes no assumption about the CCSID of the path; therefore,
|
||
|
|
the system performs no character set conversion on the path. This could produce
|
||
|
|
undesirable side effects if an application used the two API sets interchangeably
|
||
|
|
or if the application changed from using one API set to the other.</dd>
|
||
|
|
<dd class="ddexpand">A program should not create files through HFS and then try to read them
|
||
|
|
by using the integrated file system APIs. Depending on the characters that
|
||
|
|
are used in the path name, this could result in a <tt class="msgph">File not found</tt> error.
|
||
|
|
This type of problem can be avoided if the application uses only invariant
|
||
|
|
characters (for example A-Z 0-9 + = % & ( ) , _ . : ;) for path names.
|
||
|
|
Invariant characters are graphic characters that map to the same code point
|
||
|
|
in all character sets.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Held optical files</dt>
|
||
|
|
<dd>When the system writes an optical file that it cannot close normally,
|
||
|
|
the system may create a held optical file. The held file exists on i5/OS internal
|
||
|
|
disk storage and contains the data written to the file. You can then save
|
||
|
|
or release the held file through an API or command interface. The system creates
|
||
|
|
held files only when files fail to archive on HPOFS media.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Synchronous writes</dt>
|
||
|
|
<dd>You can open files on HPOFS through HFS by specifying that all write operations
|
||
|
|
be synchronous. When specified, write operations will be synchronous to i5/OS internal
|
||
|
|
disk storage, not to the optical media. In the event of a power failure the
|
||
|
|
data is recoverable from a held optical file. </dd>
|
||
|
|
<dd class="ddexpand">Similarly for the HFS <span class="apiname">Force Buffered Data</span> API and the <span class="apiname">integrated
|
||
|
|
file system fsync()</span> API, data will be forced to i5/OS internal
|
||
|
|
disk storage, not to optical. Again, in the event of a power failure, the
|
||
|
|
data is recoverable from a held optical file.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">File sharing</dt>
|
||
|
|
<dd>Multiple jobs or threads can share files. The system fully recognizes
|
||
|
|
files that share modes as specified on the open request. For example, assume
|
||
|
|
that a job opens a file that specifies it to share only with readers. This
|
||
|
|
means that you can perform other opens only as long as the access requested
|
||
|
|
remains read only.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Extended file attributes</dt>
|
||
|
|
<dd>The system supports extended file attributes for files on HPOFS media.
|
||
|
|
Extended attributes can be written to files using the HFS Change Directory
|
||
|
|
Entry Attributes API as well as through some integrated file system interfaces.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4highperfofs.htm" title="High performance optical file system (HPOFS) is an IBM-developed media format architecture available to use when initializing optical media on the i5/OS.">High Performance Optical File System</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|