104 lines
8.3 KiB
HTML
104 lines
8.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="Batch jobs" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobtypeoverview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutautostartjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutcommunicationjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksinteractivejob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksprestarttype.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksreaderandwriterjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksserverjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssystemjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowabatchjobstarts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksspawnbatchjob.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="rzaksbatchjob" />
|
||
|
|
<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>Batch jobs</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksbatchjob"><a name="rzaksbatchjob"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Batch jobs</h1>
|
||
|
|
<div><p>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. </p>
|
||
|
|
<p> Batch jobs run in the system background, freeing the user who submitted
|
||
|
|
the job to do other work. Several batch jobs can be active at the same time.</p>
|
||
|
|
<p>The following list describes the different kinds of batch jobs:</p>
|
||
|
|
<dl><dt class="dlterm">Simple batch job</dt>
|
||
|
|
<dd>The simple batch job is a job that is submitted to a job queue. It waits
|
||
|
|
in line with other batch jobs and is processed according to its priority and
|
||
|
|
sequence number.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Batch immediate job</dt>
|
||
|
|
<dd>A batch immediate job is a batch job that was started with many of the
|
||
|
|
attributes of its parent job. The job runs in the same subsystem as the parent
|
||
|
|
job. <span>(This is accomplished by using the spawn() API.) </span>Because the
|
||
|
|
job copies attributes from the parent job and does not go through a job queue,
|
||
|
|
it can start faster than jobs submitted to a job queue.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Batch MRT job</dt>
|
||
|
|
<dd>A batch MRT job is a multiple requester terminal (MRT) job. MRT jobs are
|
||
|
|
S/36 Environment jobs that act like servers, allowing other S/36 Environment
|
||
|
|
jobs to attach to them in order to run an MRT procedure.</dd>
|
||
|
|
</dl>
|
||
|
|
<dl><dt class="dlterm">Batch print job</dt>
|
||
|
|
<dd>Batch print jobs track the printer output files (also called spooled files)
|
||
|
|
that were created by a job whose current user profile is different from the
|
||
|
|
user profile that it was started under.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>Batch jobs can be started when a user:</p>
|
||
|
|
<ul><li>Causes a job to be placed in a job queue </li>
|
||
|
|
<li>Issues a communication program start request </li>
|
||
|
|
<li>Starts a subsystem with a prestart job</li>
|
||
|
|
<li>Uses the spawn() API</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakshowabatchjobstarts.htm">How a batch job starts</a></strong><br />
|
||
|
|
When a user submits a batch job, the job gathers information from several system objects before it is placed on a job queue.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksspawnbatchjob.htm">Spawn batch jobs</a></strong><br />
|
||
|
|
<dfn class="term">Spawn</dfn> is a function that creates a new
|
||
|
|
job process (child process) that inherits many attributes of the calling process
|
||
|
|
(parent process). A new program is specified and starts running in the child
|
||
|
|
process. When you spawn a batch job you are using a parent job to pass along
|
||
|
|
arguments and environment variables to the child job. The spawn() API uses
|
||
|
|
batch immediate jobs, prestart jobs, or prestart batch jobs.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjobtypeoverview.htm" title="The iSeries server processes several different types of jobs.">Job types</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaksaboutautostartjob.htm" title="An autostart job is a batch job doing repetitive work, one-time initialization work that is associated with a particular subsystem, initializes functions for an application, or provides centralized service functions for other jobs in the same subsystem. An autostart job in the controlling subsystem can be used to start other subsystems (as does the IBM-supplied controlling subsystem). The autostart jobs associated with a subsystem are automatically started each time the subsystem is started.">Autostart jobs</a></div>
|
||
|
|
<div><a href="rzaksaboutcommunicationjobs.htm" title="A communications job is a batch job that is started by a program start request from a remote system. Job processing involves a communication request and appropriate specifications.">Communication jobs</a></div>
|
||
|
|
<div><a href="rzaksinteractivejob.htm" title="An interactive job is a job that starts when a user signs on to a display station and ends when the user signs off. For the job to run, the subsystem searches for the job description, which can be specified in the workstation entry or the user profile.">Interactive jobs</a></div>
|
||
|
|
<div><a href="rzaksprestarttype.htm" title="A prestart job is a batch job that starts running before a work request is received. The prestart jobs are started before any other types of jobs in a subsystem. Prestart jobs are different from other jobs because they use prestart job entries (part of the subsystem description) to determine which program, class, and storage pool to use when they are started.">Prestart jobs</a></div>
|
||
|
|
<div><a href="rzaksreaderandwriterjob.htm" title="A reader job is a spooled input job, and a writer job is a spooled output job.">Reader and writer jobs</a></div>
|
||
|
|
<div><a href="rzaksserverjobs.htm" title="Server jobs are jobs that run continuously in the background on the iSeries system.">Server jobs</a></div>
|
||
|
|
<div><a href="rzakssystemjobs.htm" title="System jobs are created by the operating system to control system resources and perform system functions. System jobs run when the iSeries server starts or when an independent disk pool is varied on. These jobs perform a variety of tasks from starting the operating system, to starting and ending subsystems, to scheduling jobs.">System jobs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|