Руководство Пользователя для Cisco Cisco Tidal Enterprise Scheduler 6.2
5-195
Cisco Tidal Enterprise Scheduler 6.2 User Guide
6.2.1
Chapter 5 Jobs and Job Groups
Setting Dependencies on 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.
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.
The wildcard enhancement makes it quick, easy and efficient to set up and manage file dependencies
where the filename is not constant.
where the filename is not constant.
How are the wildcards structured?
Usage of wildcards in TES is consistent with the standard wildcard practice. A combination of the
question mark (
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.
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.
path to a file.
You should enter file dependencies in UNC format:
\\servername\directoryname\filename
i.e.
\\bpssch2\bpapps\files\ord????.dat
as well as in the format of a mapped drive if on the same machine:
driveletter:\directoryname\filename
i.e.
c:\files\ord*.dat
This gives you the flexibility to detect the existence of files on any shared server in the domain.
What is the logic applied in fulfillment of wildcard file dependencies?
Once a file arrives whose name qualifies based on the wildcards, the dependency is marked true and the
job with the dependency is released. Wildcards are cleanly implemented with the Exists and Does Not
Exist
job with the dependency is released. Wildcards are cleanly implemented with the Exists and Does Not
Exist
options as well as TES’s advanced file dependency features.
What if more than one file fulfills the dependency?
Multiple files may qualify for a wildcard file dependency. For example, the query ORD*.RDY may result
in three files: ORD100.RDY, ORD105.RDY and ORD200.RDY. A dependency could be set on files that
have changed in the last 30 minutes. ORD105.RDY might have changed in the last 30 minutes while the
other two files did not. In this type of situation, if one file meets the condition, then the dependency has
been met.
in three files: ORD100.RDY, ORD105.RDY and ORD200.RDY. A dependency could be set on files that
have changed in the last 30 minutes. ORD105.RDY might have changed in the last 30 minutes while the
other two files did not. In this type of situation, if one file meets the condition, then the dependency has
been met.
What happens when dependencies cross day boundaries?
A job can be scheduled to run daily depending on a file. You can use a wildcard in the file dependency
to look for the file. For example, the job may need ORD9T.RDY on Tuesday and ORD10W.RDY on
Wednesday. You can define this job to have a dependency on file ORD*.RDY. ORD*.RDY matches both
ORD9T.RDY and ORD10W.RDY.
to look for the file. For example, the job may need ORD9T.RDY on Tuesday and ORD10W.RDY on
Wednesday. You can define this job to have a dependency on file ORD*.RDY. ORD*.RDY matches both
ORD9T.RDY and ORD10W.RDY.
What if ORD9T.RDY arrives late, after the end of the day?