AW: AW: problems with program binding

["Knezevic, Mihael" <Mihael.Knezevic@xxxxxxxxxxx>]

yes. that would probably solve it. but that would also mean, that we cannot use 
a binding directory anymore!? 

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] 
Im Auftrag von AGlauser@xxxxxxxxxxxx
Gesendet: Freitag, 8. Dezember 2006 18:29
An: Midrange Systems Technical Discussion
Betreff: Re: AW: problems with program binding

Mihael Knezevic wrote on 08/12/2006 12:22:21 PM:

> it is not that i don't understand why the "wrong" serviceprogram 
> procedure is called but how to overcome this problem. binder 
> language is one method of overcoming this problem. i just wanted to 
> see if there are other ways of doing it.

Let me see if I've understood your problem.  You are adding some 
procedures to service program A (SPA).  Another developer is working on a 
program that uses SPA, but _not_ your new procedures.  Is that right?

If so, a simple solution may be for the other developer to specify the 
library of the service program at binding time.  So, instead of CRTPGM 
MODULE(PGMA) BNDSRVPGM(SPA), one would use CRTPGM MODULE(PGMA) 
BNDSRVPGM(PROD/SPA) instead.

Of course, unless you use binder source, you will have to rebind that 
program when you install your new version of SPA to production (I think 
UPDPGM would work).  Otherwise, PGMA will get a signature violation error 
when it tries to use the new version of the service program.

HTH,
Adam

#####################################################################################
Attention:
The above message and/or attachment(s) is private and confidential and is 
intended 
only for the people for which it is addressed. If you are not named in the 
address 
fields, ignore the contents and delete all the material. Thank you. Have a nice 
day.

For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
#####################################################################################