DON'T SHARE PDSE ACROSS SYSPLEXES
Neither GRS reconfiguration, nor CA-MII would help here.
What can you do?
Live with frequently corrupted PDSEs or replace PDSE sharing with some
other solution.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2016-04-01 o 15:34, Dyck, Lionel B. (TRA) pisze:
The reason for the questioning is that there are PDSE's that are access from
both sysplexes, since the dasd/catalogs, are shared that have gone bad. Adding
more discipline on the access is one way and the other is to let the system
manage the access.
--------------------------------------------------------------------------
Lionel B. Dyck (Contractor)
Mainframe Systems Programmer
Enterprise Infrastructure Support (Station 200) (005OP6.3.10)
VA OI&T Service Delivery & Engineering
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Staller, Allan
Sent: Friday, April 01, 2016 8:18 AM
To: [email protected]
Subject: [EXTERNAL] Re: Advice needed - GRS across 2 sysplexes with shared dasd
Yes, you can configure GRS for all 4 LPARS.
*DON'T DO IT* You are just asking for trouble......
GRS has *ALWAYS* claimed to have a scope of SYSPLEX.
Which brings to mind, why are you (or anyone else) seeking to change this?
<snip>
Seeking advice on how to configure the system to allow GRS to manage all of our
environment.
Current config:
4 lpars
2 in prod sysplex
2 in test sysplex
All dasd is shared
Each currently has its own grs environment.
I asked ibm l2 and was told I couldn't have grs manage all 4 lpars but was also
told by a friend that it should be possible.
</snip>
This email ? including attachments ? may contain confidential information. If
you are not the intended recipient, do not copy, distribute or act on it.
Instead, notify the sender immediately and delete the message.
--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.
This e-mail may contain legally privileged information of the Bank and is
intended solely for business use of the addressee. This e-mail may only be
received by the addressee and may not be disclosed to any third parties. If you
are not the intended addressee of this e-mail or the employee authorized to
forward it to the addressee, be advised that any dissemination, copying,
distribution or any other similar activity is legally prohibited and may be
punishable. If you received this e-mail by mistake please advise the sender
immediately by using the reply facility in your e-mail software and delete
permanently this e-mail including any copies of it either printed or saved to
hard drive.
mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
www.mBank.pl, e-mail: [email protected]
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru
Sdowego, nr rejestru przedsibiorców KRS 0000025237, NIP: 526-021-50-88.
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci
wpacony) wynosi 168.955.696 zotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
