Bruce Willmore wrote: > Sorry, but I have to disagree. And you would be correct. Where the WRITE is issued from will have no effect on the status codes as nothing happens with the physical files until the boundary is closed. > If you have transaction boundaries > enabled, then none of the exception clauses associated with writes > will function. What will happen is that TRANSEND will simply fail and > execute the logic associated with it's ELSE clause. > Yes. > If you don't use transaction boundaries, then you no longer have > atomic updates, so if there is some type of I/O failure, your code has > visibility to it, but then what do you do with that information from a > design perspective? If the I/O error is a write error and it occurs on > anything but the first write of a transaction, then something or > someone has some cleanup to do. > Which is the point of transaction boundaries of course. > Personally, I'd rather have transaction boundaries and be forced to do > some detective work if my transaction commits start failing (although > it would be nice if there was some way to be pointed in the right > direction). > Agreed, there should be a way to determine which f the writes causes the transaction to fail.
Additionally, once you are in a subroutine, you will have to program failure logic in both the subroutine and the caller. Jim --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
