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.
How to set no limits as warning while running the job
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 149
- Joined: Fri Oct 15, 2004 12:13 am
- Location: Toronto,divine_auro@yahoo.co.in
- Contact:
How to set no limits as warning while running the job
With Regards
Biswajit
Biswajit
-
- Premium Member
- Posts: 149
- Joined: Fri Oct 15, 2004 12:13 am
- Location: Toronto,divine_auro@yahoo.co.in
- Contact:
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.
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.
With Regards
Biswajit
Biswajit
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?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers