Re: QMHSNDPM in serviceprogram

Scott,

Well, I actually meant *CTLBDY, but thanks to your remark I reread the
documentation. Somehow until now it escaped me that 'control boundary' is
defined in ILE Concepts. Duh! (I still think the description in the
QMHSNDPM documentation is not very clear).

The practical problem I (and presumably Jan Grove) faced was that if I
want program A to send an escape message to its caller and I want to use a
service program wrapper around QMHSNDPM, the service program adds a call
level and a program boundary. So if the routine in the service program
sends the message to *PGMBDY 1, it sends it to A. Because I typically use
this in command processing programs (with activation group *NEW), I
resorted to *CTLBDY.

Thanks for pointing it out.

Joep Beckeringh

From:

Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>

Date:

14-10-2014 15:07

Subject:

Re: QMHSNDPM in serviceprogram

*CTLBDY 1 would send to one before the last control boundary... that's
not the same as the "program that called your routine". (Control
boundaries occur when the activation group changes, and you can have
loads of programs all run in the same activation group.)

Maybe you meant to say *PGMBDY 1?