Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.9.10, 1.10.4
-
None
Description
Current Situation
The JobSchedulerCheckRunHistory implementation is available as a job only. Therefore to check a predecessor job in a job chain an extra job node has to be added that references this job to check for the run of a predecessor.
Desired Behaviour
It should be possible to define a pre-processing monitor to check the run of a predecessor job or job chain.
- com.sos.jitl.checkrunhistory.JobSchedulerCheckRunHistoryProcessBefore
- Implements the check in the api method spooler_process_before
- com.sos.jitl.checkrunhistory.JobSchedulerCheckRunHistoryTaskBefore
- Implements the check in the api method spooler_task_before
The difference is that when calling spooler_process_before the API methods spooler_init already have been called. The task already is up and running and the methods spooler_close and spooler_exit will be called (if implemented). When using spooler_task_before the pre-processor will prevent the task to start.