Job Abort After 50 warnings
Moderators: chulett, rschirm, roy
Job Abort After 50 warnings
Hi Everyone,
I have a job which gets aborted after 50 warnings. the warnings limit is set to unlimited. but still this job aborts sometimes and sometimes it runs just fine. Can there be any other reason for such thing to happen.
thanks
I have a job which gets aborted after 50 warnings. the warnings limit is set to unlimited. but still this job aborts sometimes and sometimes it runs just fine. Can there be any other reason for such thing to happen.
thanks
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi chulett
then why do i have this option in the director so that i am able to set the warning limit to NO LIMIT in the director.
sometimes my job just runs fine with more than 50 warnings when i run from the director. sometimes it gets aborted when it sees 50 warnings.
can you please explain me . i am strcuk here
thanks
then why do i have this option in the director so that i am able to set the warning limit to NO LIMIT in the director.
sometimes my job just runs fine with more than 50 warnings when i run from the director. sometimes it gets aborted when it sees 50 warnings.
can you please explain me . i am strcuk here
thanks
Actually, according to the docs, any child job is supposed to inherit the warning limit of the job that calls it. Which means it all goes back to the limit on the 'main' top level Sequence.
If that's not happening, report it to your Support provider as a bug and let us know the outcome.
If that's not happening, report it to your Support provider as a bug and let us know the outcome.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
That is true. But just because the child encountered 50 warnings, the main sequence wont have 50 warnings. That was my point.chulett wrote:Actually, according to the docs, any child job is supposed to inherit the warning limit of the job that calls it. Which means it all goes back to the limit on the 'main' top level Sequence.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
Hi Craig,
I had to add a job paramter DSJ_LIMITWARN and give a default value of (0) Zero. so that 0 sets the warning limits to NO LIMIT.
this was recommended by IBM support. I will let you know the outcome when i encounter this problem again. because my jobs gets aborted only sometimes.
thank you all
sudharma
I had to add a job paramter DSJ_LIMITWARN and give a default value of (0) Zero. so that 0 sets the warning limits to NO LIMIT.
this was recommended by IBM support. I will let you know the outcome when i encounter this problem again. because my jobs gets aborted only sometimes.
thank you all
sudharma
Hi guru,
i got this warning issue resolved. i have a execute command stage at the end in my main sequence. this says
/apps/etl/Ascential/DataStage/DSEngine/bin/dsjob -run -mode NORMAL -warn 0 jobname&
i had to specify this -warn 0 and set the DSSetJobLimit and DSJ_LIMITWARN Parameters value to Zero so that the sequence picks the warn limits to NO LIMIT when ever it runs ( that is when it runs for any number of time ).
thanks a lot for all your hints.
thank you
sudharma
i got this warning issue resolved. i have a execute command stage at the end in my main sequence. this says
/apps/etl/Ascential/DataStage/DSEngine/bin/dsjob -run -mode NORMAL -warn 0 jobname&
i had to specify this -warn 0 and set the DSSetJobLimit and DSJ_LIMITWARN Parameters value to Zero so that the sequence picks the warn limits to NO LIMIT when ever it runs ( that is when it runs for any number of time ).
thanks a lot for all your hints.
thank you
sudharma
Remember way back up there when I said we were missing a critical piece of information? Well, here it is:
Since you didn't use a Job Activity stage, the rules for warning limit inheritance could not be enforced - except manually.sudharma wrote:i got this warning issue resolved. i have a execute command stage at the end in my main sequence. this says
/apps/etl/Ascential/DataStage/DSEngine/bin/dsjob -run -mode NORMAL -warn 0 jobname&
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers