76 lines
6.8 KiB
HTML
76 lines
6.8 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="How jobs are taken from multiple job queues" />
|
||
|
|
<meta name="abstract" content="A subsystem processes jobs from a job queue based on sequence number. A subsystem can have more than one job queue entry and can therefore allocate more than one job queue." />
|
||
|
|
<meta name="description" content="A subsystem processes jobs from a job queue based on sequence number. A subsystem can have more than one job queue entry and can therefore allocate more than one job queue." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjobqueue.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksorderedlist.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowjobqueuewrk.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobqhowtaken.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobqentryabout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobqhowallocated.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobqdoineed2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobqsecurity.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="howjobsaretakenfrommultiplejobqueues" />
|
||
|
|
<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>How jobs are taken from multiple job queues</title>
|
||
|
|
</head>
|
||
|
|
<body id="howjobsaretakenfrommultiplejobqueues"><a name="howjobsaretakenfrommultiplejobqueues"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">How jobs are taken from multiple job queues</h1>
|
||
|
|
<div><p>A subsystem processes jobs from a job queue based on sequence number.
|
||
|
|
A subsystem can have more than one job queue entry and can therefore allocate
|
||
|
|
more than one job queue. </p>
|
||
|
|
<p> The maximum number of jobs from a queue is specified by
|
||
|
|
the Maximum active jobs <span class="parmname">MAXACT</span> parameter on the Add Job
|
||
|
|
Queue Entry (<span class="cmdname">ADDJOBQE</span>) or the Change Job Queue Entry (<span class="cmdname">CHGJOBQE</span>)
|
||
|
|
commands. You can also control how many jobs of each priority can be active
|
||
|
|
by using the Maximum active priority <span class="parmname">MAXACTx</span> parameters.
|
||
|
|
For example, if MAXACT=10, MAXACT5=2, and there are three jobs on the job
|
||
|
|
queue at priority level 5, then only two of them can become active at any
|
||
|
|
given time.</p>
|
||
|
|
<p>The subsystem processes jobs from the job queue with the lowest sequence
|
||
|
|
number first. When all of the jobs that are on the job queue have been processed,
|
||
|
|
or when the maximum number of jobs from the queue is reached, the subsystem
|
||
|
|
processes jobs from the queue with the next higher sequence number.</p>
|
||
|
|
<p>The sequence continues until the subsystem has processed all of the available
|
||
|
|
job queue entries or until the subsystem has reached its limit of jobs that
|
||
|
|
can be running or waiting in the subsystem. The number of jobs that can be
|
||
|
|
running or waiting is determined by the Maximum active jobs (<span class="parmname">MAXACT</span>)
|
||
|
|
parameter in the subsystem description. In some cases the sequence is interrupted
|
||
|
|
as jobs end or are transferred. Creating, holding, and releasing job queues
|
||
|
|
can also change the sequence of job queues processed.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksaboutjobqueue.htm" title="A job queue contains an ordered list of jobs waiting to be processed by a subsystem. The job queue is the first place that a submitted batch job goes before becoming active in a subsystem. The job is held here until a number of factors are met.">Job queues</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaksorderedlist.htm" title="The ordered list refers to the order in which jobs appear on the job queue. The availability, priority, and the date and time values help determine the order of jobs on the job queue.">Ordered list</a></div>
|
||
|
|
<div><a href="rzakshowjobqueuewrk.htm" title="Job queues are allocated by a subsystem via the job queue entry. Jobs can be placed on a job queue even if the subsystem has not been started. When the subsystem is started, it processes the jobs on the queue.">How a job queue works</a></div>
|
||
|
|
<div><a href="rzaksjobqhowtaken.htm" title="Different factors determine how the jobs are selected from a job queue and started.">How jobs are taken from a job queue</a></div>
|
||
|
|
<div><a href="rzaksjobqentryabout.htm" title="A job queue entry identifies a job queue from which jobs are selected for running in the subsystem. There are five parameters in the job queue entry that control how the job queue should be handled.">Job queue entry</a></div>
|
||
|
|
<div><a href="rzaksjobqhowallocated.htm" title="A job queue can be associated with several subsystems but it can only be allocated to one subsystem at a time. When the subsystem is started, the subsystem monitor tries to allocate each job queue defined in the subsystem job queue entries.">How job queues are allocated to a subsystem</a></div>
|
||
|
|
<div><a href="rzaksjobqdoineed2.htm" title="In many cases, using QBATCH as the only job queue with the default of one active job will be adequate for your needs. If this is not adequate, you might want to have multiple job queues so that some job queues are active during normal working hours, some are for special purposes, and some are active after normal working hours.">Multiple job queues</a></div>
|
||
|
|
<div><a href="rzaksjobqsecurity.htm" title="You can maintain a level of security with your job queue by authorizing only certain persons (user profiles) to that job queue. In general, there are three ways that a user can become authorized to control a job queue (for example, hold or release the job queue).">Job queue security</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|