DSXchange

That's exactly the kind of thing QualityStage does well. You can use your xxPREP rule set to lump absolutely every element into domain-specific single fields, and have the domain-specific rule sets (xxNAME, xxADDR, xxAREA) process these. Or, instage of using the xxPREP rule set, you can assemble the...

But first check that the executing user has appropriate privileges to the target table.

Why? There's already an SDK routine for logging informational messages.

It would be possible off the old logs, assuming you either have not purged the logs or that you have archived them. The start date/time and end date/time are easily extracted, and some sort of "between" comparison performed. As Craig notes, if you have ETLstats or something similar, the in...

Given that OCI8TO9.B is a (compiled) DataStage BASIC (main?) routine, my guess is that it traverses DS_JOBOBJECTS garnering information from there and from DS_STAGETYPES to effect the change to any OCI stage records in DS_JOBOBJECTS and/or the records of any links that connect to OCI stage types, as...

Anyone thought to mention the XMETALOCKINFO table?

No it's not. There never has been, and never will be, the possibility to promote warning to fatal. There are too many implications.

Disable operator combination so that you can determine which operator is actually throwing the error.

Possibly not. But I don't have the opportunity to test that at the moment.

IBM do have such a tool set, but offer it only as a service. I believe you still have to agree to your application being "offshored".

Tell us about the sorting and partitioning used in both environments.

This is very easy to do in a server job. Are you prepared to go that route?

Write into a hashed file or UniVerse table normalized on a multi-valued field then read it back un-normalized, converting the value marks (@VM) to whatever delimiter you require.

With one node all records are on that node, so your choice of partitioning algorithm will be irrelevant. However, the optimizer may still insert sort and partition operators on the Join stage inputs.

I know for a fact that there is none.

DB2INSTANCE is not part of DataStage unless you make it so (for example by including it into the dsenv script).