|
I think changing the call stack count from 1 to 0 is wrong for this
particular issue. That would mean you're sending the message to RPG
procedure's call stack entry, which means you also need to catch it
yourself (MONITOR, I should say.)
It made perfect sense for that other thread (the one about ILE exception
handlers.) But I don't understand how it makes sense here, where the
goal is to send the error back to the IWS program that's calling your
RPG routine.
On 11/8/2013 2:07 PM, Mark S Waterbury wrote:
Hi, Scott (and all):
For the archives, it was a combination of the name formatting issue and
changing "1:" to a "0:" in the parameter list of the call to SendEscMsg.
HTH,
Mark S. Waterbury
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.
midrange.com
