Program signature violations

["Reeve" <news@xxxxxxxxxx>]

I am getting the you-know-what hammered out of me with service program
signature violations.

 

Here's a sample of my binder source:

 

strpgmexp  pgmlvl(*CURRENT) SIGNATURE('2004.02.03.1100')  

export     symbol('NYV005')                               

export     symbol('NYV005_CLOSE')                         

endpgmexp                                                 

                                                          

strpgmexp  pgmlvl(*PRV) SIGNATURE('2003.11.06.1100')      

export     symbol('NYV005')                               

endpgmexp                                                 

                                                          

strpgmexp  pgmlvl(*PRV)                                   

export     symbol('NYV005')                               

endpgmexp   

 

I'm using the same technique over a couple of dozen SRVPGM's.  I'm not
changing parameters lists and nobody else is either; it seems that doing a
bulk recompile of the couple of dozen application programs using the family
of service programs gives me a nightmare.  I recompile as I go in normal
daily activity and everything works fine; then, when I post a series of
changes, it's MCH4431's all over the place.  

 

The obvious question is if I'm actually using the binder source in the
creation of the service programs; I am.

 

The only other question I have is if using I'm missing something by using
UPDSRVPGM. 

 

I have one nerve left, and I'm jumping on it.  I'd be grateful for a clue
because I'm out of them.

 

Thanks,

Reeve