RE: Can you have nested MONITOR statements?

Nice thought, but it doesn't ring the old memory bell.

IIRC, I originally set it up that way so that the message would be set back to 
the caller of the sub
procedure that called Msg_Throw().

So Proc1 calls Proc2 which detects some error and calls Msg_throw() which sent 
the message back to
Proc1 instead of Proc2.

Keep in mind that Proc2 would normally be in a *SRVPGM.

I may have done it that way so that Proc2 didn't see the error at all. 

What I can't remember is why I may have wanted that in the first place. <grin> 
I do remember that I
did make a decision to use 2 instead of 1.

Speaking of Throw/Catch I ran across an old message in the archives in which 
you said that you didn't
like handling business logic exceptions that way and instead preferred to pass 
a status code variable.
Do you still feel the same way?

Thanks,

Charles


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On 
Behalf Of Jon Paris
Sent: Wednesday, February 21, 2007 2:45 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Can you have nested MONITOR statements?

See my reply to Simon for more info.

The original was probably set up to go back two levels so that when used in an 
ILE *PGM it went back
past the PEP to the "real" caller.

Jon Paris
Partner400

www.Partner400.com 


--
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.




This e-mail transmission contains information that is intended to be 
confidential and privileged.  If you receive this e-mail and you are not a 
named addressee you are hereby notified that you are not authorized to read, 
print, retain, copy or disseminate this communication without the consent of 
the sender and that doing so is prohibited and may be unlawful.  Please reply 
to the message immediately by informing the sender that the message was 
misdirected.  After replying, please delete and otherwise erase it and any 
attachments from your computer system.  Your assistance in correcting this 
error is appreciated.