Table of Contents |
---|
Scope
- Test case for dependency pattern: split the execution to multiple job chains and synchronize for the execution of a subsequent job chain
Test Target
Diagram
Graphviz |
---|
digraph { "Chain B" [shape="box",label="Chain B\nWorkDays\nStart Time: 18:00"] "Chain D" [shape="box",label="Chain D\n1) WorkDays after Chain B\nTime Slot: 15:00-00:00\n2) Start Time without pre.: 15:00"] "Chain E" [shape="box",label="Chain E\n1) WorkDays after Chain B\nTime Slot: 16:00-00:00\n2) Start Time without pre.: 16:00"] "Chain F" [shape="box",label="Chain F\n1) WorkDays after Chain B\nTime Slot: 19:30-00:00\n2) Start Time without pre.: 19:30"] "Chain G" [shape="box",label="Chain G\n1) WorkDays after Chain B\nTime Slot: 20:00-00:00\n2) Start Time without pre.: 20:00"] "Chain I" [shape="box",label="Chain I\n1) WorkDays after Chains D, E, F, G\nTime Slot: anytime\n2) Start Time without pre.: 14:00\n3) Sat Start Time: 14:00"] "Chain B" -> "Chain D" "Chain B" -> "Chain E" "Chain B" -> "Chain F" "Chain B" -> "Chain G" "Chain D" -> "Chain I" "Chain E" -> "Chain I" "Chain F" -> "Chain I" "Chain G" -> "Chain I" } |
Explanations
- As a general rule: whenever a predecssor job chain would have been purged then the job chain would be executed based on its invidual schedule
- All Job Chains have to complete successfully otherwise they would block the processing of their successors.
- At any point in time additional dependencies can be added, e.g. in addition to Job Chain B a
Job Chain B2
could be created with the same dependencies. - For all Job Chains the calendar has to be active otherwise the job chain would not be part of the daily plan.
Job Chain I
Job Chain I
is executed on workdays immediately after the execution of the previous job chains, i.e. some time after 18:00.Job Chain I
is executed on Saturday at 14:00 independent from previous job chains.
Test Data
- Download the attached archive csijobnet.zip
- Unzip the archive to the
live
folder. The directories should be created in$SCHEDULER_DATA/config/live/
jobnet/examples
control
: synchronization job as used by the below examples.
examples
JobChain_*
: Job Chains B, D, E and I as used for the below examples.
- Unzip the archive to the
- Deployment: components for dependency checking are expected to be Download the dependency component archive dependency.zip for dependency checking and make it available in a subfolder
dependency
$SCHEDULER_DATA/config/live/sos/dependency
Test Cases
- All job chain starts are effected by using the order
jobnet_order
of the respective job chain if not otherwise specified.
...
Status | ||||
---|---|---|---|---|
|
Test Runs
- Test runs specify the date and author of execution of the test cases in a specified environment.
...
Office Excel | ||||||
---|---|---|---|---|---|---|
|
TODOs
Giovanni
- run the attached test cases
Andreas
Open Issues
- enable manual start of orders independent from predecessor checking. However, consider successor checking
- currently this is possible by removing the
jobnet_predecessor
parameter from an existing order and keeping thejobnet_successor
parameter. - For usage in JOE right-click on an existing order and select the menu item "Add Order".
- then remove the content of the order parameter
jobnet_predecessor
like this:
- currently this is possible by removing the
- "over midnight": start job chain B that would execute over midnight and that would start D and E early next morning.
- D, E, I should execute
- apart from this for the next day day the normal processing applies
- ths forces to introduce the concept of "periods" instead of "day" which is not yet available
- convert timezones