The DSN criteria keyword is coded on a schedule or job criteria record when that schedule or job must wait for a file to be updated before the schedule or job can run. This Knowledge Document describes what needs to be done to activate this predecessor.
In order for the DSN criteria to work, the following must be done:
EVENT(DSCLOSE,ACT) EVENT(DSCLOSE,REC) EVENT(DSCLOSE,RP=1) EVENT(DSCLOSE,PURGE=Y) SELECT(DSCLOSE,ACCESS,NE,IN*)
Note that when the DSCLOSE event is activated, every file I/O will trigger an event. Therefore, to avoid unnecessary overhead, the DSCLOSE event must be filtered out using the following ENF commands:
SELECT(DSCLOSE,DSN,EQ,my.test.data) = all I/O to "my.test.data" is captured by CA ENF., I/O to other data sets are not captured.
SCREEN(DSCLOSE,ACCESS,EQ,INPUT) = blocks out the DSCLOSE event if the data set is open read-only.
The SELECT and SCREEN commands are CA ENF startup options.
Caution: Depending on your site processing and the volume of data set closes, the use of DSN criteria may not be recommended. Processing large numbers of DSCLOSE events can cause performance issues with CA Scheduler JM.
As always, please contact CA Technologies support for CA Scheduler if you have further questions.