DSXchange

Can you give us an example of a "false positive" - that is, an instance where DataStage said they were equal and you say they're not?

Yes, but with DSLogInfo() and its ilk we have no control over the key. Presumably DSD.WriteLog gets the next key (event #) value from the control record //SEQUENCE.NO and increments that. Yes, looking at the VLIST output will verify that supposition.

It's not shared memory, it's private memory of the player process executing the LUT_CreateOp operator. The same memory will be used subsequently by the LUT_ProcessOp operator. (These form a composite operator generated by the Lookup stage - you can see it in the score. They may be combined into the ...

Problems with DSD.WriteLog() might be in the hashed file itself, or the key value supplied (indirectly), rather than in the code. This function has been around since version 1.0, so I do suspect that that's the case. Is your control a job sequence, or a job control routine? If the latter, can you id...

But when the data volume is learge, it is taking more time to execute the job. Naturally. My understanding is, we should go for 'Hash partition' using the key attributes. But I am confused, where exactly we should sort the data based upon the key coulmn? Whether we should go for explictly/implicitl...

The number of dynamic hashed files open on the system is returned by the command $DSHOME/bin/analyze.shm -d | wc -l That DSD.WriteLog() failed would ordinarily suggest that the log is the culprit, but your CLEAR.FILE should have fixed most known log problems. The obvious question to ask is "what's c...

Not really. Make sure that you have configured the data source and the match passes accurately. Try moving one of the match passes into the holding area. If that works, try reinstating that one and moving the other into the holding area. In short, try to narrow the focus of your diagnosis to identif...

The previous two posts are woefully inadequate, in that they only refer to one of the tasks that can be performed using a Lookup stage.

Welcome aboard. If you Search the forum you will find that this has been answered before.

Try changing the APT_STRING_PADCHAR value so that it's not NUL.

From a file is easily doable; use cat or head in an Execute Command stage (or type if it's Windows). Strip the field marks from the $CommandOutput activity variable. Reading a row from a table is probably easily done with a server job. Use the user status area in the server job (the $UserStatus acti...

Limit in the SQL that extracts data to load in the hashed file.

It exists. Select them all, right click and choose Clear Derivation.

Because there's no other way to accumulate them all. Of course, if you want to report separately from each failed lookup, then you would not require the Funnel stage.

Were you to bother with a Search you would find that an equivalent parallel function has been posted. (You also need to be aware that Change() function and Ereplace() function are essentially identical.) Search this forum for Ereplace.