Cisco Cisco Workload Automation 6.3 User Guide
179
Jobs and Job Groups
Setting Dependencies on Jobs
Has Changed In DD:HH:MM – The file dependency is satisfied when the file has changed within the specified time
in days, hours, and minutes prior to when 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 AM (or later), the
dependency is met.
in days, hours, and minutes prior to when 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 AM (or later), the
dependency is met.
Stable For DD:HH:MM – The file dependency is satisfied when the file contents have 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 six hours and the job enters the schedule at 3:00 PM, the dependency is satisfied in four 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 six hours and the job enters the schedule at 3:00 PM, the dependency is satisfied in four hours, i.e., 7:00
PM.
Size >= – The file dependency is satisfied when the file size increases to or exceeds the value specified in bytes. The
maximum file size is 4,294,967,296 bytes.
maximum file size is 4,294,967,296 bytes.
Size <= – The file dependency is satisfied when the file size decreases to or drops below the value specified in bytes.
Wildcards in File Dependencies
The question mark (?) and the asterisk (*) are supported as wildcards in the filenames of file dependencies.
Wildcard Usage Summary
The question mark (
?) wildcard represents any single character in a string
The asterisk (
*) wildcard represents any character or group of characters in that position in the string
You may combine the wildcards (for example, T?dal.*)
UNC paths must be used if the user account under which the agent runs has the required access to the network
share
share
Wildcards are accepted in filenames only, not elsewhere in the path specification
Note that if the Has Not Changed For or Stable For option is selected with a wildcard file dependency, a large match set
may result, delaying the check for file dependencies for other jobs.
may result, delaying the check for file dependencies for other jobs.
FAQs on Wildcard Functionality
What are the benefits of using wildcards in file dependencies?
There are programs, applications, scripts and batch files that need to depend on the existence of a file. In some
situations, the exact name of the file that the program depends is unknown. The filename may include a date or time
stamp, or a sequence number may be appended to the filename at the time of creation of the file. For example, an order
file might be named ORD<sequence_number>.RDY.
situations, the exact name of the file that the program depends is unknown. The filename may include a date or time
stamp, or a sequence number may be appended to the filename at the time of creation of the file. For example, an order
file might be named ORD<sequence_number>.RDY.
The wildcard enhancement makes it quick, easy and efficient to set up and manage file dependencies where the filename
is not constant.
is not constant.
How are the wildcards structured?
Usage of wildcards in CWA is consistent with the standard wildcard practice. A combination of the question mark (
?) and
asterisk (
*) can be used. For example, a file dependency can be set on any files meeting the following wildcard criteria,
L??d?n*.dat. The file, London101.dat, would make this dependency true.
Can you use wildcards in the path as well as in the filename?
No. The path to the file must be known. The wildcard functionality does not support wildcards in the path to a file.
You should enter file dependencies in UNC format:
\\servername\directoryname\filename