Re: Grrr... signature violation

[Scott Klement <klemscot@xxxxxxxxxxxx>]

No.  It has nothing to do with the parameters.  You can't change the names
of any exports (exported procedure names or variables) or the order of the
exports, or add new exports...

The real fix to this is to use binding source.   Binding source will let
you add new exports while still maintaining the old signature.   You can
then have a "new signature" and multiple "previous signatures", each one
corresponding to what the exports were at a certain time.   This way, your
service programs stay backwards compatable.

See the ILE Concepts manual for details.


On Fri, 3 May 2002, Wills, Mike N. (TC) wrote:

> Help! I have it fixed but know I want to know why and how to prevent it. I
> just added a couple lines to my subproceedure, that is it. Then after I
> recompiled the module and recreated the service program, I got a signature
> violation. After recompiled the calling program it works fine. Do I not
> understand how this all works correctly? I thought, as long as I don't
> change the parameters, I don't have to recompile all of my programs. Is this
> a wrong assumption?
>
> A very confused Mike