Cisco Cisco Tidal Enterprise Scheduler 6.2 User Guide

5-200
Cisco Tidal Enterprise Scheduler 6.2 User Guide
6.2.1
Chapter 5 Jobs and Job Groups
Setting Dependencies on Jobs
Step 6
In the Operator field, select whether the file dependency Equals
or Does not equal the following status
to satisfy the dependency. For example, you can set the job dependency to Equal the Completed
Normally status.
Normally status.
Step 7
In the Status field, select the status to use to satisfy the dependency. You can choose between Active
,
Completed Abnormally
,
Completed Normally
,
Error Occurred, Externally Defined
and
Completed.
Note
A job group becomes active when any of its associated jobs become active. If all jobs in a job group
depend on the job group becoming active, no jobs will launch.
depend on the job group becoming active, no jobs will launch.
Step 8
If the job repeats during the day, select which instance of the job will trigger the dependency from the
Occurrence drop-down menu.
Occurrence drop-down menu.
a.
Select First Occurrence if you want the first instance of the preceding job to match the status
criterion.
criterion.
b.
Select Last Occurrence if you want the last instance of the preceding job to match the status
criterion.
criterion.
c.
Select Match Occurrence when both jobs repeat during the day, and the dependency should
match instance numbers.
match instance numbers.
There are two ways to apply the First/Last/Match
dependency logic: by day instance or group instance.
Step 9
To specify an instance offset, you can do so in the Offset field. This field only applies to First
Occurrence and Last Occurrence. When applied to First Occurrence, specifies which instance after
the first to use in satisfying the dependency. When applied to Last Occurrence, specifies which instance
from the last.
Occurrence and Last Occurrence. When applied to First Occurrence, specifies which instance after
the first to use in satisfying the dependency. When applied to Last Occurrence, specifies which instance
from the last.
Step 10
If you want to specify an instance of a job that occurred a certain number of days in the past, go to the
Date Offset field, and type the number of days in the past for the required job dependency. For example,
if Job A repeats daily, but you want your job to be dependent on Job A’s instance 3 days ago, specify
Date Offset field, and type the number of days in the past for the required job dependency. For example,
if Job A repeats daily, but you want your job to be dependent on Job A’s instance 3 days ago, specify
3
in this field.
Step 11
Select Ignore this dependency if Job not in schedule if the dependency only applies when the job is
part of the production schedule.
part of the production schedule.
Step 12
Click OK to add the job dependency.
Note
If your job has more than one dependency (file, job, variable or time), all dependencies must be satisfied
for the job to run. It is possible for a dependency’s state to change from satisfied to unsatisfied. If this
occurs, the job will only run when all dependencies have been satisfied at the same time.
for the job to run. It is possible for a dependency’s state to change from satisfied to unsatisfied. If this
occurs, the job will only run when all dependencies have been satisfied at the same time.
Adding a File Dependency
You can have a job that depends on the status of a file on any system in your network. For example, Job
A can be defined to run only when file data.txt exists in the
A can be defined to run only when file data.txt exists in the
c:\data
directory.
To add a file dependency to a job:
Step 1
From the Navigator pane, select Definitions>Jobs to display the Jobs pane.
Step 2
Double-click the job or job group that you want to edit to display the Job or Job Group Definition
dialog.
dialog.