|
On 22/02/2006, at 12:32 PM, James H H Lampert wrote:
I just had an issue, testing my project, with a "signature mismatch" on a service program whose external interface should not have changed significantly.
midrange.com
The signature changed because:
o You are using EXPORT(*ALL) -- always a dumb idea
o You changed the binding source such that SIGNATURE(*GEN) changed
o You changed the SIGNATURE value manually
That brings up an interesting question: Is it possible to bind a program in such a way that it doesn't care if the service program it uses has a newer signature?
Yes. Use previous signature support or specify a manual signature value and never change it.
Or something that can be done in the creation of the service program?
Yes. Use previous signature support or specify a manual signature value and never change it.
If you choose to specify a constant manual signature you must ensure you never change the order of the exports and always add new exports at the end of the list. I don't think much of that idea because it's not as flexible as supporting previous signatures.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.
