System: BODS 4.2 on Linux
While attempting to use scheduling events, I am seeing it is very useful in using a single job to launch multiple jobs.
I am having an issue trying to use multiple jobs to launch a single job.
I have been working on this for Data Services but it could apply to WEBIs or Crystals as well.
I have to assume that this has to do with the lifetime of the scheduling event.
Current setup
Job1 triggers the Scheduling Event "Job1 Complete"
Job2, 3, 4, 5, and 6 wait for the Job1 Complete before they start processing and trigger a "JobX Complete" (i.e Job2 Complete, Job3 Complete) event when they are done
Job 2 takes approx. 10-20 minutes
Job 3 takes approx. 15-30 minutes
Job 4 takes approx. 25-55 minutes
Job 5 takes approx. 25-35 minutes
Job 6 takes approx. 30-45 minutes
Job 7 waits for the 5 prior events but is still waiting when all the prior jobs have completed.
With the inconsistency in completion times I cannot attach Job7 to any specific prior job. Sometimes Job4 will complete before Job6, or Job5 could take longer than both of them depending on what was entered throughout the day.
My question is in two parts:
1) Does anyone know how long a scheduling event exists?
2) Is it possible to extend the lifetime of the scheduling event so that it will remain until it is consumed by the job it is triggering.
If you are going to suggest an external job scheduler, that is the option we are considering if this is not possible.