In article <[log in to unmask]>,
[log in to unmask]
says...
>
>I have a  message driver program  that reads one message file and broadcasts
>to four other message files that are in turn  read by four child processes
>of the message driver program.  The driver process itself is being used on
>100+ machines, but only these five large 3000s  appear to be having
>problems.  The problems started after a system failure, they are using
>MPE/iX 5.0, and all are large boxes.   The message files have been rebuilt
>since the system failure, but frequently the child reader processes appear
>to be 'stuck' in read or the father process appear to be stuck in write or
>read mode.    A  support call was placed to HP a couple of weeks ago, but
>since the problem is frequent but cannot be duplicated at whim nothing has
>been resolved.   So... is anyone else having problems or any suggestions for
>work arounds (other than aborting the father process!)?
>
>Thanks,
>Kelly Floyd
>Distribution Resources Company
>[log in to unmask]
 
*****
 
I have a problem on a MPE iX 4 machine in which four message files are
used to communicate between a parent and son process.  Sometimes but not
always both processes appear to be waiting for the other.  When the parent
is aborted, the son process starts up, sometimes gets part way, and then
dies because the parent has been removed.
 
Perhaps my problem is related to yours.
 
Jeff Brown
[log in to unmask]