58 lines
3.5 KiB
HTML
58 lines
3.5 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="task" />
|
|
<meta name="DC.Title" content="Held optical files" />
|
|
<meta name="abstract" content="Read about how to manage virtual files that are held due to an error while writing to optical media." />
|
|
<meta name="description" content="Read about how to manage virtual files that are held due to an error while writing to optical media." />
|
|
<meta name="DC.Relation" scheme="URI" content="tipsandtechniques.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="heldfiles" />
|
|
<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="heldfiles"><a name="heldfiles"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Held optical files</h1>
|
|
<div><p>Read about how to manage virtual files that are held due to an
|
|
error while writing to optical media.</p>
|
|
<div class="p"><p><dfn class="term">Held optical files</dfn> are virtual files that were never
|
|
successfully written to optical media. A virtual file becomes <dfn class="term">held</dfn> if
|
|
an error occurs during the close operation of a file on a non-UDF formatted
|
|
volume. You can manage these virtual files by using application interfaces
|
|
and optical utilities. No creation of held files occurs for files that fail
|
|
to archive on UDF formatted volumes.</p>
|
|
<p>Assume an optical volume is initialized
|
|
to a 95% threshold and an application writes files until the volume threshold
|
|
is reached. When the threshold is reached, the application will receive message
|
|
CPF1F61, <kbd class="userinput">No free space available on media</kbd>. In this
|
|
example, the absolute volume capacity is reached and the file is too large
|
|
to fit on the volume. Because increasing the volume threshold will not help,
|
|
another solution is needed. When the close request fails, the virtual file
|
|
becomes held. Using the Work With Held Optical Files command, this virtual
|
|
file can be saved to another volume. If you want, the file can
|
|
be saved under a different name. The save request can also be performed using
|
|
a control file system function. </p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="tipsandtechniques.htm" title="The following techniques are often helpful in designing custom optical programs for your business.">Tips: Optical programming</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |