Job Sequence Status
Moderators: chulett, rschirm, roy
Job Sequence Status
Can the job sequence's status be changed to reflect the actual job status like aborted? Or it only can be done using job control?
-
- Premium Member
- Posts: 385
- Joined: Tue Oct 07, 2003 4:55 am
Hi,
Like any other you have to catch the errors, so when you return from a job you must create trigers, for example:
If the job finished ok then goto the next job
If the job finished with warning - activate the warningToLog routine
If the job was aborted, activate abortToLog and the sequencer will abort as well.
different example:
If the job finished ok then goto the next job
Otherwise call AbortToLog
Another option (that is valid only for DS 7x) is to use in the sequencer properties 'automaticly handle activities that fail.
HTH,
Amos
Like any other you have to catch the errors, so when you return from a job you must create trigers, for example:
If the job finished ok then goto the next job
If the job finished with warning - activate the warningToLog routine
If the job was aborted, activate abortToLog and the sequencer will abort as well.
different example:
If the job finished ok then goto the next job
Otherwise call AbortToLog
Another option (that is valid only for DS 7x) is to use in the sequencer properties 'automaticly handle activities that fail.
HTH,
Amos
thanks for your guidance!
If i hav a job sequence diagram as below:
jobA ---ok----->jobB---ok & warning--->sequencer(any)---ok-->jobC
How to reflect the aborted status in job sequence if one the job aborted?
Is it have to use failed conditional trigger to link each job to a RoutineActivity(pass <job_stage>.$JobStatus to UtilityAbortToLog) ??? That means there will be 3 RoutineActivity in this job sequence.
Am i right?
If i hav a job sequence diagram as below:
jobA ---ok----->jobB---ok & warning--->sequencer(any)---ok-->jobC
How to reflect the aborted status in job sequence if one the job aborted?
Is it have to use failed conditional trigger to link each job to a RoutineActivity(pass <job_stage>.$JobStatus to UtilityAbortToLog) ??? That means there will be 3 RoutineActivity in this job sequence.
Am i right?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Depends whether you want to report just the fact that the sequencer is to abort:
or whether you need extra information about which job it was that aborted:
Code: Select all
jobA ---ok----->jobB---ok & warning--->sequencer(any)---ok-->jobC
| V |
+-------> Sequencer (Any) <--------------------------------+
|
AbortToLog
Code: Select all
jobA ---ok----->jobB---ok & warning--->sequencer(any)---ok-->jobC
| | |
| (abort) | (abort) | (abort)
| | |
AbortToLog AbortToLog AbortToLog
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.