Re: Curious Program Message Queue/Subfile Behavior -- RPG400-L

Buzz,

Every call stack level has it's own message queue. Just make sure that the messages are sent to the same queue that's specified for the SFLPGMQ and you will be all set.

Whether a subprocedure is in the same/diff activation group is irrelevant. And whether it's in the same/diff program/module/srvpgm object is irrelevant.

Whether you call something in the same procedure vs. a separate procedure, however, is highly relevant because each (main or sub) procedure call starts a new call stack entry, so it has it's own message queue. IF you're using a special value like '*' that means 'the current queue' code in one procedure will be referring to a different queue than one in a different procedure.

-SK

On 12/4/2015 12:20 PM, Buzz Fenner wrote:

In the right situation, I'm a fan of having error messages implemented through program message queues, especially when the data being edited is in a subfile, too. Makes the program code a bit simplier to write/maintain. What I really wanted though was something that would function as a service program to handle writing those messages to a program message queue. I found an old System iNetwork article written by Adam T Stallman & the late great Gary Guthrie which did just that. Their approach was to get the calling program name from a dummy send/receive message operation, and use that value for the call stack entry parameter, while setting the counter parameter to 0 (in the QMHxxxPM API's). That way, you need not concern yourself with call stack entry positions, which sounded great to me.

I've not been able to get the service program to work. I have a CLLE program with ActGrp(*new) that calls an RPGLE program with ActGrp(*caller). In that program after selecting a customer record, control goes to a local subprocedure to perform maintenance. That subprocedure handles all input/output to the display (a windowed subfile with an error message subfile). That subprocedure makes all calls to the exported procedures in the service program (ActGrp(*caller).

As a test, I copied their code into my program to use as a pair of local subprocedures, and it works.

Assuming that I've gotten the code implemented in my program where it behaves the same as the service program's code, is there something I'm missing in the big picture here? Are there activation group or boundary issues I'm failing to consider?

--
Buzz Fenner, Analyst/Systems Administrator
+1 (870) 930.3374 bfenner@xxxxxxxxxxxxxxxx<mailto:bfenner@xxxxxxxxxxxxxxxx>

City Water and Light of Jonesboro
Office: +1 (870) 935.5581 / Fax: +1 (870) 930.3301
Physical: 400 East Monroe Ave., Jonesboro, AR 72401
Mailing: PO Box 1289, Jonesboro, AR 72403-1289

This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. City Water and Light of Jonesboro is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.

________________________________

This electronic mail transmission may contain confidential or privileged information. If you believe that you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.