NOTA BENE: if you just made "one line code change" to one procedure in one *MODULE in a service program, you could have used UPDSRVPGM to update the *SRVPGM with the new *MODULE and the signature of the *SRVPGM would have remained the same.
Mark S. Waterbury
On Monday, November 1, 2021, 06:44:47 AM EDT, Alan Shore via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
We are on V7r3
We have a service program that has 6 procedures
Last Friday, I had to make a change to one of the procedures - and that change was to insert one line of code into one procedure
Just to populate a field
Now - every program that uses those 6 procedures had a Program signature violation - MCH4431
As this is a relatively new service program - that number of programs involved is relatively small
So I just recompiled them - yes - I know I could have used UPDPGM
They are now working as expected
The binding program specifies a signature as well as the 6 procedures - in order
I am scratching my head as to why a signature violation happened
Any one any ideas as to what I can look at?
IT Supply Chain Execution
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.