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


  • Subject: RE: Danger! Danger! using IGNDECERR and FIXNBR (was Question about RPGIV in V3R1)
  • From: Bernard Visser <bernard.visser@xxxxxxxxxxxxx>
  • Date: Thu, 18 May 2000 12:21:08 -0700

Well put Barbara, sometimes it takes a little more work to do it right, but
well worth it in the long run..."Pay me now or pay me later"

Bernie Visser
Sr. Software Developer
CIM Vision International
300 Oceangate, Suite 1500
Long Beach, CA  90802-4309
Bernard.Visser@cimvision.com
562-951-9080


-----Original Message-----
From: bmorris@ca.ibm.com [mailto:bmorris@ca.ibm.com]
Sent: Thursday, May 18, 2000 11:35 AM
To: RPG400-L@midrange.com
Subject: Re: Danger! Danger! using IGNDECERR and FIXNBR (was Question
about RPGIV in V3R1)





>Date: Wed, 17 May 2000 08:00:47 -0400
>From: boldt@ca.ibm.com
>
>Bill wrote:
>>I have been playing with some of the older programs we have and
>>converting them to RPVIV. Unfortunately some of them need to be
>>compiled with IGNDECERR *YES and this is not working in V3R1's
>>RPGIV.  Has anyone else had this problem?
>
>Try compile option FIXNBR(*ZONED) or FIXNBR(*INPUTPACKED)
>or even FIXNBR(*ZONED *INPUTPACKED).  (The default is
>*NONE.)

These options may stop you from getting inquiry messages, but they
probably won't help you in the long term.  I recently worked
with someone who had been using IGNDECERR(*YES) for years
because of some data structures that were not initialized.  It
turned out they also had a packed/zoned parameter mismatch that
they didn't know about since the decimal-data error that should
have warned them about this error was being caught by the
IGNDECERR(*YES).

I guess their program ran ok with garbage being used for that
parameter because the value "assumed" for the garbage was usually
zero, and their program ran ok with zero.  (!?!)

The way IGNDECERR(*YES) works, you cannot be guaranteed that the
"result" will be the same from one release of the operating
system to the next, or even, I'm told, from one operating system
PTF level to the next.

FIXNBR(*ZONED and *INPUTPACKED) are a bit better since they give
predictable and repeatable results.  The trouble is that they
handle ALL errors, not just the ones you know about.  It's probably
not always the case that a zoned value of X'12345F' should be
interpreted as 240.

In my opinion, whatever reason you have for using IGNDECERR(*YES),
it isn't reason enough.

Sorry about the rant, but I see IGNDECERR and FIXNBR as something
similar to a potion that hides cold symptoms until the cold is
gone and has a side effect of hiding pneumonia symptoms until
you die.

Barbara Morris, IBM Toronto Lab, RPG Compiler Development


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.