Hello Mike, I have tried it. It works but not always. When you also have to do DR on VSE and you have CA products it will not work. Or at least from a licence point of view that is. VSE will see the changed CPU but when the LMP keys are activated they will still report the real CPU. I did a recovery with VSE 2.6.1. from a 9672 CPU. The recovery was on a 2086 (If I remember correctly). My VSE did function but when I tried to startup FAQS and DYNAM/T I got licence key errors. I could do my test but the VSE console output was a bit, eh well, large to say the least. If it was a real DR I think I'd requested some EKG's from CA very fast.
The exact location in the VMDBK depends on your VM-version (4.x, 5.1) and if you are running 31 or 64 bit. Take a look at the CP data areas of your version in http://www.vm.ibm.com/pubs/ctlblk.html. You'll want the VMDCPUID-entry in the VMDBK description. Display that offset address within the VMDBK. It should start with FF, followed by your current CPUID and then the machine ID and finaly some 0's. Once you know the location you can write the 'correct' machine ID into this location. (Hm, I should have some rexx for this somewhere) You need to do this from your VSE machine and after changing the value you can IPL your DOSRES. (Disclaimer: use at your own risk. ...<obvious legal stuff should go here>...) Regards, Berry. On Tue, 1 Nov 2005 10:46:16 -0500, Horlick, Michael <[EMAIL PROTECTED]> wrote: >You wouldn't happen to know where in the VM control block that is ? > >I have some VSE systems running under the 2nd level system and I would >like them to act exactly as during a disaster recovery (to make sure my >new license keys work). > >Thanks > >Mike >
