DSXchange

Is there a large volume of reference data?

Your function mimics what the Lookup stage does - at least one of the things that it does. So why are you going to the trouble of writing the function? Surely it's unnecessary.

My question was a cynical response to your reinvention of this particular wheel.

Have you enabled "multiple row return from reference input"?

I'm not aware of one (a function for the parallel Transformer) within DataStage. Certainly it exists as a C function so you could implement your own parallel routine.

Try using a separation of 4 or even 8, rather than 1. You'll need to enter this manually into the Hashed File Calculator.

Repeat is not the same as rephrase. We'd like you to explain more clearly what you are attempting to do.

Have you investigated ETLstats from Kim Duke's web site? It can gather that kind of information and store the same in tables from which you can report.

Search DSXchange. "Heap allocation failed" has been addressed numerous times.

There's a Report Progress (or similar) property in the Sequential File stage. The property takes a yes/no value, default is yes. Change it to No to prevent progress reporting.

Can you please let everyone know HOW it was resolved?

There's a simple remedy for your problem.

What's the structure of the key? What hashing algorithm have you chosen?

You'd need custom SQL but, yes, you can do it during extraction. Like Craig I'd prefer to do it "in job".

In spite of Arnd's doubts, "R%8" is also correct. The width parameter is not required if there is a mask, and "%8" is a shorthand way of specifying "%%%%%%%%" as a mask. "R%8" displays the rightmost eight characters of the input, left padding with zeroes as re...

Get it through your support provider. The title of the OEM manual is Orchestrate Operators Guide. But request ALL the Orchestrate manuals, there are gems in each of them.