Ummm... Step A1. Make a DDR backup of the database disk to an MDISK that you can LINK and ACCESS even when RACF/VM is down? So that you can DDR that backup MDISK over a potentially corrupted production MDISK if things don't go perfectly the first time.
I don't run RACF/VM, but I'm just saying... :-) Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. "Alan Altmark" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 01/18/2011 02:34 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: RACF question On Tuesday, 01/18/2011 at 02:56 EST, "Feller, Paul" <[email protected]> wrote: > I've got three z/VM LPARs that share a RACF database. It is not shared with > any other systems. > > The LPARs were running z/VM Version 5 Release 3.0, service level 1001 (64-bit). > I upgraded one of the z/VM LPARs to 5.4 this weekend. It's running z/VM > Version 5 Release 4.0, service level 0902 (64-bit). > > I'm now seeing this error when I attempt to do an LU command on the 5.4 > LPAR. > > rac lu xxxxxxx > IRR52115I Error during RACF manager processing. Return code is 36. Reason code > is 3. > ICH51004I PARAMETER LIST ERROR DETECTED BY RACF MANAGER > Ready(00012); T=0.01/0.01 14:03:09 > > I've tried several other RACF display commands (SR, RL) and they all seem to > work ok. It's also possible to do an ALU on the 5.4 LPAR and see the results > on one of the other LPARs. Logins and other security checks seem to be > unaffected. > > RACF was initially installed on the 5.3 system. I verified that we have > VM64383 installed on the 5.3 systems. It was installed prior to RACF being > activated on 5.3 > > I have not run RACFCONV for zVM 5.4 yet. > > We have opened an issue with IBM support, but I thought I would ask on the list > if anyone has seen this before. Any thoughts? >From the Program Directory: "The RACF database must have templates at the function level 540 for RACF to function properly. If you are migrating from a previous release of RACF to RACF FL540, you must run the RACFCONV EXEC to convert the existing database templates to the current release." So run RACFCONV. As a reminder, the rules for sharing the database are: 1. Each RACF database (primary & backup) must be on its own full-pack minidisk or dedicated volume 2. If on a full-pack minidisk, the RDEV must be defined with the SHARED option 3. If on a full-pack minidisk, the MDISK must be defined with link mode MWV If any one of the above rules is not followed, then you may have database corruption since the database will not have been protected by RESERVE/RELEASE. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 [email protected] IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
