Cisco Cisco Workload Automation 6.3 用户指南
186
Jobs and Job Groups
Job Procedures
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
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.
11.
Select Ignore this dependency if Job not in schedule if the dependency only applies when the job is part of the
production schedule.
production schedule.
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.
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
to run only when file data.txt exists in the
c:\data directory.
To add a file dependency to a job:
1.
From the Navigator pane, select Definitions>Jobs to display the Jobs pane.
2.
Double-click the job or job group that you want to edit to display the Job or Job Group Definition dialog.
3.
Click the Dependencies tab.
4.
Click Add and select Add File Dependency from the dependency context menu to display the File Dependency
Definition dialog.
Definition dialog.
5.
Type the path and filename for the required file or click the Browse button to select a file on the local CWA Web
Client.
Client.
–or–
Click the Variables button to add System or Job variables as a file name.
6.
Select the agent where the file needs to exist.
7.
Select the dependency type for the file from the following options:
—
Exists – The file exists at the path and on the agent specified.
—
Does Not Exist – The file no longer exists, or is not found at the path or on the agent specified.
—
Has Changed In DD:HH:MM – The file dependency is satisfied when the file changed within the specified time
in days, hours, and minutes after the job entered the production schedule. For example, if the job entered the
schedule at 1:00 PM, the period specified is 6 hours, and the file changed after 7:00 PM (or later), the
dependency is met.
in days, hours, and minutes after the job entered the production schedule. For example, if the job entered the
schedule at 1:00 PM, the period specified is 6 hours, and the file changed after 7:00 PM (or later), the
dependency is met.
—
Stable For DD:HH:MM – The file dependency is satisfied when the file size has not changed for the specified
time in days, hours, and minutes from the present time. For example, if the file’s modified time is 1:00 PM, the
period specified is 6 hours, and the job enters the schedule at 3:00 PM, the dependency is satisfied in 4 hours,
i.e., 7:00 PM.
time in days, hours, and minutes from the present time. For example, if the file’s modified time is 1:00 PM, the
period specified is 6 hours, and the job enters the schedule at 3:00 PM, the dependency is satisfied in 4 hours,
i.e., 7:00 PM.
—
Size >= – The size of the file is greater than or equal to the specified amount in bytes.
—
Size <= – The size of the file is less than or equal to the specified amount in bytes.
8.
Click OK.