Page 1 of 1
Job Aborts After 50 Errors Logged
Posted: Tue Jan 04, 2005 12:35 am
by OAC
Hi,
I am running a job and it gets aborted after loggin 50 warnings eventhough the limits for warning is set as No Limit. Please let me know how to solve this issue. It is very urgent. Appreciate if i get help from this forum
Posted: Tue Jan 04, 2005 12:55 am
by chulett
If it was really set to 'No Limit', it wouldn't abort after 50 warnings.
The question is - How are you running the job?
By hand from Director, you get a chance to set the warning threshold. If you are running it from job control or a Sequencer job, then it will inherit the setting from the controlling job.
Secondary question, are you sure you really want to run something with unlimited warnings that you know is going to log more than 50 of them? Large log files can fill up server install partitions and otherwise be... problematic.
Posted: Tue Jan 04, 2005 1:26 am
by OAC
I am running from a sequencer. No Limit Warning is set for that sequencer also. I want to run eventhough it logs more than 50 errors.
Posted: Tue Jan 04, 2005 12:52 pm
by ketfos
Hi,
Trying setting Warning limit to say 25 and see if it aborts after 25 warning messages.
This will help you to find if it is really taking the parameter you have set or it is taking from some other location.
Ketfos
Posted: Tue Jan 04, 2005 11:21 pm
by aesguerra
In the director, try going to Tools --> Options, then click on the "Limits" tab and set it to what you require.
Posted: Tue Jan 04, 2005 11:26 pm
by kcbland
Go to the job control tab in the Sequencer job and look for your job name in the source code. You should see a line that uses the DSSetJobLimit API to limited the number of warning messages. The token DSJ.LIMITWARN is used to control the maximum number of warning messages prior to starting the job. A Sequence or Batch job does NOT USE the Director features for limiting warnings or rows or much less parameter values.