DSXchange

Yes and yes.

You can use any well-formed UNIX command as a Filter. The Sequential File stage will consume stdout from the filter command.

The Sequential File stage can run in parallel if you specify multiple readers per node or specify that it is to read more than one file.

The Sequential Stage is not performing poorly. Create this job to prove it: Sequential File > Transformer > Sequential File and use a constraint of @FALSE in the Transformer stage. Now ask yourself what you're asking Oracle to do. In particular are the three columns mentioned in the WHERE clause ind...

Then your field does not contain null. Maybe it contains "". This is not the same as null (null is "unknown value", whereas you know that "" is a zero-length string).

Start by having enough END statements (you need one for each THEN, one for each ELSE, etc., when the preposition is the final word on its line).

Use the formatting tool in the routine editor to make sure things line up properly. Clearly, from your posted code, they don't.

Set the Null Field Value property to BLANK for that column.

There's no error in any of that. ##I indicates an informational message, ##W indicates a warning.

You can also consult the readme files at Fix Central, as well as the "what's new in this release" documents at Information Center.

I think the comment reflects the perceived fact that people are choosing to use tools they know (SQL, shell scripts) rather than put in the effort to learn how to work with DataStage. Such people are missing out on the really heavy duty lifting capabilities of DataStage, as well as the rich set of c...

Fix Pack 4 should be a roll-up of everything previous. Check the readme file.

Meh.

Try working with Defence and Taxation authorities. I'm doing both at the moment. MUCH waiting on bureaucratic processes and even then what they give you may not be what you asked for.

Don't get me started.

Do you mean that the parameters are resolved (to fixed values) without your being prompted for values when you use the data browser?

Alas that's something I can't answer. Even in the Advanced DataStage class the statement is made that the buffer "resists input" - no mention of the actual mechanism.


Maybe you could take that class and ask the question when the module on buffering is being presented.

Indeed. As noted in a different thread right here on DSXchange, there is a Big Data stage available for version 8.7, which is essentially a Sequential File stage that connects to a Hadoop file system. So you get all the benefits of the STREAMS I/O module still, with straightforward access to Hadoop.

That is almost certainly the problem. Automatic linkage relies on the full hierarchy of hostname.data_store.data_source.table. That is, what DataStage shows as the Locator.

It's semi-automatic - you have to run "metadata workbench automated services" to stitch the bits together. This can be done from the GUI or from the command line. This only links table definitions in DataStage to implemented data sources. That said, you should get totally automatic linkage...