Re: Decimal data errors

["Michael Ryan" <michaelrtr@xxxxxxxxx>]

How about a MONITOR block around the statements that access the suspect
fields?

On 11/28/06, James H H Lampert <jamesl@xxxxxxxxxxx> wrote:
> We have a customer with a couple of files with lots of
> decimal data errors in them. Fields that are nominally
> zoned decimal, that either have packed decimal values in
> them, or EBCDIC blanks.
>
> Apparently, their own applications aren't balking at the
> wonky field content, but ours are throwing DD errors,
> locking up server jobs and in some cases creating traffic
> jams by blocking other jobs from getting locks.
>
> They don't seem to be in any kind of hurry to clean up
> their database.
>
> Obviously, I could use a FIXNBR compiler option, but that
> would be kind of a "sledgehammer" approach to the problem
> (besides which, if the packed-value-in-zoned-field is
> meaningful, it would presumably discard meaningful data
> that their application understands just fine). Likewise, I
> could program-describe the affected files, but then, if
> they were changed in any way that affected the fields we
> used, or the record length, we'd have to go in and modify
> the source, and there wouldn't be any level-check errors
> to tell us when there was a mismatch.
>
> Any other ideas?
>
> --
> JHHL
> --
> This is the RPG programming on the AS400 / iSeries (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.