On Friday, July 23, 2010, 4:42:51 PM, Alan wrote: > On Friday, 07/23/2010 at 03:41 EDT, Al Dunsmuir <al.dunsm...@sympatico.ca> > wrote:
>> One question I would like to see discussed over there is whether >> anyone needs BFS (very easy, should be able to use the z/OS USS >> code) or SFS file support. > In CMS, if you support BFS, then you also support the minidisk/SFS > filesystem. A POSIX file id of the form //fn.ft.fm can be used to "exit > out" of BFS and onto an accessed disk/directory. > Alan Altmark > z/VM Development > IBM Endicott The good news is that is the same escape that identifies non-POSIX MVS files on z/OS. I see this being able to be a lot of common code. It sounds like native-CMS and BFS should be straight forward. I still have no idea about SFS files (will have to spend some time reading the online docs). Support for those will likely come later (and will certainly need assistance for testing, as we don't use them). As always, help and advice on this and other issues/concerns that users have would be very much appreciated. It is best to do so over in the InfoZIP forum, as I'm likely to not be following this mailing very religeously. You likely want to monitor (and hopefully participate in) some of the discussions that we're having re how to map files names between the long UNIX-style names and the restrictive native MVS and CMS file names. Actually, CMS native looks a lot like PC DOS with a slightly longer file type, so that may not be as weird as MVS [GRIN]. Thanks again! Al
