DSXchange

Posted: **Thu Mar 09, 2017 12:45 pm**

A DB2 connector reject link is provided to accommodating without aborting no matter how many rejects are produced. How do we accommodate this: below is from IBM knowledge centre:

https://www.ibm.com/support/knowledgece ... tdata.html

Specify one of the following options to control whether the job fails when records are rejected:
To stop job processing based on the number of rows that are rejected, specify a number in the Abort when field, and select Rows.
To stop job processing based on the percentage of processed rows that are rejected, specify a number in the Abort when field, select Percent, and specify the number of rows processed.

Abort after (rows) is set as 0. But it's aborted. Do you guys think the document is complete?

Thanks,

Posted: **Thu Mar 09, 2017 1:03 pm**

You "specified a number". Sounds to me you would leave it empty to not abort.

Posted: **Thu Mar 09, 2017 1:17 pm**

Consider that rejecting a row and logging a warning message are not the same thing.

What warning limit did your job run with and how many warning messages were logged when the abort was triggered?

Mike

Posted: **Fri Mar 10, 2017 10:41 am**

Thanks for responses.
In my experience with a peek stage as reject link target, it's nothing with what's logged. It logs on the same number of info items as your parallel config. One job succeeds with 0 Abort after (rows), another job fails with the same setting. So the setting is unsure of its behaviour. But if you put the big number, the job won't abort anyway.

Thanks,

DSXchange

DB2 Connector Reject setting

DB2 Connector Reject setting