|
Steve, I have tried everything that I can think of to resolve the problem.
maybe CRTPGM was used to recreate the bombing programs after the SRVPGM was created with EXPORT(*ALL) and before it was created with the binding source.
After I recreated the service programs correctly with new signatures, I recreated the programs using CRTRPGMOD and CRTPGM.
start with the error message. If it is a signature violation, display the help text and find the name of the service program it is complaining about. You can use DSPPGM to see what signature the program is expecting for each SRVPGM it references. And you can use DSPSRVPGM to see the signature of the service program. However the signatures got the way they are, they have to match.
It is not a signature violation - it is having a problem with some of the modules - getting bad data. For example, a module RTVCUSMAS is supposed to get a record from the customer master record.
depends on the error message. As long as you have not changed the order in which the MODULE modules and BNDSRVPGM srvpgms are specified there should not be a problem.
I only added a module to the end of the binder source. In the case of the service programs with some duplicate modules, I removed the duplicates, recreated those service programs and bound them with the service program that had the other required modules. Eric
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.