|
>You have to add the new exports to the end of your binding source. >Which screws up your attempt to use your binding source member as a handy service program reference sheet. I don't see how updating the binding source screws up anything. We assign signatures for each change that hold the version and date. This makes the binding source a very good reference on when procedures were added. I would rather spend a minute changing the binder source than an hour recreating programs that don't use the new procedure. Mike -- 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
