× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. October 2009

Re: reThrow: escape messge changed by API QMHRSNEM?

Emil,


You should look into the sender's block in that format, because that is
what you are looking for.

Checking the call stack won't do, as its entry is no longer there.

With regards,
Carel Teijgeler


*********** REPLY SEPARATOR ***********

On 21-10-2009 at 14:46 Emil Sommarström wrote:

Found some code in the archives to resend escape messages and modifed it
to be contained in a procedure: reThrow


http://code.midrange.com/5f86798b00.html


The procedure should be called in the "on-error" part of a monitor
statement to be catched further up the call stack.


The problem is when catching the message with API QMHRCVPM using the
RCVM0300 format.
The senderReceiving information has changed.
Where the intresting information is "receivingProcedure" and
"receivingProgramStatementNumbers".
What I want to catch is the procedure that caused the escape message in
the first place, is this possible?



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.