If you can go to the CBTTAPE.ORG and find the PDS function, it has some recovery options. PDSGAS will restore based on TTR. Not pretty but might help. However, if you have deleted the orginal dataset, then all information for recovery is lost. Only hope would be an HSM backup/dump or DR volume dump.
Also, as others have mentioned, if you have HSM check with HLIST DSN(dsname) BOTH and see if you have any copies. Or see if there are full volume dumps taken. This type of error is probably due to using DISP=SHR on the compress. If this is a critical datasets, I would recommend setting up a weekly compress and ensure there is some type of change control function on UPDATES/DELETES/COMPRESS Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf > Of Ravi Gaur > Sent: Friday, March 22, 2013 2:31 AM > To: [email protected] > Subject: PDS Compress > > We had a very weird situation where one of the TSO user compressed the PDS > dataset > which had 6000+ members however eventually the JCL in all of these members got > similar atmost ..so look like during stow somehow same memory overlaid or > Directory > TTR got wrong... > > We had no backup of the dataset and then have had to create new and with best > knowledge or recovered members from 2011 ... > Now challenge been to figure out what really happened and any way to restore > it back > to the stage it was compress(been push it's not possible... but thought to > bring it on > table).. > \ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
