|
Recreate the files with DDL rather than DDS so the validation is on the WRITE, not the READ. Of course, then you have to change customer files. On 11/28/06, James H H Lampert <jamesl@xxxxxxxxxxx> 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 -- 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.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
