Scott, It's been a long time since I did a full replacement. Did the page datasets come as part of the system replacement and you just loaded them from tape or were they built on-site? The error description talks about the source DSN being RACF indicated. That means there is a RACF indicator bit set someplace (the VTOC, possibly - I don't know).
If the page datasets were loaded from tape, possibly IBM built this one with the RACF indicator bit turned on and a discrete profile to cover it. RACF couldn't find a profile to cover the target DSN so it failed the rename. Pure conjecture on my part. I'm sure there are smarter people than me on this list who could explain it correctly. :-) Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Scott Rowe Sent: Tuesday, August 18, 2009 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IDC3009I RC=110 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 ---------------------------------------------------------------------- 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
