As far as I know, DB2 was the only CF exploiter that developed and released the (enormous) code required for software duplexing. They did this essentially because system managed duplexing was delayed by IBM for a lonnnnng time. System managed duplexing requires direct connection between (I)CFs so that structure updates can be 'mirrored' without intervention by exploiters. I do not consider DB2 (user managed) duplexing to answer affirmatively the question 'are my CFs duplexed?'
Note that there can be multiple ICF LPARs within a single CEC. System managed duplexing can be implemented without cabling because connections are virtual. You would still see a reference to the 'other CF' in a D CF command. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Feller, Paul Sent: Thursday, July 25, 2019 10:22 AM To: [email protected] Subject: (External):Re: Coupling Facility duplexed [EXTERNAL] We need to make sure if we are talking hardware duplexing or software (application) duplexing. We let DB2 duplex its group buffer pools. DB2 handles/controls keeping the structures in each CF in sync. In the policy we define DUPLEX(ENABLED) for the DB2 group buffer pools. We do not have any hardware connections between our two CFs. When I display our CFs I see "NO REMOTELY CONNECTED COUPLING FACILITY DATA AVAILABLE". So if we need to take down a CF we don't have to move the group buffer pools from one CF to the other. On the flip side because we don't connect the two CFs we do have to move some structures that don't support software duplexing from one CF to the other CF when we take one of them down. Thanks.. Paul Feller AGT Mainframe Technical Support -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: Thursday, July 25, 2019 12:02 PM To: [email protected] Subject: Re: Coupling Facility duplexed [EXTERNAL] Ah yes. Issue D CF,CFNAME=... You should see something like the following. Note the duplexing ICF. This is supported by appropriate definitions in the IODF as well as any required cable connections. REMOTELY CONNECTED COUPLING FACILITIES CFNAME COUPLING FACILITY -------- -------------------------- XYZ0001 003906.IBM.02.000000004DD8 PARTITION: 0D CPCID: 00 CHPIDS ON XYZ0001 CONNECTED TO REMOTE FACILITY RECEIVER: CHPID TYPE E4 ICP E5 ICP SENDER: CHPID TYPE E4 ICP E5 ICP XYZ0002 002965.IBM.02.000000005B48 PARTITION: 0D CPCID: 00 CHPIDS ON XYZ0001 CONNECTED TO REMOTE FACILITY RECEIVER: CHPID TYPE F7 CS5 8X-PCIE3 FF CS5 8X-PCIE3 SENDER: CHPID TYPE F7 CS5 8X-PCIE3 FF CS5 8X-PCIE3 . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Mark Jacobs Sent: Thursday, July 25, 2019 9:24 AM To: [email protected] Subject: (External):Re: Coupling Facility duplexed I believe that there's a hardware requirement too. The two coupling facilities need direct connectivity to each other. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://urldefense.proofpoint.com/v2/url?u=https-3A__api.protonmail.ch_pks_lookup-3Fop-3Dget-26search-3Dmarkjacobs-40protonmail.com&d=DwIGaQ&c=9g4MJkl2VjLjS6R4ei18BA&r=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc&m=M2jHo_lSw2LUhnKppxjWyk3YlP2g38Q9lGSW_i8jb5g&s=TV9ZLyG8PTvri4T3T8kNeDzhoLKj82DzDs3EuMqTUxg&e= ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, July 25, 2019 12:01 PM, Jesse 1 Robinson <[email protected]> wrote: > It's been many a year since we moved to duplexing, by which I mean > 'system managed duplexing'. Assuming that you are at an appropriate > hardware and CF code level, you don't define duplex capability. It's > just there. . There is no 'hardware definition' for duplexing. > Duplexing is defined in the CFRM policy for structures that are to be > duplexed. If the active policy specifies duplexing for any structure, > then that structure is duplexed to the CF named in the policy. Once > enabled in a policy, duplexing can be turned off or on via the OS > command SETXCF > > So to answer OP's question, How can I tell?, look at the policy > definition(s). Also D XCF,STR for any or all structures. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > [email protected] > > -----Original Message----- > From: IBM Mainframe Discussion List [email protected] On Behalf > Of Carmen Vitullo > Sent: Thursday, July 25, 2019 5:35 AM > To: [email protected] > Subject: (External):Re: Coupling Facility duplexed > > Are you talking CF structures ? > if so D XCF,STR should get you there > among all the structures you should see something like > > DSNDB21_GBP0 06/22/2019 19:55:25 ALLOCATED (NEW) CACHE > CFNAME: CF01 > DUPLEXING REBUILD > METHOD: USER-MANAGED > PHASE: DUPLEX ESTABLISHED > > Carmen Vitullo > > ----- Original Message ----- > > From: "Bill Giannelli" [email protected] > > To: [email protected] > Sent: Thursday, July 25, 2019 3:51:31 AM > Subject: Coupling Facility duplexed > > How do I determine if our Coupling Facility is duplexed? > thanks > Bill ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
