Yes, PDSE do require SYSPLEX. Not GRS-plex, not CA-MIM (or MII), but
SYSPLEX.
Reason: PDSE use sysplex communication, not GRS facilities.
Regarding to the topic: in order to share datasets you need ...nothing.
No parallel sysplex
No base sysplex
Not even GRSplex
No SMSplex
Simply nothing except DASD available from several systems.
Of course, the more mentioned facilities you have the better sharing is.
And yes, in order to share PDSEs (properly) you still have sysplex.
However you can share ICF BCSes (catalogs), VSAM, PS, PDS, etc.
Note: there are various flavours of sharing. Shared DASD as a data
transport method, shared PDSes with jobs, REXX tools, etc. - it can be
shared easily, because it is not heavily used. Batch datasets - assuming
proper batch windows it is also can be shared easily.
For frequent sharing it is good to think about ICF ECS or RLS, etc.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 19.06.2023 o 17:03, Michael Babcock pisze:
Beware of PDSEs. I’m not 100% sure but I think the sandbox needs to be in
the plex to share them. Updating a PDSE outside of the plex can cause
corruption.
We have our sandbox in the plex just to avoid issues.
On Mon, Jun 19, 2023 at 9:25 AM Paul Gorlinsky <p...@atsmigrations.com> wrote:
We have a sandbox system that references TSO user and ISV catalogs and
datasets. The sandbox has a unique master catalog but shares virtually
everything else.
It does have access to the couple facility that the Sysplex is using ...
But it is not a member of the Sysplex.
Is it possible for a monoplex z/OS system to share DASD, user cats, etc.,
with a SYSPLEX via GRS management and coupling facility?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
