×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Wed, Jun 18, 2008 at 12:33 PM, Aaron Bartell <aaronbartell@xxxxxxxxx> wrote:
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.
I won't argue that it isn't as feature rich, but could you provide an
example of the ON-ERROR not be executed? I use MONITOR *a lot* in my code
to pass custom errors.
your monitor code will not run in the following situations:
- you call a COBOL program and it uses STOP RUN to exit.
- the called procedure sends an *ESCAPE message back to the caller
of your procedure
- the job is ended
you want your exception handling code to handle all exceptions. try
finally does that. monitor end-mon does not. ( actually I am not sure
if try finally does handle all exit situations. I just know that
monitor ... end-mon does not. )
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.