DSXchange

You can't pass it to a property of the Surrogate Key stage.

The node pools list must follow the fastname declaration.

It's almost exactly the same for parallel jobs. A prior job (which may as well be a server job, since it's only going to process one row) captures the next available key and stores it somewhere (a file, its user status area, whatever). The job sequences picks up that value from where it's stored and...

Please post your configuration file, and report what settings you have chosen for the node pool in which the Aggregator stage is to run.

It's NOT EBCDIC. It's perfectly readable and the code points correspond to ASCII. "I have some information about the record" is simply not good enough. You must have ALL of the information about the record. Once you have this you can read it with a CFF stage or with a Sequential File stage. Create t...

Get more memory.

Increase the size of the process table.

Run fewer jobs simultaneously.

If your incremental load contains creation dates from all years, then your approach (assuming it works for full load) should work OK for incremental load. I'm dubious about comparing something called "...date" against a job parameter called "#YEAR#" - maybe I'm more finicky about meaningful names th...

Welcome aboard. :D Your question is too vague. It would require someone to type in the Version Control manual. But you have this manual, on your DataStage clients CD. Read through it. If you have Version Control installed, it has its own help, and you could read that, too. Then, if you have any spec...

Remove Duplicates stage.

Missing a "g"?

I wouldn't be at all surprised if the OP requires $JobStatus.

Something a site chooses to implement.

Nothing to do with DataStage, though that may be the tool used to populate these tables.

My guesses would be as follows.

Error processing table records any errors generated within ETL processing.

Audit table is used to store row count reconciliations.

Better mark this one as resolved, too!

Look in the job that was supposed to create and populate the Data Set.

Some authorities refer to this link table as a "factless fact table" - its purpose is to register the many-to-many relationship and nothing else. Subsequently you may add some kind of measure to this table, but it doesn't need one. But, as narasimha pointed out, the link table has to be kept up to d...