DSXchange

A Lookup stage needs to load the entire reference data set into memory. It would appear that you don't have enough memory for this. You need to re-think your design - perhaps load the reference data set into a database table and perform the BETWEEN join there.

Welcome aboard.

The only place you'll get this is (a) from the vendor if you can convince them that supplying the same will lead to a sale, or (b) by buying some time in the Cloud.

Licensing rules stringently forbid redistribution of the software.

You could, if you have it, use the VEMAIL rule set in QualityStage.

Once you've resolved the disk full issue, you might also like to check how many subdirectories exist in your project directory and whether your operating system as a limit on these.

The other thing is that you have to pay to take the tests. So, if you're not properly prepared, you're wasting your money.

What Andy means is Note the extra "-param" ahead of CURRRUNDT.

Repartitioning will destroy sorted order. "Same" will preserve any sorted order.

When Ascential acquired Mercator, the product was renamed DataStage TX. When IBM acquired Ascential, they put all the DataStage products under their WebSphere brand. When the InfoSphere brand was established, they decided that TX properly belonged in the WebSphere brand. DSXchange seems to have rema...

Beware that the dsjob command may take longer to execute than your job, and may therefore generate erroneous results. However, you can check for the "job controller", which is the name of the job that started this one - and is empty if this job is a singleton or at the top of a hierarchy o...

You can write to the Parameter Set values file before invoking the job. This would substitute the existing "default" values in that file. You would, of course, need to ensure that that particular values file was chosen as the "value" of the Parameter Set when the job run request ...

We believe that there is, but there's none documented, and it depends on a number of factors primarily the amount of memory you have available.

You need to go into the Transformer stage properties and mark the link as "Reject". It should have no constraint expression, just check the box.

Never use reserved words as keywords such as column names.

If you're stuck with it, use double quotes around the column name. This turns it into a "quoted identifier" which means that certain checks (such as for illegal characters, reserved words, etc.) are bypassed.

Which stage types can be used in which job types is easily established - just look on the Palette for the job type that you have open.