Ah, power hits...  We went round and round with this sort of thing.  Power hits
can definitely cause this.  I can't tell you why, but it absolutely can and will
bite you.  HP denies it, but we have seen it so many times.

We still get occasional FSERR 105 Bad Variable Block Structure problems.  In
many cases, HP has found a marker of some kind in the file of a power fail flag
or something, but there has been no hint o f the power fail in the system logs.
They have even been able to duplicate it in the lab, but can't explain it.

All I can tell you is, yes, it will bite you.  We haven't found any way to avoid
it.
--
Rick Ingham
"One track minds usually have derailed trains of thought."
Donna Garverick wrote in message ...
|Stan Sieler wrote:

|large files?  large memory machines?  not me/longs :-)  for a nice(?) change,
|this problem is actually happening at our stores with xl machines (rather than
|the classics....).  i very much suspect that we've got code that was happily
|ignoring (blissfully unaware) some 'issue' with message files under 4.0.  now
|that we're running 5.5 *and* having power hits at the stores (it's summer
|time...), the application is croaking on some (currently) unknown something.
|when the systems are restarted, the server program that (i'm guessing) reading
|the message file appears to go into a loop.  the current workaround is to
|purge and rebuild the message file.  is the file physically or logically
|corrupt?  i don't know.  i'm trying to find out.....  <sigh>
|
|i guess the next question is: is there 'the one true way' of handling message
|files?  like a white paper?      - d
|
|--
|Donna Garverick     Sr. System Programmer
|925-210-6631        [log in to unmask]
|
|>>>MY opinions, not Longs Drug Stores'<<<
|