On Thu, 20 Aug 2015 08:21:07 -0700, David G. Schlecht <[email protected]> wrote:
>How do you catalog your OMVS datasets? > <snip> A data set is a data sets is a data set. I remember when just about all shops had different HLQs for VSAM (PROD, PRODV, TEST, TESTV etc..). I'm sure a lot of those legacy standards still exist but I bet newer standards in most shops don't distinguish by HLQ VSAM vs. non-vsam (maybe a letter somewhere in on of the mlq nodes). My setup is pretty much what Skip wrote. System / sysres z/OS unix files are in the master catalog (just like all the other sysres data sets) with a HLQ of SYS1 (SYS1.OMVS.&sysres.** to be specific). "In house" z/OS unix files use the same HLQs as other system "in house" data sets (proclibs, ISPF libs, etc.). These include /etc, /var and other sysplex unix file systems. Some of them are "directory" file systems and are just mount points for other file systems. The HLQs vary by sysplex / company. ISV or program product unix files have various HLQs, again depending on the sysplex / company and also on some sysplexes the standards have a different HLQ for different tech teams. For example, the CICS team uses CICS.** for their data sets and the unix files follow those same standards. Some sysplexes all ISV product system data sets have the same set of HLQs (with a P/D/T in the HLQ denoting production, development, or test). Any unix file associated with that product would have the same HLQ. None of the HLQs mentioned above are in the master catalog. A data set is a data set is a data set. :-) User zFSes (automounted) are a mixture between the two major companies I support. One of them uses their personal HLQ, for example userid.OMVS.ZFS, and the other one uses a system HLQ, for example SYSO.userid.ZFS or SYS.OMVS.userid.zFS. I can see why there is a recommendation for the latter because the average user really doesn't need access to their physical file system, but I also don't have a problem with the HLQ being the same as all their other files. The user can delete their zFS all they want and they aren't going to destroy anything in the system or any other persons data nor application data. On Thu, 20 Aug 2015 16:59:18 +0000, Jousma, David <[email protected]> wrote: >No real concerns either way in a single system shop. However, if you do >Sysplex >Shared filesystem "SYSPLEX(YES)" in BPXPRMxx then there is a requirement for >them >to be in a usercat connected to all systems that are sharing or you will have >problems. Change the word "usercat" to "catalog". None of our sysres unix files are in user catalogs. Some of the sysplexes have an HLQ like SYSO (O = OMVS) for things like /etc and that HLQ is in the master catalog. It doesn't have to be, but that's what was done a long time ago. Of course the master catalog is shared in each sysplex. Best Regards / Mit freundlichen Grüßen, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
