On Fri, Oct 31, 2008 at 5:50 PM, Alan Altmark <[EMAIL PROTECTED]> wrote:
> I don't understand, Rob. Every time a program writes, it must check EVERY > call it makes to ensure it worked. It can't just blindly continue. In > fact, if the connection between client and server is broken, all changes > to any open files are backed out, so the program must be restarted anyway. > (Workunits, you know!) And if a minidisk is DETACHed and LINKed, CMS > doesn't automatically ACCESS it for you. I don't know why you expect SFS > to be different in this respect. When my ACCESS has completed with RC=0, I may assume the mini disk to be accessed correctly and remain there until I release it. It is making life very complicated when I must write my application to expect the disk to be pulled underneath my fingers any moment. I understand that one could also take a real disk away, but SFS servers tend to have more fingers in the pie. When my program code is on a remote file pool, I can't even trust that the disk with my EXEC is still there to read the remainder of the program code (including the error handler for example). This is not something you can expect me to handle. (I know I can execload the stuff, but it is making things complicated). -Rob
