Re: Sending Escape Message from service program without killing itwith MCH3402

No, my caller is running in QILE activation group (yes, I know) and the service program is running in its own activation group.



"Birgitta Hauser" <Hauser@xxxxxxxxxxxxxxx> wrote in message news:<mailman.2160.1224089244.30674.rpg400-l@xxxxxxxxxxxx>...
Hi,

I assume your program is running in the default activation group and your
service program is created with activation group *CALLER.

If so, the only solution I know to use a named activation group for your
program (or service program).
Running real ILE (service) programs in the default activation will cause a
lot of problems.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Lim Hock-Chai
Gesendet: Wednesday, 15. October 2008 17:17
An: RPG programming on the AS400 / iSeries
Betreff: Sending Escape Message from service program without killing it with
MCH3402

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