DSXchange

When you did your tests, did you use the exact same compiler options that DataStage would? The ones you just posted, in other words?

Also, please let us know what kind of volume you're talking about here and how long the actual run times are for each. If we're talking 3 minutes versus 4 minutes, that's not much of a conversation but 3 hours versus 4 hours might be worth digging deeper into.

Those would be questions for IBM, I would think... unless someone here has already asked them and knows the answer. But it still seems to me it should come from the horse's mouth.

I don't believe there is any time limit.

And you are certain you used the correct value? Unfortunately, I've got nothing else to add except to suggest contacting your official support provider for help.

Sequential files don't have a data type other than "string". The ones you listed are all available in the stage, however, with Date/Time being called Timestamp here and string being either Varchar or Char.

Never used PX on Windows, so can't really other than to direct you to search for other posts on the topic. Have you verified that you can compile something outside of DataStage to try and isolate the issue?

The 'abort after rows' option means literally that - once that many records go down the link the job is aborted. Plan your constraint accordingly.

So... in other words, you can't ask for official support because you don't have a license for DataStage on Windows?

Please delete your duplicate post before someone replies to it. All that posting your question multiple times does is upset the natives.

Let's be more precise - your job is not running or it is not compiling? Big difference. For the latter, let us know what compiler you installed, the options you are using and if you installed it before DataStage.

I assume by 'parallel setup' you actually mean 'parallel startup' and have removed that factor from the comparison. After that, you would need to verify that both jobs do in fact run the exact same query by checking both explain plans while they run. You would also need to run the PX job on a single...

Hmmm... perhaps match based on three, allow multiple values to be returned from the lookup, order by length desc and take the first match per group?

One of the best references out there is here.

As far as I know, you'll need cascading lookups - five of them set to continue if they fail. First one checks for a substring of 7, the next 6, etc.