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

> You can monitor STSCODE for a value other than 00000 !
> 00102 is a divide by zero error, just monitor for it and call your error
> handler.
> With *PSSR there is not really much choice, either let RPG default
> handler take over or code it to return to some point in the fixed logic
> cycle.
> 
Its been a while, but what I've seen done successfully, is to have the PSSR
subroutine (carefully) call a generic subprogram, passing the entire program
status data structure, as a single parm.  Then, the subprogram (carefully)
logs the error, and passes back what to do.  It can also, depending on the
program/situation give an "operator" a few minutes to decide, before
defaulting with an action.


> No matter what you do to trap the error (there are as many ways, as
> errors) each error could require radically different methods to correct.
> The most modular thing you can do is display a message and allow the
> user to pick which point in the logic cycle to which they want to
> return.
> That should work in all cases, just trap the error display the error and
> let the user choose G, C, D.
> 
> 
Isn't that what OS400 does for you if you skip the PSSR?
         

Regards,
Jerry Jewel


"Better living through fine code and hot coffee!"
+---
| 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
+---