175 lines
12 KiB
HTML
175 lines
12 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 support FAQ" />
|
||
|
<meta name="abstract" content="This topic provides information to help with some common problems and questions encountered with optical devices." />
|
||
|
<meta name="description" content="This topic provides information to help with some common problems and questions encountered with optical devices." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzam4trblshtoptstg.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="rzam4optsuptfaq" />
|
||
|
<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 support FAQ</title>
|
||
|
</head>
|
||
|
<body id="rzam4optsuptfaq"><a name="rzam4optsuptfaq"><!-- --></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">Optical support FAQ</h1>
|
||
|
<div><p>This topic provides information to help with some common problems
|
||
|
and questions encountered with optical devices.</p>
|
||
|
<ol><li> <a href="#rzam4optsuptfaq__faq1">When writing objects, I receive a
|
||
|
message indicating that there is not enough optical media space available.
|
||
|
However, the volume is not full. What is wrong?</a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq2">My backup volume is filling up before
|
||
|
all objects from the primary have been stored. What is using up the extra
|
||
|
space?</a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq3">While backing up a platter, the task
|
||
|
ends abnormally. When I restart the backup, I receive the OPT1210 message
|
||
|
indicating that the directory already exists. However, the directory is not
|
||
|
listed when I use the Work with Optical Directories (WRKOPTDIR) command. How
|
||
|
can this be? </a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq4">I received an OPT1115 message indicating
|
||
|
that the file is not found when trying to retrieve an object. When I use the
|
||
|
Work with Optical Files (WRKOPTF) command, the object is displayed. Why am
|
||
|
I unable to retrieve the object?</a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq5">My application appears to be storing
|
||
|
objects correctly, but when I use the Work with Optical Files (WRKOPTF) command,
|
||
|
not all of the objects are showing up. Where are the objects going?</a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq6">My application program fails with
|
||
|
message CPF1F83 indicating that the file system name /QOPT was not found when
|
||
|
I attempt to copy a stream file using the CPYSF command. What is wrong?</a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq7">There is a volume I want to use, but
|
||
|
I cannot seem to access it. What can I do? </a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq8">Messages are occurring which indicate
|
||
|
that I should run Reclaim Optical (RCLOPT) command. A RCLOPT of type *RESET
|
||
|
can take a long time. Is there a quicker way to recover? </a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq9">What is the difference between volumes
|
||
|
marked *OFFLINE and those marked *REMOVED?</a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq10">When I add full optical volumes into
|
||
|
my optical media library by using the Add Optical Cartridge (ADDOPTCTG) command,
|
||
|
it takes a long time. Any suggestions?</a></li>
|
||
|
<li> <a href="#rzam4optsuptfaq__faq11">I entered a CD-ROM volume into my
|
||
|
CD-ROM device, but I received a message saying volume not found when I attempted
|
||
|
to access it. I did not see any error messages. What went wrong?</a></li>
|
||
|
</ol>
|
||
|
<p id="rzam4optsuptfaq__faq1"><a name="rzam4optsuptfaq__faq1"><!-- --></a><strong>When writing objects, I receive a message indicating that
|
||
|
there is not enough optical media space available. However, the volume is
|
||
|
not full. What is wrong?</strong></p>
|
||
|
<p>Either the threshold is incorrectly set, the object being stored is bigger
|
||
|
than the available space, or the <em>spares area</em> is full. Display the volume
|
||
|
attributes of the volume that you are writing to using the <span class="cmdname">display
|
||
|
optical</span> (DSPOPT) command. Verify that the threshold and space available
|
||
|
values are valid. Also, verify that access to the volume access is <em>writeable</em>,
|
||
|
and not <em>read only</em>. If it is read only, then the spares area may be
|
||
|
full. The spares area is a set of sectors to which data is written when the
|
||
|
original sector is damaged.</p>
|
||
|
<p id="rzam4optsuptfaq__faq2"><a name="rzam4optsuptfaq__faq2"><!-- --></a><strong>My backup volume is filling up before all objects from the
|
||
|
primary volume have been stored. What is using up the extra space?</strong></p>
|
||
|
<p>Several situations could cause this to happen:</p>
|
||
|
<ul><li>Device errors may have occurred when only part of a file was written.
|
||
|
When the backup operation was restarted, the complete file was rewritten.</li>
|
||
|
<li>If the backup volume type is WORM, it might have been initialized multiple
|
||
|
times before the backup operation, thus wasting some volume space.</li>
|
||
|
<li>If you are performing an incremental backup operation, you might have
|
||
|
selected the wrong option on the SLTFILE parameter (*ALL instead of *CHANGED).</li>
|
||
|
<li>If you created the primary volume on a pre-Version 2 Release 3 Modification
|
||
|
0 system, and the primary volume is over 98% full, then the Duplicate Optical
|
||
|
(DUPOPT) command may be the only choice to back up this volume.</li>
|
||
|
<li>The primary volume is a 2X media and the backup volume is 1X.</li>
|
||
|
</ul>
|
||
|
<p id="rzam4optsuptfaq__faq3"><a name="rzam4optsuptfaq__faq3"><!-- --></a><strong>While backing up a volume, the task ends abnormally. When
|
||
|
I restart the backup, I receive the OPT1210 message indicating that the directory
|
||
|
already exists. However, the directory is not listed when I use the Work with
|
||
|
Optical Directories (WRKOPTDIR) command. How can this be? </strong></p>
|
||
|
<p>When the task ended abnormally, the directory was created on the volume,
|
||
|
but the internal optical index files had not been updated yet. Remove the
|
||
|
backup volume using the Remove Optical Cartridge (RMVOPTCTG) command and add
|
||
|
it back in using the Add Optical Cartridge (ADDOPTCTG) command and specifying
|
||
|
DIR(*YES)). The internal optical index will be updated with the new path.</p>
|
||
|
<p id="rzam4optsuptfaq__faq4"><a name="rzam4optsuptfaq__faq4"><!-- --></a><strong>I received message OPT1115 indicating that the file is not
|
||
|
found when trying to retrieve an object. When I use the Work with Optical
|
||
|
Files (WRKOPTF) command, the object is displayed. Why am I unable to retrieve
|
||
|
the object?</strong></p>
|
||
|
<p>The optical media may be dirty. Contact your next level of support (hardware)
|
||
|
to get the media cleaned. </p>
|
||
|
<p id="rzam4optsuptfaq__faq5"><a name="rzam4optsuptfaq__faq5"><!-- --></a><strong>My application appears to be storing objects correctly, but
|
||
|
when I use the Work with Optical Files (WRKOPTF) command, not all of the objects
|
||
|
are showing up. Where are the objects going?</strong> </p>
|
||
|
<p>The files may be held optical files. Refer to <a href="rzam4heldoptfiles.htm">Held optical files</a> for more information on held optical
|
||
|
files. In this case, the volume may have reached its threshold. Verify that
|
||
|
your application is handling the OPT1345 message <tt class="msgph">Threshold reached
|
||
|
on optical volume</tt> or CPF1F61 message <tt class="msgph">No space available on
|
||
|
media</tt> correctly. </p>
|
||
|
<p id="rzam4optsuptfaq__faq6"><a name="rzam4optsuptfaq__faq6"><!-- --></a><strong>My application program fails with message CPF1F83 indicating
|
||
|
that the file system name /QOPT was not found when I attempt to copy a stream
|
||
|
file using the CPYSF command. What is wrong?</strong> </p>
|
||
|
<p>The file system portion of the path (/QOPT) must be specified in uppercase
|
||
|
characters. The rest of the path can be in either uppercase or lowercase characters. </p>
|
||
|
<p id="rzam4optsuptfaq__faq7"><a name="rzam4optsuptfaq__faq7"><!-- --></a><strong>There is a volume I want to use, but I cannot seem to access
|
||
|
it. What can I do? </strong></p>
|
||
|
<p>Duplicate volume names might cause this. If the volume is in a LAN server,
|
||
|
it may have the same name as a volume in a directly attached library or another
|
||
|
server. If there are duplicate names, only the first volume found is usable. </p>
|
||
|
<p id="rzam4optsuptfaq__faq8"><a name="rzam4optsuptfaq__faq8"><!-- --></a><strong>Messages are occurring which indicate that I should run Reclaim
|
||
|
Optical (RCLOPT) command. A RCLOPT of type *RESET can take a long time. Is
|
||
|
there a quicker way to recover? </strong></p>
|
||
|
<p>Yes. First read <cite>Reclaiming the Optical Index Database</cite> to gain
|
||
|
a better understanding of the RCLOPT process. Then attempt one of the following:</p>
|
||
|
<ul><li>Run RCLOPT MLB <var class="varname">device_name</var> OPTION(*SYNC).</li>
|
||
|
<li>Work with Optical Volumes (WRKOPTVOL) and press F14 (Show extended information).
|
||
|
If any volumes show <tt class="msgph">moving</tt> as the location, then do the following:<ol><li>Run RCLOPT MLB(device name) OPTION(*UPDATE) VOL <var class="varname">moving_volume_name</var>.</li>
|
||
|
<li>Refresh the Work with Optical Volumes screen. If any volumes still show
|
||
|
up as moving, repeat step 1.</li>
|
||
|
</ol>
|
||
|
</li>
|
||
|
</ul>
|
||
|
<ul><li>Run RCLOPT MLB <var class="varname">device name</var> OPTION(*RESET) DIR(*NO)<div class="note"><span class="notetitle">Note:</span> This
|
||
|
choice takes longer than the first two, but by specifying DIR(*NO), it could
|
||
|
cut the RCLOPT *RESET time in half.</div>
|
||
|
</li>
|
||
|
</ul>
|
||
|
<p id="rzam4optsuptfaq__faq9"><a name="rzam4optsuptfaq__faq9"><!-- --></a><strong>What is the difference between volumes marked *OFFLINE and
|
||
|
those marked *REMOVED?</strong></p>
|
||
|
<p>*OFFLINE entries are volumes in optical devices that are either powered
|
||
|
off, varied off, or no longer connected. *REMOVED entries are volumes that
|
||
|
were removed from the optical media library with VOLOPT *KEEP specified.</p>
|
||
|
<p id="rzam4optsuptfaq__faq10"><a name="rzam4optsuptfaq__faq10"><!-- --></a><strong>When I add full optical volumes into my optical media library
|
||
|
by using the Add Optical Cartridge (ADDOPTCTG) command, it takes a long time.
|
||
|
Any suggestions?</strong></p>
|
||
|
<p>When volumes are removed using the Remove Optical Cartridge (RMVOPTCTG)
|
||
|
command, remove them specifying *KEEP on the VOLOPT parameter. The internal
|
||
|
optical indexes save all information about these volumes, including the optical
|
||
|
directory information. When volumes are added using the ADDOPTCTG command,
|
||
|
specify *NO in the DIR parameter. The volumes are added and the directory
|
||
|
index is not rebuilt. This speeds up the import process.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> This process should not be followed if changes were made to the removed
|
||
|
volumes since the volumes were last removed from this system.</div>
|
||
|
<p id="rzam4optsuptfaq__faq11"><a name="rzam4optsuptfaq__faq11"><!-- --></a><strong>I entered a CD-ROM volume into my CD-ROM device, but I received
|
||
|
a message saying volume not found when I attempted to access it. I did not
|
||
|
see any error messages. What went wrong?</strong></p>
|
||
|
<p>Refer to <cite>CD-ROM and DVD on iSeries™ Servers</cite> for information
|
||
|
on loading CD-ROM media. In this case, you probably attempted to access the
|
||
|
CD-ROM before it was fully loaded (wait 10-20 seconds after the tray slides
|
||
|
in), or an error occurred during the load operation. Refer to the QSYSOPR
|
||
|
message queue to see if the CD-ROM volume loaded successfully.</p>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4trblshtoptstg.htm" title="This topic provides information about solutions related to optical storage.">Troubleshoot optical storage</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
</html>
|