Job aborting because of warning messages

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Bilwakunj
Participant
Posts: 59
Joined: Fri Sep 10, 2004 7:00 am

Job aborting because of warning messages

Post by Bilwakunj »

Hi ,
One of my job is getting aborted because it is throwing more than 50 warning messages.
The strange thing I noticed is, if the job is run through the designer it doesn't aborts but with everything same if I run the same job with same data through the director it aborts because of more than 50 messages.
Can anybody please explain why this is happening?

Thanks.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Because the defaults are different between the two tools.

In either tool, click on 'Run' and then switch to the 'Limits' tab before actually running the job. You'll see that Designer typically defaults to Unlimited warnings and Directory defaults to Abort after 50 warnings.

And then there's the command line. :wink:
-craig

"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:

Post by ray.wurlod »

Either way you can override from the Job Run Options dialog (Limits tab), or by using command line option with dsjob.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Kinda figured that much was obvious. :P
-craig

"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:

Post by ray.wurlod »

Perhaps not to OP?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply