DSXchange

So long as you don't run out of memory!

Fixed is the only choice. You specify the actual length through choice of data type for each individual column.

By storing the entire data stream on the SaveInputRecord stack, generating the counter while popping records off the stack once end of data has occurred.

The error message suggests that the SQL is not in the OCI stage, but that the SQL File property has been used and DataStage cannot open that file.

Some good answers in your identical post in the QualityStage forum.

If you run the job from Director (or Designer) client, the Job Run Options dialog has a tab where you can set the warning limit. You can also set the default for the entire project using Director client.

QualityStage legacy IS supported; there's a special stage exactly for that, as Robert noted. But far better to convert. Even if you don't use the free Concierge service from IBM Engineering, there is a conversion tool supplied with the Information Server software.

The philosophy of parallel job design is "one stage, one task". Unless you write it yourself there is no stage type that can perform both of these operations in "one shot".

Full outer join in Join stage should be pretty close to what you need.

Yes but you don't need either. You can do it with system variables.

Maybe they have v6.1 of xlC_r in QA and version 5.3 in Dev?

There is an option in the Lookup stage to perform a case insensitive lookup.

This is the configuration file for the xlC_r compiler. You are trying to use an old version of the configuration file with a new version of the compiler. The error message asserts that these are incompatible, and that you should be using the configuration file called vac.cfg.61.

The files on the resource disk are not descriptor files. They are "segment" (data) files. Descriptor files can live anywhere, and have ".ds" as their file name suffix. A Data Set consists of its descriptor files and all of the segment files to which that descriptor file refers. T...

My understanding is that IBM only ships this one for Windows-based servers (ditto for the SQL Server Connector).