Date:         Mon, 5 Jun 2000 17:48:14 +0200
Reply-To:     "Hellriegel, Gerhard" <Gerhard.Hellriegel@TELEKOM.DE>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Hellriegel, Gerhard" <Gerhard.Hellriegel@TELEKOM.DE>
Subject:      Re: MVS - truncated SAS library after a backup
Content-Type: text/plain; charset="iso-8859-1"

Your space management guy has to add some special parameters to avoid this. The library is destroyed if it becomes a multi-volume library. I think your backup tool uses SMS (or another space management tool) to restore datasets. You have to use special SMS classes for SAS libraries to keep them on one volume!


----------------------------------------------
Gerhard Hellriegel
DeTeCSM / SLM
Im Leuschnerpark 4
64347 Griesheim
Tel.: +49 6151 818 9806
Fax: +49 6151 818 9611
Mobil: 0171 2263497
e-mail: gerhard.hellriegel@telekom.de
privat:  ghellrieg@t-online.de
----------------------------------------------


> -----Urspr> üngliche Nachricht-----
> Von:  Hanan, Thomas J [SMTP:HananTJ@AETNA.COM]
> Gesendet am:  Montag, 5. Juni 2000 17:38
> An:   SAS-L@LISTSERV.UGA.EDU
> Betreff:      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