RE: Eval Exception Error Trapping

[Colin Williams <Williamsc@xxxxxxxxxxxxxxxxx>]

Title: RE: Eval Exception Error Trapping

Do you really prefer users to answer error messages?

-----Original Message-----
From: Leland, David [mailto:dleland@harter.com]
Sent: Monday, July 26, 1999 9:20 PM
To: 'RPG400-L@midrange.com'
Subject: RE: Eval Exception Error Trapping

Actually, ideally I'd like to see the same type of ability as in CL - C(ancel), D(ump), I(gnore), R(etry).  Error handling in CL is much better than RPG.

Dave

----------
From:   boldt@ca.ibm.com[SMTP:boldt@ca.ibm.com]
Reply To:       RPG400-L@midrange.com
Sent:   Monday, July 26, 1999 2:12 PM
To:     RPG400-L@midrange.com
Subject:        Re: Eval Exception Error Trapping





Dave wrote:
>Frankly, I don't care where I came from into the *PSSR.  I just want to
*CONTINUE
>to the next statement.   Of course knowing the statement number would be nice.
>Or even the type of  error or msgid or whatever.  But a simple continue with
the
>next statement will be great compared to the currently hobbled *PSSR.   We can
>then wrestle with QMHMOVPM and get the message out.

OK, then perhaps I need to understand more about how *PSSR
is used in practice:

1) What do you normally do in a *PSSR?  Do you do more than
   DUMP and give the user a "submit an APAR" message?

2) If you return back into the program, where do you normally
   resume processing?  Also, how do you distinguish between
   expected and unexpected exceptions?

3) In what situations would you use a *CONTINUE option on the
   ENDSR?

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com




* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *