DSXchange

Visit the data provider and make appropriate threats!

I'd probably generate a full set of rows using a Row Generator stage and left outer join that to the provided data.

I think it might be a byte order issue, as Craig suspects.

They're running on version 9.1.fp1. I don't think it's available at that version. Maybe with Fix Pack 2 (would have to research that).

Expressions in parallel transformer stages are actually in BASIC. They are translated to C++ during "compilation". However, multi-statement blocks are not available in expressions; indeed no form of statement is available in an expression. I continue to maintain that your example could be ...

Does anyone have experiences (ideally successes) with using any of the XML or Hierarchical Data stage types to work with XML data described by the GS1 XSD schemas (http://www.gs1.org/edi-xml/technical-us ... _hierarchy)?

Try explicitly setting Precision to 65535 for that column.

No, complex expressions are OK in DataStage BASIC, but you have to know the rule that every multi-statement block has to be terminated with an END statement. However, in a derivation expression things are different. You're right that you cannot assign work variables (use stage variables for these). ...

Certifications are usually either free or heavily discounted if you take them at IBM conferences, such as World of Watson next October in Las Vegas (the conference formerly known as IBM Insight).

If the data are accurate and accurately sorted you could use a Remove Duplicates stage and keep just the Last value from Column B for each group of Column A values.

The connection should be via the node agent to the ASB Server, and then to the Connector Access Service.

You could create a logging view on CAS to see what is happening.

Take a look at the Resource Estimation tool (and, possibly, Performance Analysis tool) in DataStage Designer.

Have you implemented DataStage Operations Console (which was new in version 8.7)? IF so, that would show you much more useful information.

For Entire partitioning there is no point in reporting the other nodes.

Indeed, in an SMP environment, only one copy of the data exists, stored in shared memory that is accessible by all nodes.

Given that most Enterprise (and older plug-in) stage types are being phased out in version 11.5, I would counsel using Connector stage types as much as possible.

Assuming that all three columns are defined as VarChar, there is nothing wrong with your data from a metadata perspective.

One of my "must do" tasks when a new release becomes available is to explore all the menus. If I have time, I create a lightly documented menu map (for my own convenience).