> Also, there is an interesting (at least for me) RFE that proposes either
to
> change the Edit of an "old" member generation to View, or to allow the
Edit
> but save it like a new generation. Here =>
>
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=101120
FWIW, the defau
ent: Wednesday, February 14, 2018 11:47 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Re: PDSE V2 Corruption - A Warning - Correction (kinda)
>
> According to IBM PDSE L2 this is not true corruption but an issue with
> IEBPDSE for which an APAR will be created.
>
> -
UA.EDU
Subject: [EXTERNAL] Re: PDSE V2 Corruption - A Warning - Correction (kinda)
According to IBM PDSE L2 this is not true corruption but an issue with IEBPDSE
for which an APAR will be created.
--
Lionel B. Dyck <
Mainfram
ame Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Dyck, Lionel B. (TRA)
Sent: Wednesday, February 14, 2018 8:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] PDSE V2 Corruption - A Warning
If you are using PDSE V2 libraries with member generations enabled be aware
that native I
If you are using PDSE V2 libraries with member generations enabled be aware
that native ISPF, and potentially other tools, allow you to actually EDIT a
generation. When doing this and doing a SAVE the updated generation does not
replace the base member and no new generation is created.
BUT what
