DSXchange

ERwin 7.0: No. Cognos 8.0: No. From ERwin you could, of course, generate DDL from the physical design, execute that and import the table definition. It may be possible to install Cognos Powerplay (it's optionally installable in version 8) and use the PowerPlay Metabroker. For import, an ".MD1" file ...

I understood the requirement to be to sort the aggregated data. This would involve stages in a different order; a sort (or Sort Merge collector) following the Aggregator stage and something (Head, Tail or Transformer stage perhaps) to filter the first or last 100 rows.

The output from the command contains line terminators. So that a single string can be returned infallibly, DataStage converts the line termintators to field marks (which can be represented by the @FM system variable).

As happens most weekends, I was posting from an airport lounge. That means everything is from memory, the ability to cite specific references somewhat dimiinished. What Craig's posted looks like the right area to be in.

The same word, but in italics.

It's actually DCS Strategies (the company that supports DSXchange) that offers the Server to Parallel Transition Lab. Each time one is scheduled to run, it will be advertised on DSXchange. If you'd like to get onto a wait list get in touch with the Editor. Better, if you could round up enough folks ...

You only need one Transformer stage. Perform the two lookups to the same hashed file from this stage. Zero, one or both will succeed. Your constraint expression could have the form

It's well explained in the manuals. You can either mount the location of the binaries on the other machines, or enable rsh for distributing them. There is an environment variable (whose name I can not presently recall) that governs the behaviour.

For those of you thinking about making the brain transition to parallel jobs, the same restriction applies - no stage that accesses persistent data is permitted to have both an input and an output link (apart from reject-handling links).

You can only lookup using actual key values.
You need two lookup expressions, two lookups.
After that, check that either of the lookups was successful. (That is, the returned key was not null.)

Not only those, but also typewriter-based variants like the IBM golfball. I still have one of those.

Some of the early printers also perform physical carriage return and line feed. If you ever configured UniVerse (or even DataStage) to work with one of these, you included in the configuration a small delay to allow these physical activities to occur. These delays remain provided for, because these ...

You don't need to write the story about why they won't pay for your training. There is only ever one reason. We have an expression for it in Australia - "short arms and long pockets".

Don't forget the Help you get with DataStage. It's particularly well done as a means of getting to the desired information quickly; for example some useful portals (such as "BASIC Tasks") and "click on the picture" interfaces.

Is your XML file really comma delimited? That's very unusual. The stage gave up after not finding a comma (or maybe line terminator) in the first 100KB. I would, too.