DSXchange

Upgrade to version 8. Then you get a comparison tool.

-server is indeed a valid option for dsjob command. Read the generated syntax a little more closely.

Have you reviewed the capabilities of the Compare stage?

Where is UNSET coming from? The special token that can be used as the default value for a job parameter has a leading "$" character (that is, $UNSET) but, in any case, reference must be made to the job parameter itself, not to its default value, within the "#" characters.

As with any other UNIX command the directory containing the dsjob executable must be mentioned in your command search path (the PATH environment variable), or you must supply the full pathname of the dsjob executable.

Check to see whether RT_CONFIG242 is corrupted. For example executed from Administrator client command window.

You can pick up the date from the @DATE system variable when assigning the job parameter value in your job sequence. You probably want to convert this to a "human readable" format in the assignment expression, for example

Read-only hacks are permissible!

I believe this technique will continue to work through versions 8.x - though I have yet to verify that. In any case Brad (the OP) is still on version 7.5.

Not quite true. If 4.5 million rows is smaller than the hashed file write cache size then the use of write cache could be explored, as could not loading unnecessary rows and columns into the hashed file in the first place. It might also be worth exploring the use of static hashed file but, when push...

You should have mentioned the -2 error code (DSJE.BADSTATE) earlier!

Do you invoke your jobs with "reset if required, then run" in the job sequence?

or
if the target field requires the capability to carry NULL.

Provided that they are all distinct values, no. Your examples do not form a distinct set, though I understand that you have obfuscated the actual values. XXXXXX appears twice for example. So does XXXXX. If the same invocation ID is given twice (or more) the first instance will start but the second a...

What do you expect? A hashed file is on disk - you are writing 4.5 million rows to disk. Not much else is happening, so it shows the disk subsystem to be 100% busy. That ought to be no surprise.

The correct terminology is hashed file.

For all the impatient folks out there, here's a listing of the file dictionary from the DS_LICENSE table. LIST.DICT DS_LICENSE Type & Field......... Field. Field........ Conversion.. Column......... Output Depth & Name.......... Number Definition... Code........ Heading........ Format Assoc....