We have a service program with 160ish modules, created last year. We do use binding source with it.
Whenever we add modules/procedures to it, we have to recompile everything that uses it because it always generates a new random signature, instead of respecting the binding source
We cannot work out why
I noticed today that there were several problems with the binding source:
* DSPSRVPGM listed export procedures that were missing from the binding source
* DSPSRVPGM listed export variables (data items) that were missing from the binding source
* There were procedures in the binding source that did not exist in the bound modules
I fixed all that, and it did not fix the signature.
I even tried using RTVBNDSRC to generate the binding source from the service program, changed the signature, and then recreated the service program using that source, and it still did not work.
Does anyone know what I may be missing?
Whenever we add modules/procedures to it, we have to recompile everything that uses it because it always generates a new random signature, instead of respecting the binding source
We cannot work out why
I noticed today that there were several problems with the binding source:
* DSPSRVPGM listed export procedures that were missing from the binding source
* DSPSRVPGM listed export variables (data items) that were missing from the binding source
* There were procedures in the binding source that did not exist in the bound modules
I fixed all that, and it did not fix the signature.
I even tried using RTVBNDSRC to generate the binding source from the service program, changed the signature, and then recreated the service program using that source, and it still did not work.
Does anyone know what I may be missing?
Comment