RE: service program signatures

Hi Brian,

That's what binder language is for. When you add exports to your
serviceprogram the signature will change because it is generated as a
checksum of your exports or from your own signature if you defined one.
In binder language you can add your new export, and also keep the
signature for the programs that are compiled against the original
serviceprograms. It is covered in detail in the ILE Concepts manual
(SC41-5606-06) chapter 5.

Look at the following example:

STRPGMEXP PGMLVL(*CURRENT) SIGNATURE('30.06.2005 V 1.1') 
  EXPORT SYMBOL('LNG_Libraries_getLibName')              
  EXPORT SYMBOL('LNG_Libraries_Open')                    
  EXPORT SYMBOL('LNG_Libraries_Close')                   
ENDPGMEXP                                                

STRPGMEXP PGMLVL(*PRV) SIGNATURE('30.06.2004 V 1.0') 
  EXPORT SYMBOL('LNG_Libraries_Open')                    
  EXPORT SYMBOL('LNG_Libraries_Close')                   
ENDPGMEXP                                                

As long as the programs that are calling these routines are not
recompiled, they will use the signature that is created on the *PRV
export definition.
When you recompile the using program, it will use the new *CURRENT
signature.

So if you use binder language like this, it will create multiple
signatures including the original signature.

Hope this helps,

Arco Simonse

> -----Oorspronkelijk bericht-----
> Van: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] Namens brian
> Verzonden: woensdag 13 juli 2005 21:22
> Aan: midrange-l@xxxxxxxxxxxx
> Onderwerp: service program signatures
> 
> I'm confused about service program signatures. It seems as 
> though IBM is telling me that if I add an export to my 
> service program, the signature of the service program will 
> change, and I'll have to recompile all the programs that use 
> the service program, which seems pretty unreasonable.
> 
> I'd rather have things so that it isn't necessary to 
> recompile a program that uses the service program unless 
> there is an API change, not just because I add a new export 
> or something.
> 
> Thanks for advice.
> --
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change 
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, 
> please take a moment to review the archives at 
> http://archive.midrange.com/midrange-l.
> 
> 
DISCLAIMER:
This message contains information that may be privileged or
confidential and is the property of C.Meijer B.V. It is intended only for the 
person to whom it is addressed. If you are not the intended recipient, you are 
not authorized to read, print, retain, copy,disseminate, distribute, or use 
this message or any part thereof. If you
receive this message in error, please notify the sender immediately and delete 
all copies of this message. 

This footnote also confirms that this email message has been swept by the 
presence of computer viruses