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

On Wed, Sep 13, 2017 at 3:14 PM, David Gibbs <david@xxxxxxxxxxxx> wrote:

On 9/13/2017 2:08 PM, Alan Campin wrote:

As long as the interface has not changed, you will not need to
recompile.

You need to create a current listing your procedures. then when you
add a new procedure, your current becomes your previous and your new
current is at the top.

As long as new procedures are added to the end of the list of procedures,
and you specify a constant signature in the binder source, you don't need
to recompile programs that reference the service program.

As I understand it, procedures are reference by their relative location in
the service program.

The only time you would have to specify multiple PGMLVL's in binder source
is if you remove, or reorder, the procedures that are specified.

First of all, thanks to all who responded!

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.

- Dan