DSXchange

Since your jobs are attached with jobcontrol process, it might cause the problem. We have a similar jobcontrol process and it won't allow a single warning. So if any job in the sequence get a single warning, job finished but sequence aborted due to the job warning.

it depends on the triggers we use fo the sequence...
using proper tiggers you should he able to hadle the aborts due to warnings.

"repost"

girija wrote:Since your jobs are attached with jobcontrol process, it might cause the problem. We have a similar jobcontrol process and it won't allow a single warning. So if any job in the sequence get a single warning, job finished but sequence aborted due to the job warning.

That will happen when you trigger the job on "OK" condition but we are using "OK" or "Warning".

you can try with following trigger option;
double click Job Activity and goto Triggers tab select the 'custom' option
and enter the correct expression
example :
Job1.$JobStatus<3
Where Job1 is previous Job Activity Name in the sequence.

Is project level auto purge active?
what is duration after which it clears the log?

Try running it after turning off the project level auto purge and let us know the results.

Edit : This happens some times when the auto purge tries to clear the log of multi instance jobs.

Also check whether the last line of your log says something like project level auto purge. XXX entries removed.

This only implies to the failures when its says not running.

We turned OFF the auto purge, it's running fine so far. But I want to see for some more runs.

samsuf2002 wrote:We turned OFF the auto purge, it's running fine so far. But I want to see for some more runs.

If it runs fine get a patch form IBM or leave it with auto purge off.

What patch would that be ? If any one know about it.