ibm-information-center/dist/eclipse/plugins/i5OS.ic.rbam6_5.4.0.1/rbam6scheduleexpand.htm

124 lines
7.9 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="reference" />
<meta name="DC.Title" content="JOBPTY, OUTPTY, and PTYLMT scheduling priority parameters" />
<meta name="abstract" content="The scheduling priority parameters specify the priority values used by the system to determine the order in which the jobs and spooled files are selected for processing." />
<meta name="description" content="The scheduling priority parameters specify the priority values used by the system to determine the order in which the jobs and spooled files are selected for processing." />
<meta name="DC.Relation" scheme="URI" content="rbam6expand.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbam6scheduleexpand" />
<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>JOBPTY, OUTPTY, and PTYLMT scheduling priority parameters</title>
</head>
<body id="rbam6scheduleexpand"><a name="rbam6scheduleexpand"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">JOBPTY, OUTPTY, and PTYLMT scheduling priority parameters</h1>
<div><p>The scheduling priority parameters specify the priority values
used by the system to determine the order in which the jobs and spooled files
are selected for processing.</p>
<div class="section"><p>Each job is given a scheduling priority that is used for both
job selection and spooled file output. The job scheduling priority is specified
by the JOBPTY parameter in commands like the <span class="cmdname">Batch Job (BCHJOB)</span>, <span class="cmdname">Submit
Job (SBMJOB)</span>, <span class="cmdname">Create Job Description (CRTJOBD)</span>,
and <span class="cmdname">Change Job Description (CHGJOBD)</span> commands. The priority
for producing the spooled output from a job is specified by the OUTPTY parameter
in the same commands.</p>
<p>In addition, because every job is processed under
a specific user profile, the priority for jobs can be limited by the PTYLMT
parameter specified on the <span class="cmdname">Create User Profile (CRTUSRPRF)</span> and <span class="cmdname">Change
User Profile (CHGUSRPRF)</span> commands. This parameter value controls
the maximum job scheduling priority and output priority that <em>any</em> job
running under a user profile can have; that is, the priority specified in
the JOBPTY and OUTPTY parameters of any job command cannot exceed the priority
specified in the PTYLMT parameter for that user profile. The scheduling priority
is used to determine the order in which jobs are selected for processing and
is not related to the process priority specified in the class object.</p>
<p>The
three scheduling priority parameters specify the following:</p>
<ul><li>The PTYLMT parameter specifies the <em>highest</em> scheduling priority
for <em>any</em> job that you submit. In the commands that affect the user
profile, the PTYLMT parameter specifies the highest priority that can be specified
in another JOBPTY parameter on commands relating to each specific job. You
can specify a lower priority for a job on the command used to submit the job.
If you specify a higher priority for JOBPTY in the BCHJOB or SBMJOB command
than is specified for PTYLMT in the associated user profile, an error message
is shown on the display and the maximum priority specified in PTYLMT is assumed.
If a higher job priority is specified in the CHGJOB or CHGJOBD command, an
error message is shown and the attributes are not changed.</li>
<li>The JOBPTY parameter specifies the priority value to be used for a <em>specific</em> job
being submitted. In the commands relating to a specific job being submitted,
the JOBPTY parameter specifies the actual scheduling priority for the job.</li>
<li>The OUTPTY parameter specifies the priority for producing the output from
all spooled output files from the job. The priority value specified in the
OUTPTY parameter determines the order in which spooled files are handled for
output. The same value is applied to all the spooled files produced by the
job.</li>
</ul>
<p>The scheduling priority can have a value ranging from 0 through 9,
where 1 is the highest priority and 9 is the lowest priority. Any job with
a priority of 0 is scheduled for processing before all other jobs that are
waiting and that have priorities of 1 through 9.</p>
<p>The priority parameters
can be specified on the following commands.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Priority parameter</caption><thead align="left"><tr><th valign="top" width="21.71717171717172%" id="d0e68">Priority parameter</th>
<th valign="top" width="78.28282828282829%" id="d0e70">Commands on which it can be specified</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="21.71717171717172%" headers="d0e68 ">JOBPTY</td>
<td valign="top" width="78.28282828282829%" headers="d0e70 ">ADDJOBJS, BCHJOB, CHGJOB, CHGJOBD, CHGJOBJS, CRTJOBD, SBMJOB, SBMJOBJS</td>
</tr>
<tr><td valign="top" width="21.71717171717172%" headers="d0e68 ">OUTPTY</td>
<td valign="top" width="78.28282828282829%" headers="d0e70 ">ADDJOBJS, BCHJOB, CHGDKTF, CHGJOBD, CHGJOBJS, CHGJOB, CHGJOBD, CHGJOBJS,
CHGPJ, CHGPRTF, CHGSPLFA, CRTDKTF, CRTJOBD, CRTPRTF, OVRDKTF, OVRPRTF, SBMJOB,
SBMJOBJS</td>
</tr>
<tr><td valign="top" width="21.71717171717172%" headers="d0e68 ">PTYLMT</td>
<td valign="top" width="78.28282828282829%" headers="d0e70 ">CHGUSRPRF, CRTUSRPRF, RTVUSRPRF</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section"><h4 class="sectiontitle">Values allowed</h4><p>Depending upon the command, one or
more of the following values apply to the parameter.</p>
<dl><dt class="dlterm">5</dt>
<dd>If a value is not specified in the CRTUSRPRF command, five is the default
value that is assumed for the priority limit for the user profile. That would
be the highest priority that the user could specify for any job he submits
for processing. If not specified in the CRTJOBD command, five is the default
value for both the job scheduling priority and the output priority.</dd>
<dt class="dlterm">*SAME</dt>
<dd>The priority assigned, or the highest priority that can be assigned, does
not change.</dd>
<dt class="dlterm">*JOBD</dt>
<dd>The scheduling priority for the job is obtained from the job description
under which the job runs.</dd>
<dt class="dlterm"><var class="varname">scheduling-priority:</var></dt>
<dd>Specify a priority value ranging from 0 through 9, where 0 is the highest
priority and 9 is the lowest priority. Priority 0 is allowed only on CHGJOB.</dd>
</dl>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbam6expand.htm" title="This section contains the expanded descriptions of some of the parameters commonly used in the CL commands.">Commonly used parameters</a></div>
</div>
</div>
</body>
</html>