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 <sdg><
Mainframe Systems Programmer - TRA



-----Original Message-----
From: IBM Mainframe 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 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 does also happen is that the PDSE becomes corrupt as reported by the 
IEBPDSE utility.

When a PDSE is corrupt you may see any, or all, or none, of the following:


1.      Corrupt members or generations

2.      Missing members or generations

3.      No change until something else happens

Note: If you are using PDSEGEN and try to Edit a generation the Edit is 
converted to View to prevent this from happening.

--------------------------------------------------------------------------
Lionel B. Dyck <sdg><
Mainframe Systems Programmer - TRA


----------------------------------------------------------------------
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

Reply via email to