DSXchange

One thing to keep in mind is that key values from the Update input are consumed - this is different behaviour than that of, say, the Lookup stage. But if that were the "fault" I would have expected you to say something like "nearly all the rows", not an absolute statement such as "all the rows". Unm...

<color=blood>Customary practice here is that you make a final post letting future searchers know what the answer is, and mark the thread as Resolved.

Only the original poster can mark the thread as resolved.</color>

Did you reinstall the loopback adapter?

Can you telnet to 127.0.0.1?

<color=blood>Customary practice here is that you make a final post letting future searchers know what the answer is, and mark the thread as Resolved.

Only the original poster can mark the thread as resolved.</color>

...which, in turn, comes from the most recent DTM value in the DS_AUDIT table entry for that job.

For speed or retrieval to clients, there is a VOC entry called DSR_LAST_UPDATED that contains a summary of this information for all Repository objects.

That's easy. Buy yourself some ghee.

Can you please describe all the properties in your Merge stage? What you are claiming is not consistent with the way the Merge stage is supposed to operate.

ray.wurlod wrote:...if your derivation expressions have been constructed as assignment statements, which is not correct, then you would usually expect to see zeroes...

I spotted it even earlier!
FIGJAM

That's what i'm trying to prove to tgmedear.

DataStage DOES preserve case sensitivity. It's Windows that doesn't.

My point is that is does (keep their executables separate). The routines must have different names. Their different executables are eponymous files in the DSU_BP.O subdirectory in your project. You simply can not have two routines of the same name in the same project. Prove this with the following q...

Try changing the unmatched masters mode to Keep.

Create a Reject link from the Sequential File stage that reads the file. This will capture all rows that do not match the metadata. Send them to a Peek stage - you can then view the data in the job log in Director.

That is correct. But why would you want a DF with less than 999MB of reference data?

Routines are stored in a hashed file called DS_ROUTINES. The routine name is the primary key. Hashed files are updated via destructive overwrite. It should, as a result, be impossible to have two routines of the same name in the same project. Category is a non-key field in the Routine's record. I th...

Merge stage requires at least two inputs and the same number of outputs. Is this not your entire job design?