I've used a variation of this technique for many years as well. It works well for both DIRMAINT and VM:Secure/VM:Direct. This also makes sure that the user management product is internally consistent and at current release data formats at all times.
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of gclo...@br.ibm.com Sent: Wednesday, April 13, 2011 5:16 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Dirmaint : cards ordre Alain, Normally, this kind off migration is done on few hours. My technique (resumed): 1- Install a new VM and enable DIRMAINT, with the supplied directory. 2- Split the old direct to a TEMP disk, using one homemade EXEC (DIRSPLIT). The exec reads the old USER DIRECT, and create a new -userid- DIRECT, for each machine. Based on the "USER " card. Each "USER " finish the previous. Also test if each -userid- exist (CP QUERY USER -userid-). If exist then rename the file to -userid- EXIST. 3- DIRM ADD for all the -userid- DIRECT created. 4- Manually inspect the "EXIST" files and create a batch file for the divergences: ACCOUNT, ACIGROUP, new MDISK, etc. A "DIRM GET" followed by "COMPARE" can help. 5- Make the adjusts: DIRM BATCH batch file 6- If needed, move the old machines to new dasds: DIRM CMD (depending on the number of machines to move, eventually I create additional DATAMOVs...) 7- Fine adjust (less than 2%) for not covered situations. I worked this way for years... ______________________________________________
