|
On Nov 2, 2015, at 4:58 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:
On 02-Nov-2015 14:35 -0600, Vincent Forbes wrote:
One of the things I found is that working RPG III programs, after
conversion, all of a sudden can fail due to value "overflow". That
was a bonus since it located a long time hidden bug.
It does not take a lot of effort to get rid of.
MMDDYY MULT 10000.01 YYMMDD
Was not that overflow error prevented with the Truncate Numeric (TRUNCNBR) specification of *YES, so as to "Ignore numeric overflow and move the truncated value to the result field" [to mimic] just like what happened in the older RPG? And that parameter specification defaulted to *YES, so that problem would not become an issue for that calculation with the newer compiler, unless explicitly changed was the default or the explicit specification to the value of *NO, asking to cause the overflow error to be exposed at run-time? I was too lazy to test; but interested enough to overcome my laziness to look up the parameter name, the parameter help text, and the default :-)
--
Regards, Chuck
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
