Maybe I don't know what exactly defines what an *Escape message is, but
Monitor in a procedure that has a procedure call within it will have
that procedure's error caught.
Example:
This monitor will catch any errors encountered in the callProc
procedure.
Monitor;
callProc();
On-Error;
EndMon;
I try to put Monitor statements in most/all of my exported procedures
and have seen them catch errors in subsequent internal procedure calls.
Kurt Anderson
Application Developer
Highsmith Inc
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
Sent: Wednesday, June 18, 2008 10:58 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Is RPG 'DEAD"
On Wed, Jun 18, 2008 at 11:31 AM, <Michael_Schutte@xxxxxxxxxxxx> wrote:
<SNIP>no try ... catch .... </SNIP>
Then what is???
Monitor;
On-Error;
EndMon;
it is no where as comprehensive and feature rich as exception handling
in java or c#. In RPG if an *escape message is sent to a procedure
lower on the invocation stack, your on-error ... endmon code will not be
executed. In C#, the try ... finally handler will be called. You can
rig the equivalent to try finally in RPG and ILE, but it is a lot of
code.
--
This is the RPG programming on the AS400 / 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.
midrange.com
