Interpretation in PX b/w Lnk.NOTFOUND and NOT(Lnk.NOTFOUND)

[DS_MJ]

In Server job the stream going to the hashed file will have constraint reflink.NOTFOUND and for the reject it will be NOT(reflink.NOTFOUND) .

Is this correct...?
In PX the constraint for reflink.NOTFOUND = IsNOTNULL(input_colName)
and Reject link = IsNull(Input_Col_Name)

Also, how do i interpret server NOT(reflink.NOTFOUND) in PX...?

[Edwink]

please can u explain ur job clearly?

[DS_MJ]

Not(IsNotNull(Input_Col)) = NOT(reflink.NOTFOUND)...?

[Edwink]

u dont have not found option in PX so
u have to use lookup+transformer stage.

in lookup stage have lookup failure constrints in properties tab to continue ..
take the both key column of primary and reference link to output..

And in the transformer have two o/p link applying constrints
isnotnull (referncelink. key) to get only the found records..

is null(referncelink. key) to get the not found records..
hope this might solve ur problem

[ray.wurlod]

Please refrain from using "u" for the second person pronoun - we have a Burmese user called U enrolled who - it appears - finds it offensive.
Given that the OP has also mentioned hashed files, it is opportune to ask whether this is a parallel job at all.

[Edwink]

sure... i will correct myself