DSXchange

I was afraid someone was going to ask that question. Afraid I don't know. It should be standard C++ syntax, the Operator's Manual section came from Rogue Wave documentation. You could join the www.roguewave.com website and get some of the resources on C++ coding, they might have additional informati...

Good rant though. I think we all get a shock the first time we build a parallel job that reads or writes a sequential file and we get more warning messages then information messages. By comparison server jobs were very forgiving. I always though empty strings and nulls were the same thing in a seque...

You retrieve the highest surrogate key already used, add one to it and pass it into the job as a job parameter. The job then starts incrementing from that number to ensure you do not get duplicates. You can retrieve the existing maximum surrogate key in many ways depending on what database you are o...

We usually leave it at the default combine mode for faster processing. The only time we change it is when a lookup and a transformer get combined and the reject behaviour becomes different to what we want. You can have a lookup stage with no reject link that sends rows down the transformer reject li...

From a career point of view the parallel architect is the future of the product suite and all new functionality is going into parallel job, server jobs are in cruise control. Most new customers will probably want to use enterprise edition. There are still a huge number of customers with server editi...

The Ascential devnet site has most of the 7.x release notes posted to the DataStage forum. For release notes earlier then that you need to either get them from Ascential directly or get a login to the online Ascential esupport web site, it lets you download documentation such as the install and upgr...

I think it is better to do row counting after the job has finished. Trying to embed row counting into the job only slows it down and adds a development and maintenance overhead. There are plenty of ways to do row counts, see the FAQ forum thread on DataStage reporting options such as MetaStage and E...

So you are still getting the error after the nullability change? Try breaking the job down, save it under a new name, start deleting transformer columns. Delete a few at a time until you isolate the columns that are causing the error. It is likely to be a column used in a condition derivation such a...

I have used PX running on Linux and it runs very well. I have heard that you can have longer installation times on Linux as you need to install some libraries that are missing on a standard Linux install but that are default components on Solaris. Can't help you with any details though!

Remeber that @outrownum works different in parallel jobs, when the transformer is partitioned each instance will start at 1 giving you duplicate counter values. When I need a unique counter in a transformer I use a Stage Variable, set it to a starting value of @PARTITIONNUM-@NUMPARTITIONS+1 and incr...

There is a message in the FAQ forum on project specific environment variables, these can be migrated between projects by copying the DSParams or copying the User-Defined section of the DSParams. If you are talking about ENV variables set to the value of $ENV then this needs to be done at the operati...

I use Kim's saveasbitmap script with a modification to generate an XML report along with the bitmap. This provides a context sensitive bitmap where you click on a stage on the bitmap and it takes you to the properties for that stage. Designer.exe /H= host /U= User /P= Password ProjectName JobName /R...

Sparse lookups have a limitation that normal lookups do not have, they need the lookup key fields to have exactly the same names. If you switch your database stage to sparse and then look at your lookup stage properties you no longer see the lines that join your primary columns to your lookup key co...

I couldn't see a new thread for your "Failure during execution of operator logic" however it is almost certainly related to your NULL value problem. When you moved to test you started to see a huge number of NULL value warning messages, probably because your test database has different data to your ...

It all depends on what warning messages you are getting.

You shouldn't be getting any warnings. At worst you should be getting a handful of warnings due to a null handling or implicit conversion clash that doesn't cause any harm.