Re: Message Subfile w/Call Stack

The trick with ILE programs is that you have message queues at the
procedure level as well as the program level so messages have to sent to
the program, module, and procedure to get to the right queue.

If you have a monolith program with subroutines you have one message queue.
If you have a ILE program with say 10 procedures you have 11 message
queues. One for the program and one for each procedure.

Had to deal with this 20 years ago when I started writing screens with
procedures.

On Fri, Mar 27, 2020 at 1:56 PM Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

I can vouch for this, having JUST dealt with this problem. Had a
subsystem of OPM programs and converted one to ILE, at which point it
stopped getting its messages. I had to find the subprogram that was
sending messages and add support for it to find the caller and then send
a message to that program with the value *SAME. A little bit tricky,
mostly because I had to keep backward compatibility.

On 3/27/2020 12:42 PM, dlclark@xxxxxxxxxxxxxxxx wrote:

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 03/27/2020
01:22:58 PM:

I have a menu program in RPGLE that calls othert CLPs/RPGLE
programs. When there are status messages in the CLP (and
occasionally RPGLE), the messages aren't making it back to the
original menu program.

I've done this in the past with a menu program and the messages
showed up, but not this time around. I'm avoiding changing the
called programs.

Any ideas???

To get messages from the called programs to show up in your menu
program's message subfile, then those called programs have to be smart
enough to target the menu program's message queue. This may work by
default when the called program targets the message queue for the *PRV
entry in the call stack but it may not in the case that there is more

than

one call stack entry between the menu program and the call stack entry
that is issuing the message. This is particularly true with ILE/RPG but
can also apply to ILE/CL. Meaning, ILE (sub)procedures take up space in
the call stack with their own entry -- usually *in addition* to the call
stack entry for the called program. Then service procedures called by

the

ILE/CL or ILE/RPG programs mean even more entries in the call stack.


Sincerely,

Dave Clark

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com