Advanced Job Scheduler Job Dependencies
This document describes how to set up job dependencies using the Advanced Job Scheduler using IBM iSeries Navigator.
Resolving the problem
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:
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.
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.
Resource dependencies are based on several things. Each type that follows describes the areas that are checked. Following are the types of resource dependencies:
The job is dependent on the existence or nonexistence 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.
The job is dependent on the existence or nonexistence of an 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.
Note: You can have any object type be specified. Starting in V5R4, you now have the option to select an IFS object. The path name is case sensitive.
The job is dependent on the existence or nonexistence 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.
The job is dependent upon the status of a network file in order to be processed.
The job is dependent upon the status of a subsystem in order to be processed.
|1.||Open Work Management from your IBM iSeries Navigator window.|
|2.||Expand Advanced Job Scheduler.|
|3.||Click Scheduled Jobs.|
|4.||Right-click the Job Name whose dependencies you want to work with. Select one of the following: Job Dependencies, Active Dependencies, or Resource Dependencies.|
1. Use either of the following methods to access the AJS jobs:
|o||GO JS, Opt 1, select specific jobs or press Enter on the "Work with Jobs using JS" screen to get to the "Work with Jobs" screen.
2. Select Opt. 10 for Job Dependencies, Opt. 21 for Active Dependencies, or Opt. 22 for Resource Dependencies on the job to view/change the dependencies.
|Operating System||IBM i 6.1|
|Operating System||IBM i 7.1|
More support for:
Job and system Management
Software version: 5.3.0, 5.3.5, 5.4.0, 5.4.5, 6.1, 6.1.0, 6.1.1, 7.1, 7.1.0
Operating system(s): IBM i
Reference #: N1016188
Modified date: 03 February 2013