John Reid, I hope the comments here have been as helpful to you as they seem to be to me. I am planning a two step approach to my version of the problem. First, I am going to remove the CAPTURING clause and add HUSH ON/OFF for the initial selects of my problem scenario. If that doesn't solve the problem, I will add a SLEEP at the beginning of the program in hopes that it will slow things down and lessen and issues with the race condition brought up by Ray Wurlod and Leroy Dreyfuss. I already have UDT.OPTION 112 ON (Thanks Ben).
I'm curious though. If this condition occurs where the file cannot be opened, is that a fatal error or does the process continue on with no output? DanE > If the capture file is not needed, we recommend using HUSH ON and HUSH OFF > around the EXECUTE statement, which prevents the capture file from being > created, reducing I/O. This is helpful when many such CAPTURING > clauses are > used in succession, but their output is not really needed by the > application. > Maybe udt is occasionally failing to resolve > a race condition between 2 phantoms that > are trying to create the same _PH_ file. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
