Hi all,
Using the batch model, in a few places we have "One Thread Only" synchronization either on specific steps or sections within our sequences. (Pretty common.) We occasionally see a run-time error inside the "One Thread Only" section, and then all the other threads that are waiting on that section throw error -17500.
Has anyone come up with an elegant solution such that when an error occurs in a "One Thread Only" section, the error is gracefully handled thereby preventing the waiting threads from throwing -17500? The only solution I can think of is to predict and prevent the original run-time error from occurring, which can sometimes be daunting in obscure, unforeseen scenarios.
I did attempt a cursory search that yielded many results - if this topic has already been specifically addressed feel free to point me to another post.
Thanks as always,
Mr. Jim
