Re: User-generated errors

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 12/15/2016 11:36:22
AM:

I'd like to generate my own errors that can be trapped by MONITOR.
If the procedure doesn't have a MONITOR, then it would be trapped by
a MONITOR in the calling procedure. I tried to do this using
QMHSNDPM, but it's not working right.

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.

Perhaps the best way is to send the escape message to the current
call stack. Then, if the error is not trapped by the current procedure,
the exception will bubble up to the calling procedure(s). However, note
that the exception message id for the current procedure will not be
carried up as the exception bubbles up. Instead, the exception message
will change to CEE9901 unmonitored exception messages.

Sincerely,

Dave Clark