DSXchange

That's not the default but if you've made sure that option is defaulting to on and it's still not working, I don't see what else you could do. There's nothing to change in the registry in that case.

OK, then basically what I posted. (no pun intended)

I assume someone pressed the Stop button in Director. I've done the same in the past and made a crazy assumption that when I saw 'Stopped/Restartable' as the status that I would get a checkpoint restart when I ran the job next. Problem is you cannot, you must reset it before it can be run again and ...

The part I was addressing was the 'using a wildcard on the file name' part. I don't believe that OpenSeq would support wildcards... or does it?

The resolution is there in the post before yours.

Have you tried exporting them, changing that attribute in the dsx from "1" to "0" and then importing them back? Wondering if they will allow themselves to be overwritten or not...

If for some reason you still "need" to do this: http://download.oracle.com/docs/cd/B12037_01/appdev.101/b10807/13_elems027.htm But pay close attention to the information right up there at the top. Oracle has extensive automatic features that allow multiple programs to read and write data s...

You can't. I have no idea why it works that way or what "Stopped/Restartable" is really supposed to mean when it cannot be restarted from the point of failure.

There are instructions to change that attribute here you could find by searching for NRO but I have no idea if that still works in the 8.x world and XMETA.

Then you've got absolutely nothing to worry about.

Probably significantly larger than you'd need... what exactly are you considering storing there?

Do you have any details on exactly what "the AS400 was upgraded" means?

Oracle will maintain the state of the data for you over the life of the source query without having to lock the table. That's a function of the 'transaction isolation' from what I recall. However, massive changes during that window can get you the dreaded 'SNAPSHOT TOO OLD' error. I would think a co...

Honestly, the best defense is a good offense. Make sure you don't generate those errors. Failing that, check the log 'after job' for messages like that and alert there.