Very Carefully... My feeling is the best way to move such pieces of data is to violate all security and do it in a standalone mode without any other security packag es involved. This might mean having to have management or security people looking over your shoulder at every keystroke.
1) Find out the volume, cylinder locations for your source and target, th ey match in size, right? 2) Shut down your old production system so there is NO chance of the RACF database being updated during its move. 3) IPL your rescue system (single volume disaster recovery system or your 3-5 volume maintenance system, some system where you have PRIVILEGES with out security). 4) Attach the source volume and the target volume to your running rescue system. 5) Use the DEFINE MDISK command to define both source and target minidisk s. 6) Use DDR to copy all cylinders from source minidisk to target minidisk. 7) ACCESS both minidisks read-only (ACCESS 200 C/C, ACCESS 201 D/D). 8) Compare the contents as best as you can, same number of files, same number of blocks, same MD5 Cyclical Redundancy Check? 9) Shut down your rescue system. 10) IPL your new production system. 11) Print out as much of your RACF database as possible and compare to th e printouts from before the move. (That's not part of your weekly reports? Then make that step 0, print out all of your RACF database.) 12) Backup your old system to tape. 13) Several weeks later, securely erase the DASD from your old system. 14) Several months later, securely erase those backup tapes. /Tom Kern /U.S. Dept of Energy /301-903-2211 On Fri, 21 Mar 2008 15:37:03 -0400, Hamilton, Brian <[EMAIL PROTECTED] om> wrote: >What is the best way to copy over my vm 5.2 racf database to my new vm >5.3 system? > >Also what is the best way to migrate dirmaint and its directly from vm >5.2 to 5.3? > >Thanks
