× 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 2012/9/17 9:36 AM, Dave wrote:
...
I eventually found that the reason being was that a custom compile
command compiled the RPGIII with igndecerr(*yes).

My question is, why would anyone want to compile this way?


Why? Stupidity is the only answer I can think of. Or at least, the only kind answer. Irresponsible laziness is another possibility, if whoever added IGNDECERR really understood what they were doing.

Turning off decimal data error reporting because of one known source of "ok" decimal data errors is similar to _permanently_ turning off all the smoke alarms in the house because the toaster sometimes triggers the one in the kitchen.

I wish IGNDECERR had never been added to RPG III, and I wish FIXNBR hadn't been added to RPG IV. FIXNBR is a tiny bit less horrible since it produces a predictable result, but I still think it was wrongheaded to provide an option to ignore data errors. (For the record, I am the one responsible for adding FIXNBR(*INPUTPACKED). We can't always get what we want ...)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.