On Sun, 3 Jan 2010 10:39:46 -0700, Steve Comstock wrote: >> >>> path so that we could have longer member names, longer data set names >> >> The longer names are available in the Unix filesystems. A plausible >> migration path would be providing for migration of enterprise data >> into Unix filesystems. > >Cool! I'm working on an utility to do that! In a month or two I >could use some beta testers. > I fear we're using different semantics for "migration". I was thinking that Classic data management should have enhanced capabilities for using Unix files. This is the sense of the PATH= operand in JCL and the more recent BPAM (read only; no DESERV) support for z/OS Unix directories. The next big step might be to have a Unix directory tree replacing the VTOC and catalog, with Classic CKD data sets as the leaves. This would open the larger Unix namespace, but provide compatibility and performance of Classic access methods and EXCP once the data sets were opened.
I suspect you, OTOH, are working on a utility to copy Classic data sets to Unix files. Yah, I know either scheme leaves gaps to be filled concerning security, integrity, and serialization. -- gil ---------------------------------------------------------------------- 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
