DSXchange

IMHO, technically everything in Vince's list after #1 is CDD rather than CDC.

Then it seems to me you are firmly into Support territory. From what I've seen, the 8.0 release falls squarely into the "To Be Skipped" camp. IMHO, you'd be well served to upgrade as soon as practical.

Does it work if you fully qualify the pathname to dsjob? That would be a big hint as to the issue if true. Otherwise... fixpacks?

Yes, you can execute SQL from a routine but it is on the complex side which a search here for "BCI" would reveal. Easier to leverage the command line interface (like sqlplus in Oracle) via DSExecute().

Me, I'm wondering what "see the nodes" means here.

:idea: Please start your own posts rather than jump on the end of one that's over three years old. We really have no idea how "same" your same error is, what version of DataStage you are running, what operating system - all of which could be different from here and vital in solving your pa...

Partitioning has nothing to do with duplicates or "primary keys". As you noted, you are ensuring that all rows with the same hashed value end up in the same partition. This regardless of the fact of the incoming data's uniqueness - don't think that because your data is unique, the hashed v...

Doesn't that depend on the NLS setting of your Windows environment?

Are you current on your fixpacks? Checked with your official support provider? Without access to your job, not sure what else to suggest. Is this your first time using that stage?

Well, the stage certainly seems to think you are using a map file. What happens if you specify a value (any value) for that property?

Are you doing something with the collating sequence map file? The error relates to the structure of that file, not anything about your stream data.

Basic questions should be searched for first, more than likely it's already been asked and answered. For example, this may help:

viewtopic.php?t=136035

Why not simply process all "A" reports first and then process the "B"s? This regardless of how many of each are there in your control table, including zero.

So it is removing quotes rather than colons. And that is a well documented "feature" of DataStage, it does that by default. If you had searched here, you would find the fix is to escape them.

Sorry, but how to deal with what? You asked for and got the latest log entry, which is the normal message that Auto Purge logged when a job completes without error. Look at the log via the Director and you'll see that. Make sure you specify the newest what when you call the function. In your case, y...