Amen - one shopped I worked in had the master catalog defined with a UACC of UPDATE and it took a LONG time to get it cleaned up. If a new user got created with no alias - all their files went into the MASTER. Took a lot of REPRO MERGECAT commands to clean up that mess.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Tuesday, December 13, 2016 1:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Prevent allocation of unknown-HLQ data sets? What I've done in 2 shops was to protect the master catalog(s) set UACC(READ) and only update access to your SYSPROG's you trust :) Carmen ----- Original Message ----- From: "Richard Way" <richard....@hpe.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, December 13, 2016 12:55:21 PM 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... Thanks in advance Rich Way HPE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
