Donna Garverick wrote in message ...
>we've been having trouble with message files getting
>'corrupted' recently.  'corrupted' could mean almost


I've not experienced any problems with message file data being corrupted.
There are some tricks to working with them, but no actual corruption.

For example:

- The message file is empty
- Process A opens the message file and writes 2 records to it.
- Process B asks for an FINFO('EOF',) on the message file and gets 0.

Resolution of this problem is to force Process A to close the message file
after each write.  This is additional overhead but I know of no other
alternative.


Jim Alton
eSystem Solutions
[log in to unmask]