I'm a bit confused by this. CFRMPOL is only relevant when you IPL with a CFRM couple data set (CDS) that has never been used before, so there was no previously-activated policy. It's normally not necessary to update the CFRMPOL statement when you update your CFRM policy, unless you're changing *which* policy you're using. Even then, it only matters if you come up with a new CFRM CDS. The CFRM CDS records which policy was last used, and that's the policy that will be used if you are forced to perform a sysplex-wide IPL. There must be more to this story.
<snip> A friendly reminder to update your COUPLExx CFRMPOL keywords _any and every time_ you update your sysplex CFRM policy. If you experience a total coupling facility failure (which seems impossible, but yeah) then you will be effectively performing a sysplex "cold" start on the next IPL. If you neglected to update CFRMPOL, then you will fall back to the wrong policy and that's just the beginning of your troubles... </snip> Bill Neiman Parallel Sysplex Development IBM ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
