Job aborts after 50 warning messages

kab123 · Post by **kab123** » Wed Oct 21, 2009 12:28 pm

I have a Job Control Batch which runs 10 jobs sequentially. I set the warning limit to 'No Limit' in director and I also made sure, It is 'no Limit'whil running the Batch job. However while running, the individual job gets 50 limit somehow and aborts after 50 warnings. Can somebody tell me where do you think it is picking up that number from ?
I searched forum before putting this question. I got only one post but that didnt talk about Job Control Batch.

chulett · Post by **chulett** » Wed Oct 21, 2009 1:37 pm

Please explain what you mean by a "job control batch". Is this hand code using the DSRunJob() function?

kab123 · Post by **kab123** » Wed Oct 21, 2009 1:41 pm

Yes.
we didnt force it to 'No Limit' using
DSSetLimitJob and I belive thats why, even we set the limit to 'No Limit' in director, it is not picking that up.

chulett · Post by **chulett** » Wed Oct 21, 2009 1:49 pm

You really shouldn't have to do that and even the help for DSSetJobLimit tells you that. I assume you're actually running the batch job from Director, not the command line using dsjob, right?

cppwiz · Post by **cppwiz** » Thu Oct 22, 2009 3:47 pm

Could it be a limit on a link from a parallel transformer stage? Open up your stage and click the link icon. The "Abort After Rows" column on each link should be zero.

kab123 · Post by **kab123** » Fri Oct 30, 2009 9:00 am

Yes we are scheduling thru DataStage Director.

chulett · Post by **chulett** » Fri Oct 30, 2009 9:15 am

Check what you have in your scheduler. For UNIX, it would be 'crontab -l' and after the job name would be something like 0/50/1/0/0 with the second number (50 here) being the warning limit.

ray.wurlod · Post by **ray.wurlod** » Fri Oct 30, 2009 6:27 pm

Check the default limit in Tools>Options in Director client.