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


  1.  Home
  2. RPG400-L
  3. November 2006

Re: Decimal data errors

The decimal data failure at READ-time makes sense because that is when RPG is moving the data to the fields in the program. The problem is if you put a monitor around the READ it'll probably only copy a subset of the record's data to your program's fields.
I've worked at a couple of places where all programs using a library of tainted files have to compile all of their programs using FIXNBR. It sucks but when you have to read in tainted data there isn't much of a choice. Of course I liked the old compiler's IGNDECERR parameter better. You could create an RPG-III edit program using IGNDECERR that would run through the file looking for problems and fixing them. 

James H H Lampert wrote:

"Michael Ryan" <michaelrtr@xxxxxxxxx> wrote:
How about a MONITOR block around the statements that access the suspect fields?
But it's not happening when our program tries to *use* the fields (in fact, some of those fields get ignored by our program), but when the record is read.
A MONITOR block would work, though, given that the programs in question are site-specific, and compiled on their box. But again, that presupposes it's applicable to the problem at hand, and I don't know enough about them to know one way or the other on that. 

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.