Re: Message from RPG -- RPG400-L

Subject: Re: Message from RPG
From: Rory Hewitt <rory.hewitt@xxxxxxxxx>
Date: Wed, 28 Apr 2010 18:47:19 -0700
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.