×
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.
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 :-)
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
