|
Hi Fran, > I made yet another change with P$Date but didn't change the binder > source (*Current to *Prv) because there was no need. Figured, well, I AM > still testing and will be recompiling the new RPGLE pgms that call it. > Why bother? Checked the signatures before and after re-creating the > service program. Hmmph...that current signature didn't change. The > previous still matches the program that needs to go back into producion. > I read it four times to be sure (I'm thinking seriously of giving them > my own names, now). If the signature is generated when the service > program is created, why didn't it create a new signature for *Current? I'm assuming that you're using the defaults for STRPGMEXP? In other words, you have: STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE(*GEN) If thats the case, you'll always get the same signature as long as you don't add/remove/rename/rearrange the exported symbols in your binder source. You can change the RPG source as much as you like, as long as it doesn't require a change to the binder source, it'll have no effect on the signature. If you use LVLCHK(*NO) or SIGNATURE('mysignature') then it's even less restrictive. In those cases, you'll never get a signature violation, even if you DO change the exports in the binder source. But then it's even more important not to remove or rearrange the exports in the binder source, since that could cause existing programs to call the wrong procedures...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.