Re: Processes after CRTSRVPGM

On Feb 13, 2008 3:07 PM, Lim Hock-Chai <Lim.Hock-Chai@xxxxxxxxxxxxxxx>
wrote:

Yes. Sort of. However, if you exam it a bit more, it really makes no
different between the static signature method and the *prv/*current
signature method. Both methods require you to export new procedure to
the end of the service program. Otherwise, unpredictable result will
occur.

So, if you do below, existing program (Compiled before the *current was
added) will not get signature violation but it will still execute the
wrong procedure. ==> *prv/*current method does not really buy you
anything (Actually it is more trouble than it worth).

Well, that's true. Not many techniques will buy you anything if you don't
use them correctly.

The only way around the rule to add new exports to the end of the list is
to rebind all client programs.

The value of a generated signature comes from the fact is generated from the
ordered list of exported names. If you make a mistake constructing the *PRV
signature you *will* find out quickly when you attempt to active a user of
the *PRV signature that has not been rebound. If you specify the the
signature, you loose this safeguard and you get to debug strange and
wonderful new bugs.