79 lines
5.5 KiB
HTML
79 lines
5.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="A job's life" />
|
||
|
|
<meta name="abstract" content="To understand the basics of iSeries work management, follow a simple batch job as it moves through the system." />
|
||
|
|
<meta name="description" content="To understand the basics of iSeries work management, follow a simple batch job as it moves through the system." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakswmintro.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifesubmit.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifejobq.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifesbs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifemp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblifeoutq.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="rzaksjoblife" />
|
||
|
|
<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</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksjoblife"><a name="rzaksjoblife"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">A job's life</h1>
|
||
|
|
<div><p>To understand the basics of iSeries™ work management, follow a simple
|
||
|
|
batch job as it moves through the system. </p>
|
||
|
|
<p>The life of a simple batch job begins when you submit it to the system.
|
||
|
|
The job is then sent to a job queue where it waits to enter a subsystem where
|
||
|
|
it can run. After the job moves to the subsystem it is allocated memory in
|
||
|
|
which to run. The printer output file (also called spooled files) is then
|
||
|
|
sent to the output queue to await further instruction on what to do (for example,
|
||
|
|
printing). While not every job follows this exact path, you can better understand
|
||
|
|
how other work is completed on the system by learning more about this typical
|
||
|
|
job life cycle. </p>
|
||
|
|
<p><span class="menucascade"><span class="uicontrol">Submit the job</span> > <span class="uicontrol">Job enters
|
||
|
|
the job queue</span> > <span class="uicontrol">Job enters the subsystem</span> > <span class="uicontrol">The
|
||
|
|
memory pool allocates memory to the subsystem</span> > <span class="uicontrol">The job
|
||
|
|
finishes and moves to the output queue</span></span></p>
|
||
|
|
<p></p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ol>
|
||
|
|
<li class="olchildlink"><a href="rzaksjoblifesubmit.htm">A job's life: submit a job</a><br />
|
||
|
|
When a job is submitted, it is created and enters the system. At this time, the attributes are given to the job.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaksjoblifejobq.htm">A job's life: the job enters the job queue</a><br />
|
||
|
|
<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. </li>
|
||
|
|
<li class="olchildlink"><a href="rzaksjoblifesbs.htm">A job's life: the job enters the subsystem</a><br />
|
||
|
|
<dfn class="term">Subsystems</dfn> 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.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaksjoblifemp.htm">A job's life: the subsystem uses memory from the memory pool to run the job</a><br />
|
||
|
|
<dfn class="term">Memory</dfn> is a resource from the memory pool that the
|
||
|
|
subsystem uses to run the job. The amount of memory in a memory pool, as well
|
||
|
|
as how many other jobs are competing for memory, affect how efficiently a
|
||
|
|
job runs.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaksjoblifeoutq.htm">A job's life: the job finishes and moves to the output queue</a><br />
|
||
|
|
A job's printer output (also called spooled files) is sent to an output queue where it waits to be sent to a printer or file. The output queue is similar to the job queue in that it controls how the output is made available to the printer. The output queue allows the user to control what files are printed first.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakswmintro.htm" title="Work management supports the commands and internal functions necessary to control system operation and the daily workload on the system. In addition, work management contains the functions that you need to distribute resources for your applications so that your system can handle your applications.">Introduction to work management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|