Re: Open Source discussion on error handling was: RPGIII/RPG400 ERRORMONITORING

You know I didn't mean that. What I meant was that there is now way you
can write a catch all fix all error handler. The most modular thing you
can do is tell the user there is an error, or have the program ignore
the error and the users will think everything went okey dokey. 
For an error handler to work in all cases it will have to shoot for the
lowest common denominator and that is monitor the error and notify the
user.
If you want to fix the error then you have to get application specific.

> How can the user possibly know what's the best place to go?  If the
> programmer thinks that G is a good place to go back to, then the
> programmer should go there, using '*DETC' on the ENDSR.

--
L. S. Russell Programmer/Analyst
Datrek Professional Bags, Inc.
2413 Industrial Drive
Springfield, TN. 37172
mailto:leslier@datrek.com
http://www.datrek.com
--
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---