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

Again, thanks to everyone offering advice and answers! I'd definitely be
lost without the midrange.com lists! As someone mentioned elsewhere
recently, you don't know what you don't know. I'm reading through the ILE
Concepts reference and Brad's "Implementing ILE for RPG 101".

What are the circumstances by which one needs to use UPDPGM? I presume
that it replaces the CRT* compile to a client program to which no
modifications were made to its source?

- Dan

On Wed, Sep 13, 2017 at 6:55 PM, Niels Liisberg <nli@xxxxxxxxxxxxxxxxx>
wrote:

Let me just clear it. The calls are made by vector number - not by name. So
each call to your procedures are stored as an index to an array of
procedure pointers. If you introduce a new procedure in between existing
procedures, then subsequent procedures are "moved" to one index higher-
messing up the refereces in the "client" calls..... does it make sense?

UPDPGM of all client programs will ultimately fix this if you want to keep
the procedure names in a certain order.
tor. 14. sep. 2017 kl. 00.44 skrev Niels Liisberg <nli@xxxxxxxxxxxxxxxxx>:

If you put it in the end of the binder source - you have no reasons to
recompile... imho. That is best practice.