Re: Message from RPG

[Rory Hewitt <rory.hewitt@xxxxxxxxx>]

Yes, I also have a copybook which is copied directly into the source which
includes a sendMsg *subroutine* precisely for this purpose. Again, not
ideal, but it works well in cases where I easily want to know what routine
sent the message..

On Wed, Apr 28, 2010 at 6:22 PM, Simon Coulter <shc@xxxxxxxxxxxxxxxxx>wrote:

> I think your point is that because the call QMHSNDPM is inside a
> procedure it will be that procedure name that will appear on the F9
> details so even though the module and program may be what is desired,
> in a multi-procedure program you'll lose the real sender information
> anyway. That's a valid point and the only solution to that is to call
> the message API directly from the function that needs to send the
> message.