|
Hi Rob, Thank you for your reply. No, the threads I was looking at were not discussing the Message Handling APIs, but rather the CEE APIs. I have looked at the Message Handling APIs and I decided to use the QMHRCVPM (Receive Program Message) API. My program looks like this now: monitor; proc1(); on-error; QMHRCVPM( msgInfo: %size(msgInfo): 'RCVM0300': '*': 0: '*EXCP': *blank: 0: '*SAME': errorCode ); // Compute Sender Information starting position with pointer arithmetic: // %addr(msgInfo) + 112 + Replacement Data Length + Message Length + Message Help Length // Retrieve Sending Program Name, Module Name, Procedure Name and Statement Numbers in Sender Information. // Log this information. endmon; Is it what you had in mind? Is there some important flaw with the way I am doing it right now? One problem I found is that if the original escape message was sent from another program, the escape message the QMHRCVPM API sees is a CEE9901 message instead of the original one. Is there a way to track down the original one? Thank you for your help. -- Antoine Contal Did any of those threads discuss any of the api's located at http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/mh1.htm Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.