Friday 22 June 2012

Automatic Job Flow Adjustment in control-m


Automatic Job Flow Adjustment

Predecessor and successor job flows are established through the use of
prerequisite conditions that are defined in the job scheduling definition.
Successor and predecessor jobs are identified as either “immediate” or
“eventual,” relative to a specified job:

• An immediate predecessor and successor relationship exists between jobs
when one job is directly dependent on prerequisite conditions added by
the other job.

• An eventual predecessor and successor relationship exists between jobs if
their dependency is indirectly established through a “chain” of immediate
predecessor and successor jobs.

From the network of predecessor and successor jobs, critical paths can be
identified. A critical path is a chain of jobs that must be executed in their
appropriate sequence in order for a specified job to run. A job can have more
than one critical path, if different jobs set the same OUT condition, or if a job
has OR logic in its IN conditions.

The Job Dependency Network screen, accessed through the Active
Environment screen, enables you to view the network of predecessor and
successor jobs for a specified job and determine the critical paths for the job.
Although it is prerequisite conditions that define predecessor and successor
job relationships, the actual job flow along a critical path can be greatly
impacted by the following runtime scheduling criteria in the job scheduling
definition:


Runtime Scheduling Criteria
Criteria Description

PRIORITY As mentioned earlier in “Job Priority,” a PRIORITY value affects
the job’s selection order (relative to other jobs).

DUE OUT Specifies the time by which the job must finish executing.

No comments:

Post a Comment