71 lines
5.5 KiB
HTML
71 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="How a batch job starts" />
|
|
<meta name="abstract" content="When a user submits a batch job, the job gathers information from several system objects before it is placed on a job queue." />
|
|
<meta name="description" content="When a user submits a batch job, the job gathers information from several system objects before it is placed on a job queue." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbatchjob.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssubmitbatchjob.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksstartbatchjob.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzalu/rzaluqprtjob.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="howabatchjobstarts" />
|
|
<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 a batch job starts</title>
|
|
</head>
|
|
<body id="howabatchjobstarts"><a name="howabatchjobstarts"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">How a batch job starts</h1>
|
|
<div><p>When a user submits a batch job, the job gathers information from
|
|
several system objects before it is placed on a job queue.</p>
|
|
<ol><li>A user submits a job.</li>
|
|
<li>The job searches for job attributes. If the job attributes are not found
|
|
on the Submit Job (<span class="cmdname">SBMJOB</span>) command, the job looks in the
|
|
job description (specified on the <span class="cmdname">SBMJOB</span> command), the
|
|
current user's user profile, and the currently active job (the job issuing
|
|
the <span class="cmdname">SBMJOB</span> command). <div class="note"><span class="notetitle">Note:</span> Similar to interactive job initiation,
|
|
you can specify in the job description to use the user profile. The user profile
|
|
can specify to use a system value to find certain job attributes.</div>
|
|
</li>
|
|
<li>Once the job has all of its attributes, it resides on the job queue.</li>
|
|
<li>When the subsystem is ready to handle a job, it looks for jobs in the
|
|
job queues (those that the subsystem has allocated).</li>
|
|
<li>Then, like interactive job processing, the subsystem checks the job description
|
|
for the routing data.</li>
|
|
<li>The subsystem uses the routing data to find a routing entry. The routing
|
|
entry provides information about which pool the job will use, which routing
|
|
program will be used, and from which class the job will get its run-time attributes.</li>
|
|
<li>After this information is obtained, the routing program is run. If you
|
|
use QCMD, QCMD will carry out the <span class="cmdname">SBMJOB</span> command.
|
|
It runs the command specified on the <span class="parmname">CMD</span> or <span class="parmname">RQSDTA</span> parameter. </li>
|
|
</ol>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksbatchjob.htm" title="A batch job is a predefined group of processing actions submitted to the system to be performed with little or no interaction between the user and the system. Jobs that do not require user interaction to run can be processed as batch jobs. A batch job typically is a low priority job and can require a special system environment in which to run.">Batch jobs</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzakssubmitbatchjob.htm" title="Since batch jobs are typically low priority jobs that require a special system environment in which to run (such as running at night) they are placed in batch job queues. In the job queue the batch job receives a run time schedule and a priority. To submit a job to a batch job queue, you use the character-based interface and one of two commands.">Submit a batch job</a></div>
|
|
<div><a href="rzaksstartbatchjob.htm" title="Occasionally you might need to force a job to start immediately. While moving the job to a job queue that is not busy is the most efficient method to accomplish this, there are some other methods that you can use.">Start a batch job that is waiting in the job queue</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../rzalu/rzaluqprtjob.htm" title="A QPRTJOB job is a job that spooled files are associated with when the current job's user name is not the same as the user profile currently running. System jobs can change to run under a user's profile in order for a user to obtain ownership of the spooled file instead of the system job.">QPRTJOB job</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |