In addition to protecting the master catalog, you should prohibit HLQs for which there is not a group or user profile. Then make it part of your procedures whenever a new user or group is created to simultaneously create the catalog alias.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Way, Richard Sent: Tuesday, December 13, 2016 10:55 AM To: [email protected] Subject: Prevent allocation of unknown-HLQ data sets? Realize this is a pretty basic question, but my Google-fu isn't working out today.... Can someone tell me the most common / easiest way to prevent allocating a data set that doesn't have a catalog alias defined yet? We're hitting situations where someone creates a data set by the HLQ of "TEST", for example, and because no one created an ALIAS for TEST to a USERCAT, the catalog entries for those data sets go straight into the MASTERCAT. I'm almost certain there's a way to do this, but I am struggling whether it's usually done by RACF or if there's a better / easier way... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
