What I understand if you use one star MAC.* that cover 2 nodes A.B If you have a longer dataset name I think you would use a double star MAC.**
We have a standard that the dataset profile should be coded A.*.** Lizette > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf Of > McCabe, Ron > Sent: Wednesday, March 14, 2018 4:33 PM > To: [email protected] > Subject: Problem with dataset authorization > > Hello List, > > I'm having a problem where one of my developers is getting "INSUFFICIENT > ACCESS AUTHORITY" on a dataset that I have defined in RACF and the issue is > that it is reporting on the generic definition. > > I have defined in RACF a generic dataset definition of MAC.* (this definition > has a UACC of READ and only a couple of groups have update access), I also > have defined a complete dataset name of MAC.JSF40.TEMP.JOBHIST (this > definition has a UACC of READ and allows update access for my developers). > When my developers run a job that wants to update the MAC.JSF40.TEMP.JOBHIST > dataset they get the "INSUFFICIENT ACCESS AUTHORITY" FROM MAC.* (G). > > Why isn't the system checking for the complete dataset which is the way I > thought RACF was supposed to work? > > Thanks, > Ron McCabe > Mutual of Enumclaw > > > Confidentiality Notice: This e- mail and all attachments may contain > CONFIDENTIAL information and are meant solely for the intended recipient. It > may contain controlled, privileged, or proprietary information that is > protected under applicable law and shall not be disclosed to any unauthorized > third party. If you are not the intended recipient, you are hereby notified > that any unauthorized review, action, disclosure, distribution, or > reproduction of any information contained in this e- mail and any attachments > is strictly PROHIBITED. If you received this e- mail in error, please reply > to the sender immediately stating that this transmission was misdirected, and > delete or destroy all electronic and paper copies of this e-mail and > attachments without disclosing the contents. This e- mail does not grant or > assign rights of ownership in the proprietary subject matter herein, nor > shall it be construed as a joint venture, partnership, teaming agreement, or > any other formal business relationship. > > ---------------------------------------------------------------------- > 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
