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" <[email protected]> To: [email protected] 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 [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
