On 8/17/2020 4:59 AM, Bill Neiman wrote:
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.

Take a look at software case TS004055963 and hardware PMH 59261,227,000 (and several other related PMHs automatically opened since).

We came up with new CFRM data sets using the CFRM policy specified in CFRMPOL. While up, we switched CFRM policies but did not update CFRMPOL in COUPLExx as we should have (and as my reminder admonishes others to do). We then experienced a CPC failure in the early AM on 8/15 that took down all LPARs and internal coupling facilities. When coming up after the "crash," all of our structures were at the old sizes. Turned out we were running the policy specified in CFRMPOL and not the policy we had switched to prior to the crash. That's when I started this "reminder" thread.

I took my own advice and corrected CFRMPOL to reflect our current policy. Good thing I did because we had a second second crash of the same type at 9PM that same day. Coming back up after that crash, all structure size are as expected.

--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/


--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to