When there are multiple Metro Mirror targets, the ENABLE(PPRCMT) is needed to ensure all the MM functions are enabled.
The preserve mirror required function will only keep one of the two MM pairs in duplex, the other pair will go duplex pending for the target of the FlashCopy. The GM pair, being async, is already pending except for the brief points where it makes each consistency point. The FlashCopy target data is mirrored over between consistency points. Regards, David Shackelford DFSMS Development, IBM On Mon, 30 Sep 2024 13:31:45 -0500, Michael Babcock <bigironp...@gmail.com> wrote: >We have a Multi-Target MetroGlobal Mirror (MTMGM). It seems to be >working fine. Do we need to have ENABLE(PPRCMT) coded as well? I see >the default is DISABLE(PPRCMT). > > >On 9/30/2024 11:00 AM, ERNESTO FIGUEROA wrote: >> Hello, >> >> Flashcopy onto Global Mirror was enabled with OA57173. You can find the >> details here: https://www.ibm.com/support/pages/apar/OA57173 >> >> With the PTFs installed, an update to the DEVSUPxx parmlib to add >> ‘ENABLE(FLASHCOPYTOGM)’, will honor the volumes as Flashcopy capable. >> >> I hope this helps, >> >> >> Ernesto E. Figueroa >> DFSMSdss Product Owner >> >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of >> Michael Babcock <000005ad4e2d7232-dmarc-requ...@listserv.ua.edu> >> Date: Monday, September 16, 2024 at 12:30 PM >> To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU> >> Subject: Re: [EXTERNAL] Re: MTMGM and Flashcopy >> Yes, I saw the FCTOPPRCPRIMARY. We do need to worry about the primary >> going into duplex pending so need to add PMR. I was hoping to find >> someone that said restrictions had been lifted and didn’t need to worry >> about it. >> We will do some testing with FCTOPPRCPRIMARY(PMR). >> >> Thanks! >> >> On Mon, Sep 16, 2024 at 9:54 AM Pommier, Rex <rpomm...@sfgmembers.com> >> wrote: >> >>> Not sure if this would help. >>> >>> https://www.ibm.com/docs/en/zos/2.1.0?topic=flashcopy-pprc-primary >>> >>> Rex >>> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf >>> Of Michael Babcock >>> Sent: Monday, September 16, 2024 7:39 AM >>> To: IBM-MAIN@LISTSERV.UA.EDU >>> Subject: [EXTERNAL] Re: MTMGM and Flashcopy >>> >>> No one knows the answer to this? >>> >>> On 9/13/2024 9:43 AM, Michael Babcock wrote: >>>> We currently have a MTMGM (Multi-target, Metro Global Mirror) >>>> implementation. Most of our volumes are in this MTMGM >>>> configuration, however we have a few that are not. We have a volume, >>>> say at address A000, that is not part of the MTMGM nor part of any >>>> other copyset. We have a batch job that copies to this A000 address >>>> using FASTREPLICATION(PREFERRED), so it uses flashcopy and the job >>>> completes very quickly. Back in 2019, we decided to add this A000 >>>> volume to a metro mirror copyset. When the batch job ran, it >>>> couldn't use flashcopy and fell back to standard data movement. This >>>> extended our batch window and is not acceptable. I don't remember >>>> exactly what the error was but vaguely recall it was something about >>>> not being able to use FC to a target when that target was also a PPRC >>>> source. >>>> >>>> Has anything changed with regard to using FC to a volume that is part >>>> of the MTMGM or any other copyset? >>>> >>>> MTMGM: Our config is we have one DS8950 as our primary DASD box, we >>>> have another DS8950 being used as a Metro Mirror box colocated with >>>> the primary and we have a third DS8886 (soon to be a new DS8950) box >>>> at a remote site using Global Mirror. We use MTMGM to replicate from >>>> the primary to the MM box and using GM to the remote box. >>>> >>>> We really want to add the other volumes to the MTMGM but don't want to >>>> affect the batch Flashcopies to those other volumes. Clear as mud? >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, send email >>> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >>> ---------------------------------------------------------------------- >>> The information contained in this message is confidential, protected from >>> disclosure and may be legally privileged. If the reader of this message is >>> not the intended recipient or an employee or agent responsible for >>> delivering this message to the intended recipient, you are hereby notified >>> that any disclosure, distribution, copying, or any action taken or action >>> omitted in reliance on it, is strictly prohibited and may be unlawful. If >>> you have received this communication in error, please notify us immediately >>> by replying to this message and destroy the material in its entirety, >>> whether in electronic or hard copy format. Thank you. >>> >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
