67 lines
4.1 KiB
HTML
67 lines
4.1 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="How optical files are used" />
|
||
|
|
<meta name="abstract" content="An application can manipulate optical file data by using UNIX-type APIs or the hierarchical file system (HFS)." />
|
||
|
|
<meta name="description" content="An application can manipulate optical file data by using UNIX-type APIs or the hierarchical file system (HFS)." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4recovheldoptfil.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4heldoptfiles.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apiref/api.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="rzam4howoptifileused" />
|
||
|
|
<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>How optical files are used </title>
|
||
|
|
</head>
|
||
|
|
<body id="rzam4howoptifileused"><a name="rzam4howoptifileused"><!-- --></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">How optical files are used </h1>
|
||
|
|
<div><p>An application can manipulate optical file data by using UNIX-type
|
||
|
|
APIs or the hierarchical file system (HFS).</p>
|
||
|
|
<p>An application opens a file, operates on the file, and finally closes the
|
||
|
|
file. When an application changes file data or attributes, the optical file
|
||
|
|
system stores these changes in a temporary system object in i5/OS™ storage.
|
||
|
|
The optical file system does not update the optical disk until the application
|
||
|
|
closes the file. When two or more applications concurrently change file data
|
||
|
|
or attributes, the optical file system updates the optical disk when the last
|
||
|
|
updating application closes the file. The application may force file and attribute
|
||
|
|
data to optical disk by issuing either the HFS Force Buffered Data API or
|
||
|
|
UNIX-Type <span class="apiname">fsync()</span> functions.</p>
|
||
|
|
<p>Implementing this process has the following benefits: </p>
|
||
|
|
<ul><li>Simulation of read and write access to optical files</li>
|
||
|
|
<li>File locking and sharing</li>
|
||
|
|
<li>Byte locking and sharing</li>
|
||
|
|
<li>Random processing of optical file data</li>
|
||
|
|
<li>Writing Variable-length data buffers to the optical file</li>
|
||
|
|
<li>Reduction of input and output to the optical disk</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzam4heldoptfiles.htm">Held optical files</a></strong><br />
|
||
|
|
If the optical file system is unable to update the optical disk during a close function, the operation fails and the file is marked as held.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4recovheldoptfil.htm" title="A held optical file is an optical file that could not be closed normally.">Recover held optical files</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../apiref/api.htm">Application programming interfaces (APIs)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|