ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzam4_5.4.0.1/rzam4schvolmmntdismnt.htm

86 lines
5.9 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?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="Volume mounting and dismounting schedule timers" />
<meta name="abstract" content="This topic provides information on how the iSeries server manages work requests to the directly attached optical library devices. It is a high-level view and does not include all program logic." />
<meta name="description" content="This topic provides information on how the iSeries server manages work requests to the directly attached optical library devices. It is a high-level view and does not include all program logic." />
<meta name="DC.Relation" scheme="URI" content="rzam4perfoptmedlib.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="rzam4schvolmmntdismnt" />
<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>Volume mounting and dismounting schedule timers</title>
</head>
<body id="rzam4schvolmmntdismnt"><a name="rzam4schvolmmntdismnt"><!-- --></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">Volume mounting and dismounting schedule timers</h1>
<div><p>This topic provides information on how the iSeries™ server manages work requests
to the directly attached optical library devices. It is a high-level view
and does not include all program logic. </p>
<p>You can use the Change Device Description (CHGDEVMLB) command to change
the queuing and scheduling logic used by the iSeries server for directly attached
optical media libraries. </p>
<p>Two timer values are associated with optical media libraries that affect
the scheduling of volume mounting and pre-emptive dismounts. You can change
both timer values by using the CHGDEVMLB command. The first timer value (UNLOADWAIT)
is the unload wait time. This value determines how long the system waits for
a new request for a mounted volume before removing it. The second timer value
(MAXDEVTIME) is the maximum device wait time. This value determines how long
a volume with active requests remains in a drive while other queued requests
are waiting to use the drive.</p>
<p>By using these two timer values, you can adjust the volume mount scheduling
that is used by the optical media library to match your applications use
of optical volumes. </p>
<p>You can change these timer values at any time; however, the new timer values
will not become effective until the next time the device is varied on. </p>
<p>System job priority and limit timers are used to schedule volume mounting.
The maximum number of volumes that can be mounted is equal to the number of
drives in the optical media library. Keep the following points in mind as
you schedule volume mounting:</p>
<ul><li>A volume can remain mounted in an optical drive for the maximum device
wait time if work requests with the same or lower job priority for a different
volume have been received. An exception to this is when you are initializing
a rewritable volume or using DUPOPT; the volume remains in the drive until
the operation is completed.</li>
<li>Work requests for mounted volumes are serviced before requests of the
same or lower job priority for volumes not mounted.</li>
<li>For a multiple job environment, volumes are mounted based on the job priority
for the work request. A work request from a job with a higher system job priority
causes the required volume to be mounted to handle that request. The volume
remains mounted for the maximum device wait time if work requests continue,
dismounts after unload wait time inactivity, or is overridden by a work request
from a job with higher system priority. If you are initializing a rewritable
volume or using DUPOPT, the volume remains mounted until the operation is
completed.</li>
<li>If the work on a drive is interrupted because of a higher priority request,
the maximum device wait time timer for the currently mounted volume is canceled.
All future requests for that volume are queued for normal processing by priority.</li>
<li>If the volume needed for a work request is not mounted within the system
timeout (typically 30 minutes), the job fails due to a timeout.</li>
</ul>
<p><strong>Change job priority on active jobs</strong></p>
<p> Due to the work management method used by i5/OS™ optical support, changing run priorities
of an active optical job at the user level can result in loss of time allocation
and, in some cases, cause jobs to time out. </p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4perfoptmedlib.htm" title="This topic discusses performance considerations that are specific to directly-attached optical libraries.">Performance considerations for directly-attached optical media libraries</a></div>
</div>
</div>
<img src="./deltaend.gif" alt="End of change" /></body>
</html>