Re: Service programs, procedures, not sure what to do

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Don't quite understand this...

In my experience, signature management is easy.  You simply use binder
source and a manually specified signature.  The signature only needs to
change when a code change is not backwards compatible and the user must
recompile.

New procs are added to the end of the existing binder source.

New parms on an existing proc aren't an issue as long as you add them at
the end and make them *NOPASS.

I can go from a SRVPGM with
MyProc(parm1);

To
MyProc(parm1:parm2);
MyProc2(parm1);

without needing to recompile any code using MyProc(parm1);

Charles

On Wed, Jan 7, 2015 at 4:01 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

> The reason being is keeping track of signatures can get to be a nightmare.
>
> For example, lets say you want to add a new settable variable.
>
> Instead of adding a new subprocedure for that variable (or having to update
> the current one and adding a new parameter to an already existant proc),
> just add a new settable field in the setValue() proc.  No new signature,
> just an updated version.