In a recent note, Farley, Peter x23353 said: > Date: Fri, 15 Jul 2005 11:32:57 -0400 > > Agreed. The problem is that the support for MVS DSN's is not universal in > all the tools. This is flat wrong, IMHO, if they ever hope to get > programmers who have to deal with MVS DSN's all day every day to use these > services. > > Moving MVS DSN's to (x)FS via "cp" command or whatever is NOT the answer. > Processing them directly is. > Closer to the right answer would be a facility to automount (a subset of) MVS data sets at a UNIX mountpoint. This is comparable to mounting a FAT filesystem on Linux. Isn't that done routinely?
Granted, the gulf between Legacy data sets and POSIX is wider. o How would the permission bits be handled or simulated? o How would newline conversion be handled? o How would RECFM=F be handled? o How would serialization such as SYSDSN ENQs be handled? z/OS NFS server has confronted these same problems, and not entirely overcome them. > -----Original Message----- > From: R.S. [mailto:[log in to unmask]] > Sent: Friday, July 15, 2005 10:58 AM > <Snipped> > IMHO it is documented. Unix manual clearly describes what commands do > support MVS datasets. In fact - as a user - I don't care whether the > utility uses open() or fopen(). What is important is MVS dsn support, > doesn't matter how it is achieved. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
