|
Vijosh A wrote: >Your idea is interesting. > >But let me draw your attention to a problem that comes to my mind- If >suppose you do not have a KLIST and as it often happens there are changes >to key fields (although not frequently). So if I use your method then I will >have to change the same in many a places. Especially when you are using >physical file fields in the KLIST. This may make maintenance difficult. So >therefore I would still prefer to use KLISTS. With the new approach, since expressions would be allowed, we would have to relax the rule that requires exact length match. So when you change a key field in the file, you only have to recompile. Cheers! Hans Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.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.