Scott, Is it possible that in the interim since you did the last process either PROTECTALL was activated for the first time or a prior profile (e.g. PAGE.**) existed that was deleted?
Regards - Bob Robert S. Hansel Lead RACF Specialist RSH Consulting, Inc. www.rshconsulting.com 617-969-8211 -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Scott Rowe Sent: Tuesday, August 18, 2009 2:12 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IDC3009I RC=110 I understand all that, yet the fact remains that this process worked before, when there was no PAGE.** profile defined. I guess this is not a big deal now, I was just trying to understand what had changed. >>> John Laubenheimer <jlaubenhei...@doitt.nyc.gov> 8/18/2009 2:46 PM >>> Also, check the SETROPTS for the PROTECTALL option. If you had a PAGE.* profile, which only covered the 2nd level, the PAGE.A.another_level is NOT protected, and RACF (actually DFSMS) would fail any access to the dataset. When you created PAGE.**, you then covered any number of levels after PAGE., and RACF/DFSMS would then allow access. And, as previously stated (I think), when you rename a RACF protected dataset, the dataset name that it is renamed to must also be protected. (Level of protection doesn't really matter ... just covered by a profile.) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
