I only shared a minimum set of volumes. Vary offline commands in COMMNDxx. Very few, if any PDS/E on these volumes and all are read-only after creation.
This COBOL-5 requirement for a PDS/E load library will complicate my transfers from development to test and production as that is currently a shared library which is only written from one lpar. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Dyck, Lionel B. (TRA) > Sent: Friday, April 01, 2016 7:43 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [EXTERNAL] Re: Advice needed - GRS across 2 sysplexes with > shared dasd > > Martin must be correct as a file only being read should not become > corrupted. Just identifying who the culprit is/was impossible. > > Martin - enjoy your vacation > > > -------------------------------------------------------------------------- > 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:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Martin Packer > Sent: Friday, April 01, 2016 9:40 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [EXTERNAL] Re: Advice needed - GRS across 2 sysplexes with > shared dasd > > Arguably there is no such thing as a "read only data set". It must've got > written to (at least) once (or be empty). Maybe CURRENTLY it's not being > written to. But when it was the damage could've occurred. > > And if this is woolly thinking it's OK: I'm on vacation, kinda sorta. :-) > > Cheers, Martin > > Martin Packer, > zChampion, Principal Systems Investigator, Worldwide Cloud & Systems > Performance, IBM > > +44-7802-245-584 > > email: martin_pac...@uk.ibm.com > > Twitter / Facebook IDs: MartinPacker > Blog: > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__www.ibm.com_developerworks_mydeveloperworks_blogs_MartinPack > er&d=CwIFAg&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb- > Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=0zJxLpCylE8YKC- > dfUkdX8jcFoyY9eqFDj4n0kMOwZ4&s=amaidrq_FaFffu97J6yRrn8Irhp3B3_Px > wxQ-vRutZs&e= > > > > From: Elardus Engelbrecht <elardus.engelbre...@sita.co.za> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 01/04/2016 15:24 > Subject: Re: [EXTERNAL] Re: Advice needed - GRS across 2 sysplexes > with shared dasd > Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> > > > > Dyck, Lionel B. (TRA) wrote: > > >An unintentional repeat. > > It is all right. It seemed you got caught in this bad situation. > > > >The original PDSE issue was a PDSE was being read (no updates) on both > sysplexes and it became corrupted. I was asked about PDSE protection for a > new project and that prompted this thread. > > Corrupted after reads? What programs were used to read them? What is > your RACF reports telling about any successful accesses from both > SysPlexes? If you got only Read access reports, then it is time for a PMR. > > > > And yes the PDSE's along with all datasets are shared between both > sysplexes as all dasd is shared. Not ideal but it is what it is so I was > looking for > a solution. > > Ok, let us see to help you. Must they be shared? Can you not keep two > copies which are NOT shared? Say one PDSE in one SysPlex and keeping > another in another SysPlex while using something to maintain identical > copies? > > Another question - are ALL the LPARS on the same z/OS level? I'm asking > because you can do versioning of the members from z/OS v2.1? > > Perhaps you could ensure there are timeslots for each SysPlex to allow > reads/updates? Say Morning is allowable for Plex 1 and Plex 2 in midday? > Or something like that. > > I have for example a REXX program which is looking for the 'right' time and > then do actions based on time of day. You could write it to do things on > certain times in certain LPARS. > > Someone said CA-MIM could be used, but I'm not sure. > > I know above are straws, but anything including RACF should be examinated > to prevent PDSE damages in the future. > > Groete / Greetings > Elardus Engelbrecht > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 > 3AU > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
