CBT PDS command (or ISV descendant StarTool) can handle this nicely. However, even IEBGENER can do it as well. Something like
//SYSUT2 DD DISP=OLD,DSN=marfed-up-PDS,LRECL=80,RECFM=FB,DSORG=PO,BLKSIZE=??? //SYSUT1 DD DUMMY LRECL=80,RECFM=FB You need to figure out the actual block size for SYSUT2, which is a physical attribute of the file, not a logical attribute. There are various ways to determine physical block size. If the DCB block size is lower than the physical block size, you get an I/O error trying to read it. If the DCB block size is larger but still a multiple of 80, I believe you can read it. The important point that you have not lost previous data as long as your LISTC SYSPRINT specified a member name. In other words, the data set must still be DSORG=PO. If it now says DSORG=PS, you're toast because the directory was overwritten and cannot be recreated. . . . 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 robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Wednesday, June 15, 2016 9:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Recover PDS (Was Read a PDS (all members) like PS dataset) Changing the title to start a new thread Go to the CBTTAPE.ORG and get the PDS utility. It has a recovery process. Or if you know the original attributes, use IEBGENER to write a new Member //S1 EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD * Dummy record /* //SYSUT2 DD DISP=OLD,DSN=broken.pds(@#$Dmy),LRECL=x,BLKSIZE=X,DSORG=PO,RECFM=FB You really do need both the LRECL and BLKSIZE for this to be successful. I have used this, but it is at your own risk. If you have a backup of the file, I would go back to it an re apply changes Even in a Sandbox, I use HSM to back up critical files. It is better to be safe than sorry later. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of ????? ????????? > Sent: Wednesday, June 15, 2016 8:39 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Read a PDS (all members) like PS dataset > > Always interesting, I am dealing this week with an error that I hoped > would be solved by the different solutions presented here, but after > trying some of the solutions presented herein have not recovered. > Background: In preparation for a system cutover, executed IDCAMS LISTC > with SYSPRINT to a PDS file containing very important cutover data. (thought > that > was an efficient method of documentation :) - the laugh is on me). > The original file was a typical jcl type (80 lrecl) after running the > LISTC and updating the results, the PDS members which existed prior to the > LISTC job > execution were unreadable - IO ERROR. Since the disk was a 'sandbox' type > disk, it wasn't backed up nor dumped. I have been trying various > recovery methods - many of them as advised on this discussion list to > not avail. Any ideas ? Would it be preferable for me to specify the > actions I already did to try to recover the file? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
