92 lines
6.8 KiB
HTML
92 lines
6.8 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="task" />
|
|
<meta name="DC.Title" content="Submit a batch job" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksmanagebatchjobs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksinldfX.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksidfocX.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowabatchjobstarts.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzalu/rzaluqprtjob.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowjobsrschdsbmjob.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="submitbatchjob" />
|
|
<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>Submit a batch job</title>
|
|
</head>
|
|
<body id="submitbatchjob"><a name="submitbatchjob"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Submit a batch job</h1>
|
|
<div><p>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.</p>
|
|
<div class="section"><strong>Command</strong>: Submit Job (<span class="cmdname">SBMJOB</span>)<p><strong>Command</strong>:
|
|
Submit Database Job (<span class="cmdname">SBMDBJOB</span>)</p>
|
|
<p> </p>
|
|
<p>The difference
|
|
in these commands is the source of the job:</p>
|
|
<div class="p"><ul><li>The <span class="cmdname">SBMJOB</span> command submits a job to a batch job queue
|
|
by specifying a job description and by specifying a CL command or request
|
|
data, or specifying routing data to run a program. If you want to run a single
|
|
CL command in a the batch job, use the CMD parameter on SBMJOB, which does
|
|
syntax checking and allows prompting.</li>
|
|
<li>The <span class="cmdname">SBMDBJOB</span> command can be used to submit
|
|
a job to a batch job queue from a database file. For these jobs, the job description
|
|
comes from the BCHJOB statement in the input stream.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div class="example"><strong>Example</strong>: In the following example, the <span class="cmdname">SBMJOB</span> command
|
|
submits a job named WSYS, using the job description QBATCH, to the job queue
|
|
QBATCH. The CMD parameter gives the CL command that will run in the job. <blockquote><pre>SBMJOB JOBD(QBATCH) JOB(WSYS) JOBQ(QBATCH) CMD(WRKSYSSTS)</pre>
|
|
</blockquote>
|
|
<div class="note"><span class="notetitle">Note:</span> If you get a message that the job was not submitted, you can display
|
|
the job log spooled file to find errors. Use the <span class="cmdname">WRKJOB</span> command.
|
|
Specify the job that was not scheduled, select option 4 for spooled files.
|
|
Display the job log spooled file to find the errors.</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzaksinldfX.htm">Use an inline data file</a></strong><br />
|
|
An inline data file is a data file that is included as part of
|
|
a batch job when the job is read by a reader or a submit jobs command. You
|
|
use <span class="cmdname">SBMDBJOB</span> or <span class="cmdname">STRDBRDR</span> to queue up
|
|
a CL batch stream (stream of CL commands to be executed or run). That CL
|
|
batch stream can include data to be placed into "temporary" files (inline
|
|
files). When the job ends, the inline files are deleted.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaksidfocX.htm">Open considerations for inline data files</a></strong><br />
|
|
The following considerations apply to opening inline data files:</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksmanagebatchjobs.htm" title="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.">Manage batch jobs</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakshowabatchjobstarts.htm" title="When a user submits a batch job, the job gathers information from several system objects before it is placed on a job queue.">How a batch job starts</a></div>
|
|
<div><a href="rzakshowjobsrschdsbmjob.htm" title="This character-based interface command controls the time a job is released in the job queue. It is an easy way to schedule a job that only needs to run once. It allows you to use many of the job attributes defined for your current job.">The submit job command</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> |