DSXchange

On the plus side the conference has been extended an extra half day, sessions are longer going to 60 or 90 minutes for more in depth discussion, product demos have been moved into the partner pavilion instead of being in a seperate room and there are more training options following the conference. L...

AscentialWorld 2005 has been renamed to IBM Information Integration Live! That's their exclamation mark, not mine. I guess they are trying to make it seem like American Idol. It's Live! On Stage! There is nothing more exciting in the world then watching information integration Live! Look at that dat...

Set the environment variable $APT_DUMP_SCORE to true within your job to get better Director log messages. As previously noted post your config file. Have you tried testing the same job writing to a copy stage (save job under a new name, remove all stages except DB2 and add a copy stage). This is a u...

Looks like you'll have to upgrade to get the message handler and the equally useful conditional lookup stage.

To answer your second question the best practice is to deliver jobs to production that have no warnings during normal operation. You need to minimise warnings within the jobs through design and testing, you need to downgrade unavoidable warnings using a Message Handler (see the FAQ). It is very dang...

This has been submitted to Ascential as a GUI bug after being reproduced by support. Sometimes the Input Column field is greyed out. It can be fixed by unlinking the reference link and linking it again. It can also be fixed by shuffling links on the input link order tab (if you have more then one re...

Do you have CHAR fields that are empty? Even though it is delimited it could be the parallel job is expecting some type of blank padding character. Parallel jobs are more particular about metadata then server jobs. Sounds like changing it to varchar is the way to go.

Parallel jobs can use the same before/after routines as server jobs with the same performance on those routines.

The first syntax a limited ANSI standard, the second statement is the full ANSI standard and I always go for it if the RDBMS engine supports it. I think it is far more maintainable and less likely to give incorrect results through to coding errors. It takes you down the path of joining each table in...

I think you are barking up the wrong tree. The CPU % utilisation is not nearly as important as how long the job takes. Who cares about a 100% utilisation job that takes 3 seconds? Just work out what jobs are on your processing critical path, work out which ones are taking the longest and plan to reb...

You cannot view data using the PROJDEF or ENV parameter values, they just don't work within the Designer session. A bit of a bug in the product if you ask me. The only way to view data is to replace these values with the real values each time you view data or use normal job parameters in the paralle...

There is a sticky forum message on this over at the Ascential devnet DataStage forum.

http://developernet.ascential.com/home.php

Make sure you have write access to your Program Files/Ascential/DataStage directory and call support if it keeps giving you problems.

I have found parallel jobs to have more stages in them then server jobs. Better performance is achieved by not writing to disk so our jobs try to carry the data further. There is also a tendency to move functions away from external products such as the RDBMS engine and Unix scripts into parallel sta...

Erwin is fine for capturing the business rules on static data. But is it any good for capturing transformation business rules? We use Erwin to create our data model and add column descriptions to all tables, we push these into DB2, we then import the DB2 schema into DataStage. The column definitions...