Capturing non-matched records from reference file

[vskr72]

I need to capture non-matched recrods from the reference file. Its a Hashed file. I tried using the constraint RefLink.NOTFOUND, I see all blanks in the file. Any option other than swapping the Ref to Stream and Stream to Ref.

Kumar

[I_Server_Whale]

I see all blanks in the file.
Kumar

What exactly do you mean by blanks?

spaces, empty file, etc, etc...?

What columns are you passing through the link? Do they include any keys?

The more info you provide, the better is the chance of getting a good answer.

Thanks,
Whale.

[DSguru2B]

You must be derive the rejected columns from the source and not the hashed file. I bet you are deriving it from the hashed file. The lookup failed and hence the values will be NULL. Makes sense?

[vskr72]

Thanks. I guess it makes sense.

[ray.wurlod]

It's impossible to capture the records that were not lookup up when performing a lookup, unless you immediately delete the successes from the reference table (hashed file) and inspect the survivors afterwards.

In SQL you might use a NOT IN comparison to a subquery that included all your matches. Doing such SQL against text files (for example via ODBC driver for text files) would be horribly slow.

But a lookup - especially a hashed file lookup - only allows an "=" condition on the key value. So it's out of the question that you could determine which keys were not looked for with this architecture.

[aakashahuja]

Assuming that you want to filter out the rows from the hash file whose corresponding rows couldnt be found in the stream link then it could be done the other was round.

That is to interchange the positions of your source and lookup stages. That is take hash file as the source and file (assuming this was your source) as lookup (if its PX else move the data in to a hash file first).

Then you can easily pass out the records which do not match....