Re: Bind by reference doesn't mean dynamic call?

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

I agree with everything Simon said, but wanted to add a few points:

a) If you're binding via a binding directory, then it's the library (or 
*LIBL) specified on the ADDBNDDIRE command that counts.

b) If the srvpgm is already activated, you'll need to reclaim the 
activation group before it'll pick up the new one.  (Though, I think 
there's an exception to this somewhere... like if the program that 
created an activation group is recompiled, everything in the actgrp gets 
reactivated on the next call...?  Something like that, I haven't quite 
pinned it down yet.)

c) Basically, it's the exact same behavior you'd see with *PGM calls, 
except of course that you're calling a procedure and there can be many 
procedures in a single service program.


Simon Coulter wrote:
> Depends on how you did the bind. If you qualified the reference to  
> the service program then the one in A will still be used. If you used  
> the default of *LIBL then the one in B will be used. Whether that's a  
> problem depends on how the one in B was built and whether it has a  
> signature compatible with the consuming program.