No unique catalog for USS objects. System level OMVS all have the same HLQ pointing to a general purpose user catalog. Individual USS files typically have the user's HLQ or some other HLQ associated with the application; these all go into the user catalog associated with the alias.
I've never investigated this, but I suspect that HFS/ZFS in general are much more stable than traditional MVS files. No GDGs, no temporary allocate/delete processes in batch. Allocate once, use forever at the MVS file level because the dynamic activity is all in the USS directory structure. I see no reason for a unique catalog. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of David G. Schlecht Sent: Thursday, August 20, 2015 8:21 AM To: [email protected] Subject: Catalog for OMVS datasets Hello all, How do you catalog your OMVS datasets? My predecessor created a catalog in which he put a few OMVS dataset definitions. However, it never really got used. We only have a few dozen OMVS file systems so it doesn’t seem to make sense to have a catalog just for them. What is common practice? What do you do? Do you have a separate catalog for your OMVS datasets? If so, what’s your reasoning? David G. Schlecht | Information Technology Professional State of Nevada | Department of Administration | Enterprise IT Services T:(775)684-4328 | F: (775) 684‐4324 | E:[email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
