Re: QMHSNDPM in serviceprogram

Hi there Joep,

Yes, that has always been a dilemna for me as well. Unfortunately, there's no perfect solution. In some applications using *PGMBDY 1 works nicely -- because I want to send to whomever called my service program.

But, for the other circumstance where I have a "send error" utility called from a program, and I want to send to that program's caller, there's no easy solution. The best I've come up with is to accept a parameter with the number of call stack levels. So the "send error" procedure accepts this parameter, and uses call stack '*' and call stack count is the parameter. That way, my program can specify 2, 3, 4... whatever it needs to go to the level that program desires.

Of course, that's clumsy because I have to count the call stack levels, etc, but it's the best I've found.

*CTLBDY could work nicely if you always use ACTGRP(*NEW) (or in some other way put every program in a diff activation group) -- but there are many circumstances where this isn't practical, either.

-SK


On 10/15/2014 5:06 AM, j.beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx wrote:

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?