On Mar 18, 2013, at 08:22, Jonathan Scott wrote: > > All I/O from HLASM itself is current handled via a very general > cross-platform interface, using either built-in platform specific > routines or exit routines. As you can see in the Programmers > Guide, at present there is no function in these I/O interfaces to > scan the directory of a library, and the current routines do not > even require there to be a concept of a "directory" for macros > and copy books. ... > That modularity implies that it would be fairly easy on VM/CMS to implement macros and copy books as members of an SFS directory rather than the wretched CMS MACLIBs.
We had a development project founder on CMS and move to MVS because of problems maintaining referential integrity during concurrent read access to CMS MACLIBs while they were being serially updated by other processes. (The MACLIBs were never corrupted; they only appeared so to the viewers.) -- gil
