Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
C Programming
Include path question
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Walter Roberson, post: 2491597"] Rechecking, it appears I was referring to CMS. I very briefly investigated MVS last night; found a bunch of unrelated T-shirt importation places, and lots of repetitions of sites that didn't say anything much useful. I did find that MVS's component specifiers are a convention rather than an actual grouping. What I was not able to determine within a reasonable time, though, was exactly what an MVS catalog is. I could see that there was more than one, including a critical "master catalog", and I could see a few utilities such as LISTCAT that would list the catalog given a project code. It -appeared-, with the little hard data that I could find, that an MVS catalog was arguably a "directory" within the meaning given by an earlier poster. I did see a hint that catalogs did not really organize the storage, and instead merely provided more convenient ways to go between readable names and internal dataset serial numbers, but if that is the case then it could be argued that a catalog entry was akin to a traditional Unix directory entry, which merely associates a name and an inode number with all the real action happening at the inode level. None of this was really very clear in what I found. [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
C Programming
Include path question
Top