|
Not sure who this came from: >Yes! My job today is to update 71 RPG OPM programs. > ........ >If this routine had been coded as an ILE procedure, all I would have to do >is change the procedure one time, and then recompile. Alan Addison wrote: >If it is exactly the same in each program, why not create a copy member and >use that instead. Then you only have to compile all the programs that use >it once its changed. That is exactly why it should be a procedure in a service program. When you made a change to the copy member you would have to: 1. Make one change 2. find all 71 programs that used that copy member 3. Make sure change does not create a conflicts with any variables in your 71 programs 4. Recompile all 71 programs If you development is done on a different box than your production box, 5. Replace all 71 programs on your production box with the recompiled versions. With a service program you: 1. make one change 2. Recompile the service program. 3. Replace program on production box if scenario is same as above. Regards, Seth Shields +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | 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.