Now the pieces make sense. I have made changes to our live CFRM policy for so long I did not even know you could code the CFRM DSN in the IXCMIAPU utility. I had always let it default in the past.
I imagine I must run it twice for the Primary/Alternate CFRM DSN. Thanks you very much everyone for the assistance, hopefully good news come Monday. On Wed, 15 Mar 2006 15:47:57 -0800, Skip Robinson <[EMAIL PROTECTED]> wrote: >When you create/reformat the CFRM couple data set, there is no CFRM >policy. It must be (re)created from a driver system before the first DR >IPL. (You could kludge it with multiple IPLs of the DR system, but you >really don't want to go there.) > >On the driver system, (re)create the CFRM policy you want to use--with the >DR CFs defined and included in all structure PREFLISTs--and explicitly >point to the new CFRM data set including DSN and VOL. Note: if you don't >include DSN and VOL, the policy will land in the CFRM couple data set of >the driver system; no good for the DR system. The new CFRM couple data set >will now contain only one policy--the one you just (re)created. > >At the first IPL of the DR system, there will not be any active policy, so >you need to name it in the COUPLExx member of PARMLIB that you IPL with: > >COUPLE > SYSPLEX(xxx) > PCOUPLE(x1) > ACOUPLE(x2) > CLEANUP(nn) > INTERVAL(nn) > --> CFRMPOL(new-policy) /* CFRM POLICY TO ACTIVATE IF NONE FOUND */ > >The CFRMPOL parameter tells the system which policy to activate if there >is none already active at IPL. This is where you name the policy you >(re)created from the driver system above. > >All other couple data sets, if mirrored, will contain the data they had >when mirroring was broken. > >. ---------------------------------------------------------------------- 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
