Well, it is not good idea, but sometimes even such idea is better than
nothing.
What's important the risk covers THIS catalog only, not whole world.
And yes, this catalog and shared datasets should be shared without
"sysplex features" like changes is serialization. RESERVE should be used
here or CA-MIM should be used, but the last one is add-on tool.
BTW: BCS can be defined with SHR(3 4) or SHR(3 3). For this case it has
to be SHR(3 4). AFAIK it is alterable.
Again: small activity is your friend here. Small number of datasets
cataloged in the BCS is good here. Potential problems with the BCS will
not affect other BCSes.
I use it for years (with limited activity). Mostly PS files and some
VSAM. No problems observed.
Caution: PDSE *will* break despite of way how catalog is shared. No help
from CA-MIM, AFAIK. Observed many times educated many guys who used PDSE
for sharing.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 20.04.2020 o 14:45, Allan Staller pisze:
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 <[email protected]> On Behalf Of R.S.
Sent: Monday, April 20, 2020 3:45 AM
To: [email protected]
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,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
