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.
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.
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?
-craig
"You can never have too many knives" -- Logan Nine Fingers
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.
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.
-craig
"You can never have too many knives" -- Logan Nine Fingers