Schedule job dependencies

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

  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.

• Active dependencies

  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

  Resource dependencies are based on several things. Each type that follows describes the areas that are checked. Following are the types of resource dependencies:

  File

  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.

  Object

  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 '/'.

  Hardware configuration

  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.

  Network file

  The job is dependent on the status of a network file in order to be processed.

  Subsystem

  The job is dependent on the status of a subsystem in order to be processed.

To work with job dependencies, follow these steps: