Conditions

Conditions are used to place additional restrictions on whether a Job or Job Step should run. For example, you can specify that a job should run only if a particular file exists.

Conditions do not cause a job to start—only triggers do this. Conditions are evaluated after a job has been submitted for execution. See the Comparison of Triggers and Conditions topic for more information.

adTempus offers the following kinds of conditions:

• The Job Condition depends on the state of another job.
• The File Condition depends on the presence or absence of one or more files.
• The Process Condition depends on the state of an external process.
• The Job Variable Condition depends on the value of a Job Variable.
• The Script Condition allows you to use a script to write your own condition logic.

How Conditions Work

Conditions can be attached to Jobs and/or Job Steps.

When a job is submitted for execution (by a Trigger, a Response, through on-demand execution, etc.) adTempus checks to see if there are conditions for the job. If so, it evaluates each condition to see if the rules of that condition have been met (the condition is "satisfied").

If all conditions are met, execution continues. If one ore more conditions are not met, the settings on the Conditions page of the Job Properties determine whether adTempus will wait until the conditions are met, how long it will wait, and what will happen if the conditions are never met. If the conditions are not met, you can choose to have adTempus issue a warning and execute the job anyway, skip the job, or fail the job.

If a Job Step has one or more conditions, they are evaluated in the same way. Each step's conditions are evaluated only after the previous step has completed execution.

Responding to Unmet Conditions

You can use Responses to take action if one or more conditions are not met for a Job or Job Step. To do so, add the "One or more conditions failed" Event to the Response.

Adding and Editing Conditions

Conditions for a Job are managed on the Conditions page of the Job Properties window. Conditions for a Job Step are managed on the Conditions page of the properties window for the Step.

Ignoring Conditions

In some case you may want to temporarily ignore conditions without deleting them. There are several ways to do this:

• Edit the condition and uncheck the Enabled box on the General page of the condition properties. This will cause adTempus to always ignore the condition.
• If you are running the job on demand using the Run command, you can choose to ignore job-level and/or step-level conditions.
• When you configure a Job Control Action to run a job, you can configure it to ignore job-level and/or step-level conditions

Viewing the Status of Conditions

While a job is waiting for conditions to be met, you can view the status of each condition to see which ones are met, and what adTempus is waiting for. To do this, select the waiting instance in the History panel or the Job Monitor and display the properties for the instance. The properties window has a Condition Status page, which shows the status of each condition.