DSXchange

What about holidays?

You NEED a time/calendar dimension table, and you need a holiday table.

... and have any rolled out service pack 3 ?

Yes.

Using this method for connection to the server, CD to the folder in which DataStage engine is installed and verify the integrity of UV.ACCOUNT.

You might also mention what map name(s) you have specified. Parallel map names are not the same as server map names.

Scratch space is on disk.

There is no environment variable that affects it (except, indirectly, APT_CONFIG_FILE, which names the directories to be used for scratch disk).

Don't specify float or dfloat, and always specify both precision and scale for Decimal data types.

To open the dictionary with OpenPath, specify "D_hashedfilename" as the entryname portion of the pathname.

Waves have been in the product since version 1.0.

Double click the entry for any completed job in Director status view. Wave number is reported.

It is almost certainly not worth upgrading to 8.0, because that version has been superseded by version 8.1 which has fewer bugs. That said, it's a BIG step. You will need much more server capacity and client machines with minimum 2GB of RAM. Eventually you will need to upgrade, because eventually IB...

Designer is the only Repository management tool in version 8.0 and later.

You can not run any jobs through a Sequencer.

As nagarjuna notes, you can run as many jobs as you like (given sufficient server resources) through a Sequence.

A Sequencer is a component in a Sequence that makes a decision about whether any or all of its inputs have been triggered.

Welcome aboard.

Step 1. Add many dollars to your IT budget.
Step 2. Buy IBM's high availability solution, which can only purchased as a service option (that is, IBM people come on site and implement it for you).

You can use them anywhere.

As with every other link*, the data end up in a virtual data set.

The only possible input to and the only possible output from an Orchestrate operator is a data set (virtual or physical).


* The single exception is a sparse lookup.

Find a Specification in the Modify stage that begins "FOCouponFreq=".

Beware that wired and non-wired ODBC drivers operate differently.