Jim Alton wrote:
>
> Stan Sieler wrote in message ...
> >Re:
> >> Rather than close and reopen the message file, try using FCONTROL 6.  It
> >
> >I was afraid someone would suggest this.
> >
> >Let's look at the original comment:
> >
> >> >- 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.
> >
This goes on and on.  My message file experience goes back to CM
so I may
be all wet but:

1.  Assuming process B wants to wait until there is a message in
the file.
2.  Set up the message file as unblocked so that it will be
posted
    right away.
3.  Then can't the write and reads be handled in a normal way and
    the whole thing be relatively secure from a system failure?

That's the way I programmed it in CM and if I remember correctly
it
worked without more ado.

Nick D.