RE: Eval Exception Error Trapping

[boldt@xxxxxxxxxx]

Bob wrote:
>>The E operation extender should be supplanted with a keyword on the header
>>spec. That is something like:
>>  H     ERROR(*IO | *ALLWAYS | *NONIO)
>>Then we would not have to code that big-ass "E" for everything to check
>>the %ERROR or %STATUS.
>> Bob Cozzi

You want to assume E coded on all operations in the program?
Yikes!  That means you would have to code IF %ERROR after
every statement to ensure that you can handle any unexpected
exception that crops up.

I guess I don't understand what you're asking for here.

John wrote:
>I'd vote for this suggestion.  That would cut down on the number of tags you
>would have
>to remember Hans.    Then,   Give us the *NEXT on the factor 2 of the *PSSR.

The *PSSR and INFSR give you two programming problems:
1) Figuring out where you came from; and 2) determining
where to go next.  These two problems are basically
equivalent.

Having a *NEXT (or *CONTINUE) option on the ENDSR helps
on the 2nd problem, but you still need to know where
you came from any time there is the possibility of
exceptions occurring in more than one place in the program.

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