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

DUH! What was I thinkin??? :(
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.
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.

http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/QB3AGZ01/1.5.2.1.1#HDRPTACODE

Buck Calabro wrote:
> 
> When this code encounters the divide by zero error, *PSSR sets Result to 0
> then returns to *DETC.  Since ErrFlag is raised, it executes nothing and
> exits.
> 
> Appropriate bits of changed code:
> 
> >       *main()
> >      C                   if        not ErrFlag
> >      C                   exsr      RTNADD
> >      C                   exsr      RTNSUB
> >      C                   exsr      RTNMUL
> >      C                   exsr      RTNDIV
> >      C     Result        dsply
> >      C                   endif
> >
> >      C                   Eval      *InLR=*On
> >      C                   return
> >
> >      CSR   RTNDIV        begsr
> >      C                   Eval      Result=PI/ZERO
> >      C                   endsr
> >
> >      C     *PSSR         BegSR
> >      C                   eval      ErrFlag = *on
> >      C     ErrTyp        cat       CPFNUM:0      ErrorID
> >
> >      C                   Select
> >      C                   when      ErrorId = 'MCH1211'
> >      C                   eval      Result = 0
> >      C                   EndSl
> >
> >      C                   EndSR     ErrorAct
> >
> The original code ID'd itself, encountered the divide by zero and tripped
> the PSSR, which set the error flag then returned to the top.  The code at
> the top then decoded which routine failed and continued at the next "proper"
> code fragment after the error.
> 
> Appropriate bits of original:
>       * Mainline.
>       *    *DETC         Tag
>      C                   If        ErrFlag='Y'
>      C                   Eval      ErrFlag='N'
>      C                   Select
>      C                   When      CurrRoutine = RTNDIV
>      C                   Eval      Result=0
>      C                   GoTo      PastDiv
> 
>       * Program processing occurs here
>      C     Div           Tag
>      C                   Eval      CurrRoutine=RTNDIV
>      C                   Eval      Result=PI/ZERO
>      C     PastDiv       Tag
> 
>      C     *PSSR         BegSR
>      C                   Eval      ErrFlag='Y'
>      C                   EndSR     ErrAction
> 
> Buck
> +---
> | 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
> +---

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