How to make this condition in Job Sequence Restartability
Moderators: chulett, rschirm, roy
How to make this condition in Job Sequence Restartability
Hi Everyone,
I have a job that releases several jobs to run concurrently . In those 2 jobs failed one with an abort and other has warning messages. But in my sequence i do not proceed to next step .Next step is on OK,the alternate link is "otherwise". On re-start of the job , excecution started from the 1st job which is OK, but i wanted 2nd job to restart also and it didn't.
I did not check the box "Do not check point run" because I don't want it to re-run even if it successfully finishes, only when it "fails" with warning.
Can anyone help me to overcome this problem and what approach have to follow for this ..
Thanks in Advance
I have a job that releases several jobs to run concurrently . In those 2 jobs failed one with an abort and other has warning messages. But in my sequence i do not proceed to next step .Next step is on OK,the alternate link is "otherwise". On re-start of the job , excecution started from the 1st job which is OK, but i wanted 2nd job to restart also and it didn't.
I did not check the box "Do not check point run" because I don't want it to re-run even if it successfully finishes, only when it "fails" with warning.
Can anyone help me to overcome this problem and what approach have to follow for this ..
Thanks in Advance
Sequence level would be too late, so you need to handle it "in job". Several ways, some off the top of my head...
Set the warning level when the job runs very low. Send problems down a reject link set to abort on the first record. Check the JOBINTERIMSTATUS after job and abort the job if is says it's going to finish with warnings.
Probably others.
Set the warning level when the job runs very low. Send problems down a reject link set to abort on the first record. Check the JOBINTERIMSTATUS after job and abort the job if is says it's going to finish with warnings.
Probably others.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 221
- Joined: Fri Feb 17, 2006 3:38 am
- Location: India
- Contact:
We also had same problem and we resolved it.chulett wrote:No, anything at that level would be too late. That would abort the Sequence itself and possibly any currently running jobs as well, not the one that ended with warnings. ...
Write an After Stage Subroutine and in that routine check for job status using DSJ functions. If the status is not equal to one then issue a fatal signal as DSLogFatal(<any message>,<name of routine>)
and the job will abort after throwing your custom message
Thanks & Regards
Parag Saundattikar
Certified for Infosphere DataStage v8.0
Parag Saundattikar
Certified for Infosphere DataStage v8.0
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Not true. Before/after subroutines are written as server routines whose type is "before/after subroutines", even when they are deployed into parallel jobs. This works because before/after subroutines only ever have to execute on the conductor node, and (typically) the conductor node is where the DataStage run machine is installed.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
DSXchange Learning Center has a DVD available on programming with the DataStage BASIC language. Or you can take a class
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.