|
Hi! I want to thank you for your support. The problem I had in my program was not directly related to the look-ahead fields. I misused the MR indicator, so the result was not correct. My look-ahead code was correct. My boss doesn't allow me to convert legacy code to ILE when I have to add features to the old S/36 programs we have here. He said that it is more unsafe to do a new program than modify an old one. I don't agree... Charles "Douglas Handy" <dhandy@xxxxxxxxx> a écrit dans le message de news:ca27ca770612281033q3f334489qfb7e649050b8a4ef@xxxxxxxxxxxxxxxxx
Charles, I think I misread your post originally. Do you only use lookahead on the secondary file which is defined as input only? If so, then the lookahead fields should reflect the next record contents. Are the field names used for the lookahead I-specs unique? You don't want those fields to have the same name as the corresponding fields in either
the
primary or secondary file's active record. Can you post the I specs for the primary and secondary, including the lookahead definitions? Doug -- 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.