|
You don't need to recompile just because a copy book changes (unless this is something that Turnover forces). If you use self-generated signatures, programs that don't use the new functionality don't need to be recompiled. They know nothing of the new functionality so why would they need the updated copy book? Matt -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of praveen gunda Sent: Thursday, February 16, 2006 1:07 PM To: RPG programming on the AS400 / iSeries Subject: Re: Best way of using Service programs. Thanks for so many tips guys.. I really appreciate it. This is a real happening forum and now I rue, I should have found it much before. Anyways, I like these suggestions.. One of the biggest practical problem I am finding with using one copy book per service program to store the procedure declaration is: Each time I add a new procedure to the service program, the copy book changes and as such I have to recompile all of my programs that use this. Also I cannot use updpgm as Turnover does not allow it. <snip>
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.