|
On Dec 15, 2016, at 11:40 AM, Brian Johnson <brian.johnson.mn@xxxxxxxxx> wrote:
On Thu, Dec 15, 2016 at 10:36 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:
Procedure1 => Procedure2 => ErrorProcedure
I expected the MONITOR block in Procedure2 to catch the error, but it's
actually the MONITOR in Procedure1 that's catching it.
That's because you are sending the escape message to Procedure1. You need
to use '*' and '1' for call stack and offset parameters in ErrorProcedure
to send the message to the caller of ErrorProcedure.
--
Brian Johnson
brian.johnson.mn@xxxxxxxxx
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
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
