Did you deactivate and activate the new CF LPARs?
The CFRM CDS has 8 slots to store policies by 'PGM=IXCMIAPU' and different
names from 'DEFINE POLICY NAME()'.
With SETXCF START,POL,TYPE=CFRM,POLNAME=xx you make one of the policies the
active policy. This policy is copied to the slot of the 'active policy', so you
could overwrite the policy with its original name again, without changing the
'active' policy. Although I recommend using new names for new policies, so you
can activate the new policy and as easily, you can activate the old policy
again in case of problems.
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Steely.Mark
> Sent: 16 August, 2018 22:19
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: CF - CFRM Question.
>
> We are z/OS V2.2. While I was updating the IODF It was decided to change
> the Couple Facility Partition Identifier (CFA) from 8 to 9. Nothing else
> about that partition was changed.
>
> Also another CF Partition was created as CFB with Partition Identifier
> 9. At this point nothing is attached to this partition.
>
> I was informed since the partition ID was changed that the CFRM needed
> to be updated.
>
> So I added the additional CF NAME and updated the PARTITION #.
> CF NAME(CFA)
>TYPE(00)
>MFG(IBM)
>PLANT(02)
>SEQUENCE(00094037)
>PARTITION(9)
>CPCID(00)
>DUMPSPACE(367002)
>
> CF NAME(CFB)
>TYPE(00)
>MFG(IBM)
>PLANT(02)
>SEQUENCE(00094037)
>PARTITION(8)
>CPCID(00)
>DUMPSPACE(367002)
>
> Also updated all STRUCTURE's with PREFLIST with CFA & CFB.
>
> STRUCTURE NAME(XX__X)
>SIZE(172128)
>INITSIZE(114752)
>FULLTHRESHOLD(90)
>ALLOWAUTOALT(NO)
>REBUILDPERCENT(1)
>DUPLEX(DISABLED)
>PREFLIST(CFA,CFB)
>
> Then executed the utility and received a Cond code 0.
>
> During the IPL the following message was received:
>
> IXC518I SYSTEM not using CF
>
> Reason: Not in the CFRM active policy
> Reason Flag: 1332.
>
> NOT IN THE CFRM ACTIVE POLICY. REASON FLAG: reason.
> The CFRM active policy does not have this coupling facility defined. The
> coupling facility is connected to the system but will not be used since
> not in CFRM active policy.
>
> After that re-occurring error messages .
>
> At this point I decide to change the partition number back to 8 in the
> HMC and re-activated the CF.
> I also put back in place the old CFRM. RE-IPL and was able to
> successfully bring the system back up.
>
> What would be the correct way to update this ? What I have been able to
> find is to create a new CFRM and then perform a SETXCF
> START,POLICY,TYPE=CFRM,POLNAME=CFRM.
> Do I update the current CFRM?
> Can I use the same POLNAME ?
> How do I switch to the updated CFRM ?
>
> Any help would be appreciated.
>
> We were also wondering how the system was able to use the partition #
> defined in the CFRM as partition 8 but the IODF has it defined as
> partition 9.
>
> Thank You
>
>
>
>
> *** Disclaimer ***
> This communication (including all attachments) is solely for the use of
> the person to whom it is addressed and is a confidential AAA
> communication. If you are not the intended recipient, any use,
> distribution, printing, or copying is prohibited. If you received this
> email in error, please immediately delete it and notify the sender.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands,
