Re: Service program signatures, and how to avoid unnecessarily recompiling programs that call service programs

On 9/13/17 5:40 PM, Dan wrote:

On Wed, Sep 13, 2017 at 3:14 PM, David Gibbs <david@xxxxxxxxxxxx> wrote:
Currently, my service program (and binder source) reference two RPG
modules, M1 and M2. Module M1 has four procedures M1P1 - M1P4, and module
M2 has three procedures M2P1 - M2P3. My binder source reads as follows:
STRPGMEXP PGMLVL(*CURRENT)
EXPORT SYMBOL(M1P1)
EXPORT SYMBOL(M1P2)
EXPORT SYMBOL(M1P3)
EXPORT SYMBOL(M1P4)
EXPORT SYMBOL(M2P1)
EXPORT SYMBOL(M2P2)
EXPORT SYMBOL(M2P3)
ENDPGMEXP

Now I need to add procedure M1P5 to module M1. Will I be able to add it
after M2P3 in the above binder source? If not, I'm thinking I might need
to separate my service programs to have only one module.

Add a SIGNATURE parameter to the STRPGMEXP and you can. Without the SIGNATURE parameter, the signature of the service program is calculated and will change every time you add a new procedure.

If you add a SIGNATURE parameter (like SIGNATURE('MPSRV01')), that's what the signature will always be. As long as you always add procedures to the end of the binder source, you'll be fine.

david