× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Eval Exception Error Trapping
  • From: "Bob Cozzi" <cozzi@xxxxxxxxx>
  • Date: Sun, 25 Jul 1999 16:26:20 -0500
  • Importance: Normal

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

http://www.RPGIV.com




> -----Original Message-----
> From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
> Behalf Of boldt@ca.ibm.com
> Sent: Friday, July 23, 1999 11:45 AM
> To: RPG400-L@midrange.com
> Subject: Re: Eval Exception Error Trapping
>
>
>
>
> Jon wrote:
> >Hans - I like the try/catch type approach in some ways but it is
> overkill in
> >many ways. Why not simply permit the coding of the "E" extender
> on numeric
> >operations? That way I can trap at the statement level if I wish.
>
> On the other hand, the E extender, as currently designed, already
> has serious limitations.  For example, coding E on a WRITE will
> trap file exceptions, but not program exceptions.  But on other
> opcodes, it does trap program exceptions.
>
> Perhaps it is overkill, but when writing new apps, it's the only
> exception handling method you need to know about.  Today, you need
> to know about INFSR's, *PSSR's, error indicators, extender E, etc.
> MONITOR is one easy-to-understand technique that can replace all
> others.
>
> 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          *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.