On Wednesday, 10/29/2008 at 07:03 EDT, Rob van der Heij <[EMAIL PROTECTED]> wrote: > The problem I had with a more complicated ISFC collection is that when > the ISFC collection is dropped (going through a system that takes an > outage) the accessed directories get released by CMS once you try to > use them. This is very unpleasant and extremely hard to program around > to protect yourself. It would be very useful if CMS would try to > re-access rather than enforce the release.
We always suggest a fault-tolerant network (fully interconnected is preferred, of course). So it's still on an SFS reliability issue. I'd rather focus some attention on LAN (IP)-based ISFC configurations in order to eliminte intermediate nodes as a point of failure. I appreciate the auto-release issue, but I don't see us changing that behavior. It would be a Big Deal to redesign the SFS client. For myself, I'd probably write a nucleus extension that periodically tries to re-access my preferred filemodes if they aren't accessed. Alan Altmark z/VM Development IBM Endicott
