71 lines
5.1 KiB
HTML
71 lines
5.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="Held optical files" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4howoptifileused.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4recoverheldoptfile.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4saveheldoptfile.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4releaseheldoptlfile.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4implmtheldoptfilefunc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4disablhldoptsupt.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="rzam4heldoptfiles" />
|
|
<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>Held optical files</title>
|
|
</head>
|
|
<body id="rzam4heldoptfiles"><a name="rzam4heldoptfiles"><!-- --></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">Held optical files</h1>
|
|
<div><p>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.</p>
|
|
<p>The optical file system might still consider the file to be open. If it
|
|
considers the file open, the optical file system allows any application that
|
|
already has the file open to continue operating. In any case, no new application
|
|
can open a file while it remains held. If the system can correct the condition
|
|
that caused the failure, and the file is still open, the application may attempt
|
|
to close the file again. If the close function succeeds, the system no longer
|
|
holds the file. (If an HFS application specified an open type of normal, it
|
|
cannot access the file through the HFS API any longer. IBM<sup>®</sup> provides online information on the open
|
|
types that concern the Open Stream File command.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> The system does not create held files when files fail to close on UDF
|
|
media.</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzam4recoverheldoptfile.htm">Recover a held optical file</a></strong><br />
|
|
This topic provides instructions on recovering held optical file.</li>
|
|
<li class="ulchildlink"><strong><a href="rzam4saveheldoptfile.htm">Save a held optical file</a></strong><br />
|
|
Saving a held optical file physically writes the data and file attributes to the optical disk. You can choose to save to the original volume, directory, and file name that you specified at open time, or to a new optical file path.</li>
|
|
<li class="ulchildlink"><strong><a href="rzam4releaseheldoptlfile.htm">Release a held optical file</a></strong><br />
|
|
A held file can only be released if no locks are currently imposed on the file by other active jobs.</li>
|
|
<li class="ulchildlink"><strong><a href="rzam4implmtheldoptfilefunc.htm">Implement held optical file functions</a></strong><br />
|
|
Before deciding whether to save or release a held optical file, you might want to view information that can influence save and release decisions.</li>
|
|
<li class="ulchildlink"><strong><a href="rzam4disablhldoptsupt.htm">Disable held optical file support</a></strong><br />
|
|
i5/OS™ is
|
|
shipped with held optical file support enabled. If desired, you may disable
|
|
it by using the Change Optical Attributes (CHGOPTA) command.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4howoptifileused.htm" title="An application can manipulate optical file data by using UNIX-type APIs or the hierarchical file system (HFS).">How optical files are used</a></div>
|
|
</div>
|
|
</div>
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
|
</html> |