Funny, I don't read the message that way. Nothing in the explanation indicates to me that the target name is the one with the problem. Also, I had no trouble with the last ServerPac I installed and the target was the same, though the source prefix had changed, so I assumed that that was the issue. There was a profile for 'PAGE.*', but not 'PAGE.**', so once I created that, it worked. I am certainly no RACF expert, I can barely spell it, but this still doesn't make much sense to me. Why did it work last time?
>>> "Pommier, Rex R." <rex.pomm...@cnasurety.com> 8/18/2009 12:32 PM >>> Is there a RACF profile covering the "PAGE.CPAC.COMMON" name? From looking at the error description, it appears as though the "SRVPAC.PAGE.CPAC.COMMON" dataset is RACF indicated, but the new name doesn't have a profile to cover it. HTH Rex CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. ---------------------------------------------------------------------- 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
