I design a sequense job like
JOB1 ==> JOB2 ==> JOB3 .... ==> JOBn
What conditions applied that the next job trigger without the dependence of the previous job status.Whatever the previous job stats Its Finish with OK or WARNINGs OR job ABORTED with whatever the reason, But sequencer triger next job and complete its execuation.
I Uncheck the Automatically handle Activities that fail option and trigger next job with Unconditional expression type.
Sequence Execuation of Jobs
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You have it correct. Unconditional triggers throughout, and no automatic handling of failures. The sequence will finish, possibly with a status of "Finished". You can force it to generate warnings in the compilation options, if that's what you want to see.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Sorry for Question Mark missing in post next time we care.....chulett wrote:A little lost with no question mark in your post. What you've designed should allow the sequence to run each job one after the other without regard to the status of each job. If that is not happening, tell us what IS happening.
![Idea :idea:](./images/smilies/icon_idea.gif)
Thanks for reply its working fine Sequence Finished if any job in sequence fail.ray.wurlod wrote:You have it correct. Unconditional triggers throughout, and no automatic handling of failures. The sequence will finish, possibly with a status of "Finished". You can force it to generate warnings in the compilation options, if that's what you want to see.
![Cool 8)](./images/smilies/icon_cool.gif)
Setting Sequence Job as It;
1: Just Uncheck the Automatically handle Activities that fail option In Job Properties GenerL tab.
2: Trigger next job with Unconditional expression type In Stage Properties TriggerTab.
3: Change Execuation action to Reset if required, then Run In Stage properties Job Tab