Job Trigger Target Rule Properties
The Job Trigger Target Rule window contains the settings for a single target (dependency job) for a Job Trigger.
Each rule defines a job that the current job is dependent on, and the rules for satisfying that dependency.
Settings
Enable this rule
Uncheck this box to disable the rule. adTempus will ignore any rules that are not enabled.
Trigger based on job
Select the job to depend on. Only jobs that you have "List/Reference" permission for are listed. The job may be on the same computer as the job you are editing, or on a different computer. If the job is on a different computer, the other computer must be defined as a Linked Server in adTempus.
Rule
Specify the rule that the target instance must satisfy:
- Job Started. The trigger fires when the target job starts.
- Job Ended. The trigger fires when the target job ends.
- Job succeeded. The target instance of the job must have completed with a successful result.
- Job failed. The target instance of the job must have completed with a failure result.
Instance
Specify which instance of the target job adTempus should look at to see if the rule is met. The "Target Job" is the job that you selected in the Depend on Job section. The "Dependent Job" is the job that has the trigger (the job you are currently editing).
The following instance rules are available:
- Most recent since previous execution of current job. adTempus will look at the most recent instance of the target job that executed since the last execution of the dependent job.
-
Most recent since previous successful execution of current job. adTempus will look at the most
recent instance of the target job that executed since the last successful execution
of the dependent job. -
Most recent in cycle. adTempus will look at the most recent instance of the target job that has the same Cycle ID as the dependent job.
-
Most recent instance since date/time specified in a Job Variable. adTempus will retrieve the current value of the specified variable (which must be defined as a Date/Time variable) and then look at the most recent instance of the target job that executed since that date/time.
- Most recent instance.adTempus will look at the most recent instance of the target job, regardless of when that instance executed.
- Any since previous execution of current job. adTempus will look at all instances that have completed since the last execution of the dependent job. If any of these instances matches the Rule, the condition will be satisfied.
-
Any instance since previous successful
execution of current job. adTempus will look at all instances that
have completed since the last successful execution of the dependent job. If any
of these instances matches the Rule, the condition will be satisfied.
-
Any instance in cycle. adTempus will look at all instances of the target job that have the same Cycle ID as the dependent job.
-
Any instance since date/time specified in a Job Variable. adTempus will retrieve the current value of the specified variable (which must be defined as a Date/Time variable) and then look at all instances of the target job that have executed since that date/time.
If you use one of the options based on the cycle, you must have Cycle IDs set up correctly as described in the Cycle ID topic.
See this this example for an illustration of the effects of the settings.
Ignore manual (on-demand) instances of job
When this option is checked, the condition will not look at any instances of the dependent job that were run on demand using the Run command when it is applying a "previous execution" rule.
Example
Suppose you are editing job "Data Copy" and setting a condition that job "Data Extract" must have run successfully since the most recent instance of "Data Copy." During your normal schedule cycle, "Data Extract" runs at 7am, and "Data Copy" runs at 3pm.
Today, however, "Data Copy" was run manually at 8am.
At 3pm "Data Copy" is triggered and the condition is checked.
If the Ignore manual (on-demand) instances option is not checked, adTempus will see that the previous instance of "Data Copy" was at 8am. Since "Data Extract" has not been run since then, the condition will not be met, and "Data Copy" will not run.
If the option is checked, however, adTempus will ignore the 8am instance and see yesterday's 3pm instance as the most recent instance of "Data Copy." Since today's "Data Extract" job ran after that, the condition will be met, and "Data Copy" will run.