|
On Tue, 28 Nov 2006 12:00:05 -0600, rpg400-l-request wrote
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.
You need to modify your programs to specify a DS as the result field on the READ/CHAIN operations. That way the DD error only occurs if/when the field is touched. It will not occur on the read. It currently happens on the read because RPG always moves data from the buffer into the field _unless_ you specify a result DS. That is why it blows up on the read. Use the approach outlined and it won't happen. Jon Paris Partner400 www.Partner400.com
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.