Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!JASPER.PALLADIAN.COM!dp
From: dp@JASPER.PALLADIAN.COM (Jeffrey Del Papa)
Newsgroups: mod.computers.vax
Subject: Corrupt VMS accounting file
Message-ID: <870111173505.4.DP@BANFF.PALLADIAN.COM>
Date: Sun, 11-Jan-87 17:35:00 EST
Article-I.D.: BANFF.870111173505.4.DP
Posted: Sun Jan 11 17:35:00 1987
Date-Received: Mon, 12-Jan-87 02:24:51 EST
References: <12269606425.65.OC.CIVIL@CU20B.COLUMBIA.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Jeffrey Del Papa <DP%JASPER@LIVE-OAK.LCS.MIT.EDU>
Organization: The ARPA Internet
Lines: 30
Approved: info-vax@sri-kl.arpa


    Date: Fri 9 Jan 87 15:01:04-EST
    From: Holt Farley <OC.CIVIL@CU20B.COLUMBIA.EDU>

	    I had a disk failure that corrupted the accountng.dat data file on
    one of our systems.  Approximately 1/3rd of the way into the file the 
    accounting utility reports a read error of the sort:

	    %ACC-E-READERR
		    -RMS-W-RTB, 1171 byte record too large for user's buffer

    and then gives up.  DEC Software Support claims they know of no way to read
    the data past the error.

	    Surely there is a way to get to the good data beyond the corrupt 
    records without resorting to using the ACR$ system calls.  Any suggestions?

    Thanks in advance...

    Holt Farley
    Columbia Univ. Civil Eng.
    -------


this is caused by a bad bit in the records length field at the start of the record.
the only thing to do is use a disk zapper to patch the byte..  (it is an issue of
relegion.. someone in the RMS group hates terminating bytes, and would rather have
a single byte error render much of a file unreadable.)

<dp>