Stan Sieler wrote:

> Some of the worst performance problems I've encountered this year are
> precisely because people are calling FCONTROL (6) on files!  This results
> in MPE doing a "post" operation, which can be ***EXTREMELY*** expensive on
> large files on large memory machines.   (Similarly, FLOCK/FUNLOCK can
> cause bad problems.)

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'<<<