DSXchange

A sequencer (something you can include in a job sequence) simply applies an "any" or "all" test to its inputs to trigger its output.

Documentation about job sequences is to be found in the DataStage manuals, rather than in the QualityStage manuals.

Can't see why not. A parallel routine definition (a pointer to the actual routine) would have to be set up in each project that needs to use it, but there need only be one actual routine. Be very, very careful to undertake regression testing if you ever plan to change this routine, and add emphatic ...

Any time you have problems with a *.so file suspect your shared library search list (the LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH environment variable).

Use a Transformer stage. On its input link use column names A, B, C that correspond with those you have defined for the sequential file (though, to be honest, the Sequential File stage does not care about field names - you could as easily use H, P, Q). On the output link of the Transformer stage, wh...

Each ? is what is called a "parameter" marker and corresponds to a column in your job design on the link to which the SQL applies. If the column is marked as Key the parameter marker corresponding to it goes into the WHERE clause. Non-key columns match match in data type and number with the columns ...

In a Batch job you use a call to DSExecute with "UNIX" as the first (shell) argument.

Search - this question has been answered at least twice in the past.

APT_CONFIG_FILE environment variable (which might be a job parameter).

Do tell. Iconv() and Oconv() are not available in parallel jobs. You will need to convert the date portion into a date and then back again to a string with a different format (StringToDate() and DateToString() functions) then concatenate the time portion and the seconds (":00").

With one reader per node, the Sequential File stage will execute sequentially. But you will note that there is a "fan out" icon on the link between this and the next stage, indicating that the next stage will execute in parallel (which you can verify by inspecting its Advanced tab).

There are no limits in DataStage - never have been. The only limits are those in the operating system. The only exception is hashed files, which do have a limit: 2GB unless created/resized to use 64-bit addressing, in which case the limit is theoretically approximately 19 million TB (assuming you ha...

Why are you trying to run a Korn shell script in a Bourne shell?

False.

There will be a partitioner between the Sequential File stage and any downstream stage that executes in parallel.

Further, for sufficiently large sequential files, you can assign multiple readers. If you assign N readers, each processes 1/N of the lines in the file.