Subject: | |
From: | |
Reply To: | |
Date: | Tue, 14 May 2002 00:25:00 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Sletten Kenneth W KPWA wrote:
>
> About 10 hours ago Leonard asked:
> ==============================================
> Filename: ATOINPUT
> File status is 9i
> I/O ERROR on READ [30,9x] (COBERR 664)
> Program file: ATO150CO.PHCPROG.AMISYS
> BAD VARIABLE BLOCK STRUCTURE (FSERR 105)
>
> ATOINPUT is a message file (MSG).
> ===============================================
>
> We just had the same thing happen on two message files
> after our Helpdesk "inadvertently" did a hard shut down
> on the UPS that powers our 959-400 (grrrrrr...). Maybe
> somebody else has a way to do it, but I've always ended
> up resorting to the PURGE and re-BUILD routine to be sure
> the problem has gone away...
If you are processing the file, you will get "some" records up to the
time of the crash; but beyond that, yes, I agree with Ken that the only
way to make it go away is to purge/rebuild. You can get some further
reliability (at the cost of performance) by using FCONTROL to force
posting of the file EOF in the writer application(s).
Jeff
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|