Sending messages to the correct call stack entry ( Good places to use "The Cycle" in today's RPG)

<snip>
About the only think I leave as subroutines are those that are rather particular about percolating a message up the message stack or some such animal.

Rob Berendt
</snip>

Rob;

I've used two methods to send message to the proper call stack entry so that they "show up" on a display.

1. Send the message to the *EXT message queue. Then receive and resend the messages in the *EXT message queue from inside the proper procedure. This method uses 3 procedures receiveExtMessages, reSendExtMessages, and removeExtMessages.

2. Use *PGMBDY for the callStackEntry parm and the program name in the callStackEntryQualification parm of the Send Program Message API.

Neither solution is elegant IMO. The first is more processing for the system, the second is a little more cumbersome for the programmer, thus I tend to lean more toward #1.

With the ability of creating RPG programs without a cycle the PEP call stack entry name is _QRNP_PEP_ModuleName instead of _QRNP_PEP_ProgramName which adds even more confusion to the mix.

Does anyone have a better solution to sending messages to a display file from multiple procedures?

Duane Christen

NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.