×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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.
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.
midrange.com
