Руководство Пользователя для Cisco Cisco Tidal Enterprise Scheduler 6.2

Status – The status of the job dependency. Select

Launched,

Active,

Completed Normally, 

Completed Normally (Output Pending), Completed Abnormally,

(Output Pending), Error Occurred, Externally Defined, Externally Defined (Output Pending) 
or

as the condition for which the job dependency is satisfied.

Occurrence – Used if the job dependency is a job that repeats within a production day. 

Select First Occurrence when the first instance of the job should be used to satisfy the 
dependency. 

Select Last Occurrence when the last instance of the job should be used to satisfy the 
dependency.If the job does not repeat, the last instance of the job dependency is used. If the 
dependent job has more repeating instances, the last instance of the job dependency is used to 
satisfy the dependency for the trailing instances of the dependent job.

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. 

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.

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. 

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.

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. 

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.

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.

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