88 lines
7.3 KiB
HTML
88 lines
7.3 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="Job queues" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksconcepts.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="rzakshowjobsaretakenfrommultiplejobqueues.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobqsecurity.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/wm1.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="rzaksaboutjobqueue" />
|
||
|
|
<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>Job queues</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksaboutjobqueue"><a name="rzaksaboutjobqueue"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Job queues</h1>
|
||
|
|
<div><p>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. </p>
|
||
|
|
<p>In order for jobs on a job queue to be processed, there must be an active
|
||
|
|
subsystem that is accepting work from that job queue. When a subsystem starts,
|
||
|
|
it attempts to allocate the job queues that it is configured to accept work
|
||
|
|
from, and it must successfully allocate a job queue in order to process jobs
|
||
|
|
from that job queue. Therefore, while one subsystem can process jobs from
|
||
|
|
multiple job queues, only one subsystem can process jobs from a particular
|
||
|
|
job queue at a time.</p>
|
||
|
|
<p>Subsystems select jobs from job queues in priority order, within limits
|
||
|
|
that can be configured for each priority. Each job has a job queue priority
|
||
|
|
that can be managed when the job is on the job queue through job properties.
|
||
|
|
A base set of job queues is provided with your system. In addition, you can
|
||
|
|
create additional job queues that you need.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> APIs, such as Open List of Job Queues (<span class="apiname">QSPOLJBQ</span>)
|
||
|
|
and Retrieve Job Queue Information (<span class="apiname">QSPRJOBQ</span>), can be called
|
||
|
|
to get information about job queues.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksorderedlist.htm">Ordered list</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakshowjobqueuewrk.htm">How a job queue works</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobqhowtaken.htm">How jobs are taken from a job queue</a></strong><br />
|
||
|
|
Different factors determine how the jobs are selected from a job queue and started.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobqentryabout.htm">Job queue entry</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobqhowallocated.htm">How job queues are allocated to a subsystem</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobqdoineed2.htm">Multiple job queues</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakshowjobsaretakenfrommultiplejobqueues.htm">How jobs are taken from multiple job queues</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobqsecurity.htm">Job queue security</a></strong><br />
|
||
|
|
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).</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksconcepts.htm" title="Whether you are new to work management or have been using work management tools for years, you will find something useful in the Concepts section of the Work management topic collection.">Concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../apis/wm1.htm">Work management APIs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|