RE: Overflow diagnostic messages

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

As I recall, this is working as designed.  Traditionally, RPG was very
forgiving of numeric overflow, and did not enforce any restrictions on
numeric operations.  Remember the old date format conversion trick (USADATE
Mult 10000.0001 ISODATE)?  The EVAL opcode brought runtime detection of
overflow conditions.

If you were to use Eval instead of Z-ADD, then you would get an error at
runtime.

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: paramasivam.murugesan@xxxxxxxxx
[mailto:paramasivam.murugesan@xxxxxxxxx]
Sent: Tuesday, January 25, 2005 9:52 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Overflow diagnostic messages



The following are a few lines in one RPGLE pgm.

C               Z-ADD     30157.39      VAR1              7 2
C               ....
C               Z-ADD     VAR1          VAR2              7 3

Overflow would occur as per the above code. The compilation option
TRUNCNBR was set to *NO. I did not see any diagnostic messages in the
compiler report. Am I missing something?

Is there any way to see, where are the lines, in which, overflow might
occur?

TIA,
Murugesh.






Confidentiality Notice

The information contained in this electronic message and any attachments to
this message are intended
for the exclusive use of the addressee(s) and may contain confidential or
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or
Mailadmin@xxxxxxxxx immediately
and destroy all copies of this message and any attachments.

-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.