Re: Processes after CRTSRVPGM

Grizzly Malchow wrote:

I'm looking for ideas on how to avoid program signature violations after
I run the CRTSRVPGM and the signature changes.

Are you using binder language? Are you creating a new signature every time you add a procedure to a service program? What about when you change a procedure's logic (without changing the parameter list)?

I was just curious what other people are doing to handle this.

The way I do it is to specify a signature when I initially create the service program. From then on, I add new procedures to the end of the export list in the binder language source, and UPDSRVPGM specifying the new module and binder source. Similarly, if I add a parameter I usually use the *NOPASS option, so that the only programs I need to rebind are the ones that need the new parameter, which I need to change anyway.

The only time I'd change the signature was if I had to remove a procedure entirely, or if I needed to add a parameter that was required for _every_ caller. In that case, I'd use a DSPPGMREF utility as you suggest.

Hope this helps,
Adam