reject link order

jreddy · Post by **jreddy** » Thu Apr 27, 2006 11:01 am

Usually we have the reject link as the last link from the transformer to ensure that it captures rejects of the EARLIER output stages.. I have a job that has 2 output OraOCI stages and a sequential file stage (which has the rEJECT row ticked) My goal is to have the same data coming out of the transformer to be written to both the tables represented by the 2 OraOCI stages and the rejects to be written to the reject file.

It doesnt seem to matter if the have the reject link placed 2nd in order (between links 1 and 3 to the oracle stages) or if the reject link is placed last. Can anyone help me understand why ?

kcbland · Post by **kcbland** » Thu Apr 27, 2006 11:28 am

Read page 166 of your Server Job Developer's Guide.

jreddy · Post by **jreddy** » Thu Apr 27, 2006 11:36 am

thanks Kenneth.
But still my question stays unanswered. I have it as a rule of thumb and always design my jobs to have reject link as the last one out of the transformer.. but even if i put it in the second place.. still doesnt seem to matter and i started questioning my assumption and needed clarification of the same..

DSguru2B · Post by **DSguru2B** » Thu Apr 27, 2006 11:47 am

when you brought the reject link in second place, in regards to execution order, did you bring it in second place via link ordering

jreddy · Post by **jreddy** » Thu Apr 27, 2006 11:53 am

yes, I did

kcbland · Post by **kcbland** » Thu Apr 27, 2006 12:14 pm

The manual tells you to do it. It used to be required as the last link when DS 4 came out, but in prior releases it didn't matter. Maybe IBM will change their minds. In the meantime, follow the manual.

chulett · Post by **chulett** » Thu Apr 27, 2006 12:23 pm

The answer will depend on if just the Reject Row check box is checked, there is an expression in the Constraint derivation - or both.

jreddy · Post by **jreddy** » Thu Apr 27, 2006 1:21 pm

i have the reject row checkbox ticked.. and no constraint defined on the links to the oraOCI stages - this reject file is just for a catch all

chulett · Post by **chulett** » Thu Apr 27, 2006 1:45 pm

That's odd as that is the situation where it is supposed to matter where the reject row link is in the output link order.

ray.wurlod · Post by **ray.wurlod** » Thu Apr 27, 2006 4:48 pm

A [rejects] link processes any row that has not been output on any earlier-executed output link.

Read that statement carefully.

What it means is that the reject link will not capture any row that fails to be put onto any subsequently executed output link.

It also means that a second [rejects] link will never process any rows.