|
Hard coding in a signature (which is what I mentioned) in the binder source will also work. The program won't blow up when it uses the service program after the service program has been modified because the signature never changes.
Except that you can manually change the signature when you want to deliverately trigger a signature violation (which I've done once or twice, though it's usually not necessary.)
Either way to avoid a level check on the service program could be bad for the program using the service program just as a file change with LVLCHK(*NO) could cause problems.
It's only "bad for the program" if an incompatible change was made to the service program. One of the biggest advantages of service programs is the ability to add new procedures WITHOUT breaking compatibility and WITHOUT having to go back and re-bind every program that calls it.
If you don't use binder source, you lose that capability. If that's the case, why bother with service programs? If you have to re-bind them every time you make a change, you may as well use a *MODULE!
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
