Program signature violation error

When you call the program TESTP1, you get this signature violation error since the signature would have changed when you re-created the service program. So the service program automatically will export the exported procedures in the modules. The signature is based on this exported list of modules. When the service program is re-created with one or more additional module and related procedures, the signature also changes.

So to avoid this problem, we use another source type called the BND where you control the exported list. After creating this binder source no need to compile it or anything , the service program is created with the parameters modified as mentioned above. Comments and updates are welcome. Posted by Mahesh at PM. Newer Post Older Post Home. Subscribe to: Post Comments Atom. I am not getting signature violation error. Am I missing anything here.

Can someone please help me on this? Improve this question. Akshay Akshay 11 1 1 bronze badge. Are you sure you are looking at the service program signature ID in the same library that the program is? Add a comment. Active Oldest Votes. Improve this answer. Community Bot 1 1 1 silver badge. Charles Charles 18k 1 1 gold badge 15 15 silver badges 38 38 bronze badges. Best practice is to add functionality is to a new service program. You start doing the I can create a better signature dance and you will trip over your feet.

That's overkill Again, with hardcoded signatures, you set them once and forget about them. Take a look at IBM's service programs There is no argument here. If your adding add a service program zero business exposure. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back