DSXchange

Arnd is correct. You will need to use istool import command.

Use server job components loaded into a server Shared Container which you can (if the rules aren't violated) use in a parallel job. The rules are in Chapter 2 of the Parallel Job Developer's Guide.

Have a look under Tools > Options in the Designer client.

It's not immediately a partitioning issue. Try writing out (in language, not in code) the rules that describe how each output row is to be produced.

Actually the constant needs to be 1, or DSJS.RUNOK. 0 means "running".

Everyone has access to Fix Central, where you can get that answer yourself and, indeed, download patches relevant to you.

Go to Kim Duke's website and download his material on completeness testing. It's likely that not all rows in those "works fine" jobs made it into the file, but that no rigorous testing was done; the fact that there were some rows was taken to be success.

Of course you can be diligent about not hovering over the job name.

This is probably not a NLS problem. There's something Sybase doesn't like about your job's metadata for the 19th column.

DataStage allows it because it does actually work on some (few) operating systems. Chances are that the lines are interspersed.

The literal for the PREP rule sets is supposed to encase a two-character ISO country code. This literal specifies the default country code to use if the logic of the rule set cannot determine one - in this case the flag is set to "N". Do you still get the warnings if you use "ZQUSZQ&q...

The right people at IBM do read this forum. They do note what's written, whether or not they choose to do anything about them.

This should not be happening. [xFD] is a UniData value mark; it should be able to be handled correctly. Check with your official support provider.

What overrides exist in your USPREP rule set?

Your original post specified 8x, which is probably why Mike responded as he did. In earlier versions you have to do all the coding yourself; the lookup on the business key, the testing to see whether the row exists and, if so, whether there are any changes, the generation of the new key value and th...