152 lines
10 KiB
HTML
152 lines
10 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="Memory pool ID" />
|
|||
|
|
<meta name="abstract" content="The memory pool ID (POOLID) parameter of the routing entry specifies the pool identifier of the storage pool in which the program runs. The pool identifier specified here relates to the storage pools in the subsystem description." />
|
|||
|
|
<meta name="description" content="The memory pool ID (POOLID) parameter of the routing entry specifies the pool identifier of the storage pool in which the program runs. The pool identifier specified here relates to the storage pools in the subsystem description." />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutroutingentries.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksrtentryclass.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksroutentrycompare.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksrtentrymaxact.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="rzaksrtentrymempool" />
|
|||
|
|
<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>Memory pool ID</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="rzaksrtentrymempool"><a name="rzaksrtentrymempool"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Memory pool ID</h1>
|
|||
|
|
<div><p>The memory pool ID (<span class="parmname">POOLID</span>) parameter of the
|
|||
|
|
routing entry specifies the pool identifier of the storage pool in which the
|
|||
|
|
program runs. The pool identifier specified here relates to the storage pools
|
|||
|
|
in the subsystem description. </p>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Program to call</h4><p>The program to call (<span class="parmname">PGM</span>)
|
|||
|
|
parameter of the routing entry specifies the name and library of the program
|
|||
|
|
called as the first program run in the routing step. No parameters can be
|
|||
|
|
passed to the specified program. The program name can be either explicitly
|
|||
|
|
specified in the routing entry, or extracted from the routing data. </p>
|
|||
|
|
<p>If
|
|||
|
|
a program name is specified in a routing entry, selection of that routing
|
|||
|
|
entry results in the routing entry program being called (regardless of the
|
|||
|
|
program name passed in an EVOKE function). If the program specified in the
|
|||
|
|
EVOKE function is supposed to be called, *RTGDTA must be specified in this
|
|||
|
|
parameter. If the program does not exist when the routing entry is added or
|
|||
|
|
changed, a library qualifier must be specified because the qualified program
|
|||
|
|
name is kept in the subsystem description. </p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Sequence number</h4><p>The sequence number (<span class="parmname">SEQNBR</span>)
|
|||
|
|
parameter of the routing entry tells the subsystem the order in which routing
|
|||
|
|
entries are to be searched for a routing data match. The routing entries are
|
|||
|
|
searched in sequence number order. When you add routing entries to a subsystem
|
|||
|
|
description, you should order them so that the entries likely to be compared
|
|||
|
|
most often are first. This reduces the search time.</p>
|
|||
|
|
<div class="p">
|
|||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="void" border="1" rules="all"><thead align="left"><tr><th valign="top" id="d0e40">Sequence Number</th>
|
|||
|
|
<th valign="top" id="d0e42">Comparison Value</th>
|
|||
|
|
</tr>
|
|||
|
|
</thead>
|
|||
|
|
<tbody><tr><td valign="top" headers="d0e40 ">10</td>
|
|||
|
|
<td valign="top" headers="d0e42 ">'ABC'</td>
|
|||
|
|
</tr>
|
|||
|
|
<tr><td valign="top" headers="d0e40 ">20</td>
|
|||
|
|
<td valign="top" headers="d0e42 ">'AB'</td>
|
|||
|
|
</tr>
|
|||
|
|
<tr><td valign="top" headers="d0e40 ">30</td>
|
|||
|
|
<td valign="top" headers="d0e42 ">'A'</td>
|
|||
|
|
</tr>
|
|||
|
|
<tr><td valign="top" headers="d0e40 ">40</td>
|
|||
|
|
<td valign="top" headers="d0e42 ">'E'</td>
|
|||
|
|
</tr>
|
|||
|
|
<tr><td valign="top" headers="d0e40 ">50</td>
|
|||
|
|
<td valign="top" headers="d0e42 ">'D'</td>
|
|||
|
|
</tr>
|
|||
|
|
</tbody>
|
|||
|
|
</table>
|
|||
|
|
</div>
|
|||
|
|
In the above example, the routing entries are searched in sequence
|
|||
|
|
number order. If the routing data is ’A’, the search ends with routing entry
|
|||
|
|
30. If the routing data is ’AB’, the search ends with routing entry 20. If
|
|||
|
|
the routing data is ’ABC’, the search ends with routing entry 10. Because
|
|||
|
|
routing data can be longer than the comparison value of the routing entry,
|
|||
|
|
the comparison (which is done in left-to-right order) stops when it reaches
|
|||
|
|
the end of the comparison value. Therefore, if the routing data is ’ABCD’,
|
|||
|
|
the search ends with routing entry 10.</div>
|
|||
|
|
<div class="p">When you define routing entries,
|
|||
|
|
they must be ordered from the most specific to the most general. The following
|
|||
|
|
example shows a correct and incorrect way to define routing entries:
|
|||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="void" border="1" rules="all"><thead align="left"><tr><th colspan="2" align="center" valign="middle" id="d0e81">Correct</th>
|
|||
|
|
<th colspan="2" align="center" valign="middle" id="d0e83">Incorrect</th>
|
|||
|
|
</tr>
|
|||
|
|
<tr><th valign="top" width="24.242424242424242%" id="d0e86">Sequence Number</th>
|
|||
|
|
<th valign="top" width="23.96694214876033%" id="d0e88">Comparison Value</th>
|
|||
|
|
<th valign="top" width="25.895316804407713%" id="d0e90">Sequence Number</th>
|
|||
|
|
<th valign="top" width="25.895316804407713%" id="d0e92">Comparison Value</th>
|
|||
|
|
</tr>
|
|||
|
|
</thead>
|
|||
|
|
<tbody><tr><td valign="top" width="24.242424242424242%" headers="d0e81 d0e86 ">10</td>
|
|||
|
|
<td valign="top" width="23.96694214876033%" headers="d0e81 d0e88 ">'ABC'</td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e90 ">10</td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e92 ">'ABC'</td>
|
|||
|
|
</tr>
|
|||
|
|
<tr><td valign="top" width="24.242424242424242%" headers="d0e81 d0e86 ">20</td>
|
|||
|
|
<td valign="top" width="23.96694214876033%" headers="d0e81 d0e88 ">'AB'</td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e90 ">20</td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e92 ">'ABCD'</td>
|
|||
|
|
</tr>
|
|||
|
|
<tr><td valign="top" width="24.242424242424242%" headers="d0e81 d0e86 ">30</td>
|
|||
|
|
<td valign="top" width="23.96694214876033%" headers="d0e81 d0e88 ">'A'</td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e90 "> </td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e92 "> </td>
|
|||
|
|
</tr>
|
|||
|
|
<tr><td valign="top" width="24.242424242424242%" headers="d0e81 d0e86 ">40</td>
|
|||
|
|
<td valign="top" width="23.96694214876033%" headers="d0e81 d0e88 ">'E'</td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e90 "> </td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e92 "> </td>
|
|||
|
|
</tr>
|
|||
|
|
<tr><td valign="top" width="24.242424242424242%" headers="d0e81 d0e86 ">9999</td>
|
|||
|
|
<td valign="top" width="23.96694214876033%" headers="d0e81 d0e88 ">*ANY</td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e90 "> </td>
|
|||
|
|
<td valign="top" width="25.895316804407713%" headers="d0e83 d0e92 "> </td>
|
|||
|
|
</tr>
|
|||
|
|
</tbody>
|
|||
|
|
</table>
|
|||
|
|
</div>
|
|||
|
|
In the incorrect example, it is no longer possible to match routing
|
|||
|
|
entry 20 because any routing data that matches the comparison value for routing
|
|||
|
|
entry 20 matches the routing entry 10 first. When a routing entry is changed
|
|||
|
|
or added to a subsystem description with a comparison value that causes this
|
|||
|
|
situation, the system sends a diagnostic message identifying the situation. </div>
|
|||
|
|
<p>The
|
|||
|
|
program named in the routing entry is given control when the routing step
|
|||
|
|
for the job is started. Parameters to control the run-time environment (priority,
|
|||
|
|
time slice, and so on) of the routing step for the job are taken from the
|
|||
|
|
class specified in the routing entry.</p>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksaboutroutingentries.htm" title="The routing entry identifies the main storage subsystem pool to use, the controlling program to run (typically the system-supplied program QCMD), and additional run-time information (stored in the class object). Routing entries are stored in the subsystem description.">Routing entries</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|||
|
|
<div><a href="rzaksrtentryclass.htm" title="Job run-time attributes are contained in the class object that is specified in the (CLS) parameter in the routing entry. If a job consists of multiple routing steps, the class used by each subsequent routing step is specified in the routing entry used to start the routing step. If the class does not exist when the routing entry is added, a library qualifier must be specified because the qualified class name is kept in the subsystem description.">Class</a></div>
|
|||
|
|
<div><a href="rzaksroutentrycompare.htm" title="The comparison value (CMPVAL) parameter of the routing entry specifies data that is compared with routing data to determine which routing entry to use. (The routing entry also specifies the starting position for the comparison.) The routing data is compared with the comparison value of each routing entry in sequence number order until a match is found. The sequence number contained in a routing entry defines the order in which the routing entries are scanned and can be used as the identifier of the routing entry.">Comparison data</a></div>
|
|||
|
|
<div><a href="rzaksrtentrymaxact.htm" title="The maximum active routing steps (MAXACT) parameter of the routing entry specifies the maximum number of routing steps (jobs) that can be active at the same time through this routing entry.">Maximum active routing steps</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|