DSXchange

From the IBM training class "Metadata Workbench Essentials":

• blue line = operational metadata
  
  orange line = design metadata
  
  green line = user-defined data flow

Check on the Columns tab on the Output link in the Data Set stage. There should be an RCP check box there.

Right click on the table definition for each hashed file and click "Where Used".

Or do the same for the Hashed File stage type. Or do that in Metadata Workbench.

The ones created when the project is created have names beginning with "RT_".

No. An explicit transformation will be required, as there is no implicit transformation from Decimal to Date.

Is runtime column propagation (RCP) enabled on the output link for the upstream stage?

Lookup loads the reference data set into memory, so that your lookups are performed in memory (at memory speed) and there is no need to sort the data (a hash table index is also created in memory). Join does require that both its inputs be sorted.

The old DataStage Designer (still the current one, not the new browser-based one) is a real mongrel, with bits of VB, bits of C, bits of C#, bits of C++, bits of Java (not much), and probably bits of someone's leg. And the plug-in architecture means that server plug-in stages can be written in any l...

If you're happy with 21th there's a very simple solution. Otherwise you're up for a small amount of coding.

The only stage type with Complex in its name is Complex Flat File stage. This might be used to perform a lookup against a COBOL-generated source in a job design that has been exposed through Information Services Director to be a web service.

OK, maybe it only works in BASIC-based components, such as the BASIC Transformer stage.

Thanks, Eric and Ernie. I'm operating on "the customer is always right" principle in seeking the answer to their question. Looks like I'll have to answer them in terms similar to those you used.

(The client is a bank - they're fussy about these kind of things.)

That shows only that the expression editor parser doesn't like it. Does it compile and work properly?

The log is called SystemOut.log, and it lives in the WebSphere Application Server directories, for example /opt/IBM/AppServer/profiles/server1/logs (your pathname will almost certainly be different).