Re: Message from RPG

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On 29/04/2010, at 10:25 AM, Dennis Lovelady wrote:

> Hardly seems like a valid excuse to me!

Hey, if **I'm** prepared to accept then it must be OK :)

> If nothing else, couldn't the
> routine that wants the message sent, identify itself in the  
> message?!?!

Certainly could. Second-level text would be a good place, under the  
Technical Description section, but one of the really nice things about  
OS/400 is being able to press F9 to get message details and see the  
from and to information.

> (That's what I do if there's ever any doubt.)  Meaningful messages  
> are a key
> to good problem identification!  In the final analysis, this message  
> will
> not (appear to) be sent from the routine that wants it sent anyway!   
> Why get
> hung up on what module it's in?

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.

To be honest, I've used both direct calls and wrappers and I vacillate  
between both methods. Neither of them is a perfect solution.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------