65 lines
4.4 KiB
HTML
65 lines
4.4 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="task" />
|
||
|
|
<meta name="DC.Title" content="Tips for setting job priorities" />
|
||
|
|
<meta name="abstract" content="The priorities for jobs that run in batch environments should normally be lower than priorities for jobs in interactive environments. Also, the time slice should be small enough so that a looping program does not dominate processor time and an activity level." />
|
||
|
|
<meta name="description" content="The priorities for jobs that run in batch environments should normally be lower than priorities for jobs in interactive environments. Also, the time slice should be small enough so that a looping program does not dominate processor time and an activity level." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksmngjbcmntsk.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="rzaksjobprioritytip" />
|
||
|
|
<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>Tips for setting job priorities</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksjobprioritytip"><a name="rzaksjobprioritytip"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Tips for setting job priorities</h1>
|
||
|
|
<div><p>The priorities for jobs that run in batch environments should normally
|
||
|
|
be lower than priorities for jobs in interactive environments. Also, the time
|
||
|
|
slice should be small enough so that a looping program does not dominate processor
|
||
|
|
time and an activity level.</p>
|
||
|
|
<div class="p">You may want the priority for the system operator's jobs to be higher
|
||
|
|
than priorities of other jobs so that the system operator can effectively
|
||
|
|
respond to system needs.</div>
|
||
|
|
<div class="section">If you use QCTL as the controlling subsystem, the operator is automatically
|
||
|
|
running at a higher priority after signing on at the console. This is because
|
||
|
|
QCTL routes the console job using the QCTL class, which specifies a higher
|
||
|
|
priority. <p>Another way that you can set up your system so that the operator
|
||
|
|
can run at a higher priority would be to do the following:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li><span>Add a routing entry to the subsystem with unique routing data and
|
||
|
|
specify the QSYS/QCTL class.</span></li>
|
||
|
|
<li><span>Create a new job description for the operator, specifying the same
|
||
|
|
unique routing data that you used in the routing entry.</span></li>
|
||
|
|
<li><span>Change the operator's user profile to specify the new job description.</span></li>
|
||
|
|
<li><span>Now when the operator signs on to that subsystem, the job will
|
||
|
|
route using the QCTL class, which specifies a higher priority than the class
|
||
|
|
used by normal interactive jobs.</span></li>
|
||
|
|
</ol>
|
||
|
|
<div class="section">The job run priority is the highest priority at which any thread
|
||
|
|
in the job may run. Each thread may have it's own thread priority that is
|
||
|
|
lower than the job priority. The Change Job (<span class="cmdname">CHGJOB</span>) command
|
||
|
|
will change only the job priority. The Change Job (QWTCHGJB) API can be used
|
||
|
|
to change either the job priority or a thread priority.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksmngjbcmntsk.htm" title="This information discusses the most common tasks that you can perform with jobs. It provides you with instructions for both iSeries Navigator (where available) and the character-based interface.">Common job tasks</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|