Is it possible to bypass a file trigger on ESP Workload Automation system by adding the "CONDITIONAL" option on FILE_TRIGGER?.
Component : ESP WORKLOAD AUTOMATION
RELEASE: ALL
This is an important feature as we do not always have a file available for a file trigger. When this happens, we set a abandon sub to the successor job that uses the file and continue the job stream. The file_trigger bypasses at the end of the proc conclusion. The dueout exec stops the file_trigger going into overdue status.
FILE_TRIGGER jobt CONDITIONAL
/* DESC=Utility to monitor a creation of a file.
RUN ANY
AGENT myagent
FILENAME E:\readmeX.txt
DUEOUT EXEC 23:59
RELEASE ADD(job1)
ENDJOB
JOB job1
CCCHK RC(1:4095) FAIL
ABANDON SUB 14:25
EARLYSUB 14:27
RUN ANY
RELEASE ADD(job2)
ENDJOB
JOB job2
CCCHK RC(1:4095) FAIL
ABANDON SUB 14:25
EARLYSUB 14:27
RUN ANY
ENDJOB
48 0 job1 11.45 TODAY COMPLETED AT 11.45
48 0 job2 11.45 TODAY COMPLETED AT 11.45
48 0 jobt 11.45 TODAY COMPLETED(F) AT 11.47
without the conditional statement, the file_trigger has to be force-completed.
49 0 job1 11.47 TODAY COMPLETED AT 11.47
49 0 job2 11.47 TODAY COMPLETED AT 11.47
49 - jobt 11.47 TODAY BYPASSED with the conditional statement, it bypasses at the end of the proc.