DSXchange

A hash file is a tool for shaping a block of hash. The things you work with in DataStage server edition are hashed files. Please get the terminology correct.

DSXchange has a convention that, when you mark a thread as resolved, you make a posting indicating HOW it was resolved, to aid future searchers. Please do so. It doesn't matter that it was human error (you don't have to say whose); but what went wrong and how it was fixed are valuable pieces of inf...

Cool, I've learned something useful today. :D

Are you using WebSphere Transformation Extender? Any answer you get in this forum would relate to WebSphere Transformation Extender (TX) and unlikely to be useful. Have you performed a Search? I suggest vertical pivot might be a good starting point. Please post your question in the correct forum, na...

Is there an error code with the error message?

Can you successfully, and as the same user, execute this command outside of DataStage?

No, you can not make it dynamic. The table name can be a job parameter but this would only be useful if each table (worksheet) had the same metadata.

Prepare data for Match stage as follows. Output links leading to frequency tables have been omitted for clarity: you will need them. +----------+ | | +->| Stan_1 | +----------+ | | +------->| | | +----------+ | | | | Join_A | | +----------+ | | | | +------->| | +->| Stan_2 | +----------+ +--------+ ...

The ODBC table name should be the same as that of the "system table" whose metadata you imported (including the "$" character).

First, disable operator combination intelligently so that the stage that is generating the error can be known. Second, read the message carefully. It relates to how the decimal number is stored in binary form, and suggests that what you've read is not truly a decimal number (in binary form) - it may...

Unless I have missed something, a Standardize stage can only deploy one Rule Set. On that basis you will need four Standardize stages, one for each Rule Set. You will also need an artificial key so that you can re-join the partial records downstream.

As far as I am aware, U has not provided the way to determine the exact number of processes. Nor have I produced such a document. Among other things you need to be aware of when buffer and/or tsort operators will be inserted, which stages generate composite operators, and when operator combination w...

Maybe but that's just a guess.

Can you please obtain a premium membership?

Premium membership is one of the ways that the hosting and bandwidth costs of DSXchange are defrayed. If I were to accede to your request I should be undermining that mechanism, and therefore choose not to do so.

In my opinion too many people are hiding on DSXchange behind crazy nicks and generic email addresses. It would be nice to know a bit more about everyone. Perhaps DSXchange could offer entry into a prize draw for anyone updating their profile with accurate information. No need to change the posting n...

The only fix is to get it right. Upsert (with insert invoked) requires a key. The fact that you've been relying on what really is a bug in server edition ought not to mean that they should propagate this into enterprise edition.