Without logs, it is only my imagination where debugging takes place. Given that disclaimer....
When you said you did "delete and redefine the CFRM dataset", is it possible that you actually created a new CFRM dataset, and then tried to update COUPLExx with the new data set names and/or volser for your IPL? I am asking this, because one thing the Sysplex CDS does keep is the data set name and volume serial number of the various other couple CDS data sets used by the sysplex. So, if you thought you were using a new CDS by updating COUPLExx, you might not have. When I do DR tests, I delete and create empty a CFRM CDS on the same volume with the same name as my original, and then load that new CDS with my DR CFRM policy. It is when using this technique that IPL is always clean the first time - the CFRMPOL is processed, and DR IPL works. Just a thought. Brian On Fri, 9 Apr 2010 15:54:49 -0400, Mark Jacobs wrote: >Basically you hit the high points of the steps that occurred during the test with one exception. I did delete and redefine the CFRM dataset writing the correct policy into it. We ipled again and the d**m system was still looking for the coupling facility on the incorrect CPU. I then did the only other thing I could think of which was to delete and redefine the sysplex couple dataset and try again. > >Mark Jacobs ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
