RE: End users answering messages--Was RE: Open Source discussion on e rror handling was: RPGIII/RPG

I will plead total ignorance here, so no one needs to point it out later on,
OK??

Is there a simple example program somewhere that shows what it is you are
suggesting with *PSSR?  In reading the manual it looks to me like you write
a subroutine for every possible error condition and name the subroutine
*PSSR. What use is that?  If you know the errors anyway, why not code for
them in the first place?  What part of the puzzle am I missing?  What good
is a catch-all subroutine that sets a bad array index back to 1 so
processing can continue?  That brings real meaning to "computers make
mistakes very accurately and very fast."


-----Original Message-----
From: Colin Williams [mailto:colin.williams@technocrats.co.uk]
Sent: Monday, February 14, 2000 4:07 AM
To: boothm@goddard.edu
Subject: RE: End users answering messages--Was RE: Open Source
discussion on e rror handling was: RPGIII/RPG


If your programs coded to expect errors, why should your users ever see
a message that they need to reply to. 
Any untrapped errors should be picked up by *PSSR and perform your error
processing.
+---
| 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
+---