"Clark Morris"
>To: IBM-MAIN@listserv.ua.edu
>Sent: 7/24/2019 3:12:33 PM
>Subject: Re: Sharing PDSEs in shared DASD Environment
>
>>[Default] On 24 Jul 2019 08:24:17 -0700, in bit.listserv.ibm-main
>>01439e1549b6-dmarc-requ...@listserv.ua.edu (S B) wrote:
>>
&
Gibney, Dave
Sent: Wednesday, July 24, 2019 1:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Sharing PDSEs in shared DASD Environment
The danger in sharing a PDSE "read-only" is when it get's updated "somehow" by
"someone" by "mistake"
>
The danger in sharing a PDSE "read-only" is when it get's updated "somehow" by
"someone" by "mistake"
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of S B
> Sent: Wednesday, July 24, 2019 12:26 PM
>
Thanks for all whoresponded and thank you for your suggestions – few more
points for clarification
Each LPAR has its ownmaster catalog but user catalog are shared (we use
different Res Packs during thesystem maintenance). We also use SMS and RACF
(also shared) to separate development vs. p
ble to get away with only reading from one, but even that is
dicey. Simple answer I got from IBM support: Don't do it.
Doug
Doug Fuerst
d...@bkassociates.net
-- Original Message --
From: "Clark Morris"
To: IBM-MAIN@listserv.ua.edu
Sent: 7/24/2019 3:12:33 PM
Subject: Re
[Default] On 24 Jul 2019 08:24:17 -0700, in bit.listserv.ibm-main
01439e1549b6-dmarc-requ...@listserv.ua.edu (S B) wrote:
>Thisis a simplified description of our environment (for thesake of this
>discussion)
>
>
>Weare running z/OS V2.3 and using CA MIM
>
>Wehave two LPARs LPAR1 Develop
,
> >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On
> > > Behalf Of S B
> > > Sent: Wednesday, July 24, 2019 8:23 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: Sharing PDSEs in s
EDU On
> > Behalf Of S B
> > Sent: Wednesday, July 24, 2019 8:23 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Sharing PDSEs in shared DASD Environment
> > Thisis a simplified description of our environment (for thesake of this
> > discussion)
> > Weare r
from 2 or more LPARs and you will have corruption,
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of S B
> Sent: Wednesday, July 24, 2019 8:23 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Sharing PDSEs in shared DASD Environment
>
> This
From: S B <01439e1549b6-dmarc-requ...@listserv.ua.edu>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 07/24/2019 11:30 AM
> Subject: [EXTERNAL] Sharing PDSEs in shared DASD Environment Sent by:
> IBM Mainframe Discussion List
>
> Thisis a simplified description of our environment
019 11:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sharing PDSEs in shared DASD Environment [EXTERNAL]
The very short answer is you shouldn't share PDSEs outside of a sysplex.
Under certain circumstances, you can get away with it, but you're just asking
for problems.
However, I'd note th
6-dmarc-requ...@listserv.ua.edu>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 07/24/2019 11:30 AM
> Subject: [EXTERNAL] Sharing PDSEs in shared DASD Environment
> Sent by: IBM Mainframe Discussion List
>
> Thisis a simplified description of our environment (for thesake of
> this
nuals.
>
> This is an SMS issue, not a MIM issue.
>
> -Original Message-
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of S B
>
> Sent: Wednesday, July 24, 2019 10:23 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Sharing PDSEs in shared DASD Environ
July 24, 2019 10:23 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Sharing PDSEs in shared DASD Environment
Thisis a simplified description of our environment (for thesake of this
discussion)
Weare running z/OS V2.3 and using CA’ MIM
Wehave two LPARs – LPAR1 Development and LPAR2 Production – there
Thisis a simplified description of our environment (for thesake of this
discussion)
Weare running z/OS V2.3 and using CA’ MIM
Wehave two LPARs – LPAR1 Development and LPAR2 Production – there two LPARs
areshared DASD but separate JES2 Spools and not SYSPlex. We
have"PDSESHARING(NORMAL)" in
15 matches
Mail list logo
