The OP did not mention CA-MIM. That will handle the issue. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Vernooij, Kees (ITOP NM) - KLM Sent: Monday, April 20, 2020 7:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Opinions/experience on sharing catalogs outside plex
[CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.] 2 notes: You need not regress to pre-GRS, you need to regress to pre-Hyperswap, which required the elimination of Reserves by converting them to global enqueus with GRS. CA-MIM provided (when we used it) GRS functionality across Sysplexes. Kees. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Allan Staller Sent: 20 April 2020 14:45 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Opinions/experience on sharing catalogs outside plex Yes, it can be done. I reiterate, IMO, this is most likely not a good idea. In order to accomplish this safely, you also need to regress GRS to pre-GRS functionality. Everything affecting this catalog must be handled w/Reserve/Release, and not normal processing VSAM Sharoptions for the catalog need to be changed. IIRC when I "undid" this the catalog hand Shareoptions (2,3) (or was it 4,3?). This option tells z/OS that the user is responsible for Catalog seriailization. SYSDSN, SYSIGGV2, SYSVTOC, SYSZVSAM (?) and the SPF* queues need to be excluded from GRS processing. In my case that led to various deadly embraces that usually led to manual intervention. My $0.02 USD on this is: Why point the shotgun at your foot? -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of R.S. Sent: Monday, April 20, 2020 3:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Opinions/experience on sharing catalogs outside plex [CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.] W dniu 09.04.2020 o 02:11, Rob Schramm pisze: > I am considering sharing some usercats outside of a sysplex. What I > can find is that sysiggv2 must be kept as a reserve to do so. > > Looking for others that have had to do this. > > One question I had was, what happens on a ispf 3.4 when the data set > is part of the catalog but exists in another system? Ief238d? My €0.02 1. You can share catalogs between sysplexes. Note: we mean BCS, which is usually called catalog. 2. The less activity on the BCS the better. 3. The above means: 3.1. Avoid keeping non-shared datasets in the BCS. Use another BCS for that. 3.2. It is not bad idea to have multiple "small" shared BCSes. 4. You cannot use any sophisticated catalog sharing features like RLS or ECS. Regarding you last question: I understand it as you have entry in the BCS, but the dataset reside on volume which is not share, that mean it is unavailable for one system. It's nothing exotic. It's like orphan catalog entry, which sometimes may happen even without BCS sharing (usually as result of human error). However that also means the sharing is not done correctly. The best scenario is when all datasets cataloged in shared BCS reside on volumes which are also shared. Preferably the BCS is also on the volume from that group. Keep it simple. -- Radoslaw Skorupka Lodz, Poland ====================================================================== 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,https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mbank.pl%2F&data=02%7C01%7Callan.staller%40HCL.COM%7Cffa4bd2b6c084d5c34e108d7e52a5288%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637229842282834595&sdata=fdI7BLtaR60WFeKQ8hscysetzWAiiMyYSqHcWMr2%2B4g%3D&reserved=0, e-mail: kont...@mbank.pl. 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,https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mbank.pl%2F&data=02%7C01%7Callan.staller%40HCL.COM%7Cffa4bd2b6c084d5c34e108d7e52a5288%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637229842282834595&sdata=fdI7BLtaR60WFeKQ8hscysetzWAiiMyYSqHcWMr2%2B4g%3D&reserved=0, e-mail: kont...@mbank.pl. 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- 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: https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.klm.com%2F&data=02%7C01%7Callan.staller%40HCL.COM%7Cffa4bd2b6c084d5c34e108d7e52a5288%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637229842282834595&sdata=qQrtTc88gxhSTeUZze6Ap0slVcKzWLu6v2ep4yUXUCU%3D&reserved=0. 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, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- 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