Use UPDSRVPGM to update the service program with any recompiled *MODULE(s), and that way UPDSRVPGM will preserve the current signature, rather than using CRTPGM.
Do NOT re-arrange the order of the exported procedures in the code, or insert a new exported procedure in between two existing procedures, etc.
The "rule" is to always add any new procedures on the end, and not "in the middle".
That is what the signature is trying to protect against or detect.
Mark S. Waterbury
On Monday, November 1, 2021, 02:28:56 PM EDT, Alan Shore via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
The problem is with how the object is promoted into production and the way the implementer parameters are set.
For the moment, I have left things as they are as all the programs have all been re-compiled and are working.
The next change to this service program will require a re-compile of all the same programs or UPDPGM for all of them.
At least I know what the cause was - and for that - thanks to all who replied.
IT Supply Chain Execution
60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx
"If you're going through hell, keep going." --Winston Churchill
As an Amazon Associate we earn from qualifying purchases.