We have built a DS routine that we use to execute all our DS jobs from within a sequence job or JC job. This routine does groovy stuff like:
* manage the passing of parameter values (static and dynamic) to the child job
* reset child jobs not in a runnable state
* capture child job runtime statistics
* manage restart flags
We were quite excited when DS7.1 came along with built-in sequence restart capabilities. However, we found that it is lacking when compared to the functionality offered by our routine. DS7.5 has not addressed the problem either which is described below.
Seq1 runs Seq2 and then Seq3.
Seq2 runs Job1 and then Job2.
Seq3 runs Job3 and then Job4.
Job4 aborts which causes Seq3 and then Seq1 to abort.
Re-run Seq1 after fixing the problem with Job4.
DS restart functionality will:
* Skip Seq2 as it has already completed successfully.
* Restart Seq3 as it did not complete successfully. This results in Job3 being re-run which is not desirable as it has already completed successfully.
Our custom job execution routine handles this restart problem right down to the lowest jobs at the bottom of the sequence tree.
We would obviously like to take advantage of DS's inbuilt restart capabilities if it was able to handle the above scenario. Is anyone aware of a work-around to this problem?
If you're listening Ascential, can you please accept this as an enhancement request.
Ta,
C.
Sequence job restart
Moderators: chulett, rschirm, roy
Re: Sequence job restart
They're not. At least not here, not 'officially'.chrisk wrote:If you're listening Ascential, can you please accept this as an enhancement request.
You'd either need to post this on ADN or better yet call Support and log something official.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: