The options on the Job Condition Properties page define the behavior of the Job Condition.
Depend 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.
Rule
Specify the rule that the target instance must satisfy:
Job must be running. The target instance of the job must currently be running.
Job must not be running. The target instance of the job must not currently be running.
Job must have succeeded. The target instance of the job must have completed with a successful result.
Job must have failed. The target instance of the job must have completed with a failure result.
Job must have completed. The target instance of the job must have run, but the result is not important.
Instance
Specify which instance An instance is a specific execution of a job. of the target job adTempus should look at to see if the condition is met:
The most recent instance since the previous execution of job. adTempus will look at the most recent instance of the target job that executed since the last execution of the dependent job.
The most recent instance. adTempus will look at the most recent instance of the target job, regardless of when that instance executed.
Any instance since the previous execution of 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.
It is helpful to think of a "cycle" of jobs. If job "Data Copy" is dependent on job "Data Extract," a normal cycle would be an execution of "Data Extract" followed by an execution of "Data Copy." Once "Data Copy" has run, it generally should not run again until "Data Extract" has run again.
The default Instance option "The most recent instance since the previous execution of job" will produce this kind of cycle, and is the recommended setting. The other two options can be used for specialized scenarios. See this example for an illustration of the effects of the three settings.
Condition Wait
This option determines whether adTempus will wait for the condition to be met:
Do not wait for condition to be met. If the condition is not satisfied the first time adTempus checks it for a given instance, adTempus treats the condition as "Failed."
Wait until the condition is met. If the condition is not satisfied, adTempus will wait until it is satisfied. The job or step will show a status of "Waiting for Condition."
Wait up to __ minutes for the condition to be met. adTempus will wait up to the specified time limit for the condition to be satisfied. If the condition is satisfied within that time limit, job execution will continue immediately (as depending on other conditions). If the condition is not satisfied at the end of the time limit, adTempus treats the condition as "Failed."
See the Condition Polling topic for more information.
Once satisfied, do not re-evaluate for this instance
Check this option to indicate that adTempus should stop checking this condition once it has been satisfied. See Condition Polling for more information.
See Also