75 lines
4.9 KiB
HTML
75 lines
4.9 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="Tips: Optical programming" />
|
||
|
|
<meta name="abstract" content="The following techniques are often helpful in designing custom optical programs for your business." />
|
||
|
|
<meta name="description" content="The following techniques are often helpful in designing custom optical programs for your business." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="capacitythreshold.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="capacitymanage.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="bufferio.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="bufferdata.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="heldfiles.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzau8pathnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="clexamples.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="tipsandtechniques" />
|
||
|
|
<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>Tips: Optical programming</title>
|
||
|
|
</head>
|
||
|
|
<body id="tipsandtechniques"><a name="tipsandtechniques"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Tips: Optical programming</h1>
|
||
|
|
<div><p>The following techniques are often helpful in designing custom
|
||
|
|
optical programs for your business.</p>
|
||
|
|
<p>This topic describes how the optical file system manages file data so application
|
||
|
|
programmers can optimize their applications. Since applications have different
|
||
|
|
requirements, this topic does not suggest the best way to write an optical
|
||
|
|
application. It does, however, provide explanations that all application programmers
|
||
|
|
could find useful.</p>
|
||
|
|
<p>Use this topic to determine the best way to handle optical file management,
|
||
|
|
either through the HFS or UNIX-type APIs. Use this topic only for applications
|
||
|
|
to directly attached optical support.</p>
|
||
|
|
<div class="p"><div class="note"><span class="notetitle">Note:</span> Concepts in this topic do not apply to optical LAN support.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="capacitythreshold.htm">Media capacity and volume threshold</a></strong><br />
|
||
|
|
Read about indicating a volume threshold for your applications.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="capacitymanage.htm">Managing media capacity on a per-file basis</a></strong><br />
|
||
|
|
Learn how to manage media capacity on a per-file basis.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="bufferio.htm">Expanding buffer I/O through HFS</a></strong><br />
|
||
|
|
Read about tailoring read requests for performance and to expand buffer I/O in HFS.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="bufferdata.htm">Using forced buffered data APIs</a></strong><br />
|
||
|
|
Read about using the QHFFRCSF or fscync() APIs to write optical file data to nonvolatile media while writing to optical media.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="heldfiles.htm">Held optical files</a></strong><br />
|
||
|
|
Read about how to manage virtual files that are held due to an error while writing to optical media.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzau8pathnames.htm">Path names</a></strong><br />
|
||
|
|
This topic describes path names for optical volumes.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="clexamples.htm">Examples: Moving spooled files to and from optical storage</a></strong><br />
|
||
|
|
This topic includes some basic optical programming examples using i5/OS™ control
|
||
|
|
language (CL) commands.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="kickoff.htm" title="This topic collection describes the application programming interfaces (APIs) developers can use to access optical volumes on the i5/OS operating system.">Optical device programming</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|