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



I would like to learn more about the "condition handler". Can you give me more info about this. {examples, links}

Vincent Forbes

... monitor is your friend
and a condition handler is your BEST friend.

The *PSSR subroutine is archaic and not a good solution when managing application errors that run on a web server. I
would strongly suggest using condition handlers for this as you have MUCH more control over how to proceed. Further,
*PSSR is an 'after the event' clean-up routine. Not only has the exception been thrown but it has percolated to the
control boundary, promoted to a function check (CPF9999) and the condition manager is now looking for somebody to
shoot.

Condition handlers beat monitor because monitor will handle any exception thrown within the monitor group. Condition
handlers work even better than MONMSG because you can choose to handle the exception based on any criteria you wish.
Also, the condition handler is called BEFORE the original *ESCAPE or *NOTIFY message has reached the control boundary
so the call stack is pristine. You can write code in your condition handler to pause the process so you can debug the
problem. I have been able to recover from divide by zero, substring length and array index errors this way. The
process continues from the next line of code as if nothing went wrong. You can't beat that!

I genuinely believe it is one of the many unsung heros of ILE.

Cheers

Larry Ducie

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.