Ok, "stupidity" is a bit much, >if< you consider legacy systems
some businesses have depended on for a number of years.
I work for a coka-cola bottler and there is one such system commonly used.
In many regards, a system which once was ahead of it's time, but because
of "work arounds" used to overcome limitations of older technology does,
in some cases, "benefit" from the ignominious igndecerr(*yes).
The sun is setting on this venerable system, but another, much more
prominent, world leader of a system worked for years to fill her
shoes..., so I think a little grace can be allowed for those who
labored before we had the benefit of modern computers and database
technology.
Maybe you meant to say "ignorant", but I don't think that applies either.
Maybe they even knew a better way, but time and resources dictated
other wise and their intentions of returning to fix the problem were
thwarted by . . . time and resources.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Monday, September 17, 2012 11:14 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: igndecerr(*yes)
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 ...)
--
Barbara
--
This is the RPG programming on the IBM i / System i (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.
As an Amazon Associate we earn from qualifying purchases.