Gord,
We created a DASD only SYSPLEX about 3(?) years ago on a z/14 primarily to
facilitate PDSE sharing between the PROD and DEVL lpars. I would have rather
had a coupling facility for a full sysplex, but we did not have one.There
was a ton of work to setup the CTC pairs between the three lpars, the final one
being our maintenance lpar. GRS will have to be reviewed carefully.We
have had zero issues since implementation. Feel free to write me directly for
specific questions. d...@clemson.edu<mailto:d...@clemson.edu>
Don
> -Original Message-
> From: IBM Mainframe Discussion List
> mailto:IBM-MAIN@LISTSERV.UA.EDU>> On
> Behalf Of Gord Neill
> Sent: Thursday, November 24, 2022 12:55 PM
> To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
> Subject: To share or not to share DASD
>
> [EXTERNAL EMAIL]
>
> G'day all,
> I've been having discussions with a small shop (single mainframe, 3 separate
> LPARs, no Sysplex) regarding best practices for DASD sharing. Their view is
> to
> share all DASD volumes across their 3 LPARs (Prod/Dev/Test) so their
> developers/sysprogs can get access to current datasets, but in order to do
> that, they'll need to use GRS Ring or MIM with the associated overhead. I
> don't know of any other serialization products, and since this is not a
> Sysplex
> environment, they can't use GRS Star. I suggested the idea of no GRS,
> keeping most DASD volumes isolated to each LPAR, with a "shared string"
> available to all LPARs for copying datasets, but it was not well received.
>
> Just curious as to how other shops are handling this. TIA!
>
>
> Gord Neill | Senior I/T Consultant | GlassHouse Systems
>
>
>
>
Don Parrott
zSeries Server Technical Support Team
Clemson Computing and Information Technology
Clemson University
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
