×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
1. See if the joblog or compiler printout says which procedure is duplicated.
2. If it doesn't, then you'll have to go through each service program in the binding directories you use, looking at the exports [use DSPSRVPGM]. You will see the name of the procedure that is duplicated in multiple service programs. You mentioned you still had the compile problem after removing one of the binding directories. That may reduce the research a bit.
3. Once you locate the service programs, then locate the source of the procedure [the modules].
4. Verify that the source is identical. If the source for the procedures is different in each service program, then you'll need to investigate that too. Don't laugh, I've seen that before. Check the compiled modules too if you have the debug view set to save source.
5. Once you locate where the duplicates are, you can go on from there. You could create a one off binding directory with just the service programs you need, just to get it to compile, but that is just a band-aid approach in my view.
Hope this helps.
Doug
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.
midrange.com
