Re: Message Subfile w/Call Stack

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 03/30/2020
09:10:44 AM:

Found the issue.
Out of habit, I was calling a procedure that handles calls to
QCMDEXC. The messages were getting lost because of the procedure
call. I copied my code from the procedure call into the program
itself and status messages appear!!! Didn't even think of that.

Yep, you simply reduced the length of the call stack by one by
eliminating the subprocedure call and that allowed the default *PRV target
to hit your menu program's message queue. That may have solved your
problem but you don't want to restrict yourself from using subprocedures,
if you don't have to, just because you want to get the default *PRV
message queue targeting to work.

A better solution is to always be able to dynamically determine
the name of the calling program's message queue and target your messages
to that. I put a service procedure on the midrange wiki that gives you
just that ability. Then I have three other service procedures to make it
easy to send program messages from RPG.

https://wiki.midrange.com/index.php/Find_Call_Stack_Entry

https://wiki.midrange.com/index.php/Diagnose
https://wiki.midrange.com/index.php/Escape
https://wiki.midrange.com/index.php/Inform

Sincerely,

Dave Clark