58 lines
4.3 KiB
HTML
58 lines
4.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="A job's life: the job enters the job queue" />
|
||
|
|
<meta name="abstract" content="Job queues are work entry points for batch jobs to enter the system. They can be thought of as "waiting rooms" for a subsystem." />
|
||
|
|
<meta name="description" content="Job queues are work entry points for batch jobs to enter the system. They can be thought of as "waiting rooms" for a subsystem." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblife.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifesubmit.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifesbs.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="rzaksjoblifejobq" />
|
||
|
|
<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>A job's life: the job enters the job queue</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksjoblifejobq"><a name="rzaksjoblifejobq"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">A job's life: the job enters the job queue</h1>
|
||
|
|
<div><p><dfn class="term">Job queues</dfn> are work entry points for batch jobs to
|
||
|
|
enter the system. They can be thought of as "waiting rooms" for a subsystem. </p>
|
||
|
|
<p>A number of factors affect when the job is pulled off the job queue into
|
||
|
|
the subsystem, such as the job priority on the job queue, the sequence number
|
||
|
|
of the job queue, and the maximum active jobs. When all of these factors work
|
||
|
|
together, the job will be pulled off the job queue to start running in the
|
||
|
|
subsystem. </p>
|
||
|
|
<p>When the job enters the job queue, it is available to a subsystem that
|
||
|
|
has the job queue allocated to it. Because subsystems can have more than one
|
||
|
|
job queue feeding into them (however, job queues cannot feed into more than
|
||
|
|
one subsystem), a sequence number in the subsystem determines when the subsystem
|
||
|
|
processes a job queue. The subsystem looks at the sequence number of the job
|
||
|
|
queue before the job priority of the jobs in the job queue. The subsystem
|
||
|
|
uses the priority on the job queue to determine when a job can enter relative
|
||
|
|
to other jobs on the job queue. The job priority and the maximum active jobs
|
||
|
|
determine when a job enters the subsystem. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjoblife.htm" title="To understand the basics of iSeries work management, follow a simple batch job as it moves through the system.">A job's life</a></div>
|
||
|
|
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzaksjoblifesubmit.htm" title="When a job is submitted, it is created and enters the system. At this time, the attributes are given to the job.">A job's life: submit a job</a></div>
|
||
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzaksjoblifesbs.htm" title="Subsystems are operating environments where the system manages the resources that jobs use and controls the jobs that run within them. After jobs are running in the subsystem, the subsystem job carries out user requests on a job such as holding, releasing, and ending a job. When the job enters the subsystem it becomes active.">A job's life: the job enters the subsystem</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|