Cisco Cisco Workload Automation 6.3 User Guide
178
Jobs and Job Groups
Setting Dependencies on Jobs
—
Select Match Occurrence when both jobs (predecessor and successor) repeat within a day, and the instance
of the job dependency should match the instance of the job that depends on it.
of the job dependency should match the instance of the job that depends on it.
Offset – The number of instances to offset from either the First or Last instance. When set from the First Occurrence
setting, the dependency is met using the offset+1 job instance. For example, if the offset is set to 1, the dependency
is met using the second instance.
setting, the dependency is met using the offset+1 job instance. For example, if the offset is set to 1, the dependency
is met using the second instance.
When set from the Last Occurrence setting, the dependency is met using the Last Occurrence – offset job
instance. For example, if a job is repeated 10 times, and the offset is 1, then the dependency is met using the ninth
instance.
instance. For example, if a job is repeated 10 times, and the offset is 1, then the dependency is met using the ninth
instance.
Note: The Offset option does not apply to Match Occurrence.
Relative to group (otherwise for day) – Indicates whether this dependency refers to a group instance or a day
instance. Use this option to establish job dependencies within separate instances of a repeating group. Job
dependency is then defined by a group instance number. If this option is not selected, job dependency is defined by
the day instance, using the total number of jobs that run that day.
instance. Use this option to establish job dependencies within separate instances of a repeating group. Job
dependency is then defined by a group instance number. If this option is not selected, job dependency is defined by
the day instance, using the total number of jobs that run that day.
Note: With repeating groups, this option should be selected most of the time.
Date Offset – The number of days in the past to find the job dependency. For example, if Job A runs daily, and you
want the job to depend on the instance finishing three days ago, specify 3. This value should not exceed the retention
history for the job. If it does, the job dependency is never met.
want the job to depend on the instance finishing three days ago, specify 3. This value should not exceed the retention
history for the job. If it does, the job dependency is never met.
Ignore this dependency if job not in schedule – If the job dependency is not in the schedule, the job dependency
is automatically satisfied. If this is not checked and the job dependency is not in the schedule, the dependency will
not be met until the job dependency is added to the schedule.
is automatically satisfied. If this is not checked and the job dependency is not in the schedule, the dependency will
not be met until the job dependency is added to the schedule.
File Dependency Definition Dialog
About the File Dependency Dialog
The File Dependency Definition dialog displays when adding or editing a file dependency from the Dependencies tab
of the Job or Job Group Definition dialogs.
of the Job or Job Group Definition dialogs.
This dialog contains the following elements:
File Name – The file that the underlying job depends on. The filename should be an UNC (Universal Naming
Convention) pathname from the agent running the job. (Do not use a mapped drive in the file name.) For more
information on file dependencies, see
Convention) pathname from the agent running the job. (Do not use a mapped drive in the file name.) For more
information on file dependencies, see
.
Agent Name – The agent on which the file is located. The agent doesn’t have to be the same agent on which the job
runs.
runs.
Note: If the job being defined uses an agent list, then the Inherit Agent from Job option is automatically selected
and the agent list name displays in the Agent Name field.
and the agent list name displays in the Agent Name field.
Inherit Agent from Job – Select this option if you want the dependent file to use the same agent as the job or job
group you are adding or editing. The default for this option is unchecked.
group you are adding or editing. The default for this option is unchecked.
If the job uses an agent list instead of a specified agent, the dependent file uses the first agent in the agent list unless
the agent list is the broadcast type. (The order of the agents on the selected list is determined by the sequence they
were added to the agent list.) If the agent list is a broadcast type, then the dependent file uses the same agent the
job runs on.
the agent list is the broadcast type. (The order of the agents on the selected list is determined by the sequence they
were added to the agent list.) If the agent list is a broadcast type, then the dependent file uses the same agent the
job runs on.
Exists – The file dependency is satisfied when the file exists at the specified path on the specified agent.
Does Not Exist – The file dependency is satisfied when the file does not exist at the specified path on the specified
agent.
agent.