79 lines
7.4 KiB
HTML
79 lines
7.4 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="Autostart jobs" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobtypeoverview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbatchjob.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="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="rzaksaboutautostartjob" />
|
||
|
|
<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>Autostart jobs</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksaboutautostartjob"><a name="rzaksaboutautostartjob"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Autostart jobs</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>Since all autostart jobs are started when the subsystem starts, the value
|
||
|
|
specified for the maximum number of jobs in the subsystem does not prevent
|
||
|
|
the autostart jobs from starting. If the maximum number of jobs in the subsystem
|
||
|
|
is exceeded, no other jobs can be started. When enough autostart jobs have
|
||
|
|
completed so that the number of jobs running is below the maximum activity
|
||
|
|
level, other jobs in the subsystem can start. </p>
|
||
|
|
<p>The job description that is used for an autostart job is specified using
|
||
|
|
the Add Autostart Job Entry (<span class="cmdname">ADDAJE</span>) command. When the
|
||
|
|
subsystem is started, the job operates under the user profile name in the
|
||
|
|
specified job description. You may not specify the job description which contains
|
||
|
|
USER(*RQD). Because the autostart job operates under the user
|
||
|
|
profile that is specified by the job description, you need to control who
|
||
|
|
is allowed to change the job description.</p>
|
||
|
|
<p>If more than one autostart job is specified for a subsystem, all autostart
|
||
|
|
jobs are started immediately rather than one followed by another. If the maximum
|
||
|
|
number of jobs of the subsystem is exceeded, no other jobs can be started
|
||
|
|
in the subsystem until enough autostart jobs have completed so that the number
|
||
|
|
of jobs running is below the maximum activity level.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<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="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><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>
|