|
Hi Eric,
I am confused a little bit (since I shouldn't have asked a combined question). I am using my own signatures. Are you stating "yes" to having to create another *PRV version -or- "yes", add the module to the end of the list (leaving the signature the same) and re-create the service program?
The way it works is by comparing the signature at the time the program was bound with the signature of the service program. If they're the same, you won't get a signature violation.
So, if you've coded your own signature (with the SIGNATURE keyword of the STRPGMEXP command) then you can add new procedures to the end of the binding source and it'll work just fine without any changes to the callers.
On the other hand, if the system is automatically generating the signatures for you (if you kept the default value of SIGNATURE(*GEN)) the signature will change, and every caller will need to be re-bound.
Unless, you add a *PRV group with the previous signature, in which case the caller's won't need to be re-bound because the previous signature will be invluded.
IMHO, there's absolutely no advantage to specifying SIGNATURE(*GEN) (the default) or to using *CURRENT/*PRV groups of signatures. As long as you follow one simple rule -- Always add new exports to the end -- the hard-coded signatures will work better, and be easier to maintain.
Just my opinion, of course.
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
