08-09-2013 12:13 PM
The flow contains two jobs, which are triggered by their File event separately.
File1 Exists --> Job1
File2 Exists --> Job2
The problem is that when the flow is triggered and only File1 is there, the job2 won't run and it causes the flow never complete with the status of Running.
Any solution without programming for this?
08-10-2013 03:38 AM
Tis type of logic is coming from advanced schedulers (Ctrl-D OPC expect LSF the same).
The flow(job) is collection of programs to run on a regular scheme.
- Dependicies and events are influencing when each program is allowed to run
- actions as suspending a program (removing from requirements) are possible
The logic to solve will be:
1- after a planned time and file2 does not exist have job2 suspendend (possible by running a job)
2- When Job2 is allowed to run more than once and is capable running on an empty file
Have a time event within the flow planned to deliver an empty file
3- This will be an excpetional case. Have your operators being instructed to suspend the job2 as reaction on the alert message (late) of the scheduling environment.
All depends how the environment is organized and the options in your tooling.