Modifying *SRVPGM=MCH4431

[Jon.Paris@xxxxxxxxxx]

Rob I've embedded responses in your text below:

>> First just to be sure we are all on the same page of the hymnbook ....

>> Signatures only change when a new exported procedure is added to the Service
Program or when the _sequence_ of procedure names changes in the Binder source.
The former is probably your situation. For more information check out the new
RPG Redbook or the ILE Concepts guide.

I am thinking that there are 1 of three solutions.
1)  Employ some method of changing the service program
that doesn't change the signature.

>> That would be Binder language.  You have two options, either specify both
Current and previous signatures so that your "old" programs continue to run. or
use a hard-coded signature in the binder source and only change it when you
_want_ old programs to be re-compiled.  Both methods require discipline on your
part to ensure that the slot sequence (i.e.order of procedure names) does not
change.

2)  Employ some binding trick that doesn't care what the
signature is.

>> You can specify that no level checking is to be done but it is not a good
idea.

3)  Recompile or rebind every program that uses the service program - yuck!

>> Not such a big deal if you are using a change management tool but ....

>> Whatever else you do - do not ever specify a hard-coded signature of all
zeros! Several who have gone before you have found the hard way that this is not
a good idea.  The reason for this is left as an exercise for the reader.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---