Part of our standard startup process after a crash is to run
a job that resets message files eof's to zero..Seems to work

!RUN MPEX.PUB.VESOFT;PARM=1
REPEAT
ECHO Reseting EOF to zero for file !MPEXCURRENTFILE
FILE X=!MPEXCURRENTFILE;SAVE
CONTINUE
MPE PURGE *X
FORFILES @[log in to unmask]@ [log in to unmask]@.NETBASE(ISMSG AND INTCODE >= 0 AND ACCDATE>=TODAY-1)
EXIT

-----Original Message-----
From: Sletten Kenneth W KPWA [mailto:[log in to unmask]]
Sent: Monday, May 13, 2002 22:18
To: [log in to unmask]
Subject: Re: FSERROR 105


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). Following a system
crash, we encounter this error. Is this file hosed or can
we recover it?
===============================================

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...  fortunately for us we use
our production message files mostly as semaphores to "wake
up" background jobs, so didn't lose anything of redeeming
technical value;  just introduced a little additional
delay in getting some things done...

Ken Sletten

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *