LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (June 2000, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Mon, 5 Jun 2000 11:37:36 -0400
Reply-To:   "Hanan, Thomas J" <HananTJ@AETNA.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   "Hanan, Thomas J" <HananTJ@AETNA.COM>
Subject:   MVS - truncated SAS library after a backup

Hello SAS-Lers,

I've run across this problem in the past, but have never found a solution for it. Whenever our friendly DASD folks migrate our SAS datasets to tape, once in a while when copying them back to DASD the SAS dataset gets stored on multiple DASD volumes. This causes the following dreaded error message to appear:

ERROR: Library TEST appears to have been truncated. The internal library structure reflects a high formatted relative block number that is greater than the number of blocks actually in the MVS dataset. This may be the result of using non-SAS utilities to copy a library into a dataset with insufficient space or to copy a library with an imbedded EOF mark. This library will not be opened.

I've never found a way to fix a SAS dataset when this happens, and have to go back and hope that there was a recoverable backup somewhere. I've got one today for which I have no recoverable backup... The SAS website tells me to try the option NODLTRUNCHK to try and fix this, but it doesn't help my situation this time. I've tried PROC COPY to try and copy to a new dataset, but I get a U0315 abend when I do this.

Have any of you out there ever found a way to recover a file when this happens?

Thanks, Tom


Back to: Top of message | Previous page | Main SAS-L page