91 lines
6.2 KiB
HTML
91 lines
6.2 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="Optical device programming concepts" />
|
||
|
|
<meta name="abstract" content="Read this topic collection for basic concepts of optical device programming. Basic concepts that are described for optical device programming include the i5/OS optical storage system, integrated file system, hierarchical file system, and considerations for volumes." />
|
||
|
|
<meta name="description" content="Read this topic collection for basic concepts of optical device programming. Basic concepts that are described for optical device programming include the i5/OS optical storage system, integrated file system, hierarchical file system, and considerations for volumes." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="ifsconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="hfsconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="considerations.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="rzau8concept" />
|
||
|
|
<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>Optical device programming concepts</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzau8concept"><a name="rzau8concept"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Optical device programming concepts</h1>
|
||
|
|
<div><p>Read this topic collection for basic concepts of optical device
|
||
|
|
programming. Basic concepts that are described for optical device programming
|
||
|
|
include the i5/OS™ optical
|
||
|
|
storage system, integrated file system, hierarchical file system, and considerations
|
||
|
|
for volumes.</p>
|
||
|
|
<p>This topic collection describes the interfaces that an application programmer
|
||
|
|
can use to access optical volumes on i5/OS. The proper name for these interfaces
|
||
|
|
is application programming interfaces (APIs). You can use these APIs to perform
|
||
|
|
interface functions with a variety of different file systems, of which the
|
||
|
|
optical file system is one. This topic collection does not include all of
|
||
|
|
the API documentation. It only describes the aspects of API use that are unique
|
||
|
|
to the optical file system. i5/OS optical file systems consist of any data storage
|
||
|
|
system using optical media including CD, DVD, WORM, and Magneto-Optical.</p>
|
||
|
|
<p>Programmers can use the available APIs to create, access, change, or maintain
|
||
|
|
optical files and directories. The APIs may be used to customize usage of
|
||
|
|
optical support for specific business applications.</p>
|
||
|
|
<div class="p">Two categories of APIs can be used to manipulate optical files and directories: <ul><li>Integrated file system support, which consists of UNIX-type APIs and the
|
||
|
|
generic command interface</li>
|
||
|
|
<li>Hierarchical file system (HFS) support, which consists of APIs and generic
|
||
|
|
commands. </li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>You can use both categories of APIs concurrently. For example, an optical
|
||
|
|
file that is opened for reading by one application by using the HFS Open Stream
|
||
|
|
File API can be opened for reading by another application using the Open UNIX-type
|
||
|
|
API. </p>
|
||
|
|
<p>Because different file systems exist in i5/OS, you must provide some means for
|
||
|
|
the HFS or the integrated file system to differentiate for which file system
|
||
|
|
a call is targeted. This is accomplished by requiring that the first name
|
||
|
|
in the path name parameter be the name of the file system to be called, preceded
|
||
|
|
by a leading slash. In order for the optical file system to be identified
|
||
|
|
as the receiver of a request submitted to the HFS or the integrated file system,
|
||
|
|
the first portion of the path name parameter must be <span class="uicontrol">/QOPT</span>.
|
||
|
|
The remaining path elements to follow /QOPT are volume/directory/subdirectory/file.
|
||
|
|
For an example of a path name, see the following:</p>
|
||
|
|
<p>/QOPT/CD001/Dir1/SubDir1/File</p>
|
||
|
|
<p>For more information about using integrated file system and
|
||
|
|
HFS APIs, see the <a href="../apiref/api.htm">APIs</a> topic.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="ifsconcepts.htm">Integrated file system</a></strong><br />
|
||
|
|
The integrated file system is a part of i5/OS that supports stream input/output
|
||
|
|
and storage management similar to personal computer and UNIX<sup>®</sup> operating
|
||
|
|
systems, while providing an integrating structure over all information stored
|
||
|
|
in your server. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="hfsconcepts.htm">Hierarchical file system (HFS)</a></strong><br />
|
||
|
|
A hierarchical file system (HFS) is a part of the operating system that includes the application programming interface (API) and the underlying file system (optical or otherwise) support.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="considerations.htm">Volume, directory, and file considerations</a></strong><br />
|
||
|
|
Several special considerations will make your optical programming easier.</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>
|