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

I have to say that all the error handling methods I had the displeasure to
be involved with tend to obscure the problem and make it very difficult to
track down the real error. It's a lot easier to find the problem when I can
get a program dump or at least an error message showing me the program and
the statement number where the error occurred.

Having *PSSR is very nice from the user point of view, but even if it
manages to log the details of the problem, it's one more layer I have to
figure out -- where is it logged to (spool file? job log? database file?)
did it show enough detail to back track and find the problem?

I agree that it's not a good thing for users to see those ugly error
messages, but I'd rather see a program that prevents the problem in the
first place (check for zero before dividing by it, test array indexes before
using them if they aren't under direct program control, etc.) than have it
handle it in some way that obscures the problem.

Can you tell I've been doing more maintenance than development the last few
years?

Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax

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


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.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
+---