Thanks for the overview. (I should write this out on the palm of my hand; too 
much hand washing these days, though.) As you or someone else pointed out, for 
z/OS Global, an 'XRC license' is required only at the source/prod site because, 
at the DR site, data is written to the mirror volumes via standard I/O. 

However, in a real life fail-over scenario, you may well want to *mirror back* 
to the original site. Or begin mirroring to some other site. At that point the 
DR site will need an XRC license. 

.
.
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 R.S.
Sent: Tuesday, July 14, 2020 3:17 AM
To: [email protected]
Subject: (External):Re: Two Processors and One IODF

CAUTION EXTERNAL EMAIL

I hate new names of PPRC and XRC (and PPRC-XD), but... But one should know 
there are new features. New features with new names, but no old name exist for 
them.

There are still PPRC, XRC, PPRC-XD, but there is also some kind of "XRC without 
z/OS", performed by dasd arrays without host involvement.

Names?

PPRC  - Metro Mirror
XRC   - z/OS Global Mirror or  Global Mirror for z/Series. Data is being
moved by z/OS task (Data Mover). Interesting: only source array need a licensed 
feature of XRC. Target array need not, and it can be other type/vendor.
PPRC-XD - Global Copy, neither synchronous nor asynchronous. It's inconsistent.
(none) - Global Mirror (consist of PPRC-XD and FlashCopy), asynchronous (but 
consistent) copy on unlimited distance.

To be honest, both HDS and Dell/EMC also complicated their names.
Not to mention HDS is not Hitachi, but Hitachi also delivers arrays for HP 
(HPE).
And there is also new player from Moshe Yanai, Infinidat, AFAIK.
And there are/were smaller players.

--
Radoslaw Skorupka
Lodz, Poland






W dniu 13.07.2020 o 18:39, Jackson, Rob pisze:
> Ah, the constant rebranding and re-lingo-ing.  It must really help sales.  
> The last time I had IBM storage, Global Mirror was PPRC/XD and "z/OS Global 
> Mirror" was GDPS/XRC.  And Metro Mirror was PPRC synchronous.  I can't see 
> how GDPS/XRC would work with non-unique addresses--at least between primary 
> and secondary, since they're both online to the SDMs (right?  getting fuzzy 
> on it).  Currently we use HUR (love it), but I don't believe it would work 
> with non-unique addresses either.
>
> First Horizon Bank
> Mainframe Technical Support
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On 
> Behalf Of Jesse 1 Robinson
> Sent: Monday, July 13, 2020 12:27 PM
> To: [email protected]
> Subject: Re: Two Processors and One IODF
>
> [External Email. Exercise caution when clicking links or opening 
> attachments.]
>
> We mirror with XRC, which I believe is Global Mirror. (I cannot keep the 
> current lingo straight.) In my shop, we have a business need to put any 
> device--DASD or tape--online to any LPAR regardless of location. In order to 
> do that, device addresses *must* be unique. If you have absolutely no need to 
> do that, then I don't think uniqueness is required. OTOH is costs little to 
> make them unique. If you don't do it from the get-go, it will be very 
> difficult in the future.
>
> .
> .
> 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]
>



======================================================================

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś 
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać 
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) 
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać 
karze.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 
Warszawa,www.mBank.pl, e-mail: [email protected]. Sąd Rejonowy dla m. st. 
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, 
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 
01.01.2020 r. wynosi 169.401.468 złotych.

If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have 
printed out or saved).
This message may contain legally protected information, which may be used 
exclusively by the addressee.Please be reminded that anyone who disseminates 
(copies, distributes) this message or takes any similar action, violates the 
law and may be penalised.

mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 
Warszawa,www.mBank.pl, e-mail: [email protected]. District Court for the Capital 
City of Warsaw, 12th Commercial Division of the National Court Register, KRS 
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 
169.401.468 as at 1 January 2020.

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

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

Reply via email to