|
Joe, >Pardon my ignorance, but if you are only putting on function per program, >why bother making them service programs? I am not defending the one procedure per service program scheme, but if you make procedures into service programs then you are binding by reference. If you compile the procedure into a module, and then link the procedure in your CRTPGM, then you are binding by copy. Then, say six weeks later someone changes a few lines of code in that widely used date manipulation procedure (as an example), if it is in a service program you update the service program and move on with today's activities. If that code was copied into 100 programs because you bound by copy, then you have a lot of UPDPGM statements ahead of you. A good rule of thumb is to put any procedure that is used by more than one program into a service program. HTH, Andy Holmer
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.