Protect the master catalog Sent from my iPhone
> On Dec 13, 2016, at 1:57 PM, Paul Gilmartin > <[email protected]> wrote: > >> On Tue, 13 Dec 2016 18:55:21 +0000, Way, Richard wrote: >> >> 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... >> > Protect the MASTERCAT. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
