Radoslaw,
What do you mean? Are you referring to running with PDSESHARING(NORMAL)?
Is it documented anywhere that a PDSE can be safely shared outside a
SYSPLEX when running PDSESHARING(EXTENDED)?
--
Tom Marchant
On Tue, 12 May 2020 17:02:23 +0200, R.S. wrote:
>Yes, I'm aware of that. However
olation of those types of workloads.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of R.S.
Sent: Tuesday, May 12, 2020 10:45 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IGDSMSxx setting PDSE_VERSION(2)
My humble opinion:
Everybody who want or really need PDSE v2 will c
loads.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of R.S.
Sent: Tuesday, May 12, 2020 10:45 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IGDSMSxx setting PDSE_VERSION(2)
My humble opinion:
Everybody who want or really need PDSE v2 will create such dataset explicitly
by speci
My humble opinion:
Everybody who want or really need PDSE v2 will create such dataset
explicitly by specifying DSNTYPE=(LIBRARY,2). That's OK.
You want to create PDSE v2 by default. This is the best way to find out
which system components or application still not tolerate new PDSE
flavour. Bu
On 5/11/2020 9:42 AM, Juergen Kehr wrote:
Hello,
on our new z/OS V2.4 we plan to set IGDSMSxx parameter PDSE_VERSION(2) to have
V2 PDSEs as default. Therefore I would like to know, if there are any known
issues out there, which are reason for don't do this setting.
Thanks in advance for any hi
-MAIN@LISTSERV.UA.EDU
Sent: Mon, May 11, 2020 9:42 am
Subject: IGDSMSxx setting PDSE_VERSION(2)
Hello,
on our new z/OS V2.4 we plan to set IGDSMSxx parameter PDSE_VERSION(2) to have
V2 PDSEs as default. Therefore I would like to know, if there are any known
issues out there, which are reason for
Hello,
on our new z/OS V2.4 we plan to set IGDSMSxx parameter PDSE_VERSION(2) to have
V2 PDSEs as default. Therefore I would like to know, if there are any known
issues out there, which are reason for don't do this setting.
Thanks in advance for any hints.
Kind regards
Juergen
