DSXchange

gateleys wrote:

DSguru2B wrote:I definitely do not want to use FMT(InLink.PRICE, "R2") against every decimal types.

In the Transformer select all the decimal columns then right-click and choose Derivation Substitution.

In the window that opens, type Fmt($1,"R2") in the expression field and click OK.

You may need to configure the ODBC driver so that its data source is the database rather than the data table file. Even so, being a readonly table ought not to prevent your selecting rows from it.

Double ampersand (only do command 2 if command 1 succeeds) would be even better.

And, yes, && is supported by the CMD shell.

These could, of course, be UV tables created by a UV stage or DataStage/SQL CREATE TABLE statement (which complies with pertinent standards).

The CREATE INDEX statement also complies with pertinent standards, but can not be used on a hashed file that was not created with a CREATE TABLE statement.

Original post marked as server Server Jobs The Format tab supplies to the reading process how null is represented in the file. By default this is empty, but should be replaced if null is represented in some other fashion (for example "<NULL>"). You can override this on a per-column basis by scrolli...

What's the original source for these data? Seems to me to be a good case to use CASE in the SQL SELECT statement here.

You're not right.

They get installed wherever you specify, as part of the installation process.

None of the code following the call to DSLogFatal will ever be executed. A documented side-effect of DSLogFatal (with two arguments) is to abort execution immediately without even returning from the routine that invokes it. I do trust that your controlling job sequences can handle this situation. I ...

The quote from Chuck Reid in DSGuru2B's post is entirely apposite here. Can you create a specification of how you might determine what is present and what is missing? If so, you might be able to determine techniques from that. How would it affect your source-to-target data mapping if this were the c...

Specifications, specifications, specifications! If you specify what is a "good" message, you can create a filter that only passes these. The remainder may be discarded or captured at your pleasure. It may also be possible to perform some filtering in the queue manager (or maybe even the object autho...

Hi ray I again can't see it. premium content problem,can u plz again unmark it!!! No, precisely because it IS premium content. It provides a succinct solution using intrinsic DataStage functions. Premium membership can be yours for less than $1 per week. Shudder at the thought of how much you would...

The problem here is that (as you have drawn the diagram) the Seq2 file is populated from the Seq1 stage (rows that do not match the metadata). I feel that that's not what you've really designed - try wrapping your ASCII art in Code tags to preserve its formatting. You believe that parallel and serve...

Currently there is no way around the problem of not being able to specify two input streams to the QualityStage plug-in in DataStage. It's a deficiency in the way the plug-in was written (or maybe its author was unaware that a two-file match required two inputs, having only encountered UNDUP matches...

Have you licensed parallel execution option? Certainly for the .par file to exist requires that this has been done.

Do you HAVE the lookup table? How will it be maintained? For example, XE.com have a data feed service available.