How to set no limits as warning while running the job

divine · Post by **divine** » Tue Dec 20, 2005 3:33 am

Hello to everybody.

I am facing a typical problem. When I choose warning to no limit than also the job aborts after 50 warning. I have searched this topic in this forum but I did not get a clear answer how top avoid 50 warnings and put it to no limit. I need help to finish this job as it is in the last stage and I need to schedule the job with no limits as warning.

Hope to get a clear and quick answer from the forum.

kumar_s · Post by **kumar_s** » Tue Dec 20, 2005 4:23 am

Hi divine,

You will be getting the answer as "Search"

If you are running from sequencer you can go to the LIMITS tab while run time and set it to "No Limit" to Warnings which has the high precedence. If you are running from command prompt you have the option of warn -0.

-Kumar

chulett · Post by **chulett** » Tue Dec 20, 2005 8:05 am

One answer would be - why? Jobs should run with zero errors or warnings, setting it to unlimited is just asking for trouble.

trokosz · Post by **trokosz** » Tue Dec 20, 2005 11:17 am

If your running via dsjob then set the parameter of -warn to 0

divine · Post by **divine** » Wed Dec 21, 2005 6:57 am

Dear chulett,

I am absolutly agree with your point. But I am running a job in a loop and the job will going to stop once a particular file available to the job and this file also going to create in a certain time.So every time when job runs it looks for the file and when it did not find the file it gives a warning. So I need to put no limit to the warning . But when ever I put No limit the job aborts after 50 warning. I know there will be some other ooption will be available but in this point of time I need to know how to put to no limit .

Thanks and Regards.

chulett · Post by **chulett** » Wed Dec 21, 2005 8:38 am

Sounds like you should do something to test for the existance of the file first, rather than let the job error out if it doesn't. Would the WaitForFile stage help you in this regard? What about a routine to test for the file - one that doesn't error if it doesn't exist, merely reports that fact - and then only actually run the job when the file is there to be processed?