× 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: The target for a numeric operation is too small!!!!!
  • From: "John Taylor" <john.taylor@xxxxxxxxxxxxxxx>
  • Date: Fri, 23 Jun 2000 08:57:12 -0600

Keith,

No offence intended, but I have to say that the more appropriate question
might be why you would want to supply erroneous data to your users. If it's
not possible to make your report field large enough to handle the maximum
possible result, then you should test for possible overflow and alert the
user. For example:


D MaxNum          S                          Like(  RPITC1 ) Inz( *Hival )


C                            If        ( RptValx(1) <= MaxNum )
C                            Eval    RPITC1 = RptValx(1)
C                            Else
C                            Eval    RPITC1 = 0
C                            Write  OvrFlwErr
C                             Endif

If you're intent on ignoring the overflow, use a condition handler to trap
the error yourself.


Regards,

John Taylor
Canada

----- Original Message -----
From: "keith mcintosh" <keith_eh@yahoo.ca>
To: <RPG400-L@midrange.com>
Sent: Friday, June 23, 2000 08:00
Subject: The target for a numeric operation is too small!!!!!


> Maybe someone from IBM T.O. could answer this.
>
> I am creating a report and adding up totals into an
> array.  When I eval the total into a Report Field I
> get
> a error.
>
> Message . . . . :   The target for a numeric operation
> is too small to hold the result (C G D F).
>
> Why does it give me a Hard Halt?  and why is there no
> "I"?
>
> Why would the system send a Message to qsysopr or have
> a user cancel the program in the middle of a process
> because a REPORT Field is To Small...
>
> I have "Truncate numeric . . . . . . . .   *YES"
> on the Create RPG Module.
>
> The field sizes are P(9,2) being put into a P(7,2)
> report field.
>
> RPG III is looking better every time I use RPG IV.
>
> The Statement is
>
> C                   Eval      RPITC1 = RptValx(1)
> On v4r2m0.
>
>
> K.
>
> _______________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.ca address at http://mail.yahoo.ca
> +---
> | 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
> +---

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

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.