DSXchange

The -param and -paramfile options are mutually incompatible.

Read the DataStage Programmer's Guide, the section on Command Line Interface.

It's pretty obvious once you start playing with it. There are three job designs that use the Surrogate Key Generator stage. With no links, the Surrogate Key Generator stage creates a state file. With an input link, the Surrogate Key Generator stage initializes a state file or obtains initial data fr...

This is a horizontal pivot. Use a Pivot stage or a Pivot Enterprise stage.

Sort in reverse order and use stage variables to remember previous value. Initialize the "remembering" stage variable to "". Re-sort if necessary downstream of the Transformer stage.

Read JOBCONTROL.H (or dsapi.h) to learn what they are. Then code them however you like. You can even search for them on DSXchange - I recall that someone once went to the bother of listing them all. Mnemonic tokens all begin with "DSJS." (DataStage Job Status).

On both outputs of the ODBC stage?

It may also not work, even if the data do look the same, if they are encoded differently (for an extreme example, ASCII and EBCDIC).

Get ETLstats (free) from Kim Duke's website - this will do all that and more for you.

If the reference data sets are small Lookup stages will be preferable to Join stages. If using Join stages you need to ensure that their inputs are correctly sorted. Have you given thought to the appropriate partitioning algorithm? You might consider using a single Transformer stage (with constraint...

There are variants available, like "%(m,v)/%(d,v)/%yyyy", at least in version 8.5.

dsinclude/JOBCONTROL.H

There's an information area that describes each property as it's selected (you can get the same information in a tooltip by hovering the mouse pointer over the property).

Business rules!! You need to become aware of the business rules that you have to enforce (for example a person's name may not contain a numeric character) and then implement these using DataStage logic. There is no "one size fits all" solution.

That may be a Sybase limit on the maximum column size returnable through a stored procedure. Please check your Sybase documentation.