Dont want to abort after 50 rows

SURA · Post by **SURA** » Mon Jun 29, 2015 4:43 am

Hello All

I am using a multiple instance server job to load the data.

As per the present need i don't want the job to abort even if the records has been rejected.

If i run the job manually, i can change the Warning Limits whereas when the job has been triggered Master Sequence how to chance it to "No Limit"?

ShaneMuir · Post by **ShaneMuir** » Mon Jun 29, 2015 5:36 am

So a job would normally inherit the limit value from the controlling sequence, are you saying you do not want this to happen - ie for a particular job you want to override the limit warning?

SURA · Post by **SURA** » Mon Jun 29, 2015 4:26 pm

Yes.

As per the design this is the only place where job can run no matter what? Rest of the designs are made to trigger the Abort process.

SURA · Post by **SURA** » Mon Jun 29, 2015 5:57 pm

-warn n should work i believe.

In this situation, a sequence is triggering the job, but i am using dsjob to trigger the sequence.

I am not sure -warn n to sequence will reflect to this job?

Let me try!

If you guys have any idea, please share with me.

SURA · Post by **SURA** » Mon Jun 29, 2015 8:06 pm

- warn 0 worked.

Thanks to all.