110 lines
8.5 KiB
HTML
110 lines
8.5 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="Multiple job queues" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<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="rzakshowjobsaretakenfrommultiplejobqueues.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="rzaksjobqdoineed2" />
|
||
|
|
<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>Multiple job queues</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksjobqdoineed2"><a name="rzaksjobqdoineed2"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Multiple job queues</h1>
|
||
|
|
<div><p>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. </p>
|
||
|
|
<div class="p">For example, you can designate different job queues for:<dl><dt class="dlterm">Long-running jobs so you can control how many jobs are active at the same
|
||
|
|
time</dt>
|
||
|
|
<dd>You might also want these jobs to use a lower priority than the other
|
||
|
|
batch jobs.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Overnight jobs that are inconvenient to run during normal working hours</dt>
|
||
|
|
<dd>For example, to run a Reorganize Physical File Member (RGZPFM) command
|
||
|
|
on a large database file requires an exclusive lock on the file. This means
|
||
|
|
that other users cannot access the file while this operation is taking place.
|
||
|
|
Additionally, this operation can take a long time. It can be more efficient
|
||
|
|
to place this job on a job queue for jobs which run during off-shift hours.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">High-priority jobs</dt>
|
||
|
|
<dd>You might want to have a job queue to which all high-priority work is
|
||
|
|
sent. You can then ensure that this work is completed rapidly and is not delayed
|
||
|
|
by lower-priority jobs.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Jobs that are directed to particular resource requirement such as diskette
|
||
|
|
or tape </dt>
|
||
|
|
<dd>Such a job queue needs a <span class="parmname">MAXACT</span> parameter of 1 in
|
||
|
|
the job queue entry of the subsystem description so that only one job at a
|
||
|
|
time uses the resource.<div class="p">For example, if a tape is used for several jobs,
|
||
|
|
all jobs using tape are be placed on a single job queue. One job at a time
|
||
|
|
are then selected from the job queue. This ensures that no two jobs compete
|
||
|
|
for the same device at the same time. If this happens, one of the jobs ends
|
||
|
|
with an allocation error.<div class="note"><span class="notetitle">Note:</span> Tape output cannot be spooled.</div>
|
||
|
|
</div>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Programmer work</dt>
|
||
|
|
<dd>You might want to have a job queue to handle programmer work or types
|
||
|
|
of work that can be held while production work is being run.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Sequential running of a series of jobs</dt>
|
||
|
|
<dd>You can have an application in which one job is dependent on the completion
|
||
|
|
of another job. If you place these jobs on a job queue that selects and runs
|
||
|
|
one job at a time, this ensures the running sequence of these jobs.<p>If a
|
||
|
|
job requires exclusive control of a file, you might want to place it on a
|
||
|
|
job queue when the queue is the only one active on the server, such as during
|
||
|
|
the night or on a weekend.</p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div class="p"> If you use multiple job queues, you will find that control of the various
|
||
|
|
job queues is a main consideration. You will typically want to control: <ul><li>How many job queues exist</li>
|
||
|
|
<li>How many job queues are active in a particular subsystem at the same time</li>
|
||
|
|
<li>How many active jobs can be selected from a particular job
|
||
|
|
queue at a particular time</li>
|
||
|
|
<li>How many jobs can be active in a subsystem at a particular time</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</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="rzakshowjobsaretakenfrommultiplejobqueues.htm" title="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.">How jobs are taken from 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>
|