The other members became " unreadable" as soon as the DCB values were changed in the DSCB. This probably happened when the SYSPRINT was closed. Any subsequent editing of that member did not change the situation, not for better and not for worse.
The PDS directory was not corrupted by either action. Any of the members in the PDS can be read as long as the DCB used to access the member contains the correct values. Under normal conditions those values come from the following sources, if they exist (in order of highest priority to lowest): the OPEN exit, the DCB statement in the program, the DD statement, and the DSCB. If you are using a standard utility such as IEBGENER or IEBCOPY, the first two are not an option for you. But you do have complete control over the DD statement. Regardless of the current DSCB values, if you specify in the DD statement the values used when a member was written to the PDS, you will be able to read that member back. Specifying the original values will allow you to copy all the original members to another PDS. Specifying the SYSPRINT values will let you copy the print output to a third PDS. Then you can discard the original PDS, rename the two new ones, and proceed on as if this never happened. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of ????? ????????? > Sent: Sunday, June 19, 2016 8:42 AM > To: [email protected] > Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption > > Yes - definitely - but I think I went wrong when I edited the output . > > . > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jesse 1 Robinson > Sent: Sunday, June 19, 2016 6:35 PM > To: [email protected] > Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption > > Please answer one burning question. When SYSPRINT went to the PDS, was a member > name specified? > > . > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-302-7535 Office > [email protected] > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of ????? ????????? > Sent: Sunday, June 19, 2016 2:31 AM > To: [email protected] > Subject: (External):Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption > > Thanks so much Lizette and Lionel. In my case, it was SYSPRINT of IDCAMS that > 'reconfigured' the PDS file, followed by edit of the sysprint output members. Believe me , > the 'sandbox' is now backed up daily. > > . > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Lizette Koehler > Sent: Friday, June 17, 2016 7:05 PM > To: [email protected] > Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption > > Cool. > > I will see if I can append to the RFE. > > Lizette > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Dyck, Lionel B. (TRA) > > Sent: Friday, June 17, 2016 9:02 AM > > To: [email protected] > > Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption > > > > I like the idea of the RFE but could I suggest broadening it to all > > BSAM/QSAM since any program that writes output could do the same > > thing. Put the test in the access method to prevent writing a > > sequential dataset on top of a partitioned dataset. > > > > ---------------------------------------------------------------------- > > ---- > > Lionel B. Dyck (TRA Contractor) > > Mainframe Systems Programmer > > Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI&T > > Service Delivery & Engineering > > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Lizette Koehler > > Sent: Friday, June 17, 2016 10:59 AM > > To: [email protected] > > Subject: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption > > > > After the discussion this week on recovering a PDS after IEBGENER was > > used without a member on SYSUT2, I went ahead and opened the following > > RFE (I did not find any currently in RFE on this) > > > > If you like it, please vote for it > > > > It is asking IBM to put a test into IEBGENER to see if SYSUT2 is a PDS > > or PDSE. > > And if it is, and no member is specified on the SYSUT2, to terminate > > the step with an RC12 and message about a PDS and no member name supplied. > > > > http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=9 > > 0179 > > > > > > Lizette Koehler > > statistics: A precise and logical method for stating a half-truth > > inaccurately > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
