|
On 12/8/06, Knezevic, Mihael <Mihael.Knezevic@xxxxxxxxxxx> wrote:
hi, i got a little problem with the binding of programs. but first some background. we have a test and production environment on one machine. each has its own lib (we call it test and prod here for the discussion). both libs are in the libl in the order: first test then prod (the machine is a devel machine). we are using a global binding directory for binding. the case: i'm working on a serviceprogram. the serviceprogram exists in it's old form in the prod lib and in it's new form in the test lib. another developer is working on a program which uses some procedures from my serviceprogram. during the development phase everything is working fine. now he promotes the program to the prod lib and the program gets the signature of the serviceprogram in the prod lib. seems ok so far. but now he calls the program (which is in prod) and it brings an error (MCH4431). translation: Invalid programsignature. it seems that the program tries to call the procedures from the serviceprogram in test (which is in libl before prod).
it is not that it is trying to call the srvpgm in test, it is that CRTPGM bound the program to the exports in the test service program. When the program calls a procedure in a srvpgm it uses the export number that existed at bind time. It is a good thing you got the signature violation. Otherwise your program, since it is calling by export number rather than name, would likely call a procedure in the prod srvpgm you did not intend. Bottom line is you have to learn about signatures and binding source. It is not that hard and once you know it you actually will understand srvpgms a lot better. That was my experience, at least. -Steve
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.