Re: Sending Escape Message from service program without killing it withMCH3402

I think I got it to work by using an dummy program to send the escape
message. So... When the export procedure in the service program
encountered a fatal error, instead of sending the *escape message
directly, it calls a dummy program to send the *escape message. The
power of ILE message percolation takes over and allows the caller to
continue to monitor for error if needed. (Note: To get the message
percolation to work correctly, it does require all programs to run in
the same activation group. I wonder if there is a way to get around
that.... Ummm).

Thanks.





"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote in message
news:<mailman.2107.1224083984.30674.rpg400-l@xxxxxxxxxxxx>...
I've an export procedure in a service program that will send an *ESCAPE
message to the caller when encountered a particular type of fatal error.
The caller has a choice of monitor for the *escape message or, in most
case, just error out. I'm having a problem on caller that monitor for
the *escape message. When the *escape message is monitored by the
caller, subsequent call from the caller to the procedure in the service
program is being error out with MCH3402. Is there a way to get around
this?


thanks
----------