DSXchange

You'd actually need to combine the two answers.

Just responding to your comment that 'The only way to do it is to recompile the sequence which will clear all checkpoints'. You can reset the sequence rather than recompile it to clear all checkpoints.

Reset, not recompile.

That's too many at once - run less than 12 simultaneuously.

... and are small.

Only pass along the hashed lookup failures?

How are you expecting it to be interpreted? If you are trying to pass it to a job's parameter, then you need to include the name of the parameter to set with an equal sign between to create a 'name value' pair. Try: set paramfile='type=c:\parameters.txt' I'm assuming 'type' is the name of the parame...

The links will execute in order, the 2nd waiting on the 1st.

So... you pinch hit?

(and you have my official blessing to prolong the hi-jacking)

Actually applies to the client as well. While older versions could be installed on XP Home, I believe that starting with 7.x they block installation on that O/S.

We'll need to wait for Uncle Ray to come back... not really sure why this would be considered a 'strange game'.

Typically, yes - in a mixed-mode environment the 32bit libraries are explicitly named with '32' at the end. The 64bit version aren't. So...

lib = 64bit
lib32 = 32bit

For a single 'at bat' I suppose, but I'm guessing there were more involved.

Copy and paste a warning from the log here.

You don't need to get a hit to get an RBI.