128 lines
11 KiB
HTML
128 lines
11 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="Schedule job dependencies" />
|
||
|
|
<meta name="abstract" content="Set up jobs or groups of jobs that are dependent on each other. You can select the type of dependency that reflects how jobs are processed in your environment." />
|
||
|
|
<meta name="description" content="Set up jobs or groups of jobs that are dependent on each other. You can select the type of dependency that reflects how jobs are processed in your environment." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsmanagejobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsschedulejob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsnewjobgroup.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajspredefinedschedules.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsscheduletempjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsworkflowabout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsmonitor.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsmonitormsg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajslocaldata.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajs5custapp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajswrkwinotification.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajs8library.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajs9command.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaksajsjobdependencies" />
|
||
|
|
<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>Schedule job dependencies</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksajsjobdependencies"><a name="rzaksajsjobdependencies"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Schedule job dependencies</h1>
|
||
|
|
<div><p>Set up jobs or groups of jobs that are dependent on each other.
|
||
|
|
You can select the type of dependency that reflects how jobs are processed
|
||
|
|
in your environment.</p>
|
||
|
|
<div class="section"><p>The Advanced Job Scheduler allows you to set up dependencies that
|
||
|
|
reflect how jobs are processed in your environment. Dependencies determine
|
||
|
|
when a job or group of jobs can run. You can select to have all dependencies
|
||
|
|
met before a job can run, or you can have at least one dependency met before
|
||
|
|
the job can run. Dependencies include the following:</p>
|
||
|
|
<ul><li> <strong>Job dependencies</strong> <p>Job dependencies refer to predecessor and
|
||
|
|
successor relationships for jobs. Predecessor jobs are those that must run
|
||
|
|
before the successor job will run. A successor job is a job that runs after
|
||
|
|
all the predecessor jobs have been processed. There can be multiple successor
|
||
|
|
jobs for a single predecessor job as well as multiple predecessor jobs for
|
||
|
|
a single successor job. In addition, you can specify that a dependent job
|
||
|
|
be skipped if its predecessors and successors run on a day that the dependent
|
||
|
|
job is not scheduled to run.</p>
|
||
|
|
</li>
|
||
|
|
<li> <strong>Active dependencies</strong> <p>Active dependencies are lists of jobs that
|
||
|
|
cannot be active when the selected job is to be submitted. If any of the jobs
|
||
|
|
are active, the Advanced Job Scheduler will not let the specified job run.
|
||
|
|
The selected job will be delayed until all the jobs in the list are inactive.</p>
|
||
|
|
</li>
|
||
|
|
<li> <strong>Resource dependencies</strong> <p>Resource dependencies are based on several
|
||
|
|
things. Each type that follows describes the areas that are checked. Following
|
||
|
|
are the types of resource dependencies:</p>
|
||
|
|
<dl><dt class="dlterm">File</dt>
|
||
|
|
<dd>The job is dependent on the existence or non-existence of a file and whether
|
||
|
|
it meets the specified allocation level to be processed. It can also check
|
||
|
|
whether records are present before the job is processed. For instance, JOBA
|
||
|
|
can be set up so that it will only run when file ABC exists, and the file
|
||
|
|
can be allocated exclusively and if records are present in the file.</dd>
|
||
|
|
<dt class="dlterm">Object</dt>
|
||
|
|
<dd>The job is dependent on the existence or non-existence of a QSYS type
|
||
|
|
object and whether it meets the specified allocation level to be processed.
|
||
|
|
For instance, JOBA can be set up so that it will only run when data area XYZ
|
||
|
|
exists. The job can also be dependent on the existence or non-existence of
|
||
|
|
an object found in the integrated file system. If the dependency is based
|
||
|
|
on any object in the path, end the integrated file system path with a forward
|
||
|
|
slash '/'.</dd>
|
||
|
|
<dt class="dlterm">Hardware configuration</dt>
|
||
|
|
<dd>The job is dependent on the existence or non-existence of a hardware configuration
|
||
|
|
and its status to be processed. For instance, JOBA can be set up so that it
|
||
|
|
will only run when device TAP01 exists and has a status of Available.</dd>
|
||
|
|
<dt class="dlterm">Network file</dt>
|
||
|
|
<dd>The job is dependent on the status of a network file in order to be processed.</dd>
|
||
|
|
<dt class="dlterm">Subsystem</dt>
|
||
|
|
<dd>The job is dependent on the status of a subsystem in order to be processed.</dd>
|
||
|
|
</dl>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>To work with job dependencies, follow these steps:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li><span>Open <span class="uicontrol">Work Management</span> from your iSeries Navigator
|
||
|
|
window.</span></li>
|
||
|
|
<li><span>Expand <span class="uicontrol">Advanced Job Scheduler</span>.</span></li>
|
||
|
|
<li><span>Click <span class="uicontrol">Scheduled Jobs</span>.</span></li>
|
||
|
|
<li><span>Right-click the <span class="uicontrol">Job Name</span> whose dependencies
|
||
|
|
you want to work with.</span></li>
|
||
|
|
<li><span>Select one of the following: <span class="uicontrol">Job Dependencies, Active
|
||
|
|
Dependencies or Resource Dependencies</span>. Refer to the online help
|
||
|
|
for more information.</span></li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksajsmanagejobs.htm" title="The following information will help you manage the Advanced Job Scheduler. First you need to schedule jobs using the Advanced Job Scheduler. Then, use the rest of the tasks to manage the jobs.">Manage the Advanced Job Scheduler</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><img src="./delta.gif" alt="Start of change" /><a href="rzaksajsworkflowabout.htm" title="As of V5R4, the Work Flow Manager lets you define units of work that consist of automated or manual steps. These units of work can then be scheduled or run interactively. The Work Flow Manager is located in the Advanced Job Scheduler container in the iSeries Navigator interface.">The Work Flow Manager</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzaksajsschedulejob.htm" title="Schedule a job and specify the commands that are associated with the job. You can also specify starting and ending commands to run a special version of a scheduled job.">Create and schedule a job</a></div>
|
||
|
|
<div><a href="rzaksajsnewjobgroup.htm" title="Set up and schedule a series of jobs that run consecutively in a specified order. Jobs within a job group require completion before the next job is submitted for processing.">Create and schedule a job group</a></div>
|
||
|
|
<div><a href="rzaksajspredefinedschedules.htm" title="Create schedules that contain information needed to schedule a job or calculate exception dates within a holiday calendar.">Predefined schedules</a></div>
|
||
|
|
<div><a href="rzaksajsscheduletempjob.htm" title="At times it might be necessary to run a scheduled job now or in the future in addition to its normal schedule. Use the Submit Job using Job Scheduler (SBMJOBJS) command, option 7 from Work with Jobs display, or the Run option from iSeries Navigator. It might also be necessary to process only a portion of the commands in the command list when setting up this special run.">Create a temporary scheduled job</a></div>
|
||
|
|
<div><a href="rzaksajsmonitor.htm" title="Use Advanced Job Scheduler to view a job or a job group's history or status. You can also set up the activity retention, which is how long you want to retain the activity records for a job.">Monitor job activity for the Advanced Job Scheduler</a></div>
|
||
|
|
<div><a href="rzaksajsmonitormsg.htm" title="Add message identifiers to any command within the command list of a job to monitor messages.">Monitor for messages with Advanced Job Scheduler</a></div>
|
||
|
|
<div><a href="rzaksajslocaldata.htm" title="A local data area is a portion of space that is allocated for a job. Not all jobs use their local data area but some do. Each command within a job has access to the job's local data area. You might want to use a local data area if you are scheduling a job that previously required you to manually specify additional parameters. Use the local data area to specify the additional parameters so you do not need to manually specify them each time the job starts.">Create and work with local data area</a></div>
|
||
|
|
<div><a href="rzaksajs5custapp.htm" title="Applications are jobs that are grouped for processing. They are broader than job groups and do not necessarily process sequentially. Jobs in applications can process simultaneously and one job does not need to wait for another to process. All jobs within the application can be worked with and can have their own set of job defaults. Job controls are the defaults assigned to a job as you add it to the job scheduler as well as defaults used when the job is submitted.">Create and work with applications/job controls</a></div>
|
||
|
|
<div><a href="rzaksajswrkwinotification.htm" title="This information describes how to use the notification function of Advanced Job Scheduler.">Work with notification</a></div>
|
||
|
|
<div><a href="rzaksajs8library.htm" title="Library lists are user-defined lists of libraries that are used by the Advanced Job Scheduler when a job is processing.">Work with library lists</a></div>
|
||
|
|
<div><a href="rzaksajs9command.htm" title="A command variable (previously known as a parameter) is a variable you can store and use in jobs submitted through the Advanced Job Scheduler. Examples of command variables include the beginning of each month, a division number, a company number, and so on.">Work with command variables</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|