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

126 lines
8.1 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Share tape library resources" />
<meta name="abstract" content="Because library devices can be shared among multiple systems and users, it is possible to run more jobs that use a tape library than there are resources in the library." />
<meta name="description" content="Because library devices can be shared among multiple systems and users, it is possible to run more jobs that use a tape library than there are resources in the library." />
<meta name="DC.Relation" scheme="URI" content="rzam4config.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="rzam4share" />
<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>Share tape library resources</title>
</head>
<body id="rzam4share"><a name="rzam4share"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Share tape library resources</h1>
<div><p>Because library devices can be shared among multiple systems and
users, it is possible to run more jobs that use a tape library than there
are resources in the library.</p>
<div class="section"><p>As users send commands to the tape library, requests to use a
resource are sent to a tape resource manager. The request waits until a resource
becomes available. When a resource is available, the job is assigned the resource
to complete that step. How the system handles the requests depends on the <span class="uicontrol">Properties</span> in iSeries™ Navigator
that you specify for the tape library, or by using the Change Job Media Library
Attributes (CHGJOBMLBA) command.</p>
<p>To specify the <span class="uicontrol">Properties</span> for
your tape library, do the following:</p>
</div>
<ol><li class="stepexpand"><span>In iSeries Navigator
expand <span class="menucascade"><span class="uicontrol">My Connections</span> &gt; <span class="uicontrol">your iSeries
server</span> &gt; <span class="uicontrol">Configuration and Service</span> &gt; <span class="uicontrol">Tape
Devices</span> &gt; <span class="uicontrol">Hardware</span> &gt; <span class="uicontrol">Tape Libraries</span></span>.</span></li>
<li class="stepexpand"><span>Right-click the library you want to work with and select <span class="uicontrol">Properties</span>.</span></li>
<li class="stepexpand"><span>Select <span class="uicontrol">Options</span>.</span></li>
<li class="stepexpand"><span>Specify the options you want:</span> <ul><li>Tape resource selection priority</li>
<li>Initial mount wait time</li>
<li>End of volume mount wait time</li>
</ul>
</li>
</ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4config.htm" title="After you have set up the tape library and connected it to your system, the iSeries server automatically configures it.">Configure tape libraries</a></div>
</div>
</div><div class="nested1" xml:lang="en-us" id="detailstapelibprop"><a name="detailstapelibprop"><!-- --></a><h2 class="topictitle2">Details: tape library properties</h2>
<div><div class="section"><p>The order in which requests are given a resource is determined
by the option you specify for <span class="uicontrol">Tape resource selection priority</span>.
The length of time a request will wait for a resource to become available
is controlled by the length of time you specify for the request in <span class="uicontrol">Initial
mount wait time</span> and <span class="uicontrol">End of volume mount wait time</span>.
The time you specify in these properties can also be set in the tape library
device description.</p>
<p>The character-based interface equivalent to the
properties are the following parameters of the CHGJOBMLBA command:</p>
<ul><li>Resource allocation priority (RSCALCPTY)</li>
<li>Initial mount wait time (INLMNTWAIT)</li>
<li>End of volume mount wait time (EOVMNTWAIT)</li>
</ul>
<p>You can use these parameters as a default or for a particular job
using the CHGJOBMLBA command or the Change Job Media Library Attributes (QTACJMA)
API. These values are used when a request is first sent to the resource manager.
After a request has been sent to the resource manager and is waiting to be
processed, it can be monitored and changed using the Work with Media Library
Resource Queue (WRKMLBRSCQ) command.</p>
<p>The system can automate how multiple
library resources are shared. For example, assume ten save operations (SAVLIBs)
are issued, with ten different cartridges, to a tape library device description
(TAPMLB01). If TAPMLB01 has only four tape resources available to it, the
first four requests are issued, one to each tape resource. The remaining six
are placed on a queue and are issued as tape resources become available. The
order in which they are placed on the queue is based on the RSCALCPTY parameter
in the tape library device description. The resource manager eliminates any
idle time between jobs due to early completion, from either changing data
or job failure.</p>
<p>You can use Initial Mount Wait Time (INLMNTWAIT) value
to alert you of a problem. In the previous example, the ten save operations
are started at a given time and known, through estimates or benchmarking,
to complete in six hours. Set the INLMNTWAIT time limit to six hours. If any
of the save operations do not complete in six hours, an escape message is
signaled to the jobs. A pager system can monitor for this message and page
an operator to determine the necessary recovery actions.</p>
</div>
</div>
</div>
<div class="nested1" xml:lang="en-us" id="sharetapelibresourcesbetweensys"><a name="sharetapelibresourcesbetweensys"><!-- --></a><h2 class="topictitle2">Share tape library resources between systems</h2>
<div><div class="section"><p>You can share tape library resources between more than one system.
Tape resources can be set to ALLOCATED, UNPROTECTED, or DEALLOCATED. To better
facilitate sharing between systems the UNPROTECTED status was added. When
the tape resource is set to UNPROTECTED status, the tape resource is not assigned
until it is needed. This prevents a tape resource from being assigned to a
system that is not presently using it.</p>
</div>
</div>
</div>
<div class="nested1" xml:lang="en-us" id="sharetapelibsamesys"><a name="sharetapelibsamesys"><!-- --></a><h2 class="topictitle2">Share tape library resources between systems and on the same system</h2>
<div><div class="section"><p>When sharing tape resources between systems and on the same system,
each system has a resource manager with its queue controlled by the priority
and time-out values. Between the systems, the tape resources are set to UNPROTECTED
status. While sharing between systems does not have a priority concept, the
UNPROTECTED status and the fact that tape resources are only assigned when
they are in use allows the systems to effectively share the tape resources.
The resource manager tries to get a resource by attempting to assign it. If
another system has the resource, the job is placed back in the queue and waits.
In a few seconds another assign is attempted. If the job now gets the resource,
the tape operation continues.</p>
</div>
</div>
</div>
</body>
</html>