× 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: "Mark A. Manske" <mmanske@xxxxxxxxxxxxxxxxxx>
  • Date: Fri, 23 Jun 2000 10:24:34 -0500
  • Importance: Normal

The problem is not IBM, Eval, nor ILE;

The real issue is how you are using the tools you have been given;

Eval is a great tool; but remember in numeric operations (don't forget you
can "cat" alpha using eval too), the result field MUST be large enough to
hold the largest possible value, in your code, it is not;

If you want to RISK dropping values WITHOUT knowing, use the add op code,
and hope you do not have a data overrun that no one knows about until the
IRS comes around and your reports do not total up properly.

You have only three choices here, #1.make the 9,2 field smaller (say 5,2) so
it will fit into the 7,2 field(if you are lucky and do not have alot of
detail lines with large numbers in them) #2.make the 7,2 field at least 15,2
to hold the "possible" value or lastly #3.do not use eval, use ADD, and risk
your totals being wrong.




-----Original Message-----
From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
Behalf Of keith mcintosh
Sent: Friday, June 23, 2000 9:01 AM
To: RPG400-L@midrange.com
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.