DSXchange

There is? Dang! How's the weather down there in Florida now? We've been going up and down and back up again - 60s, 20s, 60s... with snow on the way again.

As noted, you need to have your UNIX Admins do a health check on cron.

Excellent. :D

Remove the Terminator (which aborts the job) and replace it with a Sequencer. Job just stops.

No, the WFF stage would have the same problem - see file, get file. The typical solution would be to utilize a semaphore file, a small usually zero-byte file that is sent after the main file. You poll for the semaphore and, when it arrives, go get the main file. Either that or you need to build logi...

That and stop yelling.

Load your input file into a work table in your database of choice, then use sql to create your output. Load both if the hashed file source isn't present there.

Never understand why people don't search. There's hardly a question here that hasn't been asked (and answered) before.

http://www.dsxchange.com/viewtopic.php? ... ++commands

What's "not working" about it? People here would need details or your issue in order to provide any level of help.

That too.

Perhaps, just posting my experience. YMMV.

That's not how the Exception Handler works. And adding it overrides the 'automatically handle' option. Remove it, use just OK triggers and let us know what happens.

Or build a version of the hashed file with only the one key that is appropriate for this task.

What did you find when you searched the forums for "Write failed for record id"?

As noted, you can't do this kind of thing 'after stage'. Also, I respectfully disagree with the Sort stage versus the UNIX sort that Ken mentions, I've found the latter to be up to 10x more performant for 'large' volumes. However, the Sort stage is certainly easier to manage.