Binder Source

Hi all,

As someone still new to service programs, I'm having a problem understanding how to use binder source. Is the idea to be able to make several service programs with different procedures from the same modules?

Here's the reason for my question :

We have an early RPGIV containing one function that was written for use by an OPM. Subsequently other RPGIV have started calling this program. Each programmer wrote his own internal prototype to call the RPGIV function.
I've been made to transfer the code of this function to another module containing the rest of the procedures for that particular application. The existing program has therefore become an encapsulating program only.

I compared the size of the new and old objects :

OLD LIBRARY
MYPGM *PGM 843776
MYMOD *MODULE 819200

NEW LIBRARY
MYPGM *PGM 60141568
MYMOD *MODULE 2818048

This is a 7100% increase in size for the program!

This is understandable, because everything is bound uniquely by copy, and the module that now contains the function makes many other external calls.

Now, If we used a service program, I'm assuming that it would be compiled by copy uniquely on MYMOD, and the other modules used would be bound by reference to other service programmes, thus considerably reducing the size of the service program. Is that right? How would binder source help?

In this example, we may have 20 users using applications that call MYPGM. So that means that when we install, we can expect to use 20 * 60141568 in memory instead of 20 * 843776 bytes. Would that be correct?

Thanks.