× 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.




On 24/01/2009, at 1:59 AM, David FOXWELL wrote:

If there were two different functions with identical names and (god forbid) identical parameters and the compile command stated to ignore duplicate name errors, would binding occur? Has anyone tried?

You will get a binding error. I don't recall the message ID.

You can work around that with OPTION( *DUPPROC | *DUPVAR) but that's a sloppy solution and you cannot control which of the duplicates the system will use--it will pick the one from the first module it encounters that contains that name but there is no method by which you can specify the behaviour.

As I recall, you've raised this topic previously and we've already told you the proper solution. Why are you persisting with bind-by- copy for everything? You should be using service programs. A single binding directory containing all the modules will mitigate your current problem caused by programmer-level binding directories but is, at best, a kludge to work around a problem caused entirely by using the wrong approach to ILE development.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.