Discussion:
PDSE V2 Corruption - A Warning - Correction (kinda)
(too old to reply)
Dyck, Lionel B. , TRA
2018-02-14 17:45:58 UTC
Permalink
Raw Message
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-***@LISTSERV.UA.EDU] On Behalf Of Dyck, Lionel B. (TRA)
Sent: Wednesday, February 14, 2018 8:21 AM
To: IBM-***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Dyck, Lionel B. , TRA
2018-02-14 20:00:15 UTC
Permalink
Raw Message
IBM has taken an APAR on this:

From IBM:
===========================================
APAR OA54890 has been opened.

Additionally, DSC has a number of setup/processing parameters. Under my
setup an edit of a non-zero generation is like a STOW REPLACE of the
member, the edited generation replaces the base and the rest of the
generations roll accordingly.
===========================================

So it would seem that the DSC developers figured out that editing a non-0 generation made no sense as the updates could not be accessed from JCL, Dynamic Allocation, or 99% of ISPF application and utilities. I may be biased but I prefer the approach that PDSEGEN takes which is to convert the Edit request to View.

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

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Dyck, Lionel B. (TRA)
Sent: Wednesday, February 14, 2018 11:47 AM
To: IBM-***@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.

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



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Dyck, Lionel B. (TRA)
Sent: Wednesday, February 14, 2018 8:21 AM
To: IBM-***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lucas Rosalen
2018-05-10 20:29:40 UTC
Permalink
Raw Message
Hey fellas,

Apparently the APAR has been closed and PTFs are: z/OS 2.1 UA96169; z/OS
2.2 UA96170; z/OS 2.3 UA96168

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



-------------------------------------------------------------------------------------------------------------------------------
*Lucas Rosalen*
***@gmail.com / ***@ibm.com
http://br.linkedin.com/in/lrosalen
Post by Dyck, Lionel B. , TRA
===========================================
APAR OA54890 has been opened.
Additionally, DSC has a number of setup/processing parameters. Under my
setup an edit of a non-zero generation is like a STOW REPLACE of the
member, the edited generation replaces the base and the rest of the
generations roll accordingly.
===========================================
So it would seem that the DSC developers figured out that editing a non-0
generation made no sense as the updates could not be accessed from JCL,
Dynamic Allocation, or 99% of ISPF application and utilities. I may be
biased but I prefer the approach that PDSEGEN takes which is to convert the
Edit request to View.
--------------------------------------------------------------------------
Lionel B. Dyck <sdg><
Mainframe Systems Programmer - TRA
-----Original Message-----
Behalf Of Dyck, Lionel B. (TRA)
Sent: Wednesday, February 14, 2018 11:47 AM
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 <sdg><
Mainframe Systems Programmer - TRA
-----Original Message-----
Behalf Of Dyck, Lionel B. (TRA)
Sent: Wednesday, February 14, 2018 8:21 AM
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.
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tabari H Alexander
2018-05-11 00:26:04 UTC
Permalink
Raw Message
Post by Lucas Rosalen
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 default behavior for save in ISPF can be changed =>
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.f54pc00/isppcgeniset.htm


-----------------------
Tabari Alexander
IBM Advisory Software Engineer
PDSE Product Owner

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Loading...